Reference · built on requestConnectorBuilding management platforms

OpenBlue Enterprise Manager

Faults, assets, spaces, energy, and time-series points from Johnson Controls OpenBlue Enterprise Manager through its Open APIs.

Request accessPricing ↗

About

OpenBlue Enterprise Manager (OBEM) is Johnson Controls' cloud-hosted building performance platform. It takes data from Metasys and other BACnet IP systems, runs rule-driven fault detection and diagnostics, and holds spaces, meters, equipment, and work orders for a portfolio. Its Open APIs share fault details with priority, duration, and diagnostics, asset details by space, energy consumption and demand, and raw or aggregated time-series points. From release 5.8 a Bulk API retrieves or sends many sensor or meter points in one call.

Through Fibric, an operator reads faults and point history from OBEM, cross-checks them with your work order system, and proposes a next step for your approval. Each proposal leaves a receipt: what changed, why, and how to undo it.

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

  • Fault details with priority, duration, and diagnostics, as shared through the Open APIs
  • Asset details associated with a space, and the space hierarchy and details for a space
  • Energy management data such as consumption and demand, per meter or space
  • Raw and aggregated data for a time-series point, queried by an ISO 8601 date-time range
  • Many sensor or meter data points in one call through the Bulk API, from release 5.8
  • Work order and ticket information normalized by the OBEM CMMS Integration Framework

Proposed actions

  • Target capability: propose sending sensor or meter data points into OBEM through the Bulk API
  • Target capability: propose a work order status update through the CMMS framework's Call back API
  • Target capability: propose creating spaces, assets, and space-asset relationships in OBEM through the CMMS framework's POST API

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 fault into a ticket that closes

    Read OBEM faults with priority and duration, match each to an open work order in your CMMS, and propose a ticket or a status sync where none exists.

    With Work Order Aging, Predictive Maintenance

  • Catch meters that stop reporting

    Pull time-series points by date range through the Bulk API, flag meters and sensors whose last sample is stale, and propose a check for your approval.

    With Data Freshness, Sensor Health

  • Reconcile demand against the bill

    Read consumption and demand per meter from OBEM, compare with utility interval data, and propose an adjustment where the two disagree.

    With Bill Reconcile, Submeter Drift

Requirements

  • An OpenBlue Enterprise Manager subscription; data sharing is controlled by tier, throughput, frequency, and volume
  • Sites onboarded to OBEM through OpenBlue Bridge or a BACnet IP source such as Metasys
  • A Bulk API entitlement; new customers receive Bulk API access only
  • API credentials issued by Johnson Controls for your OBEM instance
Authentication
API access provisioned by Johnson Controls with your OBEM subscription; the product bulletin does not publish the credential scheme, so it is confirmed per deployment.

Limits

  • The product bulletin lists what the Open APIs share but does not publish endpoint paths, schemas, or rate limits
  • Data sharing is metered by tier, throughput, frequency, and volume; the Bulk API is the only path for new customers
  • OpenBlue Bridge supports Modbus, OPC-UA, MQTT, and BACnet/IP, but only BACnet is listed as validated with OBEM
  • Fault-to-work-order flows run through the CMMS Integration Framework, which is set up per CMMS vendor

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 OpenBlue Enterprise Manager ↗

Questions and answers

Which OBEM data can the Open APIs share?
Fault details with priority, duration, and diagnostics; asset details by space; energy consumption and demand; raw and aggregated time-series point data; and the space hierarchy. Johnson Controls also describes exposing fault APIs to a third-party CMMS and pushing data to your data lake.
What is the Bulk API?
From release 5.8, a Bulk API retrieves or sends many sensor or meter data points in a single call. It accepts ISO 8601 date-time inputs and returns only the requested range. New customers get Bulk API access only; existing customers were given a six-month transition.
Does this connector command equipment?
No. It proposes data uploads, work order status syncs, and space or asset records through OBEM's documented APIs. OBEM's own Command and control features, including alarms and control over OPC-UA, are outside this listing, and equipment commands stay with your BMS.
Ask about OpenBlue Enterprise Manager

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 OpenBlue Enterprise Manager 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