(909) 548-0925 service@cemech.com
C.E. MECHANICAL / ABB BUILDING AUTOMATIONCHINO, CALIFORNIA · SOUTHERN CALIFORNIA

Building controls. Better understood.

ABB BuildingPro. Commercial building automation for Southern California.

Commercial building automation built around ABB Ability™ BuildingPro Edge, Vision and Suites—from connected equipment and local control to the information facility teams use every day. C.E. Mechanical brings the installation, integration and HVAC field experience to make it practical.

THE SYSTEM / 001FIELD TO FACILITY
One building.
One clearer
picture.
01
BuildingPro EdgeLocal integration · openBOS · building data
02
BuildingPro VisionSchedules · floor plans · alarms · trends
03
BuildingPro SuitesConnected analytics · portfolio intelligence
ABB Ability™ BuildingProPlatform overview ↗
Manufacturer platformABB Ability™ BuildingPro
Controls + mechanicalDesign / install / integrate / service
ContractorC.E. Mechanical · CSLB #765670

01 / BUILDINGPRO

A system worth building around.

BuildingPro has different layers for different jobs. The value comes from getting the architecture right—then making it useful to the people responsible for the building.

01 /

BuildingPro Edge

The local integration and control foundation. Edge uses ABB’s openBOS® architecture to connect building systems, organize data by asset and space, and support on-site supervision. ABB offers Edge Medium and Edge Large for different scales of deployment.

ABB product details
02 /

BuildingPro Vision

The operating view. Vision brings floor plans, asset graphics, schedules, alarm management, trends and metering information into a browser-based interface for facility teams, with local access and optional remote services.

ABB product details
03 /

BuildingPro Suites

The additional intelligence layer for sites and portfolios. Modular applications bring together building, HVAC, energy and related system data for broader performance analysis and operational decisions.

ABB product details
ABB EDGE SERIESDifferent scale.
Shared platform.
Medium10,000Up to managed datapoints
Large50,000Up to managed datapoints

ABB-published capacities; not an equipment selection or a guarantee of usable point capacity for any specific architecture. Network, licensing, protocols, performance and redundancy require design review. ABB Edge Series specification ↗

BuildingPro Editor

Configuration software provided with BuildingPro Edge for project setup, connections, site structures, points and system configuration. View ABB utilities.

BuildingPro Portal

Optional cloud-side access for portfolio organization, remote operations and device/license management, depending on subscribed services and IT requirements.

02 / OPEN ARCHITECTURE

An open platform for buildings that keep changing.

ABB Ability™ BuildingPro connects building equipment and information through local integration, real-time supervision and optional building or portfolio applications. With its edge-based architecture, the facility can maintain local operation while selecting cloud-connected functions where they add value. The result is a practical foundation for alarms, trends, schedules, dashboards, reporting and coordinated building operations.

MULTI-PROTOCOLBACnet®, Modbus, KNX and MQTT support where appropriate.
EDGE-FIRSTLocal BuildingPro Edge operation with cloud-optional architecture.
USER INTERFACEBuildingPro Vision for supervision, graphics, floor plans, alarms and trends.
INTELLIGENCE LAYERBuildingPro Suites for broader building and portfolio visibility.

C.E. Mechanical helps define the actual point list, controls scope, integration responsibilities, cybersecurity coordination, commissioning plan and owner handoff.

Contemporary commercial interior
Buildings operate best when systems, spaces and people are considered together.

03 / THE SYSTEM

The data should travel. The responsibility should stay clear.

A building has systems, networks, field devices and people. The BAS should make them easier to understand together—not obscure what is actually happening.

  1. 01 / FIELD

    Equipment

    HVAC · lighting · metering · sensors · field controls

  2. 02 / LOCAL

    Edge

    Open protocols · data context · on-site integration

  3. 03 / OPERATE

    Vision

    Graphics · floor plans · trends · schedules · alarms

  4. 04 / EXTEND

    Suites

    Building and portfolio insights, when required

