The document discusses opportunities and challenges of implementing SAP Solution Manager (Solman). It presents opportunities like reduced costs, improved visibility and control. Challenges include justifying business case and overcoming tool/process overlaps. The approach involves establishing outcomes, requirements, language and processes. A case study shows how Solman integrated tools and processes, improving visibility, management and reducing costs compared to previous separate tools.

1. So you’re thinking of implementing
SAP Solution Manager?
Opportunities, Challenges and Solutions
1 Copyright 2011 Issi / EOG

2. Our Agenda
Opportunities for Solman
– Sustainment
– Projects
Challenges in moving forward
Our approach to Solman
Our Solman services
Case study
– Before Solman
– After Solman
– Project overview
2

3. The Opportunities
For Sustainment For Projects
- Reduce total operating costs - Improve impact analysis
- Enhance visibility of activity - Increase use of best practices
- Increase change control - Reduce information risk
- Increase efficiency - Enhance scope management
- Reduce issue resolution time - Reduce Basis costs
- Improve problem management - Increase testing control
- Improve quality processes - Improve defect management
- Reduce Basis costs - Enhance migration processes
- Increase access to SAP AGS - Reduce handover costs
- Increase user satisfaction - Increase reusable elements
3

4. The Challenges
- Articulating the business case
- Overlaps with existing IT tools
- Confusing semantics / terminology
- Consensus on IT practices & processes
- Consensus on priorities
- Understanding of IT & Business roles
- „Work-in-progress‟ driven SAP changes
- Scope management
- Change management
- Access to Solution Manager skills
4

5. Our Approach
Establish
Define
Determine
Refine
Improve
5

6. Our Approach
Establish expected outcomes
– Your business benefits
Establish a common understanding
– Your requirements = Our scope
Establish a common language
– “SAPinese”+ “Solman-ese” + “ITIL-speak” + Your
terminology = Our language
Define organizational model
– Specifically for Solman - not a copy of ECC. Includes
detailed roles and responsibilities
Define business processes
– Step-by-step mapping of your processes to system
actions and statuses
6

7. Our Approach
Determine conversion strategy
– Changes/Transports, Tickets/Requests, Documentation
Old / New / All data
Determine cutover & rollout strategy
– Phased / Big-bang
Determine training & change mgmt strategy
– Resources, content, delivery, timing
Refine the solution
– Prototype core process flow
– Validate process readiness
Improve operations
– Stabilize system and data then refine processes
7

8. Where We Can Help
Strategy Delivery
Business case Design
Justification Project management
Business processes Configuration
Technical architecture Development
Scoping and planning Installation
Security
Support
8

9. Before and After
Solman Implementation Case Study
10

10. The Processes
Incident & Service Mgmt
Knowledge
management
Change & release
management
11

11. The Tools
Issue & Incident trackers
Documentation
repositories
Change & migration
tracking
12

12. Work Flow
- Email provides “collaboration” not integration
13

13. Integration
- Existing integrated process steps
14

14. Integration
- Existing manual process steps
15

15. The Problems
For Sustainment For Projects
Limited visibility of activity Reduce information risk
Limited visibility of changes Increasing Basis costs
Distributed knowledge base Cumbersome defect management
Redundant data sources Complex migration processes
Significant transition costs Significant handover costs
Problem management Minimal reusable elements
Improved quality processes Mapping to IT compliance
Increasing Basis costs
16

16. After
Solman Implementation Case Study
17

17. Tools and Integrated Processes
Issue , Incident & Problem Mgmt
Knowledge
Mgmt
Change & release
Mgmt
18

18. Workflow
Solution manager provides full integration!
19

19. The Benefits
For Sustainment For Projects
Enhanced visibility of activity Reduce information risk
Increased change control Enhance scope management
Increased efficiency Reduced Basis costs
Reduced issue resolution time Improved defect management
Real problem management Enhanced migration processes
Improved quality processes Reduced handover costs
Reduced Basis costs Increased reusable elements
Efficient project transition Mapping to IT compliance
20

20. Other Tools Replaced By Solman
Multiple SharePoint (documentation) repositories
– replaced by Solution Documentation
Enhancement request log
– replaced by Service Requests
Business requirements matrix
– replaced by table linked to Service Desk
Sustainment timesheets
– replaced by recording time in Service Desk
21

21. Project Overview
– 6 months duration
– Part time project team
– Delivery team
• PM, Solution Architect, Dev Lead, Basis, Security, 2
SAP developers, 1 interface developer, 2 trainers
– Client team
• 4 key users, 3 SMEs, 2 testers
– Lessons learned
• Not just a technical project!
• Leverage standard Solman where possible
• Additional emphasis on documentation, testing,
training & change management
22