SCADA quotations are notoriously hard to compare. One bidder prices the software and a
workstation. Another prices the same words but includes RTUs, field wiring, protocol
conversion, integration with legacy panels, and a commissioning team who will sit in your plant
for six weeks. Both documents say “SCADA system”.
Understanding what a SCADA (Supervisory Control and Data Acquisition)
package actually contains is the fastest way to make those two quotes comparable — and to avoid
discovering the missing 40% during commissioning.
A PLC or RTU sits in the field, reads inputs and executes control logic. SCADA sits above
them, collecting data across many such devices, presenting it to operators, storing history,
raising alarms and allowing supervisory commands. A plant can have excellent PLCs and no SCADA,
or an expensive SCADA sitting on field devices too sparse to tell it anything useful. The value
comes from the whole chain.
| Protocol | Typically Used For |
|---|---|
| IEC 61850 | Substation automation and IEDs in modern electrical networks |
| IEC 60870-5-104 | Utility telecontrol between substations and control centres |
| Modbus RTU / TCP | Meters, drives, gensets and general field devices |
| DNP3 | Distributed utility assets and remote telemetry |
| OPC UA | Vendor-neutral exchange with enterprise and higher-level systems |
Ask any bidder to state, device by device, which protocol will be used and whether a gateway
is required. Legacy equipment with a proprietary interface is the classic source of scope
creep.
An automation project lives or dies on its signal list: every point, its type, range, source
device, cable, terminal, tag name and alarm condition. It sounds clerical. It is the document
that determines panel size, cable count, engineering hours and testing duration. A bidder who
has not produced a point-by-point I/O schedule has not priced your project — they have priced
an impression of it.
Once a control system carries remote access, it needs segmentation between the control
network and the corporate network, controlled remote access, role-based user accounts with
audit trails, hardened and patched operating systems, and defined backup and recovery for
configuration and historian data. This belongs in the design review, not in a later audit
finding.
A Factory Acceptance Test at the integrator’s works, against the approved I/O schedule and
control narrative, catches logic and graphics errors while they are cheap to fix. The Site
Acceptance Test then proves the same functionality with real field devices, real communication
paths and real operators. Insist on both, with written protocols agreed in advance and punch
lists closed before handover.
VTPL delivers control and automation, including SCADA, as part of its electrical EPC scope —
which means the field devices, panels, cabling and the automation layer are engineered by the
same team rather than split across contractors who meet for the first time at commissioning.
Our projects span power utilities, oil and gas, railways, steel and infrastructure clients
across 19+ states.
Designs the automation architecture, supplies and configures PLCs, RTUs, panels and SCADA
software, engineers communications and graphics, integrates field and legacy devices, and
carries out FAT, SAT, commissioning and training.
A PLC executes control logic in the field; SCADA is the supervisory layer above it that
collects data from many devices, presents it to operators, records history and raises
alarms.
IEC 61850 is the common standard for substation automation and IEDs, while IEC 60870-5-104
is widely used for telecontrol links to utility control centres.
By comparing the I/O schedule, integration responsibility for existing equipment, number of
screens and reports, licence terms, testing scope (FAT and SAT), training and
post-commissioning support — not the headline price.
VTPL provides control,
automation and SCADA integration as part of turnkey electrical projects. Talk to our engineering team →