Intelligent Control Systems

Chapter 14
Industrial Applications, Lifecycle Decisions and Emerging Trends

Bachelor Program in Mechatronics Engineering
Intelligent Control Systems   •   Bachelor

Industrial Applications, Lifecycle Decisions and Emerging Trends

Introduction

Intelligent control systems combine sensing, computation, communication, decision-making and actuation to achieve control objectives in environments that are uncertain, changing or only partially modelled. Unlike conventional feedback controllers designed around a fixed mathematical model, intelligent controllers may use fuzzy logic, neural networks, evolutionary optimisation, reinforcement learning, anomaly detection or combinations of these methods.

The industrial value of intelligent control is not established by algorithmic sophistication alone. A system is useful when it improves measurable outcomes such as safety, quality, energy efficiency, availability, throughput, adaptability or total cost of ownership. Deployment therefore requires an engineering lifecycle perspective: define the operational problem, select an appropriate control architecture, validate it, assess risks, integrate it with people and existing systems, monitor performance and retire or update it responsibly.

This chapter examines applications in robotics, autonomous vehicles, manufacturing, process industries, energy systems and smart buildings. It also develops a framework for key performance indicators (KPIs), reliability, maintainability, lifecycle cost, risk and return on investment (ROI). The final sections consider human–machine collaboration, federated learning, trustworthy autonomy and AI-enabled digital transformation.

Learning objectives

By the end of this chapter, a student should be able to:

  1. Explain how intelligent control is applied in major industrial sectors.
  2. Select operational, technical and business KPIs for an intelligent control project.
  3. Analyse availability, maintainability, lifecycle cost, risk and ROI.
  4. Evaluate human–machine collaboration and trustworthy autonomy.
  5. Describe federated learning and its industrial advantages and limitations.
  6. Recommend a staged deployment strategy for an AI-enabled control system.

1. From algorithm to industrial system

An industrial intelligent control system normally contains six interacting layers:

LayerMain functionTypical technologies
Physical processProduces motion, material flow or energy conversionMotors, valves, robots, conveyors
SensingObserves state and environmentEncoders, cameras, force sensors, temperature sensors
ControlConverts observations into actionsPID, model predictive control, fuzzy logic, neural control
SupervisionCoordinates tasks and detects abnormal conditionsSCADA, MES, fleet management
Data and communicationStores, transports and contextualises dataIndustrial Ethernet, OPC UA, historians, edge computing
GovernanceDefines safety, security, accountability and change controlRisk assessments, access control, audit trails

The control objective may be expressed as tracking a reference, rejecting disturbances, optimising an economic objective or maintaining operation within safe constraints. A simple feedback relation is represented by u(t) = π(y(t), r(t), z(t)), where u(t) is the control action, y(t) is the measured output, r(t) is the desired reference and z(t) represents additional information such as operating mode or detected faults. The policy π may be a conventional controller, a rule base or a learned model.

Intelligence is valuable particularly when the process is nonlinear, uncertain, multivariable, difficult to model, or subject to changing operating conditions. It is not automatically beneficial when a simple, verified controller already satisfies the requirements. In safety-critical systems, a complex AI component may be restricted to advisory or supervisory duties while a deterministic safety layer retains authority to stop the plant.

2. Industrial applications

2.1 Robotics and flexible automation

Industrial robots traditionally execute programmed trajectories. Intelligent control extends this capability through vision-guided localisation, force control, collision prediction, adaptive grasping and human-aware motion planning. A robot assembling variable-position components, for example, can estimate the component pose from a camera and modify its trajectory rather than relying on a fixed fixture.

Typical KPIs include cycle time, placement error, first-pass yield, collision rate, mean time between failures (MTBF), energy per part and successful task completion probability. The design must also address latency, calibration drift, lighting variation, payload changes and safe separation from workers.

Collaborative robots illustrate the importance of layered control. A high-level planner may use machine learning to select a grasp, while low-level torque limits, speed limits, protective stops and workspace monitoring remain governed by validated safety functions. The learned component should not be allowed to bypass a safety-rated stop mechanism.

