1. Copyright © 2003 Americas’ SAP Users’ Group Use of Impress SAP-P3 Interface for Projects – Session 3804 Stuart Graham, Halliburton Process Lead - Project Systems Monday, May 19, 2003

2. Topics  Halliburton Company  Why SAP-P3 Interface and Why Impress Pilot Project  Interface Requirements  Design Issues and Solutions  Impress Interface Process  OpenPS Comparison  Future Development  Open Discussion

3. Halliburton Company  Merger of Halliburton and Dresser Companies  Two Global Business Units Halliburton Energy Services Group - Oil Field Services Kellogg / Brown & Root - Engineering and Construction  $15 Billion Annual Revenue  80,000 Employees / 120 Countries  SAP Global Instance – 4.6c  17,000 SAP Users World-wide / 4,000 Concurrent users

4. Need for SAP P3 Interface  SAP  Strengths:  Integrated Operational Environment  Cost Accounting  Limitation: Scheduling  Scheduling Process Cumbersome  Capacity Planning Very Cumbersome  Inadequate Schedule Reporting  Managing Contractor Projects  SAP  Strengths:  Integrated Operational Environment  Cost Accounting  Limitation: Scheduling  Scheduling Process Cumbersome  Capacity Planning Very Cumbersome  Inadequate Schedule Reporting  Managing Contractor Projects  Primavera P3  Powerful Scheduling Tool  Good Schedule Reporting  Primavera P3  Powerful Scheduling Tool  Good Schedule Reporting

5. Why iMPRESS Pilot Project?  Impress Partnership with SAP / Primavera SAP Application Server SAP Connector Impress Server IMPRESS Middleware Configuration Database P3 Connector Primavera P3 Local Application  Configurability  Versatility  Expandability (P3e, MS Project….)  Configurability  Versatility  Expandability (P3e, MS Project….)  Objective – Deliver Robust, Out-of-Box Product  Impress Collaboration Engine

6. Interface Requirements  Complex Environment  Multiple Collaboration Scenarios  Complex Project Controls Environment  System Mapping  P3 Activity 10-character Limitation  Multiple SAP Object Mapping  Exclusion / Aggregation Mapping  Many to 1 Mapping (P3 to SAP / SAP to P3)  Resource Mapping (Planned and Actual)

7. Project Scenarios  ‘Simple’ Projects: SAP – P3 Congruent  Large, Multi-Site Projects: Multiple P3 Projects – One SAP Project SAP P3 SAP Eng P3 Const P3

8. Project Scenarios  Managing Contractor Projects: Large P3 – One SAP Project (subset) SAP P3

9. Projects Scenarios  Construction / Fabrication Projects: Multiple SAP Projects – One P3 Project P3 E P C SAP Fabrication SAP * Multiple Project Resource Planning

10. Projects Scenarios  Plant Shutdown Projects: Project Systems and Plant Maintenance  Plant Maintenance Contract on Owner’s SAP: PM Orders Only PM SAP PM P3 SAP PM Net P3

11. SAPP3 Project Controls Environment  Schedule – Cost Breakdown  P3 Proposal to SAP Operational Project  Differing Company Naming Conventions / Processes  Schedule / Cost Integration Different Objectives / Perspectives Different Levels of Detail Schedule Cost Work Package Matchpoint Exclusion  2 Dynamic Environments How do you Avoid data Corruption?  2 Dynamic Environments How do you Avoid data Corruption? XXXXXXXX XXXXXXXX Grouping / Summing

12. Topics  Halliburton Company  Why SAP-P3 Interface and Why Impress Pilot Project  Interface Requirements  Design Issues and Solutions  Impress Interface Process  Design Issues and Solutions  Impress Interface Process  OpenPS Comparison  Future Development  Open Discussion  OpenPS Comparison  Future Development  Open Discussion

13. Design Tools  Design Objectives  Efficiency  Flexibility  Design Toolbox  Collaboration Project  Global Parameters  Exception Overrides: P3 Custom Code Fields / SAP User Fields  Data Transfer: Synchronization Action Types (SAT)

14. Design Solutions  P3 Activity Mapping  P3 10-character Activity  SAP Network / Activity / element (12, 4, 4- characters)  Solution  Global Parameter – Default Network Prefix SAP (TE5001C100PI 0010) Prefix (TE5001) P3 (C100PI0010)  Overrides P3 Custom Data Fields (to SAP) SAP User Field (to P3)  Solution  Global Parameter – Default Network Prefix SAP (TE5001C100PI 0010) Prefix (TE5001) P3 (C100PI0010)  Overrides P3 Custom Data Fields (to SAP) SAP User Field (to P3)

