This article needs additional citations for verification .(June 2016) |
Formation | 1990-10-15 |
---|---|
Legal status | Consortium |
Purpose | a global, non-profit, industry consortium that facilitates an inclusive user community for the development, deployment and maintenance of collaborative technologies using open data exchange standards for the upstream oil and natural gas industry |
Location |
|
Region served | Worldwide |
Membership | 100+ |
Official language | English |
President & CEO | Ross Philo |
Main organ | Member Organizations |
Staff | 7 |
Volunteers | 250+ |
Website | http://www.energistics.org |
Energistics is a global, non-profit, industry consortium that facilitates an inclusive user community for the development, adoption and maintenance of collaborative, open standards for the energy industry in general and specifically for oil and gas exploration and production.
The open standards that Energistics encourages the industry to use deliver business value to the upstream oil and natural gas industry through business process efficiencies across the entire exploration and production life cycle. Energistics is a membership organization. The work of the consortium concentrates on helping upstream oil and natural gas companies through the development, support, and promotion of standards that address data definition, handling, storage, and exchange in the context of technology, computing, communications, and business processes.
Regions are a means of building local Energistics communities around the world, with local activities and events. There are eight regions: Africa, Asia Pacific, Eastern Europe, Latin America, Middle East, North America, South Asia, and Western Europe.
The predecessor of Energistics was formed in October 1990 by five founding sponsor oil companies: BP, Chevron, Elf (since merged into Total), Mobil (since merged into ExxonMobil), and Texaco (since merged into Chevron) under the name Petrotechnical Open Software Corporation (POSC). [1]
The mission of the new organization was defined as developing, supporting, evolving, and promoting open standards for the scientific, engineering, and operations aspects of the oil and gas exploration and production industry, known as Energy eStandards.
In the early years, the organization established an open process, acquired resources, and pursued a set of deliverables. The use of the specifications was intended to enable greater quality, consistency, and integration of data and data use. The initial deliverables were known as the Software Integration Platform (SIP) Specifications.
In 1993, Version 1.0 of the specifications were published as a collection of hard-cover bound books. The published specifications included base computing, data model, data access, data exchange, and user interface. [2]
During the next three years, the organization engaged in educational, testing and support activities, including two proof-of-concept implementations of the SIP enabling middleware and a multi-stage, multi-member pilot implementation program called the Industry Implementation Pilot (IIP). The IIP involved both energy company in-house developers and commercial vendor developers building up aspects of an infill drilling scenario. [3]
In 1996, the board of directors commissioned a study of the benefits of using the SIP specifications, which projected savings of US$1–3 per barrel of oil gained through improvements in data quality, data accessibility, and exploitation of information and knowledge. [4]
Additions and enhancements to the SIP specifications were published in the following few years, including SIP Version 2.2 in 1997 and software applications interoperability specifications in 1999. During these years, the organization transitioned to a fully member-elected board of directors.
The SIP Version 2.3 incremental update came out in 2000 and 2001, along with the first XML data schema specifications for basic well data (WellMasterML) and well log display parameters (LogGraphicsML) as well as a series of XML-oriented public seminars. The future course of the organization was shifting from data store and middleware specifications to subject matter data exchange specifications.
This transition progress in 2002 with the agreement to receive custodianship of the WITSML Standards for drilling data exchange based on XML and Web Services technologies. In the same year, the first of a number of member Special Interest Groups (SIGs) was organized as the user community for subject-specific standards. The subject matter of the first SIG was E&P data stores and their use.
In 2003, a SIG was formed to support the WITSML Standards. The final release of the SIP Specifications, Version 3.0, came out during that year. Reference standards for both well log data and E&P document and dataset cataloging were published, along with an E&P business process reference model.
During 2004, the organization decided to improve the alignment of its name with its mission by redefining the meaning of the name POSC to mean the Petrotechnical Open Standards Consortium. [5]
The second XML and Web Services family of standards was initiated in August 2005 with the agreement to host the first year of the PRODML, Production XML Markup Language initiative, after which the PRODML SIG was formed. A major new release of the WITSML Standards was released in 2005. Also, an open source data conversion utility for LAS to WITSML well log dataset conversion was developed and released.
Building on the most valuable initiatives and an increased emphasis on wide-scale standards adoption, the organization rebranded itself as Energistics in November 2006. This coincided with the release of Version 1.0 of the PRODML Standards and an update to Units of Measure specifications. [6]
In 2007, a WITSML-based electronic permitting XML schema specifications was published following a multi-year collaboration with US state regulatory agencies in cooperation with API PIDX's REGS EC User Group.
During 2008, WITSML Standards, Version 1.4.0 were released. Also, updated application interoperability specifications were submitted by OpenSpirit Corporation, which followed from the previous work in the area published originally in 1999.
2009 saw the formation of the RESQML SIG to address reservoir characterization standards development as a natural successor to the RESCUE Work Group's C++ Class Library. Also, updated PRODML Standards for both data and services specifications were released.
In 2011 the Standards DevKit was developed by ExxonMobil and is licensed to Energistics for maintenance, support and administration. The DevKit supports the latest versions of WITSML, PRODML and RESQML. Further development will be guided by Energistics and the user community.
In early 2012, Energistics, along with 11 other standards organizations, formed the Standards Leadership Council (SLC). The intent of the SLC is to formally unite the leaders of organizations that provide open and freely-available standards to the upstream oil and natural gas industry.
WITSML v1.4.1.1 was published in July 2012 and includes updates and bug fixes to v1.4.1 (published in 2011). A certification program for v1.4.1.1 servers is under development.
In May 2014, the Energy Industry Profile (EIP) Metadata Standard was published. EIP is an open, non-proprietary metadata exchange standard designed to document structured and unstructured information resources of importance to members of the energy community and to maximize metadata interoperability within the industry.
In July 2014, the Unit of Measure Standard V1.0 was published. This includes the Unit of Measure Dictionary and the Unit Symbol Grammar Specification. Contributors to this standard include the Energistics community, The Professional Petroleum Data Management (PPDM™) Association and the Society of Exploration Geophysicists (SEG). Also published in 2014 was the Energy Industry Profile (EIP) v1.0 of ISO 19115-1. During the summer and fall of 2014, PRODML v1.3 and RESQML v2.0 were published.
In 2015, a game changer standard was published - Energistics Transfer Protocol (ETP) v1.0 was released to the industry. ETP enables the efficient transfer of data between applications and is a part of the Common Technical Architecture (CTA) used by WITSML, RESQML and PRODML.
An industry standard data model, or simply standard data model, is a data model that is widely used in a particular industry. The use of standard data models makes the exchange of information easier and faster because it allows heterogeneous organizations to share an agreed vocabulary, semantics, format, and quality standard for data. Organizations may save time and expense by using pre-existing data models instead of developing them in-house, although the process of making data conform to external models can also be a hindrance.
The Open Document Format for Office Applications (ODF), also known as OpenDocument, standardized as ISO 26300, is an open file format for word processing documents, spreadsheets, presentations and graphics and using ZIP-compressed XML files. It was developed with the aim of providing an open, XML-based file format specification for office applications.
The common warehouse metamodel (CWM) defines a specification for modeling metadata for relational, non-relational, multi-dimensional, and most other objects found in a data warehousing environment. The specification is released and owned by the Object Management Group, which also claims a trademark in the use of "CWM".
OMA SpecWorks, previously the Open Mobile Alliance (OMA), is a standards organization which develops open, international technical standards for the mobile phone industry. It is a nonprofit Non-governmental organization (NGO), not a formal government-sponsored standards organization as is the International Telecommunication Union (ITU): a forum for industry stakeholders to agree on common specifications for products and services.
Learning Object Metadata is a data model, usually encoded in XML, used to describe a learning object and similar digital resources used to support learning. The purpose of learning object metadata is to support the reusability of learning objects, to aid discoverability, and to facilitate their interoperability, usually in the context of online learning management systems (LMS).
JT is an openly-published ISO-standardized 3D CAD data exchange format used for product visualization, collaboration, digital mockups, and other purposes. It was developed by Siemens.
WITSML is a standard for transmitting technical data between organisations in the petroleum industry. It continues to be developed by an Energistics facilitated Special Interest Group to develop XML standards for drilling, completions, and interventions data exchange. Organizations for which WITSML is targeted include energy companies, service companies, drilling contractors, application vendors and regulatory agencies.
This article describes the technical specifications of the OpenDocument office document standard, as developed by the OASIS industry consortium. A variety of organizations developed the standard publicly and make it publicly accessible, meaning it can be implemented by anyone without restriction. The OpenDocument format aims to provide an open alternative to proprietary document formats.
The Clinical Data Interchange Standards Consortium (CDISC) is a standards developing organization (SDO) dealing with medical research data linked with healthcare,made to enable information system interoperability and to improve medical research and related areas of healthcare. The standards support medical research from protocol through analysis and reporting of results and have been shown to decrease resources needed by 60% overall and 70–90% in the start-up stages when they are implemented at the beginning of the research process. Since December 2016, CDISC standards are mandatory for submission to US FDA.
The ISO 15926 is a standard for data integration, sharing, exchange, and hand-over between computer systems.
The IMS Question and Test Interoperability specification (QTI) defines a standard format for the representation of assessment content and results, supporting the exchange of this material between authoring and delivery systems, repositories and other learning management systems. It allows assessment materials to be authored and delivered on multiple systems interchangeably. It is, therefore, designed to facilitate interoperability between systems.
Geospatial metadata is a type of metadata applicable to geographic data and information. Such objects may be stored in a geographic information system (GIS) or may simply be documents, data-sets, images or other objects, services, or related items that exist in some other native environment but whose features may be appropriate to describe in a (geographic) metadata catalog.
The Microsoft Open Specification Promise is a promise by Microsoft, published in September 2006, to not assert its patents, in certain conditions, against implementations of a certain list of specifications.
PRODML is a family of XML and Web Services based upstream oil and natural gas industry standards from Energistics and its PRODML Special Interest Group.
POSC Caesar Association (PCA) is an international, open and not-for-profit, member organization that promotes the development of open specifications to be used as standards for enabling the interoperability of data, software and related matters.
As a general definition, paradata are usage data about learning resources that include not just quantitative metrics, but also pedagogic context, as inferred through the actions of educators and learners. Paradata may be operationalized as a specific type of metadata, however the construct differs from traditional descriptive metadata that classify the properties of the learning resource itself, and instead involves the capture—and open resharing—of in situ information about online users’ actions related to the resource. Learning resource paradata is generated through user processes of searching for content, identifying interest for subsequent use, correlating resources to specific learning goals or standards, and integrating content into educational practices. Paradata may include individual or aggregate user interactions such as viewing, downloading, sharing to other users, favoriting, and embedding reusable content into derivative works, as well as contextualizing activities such as aligning content to educational standards, adding tags, and incorporating resources into curriculum. Context about users is also of interest as paradata, including grade level or subject taught, experience level, or geographic location—as is information about the curricular relevance, audience, methodologies, and instructional settings of use as a resource is adopted by practitioners. Paradata are generally anonymized and/or aggregated at the community level to protect the privacy of individual users as data are shared between learning communities. Paradata may be expressed in realtime data streaming as user actions occur, or as periodic reporting of user activities over a range of time.
The Asset Description Metadata Schema (ADMS) is a common metadata vocabulary to describe standards, so-called interoperability assets, on the Web.
System Package Data Exchange is an open standard capable of representing systems with digital components as bills of materials (BOMs). First designed to describe software components, SPDX can describe the components of software systems, AI models, software builds, security data, and other data packages. SPDX allows the expression of components, licenses, copyrights, security references and other metadata relating to systems.
The Physical Security Interoperability Alliance (PSIA) is a global consortium of more than 65 physical security manufacturers and systems integrators focused on promoting interoperability of IP-enabled security devices and systems across the physical security ecosystem as well as enterprise and building automation systems.
The SAML metadata standard belongs to the family of XML-based standards known as the Security Assertion Markup Language (SAML) published by OASIS in 2005. A SAML metadata document describes a SAML deployment such as a SAML identity provider or a SAML service provider. Deployments share metadata to establish a baseline of trust and interoperability.