Companion specification · Tier 2

MDIS

Version1.3
Published2024-11
SectorSubsea oil and gas

The MDIS model, at 1.3 as of November 2024, covering subsea instrumentation and control interfaces for oil and gas. A narrow, mature, well-adopted model within its industry, which distinguishes it from most Tier-2 entries here.

Where it sits in the stack

Built on the core information model. MDIS is a registered capability code.

The types that matter

TypeWhat it carries
(type inventory not confirmed)We have not verified the type inventory. Browse the released nodeset.

Using it on a real machine

  1. Check the capability codeA server claiming MDIS is exposing subsea control interface structure.
  2. Expect a distinct engineering cultureSubsea control has its own safety, redundancy and change-control practice. OPC UA integration here is subject to it.
  3. Note the maturityUnlike many sector models, MDIS has real industry adoption and an active revision history.

What it gives you for OEE

OEE as manufacturing understands it does not apply to subsea production. Availability of equipment matters enormously, but the calculation and the economics are entirely different. Do not port a manufacturing OEE model here.

Try it free: No free public server exposes this model as far as we know. To see it you need a machine that implements it or a vendor demo. If you find a public endpoint, tell us and we will add it.

Gotchas

  • Manufacturing OEE concepts do not transfer to subsea production. Different economics, different availability definitions.
  • Safety and redundancy requirements dominate the engineering, and they constrain integration.
  • Genuinely mature and adopted within its industry, unlike many sector models.
Verify before you rely on this: We have not verified the type inventory. The type inventory on this page is deliberately short. We list only type names we are confident of and would rather publish five correct ones than twelve with four wrong. Browse a real server or the released nodeset for the complete list.
Related models

Once the machine speaks a companion spec, the OEE mapping is portable across vendors, which is the point at which analytics stops being a per-machine project.

See Jemba →

Last verified 7 September 2026 against OPC UA 1.05.07. Version and publication date read from the released nodeset. OPC UA Connect is an educational resource and is not affiliated with the OPC Foundation.

Free download
OPC UA Machine Data → OEE Mapping Kit
Which nodes to subscribe to, how they become Availability, Performance and Quality, and which companion specification already gives you the answer, so you stop inventing tags.
Get the free mapping kit →
Free, no course, no login