#

Closing the Data Gap Between Industrial IoT and Asset Management

By Kendall Kunz, Chief Revenue Officer at Appenate.

Sensors cover what they were built to measure. What people find on inspection rounds can stop short of the asset record.

In 2002, an inspector at Chevron’s refinery in Richmond, California, identified corrosion on a 52-inch-long section of piping in the crude unit. By then it had lost about a third of its wall thickness. The finding went into the inspection database only as a note. It was never entered as monitoring data, and no condition monitoring location (a designated spot where wall thickness is measured at intervals) was added for that section. “As a result, the 52-inch component was never inspected again,” the U.S. Chemical Safety Board concluded in its 2015 final report.

Turnaround planners later rejected recommendations to inspect every component of that piping or replace it. Chevron relied on existing data for replacement decisions, in the board’s account. The recorded data on that piping came only from high-silicon components that corroded far more slowly than the section that failed. On August 6, 2012, that section ruptured. The release formed a vapor cloud that engulfed 19 employees and ignited about two minutes later. Eighteen escaped before ignition; the 19th, a refinery firefighter caught in the fireball, got through the flames. Six employees had minor injuries.

The board traced the rupture through several decisions. One part of its account reaches well beyond refineries: the 2002 finding existed, but not in the data that later decisions ran on.

Industrial IoT programs can have the same seam. Picture sensor readings stored against an asset tag, and an inspection round that ends as a checklist, a photo or a note on a work order. That inspection reaches the asset record only if something carries it there.

What Sensors See and What They Miss

A fully instrumented machine can tell you it stopped, but not why, because the cause usually lies outside the machine. A piece IoT Business News ran in September 2026 made that point from one company’s experience, where an operator supplies the answer by tapping a reason into a tablet. Its wider argument was that the real constraint in industrial IoT is how many machines a data point can reach.

For physical assets, inspection findings play the operator’s part. A sensor, like a monitoring location, covers the spot where someone put it. At Richmond, no monitoring location sat on the section that failed, and an inspector identified its corrosion on an extra round of piping inspection. Sensor readings and inspection findings describe the same asset, and nothing guarantees they land in the same record.

Where the Handoff Breaks

Maintenance work-order text is often unstructured, with technical jargon, typos and shorthand, as researchers at the National Institute of Standards and Technology (NIST) describe it. Their research looks at work orders rather than inspection notes, but it’s a fair warning for both. They also see the information in such documents as underused in analysis.

Buying a computerized maintenance management system (CMMS) doesn’t fix that by itself. In the words of a NIST-led paper, “simply using a work order generated by a CMMS does not by any means guarantee high quality data.”

The form matters too. Data entry is especially error-prone when a form’s categories don’t fit the way a technician needs to describe the fault, a NIST paper argues from cognitive models and industry accounts.

Information that doesn’t travel between systems has a price. A 2004 report prepared for NIST estimated it for U.S. capital facilities at $15.8 billion in 2002. Owners and operators bore two-thirds, mostly during operation and maintenance. Their largest single item was an estimated $4.8 billion in labor spent checking that information matched what was in place. Those figures are two decades old and cover far more than inspections.

What Changes When the Two Are Captured Together

Capture each inspection as data about a specific asset, in terms the rest of the stack already uses. Five changes put that into practice.

Key every finding to the asset’s ID. The U.S. Occupational Safety and Health Administration’s Process Safety Management (PSM) standard already asks for most of the record on the processes it covers, and its equipment list includes monitoring devices and sensors. Each inspection or test must be documented with the date, who did it, the equipment’s serial number or other identifier, what was done and the results. Use the identifier your CMMS and sensor platform already hold for that asset, and the result can sit beside its trend. Table 1 maps each field.
Structure what you’ll count. ISO 14224 sorts reliability and maintenance data into equipment, failure and maintenance categories, in a standard format meant for exchange between plants, owners, manufacturers and contractors. It was written for petroleum, natural gas and petrochemical facilities. Even outside those industries, its split is a useful template for an inspection form. Keep a free-text field for what fixed choices can’t hold.
Let a finding change the plan. A finding that shows a spot needs watching should add it to the monitoring plan, the step the 2002 finding at Richmond never triggered. It can also shorten the interval there. PSM itself calls for more frequent inspection where prior operating experience shows the need. A finding outside acceptable limits should open corrective work. Where PSM applies, such deficiencies must be corrected before further use, or on a safe and timely schedule where other measures keep operation safe.
Map to a published standard. The Common Conceptual Object Model (CCOM) from MIMOSA, a not-for-profit industry association, is an information model built so that systems can exchange asset lifecycle data electronically. IEC 62264-1 describes how manufacturing operations and enterprise systems connect. A mapping built on either gives the next system something it can read.
Capture it at the asset. Every copy from one form to another is one more handoff. A record that starts at the equipment should already carry the asset ID, the checklist and the readings, in whatever format the plant uses. Where that’s a mobile form, options range from in-house builds to off-the-shelf tools; Appenate, the author’s company, offers mobile inspection checklists for field service teams.

Table 1. What a PSM inspection record must carry, and what each field should match

Field the PSM rule requires
Capture it as
Match it to

Date of the inspection or test
A timestamp set by the device
The sensor platform’s time base

Name of the person who did it
A user ID
The maintenance system’s user list

Serial number or other identifier of the equipment
The asset ID, scanned or picked
The asset record in the CMMS or asset management platform, and its sensor tags

Description of the inspection or test
An inspection type from a fixed list
The inspection plan and its monitoring locations

Results
Readings in fields, a note, photos
Acceptable limits, so an out-of-limit result opens corrective work

Where to Start

Start with inspections that already leave a regulated record, such as those under PSM or the U.S. EPA’s Spill Prevention, Control, and Countermeasure (SPCC) rule. SPCC inspection records must be signed by the supervisor or inspector and kept for three years. The rule accepts records kept under usual and customary business practices, so the format is the plant’s choice.

Pick one asset class and open a recent inspection record. Can you find it from the asset’s page in the CMMS? Can you find it from the asset’s sensor tag?

If either answer is no, that’s the gap. At Richmond, the 2002 finding stayed a note, and the section it described was never inspected again. Closing the gap starts with the next inspection on that asset class, keyed to the identifier the CMMS and sensor platform already hold.

The post Closing the Data Gap Between Industrial IoT and Asset Management appeared first on IoT Business News.

Generated by Feedzy