Control System Engineering Vendor Deliverable List

One of the first things I do at the start of any control system project is sit down with the vendor’s proposed document submission list and compare it against my own checklist.

More often than not, something is missing. Sometimes it is the Nest Loading document. Sometimes the ITP never gets raised until FAT week. And in a few cases, the vendor arrived on site without a proper SAT Procedure — expecting to run acceptance testing on a live plant from memory.

Every one of those situations is avoidable.

This article is a focused checklist of vendor engineering deliverables only — the documents your BPCS or DCS vendor is responsible for preparing and submitting throughout the project.

Use it to build your Vendor Document Requirement (VDR) list at project kick-off. it at FAT and SAT as your acceptance gate. and it at handover to make sure the operations team inherits a complete, traceable package.

How to Use This Checklist

Issue this list as your formal VDR — Vendor Document Requirement schedule — at project kick-off.

Assign a document number, planned submission date, and required date against each item. Track every submission through your document review and approval cycle.

The checklist is organized into five phases of vendor activity:

• Phase 0 — Project Kick-Off
• Phase 1 — Engineering & Design
• Phase 2 — FAT
• Phase 3 — SAT
• Phase 4 — Handover

A master summary table at the end compiles all 27 documents in one place.

Note: Not every document applies to every project scope. A small panel expansion has a lighter deliverable set than a full DCS greenfield installation.

Use your engineering judgment, document any conscious exclusion, and agree the final VDR with the vendor in writing at project kick-off.

Phase 0 — Project Kick-Off Deliverables

These two documents come first — before any engineering starts. They tell you what the vendor plans to deliver and when. Without them, you have no baseline to track the vendor against.

1. Vendor Document Deliverable List (VDDL)

The vendor’s own complete list of all documents they commit to submitting on the project — document number, document title, revision schedule, planned submission dates, and required submission dates.

This becomes your tracking tool for the entire project. Review it against this checklist at kick-off and formally agree any additions or exclusions in writing.

2. Production Schedule

The vendor’s fabrication and manufacturing timeline — key milestones from engineering start through cabinet fabrication, software development, FAT, dispatch, and site support.

Review against your project schedule and identify any float risk early. Update this at every project review meeting.

Phase 1 — Engineering & Design Deliverables

These are the technical documents produced during the vendor’s detailed engineering and cabinet fabrication phase. All must be reviewed and formally approved by the EPC or client team before fabrication starts — not after.

3. Vendor System Design Basis

The vendor’s governing engineering document for the project. Defines how the vendor interprets and meets the project requirements — hardware platform selection, software version, redundancy architecture, applicable vendor standards, and any formally proposed deviations from the client’s Control System Design Basis.

This is the first technical document you should review and approve — everything else builds on it.

4. System Architecture Diagram

Hardware block diagram of the complete BPCS — controllers, I/O chassis, power supply modules, operator workstations, engineering workstations, historian and OPC servers, communication network switches, and redundancy arrangement.

The top-level picture of what the vendor is building. Review this against your Control System Design Basis before any hardware is procured.

5. I/O Mapping / Nest Loading Document

Allocates every signal from the project I/O List to a specific controller, I/O nest, rack slot, and channel number. Also called the I/O Assignment Sheet or Nest Loading Sheet.

This document defines exactly how your field signals physically land on the controller hardware. Verify it line-by-line before the vendor starts cabinet wiring — changes after fabrication are expensive and time-consuming to correct.

6. Panel General Arrangement (GA) Drawing

Physical layout drawing of the control system cabinet(s) — external dimensions, internal component arrangement, controller and I/O module positions, power supply locations, terminal block layout, door-mounted equipment, cable entry gland plate, and earthing bar location.

Formally review and approve this drawing before fabrication starts.

7. Power & Heat Load Calculation

Vendor engineering calculation for the total power consumption of all control system hardware and the heat dissipated inside the cabinet enclosure.

Used to size the UPS, power distribution unit (PDU), and cabinet cooling or HVAC system. Cross-check this against your project electrical and HVAC design to confirm compatibility.

8. Function Block Diagram (FBD) / Controller Logic Diagrams

The controller programming documents. Graphical representation of the application logic implemented inside the BPCS controller — how field input signals are conditioned, processed, and used to drive control outputs and alarms for each control loop, sequence, and interlock.

Verify these against the project Control Narrative and Cause & Effect Chart before FAT is executed.

9. System Network Diagram

Detailed diagram of the control system communication network — Ethernet topology, switch locations and model references, network segment names (control network, OPC/data network, DMZ), IP address allocation scheme, and any firewall or network segregation devices included in the vendor scope.

10. Communication Protocol Specification

Defines the communication interface between the BPCS and any third-party system or package unit — protocol type (Modbus TCP/IP, OPC DA/UA, PROFIBUS DP, EtherNet/IP), data format, polling rate, timeout handling, and handshaking mechanism. One specification per interface link.

