Servisa
Maintenance management system · CMMS

Stop the breakdown before it stops the line.

Servisa is a CMMS for factories and industrial plants. Build the equipment hierarchy and nameplate records, standardise your PM activities, plan them by time or running hours, run work requests and work orders through your own approval route, and analyse failures until the interval is right — aligned with ISO 14224 and ISO 55001.

Servisa · MaintenanceLIVE
Open WOs
248
PM done
91%
MTBF
412h
Work order
WO-4821 · Pump P-102
In progress72%
Plants
Cranes & hoists
Condition monitoring
Boilers & furnaces
Electrical panels
UPS & power
Utilities
Chillers & HVAC
Spare parts store
Maintenance crew
PARS PETROCHEMICALBahman SteelAlborz Cementsepehr/powerKaveh IndustrialZAGROS REFINERYAria FoodsPAKSHO
Modules

Sixteen modules, built around the equipment.

Equipment-centric by design: the asset carries its own nameplate, activities, failure modes, parts and cost. That is what makes the reporting comparable across every plant you run.

Equipment management

Equipment families, technical attributes, an unlimited hierarchy tree, nameplate records and the PM activities defined per family.

Technical archive

Standard coding, technical nameplate, manuals, drawings and datasheets uploaded against the equipment or its family.

Location management

A tree of plants, halls, lines and rooms. Move an asset and its location moves with it, so the crew always knows where it stands.

Maintenance standards

Standardised PM activities and checklists per equipment family — defined once, reused on every identical machine.

PM & CM planning

Daily, weekly, monthly or annual schedules, based on calendar time or running hours, with an alert lead time you set.

Work request & work order

Report a failure, raise the request, issue the work order, route it to a crew or a person, and track its status to completion.

Emergency maintenance

EM requests raised the moment a machine stops, with downtime measured from the report to the restart.

Root cause failure analysis

Standardised failure modes and causes per equipment, recorded on the work order — the basis for Pareto and repeat-failure reports.

Spare parts

Part nameplate and coding, allocation to equipment, consumption logged per work order, and cost reported per part and per machine.

Workforce management

Personnel records, skills, work groups, and man-hour reporting per person, per crew and per piece of equipment.

Suppliers & contractors

Contractor records by discipline, work assigned out, and a history of everything each one has carried out.

User workspace

Every person and every crew opens a personal queue — the EM and PM work assigned to them, and nothing outside their scope.

Access levels

Unlimited users with permissions set per person and per section, changed by an admin at any time.

KPIs

MTBF, MTTR, MTTF, PM compliance percentage, EM trend and equipment availability, calculated continuously.

Maintenance cost

Man-hour cost, spare part cost and contractor cost recorded per work order and totalled per machine and per period.

Reports & dashboard

Pareto of worst offenders, repeat failures, downtime ranking, open requests and overdue PM — on one management dashboard.

Product

A workspace built around the equipment tree.

Management dashboard

What stopped, what is overdue, and what it is costing.

Open work orders, overdue PM activities, emergency maintenance trend, downtime by machine and cost by category — one page, live, filtered by plant, line or crew.

  • PM compliance percentage against the plan, continuously
  • Pareto of the equipment causing the most downtime
  • Jump from any figure straight to the work orders behind it
app.servisa.ir/dashboard
Dashboard
Equipment
PM plan
Work orders
Failures
Spare parts
Personnel
Reports
Open WOs
248
Overdue PM
7
PM done
91%
EM share
14%
PM vs. emergency maintenance
Last 14 days
WO-4821 · Line 2 · Pump P-102Down 3h
WO-4818 · Utilities · Compressor C-3In progress
WO-4810 · Line 1 · Motor M-45Closed
Equipment & technical archive

The equipment tree, from the plant down to the bearing.

Group equipment into families — pumps, electric motors, cranes, valves, compressors — then build an unlimited hierarchy beneath each location. Every machine carries its nameplate, its standard activities, its failure modes and its documents.

  • Equipment families with shared activities and failure modes
  • Standard coding and technical nameplate per machine
  • Manuals, drawings and datasheets attached to the record
Equipment register
10,482 assets
Equipment
Location
Last PM
Next PM
Status
Centrifugal pump P-102
Line 2 · Acid
12 Jun
12 Sep
Running
Electric motor M-45
Line 1
02 Apr
02 Jul
PM due
Overhead crane CR-2
Casting hall
28 May
28 Aug
Running
Screw compressor C-3
Utilities
19 Jan
19 Jul
Overdue
Cooling tower CT-1
Utilities
08 Jun
08 Dec
Running
PM planning

Plan a year of PM, against the crew you actually have.

Attach standard activities to each equipment family, set the interval by calendar or by running hours, and Servisa builds the dated plan and raises the alert ahead of the due date. Balance a week across your crews without losing the plan underneath.

  • Intervals by time or by equipment running hours
  • Alert lead time set per activity
  • One checklist can cover several machines in a single visit
September 2026
PMInspectionEmergency
Sat
Sun
Mon
Tue
Wed
7
Line 2 · Pumps
8
Crane inspection
Chiller CH-1
9
Motor M-45
Compressor C-3
Boiler B-2
10
Valves · Line 1
11
Annual inspection
Week 37 · 92% of crew hours allocated3 free slots
Cost & failure analysis

What every stoppage actually cost you.

Man-hours, spare parts and contractor charges are logged on the work order as the job is done. Totalled per machine and per period, they show you which equipment is quietly consuming your budget — and the failure analysis tells you why.

  • Man-hour, spare part and contractor cost per work order
  • Cost accumulated per machine, line and period
  • Failure mode and root cause recorded on every breakdown
  • Pareto of the equipment with the most failures
