CMMS — Computerized Maintenance Management System

A computerized maintenance management system (CMMS) is the system of record for everything your maintenance team owns, touches and fixes. It holds your asset register, raises and routes work orders, schedules preventive maintenance, tracks spare parts, and — if it is built properly — turns the resulting data into reliability metrics that tell you whether your equipment is actually getting better or worse over time.

Most CMMS pages you will find when searching for CMMS software in Saudi Arabia stop at the first three capabilities. They describe work orders, preventive maintenance and a mobile app, then move straight to a contact form. What they almost never show you is the part that separates a maintenance log-book from a reliability program: a structured failure taxonomy, and live MTBF, MTTR, availability and PM-compliance figures computed from your own work-order history.

Skyline CMMS is different in a way you can verify on this page rather than take on faith. It ships with a real ISO 14224 failure-code catalog — a problem / cause / remedy taxonomy seeded into the product as system defaults for every tenant — and it computes the four core reliability KPIs in-product using formulas we publish below. It is built by a Saudi engineering firm, it is genuinely Arabic-native (not a translated global product), and it runs in the cloud or fully on-premise for organisations that need data residency. This page is the canonical reference for what the platform does and how its reliability engine works.

If you are a maintenance manager comparing options for a hospital, a factory, a facilities portfolio or an oil & gas site, the questions below are the ones that should decide the purchase — and they are the questions almost no competitor page answers honestly.

Every maintenance action in Skyline flows through a defined work-order lifecycle with six statuses: open → assigned → in_progress → on_hold → completed → cancelled. The status model is what makes the KPI engine possible: MTTR can only be computed because the platform records started_at and completed_at as the order moves through these states.

Work orders are classified by ISO 14224-aligned maintenance type — corrective, preventive, calibration, installation, acceptance, inspection, routine and condition-based — and the type drives the analytics. MTBF and MTTR, for example, are computed from corrective orders only, because mixing planned preventive work into a failure metric would corrupt it. This is a distinction most consumer-grade CMMS tools simply do not make.

After a corrective work order reaches completed, Skyline offers a digital sign-off step that records who closed the order, with optional digital-signature capture. In the Skyline mobile app, closure also captures the ISO 14224 problem / cause / remedy triplet against the seeded failure-code catalog; the web closure flow captures structured root-cause and failure-code fields. Either way, your reliability data is collected at the point of work, by the person who did the work, rather than reconstructed later by an analyst working from memory.

Work intake is just as flexible as work execution. Requests can arrive by email-to-work-order, by WhatsApp, by QR / barcode / RFID scan at the asset, or through the public REST API and HMAC-secured webhooks, so a CMMS-driven request workflow can be embedded in whatever channel your staff and contractors already use.

Preventive maintenance is where a CMMS earns its keep, and Skyline supports the full spectrum used by world-class maintenance programs.

• Calendar-based preventive maintenance generates work orders on a schedule (daily, weekly, monthly, quarterly, annually) and feeds the PM-compliance KPI directly, so you always know what share of due maintenance was actually completed on time.
• Meter-based PM triggers maintenance against usage rather than the calendar — runtime hours, cycles, kilometres, kWh and similar — using a configurable trigger threshold (pm_trigger_at). A pump that runs 24/7 and one that runs intermittently no longer share the same arbitrary monthly schedule; each is serviced when it has actually accumulated the duty that warrants it.
• Inspection routes and operator rounds let you build structured walk-downs — lubrication routes, safety checks, meter-reading rounds — that technicians complete on a defined frequency, capturing readings and condition observations as they go.

Because Skyline records every preventive completion against its schedule, the platform can report PM compliance honestly: it counts schedules that were due in the period and the share that received a completed work order, rather than reporting a flattering "PM tasks created" number that ignores whether the work was ever done.

"AI-powered predictive maintenance" is the most over-claimed phrase in the CMMS market. Skyline takes a transparent, auditable approach instead: a documented health-scoring model that weights four signals you can inspect and reason about, rather than a black box.

For each asset, the predictive engine computes a health score from 0 to 100 using this weighting:

• MTBF trend — 30%. The asset’s recent (last 90 days) mean time between failures compared with its historical baseline. A shortening MTBF means something is degrading.
• Meter-reading slope — 25%. Linear regression on recent meter readings against the duty-cycle baseline; a runtime meter crossing 90% of its service interval pushes risk up sharply.
• Telemetry breach frequency — 25%. IoT alerts opened in the last 30 days, capped at 10 per asset so one chatty sensor cannot dominate the score.
• Age factor — 20%. Asset age relative to its expected useful life, where that life is configured.

The final score is health = 100 − round(100 × weighted risk), mapped to a risk level — low (≥80), medium (60–79), high (40–59), critical (<40) — with a next-failure estimate produced by linear extrapolation from the MTBF and current meter slope. Condition-based work orders and IoT telemetry (delivered via HMAC-secured webhooks with configurable thresholds) tie the model to live equipment data and can open alerts automatically when a threshold is breached.

Asset criticality is scored on a 1–25 scale, so the predictive output is always read in the context of how much a given asset matters to the operation — a high-risk score on a critical asset is triaged differently from the same score on a spare.

Healthcare is the vertical where a CMMS is not optional. The Saudi Food and Drug Authority (SFDA), the Saudi Central Board for Accreditation of Healthcare Institutions (CBAHI) and JCI all expect documented, scheduled and auditable maintenance of medical equipment — and accreditation surveyors ask to see the evidence.

Skyline CMMS addresses this directly. It carries a dedicated compliance-records capability and full audit logging, so each piece of biomedical equipment can hold its planned preventive maintenance (PPM) history, its calibration record and its compliance status, with an immutable trail of who did what and when. Calibration is handled as a first-class maintenance type, suitable for ISO 17025-style traceability, and contracts (warranty, AMC, service agreement, calibration, rental) carry SLA response-time and resolution-time targets so a defibrillator or ventilator fault is bound to a guaranteed response window rather than a best-effort queue.

The practical effect for a biomedical engineering department: when a CBAHI surveyor asks for the PPM and calibration history of a specific infusion pump, it is one search — schedule, completed work orders, sign-offs, failure codes and calibration records — rather than a binder hunt. The compliance template-and-record engine is configurable, so accreditation-specific SFDA, CBAHI and JCI checklists can be modelled without custom development; the platform does not ship pre-built SFDA/CBAHI/JCI templates, but supports their requirements through this configurable engine.

For multi-hospital groups, Skyline runs multi-site, so a head-office biomedical team can oversee equipment across several facilities while each site manages its own day-to-day work.

On a production line, the metric that matters is uptime, and Skyline’s data model is built to measure it. The downtime_start / downtime_end timestamps and the production_impact flag on each work order let you separate the failures that actually stopped the line from the ones that did not, and feed an honest availability figure rather than an optimistic one.

Meter-based PM is particularly powerful in manufacturing: machines that are serviced by runtime hours or cycle counts — not by the calendar — stay reliable without being over-maintained. Inspection routes turn operator rounds into structured data, so the first signs of a developing bearing or seal failure are captured before they become an unplanned stop. And because MTBF is computed per asset from corrective history, you can rank your machines by reliability and target the worst offenders.

Pair this with the ISO 14224 failure-code triplet and you get true failure-mode analysis on the shop floor: which machines, which failure modes, which causes, and what the remedy was — the foundation of any continuous-improvement or reliability-centred-maintenance program. Skyline also covers spare-parts and MRO inventory with automatic reorder points, so a planned repair is not derailed by a missing part.

Facilities (CAFM). For property and facilities managers, Skyline runs as a multi-site computer-aided facility management platform: a single asset register across buildings, contracts and SLAs with explicit response-time and resolution-time hours, compliance schedules for life-safety systems, and a floor-plan view where assets are pinned to their physical location. Maintenance requests can arrive by WhatsApp, email or QR scan and route automatically to the right craft.

Oil & gas and high-hazard sites. This is where ISO 14224 originated, and where Skyline’s safety workflow earns its place. The platform includes a full Permit-to-Work / Lockout-Tagout (LOTO) module: permit types for hot work, confined space, electrical, working at height, chemical work, general LOTO, excavation and radiation; issued permits that record hazards, controls, required PPE, isolation points and gas-test results; and a multi-party sign-off chain so no high-risk job proceeds without the right authorisations. Combined with asset criticality scoring, the ISO 14224 failure catalog and the reliability KPIs, Skyline supports the Aramco-grade reliability and safety discipline that operators in the Eastern Province expect — without forcing them onto a foreign, cloud-only platform.

A maintenance system that ignores the financial life of an asset only tells half the story. Skyline’s asset-management foundation tracks the full lifecycle — acquisition, in-service, maintenance history and disposal — and supports IAS 16-style depreciation with multiple methods including straight-line, declining-balance and double-declining, maintaining accumulated depreciation and book value per asset.

This matters because reliability and finance decisions are the same decision. When the predictive engine flags a critical asset as high-risk and the MTBF trend is falling, the question "repair, overhaul or replace?" is best answered with the book value and remaining useful life in the same system. Assets are tagged with QR / barcode / RFID so a technician in the field, or an auditor at year-end, scans the same record the finance team sees.

Cloud or on-premise. Skyline CMMS can be deployed as a managed cloud service or installed fully on-premise inside your own data centre. For Saudi government entities, hospitals and operators with data-residency requirements, on-premise means your maintenance and asset data never leaves your infrastructure — a guarantee that cloud-only competitors cannot make.