2.2 Autonomous vehicles and mobile robots

Autonomous vehicles combine localisation, perception, prediction, planning and control. A mobile robot in a warehouse may use lidar and cameras to build a map, estimate its position, plan a collision-free route and regulate wheel speed. An autonomous road vehicle must additionally interpret complex traffic behaviour, weather, road markings and legal constraints.

Performance cannot be represented by navigation accuracy alone. Relevant measures include intervention frequency, near-miss rate, localisation error, route completion, energy consumption, passenger comfort, false-positive and false-negative perception rates, and performance under degraded sensing. Testing should include normal operation, edge cases, sensor failures, communication loss and adversarial conditions.

A useful engineering principle is graceful degradation. If a camera becomes unavailable, the system should detect the loss, reduce speed or enter a minimal-risk condition rather than silently continuing with an invalid assumption.

2.3 Smart manufacturing

In manufacturing, intelligent control supports adaptive scheduling, predictive maintenance, visual inspection, process optimisation and quality prediction. A production line can combine machine data, product genealogy and maintenance records to predict a defect before it becomes systematic.

Overall equipment effectiveness (OEE) is a widely used composite indicator:

OEE = Availability × Performance × Quality

Availability, performance and quality are expressed as fractions between 0 and 1. Availability commonly equals operating time divided by planned production time; performance compares actual production rate with ideal production rate; quality is the fraction of good units among total units. The definitions must be agreed locally because planned stops, minor stoppages and rework can be treated differently. OEE is useful for diagnosis but should not be used as the sole objective: maximising speed may increase defects or equipment wear.

Digital twins can connect a physical asset with a computational representation containing geometry, state estimates, historical data and predictive models. The twin is valuable only when its data are sufficiently accurate, timely and contextualised. A visually impressive dashboard without reliable measurement does not constitute an effective digital twin.

2.4 Process control

Chemical, pharmaceutical, food and water processes often involve continuous dynamics, constraints and safety hazards. Intelligent methods can assist with soft sensors, fault diagnosis, inferential quality measurement and optimisation of set points. For example, a neural soft sensor may estimate product concentration from temperature, pressure and flow measurements when laboratory analysis is slow.

The intelligent layer should respect hard constraints such as maximum pressure, temperature limits, allowable composition and actuator saturation. Model predictive control (MPC) is particularly suitable because it predicts future behaviour and optimises control actions subject to constraints. Machine learning can enhance the prediction model, but the resulting controller must be tested across the operating envelope and protected against extrapolation.

2.5 Energy systems

Intelligent control is used for demand response, renewable-energy integration, battery management, microgrids and building energy optimisation. Forecasting solar generation and demand allows a supervisory controller to schedule storage and flexible loads. At the local level, a battery controller balances state of charge, power limits, temperature and degradation.

For a battery with usable energy capacity Emax, the state of charge is approximately:

SOC(t) = E(t) / Emax

where E(t) is stored usable energy and both quantities are measured in the same energy unit, commonly kWh. Practical battery models must include charging and discharging efficiency, self-discharge, temperature and capacity degradation; therefore the simple relationship is an approximation, not a complete electrochemical model.

Energy KPIs include kWh per product, peak demand, renewable-energy utilisation, comfort violations, battery degradation and cost per unit of delivered energy. Optimisation should consider both immediate energy savings and long-term asset degradation.

2.6 Smart buildings

Smart-building control integrates heating, ventilation and air conditioning (HVAC), lighting, access systems, occupancy sensing and energy storage. Intelligent occupancy estimation can reduce conditioning in unoccupied zones while maintaining thermal comfort when people arrive.

Important constraints include indoor-air quality, humidity, thermal comfort, cybersecurity and privacy. A controller that saves energy by reducing ventilation below acceptable air-quality levels is not a successful solution. Multi-objective control is therefore required, balancing energy, comfort, health, equipment life and cost.

3. KPIs and evidence-based evaluation

A deployment should begin with a baseline period and a clearly defined measurement plan. KPIs should be divided into four groups:

GroupExamples
OperationalThroughput, cycle time, yield, downtime, delivery reliability
TechnicalTracking error, latency, false alarms, intervention rate, constraint violations
EconomicEnergy cost, labour cost, maintenance cost, avoided loss, ROI
Safety and socialIncidents, near misses, ergonomic load, privacy events, operator acceptance

A KPI requires a definition, measurement method, sampling interval, owner, target and acceptable uncertainty. Comparing a new controller with historical data is weak if demand, product mix or staffing have changed. Better evidence may involve an A/B trial, a stepped deployment across similar assets, or a before-and-after study adjusted for operating conditions.

A confusion matrix is useful for a fault-detection system. Precision is the proportion of declared faults that are genuine; recall is the proportion of genuine faults detected. High recall with very low precision may overwhelm operators with false alarms. The appropriate trade-off depends on the cost of missed failures and unnecessary interventions.

4. Reliability, maintainability and lifecycle decisions

Reliability is the probability that an item performs its required function for a specified time under stated conditions. For a constant failure rate λ, the exponential reliability model is:

R(t) = e^(−λt)

Here t is operating time and λ has units of inverse time. The model assumes a constant hazard rate and is often reasonable during the useful-life period, but it does not describe infant mortality or wear-out without modification.

Mean time between failures is often approximated by:

MTBF = operating time / number of failures

Mean time to repair (MTTR) is the average active restoration time. For a repairable system with negligible waiting and logistics delays, steady-state inherent availability is:

A = MTBF / (MTBF + MTTR)

Availability is dimensionless. In practice, achieved availability may be lower because it includes spare-part delays, diagnosis, scheduling, software recovery and administrative time.

Maintainability improves when components are accessible, faults are diagnosable, software is modular, calibration is automated and replacement procedures are standardised. Intelligent systems introduce additional maintenance needs: data drift monitoring, model validation, cybersecurity patching, sensor recalibration and retraining governance.

Lifecycle cost includes acquisition, integration, training, operation, maintenance, downtime, upgrades, compliance and disposal. A simplified discounted lifecycle cost is:

LCC = C₀ + ∑[Ct / (1 + r)t]

where C₀ is initial cost, Ct is cost in period t, r is the discount rate per period and the summation covers the system life. All costs must use the same currency basis and time period. Benefits can be treated similarly when calculating net present value (NPV):

NPV = ∑[(Bt − Ct) / (1 + r)t] − C₀

A positive NPV indicates that discounted benefits exceed discounted costs under the stated assumptions. Simple ROI is often reported as:

ROI = (total benefits − total costs) / total costs × 100%

ROI is easy to communicate but does not represent timing as rigorously as NPV. Both should be accompanied by sensitivity analysis for uncertain demand, savings, failure rates and implementation time.

5. Risk, safety and trustworthy autonomy

Risk is commonly analysed as a combination of the severity of harm and the likelihood of occurrence. A qualitative risk matrix may classify hazards as tolerable, requiring mitigation, or intolerable. For intelligent control, hazard analysis should consider incorrect predictions, distribution shift, sensor faults, cyberattack, communication loss, operator misunderstanding and unsafe interactions between subsystems.

Trustworthy autonomy has several dimensions:

  • Safety: the system avoids unacceptable hazards and reaches a safe state when necessary.
  • Reliability: performance remains dependable under specified conditions.
  • Explainability: operators can understand relevant reasons, limitations or confidence levels.
  • Security: data, models and control channels resist unauthorised manipulation.
  • Privacy: personal and operational data are collected and used proportionately.
  • Accountability: responsibilities, decisions and changes are traceable.
  • Fairness: decisions do not create unjustified differential treatment.

Explainability does not mean that every neural-network internal calculation can be translated into a simple causal story. In engineering practice, useful assurance may instead include confidence estimates, input validity checks, operating-envelope monitors, counterfactual tests, audit logs and independent safety interlocks.

6. Human–machine collaboration

Automation changes work rather than simply removing it. Operators may move from direct manipulation to supervision, exception handling, diagnosis and process improvement. Poorly designed supervisory systems create automation bias, alarm fatigue and skill degradation.

