Prof. Dr. Larry AdamsAcademic, Author & Researcher
The IEEE Series: AI, Machine Learning & Data Science · Book 6

Intelligent Automation, Robotics and Control Systems

Intended audience: Engineering students and technical professionals

Dr. Lance Adams and Prof. Dr. Larry Adams

Free to read online. For a copy of this book, or to quote, highlight or reproduce any part of it, please request permission through the contact page beforehand.

Editorial and publication note

This is a proposed educational series. IEEE-style technical writing and citations do not imply IEEE endorsement, publication, accreditation, certification, or affiliation. Any standard, designation, author credential, publication detail, or institutional relationship must be verified before publication. These Word files are expanded educational drafts and chapter-development manuscripts for editorial review; they are not represented as final peer-reviewed or publication-ready books.

The proposed series title is descriptive only. Do not use IEEE logos or imply IEEE affiliation without authorisation. Any references to standards should be checked in the official IEEE Standards Association catalogue and used only within their stated scope.

About this book

Connects workflow automation, sensing, actuators, robotics, feedback control, optimisation, predictive maintenance, testing, and safety.

Who should use this book

This volume is designed for engineering students and technical professionals. Instructors should adapt pacing, depth, tools, and examples to learner needs and local curriculum requirements.

Learning outcomes

  • Explain the main concepts and vocabulary introduced throughout the volume.
  • Apply a structured method to a relevant practical problem.
  • Interpret evidence, identify limitations, and communicate results clearly.
  • Consider privacy, fairness, safety, security, and human oversight where relevant.

How to use this book

Read the chapter explanation, complete the activity, answer the review questions, and keep a learning journal recording assumptions, decisions, mistakes, and improvements. For technical work, save code, data dictionaries, test results, and software-version details.

Table of contents

  • Chapter 1: Fundamentals of Automation
  • Chapter 2: Rule-Based and Event-Driven Systems
  • Chapter 3: Workflow Automation and Process Mapping
  • Chapter 4: Sensors, Actuators, and Embedded Systems
  • Chapter 5: Robotics and Intelligent Agents
  • Chapter 6: Feedback Loops and Control Theory
  • Chapter 7: Optimisation and Scheduling
  • Chapter 8: Machine Learning in Automation
  • Chapter 9: Computer Vision for Industrial Applications
  • Chapter 10: Human–Robot Interaction
  • Chapter 11: Fault Detection and Predictive Maintenance
  • Chapter 12: Safety, Reliability, and Human Oversight
  • Chapter 13: Testing Automated Workflows
  • Chapter 14: Integrated Automation Project

Chapter 1: Fundamentals of Automation

Learning outcomes

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

  • Explain the central concepts introduced in fundamentals of automation.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Automation uses technology to execute defined tasks with reduced repetitive human intervention. Distinguish fixed, programmable, and adaptive automation and assess whether the task is stable enough to automate.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Map a process and identify inputs, outputs, exceptions, and risks.

Chapter review

  • What is the main idea in 'Fundamentals of Automation'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 2: Rule-Based and Event-Driven Systems

Learning outcomes

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

  • Explain the central concepts introduced in rule-based and event-driven systems.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Rule-based systems trigger actions when conditions are met; event-driven systems respond to messages or changes. Conflicting rules, repeated events, and unexpected states require explicit handling.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Specify rules for a fictional alerting workflow and test overlapping conditions.

Chapter review

  • What is the main idea in 'Rule-Based and Event-Driven Systems'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 3: Workflow Automation and Process Mapping

Learning outcomes

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

  • Explain the central concepts introduced in workflow automation and process mapping.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Process maps make handoffs, delays, decision points, and exceptions visible. Automating a flawed process can make errors faster, so simplify and validate the process first.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Create a current-state and proposed future-state process map.

Chapter review

  • What is the main idea in 'Workflow Automation and Process Mapping'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 4: Sensors, Actuators, and Embedded Systems

