For Genset, UPS & Power Equipment Service
Power equipment service software for genset and UPS teams.
Schedule PMs from runtime hours, monitor critical-load SLA contracts, and track van stock — BeanRails is built for the operational realities of power equipment service in Malaysia and Singapore.
14-day free trial · Built for MY & SG · PM, SLA, runtime, parts
Why power equipment teams switch
Four operational realities BeanRails is built around.
Power equipment service is not generic field service. The work is contract-driven, runtime-driven, and SLA-bound — BeanRails models all of this out of the box.
PM schedules drive revenue
Every genset under contract runs on a PM schedule — every 250 hours, every 500 hours, every 1000 hours. BeanRails schedules these from runtime or calendar intervals and auto-creates the job before the unit is due.
Runtime data lives in the generator
Modern gensets record their own runtime, fuel use, and fault logs. BeanRails imports this data so jobs are only created when the unit is actually due — not just on a fixed calendar.
Critical-load SLA contracts
Hospitals, data centres, and factories pay premiums because downtime is not an option. BeanRails tracks SLA response times per customer, escalates overruns automatically, and produces monthly SLA compliance reports.
Spare parts logistics
A service van carries dozens of SKUs — filters, belts, hoses, sensors, fluids. BeanRails tracks what is on each van and triggers replenishment when stock runs low.
Workflow
A monthly PM cycle on BeanRails.
PM auto-generated
Job appears in the queue when the unit reaches its service interval (runtime or calendar).
Dispatch
Dispatcher assigns the job to the next available technician with the right skill and parts on their van.
On-site PM
Technician completes the checklist on the mobile app, captures runtime, parts used, and any faults.
Quality review
Service manager reviews the job, photos, and any fault findings. Escalates if a major repair is needed.
Customer sign-off
Customer signs on the phone. Service report emailed automatically. Job closed.
Invoice & compliance
Monthly contract billing runs from completed PMs. SLA compliance report generated for the customer.
Features for power equipment service
The BeanRails features power equipment teams use most.
Job Scheduling
Auto-generate PM jobs from runtime hours, calendar, or both.
Learn more →Mobile Field Service App
PM checklists, runtime capture, fault code entry — all on the phone.
Learn more →Work Order Management
Multi-step PM tasks with parts allocation, photos, and sign-offs.
Learn more →CRM
Equipment records with model, serial, install date, runtime hours, and SLA tier.
Learn more →Quoting & Invoicing
Recurring contract billing and ad-hoc service job invoicing.
Learn more →Reporting & Analytics
PM compliance, SLA performance, parts consumption, and revenue per contract.
Learn more →Use case
One customer. Forty gensets. Every PM on time.
A hospital group has forty gensets across ten sites. Each genset runs on a different PM interval depending on its size and load. Some are 250-hour intervals, some are 500, some are 1000. The service contract charges monthly based on the units under coverage — and the customer expects every PM done on time, every time.
BeanRails handles this without spreadsheets. Each unit is a record with its model, runtime hours, and PM intervals. When runtime crosses the next interval threshold, a PM job is auto-created and scheduled to a technician with the right skill and the right parts on their van. SLA clocks tick from the moment the job is raised.
At the end of the month, BeanRails generates the SLA compliance report — every PM, every fault, every response time, every resolution. The hospital's facility team sees the same report. No more chasing paperwork. No more missed PMs.
FAQ
Common questions about BeanRails for power equipment service.
Does BeanRails support runtime-based PM scheduling?
Yes. Each unit is configured with its PM intervals in hours (e.g. every 250 / 500 / 1000 hours). When runtime data is imported or manually updated, BeanRails auto-creates the next PM job when the unit reaches the threshold.
Can BeanRails import runtime data from genset controllers?
Yes, via API or CSV. We integrate with common controller platforms (ComAp, Deep Sea, PowerCommand, and others) so runtime, fault codes, and battery voltage flow in automatically.
How does BeanRails handle SLA contracts?
Each contract has an SLA tier (e.g. 2-hour response, 4-hour resolve). BeanRails tracks every job against the tier, escalates when the clock runs out, and produces monthly SLA reports per customer.
Does BeanRails track spare parts on service vans?
Yes. Van stock is tracked per technician. When a part is used on a job, the count decrements. When stock falls below threshold, BeanRails raises a replenishment order to the warehouse.
Can customers see PM compliance online?
Yes. The customer portal shows upcoming PM visits, completed service history, runtime logs (where integrated), and outstanding invoices.
Does BeanRails handle multiple units per customer?
Yes. One customer can have dozens of units on the same account — each with its own PM schedule, SLA tier, and contract terms. BeanRails handles this natively without per-customer hacks.
Schedule every PM. Hit every SLA.
Try BeanRails free for 14 days. Runtime-driven scheduling, SLA tracking, van stock, and customer-facing reports — without the spreadsheets.