# US 2011/0022197 A1 · Process control application development environment and features

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2011/0022197 A1
- Document ID: US20110022197A1
- Status: Published application
- Kind: A1
- Application number: 12/843,719
- Filed: 2010-07-26
- Published: 2011-01-27
- Earliest claimed: 2009-07-27
- Assignees: REC Advanced Silicon Materials LLC
- Inventors: Urban Robert Kultgen, II
- Web page: https://patentgrep.com/patent/US20110022197A1

## CPC

- G05B 19/042: using digital processors (G05B19/05 takes precedence)
- G06F 8/20: Software design
- G06F 9/4812: {by interrupt, e.g. masked}
- G05B 2219/25416: Interrupt
- G05B: CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS (systems for controlling or regulating non-electric variables G05D; systems for regulating electric or magnetic variables G05F; control devices or systems insofar as characterised by mechanical features only G05G)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A process control application development environment provides an abstraction layer for vendor-independent process control application development. Various features such as validation of high-level representations of process control applications, exception handler agents, structured interactive operation of multiple machines, and multiple device states can be implemented for process control applications.

## Claims

### Claim 1

A computer-implemented method comprising:
in a controller, executing, via interpretation, a high-level representation of a process control application implementing a process control process, wherein the high-level representation comprises an exception handler agent comprising an exception handler type and an exception condition; and
upon detection that the exception condition is satisfied:
(a) interrupting execution of the process control application;
(b) invoking the exception handler agent according to the exception handler type of the exception handler agent; and
(c) resuming execution of the process control application.

### Claim 2 (depends on 1)

One or more computer-readable storage media having stored thereon computer-executable instructions for performing the method of claim 1.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1 wherein:
the high-level representation of the process control application comprises a plurality of high-level directives; and
the method further comprises:
storing indications indicative of whether the exception handler agent is active for respective of the high-level directives; and
inhibiting the exception handler agent for those high-level directives for which the indications indicate that the exception handler is not active.

### Claim 4 (depends on 3)

The computer-implemented method of claim 3 further comprising:
during development of the process control application, receiving a user action indicative of whether the exception handler agent is active for a particular high-level directive of the process control application; and
responsive to the user action, storing an indication indicative of whether the exception handler agent is active for the particular high-level directive as associated with the particular high-level directive.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4 wherein the user action comprises clicking on a user interface element representing the exception handler agent.

### Claim 6 (depends on 5)

The computer-implemented method of claim 5 wherein the user interface element representing the exception handler agent is one of a plurality of icons representing respective exception handler agents.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1 further comprising:
after resuming execution of the process control application, encountering an exception handler agent configuration instruction comprising an exception handler type and an exception condition;
responsive to encountering the exception handler agent configuration instruction, re-configuring the exception handler agent according to the exception handler agent configuration instruction.

### Claim 8

A system comprising:
one or more processors;
memory coupled to the one or more processors;
a stored high-level representation of a process control application;
stored configuration information for a plurality of exception handler agents, wherein the exception handler agents comprise respective exception handler types and exception conditions.

### Claim 9 (depends on 8)

The system of claim 8 wherein:
the stored high-level representation of the process control application comprises a plurality of high-level directives; and
the system further comprises stored indications of whether the exception handler agents are active for respective of the high-level directives.

### Claim 10 (depends on 9)

The system of claim 9 further comprising:
an interpreter configured to execute the stored high-level representation and further configured to activate the exception handler agents when executing high-level directives as indicated by the stored indications.

### Claim 11

A computer-implemented method of synchronizing action between a first encapsulated machine implemented via execution of a first high-level representation of a first process control application and a second encapsulated machine implemented via execution of a second high-level representation of a second process control application, the method comprising:
in the first encapsulated machine, performing (a)-(c) responsive to execution of the first high-level representation of the first process control application:
(a) sending a request for permission to an external, encapsulated machine;
(b) waiting for the request to be granted;
(c) responsive to detection that the request has been granted, proceeding with execution after the request is granted;
in the second encapsulated machine, performing (d)-(f) responsive to execution of the second high-level representation of the second process control application:
(d) waiting for a request for permission from an external, encapsulated machine;
(e) responsive to detection that a request has been received, sending grant of permission to the external, encapsulated machine;
(f) proceeding with execution after sending the grant.

### Claim 12 (depends on 11)

One or more computer-readable storage media having stored thereon computer-executable instructions for performing the computer-implemented method of claim 11.

### Claim 13 (depends on 14)

The computer-implemented method of claim 14 wherein:
the first encapsulated machine executes master functionality; and
the second encapsulated machine executes slave functionality.

### Claim 14 (depends on 11)

The computer-implemented method of claim 11 further comprising:
before sending the request for permission, checking a plurality of encapsulated machines for availability via a synchronization primitive.

### Claim 15 (depends on 14)

The computer-implemented method of claim 14 wherein:
the first encapsulated machine checks availability via execution of a high-level directive in the first high-level representation; and
the second encapsulated machine indicates it is available via an agent executing in an interpreter of the second high-level representation.

### Claim 16 (depends on 15)

The computer-implemented method of claim 15 wherein:
the second encapsulated machine indicates it is available without executing a high-level directive.

### Claim 17 (depends on 11)

The computer-implemented method of claim 11 wherein:
the second encapsulated machine comprises a plurality of field devices but appears to the first encapsulated machine as a single machine with a single identifier.

### Claim 18 (depends on 11)

The computer-implemented method of claim 11 wherein:
sending the request for permission comprises sending a get_ready synchronization primitive; and
sending grant of permission comprises sending a ready synchronization primitive after preparing at the second encapsulated machine to be used by the first encapsulated machine in a process control process.

### Claim 19 (depends on 11)

The computer-implemented method of claim 11 wherein:
sending the request for permission comprises executing a master request instruction; and
waiting for the request to be granted comprises executing a master listen instruction, wherein the master listen instruction comprises a parameter indicating a location in the first high-level representation to which execution is to proceed if a synchronization primitive later in a synchronization exchange than expected is received.

### Claim 20

A system comprising:
a controller comprising memory;
an interpreter executing, in memory of the controller, and supporting synchronization primitives comprising available, lock_request, lock_confirm, get_ready, ready, and start.

### Claim 21

(canceled)

### Claim 22

(canceled)

### Claim 23

(canceled)

### Claim 24

(canceled)

### Claim 25

(canceled)

### Claim 26

(canceled)

### Claim 27

(canceled)

### Claim 28

(canceled)

### Claim 29

(canceled)

### Claim 30

(canceled)

### Claim 31

(canceled)

### Claim 32

(canceled)

### Claim 33

(canceled)

### Claim 34

(canceled)

### Claim 35

(canceled)

### Claim 36

(canceled)

### Claim 37

(canceled)

### Claim 38

(canceled)

### Claim 39

(canceled)

### Claim 40

(canceled)

### Claim 41

(canceled)
