150 likes | 169 Views
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. BP global refining portfolio.
E N D
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
BP global refining portfolio 100% BP refineriesAreas where BP has a material marketing presence Other refineries with <100% BP interest Source: Blackwells, 3Q 2003. Russian interests not represented
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)
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 User Access Portal eRTIS Environment & Applications Applications Functions Process Graphics Data Web Services eRTIS Data Model Data Mgmt Data Interfaces Web Service Web Service Web Service Web Service Web Service RDMS LIMS Hist. ERP EAM etc Legacy Systems DCS PLC Controls Valves, Equipment, Analysers, … Equipment & Devices
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
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