Middle East Momentum: What KAFD and Marafiq Reveal About MAS at National Scale

Two IBM Maximo wins in Saudi Arabia in a single week — KAFD running MAS for smart-city asset management and Marafiq modernizing enterprise service delivery — signal a structural shift: the Middle East is becoming one of the most consequential regions for the future of Maximo. What national-scale…

Share
Middle East Momentum: What KAFD and Marafiq Reveal About MAS at National Scale

Middle East Momentum: What KAFD and Marafiq Reveal About MAS at National Scale

Category: Industries

Something notable happened in early September 2026 that should reshape how Maximo practitioners think about regional markets. Within the span of a single week, IBM announced two separate Maximo-related customer wins in Saudi Arabia, both tied to the LEAP 2026 technology conference in Riyadh. King Abdullah Financial District, better known as KAFD, is running Maximo Application Suite for smart-city asset management and has even registered a custom Transition Management App with the Saudi Authority for Intellectual Property. Days earlier, Marafiq, the joint-venture utility serving Saudi Arabia's industrial cities, confirmed it is modernizing its enterprise service delivery with IBM. These are not isolated logo wins. Together they signal something bigger: Maximo Application Suite has become a platform of choice for national-transformation-scale asset management in the Gulf, and the Middle East is quietly becoming one of the most consequential regions for the future of the product.

For most of its twenty-plus year history, Maximo's center of gravity sat firmly in North America and Western Europe. The largest user groups were American and British. The most vocal practitioners blogged in English from the US Midwest, the UK, and Australia. The Middle East was a market where Maximo had enterprise footprints, particularly in oil and gas and utilities, but it was rarely where the conversation started. That is changing, and the change is being driven by something structural rather than cyclical. Saudi Arabia's Vision 2030 program has created a class of mega-projects and giga-projects that need asset management at a scale the industry has genuinely never seen before. New financial districts, new industrial cities, new utilities, new tourism infrastructure, all of it built on modern digital foundations from day one. When those projects pick an asset management platform, they are not migrating from anything. They are making a first-generation platform decision at national scale, and increasingly that decision is MAS.

This article looks at what the KAFD and Marafiq announcements actually tell us, why Vision 2030 changes the traditional buying pattern for enterprise asset management, and what the global Maximo ecosystem should take away from the Middle East's rising momentum. Whether you are a practitioner deciding where to invest your career, a partner sizing your regional strategy, or a customer wondering whether MAS is maturing fast enough for your own program, the Gulf is now one of the best live laboratories for answering those questions.

The LEAP 2026 Signal: Two Announcements, One Week

LEAP has quickly become one of the world's largest technology conferences, and it functions as the showcase event for Saudi Arabia's digital transformation agenda. Vendors bring their biggest regional announcements there because that is where the buyers, the government stakeholders, and the press all converge. Against that backdrop, two Maximo-related announcements landing within the same window is itself a signal. IBM does not distribute its conference-stage time randomly, and two distinct asset management stories in a single event cycle suggests an active, growing pipeline rather than a one-off reference customer.

The first story is KAFD. King Abdullah Financial District is Riyadh's purpose-built financial hub, a district of towers, transit connections, public spaces, and the operational complexity that comes with running what is effectively a small city. The announcement confirms KAFD runs MAS for smart-city asset management, which means Maximo is now responsible for the physical estate of one of the region's highest-profile urban developments. Perhaps more interesting is the detail that KAFD has registered a custom Transition Management App with the Saudi Authority for Intellectual Property. That is a level of product investment that goes well beyond typical customer configuration. It says the district's operators found gaps between generic facilities management workflows and the realities of running a financial district, and they built and protected their own intellectual property to close those gaps on top of MAS. Custom apps registered with a national IP authority are also a form of commitment. You do not make that investment in a platform you plan to leave.

The second story is Marafiq, the utility jointly owned by Saudi Aramco and ACWA Power that provides power, water, and utility services to the industrial cities of Jubail and Yanbu. Marafiq announced it is modernizing enterprise service delivery with IBM, and while the public details are lighter than the KAFD story, the context matters. Industrial cities are among the most asset-dense environments that exist: generation assets, desalination and water treatment trains, distribution networks, and the customer-facing service layer on top. Modernizing service delivery in that environment with MAS in the picture means the platform is being positioned not just as maintenance back office but as part of the customer experience stack. That is a broader mandate than classic Maximo deployments typically carried.

Two announcements do not make a trend by themselves. But read them against the wider pattern, smart-city operators and industrial utilities adopting MAS at transformation scale within days of each other, and the direction becomes hard to ignore.

KAFD: Smart City Asset Management as a New Reference Class

Smart city is a term that has been abused by a decade of vendor slide decks, so it is worth being precise about what a Maximo deployment in a financial district actually involves. KAFD is not managing abstract sensors on a dashboard. It is managing a physical district: dozens of buildings, district cooling, electrical infrastructure, vertical transportation, public realm assets, parking, security systems, and the lifecycle of every one of those assets from commissioning through renewal. The asset management problem in a district like that is closer to a combination of an airport, a corporate campus, and a municipality than to anything else in the traditional Maximo world.

