A source-grounded answer set for warranty, maintenance, repair, replacement parts, calibration, software updates, and technical support. It is review material—not approved contract language, a final service level, or a price.
The requirements baseline calls for at least three years of technical support, updates, replacement parts, warranty details, a support plan, and service agreements. This does not establish a three-year full hardware warranty. [RFP p15–16]
The response must address initial performance certification, ongoing calibration needs, validation against final requirements, configuration control, updates, and maintaining fidelity through the system life. [RFP p15] [ADD3 p10 A28]
The price schedule must identify basic warranty and extended warranty separately, alongside hardware and other required pricing categories. Addendum 3 does not approve a warranty duration. [ADD3 p9 A26]
ForgeFX should define a basic system warranty separately from the three-year technical-support framework and any optional extended warranty. The final warranty schedule will name covered hardware and software, the coverage start event, defect-correction process, exclusions, manufacturer pass-through coverage, labor, shipping, and onsite-replacement responsibilities.
Do not promise yet: the July 14 discussion of a one-year hardware warranty with paid parts and labor afterward is internal direction only, not an approved commitment.
[RFP A1.4, A1.6] [ADD3 p9 A26] [MTG-04 01KX6YJ4WCDX95YEV21CMPRZV7]ForgeFX should provide a scheduled maintenance framework that separates preventive maintenance, corrective maintenance for accepted deliverables, and enhancement work. The final schedule should name the remote/onsite split, hardware inspection, backups, documentation revisions, software/platform maintenance, exclusions, annual allowance, and renewal terms.
Do not promise yet: no maintenance cadence, included annual hours, travel allowance, after-hours coverage, or price has been approved.
[RFP A1.4, A1.6] [ADD3 p10 A28] [MTG-05 01KXGS05C2EWVQ75W3K0TPCXSZ]ForgeFX should use a defined diagnosis, repair, and replacement workflow. Remote diagnosis and triage should identify whether a failure belongs to a ForgeFX-integrated assembly, a ForgeFX-fabricated component, or manufacturer-warranted commercial equipment. A hardware responsibility matrix should name who handles parts, labor, shipping, return authorization, field service, and escalation for each component.
Do not promise yet: open-ended onsite repair, 24/7 response, freight exposure, or manufacturer obligations must not be absorbed into the development price.
[RFP A1.4, A1.6] [MTG-02 01KWWFVS2HGQJY9H8B48K3PJR9] [MTG-04 01KX6YJ4WCDX95YEV21CMPRZV7]ForgeFX should deliver a recommended spare-parts list tied to the approved bill of materials. It should distinguish commissioning spares, warranty replacements, consumables, manufacturer-replaceable items, and optional onsite stock. The final plan should state quantities, ownership, lead times, storage, replenishment, obsolescence, shipping, and replacement labor.
Do not promise yet: no spare kit, quantity, stocked inventory, replenishment SLA, or included parts allowance has been approved.
[RFP A1.4] [ADD3 p9 A26] [MTG-02 01KWWFVS2HGQJY9H8B48K3PJR9]ForgeFX should establish an initial performance baseline during integration and commissioning against approved control, display, audio, timing, vehicle-response, and visual-system tolerances. The handoff should include the calibration procedure, required tools, baseline results, responsible roles, recommended recurrence or event-based triggers, and a calibration record.
Do not promise yet: the standards, tolerances, instruments, certification wording, recurring interval, onsite requirement, and post-warranty price remain open.
[RFP A1.5] [ADD3 p10 A28] [MTG-02 01KWWFVS2HGQJY9H8B48K3PJR9]ForgeFX should separate defect correction for accepted deliverables from enhancements and scope changes. Approved bug fixes and agreed security/dependency maintenance may be handled under the final warranty/support terms. New routes, rules, reports, integrations, content, operating-system or vendor-platform changes, and fidelity changes should use the approved maintenance allowance or change-control process.
Do not promise yet: annual update hours, release frequency, supported platform window, maintenance windows, cybersecurity obligations, and change-order rates remain open.
[RFP A1.4] [ADD3 p10 A28] [MTG-01 01KT6YHDGSBQ9W11C7YABCVHA1] [MTG-02 01KWWFVS2HGQJY9H8B48K3PJR9]| Topic | Decision | Owner / input | Cost-table effect |
|---|---|---|---|
| Support | Hours, severity levels, response/restoration targets, remote access, onsite and after-hours terms, annual allowance, renewals. | Mary / Adam / River / Greg | Three-year support line plus renewal options. |
| Warranty | Basic and extended durations, start event, covered items, exclusions, pass-through coverage, labor, travel, shipping. | Mary / River / Greg / Dave | Separate basic and extended warranty lines. |
| Repair | Responsibility per hardware component; remote, depot, and onsite workflows; service provider and geography. | Adam / Dave / River | Labor, travel, freight, partner/vendor exposure. |
| Replacement parts | Final BOM, included spare kit, quantities, stocking, replenishment, lead times, ownership, obsolescence. | Adam / Dave / River / Mary | Initial spares and post-warranty parts allowances. |
| Calibration | Objects, tolerances, tools, responsible party, recurrence/triggers, onsite days, records, certification wording. | Adam / Dave / River / Mary | Initial calibration plus recurring/per-event service. |
| Updates & maintenance | Included corrections and releases, annual update budget, compatibility window, maintenance cadence, change-control boundary. | Mary / Adam / River | Annual maintenance line and separately priced enhancements. |
Translate the approved service boundaries into explicit hardware, testing, installation, spares, basic warranty, extended warranty, technical support, calibration, maintenance, travel, and contingency lines.
Select and edit the approved answer language for the proposal/deck. Do not use these drafts as final commitments until the commercial and operational decisions above are closed.
Metro-Rail-Requirements.html, A1.4–A1.6 — minimum three-year support package, updates, parts, warranty detail, performance certification, calibration, support plan, and service agreements. Source links point to RFP pages 15–16.client-docs/raw/addenda/10205113a3.pdf, SHA-256 CA284F00B494BF2E88C612301A39250D8AAD8E2963C5DC0726B60932BA0F068B. Page 9 A26 requires distinct warranty price treatment; page 10 A28 addresses validation, calibration, updates, configuration control, and ongoing fidelity.01KT6YHDGSBQ9W11C7YABCVHA1 — client suggested showing software-update ability for future extensions; no commercial term was approved.01KWWFVS2HGQJY9H8B48K3PJR9 — Mary asked how updates, repairs, replacement parts, warranty, and ongoing calibration would be handled; Adam accepted the answer-prep action.01KX1G8D4W9JYFKJKNBWQX4AFG — pricing/scope context; it does not close a warranty, maintenance, repair, replacement, calibration, or update commitment.01KX6YJ4WCDX95YEV21CMPRZV7 — internal discussion proposed a one-year hardware warranty and paid parts/labor afterward. This remains unapproved working direction.01KXGS05C2EWVQ75W3K0TPCXSZ — Adam was assigned detailed pricing lines; Mary was assigned warranty, maintenance, and technical-support narrative.outputs/dinner-prep/2026-07-16-addendum-3-text-pack.md, 2026-07-16-pricing-art-reconciliation.md, and 2026-07-16-compliance-gap-register.md. These are internal working analyses, not client originals.