Hospital & Biomedical CMMS

In a hospital, maintenance is not a back-office line item — it is patient safety and regulatory survival. A ventilator that has drifted out of calibration, a medical-gas alarm panel that was not tested this month, a defibrillator (AED) with a flat battery — each can be the difference between life and death, and each is exactly what a surveyor from the Saudi Food and Drug Authority (SFDA), the Saudi Central Board for Accreditation of Healthcare Institutions (CBAHI) and JCI will ask to see evidence for during a visit.

Skyline's hospital CMMS is built for precisely this equation: that biomedical preventive maintenance is scheduled, documented and calibrated with a complete audit trail, so your accreditation file stops being a frantic pre-survey scramble and becomes a one-click report export. The platform is built in Saudi Arabia by a Saudi engineering firm, is genuinely Arabic-native rather than a translated product, and runs in the cloud or fully on-premise on the hospital's own servers inside the Kingdom for patient-data residency.

The real gap between a maintenance log-book in a spreadsheet and a proper hospital CMMS is the ability to answer the questions a surveyor actually asks: what share of biomedical equipment received its due preventive maintenance this quarter? When was this laboratory centrifuge last calibrated, and where is the certificate? Who closed the dialysis-machine repair, and at what time? These are reliability and compliance questions, and answering them needs structured data and formulas that run automatically — which is the heart of what Skyline provides. This page is the in-depth reference for healthcare; for the full platform picture, see the complete CMMS guide.

Let us be precise from the outset, because this market is full of overclaims: Skyline does not ship pre-built SFDA, CBAHI or JCI templates. What it ships is something more powerful and durable — a configurable compliance engine that lets your biomedical engineering team build the templates and records to match exactly the frequency and requirements of the relevant authority, so you are never trapped behind a rigid template list that may lag regulatory updates.

The engine rests on three integrated elements:

• Configurable compliance templates: for each equipment class you define a compliance rule (authority, frequency, reference standard), which then auto-generates the linked preventive-maintenance schedules and work orders. These templates are configured to match SFDA requirements for medical-device maintenance, CBAHI facility-management standards, or the JCI Facility Management and Safety chapter.
• Per-asset compliance records: every device carries its live compliance status, last-action date and next-due date, so you see the whole medical fleet at a glance rather than digging through files.
• A complete, tamper-evident audit trail: every maintenance action is logged with who performed it and when — the documented evidence a CBAHI or JCI surveyor expects for each critical device.

So you don't start from zero, the system ships with ready compliance templates for the critical facility equipment common to Saudi hospitals: fire extinguishers and fire-alarm systems (per Civil Defense), lifts (per the Saudi Building Code), building-management systems (BMS), eye-wash stations, AED defibrillators with a monthly battery and pad check (per the Ministry of Health), generators (per DIN 6280), HVAC (per ASHRAE 62.1) and backflow preventers (per the National Water Company). The SFDA / CBAHI / JCI templates for biomedical equipment are then configured through that same engine to match each device's frequency.

The table below maps the key regulatory expectations to the corresponding Skyline feature:

In a hospital, calibration is not just a maintenance task; it is a regulatory obligation of measurement traceability. That is why Skyline treats calibration as a first-class maintenance type with a dedicated record designed to suit ISO 17025-style traceability, capturing for each calibration:

• The certificate number and the issuing body (the name of the ISO 17025-accredited laboratory).
• The calibration date and the next-due date, so the system generates a reminder ahead of the deadline.
• The result: pass / fail / conditional.
• The measurements (before / after / tolerance) stored in a structured format, so you can see the drift before calibration and its magnitude after.
• A PDF certificate attachment alongside the record, so the document stays with the device rather than in a separate drawer.
• The calibrator, whether an in-house technician or an accredited external party.

The outcome for a biomedical engineer: when an SFDA surveyor asks for the calibration certificate of an ICU patient monitor, the certificate, the measurements and the next-due date are recalled from the device's own record in seconds — no rifling through paper files and no anxiety over a lost certificate.