Conceptual system architecture. Device support, points, software and licensing are established through project design and site verification.

View ABB's BuildingPro overview ↗
Open connections

ABB documents support for protocols including BACnet and other standard building interfaces through Edge. Actual integration scope is defined point by point.

Local-first operation

Supervision and building data can remain on site. Cloud functions and remote access are selected to fit the owner’s IT and security policies.

A maintainable system

Controls should leave the facility with clear equipment naming, useful alarms, understandable graphics and documented operating sequences.

04 / ARCHITECTURE DECISIONS

Not every building needs the same BuildingPro stack.

Three common situations. Three different control and visibility requirements. The right scope starts with the operator's decisions and the systems that must remain reliable.

01 / SINGLE FACILITY

Start with a clear local control boundary.

At a single office, industrial site or institutional building, BuildingPro Edge can organize data from multiple HVAC and metering interfaces. Vision becomes valuable when operators need usable graphics, schedules, trend review and actionable alarms across those assets.

First design question Which devices are supervised, which are merely observed, and which sequences must continue independently if the network or supervisory interface is unavailable?

02 / CENTRAL PLANT

Make the plant's control authority explicit.

One central plant may combine chillers, pumps, towers, boilers, meters, VFDs and independent OEM controllers. BuildingPro can provide visibility and integration, but the controls drawings must identify who issues lead/lag, staging and reset commands—and who retains equipment safeties and local interlocks.

First design question What exactly happens on loss of communication, loss of proof or a failed command?

03 / CAMPUS OR PORTFOLIO

Standardize the data before aggregating it.

Across buildings, point names alone are not enough. Asset hierarchy, meter boundaries, time stamps, alarm priorities and operational responsibilities need consistency. Edge and Vision establish the site-level picture; Suites can extend into broader intelligence where the owner has a defined portfolio use case.

First design question Which cross-site decisions genuinely require consolidated data, and who will maintain it?

Contemporary commercial building facade with horizontal metal panels and repeated window bands
BUILDING OPERATIONS

Architecture principle. ABB describes Edge as an openBOS-based integration platform and Vision as the supervisory operator interface. Suites is a separate modular intelligence layer. Specific software, device support, licenses, network permissions and controller sizing require project review. See ABB's BuildingPro platform ↗

05 / APPLICATIONS

Different buildings. Different operational priorities.

BuildingPro can connect information across HVAC, metering, control and operations. The value comes from deciding which signals matter, how they are used, and what the building team needs to know every day.

Commercial office tower
SINGLE BUILDING

Know what matters in each zone.

For occupied buildings, useful control data includes zone temperatures, outdoor-air conditions, equipment schedules, alarms, overrides and the response of the airside systems serving the space.

Mechanical rooftop and cooling equipment
CENTRAL PLANT

See the plant without losing control boundaries.

Plant supervision becomes useful when operators can relate CHWS/CHWR temperatures, flow proof, pump status, VFD response, staging, condenser-water conditions and alarms to actual equipment behavior.

Multiple urban buildings
PORTFOLIO / CAMPUS

Bring consistency to multi-site operations.

Across campuses and portfolios, consistent asset names, meter boundaries, timestamps, alarm priorities and user permissions make comparisons and reporting meaningful without erasing site-specific conditions.

06 / CONTROLS PLANNING

Plan the controls.
Define the critical connections.

PROJECT TOOL / 01

Choose a typical building scenario and your priorities. Review the platform direction and the questions to resolve before design, installation or integration.

ABB BUILDINGPRO / CONTROLS PLANNINGChoose a building scenario to begin.
PROJECT PLANNER What kind of project are you planning?

Select the setting and operating priorities. The guidance below identifies an initial BuildingPro approach, integration considerations, and the teams to involve.

PLATFORM DIRECTIONBuildingPro Edge + Vision

