<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>Corresponding author.
$ nicolau.santos@inf.ufrgs.br (N. O. Santos); fhrodrigues@inf.ufrgs.br (F. H. Rodrigues); dschmidt@inf.ufrgs.br
(D. Schmidt); marabel@inf.ufrgs.br (M. Abel)</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>A Well-founded Domain Ontology For Ofshore Petroleum Production Plants</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Nicolau O. Santos</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Fabrício H. Rodrigues</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniela Schmidt</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mara Abel</string-name>
        </contrib>
      </contrib-group>
      <pub-date>
        <year>2022</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0003</lpage>
      <abstract>
        <p>This article outlines the approach used to create a domain ontology for characterizing the facilities in ofshore petroleum production plants. The ontology is being built using a comprehensive set of requirements gathered from industry and defined using a series of competency questions. The ultimate objective is to provide a standard, oficially defined reference vocabulary to assist engineers and information technology professionals in categorizing and connecting facilities and measures used in production plant monitoring and simulation. The ontology uses GeoCore and a continuing version of the core ontology created by the Industry Ontology Foundry (IOF) as middle-level ontologies and BFO as a top-level ontology. This study is a component of the Petwin project, which investigates the best methods for creating a digital twin for the industry's use in monitoring and modeling petroleum output.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;petroleum</kwd>
        <kwd>ontology</kwd>
        <kwd>production plants</kwd>
        <kwd>ofshore</kwd>
        <kwd>digital twins</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>Our project has the challenge of providing the framework for the semantic interoperability
of data operated by a digital twin of a petroleum production plant. The data that supports
production operation planning and control in petroleum plants are usually spread across many
systems from several service companies that perform specific tasks during operations. These
systems exchange data using proprietary or partially standardized formats. The integrated
operation center receives these data labeled with their source and meaning and analyzes them
to support short-term decisions. Petroleum engineers produce simulations to define the medium
to long-term operations plan and evaluate economic viability with this data.</p>
      <p>
        A digital twin (DT) implements a virtual mirror of a production plant to support monitoring,