412h
average MTBF across critical equipment
3.4h
average MTTR after standardising activities
Cost report · WO-4821
Closed
From work order WO-4821
Equipment
Centrifugal pump P-102
Line 2 · Acid unit
Downtime
3h 20m
From failure report to restart
Description
Qty
Cost
Technician man-hours
4.5 h
$135.00
Bearing SKF 6208
2 pcs
$88.00
Contractor · alignment
1 job
$20.00
Man-hours$135.00
Parts & contractor$108.00
Total cost$243.00
Close work orderExport reportFailure cause recorded · bearing wear
Mobile

A shop-floor app the crew will actually open.

Scan the QR code on the machine and its nameplate, checklist and failure history are on the phone. Report a stoppage from the line, complete the PM checklist, log the parts you fitted — offline if the plant has no coverage.

Today's work orders
QR code scan
Photo evidence
Failure reporting
Works with no signal — syncs when the network is back
9:41▮▮▮
Tue, Sep 9
6 work orders today
In progress08:30
Line 2 · Pump P-102
Quarterly PM · 45 min · Acid unit
Scheduled11:00
Utilities · Compressor C-3
Monthly PM · 90 min
Scheduled14:15
Line 1 · Motor M-45
Inspection · 30 min
9:41▮▮▮
WO-4821 · In progress
Line 2 · Pump P-102
KSB EtanormQuarterly PM
PM checklist · 4 of 6
Bearing lubrication
Casing temperature
Vibration reading
Close work order
9:41▮▮▮
Supervisor sign-off
Mehdi Karimi · Maintenance Supervisor
Work order cost summary
Man-hours · 4.5 h$135.00
Bearing SKF · 2 pcs$88.00
Total cost$223.00
Close work order
How it works

From the equipment tree to a falling failure rate.

01

Equipment tree

Families, hierarchy, coding and technical nameplate.

02

Standard activities

PM checklists and failure modes per family.

03

PM planning

Intervals by time or running hours, with alerts.

04

Request & work order

Routed to the crew, executed, reported on site.

05

Cost & cause

Man-hours, parts and root cause recorded.

06

Analyse & improve

MTBF, MTTR and Pareto drive the next interval.

What plants get out of it — and why they stay.

Measured across 500 industrial sites over their first two quarters. None of this needs a consultant on site.

−41%

Less emergency work

EM share of total work orders, once PM activities are standardised and actually planned.

−32%

Less downtime

Unplanned stoppage hours on critical equipment.

+2.1×

Longer MTBF

Mean time between failures on the equipment that used to fail most.

−18%

Lower maintenance cost

Spare parts, man-hours and contractor spend combined.

1

One equipment record

One system replaces the spreadsheets, the notebook and the whiteboard.

0+
assets under management
0+
industrial sites
0%
PM compliance
0K+
work orders closed
Customers

Maintenance teams that stopped firefighting.

Our EM share was over half of all work orders. Once the equipment tree and the standard activities were in, planned work took over — and the pumps that used to fail monthly now run a full quarter.
Naser Jalali
Maintenance Manager, Pars Petrochemical
The failure analysis reports changed the argument. I can show which machine caused the most downtime and why, instead of asking for budget on instinct.
Maryam Ahmadi
Reliability Engineer, Alborz Cement
Man-hours and spare parts are now recorded against the machine. For the first time I know what each line actually costs us to keep running.
Hamid Rezaei
Technical Deputy, Bahman Steel
Pricing

Priced by plan, not by how much equipment you own.

Unlimited equipment, unlimited spare parts and unlimited users on every plan. You choose the module set, not a per-asset licence.

Trial

Evaluate it on one line before committing.

Free
30 days, one plant
  • Equipment tree and nameplate
  • PM planning
  • Work requests and work orders
  • Basic reports

Base

The sixteen core modules for a single site.

Base/mo
the sixteen core modules
  • All sixteen base modules
  • RCFA and failure analysis
  • KPIs: MTBF, MTTR, MTTF
  • Spare parts and man-hour cost
  • Unlimited users and access levels
Most popular

Plus

Management reporting and a work calendar on top.

Plus/mo
base plus management tools
  • Everything in Base
  • Management dashboard
  • Work calendar
  • Maintenance cost analysis
  • Implementation consulting

Advanced

Multi-site groups, mobile and notifications.

Advanced/mo
for holdings and groups
  • Everything in Plus
  • Mobile and tablet UI
  • SMS and push notifications
  • Multi-organisation for holdings
  • Equipment QR code scanning
FAQ

The questions every maintenance manager asks first.

Something else — talk to a specialist.

The software is the short part; collecting the equipment data is the real work. We provide free training and consulting for building the equipment tree, the coding system and the nameplate records, so the data you enter is structured correctly the first time. Most sites run their first planned PM within weeks, not months.

No. Servisa is equipment-centric rather than industry-specific, so it adapts to any plant and any machine. It is in use across petrochemical, steel, cement, power, mining, food and pharmaceutical sites.

The modules follow ISO 14224 for reliability and maintenance data collection and exchange, and ISO 55001 for physical asset management. That is what makes failure and reliability data comparable between your own sites.

Yes. There is provision for reading and writing data to any database, so equipment, personnel, spare parts and cost data can move between Servisa and your existing systems without a hard limit on format.

PM is planned work done to prevent a failure. CM is corrective work aimed at the root cause so the same failure does not recur. EM is emergency work after a stoppage. PdM is condition-based — vibration, thermography, oil analysis — used to predict a failure before it happens. Servisa plans and reports on all of them separately.

No. The mobile app captures work orders, checklists, readings, photos and failure reports on the device and syncs when it reconnects — which matters inside plants where coverage is unreliable.

Ready to see it on your own equipment?

Book a demo session and we will walk through the modules, the reports and the pricing against your own plant and your own failure history.

See the modules