Project: MJB
Rev
0
By
MJB
Description
Initial Revision for CUI 2001
This book, once assembled from the attached documents and other sources, forms the complete
documentation necessary to undertake a Controls Check Out project. The contents are:
Tab
1
2
3
4
5
6
7
8
9
10
Document
Titlepage
Contents
Location Drawings
Loop Drawings
SAMA Drawings
Motor Schematics
PLC Logic Drawings
DCS Logic Slot Drawings
Check Out Procedures
Check Out Activity Definitions
Check Out Introduction
Client Safety Information
Attached
Yes
Yes
Yes
Yes
Yes
Source
This doc.
This doc.
Separate
Separate
Separate
Separate
Separate
Separate
This doc.
This doc.
This doc.
Separate
19.
20.
21.
22.
23.
24.
25.
26.
Tag exists
Verify the tag exists on the system
2. Tag location correct
Verify the tag location (UCN and Node) matches correct HPM
3. Descriptions and label
Verify description and label against function on logic drawing
4. Number of states, descriptions, engineering units, and colors
Verify number of states and their descriptions from logic drawing
Verify the engineering units and colors from inference
5. Inputs
Verify inputs against logic drawing and PLC ladder logic
6. Input Logic
Verify inputs logic against logic drawing and forcing or activating PLC ladder logic
7. Alarm modes and priorities
Verify alarm mode and priorities against source document
8. Graphics and Change-zones
Verify proper appearance and functionality on graphics including description, labels, colors, and
change-zones. Simulation of inputs and outputs may be required.
9. Outputs
Verify outputs against logic drawing
10. Output Logic and momentary states
Verify outputs and momentary states against logic drawing and PLC ladder logic by commanding
states
11. Narrative matches functionality
Verify tag accomplishes narrative functionality requirements
Tag exists
Verify the tag exists on the system
Tag location correct
Verify the tag location (UCN and Node) matches correct HPM and tag numbering system
Inputs
Verify inputs against DCS Logic Slot drawing
Logic
Verify logic against DCS Logic Slot drawing including blocks, negations, and output control flags
Outputs
Verify outputs against DCS Logic Slot drawing
Narrative matches functionality
Verify tag accomplishes narrative functionality requirements
Tag exists
Verify the tag exists on the system
Descriptions and label
3.
4.
5.
6.
Tag exists
Verify the tag exists on the system
Tag location correct
Verify the tag location (UCN, Node, module, and slot) matches loop drawing
Descriptions and label
Verify description and label against loop drawing
Input
Verify input against loop drawing and other tags.
Range and Engineering units
Verify calibrated range and engineering units against loop drawing
Graphics and Change-zones
Verify proper appearance and functionality on graphics including description, labels, colors, percentage
or engineering units, bar graphs, and change-zones. Simulation of inputs and outputs may be required.
Alarm modes and priorities
Verify alarm mode and priorities against source document
Outputs
Verify output connections against loop drawing
Narrative matches functionality
Verify tag accomplishes narrative functionality requirements
Tag exists
Verify the tag exists on the system
Tag location correct
Verify the tag location (UCN, Node, module, and slot) matches loop drawing
Descriptions and label
Verify description and label against loop drawing
Inputs
Verify driven inputs against loop drawing and other tags.
Outputs
Verify outputs loop drawing
Output Logic
Verify outputs characterization and forward or reverse acting state against loop drawing
Narrative matches functionality
Verify tag accomplishes narrative functionality requirements
1.
Tag exists
Verify the tag exists on the system
2. Tag location correct
Verify the tag location (UCN, Node) matches loop drawing
3. Descriptions and label
Verify description and label against loop drawing
4. Inputs
Verify inputs against loop drawing and other tags.
5. Range and Engineering units
Verify calibrated range and engineering units against loop drawing
6. Graphics and Change-zones
Verify proper appearance and functionality on graphics including description, labels, colors, percentage
or engineering units, bar graphs, and change-zones. Simulation of inputs and outputs may be required.
7. Alarm modes and priorities
Verify alarm mode and priorities against source document
8. Control strategy
Verify the control strategy matches the SAMA and narrative, including overrides and interlocks or
manual control
9. Outputs
Verify outputs loop drawing
10. Output Logic
Verify outputs characterization and forward or reverse acting state against loop drawing
11. Narrative matches functionality
Verify tag accomplishes narrative functionality requirements
Check PLC I/O Verify PLC I/O responded to a change in the field state
Check PLC logic functionality Verify that the plc logic matches the design, and operates correctly.
Check process / device connection Verify that the instrument or device is correctly connected to the
process in a secure, reliable fashion, and any process lines are installed in accordance with good practices,
filled if required, and valved in.
Check / simulate starter overload Simulate overload in starter and verify starter would de-energize, and
DCS alarms, if configured.
Check starter power Once the MCC or cheater power is applied, verify the control circuit is energized.
If the starter is wired to the PLC, verify PLC input for starter power.
Force output and check input Force a change of state in the PLC and ensure the DCS input follows the
PLC.
Simulate full signal range Using a process simulator or 4-20ma generator, ramp the device through the
full signal range.
Test run / stop from DCS Verify DCS can stop and start the motor, if configured.
Test run / stop from field - With the output enabled, test start and stop the starter from the field. Verify
run indication from starter in PLC, if wired.
Verify current state The current state of the instrument or device is compared to the current state of the
process or equipment for agreement.
Timing
CCO is performed after construction is complete, but prior to a dynamic testing or operations group
receiving control of the process.
Workflow
The workflow for Controls Check Out needs to occur in the following order:
Construction complete and contractor QAd
Contractor turns completed items turned over to CCO group
CCO team assigned to perform predefined checks on items
CCO team tests the device and the software for proper operation
Deficiencies from checks are fed back to originators
Repaired deficiencies are rechecked and fed back until there are no outstanding serious deficiencies or
predefined checks
CCO team turns completed items over to a dynamic testing or operations group.
Activities
Paper management This involves receiving paper from the construction group indicating progress,
producing reports for, and receiving reports from the CCO teams, and producing completion reports for
the dynamic testing or operations group..
CCO System management The CCO database system is a large, complex, distributed database that
must be updated regularly with status information. The system develops reports based on that status
information, which must be generated and distributed to the various interested parties.
CCO Management The CCO Manager works to facilitate the CCO teams activities, including
interfacing to construction, dynamic testing, and operations. The manager is also responsible for
progress reporting to scheduling.
CCO Team leadership The team leader directs the controls check out activity, including controlling
direction and safety aspects for the team. They are responsible for reporting progress, speaking for the
team, interfacing with other groups, and distributing direction to the team.
PLC and DCS operation The control system (PLC and DCS) operators direct the field CCO teams in
meeting the check-out objectives. They also manage most of the teams paperwork.
Field checks and repairs The field crews work with the control system end-devices and the PLC and
DCS operators to verify the field device works as required by the controls design. They are also
responsible for any small construction fixes in the course of getting the field devices working.
Roles
DCS
The DCS operator is responsible for checking tags and graphics, verifying DCS based control strategies
and interlocks, actuating field devices from the DCS, tracking progress and writing up deficiency
information.
When the team is checking out analog-only devices, the DCS operator runs the commissioning crew.
PLC
The PLC operator is responsible for verifying logic, interlocks, PLC/DCS communication on the PLC side,
tracking progress and writing up deficiency information.
When the team is checking out digital devices or starters, the PLC operator runs the commissioning crew.
Field Tradesman
The field tradesman is responsible for device disassembly, jumpering, cheater-cords, electrical testing, and
in-place repairs.
CCO Administration
The CCO administrators are responsible for maintaining the CCO database and providing work lists to and
receiving work lists from the CCO teams.
They are to assist with paper and information management for the CCO teams when they are not
maintaining the CCO database.
Safety
There are three kinds of safety: Your safety, your co-workers safety, and the physical plants safety.
There are a number of risk factors: Industrial site, construction, electricity, process, mechanical action,
untested systems, unfamiliar area, poor communications.
Think through your actions, and keep others informed of your activities and status.
Assume everything is live
Do not touch any wires before checking them for voltage to ground.
Do not change terminals on energized equipment
Assume all starters are energized at all times.
Do not place any object that is not well insulated (ie: quality multimeter) into the starter cubicle
Do not poke at terminated wires, as they can come off and hurt you
Be careful about fusing. Just because it protects you doesn't mean it will protect the equipment and
vise versa.
If using a meter, ensure it is in the right mode (voltage / current). Consider never putting your meter in
current mode.
Do not do anything that could cause a device to become energized unless you have a lookout
Talk to the rest of the crew. Always tell the other party what you are doing.
Think about what's behind a valve, pump, or actuator. If you don't know, ask.
Be sure you can't be hurt by a test you perform on a device.
Watch out for pinch points and leaning against or placing things on equipment that will move.
The equipment may be old, or brand new and never tested. Be mindful of leaking pipe joints that may
become pressurized, and equipment that might fail.
Project Number
Subsystem Number
Subsystem Description
Subsystem Time Required (when this subsystem is scheduled for turnover to operations or GPOP
commissioning)
Item Tag (Area-Group for Equipment Groups, Area-Type-Group-Suffix for Instruments)
Item Location (includes Elevation, Location and Location Description if they were in AutoIndex)
Item Description
Reference Drawing Number (if it was in AutoIndex)
Deficiency Description
Deficiency Type
When the deficiency was found
CCO Complete CCO is considered to be complete for an item once all of its CCO tasks have been
completed. Deficiencies can still exist for the item however they cannot be of the Fix Now type.
Safety Documentation
600 VAC Starter CCO Cheater Cord Job Safety Analysis
600 VAC Starter CCO T Leads Removed Job Safety Analysis
600 VAC Starter CCO Full Connection Job Safety Analysis
2300 VAC Starter CCO Cheater Cord Job Safety Analysis
Control Valve CCO Job Safety Analysis
Mechanical Actuation CCO Job Safety Analysis
120VAC Instrument CCO Job Safety Analysis
120VAC Power On Signal Simulation Job Safety Analysis