That is exactly why the KAFD story matters as a reference. For years, Maximo practitioners have debated whether the platform could stretch beyond its industrial and facilities roots into genuine urban-scale asset management. Smart city pilots have come and gone, often built on bespoke IoT platforms with thin connections to real maintenance execution. What KAFD represents is different: a major urban district betting its operational backbone on MAS, the same platform used by utilities and manufacturers, rather than on a purpose-built smart city stack. The implication for other district operators, airports, ports, campuses, and new city developers is straightforward. There is now a reference deployment showing that MAS can carry that class of workload.

The Transition Management App detail deserves its own moment. Transition management, moving occupants into and out of buildings, coordinating fit-outs, handling the operational churn of a district still under active development, is one of those workflows that generic CMMS configurations handle awkwardly. KAFD building a custom app for it, and registering that app with SAIP, tells you two things. First, the MAS application framework is extensible enough that a customer can build and productize their own domain app on top of it. Second, regional customers are treating MAS as a platform to build on, not a product to consume. That distinction is the whole MAS thesis: one platform, common data model, domain applications on top. KAFD is an early proof point of the platform idea being exercised by a customer rather than described by a vendor.

For practitioners, there is also a career signal here. Smart city and district-scale asset management is emerging as a genuine specialization within the Maximo world, one that blends facilities, infrastructure, IoT, and urban operations. The people who build the first wave of skills in that space, ideally in environments like KAFD where the scale is real, will be scarce and valuable as other districts and mega-projects come online.

Marafiq: Service Delivery Modernization in Industrial Cities

If KAFD shows MAS extending into new territory, Marafiq shows it deepening in the territory Maximo has owned for decades. Jubail and Yanbu are the crown jewels of Saudi industrial policy, purpose-built cities that host refining, petrochemical, and heavy manufacturing on a massive scale. Marafiq supplies the power, desalinated water, and utility infrastructure those industries run on. In asset management terms, that is about as classic a Maximo environment as exists: regulated, capital-intensive, reliability-obsessed infrastructure.

What is new in the announcement is the framing around enterprise service delivery. Traditional Maximo deployments in utilities centered on maintenance execution: work orders, permits, planning and scheduling, asset hierarchies. Service delivery modernization is a broader brief. It implies the utility's interaction with its industrial customers, connection requests, service provisioning, outage communication, billing-adjacent processes, is being rethought with the asset management platform as part of the backbone. Whether that happens through MAS's own service management capabilities, through integration with adjacent IBM or third-party systems, or through custom applications in the KAFD mold, the direction is the same. The asset management platform is being pulled outward from the maintenance back office toward the customer edge.

This mirrors a pattern visible across the MAS customer base. As Maximo Application Suite consolidates what were previously separate products, the line between asset management, service management, and operational technology blurs. Utilities were always going to be the proving ground for that convergence because they live at the intersection of physical assets and customer obligations. A Marafiq-scale deployment gives IBM and the broader ecosystem a live demonstration of MAS handling that convergence in one of the most demanding industrial settings in the world.

There is also a regional significance to the Marafiq story that should not be understated. Saudi Aramco's ecosystem of joint ventures and suppliers functions as a talent and practices network across the Gulf. Operational standards, integration patterns, and even personnel move between Aramco, its joint ventures like Marafiq and SABIC-affiliated operations, and the wider industrial base. A visible MAS success at Marafiq does not stay contained. It propagates through that network the way reference deployments always have in the Maximo community, just at a larger scale than the traditional user-group reference call.

Why Vision 2030 Changes the Buying Pattern

The deepest reason the Middle East momentum matters is that Vision 2030 changes the fundamental structure of asset management buying decisions. In mature markets, most Maximo deals are replacement or migration deals. A utility has been on Maximo 7.6 for fifteen years and faces the end of support. A manufacturer is consolidating a patchwork of regional instances. The buyer's psychology is risk-averse, anchored to existing processes, and measured against the cost of staying put. Those dynamics have shaped Maximo sales and, honestly, shaped the product's pace of change for a decade.

Vision 2030 inverts that psychology. The Kingdom's flagship programs, NEOM, the Red Sea developments, Qiddiya, Diriyah, the expansion of Riyadh itself, are net-new builds. They have no legacy Maximo estate to migrate and no fifteen-year habits to unwind. Their platform decisions are first-generation choices made by leadership teams explicitly mandated to adopt modern technology. When one of those programs selects MAS, it is selecting the current suite, the cloud architecture, the AI capabilities, and the application framework, not a modernized wrapper around 2005-era deployment patterns. That is the healthiest possible kind of adoption for a product transition: customers who have never known the old world arriving directly in the new one.

The scale dimension compounds this. Mega-projects of this class manage asset portfolios measured in the hundreds of thousands of asset records spanning buildings, infrastructure, utilities, and transportation, often greenfield, often with aggressive commissioning timelines. Delivering asset management for a program like that requires data models, integration standards, and mobile field execution designed in from day one rather than retrofitted. Teams that do it well are creating implementation playbooks that simply did not exist in the mature-market world, because mature markets rarely get greenfield districts and greenfield utilities at this scale anymore.

