CONNECTED FLEET EVALUATION
Use a site scorecard to decide whether resident demand, access, assortment, service and data justify a connected micro market.
Demand fit
Traffic, shifts and unmet missions.
Traffic, shifts and unmet missions.
Operating fit
Access, power, network and route.
Access, power, network and route.
Expansion fit
Evidence that can transfer to another site.
Evidence that can transfer to another site.
- Who uses the site and when?
- Which products are unavailable nearby?
- Can access rules be explained in one sentence?
- Can the refill route visit without disrupting residents?
- What payment and refund path is supported?
- Which alerts have a named response owner?
- What data will prove the pilot worked?
| Area | Evidence |
|---|---|
| Demand | Traffic observation, resident survey and nearby-store map |
| Operations | Route time, power, network and service SLA |
| Commercial | Price model, settlement, refunds and venue terms |
| Pilot | Availability, stockouts, utilization and contribution |
Gate A: installation and access pass. Gate B: payments reconcile. Gate C: two review cycles show stable availability and manageable service time. Expand only after Gate C.
Do all residential sites need the same machine? No; site access, product mix and route economics decide configuration.
What is the best first metric? Availability during the actual resident demand window.
What should stop expansion? Unexplained inventory variance, unresolved refunds or an unowned alert queue.
