Platform

From equipment model to controller code and operator screens.

Define equipment once. Generate ControlLogix and PLCnext code, Ignition tags and faceplates, and a simulation for testing the control logic. Use Consystence’s own console where it fits your deployment.

Request a demo Check availability

Public beta for evaluation, simulation and supervised commissioning trials.

Build

One definition connects the engineering work.

Each device type brings together tags, states and relevant alarms, commands, faceplates and simulation profiles. Reuse the definition across sites and generate the artifacts each system needs.

Start from equipment

Choose from pumps and drives, IO and controllers, materials handling, and wet processing. Extend the library with your own device types. Browse all 29 types →

Generate controller code

Produce ControlLogix AOIs, UDTs and programs, or a PLCnext program. Generation is deterministic; shared behavior tests check conformance across targets.

Generate Ignition configuration

Create device connections, tag providers, UDTs, alarms, Perspective faceplates and an alarm status page from the model. The artifacts have been verified on our workshop gateway.

Example: model a conveyor with its motor, belt-drift input and interlocks. Generate its controller code and Ignition faceplate from that definition, then review and test the start, trip and reset behavior.

The engineering agent is early access. It loads generated ControlLogix code through the vendor’s engineering tool behind a human gate, verifies PLCnext programs read-only and applies Ignition artifacts.

Simulate

Exercise the logic before the commissioning window.

Run start sequences, introduce faults and inspect the resulting alarms and stops while the physical plant is still being built. Simulated data stays distinguishable from live measurements.

Native simulation

Run the standard library’s control logic without PLC hardware or a simulation licence key. Each equipment profile supplies the simulated process response.

Containerised PLCnext

Use Phoenix Contact vPLCnext to execute the PLCnext control program in a container when that execution environment is required.

Review fault responses

Check trips, interlocks, alarms and reset sequences. Simulation helps identify logic problems before controlled commissioning; it does not validate physical installation.

Our coal preparation model has exercised a belt-drift trip, cascade stop and reset in simulation. See the demonstration scope →

Operate

Give operators the equipment context.

Use generated Ignition screens alongside the controller, or the Consystence console. Introduce the platform alongside existing SCADA, starting with one process.

See data quality

The Consystence console distinguishes bad or stale values from live readings. A controller heartbeat helps distinguish an idle process, lost communication and stopped scans.

Follow alarms and commands

Inspect alarm states, priorities, on/off delays and history. Operator commands are attributed to an authenticated actor and recorded with their outcome.

Ask about the plant

Advisory AI reads tags, alarms and history to explain plant state. It may propose an action; operators execute commands through the normal control path.

For example, an operator can investigate why a pump is not running, inspect the relevant alarms and review a proposed action. AI cannot execute an equipment command.

Connect and deploy

Work with the controllers and networks on site.

Connect through the edge

Acquire ControlLogix and PLCnext data from one edge runtime. During an outage it buffers data locally and forwards retained samples when connectivity returns.

Run at site or in the cloud

The site server and cloud service share one codebase. Site screens and operator sign-in can work through cloud outages; site servers also support clustered deployment.

Keep an accountable record

History retains data provenance, including imported and simulated samples. Tenant access is enforced server-side and checked with cross-tenant tests.

Hosted operational data is stored in Azure Australia East. Advisory inference runs in Australia by default, with an on-site appliance option. Security and processing details →

Deployment options Technical documentation

Availability · 10 September 2026

What is available and how it has been verified.

Beta capabilities, supported targets and verification limits
Capability	Target	Evidence	Scope
Equipment library	29 types in four libraries	Available in beta	Coverage is listed in the catalogue; additional vertical libraries are planned.
Controller generation	ControlLogix and PLCnext	Bench-verified	Generated ControlLogix output checked on a physical processor; validate each site application.
Ignition generation	Tags, UDTs, alarms and Perspective faceplates	Workshop-proven	Generated artifacts verified on the workshop gateway.
Engineering agent	ControlLogix loading, PLCnext verification, Ignition apply	Early access	Engineering-tool operations require human confirmation; no runtime tag writes.
Simulation	Native engine and vPLCnext	Demonstrated	CHPP trip/cascade/reset exercised in simulation; incident replay is roadmap.
Operations and edge	Screens, alarms, historian, audit and buffering	Bench-verified	Dam pump station proved PLC to cloud; buffers have finite capacity.
Advisory AI	Australian cloud or on-site appliance	Demonstrated separately	No equipment-command execution path; CHPP advisory act still pending.

Planned: Modbus TCP and OPC UA runtime drivers, incident replay, reporting, mobile, alarm notifications, edge anomaly detection and a device-type marketplace. These are not included as available beta capabilities.

Questions engineers ask

Can we keep our existing SCADA?

Yes. Start alongside it, reading the same controllers and modelling one process. For Ignition, Consystence generates configuration and faceplates that connect to the PLC; Consystence does not need to sit in Ignition’s runtime data path.

Which controllers can we connect?

Rockwell ControlLogix through EtherNet/IP CIP and Phoenix Contact PLCnext through gRPC/GDS. An edge can connect to both. Modbus TCP and OPC UA as runtime acquisition drivers remain roadmap; OPC UA used by the engineering agent for read-only verification is a separate capability.

How close is the simulation to the controller?

The native engine runs the standard library’s control behavior, with shared conformance tests for controller targets. A containerised vPLCnext runs the PLCnext control program. Neither replaces validation of field wiring, timing, instruments and site conditions during commissioning.

Can we use the beta for production control?

The public beta is for evaluation, authoring, simulation and supervised commissioning trials alongside existing SCADA. Production control stays on your current system. Controllers retain authority over physical outputs, and site safety functions remain independent of the platform.

Start with one process.

Bring your controller details and the sequence you want to test.

Request a demo