Engineering system and method for arranging engineering software for factory automation environments

Abstract

An engineering system and method for arranging engineering software for a factory automation environment are disclosed. The engineering system (100, 260) for the factory automation environment (270) includes a message broker (140, 210) configured to access and update a knowledge base (125, 230) based on the execution of at least one of a plurality of engineering software (112, 262, 266, 268), wherein the plurality of engineering software (112, 262, 266, 268) is configured to generate and / or execute engineering data associated with at least one of design, commissioning, operation, and maintenance of the factory automation environment (270), wherein A message broker (140, 210) is configured to convert engineering data into messages recognizable by a plurality of engineering software (112, 262, 266, 268) and a knowledge base (125, 230); and at least one graphical user interface (GUI) communicatively coupled to the message broker (140, 210) is configured to enable access to the engineering data via the message broker (140, 210), whereby at least one engineering software (112, 262, 266, 268) is configured to initiate an action in a factory automation environment (270) based on the message.

Description

Technical Field

[0001] The present invention relates to the engineering of industrial automation equipment and systems in a factory automation environment, and more particularly to engineering software arranged to be used to engineer such equipment and systems. Background Art

[0002] Engineering industrial / factory automation systems in a factory automation environment can be complex given the multiple software packages that may be used for their design, configuration, debugging, and generally engineering. Often, engineering software may be limited to certain areas or disciplines and may not provide engineers with all the information they need.

[0003] Expert engineering systems for multidisciplinary / multi-domain data may require data from multiple engineering software to be in specific formats. As a result, such expert engineering systems may be inflexible and limited to a limited domain.

[0004] Artificial intelligence (AI) is increasingly being used in factory automation environments. For example, in the context of production automation, AI-based system engineering may require one or more AI technologies and workflows that interact with them. Furthermore, AI-based engineering may also involve one or more types of databases that allow for meaningful conclusions to be drawn based on correlations between engineering data from the automation environment and / or engineering software. The multiple AI technologies and associated databases used for AI-based engineering can further complicate engineering automation equipment and systems.

[0005] Therefore, such engineering systems and methods that enable seamless communication between engineering software may benefit from improvements. Summary of the Invention

[0006] The object of the present invention is to enable flexible, scalable and seamless engineering of automation devices and systems by linking / arranging engineering software for such engineering.

[0007] For example, the object is achieved by an engineering system for a factory automation environment. The system includes: a message broker configured to access and update a knowledge base based on the execution of at least one of a plurality of engineering software programs, wherein the plurality of engineering software programs are configured to generate and / or execute using engineering data associated with at least one of design, commissioning, operation, and maintenance of the factory automation environment, wherein the message broker is configured to convert the engineering data into messages recognizable by the plurality of engineering software programs and the knowledge base; and at least one graphical user interface (GUI) communicatively coupled to the message broker and configured to enable access to the engineering data via the message broker, whereby the at least one engineering software program is configured to initiate an action in the factory automation environment based on the message.

[0008] In another example, the objective is achieved by arranging a plurality of engineering software programs associated with a factory automation environment. The plurality of engineering software programs include different data structures and syntaxes. The method includes: accessing a knowledge base of the factory automation environment based on the execution of at least one of the plurality of engineering software programs, wherein the plurality of engineering software programs are configured to generate and / or execute using engineering data associated with at least one of the design, commissioning, operation, and maintenance of the factory automation environment; converting the engineering data into messages recognizable by the plurality of engineering software programs and the knowledge base; enabling access to the engineering data based on the sending and receiving of messages; and enabling at least one of the engineering software programs to initiate an action in the factory automation environment based on the message. For example, enabling a user to initiate an action in the factory automation environment based on the message.

[0009] Yet another example includes a computer program product comprising computer readable code that, when executed on a processor, performs any of the method steps of one or more methods herein.

[0010] The present invention may also include an AI-based engineering system configured to support the engineering of automated equipment and systems based on the changing needs of engineers. The AI-based engineering system may include a knowledge database configured to store engineering data generated by engineering software in a distributed manner across multiple computing devices. The AI-based engineering system may also include AI methods / AI modules configured to operate based on the knowledge database. The AI ​​modules can be individually configured to function differently from one another, thereby generating different results. Thus, the different results from the AI ​​modules can be advantageously integrated and provided to engineers.

