Custom properties in an application environment
US-2016109875-A1 · Apr 21, 2016 · US
US10338551B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10338551-B2 |
| Application number | US-201514951959-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 25, 2015 |
| Priority date | Dec 3, 2014 |
| Publication date | Jul 2, 2019 |
| Grant date | Jul 2, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A computer-implemented method for automatically exchanging data between a piping and instrumentation diagram (P&ID) and a control system comprises: parsing a P&ID and identifying instruments and/or groups of instruments within the P&ID, identifying one or more input tags and output tags associated with each identified instrument and/or with each identified group of instruments within the P&ID, and establishing at least one relationship among the one or more input tags and output tags, wherein the input tags and output tags for an instrument and/or a group of instruments and the at least one relationship between the corresponding input tags and output tags are derivable from a template library, and identifying a control loop for each established relationship among the input tags and the output tags, wherein said control loop is for controlling one or more instruments by the control system.
Opening claim text (preview).
What is claimed is: 1. A method for automatically exchanging data between a piping and instrumentation diagram (P&ID) and a control system, comprising: parsing, by a system comprising at least one processor, a P&ID and identifying instruments within the P&ID based on the parsing; identifying, by the system, a rule, of a set of rules maintained in a template library, corresponding to a group of instruments included in the instruments, wherein the rule defines input tags associated with the group of instruments, output tags associated with the group of instruments, and one or more relationships between the input tags and the output tags; identifying, by the system based on the rule, one or more input tags and one or more output tags associated with the group of instruments; determining, by the system based on the rule, at least one relationship between the one or more input tags and the one or more output tags; identifying, by the system, a control loop based on the at least one relationship between the one or more input tags and the one or more output tags, wherein the control loop is configured to control the instruments in response to execution by the control system; generating, by the system based on an identity of the control loop, executable source code that, in response to execution by the control system, causes the control system to control the instruments in accordance with the control loop; and sending, by the system, the executable source code to the control system. 2. The method of claim 1 , wherein the P&ID is in a machine-readable format. 3. The method of claim 1 , wherein each rule of the set of rules is associated with at least one instrument or at least one group of instruments, and each rule of the set of rules is a predefined part of an integration tool and defines one or more relationships between input tags and output tags for an instrument or a group of instruments. 4. The method of claim 3 , wherein the generating the executable source code comprises generating the executable source code based on a source code template corresponding to one or more of the instruments. 5. The method of claim 1 , wherein the one or more input tags relate to data that is to be input to an instrument of the group of instruments, and the one or more output tags relate to data that is to be output by an instrument of the group of instruments. 6. The method of claim 1 , further comprising: finalizing the control loops based on received control loop parameters to yield finalized control loops; and distributing the executable source code representing the finalized control loops to one or more control modules within an industrial environment. 7. A non-transitory computer-readable medium having stored thereon computer-executable instructions that, in response to execution, cause a computing system to perform operations, the operations comprising: parsing a piping and instrumentation diagram (P&ID); identifying, based on the parsing, instruments within the P&ID; identifying a rule, of a set of rules maintained in a template library, corresponding to a group of instruments included in the instruments, wherein the rule defines input tags associated with the group of instruments, output tags associated with the group of instruments, and one or more relationships between the input tags and the output tags; identifying, based on the rule, the input tags and the output tags associated with the group of instruments; determining, based on the rule, a relationship between the input tags and the output tags; identifying a control loop based on the relationship between the input tags and the output tags, wherein the control loop is configured to control one or more instruments of the group of instruments, in response to execution by a control system; generating, based on an identity of the control loop, executable source code that, in response to execution by the control system, causes the control system to control the instruments in accordance with the control loop; and sending the executable source code to the control system. 8. The non-transitory computer-readable medium of claim 7 , wherein the P&ID is expressed in a machine-readable form. 9. The non-transitory computer-readable medium of claim 7 , wherein each rule of the set of rules is associated with at least one instrument or at least one group of instruments, and each rule is a predefined part of an integration tool and defines at least one of one or more input tags, one or more output tags, or one or more relationships between input tags and output tags for an instrument or a group of instruments. 10. The non-transitory computer-readable medium of claim 9 , wherein the generating the executable source code comprises generating the executable source code based on a source code template associated with the control loop. 11. The non-transitory computer-readable medium of claim 7 , wherein the input tags relate to data that is to be input to at least one instrument of the group of instruments, and the output tags relate to data that is to be output by at least one instrument of the group of instrument. 12. The non-transitory computer-readable medium of claim 7 , wherein the operations further comprise: finalizing the control loop based on received control loop parameter values to yield finalized executable source code; and distributing the finalized executable source code to one or more control modules within an industrial environment. 13. A system for exchanging data between a piping and instrumentation diagram (P&ID) and a control system, comprising: a memory that stores executable components; and a processor, operatively coupled to the memory, that executes the executable components, the executable components comprising: a P&ID integration tool configured to identify instruments associated with the P&ID based on analysis of the P&ID; and a transformation engine configured to: identify a rule, from a set of rules maintained in a template library, corresponding to a group of instruments included in the instruments identified by the P&ID integration tool, wherein the rule defines input tags associated with the group of instruments, output tags associated with the group of instruments, and one or more relationships between the input tags and the output tags, determine, based on identifications of the group of instruments and the rule, the input tags and the output tags associated with the group of instruments and the one or more relationships between the input tags and the output tags, identify a template corresponding to the input tags, the output tags, and the one or more relationships, identify a control loop defined by the template for each of the one or more relationships, wherein the control loop is configured to facilitate control of the instruments in response to execution by the control system, and generate, based on an identity of the control loop, executable source code that, in response to execution by a control system, causes the control system to control the instruments in accordance with the control loop, wherein the P&ID integration tool is configured to output executable source code for the control loop to the control system. 14. The system of claim 13 , wherein the P&ID comprises at least one of a machine-readable P&ID or a human-readable drawing, and the P&ID integration tool is further configured to: extract data from the P&ID to yield extracted data, and parse the extracted data to identify the instruments. 15. The system of claim 13 , wherein the transformation engine is configured to generate the source code based on a s
Network design, e.g. design based on topological or interconnect aspects of utility systems, piping, heating ventilation air conditioning [HVAC] or cabling (circuit design at the physical level G06F30/39; network planning tools for wireless communication networks H04W16/18) · CPC title
electric · CPC title
characterised by CIM planning or realisation · CPC title
Cross-Sectional Technologies · mapped topic
Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.