Maximo in the Wild: How Cornell, Madrid, and Spendrups Are Redefining Enterprise Asset Management

Enterprise asset management software is easy to evaluate on paper. Feature matrices, architecture diagrams, and vendor roadmaps all tell a clean story. But the real test of any EAM platform is what happens when it meets the messy reality of a living organization: legacy systems, constrained budgets, skeptical technicians, and assets that refuse to fail on schedule.

Three organizations, operating in radically different industries, have recently shared detailed accounts of their Maximo journeys. Cornell University manages a campus the size of a small city. The Madrid City Council oversees one of Europe's largest urban service ecosystems. Spendrups Bryggeri runs three brewery sites where production downtime directly impacts revenue. Their stories reveal patterns that apply far beyond their specific industries.

Cornell University: From Paper Work Orders to Predictive Maintenance

Cornell University's Ithaca campus spans more than 700 buildings across 2,300 acres. The facilities team handles over 800 service requests daily, covering everything from HVAC repairs to laboratory equipment maintenance. Before Maximo, this was a paper-driven operation.

The Starting Point

Cornell's pre-Maximo environment was fragmented. Different shops used different systems. Work order tracking relied on paper forms that moved through physical inboxes. Labor reporting was inconsistent. When a building automation system flagged an anomaly, there was no automated path from detection to work order creation.

The university made a strategic decision to standardize on Maximo as its single EAM platform. The implementation covered preventive maintenance, corrective maintenance, project maintenance, inventory management, and procurement.

Architecture Decisions

Cornell runs Maximo as the central hub of a broader facilities technology ecosystem. Key integration points include:

• Building Automation Systems (BAS): Siemens and Johnson Controls systems feed condition data into Maximo, enabling automated work order generation when equipment parameters drift outside normal ranges
• GIS Integration: Spatial data for underground utilities, landscaping, and campus infrastructure is linked to Maximo asset records
• Mobile Access: Technicians carry mobile devices with full Maximo functionality, enabling real-time labor reporting, parts lookups, and work order updates from the field
• Financial System: Maximo procurement and invoicing integrate with Cornell's enterprise financial system for budget tracking and cost allocation

The Mobile Transformation

The COVID-19 shutdown became an unexpected catalyst. With buildings largely empty, Cornell's facilities team needed to monitor equipment remotely and dispatch technicians efficiently when issues arose. The mobile Maximo deployment, which had been underway before the pandemic, became essential overnight.

Technicians could receive work orders on their devices, document findings with photos, report labor in real time, and close out work without returning to a desktop. This eliminated the end-of-day data entry backlog that had plagued the paper-based system. It also gave supervisors real-time visibility into technician location and workload, enabling dynamic resource balancing.

Measurable Outcomes

Cornell has reported several concrete results from its Maximo implementation:

• Paperless operations: The university went fully paperless for work order management, eliminating physical forms, filing cabinets, and manual data entry
• IT resource efficiency: System maintenance requirements dropped from five dedicated IT developers to two, freeing three technical staff for other critical initiatives
• Service request volume: Maximo now supports over 800 service requests daily with consistent processing and tracking
• Predictive maintenance expansion: Cornell is actively expanding its predictive maintenance capabilities, integrating additional building automation data sources and exploring condition-based maintenance triggers
• Sustainability impact: Better equipment maintenance translates to improved energy efficiency across the campus building portfolio

Lessons for Higher Education

Cornell's experience offers several transferable lessons for other universities:

1. Start with preventive maintenance: Cornell built credibility by first mastering scheduled PMs before tackling predictive use cases. This gave technicians confidence in the system and generated clean historical data.
2. Mobile is not optional: The mobile deployment was the single biggest factor in data quality improvement. When technicians enter data at the point of work, accuracy improves dramatically.
3. Integration with BAS is a force multiplier: The connection between building automation systems and Maximo turns anomaly detection into action. Without this link, BAS alerts require manual triage and often go unaddressed.
4. Plan for IT resource reallocation: The reduction from five developers to two was not a cost-cutting measure. It was a strategic reallocation that let Cornell invest technical talent in higher-value projects while Maximo handled routine maintenance workflows.

City of Madrid: A Unified Platform for Citywide Reliability

The Madrid City Council operates one of Europe's largest and most complex urban service ecosystems. The numbers are staggering: millions of assets under management, hundreds of thousands of inspections annually, over a million citizen service requests each year, and more than 25 service providers operating under diverse contract models and SLAs.

The Challenge

