SERVICE 02 / SCADA DEVELOPMENT

See the system. Understand the next action.

Give operators a consistent way to navigate equipment information, recognise abnormal conditions and reach the detail they need. We scope the interface together with the data connections behind it.

What the scope can cover

Screen hierarchy

Plan an overview-to-area-to-equipment navigation structure that matches the way the site is operated.

Data integration

Agree the source controllers, communication interfaces, tag list and read/write responsibilities before implementation.

State & alarm presentation

Use consistent state conventions and clear alarm entry points rather than placing every available tag on one screen.

Project-specific functions

Define any trend, history, reporting and access-control requirements separately, with the relevant software and runtime licensing.

Agree the deliverables.

An agreed page structure and screen / tag register
The scoped SCADA engineering project and interface configuration
Documented alarm and parameter presentation rules
Integration checks and a handover record for the agreed functions

A SUITABLE STARTING POINT

For production lines with multiple control systems, equipment suppliers needing a supervisory interface, or existing sites adding central visibility without replacing every local controller.

Review checkpoints

Use these questions to define the test scope. They are planning guidance, not a statement that an unrelated installation has already passed these checks.

Tag and communication baseline

Confirm controller model, interface, tag address, data type, scale, read/write permission and refresh requirement.

Screen and alarm navigation

Review overview-to-area-to-device paths, operating-state conventions and alarm grouping with the intended users.

Optional history and reporting

Specify stored items, retention, report definitions and export requirements; do not assume every monitoring project includes these.

Responsibilities for commands

Confirm where a command is issued, how it is acknowledged and which PLC or field system retains control authority.

What shapes the quotation

Number of controllers, tags, equipment areas and operator stations
Screen complexity and the availability of process layouts or visual assets
Required alarms, historical trends, reports and access roles
Third-party point-list quality, runtime licences and integration-test conditions

Agreeing testing and engineering handover

Multi-area equipment monitoring Multi-station parameter management Integrated pumping-station control

Scope boundary

SCADA runtime licences, third-party subsystem development and site network changes are separate unless explicitly included. A monitoring screen does not establish that the underlying control is safe.

START WITH THE REQUIREMENT

Tell us what your
equipment needs to do.

A process description and an equipment list are a useful starting point.

Discuss your project