Chapter 12
Smart Manufacturing, IIoT and Digital Twins
Bachelors Program in Machine Technology
Advanced Manufacturing Systems
•
Bachelor
Smart Manufacturing, IIoT and Digital Twins
Introduction and Context
Manufacturing systems are increasingly connected, data-driven, adaptive, and capable of making decisions with limited human intervention. This transformation is commonly associated with Industry 4.0, the fourth industrial revolution. Whereas earlier industrial revolutions introduced mechanization, mass production, and computer-based automation, Industry 4.0 integrates physical production assets with software, communication networks, analytics, and intelligent decision-making.
Smart manufacturing is the coordinated use of machines, sensors, industrial networks, software, data analytics, artificial intelligence, and human expertise to improve manufacturing performance. Its purpose is not simply to install more technology. The objective is to create a production system that can observe its condition, understand operational events, predict likely outcomes, and respond appropriately.
The Industrial Internet of Things (IIoT) is a major enabling technology. It connects industrial equipment, products, tools, energy systems, and enterprise applications so that data can be collected and exchanged across the product lifecycle. Digital twins extend this idea by maintaining a digital representation of a physical asset, process, or system and synchronizing it with physical observations.
For machine-technology professionals, these concepts are important because modern machining centers, robots, inspection equipment, additive-manufacturing systems, and material-handling equipment increasingly operate as parts of integrated cyber-physical production systems rather than as isolated machines.
Learning Objectives
After completing this chapter, the learner should be able to:
Explain the principles and architecture of Industry 4.0.
Describe cyber-physical production systems and IIoT communication layers.
Distinguish sensors, actuators, controllers, gateways, edge platforms, and cloud services.
Explain interoperability, industrial data models, and the digital thread.
Describe digital twins across design, production, operation, and maintenance.
Adaptability: the system adjusts settings, schedules, or workflows in response to conditions.
Human collaboration: operators and engineers remain responsible for supervision, judgment, and improvement.
A conventional automated machine may execute a fixed numerical-control program. A smart machine additionally reports spindle load, vibration, tool identity, energy consumption, alarms, and quality information. A higher-level system can compare these data with production plans, detect abnormal behavior, recommend corrective action, and record the result in a traceable production history.
Industry 4.0 does not eliminate automation engineering. Instead, it adds communication, information modeling, analytics, and lifecycle integration to existing automation.
Important Terminology
Operational technology (OT): hardware and software that monitors or controls physical industrial processes.
Information technology (IT): systems used for data processing, enterprise applications, and business information.
Cyber-physical system (CPS): a system in which computational elements interact continuously with physical processes through sensing and actuation.
Cyber-physical production system (CPPS): a CPS applied to manufacturing operations.
Smart manufacturing: integrated, data-enabled manufacturing that can monitor, analyze, and improve production.
IIoT device: an industrial object capable of sensing, processing, communicating, or actuating.
Digital thread: a connected flow of lifecycle information that links requirements, design, production, service, and disposal.
Digital twin: a digital representation of a physical entity or process that is linked to the physical system through data.
2. Industry 4.0 Architecture
There is no single universally mandated Industry 4.0 architecture. In practice, organizations use layered architectures because layers separate functions and make complex systems easier to design, secure, and maintain.
A useful reference architecture contains the following layers:
Physical layer: machines, robots, fixtures, tools, materials, products, and utilities.
Sensing and actuation layer: sensors measure physical variables; actuators change process conditions.
Control layer: programmable logic controllers, CNC controllers, robot controllers, and distributed-control systems execute control logic.
Edge layer: local computers filter, store, analyze, and respond to data close to the machine.
Platform or data layer: databases, historians, data lakes, event brokers, and asset models organize information.
Application layer: manufacturing execution, maintenance, quality, scheduling, energy, and analytics applications use the information.
Enterprise and lifecycle layer: product-lifecycle management, enterprise-resource planning, supply-chain, and business-intelligence systems coordinate broader decisions.
Layered Industry 4.0 architecture from physical assets to enterprise applications
Figure: Layered Industry 4.0 architecture from physical assets to enterprise applications
Figure: A practical layered architecture for connected manufacturing systems.
The architecture is not strictly linear. Data may move upward for monitoring and analysis, while commands, recipes, schedules, and configuration values move downward. Safety functions normally remain local and must not depend on an external cloud connection.
Reference Models and Standards
Architects often use reference models to establish common vocabulary and boundaries. The Purdue Enterprise Reference Architecture separates levels of physical control from supervisory and enterprise systems. RAMI 4.0 describes Industry 4.0 assets across hierarchy levels, lifecycle value streams, and functional layers. These models are not complete implementation designs, but they help teams identify interfaces and responsibilities.
Common industrial communication technologies include OPC UA, MQTT, Modbus TCP, PROFINET, EtherNet/IP, CAN-based networks, and time-sensitive networking. They differ in timing behavior, data modeling, device support, security, and vendor ecosystem. A technology should be selected according to the required latency, determinism, reliability, interoperability, and lifecycle cost—not merely because it is popular.
3. Cyber-Physical Production Systems
A CPPS combines physical production resources with computation and communication. Its central feedback loop is:
The physical process generates measurable conditions.
Sensors acquire observations.
Controllers or edge systems process the observations.
A decision, command, or recommendation is produced.
An actuator or human changes the process.
The resulting state is measured again.
This loop supports both automatic control and human-in-the-loop operation. For example, a machine tool may measure spindle vibration, classify its condition at the edge, and alert an operator before tool failure. A closed-loop adaptive process may automatically adjust feed rate, provided that the adjustment remains within validated process limits.
A CPPS must distinguish between control data and business or analytical data. A servo-control loop may require predictable millisecond-level timing and should generally remain within a local controller. A production report may tolerate seconds or minutes of delay and can be transmitted to a cloud platform. Mixing these requirements can create unsafe or unreliable designs.
4. IIoT: Devices, Data and Communication
An IIoT system begins with a physical object and an operational question. The question might be: Why is surface finish deteriorating? Which tools produce the lowest energy per part? When is a bearing likely to fail? Data should be collected because they help answer a defined question, not simply because sensors are available.
Sensing and Data Quality
Typical manufacturing measurements include temperature, pressure, force, torque, vibration, acoustic emission, position, speed, current, power, humidity, flow, and dimensional quality. Each measurement has a sampling rate, range, resolution, accuracy, calibration condition, timestamp, and uncertainty.
A useful data record includes more than a numerical value. It should identify the asset, variable, unit, timestamp, production order, part, tool, program, operating state, and data-quality status. Without this context, a value such as “72” may be impossible to interpret.
Data quality is often assessed through:
completeness: whether expected records are present;
validity: whether values conform to permitted ranges and types;
consistency: whether related systems agree;
timeliness: whether data arrive soon enough for their use;
accuracy: how closely values represent the actual condition;
traceability: whether the origin and transformations of data are known.
Connectivity Patterns
A sensor may communicate directly with a controller, through an industrial gateway, or through an IIoT platform. Gateways commonly perform protocol conversion, buffering, filtering, normalization, and security enforcement. Publish-subscribe messaging allows producers to publish events while authorized consumers subscribe to relevant topics. This reduces point-to-point integration, although topic design and access control must be carefully governed.
5. Edge, Fog and Cloud Computing
Edge computing places computation near the machine or process. It reduces communication delay, limits bandwidth use, supports operation during network interruptions, and can keep sensitive data within the plant. Typical edge tasks include signal filtering, anomaly detection, machine-state classification, local dashboards, and buffering.
Cloud computing provides elastic storage, centralized analytics, fleet-level comparison, remote collaboration, and access to advanced computing resources. It is particularly useful when data from many plants must be combined or when models require substantial computational capacity.
A practical architecture is usually hybrid:
Requirement
Suitable location
Reason
Emergency interlock
Local controller
Requires deterministic, independent response
High-frequency vibration filtering
Edge
Avoids transmitting excessive raw data
Plant dashboard
Edge or plant server
Low-latency operational visibility
Cross-plant benchmarking
Cloud or enterprise platform
Requires aggregated data
Long-term model training
Cloud or high-performance server
Requires scalable computation
Safety-critical actuation
Validated local control system
Must not depend on internet availability
Latency is the elapsed time between an event and the required response. A system is suitable only when its total sensing, communication, computation, and actuation delay is compatible with the process dynamics. Cloud connectivity should never be treated as a substitute for a properly designed safety system.
6. Interoperability and Information Models
Interoperability is the ability of systems to exchange information and use the exchanged information meaningfully. It has at least three dimensions:
Technical interoperability: systems can connect and transmit data.
Syntactic interoperability: systems agree on message structures and formats.
Semantic interoperability: systems interpret data with the same meaning.
For example, two systems may both transmit a field called “temperature,” yet one may mean spindle temperature in degrees Celsius while the other means coolant temperature in degrees Fahrenheit. Technical connection exists, but semantic interoperability does not.
Interoperability depends on common identifiers, units, timestamps, asset hierarchies, naming conventions, and information models. OPC UA companion specifications, AutomationML, ISO 10303 product data standards, MTConnect, and open manufacturing information models are examples of approaches used to improve exchange. Standards do not automatically guarantee integration: organizations must still define mappings, ownership, version control, and validation rules.
A good information model distinguishes:
the asset identity;
asset type and capabilities;
physical and logical relationships;
measurements and units;
events, alarms, and states;
ownership and access rights;
lifecycle status and revision;
provenance and confidence.
7. The Digital Thread Across the Product Lifecycle
The digital thread links information created at different lifecycle stages. A customer requirement may lead to a product specification, CAD model, simulation, process plan, CNC program, inspection plan, production record, service history, and end-of-life decision. If these artifacts remain disconnected, engineers must re-enter information and errors become difficult to trace.
A digital thread provides relationships among artifacts. For example, a measured dimensional deviation can be linked to a specific part, machine, tool, material batch, program revision, operator shift, inspection device, and design tolerance. This supports root-cause analysis and configuration management.
The digital thread is not simply a large database. It is a governed network of identities, relationships, versions, events, and permissions. It requires:
consistent product and asset identifiers;
revision and configuration control;
documented data ownership;
lifecycle retention policies;
shared semantics;
traceable transformations;
secure interfaces.
8. Digital Twins
A digital twin is a digital representation of a physical entity that remains connected to it through data over time. The twin may represent a product, machine, production line, facility, process, or supply-chain activity.
A digital model can exist without being connected to a physical asset. A digital shadow receives data from the physical asset but may not send information back. A digital twin generally supports two-way or lifecycle interaction, although terminology varies among organizations.
Digital twins range in complexity:
Descriptive twin: reports the current condition.
Diagnostic twin: helps explain why a condition occurred.
Predictive twin: estimates future behavior or failure.
Prescriptive twin: evaluates possible actions and recommends one.
Adaptive twin: participates in controlled adjustment of the physical system.
A machine-tool twin may contain geometry, kinematic limits, maintenance history, controller state, tool data, energy behavior, and validated performance models. A production-line twin may simulate material flow, buffer levels, cycle times, labor allocation, and failure scenarios.
Digital twins can be model-based, data-driven, or hybrid. A model-based twin uses physical relationships and engineering knowledge. A data-driven twin uses statistical or machine-learning relationships learned from historical observations. A hybrid twin combines both. Hybrid approaches are valuable when physical laws constrain predictions but some phenomena are too complex to model completely.
Monitoring and Performance Measures
Real-time monitoring requires a defined operational state model. A machine may be in production, setup, idle, blocked, starved, planned maintenance, unplanned downtime, or fault. A dashboard should distinguish these states rather than label all non-production time as failure.
Overall Equipment Effectiveness is commonly expressed as:
OEE = Availability × Performance × Quality
Availability, performance, and quality are dimensionless ratios between 0 and 1. A common formulation is:
Availability = Operating time ÷ Planned production time
Performance = (Ideal cycle time × Total count) ÷ Operating time
Quality = Good count ÷ Total count
The formulation assumes that the time categories and counts are defined consistently. Ideal cycle time and operating time must use the same time unit. OEE is useful for identifying losses, but it should not be used as the sole measure of factory performance; high OEE can be undesirable if it creates excess inventory or ignores customer priorities.
Worked Example: Monitoring a Machining Cell
A cell is planned to run for 480 minutes. It experiences 60 minutes of downtime, produces 200 parts, and has an ideal cycle time of 2 minutes per part. Ten parts fail inspection.
Operating time is 480 − 60 = 420 minutes.
Availability = 420 ÷ 480 = 0.875 = 87.5%
Performance = (2 × 200) ÷ 420 = 0.9524 ≈ 95.24%
Quality = (200 − 10) ÷ 200 = 0.95 = 95%
Therefore:
OEE = 0.875 × 0.9524 × 0.95 ≈ 0.7917 = 79.17%
The result indicates that the largest improvement opportunity cannot be identified from OEE alone. The team must examine the loss tree: downtime causes, speed losses, and defect causes. A digital twin can associate these losses with specific tools, programs, materials, shifts, and machine states.
9. Analytics and Artificial Intelligence in Manufacturing
Analytics may be descriptive, diagnostic, predictive, or prescriptive. Descriptive analytics reports what happened; diagnostic analytics investigates causes; predictive analytics estimates what may happen; prescriptive analytics compares actions.
A predictive-maintenance model might estimate the probability of failure within a future interval. Its usefulness depends on representative failure data, stable sensor behavior, appropriate labels, and a response process. A high-performing model in a laboratory may fail in production because of sensor drift, changing materials, maintenance interventions, or operating conditions not represented during training.
AI should therefore be treated as a component of an engineered decision system. Important practices include:
validating models against independent data;
monitoring false alarms and missed failures;
explaining decisions when safety or quality is affected;
preserving human authority for high-consequence decisions;
controlling model versions;
detecting data drift;
defining fallback behavior when data are unavailable.
10. Cybersecurity, Safety and Governance
Connected manufacturing expands the attack surface. Threats include unauthorized access, ransomware, manipulation of process parameters, intellectual-property theft, denial of service, compromised suppliers, and falsified sensor data. A secure architecture should apply defense in depth:
inventory assets and data flows;
segment IT and OT networks;
use least-privilege access;
authenticate devices and users;
encrypt appropriate communications;
patch and manage vulnerabilities;
back up configurations and critical data;
monitor events and investigate anomalies;
test incident-response procedures;
maintain secure remote access.
Security must be balanced with availability and safety. A patch that is appropriate for an office computer may interrupt a validated production controller. Changes should be tested, approved, documented, and scheduled.
Governance also includes privacy, intellectual-property protection, data ownership, retention, compliance, and accountability. Worker-monitoring systems require particular care. Data collected for equipment improvement should not automatically be repurposed for punitive employee surveillance. Organizations should communicate purpose, limit collection, protect access, and comply with applicable labor and privacy requirements.
Functional safety and cybersecurity are related but distinct. Cybersecurity protects systems against intentional or accidental compromise; functional safety reduces unacceptable risk from hazardous behavior. Both must be designed into the system. A cloud dashboard must never replace an independent emergency-stop circuit or a validated safety controller.
11. Implementation Strategy and Best Practices
Successful implementation begins with a business and operational problem. Suitable pilot projects have measurable value, manageable scope, available data, and a clear owner. Examples include reducing unplanned downtime on a bottleneck machine, improving traceability for a critical component, or reducing energy during idle periods.
A structured implementation sequence is:
Define the objective, baseline, constraints, and success metric.
Map the process, assets, data sources, and decision points.
Establish asset identities, time synchronization, units, and ownership.
Connect equipment using secure, maintainable interfaces.
Validate data quality before building advanced analytics.
Implement local visualization and operational response.
Add analytics or a digital twin only when the information need is clear.
Integrate with MES, PLM, ERP, or maintenance systems where justified.
Measure benefits and document lessons.
Scale through reusable standards, templates, and governance.
Best practice is to preserve manual and local fallback modes. Engineers should be able to diagnose the system when a model fails, a network is unavailable, or a sensor becomes unreliable. Interoperability and cybersecurity should be specified in procurement documents rather than added after installation.
12. Illustrative Case: Digital Twin for a CNC Machining Cell
Background
The following is an illustrative case. A manufacturer produces aluminum housings on a CNC machining cell containing two machining centers, an automatic tool changer, an inspection station, and a material-handling robot.
Problem
The cell meets its average production target but experiences unexplained variation in cycle time and surface finish. Maintenance is mostly reactive. Operators record alarms manually, and process data cannot be linked reliably to individual parts.
Analysis
The improvement team identifies four information gaps:
spindle and tool-condition data are not connected to part identity;
machine states are recorded inconsistently;
inspection results are stored separately from process conditions;
maintenance history is not associated with specific failure modes.
The team defines a common asset hierarchy and synchronizes timestamps. Edge gateways collect controller states, spindle load, vibration summaries, tool identity, coolant temperature, and energy data. The inspection system publishes dimensional results using the same part identifier.
Approach and Solution
A descriptive digital twin is first created for each machine. It shows current state, active program, tool number, alarm status, and production order. A diagnostic model then compares surface-finish defects with spindle-load patterns, tool age, material batch, and coolant condition.
The team deliberately keeps control decisions local. The twin recommends tool inspection when a validated combination of tool age and vibration indicators is observed; an operator confirms the action. Maintenance records are entered against the machine and tool identifiers. A cloud platform is used only for cross-cell trend analysis, while immediate dashboards and buffering remain at the edge.
Outcome
After a trial period, the manufacturer reports fewer unexplained defects and better traceability. More importantly, engineers can distinguish speed loss caused by material handling from loss caused by machining. The project does not claim that the twin alone created improvement: standardized states, reliable identifiers, operator participation, and disciplined maintenance workflows were equally important.
Learning Points
Start with a measurable operational problem.
Data context is as important as sensor quantity.
A digital twin should mature from descriptive to predictive capability only when its data and models are validated.
Safety-critical control must remain in approved local systems.
Human expertise is needed to interpret recommendations and improve processes.
13. Challenges and Contemporary Developments
Common challenges include legacy equipment, proprietary protocols, poor data quality, uncertain return on investment, skills shortages, cybersecurity exposure, organizational resistance, and unclear ownership of data. Digital transformation can also create technology debt when organizations deploy disconnected pilots without common architecture.
Contemporary developments include industrial 5G, time-sensitive networking, machine-learning operations, synthetic data, physics-informed learning, additive-manufacturing twins, virtual commissioning, augmented-reality work instructions, and carbon-aware production control. These developments are promising but should be evaluated against reliability, explainability, lifecycle cost, and measurable operational value.
The future manufacturing professional will need combined competence in machining or production technology, instrumentation, data interpretation, networking, cybersecurity, and human-centered improvement. The most valuable systems will not merely collect more data; they will convert trustworthy data into timely and responsible action.
Chapter Summary
Industry 4.0 integrates physical production, computation, communication, analytics, and human decision-making. Cyber-physical production systems create feedback between industrial processes and digital systems. IIoT connects machines, sensors, products, and enterprise applications, while edge computing supports low-latency local processing and cloud computing supports scalable storage and cross-site analysis.
Interoperability requires technical, syntactic, and semantic compatibility. The digital thread links requirements, designs, process plans, production records, inspection results, service information, and end-of-life data. A digital twin is a connected digital representation that can describe, diagnose, predict, or prescribe actions for a physical asset or process.
Effective smart manufacturing depends on data quality, clear asset identities, appropriate architecture, cybersecurity, functional safety, governance, and human participation. OEE and other monitoring measures are useful only when their definitions and limitations are understood. Successful implementation begins with a measurable operational problem and scales through standards, validated models, secure integration, and continuous improvement.
Key Terms
Industry 4.0: A manufacturing paradigm combining connectivity, automation, data, analytics, and intelligent decision-making.
Smart manufacturing: Data-enabled manufacturing that can monitor, analyze, and improve production.
Cyber-physical system: A system linking computational functions with physical processes through sensing and actuation.
CPPS: A cyber-physical production system used in manufacturing.
IIoT: The Industrial Internet of Things, connecting industrial assets and systems for data exchange and control.
Operational technology: Technology that monitors or controls physical industrial processes.
Edge computing: Processing data near the source or machine that generates it.
Cloud computing: On-demand computing and storage delivered through shared network infrastructure.
Interoperability: The ability of systems to exchange and meaningfully use information.
Semantic interoperability: Agreement on the meaning of exchanged data.
Digital thread: A connected flow of information across the product lifecycle.
Digital twin: A data-linked digital representation of a physical asset, process, or system.
Digital shadow: A digital representation that receives data from a physical system without necessarily controlling it.
Asset model: A structured description of an asset, its properties, relationships, and lifecycle information.
Data historian: A system that stores time-series industrial data.
Predictive maintenance: Maintenance planned using predictions of condition or failure.
Machine learning: Computational methods that learn patterns from data for prediction or classification.
Defense in depth: A cybersecurity strategy using multiple protective layers.
Virtual commissioning: Testing and validating automation or production behavior using digital models before physical commissioning.
Review Questions
5 Short Answer Questions
What distinguishes a cyber-physical production system from a conventional automated machine?
Name the three dimensions of interoperability.
Why is edge computing useful in manufacturing?
What is the purpose of a digital thread?
State the three factors commonly used to calculate OEE.
5 Long Answer Questions
Explain a layered Industry 4.0 architecture and describe the role of each major layer.
Compare edge computing and cloud computing in terms of latency, bandwidth, resilience, and analytical scale.
Explain how a digital twin can develop from descriptive monitoring to prescriptive decision support.
Discuss why data quality and semantic interoperability are essential for IIoT projects.
Explain how cybersecurity, functional safety, and data governance should be addressed in a connected factory.
3 Analytical / Application Questions
A machining cell has excellent availability but poor quality. Design a digital-monitoring investigation that identifies whether tool wear, coolant condition, material variation, or inspection error is the dominant cause.
A factory wants to send all high-frequency vibration data directly to the cloud. Evaluate this proposal and recommend an edge–cloud architecture.
Develop an implementation plan for connecting a legacy CNC machine to a maintenance digital twin. Identify risks, required data, interoperability measures, and fallback arrangements.
Multiple Choice Questions with Answers
Question 1
Which capability most directly distinguishes Industry 4.0 from isolated machine automation?
A. Higher motor horsepower
B. Integration of physical assets, data, communication, and analytics
C. Removal of all human involvement
D. Use of mechanical transmission systems
Correct Answer: B. Integration of physical assets, data, communication, and analytics
Question 2
Which computing location is generally most appropriate for an emergency machine interlock?
A. Public cloud
B. Enterprise data warehouse
C. Local validated safety-control system
D. Remote business-intelligence server
Correct Answer: C. Local validated safety-control system
Question 3
Semantic interoperability means that systems:
A. Use identical computer brands
B. Can physically share the same network cable
C. Interpret exchanged data with compatible meaning
D. Store all data in one database
Correct Answer: C. Interpret exchanged data with compatible meaning
Question 4
Which statement best describes a digital twin?
A. An unconnected CAD drawing
B. A data-linked digital representation of a physical entity or process
C. A replacement for all physical safety devices
D. A paper maintenance record
Correct Answer: B. A data-linked digital representation of a physical entity or process
Question 5
A machine is planned for 400 minutes and operates for 320 minutes. Its availability is:
A. 20%
B. 40%
C. 80%
D. 125%
Correct Answer: C. 80%
Question 6
A cell produces 150 parts, of which 6 are defective. Its quality ratio is:
A. 4%
B. 94%
C. 96%
D. 106%
Correct Answer: C. 96%
Question 7
Which is an example of a digital-thread relationship?
A. Linking an inspection result to a specific part, program revision, and tool
B. Increasing machine voltage without measurement
C. Deleting production history after shipment
D. Using unrelated identifiers in every department
Correct Answer: A. Linking an inspection result to a specific part, program revision, and tool
Question 8
What is a principal advantage of an edge gateway?
A. It eliminates the need for sensors
B. It can filter and analyze data close to the machine
C. It guarantees that every cloud model is correct
D. It removes all cybersecurity responsibilities
Correct Answer: B. It can filter and analyze data close to the machine
Question 9
Which OEE component is calculated as good count divided by total count?
A. Availability
B. Performance
C. Quality
D. Utilization voltage
Correct Answer: C. Quality
Question 10
Which implementation practice is most appropriate for a smart-manufacturing project?
A. Collect every possible measurement before defining a problem
B. Begin with a measurable operational problem and validate data quality
C. Place safety control entirely in a remote cloud
D. Ignore asset identities until after deployment
Correct Answer: B. Begin with a measurable operational problem and validate data quality