Design the exercise
Name the workflow owner, authority gates, baseline, event schema, roles and success thresholds. Record what is explicitly outside scope.
PILOT & ENGAGEMENT
Start bounded.
Measure what changes.
The proposed next step is a technical working session to choose one mission use case and define a controlled evaluation.
01 / THE EVALUATION PLAN
One use case.
Three deliberate phases.
Progression depends on agreed evidence and partner approval.
Connect a sandbox
Use signed synthetic events, mock recipients, a device simulator and agreed geographic rules. No live public warnings or uncontrolled real equipment.
Run, compare & review
Exercise routing, approval, acknowledgment, update, cancellation and failure cases. Review measured results before considering any expansion.
02 / WHAT SUCCESS WOULD MEAN
A result you can inspect.
Thresholds should be agreed with the evaluation partner; none is invented here.
| Measure | Pilot question | Evidence to retain |
|---|---|---|
| Time | Does an approved event reach the right role faster than the baseline? | Event, approval, dispatch and receipt timestamps. |
| Reach | Were the eligible recipients included and all others excluded? | Expected/actual recipient and geography comparison. |
| Acknowledgment | Did recipients acknowledge, and did tasks complete? | Receipts, acknowledgments and outcome records. |
| Safety | Were unapproved actions blocked? | Denied requests, overrides, expiry and cancellation results. |
| Reliability | What happens when a source or destination fails? | Retry history, exceptions, manual escalation and recovery. |
| Usability | Do reviewers understand the message and requested action? | Exercise observations and partner feedback. |
03 / COMMERCIAL FRAMEWORK
Coverage defines
the service scope.
The geo-range subscription graphic presents a concept, not a government price schedule or contract offer.
Potential scope drivers
Population and geographic complexity; participating jurisdictions; hospitals, laboratories and agencies; alert channels; device integrations; cross-border requirements; support coverage; and training or reporting needs.
Proposed service components
Scoped routing, dashboards, coordination workflows, audit reporting, software maintenance, support and agreed training.
SOURCE CONCEPT ESTIMATES ONLY
- Regional / small state
- From $150,000 / month
- Large state / multi-region
- From $350,000 / month
- National
- From $900,000 / month
- Global / strategic scope
- Custom enterprise scope
Illustrative figures transcribed from the supplied geo-range graphic. Not validated, quoted or approved pricing. Scope, feasibility, acquisition pathway and total cost require separate review.
04 / WORKING-SESSION AGENDA
Arrive with a mission.
Leave with a testable plan.
Choose the owner and handoff
Identify an existing intelligence-to-action gap with a responsible program and operational owner.
Define the boundaries
Agree on recipients, permitted data, approval roles, systems and exclusions.
Review evidence and feasibility
Request architecture, intellectual-property records, safety evidence, security approach, resourcing and integration documentation.
Agree on the evaluation
Document a sandbox plan, baseline, measures, deliverables and an approval point for any next phase. Any letter of intent would be subject to the parties’ normal review.
THE NEXT CONVERSATION
Define one mission.
Prove the handoff.
A technical working session to agree on a use case, ownership, integration boundaries and measurable pilot criteria.
