Six industries, one layer underneath.

An industry is where the work happens. The environments inside it are how it runs.

Each industry is set out through the environments inside it: the workloads in play, the shapes the data takes, and the parts of the layer that carry them.

6 industries · 33 environments
Industrial Financial Services Enterprise & Commerce Science & Health Infrastructure & Technology Public & Sovereign

One data layer

Six industries, one layer. The settings differ; the system underneath does not.
The industry map

Choose an industry. See where it runs.

Each industry is a destination of its own, and each one is described by its data: the environments inside it, the workloads in play, the shapes that data takes, and the parts of the layer that carry them.

PLOMID data layer

Where it runs

Industrial

The operating environments inside this industry. Each is a variation on one problem: a measurement stream that never stops, and records that have to stay accurate beside it.

Open the Industrial page
Data shapes
  • Time series Measurements and events in time order
  • SQL Records, keys and joins
  • Events Operational events as they happen
  • JSON / documents Documents and nested objects
  • Objects Large assets with queryable metadata
  • Graph Relationships and traversal
Workloads
  • Production telemetry Oil & Gas
  • Well and asset records Oil & Gas
  • Operational events Oil & Gas
  • Survey and maintenance documents Oil & Gas
  • Fleet and plant telemetry Mining

How capability is described across the platform

The relationship

Industry, workload, shape, solution.

The industry is context; the workload is the thing being solved. Three chains, read left to right, each ending on the solution that carries it.

Data vocabulary

Nine shapes, one layer.

Every industry page is described in this vocabulary: what the data is, and the mark that identifies it. Eight of the nine are data models; the ninth, events, is a workload shape rather than a model.

  • Available

    SQL

    Records, keys and joins

  • Available

    JSON / documents

    Documents and nested objects

  • Roadmap

    Key-value

    Direct access by key

  • Available

    Time series

    Measurements and events in time order

  • Roadmap

    Geo

    Location as a queryable dimension

  • Available

    Vector

    Similarity and semantic retrieval

  • In development

    Graph

    Relationships and traversal

  • In development

    Objects

    Large assets with queryable metadata

  • Workload shape

    Events

    Operational events as they happen

Where the work happens

Your operation is a data problem before it is a tooling one.

Tell us what the environment produces, how fast it moves and who asks questions of it. We will map it to the workloads, the shapes and the parts of the layer that carry them.