[0011] The engineering system advantageously provides seamless integration of several AI modules / AI methods in conjunction with a distributed knowledge base. The technical benefit of this integration / arrangement is that engineers can leverage the strengths of individual AI modules in a flexible and scalable manner. The flexibility and scalability of the present invention facilitates the integration of new engineering software / AI modules. For example, if a new AI module is being used to commission automation equipment in a factory automation environment, engineers do not need to reconfigure the system.

[0012] Before describing the proposed conventions in greater detail, it should be understood that various definitions of certain words and phrases are provided throughout this patent document, and those skilled in the art will understand that such definitions apply in many, if not most, cases to prior as well as future uses of such defined words and phrases. While some terms may include a wide variety of embodiments, the appended claims may expressly limit such terms to specific embodiments. It should also be understood that features explained in the context of the proposed method may also be included in the proposed system by appropriately configuring and adjusting the system, and vice versa.

[0013] As used herein, a "factory automation environment" refers to a semi-automated or fully automated manufacturing or production facility. In addition to the facility, a factory automation environment also includes the engineering software used to design and engineer the facility. Furthermore, a factory automation environment may include automation engineers who use the engineering software. Automation equipment and systems may be part of a factory automation environment. A factory automation environment may also be referred to as an industrial automation environment or a laboratory automation environment.

[0014] As used herein, engineering software is a software tool that allows engineers from multiple disciplines to work with common or connected engineering data. Many engineering software are associated with factory automation environments. A plurality of engineering software is configured to generate and / or operate using engineering data associated with at least one of the design, commissioning, operation, and maintenance of the factory automation environment. For example, in a factory environment, a factory planner may work with a mechanical engineer, an electrical engineer, and an automation engineer to plan a new production line for door assemblies. When an automation engineer introduces a new programmable logic controller (PLC) into a project, the information is stored in a knowledge base as engineering data. A plurality of engineering software receives user input and causes computer-aided design software to act. A plurality of engineering software may include engineering software related to electrical, mechanical, process technology, software, and other subordinate elements from different engineering disciplines.

[0015] As used herein, a "knowledge base" refers to one or more databases configured to store engineering data associated with a factory automation environment. For example, the knowledge base includes at least a graph-based database, an ontology database distributed within the factory automation environment, and a cloud computing platform. The knowledge base can be updated using a data integration module. A message broker can be communicatively coupled to the data integration module, which is configured to integrate engineering data from multiple engineering software into the knowledge base. Depending on the confidentiality of the engineering data and the location of the databases, the engineering data can be indexed in each database or selectively indexed into a single database. For example, the ontology database can be located along with the factory automation environment on a private network associated with the factory automation environment. High-frequency sensor data associated with a rotating system in a factory automation environment can be stored in the ontology database compared to a knowledge graph database hosted on a cloud computing platform.

[0016] The present invention advantageously provides an engineering system capable of providing access to and updating engineering data from a knowledge base. This is achieved using a message broker, which is configured to access and update the knowledge base and then execute operations in any of the engineering software. The message broker is configured to generate messages that are transmitted between the engineering software, the knowledge base, and the engineer via a GUI. The message broker can be configured to generate messages according to a message format that can be interpreted by multiple engineering software, knowledge bases, and GUIs (collectively referred to as the interactive system). In addition, the knowledge base, GUI, AI module, and multiple engineering software are registered as subscribers and / or publishers of the message broker in a modifiable manner. For example, the message broker can be configured to operate as a message queue-based middleware for message exchange. Therefore, the message broker can serve as a dedicated message bus communicatively connected to the interactive system. The engineering software, knowledge base, and GUI can serve as multi-directional publishers and subscribers of the message broker. Therefore, the message broker can be configured to implement multi-directional transmission of messages from the rule engine, GUI, and AI module based on a unified message queue.

[0017] In an embodiment, a message broker is configured to project data based on message content and message exchange parameters. Message exchange parameters include the conditions under which messages are sent and received. The publisher of a message (such as engineering software) can use a unique message identifier, which can be used by the knowledge base and the GUI for reference. Thus, the message identifier ensures that sequences and collections of messages are uniquely identifiable. Consequently, notifications displayed on the GUI are associated with the most relevant user interactions or operations.