Effective collaboration requires an explicit allocation of authority. The machine may act autonomously within a validated envelope, request confirmation for high-consequence actions and hand over control when uncertainty exceeds a threshold. The operator interface should communicate system state, confidence, intended action, constraints and the reason for a recommendation without producing unnecessary alarms.

Training should include normal operation, abnormal events, manual takeover, model limitations and recovery from degraded modes. Organisations should involve operators in requirements definition because tacit process knowledge often reveals failure modes absent from historical data.

7. Federated learning in industrial systems

Federated learning trains a shared model across multiple sites without routinely transferring raw local data. A central coordinator sends a model to participating sites; each site trains locally and returns model updates; the coordinator aggregates updates and distributes the improved model.

For site models wk trained using local data sizes nk, a basic weighted aggregation is:

w = ∑(nk / ∑nj) wk

This approach is often called federated averaging. It assumes that updates can be communicated securely and that the aggregation method is appropriate. Industrial sites may have non-identical machines, sensors and operating conditions, so data are usually non-independent and non-identically distributed. This can reduce convergence and create a model that performs well at large sites but poorly at smaller or unusual sites.

Federated learning reduces raw-data movement but does not guarantee privacy. Model updates may leak information, and malicious participants may poison training. Secure aggregation, access control, update validation, differential privacy and rollback mechanisms may be required. Local evaluation and site-specific calibration remain essential.

8. AI-enabled digital transformation

Digital transformation is organisational as well as technical. A successful programme connects operational technology, information technology, data governance, workforce capability and business strategy. Common stages are:

  1. Instrument: establish reliable sensors, timestamps and asset identity.
  2. Connect: provide secure and resilient data exchange.
  3. Contextualise: link measurements to products, recipes, work orders and operating modes.
  4. Analyse: detect patterns, predict failures or optimise decisions.
  5. Assist: give operators recommendations with evidence and override capability.
  6. Control: automate bounded decisions after validation.
  7. Scale and govern: standardise deployment, monitor drift and manage retirement.

Many programmes fail because they begin with an attractive AI method rather than a measurable operational problem. A small pilot should have a control group or baseline, a defined owner, a rollback plan and criteria for scale-up. Model performance must be monitored after deployment because process conditions, products, sensors and personnel change.

9. Illustrative case: intelligent predictive maintenance in a packaging line

Background

A packaging line contains a conveyor, filling machine, capper and label applicator. Unplanned stoppages cause production loss. The plant has vibration, motor-current and temperature sensors, but maintenance is mainly calendar-based.

Problem

The plant proposes a machine-learning fault detector. Historical records contain 1,200 operating hours and 24 recorded failures. The pilot team must determine whether the system should be deployed and how its value should be assessed.

Analysis

The team first defines a failure event, removes periods of planned shutdown, synchronises sensor clocks and labels the data using maintenance records. It discovers that many “failure” labels actually represent different causes. The labels are therefore separated into bearing faults, belt misalignment and electrical trips. This improves engineering usefulness even though it reduces the apparent size of the dataset.

A baseline consisting of threshold alarms is compared with the proposed model. Evaluation uses time-ordered validation rather than random splitting, because random splitting can allow information from future operating conditions to enter the training set. Metrics include recall, precision, false alarms per shift, warning time and avoided downtime.

Approach and solution

The model operates as an advisory system for three months. It does not directly stop the line. Alerts are ranked by confidence and linked to sensor trends and inspection instructions. A deterministic interlock remains responsible for immediate protection. Maintenance staff confirm or reject alerts, creating better labels for later improvement.

The deployment also includes a drift monitor. If sensor distributions or error rates change beyond defined limits, the model is reviewed and may be rolled back to the baseline alarm strategy.

Economic assessment

Suppose the pilot costs $36,000. During the evaluation year it avoids $52,000 of downtime and $8,000 of secondary damage. Operating and monitoring costs are $12,000. The simple ROI is:

ROI = (52,000 + 8,000 − 36,000 − 12,000) / (36,000 + 12,000) × 100%
= 12,000 / 48,000 × 100%
= 25%

