rdOntology

The mapping between a piece of business equipment and its Niagara components is recoded on every project, differently each time: twenty sites, twenty tagging conventions.

rdOntology translates an equipment's business description into real Niagara components: the right type and the right set of tags. When a deployment describes an "air handling unit" or a "chiller", the station creates what is needed, tagged as it should be. The mapping lives in a library, checked by the station before use, not in a project's code; writing that library is upstream work that conditions the result.

• No mapping hand-written on every project.
• The same description produces the same components on every station: a portfolio comparable with itself.
• The rule is governed: what structures the portfolio cannot be changed quietly.
• Libraries stack — standard base, manufacturer, client — instead of variants to maintain.
• The description stays in business terms: the integrator talks equipment, not Niagara types.

• Industrializing a multi-site portfolio.
• Integrating a manufacturer catalogue.
• Enforcing a tagging convention by construction.
• Replaying a deployment on a new station.

Niagara ≥ 4.13.x

0.3.2

on request

rdModel & rdOntology

See the rangerdModelrdHierarchy