[0018] In another embodiment, the interactive system may not be a subscriber to all messages published by the message broker. For example, messages sent to engineers may only require messages directed to the GUI. In addition, the GUI can be configured to subscribe to messages including prompts for displaying notifications or related engineering data. Therefore, the message broker can advantageously be configured to implement customizable filters at the message exchange point or via additional message exchange points. In an embodiment, filters can be generated based on the type of participant (such as engineering software, GUI, data integration module) and the message format (e.g., question, answer, recommendation).

[0019] Access to engineering data provided by the message broker enables engineers to initiate actions within the factory automation environment. For example, a message from one of the engineering software programs may provide an updated configuration for an automation device, such as a robot. The engineer may be notified of this new configuration via the GUI. The engineer may then update the robot's configuration based on this notification.

[0020] In one embodiment, the message broker is configured to receive engineering data from a rule engine associated with a plurality of software. As used herein, the rule engine may be configured based on industry standards and / or manufacturing requirements. In one embodiment, the rule engine may be configured using the IEC 61499 standard. The IEC 61499 standard relates to distributed control and automation based on event triggers in an automation environment. In another embodiment, the ISO 26262 standard for road driving system safety may be used to configure the rule engine. As described above, the industry standard depends on the industry associated with the factory automation environment.

[0021] For example, the engine uses configuration engineering software to configure automated equipment to respond to multiple emergency stops. Emergency stops can be linked to input / output tags, program blocks, and user interface blocks. When adding a new emergency stop, it may be necessary to generate input / output tags, program blocks, and user interface blocks. If an engineer inadvertently omits the generation of a user interface block, the rules engine associated with the engineering software will recognize this omission. Furthermore, the rules engine can be configured to send engineering data to the knowledge base as a message indicating this omission.

[0022] In an embodiment, the rule engine may be further configured to access the knowledge base via a message broker. Considering the above example, the rule engine may be configured to determine the correlations and dependencies between the new emergency stop and the associated tags and blocks. By determining the correlations and dependencies, the rule engine identifies the user interface block submitted by the engineer. The rule engine may also be configured to publish a message indicating the location in the GUI associated with the user interface block to notify the engineer of the generation of the message. In another embodiment, the rule engine may be configured to publish a message to engineering software, thereby triggering the automatic generation of the user interface block.

[0023] In an embodiment of the present invention, a message broker is communicatively coupled to one or more AI modules configured to analyze the operation of a plurality of engineering software, user input from a GUI, or a combination thereof. The AI ​​modules may include neural network modules, reinforcement learning modules, rule-based modules, and combinations thereof. For example, a rule engine associated with engineering software for configuring emergency stops may be a rule-based module. The rule-based module may be configured to activate when an additional emergency stop is introduced for a particular automated device. Thus, the rule-based module may be configured based on rules generated according to industry standards. In another example, rules may also be generated based on coding guidelines associated with a knowledge base.

[0024] The AI ​​module can be configured to map the execution of multiple engineering software programs, user input, or a combination thereof to engineering data in a knowledge base. The message broker sends the mapped engineering data to at least one engineering software program, enabling the at least one engineering software program to initiate an action in the factory automation environment.

[0025] In order to efficiently access the knowledge base, the AI ​​module or rule engine can be configured to publish messages in a classifiable message format, such as a message format classified into a query format, a response format, a recommendation format, and an action format. In an embodiment, an engineer's operation can trigger a message in a question format, which has associated engineering data for querying the knowledge base. For example, an engineer will not generate a user interface block for an emergency stop. Similarly, the knowledge base, the GUI, and multiple engineering software are also configured to publish and / or receive messages in the above-mentioned message format. Therefore, in the engineering system disclosed in the present invention, messages are received and sent in one or more message formats, which are classified into a query format, a response format, a recommendation format, and an action format.

[0026] The present invention advantageously provides a method for orchestrating multiple pieces of engineering software associated with a factory automation environment. As used herein, "orchestrating multiple pieces of engineering software" refers to the integration of engineering data generated by the execution of the engineering software. Furthermore, orchestration integrates dependencies between individual pieces of engineering software and engineering data. Furthermore, orchestration refers to the automated placement and coordination of the engineering software via a message broker.

[0027] According to the method, a knowledge base is accessed based on the execution of at least one engineering software among a plurality of engineering software. The execution executed in the at least one engineering software can be mapped to the knowledge base. In an embodiment, engineering data associated with the execution is updated in the knowledge base.

