Insight
Engineering Change Intelligence for EPC
From clause to tag. From tag to space. From revision to evidence.
The problem with change in EPC is not the change itself. It is proving why it changed, when it changed, and what it affected.
The real unit of change is not a document. It is a connected chain of engineering evidence over time.
Thesis
Margin erodes when change cannot be proved — not when change happens.
Owner comments, TQs, Owner Clarifications, CRS, transmittals, and revised drawings or models do not live apart. They form one engineering decision chain over time. When that chain breaks, impact scope and commercial discussion lose their footing.
Unit of change
Not a document — a time-linked evidence chain.
A single change rarely closes in one file. The same issue spans revisions, disciplines, drawings and models, and multiple transmittals. What must be traced is the connection among clauses, identities, objects, neighborhoods, responses, and send history.
Time axis
Reconstruct what was true at each moment.
Change intelligence is not only the current state. It rebuilds the criteria and deliverables that applied at each point in time.
- 01
Baseline
Clause · Model/Drawing Rev
- 02
Comment / TQ
Identity · Transmittal
- 03
Clarification
Requirement interpretation shifts
- 04
Impact
Object · Neighborhood · Rework
- 05
CRS / Response
Evidence · Send history
- 06
Review
Change-impact review
Flow
From clause to change-impact review
A requirement or document clause moves through Tag Resolver and Spatial Resolver into an Evidence Snapshot and change-impact review.
- 01
Requirement / Document Clause
- 02
Tag Resolver → target object
- 03
Spatial Resolver → affected neighborhood
- 04
Model / Drawing revision
- 05
TQ / Owner Clarification / comment / CRS
- 06
Transmittal / revision history
- 07
Evidence Snapshot
- 08
Change-impact review
Connection
After the object — the affected neighborhood.
Once Tag Resolver finds the target, Spatial Resolver selects the spatial neighborhood for review and impact. Change impact includes surrounding relationships, not only a single object.
See Spatial ResolverEvidence
An Evidence Snapshot is a context package — not a screenshot.
It keeps visual evidence with engineering metadata: objects, revisions, clauses, TQ/OC/CRS, and transmittals. Humans and AI can review the same identities, revisions, and relationships along the change history.
Scope
What this supports — and what it does not claim
- Change impact analysis
- Commercial review support
- Evidence for change-order preparation
- Traceability
- Guaranteed entitlement, recovery, litigation, or savings
- L3D Agentic Robotics