11. Modbus / Communication Address List

Signal-level interface document for every Modbus, serial, or OPC communication link — register address, function code, data type (INT16 / FLOAT / Boolean), scaling factor, engineering unit, read/write status, and tag description for every communicated variable.

This document is critical for third-party system integration. Validate it point-by-point during FAT with the interface active.

12. HMI Graphics / Mimic Diagrams

Screen design drawings for all operator interface pages — process overview displays, unit group displays, individual loop faceplates, trend displays, alarm summary, and maintenance pages.

Review against the project P&ID and Control Narrative before FAT. Verify all tag names, engineering units, display ranges, and navigation paths are correct before the test starts.

13. Alarm Database / Alarm Tag List

The vendor-implemented alarm configuration in the BPCS — tag number, alarm description, setpoint value, alarm priority, alarm group, and any suppression or shelving logic applied.

The alarm philosophy is defined by the EPC. This document confirms how the vendor has implemented it inside the system. Review per ISA-18.2 alarm management principles.

14. Controller / Hardware Data Sheets

Manufacturer datasheets for all hardware modules supplied — CPU module, AI / AO / DI / DO I/O cards, power supply modules, and communication modules. Includes supply voltage, signal range, accuracy, isolation specification, environmental rating, and MTBF data. Retained for spares management and long-term maintenance reference.

15. Inspection & Test Plan (ITP)

The vendor’s quality document defining every inspection and test activity performed during fabrication and testing — activity description, reference procedure, acceptance criteria, responsible party, and inspection type (Vendor Hold / Witness / Review).

The ITP governs quality control from raw material receipt through to FAT. Request and review this early — it should be in place before cabinet fabrication starts, not raised on FAT day.

Phase 2 — FAT Deliverables

Factory Acceptance Test (FAT) is conducted at the vendor’s facility on the fully assembled and configured BPCS hardware, before the system is shipped to site. These documents are vendor-prepared and EPC/client-witnessed.

FAT is the last gate before equipment leaves the factory. Do not release the system to site without a formally signed FAT Report and an agreed punch list closure plan.

16. FAT Procedure

The test plan prepared and issued by the vendor before FAT execution. A complete FAT Procedure must contain:

• Scope of test — hardware configuration and software version under test, clearly identified
• Test prerequisites — I/O mapping loaded and verified, HMI graphics loaded, software version locked and recorded, test equipment list with valid calibration certificate references
• List of test cases with individual acceptance criteria:
  • I/O channel verification — signal injection at the terminal and readback at controller and HMI for every channel
  • Control loop function test — setpoint tracking, output response, alarm setpoint activation
  • HMI display verification — all tags, engineering units, display ranges, and navigation paths
  • Alarm and event list test — alarm generation, acknowledgement, and event logging verification
  • Communication link test — Modbus register read/write verification with simulated or live third-party system
  • Redundancy failover test — controller switchover, power supply redundancy, network switch failover
  • UPS and power supply integrity test
  • System diagnostics and fault indication test
• Roles and responsibilities — vendor test engineer, EPC/client witness, third-party witness if applicable
• Sign-off sheet for each test section

Review and formally approve the FAT Procedure before the FAT date — not on the morning of the test.

17. FAT Test Execution Sheets / Test Records

Pre-formatted record sheets completed during FAT execution — test case reference, description, acceptance criteria, actual measured or observed result, pass/fail status, and witness initials. These are the objective evidence that each test was performed and accepted. Never accept verbal confirmation — if it is not recorded and signed, it was not tested.

18. FAT Punch List

Deficiencies and open items identified during FAT — documented with description, category, responsible party, and target resolution date:

FAT Punch List category definitions

19. FAT Report

Formal summary document issued by the vendor after FAT completion — test scope and hardware/software configuration summary, list of all tests performed, overall pass/fail result, punch list status at time of acceptance, and sign-off by vendor, EPC, and client witnesses. This document formally closes the FAT and authorizes dispatch of the system to site.

Phase 3 — SAT Deliverables

Site Acceptance Test (SAT) is conducted on site after pre-commissioning activities are complete. The SAT Procedure and SAT Report are prepared by the vendor and executed with EPC and client witness. SAT formally accepts the control system on site and is a mandatory prerequisite for RFSU.

20. SAT Procedure

The on-site test plan prepared by the vendor before SAT execution. A complete SAT Procedure must contain:

• Scope of test — what will be formally tested on site. SAT is functional verification on live signals — it is not a full channel-by-channel repeat of FAT
• Prerequisites — all pre-commissioning complete, all FAT Category A and B punch items closed, system healthy and powered on site, all third-party communication interfaces live
• List of functional test cases with acceptance criteria:
  • Control loop response verification on live process signals
  • HMI display and alarm verification on live inputs
  • Communication link verification with connected third-party systems on site
  • Modbus address list validation on the live interface
  • Historian and data logging verification
  • Cause & Effect validation on live system
  • Override and bypass register verification
• Roles and responsibilities — vendor commissioning engineer, EPC commissioning lead, client operations witness
• Sign-off sheet for each test section

21. SAT Report

Formal record of SAT execution on site — test scope summary, list of all functional tests performed, results against acceptance criteria, punch list status, and sign-off by vendor, EPC, and client representatives. This document formally accepts the control system on site. Without a signed SAT Report, the system is not accepted.

Phase 4 — Handover Deliverables

Submitted by the vendor at project close-out, after SAT acceptance on site. These documents transfer the system formally to the operations and maintenance organization.

22. As-Built System Documentation Package

The complete updated set of all vendor-prepared engineering documents at their final accepted revision — reflecting the system exactly as built and commissioned.

Must include: System Architecture Diagram, Panel GA Drawing, I/O Mapping / Nest Loading, System Network Diagram, FBD / Logic Diagrams, HMI Graphics, Alarm Database, Modbus Address List, and Communication Protocol Specification. All documents at final as-built revision — not the issued-for-construction revision.

23. Final Controller Application Backup

Electronic backup of the final commissioned and accepted controller application — all programs, configuration files, and HMI graphics — stored on controlled media with software version reference, backup date, and project reference clearly recorded. This is what the maintenance team will restore from if the system ever needs to be rebuilt.

24. Operations & Maintenance (O&M) Manual

Vendor-prepared system manual covering hardware maintenance procedures, card and module replacement instructions, battery replacement schedule, system startup and shutdown procedure, controller diagnostics guide, and fault recovery procedure.

Must be specific to the project hardware configuration — not a generic product catalogue or marketing brochure.

25. Spare Parts List & Recommended Spares

List of recommended spare parts at card and module level — vendor part numbers, recommended stock quantities for a defined operating period (typically two years), lead time notes, and vendor ordering contact. Agree this list with the client during the project, not at handover.

26. Final Data Dossier

The complete, indexed compilation of all vendor engineering documents, test records, certificates, calculations, and approvals produced across the entire project lifecycle — from VDDL through to SAT Report.

This is the single controlled handover package that the client and operations team retain as the permanent record of what was built, how it was tested, and how it was accepted. It should be issued in both hard copy and electronic format, with a document index as the first page.

27. Packing & Dispatch List

Document prepared by the vendor at the time of shipment — itemized list of all equipment, hardware modules, cables, accessories, and documentation dispatched from the vendor’s facility.

Includes package numbers, item descriptions, quantities, weights, dimensions, and shipping marks. Used by the site team to verify receipt of all items on arrival. Discrepancies between the packing list and received goods must be formally raised against the vendor immediately on arrival.

Master Vendor Deliverables Summary Table

27 vendor engineering deliverables across five project phases — Kick-Off, Engineering, FAT, SAT, and Handover

EndNote

Every document on this list has a purpose. The VDDL and Production Schedule give you visibility and control from day one. The ITP ensures quality is tracked during fabrication — not discovered missing at FAT.

The Nest Loading document prevents wiring errors before the cabinet is built. The Modbus Address List prevents integration failures during commissioning. The Final Data Dossier ensures the operations team inherits a system they can actually maintain and troubleshoot ten years from now.

When you issue your VDR at project kick-off, do not accept a vendor submission list that is missing any of these documents. Every item here is a standard deliverable for any competent BPCS or DCS supplier.

If your project has a specific vendor deliverable that is not on this list, drop it in the comments — I will update this checklist from real-world community experience.

Have you ever had a vendor miss a critical deliverable that caused a problem during FAT or commissioning? Tell us what it was in the comments below.

Hope you like this article and now you have a clear-cut idea about the cDCS vendor engineering deliverables.

you like this article, and if you want to know about list of I&C standard list. Check out my previous article.

And you can also follow our LinkedIn group which is specially made for sharing information related to Industrial Automation and Instrumentation.

KISHAN MENDAPARA

Instrumentation & Control Design Engineer with 4+ years of hands-on experience in EPC, FEED, and detailed engineering projects across Oil & Gas, Petroleum Refineries, and Petrochemicals. Executing full-cycle engineering from FEED through commissioning on major international projects.

Expertise in control valve & orifice sizing, thermowell wake frequency calculations, P&ID review, cause & effect analysis, loop drawings, and datasheet preparation — managing 1,000+ I/O instrument indices across brownfield and greenfield projects.

“Founder of World of Instrumentation — translating real field and engineering office experience into practical guides, tools, and resources for instrumentation professionals worldwide.”