rdModel

A component tree does not say what is a site, a space or a piece of equipment: every tool — analytics, reporting, CMMS — redescribes the portfolio its own way, and a house nomenclature does not pass to a successor.

rdModel adds a layer of meaning to a Niagara station: it distinguishes sites, spaces and equipment, and attaches each piece of equipment to a definition — its type, its make, its model. That structure follows a recognized ontology (Haystack or Brick) and becomes portable: it exports, versions and travels from one station to another. The value rests on modelling the portfolio, which is the real investment.

• A portfolio described once, usable everywhere: navigation, reports, exchanges with third-party tools.
• A type can change without reworking the portfolio: equipment and its definitions stay distinct.
• A standard, not a house convention: the model passes to a partner or a successor.
• The model versions: you see what changed, when, and you can roll back.
• It travels between stations instead of being re-entered site by site.

• Preparing a portfolio for analytics.
• Delivering a model with the installation.
• Deploying a site standard.
• Tracking a portfolio's evolution since commissioning.

Niagara ≥ 4.13.x

0.16.2

on request

rdModel & rdOntology

See the rangerdOntologyrdHierarchy