vaayaa Inclusive Education
Technical risk assessment

Smart Manufacturing Systems Risk Assessment: Control Systems, Data, People and Continuity Risks

A worked example of how a small smart factory team identifies, scores and controls risks in connected machines, sensors, plant software and supplier links, from cyber exposure and data errors to skills gaps, quality drift and safety.

Updated November 2026 8 hazards assessed Review every 6 months Highest risk: Critical to Medium
See the Smart Manufacturing Systems course

Executive summary

This assessment shows how a small smart manufacturing team can find, rate and control the risks that come with connected machines, sensors, plant software and the people who run them. Eight hazards were chosen because they are plausible in a single production cell and its links to planning and suppliers. Cyber intrusion into control systems carries the highest inherent score, followed by sensor and network failure, data integrity, skills gaps, quality drift and supplier dependence. Each risk is scored before controls and again after existing and added controls. Most fall to Medium or Low once controls are in place, but injury from automated equipment stays a priority because the impact remains severe. The first actions are isolating engineering access, adding a verified isolation step before robot cell entry, restoring redundant networks and building a competence matrix. The scores are for teaching and show method, not any real plant.

Focus area
Smart manufacturing systems and industrial digital operations
Setting
Discrete manufacturing cell with networked machines, sensors, a manufacturing execution system and links to enterprise planning
Method
Five by five likelihood and impact risk register

Scope

This assessment covers a single smart manufacturing cell and its supporting systems, including connected machines, sensors, controllers, a manufacturing execution system, a process data historian, operator dashboards and links to enterprise planning. It looks at risks to strategic goals, processes, people, data, suppliers, safety, quality and continuity. Plant location, jurisdiction, product type and vendor choices are not specified, so they are treated as assumptions made for teaching only.

Context

The cell has three machining centers, two collaborative robots, a conveyor and a set of temperature, vibration and tool wear sensors. Controllers send data to a manufacturing execution system and a historian, which feed operator dashboards and weekly planning reports. Engineers maintain the software, technicians maintain the machines, and quality staff sample each batch. Components come from a small group of suppliers, and some controllers and software are proprietary. Each risk is scored before controls to show its natural level, then again after existing controls and the additional controls that should be added.

Objectives, assets and stakeholders

The objective is to run the cell safely, produce conforming parts on time, protect process data and recipes, and keep the trust of customers, the board and staff. The assets in scope are controllers, sensors, network equipment, the manufacturing execution system, the process historian, recipes and batch records, spare parts and the machines themselves. Stakeholders include operators, maintenance technicians, engineers, quality staff, planners, the plant manager, the board, suppliers and customers who rely on traceability records. Every risk has one owner role, and the operations director reviews the register with the plant manager at each quarterly steering meeting.

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: H03 H04 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: H08 Likelihood 3, impact 4, score 12, high: H06 H07
2 Unlikely Likelihood 2, impact 5, score 10, high: H05
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 Likelihood 3, impact 2, score 6, medium: H04 Likelihood 3, impact 3, score 9, medium: H07
2 Unlikely Likelihood 2, impact 2, score 4, low: H08 Likelihood 2, impact 3, score 6, medium: H01 H03 H06 Likelihood 2, impact 4, score 8, medium: H02
1 Rare Likelihood 1, impact 4, score 4, low: H05
  • 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 Unplanned stoppage from sensor or network failure 16 High 6 Medium Maintenance engineering lead
H02 Cyber intrusion into operational technology 20 Critical 8 Medium Operational technology security lead
H03 Data integrity errors in process records 12 High 6 Medium Data and systems engineer
H04 Skills gaps and reliance on a few specialists 12 High 6 Medium Plant manager
H05 Injury from automated equipment during faults or maintenance 10 High 4 Low Health and safety manager
H06 Quality escapes from undetected process drift 12 High 6 Medium Quality manager
H07 Supplier failure and vendor lock in 12 High 9 Medium Procurement lead
H08 Digital investment without clear benefits 9 Medium 4 Low Operations director
H01

Unplanned stoppage from sensor or network failure

Operational Before 16 After 6

A failed sensor, switch or wireless link stops data flow between machines and the manufacturing execution system, so the cell halts or runs without visibility until the fault is found.

Who or what is affected: Line operators, maintenance staff and customers waiting for orders

Causes

Ageing cabling, electrical noise near drives and sensors with no spares held on site.

Consequences

Lost output, late deliveries, overtime and scrap caused by restarts.

Existing controls

  • Critical machines have a manual fallback procedure.
  • Network switches are monitored by the IT team during working hours.

Control gaps

Heartbeat alerts cover the main line only, not the sub-assemblies or wireless sensors.

Additional controls

  • Prevent: Install redundant network paths and spare sensors for critical measurement points.
  • Detect: Alert on loss of heartbeat from each machine and sensor within one minute.
Likelihood 4 x impact 4 before; 2 x 3 after Owner: Maintenance engineering lead Target: Within 60 days Early warning: Repeated loss of heartbeat from the same sensor within one shift.
H02

Cyber intrusion into operational technology

Technology and data Before 20 After 8

