ISO 3151-2:2025

International
Standard
ISO 3151-2
First edition
Visualization elements of PLM-MES
2025-04
interface —
Part 2:
3D error feedback in heavy industry
Éléments de visualisation pour l’échange de données entre
systèmes d’information de gestion du cycle de vie de produits
(PLM) et de pilotage de la production (MES) —
Partie 2: Remontée d’informations d’erreur sous forme 3D pour
l’industrie lourde
Reference number
© ISO 2025
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions .1
3.2 Abbreviated terms .3
4 PLM-MES interface . 3
4.1 Needs for a PLM-MES interface in the heavy industry .3
4.2 Generic workflow for 3D error feedback data exchange between PLM and MES .5
4.2.1 General .5
4.2.2 Steps of error feedback data exchange between PLM and MES .6
4.2.3 Visualization of the error feedback data .7
5 Visualization elements for 3D feedback of production errors. 7
5.1 General .7
5.2 Product structure of mBOM .7
5.3 3D shape of the product .7
5.4 LoD (level of detail) .7
5.5 Port data of equipment .9
5.6 3D notes on geometry .9
5.7 Drawing image with markup .10
6 Class definition of PLM-MES interface data model .10
6.1 General .10
6.2 Product information package . .11
6.3 Process information package . 12
6.4 Resource information package . 13
6.5 Feedback information package .14
Annex A (informative) Entity correspondence between ISO 10303-239 and IEC 62264 series .16
Annex B (Informative) Entity mapping between ISO 10303-239 and IEC 62264 series .23
Annex C (informative) Use cases of error feedback .25
Annex D (informative) Pilot implementation of 3D interface for error feedback .34
Bibliography .36

iii
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 4, Industrial data, and Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 24, Computer graphics, image processing and environmental data representation, and
Technical Committee ISO/TC 171, Document management applications, Subcommittee SC 2, Document file
formats, EDMS systems and authenticity of information.
A list of all parts in the ISO 3151 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

iv
Introduction
0.1  General
Although commercial products exist for the product lifecycle management (PLM)-manufacturing execution
[20]
system (MES) interface, there is no official standard for the PLM-MES interface. Separate international
standards exist for PLM and MES, respectively. However, there is no international standard for interfaces for
exchanging 3D product information and manufacturing information between PLM and MES.
Data models from existing PLM and MES standards can be used as starting points to establish the PLM-MES
interface standard. Given the diverse and complex nature of the entire PLM-MES interface, this document
focuses on 3D visualization elements that provide feedback on 3D error data found in the production
department of heavy industry to the design department.
When the PLM-MES interface is visualized, details of the entire interface are hidden, and an intuitively
displayed overall view is presented. The schemas of the existing PLM and MES standards can be used to
standardize the text format feedback sent from the production department to the design department.
However, since the main obstacle is 3D shape data, it is difficult to use the existing schema. The 3D
visualization elements for feedback constitute the first step in developing the PLM-MES interface standard.
Figure 1 shows the contents defined by ISO/TR 3151-1, which outlines the visualization elements of the PLM-
MES interface, and this document (ISO 3151-2), which pertains to this part of the PLM-MES interface. The
left side of Figure 1 shows the scope of ISO/TR 3151-1, primarily an overview, while the right side shows the
scope of this document, specifying 3D visualization elements for error feedback in heavy industry.
Figure 1 — Technology tree of PLM-MES interface
0.2  Simple and short-lifespan products versus complex and long-lifespan heavy industry products

v
Industry-specific product groups can be classified based on their economic lifespan. For example, there are
clear differences in the economic lifespan of a nuclear power plant, an aircraft, a ship, an automobile, a TV, a
smartphone, and mechanical or electronic parts.
An engineering plant, such as a power plant, consist of one million parts and has a service life of several
decades. Being made-to-order (or custom-made), the demand for a 3D interface between PLM and MES in
these specific use cases is generally high. See Annex C for use cases that illustrate the challenges of the 3D
interface between PLM and MES.
On the other hand, less complex products such as motors, electronic components or control components
used for communication or control have relatively shorter lifecycles. These products must be mass-
produced to ensure economy validity and have a short economic life due to rapid technological advancement.
Consequently, the demand for 3D interfaces between PLM and MES is not high. Manufactured products with
a small set of parts are relatively less complex.

