Chapters

3 Manufacturing IoT: OT Integration Boundaries

applications
application
domains
manufacturing
Listen
Uses your device's voice. Tap ▶ beside any paragraph to hear just that one.
  • Podcast audio coming soon
  • Character narration audio coming soon
Lecture
Video lecture coming soon. The slides are the lecture for now.
Ask AI
Pick a prompt. We copy it for you and open an AI service; paste it there. Nothing is sent to IoTClass.

3.1 From a Bearing Warning to an Approved Action

Manufacturing IoT earns its place when a reading reaches someone who can act on it safely. This second part builds on Connected Factory Systems: test the complete decision loop, preserve the meaning of its records, and check its production and financial results. The applications module places this plant case among other application domains.

Follow CNC-07. Vibration sensors warn of a bearing problem; the schedule offers a maintenance window before predicted failure. A correct warning left in a separate dashboard cannot reserve that window, obtain a bearing, or generate a work order. Integration must connect these steps within the plant’s availability, safety, quality, cybersecurity, and change-control constraints.

The problem is deciding what may cross a boundary and who authorizes action. Start with read-only telemetry, establish data and control responsibilities, then trace the maintenance decision into enterprise systems. The same discipline will let us examine recall interlocks and smart packaging, before testing the vaccine example’s savings against its costs.

KEY CONCEPTS

  • OT boundaries

    Separate observation, advice, approved action and control.

  • Data meaning

    Carry units, timestamps, asset identity and batch context.

  • Maintenance workflow

    Connect the warning to parts, downtime and a work order.

  • Packaging evidence

    Link identity and condition history to an action and its cost.

3.2 Learning Objectives

  • Test ot integration boundaries with a concrete scenario and pass criteria.
  • Validate putting numbers to it with a concrete scenario and pass criteria.

3.3 Define What May Cross the OT Boundary

Operational technology (OT) monitors or controls physical production. A prototype should read first, write later, and prove how data will be governed before it can affect control. A programmable logic controller (PLC) executes machine-control logic; its tag is a named data item.

The first boundary concerns meaning across layers. A PLC tag such as MTR_07_VIB_RMS may be sampled every second at the edge, compressed by a historian (a time-series record), joined to a motor asset in a computerized maintenance management system (CMMS), associated with a batch in a manufacturing execution system (MES), summarized into an overall equipment effectiveness (OEE) dashboard, and used by finance to justify a spare-parts policy. If any layer changes the unit, timestamp, asset id, threshold, or missing-data rule without control, the final decision can be wrong even though every individual system appears healthy.

Safety and cybersecurity boundaries must be explicit. Telemetry that only informs maintenance can often be read through OPC UA, MQTT, or a historian interface with limited risk. Control writebacks, recipe changes, and interlocks require stronger review because they can affect equipment, operators, product quality, and regulatory records. In International Electrotechnical Commission (IEC) 62443 terms, the design should define zones, conduits, trust relationships, remote-access controls, certificate rotation, account ownership, patch windows, logging, and rollback. In production terms, the design should define who is allowed to acknowledge an alarm, override a recommendation, release a held batch, or defer a work order.

Test evidence should follow the complete loop, not just the device. A useful acceptance test injects a known bearing-fault pattern, verifies edge feature extraction, checks the timestamp in the broker and historian, confirms the MES or CMMS action, observes the operator response, and records whether downtime, scrap, energy, or quality actually improved. That loop-level evidence is what separates a factory demo from a deployable manufacturing system.

Control boundary. Separate read-only telemetry, advisory alerts, operator-approved actions, PLC writebacks, interlocks, and safety-instrumented functions.

Data boundary. Version tag names, units, sampling intervals, deadbands, timestamp source, historian compression, batch context, and missing-data behavior.

Cyber boundary. Define IEC 62443 zones and conduits, OT demilitarized zone (DMZ), a separated network segment, firewall rule, broker certificate, user role, remote-access policy, and patch window.

Change boundary. Define who approves tag additions, recipe changes, dashboard thresholds, MES mappings, CMMS workflow changes, and rollback after a bad deployment.

The prototype is stronger when one event can be traced from sensor or PLC tag through edge gateway, broker, historian, MES, enterprise resource planning (ERP), or CMMS action, operator response, and measured production outcome.

