Availability is produced by procedure, not by talent. This document is the controlled register of every procedure the Facility operates to, together with the scheme that governs how those procedures are written, approved, issued and retired. It is the index a reviewer samples from and the control record that shows the library is maintained rather than merely written once.

Scope is the KOM Oman AI Factory at Knowledge Oasis Muscat: the electrical chain from utility intake to rack, the cooling plant and secondary loops, the network fabric, the compute platform, the data halls and the security estate. Procedures owned by the customer for their own workloads sit outside this register.

A MOP is written against the equipment actually installed — the UPS model, the chiller make, the switchgear arrangement, the OEM's own service documentation. Writing one before the equipment is delivered produces a document that has to be discarded. The register therefore schedules each MOP to the commissioning of the system it governs, and the honest position today is that no procedure is yet approved at 1.0 because no system is yet energised.

What does exist is the register itself, the numbering and version scheme, the approval authority, and 25 procedures drafted to 0.2 — the emergency set and the core operating routines, both of which must be in place before commissioning rather than after it. Sequencing is set out at 2.4.

Every procedure carries a permanent reference and a version that changes on every release. A document without both is not controlled and must not be used at the point of work.

Reviewed on the earliest of the following. Review is recorded even where nothing changes, so a current review date always exists.

• Twelve months from the last approval or recorded review — the maximum interval, applied to every procedure.
• On change to the governed system — equipment, firmware, software, topology, or the OEM service instruction.
• After any execution that did not go as written — an abort, a deviation, or a step found wrong or ambiguous in use.
• After any incident in which it was used, whether or not it contributed — under the root-cause process in PRM-IRP-2026-001.
• On a finding from internal audit, external audit or a certification body.

A procedure is approved by a named office, not by a function. Approval is recorded against the person holding that office on the date of release, and cannot be delegated to the author.

A document that does not carry all of the following is not accepted into the register, regardless of how sound its content is.

1. Reference, version, approval date and next review date on the first page.
2. Scope and the specific equipment it applies to, by make, model and asset reference — a MOP that names only a system type is rejected.
3. Pre-conditions and permits — system state, redundancy required, isolations in place, permits obtained, customer notice given where the Demarcation Matrix requires it.
4. Numbered steps in the order performed, each with the expected result, so that a step can be signed off individually.
5. Abort criteria and rollback — the condition under which work stops, and the sequence that returns the system to its pre-work state.
6. Risk to service — stated plainly, with the redundancy relied upon and the consequence of losing it during the work.
7. Competence required — the certifications from PRM-HR-2026-001 that the executing engineer must hold.
8. Sign-off block — executed by, verified by, returned to service by, with timestamps.

Control is worthless if a superseded copy remains in circulation. The library has one source of record, and any copy taken from it is treated as uncontrolled from the moment it is printed.

Planned work on live infrastructure. Each MOP is written against the installed model and its OEM service instruction, and is scheduled to the commissioning of the system it governs — see 2.4.

Repeatable routines performed the same way on every shift. Approved before the resident team takes occupancy, so that the first day of operation is already evidenced.

Action after a system has already failed. Written to be executed by whoever is on shift without waiting for escalation, and drilled before commissioning rather than after it.

A library is only as good as the evidence that the shift can execute it. Three controls close the loop.