Rolling Stock Asset Management System

Published requirement

Based on the November 2025 planning requirement: a rolling-stock asset management system connecting maintenance, assets, materials, costs and traceable electronic records. Historic engagement dates have passed; this is not presented as a currently open tender.

What Pura has built

A working synthetic journey connects a defect to its asset, maintenance work, materials, engineer evidence, checker review and simulated release. A preventive-maintenance journey shows calendar and mileage work alongside corrective work.

Our supported interpretation

The sample hierarchy, job states, roles, reviewer steps and scoped third-party view are Pura interpretations, not verified TfW procedures.

What still needs confirming

Actual workflows, safety and release authority, data, permissions, integration, migration, mobile and offline needs, and the current procurement route. A later expired fleet/stores tender has a different procurement identifier; its relationship to the planning requirement remains unknown.

Synthetic data only

Fictional records. No TfW system connection, operational data, safety advice or real release authority. Simulated roles and audit are not production controls. No credentials, uploads, external messaging or AI dependency.

What is confirmed

• Replace the existing rolling-stock AMS.
• Legacy and modern rolling stock.
• Planning, execution and reporting.
• Preventive and corrective maintenance.
• Material availability and management.
• Inventory optimisation.
• Warranty and cost control.
• Real-time fault and delay reporting.
• Operational and financial analytics.
• Railway safety and regulatory compliance.
• Third-party maintenance operations.
• Asset traceability and auditability.
• Electronic maintenance records.
• Change logs, user activity, audit trails.
• TfW internal and third-party systems.
• Mobile and desktop usage.

Requirement description corroborated by owner-provided scope and official indexed notice; full original PDF unavailable. No operational procedures inferred as facts.

£5,000 + VAT · Two-week bounded discovery

Proposed scope under Andrew's approved DISCOVERY proposition. Not a price for a complete AMS, production railway software, certification or an awarded contract. Subject to a confirmed buyer/procurement route, named sponsor and agreed access to process descriptions; no commitment or supplier contact has been made.

Boundary: one representative corrective journey and one preventive journey for one agreed fleet/asset slice. Up to three 90-minute remote workshops plus one 60-minute readout; one review cycle of the existing synthetic prototype, if useful. No open-ended requirements programme or full fleet rollout.

Week 1: validate maintenance workflows, asset/fleet model, users/roles, materials, warranty/cost and mobile needs. Record success measures and scope exclusions. Outputs: workflow maps, persona/control matrix, indicative entity model and a prioritised requirements register with facts, assumptions and unresolved decisions.

Week 2: inventory integration boundaries and ownership, compliance/audit questions, data quality/migration dependencies and non-functional constraints. Refine the bounded non-production prototype once against feedback where appropriate. Outputs: interface inventory, migration assessment, control/assurance questions, implementation specification, dependency/risk register and prioritised roadmap. Safety applicability and release authority must be validated by TfW's competent people; Pura does not supply railway certification through this engagement.

Acceptance: both agreed journeys reviewed, feedback disposition recorded, named unknowns and dependencies retained, specification and roadmap handed over. TfW can stop with those outputs. Future delivery scope, partner requirements, budget and route are separate decisions, not an implied implementation promise.

Excluded: operational data access, live interfaces, production build/hosting/support, real migration, licences, penetration certification, safety certification, legal advice, formal bid preparation, on-site depot work and binding procurement actions. No credential or actual fleet record is needed for the synthetic discovery proof.