Learning outcomes

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

  • Explain the central concepts introduced in sensors, actuators, and embedded systems.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Sensors measure physical variables; actuators create physical changes; embedded controllers coordinate operations. Calibration, sampling, noise, latency, and operating limits affect reliability.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Design a block diagram for a temperature-monitoring system and list likely sensor errors.

Chapter review

  • What is the main idea in 'Sensors, Actuators, and Embedded Systems'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 5: Robotics and Intelligent Agents

Learning outcomes

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

  • Explain the central concepts introduced in robotics and intelligent agents.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Robots combine sensing, computation, actuation, and control. Their design depends on task, environment, precision, speed, energy, and safety constraints. Intelligent behaviour does not remove the need for physical safeguards.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Compare a warehouse mobile robot and an industrial arm by environment, sensors, and safety needs.

Chapter review

  • What is the main idea in 'Robotics and Intelligent Agents'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 6: Feedback Loops and Control Theory

Learning outcomes

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

  • Explain the central concepts introduced in feedback loops and control theory.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Feedback compares measured output with a desired setpoint and adjusts control actions. Stability, delay, overshoot, disturbances, and sensor quality affect performance.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Draw a feedback loop and explain how a delayed sensor could affect control.

Chapter review

  • What is the main idea in 'Feedback Loops and Control Theory'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 7: Optimisation and Scheduling

Learning outcomes

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

  • Explain the central concepts introduced in optimisation and scheduling.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Optimisation selects among feasible alternatives under an objective and constraints. Scheduling problems balance capacity, deadlines, dependencies, and resource availability; a mathematically optimal result may still be operationally unsuitable.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Formulate a simple scheduling problem with an objective and three constraints.

Chapter review

  • What is the main idea in 'Optimisation and Scheduling'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 8: Machine Learning in Automation

Learning outcomes

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

  • Explain the central concepts introduced in machine learning in automation.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Machine learning can classify defects, forecast demand, or detect anomalies, but it introduces uncertainty and data dependency. Safety-critical decisions need robust validation and fallback behaviour.

Worked example and application

Worked example: imagine a small team considering this concept for a clearly scoped, low-risk task. First define the intended outcome and inputs; then choose a simple baseline, document assumptions, test representative examples, inspect errors, and explain when the method should not be used. Compare the result with a human-reviewed alternative before proposing deployment.

Practical activity

Propose where ML could assist a process and where deterministic safeguards remain necessary.

Chapter review

  • What is the main idea in 'Machine Learning in Automation'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 9: Computer Vision for Industrial Applications

Learning outcomes

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

  • Explain the central concepts introduced in computer vision for industrial applications.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Computer vision extracts information from images for inspection, counting, localisation, or guidance. Lighting, camera position, domain shift, and false detections affect performance.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Create a test plan for a visual defect detector, including false-positive and false-negative consequences.

Chapter review

  • What is the main idea in 'Computer Vision for Industrial Applications'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 10: Human–Robot Interaction

Learning outcomes

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

  • Explain the central concepts introduced in human–robot interaction.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

People need predictable robot behaviour, understandable status, safe separation, accessible controls, and clear escalation paths. Design should account for training and differences in human capabilities.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Draft a user-interface checklist for an operator supervising an automated cell.

Chapter review

  • What is the main idea in 'Human–Robot Interaction'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 11: Fault Detection and Predictive Maintenance

Learning outcomes

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

  • Explain the central concepts introduced in fault detection and predictive maintenance.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Fault detection identifies abnormal conditions; predictive maintenance estimates risk or remaining useful life. Sensor drift, rare failures, and imbalanced data complicate evaluation.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Design an anomaly-monitoring plan and specify how alerts will be verified.

Chapter review

  • What is the main idea in 'Fault Detection and Predictive Maintenance'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 12: Safety, Reliability, and Human Oversight

