<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML"
         xmlns:xlink="http://www.w3.org/1999/xlink"
         article-type="methods-article"
         dtd-version="1.2"
         xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">Digital Twin</journal-id>
            <journal-title-group>
                <journal-title>Digital Twin</journal-title>
            </journal-title-group>
            <issn pub-type="epub">2752-5783</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/digitaltwin.17489.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Method Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Digital twin-driven complexity management in intelligent manufacturing</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: 2 approved]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Wang</surname>
                        <given-names>Yuchen</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Investigation</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-8384-1742</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Wang</surname>
                        <given-names>Xingzhi</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-6951-7425</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Tao</surname>
                        <given-names>Fei</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Resources</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-9020-0633</uri>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Liu</surname>
                        <given-names>Ang</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Project Administration</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-9353-0948</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>School of Mechanical and Manufacturing Engineering, University of New South Wales, Sydney, 2053, Australia</aff>
                <aff id="a2">
                    <label>2</label>School of Automation Science and Electrical Engineering, Beihang University, Beijing, 100191, China</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:ang.liu@unsw.edu.au">ang.liu@unsw.edu.au</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>11</day>
                <month>11</month>
            <year>2021</year>
            </pub-date>
            <pub-date pub-type="collection">
            <year>2021</year>
            </pub-date>
         <volume>1</volume>
            <elocation-id>9</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>22</day>
                    <month>10</month>
               <year>2021</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2021 Wang Y et al.</copyright-statement>
                <copyright-year>2021</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://digitaltwin1.org/articles/1-9/pdf"/>
            <abstract>
                <p>Complexity management is one of the most crucial and challenging issues in manufacturing. As an emerging technology, digital twin provides an innovative approach to manage complexity in a more autonomous, analytical and comprehensive manner. This paper proposes an innovative framework of digital twin-driven complexity management in intelligent manufacturing. The framework will cover three sources of manufacturing complexity, including product design, production lines and supply chains. Digital twin provides three services to manage complexity: (1) real-time monitors and data collections; (2) identifications, diagnoses and predictions of manufacturing complexity; (3) fortification of human-machine interaction. A case study of airplane manufacturing is presented to illustrate the proposed framework.</p>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>Cyber-physical system</kwd>
                <kwd>Digital twin</kwd>
                <kwd>Complexity Management</kwd>
                <kwd>Intelligent Manufacturing</kwd>
                <kwd>Engineering Design</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1" xlink:href="http://dx.doi.org/10.13039/501100001773">
                    <funding-source>National Natural Science Foundation of China</funding-source>
                    <award-id>52120105008</award-id>
                </award-group>
                <funding-statement>This research is funded by the Key Project of International (Regional) Cooperation and Exchange of the National Natural Science Foundation of China (52120105008). The principal investigators are Fei Tao and Ang Liu.</funding-statement>
                <funding-statement>
                    <italic>The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.</italic>
                </funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec sec-type="intro">
            <title>Introduction</title>
            <p>The importance of complexity management in manufacturing can never be overstated. Complexity management significantly influences decision-making, lead time, reliability, flexibility and cost of manufacturing processes
                <sup>
                    <xref ref-type="bibr" rid="ref-1">1</xref>
                </sup>. Such influences appear to be more severe for large-scale manufacturing projects (airplanes, shield tunneling machines, precision machine tools, etc.) due to their interdisciplinarity, multisystem and multitasking. Conventionally, complexity management in manufacturing merely contains the trade-off among changeability, operational flexibility and responsiveness
                <sup>
                    <xref ref-type="bibr" rid="ref-2">2</xref>
                </sup>. Nowadays, as researchers tend to place more emphasis on lifecycle management, the coverage of complexity management is being broadened by additional issues
                <sup>
                    <xref ref-type="bibr" rid="ref-3">3</xref>
                </sup>. Manufacturing complexity has two typical definitions: In the physical domain, manufacturing complexity is defined as information required to describe the system
                <sup>
                    <xref ref-type="bibr" rid="ref-3">3</xref>
                </sup>. In the functional domain, manufacturing complexity is defined as uncertainties in achieving functional requirements
                <sup>
                    <xref ref-type="bibr" rid="ref-4">4</xref>
                </sup>. Complexity management is widely considered as one of the most challenging engineering objectives as it remains ambiguous and couples with abundant engineering factors.</p>
            <p>Several factors push the rapid growth of manufacturing complexity. One such factor can be more features (functions, systems, concepts) in products. To achieve these additional features, the number of parts contained in products keeps climbing, which introduces more dimensional constraints, interferences and difficulties in connectivity. Besides, product features appear in a multi-discipline manner
                <sup>
                    <xref ref-type="bibr" rid="ref-5">5</xref>
                </sup>. For example, as a typical home appliance, a modern washing machine often contains a centrifuge (mechanical product), control panels (electronic product) and a dedicated application program (software product). Market competition is another important factor that promotes manufacturing complexity. In many industries, companies ought to keep compressing lead time, reducing costs, and improving usage rates of machines to gain advantages in competition. To achieve these goals, engineers keep optimizing operation processes and structures of manufacturing systems. Manufacturing complexity thus grows during this process
                <sup>
                    <xref ref-type="bibr" rid="ref-6">6</xref>
                </sup>. Moreover, manufacturing complexity is also promoted by global production (or distributed manufacturing). Globally distributed supply chains introduce information inconsistencies (miscommunication among suppliers, producers and consumers), environmental uncertainties and onerous logistics
                <sup>
                    <xref ref-type="bibr" rid="ref-7">7</xref>
                </sup>. Consequently, engineers are facing more and more challenges in complexity management in manufacturing.</p>
            <p>Intelligent manufacturing is coevolving with complexity management. Compared to the conventional mode, intelligent manufacturing tends to be more digital, active, autonomous, adaptable and efficient. Following this trend, intelligent manufacturing will transform complexity management in three aspects: (1) Complexity management will be more data-contextualized to improve the reliabilities of decision-making. (2) Complexity management will be more autonomous. Many human interventions can be replaced by artificial intelligence (AI) and automatic machines. (3) Complexity management will investigate product lifecycles to consider their impacts on design, usage, maintenance and disposal
                <sup>
                    <xref ref-type="bibr" rid="ref-8">8</xref>&#x2013;
                    <xref ref-type="bibr" rid="ref-10">10</xref>
                </sup>. Meanwhile, complexity management guides the realization of intelligent manufacturing. Intelligent manufacturing is an intricate framework that consists of copious systems (e.g., automated systems, ergonomic systems, data-processing systems) and units (e.g., assembly machines, conveyance machines, inspection machines). Besides, intelligent manufacturing deals with fluctuating working environments. In this condition, complexity management becomes crucial to coordination, reliabilities and adaptability in intelligent manufacturing. </p>
            <p>As an emerging technology, the digital twin (DT) plays a vital role in intelligent manufacturing. In the beginning, DT was proposed by Grieves in terms of lifecycle management
                <sup>
                    <xref ref-type="bibr" rid="ref-11">11</xref>
                </sup>. Later, Glaessgen and Stargel redefined DT as an integrated multiscale, multiphysics, probabilistic simulation to mirror the lifecycle of its physical twin
                <sup>
                    <xref ref-type="bibr" rid="ref-12">12</xref>
                </sup>. In this phase, DT was formulated as a three-dimensional model including the physical product, its virtual twin and their data exchanges. In recent years, the method of DT has been being enriched with more technologies, applications and concepts. Tao's research team expanded DT into a five-dimensional model, including physical entity (PE), virtual entity (VE), twin data (TD), services (SV) and connections
                <sup>
                    <xref ref-type="bibr" rid="ref-13">13</xref>
                </sup>. Compared to conventional interactions between physical and virtual spaces, DT has three unique features: (1) DT achieves the synchronization between PE and VE. (2) DT dramatically raises the volume of data via its real-time and comprehensive data collections. (3) DT builds high-fidelity virtual models to reflect details in the physical world
                <sup>
                    <xref ref-type="bibr" rid="ref-14">14</xref>
                </sup>. To date, DT is used chiefly for the maintenance and operation of large-scale products such as airplanes and wind turbines. For example, Tugel 
                <italic toggle="yes">et al</italic>. firstly proposed to implement DTs to predict the airplane structural life
                <sup>
                    <xref ref-type="bibr" rid="ref-15">15</xref>
                </sup>. General Electric applied DTs to its wind farms
                <sup>
                    <xref ref-type="bibr" rid="ref-16">16</xref>
                </sup>. There have been limited investigations on applications of DT on manufacturing design.</p>
            <p>This paper is written to envision the DT-driven complexity management in intelligent manufacturing. For the rest of this paper, Section 2 will review conventional complexity management and intelligent manufacturing to indicate the importance of digital twins. Section 3 will envision an innovative framework of DT-driven complexity management. This framework will cover three important sources of manufacturing complexity, including product design, production lines and supply chains. Section 4 will illustrate the proposed framework with a case study of airplane manufacturing. Section 5 will conclude and discuss future work. Nomenclatures used in the paper are shown in 
                <xref ref-type="table" rid="T1">Table 1</xref>.</p>
            <table-wrap id="T1" orientation="portrait" position="anchor">
                <label>Table 1. </label>
                <caption>
                    <title>Nomenclatures in the paper.</title>
                </caption>
                <table content-type="article-table" frame="hsides">
                    <thead>
                        <tr>
                            <th align="left" colspan="2" rowspan="1" valign="top">Nomenclatures</th>
                        </tr>
                    </thead>
                    <tbody>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">AI</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Artificial intelligence </td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">AR</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Augmented reality</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">BSV</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Business service</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">CPS</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Cyber-physical space</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">DT</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Digital twin</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">FSV</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Functional services</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">IoT</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Internet of things</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">PE</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Physical entity</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">SV</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Service</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">TD</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Twin data</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">VE</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Virtual entity</td>
                        </tr>
                    </tbody>
                </table>
            </table-wrap>
        </sec>
        <sec>
            <title>Importance of digital twin: a simple review from complexity management to intelligent manufacturing</title>
            <sec>
                <title>Manufacturing complexity and growing challenges</title>
                <p>Complexity exists in every single corner of manufacturing. In 2012, EIMaraghy 
                    <italic toggle="yes">et al</italic>. summarized sources of manufacturing complexity and classified them into three categories, including: (1) design and product development complexity (number of parts, manufacturability, size, etc.); (2) manufacturing systems complexity (changeability, flexibility, and operations of production line); (3) business and market complexity (supply chain, global competition, and market turbulence)
                    <sup>
                        <xref ref-type="bibr" rid="ref-3">3</xref>
                    </sup>. In this paper, discussions about manufacturing complexity will concentrate on those from product design, production lines, and supply chains.</p>
                <p>As introduced, there are two typical definitions of complexity: In the physical domain, manufacturing complexity is defined as information required to describe the states of a system
                    <sup>
                        <xref ref-type="bibr" rid="ref-3">3</xref>
                    </sup>. In the functional domain, manufacturing complexity is defined as uncertainties in achieving functions
                    <sup>
                        <xref ref-type="bibr" rid="ref-4">4</xref>
                    </sup>. Based on states and periods, manufacturing complexity in both definitions can be further classified. Manufacturing complexity that remains constant is classified as static complexity in the physical domain (structural, computational, network interaction, etc.) or time-independent complexity in the functional domain. Manufacturing complexity that fluctuates over time is classified as dynamic complexity in the physical domain (market turbulence, product variety, supply chain dynamics, etc.) or time-dependent complexity in the functional domain
                    <sup>
                        <xref ref-type="bibr" rid="ref-3">3</xref>,
                        <xref ref-type="bibr" rid="ref-4">4</xref>
                    </sup>. For complexity measurements, in the physical domain, Frizelle and Woodcock
                    <sup>
                        <xref ref-type="bibr" rid="ref-17">17</xref>
                    </sup> proposed to measure by system entropy:</p>
                <disp-formula id="e1">
                    <mml:math display="block" id="math1">
                        <mml:mspace width="11em"/>
                        <mml:mrow>
                            <mml:msub>
                                <mml:mi>H</mml:mi>
                                <mml:mrow>
                                    <mml:mi>s</mml:mi>
                                    <mml:mi>t</mml:mi>
                                    <mml:mi>a</mml:mi>
                                    <mml:mi>t</mml:mi>
                                    <mml:mi>i</mml:mi>
                                    <mml:mi>c</mml:mi>
                                </mml:mrow>
                            </mml:msub>
                            <mml:mo stretchy="false">(</mml:mo>
                            <mml:mi>S</mml:mi>
                            <mml:mo stretchy="false">)</mml:mo>
                            <mml:mo>=</mml:mo>
                            <mml:mo>&#x2212;</mml:mo>
                            <mml:mstyle displaystyle="true">
                                <mml:munderover>
                                    <mml:mo>&#x2211;</mml:mo>
                                    <mml:mrow>
                                        <mml:mi>i</mml:mi>
                                        <mml:mo>=</mml:mo>
                                        <mml:mn>1</mml:mn>
                                    </mml:mrow>
                                    <mml:mi>M</mml:mi>
                                </mml:munderover>
                                <mml:mrow>
                                    <mml:mstyle displaystyle="true">
                                        <mml:munderover>
                                            <mml:mo>&#x2211;</mml:mo>
                                            <mml:mrow>
                                                <mml:mi>j</mml:mi>
                                                <mml:mo>=</mml:mo>
                                                <mml:mn>1</mml:mn>
                                            </mml:mrow>
                                            <mml:mrow>
                                                <mml:msub>
                                                    <mml:mi>N</mml:mi>
                                                    <mml:mi>j</mml:mi>
                                                </mml:msub>
                                            </mml:mrow>
                                        </mml:munderover>
                                        <mml:mrow>
                                            <mml:msub>
                                                <mml:mi>p</mml:mi>
                                                <mml:mrow>
                                                    <mml:mi>i</mml:mi>
                                                    <mml:mi>j</mml:mi>
                                                </mml:mrow>
                                            </mml:msub>
                                            <mml:mspace width="0.2em"/>
                                            <mml:msub>
                                                <mml:mrow>
                                                    <mml:mi>log</mml:mi>
                                                    <mml:mo>&#x2061;</mml:mo>
                                                </mml:mrow>
                                                <mml:mn>2</mml:mn>
                                            </mml:msub>
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mrow>
                                                    <mml:mi>i</mml:mi>
                                                    <mml:mi>j</mml:mi>
                                                </mml:mrow>
                                            </mml:msub>
                                        </mml:mrow>
                                    </mml:mstyle>
                                </mml:mrow>
                            </mml:mstyle>
                        </mml:mrow>
                        <mml:mspace width="11em"/>
                        <mml:mo stretchy="false">(</mml:mo>
                        <mml:mn>1</mml:mn>
                        <mml:mo stretchy="false">)</mml:mo>
                    </mml:math>
                </disp-formula>
                <disp-formula id="e2">
                    <mml:math display="block" id="math2">
                        <mml:mtable columnalign="left">
                            <mml:mtr>
                                <mml:mtd>
                                    <mml:msub>
                                        <mml:mi>H</mml:mi>
                                        <mml:mrow>
                                            <mml:mi>d</mml:mi>
                                            <mml:mi>y</mml:mi>
                                            <mml:mi>n</mml:mi>
                                            <mml:mi>a</mml:mi>
                                            <mml:mi>m</mml:mi>
                                            <mml:mi>i</mml:mi>
                                            <mml:mi>c</mml:mi>
                                        </mml:mrow>
                                    </mml:msub>
                                    <mml:mo stretchy="false">(</mml:mo>
                                    <mml:mi>S</mml:mi>
                                    <mml:mo stretchy="false">)</mml:mo>
                                    <mml:mo>=</mml:mo>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:mi>P</mml:mi>
                                    <mml:mi>l</mml:mi>
                                    <mml:mi>o</mml:mi>
                                    <mml:msub>
                                        <mml:mi>g</mml:mi>
                                        <mml:mn>2</mml:mn>
                                    </mml:msub>
                                    <mml:mi>P</mml:mi>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:mo stretchy="false">(</mml:mo>
                                    <mml:mn>1</mml:mn>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:mi>P</mml:mi>
                                    <mml:mo stretchy="false">)</mml:mo>
                                    <mml:mi>P</mml:mi>
                                    <mml:mi>l</mml:mi>
                                    <mml:mi>o</mml:mi>
                                    <mml:msub>
                                        <mml:mi>g</mml:mi>
                                        <mml:mn>2</mml:mn>
                                    </mml:msub>
                                    <mml:mo stretchy="false">(</mml:mo>
                                    <mml:mn>1</mml:mn>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:mi>P</mml:mi>
                                    <mml:mo stretchy="false">)</mml:mo>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:mo stretchy="false">(</mml:mo>
                                    <mml:mn>1</mml:mn>
                                </mml:mtd>
                            </mml:mtr>
                            <mml:mtr>
                                <mml:mtd>
                                    <mml:mspace width="6.5em"/>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:mi>P</mml:mi>
                                    <mml:mo stretchy="false">)</mml:mo>
                                    <mml:mspace width="0.1em"/>
                                    <mml:mo stretchy="false">(</mml:mo>
                                    <mml:mstyle displaystyle="true">
                                        <mml:munderover>
                                            <mml:mo>&#x2211;</mml:mo>
                                            <mml:mrow>
                                                <mml:mi>i</mml:mi>
                                                <mml:mo>=</mml:mo>
                                                <mml:mn>1</mml:mn>
                                            </mml:mrow>
                                            <mml:mrow>
                                                <mml:msup>
                                                    <mml:mi>M</mml:mi>
                                                    <mml:mi>q</mml:mi>
                                                </mml:msup>
                                            </mml:mrow>
                                        </mml:munderover>
                                        <mml:mrow>
                                            <mml:mstyle displaystyle="true">
                                                <mml:munderover>
                                                    <mml:mo>&#x2211;</mml:mo>
                                                    <mml:mrow>
                                                        <mml:mi>j</mml:mi>
                                                        <mml:mo>=</mml:mo>
                                                        <mml:mn>1</mml:mn>
                                                    </mml:mrow>
                                                    <mml:mrow>
                                                        <mml:msup>
                                                            <mml:mi>N</mml:mi>
                                                            <mml:mi>q</mml:mi>
                                                        </mml:msup>
                                                    </mml:mrow>
                                                </mml:munderover>
                                                <mml:mrow>
                                                    <mml:msubsup>
                                                        <mml:mi>p</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mi>i</mml:mi>
                                                            <mml:mi>j</mml:mi>
                                                        </mml:mrow>
                                                        <mml:mi>q</mml:mi>
                                                    </mml:msubsup>
                                                    <mml:mspace width="0.2em"/>
                                                    <mml:msub>
                                                        <mml:mrow>
                                                            <mml:mi>log</mml:mi>
                                                            <mml:mo>&#x2061;</mml:mo>
                                                        </mml:mrow>
                                                        <mml:mn>2</mml:mn>
                                                    </mml:msub>
                                                    <mml:mspace width="0.1em"/>
                                                    <mml:msubsup>
                                                        <mml:mi>P</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mi>i</mml:mi>
                                                            <mml:mi>j</mml:mi>
                                                        </mml:mrow>
                                                        <mml:mi>q</mml:mi>
                                                    </mml:msubsup>
                                                </mml:mrow>
                                            </mml:mstyle>
                                        </mml:mrow>
                                    </mml:mstyle>
                                    <mml:mo>+</mml:mo>
                                    <mml:mstyle displaystyle="true">
                                        <mml:munderover>
                                            <mml:mo>&#x2211;</mml:mo>
                                            <mml:mrow>
                                                <mml:mi>i</mml:mi>
                                                <mml:mo>=</mml:mo>
                                                <mml:mn>1</mml:mn>
                                            </mml:mrow>
                                            <mml:mrow>
                                                <mml:msup>
                                                    <mml:mi>M</mml:mi>
                                                    <mml:mi>m</mml:mi>
                                                </mml:msup>
                                            </mml:mrow>
                                        </mml:munderover>
                                        <mml:mrow>
                                            <mml:mstyle displaystyle="true">
                                                <mml:munderover>
                                                    <mml:mo>&#x2211;</mml:mo>
                                                    <mml:mrow>
                                                        <mml:mi>j</mml:mi>
                                                        <mml:mo>=</mml:mo>
                                                        <mml:mn>1</mml:mn>
                                                    </mml:mrow>
                                                    <mml:mrow>
                                                        <mml:msup>
                                                            <mml:mi>N</mml:mi>
                                                            <mml:mi>m</mml:mi>
                                                        </mml:msup>
                                                    </mml:mrow>
                                                </mml:munderover>
                                                <mml:mrow>
                                                    <mml:msubsup>
                                                        <mml:mi>p</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mi>i</mml:mi>
                                                            <mml:mi>j</mml:mi>
                                                        </mml:mrow>
                                                        <mml:mi>m</mml:mi>
                                                    </mml:msubsup>
                                                    <mml:mspace width="0.2em"/>
                                                    <mml:msub>
                                                        <mml:mrow>
                                                            <mml:mi>log</mml:mi>
                                                            <mml:mo>&#x2061;</mml:mo>
                                                        </mml:mrow>
                                                        <mml:mn>2</mml:mn>
                                                    </mml:msub>
                                                    <mml:mspace width="0.1em"/>
                                                    <mml:msubsup>
                                                        <mml:mi>P</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mi>i</mml:mi>
                                                            <mml:mi>j</mml:mi>
                                                        </mml:mrow>
                                                        <mml:mi>m</mml:mi>
                                                    </mml:msubsup>
                                                </mml:mrow>
                                            </mml:mstyle>
                                        </mml:mrow>
                                    </mml:mstyle>
                                    <mml:mo>+</mml:mo>
                                    <mml:mstyle displaystyle="true">
                                        <mml:munderover>
                                            <mml:mo>&#x2211;</mml:mo>
                                            <mml:mrow>
                                                <mml:mi>i</mml:mi>
                                                <mml:mo>=</mml:mo>
                                                <mml:mn>1</mml:mn>
                                            </mml:mrow>
                                            <mml:mrow>
                                                <mml:msup>
                                                    <mml:mi>M</mml:mi>
                                                    <mml:mi>b</mml:mi>
                                                </mml:msup>
                                            </mml:mrow>
                                        </mml:munderover>
                                        <mml:mrow>
                                            <mml:mstyle displaystyle="true">
                                                <mml:munderover>
                                                    <mml:mo>&#x2211;</mml:mo>
                                                    <mml:mrow>
                                                        <mml:mi>j</mml:mi>
                                                        <mml:mo>=</mml:mo>
                                                        <mml:mn>1</mml:mn>
                                                    </mml:mrow>
                                                    <mml:mrow>
                                                        <mml:msup>
                                                            <mml:mi>N</mml:mi>
                                                            <mml:mi>b</mml:mi>
                                                        </mml:msup>
                                                    </mml:mrow>
                                                </mml:munderover>
                                                <mml:mrow>
                                                    <mml:msubsup>
                                                        <mml:mi>p</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mi>i</mml:mi>
                                                            <mml:mi>j</mml:mi>
                                                        </mml:mrow>
                                                        <mml:mi>b</mml:mi>
                                                    </mml:msubsup>
                                                    <mml:mspace width="0.2em"/>
                                                    <mml:msub>
                                                        <mml:mrow>
                                                            <mml:mi>log</mml:mi>
                                                            <mml:mo>&#x2061;</mml:mo>
                                                        </mml:mrow>
                                                        <mml:mn>2</mml:mn>
                                                    </mml:msub>
                                                    <mml:mspace width="0.1em"/>
                                                    <mml:msubsup>
                                                        <mml:mi>P</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mi>i</mml:mi>
                                                            <mml:mi>j</mml:mi>
                                                        </mml:mrow>
                                                        <mml:mi>b</mml:mi>
                                                    </mml:msubsup>
                                                    <mml:mo stretchy="false">)</mml:mo>
                                                </mml:mrow>
                                            </mml:mstyle>
                                        </mml:mrow>
                                    </mml:mstyle>
                                </mml:mtd>
                            </mml:mtr>
                        </mml:mtable>
                        <mml:mspace width="1.8em"/>
                        <mml:mo stretchy="false">(</mml:mo>
                        <mml:mn>2</mml:mn>
                        <mml:mo stretchy="false">)</mml:mo>
                    </mml:math>
                </disp-formula>
                <p>
                    <italic toggle="yes">H
                        <sub>static</sub>
                    </italic>(
                    <italic toggle="yes">S</italic>) represents the entropy of a static system, while 
                    <italic toggle="yes">H
                        <sub>dynamic</sub>
                    </italic>(
                    <italic toggle="yes">S</italic>) represents that of a dynamic system. In 
                    <xref ref-type="other" rid="e1">Formula (1)</xref>, 
                    <italic toggle="yes">M</italic> represents the number of resources, 
                    <italic toggle="yes">N
                        <sub>j</sub>
                    </italic> represents the number of possible states at resource 
                    <italic toggle="yes">j</italic>. 
                    <italic toggle="yes">P
                        <sub>ij</sub>
                    </italic> represents the probability of resource 
                    <italic toggle="yes">j</italic> being in state 
                    <italic toggle="yes">i</italic>. In 
                    <xref ref-type="other" rid="e2">Formula (2)</xref>, in addition to 
                    <xref ref-type="other" rid="e1">Formula (1)</xref>, 
                    <italic toggle="yes">P</italic>  represents the probability that the system is under control, 
                    <italic toggle="yes">P
                        <sup>q</sup>
                    </italic>  represents queues with length longer than 1, 
                    <italic toggle="yes">P
                        <sup>m</sup>
                    </italic> represents queues with a length between 0 and 1, 
                    <italic toggle="yes">P
                        <sup>b</sup>
                    </italic>  represents the non-programmable states
                    <sup>
                        <xref ref-type="bibr" rid="ref-17">17</xref>
                    </sup>. In the functional domain, Suh
                    <sup>
                        <xref ref-type="bibr" rid="ref-18">18</xref>
                    </sup> proposed to measure by effective information content:</p>
                <disp-formula id="e3">
                    <mml:math display="block" id="math3">
                        <mml:mspace width="15.5em"/>
                        <mml:mrow>
                            <mml:mi>I</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:msub>
                                <mml:mrow>
                                    <mml:mi>log</mml:mi>
                                    <mml:mo>&#x2061;</mml:mo>
                                </mml:mrow>
                                <mml:mn>2</mml:mn>
                            </mml:msub>
                            <mml:mrow>
                                <mml:mo>(</mml:mo>
                                <mml:mrow>
                                    <mml:mfrac>
                                        <mml:mrow>
                                            <mml:msub>
                                                <mml:mi>R</mml:mi>
                                                <mml:mi>s</mml:mi>
                                            </mml:msub>
                                        </mml:mrow>
                                        <mml:mrow>
                                            <mml:msub>
                                                <mml:mi>R</mml:mi>
                                                <mml:mi>c</mml:mi>
                                            </mml:msub>
                                        </mml:mrow>
                                    </mml:mfrac>
                                </mml:mrow>
                                <mml:mo>)</mml:mo>
                            </mml:mrow>
                        </mml:mrow>
                        <mml:mspace width="15em"/>
                        <mml:mo stretchy="false">(</mml:mo>
                        <mml:mn>3</mml:mn>
                        <mml:mo stretchy="false">)</mml:mo>
                    </mml:math>
                </disp-formula>
                <p>As shown in 
                    <xref ref-type="fig" rid="f1">Figure 1</xref>, the system range is defined by the performances and capabilities of design concepts proposed to achieve corresponding functional requirements. Design range is determined by design expectations of functional requirements and design tolerances. 
                    <italic toggle="yes">R
                        <sub>s</sub>
                    </italic> represents the range defined by system probability density, which is equal to 1. 
                    <italic toggle="yes">R
                        <sub>c</sub>
                    </italic> represents the common range between system range and design range. The information content 
                    <italic toggle="yes">I</italic>  is the logarithm of the ratio between 
                    <italic toggle="yes">R
                        <sub>s</sub>
                    </italic> and 
                    <italic toggle="yes">R
                        <sub>c</sub>
                    </italic> with a base of 2.</p>
                <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                    <label>Figure 1. </label>
                    <caption>
                        <title>Measurement of information content.</title>
                    </caption>
                    <graphic orientation="portrait" position="float"
                        xlink:href="https://digitaltwin1-files.f1000.com/manuscripts/18764/35d6fa26-cfc9-45a7-999f-b0154adad6cb_figure1.gif"/>
                </fig>
                <p>As aforementioned, manufacturing complexity has three important sources: product design, production lines and supply chains.</p>
                <p>Manufacturing complexity generated by product design (&#x2018;Product design&#x2019; in this paper represents the design for product fabrication rather than functional or conceptual design) is mainly caused by varieties in physical features of product design (size, surface, materials, etc.). Distinct products will naturally comprise various physical features, even for products of the same family. Fabrication strategies (selections of tools, machines and molds) must be customized to suit different physical features and thus introduce manufacturing complexity
                    <sup>
                        <xref ref-type="bibr" rid="ref-19">19</xref>
                    </sup>. Meanwhile, product design also determines segmentations of parts to affect manufacturing complexity. Similar to varieties in physical features, fabrication processes must be customized for different segmentation. Besides, segmentation design determines subsequent assembly strategies, bringing manufacturing complexity
                    <sup>
                        <xref ref-type="bibr" rid="ref-19">19</xref>,
                        <xref ref-type="bibr" rid="ref-20">20</xref>
                    </sup>.</p>
                <p>Three factors affect manufacturing complexity generated by production lines, including product varieties, operation deviations and quality inspections. Product varieties call for a mixed-model production line to handle different fabrication requirements. As trade-offs, a mixed-model production line causes extra uncertainties and lower productivities. In terms of operation deviations, tolerances inevitably exist through operations. Manufacturing complexity is hence generated by differences between design expectations and fabrication outcomes
                    <sup>
                        <xref ref-type="bibr" rid="ref-3">3</xref>
                    </sup>. In terms of quality inspections, inspections are conducted at an early stage of the product lifecycle. However, during usage, information contents of products fluctuate as cyclic loads accumulate
                    <sup>
                        <xref ref-type="bibr" rid="ref-18">18</xref>
                    </sup>. Besides, working environments in practice are often more intricate than inspection conditions. Consequently, differences in working environments introduce uncertainties to quality inspections.</p>
                <p>Fluctuating market demands and uncertainties of supply chain units (factories, warehouses, logistics stations, etc.) introduce manufacturing complexity in supply chains. Affected by abundant factors, market demands are continuously changing. Hence, supply chain managers must keep adjusting procurements, inventories and supplies to match dynamic market demands. In other words, supply chain managers must introduce changeability to handle fluctuating markets. Besides, market patterns are often unpredictable and thus bring uncertainties to supply chain planning
                    <sup>
                        <xref ref-type="bibr" rid="ref-21">21</xref>,
                        <xref ref-type="bibr" rid="ref-22">22</xref>
                    </sup>. Such changeability and uncertainties form into manufacturing complexity caused by fluctuating market demands. Meanwhile, uncertainties exist through each unit in supply chains. Internally, each unit can encounter unexpected problems such as safety hazards, machine breakdowns and power failures. Externally, local situations like environmental disasters, shortages of infrastructures, and strikes can interrupt supply chains' working
                    <sup>
                        <xref ref-type="bibr" rid="ref-21">21</xref>
                    </sup>. Such uncertainties also generate manufacturing complexity in supply chains.</p>
                <p>As aforementioned, manufacturing complexity is rapidly growing nowadays. In this condition, conventional strategies of complexity management tend to be incompetent. Wiendahi and Scholtissek
                    <sup>
                        <xref ref-type="bibr" rid="ref-23">23</xref>
                    </sup> summarized three traditional strategies that enterprises implement to deal with manufacturing complexity, (as shown in 
                    <xref ref-type="fig" rid="f2">Figure 2</xref>): (1) Decentralization of company functions. (2) Exploitation of creativity, experience and competence of employees. (3) Concentration on the core skills of the company. These strategies have evident drawbacks in modern manufacturing. Decentralization of company functions often sacrifices efficiency and management costs as it brings tremendous collaborative work and information inconsistency among departments
                    <sup>
                        <xref ref-type="bibr" rid="ref-24">24</xref>
                    </sup>. Besides, these strategies depend on managers&#x2019; and employees' empirical thinking to manage complexity, often subjective and unreliable. Also, these strategies lack long-term plans to manage complexity through product lifecycles, which have become particularly important in modern manufacturing. Therefore, conventional complexity management is incompetent, and a new framework is in need.</p>
                <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                    <label>Figure 2. </label>
                    <caption>
                        <title>Manufacturing complexity and the growing trend.</title>
                    </caption>
                    <graphic orientation="portrait" position="float"
                        xlink:href="https://digitaltwin1-files.f1000.com/manuscripts/18764/35d6fa26-cfc9-45a7-999f-b0154adad6cb_figure2.gif"/>
                </fig>
            </sec>
            <sec>
                <title>Complexity management in the era of intelligent manufacturing and challenges</title>
                <p>Intelligent manufacturing formulates the blueprint of future industries. Enabled by multiple emerging technologies such as cyber-physical spaces (CPS), internet of things (IoT), augmented reality (AR) and AI, intelligent manufacturing promotes an autonomous, digital and collaborative production system
                    <sup>
                        <xref ref-type="bibr" rid="ref-25">25</xref>
                    </sup>. Meanwhile, intelligent manufacturing formulates design principles of future factories, including interconnections, information transparencies, technical assistance and decentralized decisions
                    <sup>
                        <xref ref-type="bibr" rid="ref-26">26</xref>
                    </sup>. Besides, in business terms, intelligent manufacturing will improve productivity and reduce risks to boost incremental revenue
                    <sup>
                        <xref ref-type="bibr" rid="ref-27">27</xref>
                    </sup>.</p>
                <p>As aforementioned, there is coevolution between intelligent manufacturing and complexity management. However, such coevolution can be restricted by three challenges of intelligent manufacturing: insufficient quality of virtual models, gaps within virtual-physical communications, and limited data. Insufficient quality of virtual models reduces precisions of virtual simulations and thus hinders self-awareness, self-reasoning and self-direction of the manufacturing system. As for gaps within virtual-physical communications, in one aspect, virtual-physical communications are conventionally planned, supervised and operated by human efforts. Considering tremendous data related to intelligent manufacturing, such human efforts can be significantly onerous. In another aspect, virtual-physical communications are also discontinuous, which extends the lead-time of data exchanges. As for limited data, it represents both &#x201c;limited amount&#x201d; and &#x201c;limited categories&#x201d;. Both limitations hamper services related to data analysis such as identifications, diagnoses and predictions
                    <sup>
                        <xref ref-type="bibr" rid="ref-28">28</xref>
                    </sup>. Thus, overcoming these three challenges is the key to enhance complexity management in the era of intelligent manufacturing.</p>
                <p>Meanwhile, intelligent manufacturing introduces extra manufacturing complexity. Intelligent manufacturing is a sophisticated system that requires tremendous components and systems to support data collections, data processing, function outputs and communications
                    <sup>
                        <xref ref-type="bibr" rid="ref-29">29</xref>
                    </sup>. Intelligent manufacturing will inevitably introduce abundant information contents, states, and resources in the word of complexity definitions. Besides, the working of these components brings extra coordination, interferences, couplings and rigidity to manufacturing systems. Thus, overall complexity will dramatically increase in the era of intelligent manufacturing.</p>
            </sec>
            <sec>
                <title>Call for digital twin</title>
                <p>As emerging information technology, DT can overcome the challenges of intelligent manufacturing and thus enhance complexity management. In this paper, DT will be based on Tao&#x2019;s five-dimensional model , including PE, VE, TD, SV, and connections. PE represents physical products, their working environments and other items that interact with them. PE is the foundation of DT as it is the primary source of data collections and the terminal to interact with the physical world. VE represents the digital mirror of PE, including virtual models and simulations. Virtual models in VE are classified into geometrical models, physical models, behavior models and rule models. Interactions between PE and VE are bidirectional, data collections in PE guide the modeling of VE. In reverse, simulations and verifications in VE drive the work of PE. TD represents all data relevant to DT. While collecting data from the PE, VE, SVs and external resources, TD also serves as feedbacks to improve PE, VE and SS. TD Center is the hub to process and manage TD. SVs represent applications provided internally and externally. SVs are classified into functional services (FSV) and business services (BSV). The former is defined as essential applications that support the work of DT, and the latter is defined as output applications for users. Connections represent data transmissions within DT. Besides, connections also undertake data security
                    <sup>
                        <xref ref-type="bibr" rid="ref-13">13</xref>
                    </sup>.</p>
                <p>Intelligent manufacturing is challenged by gaps within physical-virtual communications, while DT synchronizes the two spaces. DT aims to exchange data between physical and virtual spaces in real-time. Data collected from PE will be continuously forwarded to VE for updates, while new data generated by VE will guide the work of PE. Besides, those data will be dynamically extracted, cleansed, analyzed and packed by the TD Center. Its outcomes will drive the work of DT.</p>
                <p>Intelligent manufacturing is challenged by the insufficient quality of virtual models, while DT aims to build a digital mirror to reflect the physical world completely. Enabled by sensing and modeling technologies (e.g., solid modeling, rule modeling, wireframe modeling), DT captures all elements to build a high-fidelity virtual mirror of the physical world
                    <sup>
                        <xref ref-type="bibr" rid="ref-30">30</xref>
                    </sup>. Supported by plentiful data collections, the similarity between virtual models to the physical entity will be higher than ever before.</p>
                <p>Intelligent manufacturing is challenged by limited data, while DT dynamically and comprehensively collects data from abundant sources. In PE, DT records real-time data from physical products, environments, peer products and users. In VE, DT extracts data from virtual simulations and models. In TD Center, DT generates data via analysis and learning. Also, different DTs can interact and exchange data with each other, which allows DT to obtain data beyond systems of attached products. Besides, developers can deliberately input data to intervene in the work of DT.</p>
                <p>In summary, 
                    <xref ref-type="fig" rid="f3">Figure 3</xref> shows how DT will enhance complexity in the era of intelligent manufacturing. This paper focuses on manufacturing complexity introduced by product design, production lines and supply chains. Manufacturing complexity has been rapidly increasing due to more product design features, market competitions and global productions. In this condition, conventional strategies of complexity management are becoming incompetent. Such a strait is expected to overturn in the era of intelligent manufacturing. However, three challenges of intelligent manufacturing will hinder complexity management, including insufficient quality of virtual models, gaps within physical-virtual communications, and limited data. DT can overcome these challenges by synchronizing physical and virtual spaces, dynamic and comprehensive data collections, and high-fidelity virtual modeling. Hence, DT can promote a more autonomous, analytical and comprehensive manner of complexity management. Here, &#x201c;autonomous&#x201d; represent a human-neutral status with self-awareness, self-decision, and self-reaction; &#x201c;analytical&#x201d; represents decision-making driven by data contextualization and mathematical processing; &#x201c;comprehensive&#x201d; represents the coverage of a whole product lifecycle.</p>
                <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                    <label>Figure 3. </label>
                    <caption>
                        <title>Importance of digital-twin driven complexity management in intelligent manufacturing. DT, digital twin; IIOT, industrial internet of things.</title>
                    </caption>
                    <graphic orientation="portrait" position="float"
                        xlink:href="https://digitaltwin1-files.f1000.com/manuscripts/18764/35d6fa26-cfc9-45a7-999f-b0154adad6cb_figure3.gif"/>
                </fig>
                <p>It should be noted that DTs still face several technical and ethical challenges. For example, the limited capability of data processing is a typical technical challenge. Many core functions of DTs heavily consume computing power, such as virtual simulations, model renderings and environment awareness. To date, very limited hardware can afford such enormous computing power consumption. Meanwhile, it is widely agreed that communication capability is constraining DTs. Due to the synchronization between physical and virtual spaces, data transmissions within DTs are tremendous with critical latencies. Both academia and industry believe that reducing data transmission latency via new technology is the key to realize DTs
                    <sup>
                        <xref ref-type="bibr" rid="ref-31">31</xref>
                    </sup>. In terms of ethical challenges, the contradiction between data collections and privacy protections is a controversial example. Theoretically, DTs aim to monitor the physical world dynamically, collect data from PE and VE, and exchange data with peer products. However, these functions enable DTs to extract privacy from stakeholders (engineers, users, business partners, etc.). Thus, the growing concern of privacy protection becomes a barrier to apply DTs. Despite these, investigations on DTs are rapidly growing in recent years, more and more researchers are contributing their efforts into realizing DTs.</p>
            </sec>
        </sec>
        <sec>
            <title>The proposed framework for digital twin-driven complexity management in manufacturing</title>
            <p>As shown in 
                <xref ref-type="fig" rid="f4">Figure 4</xref>, this section proposes the framework of DT-driven complexity management for intelligent manufacturing. The framework was innovated based on combinations between complexity management problems and functions of DTs in intelligent manufacturing. One important hypothesis of this framework is that DT is widely deployed to manufacturing equipment and products.</p>
            <fig fig-type="figure" id="f4" orientation="portrait" position="float">
                <label>Figure 4. </label>
                <caption>
                    <title>The proposed framework of digital twin-driven complexity management for intelligent manufacturing.</title>
                </caption>
                <graphic orientation="portrait" position="float"
                     xlink:href="https://digitaltwin1-files.f1000.com/manuscripts/18764/35d6fa26-cfc9-45a7-999f-b0154adad6cb_figure4.gif"/>
            </fig>
            <sec>
                <title>Services of digital twins for complexity management</title>
                <p>Motivations of complexity management vary in adaptable and unadaptable manufacturing systems. In terms of an adaptable manufacturing system, complexity management aims to minimize dependencies and uncertainties. In an unadaptable manufacturing system, complexity management seeks to control risk and cost caused by dependencies and uncertainties. Although manufacturing complexity appears in different scenarios, DT generally provides three important SVs for complexity management.</p>
                <p>
                    <bold>
                        <italic toggle="yes">Real-time monitors and data collections.</italic>
                    </bold> Enabled by sensing technologies and IoT, DT can monitor its products and environments in physical and virtual worlds. During this process, data will be collected in real-time. Data can be collected from PE, VE, historical investigations, online resources and peer products. Those data will support the analysis of complexity in manufacturing systems. Besides, such data also assist users and developers in evaluating uncertainties in manufacturing systems. As 
                    <xref ref-type="other" rid="e1">Formula (1)</xref> and 
                    <xref ref-type="other" rid="e2">(2)</xref> indicate, states and information contents of manufacturing systems represent complexity. Thus, data related to states and information contents help users understand complexity. 
                    <xref ref-type="table" rid="T2">Table 2</xref> provides some examples of data that can be collected for this purpose.</p>
                <table-wrap id="T2" orientation="portrait" position="anchor">
                    <label>Table 2. </label>
                    <caption>
                        <title>Examples of data collections for complexity management in manufacturing.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Source of manufacturing complexity</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Secondary sources</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Examples of data</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="2" valign="middle">Product design</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Design of physical feature</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">The smoothness of surfaces, tolerance of edge-cutting tools, the strength of materials, etc.</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Segmentation design</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">The number of connections joints, deviations of surface-cutting operations, assembly speeds on production lines, etc.</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="3" valign="middle">Production line</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Product variety</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Number of products, number of production processes, number of production operations, etc.</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Deviation of operation</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Tolerances of drillings, deviations of robot pose positioning, operation conformity, etc.</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Quality inspection</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Accuracy of defect identifications, Cyclic loads, on-site test recordings, etc.</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="2" valign="middle">Supply chain</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Fluctuating market demands</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Supply of substitute goods, change of customers&#x2019; incomes, cost of raw materials, etc.</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Uncertainties of supply chain units</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Frequency of power cut, change of tax, number of available infrastructures, etc.</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>
                    <bold>
                        <italic toggle="yes">Identifications, diagnoses and predictions of manufacturing complexity.</italic>
                    </bold> Conventionally, it is challenging for engineers to identify, diagnose and predict manufacturing complexity due to limited knowledge, experience and cognitions. Enabled by tremendous data and analytical methods, DT will transfer these objectives into a more objective and rational manner. Complexity appears in manufacturing systems as couplings and system failures. As DT monitors manufacturing systems dynamically, states of all engaged parts will be captured as recordings of couplings and system failures. Then, by tracing and checking these states, DT can rapidly sort out couplings and system failures. Thus, complexity can be identified. As for complexity diagnoses, DT will incorporate data of target system, recorded systems and previous decision-making. The fusion of those data will enable DT to compare and learn from existing samples to highlight complexity causes. Based on training models, DT will learn patterns of complexity dataset and thus predict trends in terms of complexity predictions. Besides, developers can customize training models by editing and filtering out specific data. Except for training models, predictions can also be conducted by simulation and verify in VE. Similar to training models, virtual models in VE can also be customized to improve simulation accuracies.</p>
                <p>
                    <bold>
                        <italic toggle="yes">Fortification of human-machine interaction.</italic>
                    </bold> Although intelligent manufacturing aims to promote a more autonomous production, flexibility and knowledge of human interventions are still essential to deal with intricate problems
                    <sup>
                        <xref ref-type="bibr" rid="ref-32">32</xref>
                    </sup>. DT provides emerging approaches to engaging human interventions. Enabled by AR and VR, users can flexibly modify virtual models of VE. As VE is synchronized to PE, PE will react in correspondence to changes in VE. Thus, users also control the physical manufacturing system remotely and conveniently. Meanwhile, as VE is a digital mirror of PE, users can flexibly observe every aspect of PE. Besides, DT also enables users to control the manufacturing system by simply editing settings, commands and data. In these ways, users can rapidly, remotely and conveniently guide complexity management when DT cannot autonomously handle problems.</p>
            </sec>
            <sec>
                <title>Digital twin-driven management of manufacturing complexity in product design</title>
                <p>As aforementioned, complexity in product design is introduced by the segmentation of parts and physical features of products. For the former, it is arguable to say that products have infinite ways to be segmented. Despite this, one ubiquitous principle is the reduction in the number of parts
                    <sup>
                        <xref ref-type="bibr" rid="ref-33">33</xref>
                    </sup>. Thus, designers tend to apply sophisticated shapes and composite parts
                    <sup>
                        <xref ref-type="bibr" rid="ref-34">34</xref>
                    </sup>. Consequently, varieties in segmentation design, shape design and composite parts result in capricious manufacturing processes. For the latter, similarly, manufacturing processes ought to be highly adaptable to produce products with whimsical feature design. Besides, even for one single manufacturing process, various combinations of tools, control systems and networks can be deployed, which is defined as station level complexity by Zhu 
                    <italic toggle="yes">et al</italic>.
                    <sup>
                        <xref ref-type="bibr" rid="ref-35">35</xref>
                    </sup>. Those altogether result in combinatorial complexity. Generally, manufacturing complexity caused by product design can be resolved in two ways: optimizing product design for easier productions or improving manufacturing plans to match product design.</p>
                <p>
                    <xref ref-type="fig" rid="f4">Figure 4</xref> shows DT-enabled approaches to complexity management. DT aims to reduce dependencies and uncertainties to manage complexity from product design.</p>
                <p>To reduce dependencies, DT will diagnose the causes of dependencies by dissecting manufacturing systems and analyzing previous cases. At first, DT identifies dependencies by analyzing couplings. When manufacturing systems have couplings, engaged workpieces will interact with each other inevitably. Hence, couplings among these workpieces can be detected by tracing their interactions. Then, DT will check the logic relations behind these couplings. Couplings among workpieces with clear logic relations can be classified as dependencies. If a candidate manufacturing plan has massive dependencies, DT will sort out production procedures that generate dependencies. Procedures with plentiful dependencies will be recommended for removal. If highlighted procedures are necessary for the manufacturing system, DT will analyze previous similar cases to explore a simplified structure. Alternatively, engineers can manually edit manufacturing plans and verify their feasibilities via simulations in VE.</p>
                <p>DT analyzes manufacturing data and makes predictions to reduce uncertainties. In the proposed framework, based on dependency analysis, uncertainties of manufacturing systems can be calculated with relevant data. 
                    <xref ref-type="fig" rid="f5">Figure 5</xref> illustrates a dissected manufacturing plan. In a manufacturing plan, parts will be produced through several processes, and the combination of these processes is defined as a &#x201c;set&#x201d; here. For example, if a part can be produced via die casting, welding, grinding and inkjet painting, these four processes and the sequence will be recorded as &#x201c;Set I&#x201d;. The part may also be produced via additive manufacturing, molding and casting, and then these can be recorded as &#x201c;Set II&#x201d;. By analyzing production machines and product inspections data, DT can collect uncertainties of each process (number of defects, conformity, operation deviations, etc.). Then, with the sequence and couplings of processes, a probability can be calculated to represent uncertainties to produce these parts in a specified set. This probability will be recorded as an entry. Similarly, applying the same approach in an assembly plan, the uncertainty to produce a product can also be calculated. Besides, different sets of processes sometimes are adopted simultaneously in a factory. Uncertainty of a factory contains uncertainties of all deployed sets. Finally, the overall uncertainty of a manufacturing plan can be evaluated after analyzing the uncertainties of all engaged factories. DT can calculate those entries of uncertainties through three phases. The first phase is the accumulation of manufacturing data. DT will keep collecting data from each factory. As DTs are deployed to all machines and products, manufacturing data can be rapidly and comprehensively collected. Thus, uncertainties of each process can be obtained with data like the number of defects, conformity of parts and operation deviations to fill in each entry. As DT collects data dynamically, the accuracy of uncertainties tends to increase over time gradually. In the second phase, when data is has been accumulated sufficiently, they can be used for self-planning. Theoretically, the manufacturing plan with minimum uncertainties is the optimal solution in terms of manufacturing complexity. DT can automatically generate the manufacturing plan with minimum uncertainties by continuously adjusting processes, production sequences, and production distributions to each factory. Besides, the developed plan can be verified in VE. The third phase is calibration. There is always a difference between anticipations and practical performances. Thus, users and DT will collaborate to improve accuracies. Accuracies can be enhanced via several approaches such as optimizing anticipation models, cleansing manufacturing data and deploy more DTs in factories.</p>
                <fig fig-type="figure" id="f5" orientation="portrait" position="float">
                    <label>Figure 5. </label>
                    <caption>
                        <title>Entries in a manufacturing plan.</title>
                    </caption>
                    <graphic orientation="portrait" position="float"
                        xlink:href="https://digitaltwin1-files.f1000.com/manuscripts/18764/35d6fa26-cfc9-45a7-999f-b0154adad6cb_figure5.gif"/>
                </fig>
                <p>Despite the autonomy of DT, users&#x2019; engagement is still meaningful in many situations. DT can also benefit users&#x2019; engagement. For example, professional users may quickly notice and correct problems with manufacturing plans. They can prototype and verify their manufacturing plans via simulations in VE. During simulations, users can intuitively observe their manufacturing plans to identify potential problems. Alternatively, DT can forward outcomes of simulations to engineers for evaluations. Besides, DT can also quickly extract existing samples of manufacturing plans to compare with new plans. Differences will be highlighted in virtual models for users to inspect. Also, users&#x2019; engagement serves as a learning resource to train DT.</p>
            </sec>
            <sec>
                <title>Digital twin-driven management of manufacturing complexity in production lines</title>
                <p>Product varieties, operation deviations and quality inspections in production lines appear in different forms and result in different manufacturing complexity. Production varieties require adaptable production lines and thus introduce dynamic complexity. Besides, compared to single-model production lines for mass productions, adaptable production lines have less reliability and productivity. As for operation deviations caused by machine precisions and human operators' skills, they introduce static complexity to production lines. With regard to quality inspections, they are caused by differences between inspections and practical usages. Besides, every product has a service life and its statistical distribution (
                    <italic toggle="yes">R
                        <sub>s</sub>
                    </italic> in 
                    <xref ref-type="other" rid="e3">Formula (3)</xref>) over time. Hence, it introduces time-dependent complexity. As the three causes in production lines result in different manufacturing complexity, goals of complexity management thus vary.</p>
                <p>With regard to product varieties, the goal of complexity management is balancing among adaptability, reliability and productivity for production lines. The key to such a balance is satisfying the production demands of varieties while preventing redundant adaptability. DT can manage complexity caused by adaptability via diagnosis and virtual simulations. To diagnose causes of complexity in production lines, Zhu 
                    <italic toggle="yes">et al</italic>. proposed an analytic model
                    <sup>
                        <xref ref-type="bibr" rid="ref-35">35</xref>
                    </sup>:</p>
                <disp-formula id="e4">
                    <mml:math display="block" id="math4">
                        <mml:mspace width="10em"/>
                        <mml:mrow>
                            <mml:msub>
                                <mml:mi>C</mml:mi>
                                <mml:mi>j</mml:mi>
                            </mml:msub>
                            <mml:mo>=</mml:mo>
                            <mml:mstyle displaystyle="true">
                                <mml:munderover>
                                    <mml:mo>&#x2211;</mml:mo>
                                    <mml:mrow>
                                        <mml:mi>K</mml:mi>
                                        <mml:mo>=</mml:mo>
                                        <mml:mn>1</mml:mn>
                                    </mml:mrow>
                                    <mml:mi>K</mml:mi>
                                </mml:munderover>
                                <mml:mrow>
                                    <mml:msubsup>
                                        <mml:mi>a</mml:mi>
                                        <mml:mi>j</mml:mi>
                                        <mml:mi>k</mml:mi>
                                    </mml:msubsup>
                                    <mml:msubsup>
                                        <mml:mi>H</mml:mi>
                                        <mml:mi>j</mml:mi>
                                        <mml:mi>k</mml:mi>
                                    </mml:msubsup>
                                    <mml:mo>,</mml:mo>
                                    <mml:mspace width="0.4em"/>
                                    <mml:msubsup>
                                        <mml:mi>a</mml:mi>
                                        <mml:mi>j</mml:mi>
                                        <mml:mi>k</mml:mi>
                                    </mml:msubsup>
                                    <mml:mo>&gt;</mml:mo>
                                    <mml:mn>0</mml:mn>
                                    <mml:mo>,</mml:mo>
                                    <mml:mi>k</mml:mi>
                                    <mml:mo>=</mml:mo>
                                    <mml:mn>1</mml:mn>
                                    <mml:mo>,</mml:mo>
                                    <mml:mn>2</mml:mn>
                                    <mml:mo>,</mml:mo>
                                    <mml:mo>&#x2026;</mml:mo>
                                    <mml:mspace width="0.1em"/>
                                    <mml:mi>K</mml:mi>
                                </mml:mrow>
                            </mml:mstyle>
                        </mml:mrow>
                        <mml:mspace width="10.5em"/>
                        <mml:mo stretchy="false">(</mml:mo>
                        <mml:mn>4</mml:mn>
                        <mml:mo stretchy="false">)</mml:mo>
                    </mml:math>
                </disp-formula>
                <disp-formula id="e5">
                    <mml:math display="block" id="math5">
                        <mml:mspace width="8.5em"/>
                        <mml:mrow>
                            <mml:msup>
                                <mml:mrow>
                                    <mml:mrow>
                                        <mml:mo>[</mml:mo>
                                        <mml:mrow>
                                            <mml:mtable>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>C</mml:mi>
                                                                <mml:mn>1</mml:mn>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>C</mml:mi>
                                                                <mml:mn>2</mml:mn>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mo>&#x22ef;</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>C</mml:mi>
                                                                <mml:mi>n</mml:mi>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                            </mml:mtable>
                                        </mml:mrow>
                                        <mml:mo>]</mml:mo>
                                    </mml:mrow>
                                </mml:mrow>
                                <mml:mrow>
                                    <mml:mi>i</mml:mi>
                                    <mml:mi>n</mml:mi>
                                </mml:mrow>
                            </mml:msup>
                            <mml:mo>=</mml:mo>
                            <mml:mrow>
                                <mml:mo>[</mml:mo>
                                <mml:mrow>
                                    <mml:mtable>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mrow>
                                                    <mml:msub>
                                                        <mml:mi>a</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mn>01</mml:mn>
                                                        </mml:mrow>
                                                    </mml:msub>
                                                </mml:mrow>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mrow>
                                                    <mml:msub>
                                                        <mml:mi>a</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mn>02</mml:mn>
                                                        </mml:mrow>
                                                    </mml:msub>
                                                </mml:mrow>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mo>&#x22ef;</mml:mo>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mrow>
                                                    <mml:msub>
                                                        <mml:mi>a</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mn>0</mml:mn>
                                                            <mml:mi>n</mml:mi>
                                                        </mml:mrow>
                                                    </mml:msub>
                                                </mml:mrow>
                                            </mml:mtd>
                                        </mml:mtr>
                                    </mml:mtable>
                                    <mml:mspace width="1em"/>
                                    <mml:mtable>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mn>0</mml:mn>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mo>&#x22ef;</mml:mo>
                                                <mml:mo>&#x22c5;</mml:mo>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mo>&#x22ef;</mml:mo>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mrow>
                                                    <mml:msub>
                                                        <mml:mi>a</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mn>1</mml:mn>
                                                            <mml:mi>n</mml:mi>
                                                        </mml:mrow>
                                                    </mml:msub>
                                                </mml:mrow>
                                            </mml:mtd>
                                        </mml:mtr>
                                    </mml:mtable>
                                    <mml:mspace width="1em"/>
                                    <mml:mtable>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mo>&#x22ef;</mml:mo>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mo>&#x22ef;</mml:mo>
                                                <mml:mo>&#x22c5;</mml:mo>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mo>&#x22ef;</mml:mo>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mo>&#x22ef;</mml:mo>
                                            </mml:mtd>
                                        </mml:mtr>
                                    </mml:mtable>
                                    <mml:mspace width="1em"/>
                                    <mml:mtable>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mn>0</mml:mn>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mn>0</mml:mn>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mn>0</mml:mn>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mrow>
                                                    <mml:msub>
                                                        <mml:mi>a</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mi>n</mml:mi>
                                                            <mml:mo>&#x2212;</mml:mo>
                                                            <mml:mn>1</mml:mn>
                                                            <mml:mo>,</mml:mo>
                                                            <mml:mi>n</mml:mi>
                                                        </mml:mrow>
                                                    </mml:msub>
                                                </mml:mrow>
                                            </mml:mtd>
                                        </mml:mtr>
                                    </mml:mtable>
                                </mml:mrow>
                                <mml:mo>]</mml:mo>
                            </mml:mrow>
                            <mml:mspace width="0.2em"/>
                            <mml:mo>&#x00d7;</mml:mo>
                            <mml:mspace width="0.2em"/>
                            <mml:mrow>
                                <mml:mo>[</mml:mo>
                                <mml:mrow>
                                    <mml:mtable>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mrow>
                                                    <mml:msub>
                                                        <mml:mi>H</mml:mi>
                                                        <mml:mn>0</mml:mn>
                                                    </mml:msub>
                                                </mml:mrow>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mrow>
                                                    <mml:msub>
                                                        <mml:mi>H</mml:mi>
                                                        <mml:mn>1</mml:mn>
                                                    </mml:msub>
                                                </mml:mrow>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mo>&#x22ef;</mml:mo>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mrow>
                                                    <mml:msub>
                                                        <mml:mi>H</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mi>n</mml:mi>
                                                            <mml:mo>&#x2212;</mml:mo>
                                                            <mml:mn>1</mml:mn>
                                                        </mml:mrow>
                                                    </mml:msub>
                                                </mml:mrow>
                                            </mml:mtd>
                                        </mml:mtr>
                                    </mml:mtable>
                                </mml:mrow>
                                <mml:mo>]</mml:mo>
                            </mml:mrow>
                        </mml:mrow>
                        <mml:mspace width="9em"/>
                        <mml:mo stretchy="false">(</mml:mo>
                        <mml:mn>5</mml:mn>
                        <mml:mo stretchy="false">)</mml:mo>
                    </mml:math>
                </disp-formula>
                <disp-formula id="e6">
                    <mml:math display="block" id="math6">
                        <mml:mspace width="2em"/>
                        <mml:mrow>
                            <mml:msup>
                                <mml:mrow>
                                    <mml:mrow>
                                        <mml:mo>[</mml:mo>
                                        <mml:mrow>
                                            <mml:mtable>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>C</mml:mi>
                                                                <mml:mn>1</mml:mn>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>C</mml:mi>
                                                                <mml:mn>2</mml:mn>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mo>&#x22ef;</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>C</mml:mi>
                                                                <mml:mi>n</mml:mi>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                            </mml:mtable>
                                        </mml:mrow>
                                        <mml:mo>]</mml:mo>
                                    </mml:mrow>
                                </mml:mrow>
                                <mml:mrow>
                                    <mml:mi>o</mml:mi>
                                    <mml:mi>u</mml:mi>
                                    <mml:mi>t</mml:mi>
                                </mml:mrow>
                            </mml:msup>
                            <mml:mo>=</mml:mo>
                            <mml:mrow>
                                <mml:mo>{</mml:mo>
                                <mml:mrow>
                                    <mml:mrow>
                                        <mml:mo>[</mml:mo>
                                        <mml:mrow>
                                            <mml:mtable>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>a</mml:mi>
                                                                <mml:mrow>
                                                                    <mml:mn>01</mml:mn>
                                                                </mml:mrow>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>a</mml:mi>
                                                                <mml:mrow>
                                                                    <mml:mn>02</mml:mn>
                                                                </mml:mrow>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mo>&#x22ef;</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>a</mml:mi>
                                                                <mml:mrow>
                                                                    <mml:mn>0</mml:mn>
                                                                    <mml:mi>n</mml:mi>
                                                                </mml:mrow>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                            </mml:mtable>
                                            <mml:mspace width="1em"/>
                                            <mml:mtable>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mn>0</mml:mn>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mo>&#x22ef;</mml:mo>
                                                        <mml:mo>&#x22c5;</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mo>&#x22ef;</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>a</mml:mi>
                                                                <mml:mrow>
                                                                    <mml:mn>1</mml:mn>
                                                                    <mml:mi>n</mml:mi>
                                                                </mml:mrow>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                            </mml:mtable>
                                            <mml:mspace width="1em"/>
                                            <mml:mtable>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mo>&#x22ef;</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mo>&#x22ef;</mml:mo>
                                                        <mml:mo>&#x22c5;</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mo>&#x22ef;</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mo>&#x22ef;</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                            </mml:mtable>
                                            <mml:mspace width="1em"/>
                                            <mml:mtable>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mn>0</mml:mn>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mn>0</mml:mn>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mn>0</mml:mn>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mrow>
                                                            <mml:msub>
                                                                <mml:mi>a</mml:mi>
                                                                <mml:mrow>
                                                                    <mml:mi>n</mml:mi>
                                                                    <mml:mo>&#x2212;</mml:mo>
                                                                    <mml:mn>1</mml:mn>
                                                                    <mml:mo>,</mml:mo>
                                                                    <mml:mi>n</mml:mi>
                                                                </mml:mrow>
                                                            </mml:msub>
                                                        </mml:mrow>
                                                    </mml:mtd>
                                                </mml:mtr>
                                            </mml:mtable>
                                        </mml:mrow>
                                        <mml:mo>]</mml:mo>
                                    </mml:mrow>
                                    <mml:mspace width="0.2em"/>
                                    <mml:mo>&#x00d7;</mml:mo>
                                    <mml:mspace width="0.2em"/>
                                    <mml:mrow>
                                        <mml:mo>[</mml:mo>
                                        <mml:mrow>
                                            <mml:mtable>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mn>1</mml:mn>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mn>1</mml:mn>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mo>&#x22ef;</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:mn>1</mml:mn>
                                                    </mml:mtd>
                                                </mml:mtr>
                                            </mml:mtable>
                                        </mml:mrow>
                                        <mml:mo>]</mml:mo>
                                    </mml:mrow>
                                </mml:mrow>
                                <mml:mo>}</mml:mo>
                            </mml:mrow>
                            <mml:mo>.</mml:mo>
                            <mml:mspace width="0.2em"/>
                            <mml:mo>&#x2217;</mml:mo>
                            <mml:mspace width="0.2em"/>
                            <mml:msup>
                                <mml:mrow>
                                    <mml:mo stretchy="false">[</mml:mo>
                                    <mml:msub>
                                        <mml:mi>H</mml:mi>
                                        <mml:mn>0</mml:mn>
                                    </mml:msub>
                                    <mml:mo>,</mml:mo>
                                    <mml:mspace width="0.1em"/>
                                    <mml:msub>
                                        <mml:mi>H</mml:mi>
                                        <mml:mn>1</mml:mn>
                                    </mml:msub>
                                    <mml:mo>,</mml:mo>
                                    <mml:mspace width="0.1em"/>
                                    <mml:mo>&#x22ef;</mml:mo>
                                    <mml:mo>,</mml:mo>
                                    <mml:mspace width="0.1em"/>
                                    <mml:msub>
                                        <mml:mi>H</mml:mi>
                                        <mml:mrow>
                                            <mml:mi>n</mml:mi>
                                            <mml:mo>&#x2212;</mml:mo>
                                            <mml:mn>1</mml:mn>
                                        </mml:mrow>
                                    </mml:msub>
                                    <mml:mo stretchy="false">]</mml:mo>
                                </mml:mrow>
                                <mml:mi>T</mml:mi>
                            </mml:msup>
                        </mml:mrow>
                        <mml:mspace width="5.3em"/>
                        <mml:mo stretchy="false">(</mml:mo>
                        <mml:mn>6</mml:mn>
                        <mml:mo stretchy="false">)</mml:mo>
                    </mml:math>
                </disp-formula>
                <p>In 
                    <xref ref-type="other" rid="e4">Formula (4)</xref>, 
                    <inline-formula>
                        <mml:math display="inline" id="M1">
                            <mml:mrow>
                                <mml:msubsup>
                                    <mml:mi>a</mml:mi>
                                    <mml:mi>j</mml:mi>
                                    <mml:mi>k</mml:mi>
                                </mml:msubsup>
                            </mml:mrow>
                        </mml:math>
                    </inline-formula> represents weights related to the task difficulty of the 
                    <italic toggle="yes">k
                        <sup>th</sup>
                    </italic> assembly activity at station 
                    <italic toggle="yes">j</italic>. The greater difficulty of assembly results in a higher 
                    <inline-formula>
                        <mml:math display="inline" id="M2">
                            <mml:mrow>
                                <mml:msubsup>
                                    <mml:mi>a</mml:mi>
                                    <mml:mi>j</mml:mi>
                                    <mml:mi>k</mml:mi>
                                </mml:msubsup>
                            </mml:mrow>
                        </mml:math>
                    </inline-formula>. The difficulty of assembly is determined by feature variants, choice of fixtures, tools, and assembly procedures. 
                    <inline-formula>
                        <mml:math display="inline" id="M3">
                            <mml:mrow>
                                <mml:msubsup>
                                    <mml:mi>H</mml:mi>
                                    <mml:mi>j</mml:mi>
                                    <mml:mi>k</mml:mi>
                                </mml:msubsup>
                            </mml:mrow>
                        </mml:math>
                    </inline-formula> represents the entropy computed from the variant mix ratio relevant to the 
                    <italic toggle="yes">k
                        <sup>th</sup>
                    </italic> assembly activity at station 
                    <italic toggle="yes">j</italic>, which can be calculated via 
                    <xref ref-type="other" rid="e1">Formula (1)</xref>. Derived from 
                    <xref ref-type="other" rid="e4">Formula (4)</xref>, 
                    <xref ref-type="other" rid="e5">Formula (5)</xref> and 
                    <xref ref-type="other" rid="e6">(6)</xref> represent the incoming and outgoing complexity of each station, respectively. Hence, each station's incoming and outgoing complexity can be calculated and plotted against station positions in a multistage assembly system. Besides, the manufacturing stations with high incoming complexity should be replaced
                    <sup>
                        <xref ref-type="bibr" rid="ref-35">35</xref>
                    </sup>. Enabled by DTs of stations, data of assembly activities at a station (
                    <italic toggle="yes">k
                        <sup>th</sup>
                    </italic>), frequencies of station states during a period (to calculate 
                    <italic toggle="yes">P
                        <sub>ij</sub>
                    </italic> in 
                    <xref ref-type="other" rid="e1">Formula (1)</xref>), the number of resources (
                    <italic toggle="yes">M</italic>) and the number of all station states (
                    <italic toggle="yes">N</italic>) will be collected. Besides, weights related to task difficulty (
                    <inline-formula>
                        <mml:math display="inline" id="M4">
                            <mml:mrow>
                                <mml:msubsup>
                                    <mml:mi>a</mml:mi>
                                    <mml:mi>j</mml:mi>
                                    <mml:mi>k</mml:mi>
                                </mml:msubsup>
                            </mml:mrow>
                        </mml:math>
                    </inline-formula>) can be automatically assigned by extracting samples from existing cases of production line models. Hence, DT can automatically sort out the complexity of each station. Stations with high incoming complexity will be forwarded to users for modifications. Modified models of production lines will be sent back to DT to verify their adaptability and productivity via virtual simulations. Meanwhile, DT also makes it more convenient to build production lines in the physical world. Production lines are characterized as modular systems. Their creations are assemblies of function modules in specific sequences. If DTs are deployed to function modules, the conveyance system will shift function modules to synchronize with users&#x2019; redesign in VE. In other words, users can conveniently restructure models of production lines by controlling their virtual twins.</p>
                <p>With regard to operation deviations, the goal of complexity management is replacements of workpieces with high uncertainties. DT can achieve this goal via dynamic monitors and statistical analytics. DTs deployed to workpieces will continuously collect their operation data. Simultaneously, collected data will be plotted by DT to compare with design expectations. As data accumulate, plots will appear in the forms of normal distributions and intersect with design ranges. According to 
                    <xref ref-type="other" rid="e3">Formula (3)</xref>, uncertainties of operations can be calculated. Besides, DT can also use these data to evaluate the significance of uncertainties based on mathematical methods. For example, with the number of defective products from each workpiece, DT can analyze variance (a statistical technique to tell differences between two data groups) tests to evaluate their differences. Workpieces with significantly higher defective rates will be maintained and replaced.</p>
                <p>With regard to quality inspections, the goal of complexity management is predicting the uncertainties of products through their lifecycles. Such predictions will be based on dynamic monitors, data retrievals and virtual simulations of DT. As shown in 
                    <xref ref-type="fig" rid="f6">Figure 6</xref>, according to the theory of Information Axiom, product performances can be plotted as probability density functions and intersect with design expectations. Their cross-section areas can be used to describe uncertainties in achieving corresponding functional requirements (as 
                    <xref ref-type="other" rid="e3">Formula (3)</xref>)
                    <sup>
                        <xref ref-type="bibr" rid="ref-36">36</xref>
                    </sup>. However, different product states (working environments, ways of usages and life stages) can shift these plots. As shown in 
                    <xref ref-type="fig" rid="f6">Figure 6</xref> either, one state will correspond to one unique plot. In the beginning, the main objective of DT is accumulating data of target products through their lifecycles. As DTs are deployed to all products, data coverage will rapidly expand from sundry product states. Collected data will be classified, cleansed, packed and stored in the TD Center. When datasets are large enough, DT can then predict uncertainties of products via data retrievals. For a specified product, DT can mobilize data of all its peers to reflect its uncertainties through the lifecycle. States with possible risks will be highlighted to guide future optimizations. Alternatively, enabled by datasets of different scenarios, users can customize virtual models to simulate uncertainties of products in various working environments, ways of usages and product life stages.</p>
                <fig fig-type="figure" id="f6" orientation="portrait" position="float">
                    <label>Figure 6. </label>
                    <caption>
                        <title>Changes in product performance over time in certain conditions.</title>
                    </caption>
                    <graphic orientation="portrait" position="float"
                        xlink:href="https://digitaltwin1-files.f1000.com/manuscripts/18764/35d6fa26-cfc9-45a7-999f-b0154adad6cb_figure6.gif"/>
                </fig>
            </sec>
            <sec>
                <title>Digital twin-driven management of manufacturing complexity in supply chain</title>
                <p>Complexity in supply chains is caused by fluctuating market demands and uncertainties of supply chain units. Although external factors often generate complexity in supply chains, it is still feasible to reduce costs and risks by implementing management strategies.</p>
                <p>To handle fluctuating market demands, DT will predict supply changes and intelligently plan productions and logistics. As DTs are deployed to products, factories and warehouses, dynamic flows of products can be monitored through the whole supply chain. Hence, DT can capture and record supplies and inventories in each site. Thus, short-term demands can also be derived. Besides, such monitors and data collections also enable DT to plan productions and logistics. For example, if DT notices that the turnover of a warehouse is far below others, DT will then check data of supplies and logistics related to this warehouse. Based on the diagnosis, DT will re-plan supply chains to balance the loads of each supply chain unit. Compared to human-lead planning, real-time monitors enable DT to react instantly and thus reduce risks and costs. Meanwhile, high-fidelity supply chain models of DT enable virtual simulations, which help users make long-term plans for supply chains.</p>
                <p>To handle uncertainties of supply chain units, DT will evaluate risks, predict losses and make emergency plans. With regard to risk evaluations, the risks of supply chain units can be internal or external. Internal risks are introduced by management issues such as safety management, power management and equipment management. External risks are introduced by local environments, infrastructures and economic policies. Internal risks can be identified by monitoring systems, analyzing previous cases and exchanging data with peer DTs. External risks can be identified via crowdsourcing. For example, to identify risks related to equipment management, DT firstly extracts data recordings of previous cases (states of equipment when hazards occur). Then, DT analyzes those recordings and compares them with data of standard equipment. Hence, differences in data will highlight indications of risks. Afterward, DT will use data of such indications as a reference to check the states of current equipment and thus identify potential risks. Besides, DTs of different factories can exchange their datasets to verify and improve risk identifications. These data are also essential to predict losses. Enabled by high-fidelity virtual models, users can input data of risks to simulate hazards. Simulation outcomes will predict losses when risks occur. Based on those simulation outcomes, feedbacks will be sent back to engineers and managers. Subsequently, these simulation outcomes support DT to generate emergency plans such as back-up inventories, reallocations of supplies and replacements of equipment. Users or virtual simulations can verify these plans.</p>
            </sec>
        </sec>
        <sec sec-type="cases">
            <title>Use case: complexity management for airplane manufacturing</title>
            <p>This section will present a use case of airplane manufacturing to illustrate the proposed framework of DT-driven complexity management. As airplane manufacturing is arguably the most sophisticated manufacturing project, this section will select some typical scenarios of airplane manufacturing for illustration. 
                <xref ref-type="fig" rid="f7">Figure 7</xref> shows a simple summary of the use case.</p>
            <fig fig-type="figure" id="f7" orientation="portrait" position="float">
                <label>Figure 7. </label>
                <caption>
                    <title>Summary of the use case.</title>
                </caption>
                <graphic orientation="portrait" position="float"
                     xlink:href="https://digitaltwin1-files.f1000.com/manuscripts/18764/35d6fa26-cfc9-45a7-999f-b0154adad6cb_figure7.gif"/>
            </fig>
            <sec>
                <title>A simple background of airplane manufacturing</title>
                <p>Complexity exists in each corner of airplane manufacturing. Airplane design is a complex of multiple disciplines such as aerodynamics, thermodynamics, mechatronics and material science. Aviation equipment enabled by different techniques coordinate with each other to support flights. Meanwhile, as one of the most sophisticated engineering products, the design for airplane production is particularly challenging for engineers. Not only because airplane structures often contain composite materials and intricate geometric shapes, but also an airplane contains massive parts for assembly. Besides, in terms of product features, aviation equipment has a much stricter requirement towards integration, stability, environmental adaptability, size and weight (especially for avionic equipment) compared to ground equipment
                    <sup>
                        <xref ref-type="bibr" rid="ref-37">37</xref>
                    </sup>. Those introduce much complexity to the airplane manufacturing plan.</p>
                <p>The complexity of airplane production lines is one popular topic in aviation and manufacturing fields
                    <sup>
                        <xref ref-type="bibr" rid="ref-38">38</xref>,
                        <xref ref-type="bibr" rid="ref-39">39</xref>
                    </sup>. Due to different purposes and usage scenarios, airplanes have significant varieties. For example, in terms of categories, aerospace engineers develop families of airliners, small fixed-wing airplanes and military airplanes. A fixed-wing airplane family shows varieties in wings, tails, fuselages, and propulsion systems in terms of design configurations. Therefore, adaptability is essential for airplane production lines. Meanwhile, due to sophisticated design and precisions, fabrications of some parts can contain a number of different  processes. Besides, airplanes usually have long service lives, while predictions of lifecycle performances are particularly challenging during quality inspections.</p>
                <p>Airplane manufacturing is arguably the most typical example of global production. Parts of airplanes (especially airliners) are usually produced in different countries. For example, for one airliner, its middle fuselage can be produced in Japan, its trailing edge of the wing can be produced in France, its tail can be produced in Canada, and its stabilizer can be produced in Italy. Finally, all parts will be transported to the same workshop for assembly. Complexity is thus introduced to supply chains of airplane manufacturing.</p>
            </sec>
            <sec>
                <title>Digital twin-driven management of manufacturing complexity in airplane design</title>
                <p>As aforementioned, composite materials and sophisticated geometric shapes of parts introduce complexity to airplane manufacturing. For example, for an airframe of a fuselage, its cross-section shape along the longitude direction is inconsistent due to the payload space, taper of tail and locations of wings. Besides, composite materials are often deployed on circular frames and longitude beams to balance weight and strength. Each circular frame or longitude beam is produced independently and is then finally assembled. Thus, the management of the manufacturing plan becomes essential.</p>
                <p>In this new framework, DTs can analyze relevant cases of airplane manufacturing and reorganizes manufacturing plans to reduce dependencies and uncertainties. Take the middle circular frame made of aluminum alloy as an example. Hypothetically, in an aluminum frame factory, users notice that the current manufacturing plan for circular frames of an airliner should be updated for fewer uncertainties. To help users update this manufacturing plan, DTs of workpieces begin with data uploading to trace manufacturing processes. The tracing outcome indicates that the &#x201c;forming press&#x201d; in this manufacturing plan is finished by Workpiece E and F. Besides, the &#x201c;forming press&#x201d; can only be executed after the &#x201c;punch press&#x201d; on Workpiece P, Q and M. After identifying such dependencies, DTs will reorganize the manufacturing plan by analyzing relevant cases. Via data exchanging with DTs in a peer factory, it is recognized that &#x201c;punch press+forming press&#x201d; can be done merely by Workpiece K and L. Besides, it is also identified that hollowing cuttings and edge bendings can also be done via other manufacturing processes. Consequently, as shown in 
                    <xref ref-type="table" rid="T3">Table 3</xref>, new manufacturing plans with fewer dependencies are generated as &#x201c;Set I, Set II and Set III&#x201d;. Afterward, DTs will compare the uncertainties of each new manufacturing plan. Set I consists of seven procedures: shearing, punch press, forming press, rolling, spot welding, frame welding, and grinding. Each procedure has specific inspection standards. For example, the quality of the punch press can be evaluated based on its hollow cut, springback effect and burst effect. DTs of workpieces can output uncertainties of corresponding inspection standards via dynamic work monitoring and data collections. Compared to Set I, Set II consists of six procedures, including shearing, punch press, rolling, forming press, pierce riveting and blasting. Set III is based on additive manufacturing. It thus merely consists of directed energy deposition and blasting. Similarly, uncertainties of each procedure can be obtained via DTs of engaged workpieces. Although different manufacturing plans vary in procedures, standards for the quality inspection of circular frames are the same, such as the diameters of hollows, heights of beams and radius of curvatures. Uncertainties of manufacturing plans can thus be calculated based on uncertainties of each inspection standard. All relevant data during this process will be forwarded to users. Uncertainties of manufacturing plans and their procedures will help users optimize and build manufacturing systems.</p>
                <table-wrap id="T3" orientation="portrait" position="anchor">
                    <label>Table 3. </label>
                    <caption>
                        <title>Manufacturing plan evaluations of circular frames for illustration.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="4" rowspan="1" valign="top">Properties of raw materials</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="4" rowspan="1" valign="top">Ultimate tensile strength:  
                                    <italic toggle="yes">A</italic>1 
                                    <italic toggle="yes">Mpa</italic>; Yield tensile strength:  
                                    <italic toggle="yes">A</italic>2 
                                    <italic toggle="yes">Mpa</italic>; Elongation at break:  
                                    <italic toggle="yes">A</italic>3%, etc. </td>
                            </tr>
                            <tr>
                                <th align="left" colspan="4" rowspan="1" valign="top">Standards of circular frames</th>
                            </tr>
                            <tr>
                                <td align="left" colspan="4" rowspan="1" valign="top">Diameter of hollows:  
                                    <italic toggle="yes">B</italic>1 
                                    <italic toggle="yes">IN</italic>; Height of beams:  
                                    <italic toggle="yes">B</italic>2 
                                    <italic toggle="yes">IN</italic>; Radius of curvatures:  
                                    <italic toggle="yes">B</italic>3 
                                    <italic toggle="yes">IN</italic>, etc.</td>
                            </tr>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Production procedures and uncertainties</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Set I</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Set II</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Set III</th>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Procedure 1</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Shearing
                                    <break/>Straight edge:  
                                    <italic toggle="yes">C</italic>1%
                                    <break/>Tearing:  
                                    <italic toggle="yes">C</italic>2%
                                    <break/>Wrinkling:  
                                    <italic toggle="yes">C</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Shearing
                                    <break/>Straight edge:  
                                    <italic toggle="yes">E</italic>1%
                                    <break/>Tearing:  
                                    <italic toggle="yes">E</italic>2%
                                    <break/>Wrinkling:  
                                    <italic toggle="yes">E</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Directed energy deposition
                                    <break/>Unequal height build:  
                                    <italic toggle="yes">Q</italic>1%
                                    <break/>Internal cracking:  
                                    <italic toggle="yes">Q</italic>2%
                                    <break/>Dilution zone:  
                                    <italic toggle="yes">Q</italic>3%</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Procedure 2</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Punch press
                                    <break/>Hollow cut:  
                                    <italic toggle="yes">D</italic>1%
                                    <break/>Springback:  
                                    <italic toggle="yes">D</italic>2%
                                    <break/>Burst:  
                                    <italic toggle="yes">D</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Punch Press
                                    <break/>Hollow cut:  
                                    <italic toggle="yes">F</italic>1%
                                    <break/>Springback:  
                                    <italic toggle="yes">F</italic>2%
                                    <break/>Burst:  
                                    <italic toggle="yes">F</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Blasting &amp; Painting
                                    <break/>Surface roughness:  
                                    <italic toggle="yes">P</italic>%</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Procedure 3</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Forming press
                                    <break/>Bending angle:  
                                    <italic toggle="yes">G</italic>1%
                                    <break/>Edge height:  
                                    <italic toggle="yes">G</italic>2%
                                    <break/>Edge gap:  
                                    <italic toggle="yes">G</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Rolling
                                    <break/>Line width:  
                                    <italic toggle="yes">I</italic>1%
                                    <break/>Longitudinal twist:  
                                    <italic toggle="yes">I</italic>2%
                                    <break/>Curvature diameter:  
                                    <italic toggle="yes">I</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top"/>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Procedure 4</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Rolling
                                    <break/>Line width:  
                                    <italic toggle="yes">M</italic>1%
                                    <break/>Longitudinal twist:  
                                    <italic toggle="yes">M</italic>2%
                                    <break/>Curvature diameter:  
                                    <italic toggle="yes">M</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Forming press
                                    <break/>Bending angle:  
                                    <italic toggle="yes">H</italic>1%
                                    <break/>Edge height:  
                                    <italic toggle="yes">H</italic>2%
                                    <break/>Edge gap:  
                                    <italic toggle="yes">H</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top"/>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Procedure 5</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Spot welding:
                                    <break/>Welding crack:  
                                    <italic toggle="yes">J</italic>1%
                                    <break/>Welding size:  
                                    <italic toggle="yes">J</italic>2%
                                    <break/>Unfused area: 
                                    <italic toggle="yes">J</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Pierce riveting
                                    <break/>Rivet fracture:  
                                    <italic toggle="yes">L</italic>1%
                                    <break/>Riveting crack:  
                                    <italic toggle="yes">L</italic>2%
                                    <break/>Misplacement:  
                                    <italic toggle="yes">L</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top"/>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Procedure 6</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Frame welding:
                                    <break/>Welding crack:  
                                    <italic toggle="yes">K</italic>1%
                                    <break/>Welding size:  
                                    <italic toggle="yes">K</italic>2%
                                    <break/>Unfused area:  
                                    <italic toggle="yes">K</italic>3%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Blasting &amp; Painting
                                    <break/>Surface roughness:  
                                    <italic toggle="yes">N</italic>1%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top"/>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Procedure 7</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Grinding
                                    <break/>Surface roughness:  
                                    <italic toggle="yes">O</italic>%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top"/>
                                <td align="left" colspan="1" rowspan="1" valign="top"/>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Overall evaluations:</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Diameter of Hollows:  
                                    <italic toggle="yes">R</italic>1%
                                    <break/>Height of Beams:  
                                    <italic toggle="yes">R</italic>2%
                                    <break/>Radius of curvatures:  
                                    <italic toggle="yes">R</italic>3%
                                    <break/>&#x2026;&#x2026;
                                    <break/>Overall uncertainties:  
                                    <italic toggle="yes">R</italic>4%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Diameter of Hollows:  
                                    <italic toggle="yes">S</italic>1%
                                    <break/>Height of Beams:  
                                    <italic toggle="yes">S</italic>2%
                                    <break/>Radius of curvatures:  
                                    <italic toggle="yes">S</italic>3%
                                    <break/>&#x2026;&#x2026;
                                    <break/>Overall uncertainties:  
                                    <italic toggle="yes">S</italic>4%</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Diameter of Hollows:  
                                    <italic toggle="yes">T</italic>1%
                                    <break/>Height of Beams:  
                                    <italic toggle="yes">T</italic>2%
                                    <break/>Radius of curvatures:  
                                    <italic toggle="yes">T</italic>3%
                                    <break/>&#x2026;&#x2026;
                                    <break/>Overall uncertainties:  
                                    <italic toggle="yes">T</italic>4%</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
            </sec>
            <sec>
                <title>Digital twin-driven management of manufacturing complexity in airplane production lines</title>
                <p>In this new framework, based on dynamic monitoring and virtual simulations, DTs can evaluate complexity from airplane production lines while maintaining adaptability. Take the fuselage assembly as an example. Although the fuselage assembly is a typical modularized production, its adaptability is still essential to customize fuselages. Besides, fuselage assembly consists of abundant procedures such as weldings, pierce rivetings and blastings. In correspondence, there are abundant tools for assembly such as fasteners, drillers and welding machines. According to 
                    <xref ref-type="other" rid="e4">Formula (4)</xref>, as difficulties of assembly and feature variants are constant, the complexity of an assembly station is determined by choices of fixtures, tools, assembly activities and resources. Meanwhile, according to 
                    <xref ref-type="other" rid="e6">Formula (6)</xref>, the complexity of a production line is determined by the number and complexity of consisted assembly stations. Hypothetically, users input multiple candidate designs of fuselage assembly lines for complexity evaluations. Enabled by high-fidelity models and recordings of assembly cases, DTs begin with simulating candidates. Those incompetent designs will be removed. Afterward, candidate designs with clearly excessive complexity will be removed either. 
                    <xref ref-type="table" rid="T4">Table 4</xref> shows some examples of the rest designs, which will come to the complexity comparison. Based on dynamic data recordings of workpieces, users&#x2019; settings and statistics of previous cases, different fixtures, tools, assembly activities and resources, weight contributions towards task difficulties and station entropies can be estimated by DTs. The outcome will be forwarded to users for selections and optimizations.</p>
                <table-wrap id="T4" orientation="portrait" position="anchor">
                    <label>Table 4. </label>
                    <caption>
                        <title>Examples of fuselage assembly line for complexity evaluations.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="7" rowspan="1" valign="top">Assembly Line 1</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <th colspan="1" rowspan="1"/>
                                <th align="left" colspan="1" rowspan="1" valign="top">Fixtures</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Tools</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Activities</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Resources</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Task difficulty (
                                    <inline-formula>
                                        <mml:math display="inline" id="M5">
                                            <mml:mrow>
                                                <mml:msubsup>
                                                    <mml:mi>a</mml:mi>
                                                    <mml:mi>j</mml:mi>
                                                    <mml:mi>k</mml:mi>
                                                </mml:msubsup>
                                            </mml:mrow>
                                        </mml:math>
                                    </inline-formula>)</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Station Entropy (
                                    <inline-formula>
                                        <mml:math display="inline" id="M6">
                                            <mml:mrow>
                                                <mml:msubsup>
                                                    <mml:mi>H</mml:mi>
                                                    <mml:mi>j</mml:mi>
                                                    <mml:mi>k</mml:mi>
                                                </mml:msubsup>
                                            </mml:mrow>
                                        </mml:math>
                                    </inline-formula>)</th>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 1</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>1</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>1, 
                                    <italic toggle="yes">T</italic>2</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>1</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>1, 
                                    <italic toggle="yes">R</italic>2, 
                                    <italic toggle="yes">R</italic>3</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>1</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>1</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 2</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>2</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>3, 
                                    <italic toggle="yes">T</italic>4, 
                                    <italic toggle="yes">T</italic>5</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>2</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>2, 
                                    <italic toggle="yes">R</italic>4</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>2</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>2</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 3</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>3</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>6</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>3</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>3, 
                                    <italic toggle="yes">R</italic>5, 
                                    <italic toggle="yes">R</italic>6, 
                                    <italic toggle="yes">R</italic>7</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>3</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>3</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 4</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>4</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>7</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>4</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>5, 
                                    <italic toggle="yes">R</italic>7, 
                                    <italic toggle="yes">R</italic>8</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>4</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>4</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="7" rowspan="1" valign="top">Overall complexity: 
                                    <italic toggle="yes">C</italic>
                                    <sub>1</sub> 
                        </td>
                            </tr>
                            <tr>
                                <th align="left" colspan="7" rowspan="1" valign="top">Assembly Line 2</th>
                            </tr>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top"/>
                                <th align="left" colspan="1" rowspan="1" valign="top">Fixtures</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Tools</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Activities</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Resources</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Task difficulty (
                                    <inline-formula>
                                        <mml:math display="inline" id="M7">
                                            <mml:mrow>
                                                <mml:msubsup>
                                                    <mml:mi>a</mml:mi>
                                                    <mml:mi>j</mml:mi>
                                                    <mml:mi>k</mml:mi>
                                                </mml:msubsup>
                                            </mml:mrow>
                                        </mml:math>
                                    </inline-formula>)</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Station Entropy (
                                    <inline-formula>
                                        <mml:math display="inline" id="M8">
                                            <mml:mrow>
                                                <mml:msubsup>
                                                    <mml:mi>H</mml:mi>
                                                    <mml:mi>j</mml:mi>
                                                    <mml:mi>k</mml:mi>
                                                </mml:msubsup>
                                            </mml:mrow>
                                        </mml:math>
                                    </inline-formula>)</th>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 1</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>5</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>6</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>3</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>3, 
                                    <italic toggle="yes">R</italic>5, 
                                    <italic toggle="yes">R</italic>6, 
                                    <italic toggle="yes">R</italic>7</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>5</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>5</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 2</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>6</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>2, 
                                    <italic toggle="yes">T</italic>4, 
                                    <italic toggle="yes">T</italic>5</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>5</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>4, 
                                    <italic toggle="yes">R</italic>9</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>6</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>6</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 3</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>7</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>7, 
                                    <italic toggle="yes">T</italic>8</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>6</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>5, 
                                    <italic toggle="yes">R</italic>7, 
                                    <italic toggle="yes">R</italic>10</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>7</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>7</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 4</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>8</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>9</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>7</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>2, 
                                    <italic toggle="yes">R</italic>11, 
                                    <italic toggle="yes">R</italic>12</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>8</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>8</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="7" rowspan="1" valign="top">Overall complexity: 
                                    <italic toggle="yes">C</italic>
                                    <sub>2</sub>  
                        </td>
                            </tr>
                            <tr>
                                <th align="left" colspan="7" rowspan="1" valign="top">Assembly Line 3</th>
                            </tr>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top"/>
                                <th align="left" colspan="1" rowspan="1" valign="top">Fixtures</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Tools</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Activities</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Resources</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Task difficulty (
                                    <inline-formula>
                                        <mml:math display="inline" id="M9">
                                            <mml:mrow>
                                                <mml:msubsup>
                                                    <mml:mi>a</mml:mi>
                                                    <mml:mi>j</mml:mi>
                                                    <mml:mi>k</mml:mi>
                                                </mml:msubsup>
                                            </mml:mrow>
                                        </mml:math>
                                    </inline-formula>)</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Station Entropy (
                                    <inline-formula>
                                        <mml:math display="inline" id="M10">
                                            <mml:mrow>
                                                <mml:msubsup>
                                                    <mml:mi>H</mml:mi>
                                                    <mml:mi>j</mml:mi>
                                                    <mml:mi>k</mml:mi>
                                                </mml:msubsup>
                                            </mml:mrow>
                                        </mml:math>
                                    </inline-formula>)</th>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 1</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>9</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>3, 
                                    <italic toggle="yes">T</italic>4, 
                                    <italic toggle="yes">T</italic>10</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>2</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>2, 
                                    <italic toggle="yes">R</italic>4</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>9</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>9</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 2</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>10</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>6</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>3</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>3, 
                                    <italic toggle="yes">R</italic>5, 
                                    <italic toggle="yes">R</italic>6, 
                                    <italic toggle="yes">R</italic>7</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>10</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>10</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 3</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>11</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>9</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>7</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>2, 
                                    <italic toggle="yes">R</italic>11, 
                                    <italic toggle="yes">R</italic>12</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>11</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>11</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Station 4</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">F</italic>12</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>11</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">k</italic>
                                    <sup>8</sup>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">R</italic>8, 
                                    <italic toggle="yes">R</italic>13, 
                                    <italic toggle="yes">R</italic>14</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">a</italic>
                                    <sub>12</sub>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">H</italic>
                                    <sub>12</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="7" rowspan="1" valign="top">Overall complexity: 
                                    <italic toggle="yes">C</italic>
                                    <sub>3</sub> 
                        </td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>DTs help users replace workpieces with high uncertainties. Operation deviations exist in every workpiece, while operation accuracy is arguably the most essential issue in airplane production lines. Timely replacement of worn workpieces is necessary to reduce production uncertainties. Take the compressor of an airplane engine as an example. Production precision significantly affects the aerodynamic performance of an engine compressor, while its intricate structure challenges conventional production techniques. Nowadays, additive manufacturing has become a popular approach to fabricating engine compressors due to its flexibility of structure shaping. 
                    <xref ref-type="table" rid="T5">Table 5</xref> shows some important parameters of powder bed fusion (a typical additive manufacturing technique to produce metal products) to produce a compressor
                    <sup>
                        <xref ref-type="bibr" rid="ref-40">40</xref>
                    </sup>. Any deviations of those parameters can cause defective compressors. DTs can be deployed to workpieces on a powder bed fusion machine, such as the substrate, leveling roller and laser shooter. Thus, DTs can dynamically monitor the states of workpieces and record operating parameters. Based on production standards, DTs of workpieces can automatically adjust those operating parameters in real-time during the operation. As data accumulate, DTs can also identify worn workpieces on powder bed fusion machines. With standard production parameters as references, DTs can conduct analysis of variance tests for workpieces based on their production data. Tests with significant data differences indicate high defective rates of corresponding workpieces. Finally, outcomes will be forwarded to users for workpiece replacements or maintenance.</p>
                <table-wrap id="T5" orientation="portrait" position="anchor">
                    <label>Table 5. </label>
                    <caption>
                        <title>Examples of parameters of powder bed fusion.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Parameters</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Value</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Laser power(
                                    <italic toggle="yes">P</italic>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">P</italic>
                                    <sub>1</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Scanning Speed(
                                    <italic toggle="yes">v</italic>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">v</italic>
                                    <sub>1</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Hatch Spacing(
                                    <italic toggle="yes">h</italic>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">h</italic>
                                    <sub>1</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Layer sickness(
                                    <italic toggle="yes">t</italic>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">t</italic>
                                    <sub>1</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Bed temperature(
                                    <italic toggle="yes">T</italic>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">T</italic>
                                    <sub>1</sub>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Laser spot size(
                                    <italic toggle="yes">d
                                        <sub>spot</sub>
                                    </italic>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">d
                                        <sub>spot1</sub>
                                    </italic>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Laser focusability(
                                    <italic toggle="yes">M
                                        <sup>2</sup>
                                    </italic>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <inline-formula>
                                        <mml:math display="inline" id="M">
                                            <mml:mrow>
                                                <mml:msubsup>
                                                    <mml:mi>M</mml:mi>
                                                    <mml:mn>1</mml:mn>
                                                    <mml:mn>2</mml:mn>
                                                </mml:msubsup>
                                            </mml:mrow>
                                        </mml:math>
                                    </inline-formula>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Laser wavelength(
                                    <italic toggle="yes">&#x03b3;</italic>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <italic toggle="yes">&#x03b3;</italic>
                                    <sub>1</sub>
                                </td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>DTs can predict the uncertainties of an airplane through lifecycles. Airplanes work in fluctuating environments and working states. Besides, airplanes usually have long service lives. Therefore, working uncertainties of airplane parts shift following accumulations of cyclic loads. Conventional quality inspections are struggled to assure reliabilities of components through lifecycles while DTs have such potentials. Take flaps on airplane wings as an example. Flaps are vital surface control units of airplanes. During airplane landings, flaps deflect to increase stall angle and drag forces, reducing taxi distance and enhancing airplane brakes
                    <sup>
                        <xref ref-type="bibr" rid="ref-41">41</xref>
                    </sup>. Actuators on wings control flaps. Performances of flaps are affected by several environmental factors such as humidity, temperature and wind speed. Besides, flaps tend to get worn out faster than many other airplane components
                    <sup>
                        <xref ref-type="bibr" rid="ref-42">42</xref>
                    </sup>. DTs of flaps can predict performances through their lifecycles. DTs can obtain data of flaps in different states (environments and service time) via three approaches. Firstly, DTs can predict the performances of flaps via relevant mathematics models. Secondly, DTs can monitor flaps in real-time and record working data in different states. Besides, data exchanges among peer DTs enable rapid accumulations of flap datasets. Finally, DTs can simulate performances of flaps in different states via high-fidelity virtual models. Afterward, based on Information Axiom and flap datasets, 
                    <xref ref-type="fig" rid="f8">Figure 8</xref> shows the system distributions of flap drag forces in different states. Thus, uncertainties of each flap state can be calculated according to the design range.</p>
                <fig fig-type="figure" id="f8" orientation="portrait" position="float">
                    <label>Figure 8. </label>
                    <caption>
                        <title>Uncertainties of flaps in different states.</title>
                    </caption>
                    <graphic orientation="portrait" position="float"
                        xlink:href="https://digitaltwin1-files.f1000.com/manuscripts/18764/35d6fa26-cfc9-45a7-999f-b0154adad6cb_figure8.gif"/>
                </fig>
            </sec>
            <sec>
                <title>Digital twin-driven management of manufacturing complexity in airplane supply chain</title>
                <p>In this new framework, DTs can help users predict supply changes and evaluate risks. Airplane manufacturing is a paradigm of global production. Suppliers, factories and logistic stations vary in local conditions. Take the landing gears of an airliner as an example. A landing gear consists of massive components. Damaged by shocks of airliner landings, landing gears often go through frequent maintenances and overhauls. Besides, landing gears are customized for each airliner. Thus, different supply chains of airliners have few intersections. Hypothetically, a landing gear factory undertakes maintenance, overhauls and replacements of landing gears for a specific airliner model in a local airport. DTs in the factory can predict required supplies by exchanging data with DTs of landing gears on airliners.</p>
                <p>As DTs of landing gears dynamically can collect data from landing gears, the health conditions of each component can thus be retrieved. Afterward, DTs of landing gears will forward data to DTs in the landing gear factory. Therefore, DTs in the factory can calculate required maintenance, overhauls and replacements at a specific moment. Thus, the factory managers can plan component productions and supplies for the airport in the following period. Then, DTs of the factory will evaluate risks from component suppliers. Hypothetically, the factory has three suppliers for trailing arms and shock absorb cylinders, respectively. The risk evaluations will be based on data about local environments, factory management and economic policies related to component suppliers. DTs can collect data of local environments from historical recordings and data release from local environmental management departments. For example, the factory is going to purchase a batch of trailing arms from a supplier during the summer. However, the supplier&#x2019;s factory is located near the equator, and data show a high possibility of floods during this period. Hence, the landing gear factory manager should consider the influence of delivery delay or turn to the other two suppliers. About suppliers&#x2019; factory management, DTs can obtain data via crowdsourcing. All stakeholders related to component suppliers can be potential data sources, such as suppliers of raw materials, other customers of component suppliers and employees of component suppliers. For example, DTs can source their feedbacks and whitepapers about component suppliers. These can be processed into risk indexes of suppliers&#x2019; factory management. Meanwhile, DTs can obtain data of economic policies by analyzing related recordings. For example, by analyzing fluctuations of exchange rates and speed of merchandizes through customs in previous years, DTs can predict these changes in a short term and highlight possible risks.</p>
            </sec>
        </sec>
        <sec sec-type="conclusions">
            <title>Conclusions and future work</title>
            <p>In conclusion, in the era of intelligent manufacturing, DT enables a new paradigm of complexity management. DT improves the management of manufacturing complexity via its three important SVs: (1) Real-time monitors and data collections; (2) identifications, diagnoses and predictions of manufacturing complexity; (3) Fortifications of human-machine interactions. For manufacturing complexity from product design, DT aims to reduce the dependencies and uncertainties in manufacturing plans. For manufacturing complexity from production lines, DT aims to: (1) balance among adaptability, reliability and productivity. (2) Replace workpieces with high uncertainties. (3) Predict uncertainties of products through lifecycles. DT aims to predict supply changes, evaluate risks, predict losses, and make emergency plans for the manufacturing complexity from supply chains.</p>
            <p>This paper proposes an innovative approach for complexity management. Conventionally, complexity management has remained an empirical process in manufacturing and is mainly driven by human efforts. DT enables this process to be more autonomous, analytical and comprehensive. Besides, compared to other cyber-physical systems, DT resolves gaps within physical-virtual communications, insufficient quality of virtual models and limited data. Intelligent manufacturing is characterized by its digitalization, autonomy and flexibility. The DT-driven complexity management will promote this trend. Meanwhile, in terms of the development of DT, as emerging information technology, its concepts, enabling technology and applications are still under investigation. Most existent research about DT concentrates on mega-project developments, production management and health care issues. This is the first proposition that applies DT to complexity management. This innovative framework enables new research about manufacturing design and DT in intelligent manufacturing. In terms of manufacturing design, this framework can be implemented for investigations on verifications and evaluations of manufacturing complexity in different scenarios. Besides, this framework also serves as a piece of puzzle for the research about the future grand manufacturing design together with functional design, process design and verification design enabled by other emerging technology. In terms of DT, this framework extrapolates functions and roles of DTs in future factories. Future research can work on collaborations of DT-driven complexity management with other functions. Also, future research can proceed this framework by completing technical details of DTs in realizing this framework.</p>
            <p>There are two important issues for future work. One is the verification of this framework in industry. This paper serves as a proposition, clarification and illustration of DT-driven complexity management in manufacturing. Its practical effect remains pending until verified in industries. However, such verification can be particularly challenging as it consists of abundant designs, resources and human efforts. Besides, several important challenges are to be resolved for its realization, such as communication latencies among systems, capabilities of tremendous data processing, and privacy protections. Therefore, the completion and verification of this framework rely on developments of relevant technologies, such as edge computing, the fifth generation of cellular networks and federated learning
                <sup>
                    <xref ref-type="bibr" rid="ref-43">43</xref>
                </sup>.</p>
            <p>The other issue is the investigation on how to manage complexity caused by DT. DT is a sophisticated system that consists of tremendous software and hardware devices. Through the working of DT, massive data flows and couplings get engaged. Therefore, when resolving manufacturing complexity, DT simultaneously introduces complexity to manufacturing. Complexity management of DT will be an essential issue of future research.</p>
        </sec>
        <sec>
            <title>Data availability</title>
            <p>No data are associated with this article.</p>
        </sec>
    </body>
    <back>
        <ref-list>
            <ref id="ref-1">
                <label>1</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Calinescu</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Efstathiou</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Schirn</surname>
                            <given-names>J</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Applying and assessing two methods for measuring complexity in manufacturing.</article-title>
                    <source>

                        <italic toggle="yes">J Oper Res Soc.</italic>
               </source>
               <year>1998</year>;<volume>49</volume>(<issue>7</issue>):<fpage>723</fpage>&#x2013;<lpage>733</lpage>.
                    <pub-id pub-id-type="doi">10.2307/3010243 </pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-2">
                <label>2</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Bozarth</surname>
                            <given-names>CC</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Warsing</surname>
                            <given-names>DP</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Flynn</surname>
                            <given-names>BB</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>The impact of supply chain complexity on manufacturing plant performance.</article-title>
                    <source>

                        <italic toggle="yes">J Oper Manag.</italic>
               </source>
               <year>2009</year>;<volume>27</volume>(<issue>1</issue>):<fpage>78</fpage>&#x2013;<lpage>93</lpage>.
                    <pub-id pub-id-type="doi">10.1016/j.jom.2008.07.003</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-3">
                <label>3</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>ElMaraghy</surname>
                            <given-names>W</given-names>
                        </name>

                        <name name-style="western">
                            <surname>ElMaraghy</surname>
                            <given-names>H</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tomiyama</surname>
                            <given-names>T</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Complexity in engineering design and manufacturing.</article-title>
                    <source>

                        <italic toggle="yes">CIRP Annals.</italic>
               </source>
               <year>2012</year>;<volume>61</volume>(<issue>2</issue>):<fpage>793</fpage>&#x2013;<lpage>814</lpage>.
                    <pub-id pub-id-type="doi">10.1016/j.cirp.2012.05.001</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-4">
                <label>4</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Suh</surname>
                            <given-names>NP</given-names>
                        </name>
               </person-group>:
                    <article-title>Complexity in engineering.</article-title>
                    <source>

                        <italic toggle="yes">CIRP Annals.</italic>
               </source>
               <year>2005</year>;<volume>54</volume>(<issue>2</issue>):<fpage>46</fpage>&#x2013;<lpage>63</lpage>.
                    <pub-id pub-id-type="doi">10.1016/S0007-8506(07)60019-5</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-5">
                <label>5</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Bashir</surname>
                            <given-names>HA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Thomson</surname>
                            <given-names>V</given-names>
                        </name>
               </person-group>:
                    <article-title>Estimating design complexity.</article-title>
                    <source>

                        <italic toggle="yes">J Eng Design.</italic>
               </source>
               <year>1999</year>;<volume>10</volume>(<issue>3</issue>):<fpage>247</fpage>&#x2013;<lpage>257</lpage>.
                    <pub-id pub-id-type="doi">10.1080/095448299261317</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-6">
                <label>6</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Perona</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Miragliotta</surname>
                            <given-names>G</given-names>
                        </name>
               </person-group>:
                    <article-title>Complexity management and supply chain performance assessment. A field study and a conceptual framework.</article-title>
                    <source>

                        <italic toggle="yes">Int J Prod Econ.</italic>
               </source>
               <year>2004</year>;<volume>90</volume>(<issue>1</issue>):<fpage>103</fpage>&#x2013;<lpage>115</lpage>.
                    <pub-id pub-id-type="doi">10.1016/S0925-5273(02)00482-6</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-7">
                <label>7</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Helo</surname>
                            <given-names>P</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Suorsa</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hao</surname>
                            <given-names>Y</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Toward a cloud-based manufacturing execution system for distributed manufacturing.</article-title>
                    <source>

                        <italic toggle="yes">Comput Ind.</italic>
               </source>
               <year>2014</year>;<volume>65</volume>(<issue>4</issue>):<fpage>646</fpage>&#x2013;<lpage>656</lpage>.
                    <pub-id pub-id-type="doi">10.1016/j.compind.2014.01.015</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-8">
                <label>8</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Kusiak</surname>
                            <given-names>A</given-names>
                        </name>
               </person-group>:
                    <article-title>Smart manufacturing.</article-title>
                    <source>

                        <italic toggle="yes">Int J Prod Res.</italic>
               </source>
               <year>2018</year>;<volume>56</volume>(<issue>1&#x2013;2</issue>):<fpage>508</fpage>&#x2013;<lpage>517</lpage>.
                    <pub-id pub-id-type="doi">10.1080/00207543.2017.1351644</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-9">
                <label>9</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Davis</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Edgar</surname>
                            <given-names>T</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Porter</surname>
                            <given-names>J</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Smart manufacturing, manufacturing intelligence and demand-dynamic performance.</article-title>
                    <source>

                        <italic toggle="yes">Comput Chem Eng.</italic>
               </source>
               <year>2012</year>;<volume>47</volume>:<fpage>145</fpage>&#x2013;<lpage>156</lpage>.
                    <pub-id pub-id-type="doi">10.1016/j.compchemeng.2012.06.037</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-10">
                <label>10</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Kang</surname>
                            <given-names>HS</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lee</surname>
                            <given-names>JY</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Choi</surname>
                            <given-names>S</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Smart manufacturing: Past research, present findings, and future directions.</article-title>
                    <source>

                        <italic toggle="yes">Int J Pr Eng Man-Gt.</italic>
               </source>
               <year>2016</year>;<volume>3</volume>(<issue>1</issue>):<fpage>111</fpage>&#x2013;<lpage>128</lpage>.
                    <pub-id pub-id-type="doi">10.1007/s40684-016-0015-5</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-11">
                <label>11</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Grieves</surname>
                            <given-names>M</given-names>
                        </name>
               </person-group>:
                    <article-title>Digital twin: manufacturing excellence through virtual factory replication.</article-title>
                    <source>

                        <italic toggle="yes">White paper.</italic>
               </source>
               <year>2014</year>;<volume>1</volume>:<fpage>1</fpage>&#x2013;<lpage>7</lpage>.
                    <ext-link ext-link-type="uri"
                         xlink:href="https://www.researchgate.net/publication/275211047_Digital_Twin_Manufacturing_Excellence_through_Virtual_Factory_Replication">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-12">
                <label>12</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Glaessgen</surname>
                            <given-names>E</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Stargel</surname>
                            <given-names>D</given-names>
                        </name>
               </person-group>:
                    <article-title>The digital twin paradigm for future NASA and US Air Force vehicles.</article-title>In
                    <source>

                        <italic toggle="yes">53rd AIAA/ASME/ASCE/AHS/ASC Structures, Structural Dynamics and Materials Conference 20th AIAA/ASME/AHS Adaptive Structures Conference 14th AIAA.</italic>
               </source>
               <year> 2012</year>;<fpage>1818</fpage>.
                    <ext-link ext-link-type="uri"
                         xlink:href="https://ntrs.nasa.gov/api/citations/20120008178/downloads/20120008178.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-13">
                <label>13</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Tao</surname>
                            <given-names>F</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Liu</surname>
                            <given-names>W</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>M</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Five-dimension Digital Twin Model and its Ten Applications.</article-title>Computer Integrated Manufacturing Systems.<year> 2019</year>;<volume>25</volume>(<issue>1</issue>):<fpage>1</fpage>&#x2013;<lpage>8</lpage>.
                    <ext-link ext-link-type="uri"
                         xlink:href="https://en.cnki.com.cn/Article_en/CJFDTotal-JSJJ201901001.htm">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-14">
                <label>14</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Qi</surname>
                            <given-names>Q</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tao</surname>
                            <given-names>F</given-names>
                        </name>
               </person-group>:
                    <article-title>Digital twin and big data towards smart manufacturing and industry 4.0: 360 degree comparison.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
               </source>
               <year>2018</year>;<volume>6</volume>:<fpage>3585</fpage>&#x2013;<lpage>3593</lpage>.
                    <pub-id pub-id-type="doi">10.1109/ACCESS.2018.2793265</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-15">
                <label>15</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Tuegel</surname>
                            <given-names>EJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Ingraffea</surname>
                            <given-names>AR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Eason</surname>
                            <given-names>TG</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Reengineering aircraft structural life prediction using a digital twin.</article-title>
                    <source>

                        <italic toggle="yes">Int J Aerospace Eng.</italic>
               </source>
               <year>2011</year>;<volume>2011</volume>.
                    <pub-id pub-id-type="doi">10.1155/2011/154798</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-16">
                <label>16</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Lund</surname>
                            <given-names>AM</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Mochel</surname>
                            <given-names>K</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lin</surname>
                            <given-names>JW</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>U.S. Patent No. 9,995,278.</article-title>Washington, DC: U.S. Patent and Trademark Office,<year>2018</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://patents.justia.com/patent/9995278">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-17">
                <label>17</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Frizelle</surname>
                            <given-names>G</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Woodcock</surname>
                            <given-names>E</given-names>
                        </name>
               </person-group>:
                    <article-title>Measuring complexity as an aid to developing operational strategy.</article-title>
                    <source>

                        <italic toggle="yes">International Journal of Operations &amp; Production Management.</italic>
               </source>
               <year>1995</year>;<volume>15</volume>(<issue>5</issue>):<fpage>26</fpage>&#x2013;<lpage>39</lpage>.
                    <pub-id pub-id-type="doi">10.1108/01443579510083640</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-18">
                <label>18</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Suh</surname>
                            <given-names>NP</given-names>
                        </name>
               </person-group>:
                    <article-title>Axiomatic design theory for systems.</article-title>
                    <source>

                        <italic toggle="yes">Res Eng Des.</italic>
               </source>
               <year>1998</year>;<volume>10</volume>(<issue>4</issue>):<fpage>189</fpage>&#x2013;<lpage>209</lpage>.
                    <pub-id pub-id-type="doi">10.1007/s001639870001</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-19">
                <label>19</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Fujimoto</surname>
                            <given-names>H</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Ahmed</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Iida</surname>
                            <given-names>Y</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Assembly process design for managing manufacturing complexities because of product varieties.</article-title>
                    <source>

                        <italic toggle="yes">International Journal of Flexible Manufacturing Systems.</italic>
               </source>
               <year>2003</year>;<volume>15</volume>(<issue>4</issue>):<fpage>283</fpage>&#x2013;<lpage>307</lpage>.
                    <pub-id pub-id-type="doi">10.1023/B:FLEX.0000036031.33790.30</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-20">
                <label>20</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hu</surname>
                            <given-names>SJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhu</surname>
                            <given-names>X</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Wang</surname>
                            <given-names>H</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Product variety and manufacturing complexity in assembly systems and supply chains.</article-title>
                    <source>

                        <italic toggle="yes">CIRP Annals.</italic>
               </source>
               <year>2008</year>;<volume>57</volume>(<issue>1</issue>):<fpage>45</fpage>&#x2013;<lpage>48</lpage>.
                    <pub-id pub-id-type="doi">10.1016/j.cirp.2008.03.138</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-21">
                <label>21</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Manuj</surname>
                            <given-names>I</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Mentzer</surname>
                            <given-names>JT</given-names>
                        </name>
               </person-group>:
                    <article-title>Global supply chain risk management.</article-title>
                    <source>

                        <italic toggle="yes">Journal of business logistics.</italic>
               </source>
               <year>2008</year>;<volume>29</volume>(<issue>1</issue>):<fpage>133</fpage>&#x2013;<lpage>155</lpage>.
                    <pub-id pub-id-type="doi">10.1002/j.2158-1592.2008.tb00072.x</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-22">
                <label>22</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Orfi</surname>
                            <given-names>N</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Terpenny</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Sahin-Sariisik</surname>
                            <given-names>A</given-names>
                        </name>
               </person-group>:
                    <article-title>Harnessing Product Complexity: Step 1&#x2014;Establishing Product Complexity Dimensions and Indicators.</article-title>
                    <source>

                        <italic toggle="yes">The Engineering Economist.</italic>
               </source>
               <year>2011</year>;<volume>56</volume>(<issue>1</issue>):<fpage>59</fpage>&#x2013;<lpage>79</lpage>.
                    <pub-id pub-id-type="doi">10.1080/0013791X.2010.549935</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-23">
                <label>23</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Wiendahl</surname>
                            <given-names>HP</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Scholtissek</surname>
                            <given-names>P</given-names>
                        </name>
               </person-group>:
                    <article-title>Management and control of complexity in manufacturing.</article-title>
                    <source>

                        <italic toggle="yes">CIRP Annals.</italic>
               </source>
               <year>1994</year>;<volume>43</volume>(<issue>2</issue>):<fpage>533</fpage>&#x2013;<lpage>540</lpage>.
                    <pub-id pub-id-type="doi">10.1016/S0007-8506(07)60499-5</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-24">
                <label>24</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zieli&#x0144;ski</surname>
                            <given-names>JG</given-names>
                        </name>
               </person-group>:
                    <article-title>Centralisation and Decentralisation in Decision-making.</article-title>
                    <source>

                        <italic toggle="yes">Econ Plann.</italic>
               </source>
               <year>1963</year>;<volume>3</volume>(<issue>3</issue>):<fpage>196</fpage>&#x2013;<lpage>208</lpage>.
                    <pub-id pub-id-type="doi">10.1007/BF02481403</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-25">
                <label>25</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zhou</surname>
                            <given-names>K</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Liu</surname>
                            <given-names>T</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhou</surname>
                            <given-names>L</given-names>
                        </name>
               </person-group>:
                    <article-title>Industry 4.0: Towards future industrial opportunities and challenges.</article-title>In
                    <italic toggle="yes">2015 12th International conference on fuzzy systems and knowledge discovery (FSKD).</italic>IEEE,<year>2015</year>;<fpage>2147</fpage>&#x2013;<lpage>2152</lpage>.
                    <pub-id pub-id-type="doi">10.1109/FSKD.2015.7382284</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-26">
                <label>26</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hermann</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Pentek</surname>
                            <given-names>T</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Otto</surname>
                            <given-names>B</given-names>
                        </name>
               </person-group>:
                    <article-title>Design principles for industrie 4.0 scenarios.</article-title>In
                    <italic toggle="yes">2016 49th Hawaii international conference on system sciences (HICSS).</italic>IEEE,<year>2016</year>;<fpage>3928</fpage>&#x2013;<lpage>3937</lpage>.
                    <pub-id pub-id-type="doi">10.1109/HICSS.2016.488</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-27">
                <label>27</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Sniderman</surname>
                            <given-names>B</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Mahto</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Cotteleer</surname>
                            <given-names>MJ</given-names>
                        </name>
               </person-group>:
                    <article-title>Industry 4.0 and manufacturing ecosystems: Exploring the world of connected enterprises.</article-title>
                    <source>

                        <italic toggle="yes">Deloitte Consulting.</italic>
               </source>
               <year>2016</year>.
                    <ext-link ext-link-type="uri"
                         xlink:href="https://www2.deloitte.com/content/dam/Deloitte/de/Documents/consumer-industrial-products/Deloitte-Industry-4-0-and-manufacturing-ecosystems.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-28">
                <label>28</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Tao</surname>
                            <given-names>F</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Cheng</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Qi</surname>
                            <given-names>Q</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Digital twin-driven product design, manufacturing and service with big data.</article-title>
                    <source>

                        <italic toggle="yes">Int J Adv Manuf Technol.</italic>
               </source>
               <year>2018</year>;<volume>94</volume>(<issue>9&#x2013;12</issue>):<fpage>3563</fpage>&#x2013;<lpage>3576</lpage>.
                    <pub-id pub-id-type="doi">10.1007/s00170-017-0233-1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-29">
                <label>29</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Lee</surname>
                            <given-names>J</given-names>
                        </name>
               </person-group>:
                    <article-title>Smart Factory Systems.</article-title>
                    <source>

                        <italic toggle="yes">Informatik Spektrum.</italic>
               </source>
               <year>2015</year>;<volume>38</volume>(<issue>3</issue>):<fpage>230</fpage>&#x2013;<lpage>235</lpage>.
                    <pub-id pub-id-type="doi">10.1007/s00287-015-0891-z</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-30">
                <label>30</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Stark</surname>
                            <given-names>R</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kind</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Neumeyer</surname>
                            <given-names>S</given-names>
                        </name>
               </person-group>:
                    <article-title>Innovations in digital modelling for next generation manufacturing system design.</article-title>
                    <source>

                        <italic toggle="yes">CIRP Annals.</italic>
               </source>
               <year>2017</year>;<volume>66</volume>(<issue>1</issue>):<fpage>169</fpage>&#x2013;<lpage>172</lpage>.
                    <pub-id pub-id-type="doi">10.1016/j.cirp.2017.04.045</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-31">
                <label>31</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Sisinni</surname>
                            <given-names>E</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Saifullah</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Han</surname>
                            <given-names>S</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Industrial internet of things: Challenges, opportunities, and directions.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Trans Industr Inform.</italic>
               </source>
               <year>2018</year>;<volume>14</volume>(<issue>11</issue>):<fpage>4724</fpage>&#x2013;<lpage>4734</lpage>.
                    <pub-id pub-id-type="doi">10.1109/TII.2018.2852491</pub-id>
            </mixed-citation>
            </ref>
            <ref id="ref-32">
                <label>32</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Lalanda</surname>
                            <given-names>P</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Morand</surname>
                            <given-names>D</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Chollet</surname>
                            <given-names>S</given-names>
                        </name>
               </person-group>:
                    <article-title>Autonomic mediation middleware for smart manufacturing.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Internet Comput.</italic>
               </source>
               <year>2017</year>;<volume>21</volume>(<issue>1</issue>):<fpage>32</fpage>&#x2013;<lpage>39</lpage>.
                    <pub-id pub-id-type="doi">10.1109/MIC.2017.18</pub-id>
            </mixed-citation>
            </ref>
            <ref id="ref-33">
                <label>33</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Boothroyd</surname>
                            <given-names>G</given-names>
                        </name>
               </person-group>:
                    <article-title>Product design for manufacture and assembly.</article-title>
                    <source>

                        <italic toggle="yes">Comput Aided Des.</italic>
               </source>
               <year>1994</year>;<volume>26</volume>(<issue>7</issue>):<fpage>505</fpage>&#x2013;<lpage>520</lpage>.
                    <pub-id pub-id-type="doi">10.1016/0010-4485(94)90082-5</pub-id>
            </mixed-citation>
            </ref>
            <ref id="ref-34">
                <label>34</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Boothroyd</surname>
                            <given-names>G</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Alting</surname>
                            <given-names>L</given-names>
                        </name>
               </person-group>:
                    <article-title>Design for assembly and disassembly.</article-title>
                    <source>

                        <italic toggle="yes">CIRP Annals.</italic>
               </source>
               <year>1992</year>;<volume>41</volume>(<issue>2</issue>):<fpage>625</fpage>&#x2013;<lpage>636</lpage>.
                    <pub-id pub-id-type="doi">10.1016/S0007-8506(07)63249-1</pub-id>
            </mixed-citation>
            </ref>
            <ref id="ref-35">
                <label>35</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zhu</surname>
                            <given-names>X</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hu</surname>
                            <given-names>SJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Koren</surname>
                            <given-names>Y</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Modeling of manufacturing complexity in mixed-model assembly lines.</article-title>
                    <source>

                        <italic toggle="yes">J Manuf Sci Eng.</italic>
               </source>
               <year>2008</year>;<volume>130</volume>(<issue>5</issue>):<fpage>051013</fpage>.
                    <pub-id pub-id-type="doi">10.1115/1.2953076</pub-id>
            </mixed-citation>
            </ref>
            <ref id="ref-36">
                <label>36</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Suh</surname>
                            <given-names>NP</given-names>
                        </name>
               </person-group>:
                    <article-title>Axiomatic design of mechanical systems.</article-title>
                    <source>

                        <italic toggle="yes">J Vib Acoust.</italic>
               </source>
               <year>1995</year>;<volume>117</volume>(<issue>B</issue>):<fpage>2</fpage>&#x2013;<lpage>10</lpage>.
                    <pub-id pub-id-type="doi">10.1115/1.2838673</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-37">
                <label>37</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Raymer</surname>
                            <given-names>D</given-names>
                        </name>
               </person-group>:
                    <article-title>Aircraft design: a conceptual approach.</article-title>American Institute of Aeronautics and Astronautics, Inc,<year>2018</year>.
                    <pub-id pub-id-type="doi">10.2514/4.104909</pub-id>
            </mixed-citation>
            </ref>
            <ref id="ref-38">
                <label>38</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hobday</surname>
                            <given-names>M</given-names>
                        </name>
               </person-group>:
                    <article-title>Product complexity, innovation and industrial organisation.</article-title>
                    <source>

                        <italic toggle="yes">Res Policy.</italic>
               </source>
               <year>1998</year>;<volume>26</volume>(<issue>6</issue>):<fpage>689</fpage>&#x2013;<lpage>710</lpage>.
                    <pub-id pub-id-type="doi">10.1016/S0048-7333(97)00044-9</pub-id>
            </mixed-citation>
            </ref>
            <ref id="ref-39">
                <label>39</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Karanikas</surname>
                            <given-names>N</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Melis</surname>
                            <given-names>DJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kourousis</surname>
                            <given-names>KI</given-names>
                        </name>
               </person-group>:
                    <article-title>The balance between safety and productivity and its relationship with human factors and safety awareness and communication in aircraft manufacturing.</article-title>
                    <source>

                        <italic toggle="yes"> Saf Health Work.</italic>
               </source>
               <year>2018</year>;<volume>9</volume>(<issue>3</issue>):<fpage>257</fpage>&#x2013;<lpage>264</lpage>.
                    <pub-id pub-id-type="pmid">30370157</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.shaw.2017.09.001</pub-id>
                    <pub-id pub-id-type="pmcid">6130003</pub-id>
            </mixed-citation>
            </ref>
            <ref id="ref-40">
                <label>40</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>King</surname>
                            <given-names>WE</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Anderson</surname>
                            <given-names>AT</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Ferencz</surname>
                            <given-names>RM</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Laser powder bed fusion additive manufacturing of metals; physics, computational, and materials challenges.</article-title>
                    <source>

                        <italic toggle="yes">Appl Phys Rev.</italic>
               </source>
               <year>2015</year>;<volume>2</volume>(<issue>4</issue>):<fpage>041304</fpage>.
                    <pub-id pub-id-type="doi">10.1063/1.4937809</pub-id>
            </mixed-citation>
            </ref>
            <ref id="ref-41">
                <label>41</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Westburg</surname>
                            <given-names>PW</given-names>
                        </name>
               </person-group>:
                    <article-title>U.S. Patent No. 3,013,748.</article-title>Washington, DC: U.S. Patent and Trademark Office.<fpage>1961</fpage>.</mixed-citation>
            </ref>
            <ref id="ref-42">
                <label>42</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Napolitano</surname>
                            <given-names>MR</given-names>
                        </name>
               </person-group>:
                    <article-title>Aircraft dynamics : from modeling to simulation.</article-title>Wiley.<fpage>2012</fpage>.
                    <ext-link ext-link-type="uri" xlink:href="https://www.twirpx.com/file/1648588/">Reference Source</ext-link>
            </mixed-citation>
            </ref>
            <ref id="ref-43">
                <label>43</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Fuller</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Fan</surname>
                            <given-names>Z</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Day</surname>
                            <given-names>C</given-names>
                        </name>

                        <etal/>
               </person-group>:
                    <article-title>Digital twin: Enabling technologies, challenges and open research.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Access.</italic>
               </source>
               <year>2020</year>;<volume>8</volume>:<fpage>108952</fpage>&#x2013;<lpage>108971</lpage>.
                    <pub-id pub-id-type="doi">10.1109/ACCESS.2020.2998358</pub-id>
            </mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report26837">
        <front-stub>
            <article-id pub-id-type="doi">10.21956/digitaltwin.18764.r26837</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Zhong</surname>
                        <given-names>Ray Y</given-names>
                    </name>
                    <xref ref-type="aff" rid="r26837a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-3011-2009</uri>
                </contrib>
                <aff id="r26837a1">
                    <label>1</label>Department of Industrial and Manufacturing Systems Engineering, The University of Hong Kong, Hong Kong, Hong Kong</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>18</day>
                <month>11</month>
            <year>2021</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2021 Zhong RY</copyright-statement>
                <copyright-year>2021</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport26837"
                          related-article-type="peer-reviewed-article"
                          xlink:href="10.12688/digitaltwin.17489.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This paper presents a digital twin-driven complexity management in intelligent manufacturing using a framework which covers three services. Some comments are given as follows:</p>
            <p> </p>
            <p> 1. What are the research questions addressed in this paper? Authors should highlight that in the introduction section.</p>
            <p> </p>
            <p> 2. Tables and figures have heterogenous font sizes and style. Please make them consistent.</p>
            <p> </p>
            <p> 3. Authors present the entropy theory to measure the system. How could it be linked to the complexity with an intelligent manufacturing system?</p>
            <p> </p>
            <p> 4. Some symbols are not clearly defined such as M(q) in Equ (2). Is this equation from the authors?&#x00a0;</p>
            <p> </p>
            <p> 5. Comparing with traditional complexity management, what are the key features/advantages by using DT? How to reflect that in the measurement model?</p>
            <p> </p>
            <p> 6. How is the previous entropy measurement approach used in the use case with quantitative analysis?</p>
            <p>Is the rationale for developing the new method (or application) clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the method technically sound?</p>
            <p>Yes</p>
            <p>Are the conclusions about the method and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>If any results are presented, are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Yes</p>
            <p>Are sufficient details provided to allow replication of the method development and its use by others?</p>
            <p>Yes</p>
            <p>Reviewer Expertise:</p>
            <p>Intelligent Manufacturing Systems, Data-driven decision-making</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report26838">
        <front-stub>
            <article-id pub-id-type="doi">10.21956/digitaltwin.18764.r26838</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Rauch</surname>
                        <given-names>Erwin</given-names>
                    </name>
                    <xref ref-type="aff" rid="r26838a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r26838a1">
                    <label>1</label>Faculty of Science and Technology, Industrial Engineering and Automation (IEA), Free University Bozen-Bolzano, Bolzano, Italy</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>15</day>
                <month>11</month>
            <year>2021</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2021 Rauch E</copyright-statement>
                <copyright-year>2021</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport26838"
                          related-article-type="peer-reviewed-article"
                          xlink:href="10.12688/digitaltwin.17489.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This manuscript shows a framework for digital twins focusing on complexity management where digital twins facilitate real-time monitoring, data exploitation and prediction as well as human-machine interaction.</p>
            <p> </p>
            <p> The paper gives a good overview on the linkage of complexity management and digital twins. The theory is well explained and the framework indicated in figure 4 is helpful for researchers as well as practitioners working in the field of DT. The application example in the second part of the paper is well described and very detailed. The paper in overall reads very well and also after critical review I have no critical comments or suggestions for the authors.</p>
            <p> </p>
            <p> My compliments for this work. I would suggest to index the paper as it is.</p>
            <p>Is the rationale for developing the new method (or application) clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the method technically sound?</p>
            <p>Yes</p>
            <p>Are the conclusions about the method and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>If any results are presented, are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Yes</p>
            <p>Are sufficient details provided to allow replication of the method development and its use by others?</p>
            <p>Yes</p>
            <p>Reviewer Expertise:</p>
            <p>Industry 4.0, Smart Manufacturing</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.</p>
        </body>
    </sub-article>
</article>