Search the field guide, causes, requirements, and glossary

Change control

These clauses bring the wireless platform, the vehicles' radios, and the floor itself into the plant's change control, so nothing reaches production untested or mid-shift.

A wireless network changes even when nobody touches it, and it changes more when somebody does. These clauses keep firmware and configuration changes out of production, treat client firmware the way you treat controller firmware, and send physical changes and new traffic through a wireless review before they reach the floor.

Free to copy into any specification (CC0). A starting point for your own wording, not a certified design. All clause groups

  1. 9.1 No automatic upgrades shall

    Automatic and vendor-scheduled firmware upgrades shall be disabled. Every infrastructure upgrade shall be tested first with the production clients, deployed under an approved plan in a maintenance window agreed with production, and have a tested roll-back.

    Where this comes from

  2. 9.2 Configuration changes only in windows shall

    Configuration changes that restart radios or require the wireless network to be shut down shall be made only in maintenance windows, and no setting shall reach the floor outside a window, including from a cloud management portal.

    Where this comes from

  3. 9.3 Client firmware pinned and piloted shall

    Vehicle and client radio firmware shall be pinned per model, recorded in the asset inventory, and tested on a pilot vehicle and route, with a way back, before fleet rollout.1

    Where this comes from

  4. 9.4 Physical changes reviewed for wireless shall

    Physical changes on the floor, including new racking, lines, walls, mezzanines, machines, enclosures, and changes to the stock profile, shall go through change management that includes their impact on the wireless network, and shall trigger revalidation of the affected routes.

    Where this comes from

  5. 9.5 New traffic and new radios reviewed shall

    Any new traffic flow, SSID, vehicle model, or radio in a production area shall be reviewed against the traffic inventory and the spectrum management plan before it goes live, and its supplier shall state its data volume, frequency, band, and marking.

    Where this comes from

About this page

Built from 7 sources: 1 standards body or lab, 2 research papers and theses and 4 vendor documents. Researched and drafted with AI assistance, then reviewed and approved by Ben Rutter on . How pages are made

First published
Last updated
Change history (1)
  • First published
Cite this page

Plain

Ben Rutter. "Change control." OT Wireless, published October 6, 2026, updated October 5, 2026. https://otwireless.com/clauses/change-control/

APA 7

Rutter, B. (2026, October 6). Change control. OT Wireless. https://otwireless.com/clauses/change-control/

BibTeX

@misc{rutter2026changecontrol,
  author = {Rutter, Ben},
  title = {{Change control}},
  year = {2026},
  howpublished = {\url{https://otwireless.com/clauses/change-control/}},
  organization = {OT Wireless},
}