AxioIX Platform

Connected Digital Twins

A connected view of your physical operations. A practical path to digital twins.

Digital twins do not have to start with complex simulation or comprehensive instrumentation.

Relatively simple digital representations of assets, processes and services become far more useful once they are connected through operational relationships, giving a clearer understanding of how changes in one part of the operation affect another.

AxioIX’s platform architecture is designed to support a progressive approach. Organisations can begin with a limited operational area, connect the assets and processes that matter, and establish an initial view of their interconnected condition. Each subsequent application can extend that view, reusing existing representations and relationships while adding more sophisticated models only where the benefits justify the investment.

Discuss Your Operational Challenge
Explore the AxioIX Platform
Conceptual illustration of an industrial process plant with pumps and pipework, transitioning into a wireframe digital representation of the same equipment.
Conceptual illustration of a physical plant and its connected digital representation.

Start with connections, not complexity

Digital-twin value begins before digital-twin sophistication.

A company may have highly sophisticated models of individual pieces of equipment, yet limited understanding of how those assets affect its wider operations.

Another organisation may have relatively simple representations of many assets and processes, but gain immediate value because their relationships and dependencies are visible.

These approaches are complementary, because breadth of operational connectivity and depth of digital-twin sophistication are independent dimensions. Not every representation needs to become a sophisticated simulation. A connected operational view needs to accommodate a mix of:

  • Simple representations of condition and operating state
  • Existing third-party digital twins and monitoring systems
  • More sophisticated models, developed where they are justified

A static representation is not, on its own, a digital twin. Operational digital-twin claims require a model that is connected to, and updated from, its physical counterpart.

Conceptual two-dimensional diagram. The horizontal axis is breadth of operational connectivity; the vertical axis is sophistication of digital representations. Four regions: simple isolated representations, simple connected representations, sophisticated but isolated twins, and connected operational intelligence. Selectively enhanced twins sit between connected and fully developed. Dashed paths show that organisations can progress along either dimension; it is not a compulsory sequence.CONCEPTUAL · TWO INDEPENDENT DIMENSIONSBREADTH OF OPERATIONAL CONNECTIVITY →SOPHISTICATION OF REPRESENTATIONS →Simple, isolatedbasic representations, no linksSimple, connectedrelationships and dependenciesSophisticated, isolateddetailed twins of single assetsConnected intelligencebroad links, deep where usefulSelectively enhanceddeeper twins where justifiedPaths differ. Not a compulsory maturity sequence: organisations may already havesophisticated twins in some areas and simple representations elsewhere.
Conceptual two-dimensional diagram. The horizontal axis is breadth of operational connectivity; the vertical axis is sophistication of digital representations. Four regions: simple isolated representations, simple connected representations, sophisticated but isolated single-asset twins, and connected operational intelligence. Selectively enhanced twins sit between simple connected and connected intelligence. Dashed paths show that organisations can progress along either dimension; it is not a compulsory sequence, and deeper twins are developed only where justified.CONCEPTUAL · TWO DIMENSIONSBREADTH OF CONNECTIVITY →SOPHISTICATION →Simple,isolatedno linksSimple,connectedrelationshipsSophisticated,isolatedsingle-asset twinsConnectedintelligencedeep where usefulSelectivelyenhancedPaths differ. Not a compulsory sequence:deeper twins only where justified.

Conceptual illustration.

From asset condition to operational consequence

A failed asset does not always mean a failed service.

Consider a cooling-water circuit with two pumps. Pump A is the duty pump; Pump B is the standby pump.

If Pump A fails and Pump B takes over while maintaining the required flow, the cooling circuit remains operational. But the circuit has lost redundancy, and is now more vulnerable to a further failure.

If Pump B cannot start, cannot deliver sufficient capacity, or the switchover fails, the circuit may no longer deliver the required service.

Component condition alone is insufficient. The question is not only which pump has failed, but whether the circuit is still delivering the cooling it is required to deliver, and how much margin remains.

