RICA Project Information Model Template

This repository is the editable starting point for project-specific RICA Project Information Models.

Sponsors should use this repository as a clean template for each project, then populate the Markdown chapters, tables, images, drawings, maps, financial model, risk register, clearance tracker, and supporting evidence for that project.

The template complements the RICA Project Information Model Standard. The standard explains what a RICA-aligned Project Information Model must contain. This repository provides the project workspace that a sponsor can copy, keep private, and fill.

v0.2 Direction

RICA Project Information Model Template v0.2 applies improved information management principles to the existing sponsor workflow. It keeps the chapter structure familiar, but adds a control layer for required information, delivery responsibility, information containers, review states, confidentiality, and handover into Atlas.

The goal is practical comparability. A sponsor should be able to show what information was required, where the evidence is held, who produced and reviewed it, what changed over time, and what should become part of the operating asset record.

Quick Start

1. Use GitHub’s Use this template workflow to create a new project repository.
2. Make the project repository private unless the sponsor intentionally approves publication.
3. Fill pim.yaml first so project metadata is consistent across the Project Information Model.
4. Review the Information Requirements, Information Delivery Plan, and Information Container Register before drafting chapters.
5. Work through the chapters in SUMMARY.md order.
6. Put source files, photos, maps, drawings, financial models, permits, and correspondence in the relevant assets/, data/, or appendices/ location.
7. Run node scripts/validate-template.mjs to confirm the template structure is intact. For a filled Project Information Model, run node scripts/validate-template.mjs --strict to flag remaining placeholders.

Project-specific repositories should usually be private because they may contain site maps, contracts, permits, financial models, stakeholder records, photos, and other diligence material.

Repository Structure

rica-project-information-model-template/
  README.md
  SUMMARY.md
  pim.yaml
  information-requirements.md
  information-delivery-plan.md
  information-container-register.md
  00-project-profile.md
  01-executive-summary.md
  02-market-context.md
  03-feasibility-evidence.md
  04-demand-supply-offtake.md
  05-project-scope.md
  06-functional-design.md
  07-engineering-design.md
  08-environment-social-stewardship.md
  09-governance-ownership.md
  10-financial-model.md
  11-risk-register.md
  12-implementation-plan.md
  13-procurement-contracts.md
  14-clearances-compliance.md
  15-quality-management.md
  16-operations-maintenance.md
  acceptance-criteria.md
  security-classification.md
  safeguards-information.md
  asset-information-handover.md
  appendices/
    README.md
    evidence-register.md
    assumptions-register.md
  assets/
    photos/
    drawings/
    maps/
    diagrams/
  data/
    financial-model.xlsx
    risk-register.csv
    clearances-tracker.csv
    open-issues.csv
  scripts/
    validate-template.mjs

How To Fill This Project Information Model

Use the visible placeholders as prompts, not as final text. Replace every REPLACE: value with sponsor-specific information, then update the tables so they point to real evidence files. Keep assumptions and evidence traceable: every important claim should have a source file, responsible owner, and review status.

Use assets/photos/ for site photos and construction photos, assets/maps/ for location and boundary maps, assets/drawings/ for drawings and layouts, and assets/diagrams/ for process, governance, or system diagrams. Use appendices/evidence-register.md to track every supporting file.

The CSV trackers in data/ are starter files. Sponsors may keep using them directly, import them into Atlas, or replace them with controlled project systems as long as the final Project Information Model links back to the evidence.

Use the v0.2 control-layer pages to keep the workspace reviewable. The information requirements identify what must be provided, the delivery plan assigns ownership and timing, the container register tracks controlled files, the acceptance criteria define readiness, and the handover page prepares the transition into Atlas.

Atlas Direction

The sponsor-filled Markdown structure should be renderable inside Atlas as a Project Information Model viewer. Atlas can use SUMMARY.md for navigation, render Markdown pages in a GitBook-like interface, display images and diagrams from assets/, and map selected sections into structured project records for site, stakeholders, finance, risk, compliance, metrics, evidence, and material events.

Validation

Run the structural validator after changes:

node scripts/validate-template.mjs

For a sponsor-filled Project Information Model, use strict mode to find remaining placeholders:

node scripts/validate-template.mjs --strict

See the Validation Checklist for the manual review checklist, including confidentiality checks before any repository is shared outside the sponsor team.