Gateway Replacement Workflow

Gateway Replacement Workflow

animation
nfc
iot
integration

Lab: Gateway Replacement Workflow

NoteScenario

A maintenance team adds NFC labels to gateways. A technician tap should open the correct gateway service record, show replacement steps, create an audit record, and allow replacement only when the work order and session permit it.

Lab Plan

Read the plan as a sequence of evidence handoffs. Begin with the objective and the approved HTTPS tag payload, then exercise both reader paths so the mobile and service-desk routes are not silently treated as equivalent. Next, apply every policy check before the replacement action: host, schema, released-tag record, technician session, work-order state, and idempotency each closes a different boundary. Run the listed failure tests after the successful path, because an unknown tag, duplicate tap, offline app, unsupported schema, or already-replaced gateway must produce an intentional result. Finish by collecting the decoded payload, decision, audit row, fallback result, and retest trigger as one release record. That order connects the lab to the chapter’s central claim: an NFC tap starts the workflow, while application policy decides what may happen.

lab_plan: objective: validate NFC tap to gateway service workflow tag_payload: approved HTTPS app link with gateway reference reader_paths: - authenticated mobile app - service-desk gateway reader policy_checks: - approved host and schema version - known released tag record - technician session - work-order state - idempotency key failure_tests: - unknown tag - duplicate tap - offline app - unsupported schema - gateway already replaced evidence: - decoded payload - decision result - audit record - fallback result - retest trigger

Review Steps

1. Verify the released tag. Read the tag, decode the record, compare it with the release record, and confirm the installed surface still reads reliably.
2. Validate the event contract. Confirm the tap event includes reader identity, payload hash, schema version, validation result, and idempotency key.
3. Exercise policy branches. Test allowed, denied, duplicate, unsupported, offline, and fallback paths with recorded expected outcomes.
4. Confirm action ownership. The tap opens the service workflow; the session and work order authorize replacement.
5. Capture release evidence. Store the test device, reader path, app version, policy version, audit sample, fallback path, owner, and retest triggers.

Back to the chapter