vaayaa Inclusive Education
Technical risk assessment

Industry 4.0 Technologies Risk Assessment: Connected Plant Hazards and Controls

A worked example of how a manufacturing site identifies, scores and controls risks from connected machines, robots, sensors, data platforms and external technology suppliers.

Updated November 2026 8 hazards assessed Review every 6 months Highest risk: Critical to Medium
See the Industry 4.0 Technologies course

Executive summary

This assessment shows how a discrete manufacturing site can identify, rate and control the risks that come with connected machines, robots, sensors, data platforms and external suppliers. Eight hazards were selected because they are plausible in daily plant work, from network loss and cyber intrusion to robot motion, sensor drift, supplier defects, procedural deviation, maintenance failure and data protection. Cyber intrusion and unexpected robot motion carry the highest inherent scores because their impact on people and production is severe. Each hazard is scored before controls and again after existing and additional controls. Most residual scores fall to Medium or Low, but cyber exposure stays at Medium because the consequences remain serious. The first actions are a segmented network with a tested fallback, safety scanner verification after every change and a supplier acceptance test. The site is a teaching example, so every score illustrates method rather than describing a real plant.

Focus area
Industrial automation, connected manufacturing and digital production systems
Setting
Discrete manufacturing plant with networked machines, robotic cells, plant data analytics and external technology suppliers
Method
Five by five likelihood and severity risk register with inherent and residual scoring

Scope

This assessment covers a discrete manufacturing site using connected machines, collaborative and industrial robots, sensors, a plant data platform and remote supplier support. It considers risks to people, equipment, product quality, data and continuity of supply. Jurisdiction, plant layout, vendors and technology stack are not specified, so they are treated as assumptions. It does not replace a formal site-specific risk assessment, functional safety review or cybersecurity assessment.

Context

The plant runs several cells where programmable logic controllers feed a supervisory system, which passes production and machine condition data to an analytics platform hosted off site. Collaborative robots share floor space with operators at some stations. Maintenance uses sensor alerts to plan work, and a small team of engineers configures machines and updates software. Two external suppliers provide components, remote support and the analytics service. Each hazard is scored before controls to show its natural level, then again after existing controls and the additional controls proposed here.

Objectives, assets and stakeholders

The objective is to keep people safe, keep machines running within their design limits, protect product quality and engineering data, and meet the duties that apply to the site. The assets in scope are programmable controllers, supervisory systems, collaborative and industrial robots, sensors, the plant data platform, spare parts and the engineering records behind each machine. Stakeholders include operators, maintenance and engineering staff, the plant manager, customers, component suppliers, remote support providers, the data protection lead and any authority with responsibility for workplace safety or personal data. Every risk has one owner role. The operations manager keeps the register current and reports to the plant leadership team at each review.

Risk matrix: before and after controls

Each cell shows hazard numbers placed by likelihood and impact. Compare the two grids to see how controls move each hazard.

Before controls

Inherent risk

Risk before controls: rows are likelihood from almost certain to rare, columns are impact from insignificant to catastrophic. Cells list hazard numbers.
1
Insignificant
2
Minor
3
Moderate
4
Major
5
Catastrophic
5 Almost certain
4 Likely Likelihood 4, impact 3, score 12, high: H06 Likelihood 4, impact 4, score 16, high: H01 Likelihood 4, impact 5, score 20, critical: H02
3 Possible Likelihood 3, impact 3, score 9, medium: H07 Likelihood 3, impact 4, score 12, high: H04 H05 Likelihood 3, impact 5, score 15, high: H03
2 Unlikely Likelihood 2, impact 4, score 8, medium: H08
1 Rare

After controls

Residual risk

Risk after controls: rows are likelihood from almost certain to rare, columns are impact from insignificant to catastrophic. Cells list hazard numbers.
1
Insignificant
2
Minor
3
Moderate
4
Major
5
Catastrophic
5 Almost certain
4 Likely
3 Possible
2 Unlikely Likelihood 2, impact 2, score 4, low: H06 H07 Likelihood 2, impact 3, score 6, medium: H01 H04 H05 Likelihood 2, impact 4, score 8, medium: H02 H03
1 Rare Likelihood 1, impact 3, score 3, low: H08
  • Low 1 to 4
  • Medium 5 to 9
  • High 10 to 16
  • Critical 17 to 25

Hazard register

A summary first, then the detail for each hazard.

