OCP Standards Framework — Binding for All Members
DAISA consortium members operate under Open Compute Project (OCP) standards as a binding requirement for participation in distributed regional compute infrastructure.
Consortium Strategic Mandate
By eliminating proprietary hardware dependencies, the DAISA framework removes vendor lock-in across compute, storage, and networking layers. This enables sovereign entities to deploy interoperable infrastructure with reduced lifecycle cost and increased auditability.
Enforced OCP Core Specifications
Open Rack V3
All deployments must conform to ORv3 structural and thermal design standards.
48V Power Architecture
Centralised 48V busbar systems with hot-swappable shelves.
Liquid Cooling
Direct-to-chip cooling with standardised manifold interfaces.
Open Firmware
Auditable stacks such as OpenBMC and coreboot only.
Procurement & Governance
Procurement processes ensure openness, modularity, and sovereign oversight.
Open Procurement
Multi-vendor sourcing is mandatory. Single-vendor lock-in is prohibited.
Lifecycle Modularity
Upgrades must be component-level, minimising e-waste.
Continuous Audit
Quarterly compliance audits mapped to OCP certification lists.
Sovereign Reporting
Bi-annual compliance reporting to host authorities.
Member Obligations
Inventory Register
Maintain a 90-day rolling hardware inventory.
Firmware Attestation
Submit firmware reports within 14 days of provisioning events.
Networking Compliance
Adopt OCP-compliant networking hardware within 18 months.
Interoperability Validation
Participate in annual interoperability test cycles.
Supply Chain Reporting
Report non-compliant supply chain events within 48 hours.
Non-Compliance Protocol
Advisory Notice
Formal notice with 30-day remediation window.
Supervised Remediation
Embedded technical oversight and corrective plan.
Suspension
Temporary loss of access until compliance is restored.
Expulsion
Permanent removal from consortium participation.