[0028] Thus, the method according to the present invention captures the actions, operations, and interactions between engineers and multiple engineering software in a tangible, searchable form. To enable access to and operations within a knowledge base, engineering data is converted into messages that can be recognized by the multiple engineering software and the knowledge base. Messages are sent and received between the multiple engineering software and the knowledge base using a message broker. By converting engineering data into messages, engineers can obtain comprehensive engineering information from multiple engineering software. This enables engineers to initiate operations within a factory automation environment. In one embodiment, when an engineering software is triggered by one or more messages from other engineering software within the multiple engineering software or from the knowledge base, an action can be automatically initiated.

[0029] The method may include integrating engineering data from a plurality of engineering software into a knowledge base. Furthermore, the method may include analyzing the operation of the plurality of engineering software, user input from a GUI, or a combination thereof using at least one of a neural network, reinforcement learning, and rule-based logic. By analyzing the operation, engineer interaction, or input provided by an engineer / user, relevant engineering data from the knowledge base may be accessed. Thus, the method may include mapping the operation of the plurality of engineering software, user input, or a combination thereof to engineering data in the knowledge base, wherein a message broker sends the mapped engineering data to at least one engineering software to enable the at least one engineering software to initiate an action in the factory automation environment.

[0030] In an embodiment, the operations, user outputs, and combinations thereof may be mapped to the engineering data by determining dependencies between the engineering data in the knowledge base and the operations, user inputs, and combinations thereof. For example, the dependencies may be determined using pattern matching neural networks, reinforcement learning, or pattern-based rules.

[0031] The method may include displaying a notification on a GUI associated with at least one engineering software, the notification indicating an action to be initiated within the factory automation environment, wherein the action and the notification are transmitted as messages recognizable by the GUI, the plurality of engineering software, and a knowledge base. For example, the action may include configuring only a system, subsystem, or component of automation equipment and systems within the factory automation environment. Thus, the method may include engineering the system, subsystem, or component based on the action received as a message by the GUI. The method may also include reconfiguring the system, subsystem, or component based on the action received as a message by the GUI.

[0032] The advantage of the present invention is that it links several AI methods in the context of factory automation. The engineering system and method are advantageously adapted to the specific requirements of the AI ​​methods while being flexible.

[0033] The foregoing has provided a fairly broad overview of the technical features of the present disclosure so that those skilled in the art may better understand the detailed description that follows. Additional features and advantages of the present disclosure that form the subject of the claims will now be described. Those skilled in the art will appreciate that they can readily use the disclosed concepts and specific embodiments as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Those skilled in the art will also recognize that such equivalent constructions do not depart from the scope of the present disclosure in its broadest form. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Hereinafter, the present invention will be described using the embodiments shown in the drawings.

[0035] Figure 1 An engineering system for a factory automation environment according to an embodiment of the present invention is shown;

[0036] Figure 2 An engineering system for a factory automation environment according to an embodiment of the present invention is shown; and

[0037] Figure 3 A method of arranging one or more engineering software to engineer automation devices and systems in a factory automation environment according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0038] Hereinafter, embodiments for implementing the present invention will be described in detail. Various embodiments are described with reference to the accompanying drawings, wherein like reference numerals are used throughout to refer to like elements. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more embodiments. Obviously, such embodiments may be practiced without these specific details.

[0039] Figure 1 An engineering system 100 for a factory automation environment according to an embodiment of the present invention is shown. The engineering system 100 includes an extraction subsystem 110, a data integration module 122, a knowledge base 125, a rule module 130, a message broker 140, and a user interface 150.

[0040] The extraction subsystem 110 includes a plurality of software programs 112 and a data extraction module 114 associated with the engineering software 112. As previously mentioned, the engineering software 112 can be used for the design, commissioning, operation, and maintenance of factory automation environments. Engineering software includes simulation software, computer-aided design software, finite element analysis (FEA) software, cause-and-effect mapping software, piping and instrumentation diagram (PI&D) software, and the like. Furthermore, the data extraction module 114 may include pattern-based modules, machine learning modules, reinforcement modules, and similar AI modules. The extraction subsystem 116 also includes an ontology editor module 116 and a graph editor module 118.

[0041] The data integration module 122 is communicatively coupled to the data extraction module 114 and the knowledge base 125. The knowledge base 125 includes an ontology database 124 and a knowledge graph database 126. The ontology database 124 is communicatively coupled to the ontology editor module 116, and the knowledge graph database 126 is communicatively coupled to the graph editor module 118. In an embodiment, the data integration module 122 and the knowledge base 125 are implemented on the cloud computing platform 120.