An attacker or an infected laptop reaches control networks through remote access or a shared engineering workstation, then changes machine settings, halts equipment or steals recipes and process data.

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

Causes

Remote support, shared accounts, unpatched controllers and USB transfers of files.

Consequences

Halted production, altered settings, product defects and loss of intellectual property.

Existing controls

  • Remote access requires a named account and a time-limited approval.
  • The control network is separated from the office network by a firewall.

Control gaps

Engineering laptops are not separated from the plant network, and controller backups are not tested.

Additional controls

  • Prevent: Restrict engineering workstations to an approved list and patch them on a set schedule.
  • Respond: Keep a written procedure to isolate the cell from the network within minutes.
Likelihood 4 x impact 5 before; 2 x 4 after Owner: Operational technology security lead Target: Within 30 days Early warning: Unexpected configuration change on a controller outside an approved change window.
H03

Data integrity errors in process records

Technology and data Before 12 After 6

Time stamp, sensor calibration or tag mapping errors in the historian and dashboards lead to wrong decisions, false alarms or hidden defects that are not seen until a customer complaint arrives.

Who or what is affected: Quality engineers, planners and customers receiving traceability records

Causes

Manual tag changes, unsynchronized clocks and calibration records kept on paper.

Consequences

Wrong batch release, alarms ignored through fatigue and weak root cause analysis.

Existing controls

  • Sensors are calibrated at set intervals.
  • Dashboard values are compared with a manual reading at the start of each shift.

Control gaps

Checks run only when someone reviews a chart, not on every record written to the historian.

Additional controls

  • Detect: Run automated checks for out of range values, data gaps and clock drift.
  • Prevent: Standardize tag naming and lock mapping changes behind a recorded change request.
Likelihood 4 x impact 3 before; 2 x 3 after Owner: Data and systems engineer Target: Within 45 days Early warning: Data gaps longer than two minutes on a key process tag during a shift.
H04

Skills gaps and reliance on a few specialists

People Before 12 After 6

Few staff understand both the machines and the software, so a resignation, illness or fault leaves the cell unable to diagnose problems or change settings safely and on time.

Who or what is affected: Production team, managers and contract partners

Causes

Rapid system change, few internal trainers and reliance on experienced staff close to retirement.

Consequences

Longer faults, unsafe workarounds and dependence on costly outside help.

Existing controls

  • Machine manuals and vendor training records are kept in a shared folder.
  • A supervisor signs off each operator for a defined list of tasks.

Control gaps

The competence matrix is out of date and does not yet cover software and data roles.

Additional controls

  • Prevent: Build a competence matrix and cross train two people for each critical task.
  • Recover: Keep a tested handover pack and a list of approved external support contacts.
Likelihood 4 x impact 3 before; 3 x 2 after Owner: Plant manager Target: Within 90 days Early warning: Two or more critical tasks on the matrix held by a single person.
H05

Injury from automated equipment during faults or maintenance

Safety Before 10 After 4

Robots, conveyors and presses move unexpectedly when a fault is cleared, a guard is bypassed or energy is not isolated before a person enters the work zone.

Who or what is affected: Maintenance technicians, operators and visitors

Causes

Pressure to restart quickly, unclear fault codes and guards bypassed during setup.

Consequences

Crush or cut injuries, legal duties triggered and work stopped while the incident is reviewed.

Existing controls

  • Light curtains and guard interlocks are fitted around the robot cell.
  • Lockout tags are issued for planned maintenance work.

Control gaps

Bypass logs are kept but not reviewed, and visitors are not trained before they enter the cell.

Additional controls

  • Prevent: Require a written isolation check and a verified zero energy state before anyone enters the work zone.
  • Detect: Log every interlock bypass and review the log at each safety meeting.
Likelihood 2 x impact 5 before; 1 x 4 after Owner: Health and safety manager Target: Within 30 days Early warning: Any interlock bypass recorded during a working shift.
H06

Quality escapes from undetected process drift

Operational Before 12 After 6

Gradual drift in temperature, tool wear or material batch properties goes unnoticed by automated controls, so out of specification parts pass inspection and reach customers.

Who or what is affected: Customers, quality team and brand reputation

Causes

Tool wear, changing material lots and control limits set once and never reviewed.

Consequences

Customer returns, rework, recalls and warranty costs.

Existing controls

  • Final inspection samples each batch.
  • Control limits raise an alarm when a value leaves a fixed range.

Control gaps

Trend data is not linked to lot numbers, so affected parts cannot be traced quickly.

Additional controls

  • Detect: Trend key quality measures and alarm on runs of drift before limits are reached.
  • Respond: Quarantine every lot linked to a drift alarm until the cause is reviewed.
Likelihood 3 x impact 4 before; 2 x 3 after Owner: Quality manager Target: Within 60 days Early warning: Three consecutive readings moving in one direction without an alarm.
H07

Supplier failure and vendor lock in

Supplier Before 12 After 9

A single source supplier of controllers, sensors or software fails, changes terms or ends support, leaving the cell without parts, updates or security fixes it needs to keep running.

Who or what is affected: Maintenance, purchasing and production planning

Causes

