Skip to content
FREN

rdCoPilotConn

SkySpark modules

A Niagara station becomes an ordinary SkySpark connector.

Analysing a Niagara portfolio in SkySpark.

rdCoPilotConn — At a glance
The problem it solves

Linking a Niagara BMS to SkySpark used to be a project: an integration layer to develop, a parallel tool that ends up diverging, and diagnosis done somewhere other than where the operator looks.

The work it does for you

rdCoPilotConn plugs a Niagara 4 station into SkySpark like any other connector, with the gestures and connection states the operator already knows. Once the connection is created, you check the station's health and bring its points' history into SkySpark, with no development. This module reads: writing to the station belongs to a separate module, by design.

Benefits for you
  • No integration layer to develop.
  • The gestures the operator already knows: nothing to learn.
  • No parallel tool to maintain.
  • History arrives where the analysis happens: rules, reports, dashboards.
  • Connection diagnosis sits on the screen the operator already watches.
Use cases
  • Analysing a Niagara portfolio in SkySpark.
  • Supervising several sites from one screen.
  • Preparing energy tracking.
  • Replacing an ageing integration.
Platform

SkySpark 4.0.x / Haxall

Version

0.8.4

Price

on request

Module family

rdCoPilot

See the rangerdCoPilotrdCoPilotAgent

See the energy twin at work

In a demo: its baseline and the detection rules applied to anonymized data.