Madrid faced a classic public-sector dilemma. Operational demands were growing. Disruptive events, including extreme weather and infrastructure failures, had exposed gaps in the city's resilience. Budgets and staffing were constrained. The existing systems landscape was fragmented across departments and service providers, making it impossible to get a unified view of asset condition, maintenance backlog, or service performance.

The city had two options: build a custom system from scratch or adopt a proven platform. Building custom would have taken years and carried significant risk of delay or failure. The council chose IBM Maximo Application Suite because it delivered standardized processes, a shared operational backbone, and a single citywide asset inventory without requiring years of bespoke development.

The Scale of the Deployment

Madrid's MAS deployment manages a unified inventory of nearly five million assets. These span:

• Transportation infrastructure: Roads, bridges, tunnels, traffic signals, public transit assets
• Water and wastewater: Treatment plants, pumping stations, distribution networks, drainage systems
• Public buildings: Schools, administrative offices, cultural facilities, sports centers
• Green spaces: Parks, gardens, street trees, irrigation systems
• Street furniture: Benches, lighting, signage, waste receptacles
• Fleet: Municipal vehicles, emergency response equipment, maintenance vehicles

The Integration Challenge

Coordinating 25-plus service providers under a single platform required careful governance. Each provider had its own systems, processes, and data formats. Madrid used Maximo's integration framework to establish standardized data exchange patterns:

• Work order handoff: Service requests from the citizen portal flow into Maximo, are triaged, and are dispatched to the appropriate provider via automated routing rules
• Status synchronization: Providers update work order status through the JSON API, giving the city real-time visibility into service delivery
• SLA monitoring: Maximo tracks response and resolution times against contractual SLAs, automatically flagging violations for contract management
• Asset data federation: Each provider maintains asset data for its domain, but all data is federated into the central Maximo asset registry

Time-to-Value

Madrid's decision to adopt a platform rather than build custom was driven by time-to-value. The city needed results quickly, not a multi-year development project. MAS delivered:

• Immediate standardization: Rather than spending months defining data models and workflows, Madrid adopted Maximo's built-in processes and configured them to local requirements
• Rapid provider onboarding: The standardized integration patterns meant new service providers could be onboarded in weeks rather than months
• Single source of truth: For the first time, city leadership had a unified view of asset condition, maintenance activity, and service performance across all departments

Lessons for Municipal Government

Madrid's experience is particularly relevant for other cities considering EAM modernization:

1. Platform beats custom for speed: When time-to-value matters, a configurable platform like MAS delivers results faster than custom development. The trade-off is less customization, but Madrid found that Maximo's out-of-the-box processes were sufficient for most use cases.
2. Provider governance is the hard part: The technical integration was straightforward. The organizational challenge of getting 25-plus providers to adopt standardized processes was the real work. Madrid invested heavily in change management and provider training.
3. Asset inventory is foundational: The five-million-asset registry was not a nice-to-have. It was the prerequisite for everything else. Without a unified asset inventory, condition-based maintenance, SLA tracking, and capital planning are impossible.
4. Citizen service requests are a forcing function: The million-plus annual citizen requests created an urgency that drove adoption. When residents report potholes, broken streetlights, and overflowing bins, the system must work. This external pressure accelerated internal alignment.

Spendrups Bryggeri: From Schedule-Based to Data-Led Maintenance

Spendrups Bryggeri is one of Sweden's largest breweries, operating three production sites and supporting approximately EUR 380 million in annual business revenue. Brewing is an asset-intensive industry where equipment reliability directly impacts production output, product quality, and waste reduction.

The Starting Point

Spendrups operated on a traditional schedule-based maintenance model. Equipment was serviced at fixed calendar intervals regardless of actual condition. This approach is common in food and beverage manufacturing because it is simple to manage and satisfies regulatory requirements. But it has significant drawbacks:

• Over-maintenance: Equipment that is running well gets serviced unnecessarily, consuming labor and parts
• Under-maintenance: Equipment that is degrading faster than expected goes unaddressed between scheduled intervals
• No condition visibility: Without real-time equipment data, maintenance decisions are based on the calendar rather than reality

The Shift to Data-Led Maintenance

Spendrups deployed Maximo Application Suite to shift from schedule-based to data-led maintenance across all three brewery sites. The implementation focused on:

• Condition monitoring integration: Sensors on critical brewing equipment (fermentation tanks, bottling lines, pasteurizers, refrigeration systems) feed real-time data into Maximo Monitor
• Predictive analytics: Maximo Predict analyzes historical failure data and real-time sensor readings to identify degradation patterns before they cause downtime
• Work order automation: When condition thresholds are breached or Predict identifies an emerging failure pattern, Maximo automatically generates a prioritized work order
• Mobile execution: Maintenance technicians receive work orders on mobile devices with full asset history, parts availability, and step-by-step procedures

