Eni s Implementation of a Project Management Information System for the Goliat Project

Transcription

1 Eni s Implementation of a Project Management Information System for the Goliat Project ECIM 2009 Conference - September 14-16, Rica Maritim Hotel, Haugesund Marco Piantanida, Eni E&P Bernardo Principato, Eni Norge Gioacchino Gaudioso, Project Objects

2 Abstract The paper will describe the implementation of a sophisticated Information Management System aimed at supporting the processes related to project planning & control, interface management and change management for the Goliat project, operated by Eni Norge. The system has been developed on top of Eni s Project Management System, named SIGEP, and it has been configured to fit the internal workflows and procedures that have been designed for the Goliat project. The system provides a framework where all project information (schedule, progress, costs, changes, interface issues, etc) can be cross referenced with each other, as well as to the main project control structures (Work Breakdown Structure, Product Breakdown Structure), therefore enforcing a consistent view of the project status from different perspectives. Moreover, the integrations of the system with SAP, Primavera and the Intergraph engineering database will be described.

3 Eni Company Profile Eni operates in the oil and gas, electricity generation and sale, petrochemicals, oilfield services construction and engineering industries Eni is active in more than 70 countries with a staff of about 79,000 employees

4 Eni Norge Company Profile Eni Norge has been part of the Norwegian petroleum industry since the start in Safe operations with minimum impact on the environment, creating value for society and our owners, are our goal. The dedicated and highly skilled people in our organization are the most important tool in achieving it. An active policy of searching for new resources while ensuring optimum production from existing fields creates a firm basis for a continued positive development of our company.

5 Outline of the Presentation The Goliat Project The Goliat Project Management System Cross-referenced Database for all Project Data Streamlined Information Exchange with Contractors Based on Eni s Standard Environment: SIGEP Supported Data: Planning & Control Interface & Change Integrations (SAP, Primavera, Intergraph)

6 The Goliat Project The Goliat field is located in Production License 229 and 229B. The discovery was made in 2000 with the first exploration well. A total of five wells have now been drilled. The licensees are Eni Norge AS (operator, 65%) and StatoilHydro Petroleum AS (35%).

7 The Goliat Project The Goliat field is expected to be in production for at least 15 years. A total of 22 wells are planned to be drilled into the Goliat reservoirs.

8 The Goliat Project Management System Cost Planning Reporting Interface Change Integrated Workflows, Procedures and Software Tools Based on Eni s standard Project Management Environment: SIGEP

9 The Goliat Project Management System Workflows Sample Workflow for Change Management Steps that are performed with the SIGEP Tool

10 The Goliat Project Management System Procedures Included in the Contractor s Package Project Control Prior Agreement on the Reporting Structure Prior Agreement on the file formats and content Primavera P6 files for schedule Protected, SIGEP-importable Excel spreadsheets for Progress and Costs Interface and Change Prior Agreement on Interfaces and Battery Limits Direct usage of the online SIGEP Tool Notifications Approval Workflows and Roles

11 The Goliat Project Management System Eni s Standard Tool for Project Management The Base Product: Project Objects Distinctive Characteristics Multiple Breakdown Structures, which can be linked with each other PBS (Product Breakdown Structures), WBS (Work Breakdown Structure), CBS (Cost Breakdown Structures) Importable from Library Templates vs. Import respectively from Intergraph Smart Plant Foundation, Primavera / MS Project, SAP Control Elements (Progress Elements, Cost Elements) can be linked to the Schedule Phasing of Forecasts can be automatic or manual Every Element in the Project (Technical Queries, Interface Issues, Permission not to Conform, Changes, Actions, Trends, Risks, Documents, etc) can be linked to any Breakdown Structure Consistent and Automatic Reporting from multiple points of view

12 The Goliat Project Management System Eni s Standard Tool for Project Management

13 The Goliat Project Management System Eni s Standard Tool for Project Management The SIGEP Oracle Database integrates Schedule Data developed with MS Project or Primavera P5/P6 with Progress and Cost Data managed with the SIGEP modules named: PT (Progress Tracking) CM (Cost Management)

14 Multiple Breakdown Structures Different, but Consistent, Point of Views Project Management Point of View Engineering Point of View Contract Administration Point of View

15 Main Goals of the Project Management Information System Project Management Information System Product Breakdown Structure(s) (PBS) Work Breakdown Structure(s) (WBS) Contractor 1 Contractor 2 Contractor 3 Cost Breakdown Structure(s) (CBS) Contractor N 1. Guarantee Internal Consistency Multiple Interconnected Breakdown Structures Update one Structure, Propagate to all Others 2. Optimize Exchange of Info Agreed Reporting Structures with Contractors Data from Contractors seamlessly Uploaded

