Reference · built on requestConnectorBuilding management platforms

SkySpark

Sites, equipment, points, and histories from SkySpark through the Project Haystack HTTP API, with pointWrite and Axon eval.

Request accessPricing ↗

About

SkySpark is SkyFoundry's analytics platform for building and equipment data. It stores tagged records and histories in its Folio database, runs Axon rules that raise sparks, and clusters nodes with Arcbeam. SkySpark is a native Haystack server, so the whole system is reachable through the Project Haystack HTTP API at /api/{project}/{op}: read by filter or id, hisRead over a range, watchSub and watchPoll for current values, pointWrite to a priority array, and eval to run an Axon expression.

Through Fibric, an operator reads points and histories from a SkySpark project, checks them against sparks and schedules, and proposes a point write or an Axon evaluation for your approval. A receipt records what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from SkySpark and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Sites, equipment, and points read by Haystack filter or by id through the read op, with an optional limit
  • Point histories through hisRead, with ranges such as today, yesterday, a date, or a date-time pair
  • Current curVal and curStatus through watchSub, watchPoll, and watchUnsub, keyed by watchId and lease
  • Project navigation and definitions through nav, defs, libs, ops, and filetypes
  • Sparks and rule results returned by eval of an Axon expression, converted to a grid
  • Priority-array state of a writable point: level, levelDis, val, and who from a pointWrite read

Proposed actions

  • Target capability: propose a pointWrite with id, level (1 to 17), val, who, and an optional duration at level 8
  • Target capability: propose an Axon expression through eval, sent as the request grid's single expr column
  • Target capability: propose hisWrite of timestamp and value samples to a historized point
  • Target capability: propose invokeAction on a target record

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Turn a spark into an approved fix

    Read sparks through eval, pull the point history behind each with hisRead, and propose a pointWrite or a work order with the evidence attached.

    With Predictive Maintenance, Economizer Check

  • Hold set points where they belong

    Watch zone set points and curVal through watchPoll, compare to the schedule, and propose a pointWrite at level 8 with a duration so the override expires.

    With Setpoint Drift, Comfort Complaint

  • Peak demand with the plant in view

    Read meter histories and chiller points, project the interval peak, and propose a staged sequence of point writes for your approval.

    With Peak Demand, Chiller Sequencing

Requirements

  • A SkySpark instance you administer, and the project name that forms the /api/{project} path
  • A SkySpark user for the connector with read access to the project and, for writes, permission on the target points
  • HTTPS reach to the SkySpark node from wherever the connector runs
  • Points tagged writable for pointWrite and his for hisRead, per the Haystack point model
Authentication
The Haystack authentication protocol: a HELLO handshake, then SCRAM (SHA-256 or SHA-512) or PLAINTEXT over TLS, which yields a bearer authToken sent in the Authorization header.

Limits

  • A Haystack server may cap what one request returns; the spec calls this incomplete data, and the fix is a narrower filter
  • SkyFoundry's product documentation sits behind a login; this listing is written from the Project Haystack specification and SkyFoundry's public pages
  • eval runs any Axon expression, so it is proposed with the exact expression shown for approval, never free-form
  • Zinc is the default encoding; JSON needs an application/json or application/vnd.haystack+json Accept header

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request SkySpark ↗

Questions and answers

Which Haystack ops does SkySpark expose?
SkyFoundry describes SkySpark as a native Haystack server, so the standard ops apply: about, close, defs, libs, ops, filetypes, read, nav, watchSub, watchUnsub, watchPoll, pointWrite, hisRead, hisWrite, and invokeAction. SkySpark adds eval for Axon expressions at /api/{project}/eval.
How does a pointWrite work?
The request grid carries id, level (1 to 17, where 17 is default), val (null to auto), an optional who, and a duration for level 8 manual overrides. Sending only id returns the priority array: level, levelDis, val, and who.
How does the connector authenticate?
With the Haystack auth protocol. The client sends HELLO with a base64url username, the server names its mechanisms, SCRAM completes the exchange, and the server returns an authToken in Authentication-Info. Later requests carry it in a BEARER Authorization header.
Ask about SkySpark

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with SkySpark through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy