What are Instrumentation Deliverables?

Instrumentation
1

If you’re new to instrumentation & control (I&C) - PLC/DCS/SCADA, field instruments, panels, wiring, loop checks—the term “deliverables” can feel abstract. In practice, deliverables are the engineering artifacts a project team creates, reviews, issues, installs, tests, and finally hands over to operations. They guide every step from idea → design → procurement → installation → commissioning → maintenance.

This guide explains what each instrumentation deliverable is, when it’s produced, who uses it, and what it must contain—with simple language and practical tips for beginners.

Instrumentation Deliverables

Instrumentation Deliverables
Instrumentation Deliverables1536×1024 340 KB

Any document, drawing, list, database, test record, or software file that:

  • communicates the intended measurement/control function,

  • enables procurement, fabrication, installation, or testing, and

  • becomes part of the project record or the as-built handover.

Think: Instrument Index, I/O List, Loop Diagrams, Hook-up Drawings, Cause & Effect (C&E), Control Narratives, Datasheets, Cable Schedules, FAT/SAT reports, As-builts, PLC/DCS backups, and more.

Project timeline view: deliverables by phase

1) Concept / FEED (front-end engineering)

  • Design Basis / Measurement Philosophy – What needs to be measured/controlled and why.

  • Tag Numbering Standard – How tags like PT-101 or LT-301A are formed.

  • Preliminary Instrument Index – Early list of instruments by tag with service.

  • P&ID Markups – Early instrument bubbles, lines, and notes on process diagrams.

  • Preliminary I/O Count – Digital/analog input/outputs for control system sizing.

  • Initial Specifications List – Which standards/specs will govern devices (e.g., pressure transmitters, control valves).

Why it matters: Locks the scope so later detailed engineering is aligned.

2) Detailed Engineering / Design

  • Instrument Index (master) – The single source of truth for every instrument tag (type, service, range, location, hazardous area, JB/panel references, calibration ranges).

  • I/O List – All DIs/DOs/AIs/AOs with signal type, range, from/to, module/slot/channel, scaling, alarm/trip flags.

  • Instrument Datasheets – Device-specific data to procure the exact item (process/ambient conditions, wetted materials, approvals like ATEX/IECEx).

  • Hook-up Drawings – How each instrument is physically installed (supports, manifolds, impulse lines, air supply, glands, fittings) + MTO (material take-off).

  • Loop Diagrams – The end-to-end wiring and signal path for each loop (field → JB → marshalling → system I/O → logic → HMI).

  • Cable Schedule – Cable IDs, sizes, pair counts, routes, from/to termination points.

  • JB Schedule / Termination Diagrams – Terminal numbers, ferrule IDs, spare allocation.

  • Interconnection & Wiring Diagrams – Panel-to-panel, panel-to-field connections.

  • Panel GA & Wiring – General arrangement and internal wiring of control panels, marshaling, system cabinets.

  • Control System Architecture & Network Topology – CPU/remote racks, SCADA servers, historians, switches, VLANs, time sync.

  • Control Narratives / FDS (Functional Design Specification) – Plain-English logic of how the plant should control, interlock, start/stop, and recover.

  • Cause & Effect (C&E) Matrix / Shutdown Key – What trips/alarms happen when a condition occurs; the definitive interlock reference.

  • Alarm & Trip Setpoint List + Rationalization Notes – Alarm types, priorities, deadbands, shelving rules.

  • Hazardous Area Classification Drawings & Schedule – Zone/Division, gas group, temperature class for each location.

  • SIS / SIF Documentation (if applicable) – SIL determination, Safety Requirements Specification (SRS), proof-test intervals, bypass/override logic.

  • Instrument Location Plans / Cable Tray Layout Inputs – Coordinates, elevations, routing hints (often shared with Mechanical/Electrical/Civil).

  • Requisitions (MR/PR) and Technical Bid Evaluations (TBE) – Vendor selection trail.

  • Inspection Test Plan (ITP) and Method Statements – How quality will be verified.

Why it matters: This is the “build manual” for procurement, fabrication, and installation.