Summary of hazards with scores before and after controls
No.HazardBeforeAfterOwner
H01 Loss of network connectivity between machines and control systems 16 High 6 Medium Plant automation engineer
H02 Cyber intrusion into connected production systems 20 Critical 8 Medium Industrial cybersecurity lead
H03 Unexpected motion of robots and automated cells 15 High 8 Medium Safety engineer
H04 Sensor drift and data quality errors in process decisions 12 High 6 Medium Quality engineer
H05 Supplier component defect or specification mismatch 12 High 6 Medium Supply chain manager
H06 Skills gaps and procedural deviation during reconfiguration 12 High 4 Low Operations manager
H07 Predictive maintenance failure and unplanned downtime 9 Medium 4 Low Maintenance manager
H08 Data protection and worker monitoring compliance gaps 8 Medium 3 Low Data protection lead
H01

Loss of network connectivity between machines and control systems

Operational Before 16 After 6

Switch, wireless or gateway failure cuts the link between controllers, robots and the supervisory system, so machines stop or run without current data and alarms are lost.

Who or what is affected: Operators, maintenance staff and production planners

Causes

Single points of failure, unmanaged wireless links and firmware updates applied without testing.

Consequences

Unplanned stoppage, scrap, delayed orders and unsafe restart if machines resume unexpectedly.

Existing controls

  • Machines fail to a safe state when communication is lost.
  • Network switches are duplicated at the main cabinet.

Control gaps

Fallback procedures are not rehearsed and the network map is out of date.

Additional controls

  • Prevent: Separate control traffic from office traffic and document every network segment.
  • Respond: Keep a manual fallback procedure and trained staff for each cell during an outage.
Likelihood 4 x impact 4 before; 2 x 3 after Owner: Plant automation engineer Target: Within 45 days Early warning: Repeated loss of heartbeat signal from any cell in one week.
H02

Cyber intrusion into connected production systems

Technology and data Before 20 After 8

An attacker or careless user gains access through remote support, email or a removable drive and alters machine settings, stops production or steals engineering data.

Who or what is affected: Operators, engineers, customers and suppliers whose data is held

Causes

Shared accounts, unpatched controllers and remote access left open after vendor visits.

Consequences

Halted lines, altered parameters that damage equipment, stolen designs and loss of customer trust.

Existing controls

  • Remote access requires an individual account and password.
  • The supervisory system is backed up nightly.

Control gaps

Controllers past their support period cannot be patched and vendor accounts are not reviewed.

Additional controls

  • Prevent: Restrict remote support to approved sessions and enable multi-factor sign in.
  • Detect: Monitor network logs for new devices and unusual machine setting changes.
Likelihood 4 x impact 5 before; 2 x 4 after Owner: Industrial cybersecurity lead Target: Within 30 days Early warning: A new device appearing on a production network segment without a record.
H03

Unexpected motion of robots and automated cells

Safety Before 15 After 8

A robot moves outside its programmed path after a software change, a sensor fault or a bad teach point, and strikes an operator or equipment within its reach.

Who or what is affected: Operators, cleaners, maintenance technicians and nearby visitors

Causes

Untested program changes, worn joints, sensor drift and reaching into cells during a fault.

Consequences

Crush, cut or impact injuries, equipment damage and an enforced stop of the cell.

Existing controls

  • Light curtains stop the cell when a person enters the work envelope.
  • Operators are trained on lockout before entering a cell.

Control gaps

Safety scanners are not tested after software updates and speed limits are not checked against the risk assessment.

Additional controls

  • Prevent: Verify each program change in a safe test mode before resuming production.
  • Respond: Post emergency stop points and rehearse a rescue drill for each collaborative cell.
Likelihood 3 x impact 5 before; 2 x 4 after Owner: Safety engineer Target: Within 30 days Early warning: Protective stop events in one cell rising over a two week period.
H04

Sensor drift and data quality errors in process decisions

Operational Before 12 After 6

Sensors drift out of calibration, tags are mapped to the wrong signal, or timestamps are wrong, so operators and analytics tools make decisions on inaccurate process values.

Who or what is affected: Process engineers, quality staff and customers receiving product

Causes

Gaps in manual calibration, tag renaming without review and harsh shop floor conditions.

Consequences

Off-specification product, false alarms, missed faults and rework.

Existing controls

  • Critical sensors are calibrated each quarter.
  • Alarm limits are set in the control system.

Control gaps

Calibration records are kept but not compared with sensor trends between visits.

Additional controls

  • Detect: Compare redundant sensors and flag readings that disagree beyond a set band.
  • Prevent: Keep a tag register with owner, unit and mapping, and check changes before release.
