The properties of a facility are its ID, description, and attributes. Facility attribute values can be used to define polling schedules, to create groups, and can be included on CygNet Studio screens and in reports. The attribute names and descriptions are configured by the CygNet administrator.
Up to 83 attributes can be used to describe a facility.
*Table attribute values must be selected from a list. This ensures standardized data entry.
See Attribute Names and Lengths for the specifics of each attribute.
|
|
| User-Defined Global Facility Attributes |
The attribute names are user-configurable and are global to the Facility Service. Use names that are generic when possible. For example, if you name an attribute as "Type" this would apply only to RTUs. A better name would be "Remote Equip Type" which could be applied to RTUs or PLCs. For table attributes, you must define the table entries.
The properties of a facility are its attributes. Attributes are descriptive elements. For example, the facility belongs to the Andrews field office (Field Office) in Texas (State). The facility is on route 13a (Route) and the person in charge of the facility is Bob (Operator). It is a Totalflow 6400x (Remote Equipment Type) that communicates using a radio (Comm Method). The serial number of the device is 23UWED12X-333 (Serial Number). This facility is on a shared lease (Yes/No). The radio (Comm Method) is a Freewave radio (Comm Equipment Type) on repeater 2 (Repeater).
Not every attribute will apply to every facility. In the example above, the Repeater attribute does not apply to the RTU, and the Remote Equipment Type attribute does not apply to the radio.
Facility attributes can be enabled/disabled and their descriptions user-defined.
A text attribute is a free-form text field. Use this field for items that do not have consistent data entry, such as a serial number or other unique identifier. The length of the text attributes vary between 20 and 80 characters.
A table attribute is a table-driven field. Use this field for items that require standard data entry, such as a state attribute. If you used a text attribute for state and one user-typed "TX" and the other user-typed "Texas" the system would recognize the values as different. A better option would be to use a table attribute where the only option would be “Texas.” A table entry has both the entry and its description. Either one can be used when displaying or reporting the attribute information. The tables are stored in the Table Reference Service. The table name for a table attribute is SYSFCTxx, where xx represents the attribute number. For example, SYSFCT03 represents Table Attrib 03.
The yes/no attribute is an attribute for which the value is either set or not set. Yes/No attributes are for yes or no situations.
Internal attributes are generically identified (for example, Table Attrib 0). You can assign a descriptive name to them. When doing so, keep in mind that attributes are global to the Facility Service, so use broad-based attribute names. If you define an attribute as "PLC Type" this would apply only to PLCs. A better name in this instance might be "Remote Equipment Type" because it could apply to PLCs or RTUs.
More:
Configuring Facility Attributes
Applying the Same Attributes to Multiple FAC Services
|
|
|