This result is conditional on the estimated avoided losses. The decision should also consider uncertainty, recurring costs, cybersecurity, staff acceptance and whether the pilot transfers to other lines.

Outcome and learning points

The appropriate outcome is not merely “the model achieved high accuracy.” The project establishes whether warnings arrive early enough to support maintenance, whether false alarms are manageable and whether savings exceed lifecycle costs. Key lessons are to improve data quality before modelling, preserve human accountability, retain a safe fallback and evaluate value at the system level.

10. Challenges and limitations

Intelligent control faces several persistent limitations:

  • Data quality: missing, biased, poorly labelled or non-representative data produce unreliable decisions.
  • Distribution shift: a model trained on one product, season or machine may fail under new conditions.
  • Closed-loop risk: errors affect the process, which then changes future data; offline accuracy may not predict control performance.
  • Verification difficulty: learned policies are harder to exhaustively verify than finite-state logic.
  • Integration complexity: legacy controllers, proprietary protocols and inconsistent asset models impede deployment.
  • Cybersecurity exposure: connected sensors and models enlarge the attack surface.
  • Economic uncertainty: benefits may depend on adoption, maintenance practice and production volume.
  • Workforce effects: poorly managed automation can reduce trust, increase workload or eliminate valuable skills.

These limitations favour staged deployment, conservative operating envelopes, independent validation and continuous monitoring rather than one-time commissioning.

11. Best-practice deployment framework

A disciplined project should:

  1. Define the problem, affected stakeholders, constraints and baseline.
  2. Determine whether intelligent control is necessary or whether a simpler method is adequate.
  3. Specify safety, performance, data, cybersecurity and human-factors requirements.
  4. Build a representative dataset and document provenance and limitations.
  5. Test in simulation, replay and hardware-in-the-loop before live operation.
  6. Deploy first in monitoring or advisory mode.
  7. Use independent acceptance tests and a documented rollback path.
  8. Measure technical, operational, economic and human outcomes.
  9. Monitor drift, incidents, interventions, maintenance and security events.
  10. Review the system periodically and retire it when its assumptions or value no longer hold.

Chapter Summary

Industrial intelligent control is a lifecycle engineering activity, not merely an exercise in selecting an AI algorithm. Robotics, autonomous vehicles, manufacturing, process control, energy and smart buildings benefit from adaptive perception, prediction and optimisation, but each application requires appropriate constraints and fallback behaviour. OEE, precision, recall, availability, MTBF, MTTR, lifecycle cost, NPV and ROI provide complementary evidence for decisions. Reliability and maintainability must include sensors, software, data pipelines and model governance. Trustworthy autonomy requires safety, security, privacy, accountability and understandable system limitations. Human–machine collaboration works best when authority, handover and override conditions are explicit. Federated learning can reduce raw-data sharing but introduces challenges involving non-identical data, privacy and model poisoning. A staged, measurable and reversible deployment strategy is central to responsible AI-enabled digital transformation.

Key Terms

Intelligent control: Control that uses computational methods to reason, learn, adapt or optimise under uncertainty.

KPI: A defined measure used to evaluate performance against an objective.

OEE: Product of availability, performance and quality for a production asset.

Digital twin: A computational representation linked to a physical asset or process.

Soft sensor: An inferred measurement calculated from other measurements and a model.

Model predictive control: Control that predicts future behaviour and optimises actions subject to constraints.

MTBF: Mean operating time between failures of a repairable item.

MTTR: Mean active time required to restore a failed item.

Availability: Probability or fraction of time that an asset is able to perform its function.

Lifecycle cost: Total discounted cost over acquisition, operation, maintenance and disposal.

NPV: Discounted value of future benefits minus costs and initial investment.

ROI: Return relative to invested cost, commonly expressed as a percentage.

Distribution shift: Change in the relationship or distribution between deployment data and training data.

Trustworthy autonomy: Autonomous operation satisfying requirements for safety, reliability, security, accountability and related values.

Automation bias: Excessive reliance on an automated recommendation despite contrary evidence.

Federated learning: Collaborative model training in which data remain at participating sites.