A practical starting point based on the selected scenario.

SYSTEM INTERFACESExample protocol types

Protocol paths and field interfaces will appear here as the scope updates.

FIRST DESIGN PRIORITYScope discussion

Define the first coordination topic for the project.

EARLY PROJECT TEAMFacility operations · BAS integrator

Team coordination follows the selected scope.

Planning examples are for initial discussion; the proposed architecture, protocol availability, controls authority and commissioning scope are confirmed against the actual building.

Interactive planning is unavailable in this view. The detailed worksheet contains a sample layout; contact C.E. Mechanical for assistance with your project scope.
ADVANCED SCOPE WORKSHEETBuild a detailed equipment and integration scope
Editable inventory, control responsibilities and exportable findings.
STEP 01 / CONFIGUREChoose equipment and interfaces. Open Step 02 when you want the analysis and matrix.
01 / SET THE CONTEXT

Describe the systems and the boundaries.

Identify equipment, connection methods and control responsibilities. The findings update as you build the scope.

02 / BUILD THE SYSTEM INVENTORY4 system groups

Use a starting layout or add systems individually. All values are editable. Entries represent equipment groups—not a verified field points schedule.

CURRENT WORKING INVENTORY Central plant · 4 units / 4 groups

Occupied-building retrofit · Occupied commercial building · BACnet/IP

First decision: define the controls responsibilities for the equipment groups. Review integration findings ↓
Chiller plantBACnet/IPConfirm authority
CHW pumpsBACnet/IPConfirm authority
Cooling towersBACnet/IPConfirm authority
Boiler plantBACnet/IPConfirm authority
03 / CONFIRM THE BOUNDARIESChoose what is known today
OEM safeties, listed equipment protections, life-safety interlocks and required independent controls are not superseded by supervisory integration. Control authority and fail-safe behavior must be engineered and tested for the actual equipment.
STEP 02 / FINDINGSReview integration findings and export the brief
4 groups · 4 equipment units
PROJECT FINDINGS / INITIAL SCOPE Local analysis
System groups4
Equipment units4
Known protocol paths1
Proposed integration approach

Occupied retrofit and transition

Validate existing operating conditions, phased cutover and a safe rollback path.

Central plant / 4 equipment units / 1 protocol path

Change an input to regenerate the integration findings.

01 / FIELDPlant + HVAC equipmentProtocol connections
02 / EDGEBuildingPro EdgeopenBOS® integration layer
03 / SUPERVISIONBuildingPro VisionGraphics · alarms · trends

Conceptual path only. Edge sizing, field controller selection, licensing, gateways, user permissions and remote access require design review. Suites may be considered separately for portfolio analytics.

Coordination checkpoints

0 / 6

Enter the site and system details to evaluate scope readiness.

Items requiring resolution

—
  1. Confirm operating sequence, point map, network route, and control authority.

Field verification priorities

  • Verify connected devices and operating conditions.
Take the outline into a meetingDownload a scope-development brief.
WORKING OUTPUT / PRELIMINARY INTEGRATION MATRIX

A working scope outline for the owner, controls contractor, mechanical team and IT—not an approved control drawing.

Equipment groupQtyProtocolBAS responsibilityField coordination
Example central plant——To be definedConfirm point schedules and safeties

Planning and discovery tool only. Equipment names, quantities, control ownership and protocols are user inputs, not site-verified facts. No point counts, controller capacity, engineered sequence, code compliance, energy savings or manufacturer compatibility are assumed. Review actual ABB documentation, OEM IOM, adopted codes/AHJ requirements and approved contract documents before design or construction.

07 / CENTRAL PLANT CONTROLS

A plant graphic is a view. A plant sequence is a responsibility.

A conceptual water-cooled chiller plant illustrates why the integration matrix matters. Supervisory controls, local OEM safeties and operating dependencies must be defined separately.

