Manufacturing execution and production planning systems evaluated for Saudi industrial operations.
Manufacturing systems and Industry 4.0 platforms are the part of the technology estate where the demonstration and the plant floor are furthest apart. Every platform in this category shows beautifully on a screen full of live gauges. Whether it survives a shift change, a maintenance window and an operator wearing gloves is a different question, and it is the only one that matters.
Most plants that ask us about this category are not missing software. They have an ERP with a production module somebody configured during the original implementation, a SCADA system the controls engineer owns, a maintenance spreadsheet, a quality file, and a production report typed up at the end of each shift from a paper log. The gap is not a missing system - it is that none of those systems agrees about what was made, when, from what, and how long the line was actually down.
The most expensive mistake here is buying a layer you already own. An ERP with a shop-floor module, an MES with a maintenance module and a CMMS with a work-order engine will each demonstrate the same capability, and a plant that buys two of them without first deciding which one owns which decision ends up running two systems that disagree about the same work order, plus a person whose job is reconciling them. Drawing those boundaries before a shortlist exists is the highest-return hour in this process and it costs nothing - which is why this page spends its first section on the anatomy of the category rather than on names.
Our interest, stated before the argument rather than after it: Trustangle is an independent advisory firm. We deliver selection and implementation work, which is a real 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 the module in the ERP you already paid for would do the job if somebody configured it.
This is a category, not a product, and the layers inside it are routinely sold to the same buyer by vendors who each describe their own layer as the centre of the plant. In roughly the order material moves through them:
Planning - MRP, MPS and advanced scheduling. What to make, in what quantity, from what, and in what sequence. Material requirements, master production scheduling, capacity checks and finite scheduling against real constraints. This layer decides how much capital is standing still as raw material and work-in-progress. It is the layer most often skipped, and its symptoms appear elsewhere: a plant with excellent execution and no planning executes the wrong quantities very efficiently.
Execution - MES and MOM. What is actually happening on the line right now: work-order dispatch to stations, operator instructions, material consumption and backflush, production counts, downtime capture and reason codes, changeover, and the genealogy record linking output to the inputs and the equipment that made it. This is the precise boundary with your ERP's production module and the single most common confusion we are called in to settle - an ERP production module keeps the accounting position; an MES keeps the physical one. A plant whose problem is that nobody knows why line 3 stopped does not have an ERP problem.
Quality - QMS and in-process control. Inspection plans, in-process checks, non-conformance and corrective action, certificates of analysis, supplier quality, and the audit trail behind each of them. In regulated output this layer is not optional and cannot be retrofitted credibly.
Maintenance and assets - CMMS and EAM. Asset register, preventive and condition-based maintenance, work orders, spares, and the reliability record. This layer overlaps asset maintenance and field operations directly, and the boundary question is whether maintenance work orders are driven by production events or managed independently.
Automation and data acquisition - SCADA, historian, IIoT. The machine layer and the time-series record beneath everything above. Where an Industry 4.0 programme actually begins, because a plant that cannot get reliable counts and downtime off its machines cannot do anything else on this list honestly.
Traceability and product data - PLM, serialisation, batch genealogy. The specification of what is being made, and the ability to trace a finished unit back to its batch, its machine, its operator and its supplier - forward for recall and backward for root cause.
Analytics and the plant control tower. OEE, yield, scrap, energy and cost per unit across lines and sites, with an exception queue that lets a small team run a large plant by handling only what has gone wrong.
Two things make the overlap worse than it looks on paper. The serious vendors in each layer have extended into the neighbouring ones, so an MES will show you maintenance and a CMMS will show you production counts - each competently enough to demonstrate, rarely deeply enough to run an operation whose centre of gravity sits there. And ERP suites include a version of nearly all of it, which is frequently sufficient and occasionally nowhere near. Establishing which is true for your plant is worth more than any feature comparison, and it is a question about your process type, your volumes and your failure modes rather than about the software.
Why this matters in this market now. Saudi industrial policy has put sustained weight behind manufacturing capability and digital adoption: the National Industrial Development and Logistics Program is one of the Vision 2030 realisation programmes [source: vision2030.gov.sa], and the Ministry of Industry and Mineral Resources runs national programmes aimed specifically at raising factories' digital maturity [source: mim.gov.sa]. The practical consequence for a buyer is that "Industry 4.0 readiness" has stopped being a slogan and started being something a plant is assessed on - which makes it worth knowing what is actually being assessed before buying software against it.
When you do not need this yet. A single line with stable output, a team that can see the whole floor, and volumes comfortably handled by the people already doing it does not need a platform. And if the real problem is master data - bills of material that do not match what is actually built, routings with invented cycle times, an asset register that was never finished, units of measure that differ between systems - then a platform will industrialise the mess rather than resolve it. An MES fed a wrong BOM will consume the wrong material faster than your current process does. That is not a reason to do nothing; it is a reason to spend a few weeks on master data first, at which point the software decision becomes both cheaper and much easier.
Every evaluation starts from your plant rather than from a feature grid, for a practical reason: at this scale the serious platforms all do the headline things, so a headline comparison always ends in a tie. What separates them is behaviour at the edges your operation lives on - your process type, your changeover profile, your automation estate, and how much routine change your own team can sustain after we leave.
What you make and by which process. How many lines, how many sites, and whether they are meant to converge. What is on the machines today and how old the oldest controller is. What your ERP already covers and what its contract says. Who would own configuration after go-live. What your largest recurring loss actually is - downtime, scrap, changeover or labour - because the answer decides which layer you are buying, and plants are frequently wrong about it until the data is gathered.
The platforms we work with 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: Fiix and Repzo CMMS. Beedigit and FactoryOnline are also in the catalogue.
Fiix and Repzo CMMS sit primarily in the maintenance layer and are covered in depth on asset maintenance and field operations, which is their home category. They appear here because maintenance is one of the seven layers above, not because this is where a maintenance decision should be made.
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 |
|---|---|---|
| Planning (MRP/APS) | What to make and in what order | Schedules are spreadsheets broken by lunchtime |
| Execution (MES/MOM) | What actually happened on the line | Nobody can say why the line stopped |
| Quality (QMS) | Whether it was made right | Quality lives outside the system |
| Maintenance (CMMS/EAM) | Whether the asset will run | Breakdowns drive the schedule |
| Automation (SCADA/historian/IIoT) | What the machines say | Counts are typed up by hand |
| Traceability (PLM/genealogy) | What went into what | A recall would be a project |
| Analytics / control tower | Where the loss is | Each site reports differently |
We publish the drivers, not a price, because the numbers that decide the bill are yours: the number of lines, stations and sites, and how the vendor meters them; connectivity work, which is the line buyers underestimate most - every machine that cannot be read needs an interface, a gateway or a retrofit, and that is engineering, not licensing; master data preparation for BOMs, routings, cycle times and the asset register; integration to the ERP in both directions; OT-network and segmentation work if the estate is flat today; training across shifts, in the language the operators use; and the run cost, meaning who owns configuration after go-live.
The three-year total is the number that matters, and on this category the largest line is very often not software at all - it is the work of making the plant legible to it.
Structural only. Institutions and obligations by function; confirm current detail with each authority.
Industrial policy and digital maturity. The Ministry of Industry and Mineral Resources is the sector's authority and runs national programmes aimed at raising the digital maturity of factories in the Kingdom [source: mim.gov.sa]. The National Industrial Development and Logistics Program sits above that as a Vision 2030 realisation programme [source: vision2030.gov.sa]. The practical consequence for a system selection is that digital-maturity assessment is part of the environment a Saudi plant operates in, rather than an internal exercise.
Industry 4.0 readiness assessment (SIRI). The Smart Industry Readiness Index is a published, structured framework for assessing a plant's Industry 4.0 maturity; it originated with Singapore's Economic Development Board and is stewarded by the International Centre for Industrial Transformation [source: incit.org]. It is worth understanding on its own terms before buying against it, because an assessment measures process, technology and organisation together - software alone moves only one of the three. Confirm with the Ministry of Industry and Mineral Resources which assessment framework applies to your facility before committing to one. [source: mim.gov.sa]
Industrial cities and utilities. Plants located in the Saudi Authority for Industrial Cities and Technology Zones' estates operate within its framework, which can affect connectivity, utilities and permitted works - relevant when a project involves physical network or plant-floor infrastructure. [source: modon.gov.sa]
Product conformity and standards. The Saudi Standards, Metrology and Quality Organization sets standards, and the SABER platform administers conformity and product-certification processes for regulated products. Where your output is in scope, conformity status is governed master data that belongs on the item master in the system running your production - not in a spreadsheet. [source: saso.gov.sa; saber.sa]
Regulated output. Food, beverage, pharmaceutical, medical-device and cosmetic manufacturing falls under the Saudi Food and Drug Authority, whose requirements reach directly into batch records, traceability and release - that is a quality and traceability-layer requirement, not a nice-to-have. [source: sfda.gov.sa]
Local content. Where you supply government or major national buyers, local content is a measured commercial factor administered by the Local Content and Government Procurement Authority, and the evidence for it is produced from your own production and procurement records. [source: lcgpa.gov.sa]
Operational technology cybersecurity. The National Cybersecurity Authority publishes controls that reach plant-floor and operational technology environments for in-scope entities. Segmentation, remote access and vendor connectivity belong in the selection criteria rather than in a later audit finding. [source: nca.gov.sa]
E-invoicing. Output is still sold. The Zakat, Tax and Customs Authority's e-invoicing regime and Fatoora platform govern the commercial documents produced at the end of the process. [source: zatca.gov.sa]
Arabic at the station. Operator-facing instructions, alarms and forms in Arabic, with right-to-left support. This is an adoption requirement, not a preference, and it is the first thing to test in a demonstration rather than the last.
Discovery on the floor, not in a meeting room: process type, line layout, automation estate, the age of the oldest controller, and what your real recurring loss is. A written shortlist with the reasoning visible, including the case for using what you already own. Scripted demonstrations against your product, your changeover and your worst shift. A commercial review of the whole three-year picture, connectivity included. Then implementation: master data first, connectivity second, one line as a pilot through a real production week, and only then a rollout. Training is delivered across shifts and in the operators' language, and aimed at whoever will own configuration after we leave.
We do not publish a number. What sets it: how many lines and sites, how much of the plant can already be read electronically, how clean the BOMs and routings are, whether the ERP boundary is settled before work starts, and whether operational-technology network changes are in scope. Connectivity and master data are the two stages that move dates. We give a dated plan after discovery, not before.
Licence plus connectivity engineering plus master data preparation plus ERP integration plus network and security work plus training across shifts plus the internal ownership cost 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 not even the largest one.
Not as a property of the product - as a property of how it is deployed and connected. The obligations that bite are sector requirements from the Ministry of Industry and Mineral Resources [mim.gov.sa], product conformity through SASO and SABER where your output is regulated [saso.gov.sa; saber.sa], SFDA requirements for regulated output [sfda.gov.sa], NCA controls where your operational technology is in scope [nca.gov.sa], local content evidence where you supply government buyers [lcgpa.gov.sa], and ZATCA e-invoicing on the commercial side [zatca.gov.sa]. Where the platform is hosted, and whether that is acceptable for a plant-floor system, 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 without that is not independent advice, whoever wrote it.
In this category, usually - and that is normally the right shape. The ERP stays the system of record, the historian stays where it is, and the execution layer is added between them. The question to settle first is which system owns the work order. Two systems that both think they do is the standard failure here, and it is a design decision, not a product feature.
This section carries no number and no claim about our size - we would rather say that plainly than publish a figure we cannot evidence. What we would tell you to demand of any adviser in this category, including us: how many plants they have taken live, on what process types, how many machine interfaces they have personally commissioned, and the name of one manufacturer who will take your call. Ask in a meeting, where the answers 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 process type 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, because an unattributable number is not evidence - and in this category an OEE improvement with no plant attached to it is the least credible number in the 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.
Asset maintenance and field operations - the maintenance layer, and the right place to make a CMMS or EAM decision. Supply chain, logistics and fulfillment - what happens to output once it leaves the plant. Manufacturing sector advisory - read it if your question is what is my problem; this page exists for what are the systems. All solutions and platforms and independent software comparisons.
Bring a line layout, a list of what is on the machines, and one month of downtime records however they are kept. Book a decision session - or start with an impartial assessment - and we will tell you, plainly, whether this is a platform decision, a connectivity project, or a master data problem wearing a software costume. It is the third one more often than anybody expects.
