Reference · built on requestConnectorBuilding management platforms

Automated Logic WebCTRL

Alarm records, Sparkplug B point streams, and exported trend history from WebCTRL, with schedule and web-service writes.

Request accessPricing ↗

About

WebCTRL is the building automation server from Automated Logic, a Carrier company. It speaks BACnet over IP, ARCnet, MS/TP, and Secure Connect, plus Modbus, N2 Open, SNMP, KNX, and M-Bus. Its integration surface has seven parts: protocol integration hardware, a licensed Java SDK, SOAP/XML Web Services, an MQTT Connector add-on, a Trend Export add-on, scheduled custom reports, and, since v9, a read-only REST API for alarm data.

Through Fibric, an operator reads alarm records, subscribes to points published over MQTT with their Haystack tags, and loads exported trends. It proposes schedule writes through the BACnet Scheduling Interface add-on or value changes through Web Services. You approve, and the receipt records the prior value.

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

  • Alarm records and counts through the read-only REST API introduced in WebCTRL v9
  • Selected points published to an MQTT broker in Sparkplug B format, enriched with Project Haystack tags for location, unit, equipment type, and point characteristics
  • Historical trend data exported as .CSV or to a database, daily, hourly, or on demand, covering up to 2 years
  • Alarm-triggered outbound GET or POST requests to an external endpoint, configured in WebCTRL
  • Trends, logic, schedules, and live values through the Java SDK where Automated Logic licenses it for the project
  • Scheduled reports, graphics, and PDFs emailed from the server to named recipients

Proposed actions

  • Target capability: propose a BACnet schedule write through the BACnet Scheduling Interface add-on, for events that move occupancy
  • Target capability: propose a value change through WebCTRL SOAP/XML Web Services, which the platform documents as able to query and interact with BAS data

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

What you can build

  • Sort a night's alarms before the morning walk

    Alarm records from the v9 alarm API come with their sources and states. The operator groups repeats, drops those that returned to normal, and proposes an ordered list with the evidence behind each.

    With Alarm Triage

  • Prove the economizer opened when it should

    Damper, mixed-air, and outdoor-air points stream over MQTT with Haystack tags. The operator compares them against the outdoor conditions and proposes a service ticket when free cooling was left on the table.

    With Economizer Check

  • Shed load during a utility event

    When an OpenADR event lands, the operator proposes the schedule and setpoint moves you pre-approved, shows the points involved, and records what was changed and when it reverts.

    With Event Response

Requirements

  • WebCTRL v8 Advantage or Premium with cumulative patch 5 or later, plus a license, for the MQTT Connector add-on
  • WebCTRL v9 for the read-only REST alarm API
  • The Trend Export add-on license for scheduled .CSV or database exports
  • An MQTT broker with TLS 1.3 reachable from the WebCTRL server, when streaming points
  • Network reach to the WebCTRL server over HTTPS, or a managed tunnel where it sits on an isolated BAS network
Authentication
Authenticated API access on the WebCTRL server for Web Services and the v9 alarm API, password or X.509 certificate authentication from the MQTT Connector to your broker, and optional SAML 2.0 or OIDC single sign-on for operators since v9.

Limits

  • The v9 alarm API is read-only; it does not command points
  • On WebCTRL Standard the MQTT Connector serves only integration with Carrier Abound; Advantage and Premium need a license
  • The Java SDK is licensed case by case and is not a general public API
  • Trend Export delivers files on a schedule; it is history, not a live feed

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 Automated Logic WebCTRL ↗

Questions and answers

Does WebCTRL have a REST API?
Two things carry the name. Since v9, a REST API gives external applications read-only access to alarm data. Separately, WebCTRL can trigger outbound GET or POST requests to external APIs when alarms occur. Neither commands points; that is the province of Web Services and the SDK.
What does the MQTT Connector send?
Points you select in its configuration, formatted to the Sparkplug B specification and published to your broker, with Project Haystack semantic tags for location, units, equipment type, control program, and point characteristics. It supports MQTT v3.1.1, password or X.509 authentication, and TLS 1.3.
How far back can Trend Export reach?
Up to 2 years of .CSV trend data, exported daily, hourly, or on demand. Scheduled exports include only new historical data received since the last export, and a database destination is also supported.
Ask about Automated Logic WebCTRL

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 Automated Logic WebCTRL 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