● IGNITION100%
InduX // Manufacturing Intelligence System
Skip to content
induXManufacturing
intelligence
When your business changes

What Changes When You Introduce Automation or Connected Technology?

Automation can increase capacity while consolidating production, safety and recovery dependency into a connected system. The critical question is how the operation behaves when access, software or connectivity is unavailable.

Change in practiceIllustrative example

A plastics manufacturer installs a robotic cell to handle part removal across three injection-moulding presses. A central monitoring system allows a shift to run with fewer people on the floor, while the machine builder’s engineers can connect remotely for diagnostics. Operations and engineering deliver the project on time and on budget. No one outside the project team is asked to map the new connections, confirm who can access them, or establish what happens to all three presses if remote access or the shared system must be isolated.

When this applies
This applies whenever equipment or software creates a live link between the shop floor and an internal network, external vendor, integrator or cloud service—not only obvious remote-diagnostics arrangements. Recognise it when production can run unattended for periods it could not before; one control or monitoring platform oversees several machines or lines; operations or engineering implements the change without an OT-focused security and safety review; or continued operation, support or recovery now depends on remote access, a licence, cloud service, internal IT or a third-party specialist.
What exposure may have shifted
Cyber exposure has moved into the production environment, where loss may include unsafe conditions, altered process parameters, defective output or stopped production—not only loss of data. Unattended running may also change fire, guarding, supervision and emergency-response assumptions that were set before the technology was introduced. Where one platform coordinates several machines, previously separate failure points may have become one shared failure domain. A fault, compromised account, failed update or isolation decision can therefore affect more production at once than the individual machines suggest.
Dependencies created or intensified
The business may now depend on the vendor or systems integrator; remote-access service; cloud platform or software licence; network equipment; supported software versions; specialist control hardware; independent configuration backups; and the small number of people able to diagnose the system safely. The dependency is not simply that vendor access remains available. The business must also be able to identify, approve, monitor and revoke that access without creating an uncontrolled production or safety consequence. If only the vendor holds current PLC logic, robot programmes, recipes or system configuration, technical knowledge and recovery capability sit outside the manufacturer.
The first 30 days
If the connected system must be isolated because of a fault, suspected compromise or failed update, leadership needs to know what stops, what can continue safely and who is authorised to decide. Not every automated process has a viable manual mode, and a theoretical fallback may not maintain required quality, volume or safety. Recovery may require clean configuration, specialist access, replacement control hardware, vendor support and evidence that the process is safe and stable before production resumes. The first-month test is whether the business can sustain, isolate and restore the operation without relying on the same connection or person that has become unavailable.
Relevant InduX pillars
  • Emerging Risk — changing OT connectivity, remote access, cloud dependence and vendor support create attack paths and failure modes that may not be covered by older risk assumptions.
  • Operational Resilience — one connected platform can become a shared failure domain across several machines, lines or shifts, while the true degraded-operation and recovery path remains untested.
  • People & Workforce — safe operation, security, isolation and restoration may depend on a small number of internal specialists or external engineers.
Evidence and controls to examine
Start with an asset and connectivity map showing each machine, controller, network connection, remote-access route, cloud service, data flow and responsible owner. Maintain an authorised-access list and confirm whether vendor access is persistent or enabled only when approved, how identity is verified, whether activity is logged and who can revoke it. Review the machinery, process, fire and safety assessments for unattended or reduced-supervision operation. Check network segregation, secure configuration, change and update control, incident escalation and the support or end-of-life position for critical software and hardware. Hold versioned copies of PLC logic, robot programmes, recipes and configuration independently of the vendor, then test that they can actually be restored. Document the safe degraded mode and isolation sequence, including what quality or production limitations remain.
Five board questions
  1. 01Do we have a current, owned map of every connection this technology creates, including vendor, cloud and internal-network access?
  2. 02If remote access or the shared system had to be isolated immediately, which machines would stop, what could continue safely and who would make that decision?
  3. 03Do we hold current, independent and tested-restorable copies of the PLC logic, robot programmes, recipes and system configuration?
  4. 04Has the change been reviewed through OT security, machinery safety, fire, quality and continuity lenses rather than assumed to fit an existing IT policy?
  5. 05Who can operate, secure, isolate and restore this system without the primary specialist or vendor, and how has that competence been demonstrated?
Three actions
  1. 01Map and assign ownership to every connection, account, service and data flow introduced by the technology, removing or restricting access that has no clear operational purpose.
  2. 02Run a controlled isolation and degraded-operation exercise, recording what stops, what remains safe, what quality limitations arise and how vendor access is revoked and restored.
  3. 03Create independent, versioned configuration backups; prove they can be restored; and cross-train a second competent person in the safe recovery process.