3) Procurement & Vendor Engineering

  • Vendor Datasheets & GA – Final, vendor-stamped data; outline dimensions & weights.

  • Interface Control Documents (ICD) – Signals, power, protocols, setpoints to integrate skid packages.

  • FAT Procedures (Factory Acceptance Test) – What will be tested at the vendor works.

  • VDR (Vendor Data Review) Comments & Resolutions – Review trail ensuring compliance.

Why it matters: Ensures devices meet the design and are testable before shipment.

4) Construction / Installation

  • Work Packs / Method Statements – Task-by-task instructions with drawings, PPE, safety.

  • Hook-up MTO & Issue for Construction (IFC) Drawings – Frozen for site use.

  • Cable Pull Cards – Cable details plus test results (IR/continuity).

  • JB/Panel Termination Records – Actual ferrule numbers, torque values (if required).

  • Calibration Certificates – Factory or site calibration records for each instrument.

Why it matters: Field teams need exact instructions and records for QA.

5) Pre-Commissioning / Commissioning

  • Loop Check Sheets – Evidence that each loop functions end-to-end as designed.

  • FAT Reports / SAT Procedures & Reports – Factory/site acceptance evidence.

  • Interlock & Trip Test Records – C&E proven in real tests.

  • “As Found / As Left” Calibration Sheets – Traceable calibration history.

  • Punch Lists & Close-out – Outstanding items, priorities, closures.

Why it matters: Converts drawings into a running, safe plant—with proof.

6) Handover / Operations

  • As-Built Drawings & Databases – P&IDs, Index, Loops, Hook-ups updated to reflect reality.

  • PLC/DCS/SCADA Backups – Source code, binaries, HMI graphics, historian configs.

  • O&M Manuals & Preventive Maintenance (PM) Plans – How to keep it healthy.

  • Recommended Spares & Special Tools – For reliability and uptime.

  • Asset Register – Tag, serial, location, warranty, calibration due dates.

  • Training Materials – Operator/maintenance training content.

Why it matters: Operations inherits an accurate, maintainable system.

The 25 core instrumentation deliverables

  1. Instrument Index (master list) – Every tag, one place.

  2. I/O List – Every signal with type, range, and module channel.

  3. Instrument Datasheets – Device-specific procurement info.

  4. P&IDs with Instrumentation – Instrument bubbles and lines on process diagrams.

  5. Hook-up Drawings + MTO – How to physically install the instrument.

  6. Loop Diagrams – End-to-end signal path and wiring.

  7. Cable Schedule – All cables with from/to and sizes.

  8. JB Schedule & Terminations – Terminal-by-terminal mapping.

  9. Panel GA & Wiring – Cabinet layout and internal wiring.

  10. Control Architecture & Network Topology – CPUs, networks, servers.

  11. Control Narratives / FDS – Human-readable logic descriptions.

  12. Cause & Effect Matrix – Interlock/shutdown truth table.

  13. Alarm & Trip Setpoint List – What alarms exist and why.

  14. Hazardous Area Docs – Zone classification and equipment approvals.

  15. SIS / SRS / SIL Docs – Safety lifecycle deliverables (where applicable).

  16. Requisitions & TBE – Procurement trail and vendor selection.

  17. FAT/SAT Procedures & Reports – Factory/site test proof.

  18. Calibration Certificates – For each instrument, traceable.

  19. Installation Work Packs – Field instructions with IFC drawings.

  20. Loop Check Sheets – Verified loop functionality.

  21. Interlock Test Records – C&E proven on site.

  22. As-Built Packages – All drawings and lists updated.

  23. PLC/DCS/HMI Backups – Code and configuration snapshots.

  24. O&M Manuals & PM Plans – Sustaining documents for maintenance.

  25. Asset Register & Spares List – What you own and what to stock.

Instrument Index vs I/O List

  • Instrument Index = Devices (tags): PT-101, TT-205A, LV-302, etc. Includes service, range, line/equipment, location, HA classification, datasheet reference.

  • I/O List = Signals: AI from PT-101 at 4–20 mA, DI from LS-304 “Tank High Level”, DO to XV-402 “Open”, AO 0–10 V speed ref to VFD-101, etc. Includes module/slot/channel, scaling, alarm/trip, HMI point.

They are linked but serve different audiences (Index for asset management, I/O List for control system implementation).

Minimum fields to include (beginner checklist)