Measurable Outcomes

Spendrups has reported several concrete improvements:

• Production reliability: Reduced unplanned downtime through earlier detection of equipment degradation
• Waste reduction: Better-maintained equipment produces fewer quality deviations, reducing product waste
• Maintenance efficiency: Technicians focus on the work that matters most rather than working through fixed schedules
• Sustainability: Equipment running at peak efficiency consumes less energy and produces less waste, supporting Spendrups' sustainability goals

Lessons for Manufacturing

Spendrups' experience offers insights for any manufacturer considering the shift to condition-based maintenance:

1. Start with critical assets: Spendrups did not instrument every pump and motor on day one. They identified the assets where downtime has the highest business impact and focused sensor deployment and predictive modeling there.
2. Historical data is the foundation: Maximo Predict's failure prediction models depend on clean historical work order data. Spendrups invested in data quality before deploying predictive analytics.
3. The cultural shift is real: Moving from "we service this every 90 days" to "we service this when the data says it needs it" requires trust in the system. Spendrups built this trust gradually by demonstrating that Predict's recommendations aligned with technician experience.
4. Integration with production scheduling matters: In brewing, you cannot take a bottling line offline during a production run. Spendrups integrated Maximo's maintenance scheduling with production planning to ensure maintenance windows align with production downtime.

Cross-Industry Patterns

Despite operating in completely different sectors, Cornell, Madrid, and Spendrups share common patterns in their Maximo journeys:

Pattern 1: Mobile is the Catalyst

All three organizations identified mobile access as the single most transformative capability. When technicians can receive, execute, and close work orders from the field, data quality improves, labor reporting becomes accurate, and supervisors gain real-time visibility. Mobile is not a convenience feature. It is the foundation of data-driven maintenance.

Pattern 2: Integration is the Hard Part

The Maximo platform itself was not the challenge. The hard work was integrating Maximo with the surrounding ecosystem: building automation systems at Cornell, 25-plus service providers in Madrid, production scheduling at Spendrups. Organizations that underestimate integration complexity pay for it in extended timelines and frustrated users.

Pattern 3: Data Quality Precedes AI

All three organizations are exploring or deploying AI capabilities (Predict, Condition Insight, visual inspection). But none of them started there. Each began by establishing clean, consistent data in core Maximo modules: assets, work orders, failure codes, and meter readings. AI without quality data produces unreliable recommendations that erode user trust.

Pattern 4: Change Management Determines Success

The organizations that succeeded invested heavily in change management. They trained technicians, communicated the vision, addressed skepticism, and celebrated early wins. The organizations that treated Maximo as a pure technology project struggled with adoption regardless of how well the software was configured.

Practical Implications

If you are planning or executing a Maximo implementation, these case studies suggest several actionable priorities:

1. Invest in your asset hierarchy before anything else: Cornell's 700 buildings, Madrid's five million assets, and Spendrups' brewery equipment all required clean, well-structured asset records. This is unglamorous work, but it is the foundation everything else depends on.
2. Prioritize mobile deployment early: Do not treat mobile as a phase two enhancement. The data quality improvements from point-of-work data entry compound over time and make every subsequent capability (reporting, analytics, AI) more valuable.
3. Plan integration architecture before configuration: Map your integration points before you start configuring Maximo. Knowing which systems need to connect, what data flows in which direction, and what the latency requirements are will prevent rework.
4. Build credibility with preventive maintenance before pursuing predictive: Predictive maintenance sounds exciting, but it requires historical failure data that only comes from consistent preventive maintenance execution. Walk before you run.
5. Budget for change management: The software license is not the expensive part. Training, process redesign, and organizational change management are where the real investment happens. Organizations that shortchange this spend more on rework and adoption remediation.

Bottom Line

Cornell, Madrid, and Spendrups demonstrate that Maximo Application Suite delivers value across radically different industries and scales. The common thread is not the software itself but the organizational commitment to data quality, mobile enablement, and integration architecture. Organizations that treat Maximo as a technology project get a technology platform. Organizations that treat it as an operational transformation get measurable improvements in reliability, efficiency, and service delivery.

The most important lesson from these case studies is that the technology works. The variable is whether the organization is ready to do the hard work of data cleanup, process standardization, and change management that makes the technology valuable.