Maintaining medical equipment requires a different specialism from general facilities work. Skyline therefore supports multi-craft assignment on a single work order, and the craft list explicitly includes a biomedical craft alongside mechanical, electrical, plumbing, HVAC, civil, IT, instrumentation and safety. That means repairing a complex anaesthesia machine can be assigned to a biomedical engineer together with an electrical technician, with estimated and actual hours tracked per craft and a designated lead.

More important for critical devices is binding them to a service-level agreement (SLA). The system supports five contract types — warranty, AMC (annual maintenance contract), service agreement, calibration and rental — each carrying response-time and resolution-time targets. A defibrillator or ventilator fault at critical priority is therefore bound to a guaranteed response window (for example, a 15-minute response and a 4-hour resolution) rather than waiting in a best-effort queue. This binding is what turns a contract from a sheet in a drawer into a commitment the system measures and warns on as a breach approaches.

On work-order closure, an optional digital sign-off step is available once the order reaches the "completed" status — it records who closed the order, with optional digital-signature capture. It is optional, not enforced, but it is there for hospitals that want documented accountability for every repair on a critical device.

When a CBAHI or JCI surveyor walks in, the first thing they look for is not the count of equipment, but evidence that due preventive maintenance was actually completed. Skyline computes this with an explicit formula that runs in the product:

PM-compliance % = (completed due schedules ÷ total due schedules in the period) × 100

A schedule counts as completed if its linked work order was completed within the period. A practical example for a biomedical engineering department: if you had 20 PPM schedules due this month and 18 were completed, PM-compliance = (18 ÷ 20) × 100 = 90%. This figure does not flatter the result by counting "tasks created"; it measures what was actually done against what was due — which is exactly what the surveyor wants to see.

Alongside compliance, the system computes the reliability KPIs MTBF (mean time between failures), MTTR (mean time to repair) and availability from completed corrective work orders, so you know which devices fail most before a failure becomes a safety issue. For the full breakdown of these formulas with worked examples, see the complete CMMS guide.

Failure data is captured at its source: in the Skyline mobile app, on closure the technician captures the ISO 14224 triplet (problem → cause → corrective remedy) from the shipped failure-code catalog, while web closure captures structured root-cause and failure-code fields. It is this structured accumulation that later reveals, for example, that a recurring failure pattern in a particular infusion-pump model warrants a review with the vendor.

In a busy hospital environment, raising a maintenance request must be easy for any member of staff. Skyline accepts work requests through multiple channels: email (auto-converting a message to a work order), WhatsApp, scanning a QR or barcode label on the device itself, and through a public REST API with HMAC-secured webhooks. A nurse who notices a fault in an electric bed can scan the QR code on the bed to raise a request in seconds.

Patient-data residency is a core concern for Saudi hospitals, so Skyline gives you an explicit choice: on-premise deployment entirely on the hospital's own servers inside the Kingdom, keeping data under your direct control, or cloud deployment if you prefer — without giving up any feature in either case. The system runs in around 30 languages in the maintenance module with full RTL support, serving the multinational maintenance teams common in Saudi hospitals.

For city-specific deployment, see CMMS in Riyadh and CMMS in Jeddah. To manage the full medical-equipment lifecycle with IAS 16 depreciation and repair-versus-replace decisions, see CMMS asset management. For long-term support and maintenance packages for critical equipment, explore SKYLINE Care. And for the complete platform picture, the complete CMMS guide remains the primary reference.

The intervals are guidance built inside Skyline's configurable template engine, tuned to match the manufacturer's recommendation and the regulatory requirements for your specific device. The upper rows are drawn from the ready hospital PPM catalog the system ships (12 real templates); the lower rows are engineering recommendations for biomedical device classes, built through that same engine.

The first several rows are taken from the hospital PPM catalog the system ships ready (monthly AHU filters, monthly medical-gas panel per NFPA 99/SFDA, quarterly centrifuge calibration, UPS battery load test, monthly generator run, annual X-ray tube calibration). The biomedical-device recommendations in the lower section are built through the configurable template engine, and the intervals remain guidance that is always governed by the manufacturer's manual and the SFDA requirements for your device.