The industrial network test makes the limit of that evidence concrete. After an inter-switch link is removed, an operator PC loses contact with a human-machine interface (HMI), while a plant PC still receives four HMI ping replies. That establishes local HMI reachability and a broken operator path. Ping tests IP reachability; it does not show that a remote operator saw a live sensor value, that a historian stored an alarm, or that a PLC alarm kept running.

Before claiming a Packet Tracer PLC threshold raised an HMI alarm, show the runnable threshold, a changed sensor input, the resulting PLC decision, and the actual HMI indication. Green Ethernet markers, default Start and Stop controls, and successful pings cannot establish that sensor-to-alarm behavior. These are different acceptance claims and need separate observations.

3.4 Follow the Data Across Four Operating Ranges

Once the boundary record is clear, ask how far each use of the data reaches. The four pillars of smart manufacturing pair capabilities with business value at increasing distances from the machine.

At the Manufacturing Plant, real-time production monitoring, waste elimination, and condition-based maintenance alerts aim to increase throughput and reduce unplanned downtime. Global Facility Insight compares several sites: remote equipment management and temperature or energy optimization can support central facility management. Quantify energy savings against a measured baseline.

At the Customer Site, operational data goes back to the original equipment manufacturer (OEM) to enable remote service, faster repairs, and proactive parts replacement. Global Operations adds cross-site visibility, usage analytics, and depreciation tracking to optimize capital allocation and predict maintenance needs. Finance can use fleet-wide patterns to inform warranty and capital decisions.

Read those ranges from the line outward. Inside one plant, data supports real-time line control. Across sites, the same feeds become energy and alarm comparisons. At a customer site, telemetry supports service rather than production. At the global level, it informs investment. A single telemetry fabric can support these four readings of one investment; each still needs its own evidence of business value. The CNC example now follows the first range from sensing through the maintenance decision.

Figure 1 brings the CNC pipeline and its four operating ranges together. Its energy-savings annotation needs a measured baseline; it does not establish a guaranteed saving.

CNC-07 pipeline from sensor timing and FFT evidence through severity scoring, MES scheduling and bearing replacement. A lower strip pairs capabilities and business value across plant, facility, customer and global operating ranges.
The CNC-07 example connects sensing, edge analysis, scheduling and maintenance action. The lower strip places that plant loop alongside facility management, customer service and global operations.

3.5 Turn the CNC Warning into Scheduled Work

In this illustrative case, CNC-07 receives a bearing-fault warning 10 days before a predicted breakdown. Check each layer before accepting the prediction or financial benefit.

Before trusting a vibration spectrum, look at what produced it: Figure 2 cuts one sensor open.

Cutaway metal industrial accelerometer with threaded mounting, hex flats and an exposed internal sensing assembly. No cable or machine is visible.
A threaded mounting transfers machine motion into an industrial accelerometer. Mounting stiffness and location belong in the maintenance evidence record alongside the spectrum. The photograph is by Jf268 and is licensed under CC BY-SA 3.0.

The coarse screw thread at the top of the housing is the signal path: a stiff stud joint passes fast machine motion into the sensor. The hex flats allow tightening to a specified value, making fitting a controlled step. The cut-away window in the middle reveals the short stack of discs clamped inside the solid metal body, which is the sensing element and its mass. Figure 2 explains why the maintenance record must state where and how the sensor was mounted, not just what the spectrum showed.

Sense the machine. A triaxial vibration sensor on the CNC milling machine’s spindle housing samples the X, Y, and Z axes at 10 kHz (10,000 readings/second). An industrial temperature sensor monitors the bearing housing every 1 second. A current sensor on the motor power line checks for electrical anomalies every 100 ms. Record these different sampling intervals.

Extract the evidence at the edge. The attached edge computer performs a Fast Fourier Transform (FFT), converting time-domain acceleration into a frequency spectrum from 0–5000 Hz. The example’s dominant peaks are 60 Hz, 120 Hz, 1800 Hz, and 3600 Hz. Its normal baseline concentrates vibration energy at 1800 Hz. Treat that as the scenario’s spectral reference, rather than an established spindle rotation frequency.

A 10.0 kHz sample rate has a 5.00 kHz Nyquist limit. A 1,024-sample FFT spans 102.4 ms with 9.77 Hz bins, placing the 1,800 Hz tone near bin 184. A hypothetical 6.20 kHz component folds to 3.80 kHz. A 16-bit ±5g input has a 0.000153g step, so sample timing, rather than amplitude resolution, sets this example’s main evidence risk.

