Asset management, CMMS and field service platforms for Saudi maintenance and operations teams.
Maintenance software is bought at one of two moments, and they produce very different projects. The first is after something expensive broke that should not have. The second is when someone asks a question - what do we own, where is it, what condition is it in, and what did it cost us last year - and discovers that answering it would take a month.
If you are at the first moment, the instinct is to buy the system that would have caught it. That instinct is usually right about the category and usually wrong about the sequence, because a CMMS is only as good as the asset register underneath it, and almost nobody has one that is finished. A maintenance system loaded with an incomplete register does not produce reliability; it produces very well-organised ignorance.
Our interest, stated before the argument: Trustangle is an independent advisory firm. We deliver selection and implementation work, which is a genuine commercial interest in your decision. Where we hold a partnership or accreditation with a vendor named here, it is published on our partners page rather than implied in the copy, and it does not decide our recommendation. We do not earn a margin on your licence - which is what makes it possible for us to tell you that your first project is a register, not a purchase.
A computerised maintenance management system is the system of record for physical assets and the work done on them. Around it sit four neighbouring layers that are routinely sold as the same thing, and the overlap is where buyers get hurt.
The asset register and hierarchy. What you own, where it sits, what it is part of, what it is made of, and what its criticality is. Everything else on this list is downstream of this, and it is the layer most often treated as a data-loading task rather than as the design decision it actually is.
Work management - the CMMS proper. Requests, work orders, planning and scheduling, preventive maintenance routines, permits, labour and parts recorded against the job, and the history that accumulates. This is what people mean when they say CMMS, and its value comes almost entirely from the history - which means it is worth nothing in month one and a great deal in year three.
Enterprise asset management - EAM. The CMMS plus the financial and lifecycle view: capital planning, depreciation and replacement decisions, contract and warranty management, and performance across sites. The distinction that matters when choosing is whether your question is "is it fixed" (CMMS) or "should we keep it" (EAM).
Field service management. The same work, done by people who are not on your site: scheduling and dispatch of mobile technicians, routing, the technician application, parts on the van, time capture, customer sign-off and invoicing. This is genuinely a different discipline from in-plant maintenance - it is optimised per visit, not per asset, and the cost of a second visit is the number the whole operation turns on.
Condition monitoring and reliability. Sensor data, condition-based triggers, failure analysis and reliability-centred maintenance. This is where a maintenance programme stops being calendar-driven, and it is the layer that most convincingly does not work without the three above it being sound first.
Two things make the overlap worse than it looks. Serious vendors in each layer have extended into the neighbouring ones, so a CMMS will show you field dispatch and a field-service platform will show you preventive maintenance, each competently enough to demonstrate. And ERP suites include an asset and maintenance module, which is frequently sufficient and occasionally nowhere near. Establishing which of those is true for your operation is worth more than any feature comparison, and it is a question about your asset base and your failure history rather than about the software.
When you do not need this yet. A small, stable asset base that one team can see and remember does not need a platform. And if the asset register does not exist, the first project is the register - walked, tagged, hierarchy agreed, criticality assigned - not the software. A CMMS loaded with a half-register will schedule confident maintenance on assets that are not there and none on the ones that are. That is not a reason to do nothing; it is a reason to sequence correctly, after which the software decision is both cheaper and much easier.
At this scale the serious platforms all do work orders and preventive routines, so a headline comparison always ends in a tie. What separates them is behaviour at the edges your operation lives on.
What do you own and is it written down. How many sites, and are they meant to converge. Is the work done by your own team, by contractors, or by you for customers - that answer alone decides half the shortlist. What does a failure cost you. What are your statutory and insurer inspection obligations. What does your ERP already cover, and what does its contract say. Who owns configuration after go-live.
The platforms we work with in this category - Fiix, Repzo CMMS, Repzo DSD and Workiom CMMS - are described on their own pages, in their vendors' own terms. Nothing is claimed for any of them here, and none is presented as the default answer.
This is the canonical home for maintenance decisions. Where a maintenance requirement sits inside a wider production programme, it is covered from manufacturing systems - but the CMMS or EAM choice itself is made here.
Compared here are the layers of the category, not the products against each other - a product comparison would be a vendor capability claim, and those are not made on this page.
| Layer | Answers | You are buying it when |
|---|---|---|
| Asset register | What we own and where | Nobody can produce the list |
| Work management (CMMS) | Is it fixed, and what did it take | History lives in memory and paper |
| Enterprise asset management (EAM) | Should we keep it or replace it | Capital decisions are made on instinct |
| Field service management | Who goes where, with what | Technicians are dispatched by phone |
| Condition monitoring | Will it fail, and when | Calendar maintenance is over- and under-servicing at once |
We publish the drivers, not a price. What decides the bill here: the number of technician or planner seats and how the vendor meters them; asset register creation, which is field labour - walking, tagging, capturing nameplate data - and is by a wide margin the line buyers underestimate most; data migration from whatever exists today; integration to ERP, stores and, if in scope, condition signals; mobile devices and connectivity for the people doing the work; training across shifts and in the technicians' language; and the run cost, meaning who owns routines and configuration after go-live.
The three-year total is the number that matters, and on this category the register work is routinely larger than the licence.
Structural only. Institutions and obligations by function; confirm current detail with each authority.
Industrial and facility safety. High-risk industrial facilities in the Kingdom operate under industrial-security requirements administered through the Ministry of Interior's High Commission for Industrial Security. Where your assets fall in scope, inspection, permit and evidence obligations are not optional features of a maintenance system - they are the reason to have one. Confirm applicability and current requirements with the competent authority.
Buildings and facilities. Facilities maintenance in the Kingdom sits against the Saudi Building Code framework and municipal requirements administered through the Ministry of Municipal and Rural Affairs and Housing, relevant to any maintenance programme covering premises rather than production equipment.
Industrial estates. Plants located within the Saudi Authority for Industrial Cities and Technology Zones' estates operate inside its framework, which can affect permitted works, contractor access and utilities coordination - all of which a work-order system has to reflect rather than fight.
Operational technology cybersecurity. Where condition monitoring connects a maintenance platform to plant-floor systems, the National Cybersecurity Authority's controls reach that connection for in-scope entities. Segmentation and vendor remote access belong in selection criteria, not in a later audit finding.
Field workforce. Dispatching technicians across the Kingdom brings labour obligations with it - working hours and overtime under the labour framework administered by the Ministry of Human Resources and Social Development and its Qiwa platform, and workforce identity and documentation requirements. A field platform that cannot express your actual shift and overtime rules will be overridden by hand within a month.
Addressing and routing. Field routing in this market rests on the national addressing scheme rather than on map pins alone. Our guide to national address registration covers what that means operationally.
Local content. Where you maintain assets for government or major national buyers, local content is a measured commercial factor administered by the Local Content and Government Procurement Authority, evidenced from your own records.
Invoicing. Where field work is billed to a customer, the Zakat, Tax and Customs Authority's e-invoicing regime applies to the resulting documents - which makes the field platform's invoicing path a compliance question, not just a convenience.
Arabic at the point of work. Technician-facing instructions, checklists and permits in Arabic, with right-to-left support, on a device used outdoors. This is an adoption requirement, not a preference, and it is the first thing to test in a demonstration rather than the last.
Discovery in the field and in the store, not in a meeting room: what you own, how it is currently recorded, what failed last year and what it cost. A written shortlist with the reasoning visible, including the case for the module in the ERP you already own. Scripted demonstrations run by an actual technician on an actual device. A commercial review of the full three-year picture, register work included. Then implementation sequenced honestly: register and hierarchy first, critical assets before the long tail, preventive routines built from real failure history rather than from vendor templates, one site as a pilot, and only then a rollout. Training is delivered to technicians in their language, because they are the control on whether any of this holds.
We do not publish a number. What sets it: how complete your asset register is today - the dominant factor by some distance - how many sites, how many integrations, whether condition monitoring is in scope, and whether the work is in-plant, field, or both. Register creation is field labour and it is the stage that moves dates. We give a dated plan after discovery, not before.
Licence plus register creation plus migration plus integration to ERP and stores plus devices and connectivity plus training across shifts plus the internal owner of routines afterwards. Section 5 lists the drivers. A quote that prices only the licence is not a three-year number, and in this category it is usually the smaller half.
Not as a property of the product - as a property of how it is deployed, connected and configured. The obligations that bite are industrial-security requirements where your facility is in scope, building and municipal requirements for premises, National Cybersecurity Authority controls where the platform touches operational technology, labour obligations for a field workforce, and the Zakat, Tax and Customs Authority's e-invoicing regime where field work is billed. Where the platform is hosted, and whether that is acceptable for a system connected to plant equipment, is a question to put to the vendor in writing and to check against current requirements - not one to take from a sales deck or from this page.
We publish the shortlist and the reasoning with every recommendation, including what we rejected and why. A recommendation that arrives without that is not independent advice, whoever wrote it.
Usually, and that is normally the right shape. The ERP stays the financial record, the stores system stays where it is, and the maintenance layer is added between them. The question to settle first is which system owns the asset master. Two systems that both think they do is the standard failure in this category, and it is a design decision, not a product feature.
The heading asks for numbers. This section has none, and we would rather say so plainly than publish a figure we cannot evidence. What we would tell you to demand of any adviser here, including us: how many maintenance implementations they have actually delivered, on what asset types, whether they have personally built an asset register in the field, and the name of one client who will take your call. Ask in a meeting, where it can be checked.
We do not name clients without their written agreement and we do not publish a logo wall assembled from projects nobody consented to display. References relevant to your asset base and your sector are offered during evaluation, by name.
Case material is shared under the same rule as section 10: relevant, named, and only with the client's agreement. We do not publish anonymous percentage improvements - an unattributable uptime figure is the least credible number in this industry.
Testimonials appear here only when a real client has written and approved one. There are none invented in the meantime.
Published and maintained on the partners page, which is the single source of truth. We do not restate them in body copy, where they go stale silently and where a claim is hardest to check.
Manufacturing systems - where maintenance sits inside a wider production programme. Supply chain, logistics and fulfillment - for spares, stores and the movement of parts. Systems integration - where the ERP and stores connections are designed. National address registration - the addressing layer under any field-routing decision. All solutions and platforms and independent software comparisons.
Bring whatever asset list exists, however incomplete, and last year's breakdown history however it is kept. Book a decision session - or start with an impartial assessment - and we will tell you, plainly, whether this is a platform decision, an integration project, or an asset register you need to build before either. It is the third one more often than anybody wants to hear.
