KR102375965B1 - Integrating system using bod schema - Google Patents

Abstract

The integrated system of the present invention may define a video schema including an application area and a data area, and use the video schema as a data model structure for mutual input/output between individual application systems for system integration.

Description

Integrated system using video schema {INTEGRATING SYSTEM USING BOD SCHEMA}

The present invention relates to an integration system that uses a standard schema for business process integration.

A smart factory refers to a factory in which all elements in the factory are organically connected and operated intelligently by combining digital technologies such as cloud, big data, artificial intelligence, Internet of Things, and mobile.

The key keywords of the future smart factory are connectivity and data, enabling productivity innovation by vertically and horizontally integrating the entire business ecosystem. The conventional manufacturing architecture has a hierarchical structure with clear boundaries between manufacturing application systems, but as the connectivity of elements within an enterprise is emphasized, the destruction of the boundaries between manufacturing application systems is accelerating. In other words, it is necessary to build a KPI (Key Performance Indicator)-centered system through vertical and horizontal data integration, aiming for an open business ecosystem, and strengthening manufacturing competitiveness.

Korean Patent Publication No. 1020200074652

An object of the present invention is to provide a standard-based data model for improving the utility of fragmented and scattered data, and to provide an integrated system that supports services for utilizing the data.

Conventional companies have recognized the importance of data in order to secure business competitiveness, and have introduced and operated various IT applications in stages. However, it is difficult to utilize and analyze data due to the absence of an interface establishment and manufacturing data standard system that does not consider the introduction of a new system. For example, problems such as missing essential data values, non-compliance with valid format and promise values between tasks, duplication of the same data, data inconsistency between individual application systems, and omission of data provision when needed occur frequently. Such inconsistent data can be a major factor in bad decision making, and it can take a lot of time, money, and effort to verify the data.

For this, data structure standards are needed to achieve data integration. Data exchange and system architecture standards have been used for many years to solve these problems, but there is a lot of overlap in the unified standards for dealing with the manufacturing value chain. For example, the Open Application Group Integration Schema (OAGIS), Business to Manufacturing Markup Language (B2MML) defines a message that allows manufacturing application systems to be integrated with low-level systems, ERP, EAM, and other enterprises at various levels of detail; MIMOSA and ISA-95 define a structure for modeling enterprises and assets at various levels within an enterprise, and ISO130303 STEP and ISO-15926 can support product information lifecycle modeling. However, these international standards are difficult to apply to domestic sites due to a sense of disparity in attributes, terms, and meanings used in domestic manufacturing sites, and users may feel it is difficult to utilize them due to their confusing and complex structure.

The video schema of the present invention is a data model structure in which individual application systems mutually input and output for system integration, and may include an application area and a data area.

The video schema of the present invention is a standard schema of each individual application system, and includes an application area and a data area. The data area is divided into a verb part and a noun part, and may be expressed in XML or JSON.

It is possible to develop a manufacturing application system that can conform to international standards by building a manufacturing data standard schema database that reflects the characteristics of domestic sites as well as international standards, and thus can be easily compatible with global integrated solution packages.

The integrated service platform also enables solution providers to efficiently perform the tasks required to interface between heterogeneous systems. In addition, the utility and field applicability of standards can be improved by participating in the standard data model update by private companies that utilize actual standards through the management system. Because it is managed in a structure, it can be managed in a consistent way.

Through this, data can be managed in the same structure from the on-site data collection to analysis and utilization stages of manufacturing companies, and all components within the business ecosystem can participate to form a foundation for building a collaborative platform that enables interactive information sharing.

Today's competition means competition between one supply chain and another, and it is changing from competition between single companies to competition between ecosystems. In order to acquire differentiated competitiveness, a strategy that can strengthen the business ecosystem is required. It is necessary to secure an efficient collaboration system between the parent company and its subsidiaries.

In consideration of this, the present invention can satisfy the needs of the following companies. The need to expand the smart factory between partners, strengthen information communication and collaboration, strengthen the self-reliance of partners, share information and data, integrate business processes, implement collaboration through building a new platform, strengthen shared growth, strengthen partnerships, improve global manufacturing quality competitiveness, timely parts Supply, quality assurance, product development collaboration, securing component cost competitiveness, securing a flexible component supply chain, etc. may be the needs of a company that the present invention satisfies.

The core of the video schema or integrated system of the present invention is connection and sharing.

The company's vertical collaboration system may include a parent company - a primary parts supplier directly supplying to the parent company - a secondary parts supplier supplying to the primary parts supplier - a general purchasing supplier supplying to a secondary parts supplier. The present invention can achieve the construction of an efficient collaboration system between the constituent companies constituting the vertical collaboration system.

The present invention can secure differentiated competitiveness or strengthen horizontal connectivity throughout the parts supply ecosystem consisting of a smart factory by utilizing various manufacturing application applications.

Through the integrated system of the present invention, the components in the business process can be connected to each other and can interact.

Each application or a function module constituting each application may be treated as one active object on the entire system. It can support Plug and Produce with little engineering achievements. Flexibility of facilities, equipment and factories can be secured. End-to-end engineering can be achieved by pursuing continuous vertical and horizontal integration. It has improved scalability and enables innovation as an open technology.

