Predictive maintenance is led by an IT incident platform and six Amazon services

Predictive maintenance is led by an IT incident platform and six Amazon services

The Predictive Maintenance use case is about machines: sensor and telemetry history, remaining-useful-life models, and work orders triggered by prediction rather than schedule. It lists 13 providers and 49 APIs. The only exemplar is an IT operations platform, six of the next seven are Amazon services, and the companies that build the equipment are at the bottom.

Who the use case ranks

Provider Kin Score Band APIs
BigPanda 70.3 exemplar 29
Amazon FreeRTOS 65.9 strong 1
Amazon SageMaker 65.9 strong 1
Amazon Lookout for Equipment 53.9 developing 1
Amazon IoT FleetWise 52.9 developing 1
Amazon IoT Events 51.5 developing 1
Amazon Monitron 47.6 developing 3
AGCO 43.8 developing 3

BigPanda correlates monitoring alerts into incidents. That is failure prediction for software estates, not for pumps and bearings, and its 29 APIs carry most of the use case’s 49. Remove it and the use case is almost entirely AWS.

The equipment makers

The companies whose machines need maintaining are where the use case thins out:

  • CAT (Caterpillar): 31.4, thin, 1 API
  • Baker Hughes: 28.6, thin, 2 APIs
  • Bosch: 13.8, emerging, 5 APIs

AGCO, the agricultural machinery maker behind Fendt and Massey Ferguson, is the one manufacturer in the developing band. Two of the 13 entries, Anomaly Detection at 45.5 and Industrial at 9.7, are topic collections, not companies. That leaves 11 providers you could actually sign a contract with.

A build path from what is here

The catalog supports one realistic path, and it runs through AWS:

  1. Collect device telemetry with Amazon FreeRTOS on the edge, or IoT FleetWise for vehicles.
  2. Detect with Amazon Monitron or Lookout for Equipment for rotating equipment, or train your own model in SageMaker.
  3. React with IoT Events, which detects and responds to events from sensors and applications.
  4. Route what matters to people through an incident layer such as BigPanda.

The manufacturer side, the asset records and service history that tell you what a machine is and what was last done to it, is where the catalog has the least. For fleets, the Fleet Maintenance Management capability fills some of that gap with work-order and inspection APIs.

What the raw terms say

The use case was built from five raw terms, including “Predictive Maintenance for Rotating Equipment” and “Manufacturing Predictive Maintenance”. The demand is industrial. The supply that publishes contracts is cloud. If you make equipment and publish an API for its condition data, there is very little competition on this page.

← HERE vs Entur, sixty points of access clarity against forty-five of governance
Rail on apis.io is a freight vertical led by a travel agency and a regulator →