There is also a talent flywheel forming. Every major MAS deployment in the Gulf creates jobs for Maximo functional consultants, MAS developers, and integration specialists, and the region has been importing and developing exactly that talent. As those practitioners accumulate experience on MAS 9.x specifically, rather than on legacy versions, the regional skill base becomes weighted toward the platform's future rather than its past. Expect Middle East-based consultancies and partner practices to become exporters of MAS expertise rather than importers, which is a reversal of the historical direction of enterprise software expertise in the region.

None of this makes the region friction-free. Large government-adjacent programs carry their own execution risks, localization requirements, and procurement complexities. But the structural driver, national-scale, greenfield, modern-platform-first adoption, is real and multi-year.

What This Means for the Global Maximo Ecosystem

For the global Maximo community, the Middle East momentum is worth tracking for three concrete reasons. The first is product validation. MAS 9.2 arrived in June 2026 carrying the most ambitious AI capabilities the product has shipped, including agentic workflows and condition-based insight. National-scale deployments like KAFD and Marafiq put those capabilities under load in environments with high consequence and high visibility. How those deployments fare with real users at real scale will tell the rest of the community more about MAS's readiness than any launch presentation. Watch for MAS-specific capabilities surfacing in Gulf customer stories over the next year.

The second is the partner and job market. The concentration of mega-projects creates sustained demand for Maximo and MAS skills in Saudi Arabia and the wider Gulf, and compensation in the region has historically reflected that. Practitioners with deep MAS experience, especially those who can bridge asset management with IoT, AI configuration, or smart-city domains, will find the region hard to ignore. Partners should likewise note that the winning implementation models in the Gulf, platform-first, custom apps on MAS, integration-heavy, are likely previews of what global customers will demand later. The region is running ahead of the curve, and lessons learned there will travel.

The third is the narrative shift. For years the Maximo community conversation has been dominated by migration anxiety, the 7.6 end-of-support countdown and the transition to MAS. That conversation matters, and the September 30, 2026 deadline for 7.6 extended support is genuinely urgent for laggards. But it is not the whole story, and the Gulf announcements are a reminder that the more interesting story is what MAS becomes once it is the default choice of a new generation of asset-heavy enterprises. A platform being adopted at KAFD and Marafiq scale, with custom applications being built and registered on top of it, is a platform with a growth story rather than merely a migration story. Community energy follows growth stories.

The practical watch items from here: track whether KAFD's Transition Management App pattern, customer-built domain apps on MAS, gets repeated by other operators, because repetition would confirm it as a template rather than a novelty. Watch for additional Vision 2030 mega-projects naming MAS publicly, which would confirm the pipeline behind the LEAP announcements. And watch how quickly the regional talent market professionalizes, through local user groups, training programs, and partner certifications, because talent depth is the truest leading indicator of sustainable regional adoption.

Practical Implications

If you work for an asset-heavy organization outside the Gulf, the Middle East momentum offers a preview you can learn from without paying mega-project prices. Start by studying how district-scale and industrial-city deployments frame the asset management problem: not as a maintenance system of record but as the operational backbone for an entire estate including customer-facing service delivery. Ask whether your own MAS roadmap, or your hesitation to start one, reflects that breadth or the narrower maintenance-back-office view.

If you are a practitioner, treat the region as a skills accelerant. Domain experience in smart-city asset management, transition management, and service-delivery modernization on MAS is scarce now and will be cited in job requirements for years. If your organization has Gulf engagements, volunteer for them. If not, follow the public announcements and the community write-ups from events like LEAP, because the implementation patterns surfacing there will reach mature markets within a couple of years.

If you are a partner or consultancy, the strategic read is that Middle East MAS work is where the newest playbooks are being written, and experience there is becoming a differentiator in global bids. Finally, if you are an IBM customer weighing MAS timing, note that greenfield adopters at national scale are effectively de-risking the platform for everyone else. Their scale and visibility mean the platform's rough edges get found and fixed in the most demanding environments first. Waiting has a cost in the 7.6 countdown, but it now also has a compensating benefit: by the time you migrate, the platform has been stress-tested at a scale larger than most readers of this article will ever need.

Bottom Line

Two Maximo announcements in one LEAP week would have been unremarkable five years ago, when regional wins were a steady backdrop to a North American and European center of gravity. What makes the KAFD and Marafiq stories matter in 2026 is their position in a structural shift. Vision 2030 is producing greenfield, national-scale asset management programs that choose modern platforms by default, and Maximo Application Suite is visibly winning a share of those choices. KAFD demonstrates MAS carrying urban-district asset management and hosting customer-built intellectual property on its application framework. Marafiq demonstrates MAS extending from classic utility maintenance into enterprise service delivery modernization. Together they mark the Middle East as a region where the MAS future is being built first, at a scale and pace mature markets no longer generate. For practitioners, partners, and customers watching the platform's trajectory, the Gulf has moved from the periphery of the Maximo world to one of its most instructive live laboratories. Keep an eye on Riyadh. The next chapter of asset management is being drafted there in public.

Read more