Reference · built on requestConnectorBuilding management platforms

Optergy Enterprise

Trend logs, energy logs, meters, alarms, and schedules from an on-premises Optergy Enterprise building management server.

Request accessPricing ↗

About

Optergy Enterprise is web-based building management software that runs on your own physical or virtual machine with a PostgreSQL database. It speaks BACnet IP, BACnet MS/TP, Modbus TCP/IP, and Modbus RTU, and is licensed by device, with 150 devices in the base licence. It manages BACnet alarms (Event Enrolments), schedules, calendars, trend logs, and notification classes, keeps meter parameters as BACnet points, and runs demand limiting, Optimum Start, and tenant billing. An Application Program Interface Module is a separate licence option for third-party integration of trend logs, energy logs, users, and groups.

Through Fibric, an operator reads trend and energy logs and alarm records from the server and proposes a next step for your approval. Every proposal leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Optergy Enterprise 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

  • Trend logs, including BACnet-compliant trend logs, with their intervals and retention settings
  • Energy logs and meter parameters for physical, virtual, calculation, and manual meters, kept as BACnet points
  • BACnet alarms (Event Enrolments), notification classes, and alarm escalation state
  • BACnet schedules and calendars, including holiday and special-event schedules
  • Demand limiting points and Optimum Start areas, up to 50 of each in the base licence
  • Users and groups, which the API module lists alongside trend and energy logs

Proposed actions

Read-only. Actions need a separate connector.

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

What you can build

  • Spot a meter that stops counting

    Read energy logs per meter, compare each against its recent pattern, and propose a check when a meter goes flat or jumps.

    With Submeter Drift, Sensor Health

  • Audit after-hours running against the calendar

    Read BACnet schedules and trend logs together, find equipment running outside its calendar, and propose a schedule correction for your approval.

    With After-Hours Audit, Schedule Leak

  • Triage alarms before escalation fires

    Read Event Enrolment alarms and their escalation state, group repeats by device, and propose which to acknowledge first.

    With Alarm Triage, Alarm Flood

Requirements

  • An Optergy Enterprise server on your LAN or WAN, on a physical or virtual machine
  • The Application Program Interface Module licence (licence code API), sold apart from the base licence
  • Network reach to the server; Optergy specifies its on-board VPN for access over the internet
  • A device licence count that covers every BACnet and Modbus device you want read
Authentication
Credentials for the licensed Application Program Interface Module on your Optergy Enterprise server; Optergy does not publish the token scheme on optergy.com.

Limits

  • Optergy publishes a datasheet and a guide specification for the Enterprise API module, not an endpoint reference
  • The API module covers trend logs, energy logs, users, and groups; no write operation is documented, so this listing is read-only
  • Optergy's published REST document (JWT bearer tokens, POST /authorize) is for the P864 controller, not the Enterprise server
  • The server is on-premises; there is no vendor cloud endpoint to call

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 Optergy Enterprise ↗

Questions and answers

Which protocols does Optergy Enterprise speak?
BACnet IP and BACnet MS/TP at BACnet protocol revision 14, plus Modbus TCP/IP and Modbus RTU. Modbus devices are converted to BACnet objects, and each BACnet or Modbus device counts once toward the device licence regardless of its point count.
Is the API included in the base licence?
No. The datasheet lists the Application Program Interface Module as a licence option with its own code, API. The base licence covers 150 devices, an unrestricted number of users and groups, BACnet and Modbus, reports, and live and scrolling displays.
Can Fibric write set points through this connector?
Not through the API module, which Optergy documents for trend logs, energy logs, users, and groups. Optergy Enterprise itself writes to writeable BACnet points and exposes meter parameters as BACnet points, so a BACnet connector is the path for any write.
Ask about Optergy Enterprise

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 Optergy Enterprise 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