One change. Every impact traced.
MUR identifies how engineering changes affect project data and deliverables — and controls what must be updated, regenerated and validated.
Engineering changes propagate. Documentation often doesn't.
A control valve change can affect datasheets, I/O, wiring, loop drawings, hook-up drawings, BOM/BoQ and operating documentation. Manual impact checks are slow, inconsistent and difficult to audit.
Change intelligence before document generation.
TV-01
A control valve selection changes. The H-01 demonstrator shows how a predefined engineering change can mark dependent project results for review, recalculation or controlled re-creation.
Affected engineering deliverables
- Valve datasheetUPDATE REQUIRED
- Loop drawingUPDATE REQUIRED
- Hook-up drawingUPDATE REQUIRED
- I/O assignmentRECHECK
- BOM / BoQUPDATE REQUIRED
- Unrelated loopsNO IMPACT
Project documents are views of the project state — not independent sources of truth.
MUR maintains a controlled reference project model covering engineering objects and properties, logical and physical topology, spatial relationships, requirements, engineering decisions and validated derived results. Drawings, lists, calculations and technical descriptions are controlled views of that state.
Explore the Project Truth Model →Each document has a defined role. None has to carry the whole project.
MUR separates functional intent, equipment requirements, connectivity, physical routing and detailed wiring so that each project document is generated and checked from the appropriate engineering facts.
AI should not invent engineering drawings.
MUR combines controlled project data, approved drawing typicals and deterministic attribute writing. AI assists where interpretation is useful; engineering outputs remain structured, repeatable and traceable.
Engineering truth before document generation.
MUR is built around a simple principle: an engineering document is trustworthy only when its data, dependencies and revision state are controlled.
Know what is known
Confirmed, calculated, assumed, AI-proposed and unknown data are explicitly distinguished. An AI suggestion never becomes an engineering fact by itself.
Understand every change
A change is evaluated by its engineering consequences, not only by comparing document versions.
Use AI where it adds value
AI interprets and assists. Deterministic software handles calculations, controlled generation and validation.
Close the engineering loop
Engineering Change → Impact Analysis → Controlled Regeneration → Consistency Validation.
The latest file is not necessarily the current engineering result.
A project result becomes current only when it is based on the current approved project state, all mandatory dependencies are current and required checks have passed.
Unknown is legitimate
A value may remain unknown until engineering maturity requires it. MUR does not replace missing facts with plausible values.
A proposal is not project truth
An AI suggestion, extracted value or engineering proposal must pass the defined verification and approval step.
Affected results become stale
When a dependency changes, the affected calculation, drawing, list or description is no longer treated as current.
Current is proven
Only after required recalculation, regeneration, review and validation can the result return to current status.
Not another AI document generator. A controlled engineering system that understands change.
MUR combines controlled project data, change intelligence and deterministic engineering output into one engineering workflow.
Engineering Memory
A canonical project model preserves engineering facts, relationships and revision history instead of scattering project truth across disconnected files.
Change Intelligence
MUR determines what an approved engineering change affects before downstream deliverables are regenerated.
Deterministic Engineering Output
Approved typicals, engineering rules and controlled data produce repeatable, traceable deliverables rather than plausible AI-generated documents.
Approved typicals, engineering rules, mappings, vendor evidence and revision history remain available as reusable organizational engineering knowledge.
The same change logic can cross engineering disciplines.
The MUR demonstrator is I&C-specific, but the project-truth approach is intended for engineering changes that cross process, mechanical, electrical, civil and spatial design boundaries.
MUR does not replace discipline-specific calculations or professional responsibility. It provides a common trace of the engineering decision and identifies which disciplines and project results require renewed verification.
Designed with controlled and regulated engineering in mind.
MUR is being designed so that project data, approvals, auditability and revision control can support future alignment with relevant standards and regulated engineering environments.
Methodology & standards
ISA-88 and ISA-95 can inform how engineering data and equipment hierarchies are structured. IEC 61511 / IEC 61508 and IEC 62443 are treated as future design targets where relevant to project scope.
Controlled engineering
Controlled revisions, approved changes, provenance, validation gates and traceable regeneration provide a defensible engineering history.
GxP-capable workflows
Role-based access, separation of duties, auditability, electronic signatures and immutable revision evidence are architectural foundations for future GxP-capable workflows.
MUR is not presented as certified or validated for these standards. Formal compliance, qualification and validation remain project- and organization-specific.
From approved change to validated output.
Generating a drawing is not the hard part. Knowing when that drawing is no longer valid is.
Run MUR on one real engineering change.
Use one existing project and one approved change. MUR maps the affected deliverables, executes the controlled update workflow and produces a traceable validation result.