Instrument Index

  • Tag, service, P&ID ref, line/equipment ref, instrument type, range/units, accuracy, model, material/wetted parts, mounting type, location (area/elevation), hazardous area data, datasheet ID, JB/panel references, remarks.

I/O List

  • Tag, loop ID, signal type (DI/DO/AI/AO), protocol (wired/Modbus/Profibus/etc.), range & engineering units, scaling (raw ↔ EU), alarm/trip flags & setpoints, HMI descriptor, PLC/DCS module/slot/channel, cable ID, termination points.

Loop Diagram

  • Loop ID, tag(s), cable IDs/core numbers, terminal numbers, grounding/shield scheme, power source, IS barriers/isolators, interposing relays, reference drawings.

Hook-up

  • Mounting detail, fittings/manifolds, impulse lines/tubing size & material, air supply/filter-regulator (for pneumatic devices), glands/conduit, supports, MTO.

C&E

  • Causes (inputs/conditions), effects (trips/alarms/actions), priorities, reset logic (manual/auto), bypass rules, test notes.

How all these fit together (simple picture in words)

  1. P&ID tells what must exist.

  2. Instrument Index lists what each tag is.

  3. Datasheets fix what exactly to buy.

  4. I/O List tells how each signal lands in the system.

  5. Hook-ups show how to install each device.

  6. Loop Diagrams prove the signal path is correct.

  7. Narratives + C&E define how the plant behaves.

  8. FAT/SAT/Loop Checks prove it works as designed.

  9. As-builts + Backups ensure operations can maintain it forever.

File naming, versions, and status

  • Use consistent names: PROJECT-AREA_DOC-TYPE_TAG/LOOP_REV.ext (example).

  • Maintain status codes: IFI (for information), IFR (for review), IFC (for construction), IFA (for approval), As-Built.

  • Control revisions (A/B/C or 0/1/2), with change notes.

  • Keep a deliverable register that lists owner, due date, approver, and cross-references (Index ↔ Loops ↔ C&E).

Common beginner mistakes (and how to avoid them)

  1. Mismatched tags across Index, I/O List, and Loops → Run a daily cross-check.

  2. Missing scaling details for analog I/O → Always include raw ↔ EU mapping.

  3. Unclear alarm priorities → Do an alarm rationalization; document rationale.

  4. Ignoring hazardous area ratings → Map device approvals to zone/temp class.

  5. No IS barrier references in loops for Ex-i devices → Show barrier part numbers and terminal mapping.

  6. Skipping as-builts after site changes → Redline during commissioning and update before handover.

  7. No code backups → Archive PLC/DCS/HMI with revision notes and dates.

  8. C&E not tested end-to-end → Record interlock tests and sign-off by Ops.

Micro examples (to make it real)

  • Tag naming: PT-101A = Pressure Transmitter, Area 1, Loop 01, ‘A’ unit.

  • AI scaling (I/O list entry): Raw 4–20 mA = 0–10 barg (EU), LRV=0, URV=10, Eng Units=barg, HMI decimal=1.

  • C&E snippet: Cause: LT-201 ≥ 90% (2oo3 voting). Effect: Trip P-101A/B, close XV-210, alarm “Tank High Level Trip”. Reset: Manual after LT < 70%.

FAQ

Q1. What is the difference between a Loop Diagram and a Hook-up?
A loop diagram shows the complete signal path and wiring. A hook-up shows how to physically install the instrument (supports, manifolds, fittings) and lists materials (MTO).

Q2. Is the Instrument Index the same as the I/O List?
No. The Index is a device list; the I/O List is a signal list tied to PLC/DCS channels and scaling.

Q3. What must be in an As-Built package?
Updated P&IDs, Index, Loops, Hook-ups, Cable & JB schedules, Panel wiring, C&E, Narratives, alarm lists, calibration sheets, interlock test records, and full PLC/DCS/HMI backups.

Q4. Do small projects need all deliverables?
Scope-dependent. For a skid or a single tank, you still need the Index, I/O list, datasheets, loop diagrams, and as-builts at minimum.

Q5. Where do safety (SIS) deliverables fit?
Under SIS lifecycle: SIL determination, SRS, verification, proof-test procedures, and records. They tie to C&E and interlocks.

3 Likes
Introduction to Instrumentation Design Engineering
2

Good insights