According to the present invention, anything such as ERP, CRM, PDM, etc. can be connected to the integrated system in a plug-and-produce method to achieve mutual information exchange and an open ecosystem with high accessibility for all users. Real-time situational response including fault and error alarms is possible. A quality management-based database is built, and by using it, facility predictive health and company-wide equipment efficiency management can be achieved.

1 is a diagram schematically showing the configuration of an open service integration system of the present invention.
2 is a screen of the portal site homepage of the integrated system of the present invention.
The process of creating and synchronizing bill of materials (BOM) information to produce a product is described as the scenario of the present invention in FIG. 3 .
4 is a block diagram showing the structure of a BOD according to the present invention.
5 shows an XML code of a video with the name 'SyncBOM' of the present invention.
6 is an example showing data exchange between systems through the BOD defined in the present invention.
7 is a block diagram illustrating a tree structure of an application area according to the present invention.
8 is a diagram showing the structure of the action verb part of the present invention.
9 is a diagram showing the structure of the response verb part of the present invention.
10 is a diagram showing the structure of the request verb part of the present invention.
11 is a diagram showing the structure of the noun part of the present invention.
12 schematically shows a procedure for using the dev editor of the present invention.
13 is a diagram showing the use of the dev editor and explorer of the present invention.
13A is a block diagram illustrating an XSD file input to a dev editor of the present invention and an XML or JSON file output from the dev editor.
14 schematically shows the structure of the Trans-API according to the present invention.
15 is a diagram schematically illustrating data transmission through the Trans-AP of the present invention.
16 shows a flow in the case of linking through the interface table of the present invention.
17 is a flowchart illustrating a case of linking through data communication according to the present invention.
18 is a diagram showing a procedure for using the management system of the present invention.
19 below shows the user interface of the integrated system of the present invention.

The present invention can integrate the following individual application systems vertically and horizontally using standard video schema. When integrating individual application systems through the integrated system, connectivity and sharability can be strengthened by utilizing BOD or BOD schema as standard data elements.

In the present invention, BOD may be used as the same term as BOD schema. BOD means standard data elements, and BOD schema may be used as a term encompassing the concept of BOD used as a standard schema.

■ Individual application systems

Individual application systems include Supply Chain Management System (SCM), Advanced Production Management System (APS), Enterprise Asset Management System (ERP), Object Relationship Management System (CRM), Product Lifecycle Management System (PLM), and Manufacturing Execution System (MES). ), a warehouse management system (WMS), a quality management system (QMS), a virtual physical production system (CPPS), and a factory energy management system (FEMS).

(1) Supply Chain Management System (SCM: Supply Chain Management) - It refers to a system that grasps the flow of logistics from parts suppliers to producers, distributors and customers from a single value chain point of view and supports the smooth flow of necessary information. It may include at least one of a material ordering, delivery management, order management, and sales management module.

(2) Advanced Production Management System (APS: Advanced Planning & Scheduling) - A production-related management program such as MRP or ERP, which collectively refers to a program that performs production planning. It may include at least one of a production planning, demand management, delivery appointment, and resource management module.

(3) Enterprise Asset Management System (ERP: Enterprise Resource Planning) - Accounting Management, Human Resources Management, Sales Management, Trade Management, Purchasing Material Management, Inventory Management, Production Management, Outsourcing Management, Standard Information Management, Logistics Management, Cost Management, It may include at least one of a quality management, facility management, and project management module.

(4) Object relationship management system (CRM: Consumer Relationship Management) - may include at least one of customer management and sales analysis module.

(5) Product Life-cycle Management System (PLM: Product Life-cycle Management) - at least one of project management, BOM management, change management, development quality management, technical asset management, reference information management, product information management, and development collaboration management module may include

(6) Manufacturing Execution System (MES) - may include at least one of production management, equipment management, standard information management, performance management, monitoring module, material management, quality management, process management, and logistics management module .

(7) Warehouse Management System (WMS) - A system for managing and operating a customer company's logistics by integrating and managing the entire logistics center process, such as warehousing, warehousing, inventory, picking, and shipment. It may include at least one of a warehousing management, performance management, return management, shipment management, and inventory management module.

(8) Quality Management System (QMS: Quality Management System) - It may include nonconformity management, claim management, partner management, quality review, change management, SPC, and PPAP modules. SPC is an abbreviation of Statistical Process Control. It can be a module that utilizes statistical data and analysis techniques (S) to identify the cause and process status of quality fluctuations (P), and manages them so that quality goals can be achieved (C). PPAP (Production Part Approval Process) may be a module for a production part approval process.

(9) CPPS (Cyber Production Physical System) - As it emerged in Industry 4.0, it can be a module that tightly integrates at all scales and levels in different virtual and physical systems.

(10) Factory Energy Management System (FEMS) - As an energy management system of a factory, it may include at least one of an energy diagnosis module, an energy storage module (ESS), an energy analysis module, and a load control management module. .

The present invention can use various support services of the knowledge sharing-based integration system to integrate business processes based on business integration scenarios and standards-based data models.