16 Main Goal 2. Information Exchange of Project Control Info Contractor 1 Project Management Information System Contractor 2 Product Breakdown Structure(s) Work Breakdown Structure(s) Contractor 3 Schedule Progress, Cost Cost Breakdown Structure(s) Contractor N Each Contractor updates his own Work Package with monthly Information about Schedule, Physical Progress, Cost. Eni Norge seamlessly integrates the Information at Project level to perform Project Monitoring, Control and Reporting. Views across different Breakdown Structures are automatically kept consistent with each other.

17 Main Goal 2. Information Exchange about Interfaces and Changes Change Interface Issue Technical Query (TQ) Color code shows what Contractor raises the issue. Contractor 1 Project Management Information System Contractor 2 Contractor 3 Enter Data Review Answers Product Breakdown Structure(s) Work Breakdown Structure(s) Notifications Cost Breakdown Structure(s) Contractor N Each Contractor can raise Issues (Technical Queries, Interface Issues, Changes) related to Quality (PBS), Time (WBS) and Cost (CBS). Eni Norge can seamlessly associate each Issue with the affected Items, therefore gaining a consistent picture of the Project

18 Main Goal 1. Guarantee Internal Consistency - Project Control A Cost Element linked to a WBS Element automatically inherits the Begin-End dates of the Activity. The Budget and Forecast Cost Phasing are accordingly displayed.

19 Main Goal 1. Guarantee Internal Consistency - Project Control If the activity is delayed within the project plan, the phasing of the cost is automatically updated. See the difference between the blue curve (original plan) and the green curve (updated plan) for the cost phasing. delay

20 Main Goal 1. Guarantee Internal Consistency - Interfaces and Changes The link between TQ, Interface Issues and Changes to both project elements and plant components will allow to build queries: from the project management perspective (e.g. which is the WBS code which is currently most affected by changes?) from the engineering perspective (e.g. which is the plant component which is being raised more TQs against?) Powerful Analysis of the Forms

21 Sample Usage of the Tool for Project Control Setup of the Breakdown Structures Cross Referencing Cost Elements CBS WBS

22 Sample Usage of the Tool for Project Control Exchanging Project Control Data with Contractors Protected Excel Spreadsheets can be generated for each Contract Holder. They contain all cost data related to the previous Cut-Off Date, with Actual Costs automatically updated from SAP Data

23 Sample Usage of the Tool for Project Control Analyzing and Displaying Project Data

24 Sample Usage of the Tool for Interface and Change Management Browsing the Change Register Interfaces, Changes, Deviations and Technical Queries can be referenced to the corresponding elements in the PBS, CBS and WBS, ensuring full consistency across project, interface and change management views. The Management of each element can be configured with a Workflow of any complexity, including Approval steps, notification and target response dates.

25 Sample Usage of the Tool for Interface and Change Management Linking an Interface Issue to an Element in the WBS

26 Sample Usage of the Tool for Interface and Change Management Configuring the Approval Workflow Workflows can be implemented so that they are compliant with internal procedures The workflow of the forms is fully configurable by a SIGEP super-user

27 Integrations SIGEP Product Breakdown Structure(s) Work Breakdown Structure(s) SPF (Smart Plant Foundation) TEF Adapter Primavera Web Services P6E (Primavera 6 Enterprise) Cost Breakdown Structure(s) Scheduled File Import SAP R/3

28 Integration with Primavera P6 SIGEP Primavera web services Activity Code, Activity Names Start/End Dates Resources Milestones Baseline Dates P6E (Primavera 6 Enterprise) Citrix Metaframe Servers Load Balanced Configuration Physical Progress Management Cost Management Schedule Management Oracle Database Oracle Clustered Servers Failover Architecture

29 Integration with Primavera P6 A button within Primavera allows to automatically transfer data into the SIGEP database No export/import operations are required

30 Integration with SAP SIGEP File Content: SAP WBE, Contract Number, Cumulated Commitment Value, Cumulated Expenditure Value, Cumulated Accruals Value Cost Management Oracle Database Oracle Loader SIGEP Server sigepsap.eni.it ftp Oracle Clustered Servers Failover Architecture SAP R/3 SAP periodically generates a set of files containing the cost information about the projects

31 Integration with SAP SAP WBE SAP Contract

32 Integration with Intergraph SIGEP and Technical Know How Portal Intergraph TEF Libraries Code, Name, Hierarchy of Plant Components SPF (Smart Plant Foundation) Facility Functional Unit Equipment Product Breakdown Structure (PBS) Oracle Database Synchronize SIGEP PBS with the SPF plant structure. Depth of the synchronization can be selected by the user (e.g. Functional Unit level, or Equipment level) Oracle Clustered Servers Failover Architecture

33 Current Deployment Architecture of SIGEP Used on 262 Development Projects within Eni Intranet Users Internet Users TEROS Secure Application Gateway CISCO CSM Load Balancer Siteminder Web Agents Siteminder Web Agents Siteminder Policy Servers SIGEP Web Modules SIGEP Client Modules Citrix Secure Gateway IIS Web Servers 3 Load Balanced Servers Citrix Metaframe Farm 3 Servers Oracle Database Oracle Clustered Servers Failover Architecture