Likelihood 3 x impact 4 before; 2 x 3 after Owner: Quality engineer Target: Within 60 days Early warning: Two redundant sensors differing by more than the agreed band for a full shift.
H05

Supplier component defect or specification mismatch

Supplier Before 12 After 6

A purchased drive, sensor or software module does not meet the agreed specification, or a supplier update changes behaviour, so machines perform below the design intent.

Who or what is affected: Production staff, product customers and the supply chain team

Causes

Unapproved part substitution, vague specifications and supplier firmware changes that are not announced.

Consequences

Line stoppage, quality escapes, warranty claims and damage to supplier relationships.

Existing controls

  • Incoming components are checked against a purchase specification.
  • Supplier certificates of conformity are filed for each batch.

Control gaps

Certificates are checked for presence but not for content, and second sources are not qualified.

Additional controls

  • Prevent: Write acceptance tests into supplier contracts and require notice before any firmware change.
  • Recover: Qualify a second source for critical drives and keep spare parts on site.
Likelihood 3 x impact 4 before; 2 x 3 after Owner: Supply chain manager Target: Within 90 days Early warning: Rising rejection rate on a single supplier part number over two consecutive deliveries.
H06

Skills gaps and procedural deviation during reconfiguration

People Before 12 After 4

Engineers and operators change setpoints, recipes or software without following the approved procedure or without understanding the new digital interfaces, leaving unsafe or unverified settings in place.

Who or what is affected: Operators, technicians, engineers and nearby colleagues

Causes

Time pressure, unclear interfaces and reliance on tacit knowledge from experienced staff.

Consequences

Quality defects, equipment damage, injury and rework.

Existing controls

  • Changes need a written work order.
  • Operators complete induction on each machine.

Control gaps

Induction is not refreshed after software changes and change logs are not audited.

Additional controls

  • Prevent: Require a two person check and a verification record before any recipe or parameter goes live.
  • Detect: Audit change logs each week and compare them with approved work orders.
Likelihood 4 x impact 3 before; 2 x 2 after Owner: Operations manager Target: Within 45 days Early warning: Parameter changes made without a linked work order in a shift.
H07

Predictive maintenance failure and unplanned downtime

Operational Before 9 After 4

Analytics models give false reassurance or miss early wear signs on bearings, motors and tooling, so equipment fails between planned services and production is interrupted.

Who or what is affected: Maintenance technicians, production planners and customers awaiting delivery

Causes

Models trained on limited data, poorly mounted sensors and alerts that are ignored.

Consequences

Unplanned stoppage, expensive emergency repairs and late deliveries.

Existing controls

  • Scheduled preventive maintenance runs to a fixed calendar.
  • Vibration alerts are sent to maintenance staff.

Control gaps

Model accuracy is not measured against actual failures and spares are not reviewed.

Additional controls

  • Detect: Check model alerts against technician inspection results each month.
  • Respond: Keep a critical spares list and a standby plan for the most important assets.
Likelihood 3 x impact 3 before; 2 x 2 after Owner: Maintenance manager Target: Within 60 days Early warning: Two unplanned failures on one asset within a month with no prior alert.
H08

Data protection and worker monitoring compliance gaps

Legal and compliance Before 8 After 3

Worker location, camera or performance data collected by connected systems is kept longer than needed, shared without notice or used beyond its stated purpose, which may breach the duties that apply.

Who or what is affected: Workers, supervisors and external data processors

Causes

Vendor default settings, unclear purposes and retention rules that were never configured.

Consequences

Complaints, enforcement action, fines and loss of worker trust.

Existing controls

  • Access to personnel data is limited to human resources.
  • A privacy notice is shown to new staff.

Control gaps

Retention settings are not checked and vendor contracts are not reviewed for data transfer terms.

Additional controls

  • Prevent: Map each data field to a purpose and a retention period before collection starts.
  • Respond: Record and report any unauthorized sharing to the data protection lead for review.
Likelihood 2 x impact 4 before; 1 x 3 after Owner: Data protection lead Target: Within 90 days Early warning: A data export request that cannot be answered from the system map.

Rating method and evaluation

Each hazard is rated on two five-point scales. Likelihood runs from 1 for rare to 5 for almost certain over the next year, and severity runs from 1 for minor to 5 for catastrophic, covering injury, equipment loss, product quality, data exposure and stoppage time. Multiplying the two gives a score from 1 to 25 that falls into one of four bands: Low from 1 to 4, Medium from 5 to 9, High from 10 to 16 and Critical from 17 to 25. Inherent risk is the score before controls, and residual risk is the score after the existing and additional controls. A residual score must never exceed the inherent score, and where inherent is 10 or more the residual must be lower. Severity is judged on people first, so a hazard that can injure is not reduced only because it has rarely happened. Critical and High risks need senior attention and a dated plan, Medium risks need routine controls with a named owner, and Low risks are accepted and monitored. Engineers, operators and the safety lead should challenge each rating at review, and any hazard whose indicator reaches its threshold is rescored early.

