Roadmap
Where this is going, stage by stage.
Nothing on the path to the first release depends on any vendor's permission. Dates are not promised; order is.
Capabilities
| Capability | Status | When |
|---|---|---|
| Atoll lab preview: install, setup, read a BACnet lab, import and correlate | Preview | Lab preview on GitHub, not a release |
| Expected artifacts per site, delivery receipts, overdue list | Preview | Public code; in the next lab build |
| Change reports between two backups, in controls language | Preview | Public code; in the next lab build |
| Whole-record export in open formats | Preview | Public code; in the next lab build |
| Scheduled pulls through documented platform mechanisms | Planned | Phase 4 |
| Import a station backup and see the model | Planned | Phase 2 |
| Import a Metasys .caf | Planned | Phase 4 |
| Import a Distech .gfx | Planned | Phase 4 |
| Import a Metasys SCT export | Planned | Phase 4 |
| Import an equipment schedule | Planned | Phase 4 |
| Model with provenance and questions | Planned | Phase 2–3 |
| Model-driven equipment views from instances | Planned | Phase 3 |
| BACnet/IP read-only connector | Planned | Phase 3 |
| Modbus TCP and RTU connector | Planned | Phase 4 |
| Niagara station connector (optional) | Planned | Phase 4, pending legal review |
| Semantic comparison of two station snapshots | Planned | Phase 3 |
| Drift detection: engineering vs controller vs supervisor | Planned | Phase 3 |
| Alarm and history configuration from the model | Planned | Phase 3 |
| Documented API and read-only MCP tools | Planned | Phase 3 |
| Floor-plan views with live equipment markers | Planned | Phase 5 |
| Commissioning verification and baselines | Planned | Phase 5 |
| Troubleshooting context and diagnostics | Planned | Phase 5+ |
| Offline operation proven by tests | Planned | Phase 2–3 |
| Signed, checksummed releases of the runtime | Planned | Phase 3 |
| Optional hosted services and trial | Planned | Phase 6, after security review |
Phases
Foundation
- Public repository, license, contributing guide, code of conduct, security policy, governance
- CI: tests, dependency and secret scanning, release approval gate
- Synthetic fixtures only; a check that refuses anything else
This website
- Every section with real content and honest status
- Security promises with implemented and planned marked
- No external requests, no analytics, self-hosted assets
The record: importers, the model, Atoll
- Station backups (.bog, .dist) and controller files (.caf, .gfx) read offline with hardened archive and XML handling
- The model: facts with provenance, supersede chains, snapshots, diff by identity
- Atoll: the local runtime with encrypted artifacts, permissions as facts, drawings and submittals, a BACnet/IP read-only connector
- A lab preview you can install (GitHub, not a release)
The system of record, then the first release
- Intake with accountability: expected artifacts per site, delivery receipts, an overdue list (public code)
- Change reports between two backups in controls language (public code)
- Whole-record export in open formats (public code)
- Equipment instances with parameters and relationships, each with provenance
- Questions queue; confirm and reject
- Model-driven equipment views from one shared template per type
- Semantic comparison of snapshots and drift detection
- BACnet/IP read-only connector using addresses found in imports
- Local web app, documented API, read-only MCP tools
- Offline tests: network-denied suite, egress tripwire, WAN-outage scenario
- Signed, checksummed release with a software bill of materials
More sources
- Modbus TCP and RTU
- Metasys .caf, Distech .gfx, Metasys SCT export, equipment schedules
- Niagara station connector, optional, after legal review of the vendor terms
Operations
- Floor-plan views with live markers from the model
- Commissioning verification: repeatable functional tests and verified baselines
- Troubleshooting context and diagnostics from relationships and histories
Optional hosted services
- Private trial with synthetic data
- Authorized pilot with controlled retention
- Public trial only after an external review and counsel-approved policies
The badge vocabulary
- Available
- A versioned download exists. Only a release record can set it. Nothing is Available today.
- Preview
- Code is public in the repository; no release.
- Planned
- Design or roadmap only. Never shown in a solid colour.
- Proven
- Used in prose only, always followed by where: "proven on a live 4.15 station", "proven on the test harness".
One data file drives every badge on this site. The build fails if a page claims Available without a release record or shows two different badges for one capability.