TL;DR: Boeing’s new agreement will use near-real-time onboard data to support predictive maintenance and cybersecurity threat detection on aircraft such as the C-17 and KC-46, so faults and intrusions can be identified at mission speed instead of hours or days later, according to Shift5. The bigger shift is that operational technology visibility becomes a shared resilience control, not a separate maintenance or security afterthought.
Editorial analysis by NHI Mgmt Group, based on content published by Shift5: “Near-Real-Time Data Powers Faster Fault and Threat Detection”.
Key questions
Q: How should OT teams govern shared telemetry for maintenance and security use?
A: They should define clear ownership, retention, escalation, and tuning rights before the same data stream becomes business-critical.
Q: Why does near-real-time data matter for fault and threat detection in OT environments?
A: Because slow data turns operational monitoring into after-the-fact reporting.
A: The control boundary breaks first.
Practitioner guidance
- Map telemetry ownership and decision rights Document which team owns aircraft or asset telemetry, who can adjust alerting logic, and who escalates when maintenance and security signals conflict.
- Measure detection latency against operational tempo Test whether the monitoring pipeline still identifies faults and anomalies early enough to change maintenance or security decisions during live operations.
- Separate operational use from security use Define how the same data stream supports predictive maintenance without weakening evidentiary quality, triage consistency, or incident review.
Bottom line: Shared telemetry can improve both maintenance and cyber detection, but only if ownership and escalation are clearly defined.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →