Implementation Checklist

Implementation Checklist

Implementation Checklist

Use this checklist before accepting an M2M implementation:

  1. Device, gateway, platform, and operations responsibilities are named.
  2. Each message type has a schema version and required fields.
  3. Event time, receipt time, sequence, quality, and provenance are preserved.
  4. Validation has accept, accept-with-marker, reject, and quarantine paths.
  5. The durable queue survives restart and reports age, depth, and replay state.
  6. Acknowledgement is tied to a durable boundary, not just socket success.
  7. Commands have identity, authority, expiry, target, and acknowledgement.
  8. Local fallback has entry, behavior, exit, and reconciliation rules.
  9. Configuration is versioned, validated, and rollback-capable.
  10. Rollout records cover prototype, pilot, staged rollout, and operations handoff.

Back to the chapter