Here’s how BLOX transforms early signals into planned actions that protect tube performance.
January 9, 2026
Every unplanned maintenance story begins the same way: a system running, a sudden stop, and a rush to respond. When the production line goes down, attention turns to the problem rather than the process. You fix what’s broken, restart the system, and move on, until it happens again. This pattern, called the reactive cycle, keeps companies stuck at the bottom of the performance curve. In the reactive circle, maintenance is driven by events rather than planning. Failures trigger actions, not insight. Engineers spend valuable hours troubleshooting instead of improving systems. And each loop, repair, restart, repeat, feels productive but leads nowhere. The more reactive you become, the less control you have over uptime, cost, and predictability.
The hidden cost of being reactive
Being reactive may feel unavoidable, but it comes at a steep price. Every unplanned shutdown means lost hours, lost revenue, and lost focus. Costs escalate as emergency parts are ordered, service engineers are dispatched, and production stops unexpectedly. But the more profound impact is cultural – a mindset that normalizes firefighting and accepts downtime as a given.
Reactive behavior blinds you to the warning signs your systems already provide. Slight temperature increases, irregular shutdowns, or abnormal cycle counts often appear months or weeks before a failure. Without structured monitoring, these signs go unnoticed. By the time action is taken, damage has already occurred. That is the real pain of being reactive: you learn only after it's too late.
At 12 o'clock – the preventive mindset
At Comet X-ray, we describe the ideal maintenance state as 12 o'clock – the top of the circle where foresight replaces reaction. It's the point where insight becomes control. At 12 o'clock, your systems don't wait for problems; they tell you what's coming. You plan service based on data, not disruption.
BLOX was designed to help OEMs and system owners maintain their competitive edge. It's an IIoT health monitor that delivers smart insights into X-ray tubes and generators —the critical core of every imaging system. BLOX collects performance data, identifies trends, and highlights where action is needed – turning uncertainty into foresight and downtime into planning.
From guesswork to clarity
"With BLOX, we move from guesswork to clarity," says Corbat, product manager for BLOX."It helps identify and manage risks in a structured way, make faster decisions, and significantly reduce the time spent troubleshooting." Unlike full-system monitoring tools, BLOX focuses precisely on what matters: tubes and generators. After Comet delivers the iXRS module, the OEM integrates it into the system that the end-user operates daily.
The OEM should ideally upload diagnostic data from the system to BLOX at regular intervals, every 1 to 2 months, gaining visibility into the system's actual performance. The insights drive preventive maintenance recommendations and structured service planning.
Roles and benefits across the chain
Data becomes power
The difference between reactive and preventive maintenance isn’t just speed; it’s knowledge. BLOX turns data into actionable intelligence. It identifies early trends such as irregular shutdowns, arcs, or temperature deviations and translates them into recommendations like adjusting warm-up routines, reducing daily cycles, or scheduling service before failures occur.
By acting on these insights, OEMs are empowered to plan maintenance in advance, shorten service visits, and reduce the mean time to repair (MTTR). End users benefit from smoother operation and more predictable uptime. The result is a shift from guesswork to governance – a process built on understanding instead of urgency.
The measurable impact of BLOX
Best practice scenarios that define the shift from reactive to preventive maintenance.
The scenarios below show BLOX’s modularity. Even when used reactively, it dramatically reduces troubleshooting time. But its real value emerges when it becomes routine – a regular, scheduled practice that enables proper preventive maintenance.
BLOX in practice
BLOX supports multiple scenarios – each showing how preventive thinking creates measurable value.
Time saved, money earned
Preventive maintenance is one of those rare strategies that saves both time and money. With BLOX, OEMs experience shorter service interventions, optimized planning, and fewer last-minute emergencies. End-users benefit from improved throughput and higher productivity.
Time saved translates directly into money earned. Preventive maintenance reduces spare part waste, improves logistics, and strengthens relationships. The service visit becomes a proactive collaboration, not a crisis response. Each saved hour compounds into better utilization, stronger reputation, and happier customers.
Latest three news
Focus topic. A conversation with Jan Bressendorff and Allen Gress about pipeline weld inspection
October 8, 2026
On a pipeline job, the X-ray system is chosen for the weld, not from a catalog. Pipe size and access determine how the crew can inspect it. The procedure sets what the image must show. Heat, weight and exposure time shape the working day. A poor choice can cost hours. A good one helps the crew get an image the inspector can assess without needless delay.
Read moreFocus topic. The HP/15 builds on two decades of proven HP/11 performance for digital detectors, in-line inspection and CT.
September 21, 2026
For two decades, the HP/11 has been the reference minifocus X-ray tube for high-resolution and high throughput radiography. The HP/15 keeps everything that made it trusted, and reengineers the rest for digital detectors, in-line inspection and computed tomography.
Read moreFrom the field. Cooler leakage with Pierre-Emmanuel Rigot at X-RIS
September 10, 2026
This is not primarily a story about a cooler leak - it is a story about what happens when insight arrives too late. About the cost of operating without remote access. About the difference between reacting to failures and preventing them. And about how weak signals only become meaningful over time when data is allowed to flow. At its core, this case shows why BLOX alone is not enough.
Read more