PZone ERP v1.0 · Manual

Chapter Seven — The Technical Office: Document Control, Quality and the Gates

The technical office controls your engineering documents (ISO 19650) and execution quality — and it is the engine behind the "gates" you met in Chapters 4 and 6: the approved sample opens purchasing, and a non-conformance holds back the payment certificate.

Chapter 7 — Technical Office: document control, quality & the gates

📑 Document control (ISO 19650) ✅ Submittals and inspection ⚠ Non-conformance (NCR) 🔒 Quality gates over the money
☰ Chapter index

01 Before we start

The Technical office module is responsible for two things: controlling engineering documents (on the ISO 19650 standard) and execution quality. And it is the engine behind the "gates" you met earlier — the approved sample is a condition for purchasing (Ch.6), and a non-conformance holds back the payment certificate (Ch.4).

i
An add-on enabled by the platform administrator (the link /technical-office, the "Technical office" menu). It has 11 registers (tabs), the default being "Overview". Editing is for editors (owner/admin/manager), and the viewer only reads.
Documents and transmittalsISO 19650 Submittals · inspection · NCRQuality Changes · correspondence · handover Technical officedocument control and quality Procurement gatean approved sample opens purchasing Quality holdNCR/RFI holds the certificate Commercial change orderfrom the technical change
Figure 1 — The technical office registers (documents, quality and changes) feed into three gates: opening procurement, holding quality on payment certificates, and generating the change order
i
Each register is attributed to a project (optionally) and may be linked to a document or a catalog material or a subcontractor — and it is precisely these links that drive the gates (Section 6).

02 The document register and transmittals

The foundation of the module: a document library controlled by its revisions, and a numbered distribution register that links them to whom they were sent.

Document register
The drawings and documents under control, with their revisions. For each document: number · title · discipline · type (drawing/specification/calculations/report/BIM model…) · suitability code (ISO 19650: from S0 "work in progress" to A1 "approved-published") · CDE status (work in progress / shared / published / archived) · review status. The New revision button creates a new current copy, serialises it above the previous one, and archives the old one automatically. And the Current revisions only toggle hides the superseded ones.
Transmittals
Numbered issue/distribution records (TR-…) that link document revisions to one another: the subject, the recipient, the purpose (for approval/for review/for information/for construction/for records), the method, and the status (draft/issued/receipt confirmed) — with a PDF cover sheet ready to send.

03 Technical submittals

The Technical submittals tab: material submittals and shop drawings with the consultant's review cycle and return codes — and it is the core on which the procurement gate depends.

Submission Consultant review Return code A — approved B — approved with comments C — revise and resubmit D — rejected A and B open procurement C → resubmit with a new revision
Figure 2 — The submittal cycle: submission ← consultant review ← return code; A/B approved (opens procurement), C revise and resubmit, D rejected
Types and fields
Types: material submittal / shop drawing / sample / method statement / prototype. Each submittal has an automatic number (SUB-…), a specification item, a linked document, a linked catalog material, the contractor and consultant, submission/required/return dates, and the return code.
Return codes
A approved · B approved with comments · C revise and resubmit · D rejected · (under review). Only A and B count as "approved" and open the purchasing of that material (Section 6). The Resubmit button opens a new revision and closes the previous one.
The critical link
Linking the submittal to the catalog material is the key by which procurement recognises "does this material have an approved sample?". Without the link, the gate does not open.

04 Requests for information and inspection

Two daily registers: technical queries directed to design/the consultant, and inspection requests for works and materials.

Requests for information (RFI)
A technical query with an automatic number (RFI-…), a priority and a cost/time impact. The cycle: Open → Answered → Closed (and void). The "stops work / holds the payment" option reveals the subcontractor and held amount fields — so the value of the works concerned is held in the client's payment certificate and payment of the subcontract certificate is prevented, and the hold is lifted as soon as it is answered/closed (Section 6).
Inspection requests (IR/WIR)
A request to inspect works or materials with an automatic number (IR-…): the type, the location, the work reference / bill of quantities item (text), the inspector/consultant, and the result (approved / approved with comments / rejected / pending), and the status (requested/scheduled/inspected/closed). A non-conformance report can be linked to an inspection.
i
The bill-of-quantities item reference in the inspection request is free text (no structural link to the item) — for attribution and documentation.