vi
International Standard ISO 3151-2:2025(en)
Visualization elements of PLM-MES interface —
Part 2:
3D error feedback in heavy industry
1 Scope
This document specifies a data model of visualization elements for 3D data exchange for error information
feedback between product lifecycle management (PLM) and manufacturing execution system (MES or MOM:
manufacturing operations management) in the engineering plant industry.
The followings are within the scope of this document:
a) data model of visualization elements for the engineering plant industry with complex and long-lifespan
products;
b) definitions of the properties of the data model for the visualization elements of the PLM-MES interface;
c) relationship with the information model of visualization elements as defined in ISO 10303-239;
d) relationship with the information model of the visualization elements as defined in IEC 62264 series;
e) information flow with equipment used in production and related measuring equipment as managed
inside MES.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 20924, Internet of Things (IoT) and digital twin — Vocabulary
3 Terms, definitions and abbreviated terms
For the purposes of this document, the terms and definitions given in ISO/IEC 20924 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1 Terms and definitions
3.1.1
port
located, oriented and directed feature of the product's geometry model (1) for connecting the product with
other ports to transfer media or (2) to fasten the product to other products, accessories, walls, ceilings,
floors, etc. or (3) for executing control
[SOURCE: ISO 16757-2:2016, 3.3]

3.1.2
3D note
text information attached to graphical information of a digital shape model of a product
[SOURCE: ISO/TR 3151-1:2023, 3.1.1, modified — "3D" has been removed at the beginning of the definition.]
3.1.3
level of detail
LoD
alternate representations of an object at varying fidelities based on specific criteria
[SOURCE: ISO/IEC 18023-1:2006, 3.1.8]
3.1.4
interface
set of services and related service mechanisms, available via a logical or physical access point, provided by a
resource (3.1.8), in order to transfer or exchange information, material, energy, and other manufacturing aspects
[SOURCE: ISO 18435-1:2009, 3.11, modified — Note 1 to entry was removed.]
3.1.5
entity
concrete or abstract thing in the domain under consideration
[SOURCE: ISO 8000-2:2022, 3.3.3]
3.1.6
heavy industry
industry that uses large machines to produce large and heavy products, large and heavy equipment and
facilities, large machine tools, huge buildings and large-scale infrastructure
Note 1 to entry: Modified from Oxford Learner's Dictionaries.
3.1.7
social network service
SNS
electronic service designed to allow users to establish a personal or organizational profile and contact other
individuals for the purpose of communicating, collaborating, and/or sharing content with them
[SOURCE: ISO 18461:2016, 2.4.16, modified — Notes 1 and 2 to entry were removed.]
3.1.8
resource
stock or supply of money, materials, staff and other assets that can be drawn upon to achieve a specific
function or outcome
[SOURCE: ISO 24389-1:2023, 3.1.5]
3.1.9
point cloud
collection of 3D points in space referenced by their coordinate values
Note 1 to entry: A point cloud constitutes the raw data from a 3D scanner and needs to be translated to a human
axis system.
[SOURCE: ISO 20685-1:2018, 3.9]

