# US 2008/0082185 A1 · Hmi views of modules for industrial control systems

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

- Number: US 2008/0082185 A1
- Document ID: US20080082185A1
- Status: Published application
- Kind: A1
- Application number: 11/536,746
- Filed: 2006-09-29
- Published: 2008-04-03
- Earliest claimed: 2006-09-29
- Assignees: Rockwell Automation Technologies, Inc.
- Inventors: Gavan W. Hood; Kenwood H. Hall; Sujeet Chand; Paul R. D'Mura; Michael D. Kalan; Kenneth S. Plache
- Web page: https://patentgrep.com/patent/US20080082185A1

## CPC

- G05B 19/409: characterised by using manual data input [MDI] or by using control panel, e.g. controlling functions with the panel; characterised by control panel details or by setting parameters (G05B19/408, G05B19/4093 take precedence)
- G05B 19/0426: {Programming the control sequence}
- G05B 2219/23258: GUI graphical user interface, icon, function bloc editor, labview
- G05B 2219/23261: Use control template library
- G05B 2219/36133: MMI, HMI: man machine interface, communication
- 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)

## Abstract

A human machine interface (HMI) interface for an industrial automation system is provided. A module is provided that employs resources and logic to expose functionality of the module while providing generic interfaces to external components of the module. A human machine interface (HMI) component associated with the module adapts functionality of a display based at least in part on a type of user or application. In addition to the display, the HMI component adapts functionality of one or more interface inputs based in part on the type of user or application.

## Claims

### Claim 1

A human machine interface (HMI) for an industrial automation system, comprising:
a module that employs resources and logic to expose functionality of the module while providing generic interfaces to external components of the module; and
a human machine interface (HMI) component associated with the module, the HMI adapts functionality of a display based at least in part on a type of user or application.

### Claim 2 (depends on 1)

The HMI of claim 1, the HMI component adapts functionality of at least one input based in part on the type of user or application.

### Claim 3 (depends on 1)

The HMI of claim 1, further comprising one or more module classes and templates that are maintained in libraries which facilitate access to desired interface functions.

### Claim 4 (depends on 1)

The HMI of claim 1, the module includes one or more attributes that are exposed or hidden based on user type or application.

### Claim 5 (depends on 4)

The HMI of claim 4, the attributes include one or more command interfaces.

### Claim 6 (depends on 5)

The HMI of claim 5, the command interfaces are used as access points that include real time diagnostics and security.

### Claim 7 (depends on 5)

The HMI of claim 5, the command interfaces include I/O mapping and material management logic routines.

### Claim 8 (depends on 4)

The HMI of claim 4, the attributes include one or more alarm and event messages visible to external systems during execution of a module.

### Claim 9 (depends on 8)

The HMI of claim 8, the attributes include one or more artifacts that include information that documents an operation or structure of a resource or interface.

### Claim 10 (depends on 1)

The HMI of claim 1, the display provides an Organizational View, a Geographical View, or an Asset Management View of modules.

### Claim 11 (depends on 1)

The HMI of claim 1, further comprising an application component that determines a type of role for a user or determines a particular application that the user has selected and alters a display or view presented to the user.

### Claim 12 (depends on 11)

The HMI of claim 11, the application component determines the role based on direct input from the user or inferred from a task.

### Claim 13 (depends on 1)

The HMI of claim 1, further comprising a developer view that shows substantially all interfaces, logic, and data of a module, a deployment view that shows administrative elements of interest when configuring a system, a management view for debugging and maintenance of applications, or resource logic views for design and management of a control system.

### Claim 14 (depends on 13)

The HMI of claim 13, the developer view, the deployment view, and the management view shows at least two modules cooperating to form an application.

### Claim 15 (depends on 13)

The HMI of claim 13, the deployment view enables an administrator to resolve interface connections required for proper operation of a module including internal and external connections.

### Claim 16 (depends on 13)

The HMI of claim 13, the deployment view facilitates loading of at least one module into at least one controller.

### Claim 17 (depends on 13)

The HMI of claim 13, the deployment view enables attributes associated with a module to be bound to one or more system components.

### Claim 18 (depends on 13)

The HMI of claim 13, the management view provides a black box representation of a module where logic and resources are hidden and module functionality is exposed.

### Claim 19 (depends on 18)

The HMI of claim 18, the management view includes public interfaces with defined semantics, public properties that can be used to configure a module and report module state, or alarm and event messages that are published by the module.

### Claim 20 (depends on 18)

The HMI of claim 18, further comprising production execution views or maintenance views that present CAD drawings, I/O wiring diagrams or message logs associated with a module.

### Claim 21 (depends on 13)

The HMI of claim 13, further comprising a component to navigate between views.

### Claim 22

A computer readable medium having a data structure stored thereon to facilitate module interfacing in an industrial automation environment, comprising:
a first data field to specify resources and logic to perform one or more actions;
a module data field to associate the resources and logic; and
a third data field that generates an interface for the module based in part on a type of user or application.

### Claim 23 (depends on 22)

The computer readable medium of claim 22, the interface further comprising a display and an input that are adjusted based on the type of user or application.

### Claim 24 (depends on 22)

The computer readable medium of claim 22, the interface further comprising data based components or message based components.

### Claim 25 (depends on 22)

The computer readable medium of claim 22, the interface is associated with at least one category.

### Claim 26 (depends on 25)

The computer readable medium of claim 25, the category includes a command, a status component, an alarm, an event, a configuration component, an external component, or an interlock component.

### Claim 27 (depends on 22)

The computer readable medium of claim 22, further comprising at least one predefined interface.

### Claim 28 (depends on 22)

The computer readable medium of claim 22, further comprising a component to automatically generate documentation for an interface.

### Claim 29 (depends on 22)

The computer readable medium of claim 22, further comprising at least one interface faceplate.

### Claim 30 (depends on 29)

The computer readable medium of claim 29, the interface faceplate further comprising at least one icon to reflect status of a module.

### Claim 31 (depends on 22)

The computer readable medium of claim 22, further comprising at least one default interface component.

### Claim 32

A method to generate industrial control interface, comprising:
defining one or more resources for a module;
defining logic to control the resources for the module; and
determining at least one interface for the module base in part on a user type or application selected by the user.

### Claim 33

A modular interface for an industrial control system, comprising:
means for specifying at least one resource that defines a control system action;
means for generating logic that performs the control system action; and
means for generating an interface associated with the resource and the logic, the interface base in part on a user type or a user application.
