When a state university system operates eight campuses under one governing board, "standardization" usually stays a slide in a strategic plan — every campus runs its own spreadsheets, its own vendor relationships, and its own definition of what counts as a completed work order. That changes the moment a system-level facilities director needs to answer one simple question for the board: how many deferred maintenance items exist across the entire system right now, and what do they cost. This case study follows how one state university system took Oxmaint from a single pilot campus to all eight campuses in twelve weeks, building a shared PM template library, campus-level access controls, and a system-wide reporting dashboard that the central office uses for budget planning. If your system is managing eight different versions of the same maintenance program, start a free trial to see how a shared CMMS structure works across campuses, or book a demo to walk through a multi-campus rollout plan.
Eight Campuses, One CMMS, Twelve Weeks
A state university system replaced eight independent maintenance tracking methods with one Oxmaint instance — shared PM templates, campus-level dashboards, and a single system-wide report for the board.
Eight Campuses, Eight Different Ways of Tracking the Same Work
Before standardization, each campus in the system managed facilities maintenance independently. Some used spreadsheets, some used an older legacy CMMS that had not been updated in years, and at least two campuses tracked work orders through email threads and paper logs. The result was a system office that could not answer a basic budget question: across all eight campuses, how many HVAC units are past their service interval, and what would it cost to bring every campus current. Each campus had its own asset naming conventions, its own PM schedules built by whoever happened to be the maintenance supervisor at the time, and no shared reporting format. When the system office requested deferred maintenance data for a capital planning cycle, it took three separate follow-up rounds and six weeks to assemble a report that everyone agreed was still incomplete.
A Twelve-Week Phased Deployment Across Eight Campuses
The system office selected one mid-sized campus as the pilot. Facilities staff built a master PM template library covering HVAC, plumbing, electrical, life safety, and grounds equipment — the categories common across all eight campuses.
The pilot campus registered its full asset inventory in Oxmaint, mapped each asset to the shared template library, and ran the first PM cycle to confirm the templates worked in real conditions before scaling.
The remaining seven campuses were rolled out in two waves of three to four campuses each, using the validated template library and a standardized onboarding checklist developed during the pilot.
With all eight campuses live, the system office activated a portfolio-level dashboard showing PM compliance, open work orders, and deferred maintenance estimates by campus and system-wide.
One PM Template Library, Eight Campus Implementations
The core of the standardization was the shared PM template library. Instead of each campus building its own PM schedules from scratch, the system office defined a master set of templates for common asset types — air handling units, boilers, chillers, electrical switchgear, fire alarm panels, elevators, and roofing systems — with default intervals based on manufacturer recommendations and ASHRAE guidance. Each campus could adjust intervals for local conditions, such as coastal campuses requiring more frequent corrosion inspections, but the underlying template structure stayed consistent. This meant that when the system office pulled a report on chiller PM compliance, it was comparing the same service actions across all eight campuses rather than eight different definitions of "chiller maintenance."
| Asset Category | Before Standardization | After Standardization |
|---|---|---|
| HVAC PM Definitions | 8 different schedules across campuses | 1 shared template, campus-adjustable intervals |
| Asset Naming | No consistent convention | System-wide naming standard |
| Reporting Format | Manual compilation, 6+ weeks | Live dashboard, real-time |
| Deferred Maintenance Visibility | Campus-level only, inconsistent | System-wide, comparable across campuses |
Campus-Level Access With System-Level Visibility
Each campus team works within its own asset list, work orders, and PM schedules — daily operations look and feel local, with no need to navigate other campuses' data.
Campus directors see their full campus dashboard plus benchmark comparisons against system-wide averages for PM compliance and response times.
The system office sees a portfolio rollup across all eight campuses — overdue PMs, open critical work orders, and deferred maintenance estimates — without needing to log into each campus instance separately.
Standardizing a Multi-Campus System Doesn't Require a Multi-Year Project
With a shared template library and a phased wave rollout, a state university system brought eight campuses onto one CMMS in twelve weeks — giving the board its first true system-wide view of facilities condition. If your system is ready to move from eight spreadsheets to one dashboard, talk to the Oxmaint team about a multi-campus rollout plan built around your asset categories and campus structure.
What Changed After the Rollout
Frequently Asked Questions
How long does a multi-campus CMMS rollout typically take?+
Can each campus keep some independence in how it manages PM schedules?+
Does the system office need to log into each campus separately to see overdue PMs?+
What happens to existing asset data from each campus's old system?+
Is this approach only for large state systems with many campuses?+
Ready to Give Your System Office One View Across Every Campus
A shared PM template library, campus-level access, and a system-wide dashboard turned eight separate maintenance programs into one. Get started with a pilot campus and a rollout plan built for your system's structure.