Illustrative duty and standby pump example in two states. State 1: Pump A, the duty pump, has failed; Pump B, the standby pump, is running; the required flow is met, so the cooling circuit is still delivering its service, but redundancy has been lost and a further failure would stop cooling. State 2: Pump A has failed and Pump B did not start; the required flow is not met and the cooling service is lost. Circuit condition follows operating rules, not the worst component colour.ILLUSTRATIVE · DUTY AND STANDBY PUMPSSTATE 1 · SWITCHOVER SUCCEEDSWatersupplyPump A · duty✕FAILEDPump B · standby✓RUNNINGCooling circuit✓SERVICErequired flow: met!REDUNDANCY LOSTa further failure would stop coolingSTATE 2 · SWITCHOVER FAILSWatersupplyPump A · duty✕FAILEDPump B · standby✕DID NOT STARTCooling circuit✕SERVICE LOSTrequired flow: not metCircuit condition follows operating rules — is the required flow delivered? —not the worst colour among its components.
Illustrative duty and standby pump example in two states. State 1: Pump A, the duty pump, has failed; Pump B, the standby pump, is running; the required flow is met, so the cooling circuit is still delivering its service, but redundancy has been lost and a further failure would stop cooling. State 2: Pump A has failed and Pump B did not start; the required flow is not met and the cooling service is lost. Circuit condition follows operating rules, not the worst component colour.ILLUSTRATIVE · DUTY AND STANDBYSTATE 1 · SWITCHOVER SUCCEEDSWater supplyPump A · duty✕FAILEDPump B · standby✓RUNNINGCooling circuit✓SERVICErequired flow: met!REDUNDANCY LOSTA further failure would stop cooling.STATE 2 · SWITCHOVER FAILSWater supplyPump A · duty✕FAILEDPump B · standby✕DID NOT STARTCooling circuit✕SERVICE LOSTrequired flow: not metCircuit condition follows operating rules(is the required flow delivered?), not theworst colour among its components.

Conceptual illustration.

Relationships make the model intelligent

The relationship determines the consequence.

A simple hierarchy can show which assets belong to a system. A relationship-aware model goes further: it describes how those assets contribute to the system’s operating capability.

Duty and standby
One component can substitute for another, subject to availability, capacity and successful switchover.
Parallel
Several components contribute to the required output. Losing one may reduce capacity without necessarily stopping the service.
Series
Components are required in sequence. Failure of a required component may interrupt the entire process, unless a bypass or alternative route exists.
Illustrative comparison of three equipment relationships, each with one failed unit. Duty and standby: the duty unit has failed and the standby unit runs, so the service is delivered but redundancy is lost. Parallel: one of three units has failed, so output is reduced below full capacity. Series: the middle unit has failed, so the service is interrupted unless a bypass exists. The same failed unit has three different consequences.ILLUSTRATIVE · RELATIONSHIP DETERMINES CONSEQUENCEDUTY AND STANDBYone unit can substitute for anotherDuty✕Standby✓Service✓DELIVEREDredundancy lostPARALLELunits share the required outputA✓B✕C✓Service!REDUCEDbelow full capacitySERIESevery unit is needed in sequenceA✓B✕C✓Service✕INTERRUPTEDunless bypassedSame failed unit, three different consequences.
Illustrative comparison of three equipment relationships, each with one failed unit. Duty and standby: the duty unit has failed and the standby unit runs, so the service is delivered but redundancy is lost. Parallel: one of three units has failed, so output is reduced below full capacity. Series: the middle unit has failed, so the service is interrupted unless a bypass exists. The same failed unit has three different consequences.ILLUSTRATIVE · RELATIONSHIP MATTERSDUTY AND STANDBYone unit can substitute for anotherDuty✕Standby✓Service✓DELIVEREDredundancy lostPARALLELunits share the required outputA✓B✕C✓Service!REDUCEDcapacity reducedSERIESevery unit is needed in sequenceA✓B✕C✓Service✕INTERRUPTEDunless bypassedSame failed unit, three different consequences.

Conceptual illustration.

One connected operational view

Understand the condition of the operation, not just the equipment.

Assets support operating systems. Operating systems support production processes, and production processes support enterprise services. In the cooling example: pump, cooling circuit, production process, enterprise service.

  • A pump failure may have no immediate production consequence if standby capacity maintains cooling.
  • An insufficient cooling supply may constrain production throughput.
  • A more serious cooling failure may interrupt production or create a quality or safety concern.

The intended platform architecture evaluates these consequences against actual operating requirements and evidence, rather than copying the worst component status upward. The connected model can inform operational decisions and workflows. Any automated intervention would require separately designed, authorised and validated control integration.

