chemtura archives and carves out data to reduce risk · pdf fileteched 2016: itm211 -data ......
TRANSCRIPT
Chemtura Archives and Carves Out Data to Reduce Risk for Move to SAP HANA
BITI7181
Jim Prins, ChemturaKatharina Perigo, Dolphin
Jim PrinsVP-Director Of Technology, LanXess
James (Jim) Prins is an IT Leader managing internet and enterprise applications and the on-site and offshore teams that build, enhance and support them. He is responsible for Basis, Compliance, IT Operations and Custom Development.
Katharina Perigo Principal Data Consultant, Dolphin
Katharina has almost 20 years of experience with SAP systems, specializing in information lifecycle management strategies. She has worked with some of the largest and most complex SAP systems in North America and Europe.
4
Speakers
• About Lanxess
• Why Data Volume Management?
• Divestiture & Data Carve Out
• Results
• Wrap Up
Agenda
6
Spin-off from Bayer in 2004
Specialty chemicals portfolio: plastics, rubber, intermediates and
specialty chemicals
75 sites worldwide
Approximately 19,200 employees in 25 countries
Global sales of EUR ~9.2 billion in 2016*
Enhancing its leading position in mid-sized markets
Chemtura is Now LANXESS –A globally operating specialty chemicals company
Specialty chemicals company
Global success story
Strategy of profitability and resilience
*Combined sales of LANXESS and Chemtura in 2016
7
Successful transformation – Latest Chemtura acquisition strengthened our engineering materials position
Our path towards the New LANXESS
Restructuring
C&D Acquisition
Ongoing business and
portfolio improvements
ARLANXEO operational
Energizing Chemistry!
Acquisition
Petroleum Additives
Urethanes
Great Lakes Solutions
Organometallics
8
2014 Divestiture
Remove divested data to reduce cost & complexity
of move to SAP HANA
Business view
IT view
Agrochemical data
Chemturadata
SAP
• About Lanxess
• Why Data Volume Management?
• Divestiture & Data Carve Out
• Results
• Wrap Up
Agenda
Needed an information management strategy to:• Remove data from divested company• Reduce system size to rationalize the
cost of transitioning to HANA in 2016
Goals for SAP System: • Smaller• Less Costly• No Loss in Business Functionality
10
Business Drivers for Data Management
Agrochemical data
Chemtura/Lanxess data
SAP
8 TB System growing at
11 GB per month
A significant percentage of the data in existing SAP systems is old or obsolete.
• Slows down SAP system performance
• Increases maintenance time and effort
• Increases TCO of SAP systems
11
The Need for Data Management
TechEd 2016: ITM211 -Data Volume Management in the Context of SAP S/4HANA Conversions
~50%of data in SAP
systems is 2 years old
or older
22% of data is related to
basis objects
33% of the largest ERP
tables are custom (z-)
tables
Archiving Reduces Data Volume in On Line Systems
Control Data Volume Growth with Archiving
Y10Y9Y1 Y2 Y3 Y4 Y5 Y6 Y7 Y8
On
line
Time
Arc
hiv
e
Data Archiving Moves Static Data to Archive Storage
Data Growth in Production SAP Systems is Controlled
Phased approach enabled company to achieve goals without disrupting business:
1. Get rid of data the company did not need
• Reduce size of SAP system by removing technical/binary data (iDocs, MSDS documents, etc.)
2. Relocate the non-operational data to less expensive archive storage
• Automate the archiving process to ensure consistent data volume management according to policies
3. Provide seamless access to archived data for business users
• Maximizes the potential to archive operational data and positions company for future data management initiatives
14
Phased Approach to Information Management
15
Project Timeline
March2015
May 2015
Technical
Archive & Doc
Migration Begins
Removed
~3 TB of
data &
documents
Phase 1:
Data Volume Management
Jan 2017
Removed
~1TB of data
March 2016
Phase 2:
Data Carve Out
Data Carve
Out Begins
HANA compression reduces data
volume
S/4HANA
Conversion
Begins 8TB 5TB
+3TB
+1TB
Phase 3:
Future Data Mgmt
Data reorg
further reduced
data by ~1 TB
Oct 2016
Oct 2016
Total Reduction of ~7 TB
Conducted an analysis with Dolphin to determine best approach.
Recommendations:• Archiving of Technical Objects to
regain ~20% of database• Replace aging content repository
which was costly to maintain • Migrate documents to new
repository
16
Database Analysis & Blueprint
Phase 1: data clean up and technical archiving • Established the infrastructure & team
necessary for future information management
To demonstrate value quickly:• Selected top 8 archiving objects • Identified tables with fastest growth• Estimated savings from the archive
17
Information Management Strategy: Phase 1
Small staff of IT employees that manage strategy and governance
Archiving is a well defined and contained project that doesn’t touch a lot of areas
Sought to partner to provide archiving services
Engaged partner with expertise to complete the projects quickly
Comprehensive archiving solution with products and services
Only billed for hrs we use – this is HUGE as when the project was paused due to business push back – would have impacted project costs
18
IT & Information Management Partner Strategy
~3.5 TB removed from system
through data archiving
and document migration
19
Phase 1: TimelineJanuary
2015
Ongoing archiving efforts to sustain
benefits of data reduction
IDocs
Migration
Logging
Workflow
March 2015
May 2015
Analysis & Planning
Server Built
Reorg
• About Lanxess
• Why Data Volume Management?
• Divestiture & Data Carve Out
• Results
• Wrap Up
Agenda
Divested business was consumer focused with lots of transactional data
14 million+ documents related to divested company codes
65% of total system data was related to divested business
Decided to carve out data to reclaim space
21
ILM Strategy: Phase 2
Org. Entity
Plant List OtherField-level
(as required). . .
Date Range
Phase 2: Carve Out Requirements
Company Code
Sales Org.
Example: Fiscal Years 2000-2014
Example: Jan 1 – May 31, 2011
Wholesale • Customer
• Vendor
Materials
• Name 1
• Name 2• Credit Card
• SSN
• Date/Time
Required Criteria
• Optional
Implemented Archive Accelerator (ACA) solution to manage carve-out of data
Identified ‘In-scope’ data parameters for carve-out by object
23
Phase 2: Accelerated Carve Out of Divested Business Data
• Archive Accelerator
24
Data Volume Management Solution Components
Schedule all configured
Archiving objects
Monitor Progress of
Archiving jobs
25
Phase 2: Timeline Dec
2015
Archive Retrieval enabled for
Accounting Documents &
Material Documents
Accounting Documents
Controlling Line Items
Sales & Distribution
Purchasing
May 2016
Aug 2016
Analysis & Planning
Prototype ~1.2 TBCarved-out
Carve-out in Production
Material Documents
Testing reveals company code should NOT be included
Identified compliance requirement to retain access to archived accounting information (data and documents) for divested company
Due to a bug in SAP archiving the archive flag was not set. Had to apply OSS notes to get through the S/4 data conversion: 2225321 2225322
26
Phase 2: Project Gotchas!
Archive Add Ons Provide Easy Access to Online and Archived Data to Minimize Disruption to the Business
Phase 3: Seamless Access to Archived Data
Selection results
Online data
Archive data is indicated
with an * in the “A“column
Totals from
archive + database
• Why move to SAP HANA?
• About DPSG and the Journey to SAP HANA
• DPSG Data Volume Management Strategy
• Results
• Wrap Up
Agenda
29
Divested Business Carveout
Dolphin executed archiving jobs, provided regular status updates and throttled jobs to preserve system performance during project.
30
Data Volume Management ResultsStarting PointStarting Type Size (TB)Data eligible for Archiving (Phase 1) 2.5
Fragmentation 1
Consumer data eligible for Archiving (Phase 2) 1.2
Required Data 3.05
Free Space 0.3
Total 8.05
End PointEnding Type Size (TB)Required Data 3.05
Free Space 5
Total 8.05
5 TB of free space created
through data volume
management initiatives
31
Project Timeline
March2015
May 2015
Technical
Archive & Doc
Migration Begins
Removed
~3 TB of
data &
documents
Phase 1:
Data Volume Management
Jan 2017
Removed
~1TB of data
March 2016
Phase 2:
Data Carve Out
Data Carve
Out Begins
HANA compression reduces data
volume by almost 2 TB
S/4HANA
Conversion
Begins 8TB 5TB
~3TB
~1TB
Phase 3:
Future Data Mgmt
Data reorg
further reduced
data by ~1 TB
Oct 2016
Oct 2016
Total Reduction of ~ 7 TB
• Why move to SAP HANA?
• About DPSG and the Journey to SAP HANA
• DPSG Data Volume Management Strategy
• Results
• Wrap Up
Agenda
Difficult to realistically size until you do the conversion to SAP HANA. How much hardware do you need?
SAP sizing tools are more accurate if you reorg your database first. Initially sized the database at over 3 TB. After reorg only needed
1.5 TB
Bugs in SAP archiving did not flag data as having been archived. (no archive indicator) Had to apply OSS notes to get through the S/4 data conversion
33
S/4HANA Conversion Considerations
The move to SAP HANA required information management to keep costs reasonable.
Don’t just consider the size of the production production system. Need to consider costs for all the systems in your environment (Dev, QA, etc.).
Licensing is complex – some options are dependent on data volume
Taking 1 TB out of the database takes 3 TB of RAM out of hardware, this results in HUGE savings when you move to HANA
Cost Savings from Managing Data Before Moving to SAP HANA
Identify business owners and communicate their role in the project early. Don’t make it just an IT project
Identify the business benefit. Why are you doing this?
What’s in it for the business users? The data in the live system will still be available once it’s archived
Estimate the savings. Users understand that they will have to give up something to get that benefit. Stay focused on my experience
If accessing archived data from a standard SAP transaction, then custom reports need to be retro-fitted
Need to weigh the risk of access to archived data and whether those reports need to be enhanced. This is particularly true for consumer data
35
Communications Strategy & Risk Considerations
1. Include the business early in the process and include them in decision making and testing.
2. Technical objects provide an easy way to start information management projects and set the stage for future archiving of business objects.
3. SAP Data Archiving is a unique skillset, get the right resources to ensure success.
4. Be prepared for delays – the better your communication strategy the easier it will be to keep everyone on track.
5. Don’t forget to test. Testing can be complex and you need to have enough time and the right resources to do so.
6. Automated archiving significantly reduces time and effort required to carve out data, which is essential when there are legally binding deadlines.
7. Data management should be considered early in the lifecycle of every system.
36
7 Take Aways
5© 2016 Dolphin
37
Focus: SAP Customer Only
Proven: solutions for the SAP customer leveraging SAP technology and certified by SAP
Stature: 1/3 of all Fortune 100TM companies running SAP are Dolphin customers
Stability: Employee owned; private; independent of other stakeholders; organic growth
Longevity: Established in 1995
Global Solutions : Hundreds of scalable, flexible and cost effective deployments
ABOUT DOLPHIN
Insert Presentation TitleInsert Speaker Name(s)
& Company
Chemtura Archives and Carves Out Data to Reduce Risk for Move to SAP HANA
BITI7181Jim Prins, Chemtura
Katharina Perigo, Dolphin
Thank you for attending my session!
For questions, contact me at:
Don’t forget to fill out the Session Evaluation on the Mobile App!
Follow Us
Thank you for your timeFollow us on at @ASUG365