This Use Case describes the handover of O&M oriented information from the EPC community to the owner/operator in a properly sequenced way during the Design and Construction phases prior to Commissioning. While there are massive amounts of information that an EPC may need to exchange with other EPCs and the Owner/Operator engineering and construction team, this use case is focused on the information that is needed to properly populate and commission a sustainably interoperable Operations and Maintenance Execution Environment. This information falls into two basic categories. The first category is engineering information about the plant breakdown structure and system design models (Logical P&ID and PFD), which provide the identifiers and logical engineering structure to which all other information, systems and services must be related. The second category is the portion of as-built information detailing serialized assets that have been installed in specific structural locations.
Background
A core problem for Owner/Operators (O/O), vendors and systems implementers is the lack of good mechanisms for managing the needed information exchanges between EPC activities and the O&M related systems, applications and technologies. The problem has a variety of sub-parts, all of which are exacerbated when multiple EPC firms using multiple Design, Engineering and Construction Management tools are engaged, either in parallel or over time.
Success for individual project teams and sub-teams is often measured only against a discreetly identified set of work, without a requirement to make sure that the information envelope contains everything required to properly support the overall enterprise knowledge and information management requirements. While sustainable interoperability between various systems is increasingly critical for effective O&M, the basis for achieving interoperability is often made more difficult by the lack of appropriate interoperability requirements for each individual project that would enable a comprehensive solution.
There is also a lack of maturity in the engineering reference standards models. No single standard has broad, in-depth support for capturing all of the required process, structural, mechanical, electrical, electronic and software information elements that are required for full-lifecycle interoperability. In order to progress from the current model where much of the information is managed through proprietary methods, multiple standards need to be harmonized so they can be used together in a portfolio. This portfolio approach leverages a combination of external reference data libraries and published standards for format, content and services – properly addressing the interoperability requirements for process industries.
The key to making required progress on a timely basis is leveraging the established MIMOSA and OpenO&M models, and methods for O&M interoperability while constraining the information being exchanged to the subset required to populate the O&M Execution Environment. Using these methods and constraints in conjunction with the ISO 15926, ISO 18435, ISO 13374 and ISO 14224 communities offers the best chance for achieving sustainable lifecycle interoperability.
Note POSC Caesar Association and MIMOSA have formed a Joint O&M Special Interest Group (SIG) which is focused on including the MIMOSA CCOM concepts in ISO 15926 on an accelerated basis in order to enable the proper modeling and exchange of O&M oriented information. POSC Caesar Association and MIMOSA have also formed a Joint O&M SIG for IT Architecture which will focus on incorporating the OpenO&M specifications such as the ISBM in the overall IT solution to support the information exchanges and service methods being developed in the Joint O&M SIG.