■ Open service integration system

The open service integration system of the present invention can share and utilize data generated by users as a website based on knowledge sharing for use and update of business integration scenarios and standard data models.

1 is a diagram schematically showing the configuration of an open service integration system. The integrated system may include an integrated scenario and standard data model BOD, a management system, a dev editor, an explorer, and a transAP.

2 is a screen of the portal site homepage of the integrated system. The basic menu of the integrated system consists of a total of six. Introduction menu including an overall introduction of the present invention, a download menu for downloading related materials such as technical documents and XSD files, a tool kit menu for introducing and accessing support tools, New Proposal, a user-participating video management system Includes menu and membership menu for service use application.

■ Business Integration Scenarios

The business integration scenario defines a business process that is commonly applicable to all industries, and can be expressed as a BOD flow that exchanges messages between manufacturing application systems. By defining the information exchange subject of the scenario as the functional unit of the manufacturing system rather than the unit of the manufacturing application system, it is possible to form a mesh-type network structure in which each function can interact with each other as a participant in the manufacturing environment. Through this, data generated at the production site can be easily shared, and KPI (Key Performance Indicator) or desired information suitable for the manufacturing level and characteristics of the company can be identified in real time. That is, the BOD may organically connect each individual application system, and an organic combination of a plurality of individual application systems may form a scenario.

A scenario can be defined as a process in which each individual application system uses standardized data, BOD, and performs requests and responses. The first individual application system transmits a first BOD toward the second individual application system and requests a first request, and as a first response to the first request, the second individual application system sends the first individual application system to the first individual application system. It may be a process of transmitting a second video-to-video (BOD) to the first request and talking as a first response to the first request. Individual application systems and video schemas can be extended to a greater number. However, the component's own process within the scenario is not BOD.

A scenario may be expressed as a UML (Unified Modeling Language) sequence diagram. UML (Unified Modeling Language) may mean mainly a pictorial notation to express program design. It can be viewed as an object-oriented modeling language. To design a model before coding, UML can be used for visual modeling.

The scenario may be stored in the scenario database unit.

The scenario of Figure 3 describes the process of creating and synchronizing bill of materials (BOM) information to produce a product. To this end, individual application systems in the scenario of FIG. 3 may include a product life cycle system (PLM), an enterprise asset management system (ERP), and a manufacturing execution system (MES). In the absence of a product lifecycle system (PLM), an enterprise asset management system (ERP) can replace the PLM role.

According to the scenario shown in FIG. 3, the first request is made while transmitting a BOD called SyncBOM in order to synchronize the bill of materials (BOM) information generated in the individual application system, PLM, to the individual application system, ERP. can transmit In response to the first request, the ERP may transmit a first response that is a response to the first request while transmitting a BOD called a SyncResponseBOM toward the PLM.

Next, the PLM may transmit a BOD called SyncBOM to the MES to transmit a second request requesting synchronization of BOM information to the MES. As a second response that is a response to the second request, the MES may transmit a BOD called SyncResponseBOM to the PLM.

■ Standard data model video (BOD)

BOD is an abbreviation of "Business Object Document", and may be a data schema, which is a common message structure that must have for smooth data exchange between systems. A schema may be stored in a database in the form of meta data, and may be created using a specific data model as a representation of a specific part of the real world. The BOD of the present invention is a result of benchmarking international standards such as IEC 62264, and the BOD defined in the international standard was reconstructed and developed so that it can be easily utilized in Korea by reflecting the characteristics of the domestic manufacturing site. In this case, compatibility with future international standards was considered by applying the meaning of terms defined in international standards and camel notation.

The present invention can standardize data management, delivery, and sharing by utilizing a BOD having a multi-layered structure in which information can be reused. Conventionally, compatibility or standardization of data of different individual application systems has not been made, but it can be integrated through BOD. The proposed BOD has no industry restrictions and can be applied to all data exchanges between applications (A2A: Application to Application). That is, it is applicable not only to the case where a plurality of applications exist within one company, but also to the interface between applications of different companies (B2B: Business to Business). Also, BOD can be applied from the field facility area where communication is possible to the business decision-making system area.

4 is a block diagram showing the structure of a BOD according to the present invention. Referring to FIG. 4 , the BOD may include an application area and a data area. The data area may include a verb part and a noun part, and the noun part may include a field part and a reference field part. The name of the BOD can be named through the combination of the verb part and the noun part.

BOD may be expressed in XML or JSON. XML (Extensible Markup Language) is a text based markup language similar to HTML, and was created for the purpose of storing and delivering data. XML tags are not predefined like HTML tags, and users can define their own. XML can easily exchange various types of data between different systems, and it is scalable because it continues to operate even if new tags are created and added. XML can be primarily aimed at conveying and storing data, rather than displaying the data itself. XML is a text data type language, and XML documents are made up of only Unicode characters, which can be very versatile.

5 shows an XML code of a video with the name 'SyncBOM'. At the top, 'SyncBOM', which is the name of the video, may be shown as <SyncBOM>. The video may include an application area indicated by an <Application Area> tag and a data area indicated by a <DataArea> tag.

