Content
What are the Key Activities that require Joint User Involvement ?
The Key activities which require Joint User involvement are as follows:
- Inputs to high level defence planning, providing their views on current joint capabilities, joint advice across capabilities, Lessons Identified and coherency with commitment area activities to:
- Defence Planning Assumptions (DPAs)
- Future Capabilities Development (FCD).
- Inputs to the Planning Round
- Capability Audits - provides advice on joint programmes, inter-service Capability Integration, assumptions on the joint force composition and priorities.
- Joint Operational Priorities List (JOPL). The JOPL provides guidance to the Capability Sponsor and Resource and Plans (RPs) communities on the capability priorities from the Joint User point of view. Inputs are accepted and ordered by importance in line with Defence Support Group guidance and Lessons Identified from:
- Chief of Defence Intelligence (CDI)
- Special Forces (SF)
- Policy and Commitments
- Assistant Chief of the Defence Staff (Logistics Operations) (ACDS(Log Ops))
- Single Service RPs and DCI(A) in the Centre
- The Front Line Commands
- Warfare centres
- Joint formations
- Permanent Joint Headquarters (PJHQ).
- Deputy Chief of Defence Staff (Commitments) (DCDS(C)) and Chief of Joint Operations develop and agree their Joint priorities. They publish the JOPL ahead of the Joint Capabilities Board (JCB) issuing their strategic guidance. The JOPL is used help the Options generation process and to assess the Heads of Capability (HoCs) priorities.
- Capability Investigations and Short Term Planning (STP) Review Year Work - The designated User will provide a view on the capability requirements, impacts and the alternative Joint force mix options. They will ask the Joint User to mediate, where necessary, to resolve structural issues and ensure that coherence is maintained with the endorsed Applied Concepts and wider Defence Support Group requirements.
- Candidate Options Preparation. From the full list presented by the RPs and HoCs, ACDS(RP) and the JCB will down-select the most promising Candidate Options for detailed costing. The Joint User provides advice and guidance to the HoCs on the Joint operational aspects of the impact statements. Should further options to meet savings targets or implement FCD enhancement guidance, outside the Investigation Options, be required, this activity will be co-ordinated by the relevant Capability Working Group (CWG) supported by the Joint User.
- Decision Conferences (DCs). At the HoC level DCs, Candidate Equipment Plan (EP) Options are prioritised into a recommended HoC Order-Of-Buy (OOB). These OOBs are then amalgamated and the resultant model reviewed by the JCB at its DCOOB. Joint User support to HoC DCs is provided through the CMG organisation.
- Extended JCB. The Capability Sponsor OOB forms the basis of the EP submission which is endorsed by the Extended JCB. DCDS(C) and CJO will represent the Joint User view on priorities.
- Programms and Policy Steering Group. ACDS(Ops) will represent the Joint User community advising on Joint priorities, including those in the Non Equipment Investment Process, and the balance of investment across the EP and STP.
- Defence Board. The Joint priorities are represented by VCDS.
- The Joint User role in the Urgent Operational Requirement (UOR) Process:
- Act as the Operations Secretariat Branch delegated ‘approving’ authority for all UOR Business Cases (BC).
- Prioritise UOR in conjunction with PJHQ.
- Conducts UOR Contingency Planning.
- Provides advice to the HoC on production of the BC.
- Represents the designated User view.
- Endorses BC - Concept of Operations.
- Arbitrates between conflicting priorities.
Change History
Change History
The 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.
- 1 November 2009
- Minor amendments made for Plain English review.
- 1 October 2007
- New content – User – Key activities requiring User involvement.