3.2 Abbreviated terms
3D three dimensional
AP application protocol
BOM bill of material
eBOM engineering BOM
ERP enterprise resource planning
HHI Hyundai heavy industries
ID identifier
IEC international electrotechnical commission
ISA international society of automation
ISO international organization for standardization
mBOM manufacturing BOM
MES manufacturing execution system
MOM manufacturing operations management
P&ID piping and instrument diagram
PDA personal digital assistant
PLCS product life cycle support
PLM product lifecycle management
R&D research and development
SHI Samsung heavy industries
STEP standard for the exchange of product model data
xBOM any BOM including eBOM, mBOM
X3DOM X3D document object model
JT format Jupiter tessellation format
4 PLM-MES interface
4.1 Needs for a PLM-MES interface in the heavy industry
In heavy and construction industries, 'custom-made' production (or 'personalized' production) has existed
since the industry's early days, hundreds of years ago. Every product has an individual design, and due to the
pressure to design products quickly, the production cycle begins even when the design is not yet complete.
In the electronics or automotive industries where mass production occurs, production begins after
improving design quality through repetitive design. However, in the ‘custom-made’ industry, repetitive
design is not possible due to design cost issues.

Procedures with partial overlap between design and production phases are widely used in concurrent
engineering. In this context, design and production departments must work closely together and exchange
data to avoid design errors. Since both the design and production departments operate in a 3D environment,
3D data needs to be shared between the two departments.
Even in a mass production industry such as the automotive industry, the need for a PLM-MES interface is
growing as smart manufacturing spreads. The automotive industry is gradually moving from the mass
production toward the mass customization and finally to the personalized production (lot size 1) similar
to the heavy industry or the construction industry. As mass production industries move toward the
personalized production, the needs for a PLM-MES interface between the production department and the
design department are increasing.
Similarly, the PLM-MES interface is needed to compensate for the deviations between R&D (prototype
production) facilities and mass production (volume production) facilities in mass production industries. In
order to minimize deviations or errors between R&D facilities and mass production facilities, a PLM-MES
interface including a 3D interface is needed. As personalized production progresses, it is expected that R&D
(prototype production) facilities and mass production (volume production) facilities will become similar.
Because heavy industries have been engaged in 'custom-made' production since the early days of the
industry, there are many use cases and extensive know-how for 'custom-made' production. On the other
hand, it is still challenging to find good use cases for 'custom-made' production in mass-production
manufacturing industries such as the automotive or electronics industries.
ISO 10303-239 and the IEC 62264 series
ISO 10303-239 (AP239) is an International Standard for PLM that defines an information model for product
design, production processes and resources throughout the entire lifecycle of a product, as shown in
Figure 2.
AP239 is an application protocol (AP) that manages the lifecycle of a product. Therefore, Figure 2 shows the
relationship with other APs of the ISO 10303 series along the time axis of product development. The core of
AP239 is to manage product overview data for the entire period, while other APs handle more detailed areas
at specific points along the time axis.
Figure 2 — Scope of ISO 10303-239 and related standards for PLM[21]

The PLM-MES interface between ERP and MES is standardized in IEC 62264-1, IEC 62264-2 and IEC 62264-5.
The ERP-MES interface defines information models and methods for exchanging ERP and MES data.
IEC 62264-3, IEC 62264-4 and IEC 62264-6 define the functions and properties of the MES (see Figure 3). The
[19]
IEC 62264 series is developed based on ANSI/ISA-95. The entity correspondence between ISO 10303-239
and the IEC 62264 series is presented in Annex A. The entity mapping is described in Annex B.
Reproduced with permission from IEC 62264-1. IEC has no responsibility for the placement and context (in-
cluding other content or accuracy) in which the extracts are reproduced, nor is IEC in any way responsible for
the other content or accuracy therein.
Figure 3 — Manufacturing functional hierarchy of IEC 62264-1
4.2 Generic workflow for 3D error feedback data exchange between PLM and MES
4.2.1 General
3D visualization elements for error feedback of the PLM-MES interface and the overall steps of data exchange
are defined in Figure 4. They are based on analysis of the PLM standards and MES standards, respectively.
These definitions result from use case analysis, as shown in Annex C, regarding the error data feedback
from the production department in three heavy industries.