15. Design Solutions  Multiple SAP Object Mapping  Network / PM Order  Activity / Activity element  Subnetwork  Multi-Plant (Company)  Solution  Global Network Type (Project Profile/Network Profile)  P3 Custom Data Fields Order Type Override (Plant, MRP Controller, Order Type) Activity Type, Superior Activity, Subnetwork  I, E, S, P, X (Internal, Preq, Service, Primary, Exclude)  Solution  Global Network Type (Project Profile/Network Profile)  P3 Custom Data Fields Order Type Override (Plant, MRP Controller, Order Type) Activity Type, Superior Activity, Subnetwork  I, E, S, P, X (Internal, Preq, Service, Primary, Exclude) XP3 Activity (Exclude) E0010External Activity element to Activity 0010 G0030SG090E200Primary Activity of Subnet to Network SG090E200 0030 IInternal Activity Examples:

16. Design Solutions  Exclusion / Aggregation Mapping  SAP Objects  P3 Objects  Solution  SAP Objects Priority Code = “X” Activity element Grouping / Summarization  P3 Activities Custom Data Field: Type = “X” Grouping / Summarization  Solution  SAP Objects Priority Code = “X” Activity element Grouping / Summarization  P3 Activities Custom Data Field: Type = “X” Grouping / Summarization

17. Design Solutions  Many to 1 Mapping  Many P3 Projects to One SAP Project  Many SAP Projects to One P3 Project  Solution  Many P3 Projects Separate Impress Collaboration Projects Mapping Options:  WBS Subtree  Priority Code  Many SAP Projects Multiple Parameter (Value) Sets  Solution  Many P3 Projects Separate Impress Collaboration Projects Mapping Options:  WBS Subtree  Priority Code  Many SAP Projects Multiple Parameter (Value) Sets

18. Design Solutions  Resources - Planned / Actual  P3 Resource to SAP Work Center Mapping  Planned / Actual / Forecast Work Mapping  Solution  Resources Mapping Global Parameters by Plant Overrides (P3 / SAP)  Work Quantity Mapping Multiple Synchronization Action Types (SATs) SAT Parameters (Switches)  Solution  Resources Mapping Global Parameters by Plant Overrides (P3 / SAP)  Work Quantity Mapping Multiple Synchronization Action Types (SATs) SAT Parameters (Switches)

19. Design Solutions  Dynamic Environments – How do you avoid obliterating the Other System?  SAP Scope / Plans  Primavera Schedule  Impress Synchronization Action Types (SAT) - Multiple SATs (10 to date)  WBS Update: Both ways (optional)  Activity Update – Multiple (parameterized)  Relationships: Both ways (optional)  Sequencing SATs  Impress Synchronization Action Types (SAT) - Multiple SATs (10 to date)  WBS Update: Both ways (optional)  Activity Update – Multiple (parameterized)  Relationships: Both ways (optional)  Sequencing SATs Collaboration Project

20. Impress SAP-P3 Process  Create Collaboration Project(s) Project Name Source System Source System Parameters Target System Project is Set up! Target System Parameters +

21. Impress SAP – P3 Process  Project Synchronization Select Project Synchronization Types Synchronization Parameters Action  Simulate  Synchronize Now  Schedule  Reprocess Action  Simulate  Synchronize Now  Schedule  Reprocess Synchronization History

22. Topics  Halliburton Company  Why SAP-P3 Interface and Why Impress Pilot Project  Interface Requirements  Design Issues and Solutions  Impress Interface Processes  OpenPS Comparison  Future Development  Open Discussion  OpenPS Comparison  Future Development  Open Discussion

23. OpenPS Interface  OpenPS Advantages  Many Users at Relatively Low Cost  No Servers Required  Simple to Maintain  WBS / Network Coding Same  For Smaller, Less Dynamic Projects (Most Projects)  HR Integration (Resources by Employee)  Fixed Mapping  Fixed Mapping Rules / No Flexible Configuration  No Exclusions (SAP or P3)  No Hybrid PS / PM Projects  Fixed Synchronizations  SAP to MS Project – Creates New MS Project  MS Project to SAP – Creates / Updates Structure and Schedule: Can be modified as to what is updated.  Close Synchronization Coordination Required

24. Future Development  Project Scenarios (on-going):  Many SAP to 1 P3 (designed)  PM Orders (NPPD deployed)  Plant Shutdown (PS – PM Projects)  Engineer-to-Order Projects (PP Orders)?  Synchronization Action Types  SAP Calendar  SAP Resources  Planned Costs / Actual Costs  Earned Value  Confirmations (limited)?  Simulation Versions?

25. Key to Success  Rationalize Code Conventions between SAP and Primavera  Define Cost / Schedule Integration Matchpoint - Activity OR  Suffer Detailed Cross-Coding  Risk  Suffer Detailed Cross-Coding  Risk ! Business Processes NOT Systems

26. Any Questions? SAP – P3 Interface

27. Copyright © 2003 Americas’ SAP Users’ Group Thank you for attending! Please remember to complete and return your evaluation form following this session. Session Code: 3804