Manufacturing
Site, area, line, cell, equipment
The manufacturing template follows ISA-95, so the structure is the one your engineers and your MES already use. Failure coding follows ISO 14224, which means the maintenance data that comes out is comparable rather than free text.
What the template gives you
A domain template is a starting hierarchy, a set of asset types and a failure vocabulary, so the first week is spent checking a model rather than inventing one.
ISA-95, not our own invention
Site, area, production line, work cell, equipment. Standard levels, so the model transfers to the people who have to live in it.
Failure coding that is enforced
Detection method, failure mode, mechanism and cause on every job, against a vocabulary the server validates. An out-of-vocabulary code is rejected, not quietly stored, which is the difference between reliability data and a text box.
Down to the sensor channel
The hierarchy does not stop at the machine. A channel on a vibration sensor is a node like any other, so a reading has a home.
Availability where you need it
Reliability figures roll up the structure you defined, per cell, per line, per plant, rather than a fixed three-level model.
What it does not do
This sits above your control layer and never inside it. It does not actuate, it is not a historian replacement for high-rate process data, and it does not speak OPC-UA. The protocol most often asked for here. If the requirement is to pull tags straight off a PLC network at scale, say so early.
Bring one line
Model a single production line and see whether the failure coding tells you something your current system does not.