6 is an example showing data exchange between systems through a defined BOD. When the system (Sender) that has the information sends a message (SyncBOM) to synchronize (Sync) Bill Of Material (BOM) information to another system, the receiving system (Receiver) returns a message with the processing result (SyncResponseBOM) is sent. In this way, when the sending application sends a request video message for information processing and necessary information, it is preferable that the receiving application transmits a reply video message to the received video message.

■ Standard Data Model BOD Structure - Application Area

The application area delivers information necessary in the communication layer for video message processing, such as the IP address of the video transmission/reception application and the video transmission date. In addition, information necessary for identification and authentication of the video message may be included.

7 is a block diagram illustrating a tree structure of an application area according to the present invention. The application area may include at least one of a sender (Sender), a receiver (Receiver), a creation time (CreationDateTime), a scenario ID (ScenarioID), and a video ID (BODID) as primary attributes.

The primary attribute, 'Sender', refers to an individual application system that transmits a video message. The sender contains, as secondary attributes, the host address (Host) and application ID (ApplicationID), which are information about the location of the system such as the IP of the sending application and the server port. In addition, it includes a confirmation code (ConfirmationCode) for requesting a simple confirmation of whether the video message was successfully received from the receiving application.

The primary attribute, 'Receiver', refers to an individual application system that receives a video message. The receiver (Receiver) may include at least one of a host address (Host) and an application ID (ApplicationID) as secondary attributes (attributes) similar to the sender attributes (attributes).

The creation time (CreationDateTime), which is a primary attribute, may contain information on when the video is created.

ScenarioID, which is a primary attribute, may contain information about an integrated scenario related to video.

A video ID (BODID), which is a primary attribute, may indicate ID information for identifying a video audio device.

■ Standard Data Model BOD Structure - Data Area

The data area includes information delivered by the video message, and may be composed of a verb part (Verb) and a noun part (Noun).

The verb unit may indicate an operation to be performed by the receiving application or an operation connected with information, such as a response to a request of the sending application. In principle, in BOD, when the sending application sends a request message for information processing and necessary information, the receiving application sends a reply message to the received message. As such, the type of verb to be used is determined according to the context in which the message is sent. The types of verbs can be defined as an action verb part, a response verb part, and a request verb part.

The action verb refers to a verb that creates a business object or performs an action with a business object. The action verb part can be used in a situation where a specific processing of the transmitted information is requested. A specific processing of information represents an action that must be taken on data or video, such as adding, changing, or deleting information. 8 is a diagram illustrating the structure of an action verb unit. The acknowledgment code determines whether to reply to the video message responding to the verb part of the action type. The action criteria includes the action to be taken on the information (actionCode) and information about the target (Xpath). Specific types of action verbs include Sync, Change, Cancel, Process, and Notify.

The response verb refers to a verb used when reporting or returning the result of the requested processing for the original message, which is the recipient. 9 is a diagram showing the structure of a response verb part. The response criteria includes the processing result (actionCode) of the information received by the previous request message and the content to be returned (Xpath). The types of response divisions include SyncResponse, ChangeAcknowledge, CancelAcknowledge, Acknowledge, Show, and Confirm. .

The request verb refers to a verb used when requesting specific data of a receiving application. 10 is a diagram showing the structure of a request verb unit. In Expression, the request to the receiving application is expressed in XPath. The type of the request verb part may be Get.

The noun part includes information to apply the action defined in the verb part. 11 is a diagram showing the structure of a noun part. The noun part consists of a reference field part and a field part. The reference field part is a key value for referencing other tables, and it enables reuse of information to secure flexibility and extensibility during the interface. The field part is a value that does not refer to other tables. The contents of the noun part were defined by applying international standard terminology and notation by arranging the data attributes commonly used in the domestic field to deliver each information. For example, the name and description of the noun part are as follows.

(1) Bill of Materials (BOM): It can mean a bill of materials that is used to compose an item or produce an item.

(2) Item Master: It may refer to an item master that manages various attribute values such as item code, item name, standard, and the like.

■ Supporting tools for using scenarios and BOD

The present invention can achieve interface-oriented manufacturing data standardization using BOD. Using BOD as a basic element, we propose DevEditor, Explorer, and Trans-API, which are support tools to increase standard usability.

DevEditor is a developer collaboration tool that creates business processes and videos tailored to the user's situation. 12 schematically shows a procedure for using the DevEditor. The process of FIG. 12 is passed through the dev editor, and members participating in the project must complete the review to proceed to the next step. In this way, if you use DevEditor, you can create a project and perform real system interface project collaboration, and you can utilize functions such as notifications and chatting for smooth collaboration.

The explorer is a tool that can search the properties of the scenario and video provided by the integrated system of the present invention. If you use Explorer, you can find out the exact meaning of the scenario, the video, and the properties of the video. Explorer can provide a scenario and video recommendation service suitable for the user's situation.

13 is a diagram showing the use of DevEditor and Explorer. Users can search scenarios and BODs provided as standard in the integrated system through DevEditor and Explorer.

User-defined scenarios or BODs created through DevEditor can be saved separately and shared in Explorer.

