Source systems own observations; the analytics product owns declared calculations; accountable teams own decisions and outcomes.
Analytics, KPI and operational reporting
Carry named definitions, source windows, denominators, gaps, privacy policy and reproducible calculation revisions.
Name the source—and name what it cannot prove.
The same message can be observation, projection, plan, receipt or physical evidence. This contract keeps those meanings separate.
Missing coverage, withheld data, late events and definition changes remain visible; predictions and estimates are labelled.
A dashboard metric, score, forecast or candidate does not imply causal effect, billing acceptance or operational decision.
Producer and consumer responsibilities are explicit.
A product can appear on both sides when it transforms one authority into another; each transformation retains its own evidence.
Producers
SAAS-01Connected Vehicle CloudSaaS & cloudSAAS-02InTouch & Fleet Control TowerSaaS & cloudSAAS-03RouteNet OptimizationSaaS & cloudSAAS-05EV Journey & Charging CloudSaaS & cloudSAAS-08Geoanalytics & Command CenterSaaS & cloudSAAS-11Charging Intelligence OperationsSaaS & cloudChoose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
Compatibility vector
- schema or ABI version
- producer release
- consumer release
- policy and entitlement revision
- content/configuration revision
- territory/platform profile
Acceptance evidence
- contract compatibility
- nominal and negative scenarios
- ordering, replay and idempotency
- latency, capacity and resource bounds
- security, privacy and role enforcement
- offline, recovery and rollback
- target or operational acceptance
Freeze the Analytics, KPI and operational reporting contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.