Figure 4 — Steps of error feedback data exchange between PLM and MES
Figure 4 shows the use case of data exchange between the PLM of the design department and the MES of the
production department. The use cases shown in Annex C have been collected from three shipbuilding and
offshore companies in the Republic of Korea. The numbered business steps in Figure 4 are described below.
4.2.2 Steps of error feedback data exchange between PLM and MES
4.2.2.1 Step 1
The design department uses PLM to transmit information such as 3D configuration data, drawings and
process information to the production department, and the production department uses MES to produce
products.
4.2.2.2 Step 2
The production department feeds back error information such as design error, process change, equipment
change and equipment malfunction found during production planning or manufacturing to the design
department through PLM.
4.2.2.3 Step 3
The design department updates the design data and delivers the updated information back to the production
department. Depending on the type of design change, additional small-scale purchase requests to ERP and
the purchasing department may occur.
4.2.2.4 Step 4
The production department can feed back the operation status data of the production equipment such as
on-site information, indicating the normal operation status of the production equipment, temperature, RPM,
pressure and product status such as deformation to the design department through the PLM-MES interface.

4.2.3 Visualization of the error feedback data
Even in scenarios with advanced technology, the 3D geometric model of the design department is not
usually passed on to the production department. In some cases, a simplified digital model of the computer
aided design (CAD) model is converted into a polygon model and delivered to the production department,
but in many cases, 2D drawing files or printed paper drawings are delivered. Personal digital assistants
(PDAs) (also called tablets) are increasingly being used to visualize 3D models in the form of polygons at
the production site. The delivery channel of the 3D product model often uses a channel separate from the
sequential interface that connects PLM to ERP and then to MES.
When a production-related problem that cannot be controlled within the production department occurs,
the problem should be reported to the design department. The communication channel currently used in
the shipyards of the Republic of Korea involves scanning an image after marking with a pen on a printed
drawing. A message is sent through email or voice communication, and a drawing with a hand-marked
printed on paper is delivered along with the scanned image.
There is a need for a reliable digital channel of feedback information using 3D data rather than 2D images. If
the 3D visualization interface works, both PLM and MES share the same 3D model of the project and can be
modified. The focus of this document is on the 3D visualization of the data model related to step 2 and step
3 in Figure 4.
5 Visualization elements for 3D feedback of production errors
5.1 General
Visualization is a part of the overall PLM-MES interface, and the focus of this document is on the visualization
of 3D models for feedback of errors found in production sites in the heavy industry to the design department.
Many items can be visualized in the PLM-MES interface between PLM and MES. In this document, only major
items are selected as standard items.
It is necessary to standardize the PLM-MES interface. The visualization elements, one of the most important
items among interfaces, are standardized with a new schema. Basic visualization elements existing in
the ISO 10303 series can be reused. The visualization elements of the PLM-MES interface utilize common
resources such as ISO 10303-41, ISO 10303-42, and ISO 10303-46.
Many of the visualization requirements can be satisfied by utilizing the existing visualization elements. A
few items that are not in the existing standards can be newly proposed. For each use case, a data set that
needs to be exchanged is identified, and visualization elements are identified in this data set. A mapping of
these elements between PLM and MES is proposed as shown in Annex A and Annex B.
5.2 Product structure of mBOM
The product structure is a priority item to be shared between PLM and MES, and mBOM is a manufacturing
bill of material (BOM) that can be visualized as a product structure. The product structure is information
that shows the assembly state of the parts constituting the product.
5.3 3D shape of the product
In the existing method (Annex C) or in this document (see 4.2, Figure 3), only text and 2D information
are shared between ERP and MES, so the 3D shape of the product is the core information of the PLM-MES
visualization interface in this document. A standardized 3D direct interface between PLM and MES is needed
to share 3D information of a product between the design department and the production department.
5.4 LoD (level of detail)
Since a heavy industry facility is a huge and complex product, it goes through several stages from design to
production. Each stage has a different LoD in the design, and the LoD gradually increases over time.

