A connected machine is part of an operating system that includes people, networks and support arrangements. Procurement decisions can determine how it is accessed, updated and restored after a problem. Leaving these questions until commissioning limits the options and can create friction between production requirements and cyber controls. The specification should expose them while the supplier's scope is still negotiable.
Describe the connections and access needs
Identify which systems the equipment must exchange information with and why each connection is needed. Clarify remote support, supplier accounts and local maintenance access. Ask how access will be authorised, reviewed and withdrawn. A general statement that the machine supports connectivity is not enough to define its operating relationship with the factory.
Include the people responsible for controls, production support and cyber security in the specification review. Their objectives overlap but may use different terminology. A shared description of the required production function helps them evaluate access without losing sight of the machine's duty, support needs and operating constraints.
Specify recovery as a purchased capability
Agree what configuration, programs and documentation will be handed over. Clarify the backup arrangements and what is required to restore equipment after a failure or disruption. A file copied to storage may not be sufficient if restoration depends on unavailable software, licences or specialist knowledge. The buyer should understand the complete recovery route.
NIST's manufacturing cyber resources include backup considerations for operational technology. They provide a useful reference, not a UK legal compliance checklist. The procurement application is to ask for a recoverable operating package and evidence that it works, rather than treating backups as an administrative task after installation.
Test controls against operational requirements
Discuss how proposed security measures affect the equipment's performance, support and maintenance workflows. NIST's robotic workcell research examines cyber measures alongside operational performance. The transferable principle is to evaluate the system together. A control should be technically appropriate without being assessed in isolation from the process it protects.
Plan changes and testing with competent specialists. Avoid assuming that an ordinary office IT practice can be applied unchanged to every industrial device. Ask the supplier to state supported update methods, dependencies and any restrictions. Record how vulnerabilities and software changes will be communicated during the equipment's operating life.
Close the handover gaps before acceptance
Review user and supplier access, documentation, recovery evidence and support responsibilities as part of acceptance. Make unresolved issues visible to the authorised decision-makers. A machine can produce acceptable parts while its ownership and recovery arrangements remain incomplete. Those are different questions and need separate evidence.
Maintain the agreed arrangements after the project team leaves. Changes in supplier support, network connections and equipment duty can alter the original assumptions. Procurement is the best moment to purchase clear cyber and recovery interfaces, but their value depends on continued ownership. A maintainable connected machine is one whose access and restoration routes remain understood throughout operation.
Sources & further reading
NIST: Manufacturing Profile Implementation Methodology for a Robotic Workcell ↗
Voluntary research context on cybersecurity and operational performance in a robotic workcell.
Official manufacturing cybersecurity resources, including backup considerations; not a UK legal compliance statement.
Prepared 2026-10-13. Source references retained from that edition. Corrections and feedback.