PMT
Request a demo
← Modules

Modules / Engineering

Engineering

Every document: its revision, its review, its transmittal and who holds the controlled copy.

Used by Engineering manager, lead and design engineers, document controllers, client reviewer, vendors (VDRL)

EPCIMA PMT Engineering screen.
Engineering · overview

What it does

Engineering owns a list of documents it has to produce. We move each one through your status ladder, through review inside the company and by the client, and out again as a new revision. Technical queries, take-offs and as-built markup sit in the same register, with the clocks and the sign-offs. Document control is the gate on the way: number, stamp, transmittal, distribution, and who holds which revision.

What the dashboard reads from it

  • Documents by discipline and status
  • % AFC against planned
  • Open TQs and average response time
  • Review overruns and documents overdue for return
  • Vendor document review results (A/B/C)

How the work flows

3 flows · 18 steps · 2 gates · 2 in the portal

Document lifecycle

One register, one status ladder per project. A document only moves forward when the right people have signed.

  1. Deliverable listLead engineer
  2. Create or reviseDesign engineer
  3. Check and approveThree different peoplegate
  4. Number and stampDocument control
  5. Transmittal outDocument control
  6. Client reviewClient, in the portalportal
  7. Code A / B / CRecorded with date
  8. Re-issueNext revision

Technical query

A question from site or a vendor becomes a record with an owner and a clock.

  1. Raise TQSite, vendor or engineer
  2. Assign disciplineLead engineer
  3. AnswerDiscipline engineer
  4. Impact flagsCost, schedule, MTO
  5. CloseOverdue if the clock runs outautomatic

Vendor documents

The VDRL is agreed at kick-off. Vendors upload against it; engineering returns a code.

  1. VDRL per orderAgreed at kick-off
  2. Vendor submitsVendor, in the portalportal
  3. ReviewWorking-day SLA
  4. Code A / B / CEngineering
  5. Production and FAT gatesCode B allows production, blocks FATgate

Gate: cannot pass until recordedPortal: the outside party does this stepAutomatic: the system does it

Screens

EPCIMA PMT Engineering: Master document register.
Master document register
EPCIMA PMT Engineering: Review results by document.
Review results by document
EPCIMA PMT Engineering: Technical query register.
Technical query register
EPCIMA PMT Engineering: Vendor documents (VDRL).
Vendor documents (VDRL)

Screens from the working product. The project data is illustrative, and company and people names are replaced. Click a screen to enlarge.

What is inside

22 capabilities in 5 groups

Register

  • Master document register per discipline
  • Revision and status ladder per project (IFR, IFA, AFC, AB)
  • Status codes are configuration, not codeconfigured
  • Search by number, tag, discipline, status
  • Full audit trail per document

Review

  • Preparer, checker and approver must be three people
  • Inter-discipline review sheets with per-reviewer sign-off
  • Client review results in the portal, no email chainsportal
  • Review overrun flag when the return date passesautomatic
  • Latest-revision check so site never builds from the wrong revision

Control

  • Transmittals in and out with reason codes (IFI, IFC, IFA, AFC, ASB)
  • Distribution matrix with receipt sign-off on controlled copies
  • Overdue transmittal returns flagged both directionsautomatic
  • Design change notices, change orders, rework notices

Queries and take-off

  • Technical queries linked to a document or a tag
  • Close-out with impact flags: cost, quality, schedule, design, MTO
  • Material take-off per revision
  • MTO change notifies material controlautomatic

Vendor documents

  • Vendor document register (VDRL) per order
  • Vendors upload against the list themselvesportal
  • Status codes A / B / C with production and FAT gates
  • As-built markup and project data book

How it connects

RecordsStay in this module. Entered once, with an owner and a date.
DashboardsL1 to L3 read a snapshot of this module on a schedule and print where the number came from.
RolesOne identity across modules. Vendors and the client see only their own packages.
Source per projectManual register in PMT, or the module feed, chosen in Config per project.

All modules and portals

← RiskProcurement →

See Engineering on your project.

A short walkthrough on your own project structure. Send us your WBS and we load it in before the call.

Request a demo by email WhatsApp

We reply within one working day.