SECTION 40 61 93 PROCESS CONTROL SYSTEM INPUT/OUTPUT LIST

SECTION 40 61 93

PROCESS CONTROL SYSTEM INPUT/OUTPUT LIST

PART 1 - GENERAL

_{1.1 DESCRIPTION}

A. Scope:

1. This Section describes the system input/output (I/O) list Contract deliverable and requirements for configuring the control system database. A sample I/O list follows this Section. The CONTRACTOR shall supply a complete and fully populated I/O list. The I/O list shall include all existing I/O being moved by the CONTRACTOR to the new PAC panels and all new I/O required for this contract.

B. Related Sections:

1. Section 40 64 00, Programmable Automation Controllers.

1.2 SUBMITTALS

A. For each I/O attribute listed in the I/O list that cannot be completed, submit an explanation of the reason for the deviation. Do not proceed with any configuration until a method of resolving deviations is accepted by the ENGINEER.

B. Include the PAC specific submittals for Section 40 64 00, Programmable

Automation Controllers.

C. CONTRACTOR shall provide and complete the information requested in the sample table, including identification of all soft I/O for digital communication networks including DeviceNet, Modbus, and Ethernet. The Listing shall include the node address, and addresses within the device. The addresses shall be coordinated by the CONTRACTOR so that node and segment addresses are unique within the Monitoring and Control System.

_{1.3 I/O POINT LIST DESCRIPTION}

A. “TAG NO.” is an alphanumeric character string. The point tag shall follow the format: [site][area]_[desc1][train][parallel]_[loop]_[desc2][train][parallel]_[para- meter].attribute:

1. Site – Site designation, in lower case.

2. Area – The two digit process area number.

3. Desc1 – The first descriptor field intended for the specific process description. If more appropriate, it may be used for primary equipment

name, area, building, etc.

4. Train – The process train number.

5. Parallel – The lower case alphabetical designator for multiple equipment operating in parallel on a single process train.

6. Loop – The loop number from the flow diagram or instrument tag. In the case of valves, this will be the valve number.

7. Desc2 – The second descriptor field intended for the equipment or device associated with the tag.

8. Parameter – The process variable of the associated equipment.

9. .Attribute – The tag attribute of a Wonderware object or parameter within a

ControlLogix object.

10. Example – e28_inc1_xxxx_wb_psi.ind

a. “e” represents the Easterly WWTP site.

b. “28” is the process area number for the Primary Settling Tanks c. “inc1” is the fluidized bed incinerator, process train 1.

d. “wb” is windbox, the device or equipment description. e. “psi” is pressure, the process parameter.

f. “ind” is the attribute for indication. g. “xxxx” is the 4-digit loop number.

B. “DESCRIPTION” is an alphanumeric character string up to 40 positions in length. Points described as “SPARE” denote pre-wired I/O.

C. “SIGNAL TYPE” describes whether the point is connected through a digital network, discrete, or analog means.

D. “DATA FIELD” is a modifier for the signal type, which shows additional details. E. “RANGE / UNITS” lists the high and low ranges of the signal in engineering

^units.

F. “SET POINT” shows the trip points of discrete items such as switches.

G. “SIGNAL FROM” lists the origin of the signal, as related to the control panel or valve actuator, etc.

H. “TB NO.” is the terminal block where the signal originates.

I. “PANEL/DEV. TERMINAL NO.” is the terminal on the panel or device from which the signal originates.

J. “POWER SOURCE” lists the location of the power source which is powering the signal.

K. “SIGNAL TO” lists the destination of the signal, as related to the control panel or valve actuator, etc.

L. “PLC TERMINAL NO.” is the terminal in the PLC panel which is connected to the signal.

M. “PLC POINT ADDRESSES” is the terminal on the PLC module corresponding to the signal.

PART 2 - PRODUCTS (NOT USED)

_{PART 3 – EXECUTION}

3.1 I/O CONFIGURATION

A. Implement the control system database fields in a consistent manner by using the following procedures:

1. Use abbreviations and acronyms already established in the Contract

Documents.

2. Use only an abbreviation or an acronym for a word or group of words, respectively.

3. Use the same subject and word order within data fields.

4. Use the same term (either phrase, word or acronym) to denote the same meaning. Do not use multiple terms for a single meaning.

5. Use the point names, descriptions, logic state descriptions, ranges and units of measurement exactly the same wherever the point is referenced.

6. Show point names and descriptions for all point references on documentation.

7. Spell correctly.

8. Maintain lists of acronyms and abbreviations used.

_{3.2 I/O HARDWARE CONFIGURATION}

A. Partition the I/O among cards within an I/O enclosure to provide control loop integrity.

1. Put all inputs of the same I/O type associated with a device (e.g. pump, blower, clarifier or other piece of equipment) on the same card.

2. Put all inputs of the same I/O type for devices arranged in process trains

(e.g. a pump, its inlet valve and its outlet valve, or a pump and its associated macerator) on the same card or cards if more than one card is required to accommodate the points.

3. Put all outputs of the same I/O type associated with a device or group of devices in a process train on the same card or cards if more than one card is required to accommodate the points.

4. Where the preceding requirements specified in this paragraph would cause more than 20 percent spare points on a card, points for a device or process train may be split between two consecutive cards.

5. Make unused terminals resulting from partitioning the I/O into pre-wired

spares. Provide pre-wired spare points with all cabling and termination internal to the PAC as done for other I/O points.

3.3 POINT DATA FIELDS

A. I/O point data fields may be subject to review and modification by the ENGINEER during the Shop Drawing review phase. Incorporate changes directed by the ENGINEER completely into the entire system, at no additional cost to OWNER, subject to the following limitations:

1. Limit the total number of modifications to 20 percent of the total number of

I/O points.

2. Each unique change will count as one modification. For example, modifying the description, range, and engineering unit on an analog input count as three modifications.

3. Analog input alarm limit definition will not be counted as a modification.

_{3.4 INPUT/OUTPUT TAGGING}

A. The project Input/Output list shall indicate all required MCS I/O for the project, including all hardwired I/O as well as soft I/O to be communicated between processors over and DeviceNet, Ethernet, and Modbus protocols. Exiating, relocated I/O and new I/O shall both be included.

B. The I/O list shall include all details that must be coordinated during project implementation, such as final node addresses and registers for all I/O.

C. The CONTRACTOR shall follow the OWNER-approved format included herein.

The attached sample I/O list can be provided to the CONTRACTOR in electronic form (Microsoft Excel) upon request.

D. For each PAC/PLC and RIO panel, the CONTRACTOR shall submit the required tag database submittals as described under Section 40 61 13, in the format attached, in both hardcopy and electronic form (Microsoft Excel).

E. Each submittal shall include all information coordinated with equipment vendors and suppliers for the systems integration work including, but not limited to:

1. Alarm settings and class

2. Terminal block information

3. Power source

4. PLC term no

5. Final PLC register location

F. Additionally, for soft I/O communicated over DeviceNet, Ethernet, and Modbus the submittal shall include similar information coordinated with all equipment vendors and suppliers. For soft I/O include, but not be limited to:

1. Alarm settings and class

2. Terminal block information

3. Communication segment tag

4. Node address on segment coordinated with all vendors and suppliers with equipment on that segment. NOTE: All Ethernet IP addresses shall be furnished and coordinated with the OWNER’S IT and SCADA departments.

5. Final PLC register location.

3.5 ATTACHMENTS

A. See attached I/O List Sample schedule to be as a template by the CONTRACTOR for completion of the I/O list required for the Primary Settling Tanks Rehabilitation Project.