Updated on 9-Jan-2024

Greenfield Primary system

Customer will
only get DR 4-6
customer with Long Distance start date same
weeks after
DR DR as DR start
Primary system
date
requirements CDD

DR start X
months after No issue.
Primary system

Primary system Primary and

Short Distance start date same DR system will
DR as DR start be deployed on
date same date.

CAA must submit

ECSCTOCH Ticket for
Azure approval. Post approval
END
CAA to use workaround
& architecture1
1Phasing of SDDR is possible under the GCP Refer subsequent slide
DR start X about agents /
below conditions: NW HANA connectors
months after
Systems
• If the landscape is built in PQA with Primary system
ASCS and ERS from day 1 then
phasing of SDDR can be done. Only allowed if with
workaround
• At the time of phased DR deployment, AWS architecture1
HA node and app servers will be Only Refer subsequent
added. No rebuild needed. Downtime slide about agents /
connectors
of 8-10 minutes may be required.
• The above is applicable for 99.7% NON-HANA
SLA scenario. NOT ALLOWED
Systems*

*For agents and connectors see next slides 1

 Updated on 9-Jan-2024

Brownfield Primary system

Customer will
customer with only get DR 4-6
Long Distance start date same
weeks after
DR DR as DR start
Primary system
date
requirements CDD

DR start X
months after No issue.
Primary system

Primary system Primary and

Short Distance start date same DR system will
DR as DR start be deployed on
date same date.

1Phasing of SDDR is possible under the CAA must submit

below conditions:
ECSCTOCH Ticket for END
Azure approval. Post approval
CAA to use workaround
• If the landscape is built in PQA with & architecture1
ASCS and ERS from day 1 then
GCP Refer subsequent slide
phasing of SDDR about agents /
DR start X
• At the time of phased DR deployment, NW HANA connectors Special
months after
HA node and app servers will be Systems Condition2
Primary system
added. No rebuild needed. Downtime
of 8-10 minutes may be required. Only allowed if with
workaround
• The above is applicable for 99.7% AWS architecture1
SLA scenario. Only Refer subsequent slide
about agents /
2There has to be a gap of 4 weeks connectors
between system status in DED changing
to LIVE and DR start date. DED status is
changed once the system is handed over NON-HANA
NOT ALLOWED
to ECS by customer/SI after migration of Systems*
each system. (Refer to the illustration
below)
*For agents and connectors see next slides 2
 Updated on 20-Dec-2023
Guidance for PCE Packaged
(SDDR, Phased SDDR & SDDR as Upsell for Agents/Connectors) The information in this page is
preliminary from ECS and might not
be available in the ESP (13-Nov) yet.
Component SDDR Status as per ESP Deployment for Phased SDDR Commercialization
AWS Azure GCP The subsequent release of the ESP
will be updated.
Will be deployed in Active-Active No additional costs as PCE Packaged pricing
DP Agent Yes
configuration from Day 1 file considers 2 VMs for PRD
Yes
These are stateless agents without
Will be deployed in Active-Active No additional costs as PCE Packaged pricing
DS Agent synchronization in Active-Active configuration.
configuration from Day 1 file considers 2 VMs for PRD
HA and DR have to be managed by the customer
via CPI-DS portal.
Costs of additional VM from day 1 is not
covered. Additional VM costs from day 1
Pilot Pilot Will be deployed in Active-Active until SDDR’s start date to be covered using
SAC Agent Yes
Ticket Required Ticket Required configuration from Day 1 “Connection Package PROD tier” SKU.
Connection Package needs to be added as
Short Term SKU (already initiated)
Yes
Costs of additional VM from day 1 is not
OT Cloud Connector on Windows
covered. Additional VM costs from day 1
Available as GA on SAP DC and all hyperscalers
OT Archive Cloud Will be deployed in Active-Active until SDDR’s start date to be covered using
for both LDDR and SDDR
Connector configuration from Day 1 “Connection Package PROD tier” SKU.
Connection Package needs to be added as
OT Cloud Connector on Linux
Short Term SKU (already initiated)
LDDR and SDDR on Pilot. ECSCTOCH ticket is
required for tracking

For PCE TO deals

Ensure the additional VM is priced for all the agents/connectors in case of phased SDDR scenario.

3
 Updated on 31-Oct-2023
A demonstration for customer who opts for phased SDDR with Brownfield provisioning.

Customer
Customer / SAP / SI Customer / SI SAP SAP SAP Customer / SI SAP SAP
/ SI

SI / customer
SI perform SAP
share S-Users SAP
Customer to migration & completed
credentials Conduct Build Phase handover
complete PPF Contract and
handover the the “post” & DR Build
Sales to (based on - Skeleton
& returned to Signed system to SAP set internal Phase
Installation Delivery CDD) System to
CAA for post status to
Number to Customer
CAA
processing “LIVE”

5 working days 5 working days 7 working days Depends on customer’s minimum 4 weeks
project timeline before start of DR

(Sales to Delivery)

Delivery Date)
Pre-provisioning form

(DR Start Date)

(Committed
1
(PPF) must be completed date
by customer and returned
to CAA before Contract S2D happen within 10 working days after
Signature contract signed. Any delay of the S2D will
impact to CDD as well.

Signing date S2D CDD DR CDD

Note:-
- Changes to the BOM / requirements might affect the timeline
- If IAE believes customer need more time to complete their part, then IAE should choose a later delivery date
- The working days above excluding Saturdays, Sundays
- This timeline is based on a standard build timeline, changes to standard build (e.g. BP activation; add. Languages) will leads to longer time.
1
- Customer / SI to ensure the Production system is LIVE (completed with SAP’s post-processing) at least 4 weeks before the start date of DR.

4
 Updated on 19-Feb-2024

Old PCE Customer with no CS /

ERS Split and upgrade to SDDR
with CR process / DR SKU
 Updated on 19-Feb-2024

Pre-requisite for

AS-IS TO-BE Upgarde to SDDR

downtime activity

Standalone SKU + DR SKU :

NW on HANA
Standalone SKU • Infra Costs are already
NW on HANA in DR SKU
• Additional Service for
CS ERS
Basic_1.8.20 : Split of
CS/CS CS / ERS (CDM to
request – CSP should
Split of CS be involved) – 10 hrs
of efforts from CSP (
PAS AI01 1370 Euro)

DB
HANA

DB01 DB02 Once the CS / ERS Split is

HANA HANA done Build can continue with
Upgrade to SDDR