Provisioning a Replacement Device Mid-Shift

A workable order is:

1. Set date, time, and time zone first. The clock is seven minutes slow, and certificate validation, audit timestamps, and record ordering all depend on correct time. Correcting time after records are created would leave misleading timestamps.
2. Set locale, units, and 24-hour format. Set metric units and the plant's time format before any inspection data is entered, because changing units later can silently reinterpret stored values.
3. Join the 2.4 GHz network and install or validate the sync certificate. The device cannot pull the site profile or sync inspections without network trust. Do this before the profile step so the profile can be retrieved centrally rather than typed by hand.
4. Apply the site device profile and enter the asset tag. The procedure requires the asset tag before production data, so this must precede the first inspection record.
5. Configure the scanner to the serial profile expected by the cradle. The default keyboard-wedge mode would send barcode characters as keystrokes and may not interoperate with the line's cradle.
6. Run acceptance tests before releasing the device. Test a scan, a metric inspection record, a 24-hour timestamp, and a sync.

The order matters because later steps depend on earlier ones. For example, a wrong clock can cause certificate rejection, and a wrong network band prevents profile download. The old device's 14 unsynced records must also be reconciled or transferred before the old device is retired.

The certificate should be renewed or replaced before the device is released, not deferred because the device works today. A four-day expiry is inside the device's likely field window, and an expired certificate can cause sync failures at the worst possible time, after inspection data has accumulated locally.

The technician should:

• Install the renewed certificate and its trust chain through the approved management channel.
• Verify that the device clock and time zone are correct, because a valid certificate can still fail validation against a wrong clock.
• Test an actual TLS connection to the sync endpoint, not just check that the certificate is present.
• Confirm that the new certificate's subject and endpoint match the site's sync service.
• Record the expiry date and set a renewal reminder.

Disabling certificate validation or accepting an untrusted certificate to "make it work" is not acceptable: it weakens the integrity of the inspection records and may violate site security policy. If renewal cannot be completed before the shift, the device should be restricted to local recording with a documented sync limitation, and the supervisor should approve that interim control.

The device is ready only when it passes checks that mirror real production use:

1. Identity and profile - the correct asset tag is displayed, and the site profile is active.
2. Time and units - the timestamp is 24-hour and matches the plant clock; a test length or weight entry displays metric units.
3. Scanning - scan at least ten known case barcodes through the cradle and confirm the correct characters appear in the right field, with no keyboard-wedge duplication.
4. Record creation - create one test inspection record with a known value and confirm it saves with the correct user, asset, date, and time.
5. Sync - upload the test record and confirm it reaches the correct server record set; then confirm the device reports a successful sync.
6. Capacity and power - check storage headroom and battery state; the spare is at 88%, but the installed battery should be confirmed as adequate for the shift.
7. Legacy data - the old device's 14 unsynced records are transferred or explicitly reconciled, so the replacement does not cause a hidden data gap.

A quick visual check is not enough. The acceptance test should prove that a scanned, metric, time-stamped inspection record can travel from the line to the server without manual correction.