Smart Infrastructure / SCADA

Operate distributed infrastructure from one control layer.

Combine telemetry, device status, control, alarms, automation and GIS in a unified operational environment.

Book a DemoDiscuss this Solution

Automation cabinet with DIN-rail modules, an industrial motor and a process instrument connected to the Vision Smart Platform core, with a command state list

Above local control, not instead of itSafety and real-time behaviour stay in the field.
Commands that confirmResponse metrics validate what the equipment actually did.
One estate, one historyTelemetry from every site in a single, comparable model.

Challenge

Control systems age faster than the assets they run.

Industrial and utility sites usually already have control. What they lack is a layer above it that everyone can use.

Islands of supervision

Each site or subsystem has its own supervision, with its own tags, its own screens and its own idea of what a device is.

History that stops at the site

Trends are often local. Comparing this station with that one, or this year with last, means exporting and reconciling by hand.

Commands without a trail

When an operator acts, the useful question later is who did what, when, and whether the equipment actually confirmed it.

Architecture

An operational layer over the control you already run.

The platform does not replace local control. It models the assets, normalises what they report and gives the estate one place to be operated from. The exact architecture is configured around the devices, protocols and processes of each deployment.

Field equipmentSensors, actuators, instruments

›

Controller or RTULocal logic and safety

›

NetworkEthernet, fibre, LTE, MQTT

›

Protocol instanceContainerised service per protocol

›

Vision Smart PlatformRegistry, telemetry, rules, screens

What each stage becomes in the platform

Assets become instancesControllers, instruments and accessories are modelled as versions and instances, grouped into IoT systems that match the real installation.
Telemetry becomes metricsMetric templates decode the payload into values with units and timestamps, so a reading means the same thing across sites.
Actions become validated commandsA command template defines the parameters supplied at execution and the response metrics that confirm the equipment did what was asked.
Local control stays localSafety and real-time behaviour remain where they belong. The platform is the operational and administrative layer above them.

Operational scenario

A command that has to be provable.

The value of the operational layer shows up after the action, not during it.

Illustrative example

1

An operator issues a command

The command template supplies the parameters the equipment needs, and the platform records who issued it.

2

The command is queued

It travels through the protocol instance for that network, with its own state rather than a fire-and-forget message.

3

The equipment responds

The device reports back, and the response metrics named on the template are what gets checked.

4

The command is validated

Sent, confirmed and failed are distinguishable states, so an operator is not guessing.

5

The dashboard reflects it

The new state appears on the screens and, where relevant, on the map.

6

The trail survives

The audit section keeps the action with its old and new values, available long after the shift ends.

This example is illustrative. Which commands exist, who may issue them and what confirms them are configured per deployment.

Operational scenario

Operational metric changes
Rule
Command / workflow
Confirmation
Audit

Outcome

One operational view across heterogeneous infrastructure.

 

Inside the platform.

Vision Smart Platform operational dashboard: device alerts, cumulative active energy, programmed and reported values, active power charts and a command control

What it is built on

The platform capabilities behind this solution.

Use the documented device, data, automation, visualisation and integration capabilities to build a supervisory layer around your existing control systems.

Digital Twins & Device Lifecycle

Controllers, instruments and accessories as models, versions and instances, organised into IoT systems and groups.

Explore ›

Data, Metrics & Commands

Metric templates for telemetry, command templates with response validation and a command state over time.

Explore ›

Rules & Automation

Conditions on metrics, parameters and time, with priorities and operational enable or disable.

Explore ›

Connectivity & Integration

Protocols as containerised service instances, plus CODEC definitions where payloads need decoding.

Explore ›

Dashboards & Visualization

Operational screens per version and per installation, built from a widget palette.

Explore ›

Security & Audit

Identity, roles and permissions, with a change history that records old and new values.

Explore ›

Fit with what you already have

Existing controllersEquipment is described by its model and version. A different vendor is a different model, not a different platform.
Existing control logicLocal control and safety stay where they are. The platform adds registry, history, rules and screens above them.
Existing systemsIntegration APIs let another application read the same values or trigger an action on the same objects.
What stays configurableModels, parameters, metric and command templates, rules and dashboards are configured in the interface.

See how Vision can fit your deployment.

Share your current devices, connectivity and operational objectives.

Discuss your project