When a user accesses the portal site of the integrated system without logging in, the description screen of the dev editor may be displayed. On the other hand, if the user clicks the dev editor menu of the portal site after logging in to the portal site, the dev editor may be executed. The dev editor may provide a notification or chat function for user collaboration.

When a user accesses the dev editor through a login method, a video may be created or edited by the dev editor. The properties of the video can be edited with a dev editor.

13A is a block diagram illustrating an XSD file input to a dev editor of the present invention and an XML or JSON file output from the dev editor.

An XSD file may be input to the input side of the dev editor, and an XML file or JSON file may be output to the output side. One XSD file input to the dev editor may be output separately as a plurality of XML files or JSON files for each individual application system.

The dev editor may receive the XSD file and output the first XML file or the first JSON file to the first individual application system. The dev editor may receive the XSD file and output the second XML file or the second JSON file to the second individual application system.

The XSD file and each XML file or JSON file may be the same without changing the verb part. According to Fig. 13a the SyncBOM is shown as a common verb part.

The field part of the noun part may be separated according to the characteristics of each individual application system while going through the dev editor, and the field part of the separated noun part may be allocated to each individual application system.

Referring to FIG. 13A , the noun part of the XSD file may include a first field part and a second field part. The first field unit is shown as Field 1 and may indicate a company ID. The second field part is shown as Field 2 and may indicate item specifications.

The first field part of the XSD file may be transmitted to the first individual application system through the dev editor, and the second field part of the XSD file may be transmitted to the second individual application system via the dev editor.

The first field unit may be transmitted to the first individual application system in the form of a first XML file or a first JSON file. A company ID shown as Field 1 may be stored in the first XML file or the first JSON file. The item specification shown in Field 2 is the second field part and is unnecessary for the design purpose of the first individual application system, so it is transmitted in the form of a second XML file or a second JSON file to the second individual application, which is an individual application system for manufacturing purposes. can be

The property of the noun part may include at least one of a name, a type, and a length of a field part or a reference field part included in the noun part. The Dev editor can separate the properties of the noun part while keeping the verb part as it is, so that it can be customized for each application system.

The Dev Editor adds a video to a scenario or edits the properties of a video added to a scenario as desired by the user, so you can create a custom video or a custom scenario. Because data is shared, the Dev Editor can be used as a developer collaboration tool for project execution.

Dev editor can create or edit video. As shown in FIG. 13A , the properties of the noun part of the video transmitted to each application system may be separately assigned. The attribute of the noun part of the XSD file may be assigned as the attribute of the noun part of the XML file or the JSON file.

Trans API can be a tool that supports a seamless interface between individual application systems.

Since the data names defined for each system are different, Trans-API was developed in the form of an integrated package equipped with a standard mapping function, comprehensively considering user usability and field applicability. 14 schematically shows the structure of a Trans-API. The integrated system support tool can perform one-to-one mapping between standard data models and system data. In addition, you can receive completed project information from DevEditor and download BOD information and schema files to your local PC.

■ Interface support tool Trans api

It can act as an adapter that supports the system interface in the field of the company by interworking with the Trans-API of the integrated system. 15 is a diagram schematically illustrating data transmission through the Trans-AP. In this case, it is assumed that the data communication method using the interface table is used. In order to transmit data, the transmitting system calls TransAPI in the form of a URL, and the TransAPI accesses the interface table of the transmitting system to retrieve interface data. The schema is converted into a standards-based XML document through the mapping table of Trans API, and data consistency is verified by comparing it with the BOD schema XSD file. After that, the data is converted back into the schema of the receiving system and data is inserted into the interface table of the receiving system.

In order to perform such a series of processes, Trans API must have access to the interface table of each individual application system.

In addition, by storing and managing the events and logs made in Trans-API in the log database, the status of the interface between each application can be inquired in real time.

■ Data linkage method through Trans API

As a data interface method between applications, there may be a method using an interface table and a method using data communication. Trans API of the present invention can support both methods.

16 shows a flow in the case of linking through an interface table. When the interface table is used, a separate interface table is placed between each application and the interface table is temporarily created for data to be linked in such a way that the interface table is interrelated. However, Trans API must have access to the interface table to select and insert data in the interface table of each system.

The interface table can be designed by adding not only data to be linked, but also items necessary for transmission and reception, such as transmission/reception date and time, and transmission/reception status. Trans API creates an interface table in each individual application system through the data attribute mapping table input by the user into the integrated system. If the interface table already exists, the script for creating it is stored in a separate space.

The generated interface table may be composed of reference fields and fields of a noun part based on a BOD structure along with interface essential items such as transmission/reception date and time, transmission/reception status, and the like. In this case, the interface table structure of the transmission/reception application may be the same.

17 is a flowchart illustrating a case of connection through data communication. In the case of the interface method through data communication, when the data format to be linked is delivered as an XML file, the receiving side parses it and interprets it. The XML file is generated in a BOD structure, and the generated XML file can be transmitted through FTP (File Transfer Protocol).

In both methods, consistency verification can be performed through the XSD file in Trans-AP. In the case of using the interface table, data integrity can be verified by converting data from Trans API to an XML file and comparing it with the XSD file of Trans API. Even when data communication is used, data can be verified through the XSD file possessed by Trans API before the XML file is transmitted to the receiver.

