<!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>FOMI</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Ontology-Based Cloud Manufacturing Framework in Industrialized Construction</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jianpeng Cao</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Edlira Vakaj</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniel Hall</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Basic info</institution>
          ,
          <addr-line>Functional info, QoS, status, Capacity Resources, Services, Owners, Knowledge, Transaction, Status Basic info, Functional info, Process Basic info, Functional info, Status, QoS Basic information, Sub-tasks, Relations, Demand, Status Task information, Sub-tasks, Relations</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Birmingham City University</institution>
          ,
          <addr-line>Millennium Point, 1 Curzon Street, Birmingham, B4 7XG</addr-line>
          ,
          <country country="UK">United Kingdom</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>ETH Zürich</institution>
          ,
          <addr-line>Stefano-Franscini-Platz 5, 8049 Zürich</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2021</year>
      </pub-date>
      <volume>11</volume>
      <fpage>11</fpage>
      <lpage>18</lpage>
      <abstract>
        <p>Cloud manufacturing is an emerging manufacturing paradigm to enable rapid production for mass customization. Industrialized construction shares a similar production environment with manufacturing products, so it has a great potential to utilize the paradigm. Previous studies never examined cloud manufacturing in the construction context. This work takes the industrial diference into account and proposes a cloud manufacturing framework by ontology modeling. Three ontologies, including ifcOWL, OPW, and OWL-S, are linked to support the design to the manufacturing process of a building project. The framework benefits the design data and manufacturing data integration, and enhances the resource sharing by semantic web service.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;cloud manufacturing</kwd>
        <kwd>ontology</kwd>
        <kwd>design for manufacturing and assembly</kwd>
        <kwd>BIM</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Cloud manufacturing is a new manufacturing paradigm, driven by the trend of mass