The scenario assigns new peaks to degraded bearings: inner race, 1800 + (1800 × 0.042) = 1875.6 Hz; outer race, 1800 − (1800 × 0.035) = 1737.0 Hz; and ball defect, 1800 × 0.021 = 37.8 Hz sidebands. These are illustrative assignments, not general bearing-fault formulas. Validate them for the actual bearing and operating speed before using them to diagnose a machine.

The maths

Connect sample rate, window length, bin width, aliasing and quantisation with Motion Marley.

Explore the sample-rate Math Bridge

Compare and trend. An edge machine-learning (ML) model, trained on 2 years of historical data from 50 identical machines, compares the spectrum with its baseline. Severity runs from 0 (healthy) to 100 (imminent failure). The current score is 35, the yellow zone for scheduling maintenance. It rose from 10 to 35 over the past 7 days; linear extrapolation reaches roughly 70 in another 10 days. That trend supports a planning horizon, but does not by itself establish a failure date.

Connect the decision to the schedule. The edge gateway sends MES the scenario’s alert: “Machine CNC-07 bearing fault detected, predicted failure in 10 days.” MES finds planned downtime in 8 days for a tool change, automatically orders bearing SKU FAG-6205-2RSR ($45, 3-day delivery), and generates the work order: “Replace spindle bearing during scheduled downtime on Day 8.” Validate the predicted date and observe completion of the scheduled response.

Measure the outcome. The bearing is replaced during a 4-hour planned maintenance window. The hypothetical breakdown would have caused a 48-hour production halt ($120K revenue loss), a $200 expedited emergency bearing, $500 overtime labor, and an $8K damaged spindle. Planned replacement costs $45 for the part plus $200 labor during normal downtime, totaling $245. The listed avoided amounts sum to $128,700; the original rounded comparison used $128K / $245 = about 523×. This is an avoided-cost-to-intervention-cost ratio, rather than a full investment ROI.

The vibration sensor supplies the warning; integration with MES makes the timely intervention possible. Without the production schedule, maintenance might log the alert without knowing that early work fits a planned stop. A common failure is to send correct sensor evidence only to a separate condition-monitoring dashboard that the maintenance team checks weekly. By then the bearing may already have failed. Review sensing, edge analysis, MES/ERP scheduling, work orders, and spare-parts supply as one loop.

Check knowledge

Check OT responsibilities, network evidence and the CNC maintenance workflow.

Check the plant decision loop

3.6 Connect Recall Detection to a Safe Response

The maintenance loop coordinates a planned intervention. A safety recall may require a connected product to refuse operation. Both need explicit authority for physical action.

The same pattern can begin on the production line. A machine-vision check can detect a faulty food packet and stop the machine from pressing or sealing that packet. Detection alone is not the control outcome: the design must connect the inspection result to the interlock that prevents the next unsafe process step.

When a produce recall is issued, a connected juicer can check QR codes on ingredient packs against a recall database, prevent pressing of affected batches, alert the user to return affected products, and provide the manufacturer with real-time recall compliance data.

Traditional recalls rely on customers hearing the news and checking pantries. A connected product can actively prevent consumption of recalled items and give the manufacturer immediate visibility into recall effectiveness. This matters particularly for infant formula, medications, and allergens. Record the blocked process step and user response to demonstrate the safety loop.

3.7 Make Packaging Conditions Actionable

A radio-frequency identification (RFID) label illustrates how little hardware a package can carry (Figure 3).

Thin adhesive RFID label with a printed antenna around a central chip.
An RFID label carries machine-readable identity in a thin package. The printed antenna supplies energy from the reader field to the central chip. The photograph is by Maschinenjunge and is licensed under CC BY-SA 3.0.

Look first at the ruler along the bottom. The whole tag is about three centimetres across and flat enough to sit under a printed label, which is what makes one per package affordable. Now follow the spiral of printed tracks inward. Those loops are the antenna, and they are also the power supply, because the reader’s field is what wakes the tag. There is no battery to fit or replace. At the centre sits the only silicon in the device, a chip far smaller than the coil that feeds it. Figure 3 sets the honest baseline here. Identity travels cheaply, while active sensing has to earn its extra cost.

Smart packaging systems for food and pharmaceuticals go beyond passive containment to actively sense, measure, communicate, and respond to product conditions.