simulation, prediction, and data analytics on the production and facility maintenance data[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
This real-time integrated view of a petroleum plant requires a uniform view of the data to
help operators supervise the behavior of oil flow and facilities in actual time. However, the
data transformation to a common platform or format would be an extraordinarily complex and
efort-demand task in such a diverse data volume. Then, a semantic tool to identify and describe
the data under a common descriptive vocabulary with an associated explicit description of
each term’s meaning and logical restrictions emerges as a valuable contribution to the data
integration problem. Many researchers have focused on using ontologies for this problem due
to their great potential in improving communication in digital twin environments [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>This paper presents the current development of the Ofshore Petroleum Production Plant
Ontology (O3PO), a well-founded domain ontology of production plant physical assets and
associated properties.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        When it comes to data management, the petroleum sector has several obstacles. The large
number of businesses that provide specialized services and utilize proprietary software creates
a complicated environment for handling field data across the whole supply chain. As a result,
a substantial efort has been undertaken to create industry standards in response to the
digitalization requirements of Industry 4.0. Some eforts in this way are the industry glossaries
like the Professional Petroleum Data Management (PPDM) "What is a Well?"1 and "What is a
Completion?"2. Also, there are initiatives to provide a semantic framework, such as the ontology
and reference library of ISO 15926 [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and a syntactic framework, such as the integrated data
platform from the Open Subsurface Data Universe Forum (OSDU)3, data standards of
Energistics Consortium, such as PRODML and RESQML standards, and the equipment specifications
from CFIHOS. The previous projects have centralized data accessibility in two approaches: (1)
defining a typical software architecture for data storage and access and (2) defining a standard
data model that supports an integrated view. Both approaches are complementary but leave
behind one of the complex aspects of data integration and interoperability: providing the users
and software applications an explicit representation of the meaning of the entities to support
the automatic alignment of data. Then, despite the referred eforts, accessing integrated data
and reasoning over it remains an issue in the ofshore environment, in which service companies,
operators, and platform leasing companies work together, but each with their distinct system.
In this way, we aim to develop an approach to deal with this issue in a better way.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Material and Methods</title>
      <p>
        We followed NeOn methodology [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]for the construction of our ontology. Following the steps
outlined in the process, the requirements specification was realized through a series of interviews
with subject matter experts from the sector, mostly petroleum engineers involved in the daily
operations of the petroleum facility. The professionals were questioned about their daily work,
information needs, and general activities during each one to two hour session. One ontology
expert and two domain experts conducted each interview over the phone while it was being
recorded. Following the transcription of the interviews, competency questions (CQs) were
1https://ppdm.org/ppdm/PPDM/Standards/What_is_a_Well/PPDM/What_is_a_Well.aspx
2https://ppdm.org/ppdm/PPDM/IPDS/What_is_a_Completion/PPDM/What_is_a_Completion.aspx
3https://osduforum.org
defined and used as specified requirements to create our ontology. Some examples of competency
questions we identified in this phase are provided in Table 1.
      </p>
      <p>
        The O3PO ontology uses BFO [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] as a top-level ontology. It is a straightforward, condensed,
and thoroughly documented fundamental ontology with a realist philosophical underpinning
that demonstrates its suitability for a material domain like the structure of a production plant.
Furthermore, because BFO is widely used across many areas, it can serve as a unifying framework
for other relevant ontologies created in the domain. The adopted version of BFO is 2.0, made
available in 2015. Besides BFO, O3PO derives some concepts from the GeoCore [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and the
Industrial Ontology Foundry (IOF) ontologies [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] middle-level ontologies. GeoCore, in particular,
provides GeoCore:rock and GeoCore:earth_fluid which were later specialized for the terms
reservoir and petroleum present in O3PO. IOF-Core provides a set of middle-level terms that
facilitate the definition of domain entities such as equipment in petroleum production.
      </p>
      <p>Prior to the conceptualization phase of ontology development, standards that provide
definitions were used as non-ontological resources to be later merged, producing a consensual formal
definition of entities. ISO 15926-4, and glossaries from PPDM were considered non-ontological
resources since they deliver such definitions. Table 2 shows some of the chosen terms along
with their semi-formal definitions.</p>
      <p>Definition
def. an IOF:engineered_system that is contained in a O3PO:wellbore
for producing or injecting fluid from or to a O3PO:reservoir.
def. an IOF:engineered_system that is composed of one or more
O3PO:pipe, that may also be composed of pipe joints, O3PO:pump,
O3PO:valve, and control devices, that has all its components connected
in a single line, and that can convey liquids, gases or finely divided solids.
def. an O3PO:pipeline that is installed in a O3PO:well, located inside all
casing strings, that extends from the O3PO:wellhead to the production or
injection O3PO:zone, to conduct fluids between the O3PO:reservoir and
the O3PO:christmas_tree.</p>
    </sec>
    <sec id="sec-4">
      <title>4. The ontology</title>
      <p>The taxonomy is shown in Figure 1 along with the primary categories of independent
continuants taken into account in the ontology. The main components of the oil path from
a O3PO:reservoir to a O3PO:platform are covered, passing through a O3PO:well, a
O3PO:christmas_tree, possibly a O3PO:manifold gathering the flow from several wells,
and the various O3PO:pipeline connecting these items.</p>
      <p>It also provides means to further detail the description of the oil path by including specific
instances of O3PO:tube and O3PO:valve that compose a pipeline or other pieces of equipment,
e.g., a christmas tree (related to the oil and gas domain). For instance, a pipeline is a system
that is composed of a combination of connected pipes, valves and other pieces of equipment
and that has the ability of conveying fluids, regardless the context in which it is present.</p>
      <p>Besides those, our ontology also includes categories for entities that are defined in terms
of their contingent aspect, notably, regarding the way in which an asset is being employed.
Among those, we have the O3PO:producer_well and O3PO:injector_well types, i.e., wells
involved in the flow of oil from the reservoir to the platform or from the platform to the reservoir,
respectively. We also have diferent subtypes of O3PO:pipeline, namely, O3PO:tubing (i.e.,
pipeline installed inside a well), O3PO:flowline (i.e., pipeline connecting the well to a manifold
or to a platform) and O3PO:riser (i.e., pipeline connecting a well or a manifold to a platform).
Those are entities defined as bearing certain BFO:roles.</p>
      <p>The ontology includes certain types of properties of importance for monitoring the state
of the plant. They are defined as specializations of BFO:quality and include both natural,
physical quantities (e.g., O3PO:temperature, O3PO:pressure) as well as properties that
artifacts have in virtue of their design (e.g., O3PO:valve_position, which corresponds to
the degree to which a valve is open/closed).</p>
    </sec>
    <sec id="sec-5">
      <title>5. Current State of Research</title>
      <p>
        The research is currently focused on modeling ocurrents for the realization of BFO:roles. Also
specializations of the relation "connected to" based on Flow Systems Ontology (FSO) are being
added[
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. The ontology is been applied to a dataset from Mero Field, in order to provide the
semantic requirements for a time-series visualization application generated as a product of
Petwin Project.
5.1. Publications
We submitted a full paper in Formal Ontologies Meet Industry (FOMI) conference held in Tarbes,
France, in October 2022. The paper was accepted and is currently published in the conference
proceedings [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Also, we are currently rewriting a journal paper to be submitted later this year.
      </p>
      <p>The ontology is available in a public repository at this link. Please feel free to point any
issues and problems.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Next Steps</title>
      <p>• Validate the ontology by comparing results obtained from the ontology to expected
answers of competency questions and applying to real data.</p>
      <p>• Finish writing documentation for the ontology and master’s thesis.</p>
    </sec>
    <sec id="sec-7">
      <title>7. Acknowledgements</title>
      <p>Research partially supported by CAPES (Funding Code 001), CNPq, and Project Petwin (financed
by FINEP and LIBRA Consortium).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>R.</given-names>
            <surname>Minerva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. M.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Crespi</surname>
          </string-name>
          ,
          <article-title>Digital Twin in the IoT Context: A Survey on Technical Features</article-title>
          , Scenarios, and Architectural Models,
          <source>Proceedings of the IEEE</source>
          <volume>108</volume>
          (
          <year>2020</year>
          ). doi:
          <volume>10</volume>
          . 1109/JPROC.
          <year>2020</year>
          .
          <volume>2998530</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>E.</given-names>
            <surname>Kharlamov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Skjaveland</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Hovland</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Mailis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Jimenez-Ruiz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Xiao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Soylu</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Horrocks</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Waaler</surname>
          </string-name>
          ,
          <article-title>Finding Data Should be Easier than Finding Oil</article-title>
          , in: Proceedings - 2018
          <source>IEEE International Conference on Big Data, Big Data</source>
          <year>2018</year>
          ,
          <year>2019</year>
          . doi:
          <volume>10</volume>
          .1109/ BigData.
          <year>2018</year>
          .
          <volume>8622035</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>International</given-names>
            <surname>Organization</surname>
          </string-name>
          for Standardization,
          <article-title>Industrial automation systems and integration - Integration of life-cycle data for process plants including oil and gas production facilities - Part 4: Initial reference data (ISO/TS Standard No</article-title>
          .
          <issue>15926-4</issue>
          ),
          <year>2019</year>
          . URL: https://www.iso.org/standard/73830.html.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M. C.</given-names>
            <surname>Suárez-Figueroa</surname>
          </string-name>
          ,
          <article-title>NeOn Methodology for Building Ontology Networks: Specification, Scheduling and Reuse (</article-title>
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>J. N.</given-names>
            <surname>Otte</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Beverley</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ruttenberg</surname>
          </string-name>
          , BFO: Basic Formal Ontology,
          <source>Applied Ontology</source>
          <volume>17</volume>
          (
          <year>2022</year>
          )
          <fpage>17</fpage>
          -
          <lpage>43</lpage>
          . doi:
          <volume>10</volume>
          .3233/AO-220262.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>L. F.</given-names>
            <surname>Garcia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Abel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Perrin</surname>
          </string-name>
          , R. dos Santos Alvarenga,
          <article-title>The GeoCore ontology: A core ontology for general use in Geology</article-title>
          ,
          <source>Computers &amp; Geosciences</source>
          <volume>135</volume>
          (
          <year>2020</year>
          )
          <article-title>104387</article-title>
          . doi:
          <volume>10</volume>
          .1016/J.CAGEO.
          <year>2019</year>
          .
          <volume>104387</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>B.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Ameri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Cheong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Kiritsis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Sormaz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Will</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. N.</given-names>
            <surname>Otte</surname>
          </string-name>
          ,
          <article-title>A First-Order Logic Formalization of the Industrial Ontology Foundry Signature Using Basic Formal Ontology</article-title>
          ,
          <source>in: Proceedings of the Joint Ontology Workshops (JOWO)</source>
          ,
          <year>Graz</year>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>V.</given-names>
            <surname>Kukkonen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kücükavci</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Seidenschnur</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. H.</given-names>
            <surname>Rasmussen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. M.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. A.</given-names>
            <surname>Hviid</surname>
          </string-name>
          ,
          <article-title>An ontology to support flow system descriptions from design to operation of buildings, Automation in Construction 134 (</article-title>
          <year>2022</year>
          ). doi:
          <volume>10</volume>
          .1016/J.AUTCON.
          <year>2021</year>
          .
          <volume>104067</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>N. O.</given-names>
            <surname>Santos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Abel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. H.</given-names>
            <surname>Rodrigues</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Schmidt</surname>
          </string-name>
          ,
          <article-title>Towards an ontology of ofshore petroleum production equipment (</article-title>
          <year>2022</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>