Professional Documents
Culture Documents
April 2020
1
CLOUD@CORE
ALIGNED TO OUR CUSTOMERS’ CLOUD TRANSFORMATION
PURSUIT
Migration to AWS
S/4 HANA Carve-out
implementation on CI US customer on AMS
SoH migration
Added multiple AMS 2019
customers
2017
SNAPSHOT OF SIFY’S SAP OFFERINGS
Event Management
Cloud Technical Infrastructure Managed Recurring review of job and application logs
Services Services follow up of relevant error messages
Cloud integration (end-to-end monitoring)
Cloud S/4 HANA /ECC Cloud
Infrastructure Infrastructure Change Management
Technical change management
Integration management
Dedicated
• Flexible & scalable support models Onsite/Offshore Near-shore
• Cost effective – benefits of tools and automation model support
• Pro-active support
• Reduced person dependency knowledge process
framework
• End to end coverage from Infrastructure to
Applications
Shared pool
• resources
Performance dashboard
8
S/4 HANA IMPLEMENTATION AND MIGRATION SCENARIO
Brownfield
Migration/System
Conversion
SAP ERP with
Migrate to SAP S/4 HANA Release 1909
HANA (SoH)
Greenfield
New Implementation Legacy / SAP ERP New Installation of S/4 HANA Release 1909
WHAT DO THE CUSTOMERS ASK?
1 2 3 4 5 6
Maintenance Custom code
Pre-requisites Pre-checks SUM Post processing
planner migration
Database
Simplification list for S/4HANA
migration
Application
upgrade
Data
conversion
SAP S/4 HANA IMPLEMENTATION ACTIVATE METHODOLOGY
CARVE-OUT
Business scenarios:
• Mergers & Acquisitions
• Business specific carve-out requirements
Business 01
Acquired
Divested Business
Business Division
Division
Hybrid/Multi Cloud
SAP CLOUD OFFERING ON SIFY CI
CERTIFIED MULTI
MULTI DEDICATED APPLIANCE
DEDICATED On Demand TENANT
TENANT
VIRTUAL
VIRTUAL SHARED
SHARED
BARE
BARE METAL
METAL
pHANA vHANA
BARE
BARE
METAL
METAL
VPE
SAP-VPI
E5 E7 E5 E7
• Approx. 5-10 SAP landscapes with SAP ERP database size <2 TB.
• Projects implement S/4HANA as a greenfield option or Lift/shift existing HANA implementation on-premises as
well as customers upgrading SAP BW applications from AnyDB to HANA tend to fall in this category and a
Medium Segment typical
• Migration can take 4-6 months.
• Customers in this segment can generate 1 Cr – 2.5 Cr ARC per year including Managed Services
• Approx. 10-50 SAP landscapes with SAP ERP database size < 4TB and SAP BW systems that are implemented as
Scale out > 4TB.
Large Segment: • Projects include ERP to HANA or S/4HANA greenfield tends to be considered large in scope and a typical
• Migration can take 6 to 9 months to complete.
• Customers in this segment can range from 2.5 Cr – 6 Cr per year with Managed Services.
19
SAP ON AWS HYBRID CLOUD SOLUTIONS
Use Cases
o Lifecycle Distribution: Separate
Development and Test Environments
Enabled by Sify o Workload Distribution
Metro-X-Connect
Interconnect o High Availability Deployments
Business Benefits
o Best of breed performance with Hybrid
Cloud configuration
o Efficient integrations with extended
ecosystems
o Compliance with data sovereignty
o Business continuity with resilience
o Simplicity with self service
o Operational efficiency with reduced IT
administration
o Cost reduction with On-demand bursting to
public clouds
CASE STUDIES
CASE STUDY 1: FIELDFRESH– SAP MIGRATION/ UPGRADE & SAP AMS
FieldFresh Foods Private Limited is a joint venture between Bharti Enterprises & Del Monte
Client Pacific Limited. The company offers processed food and beverage products in India under the
Overview brand Del Monte and fresh vegetables in its export markets under the brand FieldFresh. It has
implemented the ERP software, SAP ECC6 EHP2.
Benefits Challenges
• TCO reduced significantly • Port opening for the New Cloud Servers.
• Improvement in SAP system and DB performance • Transporting the SAP Export from Source to Target Server
• Scalable (being on Cloud) • SAP Server Connectivity for both the Source and Target SAP servers
• Single window service for Infra as well as SAP services • Downloading the SAP Dumps and moving it to the Servers
• Knowledge Transition
LUCAS – SOH MIGRATION
Lucas Indian Service (LIS) established in 1930, is a specialist organization in sales and
Client service of "Lucas-TVS" auto electrical and "Delphi-TVS" diesel fuel injection
Overview equipment.
• Technical Upgrade from SAP ECC 6.0 EHP5 to ECC 6.0 EHP7 • ( Phase – I ) Performed EHP Upgrade along with Suite on HANA
• DB Migration from Oracle 11G to HANA 2.0 Migration at Single Step Approach using DMO Technique in SANDBOX
• SAP HANA DR Setup System.
• ( Phase – II ) Performed EHP Upgrade along with Suite on HANA
Migration at Single Step Approach using DMO Technique in DEV, QA &
PRD System
• ( Phase – III ) Setup HANA DR Replication for Production Server
Benefits
Challenges
• Improvement in SAP System with Latest EHP Level
• Key Business Benefits of SAP HANA like Performance, Efficiency,
• No VPN Connection provided by Customer to access their Network (Customer
Optimum Data Management, Simplification and Innovation. Provided only TeamViewer connection for the entire SOH Migration Project)
• Business continuity in the event of Primary Disaster • Source Production Server Hardware was Older and Lower Performance Disk I/O
which took more time to complete SUM tasks ( Ex : DDIC Activation Jobs ).
• 10 MBPS Link was provided between DC to DR replication. So, during Initial DR
replication of 500 GB Data transfer DC to DR took longer time to complete (5
days)
CASE STUDY 2: TRANSRAIL LIGHTING LIMITED – SAP MIGRATION,
UPGRADE & DR, BASIS ADMINISTRATION
Transrail business has been a part of Gammon India Limited before it demerged and
Client transferred to Transrail Lighting Limited. It was on SAP ECC6.0 , they wanted to
Overview upgrade to ECC 6.0 EHP 8 & migrate SAP to Sify Cloud.
• Migrate SAP landscape from On-premises Transrail to Sify Cloud. • Built the SAP DEV,QAS and PRD server from existing server in
• SAP Upgrade from ECC 6.0 to ECC 6.0 EHP 8. Transrail DC to SIFY Cloud and Testing has been carried
• SAP landscape to be moved from AIX/Oracle to Linux/Oracle. successfully.
• SAP ECC 6.0 EHP 8 (DEV/QA/PRD/BI-DEV/BI-PRD,DMS).
• Solution Manager 7.2 & SAP Router. • The End User connectivity for the New Cloud Servers.
• Sybase DB size 600 GB
• SRS replication methodology
Benefits • RTO: <=4 hours and RPO: <=30minutes
ONGC Tripura Power Company (OTPC) also known as Palatana Power Plant, is a thermal
Client power plant station in Palatana, Udaipur in the Gomoti district of the northeastern Indian
Overview state of Tripura. It is ONGC's first power plant in India & also the biggest Plant in Northeast
India. it has implemented the ERP software, SAP ECC6 EHP6.
Benefits Challenges
Benefits Challenges
• Implementing GST as per Government of India regulation • Last minute changes by Government in GST and subsequent
• Improvement in SAP system performance by regular AMS changes from SAP delayed the GST implementation
support • Training the users into GST related changes
• Coordination with client’s BASIS team - located in Germany
with 5 ½ hours of time difference
CASE STUDY 5: ESAB –SAP AMS
ESAB is the world's largest producer of standard welding equipment, consumables, and
Client automation equipment, as well as cutting machines and systems.
Overview it has implemented the ERP software, SAP ECC6 EHP4.
• SAP ECC6 EHP4 (DEV/QA/PRD/SB2/BIP) • Providing AMS support in SAP Security, GRC, BASIS tasks.
• SAP BASIS, GRC, Security, ABAP • Approximately 800 tickets resolved (in 10 months) without
any major escalations
Benefits • 804 SAP Active users in multiple locations
• Work orders resolution without SLA breach
• Structured role matrix, Adherence to SOX rules, Efficient SOD matrix. • Emergency support in weekends and non support window.
• 24x 7 Technical and Managed SAP BASIS services delivery capabilities
• Monitor risk within the SAP environment.
• Project stakeholders with guidance in regards to application Challenges
maintenance, security design.
• Fixing issues in customised reports, forms.
• Interfaces (File Handling) • Mass Role revamping at the time of user access review audit.
• Forms Development and Support (Smart forms and Adobe forms). • Extended GO-Live support for Bowling green location.
• Enhancement Support (User Exits, BADI, BTE, Enhancement • Supporting for GRC implementation and new role testing.
Framework).
• Data Conversion Techniques Development and Support (BAPI, BDC,
LSMW)
CASE STUDY 6: RCI INDUSTRIES – S/4 HANA IMPLEMENTATION & AMS
RCI Industries and Technologies Limited is a private company which offers Indian
Client handicrafts, specially made by Copper & Brass metals. It also has copper strips and copper
Overview wire as its product. Sify is implementing the ERP software, SAP S/4 HANA 1610 FSP2 at RCI
Industries and technologies limited.
• Implementation of SAP S/4 HANA 1610 FSP2 on cloud solution • Implementing the SAP DEV,QAS and PRD server on Sify Cloud
• Landscape design SAP S/4 HANA 1610 (DEV/QA/PRD) • Documented AS IS - TO BE process for business
• Documenting business process • Configuration of SAP S/4 HANA FI,CO, MM, SD, PP, PM, PS, HR, Basis,
• ABAP modules
Mapping business requirements in SAP
• Developing custom programs for process enhancements
• Fiori apps, output and reports • Developing Fiori application for analytical and transactional requirements
• S4HANA – AMS & books closure for 4 Quarters • 100 No of Users
• 200 Man-days AMS support
• 20 No of CR’s completed in AMS period
Benefits Challenges
• Rollout the Rittal HCM process into Eplan • Replicating the Rittal HCM scenarios to Eplan (newly acquired
• Implementation of temporary workers with Rittal full time company)
• Updating & migrating of master data into the newly rolled out HCM
system
• Capturing the punch in and out timings of the temporary workers
in SAP HCM payroll system
• Canteen management - linked to the salary component for the
amount of food items the employees consume
Benefits Challenges
• Rittal and Eplan employees coming under single HR umbrella • Master Data validation, correction, upload, training end
• Automation of canteen and the canteen meal passes and direct users on SAP as Eplan was using Tally before this
links to SAP HCM salary master transformation
• Migration of legacy excise based pricing procedure to GST • Identifying the appropriate approving authority in Eplan
based procedure • Integration of finger swipe machine installed in canteen
with SAP system
CASE STUDY 8: EMAMI CEMENT – SAP S/4 HANA DR
A well-know diversified group with strong manufacturing operations. It has chosen SAP
Client S/4 HANA as ERP for the backend operations.
Overview
• This is a greenfield SAP S/4 HANA implementation. • Phase 1: One SAP HANA SP10 physical box for QAS and
• Infrastructure provisioning for SAP DEV,with 7 VMs, another SAP HANA SP10 Production Physical
• Managed Services(OS, Virtualization) box with 3 VMs & Phase 2 - BI/BW 7.4 provisioning completed
• Managed Backup Services. • Phase 3: DR needed after 18 months
• Network &Security Services. • Implementation DC location – Navi Mumbai (Rabale).
• Disaster Recovery setup for SAP HANA Production System. • Implementation DR location – Bangalore.
• HANA DB size 350 GB
• RTO: <=4 hours and RPO: <=30minutes
Benefits Challenges
• This solution is aligned to client’s business objectives. They • Minor issues in Data Centre Readiness
wanted to leverage S/4 HANA’s Simple Finance offering, • There were some issues in ‘last mile’ connectivity (client
besides the usual SAP ECC core modules office in Chhattisgarh)
• Single window governance of Infra.
CASE STUDY 9: LUX INDUSTRIES LTD – SAP HANA DR SETUP ON AWS
• Disaster Recovery setup for SAP HANA on AWS cloud • We managed the entire project for setup HANA DR, working
• Infrastructure provisioning for SAP HANA with multiple vendors (Win for OS, SAP components, & HANA
• Managed Services(OS, Virtualization & HANA DB) replication)
• Managed Backup Services. • We helped Lux integrate the proposed new setup with their
• Network &Security Services. running production for Stand by Production system as DR
• Implementation location – AWS (Mumbai)
• Monitoring the DC and DR Sync
• Application and DB level patch upgrades.
Benefits • Managing the DR Drills.
• RTO: <=4 hours and RPO: <=30minutes
• Business continuity in the event of primary disaster
• Stand by for Production system
• Maintain application availability during planned and unplanned Challenges
downtime.
• Avoid data loss • Some issues due to late delivery by hardware vendor
• SLA-managed committed service Delivery • Coordination between vendor/s and internal teams
CASE STUDY 10: TATA SPONGE – SAP CARVEOUT
Tata Steel is currently the world’s second-most geographically diversified steel producer.
Client TATA STEEL has purchased steel business from UML (Usha Martin Limited). As the part of
Overview agreement and out of statuary requirement, business specific data required to move to
new system landscape.