Arabic-native and RTL. The platform is genuinely Arabic-first with full right-to-left support, built in the Kingdom rather than translated into it, so technicians and engineers work in the language they actually use on the floor.

Pricing posture. We do not publish per-seat pricing because no two maintenance programs scale the same way — but we will tell you plainly that Skyline is not sold on per-user fees that punish you for adding technicians. Pricing is scoped to your asset count, sites and deployment model, and we quote it transparently. If a competitor will not put a number anywhere near a contract, that is information too.

To go deeper on the financial and facilities sides of the platform, see CMMS asset management and CMMS facilities management. For city-specific deployments, see CMMS in Riyadh, Jeddah and Dammam, or explore SKYLINE Care support plans.

Run the test against everything else on the page-one results. The other CMMS pages will tell you they have work orders, preventive maintenance and a mobile app. None of them shows you a real ISO 14224 failure-code catalog you can read on the page. None publishes the exact MTBF, MTTR, availability and PM-compliance formulas the product computes, let alone a worked example. None maps the platform to SFDA, CBAHI and JCI obligations with a compliance-records and audit-log engine behind the claim. None offers a true on-premise option for data residency. And almost none will discuss price honestly.

Skyline CMMS does all of these, because it is a real product shipped by a Saudi engineering firm — not a brochure. If you are choosing a computerized maintenance management system for a hospital, a factory, a facilities portfolio or an oil & gas site in Saudi Arabia, this is the page that shows you the engine, not just the bodywork.

To start a scoped evaluation — asset count, sites and cloud-versus-on-premise — get in touch and we will map your reliability requirements to the platform before you commit to anything.

Problem codes — what the technician observed (14)

Cause codes — why it happened (14)

Remedy codes — what action was taken (11)

Because every closed work order in the Skyline mobile app can carry a problem / cause / remedy triplet (and the web flow captures structured root-cause and failure-code fields), the catalog is not decorative — it is the raw material for failure-mode analysis. When you can sort six months of corrective work by cause code and see that LUBE and FATIGUE account for 40% of your unplanned stops, you stop firefighting and start engineering the failures out.

The four formulas Skyline computes

• MTTR (Mean Time To Repair) = total repair time ÷ number of repairs, where repair time = completed_at − started_at in hours, across completed corrective work orders. Result expressed in hours.
• MTBF (Mean Time Between Failures) = total operational period (in days) ÷ number of corrective failures in that period, across completed corrective work orders. Result expressed in days.
• Equipment downtime % = (sum of work-order downtime hours ÷ total hours in the period) × 100. Availability is the complement: 100 − downtime %.
• PM (PPM) compliance % = (PPM schedules with a completed work order ÷ PPM schedules due in the period) × 100, evaluated per period (monthly by default).

A worked example for one chiller over 180 days

Suppose an air-cooled chiller is monitored from 1 January to 30 June — a 180-day window — and Skyline records the following on its work orders:

• 3 corrective failures (unplanned breakdowns), all completed.
• Repair durations of 4, 6 and 8 hours (each = completed_at − started_at).
• 30 total downtime hours summed across all work orders in the window.
• 6 preventive schedules due in the period, of which 5 were completed on time.

Skyline computes:

• MTTR = (4 + 6 + 8) ÷ 3 = 6.0 hours per repair.
• MTBF = 180 days ÷ 3 failures = 60 days between failures.
• Downtime % = (30 ÷ (180 × 24)) × 100 = (30 ÷ 4,320) × 100 = 0.69%, so Availability ≈ 99.31%.
• PM compliance = (5 ÷ 6) × 100 = 83.3%.

Three months later, if MTTR has fallen to 4 hours and MTBF has risen to 90 days, you have hard evidence that your reliability program is working — and if MTBF is falling, the predictive engine (below) will have flagged it before the next breakdown. To make these numbers trustworthy, Skyline work orders capture downtime_start and downtime_end timestamps and a production_impact flag, so downtime is measured from real clock events rather than estimated after the fact.

Free tools: compute these KPIs yourself with our open MTBF / MTTR / Availability calculator, or browse the full ISO 14224 failure-code reference.

In addition, the platform ships ready compliance templates for critical facility equipment in Saudi sites: fire extinguishers and fire-alarm systems (Civil Defense requirements), lifts (KSA Building Code), building-management systems (Saudi Building Code), eyewash stations, AEDs (MOH), generators (DIN 6280), HVAC (ASHRAE), and backflow preventers (NWC). SFDA, CBAHI and JCI checklists are not pre-seeded — they are configured through the same template engine to match each authority’s cycle and requirements.

The practical effect for a maintenance manager at a Saudi hospital: instead of spending a week before a CBAHI visit assembling paperwork, the compliance report exports in one click, with a full audit trail per device.