Illustrative operational dependency chain with four levels. Physical assets: Pump A has failed and Pump B is running. Operating system: the cooling circuit is delivering flow but its resilience is reduced. Production process: throughput is maintained but would be exposed if cooling failed. Enterprise service: commitments are met and future risk is under review. Links between levels are labelled duty and standby supply, provides cooling, and supports. Each level is evaluated against its own requirements; failure is not copied upward automatically.ILLUSTRATIVE · OPERATIONAL DEPENDENCY CHAINPHYSICAL ASSETSPump A · Pump B✕PUMP A FAILED✓PUMP B RUNNINGduty / standby supplyOPERATING SYSTEMCooling circuit✓FLOW DELIVERED!RESILIENCE REDUCEDprovides coolingPRODUCTION PROCESSProduction line✓THROUGHPUT MAINTAINED!EXPOSED IF COOLING FAILSsupportsENTERPRISE SERVICEProduct supply✓COMMITMENTS MET?FUTURE RISK UNDER REVIEWEach level is evaluated against its own requirements and evidence.A red asset does not turn the chain red; lost resilience is shown separately.
Illustrative operational dependency chain with four levels. Physical assets: Pump A has failed and Pump B is running. Operating system: the cooling circuit is delivering flow but its resilience is reduced. Production process: throughput is maintained but would be exposed if cooling failed. Enterprise service: commitments are met and future risk is under review. Links between levels are labelled duty and standby supply, provides cooling, and supports. Each level is evaluated against its own requirements; failure is not copied upward automatically.ILLUSTRATIVE · DEPENDENCY CHAINPHYSICAL ASSETSPump A · Pump B✕PUMP A FAILED✓PUMP B RUNNINGduty / standby supplyOPERATING SYSTEMCooling circuit✓FLOW DELIVERED!RESILIENCE REDUCEDprovides coolingPRODUCTION PROCESSProduction line✓THROUGHPUT MAINTAINED!EXPOSED IF COOLING FAILSsupportsENTERPRISE SERVICEProduct supply✓COMMITMENTS MET?FUTURE RISK UNDER REVIEWEach level is evaluated against its ownrequirements and evidence. A red asset doesnot turn the chain red; lost resilience isshown separately.

Conceptual illustration.

Three dimensions of condition

Asset health, service performance and operational resilience are different.

A single overall colour hides what matters. A cooling circuit can have a failed duty pump, maintained cooling performance and reduced redundancy, all at the same time.

Asset health
Is the individual component healthy, degraded or failed?
Service performance
Is the process or system delivering the required output?
Operational resilience
Can the system tolerate additional disruption, and what recovery capacity remains?

Evidence basis and evidence confidence

A connected model should record how each condition was established, its evidence basis, separately from how reliably it is known, its evidence confidence. The evidence basis may be:

  • Directly measured: observed by an instrument or system, such as circuit flow
  • Inferred or estimated: derived from other evidence, such as flow estimated from pump speed and system characteristics
  • Simulated or predicted: produced by a model of expected behaviour
  • Unknown or unavailable: not observed and not safely inferable

Evidence confidence is the degree to which an assessment is supported by reliable, current and appropriately validated evidence. Cooling flow might be measured directly or inferred from pump speed and system characteristics; either assessment can carry higher or lower confidence. Observations can also be stale, incomplete or contradictory, so they should not automatically be treated as current, verified conditions. A reported standby-pump start does not, by itself, prove that the necessary cooling flow has been delivered.

Illustrative cooling circuit after Pump A fails, shown with three separate conditions rather than one overall colour. Asset health: Pump A failed and Pump B healthy; evidence basis measured, from pump status. Service performance: flow delivered; evidence basis measured, from circuit flow. Operational resilience: no standby left; evidence basis inferred, from the configuration. Evidence basis is how a condition was established; evidence confidence is how reliable, current and validated the supporting evidence is. A reported standby start does not by itself prove that the required cooling flow is delivered.ILLUSTRATIVE · ONE CIRCUIT, THREE CONDITIONSCooling circuit — after Pump A failsASSET HEALTHAre the components healthy?basis: measured · pump status✕PUMP A FAILED✓PUMP B HEALTHYSERVICE PERFORMANCEIs the required output delivered?basis: measured · circuit flow✓FLOW DELIVEREDOPERATIONAL RESILIENCECan it tolerate another failure?basis: inferred · from configuration!NO STANDBY LEFTEVIDENCE BASIS AND EVIDENCE CONFIDENCEBasis is how a condition was established. Confidence is how reliable,current and validated the supporting evidence is. A reported standbystart does not by itself prove that the required flow is delivered.
Illustrative cooling circuit after Pump A fails, shown with three separate conditions rather than one overall colour. Asset health: Pump A failed and Pump B healthy; evidence basis measured, from pump status. Service performance: flow delivered; evidence basis measured, from circuit flow. Operational resilience: no standby left; evidence basis inferred, from the configuration. Evidence basis is how a condition was established; evidence confidence is how reliable, current and validated the supporting evidence is. A reported standby start does not by itself prove that the required cooling flow is delivered.ILLUSTRATIVE · THREE CONDITIONSCooling circuit after Pump A failsASSET HEALTHAre the components healthy?✕PUMP A FAILED✓PUMP B HEALTHYbasis: measured · pump statusSERVICE PERFORMANCEIs the required output delivered?✓FLOW DELIVEREDbasis: measured · circuit flowOPERATIONAL RESILIENCECan it tolerate another failure?!NO STANDBY LEFTbasis: inferred · from configurationBASIS AND CONFIDENCEBasis: how a condition was established.Confidence: how reliable, current andvalidated the supporting evidence is.A reported standby start does not byitself prove the flow is delivered.

