BP Refining eRTIS Project Case Study: eRTIS Project and use of MIMOSA and Generic Web Services

BP & refining BP’s business is conducted in four major Segments:  Exploration & Production  Refining & Marketing  Petrochemicals  Gas, Power and Renewables

Source:Blackwells, 3Q Russian interests not represented 100% BP refineries Areas where BP has a material marketing presence Other refineries with <100% BP interest BP global refining portfolio

BP refineries IT heritage BP Refining has grown through acquisition –Amoco (USA) –ARCO (US West Coast) –Veba (Rhine Region - Germany) IT Systems heritage diverse –Enterprise Asset Management Systems (Maximo, SAP, Teroman, MIMS, other) –Laboratory management systems diverse (Sample Manger, WinBliss, other) –Multiple Real-time Historians (PI, PHD, IP21) Each Refinery historically has had autonomy of IT acquisition / implementation Diverse Information Landscape

What is eRTIS Problem: –Diverse IT infrastructure –Capability to effect corporate business process change hampered by IT Information, applications & Infrastructure divergence at sites Requirements: –Project to provide common operating environment & integration infrastructure for 14 majority owned BP Refineries Solution: –Common Data Model –Common Integration & Application Infrastructure (Mega Centre) –Common Applications (8 Operations & Maintenance Composite Applications)

What data model? NameDescriptionDomains ISO10303Step, PIStep, Epistle, many parts, basis of other standards, file transfer onlyEquipment data ISO15926http:// data MimosaOSA-EAI, OSA-CBM, data OPCwww.opcfoundation.orgProcess Data, Embedded systems ISA – SP95http:// and Production planning and Equipment data B2MMLhttp:// planning API690http:// 20.pdf Equipment data API-689ISO14224 – see aboveOperations and maintenance data API-610See aboveProcurement, engineering, construction OASISXML only transfer of PSLX see open.org/committees/tc_home.php?wg_abbrev=ppshttp:// open.org/committees/tc_home.php?wg_abbrev=pps Production planning OMG MfgDTFObject Management Group – Manufacturing Domain Task force Manufacturing software components interoperability via CORBA (out-of-scope) ISO/TC184/SC5JWG 8 (Manufacturing Process and Management Information - administered by ISO/TC 184/SC 4

Requirements domain

Mapping of data models to requirements

Industry models Requirements domain: –Operations & Maintenance Best coverage of requirements by: –Mimosa –ISA SP-95 Initial requirements pre-dominantly covered by: –Relational model of Mimosa CRIS 3.0

eRTIS technical overview Web Service eRTIS Data Model LIMSHist.ERPEAMetc DCSPLC RDMS Valves, Equipment, Analysers, … Data Web Services Data Mgmt Data Interfaces Legacy Systems Controls Equipment & Devices User Access eRTIS Environment & Applications Portal Web Service ApplicationsFunctionsProcess Graphics

Generic interface requirement Problem: –No existing OPENO&M interface for data sources –Data sources do not contain unique segment id –Difficult to add unique id to data sources –Desire not to perform look-ups prior to data transformation Requirements: –Generic data transformation service for re-use to load MIMOSA Repository –Synchronisation process between source and target databases required Solution: –Extract source data as XML –Transform from source data to MIMOSA compliant XML –Send XML to stored procedure –Within stored procedure use existing hierarchy inherent from source data to determine segment_id –If segment exists update application data in MIMOSA database –If segment doesn’t exist create segment then insert application data in MIMOSA database

Interfaces Connection Types at sites –Maintenance System –Laboratory System –Document Management System –Drawing Management System –Other (RDBMS) Interface Details –70+ Interfaces –Suite of 10 Generic Web Services (Read & Write) –Associate Site specific XSLT Transformation with Generic Web Services to create Site interfaces

Data transformation

Operating Envelope (OE) Hierarchy & data synchronisation

In Summary Mimosa Data Model maps to our Operations & Maintenance requirements MIMOSA is being used as more than an interface standard – it is a the heart of our portal integration solution and will form a significant portion of our future Refining Roadmap BP would ideally not want to develop and maintain interfaces Ideally vendors could provide interface / data model in future