AOF
Acquisition Operating Framework
The high level principles and information that guide how the UK MOD Defence Acquisition Community works
version 2.0.21 – March 2010
The high level principles and information that guide how the UK MOD Defence Acquisition Community works
version 2.0.21 – March 2010
Explorer
|
Content
The Division and Transfer of Responsibilities between Sponsor and UserThroughout the Acquisition Lifecycle, the balance of effort and responsibilities between the Sponsor and User varies according to the lead issue at the time. Transfer of LeadBefore the In-Service Date (ISD), the Capability Sponsor is responsible for analysing, stating, planning for, managing and accepting the required capabilities. They draw on the advice, skills and experience of the User community, ensuring their involvement in the Through Life Management (TLM) of the project from the outset. Around ISD, there is a shift of lead status from the Capability Sponsor to the designated User. There are a number of factors that will influence when it is best (if ever) to transfer that lead status. Where a capability is being acquired through incremental acquisition:
The Capability Sponsor, when the lead is passed to the User, takes on the maintaining role, making sure the capability is kept up to date. They achieve this through technology inserts, mid-life updates or life extensions. At these times the lead status passes back to the Capability Sponsor. As such during the life of a capability the lead status moves between the two roles, Capability Sponsor and the User as the need arises. Division of Responsibilities by Phase:ConceptDuring the Concept phase up to Initial Gate, thinking focuses on capability rather than on a specific equipment solution. As a result many programmes are likely to have a designated User from the Joint User community. The role of the designated User in this phase is to:
AssessmentDuring the Assessment phase and up to Main Gate the outline System Requirements Document (SRD) is produced by the Defence Equipment and Support (DE&S) Team drawing from and linked to the URD. The balance of effort between the Capability Sponsor and User is likely to remain the same throughout this phase. During this phase the designated User will:
DemonstrationA single prime contractor is normally selected during the Demonstration phase. The designated User is responsible for evolving the CONEMP into a Concept of Use (CONUSE) during this phase. They will keep it updated as the design evolves and assumptions change but the decision of when to transfer to a CONUSE will depend upon the programme. However, the transition must occur ahead of ISD. During this phase the Heads of Equipment Capability (HoCS) will seek advice from the designated User to confirm that the proposed solution produces an integrated capability that takes account of:
A key activity during this phase is the refinement of estimates for the introduction of the new capability and their impact on the Short Term Plan. This work should be started early in the phase and involve the designated User, to help populate the COO information within the TLMP. Help refining cost estimates can be sought from DE&S Cost Analysis and Assurance Services Team. ManufactureDuring the Manufacture phase the equipment solution is delivered to meet the requirement within performance, time and cost parameters. The User involvement increases with the first delivery of equipment. The User ensures the integration of the non-equipment DLoD to support the delivery of an overall capability; this may require a dedicated Capability Integration Working Group (CIWG). Under the direction of the Programme Board the Integrated Test, Evaluation and Assessment Plan (ITEAP) is finalised and held within the TLMP. User budgets will start to incur costs associated with the new equipment as the first elements of deployable capability, and the associated development costs, are transferred to their balance sheets. The capital assets will, in future, transfer for accounting purposes to a central budget. With the increased use of Incremental Acquisition which allows the staged delivery of the capability there needs to be clarity of role between the HoCs and designated User between IOC and FOC. This can be achieved through the use of Joint Business Agreements (JBAs) or Customer Supplier Agreements (CSAs). In-ServiceWhen in service, the designated User will take on the Lead customer status and deal directly with the Team who is responsible for supporting their needs through the agreed levels of availability and sustainability in the JBAs or CSAs. The User is responsible for providing updated information, when known, to Teams, so that they are able to meet their mandate of maintaining fully costed TLMPs for their equipment. Although not the Lead in this phase the Capability Sponsor is responsible for addressing deficiencies in equipment capability when in service. When this occurs the Lead may move back to the Capability Sponsor, until the update has taken place. Upgrades must be initiated by the Capability Sponsor and funded from the Equipment Plan (EP). Although updates to address obsolescence or safety issues are usually be initiated by the relevant Team in conjunction with the designated User, funded from the Equipment Support Plan (ESP) and Short Term Plan (STP). Major Mid-Life Improvements (MLIs) need to be considered across all DLoDs. Where the capability is changed the CONUSE needs to be updated to reflect the changes. DisposalDuring the Disposal phase, the designated User is responsible for the equipment until it is no longer operationally useful. Assisted by the designated User, the relevant Team:
The Defence Logistics Support Chain Manual - Joint Service Publication 886 - Volume 9 – The Disposal of Material The TLMP should be used to demonstrate Project Evaluation (PE) / Learning from Experience (LFE) for future capabilities of similar nature, during Capability Identification (Stage 1).
Contacts
UserOwner
Point of Contact
Change History
Change HistoryThe AOF has been updated to Version 2.0.0 on 1st April 2008 following the introduction of the main content in the tactical layer. In addition small changes have been added to the Operational layer. Individual document Change History pages will detail any changes other than minor editorial amendments.
|
