Skip to content
SOMA Controls
How we work · Integrate

Building Systems Integration

We integrate equipment, meters, and third-party systems using BACnet, Modbus, and Niagara-based supervisors. You receive documentation of the connections and retain ownership of the result.

Discuss this serviceView services
From equipment to operatorConcept diagram
Building equipmentHVAC · meters · lighting
Local controlsPoints · logic · sequences
System connectionsProtocols · point mapping
Operator viewGraphics · alarms · trends
A simplified view of how building controls connect. Every building has its own architecture.

Scope at a glance

Outcomes, deliverables, boundaries, and handoff in one place.

Operational outcomes

  • One front end across multi-vendor equipment where the installed systems allow
  • Open-protocol integration paths where the installed systems allow
  • Documented, maintainable integration paths
  • You keep clear ownership of the result

Deliverables

  • One front end across your multi-vendor equipment where the installed systems allow
  • An integration map and protocol plan
  • Documented, maintainable integration paths over open protocols
  • Validated data and control across the connected systems

Scope boundaries

  • Field equipment, meters, and gateways require a separately agreed hardware and installation scope
  • We do not perform electrical or mechanical installation labor
  • We do not add a proprietary SOMA Controls layer or require our continued involvement

Handoff

You keep clear ownership of the integrated system and the documentation that describes it. Integration paths stay documented and maintainable by qualified others within the installed systems' access and licensing constraints.

From the network to the zone

See how the control layers connect.

Operator access, controllers and field devices each have a different job. A readable architecture makes their relationships easier to maintain.

Illustrative BAS network overview on a drawing sheet: operator and supervisor, Ethernet and BACnet/IP controllers, then sensors and actuators with a separate DALI lighting bus.
  1. Operate and superviseOperator access brings schedules, alarms and trends into view.
  2. Network and controlEthernet and BACnet/IP connect the supervisor to the equipment controllers.
  3. Sense and actTemperature, airflow and fan-proof inputs inform control. Outputs position dampers; the lighting controller uses a separate DALI bus.

Illustrative architecture, not a wiring drawing or customer installation. Open the image to inspect its labels.

Open integration panel with an Ethernet switch, two gateway modules, a controller and neatly routed blue patch leads.

The equipment behind the connections.

An Ethernet switch, gateways and controllers give those network relationships a physical home.

Illustrative integration equipment, not a customer installation or a wiring reference.

Follow the air. See the response.

Trace a conceptual supply-air path from the rooftop unit to a selected floor. Explore the illustrated damper position with an optional ten-second sequence.

Illustrative building cutaway with a rooftop unit, three office floors, ductwork and a ground-floor plant room.Illustrative supply-air route and zone dampersA dashed inferred connection links the rooftop unit to the right-hand supply riser. Three branches follow the visible floor ducts. The selected branch and representative damper show a conceptual air path, not measured performance.ABC
Supply-air directionInferred roof connectionIllustrated zone damper

Explore a zone

These values are demonstration positions. They are not live building readings.

Static view. Interactive controls require JavaScript.

45%
ClosedOpen

Blade angle only; percentage is not an airflow calculation.

The roof connection and damper locations are conceptual additions to the illustration. Return air, exhaust and a complete ventilation sequence are outside this view.

Connecting supported protocols through one supervisor
Network topology diagram: mixed-vendor field equipment connects over BACnet/IP, BACnet MS/TP, Modbus TCP, Modbus RTU, and LonWorks through routers and gateways into a single supervisor, with an open lane for other protocols reviewed by scope.
04 steps

How it works

  1. 01

    Discover

    Inventory equipment, protocols, and data points.

  2. 02

    Design

    Plan the integration architecture and data model.

  3. 03

    Build

    Connect the systems through the agreed integration architecture.

  4. 04

    Commission

    Validate data and control across the systems in scope.

Common questions

What platforms do you work across?

Common open platforms such as Niagara, coordinating equipment from different manufacturers under one front end where conditions allow.

Do you support BACnet and Modbus?

Yes. We use open protocols where available and document any OEM-specific constraints.

Related controls services

Next step · Your service inquiry

Tell us about the controls work you need.

Discuss this serviceFind the right service