Industrial cooling towers and mechanical equipment on a commercial building rooftop
Cooling equipment and central-plant infrastructure
EXAMPLE 001 / WATER-COOLED PLANT

The BAS should make the operating state visible without taking away the protection that belongs to the equipment.

Conceptual example—not a C.E. Mechanical project, final sequence or equipment selection.
Conceptual supervisory-to-field architectureCOMMAND, PROOF & RESPONSE
SUPERVISORY LAYER / ABB BUILDINGPROSchedules · enable requests · lead/lag · reset targets · alarms · trendsOnly where the approved points list and written sequence assign these functions to BAS.
01 / PLANTChillers

Enable permission, status, faults, leaving-water temperature, load feedback

02 / WATER SIDECHW / CW Pumps

Run proof, VFD response, flow/DP, valve position, permissives

03 / HEAT REJECTIONCooling towers

Fan status, VFDs, basin safeties, condenser-water temperature

04 / MEASUREPlant sensors

Temperature, pressure, flow, meters, data plausibility

OEM / LIFE-SAFETY BOUNDARYLocal safeties, freeze and high-pressure protection, minimum-flow protection and equipment-specific lockouts remain governed by the applicable OEM/listed controls and engineered sequence.
BEFORE PROGRAMMING / 01

Define permissives and ownership.

Identify the source and logic for flow proving, valve position, pump availability, local interlocks, chiller enable, minimum on/off time and restart inhibit. A writable BACnet object is not automatically permission to operate equipment.

BEFORE CUTOVER / 02

Prove the physical response.

Verify command/status points against actual pump operation, flow or differential pressure, temperature sensors, VFD feedback and actuator position. Record what happens when a device trips, loses communication or returns from an outage.

AFTER TURNOVER / 03

Leave a diagnostic record.

Trend starts, stops, demand, CHWS/CHWR and condenser-water temperatures, setpoints, alarms and proof conditions. Commission at representative operating conditions and provide the owner with sequence narratives and an actionable alarm response path.

08 / MECHANICAL + CONTROLS

A better interface is only half the job.

C.E. Mechanical works at the point where controls meet equipment. A nice graphic is not proof that a valve, damper, VFD or chiller is doing what the sequence requires.

Commercial rooftop HVAC equipment for airside BAS and controls service
AIRSIDE / EQUIPMENT

RTUs, AHUs, VAVs and economizers.

Sensor accuracy, fan status, damper position, airflow, static pressure, safeties and the actual equipment response.

Commercial hydronic piping and central-plant systems
HYDRONICS / PLANT

Boilers, chillers, pumps and valves.

Waterflow, ΔT, staging, resets, VFD response, safeties and plant operating logic matched to the mechanical installation.

THE FIELD RULE

First confirm what the BAS reports. Then verify what the controller commands. Finally, measure what the equipment actually does. That is how we separate programming issues from mechanical and device problems.

09 / DELIVERY

From a controls plan to a building that runs.

Whether the project is a new installation, a building retrofit or integration into an occupied facility, we keep installation, equipment operation and owner handoff connected.

01

Design & scope

Point lists, control sequences, device and network planning, equipment interfaces, shutdown constraints and coordination with the owner’s standards.

02

Install & integrate

Controllers, panels, field wiring coordination, network communications, BACnet point mapping, graphics and operator-facing controls.

03

Program & verify

Schedules, economizer logic, resets, alarms, VAV and central plant sequences; field checks and startup with TAB and commissioning coordination.

04

Support & improve

Service diagnostics, trend review, override cleanup, control-device corrections, software coordination and phased system modernization.

A useful BAS handoff includes:
  • Point-to-point verification
  • Exercised operating sequences
  • Prioritized alarms
  • Relevant trends
  • Validated schedules
  • Operator documentation and training

10 / FIELD EXECUTION

Controls engineering has to survive the mechanical room.

Successful integration is measured by more than a connected device list: point-to-point checks, electrical and network boundaries, equipment response, startup records and a serviceable handoff.

