Product reference
RampWorks ships 11 modules grouped into four areas. Each page below covers what the module does, how to work it, who uses it and what it exports.
Where every session starts — the state of the operation, and the work that is yours.
The landing screen for every signed-in user. It totals allocated, completed, in-progress, upcoming and overdue work across the stations you have access to, then plots the same set on a due-date calendar so a month of exposure is legible at a glance.
Explore the moduleThe technician view. Instead of the whole station, My day shows only the work orders assigned to the signed-in user, sorted by urgency and then by due date, with a calendar alternative for anyone who plans a week ahead.
Explore the moduleThe modules crews live in during a shift: jobs, inspections, fuel and scheduled maintenance.
The core record. A work order carries the job description, the asset it applies to, who owns it, the checklist to be worked through, the defects found, the materials consumed, the labour booked and the full audit history of every status change.
Explore the moduleA deliberately short form so that logging a refuel takes seconds on the ramp, backed by a reporting view that turns those entries into an asset-by-date consumption matrix.
Explore the moduleA per-asset daily inspection with a checklist drawn from the asset type, a serviceability outcome, and a direct path from a failed check to a work order — so a defect found at 6 am is a tracked job by 6.05 am.
Explore the moduleScheduled maintenance as a rule rather than a reminder. A PMI group targets an asset type and fuel type, carries a frequency and a service sequence, and generates the due work orders itself — idempotently, so running generation twice does not double-book the fleet.
Explore the moduleThe registers behind the work — the equipment itself, and the parts that keep it running.
The master record for every piece of ground support equipment: identity, location, lifecycle, fuel type, make and model. Every work order, refuel entry and health check hangs off an entry here, which is why getting the registry right is the highest-leverage setup work in the platform.
Explore the moduleA lightweight parts store: what is on the shelf, what the safety level is, and every add and use that moved the count — enough to stop a job stalling on a part nobody knew had run out.
Explore the moduleStandards, reporting and the master data that every other module reads from.
One place to define what "inspected" means. Items are mapped to a work type and an asset type, and every work order and health check of that combination is populated from the library automatically — so improving a checklist improves every future job at once.
Explore the moduleThree panels — work operations, fleet and safety, fuel and resources — built from the same live records the crews are creating, plus an executive PDF and detailed Excel exports for the reporting pack.
Explore the moduleThe administrator module. Five tabs cover user accounts, stations, service providers, roles and module access, and the reference values every other module draws its dropdowns from.
Explore the moduleAcross every module
Operational modules export the list you are looking at, with your filters applied, to Excel and PDF. Work orders additionally produce an individual job PDF, and reports produce an executive overview PDF alongside detailed Excel.
Station, date range, type and status filters behave the same way in every module, and a Clear filters control resets them in one click. What is on screen is what exports.
Entries carry who submitted them and when, and corrections carry who edited them. Work-order status changes are kept as an audit history rather than overwritten.
A module hidden by role is not reachable by typing its address, and records outside your station or provider scope are not returned by the API in the first place.
The how-to-use guide covers the same modules as ordered procedures — what to press, in what order, and what the field actually means.