[0042] The extraction subsystem 110, data integration module 122, knowledge base 125, and user interface 150 are configured to communicate with each other using a message broker 140. The message broker 140 is communicatively coupled to a rules module 130, which is configured to define rules for communication between the automation engineering software 112, the data extraction module 114, the user interface 150, and the message broker 140. The rules module 130 includes a configuration rules engine 132, which is used to generate message rules for hardware configuration software used to configure hardware in a factory automation environment. The rules module 130 also includes an interface rules engine 134, which is used to generate message rules for the user interface 134. The rules module 130 further includes a recommendation rules engine 136, which is used to generate message rules for recommendation engineering software that recommends the latest hardware and software versions for automation devices in the factory automation environment. The rules module 130 also includes a software rules engine 138, which is used to configure controller software for controllers in the factory automation environment.

[0043] Engineers engineering a factory automation environment can use user interface 150 to access knowledge base 125. Additionally, an administrator or any user can use user interface 150 to customize rule module 130, ontologies in ontology database 114, and visualize knowledge database 126 via ontology editor 116.

[0044] During initialization, the data extraction module 114 is configured to populate the knowledge graph database 126. For example, semantic information about ontologies associated with the factory automation environment is used to populate the knowledge graph database 126. Ontologies provide definitions of concepts and relationships between engineering data. Engineering ontologies can be constructed based on existing ontology standards in the field. For example, the IEEE 1872-2015 Standard Ontology for Robotics and Automation (IEEE-SA, 2015) establishes a series of ontologies for robotics and automation. In another example, the Ontology for Industry 4.0 (O4I4) is specifically designed to capture domain concepts specific to Industry 4.0.

[0045] During operation, data extraction module 114 is configured to extract engineering data related to different disciplines from the plurality of engineering software 112. For example, data extraction module 114, including an AI module, is configured to analyze the operation of engineering software 112, user input from user interface 150, or a combination thereof. Based on the analysis, data extraction module 114 publishes the engineering data as messages to message broker 140.

[0046] Data integration module 122 is configured to integrate the engineering data extracted by data extraction module 114 into ontology database 124 and knowledge graph database 126. This integration operation can be performed by generating additional links in knowledge graph database 126 to store the extracted engineering data. Data integration module 122 can be configured to map the extracted engineering data associated with the operation and / or user input to knowledge base 125. Based on this mapping, a notification can be generated as a message to user interface 150.

[0047] The message broker 140 is configured as a message queue-based middleware for message exchange. Engineering data extracted by the data extraction module 114 is converted into messages and published to the message broker 140. Messages may also include message types or formats, such as questions, answers, recommendations, and automated engineering actions. Based on the sent and received messages, the at least one engineering software 112 is configured to initiate actions within the factory automation environment based on the messages.

[0048] During operation, the data extraction module 114, the data integration module 122, the knowledge base 125, and the user interface 150 can be registered as "consumers" / "subscribers" for certain messages and "publishers" for certain "channels and sub-channels." Channels and sub-channels can include filters to enable consumers to subscribe to specific messages (project data) of interest.

[0049] For example, a message might include the following:

[0050] Publisher, associated engineering data, subscribers, user input / execution performed in engineering software 112, metadata associated with user input / execution (such as previous runs), current engineering software used, semantics of user input, response from knowledge base 125, semantics of response.

[0051] The message broker 140 can also be used to configure messages. For example, a new message provider or a newly registered publisher can transmit the structure of a message to the message broker 140. In another example, the rule module 130 is configured to generate a message structure and publish the message structure to providers and subscribers. The message structure can be read by subscribers registered with the message broker 140. In addition, publishers and subscribers can cancel certain channels of the message broker 140. In addition, subscribers can receive standardized message text indicating that a channel is no longer in service. Therefore, the data extraction module 114, the data integration module 122, the knowledge base 125, and the user interface 150 can be linked in a highly flexible manner.