■ Scenario and video (BOD) management system

The manufacturing data schema may be added and changed according to changes in the requirements of suppliers and demanding companies, development of technology, etc. These additions and changes to the manufacturing data schema require continuous and consistent management according to standard procedures. In the present invention, by systematizing and providing a standardized management system of manufacturing data schema, it is possible to support schema management in a consistent way.

Stakeholders who use the management system include users, management agencies, and the Deliberation Committee. The user proposes management (creation/modification/deletion) of the manufacturing data schema, and the management agency processes the manufacturing data schema management (creation/modification/deletion) suggested by the user in the manufacturing data management system, and the Deliberation Committee handles the manufacturing data schema management (creation/modification/deletion) It is composed of related industry/academic/research experts and conducts a review on whether to approve or reject the management organization's manufacturing data schema management.

18 is a diagram showing a procedure for using the management system. In the manufacturing data schema definition stage, for the purpose of defining the scope of the schema to be developed and configuring the participating members, the schema scope, scenarios, schema messages and data (XML items) to be registered and changed, schema registration and change plan / related organizations and It is defined including resources, schema-related assumptions, dependencies with other schemas, and issues. In the development stage, for the purpose of creating schema contents, related documents and examples, it includes the creation of related documents such as XML schema example creation. In the schema review and approval phase, the manufacturing data schema stakeholders review the registered and changed manufacturing data schema by the Deliberation Committee to ensure that it can support the existing work and to ensure that it is a better outcome than the registered and changed existing schema. do. In the schema publication stage, for the purpose of publishing and announcing the registered and changed manufacturing data schema on the homepage of the schema management institution, the new registered and changed schema is posted on the schema management institution's Internet homepage, and a notification e-mail is sent to the stakeholders, and the final version is published. merge

■ Dev editor's user interface

The main features of the Dev Editor are:

(1) User-customized scenario and video creation function - Through the Dev Editor, users can create scenarios and videos as desired. Through the Dev Editor, the user can add a video to the scenario or edit the properties of the video added to the scenario as desired by the user.

(2) Scenarios and videos created by users can be shared on the website or viewed in Internet Explorer. The scope of the scenario and video that can be disclosed can be determined in the integrated system policy.

(3) Dev editor can be used as a developer collaboration tool for project execution. Dev Editor can be used as an online collaboration tool such as dashboard, notification, and chat for efficient work performance. Dev editor can increase the linkage in heterogeneous system linkage projects.

The three tool kits are included in the second function that is executed after the user logs in.

Dev editor among the tool kit menu at the top of the home page of the integrated system can be executed when the user logs in and clicks.

The second function of the integrated system can be executed when a user accessing the portal site logs in. General users may include demand enterprise users and supply enterprise users.

A list of projects related to the user may be displayed. You can show the list of projects of the logged in user. A project registration menu may also be displayed. The project registration menu can be displayed only to demanding enterprise users.

A project creation window that is displayed only to the demanding enterprise user may be displayed. When the user clicks the project name, it can be moved to the project detail information screen.

19 is an interface for registering or modifying a project. The selection of the supplier or individual application system participating in the project in the pop-up window of FIG. 18 is reflected. A registered supplier or individual application system can be deleted or added from the basic project information.

20 is a detailed screen of the project selected in the dev editor.

The dev editor may display at least one of a dashboard, a list of materials, a project discussion, a scenario, and a video in a tab format.

21 is a screen displayed when the data list tab of the dev editor is clicked. If you click the document tab on the project detail screen, you can register or share project-related materials or documents. 22 is a window for deleting a document.

23 is an interface in which project discussion items are opened as tabs. You can display opinions about the project, and add, edit, or delete opinions. As described above, the integrated system has the advantage of being able to share the opinions of multiple users on a project with each other.

24 is an interface executed when the scenario tab of the project detail screen is clicked. Scenarios can be added. A blank record for entering scenario information is created and scenario content can be entered. When adding a scenario, it is desirable to input and save the scenario content.

Referring to FIG. 25 , it can be seen that the My Workspace list in the left tree is updated when a scenario is added/stored or deleted. Selecting an item in the tree can display its contents in a tabbed screen.

26 is a screen for adding and setting a video of a created scenario.

An explorer that inquires a scenario or video may be called. Scenarios and videos to be applied can be added in the pop-up window. When a scenario is edited, a diagram of the scenario including the video list may be displayed. When the scenario is completed, other participants in the project are requested to review the scenario, and a message can be delivered.

Referring to FIG. 27 , a scenario and a video can be inquired. When a process is added on the scenario detail screen, it can be opened as a pop-up window. You can search for scenarios and videos with the entered keyword. When a scenario is selected, the entire video included in the selected scenario can be added. The selected video is added, and duplicate addition of the same video may be possible. You can call the video composition by scenario and the diagram display screen of the scenario.

Referring to FIG. 28 , a detailed information pop-up window for each scenario may be displayed. A video list for each scenario and diagram information of the scenario may be displayed. A video to be applied may be selected, and when the selected video is applied, a scenario diagram may be displayed.

