DCS Commisioning Steps
DCS Commisioning Steps
DCS Commisioning Steps
Physical Checks
Ensure proper lighting available in the control room and Panel Room.
Ensure HVAC is commissioned for the area or ensure proper ventilation in the area.
Ensure proper installation and fixing of the panels at the location as per GA drawing.
Check DCS panels for the physical damage – Door lock, door limit switch, Fans, Tube lights, internal cables,
MCBs, isolators, modules, racks, controllers, prefab cables, etc.
Check all the components of the panel as per BOM. Check for loose supplied items.
Check and verify all hardware like Engineering and operator station as per BOM.
Pre-Requisites
Ensure availability of instrumentation technicians, engineers, programmers, and tools – like Screw Driver,
Tester, Digital Multimeter, Insulation resistance tester, Earth pit resistance checker, 4-20 mA source, HART
communicator, Loop check tester, short links, etc.
Ensure UPS (redundant) and Non-UPS (Utility) power supply is available. Before charging the DCS check
whether UPS and battery banks commissioning is completed.
Operator work Station (OWS), Engineering work station (EWS) HMI are ready with installed software as per
system requirement. Check Antivirus is installed.
Check the validity of license software for HMI and Logic software/configuration software.
Electronic/instrument (IE) and Intrinsically Safe (IS) earth pit/grid is ready as per installation drawing.
Cabling from earth pit or IS Earth Grid to DCS Panel is completed. Isolation between instrument Earth and panel
earth/ cabinet body earth/system earth (SE).
Safety
The area under commissioning shall be tagged and PTW (Permit to Work) is issued/available.
To protect personnel and the equipment in the area of commissioning, “area restrictions” shall be
displayed/tagged.
One has to follow agreed templates/checklists/procedures or protocols for the entire DCS system commissioning.
Verification of component inside the cabinet/console and its specification w.r.t approved documents.
Labeling check
All components inside the cabinet (Controllers, firewalls, switches, I/O modules, barriers/isolators, racks/nodes,
Power supply modules, terminals & its size, relay boards, Safety earth, instrument earth, MCBs, MCB rating, sockets,
cross ferrule, patch panels, convertors, servers, etc) shall be properly labeled so that can be easily identified.
It is to verify that the cabinet internal wirings are as per the project specification and approved drawings.
AC power, DC power, signals (AI, AO, DI, DO, RTD, TC, Special modules) internal wiring, earthing wire color, size, duct
color.
Continuity check.
Main cable installation, termination, gland plates, and sealing shall be verified.
When required parameters are within tolerance then power on of system is done step by step.
Ensure that all components automatically boot up and components are in healthy condition.
Redundancy Check
It is to verify that system operation is uninterrupted when the active hardware fails.
Ensure that all IP addresses are properly configured uniquely for each station including printers.
GPS antennas,
GPS receivers,
NTP/SNTP switches, and their power on.
It is to check all applicable licenses for Workstation (Operator, engineering) and its applications like a logic builder,
HMI, reports, server licenses, etc.
Graphics layouts checking w.r.t P&ID, shape, size, backgrounds, and icon color when status changes (red, green,
blue, etc).
Functionally as per the requirement of the process (Auto, manual, local, remote, bypass, etc) shall be implemented.
I/O Assignment is configured properly in PCS. Marshalling wiring and termination matches with I/O allocation.
This can be done either cold loop or hot loop testing. Cold loop checking means loop checking is done without
powering on instruments.
Only wiring continuity is checked from field to Junction Box and then to the control room. Hot loop checking is done
by powering the instrument.
At the site, it is good to perform a cold loop check first and then perform a hot loop check with
actual instruments and interfaces.
Logic Check
It is to verify Control Algorithm Implementation with reference to logic diagrams, functional schematics, or control
narrative.
Nest loading is also important to know associated I/O tags and their addresses.
Alarm and trip value to be verified. Closed-loop control (PID parameters) and controller action to be verified.
Logical opening/closing of valves/dampers, starting or stopping of drives (pumps, compressors, etc) to be verified.
Trend group is necessary during logic/ loop testing and plant operation to know the accurate functioning of relevant
inputs and outputs.
Log reports are necessary to know the overall inputs, outputs, and performance of the plant and to plan the
resources and future maintenance. Along with this, printer functionality is also tested.
It is to verify system behavior Online or offline Configuration/Modification from the engineering station.
It is to demonstrate that controller’s actual scan time is within the project specification. This is more relevant to the
safety system.
Usually, this communication will be Modbus RTU (RS 485), Modbus TCP/IP, OPC, and IEC 61850 for electrical
systems.
Modification
Change management procedures to be followed and documented.
Spare Check
It is to verify the installed spares within the system, commissioning spares, operational spares as per contract
requirement.
Sometimes this also includes Spare space checking inside the cabinet, Hard drive space, etc.
Miscellaneous Checks
depending upon project scope of work other functionality of hardware or software can be checked like
Asset management,
cybersecurity,
alarm rationalization,
Partial stroke testing,
HART multiplexer (master and slaves), etc
Punch list
It is to document all non-conformances or faults found on the system during the acceptance test along with their
corrective actions.
At the site, one can have an overview of open punch points during the FAT test at vendor works. These non-
conformances can be attended as per the agreed schedule and resources.
Reports
once all the tests are completed, all the relevant test reports shall be preserved and handed over to end-user.
All the changes in affected drawings, documents, configuration shall be properly marked for As-built documentation.
Handover
once all the non-conformances are clear, a certain performance period is over, DCS can be handed over to the end-
user.
It is essential to have proper training in the DCS system before working on the same.