[0052] Figure 2 An engineering system 260 for a factory automation environment 270 according to an embodiment of the present invention is shown. The engineering system 260 is configured to execute one or more engineering software applications 262, 266, and 268. For example, the engineering software applications are process engineering software 262 and associated process ontology editor 264, simulation software 266, and project scheduling software 268. Those skilled in the art will appreciate that ontology editors or knowledge graph editors can be plugged into the simulation software 266 and the project scheduling software 268. Ontology editors, such as the process ontology editor 264 and the knowledge graph editor, can be configured as data extraction modules 114.

[0053] The engineering system 260 may also include a message broker 210 configured to receive engineering data from software applications 262, 266, and 268 via an ontology editor and a knowledge graph editor. For example, an engineer may use the process engineering software 262 to add an additional process element 265. The process ontology editor 264 is configured to map the engineer's execution to the engineering data associated with the process element 265. The process ontology editor 264 publishes a message to the message broker 210 containing the engineering data associated with the process element 265, metadata associated with the execution of the added process element 265, input / output tags of the process element 265, and the like.

[0054] In an embodiment, the factory automation environment 270 may include a knowledge base 230 including an ontology database 232. The knowledge base 230 is configured to store engineering data and ontology rules associated with the factory automation environment 270. The knowledge base 230 may be distributed across multiple devices within the factory automation environment 270.

[0055] Engineering system 260 is configured to communicate with cloud computing platform 250. Cloud computing platform 250 includes multiple modules 210, 220 and a database 230 hosted and deployed in a distributed computing environment. For example, cloud computing platform 250 includes an AI integration module 220 configured to integrate engineering data extracted by the ontology editor and the knowledge graph editor. AI integration module 220 is configured to update knowledge base 230 by updating ontology database 232 and / or knowledge graph database 234.

[0056] The knowledge base 230 hosted on the cloud computing platform 250 may be a copy of the knowledge base 230 hosted within the factory automation environment 270. In an embodiment, the factory automation environment 270 may include a controller to determine which engineering data may be copied / transferred to the knowledge base 230 on the cloud computing platform 250. Those skilled in the art will appreciate that the knowledge base 230 is distributed across both the factory automation environment 270 and the cloud computing platform 250.

[0057] In an embodiment, engineers can directly access knowledge base 230 using user interface 240. User interface 240 can be a web-based graphical user interface configured to receive input from engineers (user input). The user input is published to message broker 210 and subscribed to by knowledge base 232. Knowledge base 230 is configured to publish responses to the user input as messages to message broker 210. The responses can also be published to engineering software 262, 266, 268 to trigger one or more actions in the engineering software. For example, process element 265 can be automatically configured based on the responses from knowledge base 230.

[0058] In another embodiment, the addition of the execution of process element 265 is published as a message to message broker 210. Simulation software 266 is configured to subscribe to messages associated with process element 265. Furthermore, simulation software 266 is configured to determine configuration parameters for process element 265 based on a simulation of factory automation environment 270. These configuration parameters are published as messages to message broker 210 and subscribed to by process engineering software 262. A notification can be displayed to the engineer on graphical user interface 240 indicating the configuration parameters. Alternatively, process engineering software 262 can be triggered to automatically configure process element 265 based on the configuration parameters published by simulation software 266. Those skilled in the art will also appreciate that process scheduling software 268 can be used in a similar manner.

[0059] For example, an engineer is scheduling / inquiring about the paint formula production process for automotive paint via process scheduling software 268. Simulation software 266 is triggered by an inquiry based on the inquiry message published to message broker 210. In response, simulation software 266 simulates the time required to produce the first batch of paint and publishes a simulation message to message broker 210. Simulation message 210 is displayed as a notification to the engineer scheduling the paint formula production.

[0060] Figure 3 A method 300 for arranging one or more engineering software to engineer automation devices and systems in a factory automation environment according to an embodiment of the present invention is shown. The method begins at step 310, where a knowledge base of the factory automation environment is accessed based on the execution of at least one engineering software. The engineering software is configured to generate and / or execute engineering data associated with at least one of the design, commissioning, operation, and maintenance of the factory automation environment.

[0061] Step 310 includes analyzing the operation of a plurality of engineering software, user input from a web-based GUI, or a combination thereof through at least one of a neural network, reinforcement learning, and rule-based logic. The analysis enables efficient access to a knowledge base.

