Status
Owner	MUTHUSAMY-ext, Kunalan
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Introduction

Purpose

The purpose of this document is to outline the detailed design of the BlackLine application, components, configurations and landscape.

Scope & Objectives

This document will describe the high-level architecture of BlackLine application and integration with other components.

Out of Scope:

Since BlackLine is a SaaS aaplication, network and infrastructure architecture will be considered as out of Scope.
Information related to product documentation and can be found online will not be documented here.

Key Decisions and Requirement

Description	Rationale
Configure SSO for S/4HANA.	As part of SyWay project, a common authentication mechanism (e.g., SAML) will be adopted for ease of access and unified user experience.
Users must access BlackLine using HTTPS.	Synesqo cybersecurity requires all data in transit to be encrypted.
Data stored in BlackLine must be encrypted.	Synesqo cybersecurity requires all data at rest to be encrypted.
BlackLine must have appropriate data protection.	BlackLine performs data backups regularly so that point in time recovery can perform to recover data. Additional, backups must be replicated to another site to protect against a site disaster.

Application Architecture

Application Architecture Design

Insert the Architecture design below. Architecture can be designed in either Visio or word or another format.

Application Architecture Components

Provide the details of each and every major component used in the Application Architecture. Below are some of the sample application components provided as a reference.

Web Dispatcher

Provide the details of Web dispatcher

Gateway Server

Provide the details of Gateway Server

S/4HANA

Provide the details of SAP ERP Central Component

ADFS

Provide the details of ADFS

Application Security

Classification

Security configuration or hardening depends on the classification and the associated risks. Security controls are implemented depending on the classification of the data per IT policy and risk management policy.

Authentication

Provide the details of authentication architecture used for the application

Authorisation

Provide the authorization guidelines/principles followed for the application

Communication Security

Provide the details of the communication security controls implemented based on the classification

Data Security

Provide the details of the data security controls implemented based on the classification

Other Controls

Provide the details of any other controls implemented based on the classification

System Landscape

Development Environment

Include the DEV environment details

Project Test Environment

Include the Project Test environment details. Mention Not Applicable, if the environment is not relevant for the application

Quality Environment

Include the Quality environment details. Mention Not Applicable, if the environment is not relevant for the application

Production Environment

Include the PROD environment details

Operation Architecture

Change and Configuration Management

This section will include the details related to change and configuration management of SAP and non-SAP systems.

Transport Management

Provide the details on how transport management will be handled

Release Management

Provide the details on how release management will be handled

Monitoring

This section will include the details related to monitoring enabled for the application

Application Monitoring

Provide the details of application monitoring configuration

System Monitoring

Provide the details of System monitoring configuration

Sizing

Provide the details of sizing approach and the future recommendations

High Availability

Provide the details of High Availability. You may provide a reference to other document or attach a document, if the section contains lot of content

Disaster Recovery

Provide the details of Disaster Recovery. You may provide a reference to other document or attach a document, if the section contains lot of content

Backup/Restore

Provide the details of Backup/Restore. You may provide a reference to other document or attach a document, if the section contains lot of content

Maintenance Plan

Provide the details of system and application maintenance plan. This should follow the upgrade strategy

Service Introduction

Application Category

Provide the details of application category based on application classification. Application category is defined based on RPO, RTO requirements

Support Team

Provide the details of support team that may be required to support the application

Skill required

Provide the details of skills that are required to support this application

Checklist

Provide the checklist for support organization to support the application

Exceptions

This section covers any exceptions to the reference architecture. Some Applications may have limitations and may not meet the Enterprise Architecture, Reference Architecture and IT Policy guidelines. All exceptions should be included in this section.