Oil & Gas CMMS & Reliability

On an oil & gas site in Saudi Arabia's Eastern Province, or anywhere in the Aramco supplier tier, the failure of a centrifugal pump or a gas compressor is not an operational nuisance. It is production loss measured in barrels per hour, a safety exposure, and an audit finding. That is why a reliability engineer in this sector needs something fundamentally different from a generic tool: not a maintenance management system that records that the pump failed, but one that tells you why it failed, how many times this year, how many hours of downtime it cost, and which failure pattern keeps recurring — so you fix the root cause, not the symptom.

That is the language of industrial reliability, and it has an international standard: ISO 14224, the global standard for the collection and exchange of reliability and maintenance data for equipment in the petroleum, petrochemical and natural-gas industries. The major operators in this sector — including the Aramco supplier chain — already speak it: an equipment hierarchy, and a unified taxonomy of failure modes (Problem), causes (Cause) and remedies (Remedy), so reliability data becomes comparable and analysable across sites.

Most pages you find when searching for CMMS for oil and gas in Saudi Arabia name reliability terms without actually running them inside the product: they do not publish an ISO 14224 taxonomy, they do not reveal how MTBF and MTTR are computed, and they do not show a Permit-to-Work lifecycle. Skyline CMMS is different in a way you can verify on this page. It is built in Saudi Arabia by a Saudi engineering firm, it is genuinely Arabic-native rather than a translated global product, and it ships real industrial-reliability capability that runs in the core of the product — not just on the sales page. This page explains, with original tools and tables, exactly how the platform serves Saudi oil & gas operations.

Whether you run a producing field, a pumping station, a gas plant, a refinery or a pipeline in the Eastern Province, Jubail or Yanbu, the sections below answer the questions that should decide the purchase: the full ISO 14224 catalog, the four reliability formulas, Permit-to-Work and LOTO, asset criticality, FMEA, and IoT condition monitoring.

The single thing that separates a real oil & gas CMMS from an ordinary maintenance log is a unified, classified failure taxonomy. Skyline ships, by default and for every tenant, a ready failure-code catalog of 39 codes classified to ISO 14224, available as system defaults to all tenants, with the ability for each site to add its own codes:

• 14 Problem codes — what the technician observed in the field: leak (LEAK), excessive vibration (VIBRATION), overheating (OVERHEAT), low flow / pressure (LOWFLOW), fails-to-start (NOSTART), corrosion observed (CORROSION), and more.
• 14 Cause codes — why it happened, in ISO 14224 logic: mechanical failure of a bearing/seal/coupling (MECHFAIL), material fatigue/fracture (FATIGUE), corrosion/erosion (CORROSION), insufficient or contaminated lubrication (LUBE), environmental factors such as heat and moisture (ENV), or cause unknown (UNKNOWN).
• 11 Remedy codes — what was done: repaired in place (REPAIRED), component replaced (REPLACED), calibrated/adjusted (ADJUSTED), escalated to vendor/contractor (VENDORCALL), deferred pending parts (DEFER).

An important precision note: the codes and categories ship in the product with English labels and ISO 14224 categories. Any Arabic rendering of these codes is our own explanatory translation to help Arabic-speaking teams — it is not Arabic text shipped inside the product. We present the catalog applied as an "equipment class → failure mode" reference in the next section, the way a reliability engineer actually uses it.

How the data is collected matters just as much. The ISO 14224 problem / cause / remedy triplet tied to this catalog is captured through the Skyline mobile app when the work order is closed in the field, while the web closure flow captures structured root-cause and failure-code fields. Either way, reliability data is collected at the point of work by the person who did it, rather than reconstructed later from memory.

Most importantly, this triplet is not dead documentation — it is fuel for reliability analysis. Once hundreds of closed work orders accumulate with these codes, you can see clearly that 40% of your pump stoppages are caused by LUBE (insufficient lubrication) rather than bearing wear, so you fix the lubrication program instead of buying new bearings. That is the difference between a CMMS that records the failure and one that helps you prevent it.