The product shown in Table 1 is a valve used in offshore structures. Although it is the same valve, different
types and different levels of detail are used in shipyards during the various stages of design and throughout
the product lifecycle.
[22]
Table 1 — Classification of plant equipment models based on LoD
Level Type Description Example: valve
Symbol-level model
Simple model (3-dimensionalized symbol from P&ID). Model
(basic design stage,
1 in default libraries (known as catalogue model) provided by a
send to manufactur-
PlantCAD system.
er)
Model that plant manufacturer re-models based on ven-
Production model
dor-package (collection of 2D drawings, simplified symbol
2 (Production design
model) of equipment. The product model which is suitable for
stage of plant)
plant manufacturer
Handover model
Model that plant owner or operating company requests. Has
3 (reconstructed model
different LOD depending on the requests.
from scanned data)
Scanned model (dur- A point cloud model from 3D scanning during or after manu-
4 ing or after construc- facturing or construction of the plant. It shows additional ma-
tion) terial such as insulation material surrounding the equipment.
Detail model of vendor for producing the equipment. Contains
Detailed model from all (geometric/non-geometric) information about the product
5 manufacturing (Ven- such as internal geometric information as well as detailed
dor) surface information. Due to security issues, only vendors have
the model.
The level 1 model is a 3D model but has an LoD similar to that of a 2D symbol. P&ID (piping and instrument
diagram) drawings are core and basic drawings in the plant industry. They are similar to electronic circuit
diagrams as they represent the equipment and the pipes connecting the equipment with symbols and lines.
The model is sent to the subcontract manufacturer, and the manufactured equipment will be supplied for
the assembly into the plant.
Level 2 is a production-level equipment model instead of a symbol, which shows the size and location of the
equipment. To assemble an engineering plant like a ship, three-dimensional size and location are important.
However, it is still represented by simplifying the outline of the equipment. If the internal shape of the
equipment is modelled in detail, the file size of the entire plant model becomes too large. If one million pieces
of equipment are combined in the plant, it is difficult to modify or manipulate the whole plant model.
NOTE When explaining the complexity of a design, it is usually explained that a car is made up of 30,000 parts and
an aircraft is made up of 3 million parts.
The level 3 model shows the LoD of the CAD model that is delivered with the plant to the owner-operator
after the plant is complete. In the past, paper drawings were delivered to plant operators, but owner-
operators who are seeking to automate plant operation are requesting more digital information and
demanding models detailed enough to be used as digital twins. The current situation at the shipyard site is
that production work is based on the CAD model shown in level 2, and the revised and supplemented model
is completed as a level 3 model with reference to the scanned point cloud shown in level 4 and delivered to
the owner-operator.
Level 4 is a point cloud model obtained by laser scanning the finished plant. In large construction projects
such as heavy industry and buildings, small differences between design drawings and actual products are
found. The use of scanned point cloud is also becoming common to check the quality of such discrepancies.
However, the point cloud model also has a different appearance depending on the time of the scan.

