When a 3,200-student liberal arts college in the Northeast received its third consecutive annual energy cost increase, the VP of Finance issued a direct challenge to the facilities team: find the waste or justify the spend. The campus ran 38 buildings across 1.8 million gross square feet, but the facilities director had no building-level consumption data, no setpoint compliance history, and a building management system that operated entirely independently of the maintenance platform. HVAC equipment was running on commissioning-era schedules. Preventive maintenance on mechanical systems was tracked in spreadsheets. Fault conditions went undetected for weeks. The college had invested in a BMS years earlier, but without integration into a CMMS, the operational data it generated never translated into work orders, schedule corrections, or capital decisions. Over 18 months, the college deployed Oxmaint as its central CMMS, integrated BMS data feeds into the maintenance workflow, and restructured its PM program around actual equipment runtime and setpoint compliance. The result was a verified 22% reduction in energy costs — without a single major capital renovation. If your campus is in the same position to begin building your energy baseline, or Book a Demo to see how BMS-CMMS integration works in practice.
Stop managing energy by complaint. Oxmaint connects your BMS data to maintenance workflows so setpoint deviations become work orders — automatically.
The Challenge: A BMS Without a Maintenance Bridge
Invisible Setpoint Drift
The BMS logged temperature and pressure deviations in 24 buildings — but no mechanism existed to generate maintenance work orders from those alerts. Faults aged unaddressed for an average of 19 days before technician awareness.
Unoccupied HVAC Runtime
Fixed schedules set during original commissioning kept air handling units running 168 hours per week in buildings occupied fewer than 55 hours. Weekend conditioning of empty classrooms and offices accounted for an estimated 31% of HVAC energy spend.
PM Compliance Gaps
Preventive maintenance on 214 mechanical assets was tracked in disconnected spreadsheets. Filter changes, belt inspections, and coil cleanings were completed based on calendar dates rather than runtime hours — creating both over-maintenance and critical missed intervals.
No Energy Attribution
Utility invoices arrived at the campus level. The facilities director could not identify which of the 38 buildings consumed disproportionate energy, making prioritization of operational corrections or capital projects essentially impossible.
Simultaneous Heating and Cooling
BMS data showed 18 terminal units across 9 buildings with hot water and chilled water valves open simultaneously — a control fault generating an estimated $290,000 in annual waste that no technician had been dispatched to address.
Board Reporting Without Verification
The sustainability office submitted energy reduction estimates to the board and AASHE STARS based on modeled projections rather than measured data — leaving the institution unable to verify actual progress toward its 2035 carbon neutrality commitment.
The Solution: Oxmaint CMMS Integrated With BMS Data
The college selected Oxmaint as its CMMS platform specifically for its ability to ingest BMS alert data and translate equipment fault conditions directly into maintenance work orders. Rather than treating building automation and maintenance management as separate systems, the implementation team mapped 847 BMS data points across 38 buildings into Oxmaint's asset hierarchy — creating a unified operational view where energy anomalies, setpoint deviations, and runtime data all feed the same maintenance workflow. Book a Demo to see how the BMS-CMMS data bridge is configured for campus environments.
Implementation: Three Phases Over 18 Months
01
Asset Registry and BMS Mapping (Months 1–3)
The facilities team built a complete digital asset registry in Oxmaint covering 214 mechanical assets across 38 buildings — AHUs, chillers, boilers, pumps, and terminal units. Each asset was linked to its corresponding BMS data points, establishing the connection between equipment condition and operational status. Electrical submeters were installed on all 38 buildings, providing building-level consumption data for the first time. Within 45 days, the submeter data identified 6 buildings consuming 38% of total campus energy — three of which had no operational justification for their consumption levels.
02
Automated Fault Detection and PM Restructuring (Months 2–8)
Oxmaint's work order automation was configured to generate maintenance tickets when BMS data exceeded defined thresholds — setpoint deviations beyond ±3°F, simultaneous heating/cooling valve positions, AHU runtime during confirmed unoccupied periods, and economizer faults. The PM program was restructured from calendar-based to runtime-based scheduling for all 214 assets, using actual operating hours logged through BMS integration. This eliminated 34% of unnecessary PM events while ensuring critical intervals on high-runtime equipment were never missed.
03
Occupancy-Aligned Scheduling and Capital Justification (Months 6–18)
Six months of Oxmaint operational data — combining BMS runtime logs, occupancy sensor feeds, and submeter consumption records — provided the evidence base for HVAC schedule corrections across 28 buildings. Schedules were adjusted to align with verified occupancy patterns, with 2-hour pre-conditioning windows replacing 24/7 operation. The same dataset was used to justify $380,000 in capital investment across 4 targeted projects, each supported by verified ROI calculations based on measured baseline consumption rather than engineering estimates.
Sign Up Free to start building the data record your capital requests require.
Results: Verified Outcomes After 18 Months
22%
Total energy cost reduction — verified by submeter data, not modeled
$2.1M
Annual savings on a $9.5M energy budget — payback in under 4 months
31%
Reduction in HVAC runtime hours across 38 buildings
19 days → 4 hrs
Average fault response time after BMS-to-work-order automation
68%
Drop in occupant comfort complaints — fewer zones overcooled or underheated
+4.1 pts
AASHE STARS energy credit improvement — Silver to Gold rating achieved
Key Business Impact by Category
74% of total savings came from operational corrections requiring no capital investment — only data visibility through Oxmaint and schedule adjustments by existing staff.
The BMS was logging faults for years that nobody acted on. Once those alerts became Oxmaint work orders, our response time dropped from weeks to hours. That single change accounted for more savings than our entire lighting retrofit.
— Director of Facilities, Liberal Arts College, New England
Your BMS is already collecting the data. Oxmaint turns that data into maintenance work orders, PM schedules, and board-ready savings reports — without replacing your existing systems.
Frequently Asked Questions
Does Oxmaint integrate with existing building management systems?
Yes. Oxmaint connects to BMS platforms via API, BACnet, or CSV data feeds. BMS alert conditions are mapped to Oxmaint asset records and trigger work orders automatically — no BMS replacement required.
Book a Demo to walk through a BMS integration for your specific platform.
How long does a campus CMMS deployment typically take?
Most campus deployments reach operational status in 4–6 weeks. Asset registry build, BMS mapping, and PM schedule configuration can be completed in parallel. Measurable energy data typically appears within the first 30 days of submeter integration.
Can Oxmaint support AASHE STARS energy reporting?
Yes. Oxmaint exports consumption data aligned with OP-5 and OP-6 STARS credit requirements — kBTU/GSF by building, year-over-year trends, and verified savings documentation. This college improved its energy credits by 4.1 points using Oxmaint-sourced data.
Sign Up Free to begin building your verified STARS data record.
What is the ROI timeline for a CMMS deployment on a small campus?
This college achieved full program payback in under 4 months. Operational corrections from the first 8 months — requiring only schedule changes and minor repairs — delivered 74% of total savings with near-zero capital outlay.
Does Oxmaint support runtime-based PM scheduling for mechanical assets?
Yes. Oxmaint triggers PM work orders based on actual equipment runtime hours pulled from BMS or IoT sensor data — replacing calendar-based schedules with condition-aligned intervals. This eliminates unnecessary maintenance events while ensuring critical assets are never past due.
Can Oxmaint generate work orders automatically from BMS fault alerts?
Yes. Configurable fault detection rules in Oxmaint convert BMS threshold violations — setpoint deviations, simultaneous valve conditions, anomalous runtime — into maintenance work orders assigned to the appropriate technician automatically.
Book a Demo to configure a fault rule for your most common HVAC issue.
This college found $2.1 million in annual savings because they connected their BMS data to a maintenance workflow. Oxmaint gives your facilities team the same capability — in weeks, not years.