• Fleet managers compiling serviceability states from multiple unit-level spreadsheets and email reports each morning, with no single authoritative view of how many platforms are available for tasking at any given time?

  • Modification control managed through a paper-based configuration state record that takes days to update after each modification embodiment, leaving the configuration baseline uncertain during the gap?

Defence Equipment Lifecycle Management Software

Defence equipment management spans the full lifecycle from acceptance into service through routine maintenance, modification, deep maintenance, and eventual disposal -- and each phase generates documentation obligations that standard commercial asset management platforms were not designed to meet. Fleet managers, technical authorities, and project offices need visibility of the current configuration, serviceability status, and maintenance state of every platform across the force element.

We build equipment lifecycle management systems designed around the specific requirements of defence asset management -- your equipment types, your maintenance schedule structure, your modification control process, and the serviceability reporting your command chain relies on for operational planning.

  • Asset register capturing the full equipment inventory with individual platform records linked to their configuration baseline, modification state, and maintenance history

  • Maintenance scheduling from operator-level servicing through deep maintenance with due dates calculated from the current usage reading and the schedule in the maintenance publication

  • Modification state tracking recording each applicable modification, its embodiment status on each platform, and the configuration difference between the baseline and the current as-modified state

  • Serviceability reporting at unit, formation, and force-element level so commanders have a consistent, near-real-time view of available platforms

RaftLabs builds custom defence equipment lifecycle management software for defence organisations that need asset registers, maintenance scheduling, modification state tracking, serviceability reporting, technical data management, and disposal workflow in one connected system. Most projects deliver in 14 to 20 weeks at a fixed, agreed cost.

Vodafone
Aldi
Nike
Microsoft
Heineken
Cisco
Calorgas
Energia Rewards
GE
Bank of America
T-Mobile
Valero
Techstars
East Ventures
100+Software products shipped
FixedCost delivery
14-20Week delivery cycles
24+Industries served

When commercial asset management platforms cannot meet defence equipment management requirements

Commercial enterprise asset management platforms handle maintenance scheduling and inventory management well for standard commercial and industrial assets. Defence equipment management has additional requirements that commercial platforms do not address. A military vehicle fleet needs modification state tracking against a configuration baseline defined by the design authority. A naval vessel needs maintenance scheduling against a planned maintenance system that spans operator-level through deep maintenance periods, with each maintenance interval tied to usage parameters -- operating hours, cycles, or calendar time -- rather than a simple calendar schedule. A weapons system needs technical data management linking each maintenance task to the approved technical publication and the applicable amendment state.

Custom defence equipment lifecycle management software is built around the specific requirements of your equipment type and your maintenance management system -- whether that follows JSP 886, the Defence Materiel Organisation's maintenance management framework, or the maintenance publication structure specific to your force element.

What we build

Asset register and configuration baseline

Equipment inventory structured at fleet, unit, and individual platform level -- each platform record capturing the equipment type, mark, serial number, national stock number, owning unit, physical location, acceptance date, and current configuration baseline. Configuration baseline management recording the design authority's approved baseline for each equipment mark and variant, against which the as-modified state of each individual platform is compared to identify configuration deviations. Sub-equipment and component register for major assemblies and life-limited components fitted to each platform, with the assembly serial number, manufacture date, installed date, and accumulated usage linked to the parent platform record. Acceptance documentation storage linking the acceptance certificate, initial technical inspection report, and handover documentation to each platform record at the time of entry into service. Platform history recording every significant event in the platform's service life -- maintenance periods, modifications, repair actions, defect reporting, and deployment -- as a chronological record accessible from the platform record.

Maintenance scheduling

Maintenance schedule structured across the schedule hierarchy defined in the maintenance publication -- operator servicing, first-line maintenance, second-line maintenance, and deep maintenance -- with each schedule item configured with its usage interval, its calendar interval, and the maintenance organisation authorised to carry out the work. Usage reading update from the operational record -- flying hours, engine hours, kilometres, cycles, or round counts -- triggering recalculation of all maintenance due dates for the affected platform. Due date visibility for each platform showing the next-due maintenance item across all schedule levels, the current usage, and the remaining life before the next due date, in a format usable by both the unit REME or equivalent and the fleet manager. Deferred maintenance management recording items deferred beyond the scheduled due date with the deferral authority, the deferral basis, and the revised due date -- so deferred items are visible and tracked rather than lost in a paper trail. Maintenance period planning for deep maintenance activities requiring the platform to be out of service for an extended period, with the planned induction date, expected completion date, and unit impact tracked against the maintenance programme.

Modification state tracking