Concept drift: Change over time in the process relationship that a model represents.

Graceful degradation: Controlled reduction of capability when faults or uncertainty occur.

Digital transformation: Organisational and technical change enabled by connected digital systems.

Review Questions

Short Answer Questions

  1. Why should an intelligent controller retain a deterministic safety layer in many industrial applications?
  2. Define MTBF and MTTR and explain their relationship to availability.
  3. What are the three components of OEE?
  4. State two advantages and two limitations of federated learning.
  5. Why is a baseline necessary before evaluating an intelligent control deployment?

Long Answer Questions

  1. Explain the application of intelligent control in robotics, including perception, force control, safety and performance measurement.
  2. Discuss how lifecycle cost, NPV and ROI support different industrial investment decisions.
  3. Describe a trustworthy-autonomy framework for an autonomous mobile robot operating near people.
  4. Analyse the role of human operators in an AI-enabled process-control plant.
  5. Explain a staged digital-transformation pathway from instrumentation to bounded autonomous control.

Analytical / Application Questions

  1. A system has an MTBF of 900 h and an MTTR of 6 h. Calculate its inherent availability, state the assumptions, and explain why achieved availability may be lower.
  2. A factory pilot costs $50,000, produces $70,000 in avoided losses and requires $15,000 in operating cost. Calculate simple ROI and identify two uncertainties that should be tested before scale-up.
  3. Design a KPI and risk-monitoring plan for an intelligent HVAC controller that optimises energy while maintaining indoor-air quality and occupant comfort.

Multiple Choice Questions with Answers

Question 1

Which KPI is calculated as availability × performance × quality?

A. MTBF

B. OEE

C. NPV

D. Precision

Correct Answer: B. OEE

Question 2

Under the constant-failure-rate assumption, which expression represents reliability?

A. R(t) = 1 − λt

B. R(t) = λ/t

C. R(t) = e^(−λt)

D. R(t) = MTTR/MTBF

Correct Answer: C. R(t) = e^(−λt)

Question 3

A system has MTBF = 900 h and MTTR = 6 h. Its inherent availability is closest to:

A. 0.667

B. 0.900

C. 0.993

D. 1.006

Correct Answer: C. 0.993

Question 4

What is the main characteristic of federated learning?

A. All raw data must be uploaded to a central server

B. Models are trained only without sensors

C. Participating sites train locally and share model updates

D. It eliminates the need for cybersecurity

Correct Answer: C. Participating sites train locally and share model updates

Question 5

Which practice best supports graceful degradation in an autonomous vehicle?

A. Ignoring a failed camera

B. Continuing at full speed with missing sensor data

C. Reducing capability or entering a minimal-risk condition

D. Disabling all diagnostic messages

Correct Answer: C. Reducing capability or entering a minimal-risk condition

Question 6

Why is time-ordered validation important for predictive maintenance data?

A. It guarantees perfect recall

B. It prevents future information from improperly entering training

C. It removes the need for labels

D. It increases the number of physical sensors

Correct Answer: B. It prevents future information from improperly entering training

Question 7

Which measure is most directly associated with false alarms in a fault detector?

A. Precision

B. MTBF

C. Energy capacity

D. Cycle time

Correct Answer: A. Precision

Question 8

A project has total benefits of $60,000 and total costs of $48,000. Its simple ROI is:

A. 12.0%

B. 20.0%

C. 25.0%

D. 80.0%

Correct Answer: C. 25.0%

Question 9

Which statement about NPV is correct?

A. It ignores the timing of cash flows

B. It discounts future net cash flows and subtracts initial investment

C. It is always identical to simple ROI

D. It can only be used for safety metrics

Correct Answer: B. It discounts future net cash flows and subtracts initial investment

Question 10

Which is an appropriate role for a human operator in a trustworthy intelligent-control system?

A. Override and handover decisions defined by validated procedures

B. Accept every automated recommendation without review

C. Disable all safety interlocks during abnormal operation

D. Change the model directly during production without records

Correct Answer: A. Override and handover decisions defined by validated procedures

Intelligent Control Systems
Chapter 14 of 14