- product-portfolio
- ecosystem-catalog
- deep-dives
- vertical
Energy, Utilities, ESG & Sustainability - Analysis¶
Planning-layer analysis for category 26. It groups the 50 candidate services into capabilities, recommends what becomes a standalone service versus a module, and captures domain, interface, and non-functional notes. For the plain item list see the browse page.
Scope & Bounded Context¶
- Primary bounded context: Energy & ESG
- Group: vertical
- Default wave / cycle: Phase 5 · Cycle 5: Marketplace & Ecosystem
- Items: 50 candidates
This category is anchored to the ConnectSoft DDD baseline in the SaaS framework DDD blueprint and the service classification model.
Classification Breakdown¶
| Classification | Count |
|---|---|
| Module-in-service | 36 |
| Platform Product | 7 |
| Portal/UI Module | 6 |
| Workflow Template | 1 |
Anti-fragmentation stance
Per ADR-0011, the 36 module candidates below are delivered inside the Energy & ESG bounded-context service, not as separate microservices. Only the 7 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-1252 | Utility Billing Platform | 1 | Planned |
| CS-SVC-1255 | Carbon Accounting Platform | 5 | Planned |
| CS-SVC-1256 | Smart Meter Data Platform | 5 | Planned |
| CS-SVC-1262 | Energy Trading Platform | 5 | Planned |
| CS-SVC-1281 | Waste Management Platform | 5 | Planned |
| CS-SVC-1298 | Utility Control Tower | 5 | Planned |
| CS-SVC-1300 | Climate Intelligence Platform | 5 | Planned |
Portal / UI Modules¶
- Utility Customer Portal (
CS-SVC-1258) - Charging Station Portal (
CS-SVC-1267) - ESG Reporting Portal (
CS-SVC-1272) - Sustainability KPI Dashboard (
CS-SVC-1273) - Supplier Sustainability Portal (
CS-SVC-1278) - ESG Executive Dashboard (
CS-SVC-1299)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Energy & ESG context; cross-context reads go through published contracts, never shared databases.
- Integration is event-first (outbox + integration events) per the event-driven mindset.
- APIs are contract-first and versioned through the API & Integration context.
Non-Functional Posture¶
- Multi-tenancy & edition-awareness: required for all serious candidates.
- Security: Standard baseline; secrets via the platform secret store; least privilege.
- Compliance: critical - audit + evidence by default.
- Observability: OpenTelemetry traces, metrics, and structured logs.
MVP vs Future¶
- MVP (Tier 0-1): Utility Billing Platform, Sustainability Audit Service
- Future (Tier 4-5): Energy Usage Monitoring, Renewable Energy Asset Management, Grid Outage Management Service, Carbon Accounting Platform, Smart Meter Data Platform, Meter Reading Service, Utility Customer Portal, Tariff Management Service
Open Questions¶
- Which module candidates, if any, develop independent scaling or ownership needs that would justify promotion to a standalone service?
- Where do this category's contracts overlap with adjacent contexts, and who owns them?