Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Map which packages need FAT, SAT or both
Every purchase order on a project carries some test obligation, but on a typical plant job only a fraction of the equipment packages justify sending someone to the vendor's shop. One table listing each package, the tests its specification demands and whether they happen at the factory, on site or both lets you plan witness travel, budget and schedule before vendors start booking test dates.
First tasks
- Export the current procurement register with tag numbers and PO references
- Mark each package FAT, SAT, both or review only with a one-line reason
- Note the expected test month beside each package from quoted delivery dates
- Walk the table through with the package engineers and record their changes
Test requirements matrix from the purchase order
Test obligations are scattered across the purchase order, the equipment datasheet, the project specifications and the standards those documents reference, and vendors quote against whatever they happened to find. Pulling them into one matrix per package, clause by clause, is how you discover before the test that the specification asked for a mechanical run test or a noise test that the vendor never priced.
First tasks
- Open the PO, datasheet and specifications for the most critical package
- List every test clause with its document number and section
- Ask the agent to compare the matrix with the vendor's quoted test list and flag gaps
- Send the gaps to the vendor as technical queries through the buyer
Inspection and test plan review with each vendor
The inspection and test plan is the working contract for what gets checked, by whom and when, and its hold, witness, monitor and review codes decide whether production can carry on without you. Reviewing each vendor's ITP against your requirements matrix soon after award stops the classic failure where a hold point appears for the first time in a notification email.
First tasks
- Chase every ITP not yet received for packages on the FAT list
- Check each ITP line against the test requirements matrix
- Mark client hold and witness points on the critical tests
- Return the commented ITPs with a resubmission date