Thread Content
In a complete set of equipment, there are many types of non-process variable signals. For example, there is the manual start signal for Battery #1, input signals for engine operation alarms, input signals for engine overspeed alarms, input signals for general fault alarms, an output for idle speed control, an output reflecting the automatic mode of the control system, an output indicating engine faults, and so on. To enable communication with the DCS, these signals need to be assigned as instrument tag numbers – but how should they be written? For example: engine overspeed alarm signal input, SHA-0101, S – speed, H – high, A – alarm. Is this standard and feasible? For signals such as engine operation alarm inputs and automatic mode feedback outputs from the control system, since there are no letters indicating the instrument tag number, how should such tag numbers be assigned?
Refer to the numbering method in the original DCS and seek user preferences to maintain consistency
According to the numbering rules set by the design institute, only process variables are allowed; however, equipment manufacturers provide rather confusing specifications. To maintain consistency, we developed our own numbering system, but we’re not sure how to approach handling such signals. Thank you for the reply
Refer to the specifications and write in the way you are accustomed to; the annotations should be clear. Such tag numbers are only for configuration purposes – process engineers aren’t interested in them; it’s sufficient as long as you understand them. Remember to archive and print it; otherwise, no one will know what that code means later on. :lol