The present disclosure generally relates to the field of industrial automation control systems. Various embodiments of the teachings herein include computer-implemented methods and/or apparatus for transforming an industrial standard specification into at least one rule for amending an information model of an industrial automation control system.
Industrial automation control systems are designed to capture real-world instrumentation data, e.g., sensor data and actuate responses in real time, while operating reliably and safely. To components ensure seamless interaction 41 of involved within industrial automation control systems, conformity with industrial standards is required for such components. Conformity with current industrial standards is particularly necessary for communicative and software-technical behavior of components operating within or controlling the industrial automation control systems. In recent times, semantic web technologies including a usage of semantic information models have gained a predominant role in specifying communicative aspects of such components.
Information modelling is a key concept in the quest to enable industrial automation control systems not only to deliver or consume data but also the express a meaning of data. While this idea is still far from being globally realized, semantic web communities have produced industrial automation standards such as RDF, RDFS, OWL, SPARQL, etc. along with a large number of tools to efficiently create, store and query information models.
Industrial automation standards are set out in specification documents which are intended for human reading. These specification documents pertaining to the semantics of automation control systems and components usually contain thousands of pages of textual information. Some standardization bodies also offer machine-readable snippets of information models for download and for use in software development projects with the aim of easing a standard-compliant implementation of the industrial automation standard. Such machine-readable snippets, however, only represent implementation examples which are not constitutive for standard-compliant implementations.
In other words, these specifications are entirely defined in a textual format intended for human reading, particularly aimed at semantic experts as a target group, which means that solely semantic experts are able to understand these specifications and use their teaching for implementing semantic rules tailored to a given industrial automation system. There is currently no automated way of extracting information from industrial automation standards documents and formalizing it in a meaningful manner.
Further, an implementation of industrial automation standards in an industrial automation control system requires both, semantic expertise for understanding and using semantic descriptions, and process skills of the specific industrial automation control system. Consequently, even the configuration for onboarding components within the industrial automation control system is challenging for a process engineer without special expertise in coding or amending formal semantic rules.
Accordingly, there is a need in the art for a standard-compliant implementation of semantic rules tailored to a given industrial automation system whereby the implementation process is at least partially severed from the burden of conceptually comprehending extensive corpora of present standard specification documents. Further, there is a need in the art for re-using existing standard-compliant semantic rule patterns, enabling amendments without needing to understand or re-code the underlying semantic descriptions. Still further, there is a need in the art for supporting a process engineer in configuring a component for onboarding or maintaining an industrial automation control system without particular knowledge in coding semantic descriptions.
The teachings of the present disclosure include methods and/or systems for transforming an industrial standard specification into one or more semantically constrained rules. The rules are compliant with the industrial standard and may be used for amending an information model of an industrial automation control system. As an example, a method incorporating teachings of the present disclosure may comprise:
The objects as well as further advantages of the teachings of the present disclosure will become more apparent and readily appreciated from the following description of the example embodiments, taken in conjunction with the accompanying drawing accompanying drawing of which:
Teachings of the present disclosure include methods and/or systems for transforming an industrial standard specification into at least one instantiated rule are disclosed. At present, industrial automation standards such as OPC UA, or IEC standards (e.g., IEC 61850), etc., are specified in specification documents intended for human reading. These specification documents pertaining to the semantics of automation control systems and components usually contain thousands of pages of textual information. The specification documents are defined in a textual format intended for human reading. The IEC 61850 standard of the International Electrotechnical Commission (IEC) describes a general transmission protocol for protection and control technology in the industrial automation domain. The series of standards include general specifications for automation systems, functions and devices and for the exchange of information for protection, monitoring, control, and measurement purposes.
OPC UA (Open Platform Communications Unified Architecture) is an industrial standard protocol of the OPC Foundation for with the purpose of manufacturer-independent communication interchanging industrial data in process automation. The protocol OPC UA defines a manufacturer-industrial standard independent information model and communication amongst components industrial automation control system with the purpose of interchanging industrial data in process automation. OPC UA define semantics in the form of documents and information models by a multiplicity of both, domain-independent and domain-specific semantics in order to enable interoperability between industrial machines.
These standard specification documents usually contain thousands of pages of textual information. For example, the OPC UA core specification alone contains around one thousand pages of information. Moreover, OPC UA also defines companion specifications to further define domain-specific semantics for a growing number of specific domains. Currently there are 28 companion specifications available, and this number is increasing significantly every year.
The information such as the semantics, the rules that should be fulfilled by the industrial components, or machines to use these standards are all defined in these specifications. Typically, only experts can understand them and use them. Currently there is no automated way to extract this valuable information from the industrial standard documents and formalize it in a meaningful manner.
To date, the formalization of semantics or validation of rules from the industrial standard documents has been done manually in a tedious and time-consuming manner. Moreover, only experts having a deep knowledge of the standards are able to implement the standards in information models of a given automation control system. Still further, a significant amount of time and effort is required to automate the process of validation of information models based on the industrial standards. First of all, the rules defined in the standards in textual format have to be identified by an expert. After that, these rules have to be formalized using a machine understandable language.
Consequently, existing information models have to be validated against the formalized rules. This process is extraordinary laborious, since the standards are voluminous with thousands of pages of specification. Moreover, the standard specification may be supplemented with application examples or accompanying specification documents, as it is the case with companion specifications of the OPC UA standard. Although these companion specifications are domain-specific, particular companion specifications may be mandatory for particular domains. As a result, the procedure described above may have to be repeated for a multiplicity of companion specifications.
In case of OPC UA, an OPC UA expert has to manually identify the rules in the base specification and a semantic expert has to formalize a part of the identified rules in a standardized semantic web language, using validation instruments for validating graph based OPC UA data against a set of conditions.
The exemplary embodiments described below aim to automate this lengthy and labor-intensive process at least partially and thus to make it much more efficient.
At Step S1 at least one text corpus CPS pertaining to an industrial standard specification is loaded into a memory assigned to a semantic processing module. The text corpus CPS may include specifications in a textual format pertaining to an industrial standard such as OPC UA, or IEC standards (e.g., IEC 61850), etc. The human-readable text corpus CPS is loaded into the memory in a machine-readable manner or, if necessary, rendered machine-readable from paper documents using document digitalization technologies including scanning and OCR (optical character recognition) techniques.
At Step S2 the one or more text corpora CPS are semantically processed by a semantic processing module to identify one or more textual rule blocks TRB and to extract at least one of said textual rule blocks TRB. A user UR2, particularly a semantic expert UR2, may be involved in the process of reviewing extracted and classified textual rule blocks.
Step S2 comprises semantically processing, by a semantic processing module, the one or more text corpora CPS of the industrial standard specification to identify one or more textual rule blocks TRB and to extract at least one of said textual rule blocks TRB.
In some embodiments, industrial standard core specifications may refer to companion specifications and vice versa. Domain-specific vocabularies and/or semantics as defined in the core specification are used across one or more companion specifications while one or more companion specifications may additionally define their own domain specific vocabularies and/or semantics. In order to deal with this type of intersectional or dynamic relationships situations, the processing may dynamically identify domain-specific information in more than one text corpus—e.g., comprising a core specification and one or more companion specifications—in order to add the identified domain-specific information to one of the text corpora CPS during—or won the fly«—the semantically processing.
In some embodiments, unstructured data within the specifications may be accessed by an extraction module. The extraction service may parse unstructured data while also associating the source document with the unstructured data. The parsed unstructured data may be sent to a capture schema and then sent to one or more commercial, open source, or custom developed transformation components capable of extracting individual pieces of data from unstructured text, determining the topic of a section, extracting a section of text from a whole document, matching names and addresses, and other text and data processing activities.
In order to dynamically identify domain-specific information in the specification documents and adding domain-specific information to one or more text corpora during the extraction process, the extracted data may be combined with data already extracted by the optional capture schema.
In some embodiments, an extraction algorithm of the semantic processing module is trained with presently or previously standard specification text corpora and reviewed or trained with respect to its results, textual rule blocks TRB as eventually inferred by this step S2. The extracted textual rule blocks TRB may be reviewed by a semantic expert UR2 expert, judged with respect to the quality of the extraction process and used to improve the algorithm of the extraction process.
In some embodiments, rules within the specification of an industrial standard specification may be manually identified, classified, and formalized by the semantic expert UR2. These formalized rules may be used as a gold standard for training the extraction algorithm or for simply comparing the humanly selected rules with rules extracted and/or classified by the method according to the present embodiments.
In a subsequent step S3 a textual rule blocks TRB is classified, by a classification module, into one or more of a plurality of rule categories in order to obtain a classified textual rule block CTB.
In some embodiments, one or more rule categories are provided, wherein one or more rule categories are used for a classification of constraints or rules in the industrial standards. These rule categories may be previously defined and may include:
The previous example declares that nodes conforming to the shape targetClass must have a property sh: path with a reference to a path referenced by a reference or rather placeholder <Reference_name>. Further on, the nodes must conform to a property sh: minCount whose values must conform with a minimum count or minCount referenced by a variable <minCardinality> and to a property sh: maxCount whose values must conform with a maximum count or maxCount referenced by a variable <maxCardinality>. Nodes conforming to this shape further must have a property sh: message being a string referenced by <violation_message_string>. The following section shows a SHACL sharp template for validating the datatype rule shown above:
The previous example declares that nodes conforming to the shape targetClass must conform to a datatype property sh: datatype which specific property value is referenced by a reference entitled <xsd_datatype>.
Based on the rule categories assigned to the classified textual rule block CTB, one or more rule templates RLT may be automatically assigned to a classified textual rule block CTB. The resulting rule templates RLT are the formalized rule templates.
At step S5 the rule template RLT is instantiated, by a—not shown—instantiating module, to eventually obtain the instantiated rule IRL. In the process of instantiating the instantiating module adapts the rule template RLT by constraints of the information model of the industrial automation control system to obtain the instantiated rule IRL.
In some embodiments, these formalized rule templates RLT may be presented to a user in a visual format. This user interface is adapted to meet skills of the user URI, which may not be familiar in understanding the formalized rule templates as formulated in a SHACL sharp template shown above. Thus, an editable representation of the rule template being adapted by said constraints of the information model is presented to the user URI by a user interface defined by the instantiating module. The instantiating module consequently receives at least one input from the user URI to form an amended rule template RLT and, eventually, an input by the user concluding the instantiation.
In some embodiments, an additional input may be provided by the user UR1 categorizing the rule template RLT as a formalized rule template.
In
Using the user interface as shown, a cardinality rule template may be instantiated according to the following example of an instantiated cardinality rule:
The previous example of an instantiated cardinality rule shows the effect of instantiation: references-which have been noted in <angle brackets>—of the previous example of the non-instantiated cardinality rule are now resolved in favor of instantiated values, e.g.:
Number | Date | Country | Kind |
---|---|---|---|
21191461.9 | Aug 2021 | EP | regional |
This application is a U.S. National Stage Application of International Application No. PCT/EP2022/071904 filed Aug. 4, 2022, which designates the United States of America, and claims priority to EP application Ser. No. 21/191,461.9 filed Aug. 16, 2021, the contents of which are hereby incorporated by reference in their entirety.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/EP2022/071904 | 8/4/2022 | WO |