Revision
Track every issued set against the ones before it, then pick two points and see what changed, sheet by sheet, located on the drawing
Revision answers the question a superintendent asks every time a new set lands: what actually changed, and does it hit work that is already open.
You pick two points on the project's timeline, run the comparison, and get a list of located changes you can open on the sheet.
The timeline
The comparison axis is whichever the project actually has.
- Issued sets. If the project has two or more published drawing sets, the timeline is those sets, oldest issue first. The selects read From set and To set. This is the axis most projects use, because sheets arrive inside an issued set.
- Revision history. If the project grows revisions document by document rather than by issuing sets, the timeline is the per-sheet revision chain instead, with a baseline set and Rev 1 onward. The selects read From and To.
Either way, the two selects are what the run uses. Clicking a node on the timeline moves the To end; clicking the earliest node moves the From end back to the beginning.
From must come before To. An equal or inverted window is refused with the reason stated, never silently corrected.
Compare two points
- Set From and To.
- Press Detect changes. The button reads Detecting while the run is in flight.
- Read the change list on the left, and the sheet on the right.
A set-to-set comparison is hundreds of sheet pairs and real credits, so before starting one STRUX looks for a comparison that already exists for exactly that pair. If it finds a completed one it shows those results and says it is showing an earlier comparison, with a Re-run button if you want a fresh one. If the lookup fails, a new run starts rather than blocking you.
Reading the results
The metric strip counts Changes, Added, Revised, Moved, Not examined, and Sheets touched.
| Kind | Meaning |
|---|---|
| Added | Content that is on the To side and not on the From side |
| Revised | Content that exists on both sides and differs |
| Moved | Content that exists on both sides in a different place |
| Not examined | A difference was detected but nothing has said what it is |
Not examined is not a fourth kind of change. The classifier covers up to 24 regions per sheet and leaves the rest unlabelled, and a failed classification does the same. Those regions are counted separately and are deliberately not counted as changes, because naming a change nobody examined would be inventing one. The list says so above the rows.
On a set comparison you also get set-level chips: how many sheets were added, how many removed, and how many the engine could not compare at all.
Two sources, never mixed
- After a run, the rows are the located change regions the diff engine produced. Each carries a position on the sheet, so the pin lands where the change is. When a run is ready, its output is the only source: an empty result renders an empty list rather than falling back to something softer.
- Before a run, on the revision-history axis only, the rows are sheets whose revision number changed inside the window. These have no located position, and the list says they came from the revision history and that running Detect changes is what locates them on the sheets.
The sheet
Selecting a row shows the sheet on the right with the change pinned on it, where the project has a rendered sheet image for that document. Many documents do not, in which case the panel shows a labelled tile instead of hanging on a render that will not arrive. Expand drawing opens the full viewer either way. See Sheet viewer.
Upload a revision
Upload revision is the one write this instrument offers.
- Press Upload revision.
- Add the revised drawings. PDF only.
- For each file, choose the sheet it revises under Revision of. An exact sheet-number match is selected for you; confirm it.
- Add an optional reason, for example a bulletin number or the RFI it answers.
- Upload.
Two files cannot revise the same sheet in one go; the dialog says so. Sheets that arrived as part of a drawing set cannot take a per-sheet revision yet, and those are labelled with that reason rather than being silently unselectable. Issue a new set for those instead. See Drawings.
What a comparison feeds
An approved submittal whose covered sheets changed in a later revision is flagged for re-review in Submittal Review.
Troubleshooting
"No revisions yet." The baseline set is the only record on the project. Upload a revision, or publish a second drawing set, and the timeline gains a second point.
"Pick two sets and run Detect changes." The window is set but no comparison has run for it yet.
"No changes located between these two sets." The run completed and found nothing. That is a real result, not an error.
Detect changes is disabled. Either the window is invalid, in which case the reason is stated above the selects, or you are on the shared demo project, which is read only.
"Could not load the issued sets." The set list failed to load, so the instrument fell back to the revision-history axis. It says so rather than pretending the sets do not exist.
The comparison is still running when you come back. Runs continue on the server. Reopen the instrument and the state is picked up.
A count of sheets not compared. Those sheets failed inside the engine. The chip carries the reason.