Skip to content
GroundBoot
Menu

BuildingMGR Bridge / Private preview

Bring the building
into the picture.

BuildingMGR Bridge is the proposed connection between selected on-site systems and PropertyMGR. Carry readings with their equipment, source and timing into a useful operating view.

A connection qualified for your building and the people responsible for it.

01 / A reading with a place to go

From a local reading
to useful context.

Knowing a value is only the beginning. Keep what it describes, where it came from and when it was observed with the information the operator sees.

At the building

Supply air

18.4 °C

AHU-02 / Rooftop plant

Observed09:41SourceBuilding system
The proposed connection

BuildingMGR
Bridge

  1. 01 Select agreed readings
  2. 02 Keep source and timing
  3. 03 Deliver within the scope
In PropertyMGR
Northline buildingAHU-02

Rooftop plant / Supply air

18.4 °C

Observed at 09:41

Source
Building system
Equipment context
Location and operating history
Useful follow-up
Review alongside maintenance

At the building

Start with what
you need to understand.

Select the equipment and readings that answer the operating question. The local source, unit and observation time are part of the record.

The example follows one supply-air reading. Supported sources are qualified for each building.

Through the connection

Give the reading
a reliable identity.

Map the source to the right equipment and preserve when the observation happened. The preview design includes connection health and bounded queued delivery.

The connection is initiated from the building. Data volume, buffering and retention are agreed before activation.

In the operation

See what the value
belongs to.

Put the reading beside its building, equipment and relevant work. Give the authorized operator a clearer starting point for review and follow-up.

This illustration sends no readings or commands. Bridge and PropertyMGR remain private-preview components.

Conceptual private-preview connection with synthetic readings. The diagram describes a proposed software role, not a hardware appliance or live system.

02 / Keep the timing honest

An interruption
should be visible.

A last-known reading should carry its observation time. A connection pause should be visible. Queued information should keep the time it was captured.

  1. 09:41 / Last delivered

    A known observation.

    The operator can see when the last value was recorded.

    Supply air18.4 °CObserved 09:41
  2. Connection paused

    A visible interruption.

    The design keeps connection status and queued records distinct.

    Observation / 09:42Observation / 09:43Within agreed buffer capacity
  3. Connection restored

    The original timing stays.

    Delivery resumes with the captured times, so the sequence remains understandable.

    Delivered after the pause09:42 · 09:43Original observation times
Illustrative recovery design. Buffer capacity, supported interruption duration and recovery behavior must be validated for the deployment.

03 / Defined for the building

A defined connection.
Clear responsibility.

Agree what the connection is for, what it carries and who looks after it. Keep the operating boundaries understandable.

01

Selected readings

Approve the building, sources and access. The preview uses an outbound-initiated connection for the information in scope.

02

Visible freshness

Keep source, observation time and connection health visible. Define how delayed or unavailable information is presented.

03

An operating owner

Agree enrollment, connection maintenance, updates and support. Local systems stay under the building operator’s control.

BuildingMGR Bridge is a private-preview integration component for PropertyMGR, not a separate tenant plan. Any command or remote-control path requires its own qualified Enterprise scope.

04 / A practical first scope

Start with the question.
Qualify the connection.

Bring the operating question and the systems involved. We can assess the sources, the useful first connection and what it will take to support it.

  1. 01

    The result

    What should the operator understand or do with the information?

    A useful operating question
  2. 02

    The sources

    Which systems provide the readings, and who manages access to them?

    Interfaces qualified for the building
  3. 03

    The record

    How often is information needed, how much is retained and how are gaps handled?

    Defined volume, timing and recovery
  4. 04

    The responsibility

    Who approves the connection, validates the result and supports it afterward?

    An agreed operating arrangement
Which building systems can we assess?

Existing BACnet, Modbus, OPC UA, MQTT and vendor API interfaces can be assessed per building. Connector support, source access, expected volume and operating behavior must be qualified before activation.

A building connection with a purpose

What would you like
your building to tell you?

Tell us about the equipment, the systems and the question you want to answer. We can assess a practical first connection.

Discuss a building connection