Documents
The paperwork a control system project actually produces
17 templates covering the full project, from the requirement the client writes to the pack the site keeps afterwards. These are working documents with the tables, the acceptance criteria and the sign-off blocks already in them, not outlines with empty headings.
Free, no account. Fill in your project details on any template and the download arrives already populated.
17 templates 20 files Markdown and CSV
Which of these do I actually need?
Not all of them, on most jobs. Scale the set to the work.
Small machine build
3 documents
- FDS
- I/O list
- Commissioning checklist
Mid-size project
8 documents
- URS
- FDS
- I/O list
- BOM
- Cause and effect
- Risk assessment
- FAT
- SAT
Regulated or process plant
The full set
- Everything, with traceability
- Alarm rationalisation
- Change control from day one
Specification
What the client wants, and how the system will meet it.
3- URS1 file
User Requirement Specification
What the client needs the system to do, written before anyone decides how it will be done.
Preview and download
- FDS1 file
Functional Design Specification
How the system will actually work, in enough detail that someone else could program it.
Preview and download
- CN1 file
Control Narrative
The process described in prose, loop by loop, for the people who will operate and maintain it.
Preview and download
Design
How the software is built, so the next engineer can read it.
1Registers
The lists: signals, parts, cables, trips and alarms.
6- I/O2 files
I/O List
Every signal in and out of the controller, with address, type, range and where it terminates.
Preview and download
- BOM1 file
Bill of Materials
Every part in the panel and in the field, with manufacturer, part number and quantity.
Preview and download
- CS1 file
Cable Schedule
Every cable, from which gland to which terminal, with type, cores, length and route.
Preview and download
- C&E2 files
Cause and Effect Matrix
A grid of every trip condition against every action it causes, with nothing implied.
Preview and download
- RATS1 file
Range, Alarm and Trip Schedule
Every instrument's range and every limit set against it, on one page.
Preview and download
- ALM2 files
Alarm List and Rationalisation Record
Every alarm, why it exists, what the operator should do about it, and how quickly.
Preview and download
Safety
Hazards, required performance levels, and the evidence.
1Testing
Proof that it works, on the bench and then on the plant.
3- FAT1 file
Factory Acceptance Test Protocol
The test run at the integrator's works, on simulated I/O, before anything ships to site.
Preview and download
- COMM1 file
Commissioning Checklist
The pre-power and first-energisation checks, in the order they have to happen.
Preview and download
- SAT1 file
Site Acceptance Test Protocol
The test run on site, on real equipment, that proves the system works where it has to work.
Preview and download
Handover
What the site keeps, and how changes are controlled afterwards.
3- HO1 file
Handover and As-Built Pack
The index of everything the site receives, and the record that they actually received it.
Preview and download
- O&M1 file
Operation and Maintenance Manual
How to run it, how to fix it, written for the people who will do both at 3 am.
Preview and download
- MOC1 file
Change Control Record
A single form for any change after handover: what, why, what it affects, who agreed.
Preview and download
Common questions
- What documents does an automation project need?
- A full control system project produces a URS, an FDS, an I/O list, a BOM, a cable schedule, a cause and effect matrix, a risk assessment, FAT and SAT protocols, and a handover pack. A small machine build needs three: an FDS, an I/O list and a commissioning checklist.
- What is the difference between FAT and SAT?
- A Factory Acceptance Test runs at the integrator's works on simulated I/O, before the panel ships. A Site Acceptance Test runs on the plant with real field devices after installation. The FAT proves the logic, the SAT proves the installation. Neither substitutes for the other.
- What is the difference between a URS and an FDS?
- The URS states what the client needs in plant terms and is the client's document. The FDS states how the control system will meet each of those requirements and is the engineer's document. Every FDS section should trace back to a numbered URS requirement.
- Are these templates free?
- Yes. Every template downloads without an account, as Markdown or CSV. You can fill in the project details first and the download arrives already populated.