Companion specification · Tier 2

LaserSystems

Version1.0.0
Published2024-02
SectorLaser systems

The laser systems model, published in 2024. Laser sources and systems appear inside cutting, welding and marking machines, so this model is often a component of a larger integration rather than the whole of one.

Where it sits in the stack

Built on the Machinery building blocks and the Device Information Model. Frequently found alongside MachineTool, where the laser is a subsystem of the machine.

The types that matter

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

Using it on a real machine

  1. Establish whether the laser is the machine or a componentThis changes the integration completely. A laser inside a cutting machine is a subsystem; a standalone marking system is the machine.
  2. Look for MachineTool alongside itOn laser cutting machines you may find both models, with MachineTool describing production and LaserSystems describing the source.
  3. Track source conditionLaser source hours and condition are maintenance data, and they are the kind of thing that predicts a stoppage before it happens.

What it gives you for OEE

Mostly condition and maintenance data rather than production data. Source hours and condition feed maintenance planning; production counts come from MachineTool or the Machinery counters where the laser is part of a larger machine. Useful for explaining a category of unplanned downtime rather than for computing OEE directly.

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

  • Often a subsystem rather than the machine. Work out which before designing the integration.
  • May coexist with MachineTool on the same server, describing different aspects.
  • Published 2024, implementations still maturing.
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.

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