As another similar example, the appearance of a building varies greatly depending on the construction
stages of the building, and in particular, the appearance varies considerably depending on the progress of
the interior work. Insulation is added to steel pipes in many cases in engineering plants, so it is necessary to
decide whether to scan the appearance with the insulation or the bare steel pipe, which can be checked with
the design drawings. It is possible that the mechanical devices that actually function are not visible because
they are covered by the insulation material.
Level 5 is a CAD model provided by the subcontract manufacturer of individual equipment. The internal
configuration of the equipment is modelled in detail. Since a piece of equipment (a valve in the case of
Table 1) is the equipment manufacturer's final product, its design and components are modelled in detail
and used to manufacture the equipment.
However, a shipbuilder who procures and installs the equipment (valve) is not interested in the internal
configuration of the equipment, but is only interested in information such as the outline of the equipment
and the connection point (to the pipe) for assembly and installation. The shipyard needs a CAD model for
ship production (level 2), not for equipment production. On the other hand, another level (level 3) of digital
assets is required for operators who operate the plant and have to maintain it for long periods of time. The
operator may need the internal configuration of the equipment.
The five different levels of detail in Table 1 show that a single piece of equipment, a valve, is modelled
differently throughout the design and construction lifecycle.
5.5 Port data of equipment
In an engineering plant construction, most of the equipment is either outsourced or purchased, so
shipbuilders and construction companies pay more attention to the correct connection between equipment
and pipelines. A specific portion of equipment that is connected to another device (via pipeline) is called a
“port”. This port information serves as an important reference point for installing and connecting purchased
equipment. Therefore, details of “port” information, including location and orientation data, need to be
shared between PLM and MES.
In general, since MES does not hold or handle 3D information, various problems arise in information
communication at the production site. When manufacturing errors occur, feedback to the design department
is not smooth. To this end, it is helpful to visualize the product in 3D and share data between the design
department and the production department along with port information.
Currently, this function is not provided in MES, so 2D images drawn by hand and pen on drawings are
scanned and delivered to the design department. Due to the current low level of information exchange, there
are problems in work efficiency (errors and delays), so a 3D error feedback visualization element is needed
in the PLM-MES interface.
5.6 3D notes on geometry
When a product problem arises in the design department or in the production department, the problem item
and the information should be shared among the parties concerned. If the 3D note is shared by attaching it
to the 3D shape information, the quality of data exchange between the parties can be improved.
With the component schema of ISO 10303-242, it is possible to pass information downstream from the design
department to the production department, but passing error information from the production department
(MES) to the design department (PLM) requires a (upstream) feedback loop.
A schema, such as "Associative Text" (ISO/TS 10303-1132) used in ISO 10303-242, can be used as it is,
but additional information or requirements accompanying error feedback need to be reflected and
supplemented. In the case of complex errors that the production department cannot handle on its own, a
bundled set of 3D visualization elements for error feedback shall be sent to the design department to solve
the problem.
5.7 Drawing image with markup
When a malfunction (or error) is reported to the shipyard's on-site design department, the error is marked
on the printed 2D drawing, the drawing is scanned into an image, and the error information is shared with
other departments. Even when sharing 3D models between PLM and MES, scanned images can be used as
auxiliary information.
6 Class definition of PLM-MES interface data model
6.1 General
The PLM-MES interface data model defines the data model of the PLM-MES interface, which can be used to
map and visualize corresponding entities with the same meaning in the PLM standard (ISO 10303–239)
and the MES standard (IEC 62264 series). Entity mapping between ISO 10303-239 and IEC 62264 series is
summarized in Annexes A and B.
The proposed PLM-MES interface consists of one upper package and four lower packages inherited from
the top-level package as shown in Figure 5. The top-level package is an “interface version information”
package, including an interface version information class. This class has information about versions and
lifecycle stages. The lower-level “product information” package, “process information” package, “resource
information” package, and “feedback information” package are inherited from the “interface version
information” package.
Figure 5 — Overall structure of the PLM-MES interface
The “interface version information” class contains three attributes: “version”, “lifecycle phase” and
“description”, as shown in Figure 6. The “version” attribute has a serial number indicating the current
version of the information, and “the lifecycle phase” attribute can indicate two types of information. If the
“lifecycle phase” attribute has a value of "engineering phase", data is transferred from the PLM to the MES.
If the lifecycle stage attribute has a value of "manufacturing stage", data is transferred from the MES to
the PLM. The “description” attribute includes a description of PLM-MES interface version information or
additional information.
Figure 6 — UML diagram of "interface version information" class

