Utilities and Renewables in MAS 9.1: What NYPA, Wind Operators, and Water Utilities Built Differently

The utilities and renewables sector is the largest single vertical for IBM Maximo Application Suite, and the sector that has invested most aggressively in the MAS 9.1 feature set. New York Power Authority (NYPA), the largest state public power organization in the United States and the first electric utility in North America to earn ISO 55001 certification, has been the most visible public reference. NYPA manages approximately 60,000 power generation and transmission assets on Maximo and runs the Maximo for Transportation module for approximately 1,600 fleet vehicles. The work that matters, though, is not the asset count. It is the patterns: how the asset health scores are produced, how the FMEA mapping is structured, how the work management is integrated with the GIS, and how the AppPoint footprint is tuned for the utility's specific mix of authorized and concurrent users.

This article is a pattern library drawn from three reference deployments: NYPA-style transmission and distribution, a North American wind and solar operator with 4,000+ MW of capacity, and a regional water utility serving 1.4 million customers. The patterns are the ones that survived the MAS 9.1 upgrade and that have measurable operational impact.

Pattern 1: Compatible Unit Estimating for T&D Work

The Compatible Unit (CU) library is the cornerstone of transmission and distribution work management. A CU is a standardized bundle of labor, materials, tools, and time required to perform a specific unit of work, such as "replace a 100 kVA pole-mounted transformer". Utilities build CU libraries over years, and the libraries encode the utility's preferred construction practices, vendor preferences, and labor standards. The Maximo for Utilities solution includes a CU Estimating (CUE) module and a multilevel CU library structure.

In MAS 9.1, the CU library is exposed through the REST API and integrated with Maximo Spatial for map-based work planning. The pattern:

CU Library structure:
  CU Category: "Pole-Mount Transformer"
    CU: "REPLACE-PMT-100KVA"
      Labor:
        - Electrician, 4 hours
        - Apprentice, 4 hours
      Materials:
        - Transformer 100 kVA, qty 1
        - Connector kit, qty 1
        - Ground wire, 50 ft
      Tools:
        - Bucket truck, 4 hours
        - Hot stick, 4 hours
      Estimated duration: 8 hours
      Estimated cost: $4,200
      Crew type: T&D-2-PERSON

The CU is referenced from a Compatible Unit Work Plan, which is attached to a work order. When the work order is created, the CU expands into the planned labor, materials, and tools. The actuals are reconciled against the plan at work order close. The variance analysis is the input to the CU library refinement cycle.

In MAS 9.1, the CU library is searchable through the Maximo AI Assistant. A planner can ask "What is the CU for replacing a 100 kVA pole-mount transformer in a coastal environment?" and the Assistant returns the matching CU with the appropriate regional modifier.

Pattern 2: Crew Management and Crew Composition

Utilities dispatch crews, not individual workers. A crew is a collection of workers with the qualifications required for the work. Maximo for Utilities includes enhanced crew management that tracks crew composition, qualifications, and availability. In MAS 9.1, the crew management is integrated with Maximo Scheduler and with the GIS-based routing system.

The pattern:

crew:
  id: "T&D-NORTH-2"
  description: "T&D North Service Area, 2-Person Crew"
  primary_qualifications:
    - "ELECTRICIAN-LICENSE-STATE"
    - "HOT-STICK-CERTIFIED"
  secondary_qualifications:
    - "FIRST-AID-CURRENT"
    - "CDL-CLASS-B"
  members:
    - laborcode: "E-1024"
      role: "LEAD"
      qualifications: ["ELECTRICIAN-LICENSE-STATE", "HOT-STICK-CERTIFIED", "FIRST-AID-CURRENT"]
    - laborcode: "E-1187"
      role: "APPRENTICE"
      qualifications: ["APPRENTICE-YEAR-3", "HOT-STICK-CERTIFIED", "FIRST-AID-CURRENT"]
  availability:
    shift_start: "07:00"
    shift_end: "15:30"
    work_days: ["MON", "TUE", "WED", "THU", "FRI"]
  assigned_territory: "SERVICE-AREA-NORTH"
  vehicle: "BUCKET-12"

The crew is the work assignment unit. The Maximo Scheduler assigns work orders to crews, not to individual workers. The crew's qualifications are validated against the work order's required qualifications, and a crew cannot be assigned to a work order that requires a qualification the crew lacks. This is the safety enforcement layer.

In MAS 9.1, the Maximo AI Assistant can recommend crew assignments based on proximity, qualifications, and current workload. The pattern is useful for storm response, when the dispatch team is overloaded and needs a quick way to identify the best available crew.

Pattern 3: Health Scores Aligned to ISO 55001