29 is a screen showing a result of adding a video to a scenario. After registering the video, an individual application system that becomes a sender and an individual application system that becomes a receiver can be set. Individual application system information of the video can be set, and a scenario diagram can be created by saving it. Scenarios can be displayed as UML diagrams in the right diagram pane. The UML of the diagram window may be downloadable.

30 is a video tab of the project detail screen. If you click on the video, you can select the properties of the video.

31 is an attribute selection screen for creating a user-customized video.

Attribute information of a video provided as a standard may be displayed. When a user selects and saves a desired attribute among all attributes, a video schema including only the selected attribute can be downloaded. You can download the settings as an XSD file or a JSON file.

53 is a new project registration screen. The user can input a project name and a description of the project in the description window. You can enter the name of the demanding company or the name of the person in charge of the demanding company.

At least one of a company name participating in a project, an individual application system name, and manager information may be displayed in the project management table.

A project information management button may be provided, and if clicked, project information can be modified. You can create, manage, and delete projects through the project management table.

■ Explorer's user interface

The following describes the Explorer. Referring to FIG. 32 , the explorer main screen is displayed. If you enter a keyword in the search box at the top, you can search scenarios and videos that include the keyword.

FIG. 33 may display a scenario or video searched as a result of inputting a keyword into the search window of the explorer. Fig. 34 is an enlarged view of the main part of Fig. 33; Search results can show all results related to keywords. For example, a scenario, video, verb, noun, reference field, field, etc. may be displayed.

35 is a pop-up window showing scenario properties, a video list included in a scenario, and a diagram of a scenario.

Scenario details may include at least one of a video name, a name of an individual application system serving as a sender, and an individual application system name serving as a receiver. The scenario may be displayed as a diagram in UML format including at least one of a video audio name, an individual application system name serving as a sender, and an individual application system name serving as a receiver.

36 may display a list of scenarios registered in the integrated system. In the scenario list, the video name, description, and frequency of use of the scenario may be displayed.

Referring to FIG. 37 and a partially enlarged view of FIG. 38 , a list of individual application systems registered in the integrated system may be displayed. The state of the individual application system may include at least one of the name, description, and frequency of use of the individual application system.

■ Trans API's user interface

Trans API that performs conformity verification through the XSD file may be provided.

In the case of using the interface table, data integrity can be verified by converting data from Trans API to an XML file and comparing it with the XSD file of Trans API.

In the case of data communication, data integrity can be verified through the XSD file of Trans API before transmitting the XML file to the receiver.

Trans API can be an adapter for interfacing between heterogeneous systems. Trans API can support both of the above functions.

Trans API can support one-to-one mapping of standard data and system data. Interface status can be inquired through Trans API.

Referring to FIG. 39 , a list of noun parts is displayed, and when a noun part is selected, a list capable of mapping the state of the noun part and the column name of an individual application system is displayed on the right side. Data attributes defined in individual application systems and standard data attributes can be mapped for the noun part.

40 is a detailed view screen of a completed project. Excel download of table information is available. An Excel download of the video list is available. Selecting or changing a scenario may display a corresponding sequence diagram.

■ User interface of the Miscellaneous menu

41 is a detailed screen of the training and service menu.

42 is a detailed screen of a New Proposal menu, which is a video management system. A list of deliberation requests may be displayed. You can show the information you entered in the search bar. Click the request title to go to the detail screen.

Referring to FIG. 43 , a New Proposal review request screen is displayed. You can choose the request type. A request for deliberation can be made based on the entered content.

44 and 45 show processing results of a message requested for deliberation (New Proposal).

A demanding enterprise user or a supplying enterprise user may request creation, modification, or deletion of a scenario or video. The user of the demanding company or the user of the supplying company may input a request for deliberation for a new proposal through the integrated system, and the reviewer may respond to the result by examining the inputted request for deliberation.

52 shows a New Proposal list. The deliberation request list may include at least one of a deliberation request type, a deliberation request name, a user name, a deliberation request date, and a deliberation request status.

The deliberation request type may be for at least one of a scenario, a field part, and a noun part.

The results of reviewing the review request by the reviewer can be shared between the reviewer and the user. The status of the review request may include at least one of Accepted, Rejected, Reviewd, and Queued, and the status of the review request is a selection menu that can be shared by reviewers and users. can

46 is a screen for managing a verb unit. The verb part management table may include at least one of a name of a verb part, a registration date, whether to use it, and an attribute management menu for a verb part. When a user or administrator newly inputs a name for a verb part, a new verb part can be added. If the state of the verb part is changed to unused, the video associated with the corresponding verb part may also be changed to unused.

47 is a noun part management screen. The noun part management table may include at least one of a name of the noun part, whether to use it, a registration date, and an attribute management menu for the noun part. When a user or an administrator newly inputs a name for a noun part, a new noun part can be added. If the state of the noun part is changed to unused, the video associated with the corresponding noun part may also be changed to unused. A menu window to manage the properties of the noun part is also selectable.

48 is an attribute management screen of a noun part. The attribute of the noun part may include at least one of a name, type, length, PK or not, NULL permission, and format of a field part or a reference field part included in the noun part. You can add and edit properties of the noun part.

