The sequence of operation for a cleanroom AHU runs to two or three pages, and it decides what your rooms do in a power cut.
On most projects it is read by the controls engineer who wrote it and the programmer who codes it. QA meets it at OQ, when the logic is already in the PLC and the panel is on the wall. Every change after that is a software revision, a repeated test and a deviation record.
We prefer to walk the narrative with QA and maintenance before the panel is built, one line at a time. The start order gets the longest discussion. If exhaust runs before supply, a Grade C room can sit negative to its corridor for the first minute of every restart. Then the trips: where the dampers go when the AHU stops on a fault, which is a different case from someone pressing stop. Alarm delays for door openings come next, and who acknowledges which alarm. Last, the fail position of every damper and valve on loss of power or signal, and whether the suite recovers by itself when power returns.
Maintenance tends to ask the question nobody else does: how do I isolate one fan for repair without taking the suite out of its grade? If the narrative has no answer, the panel will not have one either.
At Humiley the URS and validation strategy are written alongside the design, so the narrative gets its review while it is still a document and cheap to change.
Who signs off the sequence of operation on your projects before the panel is built?




