Check RFI answers before you close them, and stop flagged plant

This update covers a couple of weeks, so it's longer than usual. The main changes are to RFI answers and plant, with several smaller fixes to packages, drawings and RAMS.

What's new

• Know whether an RFI answer settles the question. When an answer comes back, PlanOps reads it against the question. The review opens with what was read, quotes the words it relied on, and has a closure note or a follow-up question ready for you to edit. If you ask again, the responder's page opens with what you still need from them above their previous answer. Each assessment uses IU credits, and you can turn the automatic assessment off for a project and run it on a single answer when you want one.
• Find out when a new revision affects an RFI answer. When a new revision arrives of a document that an open RFI was raised against, the RFI's answer is assessed again, so you find out whether it still holds.
• Give the person answering the relevant project information. When you ask for an RFI answer you can choose to show the relevant package of works, temporary works and programme activities on their answer page, so they can see what the RFI question affects.
• A plant defect on an examination report is now flagged. When PlanOps reads a report of thorough examination that lists defects, it records the examination and raises each defect as an open defect on that check. A defect the examiner describes as a danger now, or as a reason not to use the machine, is marked stop-work, so the next daily check can't start until it's cleared. The defect opens the report itself, so you can check the examiner's wording before you clear it.
• Move a machine to another site and keep its history. Transfer plant to another project in your organisation. The old site keeps its record, marked off hire, and the new site gets an on-hire record with the machine's documents, certificates, checks and QR sticker.
• Plant records you can show an inspector. A check's certificate is now picked from Documents or uploaded in place, and each check names a responsible person on the project. You can download a whole project's daily checks for a date range as CSV or PDF, and a cleared defect shows who cleared it, when and why.
• See what each package is waiting for. Every row on the Packages list now shows the package's next step, such as assigning a contractor, requesting the RAMS or creating the handover. If a package already has a handover, PlanOps opens it instead of starting a second, so a subcontractor isn't asked for the same pack twice.
• Build a handover from what you've already accepted. Add accepted information schedule deliverables and inbound handover items to an outbound handover at their latest revision, with the source of each one shown. You don't have to collect the same documents a second time.
• Give each drawing change an owner. Assign changes to a person from the changes queue, one at a time or in bulk, and generate a register from the filters you've set. A change nobody owns is easy to spot.
• Show a subcontractor what changed without giving them an account. Share a drawing comparison by link. The link opens a read-only view, expires after 30 days and can be revoked at any time.
• See which RAMS need attention before they lapse. RAMS that are due or expiring within 14 days move to Needs attention with a countdown, accepted RAMS read Active, and expired ones get their own group.
• Get back a record that was deleted by mistake. Project and organisation admins can delete an item from the list's row menu, and restore deleted RFIs, RAMS, plant, packages, handovers and temporary works from the project's Settings.
• Smaller things. Large PDFs whose text is too complex to extract are read from the page image, so a long drawing pack or RAMS isn't reviewed with pages missing. The documents list hides a superseded revision as the new one arrives and shows how many earlier revisions sit behind it.

Why it matters

An RFI answer that doesn't actually answer the question often isn't noticed until the work is built from it. Reading every answer against its question, and making it easy to ask again, means you find the gap while it's still a quick email.

Under LOLER, a report that lists defects is still a completed examination, but those defects decide whether the machine can be used. If they only live in a PDF, the machine keeps working until someone reads it. Raising each one against the check means the next person to start a daily check finds out, and the record shows when the defect was found and when it was cleared.