<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Comparing Ontological Alternatives to Model Engineering Systems and Components</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Francesco</forename><surname>Compagno</surname></persName>
							<email>francesco.compagno@loa.istc.cnr.it</email>
							<affiliation key="aff0">
								<orgName type="department">ISTC-CNR Laboratory for Applied Ontology</orgName>
								<address>
									<addrLine>via alla cascata 56/C</addrLine>
									<postCode>38123</postCode>
									<settlement>Povo</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Adige S.P.A</orgName>
								<address>
									<addrLine>via per Barco, 11, Levico Terme</addrLine>
									<postCode>38056</postCode>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Stefano</forename><surname>Borgo</surname></persName>
							<email>stefano.borgo@cnr.it</email>
							<affiliation key="aff0">
								<orgName type="department">ISTC-CNR Laboratory for Applied Ontology</orgName>
								<address>
									<addrLine>via alla cascata 56/C</addrLine>
									<postCode>38123</postCode>
									<settlement>Povo</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Claudio</forename><surname>Masolo</surname></persName>
							<email>claudio.masolo@cnr.it</email>
							<affiliation key="aff0">
								<orgName type="department">ISTC-CNR Laboratory for Applied Ontology</orgName>
								<address>
									<addrLine>via alla cascata 56/C</addrLine>
									<postCode>38123</postCode>
									<settlement>Povo</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Emilio</forename><forename type="middle">M</forename><surname>Sanfilippo</surname></persName>
							<email>emilio.sanfilippo@cnr.it</email>
							<affiliation key="aff0">
								<orgName type="department">ISTC-CNR Laboratory for Applied Ontology</orgName>
								<address>
									<addrLine>via alla cascata 56/C</addrLine>
									<postCode>38123</postCode>
									<settlement>Povo</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Comparing Ontological Alternatives to Model Engineering Systems and Components</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">7A0DFBA58BF5FDC80B66C4B014A684BB</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T12:10+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Engineering systems</term>
					<term>Maintenance</term>
					<term>Assembly modeling</term>
					<term>Engineering design</term>
					<term>Ontology</term>
					<term>3D</term>
					<term>4D</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>In this paper, we study from an ontological viewpoint some modeling challenges related to the design, realization, and maintenance of engineering systems such as what it means that an assembly complies to a specification and how it persists through time when some of its components are missing or replaced. These challenges intertwine with the missing component and the replacement problems, which are by themselves fundamental from an engineering stance and are thus explicitly addressed in the paper. We describe these topics and for each one we compare different modeling approaches dealing with them, considering also the differences between the three-and four-dimensionalist views. In conclusion, we summarize the comparison of the approaches by highlighting their advantages and shortcomings from an engineering perspective.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>This paper continues a line of research started in <ref type="bibr" target="#b0">[1]</ref>. The goal is to systematically assess a number of ontological models which focus on the same engineering scenario. This goal is achieved by formalizing the given scenario according to different ontological viewpoints, and by technically comparing the obtained formalizations. In this way, one acquires information on the formal and conceptual consequences of adopting an ontological perspective as well as on the technical aspects in which these perspectives differ. Beside highlighting advantages and disadvantages of each ontological model, this analysis can help knowledge engineers and practitioners to choose the (foundational, top-level) ontology most suited to their interest and purposes.</p><p>More specifically, our research line concentrates on the design, realization, and maintenance of engineering systems, intended here as mereologically compound devices, i.e., assemblies of inter-related components. The paper considers only general modeling approaches which are wellknown and widely used in ontology research. This allows us to make general assessments which hold in general and shed light on commonalities across models that adopt the same ontological perspective. Even though the analysis we present remains general for the given purposes, our work is driven by real industrial scenarios that we analyze in collaboration with Adige S.P.A (of the BLM Group<ref type="foot" target="#foot_0">1</ref> ), a company specialized in the manufacturing of laser cutting machines.</p><p>Our analysis applies to systems which are characterized by a specification. Such specification is the result of a design process and identifies a set of conditions that the system must satisfy.</p><p>A first challenge concerns the formal representation of these specifications and, related to it, the clarification of what it means that a system must satisfy the conditions to be compliant with the specification. A second challenge concerns the manner in which systems persist through time. In industrial scenarios, there may be periods of time in which a system is not operative, e.g., because it undergoes maintenance operations, which could have been scheduled earlier or due to unexpected malfunctioning of some of its components. Maintenance can also end up with the replacement of some components. Therefore, the modeler has to state whether during these periods of maintenance the physical system still complies (perhaps in a weaker way) with its specification, and to which kinds of components replacements it can survive. From an ontological perspective, this aspect is intimately related to the spatio-temporal nature of systems that one adopts. For instance, the standard ISO 15926 <ref type="bibr" target="#b1">[2]</ref> embraces a four-dimensionalism (4D) view. According to this view, systems persist through time by accumulating temporal parts. In a three-dimensionalism (3D) view, one assumes that systems persist by being wholly present at each time in which they exist. The 4D and 3D views are basic ontological distinctions that have practical consequences on the models one obtain. We will analyze how these differences impact the representation of systems' compliance through time.</p><p>Starting from this general stand, we will pay particular attention to two more specific problems in engineering modeling considered in the literature, e.g. <ref type="bibr" target="#b2">[3,</ref><ref type="bibr" target="#b3">4,</ref><ref type="bibr" target="#b4">5]</ref>. The first problem, i.e., the replacement problem, concerns components replacement. In experts' terms, it is common to claim that a system's component can be replaced n-times, as if a component were something that could be entirely substituted while keeping its identity. Understanding what components are in this view becomes therefore crucial to make sense of experts' talks. The second problem, called missing component problem, concerns reference to systems or components when they are not physically present or even realized. This can happen at design time, e.g., when experts talk about the machine that they are designing claiming that, e.g., it has given dimensions (within certain tolerances). A similar situation occurs during maintenance tasks, when components are removed from their hosting systems, e.g., to be controlled, cleaned or repaired. During these periods, or when a component has never been installed like in a system under construction, experts may address the component as if it were present in its position; e.g., they may assemble the system while referring to how the missing component should be connected to other systems' parts. Again, we wonder how to make sense of experts' talks from an ontological perspective; e.g., whether it is necessary to introduce a class for engineering items which exist without being physically present. Of course, one can always take a revisionist approach, i.e., claiming that engineers' expressions, when taken ontologically, should be opportunely rephrased.Yet, before considering this option, one should take engineers' talk at face value since this is the information actually exchanged and needed in engineering.</p><p>The paper is structured as follows. Section 2 introduces the notation and key notions that we use in the formal discussion like feature, component, and specification. Section 3 presents alternative ways to formalize engineering notions and their usage in particular from the 3D vs. 4D ontological viewpoints. Section 4 draws some conclusions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">System's Specifications</head><p>We introduce in this section the general view and notation that we will use in section 3 to discuss systems from different ontological perspectives.</p><p>By engineering systems we mean engineering assemblies, i.e., physical objects based on an explicit design and composed of several interrelated components. To exemplify the presentation, we represent the structure of systems-types as (connected) graphs like the one depicted in Fig. <ref type="figure" target="#fig_0">1</ref>. Each node represents a systems' component characterized in terms of (complex) features, labeled Fi. A feature Fi is a Boolean combination of (non-relational) properties that may include types (e.g., pump, hole) and/or properties describing shape, size, color, etc. <ref type="foot" target="#foot_1">2</ref> For instance, we could have that feature F1 characterizes physical objects with weigh 2kg ± 0.1kg, made of metal or plastic but not wood, with a rectangular slot, etc. Usually, a feature does not identify a unique object; this is necessarily true when the feature is associated with a replaceable component. Arcs between nodes denote relations, labeled Ri, holding between the corresponding components. <ref type="foot" target="#foot_2">3</ref>For simplicity, we consider only binary relations, however, the framework is general and applies to n-ary relations as well. Thus, Fig. <ref type="figure" target="#fig_0">1</ref> shows a specification of systems with three components (one for each node) characterized by features F1, F2 and F3, respectively, and satisfying relations R1 and R2 as shown. To avoid ambiguities, engineers tend to use tags to securely identify each component in a system. These tags are useful for maintenance purposes, e.g., to exactly identify the component upon which a technician needs to operate. Fig. <ref type="figure">2</ref> shows a graph similar to the one in Fig. <ref type="figure" target="#fig_0">1</ref> but now enriched with tags C1, C2, and C3. The tags are assumed to be unique identifiers of components in the system. Note that in some graphs components' features cannot explicitly play an identification role. To see this, consider the diagram in Fig. <ref type="figure" target="#fig_1">3</ref>. Here, the components C2 and C4 are characterized by the same feature and are distinguished only because the relation R3 is asymmetric.</p><formula xml:id="formula_0">F1 R1 → → F2 R2 → → F3</formula><p>The components Ci (like the features F i ) could be recursively specified and further decomposed. For simplicity, however, we will work with Ci components that do not have proper parts. It follows that the components of a system do not have common parts, i.e., they are mutually disjoint.</p><formula xml:id="formula_1">[C1] F1 R1 → → [C2] F2 R2 → → [C3] F3 Figure 2:</formula><p>The graph specification in Fig. <ref type="figure" target="#fig_0">1</ref> with tags C1, C2, C3. Also, we will refer in the following sections to the example in Fig. <ref type="figure" target="#fig_1">3</ref>, although the analysis applies to arbitrary graphs of components/features and relations between them.</p><formula xml:id="formula_2">[C2] F2 R2 → → R3 ↓ ↓ [C1] F1 R1 → → [C3] F3 [C4] F2 → → R1 R2 → →</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Modeling Options for Engineering</head><p>The purpose of this section is to make explicit the underlying assumptions that different ontological approaches require to model the problems raised in the introduction.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">3D vs. 4D Approaches</head><p>The way the 3D and the 4D approaches understand and model systems is definitely different. The difference is evident when we look at how systems and components relate to time. Let us represent the existence of objects in time with the primitive EX t x standing for "at time t, the object x is present". <ref type="foot" target="#foot_3">4</ref> We focus here only on objects that exist at some time, i.e., we assume formula (f1) stating that for every object x there exists a time t at which it exists. <ref type="foot" target="#foot_4">5</ref>f1 ∃t(EX t x)</p><p>According to 3D, objects persist in time by enduring, i.e., by being wholly present at every time at which they exist. To account for change, 3D qualifies properties and relations on objects with respect to time. For parthood we introduce x ≤ t y ("at time t, the object x is part of the object y") characterized by (f2)-(f5), where the overlap relation ≬ is defined in (d1) and holds between two objects at the times at which they have a common part. At time t, two objects coincide if, at t, they have the same parts (d2). <ref type="foot" target="#foot_5">6</ref> Parthood simpliciter can be defined as in (d3) which allows the introduction of the mereological sum of a plurality of objects-we write x 1 + . . . + x n for the mereological sum of n objects-and the sum (called fusion) of all the objects satisfying some property (in the language)-we write σ x(φ (x)) for the fusion of the objects satisfying property φ .</p><p>A mereological system is called closed when it assumes the existence (and uniqueness) of the sum of any (finite) plurality of objects and of any fusion based on properties in the language <ref type="bibr" target="#b6">[7]</ref>.</p><formula xml:id="formula_3">d1 x ≬ t y ≜ ∃z(z ≤ t x ∧ z ≤ t y) d2 x ≡ t y ≜ ∀z(z ≤ t x ↔ z ≤ t y) d3 x ≤ y ≜ ∀t(EX t x → x ≤ t y) f2 x ≤ t y → EX t x ∧ EX t y f3 EX t x → x ≤ t x f4 x ≤ t y ∧ y ≤ t z → x ≤ t z f5 EX t x ∧ EX t y ∧ ¬x ≤ t y → ∃z(z ≤ t x ∧ ¬z ≬ t y)</formula><p>Regarding 4D within the engineering literature, we refer to West's work <ref type="bibr" target="#b2">[3]</ref>, 7 which follows closely the standard ISO 15926 <ref type="bibr" target="#b1">[2]</ref>. More generally, 4D is the thesis for which objects consist of both spatial and temporal parts, i.e., they persist in time as they extend in space. This hypothesis allows 4D models to take a classical (atemporal) extensional mereology axiomatized as in (f6)-(f10) with overlap defined as in (d4). According to Sider <ref type="bibr" target="#b8">[9]</ref>, 4D can be characterized by introducing the notion of temporal part (temporal slice) as in (d5)-here TP t xy stands for "at time t, the object x is a temporal part of the object y"-and by assuming that at every time at which an object exists it has a temporal part, as stated in (f11). From (f1) and (f6)-(f11) it is possible to prove that the temporal part of an object at a given time is unique. To simplify the notation, when x exists at t, we write x @t to indicate the unique object y such that TP t yx. In this view, objects consist of the mereological sum of their temporal parts. For instance, if x exists only at t and t ¯, it has two different temporal parts at those times, i.e., respectively, x @t and x @t ¯, and x itself is equal to their sum: x = x @t + x @t ¯.</p><p>4D allows for the definition of temporary parthood as in (d6), i.e., x @t ≤ y @t . This strategy can be replicated for all temporally qualified predicates, i.e., R t x 1 . . . x n reduces to Rx 1@t . . . x n@t . Furthermore, the temporal coincidence x ≡ t y reduces to identity of the corresponding temporal parts, i.e., x @t = y @t .</p><p>Notice that, starting from (f1) and (f6)-(f11), all the axioms considered for the temporally qualified parthood can be proven. The vice versa does not hold: 3D does not commit to temporal parts. In this sense 4D makes a heavier ontological commitment with respect to 3D (see <ref type="bibr" target="#b9">[10]</ref>).</p><formula xml:id="formula_4">d4 x ≬ y ≜ ∃z(z ≤ x ∧ z ≤ y) d5 TP t xy ≜ EX t x ∧ EX t y ∧ ¬∃t ¯(EX t ¯x ∧ t ̸ = t ¯) ∧ x ≤ y ∧ ∀z(z ≤ y ∧ EX t z → z ≬ x) d6 x ≤ t y ≜ ∃uv(TP t ux ∧ TP t vy ∧ u ≤ v) f6 x ≤ y ∧ EX t x → EX t y f7 x ≤ x f8 x ≤ y ∧ y ≤ x → x = y f9 x ≤ y ∧ y ≤ z → x ≤ z f10 ¬x ≤ y → ∃z(z ≤ x ∧ ¬(z ≬ y))</formula><p>f11 EX t x → ∃y(TP t yx)</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Specification and Compliance</head><p>We now consider how to logically represent the graph specifications introduced in Sect. 2 and the compliance of individual systems with them.</p><p>A common approach consists in embracing 3D and seeing the specifications as (complex) relations represented in first-order logic (FOL) via predicates. Let us assume that Fig. <ref type="figure" target="#fig_1">3</ref> depicts the specification of a target system-type K. To state that four specific components, say x, y, z and v, at a certain time t, satisfy the constraints in the specification we can use a single complex relation S, see (f12). <ref type="foot" target="#foot_6">8</ref> The component types can be characterized by introducing a specific S-relational role; see, e.g., (f13) for C1. Following standard practice, one can introduce necessary and sufficient conditions for being a K (at a given time) as in (f14) where K t x is read as "at time t, the physical object x is an instance of the type K". Since we adopted a closed mereology, (f13) and (f14) guarantee that an entity x is a C1-instance only if there exists a K-system which has x among its components, i.e., a C1-component implies the existence of a K-system. In other words, C1-components are existentially dependent on K-systems.</p><p>Introducing formula (f13) for C2-C4, too, one can trivially prove (f15), i.e., K-systems are the mereological sums of the Ci-components considered in the specification. However the converse of (f15) does not hold in general. For instance, assume that C1 t a holds for S t ab ¯cd only, while C1 t b holds for S t a ¯bcd only (with a ̸ = a ¯and b ̸ = b ¯), then there is no suitable 4-tuple satisfying S t to infer the converse of (f15).</p><formula xml:id="formula_5">f12 S t xyzv ↔ F1 t x ∧ F2 t y ∧ F3 t z ∧ F2 t v ∧ R1 t xy ∧ R1 t xv ∧ R2 t yz ∧ R2 t vz ∧ R3 t yv ∧ ¬(x ≬ t y) ∧ ¬(x ≬ t z) ∧ ¬(x ≬ t v) ∧ ¬(y ≬ t z) ∧ ¬(y ≬ t v) ∧ ¬(z ≬ t v) f13 C1 t x ↔ ∃bcd(S t xbcd) f14 K t x ↔ ∃abcd(S t abcd ∧ x ≡ t a + b + c + d) f15 K t x → ∃abcd(C1 t a ∧ C2 t b ∧ C3 t c ∧ C4 t d ∧ x ≡ t a + b + c + d)</formula><p>In a 4D setting, the previous formulas can be rewritten with atemporal predicates following what done for parthood in (d6); e.g., (f14) can be rewritten as in (f16). Given this observation, we will consider in the remaining of the paper only temporally qualified predicates and discuss 4D only for some specific problems mainly concerning components (e.g., in Sect. 3.3). f16 K t x ↔ ∃abcd(Sa @t b @t c @t d @t ∧ x @t = (a+b+c+d) @t )</p><p>Another approach in conceptual modeling <ref type="bibr" target="#b10">[11]</ref>, even though less common than the ones just presented, considers specifications as complex relations represented by individual constants. In this view, the predicate S t xyzu is replaced by xyzu :: t s where s represents the complex relation S and :: is a sort of instantiation relation: here xyzu :: t s stands for "at time t, objects x, y, z, u satisfy the relation S". For simplicity, the different instantiation primitives corresponding to the arities of predicates are noted in the same way. We can then follow the previous discussion by observing that the formulas (f12), (f13), (f14), and (f15) can be easily rewritten in this new framework; e.g., (f14) now becomes (f17). We will explicitly consider this option only in Sect.3.4 to manage the problem of the missing component. In this approach the main difficulty consists in characterizing the instantiation relation. However, the introduction of system-types in the domain of quantification allows taking into account their intensional and intentional dimensions. Different types could have the same instances and type differences may be grounded on contextual information; e.g., a design feature (or the entire specification), since designed by a company, may have copyright, etc.</p><p>A further interesting point of this approach concerns the possibility to align the mereological structure of a system-type with that of its instances. For instance, since K-systems have four components, individuated by the Ci-tags, so the type K is composed by four components-types, i.e., k = c1 + c2 + c3 + c4. Thus, K can be seen as a structural property composed by the Ci-properties. The fact that the Ci-properties uniquely identify components rules out the cases where the same property is part of the structural one several time as, for instance, H in H 2 O (see <ref type="bibr" target="#b11">[12]</ref> for the debate on structural universals). The mereological alignment is partially guaranteed by the rewriting of (f13)-(f15).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3.">The Components of a Given System and the Replacement Problem</head><p>The notion of component in (f13) can be relativized to a system s as in (f18). Note that now (f19) holds. The left to right arrow is trivial. To see that the opposite direction holds, assume C1 t ax. By (f18) there exist b, c, d such that S t abcd and x ≡ t a + b + c + d that, by (f14), imply K t x.</p><formula xml:id="formula_6">f18 C1 t xs ↔ ∃bcd(S t xbcd ∧ s ≡ t x + b + c + d) f19 K t x ↔ ∃abcd(C1 t ax ∧ C2 t bx ∧ C3 t cx ∧ C4 t dx)</formula><p>In the context of a specific system, each tag Ci should have an identification role, i.e., the relational constraints in the specification S should grant the fact that all the Cis are unambiguous identifiers of the specific components composing the system, so that, e.g., (f20) would hold for C1. For instance, in Fig. <ref type="figure" target="#fig_1">3</ref>, C2-components can be distinguished from C4-components only when the relation R3 is asymmetric. <ref type="foot" target="#foot_7">9</ref> A specification S should indeed ensure (f21) from which (f20) follows. Similarly for the other Cis.</p><formula xml:id="formula_7">f20 C1 t xs ∧ C1 t ys → x = y f21 S t xbcd ∧ S t ybcd → x = y</formula><p>Concerning the replacement problem, the replacement of the C1-component for system s can be represented by formula C1 t 0 xs ∧ C1 t 1 ys ∧ C1 t 2 zs ∧ x ̸ = y ̸ = z, which shows a case where the role of 'being the C1-component of s' is played, at different times, by three different objects.</p><p>According to 4D, there exists three temporal slices: x @t 0 , y @t 1 , and z @t 2 . One can then consider the mereological sum of all the C1-slices of s, see (f22), as the referent of the expression 'the Ci-component of s'. As claimed by West <ref type="bibr" target="#b2">[3]</ref>, systems' components are existentially dependent on the whole system and they are non-ordinary objects since they are submitted to discontinuous changes, i.e., the installed component can be (instantaneously) replaced by a new one.</p><formula xml:id="formula_8">f22 C1xs ↔ x = σ y(∃tz(y = z @t ∧ y ≤ s ∧ C1y))</formula><p>Vice versa, in a 3D-framework, to have, for a given system s, a single Ci-component and, at the same time, allowing its replacement, one needs to add a type of individuals in the domain of quantification. Call these new individuals stable components or simply s-components. Stable components abstract from the actual objects installed in the system during its lifetime. Intuitively they are essentially characterized in terms of the patterns of features and relations considered in the specification (see (f18) for C1). This move is similar to the classical one where the statue is distinguished from the clay, see <ref type="bibr" target="#b12">[13]</ref>. To characterize s-components, (f20) is strengthened as in (f23), i.e., the unicity is now guaranteed also diachronically. To state that at every time at which a K-system exists it always has the same four s-components, we can rewrite (f19) as in (f24). Note that in (f23) and (f24) the first argument of the Ci predicates is now an s-component. To account for the replacement process, one could assume that the s-components may change constituents. This requires to introduce a relation x ◁ t y for "at time t, x constitutes y". The identification role of the Cis is preserved by requiring the unicity (at a given time) of the constituent of an s-constitutent (f25). In this approach an s-component c that has been replaced twice will satisfy formula</p><formula xml:id="formula_9">C1 t 0 cs ∧ C1 t 1 cs ∧ C1 t 2 cs ∧ x ◁ t 0 c ∧ y ◁ t 1 c ∧ z ◁ t 2 c ∧ x ̸ = y ̸ = z.</formula><p>Note that according to 4D constitution amounts to coincidence, i.e., x ◁ t y reduces to x ≡ t y which reduces to x @t = y @t .</p><formula xml:id="formula_10">f23 C1 t xs ∧ C1 t ¯ys → x = y f24 ∃t(K t x) → ∃abcd(∀t(K t x ↔ C1 t ax ∧ C2 t bx ∧ C3 t cx ∧ C4 t dx)) f25 x ◁ t c ∧ y ◁ t c → x = y</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.4.">Missing Components and Partial Compliance</head><p>According to the approaches discussed in the previous sections, both systems and components can exist intermittently, i.e., their temporal extension may not be a temporal interval. Yet, when the system exists, all its components must be physically present. Hence, to deal with the missing component problem, i.e., the possibility that some components of a system are not physically realized, one needs to conceive both notions of system and compliance in a more flexible way.</p><p>A way to realize this is to allow for partial compliance, i.e., systems are classified under a type even though they do not fully match the corresponding specification. One can intend partial compliance as a sort of specification-weakening; e.g., for K-systems, in (f13) and (f14), S can be substituted with S ˇwhere S t xyzv → S ˇtxyzv but not vice versa, <ref type="foot" target="#foot_8">10</ref> i.e., some constraints in the specification S are relaxed or ruled out. K-systems and Ci components could then lack some (optional) characteristics indicated in the original specification. Interestingly, one could consider different conditions at different times. For instance, immediately after the completion of the production process, a system could be required to fully comply with the specification, i.e., it must satisfy S. However, through time, one can tolerate the loss of some characteristics of the system, so that it is enough if it satisfies S ˇ, especially when this loss does not compromise its basic functionalities and is not attributable to production defects (e.g., cars can be scratched).</p><formula xml:id="formula_11">[C1] F1 R1 → → [C2] F2 R2 ↓ ↓ [C3] F1 R3 ← ← [C4] F4</formula><p>This approach allows representing optional characteristics of systems but it still requires the presence of all the components. A second way to intend partial compliance is to consider optional components (the two possibilities can clearly be combined). Suppose, for instance that K-systems can lack C4-components, i.e., consider S ¯in (f26) and modify (f14) as in (f27) allowing K-systems to lose or acquire components during their lifecycle. <ref type="foot" target="#foot_9">11</ref> Unfortunately, by adopting (f26), i.e., by tolerating that some components are missing, some Ci-tags could lose their effectiveness because one can have troubles in re-identifying them through time: the second disjuncts in the definitions (f28) and (f29) of, respectively, C2 and C4, are identical.</p><formula xml:id="formula_12">f26 S ¯txyz ↔ F1 t x ∧ F2 t y ∧ F3 t z ∧ R1 t xy ∧ R2 t yz ∧ ¬(x ≬ t y) ∧ ¬(x ≬ t z) ∧ ¬(y ≬ t z) f27 K t x ↔ (∃abcd(S t abcd ∧ x ≡ t a + b + c + d) ∨ ∃abc(S ¯tabc ∧ x ≡ t a + b + c)) f28 C2 t xs ↔ (∃acd(S t axcd ∧ s ≡ t a + x + c + d) ∨ ∃ac(S ¯taxc ∧ s ≡ t a + x + c)) f29 C4 t xs ↔ (∃abc(S t abcx ∧ s ≡ t a + b + c + x) ∨ ∃ac(S ¯taxc ∧ s ≡ t a + x + c))</formula><p>This problem is prevented in the case of systems having one "reference" component c, i.e., all the other components can be identified just by taking into account the relation they have with c. For instance, consider the specification in Fig. <ref type="figure" target="#fig_3">4</ref> where the reference component C4 is characterized only by F4, i.e., it does not have a relational characterization, and where C1 is characterized as in (f30) (similarly for C2 and C3). A typical example of a reference component is a frame: the "position" in the frame is enough to identify all the other components. One can then assume that the system can persist the replacement and/or the loss of all the components except the frame. By relaxing (f30) as in (f31) one could take into account some cases of C1-components that are malfunctioning because they lack some features required by the specification.</p><formula xml:id="formula_13">f30 C1 t xs ↔ F1 t x ∧ ∃a(F4 t a ∧ R1 t xa ∧ x + a ≤ t s) f31 C1 t xs ↔ ∃a(F4 t a ∧ R1 t xa ∧ x + a ≤ t s)</formula><p>Let us now consider the interaction between partial compliance and the approach based on s-components previously discussed. A first possibility is to assume that, during its whole lifetime, a system (of a given kind) maintains its essential s-components, but can in principle lose (for localization or its specific temperature to infer additional information concerning the specific system of which the physical frame is a component. Note however, that only the approach based on saturated roles allows having an individual in the domain of quantification that can be used to refer to the component even though it is missing.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Discussion and Conclusion</head><p>As we have seen in the previous section, the identified engineering modeling problems can be tackled from different ontological perspectives. The result of our analysis is that none of these views is clearly more advantageous than the others. Therefore, there is no definite preferable approach. We gained however some insights that can hopefully help knowledge engineers to choose an approach to develop their models on the basis of formal implications along with, for those interested, philosophical principles (e.g., 3D vs 4D).</p><p>To sum up, in all cases we have seen, engineering physical systems are discussed in relationship with design specifications; the match between the two establishes the degree of systems compliance. In particular, design specifications represent the properties (in terms of features Fi and relations Ri) of physical systems. In a standard FOL setting, properties correspond to predicates and FOL predication models the ontological notion of instantiation. This formal mechanism can be tuned to both 3D and 4D views (see Sect. 3.2). In addition, there is the option to reify properties to model them as FOL individual constants (see (f17)). This move, which is coherent with both the 3D and 4D, complicates the formal representation, since new predicates are needed to characterize the new constants (see, e.g., (f14) and (f17)).</p><p>The notion of compliance can be treated in different ways. A physical system is compliant with a specification when it satisfies all properties established by the latter (see, e.g., (f14) for 3D, (f16) for 4D, and (f17) for the reified variant of 3D). However, there are cases where a weaker sense of compliance, which we called partial compliance, is preferable. To capture this notion, one can introduce the distinction between essential and optional systems' properties such that the lack of the latter does not compromise systems' identity (see <ref type="bibr">Sect. 3.4)</ref>.</p><p>For the representation of components' replacement, in West's 4D-framework <ref type="bibr" target="#b2">[3]</ref>, a whole system's component is a 4D worm formed by all temporal slices that at different times have been part of it. In this sense, having a system's component replaced at a certain time implies that, from that time, the whole worm has as part a temporal slice of a different object. This view requires however the specification of some rules, possibly motivated from an engineering perspective, to guarantee the continuity of the 4D worm. Otherwise, it is not clear how (possibly) disconnected temporal slices come to form a unique whole. In a standard 3D approach, we showed how to overcome the identity problem of an object whose components are all replaced by relying on the notion of stable components, namely, objects that -at different times -can change constituents while remaining the same entities (see (f23)-(f25)). Hence, in this perspective, to replace a system's component means to change its constituent.</p><p>Finally, we have seen that engineers talk of systems and their components referring sometimes to specific physical entities and some other times to their conceptual counterparts. In both 3D and 4D approaches, reference to entities that have not been physically realized or are simply absent at some time can be made meaningful by referring to the reification of the tags in the specification standing for possibly empty components, i.e., the things engineers refer to as if they were fully-fledged physical entities. Overall, the approach based on reification makes the modeling framework logically more complex but it allows making sense of engineers talks about the missing component problem.</p><p>Further work is necessary to complete the analysis we presented here. First, other approaches, (e.g., see <ref type="bibr" target="#b0">[1]</ref> for a preliminary proposal based on possible objects), should be explored and added to the comparison. Second, one should assess the identified ontological views in more specific and varied engineering requirements, a larger set of requirements may help to better identify the dis-/advantages of the views in more articulated scenarios.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: A system-type with three components.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: A graph specification where the components C2 and C4 have the same feature F2.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head></head><label></label><figDesc>f17 x :: t k ↔ ∃abcd(abcd :: t s ∧ x ≡ t a + b + c + d)</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: A graph specification with the "reference" component C4.</figDesc></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://www.blmgroup.com/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">Note that we use the term 'feature' in a more general sense in comparison to the engineering literature, where it commonly refers to things such as holes, slots, bumps, etc. described from different viewpoints<ref type="bibr" target="#b5">[6]</ref>.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">Things like wires, pipes, or sets of bolts and nuts can be explicitly taken into account by designers, hence they can be treated as components linked to other components via specific relations. An example of such a relation is the contact between a pin and its socket. Alternatively, designers can (partially) encapsulate them in the Ri-relations.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">We write P t x instead of Pxt to highlight the time-argument t.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">Since it is clear from the language when a variable is quantified over time or over objects, we leave implicit these quantification constraints.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">Neither coincidence at t nor coincidence during the whole lives of objects imply their identity.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_6">We add the non-overalapping conditions for generality. Since by assumption our components do not have proper parts, strictly speaking these constraints are not needed.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="9" xml:id="foot_7">Features themselves may not be enough because often systems have several components of the same type, e.g., the same kind of valve, electric engine or fastener can be present in several places.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="10" xml:id="foot_8">As done for S, we assume that components of S ˇdo not have proper parts.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="11" xml:id="foot_9">Note that we cannot just write K t x ↔ ∃abc(S ¯t abc ∧ a + b + c ≤ t x) otherwise it would be possible to have K-systems with five or more components or with four components that however do not satisfy S.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="12" xml:id="foot_10">As discussed, this could be problematic when the absence of C1-components causes the loss of the individuation role of other components, and could be prevented, e.g., by using a component as "reference".</note>
		</body>
		<back>
			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>some periods) optional s-components. In this case we need to modify (f24) taking into account only essential s-components. Optional components are then, in general, intermittent entities, a view embraced by West in a 4D-setting.</p><p>A second possibility is to allow for "empty" s-components, which we will argue for in the following. When experts talk about components or systems, they seem to refer sometimes to physical individuals and some other times to conceptual or abstract ones. In a sense, components and systems seem to have both a physical and a conceptual dimension, a sort of "dual nature". To capture this duality, one could allow s-components to be "empty", i.e., to lack a physical realization: when an s-component is physically realized, experts refer to this realization while when it is empty, they refer to the s-component itself. Systems would be therefore static with respect to their s-components while optional components would reduce to possibly empty scomponents. However, this notion of s-component does not match the one discussed at the end of Sect. 3.3 where s-components are intended as physical entities that always have a constituent, i.e., given an s-component c, the constitution relation ◁ usually satisfies EX t c → ∃x(x ◁ t c).</p><p>We sketch a possible way to capture this duality where s-components have a conceptual nature. Consider the approach based on the reification of properties discussed in Sect. 3.2 but now consider the reifications of the Ci-properties specialized to a given K-system s: ci s is the reification of Ci s t x ↔ Ci t xs, i.e., x :: t ci s ↔ xs :: t ci (these properties are sort of saturated roles as introduced in <ref type="bibr" target="#b13">[14]</ref>). By assuming that the instances at time t of a concept all exist at t (i.e., x 1 . . . x n :: t c → EX t x 1 ∧ . . . ∧ EX t x n ), then ∃x(x :: t ci s ) → EX t s holds for all the components while the vice versa does not hold for optional components, i.e., one can have empty ci s . Furthermore, when replacement is allowed, x :: t ci s ∧ y :: t ¯ci s → x = y holds in general only when t = t ¯. However, differently from the previous s-components, the ci s are not part of the system s. Our idea is to introduce the conceptual counterpart d s of the system s by defining it as d s = c1 s + c2 s + c3 s + c4 s . By guaranteeing that both EX t s → s :: t d s and x :: t d s → x ≡ t s hold, d s becomes a sort of definite description of s, i.e., it is a concept that individuates a single system. In this way, both the conceptual (via d s and the ci s ) and the physical (via s and, when present, the instances of the ci s ) perspectives on a system can be represented. Note however that, following the discussion about (f28) and (f29) and assuming that some Ci-components are optional for s, this strategy can be pursued only when the definition of the other C j-components (or at least some of them) can be satisfied also when the Ci-components are not present. 12 Otherwise the loss of (some of) the Ci-components would imply the loss of all the other components.</p><p>Let us consider now the problem of the missing component discussed in Sect.1. One can approach the problem at the conceptual level. The specification and the explicit conditions required to (fully or partially) comply with it allow talking about the characteristics of any realization of a system-kind. From the characterization of K-systems (f14) and of their Cicomponents (e.g., (f13)), together with additional (background) knowledge on the world shared by engineers and (if the system is at least partially realized) the information about the physical properties of the actual components, some properties of K-systems and Ci-components can be inferred. For instance, consider again the example of the frame, assuming it is an essential component of the whole system. In this case, we can use the information about its spatial</p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">An overview of some ontological challenges in engineering maintenance</title>
		<author>
			<persName><forename type="first">S</forename><surname>Borgo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Compagno</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Guarino</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Masolo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Sanfilippo</surname></persName>
		</author>
		<ptr target="https://openreview.net/forum?id=CIqto9pUgqm" />
	</analytic>
	<monogr>
		<title level="m">Workshop on Domain Ontologies for Research Data Management in Industry Commons of Materials and Manufacturing (DORIC-MM) at ESWC 2021</title>
				<imprint>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<idno>ISO 15926</idno>
		<title level="m">Industrial automation systems and integration-Integration of life-cycle data for process plants including oil and gas production facilities</title>
				<meeting><address><addrLine>ISO</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
	<note type="report_type">Technical Report</note>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">Developing high quality data models</title>
		<author>
			<persName><forename type="first">M</forename><surname>West</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2011">2011</date>
			<publisher>Elsevier</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Artefactual systems, missing components and replaceability</title>
		<author>
			<persName><forename type="first">N</forename><surname>Guarino</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Artefact Kinds</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2014">2014</date>
			<biblScope unit="page" from="191" to="206" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Candidate worldviews for design theory</title>
		<author>
			<persName><forename type="first">P</forename><surname>Galle</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Design Studies</title>
		<imprint>
			<biblScope unit="volume">29</biblScope>
			<biblScope unit="page" from="267" to="303" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">What are features? an ontology-based review of the literature</title>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">M</forename><surname>Sanfilippo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Borgo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Computer-Aided Design</title>
		<imprint>
			<biblScope unit="volume">80</biblScope>
			<biblScope unit="page" from="9" to="18" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<author>
			<persName><forename type="first">R</forename><surname>Casati</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">C</forename><surname>Varzi</surname></persName>
		</author>
		<title level="m">Parts and places: The structures of spatial representation</title>
				<imprint>
			<publisher>MIT Press</publisher>
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Temporal Parts</title>
		<author>
			<persName><forename type="first">K</forename><surname>Hawley</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Stanford Encyclopedia of Philosophy</title>
				<editor>
			<persName><forename type="first">E</forename><forename type="middle">N</forename><surname>Zalta</surname></persName>
		</editor>
		<meeting><address><addrLine>summer</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2020">2020. 2020</date>
		</imprint>
		<respStmt>
			<orgName>Metaphysics Research Lab, Stanford University</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<author>
			<persName><forename type="first">T</forename><surname>Sider</surname></persName>
		</author>
		<title level="m">Four-dimensionalism: An ontology of persistence and time</title>
				<imprint>
			<publisher>Oxford University Press on Demand</publisher>
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Parthood simpliciter vs. temporary parthood</title>
		<author>
			<persName><forename type="first">C</forename><surname>Masolo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Ninth International Symposium on Logical Formalizations of Commonsense Reasoning (Commonsense</title>
				<meeting>the Ninth International Symposium on Logical Formalizations of Commonsense Reasoning (Commonsense</meeting>
		<imprint>
			<date type="published" when="2009">2009. 2009</date>
			<biblScope unit="page" from="97" to="102" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Design knowledge representation: An ontological perspective</title>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">M</forename><surname>Sanfilippo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Masolo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Porello</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 1st Workshop on Artificial Intelligence and Design (at AI*IA 2015)</title>
		<title level="s">CEUR workshop proceedings</title>
		<meeting>the 1st Workshop on Artificial Intelligence and Design (at AI*IA 2015)</meeting>
		<imprint>
			<date type="published" when="2015">2015</date>
			<biblScope unit="volume">1473</biblScope>
			<biblScope unit="page" from="41" to="54" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Against structural universals</title>
		<author>
			<persName><forename type="first">D</forename><surname>Lewis</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Australasian Journal of Philosophy</title>
		<imprint>
			<biblScope unit="volume">64</biblScope>
			<biblScope unit="page" from="25" to="46" />
			<date type="published" when="1986">1986</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">The statue and the clay</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">J</forename><surname>Thomson</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Nous</title>
		<imprint>
			<biblScope unit="volume">32</biblScope>
			<biblScope unit="page" from="149" to="173" />
			<date type="published" when="1998">1998</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Social roles and their descriptions</title>
		<author>
			<persName><forename type="first">C</forename><surname>Masolo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Vieu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Bottazzi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Catenacci</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Ferrario</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gangemi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Guarino</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Ninth International Conference on the Principles of Knowledge Representation and Reasoning (KR 04)</title>
				<editor>
			<persName><forename type="first">D</forename><surname>Dubois</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">C</forename><surname>Welty</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Williams</surname></persName>
		</editor>
		<meeting>the Ninth International Conference on the Principles of Knowledge Representation and Reasoning (KR 04)<address><addrLine>Whistler Canada</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="267" to="277" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
