Supplemental Features — Catalogue & Recommendations
Purpose: beyond the 12 core phases (P0–P11), this catalogue lists every additional capability worth considering for SFMS + Atlas. Each item carries a priority, an effort estimate, and a recommended sequencing slot (extend an existing phase, slot before v1.0, or post-launch).
How to read:
- MUST — pre-v1.0; either extend a phase or slot a small phase between others.
- SHOULD — short post-v1.0 backlog (within 6 months of launch).
- COULD — longer post-launch roadmap (6–18 months).
Effort: XS (≤ 1 wk), S (1–2 wk), M (2–4 wk), L (4–8 wk), XL (> 8 wk).
1. SFMS operational modules
| # | Feature | Priority | Effort | Recommended phase | Notes |
|---|---|---|---|---|---|
| 1.1 | Inventory / Spare Parts Management | SHOULD | M | Phase 12 | Stock levels, reorder thresholds, supplier links, attach parts to work orders. Pairs with CMMS-style operations. |
| 1.2 | Vendor / Contractor Portal | SHOULD | M | Phase 12 | External vendor login (limited tenant); work-order assignment, document exchange, timesheets, compliance docs. |
| 1.3 | Visitor Management | MUST | S | Extend P4 | Kajima BOS reference already includes this (QR via Outlook/Teams). Pre-register, host approval, badge issue, audit. |
| 1.4 | Space / Room Booking | SHOULD | M | Phase 12 | Calendar-integrated, capacity-aware, IoT-linked (auto-release if no presence). |
| 1.5 | Statutory Compliance Tracker | MUST | M | Extend P4 | Periodic inspections (lifts, fire, electrical), certificate expiries, regulator-ready report. |
| 1.6 | Move Management | COULD | M | Post-launch | People + desk + asset moves with checklists. |
| 1.7 | Service Request / Occupant Helpdesk | SHOULD | M | Phase 12 | Occupant-facing app/portal for requests; auto-route to work orders. |
| 1.8 | Safety & Incident Management | MUST | S | Extend P4 | KY-style hazard logging, incident reporting (24h SLA), root-cause analysis, link to assets. |
| 1.9 | Emergency Drill Management | SHOULD | S | Phase 12 | Drill planning, attendance, post-drill review. |
| 1.10 | Lease & Contract Management | COULD | M | Post-launch | Lease terms, renewals, indexation, document store. |
| 1.11 | Cost Allocation / Chargeback | SHOULD | M | Phase 12 | Allocate FM costs per cost-center / tenant / floor; export to ERP. |
| 1.12 | Tenant Billing | COULD | L | Post-launch | Full billing engine (CAM, utilities recharge). |
2. Building intelligence (sensor & analytics)
| # | Feature | Priority | Effort | Recommended phase | Notes |
|---|---|---|---|---|---|
| 2.1 | Indoor Air Quality (IAQ) Monitoring | MUST | S | Extend P11 | CO2, PM2.5, TVOC, RH, temp; comfort + health KPIs; alerts. Critical for ESG and wellness certifications. |
| 2.2 | Occupancy & People Counting | MUST | M | Phase 12 | Wi-Fi probe / camera / sensor / badge fusion. Drives space optimisation, energy savings, comfort. |
| 2.3 | Water Management | SHOULD | S | Extend P11 | Consumption, leak detection (flow anomaly), legionella temperature check, sub-metering. |
| 2.4 | Waste Management | SHOULD | S | Extend P11 | Stream tracking (recycling / landfill / organics), diversion rate KPI for ESG. |
| 2.5 | Lighting Optimisation | SHOULD | M | Phase 12 | Daylight harvesting, schedule optimisation, occupancy linkage. Reuses CPMS + EMS pattern. |
| 2.6 | Renewable & Storage Optimisation | COULD | L | Post-launch | On-site PV optimisation, BESS dispatch, microgrid coordination. |
| 2.7 | Air-Side Optimisation (AHU/VAV) | SHOULD | L | Post-launch | Counterpart to CPMS Phase 10 — AHU + VAV + terminal-unit FDD + optimisation. |
| 2.8 | Building Performance Benchmarking | SHOULD | M | Phase 12 | Cross-building (within and across tenants opt-in) benchmarks: EUI, kW/RT, work-order rates. |
| 2.9 | Predictive Maintenance | SHOULD | L | Post-launch | Per-asset RUL (remaining useful life) using telemetry + work-order history; ML-based. |
3. AI extensions (Phase 6 follow-ons)
| # | Feature | Priority | Effort | Recommended phase | Notes |
|---|---|---|---|---|---|
| 3.1 | Computer Vision for Inspections | SHOULD | M | Post-launch | Photo upload → defect detection (corrosion, leaks, broken signage). |
| 3.2 | Voice Notes & Transcription | SHOULD | S | Post-launch | Field engineer dictates; transcribed + categorised; attached to work order. |
| 3.3 | Document Understanding | SHOULD | M | Post-launch | Extract data from drawings, invoices, datasheets; populate asset attributes. |
| 3.4 | Knowledge Graph over the Data | COULD | L | Post-launch | Entity graph for richer NL query and impact analysis. |
| 3.5 | AI Assistant Personas | SHOULD | S | Post-launch | Per-role assistants (Sustainability, Operations, Compliance) with curated tool sets. |
| 3.6 | Bring-Your-Own-Model (BYOM) | COULD | M | Post-launch | Customers can plug in fine-tuned models per tenant. |
4. Integration & connectors
| # | Feature | Priority | Effort | Recommended phase | Notes |
|---|---|---|---|---|---|
| 4.1 | OPC-UA Connector | MUST | M | Extend P3 | Mentioned as stretch in P3; many industrial buildings require it. |
| 4.2 | Modbus TCP/RTU | MUST | S | Extend P3 | Common for sub-meters; stretch in P3. |
| 4.3 | CMMS / CAFM Bridge | SHOULD | M | Phase 12 | Two-way sync with Maximo, Archibus, TRIRIGA, custom systems. |
| 4.4 | HRIS / SCIM | MUST | S | Extend P2 | User provisioning from HR systems; SCIM 2.0 protocol. |
| 4.5 | ERP Bridge | SHOULD | M | Post-launch | SAP / Oracle for asset, purchasing, finance. |
| 4.6 | Calendar Integration | SHOULD | S | Phase 12 | Microsoft 365 / Google for bookings, approvals, scheduled actions. |
| 4.7 | Microsoft Teams / Slack Notifications | SHOULD | XS | Phase 12 | Channel-targeted alerts and approvals. |
| 4.8 | GIS / Geographic Layer | COULD | M | Post-launch | Site maps, campus view, geofencing for mobile. |
| 4.9 | EV Charging Network APIs | COULD | S | Post-launch | OCPP integration; consumption + cost. |
| 4.10 | Weather Provider abstraction | MUST | XS | Extend P3 | Plug in NOAA / JMA / commercial; required by CPMS + EMS. |
5. Platform capabilities
| # | Feature | Priority | Effort | Recommended phase | Notes |
|---|---|---|---|---|---|
| 5.1 | Marketplace / Plugin SDK | COULD | L | Post-launch | Third-party widgets, connectors, workflow nodes — sandboxed. |
| 5.2 | White-label / Multi-brand | SHOULD | M | Phase 12 | Service-provider mode: per-customer branding, hostname, login. |
| 5.3 | Multi-currency | SHOULD | S | Phase 12 | Cost rollups across regions. |
| 5.4 | Multi-time-zone | MUST | S | Extend P2 | Every site can have its own TZ; reports and schedules respect it. |
| 5.5 | Soft Delete + Restore | MUST | XS | Extend P2 | Recover from accidental deletes within retention window. |
| 5.6 | Entity Versioning | MUST | S | Extend P2 | Diff + revert for asset / location / system records. |
| 5.7 | Bulk Operations Framework | SHOULD | M | Phase 12 | Selection-driven bulk update across list pages; safe preview + audit. |
| 5.8 | Self-Service Backup / Restore | SHOULD | M | Phase 12 | Per-tenant snapshot + selective restore (entity-level). |
| 5.9 | Real-time Co-edit on Dashboards / Workflows | COULD | M | Post-launch | CRDT-based for simultaneous editing. |
| 5.10 | In-App Help & Onboarding Tours | MUST | S | Extend P5 | Guided tours per persona; reduces support load. |
| 5.11 | Localization beyond JP/EN | SHOULD | S | Post-launch | Resource files structured to add languages quickly. |
6. Security, privacy & compliance
| # | Feature | Priority | Effort | Recommended phase | Notes |
|---|---|---|---|---|---|
| 6.1 | Customer-Managed Encryption Keys (CMEK / BYOK) | SHOULD | M | Post-launch | Enterprise requirement for high-trust customers. |
| 6.2 | Data Masking & Redaction | MUST | S | Extend P2 | Field-level masking for PII in audit + exports. |
| 6.3 | PII Inventory & Data Map | MUST | S | Extend P9 | Required for APPI / GDPR; auto-discovered from schemas. |
| 6.4 | Right-to-Erasure Workflow | MUST | S | Extend P9 | Per-user erasure across collections; cryptographic erasure for backups. |
| 6.5 | Data Residency Per Tenant | SHOULD | L | Post-launch | Region pinning enforced at storage layer. |
| 6.6 | Compliance Certifications Dashboard | SHOULD | S | Phase 12 | Surface ISO 27001 / SOC 2 / APPI / PDPA status, audit history, SBOM. |
| 6.7 | IP Allow-list per Tenant | MUST | XS | Extend P2 | Common enterprise control. |
| 6.8 | Audit Trail with Blockchain Anchoring | COULD | M | Post-launch | For very-high-trust customers (regulators, defence). |
| 6.9 | Anti-malware Scan on Uploads | MUST | XS | Extend P4 | ClamAV / commercial scanner before document persist. |
7. Observability & operations
| # | Feature | Priority | Effort | Recommended phase | Notes |
|---|---|---|---|---|---|
| 7.1 | SLO + Error Budget Dashboards | MUST | S | Extend P9 | Per-service SLOs; alert on budget burn. |
| 7.2 | Tenant-Level Usage Metering | SHOULD | M | Phase 12 | Per-tenant cost dashboards (storage, AI calls, API quota). |
| 7.3 | Chaos Testing | SHOULD | M | Post-launch | Game-day program; failure-injection in staging. |
| 7.4 | Feature Flags Service | MUST | S | Extend P0 | Per-tenant / per-user flag management; gradual rollouts. |
| 7.5 | A/B Experimentation | COULD | M | Post-launch | For UX changes. |
8. Developer / partner experience
| # | Feature | Priority | Effort | Recommended phase | Notes |
|---|---|---|---|---|---|
| 8.1 | Webhooks (outbound) with HMAC + retry | MUST | S | Extend P2 | Allow downstream systems to subscribe to events. |
| 8.2 | Public Developer Portal | SHOULD | M | Post-launch | Docs, API reference, SDK, sandbox tenant, examples. |
| 8.3 | Sandbox Tenant per Developer | SHOULD | S | Post-launch | Self-serve sandbox with seed data. |
| 8.4 | Postman Collection (auto-generated) | MUST | XS | Extend P2 | From OpenAPI; published with each release. |
| 8.5 | Custom Reports SDK | COULD | M | Post-launch | Tenants write report templates in YAML / JS sandbox. |
9. Module dependency map (for the additions above)
Phase 12 (proposed) — Operational extensions
├─ Visitor Mgmt (extend P4)
├─ Statutory Compliance Tracker (extend P4)
├─ Safety & Incident Mgmt (extend P4)
├─ Inventory / Spare Parts
├─ Vendor Portal
├─ Service Request / Helpdesk
├─ Space / Room Booking
├─ Cost Allocation / Chargeback
├─ Occupancy & People Counting
├─ Compliance Certifications Dashboard
├─ Tenant-Level Usage Metering
├─ Bulk Operations Framework
├─ Self-Service Backup / Restore
└─ White-label / Multi-brand
Phase-extensions (no new phase needed; bundle into existing)
├─ P0 — Feature Flags Service
├─ P2 — HRIS / SCIM · Multi-TZ · Soft Delete · Versioning · Data Masking · IP Allow-list · Webhooks · Postman
├─ P3 — OPC-UA · Modbus full · Weather Provider abstraction
├─ P4 — Anti-malware scan on uploads
├─ P5 — In-App Help / Onboarding Tours
├─ P9 — PII Inventory · Right-to-Erasure · SLO + Error Budget
└─ P11 — IAQ · Water · Waste (add to EMS)
Post-launch roadmap
AI extensions (CV, voice, doc-understanding, knowledge graph, BYOM)
Air-Side Optimisation
Predictive Maintenance
Marketplace / Plugin SDK
Public Developer Portal
Customer-Managed Keys
GIS layer
Microgrid + BESS optimisation
10. Suggested next moves
- Confirm Phase 12 scope with Product (the 14 items in §9 are the proposed bundle; some can be cut to fit a 4-week phase, some deferred).
- Promote the MUSTs in §9 into the relevant existing phases before the phase begins — e.g., Webhooks and SCIM into Phase 2; OPC-UA and Modbus full into Phase 3; PII Inventory into Phase 9. These are not large deltas individually but shouldn't slip past the gate they belong to.
- Draft Phase 12 outline if confirmed, following the same template as Phases 10 and 11.
- Maintain this catalogue as a live document. Move items between MUST/SHOULD/COULD as customer feedback comes in; archive completed items.
11. Anti-features (intentionally not built at v1)
The following are not recommended for v1.0 even if asked:
- Native mobile shell (iOS/Android) — PWA covers the use cases; native investment can be revisited if metrics warrant.
- General-purpose CMS — Atlas is a data platform, not a website builder.
- Real-time video conferencing — out of scope; integrate Teams/Zoom instead.
- Full ERP functions — integrate, don't rebuild.
- Custom hardware — Atlas is software; partner for hardware.
Saying no protects velocity and identity.