Guide · fleet management
Software for railway equipment and fleet management
"Railway equipment" can refer to rolling stock, specialised works equipment, a shunter or a road-rail machine: these pieces of equipment do not share the same records or the same rules. Management software must therefore first qualify the equipment, then link identity, configuration, documents, maintenance, scheduling and field reports in a single record.
Definition
Railway equipment, rolling stock or road-rail vehicle: define it before you manage it
The term "railway equipment" is broad. It can refer to rolling stock, specialised works equipment, a shunter (rail tractor), or a road-rail machine able to operate off-track then on rail. These pieces of equipment do not share the same records, the same operating rules, or the same mission information. Software should therefore not infer its model from the word "equipment" alone.
Trackary is presented as a fleet management piece of software for road-rail equipment. Other equipment can only enter a deployment if its use, its data and its workflows are explicitly defined. This boundary avoids claiming that an application universally covers the whole railway sector when reality depends on the family, the configuration, the network and the organisation.
Equipment family
Name the machine and its actual function: road-rail excavator, aerial work platform, vehicle, shunter or specialised equipment.
Tracked configuration
Distinguish the base machine, the railway components, the tools, the attachments and the variants relevant to the mission.
Area of use
Link the equipment to the site, the network, the procedures and the people who prepare or approve its use.
A search term does not define a software scope
Before any demo, you need to check which families are actually managed and which decisions the application must document. Trackary does not replace this qualification work.
Data model
What a fleet management piece of software must link in a single record
A useful record is not limited to a name, a model and a next date. It must help you understand which equipment is concerned, in which configuration, with which parts and which history. This structured information then feeds scheduling, maintenance, configured inspections and field reports.
The level of detail depends on the fleet. If every variant is tucked into a comment, searches and inspections become fragile. Conversely, a hundred mandatory fields slows down field work. The pilot deployment should therefore find a level of detail sufficient for decisions without turning the record into a theoretical inventory.
| Block | Useful information | Decision it enables |
|---|---|---|
| Identity | Fleet number, manufacturer, model, identifiers and ownership or holding status | Find the right machine without ambiguity |
| Configuration | Railway components, tools, attachments and recorded restrictions | Compare the need against the prepared configuration |
| Documents | Type, version, scope, date, author or body, and the linked file | Find the applicable document without confusing two machines |
| Availability | Planned mission, downtime, open action and known status | Spot a conflict before assignment |
| Maintenance and deadlines | Plan, relevant meter, work order, report, observation and next action | Prepare the work and keep its timeline |
| Field work | Configured inspection, event, useful photo, report and synchronisation | Pass the finding to the office without re-entering data |
Trackary links data to the workflow
Trackary centralises machine records, scheduling, configurable inspections, documents and the report history. The detail of fields and rules is defined during the fleet's scoping phase.
Fleet management
Moving from "managing a machine" to a verifiable workflow
Managing railway equipment is not a single action. It links a request, an available machine, a configuration, parts, a field finding and a return decision. An application becomes useful when each role picks up the information where the previous one left it, without creating a side spreadsheet or a separate message thread.
To evaluate equipment software, you need to run through a normal case and then a case with a deviation. The second one reveals the limits: a missing document, a scheduling conflict, an observation before departure, a network outage or an action left unclosed. The product should show the status and the history without inventing the business decision.
- Qualify the request Describe the mission, the period, the site, the family and the expected configuration.
- Select a machine Compare the request against the fleet, assignments, open actions and available information.
- Prepare the file Gather the parts, attachments, contacts and inspections planned for this mission.
- Work in the field Consult the prepared data, record findings and make the synchronisation status visible.
- Handle deviations Keep the initial finding, assign the action and record the competent person's decision.
- Close and learn Attach the report to the record, update availability and analyse recurring issues.
Checklist
- ✓ A user can find the right machine with a stable identifier.
- ✓ The schedule shows the request, the assignment and the downtime without confusing them.
- ✓ Documents stay linked to their scope and version.
- ✓ Field teams can tell apart data that is available, local, pending or synchronised.
- ✓ An observation keeps its author, its date, its part and its follow-up.
- ✓ Returning to service results from an identified decision, not an automatic colour.
Software choice
Comparing fleet management, CMMS and business software on the same scenarios
A fleet tool can be effective for inventory and assignment. A CMMS generally structures equipment, maintenance plans and work orders. Business software links requests, configurations, field forms and organisation-specific rules more closely. These categories sometimes overlap: only testing real workflows lets you choose.
The right criterion is not the number of advertised modules. Note what works natively, what needs configuration, what needs customisation and what remains out of scope. Data migration, access rights, offline mode, exports, backups and software maintenance are all part of the decision.
Fleet management
To be evaluated for inventory, assignments, availability and information shared across a fleet.
CMMS
To be evaluated for maintenance plans, meters, work orders, parts and technical history.
Business software
To be evaluated when configurations, field inspections, roles and exceptions form a differentiating process.
- Have the fleet manager, field staff and workshop test the software.
- Import some representative data rather than relying on an entirely scripted demo.
- Actually disconnect the network if an offline workflow is required.
- Check exports and that someone who did not take part in the test can read the history.
- Define a pilot, its indicators and the conditions for rolling it out.
A Trackary demo starts from the fleet
The demo can reuse representative families, documents and scenarios to check the full workflow. A feature is only considered covered once it has been shown within the agreed scope.
Hired equipment
Managing the hire of railway equipment without mixing up software and rental company
A search such as "rail equipment for hire" may be aimed at an equipment supplier. Trackary is neither a rental company, nor a marketplace, nor a matchmaking service. The software comes into play after the organisation has identified its need and its partners.
In a fleet that includes hired equipment, Trackary can organise the operational file agreed during scoping: request, equipment received, configuration, documents, starting condition, field reports, events and return. The contract, the choice of provider, compliance, responsibilities and the decision to use the equipment remain the responsibility of the relevant parties and competent people.
Looking to hire equipment?
Trackary does not provide a catalogue and does not recommend any rental company. The page on managing hire only explains how to track equipment whose hire has already been arranged.
Going further
Trackary is also equipment fleet management software and a CMMS for the whole fleet, not just railway equipment. For statutory deadlines, see the VGP inspection tracking software; to plan servicing by the hour, the preventive maintenance plan (free Excel template); for budgeting, the cost of a CMMS.
Frequently asked questions
Sources and limits of this guide
- EPSF — Works trains and construction equipment ↗ Useful background to avoid reducing railway equipment to a single software category.
- SNCF Réseau — Checking the compliance of your works equipment ↗ Overview of the compliance-checking framework for works equipment, distinct from the tracking carried out in a management application.
- INRS — Acquisition, resale, hire, loan and provision of machinery ↗ Points of reference on the information, documents and responsibilities linked to hiring or providing a machine.
- Software centralises information and formalises a process defined by the organisation. It does not replace regulatory analysis, physical inspection or the decision of a competent person.
- The term "railway equipment" covers different equipment types and frameworks. Trackary's scope must be verified for each family and organisation.
- Trackary is fleet management software for road-rail equipment. It does not hire, sell, certify or recommend any equipment or provider.