49 is a video management screen. The video management table may include at least one of a video name, detailed content, registration date, verb part, and noun part. A video property management menu may also be displayed.

50 is a scenario management screen. The scenario management table may include at least one of a scenario name, detailed content, a scenario type, whether to use it, a registration date, and a scenario attribute management menu. You can search by entering the scenario name.

Scenarios can also be added. A new scenario can be added by entering the scenario name, entering scenario information, and completing the items in the scenario management table. A video setting screen may also pop up on the scenario management screen.

51 is a pop-up video setting screen. Video properties and scenario diagrams can be displayed.

Claims (14)

As an integrated system for exchanging data for smart factory,
individual application systems; and
It is connected to the individual application systems, mutually inputs and outputs data between the individual application systems, and exchanges data using each BOD including an application region and a data region including one verb part and a noun part, and a platform server on which a scenario in which the individual application systems exchange the video is performed;
In the platform server,
Dev editor that creates or edits the video and the scenario according to the characteristics of the individual application systems and provides them;
an explorer to search for the scenario and the video; and
Trans API that matches the video between the individual application systems is installed;
The portal site provided by the platform server,
a user interface of the dev editor, the explorer, the trans api, and the review request menu;
It provides a management interface of the verb part, the noun part, the video, and the scenario,
The user interface of the dev editor of the portal site includes information on a first individual application system and a second individual application system, video information exchanged between the individual application systems, and scenario information defined by the video exchange process; Display information about the project that is the aggregate of the scenario,
The user interface of the explorer of the portal site displays a list screen of the scenario and the video,
The user interface of the Trans API of the portal site displays a data mapping screen,
The user interface of the deliberation request menu of the portal site displays a deliberation request list for receiving proposals for at least one of the video and the scenario;
The management interface of the verb unit of the portal site displays a verb unit management table for generating or managing the verb unit of the video,
The management interface of the noun part of the portal site displays a noun part management table for creating or managing the noun part of the video,
The video management interface of the portal site displays a video management table for managing information about the video,
The scenario management interface of the portal site displays a scenario management table for managing information of the scenario expressed in a UML sequence diagram,

The dev editor receives a standard video XSD file and outputs it as a first XML file or a first JSON file for the first individual application system or a second XML file or a second JSON file for the second individual application system, and outputs a custom video and, when the noun part of the XSD file includes a first field part and a second field part, the first field part is included in the noun part of the first XML file or the first JSON file, and the second XML file Alternatively, the second field part may be included in the noun part of the second JSON file,
The Trans-AP uses an interface table to match the data interface between the individual application systems, and the interface table transmits the video transmitted between the first individual application system and the second individual application system to each individual application system. Convert to the corresponding data schema,
The application area is a data integration system for a smart factory including a plurality of primary attributes (attributes) and secondary attributes (attributes) that are sub-attributes of the primary attributes (attributes).
The method of claim 1,
The application area is
Includes basic information for data or video transmission when the individual application systems are integrated,
The application area is represented by XML code,
The basic information includes at least one of a sender, a receiver, a creation time, a signature, a scenario ID, a correlation ID, a video ID, and an extension means.
3. The method of claim 2,
The application area is
Transmits information necessary in the communication layer for video message processing including the IP address of the video transmission application system and the transmission date of the video,
A data integration system for smart factories that includes information for identification and authentication of video messages.
delete 4. The method of claim 3,
The application area is
Including at least one of a sender (Sender), a receiver (Receiver), a creation time (CreationDateTime), a scenario ID (ScenarioID), and a video ID (BODID) as primary attributes (attributes),
The sender is an individual application system that transmits the video,
The receiver is an individual application system for receiving the video data integration system for a smart factory.
6. The method of claim 5,
The application area is
Data for a smart factory having secondary attributes including at least one of a host address (Host), an application ID (ApplicationID), and a confirmation code (ConfirmationCode) as a sub-attribute of the primary attributes displayed as a sender integrated system.
delete 7. The method of claim 6,
The verb part of the data area is any one of an action verb part, a response verb part, and a request verb part,
The action verb unit includes at least one of Sync, Change, Cancel, Process, and Notify,
The response verb part is SyncResponse, ChangeAcknowledge, CancelAcknowledge, Acknowledge, Show, Notify, Confirm. comprising at least one of
The data integration system for the smart factory including the request verb (Request verb) get (Get).
9. The method of claim 8,
The action verb part includes an action criterion,
The action criteria is a data integration system for a smart factory comprising at least one of an action expression (Action Expression) and a change status (Change Status).
10. The method of claim 9,
The verb part of the data area includes a response verb part,
The response verb part includes a response criterion,
The response criteria is a data integration system for a smart factory that includes at least one of a processing result (actionCode) of information received by a previous request message and a content to be returned (Xpath).
11. The method of claim 10,
The verb part of the data area includes a request verb part,
The request verb is a data integration system for a smart factory, which is a verb used when requesting specific data of a receiving application.
12. The method of claim 11,
A data integration system for a smart factory including a noun part of the data area including a field part and a referenced field part.




delete delete

Images