01 / BEFORE INSTALLATIONPoint list + sequence review
02 / BEFORE STARTUPDevice and network verification
03 / AT COMMISSIONINGFunctional tests + failure states
04 / AT OWNER TURNOVERTrends + alarm priorities + training

11 / INTEGRATION DETAILS

An open protocol is a starting point. Not a finished controls scope.

BACnet, Modbus and hardwired interfaces can move information. They do not, by themselves, define who may start equipment, which safeties remain local, what an operator can override, or what happens when communication is lost.

What a useful BAS integration review actually covers

  • Point-by-point intent. Monitor-only, supervised commands, or full sequence responsibility—not simply “BACnet compatible.”
  • Plant dependencies. Flow proving, pumps, valves, bypass, minimum run/off timers, lead–lag and equipment protection.
  • Network & access. BACnet/IP routing, MS/TP trunks, Modbus registers, gateways, segmentation, credentials and the BAS/IT boundary.
  • Verification. Alarm priorities, trends, graphic accuracy, command/feedback checks, failure recovery, owner training and documented turnover.

For a central plant, this can mean mapping chillers, pumps, cooling towers, boilers and common plant sensors before any graphics or supervisory programming begins. For an occupied building, it also means planning coexistence, cutover, and rollback so the new front end never becomes the single point of operational confusion.

Review an ABB BuildingPro integration with C.E. Mechanical

12 / EXISTING BAS SUPPORT

Already running ABB Cylon? We know the installed world matters.

We continue to support ABB Cylon ASPECT, INTEGRA, BACnet CB Line, CBX/CBXi, FLXeon and CXproHD environments where applicable. Existing Siemens, Honeywell, Johnson Controls, Niagara and mixed-platform systems may also be assessed for troubleshooting or integration.

Moving toward BuildingPro starts with verifying existing controllers, exposed BACnet points, communication paths, software, licensing and field conditions. We do not assume that every older device can be reused or migrated.

ABB Cylon reference
PLANNED MODERNIZATION · OCCUPIED FACILITIES

Three stages. One controlled transition.

Keep critical systems operating while introducing new BuildingPro capabilities. Each phase starts with an inventory, defined control authority, and an agreed verification plan.

Survey

Inventory controller families, firmware, field wiring, point names, network segments, front-end access, OEM interfaces and licensing. Identify unsupported drivers and devices before declaring reuse feasible.

Coexist

Confirm the monitoring-versus-commanding boundary, point ownership and supervisory communication routes. Establish cutover windows, backups, fail-safe behaviors and rollback authority before changing live sequences.

Validate

Compare pre- and post-cutover trends, command and feedback, alarm delivery, schedules and operator graphics. Close out with as-builts, test records, owner training and the next-stage migration plan.

13 / SOUTHERN CALIFORNIA

Local to the equipment. Accountable to the building.

Based in Chino, C.E. Mechanical supports commercial and institutional HVAC controls projects throughout Greater Los Angeles, Orange County and the Inland Empire. We plan around access, live operations, permit/AHJ requirements, construction coordination and long-term service needs.

Los Angeles CountyGreater LA / Long Beach
Orange CountyAnaheim / Irvine and beyond
San Bernardino CountyChino / Ontario / Inland Empire
Riverside CountyRiverside / Inland Empire
Downtown Los Angeles skyline backed by the San Gabriel Mountains
LOS ANGELES · SAN GABRIEL MOUNTAINS

14 / COMMON QUESTIONS

A few things worth knowing before you start.

ABB BuildingPro, existing controls and the project information that helps get to a workable scope.

What is ABB Ability BuildingPro?

ABB Ability™ BuildingPro is ABB’s open, edge-based building integration platform. BuildingPro Edge connects and contextualizes building data locally, BuildingPro Vision provides web-based supervision, and BuildingPro Suites offers additional building and portfolio intelligence. The project architecture and licensed modules depend on the facility’s requirements.

