Skip to content

Sample Template for an MO-oriented Machine Details Page

This chapter provides a sample template for a machine details page that visualizes the data most commonly of interest to machine owners across OEMs and industries.

A Foreword on Standard Signals

Proemion recommends a set of Proemion Standard Metrics with defined semantics, so that all stakeholders understand what a signal represents and the unit it uses to express its magnitude.

For example, many machines track the total distance traveled. Naming this signal distance_traveled and expressing it in leagues, which isn't a standard metric or imperial unit, still delivers the metric to the DataPortal, but prevents users from:

  • Selecting their preferred unit system, metric or imperial, and getting the value accordingly.
  • Delivering cumulative distance traveled data in an ISO 15143-3 (AEMP) compliant format.
  • Using the metric in the Machine Companion App, see Machine Companion App (Google Play).

Using the standard value.common.machine.distance.total signal key, the length.KILOMETER unit, and the counter signal type (see PDC Value Definition) instead lets the platform:

  • Support the signal automatically in the Machine Companion App.
  • Represent the values in both supported unit systems, converting between them automatically.
  • Make the signal immediately available through the AEMP API without additional configuration, if a user wants to export their machine data that way.

Using standard signals means many DataPortal features work out of the box, and new features become available as they ship, without extra configuration effort.

This guide uses a subset of standard signals that applies to most machines across industries, to illustrate a minimal configuration for machine details pages focused on the interests of a machine owner:

  • Location (degrees): value.common.machine.geo.latitude, value.common.machine.geo.longitude
  • Fault codes: value.common.machine.caution.code, value.common.machine.diagnostic.trouble.code
  • Total distance traveled (kilometers): value.common.machine.distance
  • Total operating hours (hours): value.common.machine.hours.operation.total
  • Total number of loads, for example for earth moving machines or elevator platforms: value.common.machine.load.count.total
  • Total weight loaded (kilograms): value.common.machine.load.total
  • Current diesel exhaust fluid level: value.common.engine.def.level
  • Current fuel level: value.common.engine.fuel.level
  • Current oil level: value.common.engine.oil.level
  • Total fuel used (liters): value.common.engine.fuel.used.total
  • Machine speed (kilometers per hour): value.common.machine.speed
  • Engine speed (revolutions per minute): value.common.engine.speed

Tip

In the DataPortal, go to Settings > Machine Data Management > Signal Catalog to check how many of the standard signals your fleet already covers. Covering all standard signals isn't required. Covering a few of the core signals listed above already unlocks most of the platform's potential.