customization, globalization, digitalization in the industry 4.0 era. The paradigm is built upon emerging
technologies, such as service-oriented architecture (SOA), Internet of Things (IoT), and artificial
intelligence (AI) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Similar to cloud computing sharing computing services – servers, storage,
databases, software, cloud manufacturing provides on-demand manufacturing services –
machines, materials, analytic tools, experimentation, to customers via the Internet, to facilitate
the distributed resource utilization and the cross-enterprise collaboration [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Although cloud
manufacturing has been researched in the context of the manufacturing industry since 2009 [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ],
there are few studies on adapting the paradigm to the construction industry.
      </p>
      <p>Industrialized construction follows a design-manufacturing-assembly approach to deliver
new buildings comprised of kit-of-parts, ranging from linear structural elements (e.g., columns
and beams), planar elements (e.g., panels and trusses), to volumetric units (e.g., bathroom
pods). The kit-of-parts share a similar production environment with manufacturing products.
However, diferences also exist in the aspects of product characteristics, supply chain models
and supporting hardware and software. For example, one diference is the domain knowledge
used to design a product. Therefore, it requires a novel model to support cloud manufacturing
in the construction industry.</p>
      <p>
        Ontology is a formal representation of domain knowledge, supporting knowledge sharing
in distributed enterprise organizations. Recently, well-designed ontology-based models are
applied to information modeling in cloud manufacturing [
        <xref ref-type="bibr" rid="ref4 ref5 ref6 ref7">4, 5, 6, 7</xref>
        ]. However, none of these
models is built upon existing construction knowledge. Besides, most models only address the
manufacturing concepts without bridging the gap between design and manufacturing. For
construction products, building information models (BIM) are widely used on the design stage.
BIM is a shared digital representation of a built asset to facilitate design, construction and
operation processes. Considering the fact that many design semantics are available in the BIMs,
ontology can map this semantic knowledge to the manufacturing domain, aiming at design for
manufacturing and assembly (DfMA).
      </p>
      <p>
        In this paper, we present an ontology-based framework for cloud manufacturing development.
The framework is developed based on the of-site production workflow ontology (OPW), which
represents ofsite construction domain terminology and relationships. The ontology is linked
to the ifcOWL ontology to capture design details defined in BIM applications, such as Revit.
Next, to transform manufacturing resources and manufacturing capabilities into manufacturing
services, which can be used for small-batch customized design, those sources and capabilities
are virtualized as web services and managed in a unified way by OWL-S framework [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. The
applications, such as service search and allocation, are built upon the developed ontology.
      </p>
      <p>The rest of the paper is organized as follows: Section 2 introduces the state-of-the-art related
to ontology-based cloud manufacturing. Section 3 presents our proposed approach. Section 4
discusses the limitation of the proposed framework. Finally, section 5 concludes our work and
introduces the future works.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        In contrast to other sectors, the construction industry is slower in utilizing ontologies in practice
and research. Existing ontologies established in the construction industry include: ifcOWL [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ],
Building Topology Ontology (BTO) [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], and Building Product Ontology (BPO) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and Ofsite
Manufacturing Production Workflow ontology ( OPW ). The applications of these ontologies
are focused on knowledge management, BIM, cost management, quality checking, and safety
analysis [12]. Considering that the first three ontologies lack the DfMA concepts for ofsite
manufacturing [13], we prioritize the OPW ontology for cloud manufacturing development.
Therefore, this section firstly reviews the ontologies for DfMA. Then, the operation model of
cloud manufacturing is introduced. In the end, how ontology modeling is applied to cloud
manufacturing is analyzed.
      </p>
      <sec id="sec-2-1">
        <title>2.1. Ontologies for DfMA</title>
        <p>Design for manufacturing and assembly (DfMA) is first developed for product design, aiming
for reducing production time and cost by evaluating manufacturing and assembly performance
during design phase. Related work on ontologies for DfMA is still under development. Many
researchers developed their own DfMA ontologies for task-specific domains. An et al define a
product ontology for wood frame intersections. Based on the ontology, feasible manufacturing
operations can be retrieved [14]. Favi et al. use an ontology to formalize the welding knowledge.
The appropriate welding methods are derived according to the geometric features [15]. By
comparison, Ayinla et al. established a comprehensive of-site production workflow ontology
(OPW), which models the production process from material delivery to transportation of
products to the site. Our work is built upon the OPW ontology, aiming at providing manufacturing
services for customized kit-of-parts.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Operation Model of Cloud Manufacturing</title>
        <p>
          A cloud manufacturing system consists of main stakeholders, namely service consumers, service
providers and service operators [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ].
        </p>
        <p>
          • Consumers submit design files to the cloud manufacturing platform and receive
manufacturing quotes and service recommendations from the available manufactures registered on
the platform. In the construction industry, service consumers include general contractors,
design firms, and individual consumers;
• Providers are able to publish their available manufacturing resources on the cloud platform
and receive the design orders assigned by the platform. Service providers are construction
companies who own the factories and manufacturing equipment;
• Operators refer to the agents on the cloud manufacturing platform who manage the design
orders from the service consumers and manufacturing resource from service providers;
Typical cloud manufacturing services include soft manufacturing resource, hard
manufacturing resource, service resource, manufacturing capacities and other resource [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. This work
focuses on hard manufacturing resource, such as machining centers. Due to the fluctuation of
the housing market, manufacturers are motivated to increase the resource utilization and avoid
resource waste.
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3. Ontology-based Cloud Manufacturing</title>
        <p>
          The study of ontology in cloud manufacturing is done in two aspects: manufacturing service
modeling for service providers [
          <xref ref-type="bibr" rid="ref4 ref6">4, 6, 16, 17</xref>
          ] and manufacturing task modeling for service
consumers [
          <xref ref-type="bibr" rid="ref7">7, 18</xref>
          ]. Table 1 summarizes the main concepts in the ontologies. The basic information,
including service/task name, type, location., are used for identification. The functional
information, including input/output, precondition, are used for task-service matching. The quality
of service (QoS), such as cost, time limit, reliability., are decision-making factors for service
allocation. The status manifests the load condition and fault condition, which are important for
service scheduling and monitoring.
        </p>
      </sec>
      <sec id="sec-2-4">
        <title>2.4. Cloud Manufacturing System Framework</title>
        <p>The development of a cloud manufacturing framework has attracted considerable attention from
academia and industry. Many scholars use the multi-layer construction method to establish
the system. Ming et al. analyzed the similarities among 66 articles and identified six main
layers, including application layer, resource layer, core service layer, resource virtualization
layer, application interface layer, and basic supporting layer [19]. However, they did not explore
the role of ontology in the system. The ontology acts as a role of transferring domain knowledge,
which is crucial for adapting the framework in the construction industry. In this research, an
ontology layer is set on the back end to support the service search and allocation. The interface
design, as well as the use of other supporting techniques, is ignored in this research.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Proposed Approach</title>
      <p>In this section, the framework of cloud manufacturing for industrialized construction is
presented. The framework contains three layers: (1) user layer; (2) application layer; (3) ontology
layer. The architecture of the proposed framework is illustrated in Figure 2. The user layer
reads data input. There are two types of data inputs: design files and manufacturing resource
profiles. The data model will be created in the ontology layer and instantiated by the input.
Then, Shapes Constraint Language (SHACL) rules are used for data validation. Next, semantic
matching will be performed for service search. In the end, service allocation is implemented to
return service recommendations for users.</p>
      <sec id="sec-3-1">
        <title>3.1. User layer</title>
        <sec id="sec-3-1-1">
          <title>3.1.1. Building Information Model (BIM)</title>
          <p>The user input is an industrialized construction project modeled in BIM applications. Revit
is a widely used BIM tool for product modeling. Unlike other CAD software used in the
manufacturing industry, it incorporates domain concepts and relationships, such as element
types, materials and geometries. The project information, classified in the model, supports
the manufacturing analysis and further drives the service search. To achieve interoperability
between various BIM applications, Industry Foundation Classes (IFC), a neutral, non-proprietary
data model is required. An example of timber panels modeled in Revit is shown in Figure 3.</p>
        </sec>
        <sec id="sec-3-1-2">
          <title>3.1.2. Manufacturing Service Modeling</title>
          <p>For industrialized construction, the manufacturing service consists of detailed design
development, production, of/on-site assembly, and delivery. The granularity of a manufacturing
service is dependent on project itself. A finer granularity can refer to a production activity,
such as panel framing. A composite service can fulfill an value-added task. From the previous
review, four main categories are used to model a service, namely basic information, functional
information, QoS and status. In detail, Table 2 shows some properties for each category. An
example of panel assembly service is given in Table 3.</p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Ontology Layer</title>
        <sec id="sec-3-2-1">
          <title>3.2.1. IfcOWL Ontology</title>
          <p>
            Each IFC data model is represented as a schema in the EXPRESS data specification language
defined in ISO 10303-11:2004. Since the IfcOWL is automatically generated from the EXPRESS
schema using the “IFC-to-RDF" converter [
            <xref ref-type="bibr" rid="ref9">9</xref>
            ], it maintains almost the same information as
defined in BIM applications. The ontology contains general concepts of building components,
such as “IfcWall", and their properties, such as “IfcRectangleProfileDef" for a rectangular
geometry and “IfcMaterial" for building material. Acting as a common knowledge base, IfcOWL
is used in the framework to identify ambiguous information defined in BIM.
          </p>
        </sec>
        <sec id="sec-3-2-2">
          <title>3.2.2. OPW Ontology</title>
          <p>Due to the lack of DfMA concepts for industrialized construction, the design information in
ifcOWL cannot be directly used for the manufacturing domain. IfcOWL does not contain
descriptions on manufacturing resources and production processes. To bridge the design and
manufacturing domain, the OPW ontology is aimed to associate the product components with
production approaches and required resources. In the OPW ontology, there are eight major
classes, including building, product, resources, activity, process type, workstation, production
process and factory production method. Besides, some key properties are defined in the ontology,
such as “isA", “hasComponentPart", “consumes", “consistOf". The ontology enables practitioners
in industrialized construction to formalize the product description and production planning.
Take a panel production as an example, OPW specifies the sequential production activities, and
required labor, material, equipment and overhead.</p>
        </sec>
        <sec id="sec-3-2-3">
          <title>3.2.3. OWL-S Ontology</title>
          <p>
            Semantic web service (SWS) technology is used to describe concepts of manufacturing services
on the one hand, and relationships to the OPW ontology on the other hand. OWL-S provides a
standard specification approach for service definition, execution and monitoring. The
description of a service via OWL-S contains four conceptual areas: the process, the service, the profile
and the grounding model [
            <xref ref-type="bibr" rid="ref8">8</xref>
            ]. In this work, the profile model is mainly used, as it contains a set
of concepts and properties relating to a service definition. Specifically, the basic information
of a service, such as service name and service provider, can be defined in the profile model as
“serviceName” and “contactInformation”. The functional information of a service, including
parameters, inputs, outputs, preconditions, and results, can be defined and related to a service
class via a set of properties in the model, such as “hasInput” and “hasParameter”.
          </p>
        </sec>
        <sec id="sec-3-2-4">
          <title>3.2.4. Ontology Alignment</title>
          <p>The three fundamental ontologies mentioned above act as an integral to support the
information modeling of cloud manufacturing. First, the ifcOWL supports the preliminary design
analysis from the user aspect. Second, the OWL-S describes the manufacturing service from
the manufacturer aspect. Finally, the OPW ontology connects the design information to
manufacturing information by specifying the product structures and corresponding production
processes. The "IfcElement" class in IfcOWL is connected to "BuildingElement" class in OPW,
while "ServiceCategory" class in OWL-S is connected to "Production Process" class in OPW.
The entire architecture of the ontology for cloud manufacturing is shown in Figure 4.</p>
        </sec>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Application Layer</title>
        <sec id="sec-3-3-1">
          <title>3.3.1. Data Extraction</title>
          <p>According to IFC standard, the design parameters of a BIM object are defined as IFC entities.
To support manufacturing analysis, element types, shapes, dimensions, and materials are of
great importance and extracted from the IFC file. Table 4 shows the relationship between the
extracted parameters and the IFC entities. The data extraction is done by IfcOpenShell, an
open-source software library that helps developers to work with IFC file format.</p>
        </sec>
        <sec id="sec-3-3-2">
          <title>3.3.2. Data Validation</title>
          <p>The Level of Development (LOD) specification, developed by America Institute of Architects
(AIA) articulates the characteristics of the BIM models at various stages in the design and
construction process. For example, a timber exterior wall at LOD 200 should be modeled as an
object with layouts and locations, layers of materials, as well as approximate thickness [20].
The LOD specification is encoded as SHACL rules to check the necessary data entries and
required data types from consumers. Figure 5 displays a SHACL rule to check the wall entry
with geometric parameters and necessary structures.</p>
        </sec>
        <sec id="sec-3-3-3">
          <title>3.3.3. Service Search</title>
          <p>Once the ontology is instantiated by user inputs representing a product order and various
manufacturing resources, service search can be conducted by input/output matching [21].
The matching algorithm consists of three steps: elimination, similarity measurement, and
aggregation. In the context of cloud manufacturing, the elimination stage is to narrow down the
candidates for matching to the service classes and sub-classes. Additionally, the services which
have a running status are also eliminated. Then, the similarity of concepts and properties is
measured respectively. For example, material and geometry can be set as comparing factors. In
the end, the conceptual similarity and property similarity are aggregated as a weighted average.</p>
        </sec>
        <sec id="sec-3-3-4">
          <title>3.3.4. Service Allocation</title>
          <p>The objective of this step is to select manufacturing services and allocate workloads to them so
that the design order can be fulfilled optimally. We model resource allocation as a constrained
multi-objective optimization. The manufacturing time and cost are set as objectives of the
optimization. Other objectives, such as distance, can also be used. Some assumptions are made
in advance: (1) one service can only be assigned to one order at a time. (2) the workloads
designated to each service should be multiples of the minimum batch size. (3) all services are
available at the initial stage. (4) When an order is assigned to multiple manufacturers, the
manufacturing time is calculated as the maximum production time among them.</p>
          <p>In detail, the manufacturing time is calculated as:
 = (  1 ,  2 , ...,  
  (1)   (2)   ()
)
(1)
where   the workload allocated to service i.   (· ) returns the productivity rate
of the service i. The sum of all workloads should equal the total quantity of the order (Total),
shown as below:</p>
          <p>The manufacturing cost is calculated as:</p>
          <p>∑︁   =  
=1</p>
          <p>= ∑︁   ·</p>
          <p>=1
where  is the product unit cost of the service i.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Discussion</title>
      <p>The proposed framework adapts the cloud manufacturing model in the construction industry.
The major diferences to the framework in the manufacturing industry lie in two aspects: (1) the
domain knowledge is extracted from BIM and mapped to domain ontologies, namely ifcOWL
and OPW. (2) the service granularity is the production-line level, which determines the service
search and allocation strategy. However, the framework has some limitations:
• There is a lack of real-time resource availability information. The information can be
obtained using IOT technology.
• The service-to-task relationship is one-to-one, which is not fit for complex products. A
mechanism of service composition is required.
• The service scheduling is lacking in the current framework. Construction products are
transported to site and assembled. Therefore, logistics factors, such as transportation,
need to be considered in the service scheduling.
(2)
(3)</p>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion</title>
      <p>Similar to the manufacturing industry, the construction market is facing a demand of
customization. Clients are eager to participate in the design or manufacturing process. Cloud
manufacturing provides clients with on-demand services to their various design requirements.
From the manufacturing enterprises perspective, the paradigm enables them to enhance
resource utilization by eficient resource sharing and allocation within an enterprise network.
However, challenges still exist in many aspects. The main contribution of this work is an
ontology-based cloud manufacturing framework for industrialized construction. To model the
domain knowledge and manufacturing service, three ontologies, namely ifcOWL, OPW, and
OWL-S, are used. The framework is aimed at (1) analyzing the design requirements in BIM, (2)
creating a manufacturing service pool, (3) searching competent service by semantic matching,
and (4) allocating resources by multi-objective optimization. It is expected that the framework
will contribute to cloud manufacturing platform development in future research.
Proceedings of the 7th Linked Data in Architecture and Construction workshop (LDAC
2019)’, Lisbon, Portugal, 2019, p. 12.
[12] Z. Zhou, Y. M. Goh, L. Shen, Overview and analysis of ontology studies supporting
development of the construction industry, Journal of Computing in Civil Engineering 30
(2016) 04016026.
[13] K. Ayinla, E. Vakaj, F. Cheung, A.-R. H. Tawil, A semantic ofsite construction digital
twin-ofsite manufacturing production workflow (opw) ontology, in: Second International
Workshop on Semantic Digital Twins, 2021.
[14] S. An, P. Martinez, M. Al-Hussein, R. Ahmad, Bim-based decision support system for
automated manufacturability check of wood frame assemblies, Automation in Construction
111 (2020) 103065.
[15] C. Favi, R. Garziera, F. Campi, A rule-based system to promote design for manufacturing
and assembly in the development of welded structure: Method and tool proposition,
Applied Sciences 11 (2021) 2326.
[16] X. Li, P. Zhuang, C. Yin, A metadata based manufacturing resource ontology modeling in
cloud manufacturing systems, Journal of Ambient Intelligence and Humanized Computing
10 (2019) 1039–1047.
[17] N. Liu, X. Li, W. Shen, Multi-granularity resource virtualization and sharing strategies in
cloud manufacturing, Journal of Network and Computer Applications 46 (2014) 72–82.
[18] Y. He, Q. L. Zhang, D. C. Hu, Research on ontology-based task modeling in manufacturing
grid, in: Applied Mechanics and Materials, volume 63, Trans Tech Publ, 2011, pp. 537–540.
[19] M. K. Lim, W. Xiong, C. Wang, Cloud manufacturing architecture: a critical analysis of
its development, characteristics and future agenda to support its adoption, Industrial
Management &amp; Data Systems (2021).
[20] J. Bedrick, J. Reinhardt, W. Ikerd, Level of development specification, 2020. URL: https:
//bimforum.org/lod/.
[21] N. Trokanas, F. Cecelja, T. Raafat, Semantic input/output matching for waste processing
in industrial symbiosis, Computers &amp; Chemical Engineering 66 (2014) 259–268.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X. V.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <surname>L. Zhang,</surname>
          </string-name>
          <article-title>Scheduling in cloud manufacturing: state-ofthe-art and research challenges</article-title>
          ,
          <source>International Journal of Production Research</source>
          <volume>57</volume>
          (
          <year>2019</year>
          )
          <fpage>4854</fpage>
          -
          <lpage>4879</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Y</given-names>
            <surname>.-K. Lin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. S.</given-names>
            <surname>Chong</surname>
          </string-name>
          ,
          <article-title>Fast ga-based project scheduling for computing resources allocation in a cloud manufacturing system</article-title>
          ,
          <source>Journal of Intelligent Manufacturing</source>
          <volume>28</volume>
          (
          <year>2017</year>
          )
          <fpage>1189</fpage>
          -
          <lpage>1201</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>L.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Luo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Tao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B. H.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Ren</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , H. Guo, Y. Cheng, A. Hu, Y. Liu,
          <article-title>Cloud manufacturing: a new manufacturing paradigm</article-title>
          ,
          <source>Enterprise Information Systems</source>
          <volume>8</volume>
          (
          <year>2014</year>
          )
          <fpage>167</fpage>
          -
          <lpage>187</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M.</given-names>
            <surname>Yuan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Deng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W. A.</given-names>
            <surname>Chaovalitwongse</surname>
          </string-name>
          ,
          <article-title>Manufacturing resource modeling for cloud manufacturing</article-title>
          ,
          <source>International Journal of Intelligent Systems</source>
          <volume>32</volume>
          (
          <year>2017</year>
          )
          <fpage>414</fpage>
          -
          <lpage>436</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Lu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <article-title>A semantic web-based framework for service composition in a cloud manufacturing environment</article-title>
          ,
          <source>Journal of manufacturing systems 42</source>
          (
          <year>2017</year>
          )
          <fpage>69</fpage>
          -
          <lpage>81</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>W.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Zhou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Xie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. T.</given-names>
            <surname>Pham</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ji</surname>
          </string-name>
          ,
          <article-title>Dynamic modeling of manufacturing equipment capability using condition information in cloud manufacturing</article-title>
          ,
          <source>Journal of Manufacturing Science and Engineering</source>
          <volume>137</volume>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>T.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Guo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.-G.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <article-title>Manufacturing task semantic modeling and description in cloud manufacturing system</article-title>
          ,
          <source>The International Journal of Advanced Manufacturing Technology</source>
          <volume>71</volume>
          (
          <year>2014</year>
          )
          <fpage>2017</fpage>
          -
          <lpage>2031</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>D.</given-names>
            <surname>Martin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Burstein</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Hobbs</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Lassila</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>McDermott</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>McIlraith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Narayanan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Paolucci</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Parsia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Payne</surname>
          </string-name>
          , et al.,
          <article-title>Owl-s: Semantic markup for web services</article-title>
          ,
          <source>W3C member submission 22</source>
          (
          <year>2004</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>P.</given-names>
            <surname>Pauwels</surname>
          </string-name>
          , W. Terkaj,
          <article-title>Express to owl for construction industry: Towards a recommendable and usable ifcowl ontology</article-title>
          ,
          <source>Automation in construction 63</source>
          (
          <year>2016</year>
          )
          <fpage>100</fpage>
          -
          <lpage>133</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M. H.</given-names>
            <surname>Rasmussen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lefrançois</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. F.</given-names>
            <surname>Schneider</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Pauwels</surname>
          </string-name>
          ,
          <article-title>Bot: The building topology ontology of the w3c linked building data group</article-title>
          , Semantic
          <string-name>
            <surname>Web</surname>
          </string-name>
          (
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>19</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>A.</given-names>
            <surname>Wagner</surname>
          </string-name>
          , U. Rüppel,
          <article-title>Bpo: the building product ontology for assembled products</article-title>
          , in:
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>