| Status | |
| Owner | WENNINGER-ext, Sascha |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Succinctly describe the issue or problem statement that this Decision addresses. Why is a decision required? What business or technical problem does it address?
Summarise the recommendation being made for the reader, leaving the pro/con evaluation and exact decision-making process to the subsequent sections.
Explain the context in which the decision is being made.
Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited.
Capture any constraints or limitations inherent to the recommended option. This could be aspects which, if changed or removed in future, could cause the decision to be revisited or invalidated. For example, a constraint might be that a new product has significant gaps in important functionality, which caused an older alternative to be recommended. If those gaps are closed in future, this might cause the decision to be invalidated.
Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.
The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order".
List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.
Option A | Option B Located in EU | |
|---|---|---|
| Legal/regulatory requirements for data localisation |
|
|
| Internal legal support, inc. data export and data processing agreements |
| |
| Availability of SaaS applications | ||
| Depth and breadth of technology platform components | ||
| Network latency impact for end users | ||
| Carbon footprint | ||
| All major IaaS providers purchase electricity via long-term purchase agreements from power utilities, often under direct purchase agreements which favour renewable energy, rather than obtaining power directly from the national grid. They also tend to purchase renewable energy offsets for a large part of their operations (e.g. in 2023, AWS offset 100% of their carbon emissions in 22 Regions). Their actual CO₂ footprint is thus likely to be quite different to that of the national grid. | ||
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
List of SAP Data Centres for SAP Cloud Services
Maps showing the carbon intensity of the electricity grid by geography
A summary of the List of SAP Data Centres for SAP Cloud Services for products and services relevant for Syensqo is represented below. The information for this summary table was retrieved in September 2024, using the then-current version v.9-2024 of the document.
Available of a product or service in only a single region in a particular geography may limit the Disaster Recovery options available for that service. This is thus represented as a paler shade of green in the table below.
| Product | EU | US | China |
|---|---|---|---|
| AI | 2 | 4 | 1 |
| Application Development and Automation | 3 | 8 | 1 |
| Customer Data Solutions | 2 | 2 | 1 |
| Data and Analytics | 3 | 7 | 1 |
| Data Custodian KMS | 1 | 2 | 0 |
| Foundation / Cross-Services | 4 | 8 | 1 |
| Integration | 3 | 8 | 1 |
| Miscellaneous | 4 | 8 | 1 |
| RISE with S/4HANA, Private Edition | 17 | 18 | 6 |
| SAP Advanced Financial Closing | 1 | 1 | 0 |
| SAP Ariba | 1 | 1 | 1 |
| SAP Ariba Buying | 1 | 1 | 0 |
| SAP Asset Performance Management | 2 | 2 | 0 |
| SAP Business Network | 2 | 2 | 1 |
| SAP Cloud ALM | 2 | 1 | 1 |
| SAP Cloud for Customer | 1 | 2 | 0 |
| SAP Concur | 1 | 1 | 1 |
| SAP CPQ | 1 | 1 | 0 |
| SAP Digital Manufacturing | 2 | 2 | 0 |
| SAP Document and Reporting Compliance Cloud | 1 | 0 | 0 |
| SAP Sales & Service Cloud v2 | 1 | 1 | 0 |
| SAP SuccessFactors | 6 | 6 | 1 |
| SAP Sustainability Control Tower | 1 | 1 | 0 |
| SAP Test Automation by Tricentis | 1 | 1 | 0 |
