# US 2012/0084696 A1 · User interface list control system

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

- Number: US 2012/0084696 A1
- Document ID: US20120084696A1
- Status: Published application
- Kind: A1
- Application number: 12/895,640
- Filed: 2010-09-30
- Published: 2012-04-05
- Earliest claimed: 2010-09-30
- Assignees: Honeywell International Inc.
- Inventors: Jerry Marti
- Web page: https://patentgrep.com/patent/US20120084696A1

## CPC

- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q 10/10: Office automation; Time management
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A user interface list control system having a supervisor user application providing tools to create, deploy, modify and monitor a multi-site enterprise of remote building management systems (BMS). BMS controllers may be configured to control or monitor similar entities across all sites. As site controller configurations are created, the user must identify each configuration item with a recognizable name and/or type tag that indicates function, definition, and/or location of the item. The user may be allowed or required to apply names and type string tags consistently across all multiple site configurations. Within the context of a single supervisor, multiple users may be allowed to utilize common lists of name and type tags. The user may apply an application-specific name and/or type tag to a configuration item, using a drop down list where the user can add a new string to a tag list or select a previously entered string tag.

## Claims

### Claim 1

A method for controlling components at a user interface, comprising:
navigating to a component configuration;
attaching component name property to a root of the component configuration;
selecting a name for a component name property by entering new name text or selecting an existing name from a list from a memory;
appending the list if new name text is entered; and
setting the new name to the component name property.

### Claim 2 (depends on 1)

The method of claim 1, wherein each component has just one name.

### Claim 3 (depends on 1)

The method of claim 1, wherein:
the component name property is instantiated in a site controller;
the list is a drop down list stored in a supervisor data server; and
the name is set to the component name property is in the site controller.

### Claim 4 (depends on 1)

The method of claim 1, wherein a component is a control entity.

### Claim 5 (depends on 1)

The method of claim 1, wherein a component is a schedule entity.

### Claim 6 (depends on 1)

The method of claim 1, wherein a component is an alarm type.

### Claim 7 (depends on 1)

The method of claim 1, wherein a component is a point group.

### Claim 8 (depends on 1)

The method of claim 1, wherein a component is a site category.

### Claim 9

A user interface list control system comprising:
a user interface;
a plurality of components;
a memory for holding a list of names assigned to components of the plurality of components;
wherein:
a component is selected from the plurality of components with an entry at the user interface of a name assigned to the component;
selecting a component requires the entry of a name on the list of names;
if a new name is assigned to a component, the name is entered in the list of names as the only name assigned to the component.

### Claim 10 (depends on 9)

The system of claim 9, wherein a component has only one name on the list names.

### Claim 11 (depends on 9)

The system of claim 9, wherein a component comprises a component name property.

### Claim 12 (depends on 9)

The system of claim 9, wherein name assigned to the component is set at the site controller.

### Claim 13 (depends on 9)

The system of claim 9, wherein a component is selected from a group consisting of a control entity, a schedule entity, an alarm type, a point group and a site category.

### Claim 14 (depends on 11)

The system of claim 11, wherein getting to a component name property comprises:
navigating to a component configuration; and
attaching a component name property to a root of the configuration; and
instantiating the component name property at the site controller.

### Claim 15 (depends on 9)

The system of claim 9, wherein the memory holding the list of names is a data store at a supervisor server.

### Claim 16

A user interface list control system comprising:
supervisor data server;
a user interface console connected to the supervisor data server; and
a site controller connected to the user interface console; and
wherein:
the supervisor data server comprises site groups;
the site groups comprise a string lists;
the user interface console comprises a plurality of user interface field editors; and
the site controller comprises a user interface list selector control.

### Claim 17 (depends on 16)

The system of claim 16, wherein the string lists comprises:
a control entity list;
a schedule entity list;
an alarm type list;
a point group list; and/or
a site category list.

### Claim 18 (depends on 17)

The system of claim 17, wherein each instance of a control entity, schedule entity, alarm type, point group and/or site category has just one assigned name for selection of the instance.

### Claim 19 (depends on 17)

The system of claim 17, wherein the plurality of user interface field editors comprises:
a control entity user interface field editor connected to the control entity list;
a schedule entity user interface field editor connected to the schedule entity list;
an alarm type user interface field editor connected to the alarm type list;
a point group field editor connected to the point group list: and/or
a site category field editor connected to the site category list.

### Claim 20 (depends on 19)

The system of claim 19, wherein the user interface list selector control comprises:
a control entity connected to the control entity user interface field editor;
a schedule entity connected to the schedule entity user interface field editor;
an alarm type connected to the alarm type user interface field editor;
a point group connected to the point group field editor; and/or
a site category connected to the site category field editor.

### Claim 21 (depends on 20)

The system of claim 20, wherein the user interface list selector control further comprises:
a control system connected to the control entity;
a schedule connected to the schedule entity;
an alarm extension connected to the alarm group type;
a history extension connected to the point group; and
a site connected to the site category.