Proprietary platforms, low volume buying and pressure to cut unit cost.

Consequences

Extended downtime, high replacement costs and systems left without security fixes.

Existing controls

  • Critical spares are listed in the inventory system.
  • Vendor contracts include a reminder before the support end date.

Control gaps

Spare stock is counted only once a year, and the second source has not been qualified.

Additional controls

  • Prevent: Qualify a second source for critical parts and write data export rights into contracts.
  • Recover: Hold a tested fallback plan for running the line under manual control.
Likelihood 3 x impact 4 before; 3 x 3 after Owner: Procurement lead Target: Within 90 days Early warning: A supplier notice of end of support or a price change for a critical item.
H08

Digital investment without clear benefits

Strategic Before 9 After 4

Connected systems are bought before goals, measures and ownership are agreed, so costs rise and the expected gains in output, quality or flexibility never appear in practice.

Who or what is affected: Board, finance team and plant staff

Causes

Vendor led sales, vague goals and projects that grow in scope without review.

Consequences

Wasted budget, stalled projects and loss of staff confidence in new systems.

Existing controls

  • Major spend needs sign off by a steering group.
  • A business case is written for each project.

Control gaps

Benefits are reported as activity counts, such as devices installed, rather than outcomes.

Additional controls

  • Prevent: Set measurable goals and a named benefits owner before each purchase.
  • Detect: Review realized benefits against the business case at each quarterly steering meeting.
Likelihood 3 x impact 3 before; 2 x 2 after Owner: Operations director Target: Within 90 days Early warning: A project milestone missed twice without a re-approved plan.

Rating method and evaluation

Each risk is rated on two five point scales. Likelihood runs from Rare to Almost certain, and impact runs from Insignificant to Catastrophic. Multiplying the two gives a score from 1 to 25, which 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 any controls are applied. Residual risk is the score after the existing controls and the additional controls are in place, and it must never be higher than the inherent score. Impact is judged on safety harm, output lost, quality escapes, data exposure and effect on customers. Critical risks need immediate action and senior sign off. High risks need a dated plan approved by the plant manager. Medium risks need routine controls with a named owner. Low risks are accepted and watched. Ratings are challenged by the people who operate and maintain the equipment, and they are reviewed whenever a monitoring indicator reaches its escalation threshold or a significant change is made to the cell.

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
Unplanned stoppages longer than 15 minutes per shift in the cell.Escalate to the plant manager after any stoppage over 30 minutes, and to the operations director if stoppages repeat within a week.
Controller configuration changes made outside an approved change window.Escalate to the operational technology security lead at once, and isolate the cell until the change is verified.
Interlock bypasses recorded during working shifts.Escalate to the health and safety manager on the same shift, with a review at the next safety meeting.
Process drift alarms that have no matching lot quarantine.Escalate to the quality manager when any drift alarm is not actioned within one shift.
Critical tasks held by only one trained person on the competence matrix.Escalate to the plant manager when a single person is the only cover for a critical task for more than two weeks.

Contingency arrangements

If a serious event occurs, such as a confirmed intrusion, a fire or injury at the cell or a supplier failure that stops the line, the plant manager stops the cell in a safe state and preserves logs and configuration backups. The operational technology security lead isolates the network and the affected controllers. The health and safety manager leads any injury or near miss response. Production moves to the manual fallback procedure where it is safe to do so, and customers are informed early and plainly of any delay.

Prioritized action plan

  1. Isolate engineering workstations and restrict remote access, owner operational technology security lead, within 30 days.
  2. Add a verified isolation check before any access to the robot cell, owner health and safety manager, within 30 days.
  3. Restore redundant network paths and spares for critical sensors, owner maintenance engineering lead, within 60 days.
  4. Automate data checks and link quality trends to lot numbers, owner quality manager, within 60 days.
  5. Build a competence matrix and cross train two people for each critical task, owner plant manager, within 90 days.

Conclusion

Smart manufacturing depends on a few steady habits: separated and monitored control networks, verified isolation before access, trained people who can cover each critical task, tested backups and data checks that run on every record. The highest scores sit with cyber exposure, sensor failure and data errors, and each has actions that bring the residual score down. Treat the register as a living record, review it on the stated cycle, and seek qualified engineering, safety and security advice for any real installation.

Assumptions and limitations

Assumptions

  • The cell uses programmable controllers, networked sensors and a manufacturing execution system that the team can configure and access.
  • Plant location, jurisdiction and product type are not specified, so legal duties are described only in general terms.
  • Staff are trained operators, technicians and engineers who use managed computers and follow written procedures.

Limitations

  • The scores are examples for learning and do not describe any real plant, vendor or product.
  • Machine safety, cyber security and quality rules vary by sector and country, so specialist review is needed.
  • This is educational content and does not replace a formal site specific assessment or licensed engineering advice.

Related frameworks to study

  • Failure mode and effects analysis
  • Hazard and operability study for process changes
  • Hierarchy of controls
  • Three lines model of risk ownership
  • Information security principles for operational technology

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.

Smart Manufacturing Systems course Read the best practices for this course

More Technical risk assessments

Hourly Active: 45,552 Learners