1. Vision & Mission

V Vision

To be Alberta's most trusted, transparent, and effective Clean Energy Improvement Program administrator, serving all property types across every municipality through technology-driven efficiency.

M Mission

Deliver a fully digital platform that automates the CEIP lifecycle from application through decades of monitoring, reducing administrative burden while maximizing clean energy outcomes for Albertans.

2. Objectives & Key Results (OKRs)

Each objective is paired with measurable key results that define success criteria for the DRC CEIP Platform.

Objective Key Results
O1
Launch platform for first municipality partnership
KR1 Complete Phase 1-3 workflows for commercial properties
KR2 Onboard 10 qualified contractors
KR3 Process first 5 applications end-to-end
O2
Achieve $100M in qualified CEIP project pipeline (Year 1-2)
KR1 Aggregate 75+ LED lighting projects
KR2 Aggregate 25+ HVAC system projects
KR3 Aggregate 20+ solar panel installations
O3
Expand to all property types
KR1 Residential workflow live
KR2 Farm workflow live
KR3 Industrial workflow live
O4
Establish monitoring & reporting excellence
KR1 Real-time energy monitoring for 100% of completed projects
KR2 First annual public report published by Sept 1
KR3 >95% stakeholder satisfaction with reporting

3. Feature Roadmap

An aggressive 6-month delivery plan from platform foundation through Calgary pilot launch. Achievable with committed stakeholder participation at every phase.

M1 M2 M3 M4 M5 M6
Foundation
M1
Phase 1 MVP
M1 - M2
Phase 2 MVP
M2 - M3
Phase 3 MVP
M3 - M4
Phase 4 MVP
M4 - M5
Phase 5 MVP
M5 - M6
Residential Expansion
M4 - M5
Farm Expansion
M5 - M6
Integration Layer
M3 - M6
Compliance & Launch
M6
Foundation Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 Residential Farm Integration Compliance

Foundation (M1)

Platform architecture, design system, RBAC

Phase 1 MVP (M1-M2)

Registration portals, eligible improvements catalog, bylaw management

Phase 2 MVP (M2-M3)

Application workflow, contractor qualification, document management, ASHRAE audit intake

Phase 3 MVP (M3-M4)

Loan approval, CEIP agreement builder, SPIN2 integration, digital signatures

Phase 4 MVP (M4-M5)

Installation tracking, completion verification, payment triggers

Phase 5 MVP (M5-M6)

Monitoring system, reporting engine, public dashboard

4. MoSCoW Prioritization

Features ranked by criticality to the first production release and ongoing platform success.

M Must Have
  • Application workflow
  • Contractor registry
  • CEIP agreement builder
  • SPIN2 registration
  • Basic monitoring
  • Annual reporting
  • Role-based access control (RBAC)
  • Audit trail
S Should Have
  • Real-time monitoring dashboard
  • Automated notifications
  • Digital signatures
  • Energy savings calculator
  • Document templates
C Could Have
  • What-if scenario engine
  • Portfolio analytics
  • Public project showcase
  • Mobile app
W Won't Have (v1)
  • AI-powered audit analysis
  • Blockchain audit trail
  • International expansion

5. Execution Tracking Dashboard

Real-time milestone status for the DRC CEIP Platform build-out.

1 Foundation
Not Started
Target: M1 Dependencies: None
2 Phase 1 MVP
Not Started
Target: M2 Dependencies: Foundation
3 Phase 2 MVP
Not Started
Target: M3 Dependencies: Phase 1 MVP
4 Phase 3 MVP
Not Started
Target: M4 Dependencies: Phase 2 MVP
5 Phase 4 MVP
Not Started
Target: M5 Dependencies: Phase 3 MVP
6 Phase 5 MVP
Not Started
Target: M6 Dependencies: Phase 4 MVP
7 Residential Expansion
Not Started
Target: M5 Dependencies: Phase 2 MVP
8 Integration Layer
Not Started
Target: M6 Dependencies: Phase 2 MVP
9 Compliance & Security
Not Started
Target: M6 Dependencies: Integration Layer
10 Calgary Pilot Launch
Not Started
Target: M6 Dependencies: Compliance & Security

6. Risk Register

Identified risks categorized by severity with mitigation strategies.

High Severity

Municipal Partnership Delays

Impact Critical
Likelihood Medium
Category External
Mitigation: Engage multiple municipalities in parallel. Build platform with configurable bylaw templates so any municipality can onboard with minimal customization. Maintain ongoing relationships with municipal contacts and provide regular demos of platform progress.

SPIN2 Integration Complexity

Impact High
Likelihood High
Category Technical
Mitigation: Begin SPIN2 API investigation in Phase 2. Build an abstraction layer to decouple platform from SPIN2 specifics. Maintain a manual fallback process for SPIN2 registration until automated integration is fully validated.

Capital Market Regulatory Requirements

Impact Critical
Likelihood Medium
Category Regulatory
Mitigation: Engage legal counsel specializing in Alberta municipal finance early. Design the agreement builder and loan workflows with regulatory compliance checkpoints. Maintain a compliance matrix that maps platform features to regulatory requirements.
Medium Severity

Contractor Adoption Rate

Impact Medium
Likelihood Medium
Category Market
Mitigation: Simplify contractor onboarding to under 15 minutes. Provide clear value proposition documentation. Offer dedicated onboarding support and create a contractor advisory group to incorporate feedback into platform design.

Property Owner Awareness

Impact Medium
Likelihood High
Category Market
Mitigation: Partner with municipalities for co-branded awareness campaigns. Build a public-facing project showcase demonstrating real savings. Develop energy savings calculators that make the financial case immediately clear to property owners.

Cross-Browser Compliance

Impact Low
Likelihood Medium
Category Technical
Mitigation: Adopt a progressive enhancement strategy with a well-tested design system. Implement automated cross-browser testing in CI/CD pipeline. Define a clear browser support matrix in the engineering standards.
Low Severity

Hosting Infrastructure Scaling

Impact Low
Likelihood Low
Category Technical
Mitigation: Design for horizontal scalability from the start. Use containerized deployments with auto-scaling policies. Conduct load testing during Phase 3 to identify bottlenecks before they impact production users.

Design System Maintenance

Impact Low
Likelihood Low
Category Process
Mitigation: Establish shared CSS design tokens and a component library from the Foundation phase. Assign ownership of the design system. Include visual regression tests to catch unintended drift as the platform evolves.

Documentation Freshness

Impact Low
Likelihood Medium
Category Process
Mitigation: Integrate documentation generation into the development workflow. Use code-generated docs where possible. Include documentation review as a mandatory step in sprint retrospectives.