Traditional packaging contains and protects. Its printed date is static, shelf life rests on conservative estimates, and temperature abuse can stay unknown until spoilage. Smart or active packaging adds sensing, communication, and response: dynamic freshness data, real-time remaining-quality information, and visible temperature logs. A verified quality chain can give consumers more evidence than a “best by” estimate, provided the measurements support the claim.

Choose the technology for the condition you need to observe. Time-temperature indicators (TTI) monitor cumulative heat exposure for vaccine and seafood cold-chain integrity. Freshness indicators detect CO2, ammonia, or volatile amines for meat and fish spoilage. Oxygen indicators monitor O2 in modified atmosphere packaging (MAP) to check atmosphere integrity.

RFID and near-field communication (NFC) tags carry product identity; temperature-logging versions support supply-chain tracking and authentication. Printed electronics can monitor moisture, pH, and bacterial contamination, including in pharmaceutical blister packs. A passive identity label alone does not establish that these conditions were measured: active sensing has to justify its additional cost.

The economic opportunity needs the same care as the condition record.

Food loss and waste are significant, and confusion over date labels is one contributing cause; quantify the avoidable loss in the target supply chain before claiming a packaging benefit. Estimate US pharmaceutical expiry waste from a defined product population and dated inventory records before claiming a national dollar total. Vaccine cold-chain excursions can compromise product quality; use shipment temperature logs and potency guidance to estimate the affected share in the target distribution network. Authentication packaging may help detect suspect medicines; quantify its detection performance and addressable loss in the target distribution channel. Size a smart-packaging opportunity with a dated, defined market study before giving a 2030 revenue forecast.

A useful packaging record therefore connects product identity, condition history, cold-chain state, and the action a customer or supplier should take. Use the separate calculator to test whether a proposed reduction in degradation pays for its tags and cloud logging.

Try it

Vary vaccine volume, dose value, degradation rates and tag cost; compare gross avoided waste with net savings.

Use the Smart Packaging ROI Calculator

3.8 Test the Vaccine Savings Against the Costs

These are scenario assumptions, not a measured national loss rate. A pharmaceutical distributor ships 500,000 vaccine doses per year at $45 per dose. If 25% arrive degraded because of cold-chain failures, annual waste is 500,000 x 0.25 x $45 = $5,625,000.

TTI smart packaging costs $0.85 per dose, including the tag and cloud logging. If that monitoring reduces degradation to 3%, the new waste is 500,000 x 0.03 x $45 = $675,000, and the packaging program costs 500,000 x $0.85 = $425,000.

Annual gross avoided waste is $4,950,000. After $425,000 in annual tag and logging costs, net annual savings are $4,525,000, or about $377,083 per month at steady volume. This example does not specify an upfront investment, so it does not establish a payback period.

Monitoring must lead to action that reduces degradation; a tag cannot recover damaged stock. Validate the assumed improvement against shipment logs, potency guidance, and the defined product population. Keep avoided waste, recurring costs, and upfront investment separate.

Check knowledge

Check recall actions, packaging evidence and net vaccine savings.

Check packaging evidence and costs

Hands-on lab · 75 min · Cisco Packet Tracer

Industrial Device-State and Network Boundary

I have explained OT boundaries; now let us test local and operator reachability around one industrial network conduit.

Open the lab

Summary

A plant integration is reviewable when one event can be followed from sensor or PLC tag through the edge, historian, MES/ERP/CMMS action, operator response, and measured production outcome. Preserve the units, timestamps, asset identity, batch context, and missing-data rules, and state who may approve each control or workflow change.

CNC-07 shows why an accurate warning needs a production window, a replacement part, and a completed work order. Recall interlocks and smart packaging extend the same discipline to products: connect identity and condition evidence to an observed response. The vaccine calculation keeps avoided waste and tag spending separate and makes no payback claim without an upfront investment.

Test the whole decision loop: a reachable device, a detected fault, or a condition label becomes useful only when the authorized action and its result are demonstrated.

Carry that evidence discipline into Manufacturing IoT: Maintenance and Supply Chains.

Hi, I’m Ada. What do you need?

Find help

Let’s find what you need

Find a lesson or return to your module guide.

Give feedback

Help improve this chapter

Tell us what helped or what needs fixing.

Tips

Try a small next step

A few ways to get more from this chapter.

Ask AI

Continue the conversation

Take the conversation further with your preferred assistant.

AI help is available in supported modules when enabled in Settings.

No live person answers on independent study. Feedback does not promise a personal reply.

For welfare or safety concerns, follow your school’s procedures outside IoTClass.