← All guides
Process digital twins

Process digital twins: a flowchart is not an evaluable twin

At least once a month, a procurement slide deck attaches a static Swimlane flowchart, slaps "Digital Twin of Permitting Operations" in the subtitle, and treats the diagram as software architecture. A drawing you can't query against live queue state or replay against production logs isn't a twin—it's wall art.

Author: Escherbridge. Published . Last reviewed: , America/Denver.

NIST IR 8356 (Security and Trust Considerations for Digital Twin Technology, February 2025, plus its 14 February 2025 summary release) is explicit that digital twins are not restricted to turbines and buildings: "A digital twin can emulate both physical things (e.g., buildings, electronics, living things), and non-physical things (e.g., processes, conceptual models)." Yet the exact same engineering bar still applies: it must provide "the capability to evaluate this entity," and "The full benefits of digital twin technology will require interoperable definitions, tools, and standards as well as early consideration of digital twin cybersecurity and trust."

If your entity is an approval pipeline, settlement graph, or permit routing state machine rather than concrete walls, the base definition in What makes a digital twin worth maintaining still governs whether you actually built anything testable.

What separates a testable process twin from a static diagram

A real process twin needs an unambiguous sync boundary—how state events enter from the field—an explicit way to evaluate queue bottlenecks or stalled approvals against reality, and early trust controls deciding who is allowed to propose or override transitions. Whenever automated tooling acts on that state, logging the decision path belongs right alongside what to write down when software recommends.

Scope and boundaries

NIST's warning on interoperable standards and early trust is a technical engineering standard, not a PrimusNeo roadmap guarantee. This page does not claim a live PrimusNeo process twin, does not fabricate throughput or factory numbers, does not detail exploit steps, and is not investment or customer-deployment prose.

A situation like this

A proposal labels an onboarding flowchart a "process digital twin" while omitting event ingestion, lag tolerance, rollback semantics, and an evaluation check—leaving teams unable to verify whether the diagram matches production tickets.

Sources

  1. Voas, Mell, Laplante, and Piroumian, Security and Trust Considerations for Digital Twin Technology, NIST IR 8356, February 2025. https://nvlpubs.nist.gov/nistpubs/ir/2025/NIST.IR.8356.pdf · DOI: https://doi.org/10.6028/NIST.IR.8356
  2. NIST, "Security and Trust Considerations for Digital Twin Technology: NIST Releases IR 8356," 14 February 2025. https://www.nist.gov/news-events/news/2025/02/security-and-trust-considerations-digital-twin-technology-nist-releases-ir
  3. Definition sibling: What is a digital twin /guides/digital-twins

Also in this section

The useful next step is to say what process is being represented and how it can be evaluated, or to read What is a digital twin. If something on this page is wrong, write to us.