How do rail component makers answer a tender?
A train builder buys a subsystem for a named vehicle project. An operator or maintainer buys overhaul components or replacement units for a fleet. Either way the enquiry is a package of documents, and four of them carry most of the obligations.
| Document | What it holds | What catches a bidder out |
|---|---|---|
| Technical specification | Function, performance, environment, mass, noise, interfaces, standards, tests and documents for the subsystem | Requirements written as prose with several obligations in one paragraph, and standards cited without an edition |
| Requirement list | The same requirements as numbered lines, exported from the customer's requirements tool to a spreadsheet or PDF, each with an identifier | Lines in the list that have no match in the specification text, and columns the supplier is expected to fill in |
| Interface documents | Mechanical fixing points, envelope, electrical connectors, supply voltage, signals to and from the train control system, air supply | Values marked as to be confirmed, and interface requirements that sit only in a drawing |
| Supplier quality requirements | The customer's general rules for suppliers: quality system certificate, first article inspection, change control, special processes, traceability and record retention | A general document that applies to every order and that nobody on the bid team has read against this product |
| Commercial and project documents | Delivery programme, design review dates, warranty, reliability commitments and the list of documents to be delivered | Reliability or availability figures and penalties placed in the contract terms and not in the specification |
Most customers want the answer returned in their own format. That is usually the requirement list with extra columns filled in for each line: a status, a comment and how the supplier will prove the requirement. The identifiers must come back unchanged, because the customer imports the answers into the same tool they were exported from.
- Collect every document in the enquiry and note its revision. Check that the requirement list and the specification are at matching issues.
- Split prose requirements so that each line asks for one thing.
- Read the supplier quality requirements and the interface documents with the same care as the specification.
- Answer each line from a product document you can name: a technical description, a calculation summary, a test report or a procedure.
- State how each requirement will be verified and at which project stage.
- List every difference and every open question, with the requirement identifier.
Which standards come up in rail component tenders?
A rolling stock specification names a long list of standards. Six families appear in almost every component enquiry. The table gives each at name level only. It is our own summary and not a substitute for the documents. Editions change, and two of these were reissued in 2026, so use the edition your contract names.
| Standard | Subject | What the tender usually asks the supplier for |
|---|---|---|
| ISO 22163 | Quality management system requirements for rail sector organisations, built on ISO 9001. It is the basis of IRIS Certification | A valid certificate whose scope covers the product and the site that will make it |
| EN 15085 | Welding of railway vehicles and components, in six parts | A welding manufacturer certificate at the classification level the welded parts need, plus the weld records |
| EN 50126 | Specification and demonstration of reliability, availability, maintainability and safety, known as RAMS | A RAMS plan and a set of analyses and data at fixed project milestones |
| EN 45545 | Fire protection on railway vehicles. Part 2 covers the fire behaviour of materials and components | Fire test reports for each non-metallic material, to the hazard level the vehicle needs |
| EN 50155 | Electronic equipment used on rolling stock | Type test evidence for control units and other electronics, and routine tests on each unit |
| EN 12663 | Structural requirements of railway vehicle bodies | For structural parts and equipment fixings, strength evidence against the load cases the vehicle builder passes down |
Product standards for the subsystem itself sit beside these: doors, brakes, HVAC, couplers and so on each have their own. The customer may also name national rules and its own company standards. Where two documents disagree and the order of precedence is not written down, ask.
What goes in the compliance matrix and deviation list?
A rail compliance matrix has one row per requirement identifier. It differs from a matrix in other sectors in one respect: the customer expects a verification method on every row, because the same matrix later becomes the plan for proving the design.
| Column | What goes in it |
|---|---|
| Requirement identifier | The customer's own identifier, unchanged, with the specification clause where there is one |
| Requirement text | The customer's wording, copied and not paraphrased |
| Compliance statement | Compliant, partially compliant, not compliant or not applicable, in whatever terms the customer's template uses |
| Supplier comment | What is offered, in one or two sentences, with the supplier document that supports it |
| Verification method | How compliance will be shown. Customers commonly offer a short list such as analysis or calculation, review of design, type test, routine test and inspection |
| Verification stage | The project milestone at which the evidence is due, such as a design review, first article inspection or vehicle-level test |
| Evidence reference | The document number of the report or record, filled in as the project runs |
The deviation list carries only the rows that are not fully compliant, with the reason and what is offered instead. In rail component offers the same subjects come up again and again.
- Mass and envelope: the offered unit is heavier or larger than the allowance in the interface document.
- Fire: a material has reports to a lower hazard level than the one specified, or the reports are older than the customer accepts.
- Reliability and life: the specified failure rate or design life is tighter than the supplier's service data supports.
- Type tests: the supplier offers existing reports from a similar product in place of new tests.
- Standards editions: the product was qualified to an earlier edition than the one the specification cites.
- Welding: the classification level or the inspection extent the customer wants is higher than the supplier's certificate or standard practice.
- Documents: the delivery dates for RAMS and design documents do not fit the supplier's design programme.
A row marked compliant is a promise to produce evidence
Each compliant row with a type test as its verification method is a test someone must run and report. Count them before the offer goes out. The cost and the programme of the qualification campaign follow from the verification column, not from the status column.
Free layouts are on the compliance matrix template and requirements traceability matrix template pages. The glossary explains how a requirements traceability matrix differs from a compliance matrix.
Which documents follow after award?
After the order, the verification column turns into a list of evidence. The contract and the customer's document list decide what is due and when. A component maker should expect most of the following.
| Document | What the customer looks for |
|---|---|
| First article inspection report | The first unit made with series tooling and processes, checked characteristic by characteristic against the approved drawings and specification, with open points listed and closed |
| Type test reports | The item tested and its build standard, the specification and edition, the laboratory, the date and each result. See type test vs routine test |
| Routine test reports | One record per serial number, with every test in the agreed routine test list present |
| Welding certificate and welder qualifications | The EN 15085-2 certificate for each site that welds, with its level and scope, and the procedure and welder qualification records behind the welds |
| Weld inspection records | Visual and non-destructive test reports to the inspection class marked on the drawing |
| Fire test reports for materials | A report for each non-metallic material from a laboratory the customer accepts, showing the requirement set, the hazard level reached and the tested thickness or build-up |
| RAMS deliverables | The agreed plan, analyses and data, each at the milestone the contract sets. The EN 50126 page lists typical requests |
| Material certificates and declarations | Inspection certificates for structural materials and a certificate of conformance with each delivery |
| Manuals and spare parts data | Operation and maintenance instructions, a spare parts catalogue and maintenance task data |
| Documentation dossier | All of the above in the customer's index order, at the approved revision, per product or per serial number as the contract says |
Welding records are the part of the dossier that most often arrives incomplete. A list of what to gather is on the rail welding documentation checklist template page.
How does OdysseyGPT help?
OdysseyGPT reads the documents you upload and checks them against the customer's written requirements. Every finding shows the passage it rests on in both documents, so an engineer can confirm it in seconds. Document Review takes the technical specification or the exported requirement list as the base and your technical description, quality plan, test plans and certificates as the documents to check. It works in both directions and exports an editable compliance matrix with a deviations and clarifications list. The other tools each read a narrower set of records.
| Your document | Tool | What it reports |
|---|---|---|
| Technical specification or requirement list export, and your offer documents | Document Review | A status and a pair of quotes for each requirement, plus statements in your documents the customer's text does not cover |
| Technical specification, interface documents and supplier quality requirements | Customer Specification Review (beta) | A requirements register: one line per obligation, typed and tied to its clause, including the ones in the general supplier document |
| Offer, clarification replies and the agreed deviations | Deviation Register (beta) | One running record of each deviation from offer to the customer's decision |
| The customer's list of documents to be delivered | VDRL/MDR Tracker (beta) | A register of each deliverable with its due-date rule, revision and status, and overdue items flagged |
| Material inspection certificates for structural parts | Material Certificate Review (beta) | Each certificate checked against the order and material specification for grade, heat number, properties and certificate type |
| Welding procedures, procedure qualification records, welder qualifications and the weld list | Welding Qualification Review (beta) | Welds whose procedure or welder qualification does not cover them, or was not valid on the production date |
| Weld list and non-destructive test reports | NDE Coverage Review (beta) | Welds that need testing and have no report, or a report that covers less than the requirement states |
| Your inspection and test plan and the customer's quality clauses | ITP Validator (beta) | Inspections and tests the customer asks for that the plan omits, and witness points that do not match |
| Test procedure, approved documents and open items before a witnessed test | FAT Readiness Check (beta) | Whether the documents a witnessed test depends on are in place before the customer travels |
| Dossier folder and the customer's dossier index | MRB Readiness Check (beta) and MRB Compiler (beta) | Records that are missing, unapproved or at the wrong revision, and a manifest in index order |
Fire test reports, EN 15085 certificates and RAMS documents have no tool of their own. Document Review can read them as documents and compare what they state with what the customer asks for: the hazard level on a report, the level and expiry date on a certificate, the list of analyses in a RAMS plan. It does not judge the engineering behind them. The tools are grouped by stage under tender, manufacturing, inspection and handover.
What does a result look like?
The table below is an invented example. The train builder, the vehicle, the requirement identifiers, the supplier's documents and every figure are made up to show how a result is laid out. Nothing in it comes from a real specification, a real supplier or a standard.
| Customer requirement (quoted) | Maker's document (quoted) | Status | Note |
|---|---|---|---|
| "The unit shall deliver a cooling capacity of not less than 32 kW at the design conditions of Table 4." (REQ-HVAC-0112) | "Rated cooling capacity: 34 kW at the customer design conditions." (Technical description TD-88, p. 9) | Complies | Capacity offered is above the minimum, on the same stated conditions. |
| "All non-metallic materials shall meet EN 45545-2 for hazard level HL3." (REQ-HVAC-0240) | "Materials are selected and tested to EN 45545-2, hazard level HL2." (Technical description TD-88, p. 21) | Deviates | The offer states a lower hazard level than the specification. |
| "Fire test reports shall be issued by an accredited laboratory and shall be no more than five years old at delivery." (REQ-HVAC-0243) | "Fire test reports for all materials are listed in Annex F." (Technical description TD-88, p. 22) | Clarification | Annex F gives report numbers. It gives no dates and does not name the laboratories. |
| "Welded parts of the unit frame shall be made by a welding manufacturer certified to EN 15085-2, classification level CL 1." (REQ-HVAC-0301) | "The frame is fabricated by our certified welding sub-supplier." (Quality plan QP-HV-03, p. 5) | Clarification | The supplier's text names no standard, level or certificate scope. |
| "The Supplier shall deliver a reliability prediction and an FMECA four weeks before the preliminary design review." (REQ-HVAC-0410) | "RAMS analyses are issued at the final design review." (Project schedule PS-12, line 31) | Deviates | The documents are offered one design review later than requested. |
| "The mean distance between service-affecting failures of the unit shall be not less than 400 000 km." (REQ-HVAC-0415) | No matching statement found in the documents supplied. | Not addressed | No reliability figure is offered. Add one or declare the gap. |
| "The control unit shall be type tested to EN 50155:2021 and the reports submitted." (REQ-HVAC-0522) | "Controller type tested to EN 50155:2017, report TR-5521." (List of type test reports, item 6) | Clarification | The report is to an earlier edition than the one cited. Ask whether it is accepted. |
| "A first article inspection shall be held at the Supplier's works. Twenty working days' notice shall be given." (Supplier quality requirements 7.3) | "First article inspection is performed on the first series unit. Notice to the customer: 10 working days." (Quality plan QP-HV-03, p. 8) | Deviates | The notice period offered is shorter than the customer's general requirement. |
| "Each unit shall pass a routine test comprising a refrigerant leak test and a functional test. A report shall accompany each unit." (REQ-HVAC-0601) | "Every unit is routine tested: leak test, electrical safety test and functional test. A report is issued per serial number." (Routine test procedure RT-07, p. 2) | Complies | Both named tests are in the procedure and a report is issued for each unit. |
A bid engineer opens the two quotes on each row and keeps or changes the status. Rows left as deviates go to the deviation list. Rows left as clarification become questions to the customer or tasks for the supplier's own team, such as finding the dates of the fire reports.
Where OdysseyGPT falls short
- It performs no RAMS analysis. It does not calculate a failure rate, build an FMECA or a fault tree, apportion targets or assess a hazard. It can show whether a document you wrote states what the customer asked for.
- It is not a requirements management system. It does not replace DOORS, Polarion or a similar tool, it holds no baselines or links between requirement levels, and it does not connect to the customer's tool. You export the requirement list to a file and upload that.
- It does not read drawings. A weld performance class, an inspection class, a fixing point or an envelope dimension that appears only on a drawing is not checked.
- It certifies nothing. It does not issue or validate an IRIS or EN 15085 certificate, and it does not confirm a certificate against the certification body's register. It reads the text of the copy you upload.
- It does not judge fire performance, structural strength or electromagnetic compatibility. It compares what a report states with what the specification asks for.
- It holds no standards. A limit that sits only inside EN 45545, EN 50155 or another paid standard is checked only if you upload a licensed copy of the edition and its text is readable.
- It can match a requirement to the wrong passage or miss one, most often in long requirement lists with near-identical lines. The quotes are shown so that a person can catch this.
- Tools that carry a beta marker on this page are available on request, and we set each team up ourselves.
Talk through your tender review
See how OdysseyGPT reviews a tender
Tell us how your team reviews tenders today. We can walk through an example together.
