If you have difficulty in submitting comments on draft standards you can use a commenting template and email it to admin.start@bsigroup.com. The commenting template can be found here.
The standard interface between PLM and MES can be big. This standard part covers only the visualization components as a start which can reveal the scope of the work.
The followings are within the scope of this standard:
a) Information model of visualization components for the plant industry where product is complex and has long life cycles
b) Definition of attributes of the data model classes which represent the information model of visualization components of PLM and MES interface
c) Relationship with information model of visualization components as defined in ISO 10303-239 product life cycle support
d) Relationship with information model of visualization components as defined in IEC 62264 enterprisecontrol system integration
The followings are outside the scope of this standard
a) An information model of visualization components for industries where products are simple and have short life cycles
b) Definition of methods of the data model classes which represent the information model of visualization components of PLM and MES interface
Purpose and justification of the proposal
Figure 1 shows the current interface among PLM, ERP, MES systems which is optimized for the mass production context. Because ERP does not handle 3D engineering information such as CAD models, sometimes there is a separate direct link between PLM and MES. As the production system is well tuned for the mass production system through a series of test productions the direct link does not exist for many cases.
Figure 1 As-Is Configuration of PLM-MES Data Exchange
Because the commercial markets have more than enough suppliers, customers have more power than suppliers. That unbalanced force promotes ‘mass customization’ to satisfy customers and arrives at the concept of ‘personalized production’. The problem of personalized production is that cost and time can increase as similar to the old-fashioned custom-tailor cloths. The new technologies should help to provide the personalized product with the price of mass production.
Another problem is the maturity level of design. In the case of mass production context, the maturity level of design is high because any small design error creates a big problem at the automated production line. Through a series of test production cycles the design maturity level goes higher. This is possible because the design cost is relatively small compared to the production volume and costs. When it comes to the personalized production, the maturity level of design cannot be high so that during the production cycle the design can be modified to heal the error found late. The plant industry including shipbuilding and construction is born to be a personalized type. Because every product has its own design, there is pressure to design the product fast so that the production cycle begins even though the design is not yet finished. In addition to the short time allowed for design, the design cost does not afford many cycles of iteration because each product should be designed individually.
In this kind of situation where the design and production are overlapping (This concept is already popular in concurrent engineering), the two departments of design and manufacturing should well collaborate and exchange more information. 3D information should be shared between two departments because both design and manufacturing work in 3D world. Figure 2 shows the proposed configuration among three systems where there is a direct link between PLM and MES to support the personalized production context. Because two systems are developed without any mutual consideration, there are mismatches of terminology and concept. There is a need for standardized interface definition and implementation of the interface.
Figure 2 To-Be Configuration of PLM-MES Data Exchange
Based on an analysis of related PLM standards and MES standards, the visualization components of PLM-MES interface defines an information model of PLM-MES interfaces which can be used to map and to visualize corresponding entities with the same meaning.
Figure 3 Process of PLM-MES Data Exchange
Figure 3 shows the use case of data exchange between PLM of a design department and MES of a production department. The use case was collected from a shipbuilding company of Korea. The numbered stages in Figure 3 are explained below.
(1) The design department handovers information such as 3D configuration data, drawings, process information to the production department using PLM and the production department produce products using MES.
(2) The production department feedbacks information (design errors, process changes, facility changes, or malfunctions of facilities) which are generated during the production planning to the design department through PLM.
(3) The design department updates the design data and delivers again the updated information to the production department. There can be a separate and small purchase request to ERP and to the procurement department.
(4) Field generated information such as temperature, RPM, pressure, deformation which show the status of the steady operation of production facilities can be feedback to the design department.
The states-of-the-arts technology in a world class shipyard shows that the 3D shape model from the design department is usually delivered to the production department using a digital model which is a simplified mesh model of the original CAD model. The PDA (personal digital assistant, also known as a handheld PC) is used to visualize the 3D model. The delivery channel of 3D product model is separate from the traditional PLM ~ ERP ~ MES sequential interface as shown in Figure 1.
The problem is when something is wrong with the production which is not controllable inside the production department and needs input from the design department. Current channel of communication is to print out the 3D model from PDA and to highlight the problem area. It is sent to the design department with messages via email or voice communication together with the scanned image of the hardcopy with hand markings. There is a need for a reliable digital channel of 3D feedback information. Where both PLM and MES share and modify the same 3D model of the project. The focus of this specification is on the stage (2) and stage (3) of Figure 3 and visualization of the related data models. The same concept can be expanded to include the whole aspects of the project and the whole scope of MES and PLM.
This standard part specifies information models of visualization components for exchanging data between PLM (Product Lifecycle Management) and MES (Manufacturing Execution System or MOM - Manufacturing Operations Management). The focus is given to the use cases of shipbuilding industry because the industry is typical in terms of ‘personalized production’ from the beginning of the industry and characteristics of the industry are similar to those of the construction industry or plant industry. The interface can be expanded to accommodate requirements of other industry domains as the industry 4.0 or the personalized production is getting established.
Consider the following:
Is there a verified market need for the proposal?
What problem does this document solve?
What value will the document bring to end-users?
You are now following this standard. Weekly digest emails will be sent to update you on the following activities:
You can manage your follow preferences from your Account. Please check your mailbox junk folder if you don't receive the weekly email.
You have successfully unsubscribed from weekly updates for this standard.
Comment on proposal
Required form fields are indicated by an asterisk (*) character.