Robert Aydelotte ExxonMobil - Upstream Technical Computing 13 May 2004 Standardizing Fluid Property Reporting

Standardizing Fluid Property Reporting 2 Introduction  Objective  Constraints  Lessons Learned  Work Process Improvement  Design and Implementation  Current Status

Standardizing Fluid Property Reporting 3 Objective  Describe efforts of ExxonMobil –design and implement an XML-based system –exchange and communicate fluid property data –improve internal and external work processes: Improve efficiency and accuracy in capture and use of fluid property data Improve management of these data

Standardizing Fluid Property Reporting 4 Constraints  Any solution must work within ExxonMobil’s existing technical computing environment –globally implemented system (hardware, network ids, applications, databases, etc.) is a consistent mix of commercial and proprietary products –fluid characterization application and fluid property database are proprietary components  Workable with external work processes –as close to “seamless” as possible –product independent technology  Retain value of existing data and work processes  Move towards industry standardization

Standardizing Fluid Property Reporting 5 Lessons Learned  Change changes –specifically the technology components that support the workflow (i.e., applications and databases)  Loose Integration –workflows do not always require high performance components  First need to understand the workflows –handling measured data as part of a lifecycle –include metadata (ids, units, codes, etc.)  XML tools are not yet consistent –desirable features could not be used

Standardizing Fluid Property Reporting 6 Work Process Improvement  Existing internal workflow mostly manual –Data Management Fluid property data are usually delivered directly to the business unit that commissioned the work Results in “data on disks in desks” –Data Entry “Cut and Paste” data entry into desired application Re-type the data when necessary Data may not be consistently characterized or interpreted

Standardizing Fluid Property Reporting 7 Work Process Improvement  Existing external workflows inconsistent –Technical work is well managed and standardized –Data Reporting Reports are textual documents and spreadsheets –both procedures (text) and data values (tables) are important Formatting varies by vendor and office –Many customers with differing expectations –Expectations and applications change over time –Data Review Extra cost when re-work required

Standardizing Fluid Property Reporting 8 Work Process Improvement  Opportunities –consistent and verifiable data structure from vendors –automated data validation and loading (both databases and applications) –capture of the lifecycle of the data  Actions –FluidReportML (XML Schema) –modified databases to store FluidReportML –modified application to import and export FluidReportML –modified data movement tool for FluidReportML –constructed tool to create FluidReportML data files

Standardizing Fluid Property Reporting 9 Design and Implementation  “Loose Integration” –provide a common interface –accommodate structural inconsistencies –enable de-coupling of development efforts  Basic Requirements –self-describing –computer parsable –human readable –commonly verifiable –incorporate existing standards

Standardizing Fluid Property Reporting 10 Design and Implementation

Standardizing Fluid Property Reporting 11 Design and Implementation

Standardizing Fluid Property Reporting 12 Design and Implementation

Standardizing Fluid Property Reporting 13 Current Status  System has been deployed worldwide –databases, applications and interface tools  Working with fluid laboratories  ExxonMobil supports the adoption of an industry standard –FluidReportML has been submitted to POSC for additional work towards endorsement of an industry standard