NYPA's ISO 55001 certification is the public marker of the asset management maturity that the rest of the sector is working toward. ISO 55001 requires evidence-based decision-making for asset investment, risk management, and lifecycle optimization. Maximo Health produces the evidence: health scores, criticality scores, risk scores, and end-of-life estimates for each asset.

The MAS 9.1 pattern:

Asset: TX-4471 (Power Transformer, 230/115 kV, 200 MVA)
  Health Score: 72 (Good)
  Criticality Score: 95 (Critical - transmission hub)
  Risk Score: 22 (Moderate)
  End-of-Life Estimate: 2032 (based on health trend)
  Contributing Factors:
    - DGA trend: stable
    - Bushing condition: minor degradation
    - Load profile: within nameplate
    - Age: 18 years
  Recommended Actions:
    - Continue quarterly DGA sampling
    - Schedule detailed inspection Q4 2026
    - Review for end-of-life replacement planning
  FMEA Match: None (no active failure modes)

The health score is calculated by Maximo Health from a combination of asset-specific data (age, maintenance history, cost data), sensor data (from Maximo Monitor), and predictive alerts (from Maximo Predict). The criticality score is calculated from the asset's role in the network (NYPA uses a custom criticality calculator that weights substations, transmission corridors, and generation assets differently). The risk score is the product of health and criticality.

The ISO 55001 audit trail is the historical record of these scores. NYPA publishes the scores quarterly to the asset investment review committee, and the committee uses the scores to prioritize capital investment. The pattern is reproducible: any utility with Maximo Health, Predict, and Monitor can produce the same evidence chain.

Pattern 4: Wind and Solar Fault Code Taxonomy

A North American wind and solar operator with 4,000+ MW of capacity uses Maximo to manage work across hundreds of wind farms and solar sites. The pattern that matters most is the custom fault code taxonomy. The fault codes are the structured way the company captures failure, cause, and remedy data on every work order. The data feeds the reliability engineering team, which uses it to identify systemic issues and to refine the PM strategy.

Fault Code Structure:
  Failure (Problem): WIND-TURBINE-GEARBOX-OVERHEAT
  Cause: LUBE-OIL-DEGRADED
  Remedy: OIL-CHANGE-COMPLETED
  
  Failure (Problem): SOLAR-INVERTER-DC-OVERVOLTAGE
  Cause: STRING-MISMATCH
  Remedy: STRING-RECONFIGURED

  Failure (Problem): WIND-TURBINE-PITCH-SYSTEM-FAULT
  Cause: HYDRAULIC-LEAK
  Remedy: SEAL-REPLACED

The fault codes are not free text. They are a controlled vocabulary maintained by the reliability engineering team. New codes are added through a formal review process that includes the reliability team, the field service team, and the warranty management team. The result is a structured dataset that supports root cause analysis, warranty claim tracking, and PM optimization.

In MAS 9.1, the Maximo AI Assistant can query the fault code history and produce reliability summaries: "What are the top 5 failure modes for the GE 1.5 MW fleet over the last 12 months?" The response is grounded in the fault code data and includes the associated work orders, asset population, and recommended PM changes.

Pattern 5: Travel Time Matrix and Bundling

For wind farms with hundreds of turbines spread across hundreds of square miles, travel time is a significant operational cost. Maximo for Utilities includes a destination travel time matrix that calculates travel times between service addresses. In MAS 9.1, the matrix can be run as a cron task to compute travel times between all asset pairs on a regular cadence.

The pattern:

# Cron task to compute travel time matrix
cronTask:
  name: "TRAVEL_TIME_MATRIX"
  description: "Compute travel time matrix between all service addresses"
  schedule: "0 0 1 * * ?"  # First of every month
  parameters:
    siteId: "WIND-FARM-WEST"
    assetClass: "WIND-TURBINE"
    maxTravelTimeMinutes: 240
    originPoints: "ASSETS_WITHIN_SITE"
    destinationPoints: "ASSETS_WITHIN_SITE"
    travelMode: "DRIVING"
    outputTable: "TRAVEL_TIME_CACHE"

The matrix is used by the planning team to bundle work orders. A technician assigned to a turbine can pick up adjacent work orders on the same trip, reducing travel time by 20 to 30%. The renewable operator reports a 25% reduction in travel time and a 30% reduction in maintenance spend as a result of the bundling.

Pattern 6: Service Provider and O&M Contracts

Renewable operators frequently outsource O&M (operations and maintenance) to third-party service providers. The Maximo Service Provider module supports O&M contract management, including the capture of work and resources used, and the facilitation of customer billing for non-owned renewable assets.

The pattern:

serviceProvider:
  id: "SP-SOLAR-MAINT-001"
  description: "Solar Maintenance Service Provider"
  contractType: "O&M-FIXED-FEE-PER-MW"
  scope:
    assetClasses: ["SOLAR-PANEL", "SOLAR-INVERTER", "SOLAR-TRANSFORMER"]
    serviceAreas: ["WEST-REGION", "CENTRAL-REGION"]
    serviceTypes: ["PREVENTIVE", "CORRECTIVE", "EMERGENCY"]
  rateSchedule:
    preventive: "$15/MW/month"
    corrective: "$250/incident"
    emergency: "$500/incident"
  billingCycle: "MONTHLY"
  contractStart: "2026-01-01"
  contractEnd: "2026-12-31"
  slaRequirements:
    responseTime: "EMERGENCY: 4 hours, CORRECTIVE: 24 hours, PREVENTIVE: 7 days"
    firstTimeFix: "85%"
    availability: "99.5%"

The service provider's work orders flow through Maximo, and the billing is calculated from the work order data. The asset owner has visibility into the service provider's performance through Maximo dashboards. The SLA compliance is tracked and reported monthly.

Pattern 7: Condition-Based Maintenance for Transmission Assets

A regional water utility serves 1.4 million customers through 5,200 miles of pipeline, 42 treatment plants, and 180 pump stations. The asset base is geographically dispersed, and the failure modes range from slow leaks to catastrophic pipe bursts. The utility adopted Maximo Health and Predict to move from time-based PM to condition-based maintenance.

The pattern uses Maximo Monitor to collect vibration and pressure data from the pump stations. The predictive models in Maximo Predict score the pump health daily. The Maximo AI Assistant runs the daily Condition Insight query to summarize the pump fleet status and recommend work. The output is a daily briefing emailed to the operations manager.

The result, reported in the utility's 2025 annual report, was a 15% reduction in unplanned downtime and a 20% reduction in maintenance cost per pump. The savings funded the expansion of the predictive program to the treatment plants in 2026.

Pattern 7: Storm Response and Mutual Assistance

Utilities face the storm response challenge every hurricane season, every ice storm, every wildfire season. The work is not the routine work management; it is the surge response when the routine system is overwhelmed by damage. Maximo for Utilities supports storm response through a dedicated Storm module that handles crew mobilization, mutual assistance, damage assessment, and restoration tracking. In MAS 9.1, the Storm module is integrated with Maximo Mobile, the GIS system, and the Maximo AI Assistant for real-time situational awareness.

The storm response pattern:

1. Pre-storm preparation. The storm module pre-positions crews and materials at staging areas. The crews are scheduled in Maximo Scheduler with extended shifts. The materials (poles, transformers, conductor) are pre-staged at the staging areas with the inventory updated in Maximo.
2. Damage assessment. As the storm hits and damage reports come in, the storm module captures each damage location, the asset affected, the damage type, and the estimated restoration time. The damage assessments feed the GIS map and the operations dashboard.
3. Crew dispatch. The dispatch team uses the Storm module to assign crews to damage sites. The dispatch considers crew qualifications, proximity, and current workload. The Maximo AI Assistant recommends crew assignments based on the damage priority and the crew's qualifications.
4. Restoration tracking. As crews restore service, the Storm module updates the restoration status. The operations dashboard shows the real-time restoration progress. The Maximo Mobile app allows the field crews to update the status from the field.

The mutual assistance pattern allows utilities to bring in crews from other utilities when the local crews are overwhelmed. The mutual assistance crews are temporary workers in Maximo, with the qualifications and certifications documented. The crew assignments respect the qualifications, and the work orders flow through the same Maximo work management discipline.

In MAS 9.1, the Storm module integrates with the Maximo AI Assistant for natural-language queries during the storm. The incident commander can ask "Show me all open damage reports in the BEDFORD service area that are more than 4 hours old and not yet assigned" and get a real-time answer. The pattern reduces the time spent on dashboard navigation during the storm.

Pattern 8: Regulatory Compliance and Reporting

Utilities operate under extensive regulatory oversight: NERC for the bulk electric system, state public utility commissions for distribution, environmental agencies for emissions and water quality, OSHA for worker safety. Maximo for Utilities includes regulatory compliance features that support the reporting requirements. The MAS 9.1 pattern uses the Condition Insight capability to produce regulatory briefings on demand.

The compliance pattern:

complianceProgram:
  - regulation: "NERC-TPL-001-5.1"
    description: "Transmission Planning Standards"
    reportingCadence: "ANNUAL"
    dataSources:
      - "ASSET"
      - "WORKORDER"
      - "INSPECTION"
      - "FAILURE"
    maximoReports:
      - "TPL-001-Asset-Health-Summary"
      - "TPL-001-Failure-History"
      - "TPL-001-Mitigation-Actions"
    aiBriefing: "NERC-TPL-001-Condition-Summary"
  
  - regulation: "OSHA-1910.269"
    description: "Electric Power Generation, Transmission, Distribution"
    reportingCadence: "INCIDENT"
    dataSources:
      - "WORKORDER"
      - "INCIDENT"
      - "SAFETY"
    maximoReports:
      - "OSHA-Recordable-Incident-Detail"
      - "OSHA-Near-Miss-Summary"
    aiBriefing: "OSHA-Safety-Trend-Summary"

The regulatory reports are BIRT reports that pull from the standard Maximo object structures. The AI briefings are Condition Insight queries that produce natural-language summaries. The reports and the briefings are reviewed by the regulatory affairs team before submission.

The pattern reduces the regulatory reporting effort from weeks to days because the data is already structured in Maximo. The traditional approach (rebuilding the data in spreadsheets for each reporting cycle) is replaced by the live Maximo queries. The audit trail is clear because the data is traceable to the underlying work orders, inspections, and failure records.

Common Pitfalls in the Utilities Vertical

The first pitfall is to deploy Maximo for Utilities without the CU library. The CU library is the foundation of the work estimation and the asset investment planning. Without it, the work management degrades to free-text descriptions and the estimating is per-work-order. The CU library is the work. Build it first.

The second pitfall is to treat the crew management as a feature instead of a discipline. Crew management only works if the qualifications are current and the assignments respect them. The qualifications drift if they are not audited regularly.

The third pitfall is to deploy the predictive models without the sensor data. Maximo Predict needs Maximo Monitor to provide the time-series data. The utilities that get the most value deploy Maximo Monitor first and Maximo Predict second, in that order.

The fourth pitfall is to ignore the AppPoint footprint. Utilities have large authorized user populations (every lineworker is a Maximo user), and the AppPoint cost for an authorized user is 3 to 5 points per user depending on tier. A 500-lineworker utility with Base tier authorized users consumes 1,500 to 2,500 AppPoints per month just for user entitlements. The license negotiation should account for this.

Best Practices

1. Build the CU library before going live. The CU library is the foundation of the work estimation. It is also the foundation of the ISO 55001 evidence trail.
2. Treat crew management as a discipline. Qualifications drift if they are not audited. Schedule the audit.
3. Deploy Monitor before Predict. The predictive models need the sensor data. Deploy in order.
4. Standardize the fault code taxonomy. The reliability data is only as good as the fault code vocabulary. Maintain it actively.
5. Negotiate AppPoints based on the user population. Utilities have large authorized user populations. The license should reflect the reality.

Practical Implications

The utilities vertical is where MAS 9.1's full feature set pays off. Maximo Health, Predict, Monitor, the AI Assistant, the Condition Insight capability, and the Utilities industry solution work together to produce the asset investment evidence that ISO 55001 demands. The patterns above are the operating model.

For utilities that have not yet deployed the full stack, the right starting point is Maximo Health. The health scores produce immediate value: the reliability team gets a consistent view of asset condition across the fleet, and the asset investment review committee gets the evidence for capital prioritization. Add Predict and Monitor incrementally, then add the AI Assistant and Condition Insight.

For renewable operators, the Maximo Service Provider module is the right starting point. The contract management and billing automation produce immediate savings. Add the fault code taxonomy and the reliability analysis produces the data that drives the PM optimization.

Bottom Line

Utilities and renewable operators have built Maximo environments that are the most mature in the MAS ecosystem. The patterns above are the field-tested defaults: CU libraries, crew management, ISO 55001 evidence, fault code taxonomies, travel time bundling, service provider contracts, and condition-based maintenance. Each pattern is the work of years of refinement by the practitioners who run the systems. Adopt the patterns, do the data work, and the operational results follow.

Sources

• [The drive to digitize at New York Power Authority](https://www.ibm.com/case-studies/new-york-power-authority)
• [Renewable energy: Meeting demand (IBM case study PDF)](https://www.ibm.com/downloads/cas/APM6E8RX)
• [Energy and utilities asset management software - Maximo](https://www.ibm.com/products/maximo/energy-utilities)
• [IBM Maximo for Utilities (overview)](https://www.slideshare.net/slideshow/ibm-maximo-for-utilities/4910404)
• [IBM Maximo Health (product brief PDF)](https://www.ibm.com/downloads/documents/us-en/10a99803c6afda55)
• [IBM introduces Maximo Condition Insight](https://www.ibm.com/new/announcements/maximo-condition-insight)