Likelihood, impact and rating bands

Likelihood

  • 5 Almost certain: Expected to happen in most circumstances.
  • 4 Likely: Will probably happen in many circumstances.
  • 3 Possible: Could happen at some time.
  • 2 Unlikely: Not expected, but it could happen.
  • 1 Rare: Only in exceptional circumstances.

Impact

  • 1 Insignificant: No lasting effect. Handled within routine work.
  • 2 Minor: Small effect that is quickly corrected.
  • 3 Moderate: Noticeable effect that needs managed effort to correct.
  • 4 Major: Serious effect on people, delivery or reputation.
  • 5 Catastrophic: Severe or lasting effect that threatens the whole activity.

Bands (likelihood x impact)

  • Low (1 to 4): Accept and monitor.
  • Medium (5 to 9): Manage with routine controls.
  • High (10 to 16): Senior attention and a treatment plan.
  • Critical (17 to 25): Act first. Do not proceed until reduced.

Monitoring, escalation and review

Review this assessment every 6 months, and sooner when an indicator below reaches its threshold.

Early-warning indicators and escalation thresholds
Indicator to watchEscalate when
Repeated loss of heartbeat signal from any cell within one week.Escalate to the plant automation engineer at once, and to the operations manager if the cell is down for more than one shift.
Unknown devices or unapproved remote sessions on production network segments.Escalate to the industrial cybersecurity lead immediately, isolate the segment and inform the plant manager.
Protective stop events in one cell rising over two weeks.Escalate to the safety engineer when the count doubles, and stop the cell until the cause is verified.
Calibration drift between redundant sensors beyond the agreed band.Escalate to the quality engineer when the band is exceeded for a full shift, and hold affected product for review.
Supplier rejection rate rising on one part number over two deliveries.Escalate to the supply chain manager at the second rejection, and to the plant manager if line stoppage results.

Contingency arrangements

If a serious event occurs, such as a cyber intrusion that changes machine settings, a robot injury or a failed supplier part that stops a line, the plant manager stops the affected cell and isolates the network segment. The control engineer restores settings from verified backups and checks each machine before restart. Safety incidents follow the site emergency response plan and are reported to the relevant authority as local rules require. Customers and suppliers are told early and plainly, and a second source is called in for critical parts.

Prioritized action plan

  1. Segment control networks from office traffic and test the fallback procedure, owner plant automation engineer, within 45 days.
  2. Require multi-factor sign in and approved sessions for all remote supplier access, owner industrial cybersecurity lead, within 30 days.
  3. Verify safety scanners after every program change and rehearse rescue drills, owner safety engineer, within 30 days.
  4. Write acceptance tests into supplier contracts and qualify a second source for critical drives, owner supply chain manager, within 90 days.
  5. Map worker data fields to purposes and retention periods, owner data protection lead, within 90 days.

Conclusion

Safe and reliable connected production depends on a few habits: segmented networks, verified program changes, tested safety functions, calibrated sensors, qualified suppliers and planned maintenance backed by real checks. The highest inherent scores sit with cyber exposure and robot motion, and each has controls that bring the residual score down. Keep the register as a living record, review it on the stated cycle, and seek qualified engineering, cybersecurity and safety advice for any real plant decision.

Assumptions and limitations

Assumptions

  • Jurisdiction is not specified, so legal duties are described in general terms only.
  • Robots and machines are installed and configured by qualified integrators.
  • Analytics and remote support come from a small set of named suppliers.

Limitations

  • Scores are teaching examples and describe no real plant.
  • Engineering, cybersecurity and safety rules need specialist review by qualified people.
  • This is educational content, not engineering, safety or legal advice.

Related frameworks to study

  • Hierarchy of controls
  • Failure mode and effects analysis
  • Functional safety lifecycle concept
  • Purdue enterprise reference model for industrial networks
  • Asset management lifecycle planning

Technical Risk Assessment

China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.

For Learning Reference Only: This assessment demonstrates how risk assessment principles are applied in a practical setting, providing a useful reference for learning and understanding. Actual assessments may be adapted to suit specific site conditions and circumstances.

Keep learning

Study the subject behind this assessment.

More Technical risk assessments

Hourly Active: 35,661 Learners