Learning outcomes

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

  • Explain the central concepts introduced in safety, reliability, and human oversight.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Safety analysis identifies hazards, severity, likelihood, and controls. Fail-safe states, emergency stops, interlocks, inspection, and human oversight must match the context and applicable requirements.

Worked example and application

Worked example: list the system's users, affected people, assets, likely failure modes, and potential consequences. Select preventive and detective controls, assign an accountable owner, and record the residual risk that remains after controls.

Practical activity

Prepare a preliminary hazard log for a fictional automated workflow.

Chapter review

  • What is the main idea in 'Safety, Reliability, and Human Oversight'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 13: Testing Automated Workflows

Learning outcomes

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

  • Explain the central concepts introduced in testing automated workflows.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

Test normal cases, edge cases, interruptions, retries, network loss, and recovery. Log events and make operations idempotent where repeated execution could cause duplicate effects.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Create a test matrix for a workflow that transfers records between systems.

Chapter review

  • What is the main idea in 'Testing Automated Workflows'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Chapter 14: Integrated Automation Project

Learning outcomes

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

  • Explain the central concepts introduced in integrated automation project.
  • Apply the ideas to a clearly defined example or practical task.
  • Identify at least one limitation, assumption, or responsible-use consideration.

Core explanation

An automation proposal should specify architecture, sensors or data sources, logic, exception handling, human review, test evidence, and maintenance.

Worked example and application

Worked example: define a real-world task, list the inputs and constraints, sketch the steps or system components, and test the proposed solution with at least one ordinary case and one edge case. Record the outcome and what you would improve.

Practical activity

Design an automation workflow with inputs, outputs, error handling, safety checks, and human escalation.

Chapter review

  • What is the main idea in 'Integrated Automation Project'?
  • Which assumptions or data requirements matter most in this topic?
  • What could cause the approach to fail or produce a misleading result?
  • How would you explain the result or limitation to a non-specialist?

Key takeaways

  • Start with a clear question, objective, or system requirement.
  • Document inputs, assumptions, methods, and limitations.
  • Test the approach with relevant examples and review the consequences of errors.

Capstone project

Design an automation workflow with documented inputs, outputs, error handling, safety checks, test evidence, and human escalation. Include a process map, risk log, monitoring plan, and maintenance approach.

Suggested project deliverables

  • A short problem statement and intended audience.
  • A description of data, inputs, assumptions, tools, and method.
  • Evidence of testing, analysis, or evaluation appropriate to the project.
  • A clear explanation of results, limitations, and foreseeable risks.
  • A final report or presentation and a reflection on possible improvements.

Assessment guidance

Assess process analysis, system design, control reasoning, test coverage, safety awareness, and whether human intervention is defined for foreseeable failures.

Glossary

Actuator: A component that produces physical action in response to a control signal.

Feedback: Information about system output used to adjust subsequent action.

Setpoint: The desired target value for a controlled variable.

Interlock: A safeguard that prevents an action unless specified conditions are met.

Predictive maintenance: Maintenance planning informed by observed condition or predicted failure risk.

Responsible practice checklist

  • Use data and materials only when their source and permitted use are understood.
  • Avoid exposing personal, confidential, or credential information.
  • Document assumptions, missing information, and important limitations.
  • Test ordinary cases, boundary cases, and foreseeable failure conditions.
  • Use human review where errors could materially affect people, safety, rights, or resources.
  • Do not claim that a system is fair, safe, secure, compliant, or reliable without appropriate evidence.

References and further reading

The source material supplied for this project does not provide a complete, volume-specific bibliography. Before publication, add verified primary sources, textbooks, official documentation, and standards applicable to this volume. Confirm exact titles, editions, publication dates, URLs, licences, and access dates. Do not cite a standard as evidence of conformity unless the required assessment has actually been performed.

For IEEE-style technical manuscripts, use numbered citations in order of first appearance when required by the target venue, and verify the venue's official author instructions.