Comparing a revision with the one before tells you what moved. The harder question is whether anyone has dealt with it. This release is about that.
What's new
- See which changes are still open. Each difference found between drawing revisions is now recorded as a change you can review, act on and close, with a history of what was done and by whom. A change that a later revision overtakes is closed for you, so the open list doesn't fill up with things that no longer matter.
- Issue a register of open changes to the right people. Generate a drawing change register by issue or by package, then print it, save it as a PDF or CSV, or send it to the package contacts through the distribution flow you already use. A subcontractor can see the changes that affect their package without being sent everything.
- Compare any two revisions, not just the last two. Put P04 against P06 when P05 was never circulated, or when you need to know what changed since the issue a package was built from. Comparing uses Intelligence Units, and a pair you've already compared opens straight away instead of being run again.
- Read a comparison in plain terms. Changes now carry an impact rating in words rather than a score, with a flag where one may have a cost consequence. A "What changed" tab on each drawing lists the areas that moved and where each one stands.
- Start from Home or your phone. Home shows how many drawing changes are open and links to the filtered list. On a phone, open changes are grouped by issue so you can work through them on site.
- Find documents by type first. The documents list now groups by type, with counts that come from the whole register rather than the page you happen to be on.
- Say so when a file is already there. Uploading a file that's already in the project now returns the existing document and tells you no copy was made, so the same sheet doesn't end up linked to a RAMS review twice.
- Answer each RAMS finding when you accept. Accepting a RAMS that raised findings now asks for a response to each one, so the record shows what was waived and why.
Why it matters
A drawing change that nobody owns tends to turn up at the wrong moment: a bay built to the previous issue, or a variation claimed for something the site was never told about. Recording each change, closing it when it's dealt with, and issuing the open ones by package gives you a list you can put in front of a subcontractor and a trail if the change is disputed later.
New featureImprovementDocumentsDrawings