05 Non-conformance (NCR)

The Non-conformance tab: NCR reports on the ISO 9001 style to record deviations, determine the disposition and close them — and they are the quality gate with the strongest impact on the money.

Open In progress Closed The held value is excluded while open/in progress Disposition: rework · repair · accept as is · reject · concession Bridge: "Create return" → Procurement › Returns
Figure 3 — The NCR cycle: open ← in progress ← closed; the held value is excluded until closure, the disposition is documented, and a material return is created toward procurement
Fields and cycle
An automatic number (NCR-…), a severity (minor/major/critical), a source (inspection/audit/the client/internal), a description, the disposition (rework/repair/accept as is/reject/concession), a root cause and a corrective/preventive action, and a responsible party and a due date. The cycle: Open → In progress → Closed.
The held value
The subcontractor and held value fields: as long as the NCR is open or in progress, this value is excluded from the client's payment certificate and payment of the subcontract certificate is prevented (Section 6).
The material return bridge
A "Material return" section: you specify the source purchase order, the material and the rejected quantity, and the Create return button creates a vendor return (draft) that you post from Procurement › Returns (Ch.6).

06 The gates: how the technical office protects the money

Here is the module's great value: its registers are not documentation only, but binding controls over procurement and payment certificates.

1) The procurement gate Approved sample (A/B) Purchase order: allowed ✓ No sample · C · D Purchase order: blocked ✕ 2) The quality hold on payment certificates Open NCR / blocking RFIwith a held amount and a subcontractor Excluded from the client certificate value Prevents payment of the subcontract certificate The hold is lifted as soon as the NCR is closed or the RFI answered
Figure 4 — Two gates: the approved sample (A/B) is a condition for the purchase order, and a non-conformance/blocking request holds a value from the client's payment certificate and prevents payment of the subcontract certificate until closure/answer
The procurement gate
When awarding a request for quotes or saving a purchase order, material line items that do not have an approved sample (code A or B) linked to the catalog material are not accepted — and hints appear on the line item: ✓ Sample approved (code …) or ⚠ No approved sample. Services and items without a catalog are exempt.
The quality hold on payment certificates
The value of any open NCR or blocking RFI (with a held amount) is excluded from the approved amount in the client's payment certificate — with a "quality hold" tag — and approval/payment of the subcontract certificate against that contractor is prevented. And the hold is lifted automatically as soon as the NCR is closed or the RFI is answered/closed.

07 Technical changes, correspondence and handover

Three registers complete the project cycle: the engineering change that feeds the commercial side, correspondence tracking, and the final handover file.

Technical changes
An engineering change (design/site instruction/value engineering…) with a cost, sale and time impact. The Create commercial change order button generates a variation order (VO) in the commercial module and links it — so after its approval the adjusted contract value and revenue enter (Ch.4). (Requires specifying a project.)
Correspondence
Incoming/outgoing with an automatic number (LTR-…), with tracking of "whose court the ball is in" (us/them/closed) and reply dates — to manage your claims and notices with the parties.
Method statements and handover
Method statements: work procedures with a risk level and approval. And handover: the project closeout list (As-built drawings, operation and maintenance manuals, warranties, certificates) with a status and completion percentage and a PDF file.

08 Permissions — and the summary

ActionOwnerAdminManagerViewer
View the eleven registers (read)✔✔✔✔
Documents and transmittals — create/new revision✔✔✔✖
Submittals/RFI/inspection/NCR — create, review and close✔✔✔✖
The bridges — change order · material return✔✔✔✖

All registers are for editors (owner/admin/manager) in creation, review and closure, and the viewer only reads. Note: "the consultant/inspector" in the forms is a text field, not a binding role within the system — so the return code, the inspection result and the closure of the NCR are set by any editor.

✓
Chapter Seven summary: the technical office links quality to the money: the approved sample opens purchasing, a non-conformance/blocking request holds the payment certificate until closure, and the technical change generates the commercial order — on top of full document control (ISO 19650) and a handover file that closes the project. The support modules (HR & payroll, rentals, governance) remain for later chapters.