[0062] Operations and user input are transmitted to the knowledge base in the form of messages. Therefore, step 320 includes converting the engineering data into messages recognizable by the plurality of engineering software and the knowledge base. The knowledge base uses the messages to map the operations and / or user input to the engineering data stored in the knowledge base. Step 320 may also include mapping the operations of the plurality of engineering software, user input, or a combination thereof to the engineering data in the knowledge base. For example, step 320 includes determining dependencies between the engineering data in the knowledge base and a pattern matching neural network, reinforcement learning, or pattern-based rules based on the operations, user input, and the combination.

[0063] Effectively sending and receiving messages via the message broker is equivalent to updating and retrieving engineering data in the knowledge base. Therefore, step 330 includes implementing access to engineering data based on sending and receiving messages.

[0064] The message broker sends the mapped engineering data in the knowledge base as a notification message to at least one engineering software to enable the at least one engineering software to initiate an action in the factory automation environment. Therefore, step 340 includes enabling the at least one engineering software to initiate an action in the factory automation environment based on the message. Step 340 includes displaying a notification on a GUI associated with the at least one engineering software, the notification indicating the action to be initiated in the factory automation environment. As described above, the action and the notification are transmitted as messages that can be recognized by the GUI, the engineering software and the knowledge base. In addition, step 340 includes initiating an action in the factory automation environment. The action can be initiated by configuring or reconfiguring the automation equipment and components in the factory automation environment. Therefore, step 340 may also include engineering a system, subsystem or component in the factory automation environment based on the action. In addition, step 340 includes reconfiguring the system, subsystem or component based on the action.

[0065] For the purpose of this specification, a computer-usable or computer-readable non-transitory storage medium can be any device that can contain, store, transmit, propagate or transmit a program for use by an instruction execution system, device or equipment or for use in combination with it. The medium can be an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system (or device or equipment), or the propagation medium itself is not included in the definition of a physical computer-readable medium as a signal carrier, including semiconductor or solid-state memory, magnetic tape, removable computer disk, random access memory (RAM), read-only memory (ROM), hard disk and optical disk such as CD-ROM, CD-ROM read / write and DVD. As known to those skilled in the art, the processing unit and program code for implementing each aspect of the present technology can be centralized or distributed (or a combination thereof). In addition, although the index module and crawler platform are currently disclosed as independent components, these modules can be software components and can be implemented in a distributed control system or an engineering software suite. In addition, in an embodiment, one or more parts of the engineering module can be implemented in a technical system.

[0066] Although the present disclosure has been described in detail with reference to certain embodiments, it should be understood that the present disclosure is not limited to those embodiments. In view of the present disclosure, as described herein, many modifications and variations will occur to those skilled in the art without departing from the scope of the various embodiments of the present disclosure. Therefore, the scope of the present disclosure is indicated by the following claims rather than by the foregoing description. All changes, modifications and variations that come within the meaning and range of equivalents of the claims should be considered to be within the scope of the claims. All advantageous embodiments claimed in the method claims are also applicable to the system / device claims.

Claims

1. An engineering system (100, 260) for use in a factory automation environment (270), the system comprising: a message broker (140, 210) configured to access and update a knowledge base (125, 230) based on execution of at least one of a plurality of engineering software (112, 262, 266, 268), wherein the plurality of engineering software (112, 262, 266, 268) is configured to generate and / or execute using engineering data associated with at least one of design, commissioning, operation, and maintenance of the factory automation environment (270), wherein the message broker (140, 210) is configured to convert the engineering data into messages recognizable by the plurality of engineering software (112, 262, 266, 268) and the knowledge base (125, 230); and at least one graphical user interface communicatively coupled to the message broker (140, 210), the at least one graphical user interface configured to enable access to the engineering data via the message broker (140, 210), whereby at least one engineering software (112, 262, 266, 268) is configured to initiate an action in the factory automation environment (270) based on the message, wherein the message agent (140, 210) is communicatively coupled to one or more artificial intelligence modules (220), the one or more artificial intelligence modules being configured to analyze the operation of the plurality of engineering software (112, 262, 266, 268), user input from the graphical user interface, or a combination thereof, wherein the artificial intelligence module is configured to map the operation of the plurality of engineering software (112, 262, 266, 268), the user input, or the combination thereof to the engineering data in the knowledge base (125, 230), wherein the message agent (140, 210) sends the mapped engineering data to the at least one engineering software (112, 262, 266, 268) to enable the at least one engineering software (112, 262, 266, 268) to initiate an action in the factory automation environment (270), the artificial intelligence module comprising one of a neural network module, a reinforcement learning module, a rule-based module, and a combination thereof.

