POSC has developed and delivered specifications for a software integration platform for E&P technical applications. This platform is formed by a set of standard interfaces between petrotechnical software applications, database management systems, workstations and the users. POSC focuses on development of interface specifications and prototype implementations.
The POSC Specifications (Version 2.2) are available at the POSC Web site and on CD-ROM. To view the Version 2.2 documentation you will need an HTML browser that supports HTML 3.0 and Javascript 1.1, e.g., Internet Explorer 3.02 (with JScript v2.0 upgrade), 4.0x, or up; Netscape 3.0x or up, and Netscape Communicator 4.0x or up.
To view any of the on-line specifications, start at the opening page of the
For any problems related to using the Specification Viewer, or to order a CD-ROM containing the POSC Specifications, please contact the POSC Help Desk, help@posc.org
For a brief description of any of the POSC Specifications, select one of the links below (bold type indicates availability on-line):
POSC and its members have specified a tool to support the integrated E&P business processes oriented to the entire lifecycle of a reservoir asset, and the teamwork of knowledge workers who collaborate to manage the asset. This tool, named Epicentre, is an integrated E&P data model that spans the entire lifecycle of a field.
The Epicentre Data Model defines objects and their characteristics relevant to petroleum Exploration and Production (E&P), and establishes relationships between these objects. Implementing the data model enables various disciplines within the E&P industry (users, data base administrators, software developers) to share the same set of data regardless of application or computing platform.
The Data Access and Exchange specification provides for the portability of POSC-compliant data across multiple computing platforms by specifying both a language and an application programming interface (API) that are independent of the data storage structure or underlying DBMS technology. This standard allows users working with compliant software to access, create, query, update, and delete E&P data. And because it is independent of the data base management system (DBMS) technology, it can withstand technological changes, including the industry's current migration from relational data bases to object-oriented data bases.
Data Exchange Operations specification defines an interface that enables users and applications to exchange data independently of both the data access implementation and the database engine technology.
Note: Prior to the Verions 2.1 release of this document, the data exchange operations were documented in the Data Access and Exchange specification.
The POSC Exchange Format (PEF) is a way to transfer compliant E&P data to different computing environments, to efficiently manage that data, and to decode it without misinterpretation. Whether the exchange programming is done by the commercial software developer or the in-house programmer, the specifications provide a vendor-neutral data link to the POSC world that enables end users to:
The requirement for high-speed Inter-Application Communication was established by the Data Access Request for Comment (RFC) process. This requirement has manifested itself in the industry as general purpose toolkits and the applications that use them. Unfortunately, the E&P industry does not consistently use any specific toolkit nor does it use any given toolkit in a consistent manner. These inconsistencies have created a high barrier to interoperability among E&P applications. The Inter-Application Communications specification includes an application programming interface (API) and protocols.
The CGM*PIP specification establishes the requirements to be met when two-dimensional graphic picture data that is vector, or mixed vector and raster, is used in the graphical interchange between petrotechnical applications employed in E&P applications, using the format of the Computer Graphics Metafile (CGM). The CGM*PIP/I and CGM*PIP/II specifications address constraints on CGM and provide extensions for seismic trace drawing and continuous rendering. CGM*PIP/III and CGM*PIP/IV specifications provide extensions for well logging.
Additional information related to CGM*PIP is available at this Web site:
The BCS technical specification defines services that enable applications to achieve portability and interoperability with a minimum investment in system-specific modification. Spanning the whole E&P technical applications environment, the BCS serves as a technical foundation for those who develop and use POSC-compliant products in their E&P business.
The current version of BCS (V2.0) published by Prentice Hall (ISBN 0-13-125600-9, 179 pages, softcover) is available only in hardcopy. Contact the POSC Help Desk (a href="mailto:help@posc.org">help@posc.org for assistance in obtaining a copy of the BCS.
As the complexity of E&P computer applications increases, so does the importance of a common computer-human interface. The E&P User Interface Style Guide addresses the issue by specifying the appearance and behavior of user interfaces across multiple vendor platforms and applications, with an emphasis on display of and interaction with graphics.
| FAQ Index | POSC Home Page |
Copyright © 1994-1998 Petrotechnical Open
Software Corporation. All rights reserved.
POSC ®, the POSC logo ® and Epicentre® are registered
trademarks of Petrotechnical Open Software Corporation.