Post on 11-Apr-2018
Agenda
• Our Solution Manager journey
• Status before upgrade
• Upgrade decisions
• The upgrade process
• The go-live weekend
• Next steps
2
Our SolMan journey
• July 2008: Live with ChaRM and Service Desk
– All transports for ERP
– SAP Incidents
• July 2008 – March 2010
– Added WM & BI transports
• March 2010
– Replaced SolMan service desk with CRM ITSM
– SolMan integration from CRM RFC -> SolMan change document
• March 2010 – Dec 2012
– Added CRM & GRC10 transports
– BPM
– CDMC 3
Status before upgrade – Transports
4
ChaRM with CTS project set as compulsory
DEV
QA
DEV DEV DEV DEV
PRD
QA
PRD PRD PRD PRD
QA QA QA
ECC BI WM CRM GRC
Status before upgrade – Workflow
5
SAP
SolMan
standard Pioneer standard
CRM: Incident/Service request
CRM: Request for change SolMan incident
SLFN
SolMan change request
SDCR
SolMan change
doc SDHF
SolMan change doc
Z1HF Low risk
(Trp daily)
SolMan change doc
Z2HF High risk
(Trp weekly)
SolMan change doc
Z6HF Finance appr. (Trp weekly)
Status before upgrade - BPM
• Monitors running for following processes
– Sales
– Procurement
– Plant maintenance
– Key background jobs
• BPO’s in business responsible for thresholds
• Business used the BPM Work center
• Accessed detailed results in ECC
6
Status before upgrade - General
• Everything was working great
• Stable system – almost no changes
• Well ingrained and adopted
• Business was getting excited about BPM
• Why would you change it?
7
Upgrade decisions
• Business drivers for upgrade
– SolMan 7.1 end of maintenance Dec 2013
– New functionality – Monitoring cockpits
– BI 7.3 upgrade requirement on SolMan
• Complicators
– ChaRM: Upgrade or new installation?
– Timing (start and go-live)
• Crucial due to impact on config & development
• Current project development & go-live’s
8
Upgrade decisions
Goal
To do a technical upgrade with minimal/zero impact on users and current
processes
9
Upgrade decisions – What impacts goal?
10
SolMan
7.0
SolMan incident
SLFN
SolMan change request
SDCR
SolMan change
doc SDHF
SolMan incident
SMIN
SolMan change request SMCR
SolMan change
doc SMHF
SolMan
7.1
New doc type
New doc type
New doc type
• Data migration
• Action changes
• New screens
Upgrade decisions – address goal impact
• No data migration needed – we used “Z” doc types
• Staying on “Z” docs meant no changes to actions
• We could stay on GUI – no immediate need for WEB UI – determined by auth’s
• Goal achieved!! Well, at least for ChaRM
11
The upgrade process
• Started in mid December 2012
– Perfect solution for skeleton staff
– Basis & SolMan teams (2 from each team)
– Preparation steps & documentation
• Mid Jan – DEV (landscape freeze)
– 3 weeks to complete upgrade
– Testing issues:
• Authorisations
• BPM
• Basis (system monitoring – DSWP moves to work center)
12
Go-live weekend
Upgrade Prep Phase
18.02.2013 Prerequisite checks and preparation (SIM comp) 4 days
Start downtime & pre-apply steps
Thursday 21.02.2013 18:00 Shut Down and Back-up
1 hour
Clone SolMan PRD
21.02.2013 19:00 Upgrade SolMan PRD 48 hours
23.02.2013 19:00 Run S-Gen for SolMan PRD 12 hours
24.02.2013 07:00 SPAU Transports to SolMan PRD 1 hour
24.02.2013 08:00 Back-Up/Clone Upgraded SolMan 1 hour
24.02.2013 09:00 SolMan_Set-Up (Initial Configuration) 16 hours
Monday 25.02.2013 01:00 System verification 3 hours
13
Next steps
• Determine BI strategy for SolMan
• Cutting BI team over to new web UI
– Process chain monitoring
– DVM cockpit
• Strategy for CRM ITSM vs SolMan ITSM
• Conversion to new doc types
– Do we really need history if it is in BI?
– What do we have that we really need to keep?
• Identity new actions on change docs
14