A single 2015 Contracts Finder notice points to a narrow, technical question that still shapes AP1000 generic design assessment (GDA) deliverables: whether fault modelling submitted by the UK AP1000 vendor actually maps onto the reference design under review. [S1]
For specifying engineers, the notice flags a procurement-relevant dependency. Fault schedules, assumptions, and detection-and-analysis outputs are not generic line items; they are tied to a specific reactor design baseline. Buying the wrong scope, or buying it at the wrong design freeze, creates downstream rework in safety case documentation and in instrumentation procurement for detection and analysis apparatus. [S1]
What the notice actually covers
The record is a Contracts Finder notice dated 10 July 2015, titled 'The review of the applicability of submitted UK AP1000 design basis fault modelling to the GDA reference design'. The CPV description refers to detection and analysis apparatus, which is consistent with the type of instrumentation and analytical outputs associated with fault schedule work, though the notice itself does not enumerate specific instruments or quantities. [S1]
The procurement is geographically United Kingdom. No awarding body, supplier, award value, or framework reference is given in the evidence. That matters for specifiers: the document is a pointer to a scope of work, not a priced line item set. [S1]
Why applicability is the operative word
The title's focus on 'applicability' indicates that the deliverable is a review, not a fresh fault schedule. The buyer is asking whether an existing fault model, prepared by the UK AP1000 designer, holds up against the GDA reference design. For specifiers, this is a useful pattern: an applicability review is a gating step that determines whether downstream safety case and instrumentation scopes can proceed as drafted. [S1]
If the review concludes that submitted fault modelling does not map cleanly to the reference design, then detection and analysis apparatus requirements may need to be re-scoped. The CPV tagging in the notice is therefore a downstream signal, not the primary procurement object. [S1]
Implications for specifying engineers
Engineers drafting requirements for detection and analysis apparatus in an AP1000 context should anchor the specification to a named design baseline and require traceability from each instrument or analytical output back to a fault category. The 2015 notice demonstrates that the buyer expects a documented justification of why a given fault model applies to the design being assessed, and the same logic applies to instrumentation derived from that model. [S1]
Because the notice offers no excerpt and no quantities, any specifier using it as a reference should treat it as evidence of a review activity, not as evidence of specific equipment counts, dates of design freeze, or supplier identity. The only firm facts available are the title, the CPV term, the 2015 date, and the UK geography. [S1]
Primary notice: Contracts Finder.