Features

Everything for a technical project, in one place

From the first request to the file for production. This is what we are building; anyone on the waiting list helps decide the order.

Gates

Every gate a checklist and approvals

  • Six phases with five gates, or a short version for a shutdown
  • Per gate the deliverables per discipline, with a counter
  • Approval in steps: submit, co-sign, decide; whoever is informed gets a message automatically
  • Open HAZOP actions or an open MOC block the gate
  • The decision goes onto the decision log automatically
A gate in Project2Work: approval in three steps and the deliverables per discipline
Documents

Always the right revision

  • Every document with number, revision and status
  • What changed in each revision, and who approved it
  • Supplier documents per order, with deadline and reminder
  • A deliverable is only done when the right revision is approved
Documents in Project2Work: revision C in review, revision B valid, and supplier documents that are late
Testing

FAT and SAT on the tablet

  • The test protocol as a checklist, OK, not OK or n/a per step, with a measured value or photo
  • A not OK becomes a punch list item straight away
  • Also works offline, in the supplier’s workshop
  • Signed off by supplier, project and client, with an audit trail for GMP
A FAT on the tablet: step 3.3 is not OK and has become a punch list item
Also in Project2Work

What else is included

Requests and quotes

Requests to suppliers and quotes compared per URS requirement.

Meetings and minutes

Minutes during the meeting; actions and decisions go onto the lists automatically.

HAZOP

Guide words against parameters per node, with actions that guard the gate.

Punch list

Photo first, type and priority, and a status that updates itself.

Schedule

Milestones and gate dates from MS Project or Primavera P6.

Handover

A file per system, with equipment passed on to maintenance.

What do you miss most?

Join the waiting list and tell us. Then we will build that first.