Project Information Model Standard
A RICA Project Information Model is the formal project record used to test whether a rural climate adaptation asset is ready for financing review, monitoring, and later investor visibility. It combines project facts, evidence, technical design, operating model, financial model, governance, risk, compliance, and reporting obligations in one controlled document set.
The Project Information Model must be specific enough for a reviewer to test the project without relying on informal sponsor explanations. It must distinguish confirmed evidence from assumptions and must identify unresolved diligence items.
What A Project Information Model Is
Section titled “What A Project Information Model Is”A Project Information Model is a diligence document, not a fundraising story. It explains the asset, why it matters, how it works, who owns and operates it, how it generates cash flow, how risks are controlled, and what evidence supports each claim.
In RICA, the Project Information Model also shows how the project fits a solution framework, how it supports community ownership or participation, how nature stewardship receives residual economics where applicable, and how the project record will be maintained in Atlas.
Maturity Levels
Section titled “Maturity Levels”| Level | Evidence Depth | Financial Model | Engineering Status | Approvals Status | Investor Use |
|---|---|---|---|---|---|
| Concept | Problem, sponsor, site, and solution hypothesis. | Initial cost and revenue ranges. | Concept layout or asset description. | Known requirements listed. | Early screening only. |
| Pre-Feasibility | Initial site, market, stakeholder, and technical evidence. | Driver-based model with stated assumptions. | Preliminary design basis and capacity logic. | Critical approvals mapped. | Origination pipeline review. |
| Investment-Ready Project Information Model | Complete evidence package, risk register, governance model, and Atlas mapping. | Full capex, opex, revenue, cash flow, loan, and sensitivity model. | Design sufficiently mature for financing decision. | Required permits submitted or conditions identified. | Financing review and credit memo input. |
| Approved Project Information Model | Reviewer comments resolved and decision conditions recorded. | Locked base case with approved sensitivities. | Approved design package and procurement plan. | Financing conditions and covenants identified. | Project loan execution support. |
| Operating Update | Project Information Model updated with as-built records, operating data, and material events. | Actuals compared to base case. | As-built and O&M records. | Operating permits and renewals tracked. | Servicing, purchase review, and investor monitoring. |
Required Standard
Section titled “Required Standard”Every RICA Project Information Model must provide enough evidence to answer four questions:
| Question | Required Answer |
|---|---|
| Is the asset real? | Location, boundary, sponsor, operator, asset rights, design, and implementation plan are documented. |
| Is the asset financeable? | Revenue, cost, repayment, risk, governance, and controls are credible and testable. |
| Is the asset RICA-aligned? | It fits a solution framework, supports adaptation, maintains transparency, includes local participation, and defines stewardship treatment. |
| Can the asset remain visible? | Atlas records, reporting cadence, metrics, evidence updates, and material-event obligations are defined. |
Required Evidence Discipline
Section titled “Required Evidence Discipline”| Claim Type | Required Evidence | Atlas Location | Reviewer Test |
|---|---|---|---|
| Site control | Land title, lease, concession, right-of-use agreement, or equivalent. | Documents / Site | Does the sponsor have legal capacity to build and operate? |
| Sponsor capability | Track record, financial statements where available, governance documents, references, and key personnel. | Stakeholders / Sponsor | Can the sponsor deliver and remain accountable? |
| Revenue case | Contracts, letters of intent, customer data, pricing evidence, benchmark data, or survey results. | Financials / Revenue | Are volumes, prices, and collections supported? |
| Technical design | Drawings, specifications, capacity calculations, vendor quotations, and design review notes. | Documents / Technical | Is the design consistent with the operating model? |
| RICA alignment | Solution-framework mapping, adaptation outcomes, stakeholder structure, and stewardship design. | Project Profile / RICA Review | Does the project qualify as a RICA asset? |
Version Control
Section titled “Version Control”Every Project Information Model must identify its version, date, preparer, reviewer, approval status, and open issues. Material changes after approval must be logged as amendments and connected to Atlas records.
Minimum Version Register
| Version | Date | Prepared By | Reviewed By | Status | Material Changes |
|---|---|---|---|---|---|
| v0.1 | [date] | [name] | [name] | Draft | Initial sponsor draft. |
| v1.0 | [date] | [name] | [name] | Approved | Financing-review version. |