IoT & Edge IoT Platforms & Analytics

Linking Industrial IoT Sensors With Inspection and Asset Records

Industrial IoT systems can collect detailed measurements from equipment while leaving important inspection findings outside the records used for maintenance and operating decisions. The gap is not necessarily a lack of data: it can arise when observations made by people are recorded in a checklist, photograph or work-order note that is not connected to the asset’s sensor history or maintenance plan.

Kendall Kunz, chief revenue officer at Appenate, makes that case using the 2012 Chevron refinery fire in Richmond, California. The U.S. Chemical Safety Board’s 2015 final report found that an inspector had identified corrosion on a 52-inch section of crude-unit piping in 2002. The observation was entered as a note, but not as monitoring data, and no condition-monitoring location was established for that section. The board concluded that the component was never inspected again.

The piping section later ruptured on August 6, 2012. The release engulfed 19 employees and ignited about two minutes later; six employees sustained minor injuries. The board described multiple decisions and contributing factors in its investigation. The data-handling issue illustrates a broader operational risk: a finding can exist, yet remain unavailable to the systems and processes that guide later inspection and replacement decisions.

Two views of the same asset

Sensors measure what they are installed to measure. They can report a condition or change at a monitored location, but they do not necessarily capture an inspection observation or explain the cause of a fault. Inspectors, in turn, may record findings in forms or work orders that do not connect to sensor readings or the asset’s maintenance record.

That makes the handoff between systems as important as the collection of data. An asset tag may identify equipment in an IoT platform, while a technician’s note uses shorthand or a different identifier. Even when a computerized maintenance management system (CMMS) is in place, the system alone does not ensure that records are complete, consistent or usable. Research by the National Institute of Standards and Technology (NIST) has highlighted the challenges posed by unstructured maintenance text and by forms whose categories do not fit the way technicians describe problems.

Information that cannot be readily reconciled can also create work for asset owners. A 2004 report prepared for NIST estimated that poor interoperability cost U.S. capital facilities $15.8 billion in 2002, with owners and operators bearing about two-thirds of the total. The estimate covered a broad range of information-management problems, not inspections alone, and is now more than two decades old.

Make findings usable across systems

Kunz recommends treating inspections as structured data about a specific asset, while retaining room for observations that do not fit predefined choices. Several established frameworks and requirements can help plants organize that information:

  • Use the asset identifier already recognized by the CMMS and sensor platform. For processes covered by OSHA’s Process Safety Management (PSM) standard, inspection and test records include the date, the person performing the work, an equipment identifier, a description of the inspection or test, and its results.

  • Structure common fields using a consistent taxonomy. ISO 14224 organizes reliability and maintenance data into equipment, failure and maintenance categories. It was developed for petroleum, natural gas and petrochemical facilities, though its categories can provide a reference beyond those sectors.

  • Connect findings to the inspection plan. If an observation indicates that a location should be monitored, the maintenance process should be able to add it to the plan or adjust the inspection interval. Findings outside acceptable limits can trigger corrective work, subject to applicable safety requirements.

  • Map records to information models or standards that support exchange. MIMOSA’s Common Conceptual Object Model (CCOM) addresses electronic exchange of asset lifecycle information. IEC 62264-1 describes connections between manufacturing operations and enterprise systems.

  • Capture information at the equipment where practical. A mobile form can record the asset ID, inspection type, readings and supporting notes or photographs at the point of work, reducing repeated transfers between forms and systems.

These measures do not guarantee that every observation will be interpreted correctly or lead to the right maintenance decision. They can, however, make a finding easier to locate alongside the asset’s history and give downstream systems a more consistent record to work with.

Start with a defined asset group

Plants can begin by reviewing an inspection record that already has regulatory requirements, such as one covered by PSM or the U.S. Environmental Protection Agency’s Spill Prevention, Control, and Countermeasure rule. Under SPCC, inspection records must be signed by the supervisor or inspector and retained for three years; the rule allows records to follow usual and customary business practices.

A practical test is to select an asset class and try to retrieve a recent inspection from both the asset’s CMMS page and its sensor record. If the finding cannot be found through either route, the organization can examine where the identifier or information handoff is missing. Connecting the next inspection to the identifier shared by asset-management and IoT systems is a concrete first step toward closing that gap.