Most competitors name MTBF and MTTR without revealing how they are computed. In Skyline these KPIs run on explicit formulas in the core of the product, which we publish here with a worked numeric example for a single feed pump — exactly the metrics a reliability engineer and a safety auditor both ask for.

1) MTTR — Mean Time To Repair (hours)

The in-product formula: MTTR = total repair hours ÷ number of repairs, where each work order's repair time = (completed_at − started_at), computed from completed corrective work orders only — because mixing planned preventive work into a failure metric would corrupt it.

Example: a feed pump failed 3 times this month with repair times of 4, 6 and 2 hours. So MTTR = (4 + 6 + 2) ÷ 3 = 4 hours. The lower this number, the better your maintainability and response.

2) MTBF — Mean Time Between Failures (days)

The in-product formula: MTBF = total operating period ÷ number of failures, where the period is measured in days and failures are counted from completed corrective work orders in the period.

Example, same pump: over 90 days it failed 3 times. So MTBF = 90 ÷ 3 = 30 days. A higher number means a more reliable asset, and trending it over time exposes degradation before a major failure — which is what later feeds the predictive-maintenance model.

3) Downtime / availability — percentage

The in-product formula: downtime% = (downtime hours ÷ total period hours) × 100, from which availability = 100 − downtime%. Downtime hours are aggregated from work orders in the period (default last 30 days).

Example: over 30 days (720 hours), the pump was down 18 hours. Downtime% = (18 ÷ 720) × 100 = 2.5%, so availability = 97.5%.

4) PM-compliance — percentage

The in-product formula: PM-compliance% = (completed PPM schedules ÷ total due in the period) × 100. A schedule counts as completed if its linked work order was completed within the period. Example: 20 schedules due, 18 completed, so compliance = 90% — the first figure auditors ask for.

These metrics are generated automatically from data you already enter. To keep them accurate, each work order captures downtime_start, downtime_end and a production_impact flag, so downtime is measured from real time-stamped events rather than estimates — and failures that actually stopped production are separated from those that did not.

Free tools: compute these KPIs for your own assets with our open MTBF / MTTR / Availability calculator, and explore the full ISO 14224 failure-code reference.

In oil & gas environments it is not enough to fix the equipment — you must fix it safely and prove it to the asset owner and the auditor. This is precisely what lifts Skyline from a "maintenance system" to a "maintenance system ready for Aramco-supplier-tier sites," where safety documentation is a contractual requirement, not an option.

The Permit-to-Work module provides a full permit lifecycle — draft → issued → active → closed/cancelled — with eight operational permit types: lock-out/tag-out (LOTO), hot work, confined space, electrical, working at height, chemical, excavation and general. For radiographic inspection work (pipeline radiography and NDT), the platform also supports a radiation permit category at the permit-type classification level.

• Hazards and controls documentation: every issued permit records the identified hazards, required controls, checklist and required personal protective equipment (PPE).
• LOTO isolation points: energy-isolation points (electrical, pressure, hydraulic) are recorded to ensure the equipment is genuinely isolated before work begins.
• Gas-test results: gas-test readings before entry to confined spaces are documented — a baseline requirement in gas plants and refineries.
• Multi-party sign-off chain: a permit is not approved by a single signature, but through a documented chain (issuer, performer, approver), so hazardous work never starts without formal approval.
• Permit linked to the work order: the work order carries a "permit-required" flag and a reference to the permit and its status, so high-risk work cannot be closed without a valid permit.

Beyond permits, the platform supports multi-craft assignment on a single work order (mechanical, electrical, instrumentation, safety and others) with estimated and actual hours per craft and a lead flag — essential for major turnaround work that requires several crafts to coordinate on one piece of equipment. It also captures ISO 17025 calibration records (certificate number, issuer, calibration and next-due dates, result, and before/after measurements) for critical instrumentation.

Asset integrity in oil & gas starts with one question: which of my assets is the most dangerous if it fails, and how do I direct the reliability budget there first? Skyline answers this with an integrated toolset:

Asset criticality

Each asset's criticality is assessed through a risk matrix: business impact × failure likelihood, each on four levels (low / medium / high / critical), producing a criticality score by which assets are ranked. Assets are also classified A/B/C following ISO 55000 logic. The result: the reliability budget concentrates on critical assets (main gas compressors, feed pumps) rather than being spread evenly across everything.

FMEA and the Risk Priority Number (RPN)

FMEA is a core tool in oil & gas reliability programs, and in Skyline it is a first-class table per asset or asset class: failure mode, effect on the system, cause, then a rating of Severity (1-10) × Occurrence (1-10) × Detection (1-10) producing the Risk Priority Number RPN = Severity × Occurrence × Detection, with a recommended action, owner, due date and status (open / in-progress / closed). Your FMEA workshop becomes a live action plan inside the system instead of a forgotten spreadsheet.

Predictive maintenance with a transparent model, not a black box

Instead of vague "artificial intelligence" claims, Skyline uses a transparent, explainable 0-100 asset-health scoring model with clear weights: MTBF trend at 30% (last 90 days vs a 12-month baseline), meter-reading slope at 25%, IoT threshold-breach frequency at 25%, and an age factor at 20%. The score falls into risk bands (low ≥80, medium 60-79, high 40-59, critical below 40), with a next-failure-date estimate by linear extrapolation. You know why an asset is high-risk, not just a number from a black box.

IoT condition monitoring

The platform ingests real-time sensor data over a secure connection (HMAC webhook): vibration, temperature, pressure, current, rpm, humidity, power and runtime hours. Per-asset alert thresholds (min/max) are configured with severity levels and an action priority, so the system automatically opens a work order or raises an alert when a limit is breached — such as a compressor bearing's vibration rising above its threshold — before the signal becomes a full failure and stops production.

And when a repair-or-replace decision arrives for a critical asset, reliability meets finance: the platform computes depreciation under IAS 16 using multiple methods (straight-line, declining-balance and others) while tracking book value, so the decision is backed by reliability data (MTBF and accumulated repair cost) and book value together.

Data residency is fundamental for energy operations in Saudi Arabia. That is why Skyline gives you an explicit choice that most cloud-only competitors do not: on-premise deployment entirely on your own servers inside the Kingdom for data sovereignty and regulatory compliance, or cloud deployment if you prefer it — without giving up any feature in either option.

The platform runs in around 30 languages in the maintenance module with full RTL support, serving the multinational maintenance teams common on Saudi oil & gas sites (engineers, technicians, contractors) without a language barrier. The Skyline team — a Saudi engineering firm — handles implementation from building the asset register and classifying criticality, through scheduling preventive maintenance, to your first reliability report.

On pricing, we take the transparency position the market avoids: no per-user fees, and clear local pricing scoped to the size of your operation.

The oil & gas maintenance system is part of the wider Skyline platform. For the core capabilities, see the comprehensive guide CMMS computerized maintenance management. For the full financial asset lifecycle and depreciation, see CMMS asset management. For facilities, buildings and multi-site management across your industrial complex, see CMMS facilities management. For deployment by location in the Eastern Province and industrial cities, see CMMS in Dammam, Jubail and Yanbu. For support and maintenance packages, see SKYLINE Care — and the complete CMMS guide remains the place to request a demo tailored to the oil & gas sector.

The codes and English categories are taken from the product catalog as shipped; the Arabic glosses we use are our explanatory translation. Use this as a starting point for building your own reliability register.

How does this table turn into a reliability return? Suppose a pumping station with 12 centrifugal pumps. After six months of closing work orders with these codes, a Pareto analysis shows that VIBRATION caused by MECHFAIL accounts for 38% of pump stoppages, and LEAK caused by WEAR in mechanical seals accounts for 22%. The resulting decision is not a guess: review the shaft-alignment program and bearing specification first, because those two modes alone represent 60% of your lost availability. That is what an ISO 14224 taxonomy does when it runs inside the product instead of sitting on paper.