What is the difference between BuildingPro Edge and BuildingPro Vision?

BuildingPro Edge is the local hardware and openBOS® integration/control layer. BuildingPro Vision is the operator-facing supervisory software, with dashboards, floor plans, asset views, schedules, alarms, trends and metering views. Vision uses information provided through Edge.

Does ABB BuildingPro require a cloud connection?

ABB describes BuildingPro as an on-premises-first platform with optional cloud features. BuildingPro Vision can be accessed locally, while remote access and portfolio services depend on the selected options, network design and licensing. Confirm the site’s cybersecurity and IT requirements before specifying access.

Can BuildingPro connect to an existing ABB Cylon system?

Potentially. ABB BuildingPro Edge supports multiple building protocols, including BACnet connectivity. Existing ABB Cylon BACnet controllers may be candidates for integration, subject to installed hardware, point availability, networks, software, licensing and project verification. Legacy proprietary equipment requires a separate compatibility assessment.

Does C.E. Mechanical still service ABB Cylon ASPECT and older controls?

Yes. C.E. Mechanical supports existing ABB Cylon controls, including assessment, service, graphics and trends, troubleshooting, field-device verification and phased modernization. We also work with other established commercial BAS environments when the building requires it.

Does C.E. Mechanical handle both BAS and mechanical HVAC issues?

Yes. Our controls work is coordinated with commercial HVAC field service. That helps differentiate problems caused by sensors, actuators, airflow, hydronics or equipment operation from controller, network or sequence issues.

Where does C.E. Mechanical provide ABB building automation services?

C.E. Mechanical is based in Chino and serves commercial and institutional facilities across Greater Los Angeles, Orange County, San Bernardino County, Riverside County and the Inland Empire. Availability depends on the project, site access and service requirements.

What information is useful when requesting a BuildingPro or BAS proposal?

Send the facility location, equipment served, existing BAS platform, controller and panel photos, points list or controls drawings if available, known network and access conditions, operating concerns, project timing, and any shutdown or occupancy restrictions. That information helps establish an appropriate site assessment and scope.

What is a BAS integration matrix for a central plant?

A BAS integration matrix identifies each connected equipment group, the communication method, whether the supervisory system monitors or commands it, and the field tests needed before turnover. A central plant matrix may include chillers, pumps, cooling towers, boilers, meters, sensors, and their operating interlocks. It is a scope-development tool—not a substitute for engineered sequences or approved control drawings.

Can ABB BuildingPro Edge connect a mixed BACnet and Modbus HVAC plant?

ABB BuildingPro Edge is designed to integrate building systems using open protocols including BACnet and Modbus. Whether a particular chiller, pump, meter or legacy controller can be integrated depends on the device interface, available points/registers, write permissions, network path, licensing and approved project scope. OEM safeties and local equipment interlocks remain separate from supervisory commands.

When does a BuildingPro project need Edge, Vision or Suites?

BuildingPro Edge is the local integration platform. Vision supplies the facility-facing supervisory view for graphics, alarms, trends and schedules. Suites extends into modular building and portfolio intelligence. The combination depends on the systems, number of sites, operator workflow, required analytics and applicable licensing.

Can ABB BuildingPro supervise a central chiller plant?

A BuildingPro integration can support central-plant monitoring and supervisory functions where the approved architecture, field interfaces and sequences permit them. Before commissioning, establish command authority, flow and equipment permissives, OEM/local safeties, lead/lag and reset logic, alarm behavior, communication failure response and functional testing. Do not assume protocol availability grants control authority.

LET’S MAKE THE NEXT CONTROLS DECISION A GOOD ONE.

A better building starts with a real conversation.

Tell us what systems you have, what you want to improve and what cannot go offline. We’ll help establish the right first step for BuildingPro, a BAS retrofit or an active controls issue.