Registration history
Materials state registration on 5 December 2007 and prior activity in Nigeria’s construction and energy sectors.
Project structure
A project vehicle pathway for aligned infrastructure participants.
The objective is to engage data center operators and infrastructure partners, then move qualified project activity into a formal structure where contributing parties can be properly represented.
Structure intent
The project vehicle follows the diligence path.
A dedicated project vehicle may be appropriate once the project has clearer commercial scope, technical basis, participant roles, approval requirements, and funding pathway.
Public materials do not imply that final vehicle terms, operator commitments, approvals, or returns are already secured. The structure presents an orderly pathway toward a financeable project vehicle.
Legacy records
Historical materials for the diligence file.
Legacy Westminister materials form part of the background record for project data-room diligence, subject to legal review and current verification.
Company profile
The legacy profile provides historical context while current investor/operator materials are maintained for qualified discussions.
HSE and project discipline
Prior statements on environmental impact, process safety, health protection, and zero-accident objectives provide context for HSE and execution discipline.
Leadership and technical partners
Names, titles, partner roles, client references, and public-sector relationships are qualified against current transaction documentation.
Indicative structure
Participant roles to define.
| Participant | Potential contribution | Diligence focus |
|---|---|---|
| Westminister Technologies Ltd. | Lead development platform, project coordination, operator engagement, and commercial structuring. | Corporate role, authority, contribution, governance, and economics. |
| Mosand Herj | Project history, oil and gas background, registration history, and potential licensing context. | Verified documentation, scope of participation, and approved public statements. |
| Technical partners | Generation design, EPC, operations, controls, resilience, and technical delivery support. | Capability, references, warranties, performance obligations, and risk allocation. |
| Data center operator or offtaker | Demand profile, power offtake, campus requirements, and operational requirements. | Capacity, term, service levels, credit, expansion options, and operating assumptions. |
| Capital partners | Development capital, project finance, equity, debt, or structured investment participation. | Terms, conditions precedent, diligence requirements, protections, and exit rights. |
Governance
A bankable structure makes open questions visible.
- Define the project perimeterSite, power source, capacity, offtake, technology, regulatory pathway, and development timeline.
- Confirm participant rolesDocument who contributes what and how each contribution is valued, governed, protected, and approved.
- Form the project vehicleCreate the dedicated vehicle or other formal structure only once legal, tax, regulatory, commercial, and financing advice supports it.