Dispatch assistance & ETA

Support the decision. Show the reasoning.

Compare candidate resources, estimate arrival ranges, and surface configured decision support while keeping dispatchers accountable for the final action.

Explainable assistance

Useful guidance without invented certainty.

Responses label whether they came from a trained model, a rule set, a heuristic fallback, or an external AI provider.

01

Candidate scoring

Score available resources using configured operational factors rather than a hidden autonomous action.

02

ETA quantiles

Use the ETA model pathway for p50 and p90 predictions when a trained accepted model is available.

03

Labelled fallback

Return an explicit heuristic result when model inputs or model artifacts are unavailable.

04

Provider-backed analysis

Optionally use configured OpenRouter-backed analysis, summarization, decision support, or risk assessment with explicit provider failure behavior.

05

Unavailable inputs

Disclose missing weather, traffic, model, or provider data rather than silently fabricating it.

06

Human authority

Keep recommendations in the dispatcher workflow with visible rationale and user-controlled action.

Provenance matters

Every recommendation should answer: “why this?”

The operating team needs to know which method produced the result, what data it used, what was missing, and when to disregard it.

MethodModel, rule, heuristic, external provider, or unavailable.
InputsLocation, unit status, capability, history, and configured factors.
UncertaintyPrediction range, missing feed, fallback, and known limitation.
AuthorityDispatcher review, override, action, and audit trail.
Acceptance before automation

Validate the model in the market and operating environment.

A responsible deployment defines training data, drift, bias, fallback, monitoring, clinical boundary, user authority, and incident response before relying on a recommendation.

  • Document intended use and prohibited use
  • Measure model and fallback performance separately
  • Monitor input availability and change
  • Record user action and overrides
  • Revalidate after material workflow or data changes
DECISION-SUPPORT BOUNDARY

Not autonomous care or dispatch.

The platform can assist operational decisions. It does not claim to replace trained dispatchers, clinicians, medical direction, policy, or local authority.

Test the recommendation

Bring historical scenarios and the rules your dispatchers actually use.

We will compare model, rule, and fallback behavior against an agreed review process.