Skip to content
FREN

rdCoPilotAgent

SkySpark modules

The right to write to a station, granted separately.

Closing an optimization loop.

rdCoPilotAgent — At a glance
The problem it solves

On a live portfolio, analytics access can inadvertently become command access; conversely, correcting a setting on a hundred devices takes a hundred interventions.

The work it does for you

rdCoPilotAgent adds to SkySpark the gestures that modify a field station: write a value, trigger an action, create or delete a component, import and export records. It is deliberately separate from reading: one is granted without the other. Its gestures act on a real installation — a write changes a physical setpoint — and it is installed knowingly.

Benefits for you
  • The right to write is an explicit decision: installing read access does not install write access.
  • Driving from the analysis: detected drift is corrected without a third-party tool.
  • Bulk gestures become possible: described once, applied to a portfolio.
  • A readable scope: few gestures, named and documented.
  • Knowing which projects can write means looking at where this module is installed.
Use cases
  • Closing an optimization loop.
  • Deploying a seasonal setting across a portfolio.
  • Industrializing commissioning.
  • Reserving the right to write for projects that drive.
Platform

SkySpark 4.0.x / Haxall

Version

0.1.4

Price

on request

Module family

rdCoPilot

See the rangerdCoPilotrdCoPilotConn

See the energy twin at work

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