Every UNUS London governance system is engineered against ISO, ITIL 4, and IEC frameworks. Clauses are not referenced in policy documents — they are enforced by database triggers, stored procedures, and compliance views that cannot be bypassed.
UNUS London compliance systems are not mapped to standards after the fact. The schema design, trigger logic, stored procedures, and reporting views are structured from first principles around each framework's requirements. Clauses are satisfied by design.
ISO 9001:2015 structures the quality management system around eight clauses covering context, leadership, planning, support, operation, performance evaluation, and improvement. UNUS London implements the operational and evidence requirements through database objects — not paper-based procedures.
ISO/IEC 27001:2022 restructures the Annex A controls into four themes: Organisational, People, Physical, and Technological. UNUS London implements the technological controls directly in the database layer — access logging, input validation, event recording, and encryption in transit are enforced structurally.
ISO/IEC 19770-1:2017 defines the requirements for IT asset management processes across the full asset lifecycle. The standard is structured around four tiers: trustworthy data, practical management, operational integration, and optimised management. UNUS London implements the foundational data requirements — asset registers, license entitlements, and lifecycle events — in a queryable, reportable schema.
ITIL 4 provides the service management framework that governs how UNUS London systems are designed, deployed, and operated. Three practices are directly implemented in the compliance infrastructure: Change Enablement, Knowledge Management, and Service Request Management. Every workflow is structured as a service asset with defined inputs, outputs, and definitions of done.
IEC 80000 defines the quantities and units for all scientific and technical fields, aligned to the International System of Units (SI). UNUS London applies IEC 80000 to schema design, data type selection, and reporting notation — ensuring that all numerical quantities, storage units, time intervals, and performance metrics are expressed in unambiguous, internationally recognised form. This is particularly relevant to data storage metrics, transmission rates, processing times, and audit interval expressions across the compliance reporting layer.
Compliance is not asserted through policy documentation. Each standard clause is mapped to the specific schema object — trigger, stored procedure, view, or constraint — that enforces it. This traceability matrix is included in every system's build guide within the Governance Academy.
Access Build Guides — £97/month →| Standard Clause | Implementation Object | Status |
|---|---|---|
| SRA Code §7.1 — Supervision | SELF_SUPERVISION_VIOLATION trigger | ✓ Enforced |
| ISO/IEC 27001 A.8.15 — Logging | sra_report_history (insert-only) | ✓ Enforced |
| ITIL 4 Change Enablement | sp_approve_version stored procedure | ✓ Enforced |
| ISO 9001 §7.5 — Document Control | version_status ENUM + approval gate | ✓ Enforced |
| ISO 9001 §10.2 — NCR & Corrective Action | ncr_tracker schema + closure workflow | ✓ Enforced |
| ISO/IEC 27001 A.8.28 — Secure Coding | Parameterised queries in all procedures | ✓ Enforced |
| ITIL 4 Knowledge Management | vw_search_gaps continual improvement view | ✓ Enforced |
| IEC 80000-13 — Storage Units | PostgreSQL BIGINT · bytea types applied | ✓ Applied |
Book a discovery call to confirm which frameworks govern your obligations and map out the exact systems required to satisfy them.