2. The system according to claim 1, wherein: The message broker (140, 210) is communicatively coupled to a data integration module (122, 220) configured to integrate the engineering data from the plurality of engineering software (112, 262, 266, 268) into the knowledge base (125, 230).

3. The system according to claim 1 or 2, wherein: The message broker (140, 210) is configured to receive the engineering data based on a rule engine (130) associated with the plurality of engineering software (112, 262, 266, 268), wherein the rule engine (130) is configurable based on one of an industry standard and a manufacturing requirement.

4. The system according to claim 3, wherein: The message agent (140, 210) is configured to implement multi-directional transmission of messages from the rule engine (130), the graphical user interface (150, 262) and the artificial intelligence module (122, 220) based on a unified message queue.

5. The system according to claim 1 or 2, wherein: The knowledge base (125, 230), the graphical user interface, the artificial intelligence module (122, 220), and the plurality of engineering software (112, 262, 266, 268) are registered as subscribers and / or publishers of the message broker (140, 210) in a modifiable manner.

6. The system according to claim 1 or 2, wherein: The messages are received and sent in one or more message formats, which are categorized into a query format, a response format, a recommendation format, and an action format.

7. The system according to claim 1 or 2, wherein: The knowledge base (125, 230) includes at least a graph-based database (126, 234), an ontology database (124, 232) distributed within the factory automation environment (270), and a cloud computing platform (280).

8. A method of arranging a plurality of engineering software (112, 262, 266, 268) associated with a factory automation environment (270), wherein: The plurality of engineering software (112, 262, 266, 268) include different data structures and syntaxes, and the method includes: accessing a knowledge base (125, 230) of the factory automation environment (270) based on execution of at least one of the plurality of engineering software (112, 262, 266, 268), wherein the plurality of engineering software (112, 262, 266, 268) is configured to generate and / or execute using engineering data associated with at least one of design, commissioning, operation, and maintenance of the factory automation environment (270); Using one or more artificial intelligence modules (220) to convert the engineering data into messages recognizable by the plurality of engineering software (112, 262, 266, 268) and the knowledge base (125, 230), wherein the artificial intelligence module (220) is configured to map the operation of the plurality of engineering software (112, 262, 266, 268), user input, or a combination thereof to the engineering data in the knowledge base (125, 230); enabling access to the engineering data based on sending and receiving the message; and implementing at least one engineering software (112, 262, 266, 268) to initiate an action in the factory automation environment (270) based on the message, wherein the execution of the plurality of engineering software (112, 262, 266, 268), user input from a graphical user interface, or a combination thereof is analyzed via at least one of a neural network, reinforcement learning, and rule-based logic; and The operation of the plurality of engineering software (112, 262, 266, 268), the user input, or the combination thereof is mapped to the engineering data in the knowledge base (125, 230), wherein a message broker (140, 210) sends the mapped engineering data to the at least one engineering software (112, 262, 266, 268) to enable the at least one engineering software (112, 262, 266, 268) to initiate an action in the factory automation environment (270).

9. The method according to claim 8, further comprising: The engineering data from the plurality of engineering software (112, 262, 266, 268) is integrated into the knowledge base (125, 230).

10. The method according to claim 8 or 9, wherein: Analyzing the operation of the plurality of engineering software (112, 262, 266, 268), the user input from the graphical user interface, or a combination thereof includes determining dependencies between the engineering data in the knowledge base (125, 230) and a pattern matching neural network, reinforcement learning, or pattern-based rules based on the operation, the user input, and the combination.

11. The method according to claim 8 or 9, further comprising: A notification is displayed on a graphical user interface associated with the at least one engineering software (112, 262, 266, 268), the notification indicating the action initiated in the factory automation environment (270), wherein the action and the notification are transmitted as the message recognizable by the graphical user interface, the plurality of engineering software (112, 262, 266, 268), and the knowledge base (125, 230).

12. The method according to claim 8 or 9, wherein: The actions initiated in the factory automation environment (270) include: Engineering a system (100, 260), subsystem, or component in the factory automation environment (270) based on the action received as the message by the graphical user interface; and The system, the subsystem, or the component is reconfigured based on the action received as the message by the graphical user interface.

13. A computer program product comprising computer readable code which, when executed on a processor, performs any one of the steps of the method according to any one of claims 8 to 12.

Images