6.2 Product information package
The “product information” package consists of a “product information” class, a “product structure” class,
and a three-dimensional “shape information” class. The “product information” class contains the “product
structure” class as an association, and the 3D “shape information” class is related to the associated 3D
construct (see Figure 7).
The “product information” class contains ID, name, type, quantity, unit, and description as attributes. The
“ID” attribute is a unique string that identifies a product. The “name” attribute is the name of the product.
The “type” attribute is information that indicates whether a product is a part, a subassembly, or a final
assembly. The “quantity” attribute represents the quantity of the product or its parts. The “unit” attribute is
a unit of quantity.
The “product structure” class has a “parent ID” property and a “child ID” property. The “product structure”
class uses “parent ID” and “child ID” to represent the hierarchical relationship of product-part. The “parent
ID” attribute indicates the ID of the assembly containing this class. The “child ID” attribute indicates the ID
of the part included in this class.
The 3D “shape information” class includes a “file name”, “file format”, and “file location” as attributes. The
“file name” attribute indicates the name of the 3D shape file. The “file format” attribute indicates the format
of the 3D shape file, such as X3DOM format or jupiter tessellation format (JT format, see ISO 14306). The “file
location” attribute indicates the path of the file.
NOTE 1 The “version” attribute of the “interface version information” class can add version information such as
registration date such as ISO 10303-1 and can be used to track previous versions. The change history of data can
be managed using the “version” attribute. The “descriptive” attribute can be used to include additional data, such as
registrars.
NOTE 2 The “ID” attribute of the “product information” class represents a unique identifier even if the product
has a duplicate name. The “name” attribute contains the product name. The “type” attribute represents an assembly,
subassembly, or component. The “quantity” attribute contains a number such as 3 and the “unit” attribute contains
units such as mm or EA.
NOTE 3 The parent ID of the “product structure” class represents the product identification of the parent node. The
child ID of the “product structure” class represents the product ID of a child node such as part1 or sub_assembly1.
NOTE 4 If any other format is used as the file format, it can be treated as an error.

Figure 7 — Structure of the «product information» package (UML diagram)
6.3 Process information package
The “process information” package consists of a “manufacturing process” class and a “manufacturing process
sequence” class, as shown in Figure 8. The “manufacturing process” class includes the “manufacturing
process sequence” class as an association.
The “manufacturing process” class has attributes such as “ID”, “description”, “objective”, and “objective
description”. The ID attribute is either a process name or a string of process type. The “target” attribute
represents the function of the process. The “goal description” attribute describes the purpose of the process.
The “manufacturing process sequence” class has “ID”, “description”, “pre-process”, and “post-process”
attributes. The “manufacturing process sequence” class uses these attributes to represent process
sequences. The “ID” attribute of the manufacturing process sequence class represents the unique identifier
of the production process sequence. The “pre-process” attribute represents the ID of the pre-production
process. The “post process” attribute represents the ID of the next production process.

Figure 8 — Structure of the «process information» package (UML diagram)
NOTE 1 "Milling" can be written as the “ID” attribute of the manufacturing class, and "making_part1" can be
written as the “target” attribute of the manufacturing class.
NOTE 2 A process sequence identifier such as "part production 1" can be written as the “ID” attribute of the
“manufacturing process sequence” class. "Receiving" or "rolling" can be used as “pre-processing” attributes and “post-
processing” attributes, respectively.
6.4 Resource information package
The “resource information” package consists of a “manufacturing resource group” class and a “manufacturing
resource” class, as shown in Figure 9. The “manufacturing resource group” class includes manufacturing
resources as a dependency. The “manufacturing resource group” class has an “ID” attribute, a “description”
attribute, and a “higher-level group” attribute. The “ID” attribute and “description” attribute indicate the
name of the resource and additional information. The subclass “manufacturing resources”, has an “ID”
attribute and a “description” attribute that indicate the resource's name and additional information.

Figure 9 — Structure of the «resource information» package (UML diagram)
6.5 Feedback information package
The “feedback information” package is used to represent information sent from the manufacturing department
to the design department (see Figure 10). Using the 3D associative text schema (ISO/TS 10303-1132) of
ISO 10303-242 (or AP242), feedback is expressed in the form of 3D notes.
It defines both the annotation text and the leade
...