Production case studies: scale-up activities
Production case studies: scale-up activities
Pick one field decision, such as closing a valve or sending a repair visit. Trace the device identity, event time, unit, quality mark, software version, route, decision owner, safe local action, and support record. Name the scale and conditions under which the evidence was gathered.
Test a group update, a failed update, a replaced unit, a lost account, a full queue, a regional link loss, and recovery after power returns. Measure how many units are known, unknown, late, or on the wrong version. Reconcile the count before calling the fleet healthy.
Success at one site does not prove a design for every building, season, network, or support team. Record the limit and the event that forces a new review.
Use this pilot-to-fleet check:
- Count every unit expected in service.
- Count every unit actually seen.
- List all active software versions.
- Mark units with unknown owners.
- Replace one unit and trace identity.
- Fail one update and recover it.
- Lose one region and count impact.
- Fill one queue on purpose.
- Restore power and reconcile records.
- Check the local safe path.
- Name the support owner for gaps.
- Set the next fleet review trigger.
Start simple: take one field case and write what changed when it moved from pilot to fleet. The case is useful when the proof shows how the system stayed controllable.
Scale-up decision prompts:
- What work is still manual in the prototype?
- How are devices provisioned, configured, updated, and retired?
- What happens when many devices reconnect, report errors, or request updates at the same time?
- How are fleet differences tracked: hardware revision, firmware version, location, connectivity, and sensor type?
- Which metrics trigger a rollout pause or rollback?
Technical boundaries. The scale-up drill uses an illustrative fleet and failure list; a real fleet needs its own device counts, update windows and support limits, so treat the cases as practice, not as a plan.