23 Industry 4.0: Technologies and Integration
More
Depth: Practitioner
Progress saves as you read. Mark sections complete as you go; your progress appears in the sidebar.
- Podcast audio coming soon
- Character narration audio coming soon
23.1 From Machine Signals to Maintenance Decisions
Industry 4.0 links sensors, machines, models, and control. Place each tool where it can change a factory decision. The applications module index places the factory technologies in context. The preceding chapter, Industry 4.0: Industrial Revolutions and Adoption, provides the historical context.
A CNC spindle’s vibration reading becomes useful when it changes a maintenance decision. The signal needs machine state, a baseline, and a threshold or model before it can become a work order with a named owner. A dashboard alone does not close that loop. Nor can a fast control loop wait for a cloud round trip.
The problem is to connect observation, analysis, and action while respecting timing and safety boundaries. The approaches below use cyber-physical systems, digital twins, smart manufacturing, and vertical and horizontal integration, then test their fit against existing equipment and OT risk.
23.2 Learning Objectives
- Test industry 4.0 technologies with a concrete scenario and pass criteria.
- Validate dashboards need action loops with a concrete scenario and pass criteria.
KEY CONCEPTS
- Cyber-physical systems
Computation and physical processes form a feedback loop.
- Digital twins
Simulation informs decisions about a physical asset.
- Integration
Connect factory activities and supply-chain partners.
- Action ownership
Every signal needs an owner and a route to action.
23.3 Industry 4.0 Technologies
Industry 4.0 relies on the convergence of multiple technologies:
Before reading the technologies in Figure 1, look at what the figure says they are for.
The five numbered requirements on the left of Figure 1 are the familiar part, so move past them to the band they feed. Convergence is defined there as something narrow and testable: a measured plant condition changes a real work decision in time to matter. The spindle example below it shows what that costs. A vibration signal alone proves nothing. It has to be tied to machine state, a baseline, and a threshold or model before it can become a work order in the maintenance system. The timing note on the right is the boundary that keeps the picture honest. A control loop that must answer in a few milliseconds cannot wait for the cloud, so not every decision belongs in the same place.
This diagram introduces ISA-95 activity levels across industrial automation. A control loop’s deadline comes from the process and design requirements, not from a fixed timing limit assigned to an ISA-95 level.
Response windows lengthen from field control to operations and business planning in Figure 2.
Start at the field devices at the bottom of Figure 2. Move up through basic control, supervision, operations, and enterprise planning. Notice how the example response windows grow longer as you climb. The arrows carry data and context upward. The notes at the bottom keep fast control near the process. Slower layers use checked state for plans and coordination. These are examples, not fixed timing rules for each level. The process and system design set the deadline. A local control decision must not wait for a cloud round trip.
23.3.1 Cyber-Physical Systems (CPS)
Cyber-Physical Systems integrate computation, networking, and physical processes. Physical processes affect computations, and computations control physical processes: this is tight coupling. Distributed components communicate over industrial networks and make local decisions without human intervention. They must respond within strict time limits, often <1 ms. Examples include adaptive cruise control, smart grids, and robotic assembly cells.
Figure 3 turns the idea of a cyber-physical system into one machine and the loop that closes around it.
Read Figure 3 in three stages. The machine on the left is doing ordinary work, and its panel shows position and a running state; the additions that matter are the four signals beside it, including vibration and tool wear, which the controller does not need but a maintenance team does. The middle stage refuses to treat those numbers alone as evidence. It ties them to machine state and service history, and expects the threshold or model to be explainable. The third stage is where value appears: a work order with a named owner, an approved change, and a check that the change worked. The line at the foot is the caution for this section.
CNC machines represent a core Industry 3.0 technology now enhanced with IoT capabilities. Modern connected CNC systems continuously stream operational data to analytics platforms, enabling predictive maintenance when the signals are tied to machine state, maintenance history, and a work-order process.
CPS overlaps with traditional embedded systems and emphasizes the integration of computation, networking, and physical processes. Real-Time Systems develops the timing requirements of this tight coupling.
23.3.2 Digital Twins
A digital twin is a real-time virtual replica of a physical asset, process, or system. Physical sensors feed the digital model, and digital simulations inform physical operations: data flows in both directions. Synchronization reflects physical state at a rate suited to the application. Predictive capabilities let teams test scenarios without disrupting production, and lifecycle coverage extends through design, manufacturing, operation, maintenance, and retirement.
Use cases:
- Product design: Test virtual prototypes before building physical ones
- Process optimization: Simulate production changes without stopping the line
- Predictive maintenance: Model asset degradation to schedule maintenance
- Operator training: Train on virtual replicas without risk
Deployment patterns:
- Commissioning simulation: Test control logic, robot paths, and operator workflows before equipment arrives or before a shutdown window begins.
- Fleet monitoring: Compare many similar assets so abnormal vibration, temperature, fuel use, or quality drift stands out early.
- Process optimization: Run what-if experiments in a model before changing recipes, pressure, speed, or temperature on the live line.
- Training and safety: Let operators practice rare faults, alarm floods, and recovery procedures without putting production at risk.
Virtual replicas enable simulation before physical testing; Simulation and Modeling develops that approach.
The economics of digital twins follow a clear pattern: the model is valuable when it changes a costly decision. The break-even calculation favors assets with high downtime cost, expensive physical tests, repeated operating cycles, and enough sensor data to keep the model trustworthy.
Figure 4 answers what makes a twin different from a dashboard, and the answer is that the arrows run both ways.
The left half of Figure 4 is a real machine with four measurements coming off it: spindle speed, vibration, temperature and tool wear. The right half is the model those readings keep current. Between them sit two arrows, not one. Readings flow right to keep the model honest, and simulation results flow left to change how the machine is run. That return arrow is the whole argument, because without it the twin is only a display. The band beneath names what the return path is for: trying a recipe change without stopping the line, predicting wear early enough to schedule the work, and training an operator on faults nobody wants to stage in production. Each is a costly decision the model can move.
Digital factory twins enable manufacturers to test process changes, train operators, and optimize production schedules in simulation before committing to physical changes. This virtual environment reduces commissioning time and minimizes the risk of costly production disruptions.
23.3.3 Smart Manufacturing
Smart manufacturing applies IoT, AI, and automation to create adaptive, self-optimizing production systems. Connectivity means assets are networked and communicating; visibility means real-time monitoring of all processes. Transparency adds an understanding of cause-and-effect relationships through data. Predictability forecasts future states using AI models, and adaptability provides automatic responses to changing conditions.
The technologies have distinct jobs. Industrial IoT sensors measure temperature, vibration, pressure, and images through vision systems. Machine learning supports quality prediction, anomaly detection, and optimization. Advanced robotics includes collaborative robots (cobots) working alongside humans. Additive manufacturing uses 3D printing for customized production, while augmented reality uses AR glasses for maintenance guidance.
Figure 5 shows what has to be true before a wall of screens becomes useful rather than merely impressive.
Thousands of sensors feed the left side of Figure 5, and the middle panel squeezes them into one view an operator can hold in mind. The sample reading, a reactor core and primary coolant at 325 degrees, is there to show the form: a named asset, a named quantity, a number. The third panel is the demanding part. Every signal on that screen needs an owner, an account of the threshold or model behind its alarm, a route to a work order, and a rule for what to do when the data itself looks wrong. Without those, an anomaly highlight is only a colour on a screen.
Centralized control rooms provide operators with comprehensive visibility across distributed production facilities. Modern SCADA systems aggregate data from thousands of sensors into intuitive dashboards that highlight anomalies and guide rapid response to equipment issues.
23.3.4 Horizontal and Vertical Integration
Integration also sets the communication problem. Real-Time Requirements and ISA-95 examines hard versus soft real-time in manufacturing and the automation hierarchy in detail.
Industry 4.0 requires integration across two dimensions:
23.4 MVU: ISA-95 Automation Levels
Core Concept: ISA-95 has five levels: Level 0 physical processes, Level 1 sensors and actuators, Level 2 monitoring and control including PLCs, Level 3 manufacturing operations including MES, and Level 4 business planning including ERP. The level labels do not impose fixed response-time limits. Why It Matters: Place each function at the level responsible for that activity, and set its deadline from the process and safety requirements. A cloud or ERP service should not own a fast motor-control loop when its network and business-planning role cannot meet the design deadline. Key Takeaway: Use ISA-95 to describe industrial activities and interfaces; determine timing constraints from the actual application before selecting protocols and computing infrastructure.
Vertical Integration (within a factory):
Read the response-time column on the right of Figure 6 before the level names on the left.
The five levels in Figure 6 describe different activities, from physical processes and sensing through control, manufacturing operations, and business planning. The two arrows explain the traffic: commands travel down and data travels up. A function’s response deadline comes from its process and safety requirements, not from a fixed ISA-95 timing window. A planning system should not own a control action whose deadline it cannot meet.
Instead of abstract level names, this diagram shows concrete examples of what happens at each level. This practical view helps students understand what information flows between levels and why each layer exists.
Inspect Figure 7 to place each example decision at the ISA-95 level whose timing and authority fit it.
Start with the order for 1,000 widgets due Friday in Figure 7. Follow it down from business planning to operations, where MES schedules work and tracks progress. Next, SCADA monitors live values and raises alarms. Below that, PLC logic runs a control loop in 5 ms; the timing column shrinks from hours to days at the top to sub-millisecond at the process. Sensors and actuators sit at the physical process at the bottom. Notice that data crosses the level boundaries along with the deadline and safety owner. Keep fast control close to the process. A cloud view can inform plans without taking charge of that control action.
Horizontal Integration (across supply chain):
- Suppliers provide real-time inventory data
- Manufacturers share production schedules
- Logistics partners track shipments
- Customers trigger production through orders
- End-to-end visibility from raw materials to customer
Inspect Figure 8 to follow how shared operational data coordinates suppliers, production, logistics, and customers.
Start at the suppliers in Figure 8. They provide live inventory data. Follow the chain to the manufacturers, who share production schedules. Next, logistics partners track shipments. At the customer end, orders trigger production. Notice the data flow and feedback loops below these stages. They support changes across the chain rather than at just one handoff. The lower notes show the intended result: a view from raw materials to the customer and fewer IT/OT silos. The dashed arrow leads from feedback loops to continuous optimization.
This horizontal integration diagram shows how Industry 4.0 connects the entire value chain, enabling real-time data flow from suppliers through manufacturing and logistics to customers, with feedback loops driving continuous optimization.
This integration breaks down traditional IT/OT (Information Technology/Operational Technology) silos, enabling data-driven decision making across the entire value chain.
Checkpoint: Technology Placement
You now know:
- Cyber-physical systems keep computation and physical processes tightly coupled, often under 1 ms.
- Digital twins earn their cost when simulation changes a real design, commissioning, training, maintenance, or process-optimization decision.
- Vertical integration connects ISA-95 Levels 0-4 inside the factory, while horizontal integration connects suppliers, manufacturers, logistics partners, and customers.
The remaining sections are risk filters. Use them to test whether the architecture respects brownfield constraints, OT security, protocol reality, and the action loop that turns prediction into work.
23.5 ISA-95 Latency Validator
23.6 Brownfield vs Greenfield Tradeoff
Option A (Brownfield Retrofit): Integrate IIoT sensors and connectivity into existing factory equipment. This preserves existing assets and allows phased rollout, but legacy PLCs, undocumented register maps, closed vendor systems, cabinet space, and shutdown windows often dominate the real schedule. Option B (Greenfield Deployment): Build a purpose-designed smart line or facility with native IIoT capabilities. This can simplify integration and improve timing control, but it requires larger capital approval, commissioning risk, migration planning, and a clear reason to replace still-useful equipment. Decision Factors: Choose brownfield when equipment is less than 10 years old with documented protocols, capital budget is constrained, or production cannot tolerate extended downtime. Choose greenfield when equipment replacement is already planned within 5 years, competitive pressure demands step-change improvements, or existing facility cannot meet quality/throughput requirements regardless of digitization.
23.7 OT-First vs IT-First Integration
Option A (OT-First): Start integration from the plant floor up, beginning with PLC/SCADA connectivity before enterprise integration. This protects operational stability and lets OT engineers define safe read-only paths, but business-facing dashboards and analytics arrive later. Option B (IT-First): Start from enterprise systems such as ERP, MES, and analytics platforms, then extend downward to plant-floor data. This can show business value quickly, but it risks production disruption if the design ignores OT timing, segmentation, and change-control constraints. Decision Factors: Choose OT-first when production uptime is the primary KPI (24/7 continuous process industries), OT systems use legacy protocols requiring specialized translation, or cybersecurity requirements mandate strict network separation. Choose IT-first when business intelligence and analytics are the immediate priority, factory already has modern PLCs with Ethernet connectivity, or organization has stronger IT than OT capabilities.
23.8 OT Security Differs From IT
OT/IT convergence sends factory data to business systems securely. Security Architecture develops the architecture, while Security for Industrial IoT covers OT network protection and the Purdue model.
Misconception: Organizations assume their IT security team and existing cybersecurity tools (firewalls, antivirus, patch management) can directly protect OT/IIoT systems.
Reality: OT and IT have fundamentally different priorities and constraints:
- Priority: IT security puts confidentiality first; OT security puts availability first because production uptime is the primary concern.
- Patching: IT systems are patched immediately; OT systems are patched only during planned shutdowns, often quarterly or annually.
- Scanning: Active vulnerability scanning is normal in IT; the same scans can crash PLCs and halt production in OT environments.
- Protocols: IT relies on TCP/IP, HTTP, and TLS; OT commonly depends on Modbus, PROFINET, and EtherNet/IP, including legacy protocols with weak built-in security.
- Lifecycle: IT refresh cycles are typically 3-5 years; OT equipment often remains in service for 15-30 years.
- Failure impact: IT failures usually mean data breach or financial loss; OT failures can create physical safety risks and environmental damage.
Why it matters: In 2017, the TRITON/TRISIS malware targeted Safety Instrumented Systems (SIS) in a petrochemical plant — systems designed to prevent explosions. Applying IT-centric security assumptions to OT environments can leave the most critical safety systems unprotected while simultaneously disrupting production through aggressive scanning or patching.
The fix: Build a dedicated OT security program with International Electrotechnical Commission (IEC) 62443 as the framework, not International Organization for Standardization (ISO) 27001 alone. Staff with engineers who understand both cybersecurity and industrial control systems. Implement network segmentation using the Purdue Model (ISA-95 levels) with demilitarized zones between IT and OT networks. Never scan or patch OT systems without OT engineering approval.
Predictive Maintenance develops vibration analysis and ML for failure prediction. The worked example below tests the economics of that approach.
23.9 IIoT Predictive Maintenance ROI
Illustrative scenario: An automotive parts manufacturer operates 12 CNC machines that cost $50,000/hour in lost production when down unexpectedly. Historical data shows each machine fails once per year on average, with repairs taking 8 hours. They are evaluating a predictive maintenance system.
Current State (Reactive Maintenance):
- 12 machines × 1 failure/year × 8 hours downtime = 96 hours/year total
- Cost: 96 hours × $50,000/hour = $4,800,000/year in unplanned downtime
- Plus: Emergency parts expediting (
$25,000/year), overtime technician labor ($40,000/year) - Total annual cost: $4,865,000
Proposed IIoT Solution Investment:
- Vibration sensors (3 per machine): 36 × $200 = $7,200
- Temperature sensors (2 per machine): 24 × $50 = $1,200
- Edge gateway with ML inference: $15,000
- Cloud platform subscription: $2,000/month = $24,000/year
- Integration and setup: $80,000 (Year 1 only)
- Year 1 total: $127,400
- Ongoing annual after Year 1: $24,000
Illustrative Expected Outcomes (Assumptions):
- Predictive maintenance catches 70% of failures before unplanned downtime occurs
- Prevented failures: 12 × 0.70 = 8.4 failures/year
- Remaining unplanned downtime: 12 - 8.4 = 3.6 failures × 8 hours = 28.8 hours/year
- Planned maintenance windows: 8.4 repairs × 4 hours (scheduled, not emergency) = 33.6 hours (during off-shift)
- Reduced unplanned downtime cost: 28.8 hours × $50,000 = $1,440,000/year
- Savings: $4,800,000 - $1,440,000 = $3,360,000/year
ROI Calculation:
- Net Year 1 benefit: $3,360,000 - $127,400 = $3,232,600
- Payback period (assuming savings accrue evenly through the year, unlike the year-end NPV cash flows): 127,400 / 3,360,000 × 12 months = 0.45 months (~14 days)
- 5-year NPV (10% discount rate): with the $127,400 Year 1 cost paid upfront, $3.36M savings at each year-end, and $24,000 subscription costs at each year-end from Year 2, the net benefit is approximately $12.54M
Key insight: In the scenario, a single prevented failure pays for the sensor investment. The lesson is not that every IIoT project pays back in weeks; it is that the strongest business cases start with expensive, frequent, observable failure modes.
23.10 Brownfield vs Greenfield IIoT
The business case now meets the equipment constraint: can the existing line provide usable signals without disrupting production?
When implementing Industry 4.0, choosing between retrofitting existing equipment (brownfield) versus building new smart facilities (greenfield) is a strategic decision with multi-year implications.
- Initial capital: Brownfield pilots tend to start smaller because they reuse existing machines; greenfield lines require a larger capital case because the project includes new equipment, commissioning, and migration.
- Integration timeline: Brownfield projects often spend schedule on legacy protocols, documentation gaps, and shutdown windows; greenfield deployments spend schedule on construction, vendor coordination, and commissioning.
- Maximum OEE improvement: Brownfield upgrades are usually bounded by existing mechanical constraints; greenfield lines can redesign flow, instrumentation, and control from the start.
- Protocol compatibility: Brownfield projects usually need gateways for Modbus RTU, PROFIBUS, and proprietary serial links; greenfield deployments can standardize on OPC UA, MQTT, and vendor-supported integration from day one.
- Timing capability: Brownfield retrofits inherit existing PLC cycle times, networks, and safety approvals; greenfield cells can specify timing and synchronization requirements upfront.
- Equipment remaining life: Brownfield makes more sense when current equipment has meaningful useful life left; greenfield planning assumes a fresh asset lifecycle.
- Business disruption: Brownfield rollouts can be phased during scheduled downtime; greenfield transitions are much more disruptive because production moves to a new line or facility.
- Sunk cost recovery: Brownfield preserves the value of existing equipment; greenfield may require writing off old assets and funding a new asset base.
Decision Rules:
-
Choose Brownfield when:
- Equipment is <10 years old with documented communication protocols
- Capital budget is constrained (<$1M available)
- Production cannot tolerate extended downtime (>2 weeks)
- Existing equipment meets quality/throughput targets with minor improvements
- Goal is incremental improvement (10-20% OEE gains acceptable)
-
Choose Greenfield when:
- Equipment replacement is already planned within 5 years (accelerate timeline)
- Competitive pressure demands step-change improvements (not incremental)
- Existing facility cannot meet demand regardless of digitization
- Industry 4.0 capabilities are a core competitive differentiator
- Access to low-cost capital or government incentives available
Hybrid Strategy: Many manufacturers adopt a “brownfield first, greenfield later” approach. Prove ROI with pilot brownfield retrofits (6-12 months), then use demonstrated savings to justify greenfield expansion. This reduces risk while building internal expertise.
Pattern example: A supplier might begin with a brownfield retrofit on a small group of presses, prove that the data improves maintenance and quality decisions, then use that evidence to justify a later greenfield line. The sequencing reduces risk because the team learns the process, data, and organizational constraints before funding the larger asset.
23.11 See Also
Timing constraints dictate protocol choice. Industrial Communication Protocols examines EtherCAT, PROFINET, Modbus, OPC UA, and protocol selection for manufacturing. The OPC UA Standard develops the unifying standard for industrial interoperability.
Edge analytics keeps sub-millisecond decisions local. Edge Computing develops processing architectures for millisecond latency. These placement choices must fit the plant’s actual protocols.
23.12 OT vs IT Protocol Confusion
The Mistake: IoT engineers from IT backgrounds often assume industrial systems use standard TCP/IP networking and can be integrated like web services. They design IIoT architectures using RESTful APIs, HTTPS, and cloud-first approaches without understanding OT (Operational Technology) requirements.
Why This Fails:
Industrial equipment may use protocols different from those in IT systems, although both can use Ethernet and TCP/IP:
- HTTP/REST over Ethernet vs. Modbus RTU over RS-485: OT systems may not expose IP addresses at all, so the usual TCP handshake and REST model simply does not exist.
- JSON payloads vs. raw register reads: IT systems exchange self-describing payloads; OT systems often return fixed 16-bit registers that require protocol-specific mapping.
- TLS as a default vs. little or no built-in encryption: OT security is frequently enforced through segmentation and controlled gateways rather than end-to-end encryption on every device.
- 50-500 ms acceptable latency vs. <10 ms control loops: Cloud roundtrips that feel fine in IT can break deterministic machine control.
- Request/response vs. cyclic polling: PLCs expect data at fixed intervals such as every 10 ms, not only when an application chooses to request it.
Failure pattern: A team designs an IIoT gateway around HTTP polling and JSON payloads, then discovers that the real equipment exposes Modbus registers, PROFIBUS segments, vendor-specific fieldbus behavior, or undocumented serial links. The gateway work stalls while the team adds protocol converters, maps registers, validates units, and negotiates safe read-only access with OT engineering.
Typical consequences:
- Schedule slip: Integration moves from application work into protocol discovery, cabinet access, and test-window coordination.
- Budget pressure: Protocol gateways, OT consultants, spare parts, and plant access become unplanned cost items.
- Technical debt: Each converter and custom register map becomes another device to monitor, patch, document, and recover after a failure.
23.13 In 60 Seconds
Industry 4.0 connects plant sensors and control systems to analysis while keeping operational timing and safety boundaries visible.
How to Avoid This:
-
Conduct OT inventory BEFORE design: Document every PLC model, firmware version, and communication protocol in the facility. Tools: Nmap scan for networked devices, physical inspection for serial protocols.
-
Bring OT expertise in early: Have industrial automation engineers review existing systems and specify integration requirements before software architecture is locked.
-
Use OT-native gateways: Platforms such as Kepware, Ignition, and Amazon Web Services (AWS) IoT Greengrass include industrial protocol drivers and operational deployment patterns. Do not build your own protocol stack unless you have a strong reason and the plant can support it.
-
Accept hybrid architecture: OT and IT networks must remain segregated. Use DMZ gateways with one-way data flow (OT→IT). Never expose PLCs directly to the internet or cloud.
-
Prototype with real equipment: A bench PLC, drive, or gateway with representative firmware and protocol settings reveals integration challenges faster than any architecture diagram.
Key Lesson: IIoT is fundamentally different from consumer IoT. Industrial systems prioritize determinism (data arrives exactly when expected) over throughput, uptime over features, and proven reliability over cutting-edge technology. Respect the 30-year lifespan and safety-critical nature of OT equipment.
Checkpoint: Business Case and Risk
You now know:
- Predictive maintenance return on investment (ROI) depends on observable failure modes, not a generic dashboard: the example uses 12 CNC machines, 8 hours per failure, and a 70% capture assumption.
- Brownfield and greenfield choices trade initial capital, integration timeline, timing capability, remaining equipment life, and business disruption.
- OT security differs from IT because availability, planned patch windows, protocol age, 15-30 year lifecycles, and physical safety change the risk model.
At this point the main argument is complete. The last checks ask you to apply timing placement, concept matching, implementation order, diagram labels, and a small signal-gate code pattern.
23.14 Industry 4.0 Tech Relationships
Industry 4.0 success depends on respecting timing boundaries: a machine control loop (1 ms) cannot wait for cloud analytics (200 ms+). Match processing location to the latency requirement. The concept and implementation checks below bring those relationships together.
Common Pitfalls
23.15 1. Treating Monitoring as Control
Reading a PLC tag for visibility is not the same as writing a command back to the machine. Monitoring can often be added through read-only paths, but control changes need safety review, rollback plans, operator training, and acceptance testing.
23.16 2. Ignoring Maintenance Windows
IIoT work happens around production. A design that assumes frequent reboots, firmware changes, cabinet access, or active scanning will fail in plants where maintenance windows are short and tightly controlled.
23.17 Dashboards Need Action Loops
A dashboard is not an outcome. Every IIoT signal needs an owner, a threshold or model explanation, a work-order or escalation path, and a rule for false positives, missing data, duplicated alerts, and stale readings.
23.18 Code Challenge
Summary
Industry 4.0 represents the digital transformation of manufacturing through cyber-physical systems, IoT connectivity, and artificial intelligence:
Historical context: Four industrial revolutions changed how factories produce through mechanization, electrification, automation, and now digitalization.
Core technologies: Digital twins, smart manufacturing, cyber-physical systems, and horizontal/vertical integration converge to create adaptive, self-optimizing factories.
ISA-95 levels: Industrial systems span physical processes (Level 0), sensors and actuators (Level 1), monitoring and control including PLCs (Level 2), manufacturing operations (Level 3), and business planning (Level 4). ISA-95 levels classify activities rather than fixed response times.
Integration strategies: Both vertical (field-to-enterprise) and horizontal (supply chain) integration are required, with careful consideration of brownfield vs greenfield deployment approaches.
A measured plant condition creates value when it changes a real work decision in time to matter. Keep fast control local, make the model explainable, and give every signal an owner and an action path.
