resource classes
to co-manage
police · fire · transit
utility · EMS = B5
constraint dimensions
governing those classes
geography · skill · time
priority · SLA · demand
$200M+ Yr-1 Benchmark
SymphonyAI computes C from an operational environment description, assigns the domain to the appropriate Zone, and deploys the correct engine configuration — eliminating the architectural guesswork that causes every competing system to either over-engineer simple problems or collapse under complex ones.
Continuously measures the Index of Optimality (IO) — a real-time metric expressing how close the current schedule is to the theoretical optimum. When IO decay reaches the τ threshold, SymphonyAI autonomously triggers recomputation. No human decides "when do we re-optimize." The math does.
Simultaneously co-optimizes all resource classes — not sequentially, not in silos — using a unified constraint satisfaction engine that processes all B classes across all E dimensions in a single computational pass. The result is a schedule that is globally optimal across the entire resource ecosystem, not locally optimal within each class.
When an event in one domain crosses a significance threshold, the CDSP layer propagates its implications to all dependent domains simultaneously in under 500ms — before any human connects the dots. A water main break signals transit, police, emergency services, and hospitals autonomously. No coordination meeting required.
SymphonyAI deploys resources to predicted demand locations before demand materializes, using probabilistic demand forecasting and the pre-positioning engine. Multi-Hop Assignment Optimization (MHAO) optimizes not just the next task assignment but the next 3–5 simultaneously — eliminating the myopic next-ticket local optimum that plagues all reactive systems.
The BT Field Service deployment is the reference benchmark against which all Symphony-AI domain projections are scaled. B=4 resource classes (engineers, vehicles, parts, job types) · E=7 constraint dimensions (geography, skill, time, priority, SLA, parts availability, customer dependency) · τ=15 minutes empirically determined as the optimality half-life for dynamic trouble-ticket field operations. Zone 3 engine deployed. Complexity ratio C/C_ref scales efficiency recovery projections for any target domain.