Conceptual illustration.

Progressively deepen the digital twins

Develop sophistication where the decision requires it.

Connected digital twins can be built in capability increments. These are complementary, not mandatory sequential stages.

Context

Connect

Establish identities, representations, relationships and dependencies using existing enterprise information.

Evidence

Observe

Connect existing monitoring systems, equipment states, alarms and relevant operating evidence. Add instrumentation where necessary.

Rules

Interpret

Introduce service requirements, redundancy rules, operating constraints and condition propagation.

Depth

Deepen

Add richer measurement, statistical models, AI, physics-based simulation, prediction or optimisation, selectively.

A simple model may remain entirely adequate for some applications, while a sophisticated simulation may be essential elsewhere. Sophistication therefore develops unevenly across an organisation, wherever the decision justifies it.

Individual representations can be developed and evolved independently while sharing operational context and relationships, so validated capabilities can be reused rather than rebuilt.

Conceptual connected operational model in which individual representations have different levels of sophistication: several simple representations of pumps, a fan and a line; observed and interpreted representations of a circuit and a process; one deepened model of a compressor; and an existing third-party digital twin, all linked to a service. Sophistication develops unevenly where decisions require it, rather than every asset progressing to advanced simulation.CONCEPTUAL · UNEVEN, PROGRESSIVE DEVELOPMENTPumpPumpCircuitFanCompressorProcessServiceEXTVendor twinLinesimple representationobserved and interpreteddeepened modelexisting third-party digital twin, connected
Conceptual connected operational model in which individual representations have different levels of sophistication: several simple representations of pumps, a fan and a line; observed and interpreted representations of a circuit and a process; one deepened model of a compressor; and an existing third-party digital twin, all linked to a service. Sophistication develops unevenly where decisions require it, rather than every asset progressing to advanced simulation.CONCEPTUAL · UNEVEN DEVELOPMENTPumpPumpCircuitFanCompressorProcessServiceEXTVendor twinLinesimple representationobserved and interpreteddeepened modelexisting third-party twin, connected

Conceptual illustration.

Part of the AxioIX Platform

Digital twins are part of the platform architecture, not a replacement for it.

The AxioIX Platform vision connects physical assets, identity, location, condition, evidence, events, operational relationships, responsibilities and enterprise workflows. Connected digital twins sit within that architecture, which emphasises:

  • Interoperability across existing systems and monitoring technologies
  • Independent development and evolution of individual representations
  • Shared operational context and relationships
  • Evidence-based interpretation of condition and consequences
  • Progressive implementation and reuse of validated capabilities
  • Decision-oriented rather than technology-led adoption

Architecture and vision, not a finished product. The capabilities described on this page set out the direction of the AxioIX Platform. Not all of them are implemented, validated or commercially released today; they are being developed progressively, and the platform is not dependent on any particular sensor, AI model, simulation engine or dashboard. The diagrams and examples on this page are conceptual illustrations, not engineering simulations, customer installations or descriptions of deployed AxioIX functionality. A digital twin does not by itself establish causation or guarantee operational improvement.

Start with the answer you need

Begin with the operational decision, not the technology.

A connected model grows from the decisions it needs to support. It typically develops in three stages.

01

Establish the connected model

Begin with the assets, processes and services relevant to the operational problem, and represent their relationships, dependencies and operating requirements.

02

Understand operational consequences

Use available measurements, equipment states and other evidence to evaluate what a change in component condition means for the processes and services it supports.

03

Deepen intelligence selectively

Add richer sensing, analytical models, AI, prediction or simulation where the added sophistication improves decisions or operational capability.

You do not need to digitise everything before you can understand how your operations are connected.

Tell us which operational decision matters most. We will help identify the representations, relationships and evidence needed to support it.

Discuss Your Operational Challenge
Explore the AxioIX Platform