Modification register for each applicable modification or engineering change to the equipment type -- each modification record capturing the modification authority, the modification description, the applicable platforms by serial number range or individual serial number, and the embodiment method. Embodiment status for each modification on each applicable platform -- not yet embodied, embodied, or not applicable -- updated when the modification is completed and the modification state record is signed off by the authorised person. Configuration difference report for any platform showing the modifications embodied relative to the current baseline and the modifications outstanding -- the basis for the platform's current configuration state record. Modification kitting management for modifications requiring spare parts or special tools -- the kit status tracked against each planned embodiment so the unit can see whether the kit is available before scheduling the modification work. Modification authority document storage linking the relevant equipment programme office instruction, modification leaflet, or technical bulletin to each modification record so the authorised text is accessible from the modification register.

Serviceability reporting

Daily serviceability state at platform level showing each platform's current status -- fully serviceable, downgraded, unserviceable, under maintenance, or awaiting spare parts -- with the reason for any non-serviceable status and the expected return to service date. Unit-level serviceability roll-up showing the total held, the serviceable count, the maintenance count, and the unserviceable count for each equipment type within the unit, in a format matching the reporting requirement of the higher formation. Formation and force element reporting aggregating serviceability across all subordinate units, with the percentage serviceable calculated against the establishment and the overall fleet ready rate. Unserviceability reason analysis showing the primary reasons for unserviceability across the fleet -- awaiting maintenance, awaiting spare parts, awaiting technical authority decision, or defect under investigation -- to support sustainment prioritisation decisions. Trend reporting showing serviceability rate over time by unit and fleet, identifying whether fleet readiness is improving or declining and correlating changes with maintenance programme or spare parts supply events.

Technical data management

Technical publication register for each equipment type -- maintenance manual, illustrated parts catalogue, operator's handbook, technical bulletins -- with the current amendment state, the next scheduled review date, and the authority responsible for maintaining the publication. Amendment management tracking each publication amendment, its effective date, and its incorporation status across the relevant units, with the amendment authority and distribution list recorded. Maintenance task linkage connecting each scheduled maintenance item and modification embodiment instruction to the applicable chapter, section, and paragraph of the authorised technical publication -- so the maintainer always has the correct publication reference visible alongside the task. Technical query management for questions raised by units about the interpretation of a technical publication, routed to the technical authority with the response and its reference recorded against the query for future use. Publication access control ensuring that units can access the current amendment of the publications applicable to their equipment while archive versions are retained for historical reference and investigation purposes.

Disposal workflow

Disposal authorisation workflow for platforms reaching the end of their planned service life, a fatigue life limit, or the decision point for withdrawal from service -- the disposal authority, the disposal basis, and the planned disposal date recorded against the platform record. De-preservation and preparation checklist for platforms being prepared for disposal, with each step signed off by the responsible person and the completion date recorded. Cannibalisation authorisation for serviceable components and assemblies removed from disposal platforms for use on active platforms -- each cannibalisation event recording the removed item, its condition, its transfer to stores inventory, and the platform it was removed from. Disposal documentation package generation compiling the platform's service record, modification state, component history, and disposal authority documentation into the package required for the disposal authority or the receiving disposal organisation. Platform record closure when disposal is complete, retaining the full service history in an archived state for the regulatory retention period without the platform appearing in active fleet serviceability reports.

Frequently asked questions

Yes. The system supports multiple equipment types -- vehicles, aircraft, vessels, weapons systems, communications equipment -- each with its own maintenance schedule structure, modification baseline, and serviceability reporting hierarchy. Role-based access controls which users can see and update records for each equipment type and unit.

The technical data management module tracks the current amendment state of each publication and the distribution of each amendment to units. When a new amendment is issued, the system records the amendment, distributes it to the relevant units, and updates the effective amendment state of the publication. Units acknowledge receipt and incorporation, and the incorporation status is visible to the technical authority.

Yes. Serviceability report formats are configured to match the reporting requirements of your formation's standard report structure. Where the higher formation requires a specific format -- a SALSTAT, a vehicle state report, or a formation readiness report -- the system generates that format from the underlying data without manual compilation.

A focused build covering asset register, maintenance scheduling, and serviceability reporting typically runs $55,000 to $110,000 depending on scope and equipment types. Adding modification state tracking, technical data management, and disposal workflow brings the total to $110,000 to $200,000. Fixed cost agreed before development starts, no hourly billing.

Related defence software

Talk to us about your equipment lifecycle management project.

Tell us about your equipment types, your maintenance management framework, and where your current lifecycle management process creates gaps in configuration visibility or serviceability reporting. We'll scope a system built around your actual fleet and reporting requirements.