Reference · built on requestConnectorBuilding management platforms

Kaizen

Buildings, systems, BACnet objects, insights, and trend-log data from CopperTree Analytics' Kaizen through its public API.

Request accessPricing ↗

About

Kaizen is CopperTree Analytics' cloud building analytics platform, fed by CopperCube collectors on BACnet networks. Its public API has two halves. JWT-authenticated endpoints under /api/v3 and /yana return buildings, systems, objects (AI, AO, BI, BO, AV, BV, MI, MO, BT, TL), and Insights raised by rules, with insight history and class ids such as Fault Detection and Energy. Kaizen Key endpoints under /public_api/api return trend-log samples for a tl reference between a start and end time, raw or aligned to 5-minute intervals, and values from a rule instance's logic blocks.

Through Fibric, an operator reads active Insights and the trend logs behind them and proposes a next step for your approval. Each proposal is recorded: what changed, why, and how to undo it.

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

  • Buildings under your client tree through GET /api/v3/buildings, with id, location, and square footage
  • Systems in a building in raw, grouped, or tree format through the System API
  • Objects by building and object_type (AI, AO, BI, BO, AV, BV, MI, MO, BT, TL) through /yana/mongo/objects/
  • Insights per building through /yana/rulestate/public-api/v1/insights/{building_id}, 500 per call, filterable by state
  • Insight history through /yana/rulestate/public-api/v1/insight-history/{insight_id}
  • Trend-log samples through get_tl_data_start_end with tl, start, end, and data=raw or align
  • Values from a rule instance's logic blocks through get_instance_values, aggregated at an interval such as Daily

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

  • Act on an Insight before it ages

    Read active Insights with priority and class, pull the trend log behind each, and propose a work order or an acknowledgment with the evidence.

    With Alarm Triage, Predictive Maintenance

  • Find outputs left in manual

    Read Infrastructure insights such as a commissioned output commanded to Manual, check how long each has been active, and propose a release for your approval.

    With After-Hours Audit, Setpoint Drift

  • Watch energy KPIs by building

    Pull Energy and Energy KPI insights and rule-instance values at Daily interval, compare buildings, and propose where to look.

    With Site Benchmark, Submeter Drift

Requirements

  • A client_id and client_secret issued by CopperTree Customer Solutions for each Kaizen instance you access
  • A Kaizen user whose profile Kaizen Key is used for the trend-log and rule-instance endpoints
  • Building ids from Kaizen URLs and trend-log references in building.device.TL form, such as 2914.123.TL45
  • The right regional host: kaizen.coppertreeanalytics.com (Central) or kaizen-east.coppertreeanalytics.com (East)
Authentication
A machine-to-machine JWT from POST /oauth2/token on login-ca-central-prod or login-us-east-prod with client_credentials, sent as a Bearer header; trend-log endpoints take the user's Kaizen Key as api_key.

Limits

  • JWT tokens expire and must be regenerated every 30 days; different Kaizen instances need different client ids and tokens
  • Pagination: page size defaults to 50 with a maximum of 1000, and insights return 500 per call
  • All documented endpoints read; CopperTree publishes no write endpoint, so this listing is read-only
  • Trend-log data is what CopperCube samples; Kaizen does not accept samples faster than 1 minute

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 Kaizen ↗

Questions and answers

Which authentication does each Kaizen endpoint use?
Buildings, systems, objects, and insights take a Bearer JWT from the client-credentials token endpoint. Trend-log series and rule-instance values take the Kaizen Key from your user profile as an api_key query parameter, and the trend-log list takes it as an Authorization: token header.
What is an Insight?
A record raised by a Kaizen rule against a building's data. Each carries an insight_class_id and name (Alarm 1, Notification 2, Fault Detection 3, Energy 4, KPI 8, Infrastructure 11, among others), a priority_id, a state of active or inactive, active_since, a message, and a value.
How is trend data requested?
GET get_tl_data_start_end with api_key, a tl reference in building.device.TL form, start and end as YYYY-MM-DDThh:mm:ss, and data=raw for samples as read from the BAS or data=align for 5-minute alignment. Rows return ts and v.
Ask about Kaizen

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 Kaizen 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