?
MISCELLANEOUS EQUIPMENT (TANKS, HEAT EXCHANGERS, BINS, VESSELS, ETC.)
1) Background Presentation [Non-active data]
? Equipment = Any color except Red or Green 2) Active Equipment [i.e. targets] (outline only)
? Non-selected state = White or Black, No Blink ? Selected = White or Black, Blinking
?
1) Background Presentation (Non-active data)
? Text = Cyan, Green, Black, Blue
? Engineering Units (Psig, Kg, DegF, DegC, etc.) = Cyan or Black 2) Live Alpha-Numeric Data (excluding PV & RV values)
? Selectable, ChangeableAlpha-Numeric Text = Yellow ? Non-Selectable, Live Alpha-Numeric Text = White
?
LIVE PROCESS OR MACHINE DATA ON GRAPHIC Numerical text followed by the units which will be Cyan or Black.
1) Process Variables (PV) = Yellow or Green
2) Set Points (SP) = Yellow (Red on Tuning Trend for contrast) 3) Non-Control Loop Analog Data (RV) = White 4) Bar Graphs = Cyan or White or Yellow or Green ?
1) Alarm = Blinking Red
2) Acknowledged but still alarmed = Red ALARM STATES
3) Tables of data with many lines of live text = White or Yellow or Green ALPHA-NUMERIC TEXT 3) (Optional) No longer alarmed but never Acked = Blinking Yellow.
?
1) Process or machine Condition Not Sensed
= Red (OFF)
2) Process or machine Condition Sensed (On) = Green SWITCH STATES 3) If “On” condition is an alarm, then item 7 (Alarm States) dictates
action.
?
1) Color = Project specific
2) Line thickness = one or two pixel
PIPING AND DUCT WORK 6. Shapes
A library of standard, reusable, shapes includes items such as: ?
Shape States
1) Motor- (Color indicates state)
2) Centrifugal Pump - (Color indicates state)
3) Positive Displacement Pump - (Color indicates state)
4) Throttling Control Valve- (Color and analog value indicates state) 5) Speed Controlled Motor- (Color and analog value indicates state) 6) Block Valve - (Color indicates state) 7) 3-Way Block Valve - (Color indicates state) 8) Field Mounted Switch - (Color indicates state) 9) Analog Sensor/Transmitter
(Small solid white box to indicate location only, no live data) - Do not use \because this uses too much space!
?
Shape Actions
Note that for some shapes, a hidden graphic object serves as the selection target. It does not appear on the screen because it is the same size and shape as the first graphic object and it is located behind the first graphic object. These selection targets typically call Quick functions which perform the following actions:
1) Hide any Bottom Popup screens that may be open.
2) Clear any Bottom Popup screens names that have been selected. 3) Pass all tags for the selected device to the Indirect Tags that are used
by the Bottom Popup screens to operate the device.
4) Shapes that do not use the maximum number of inputs or outputs
pass \done in order to ensure that all indirect tags contain only data for the currently selected device.
5) Set the value of a device specific tag to 1 so that the cyan box will
appear on the screen.
6) Open the Bottom Popup screen.
such as:
7. Command Entry
?
General Practice
Command execution from Graphic Displays must have safeguards to prevent accidental activation of field equipment or automated procedures.
This will be accomplished by requiring 2 entries to activate any command that will affect field equipment, the process, or the machine. Commands that do not affect field equipment and are used for display or program control can be activated with a single entry.
Examples include:
?
Commands to be executed with one entry. 1) Change/Show graphic display. 2) Clear/Hide a windowed display. 3) Resetting and starting timers.
?
Commands requiring multiple entries.
1) Commands that cause field equipment to change.
2) Command that cause an automated procedure to be initiated,
? Automatic Startup. ? Automatic Shutdown. ?
Formula Download
8. Bottom Menus
In to meet the criteria of requiring 2 entries to activate any command that will affect field equipment, the process, or the machine, bottom menus must be designed to allow 2 entries. The following items illustrate the behavior of bottom menus:
1) The bottom menu monitors for the last operator selection. 2) The bottom menu then activates an “Execute Command” button to
notify the operator that the “Execute Command” button must be pressed to initiate the command.
3) A “Cancel Command” button may be pressed to cancel the operator
selection without initiating the command.
4) The “Cancel Command” button also serves as an “Exit” button to hide
the bottom menu if no operator selection has been made.
10.C.3. TAGNAMING CONVENTIONS
The purpose of this tag naming conventions is to have a consistent, descriptive, and structured tag list.
TAGS FOR NON-BATCH CONTROLS ?
The tag naming format is represented below. The Maximum number of characters per tag, including underscore characters, is 20.
AAAA_BBBBBBBBBB_CCCC
The table below describes each part of the tag format for a non-batch process control. Field AAAA Description 4 characters or less that describes the Area of the process or machine. This field is optional and can be deleted from tag names if there is no Area for an application. In this case the naming convention is BBBBBBBBBB_CCCC BBBBBBBBBB CCCC 10 characters or less that describes the Device. Examples are: FV2345, AcidPump, LIC54321, Mtr382 4 characters or less that describes the Parameter that the point represents. Examples are: CMDA that can stand for Command Disagree Alarm. _
Table 1: Tag Naming Convention
Other examples of the CCCC parameter is shown below: CCCC Name CMDA DO01 DO02 DI01 DI02 Parameters Device name Command Disagree Alarm Digital Input Number 1 Digital Input Number 2 Digital Output Number 1 Digital Output Number 2 Underscore characters are Field Separators. Naming Structure
MO Cmd0 Sta0 Cmd1 Sta1
Automatic/Manual Mode Test string for the OFF command Test string for the OFF feedback state Test string for the ON command Test string for the ON feedback state Table 2: Examples of CCC Parameters
Examples of CCCC parameters used in tagnames for the PLC-5 PID instructions elements. CCCC EUS PV OUT SP PE MO CL SUP KP KI KD MAXS MINS
Table 3: Examples of CCCC Parameter Used in PLC-5 PID Instruction
As a complete example, an acid pump motor can have a tagname in InTouch with the following parameters:
Tagname PRC1_AcidPump_MO PRC1_AcidPump_DO01 PRC1_AcidPump_CMDA
Description Acid pump located at Process 1 Automatic/Manual Mode tagname Acid pump located at Process 1 digital input 1. Acid pump located at Process 1 command disagree Parameters Engineering Units Process Variable Output Setpoint Control Equation Automatic or Manual Mode Cascade Mode Supervisory Mode (not in AB structure) Proportional tuning constant Integral tuning constant Derivative tuning constant Maximum scaling Minimum scaling