Transcript Title

David Platt, Chevron Corporation
Pavan Manocha, Independent
]
Extending the Use of SAP Solution Manager
into Modeling, Testing and Training
SESSION CODE: 3104
[ LYNN LUPO
SAP POINT OF CONTACT
MEMBER SINCE: 2000
[ PAUL SHEPHERD
ASUG INSTALLATION MEMBER
SINCE: 2003
[ ANDREA BENSON
ASUG INSTALLATION MEMBER
MEMBER SINCE: 2003
[
Learning Points
 Benefits of an Integrated Tool Suite on a Global
Project
 Use of Solution Manager at Chevron
 Tool Related Key Learnings
 Best Practice Recommendations
2
Who We Are
[
Introduction
 David Platt – Manager, Business Systems
 8 Functional teams, 4 global locations (250 FTEs)
 Experienced Project Leader in Corporate,
Upstream, Downstream and International Systems
work (25 Years in IT)
 Enjoying 6th SAP Project since 1997
 Pav Manocha – SAP Project Management
Specialist
 15+ years SAP Downstream integration
experience
 Multiple global full-lifecycle implementations
 Independent advisor
 Global Design Architect
 Project Manager, PMP
3
Who We Are
[
Chevron is an Integrated Energy Company
2nd largest
U.S.-based integrated
energy company
$22.9 Billion
Capital budget
for 2008
$18.7 Billion
2007 Net Income
62,000+
employees worldwide
4
Chevron
Headquarters
(includes Global
Upstream & Gas and
Downstream
headquarters)
* In some cases, one dot
designates multiple locations
Who We Are
[
Chevron and SAP Software Usage
SAP




Corporate
Downstream
Global Gas
Upstream
Domestic
12 Instances
Versions
 4.6c
 4.72
 6.0
43,000
SAP Footprint
Oracle JD Edwards Footprint
Ariba Footprint
5
Physical Installations
Users Worldwide
What Our Project Was
[
Project Olympic is a Global Post-merger SAP
Systems Consolidation & Standardization Initiative
End-to-End
Process Areas
Project Olympic
6
SALES
FUEL SUPPLY
LUBRICANTS SUPPLY CHAIN
PROCUREMENT TO PAYABLES
FINANCE
HUMAN RESOURCES
What Our Project Was
[
Timeline
2007
Apr
Jul
We Are
Here
2008
Sept
Dec
Jan
Apr
Jul
HR Final Prep HR
HR
Cutover
Go-Live & Support HR
Realization
Release 1
U.S.
Final Prep U.S.
Cutover
Go-Live
Release 2
Africa
Realization (Asia and Africa)
Final Prep Africa
Cutover
Go-Live
Release 3
Asia/
Pakistan
7
Realization Asia
Final Prep Asia
Cutover
Go-Live
[
Key Learnings
 Integrating Our Project Tool databases proved
invaluable
 Maturity of Solution Manager & ARIS integration
tools in 2004/05 raised risk level
 ARIS flowcharting required more up-front work
than expected
 We reversed key step to integrate with Solution
Manager
 Many aspects of Business Models were used
extensively throughout Project Lifecycle
8
Our Approach
[
We Integrated the Following Tool Databases
Web Based
Central Storage
Non-Web
SAP
HP/Mercury
Quality Center
SAP GUI
OnDemand
Training
Software
Solution
Manager
ARIS Browser /
Review Tool
ARIS
Database
MODELING
METHODOLOGY
Processes
Olympic Manager
Web Front-End
9
Olympic (ERP)
Estimating Model
Methodology
Role-to-User
Mapping
PROJECT
MANAGEMENT
ARIS
Microsoft
Project (MSP)
Browser
Olympic
Manager
Database
WBS & Actuals
Deliverable
Assignments
Plan Generator
Team Plan
MS Project
MS Project
Enterprise
Our Approach
[
Roles of Global Integrated Tool Suite
Application Lifecycle Methodology
Project
Prep
Blueprint
Realization
Olympic Manager
IDS Scheer ARIS
Business Model
Model To-Be BP
Final Preparation
SAP SolMan
Go-Live
and Support
HP QualityCenter
Continuous
Improvement
ETL / Manual
Create Blue Print
Define Quality PreReq
Build Requirements
RICEF Inventory
Write Test Plan
ComposeTest Cases
Create Test Data
ASAP+ WBS
Execute Test Cases
Modify Config
/ Custom Code
10
Log Defects
Analyze Results
Our Approach
[
High-Level View Solution Manager Usage
 “Portal” view into all
configuration
 Link Sub-Processes to
Configuration Transactions
 Tracking statistics
 By Sub-Process
 By IMG Area
eRoom
Config
Design
Solution
Manager
 Documented
during Detail
Design
 All updates to
configuration
should be made
to the original
files
11
R/3
 Direct links
from Solution
Manager
APO
 Start config
through the
SM portal
BW
 Once config
complete,
update status
in SM to
Aspen
Ariba
 No link from
Solution
Manager
 Solution
Manager only
used to track
status
Our Approach
[
Usage of Solution Manager
at Chevron
 Solution Manager was one of several
implementation tools
Test
 Its primary usage was in:
Test
Knowledge
Management
Management
Management
 Change Control Management
 Configuration Status
Project
Solution
Mgmt.
Monitoring
SAP
 License Management
Solution
Manager
 Solution Manager was not used for:
Service
Knowledge
 IT and applications support
Desk
Transfer
 System monitoring
Service
Change
Delivery
Management
 Service level management
and reporting
IMPLEMENT
OPERATE
OPTIMIZE
12
Our Approach
[
In ARIS 6.23 We Did As-Is and To-Be
Business Models
Some Scope Stats:
 Process – 14
 Sub-Process – 99
 Activity – 657
(Workstep &
Transaction level)
13
Our Approach
[
14
We Loaded the Business Model into Mercury
Quality Center to Manage Test Phases
Our Approach
[
Integrating Business Model into Testing Tool Gave
Us Traceability and Risk Assessment
 When the inevitable “Testing Scope Cuts” traceability was
key to developing revised risk profile.
Key
75 - 100% in scope
50 - 75% in scope
25 - 50% in scope
1 - 25% in scope
Out of scope
TBA
NA
15
US - RICE Regression Test
ME
N/A
Localization
Comparison**
Operational R2
1
Supply Network Planning
LSC
Demand Planning
Warehousing &
Inventory
HR
HR
Fuels Supply Inventory
FS
Exchange
TSW
Plant Maintenance
Procurement
Accounts Payable
Real Estate
Profitability
0
G/L Cons & Close
0
Asset Management
4
Functional Scope
P2P
FI
Tax
4
Loans, AR & Credit
Billing & Pricing
BI Content Area Test R1
BI Content Area Test R2
BPIT R1 - Workstep
BPIT R1 - BPID
BPIT R2 - Workstep
BPIT R2 - BPID
Regression R1
Regression R2
Regression R3
Order to Delivery
Test Phase
Sales
Our Approach
[
16
ARIS “Process Roles” led to Security Assignments
Using Our Role to User Mapping Tool
Key Learnings
[
Integrating Our Project Tool Databases Proved
Invaluable
What we did:
What we should have done:
 Paid IDS Scheer for a
 Pushed SAP & ARIS to
interface of key model
share cost of developing
components into our
since it’s become
Project Management Tool
mainstream now!
(Olympic Manager)
ARIS
 Putting into SQL database
allowed us to queries and
OLY MGR
(SQL)
interfaces to other tools
 Used to interfaces to aid
MERCURY
multiple project facets
17
Key Learnings
[
Maturity of Solution Manager & ARIS Integration
Tools in 2004/05 Raised Risk Level
What we did:
What we should have done:
 In 2004/05, we surveyed  Hired more ARIS
multiple SAP clients
consultants early after
trying out Solution
purchasing tool to get
Manager.
benefits from bidirectional interface to
 Found no clear best
Solution Manager
practices to follow
 Paid for SAP Solution
 We found SAP
Manager and ARIS
consultants knowledge
consultant to be on-site at
limited at the time
same time and advise
 Decided Too Much Risk,
us on how to use the
so we abandoned fulltools.
implementation
18
Key Learnings
[
19
Using ARIS Flowcharting Required More Up-front Work
To Standardizing Symbol Set and Model Standards.
What we did:
What we should have done:
 Got basic 1 day training
on standard ARIS usage
 Went off and developed
our template of symbols
 Flow charted without
true knowledge of
“boolean logic” across
team
 Hired more ARIS
consultants early to work
with us on standards
training and enforcement
Key Learnings
[
Security & Training Team’s Reliance on ARIS Flows
Delayed Full Development of Accurate User Access.
What we did:
20
What we should have done:
 Rebuilt all security roles to  Spent more time in the
remove past kluges
As-Is
 Built a custom tool which  Got better engagement
associated specific users
from business on QA of
to job role(s).
security assignments
 Security team relied on
 Realized hybrid nature of
ARIS Models as their
user roles in reality
specifications
upfront
 Delayed completion
because of late and
changing designs
[
Best Practice Recommendations
 Clearly document the As-Is Business Processes to the
Workstep level (Activity)
 Go into Solution Manager download Business
Process areas and T-Codes via ARIS interface into
“stub models”
 Create To-Be Sub-Processes and Activities using ARIS
Flowcharting Standards
 Use Solution Manager/ARIS two-way interface to
synchronize changes
 Load into HP’s Mercury for traceability during testing
 Use for design basis for End-User Training and
Security Access
21
[
Please remember to complete and return your
evaluation form following this session.
For ongoing education on this area of focus, visit the
Year-Round Community page at www.asug.com/yrc
SESSION CODE:
3104
[
22
]
 Thank you for participating.