Content
Governing Policy (GP) 1.1 - Logistics Readiness and Sustainability Requirements
Scope
Logistic Readiness and Sustainability Requirements provides a mechanism for project teams to assess and gain assurance that their support solutions are consistent with MOD policy and User needs around the Operational Planning Cycle. It also provides for Logistics Operational Assurance (LOA).
This scope is expanded into greater detail below under the heading ‘Supporting Information’.
Applicability
Assurance against Logistics Readiness and Support requirements is applicable to all projects that require to be supported and sustained irrespective of whether deployed outside the UK home base or not. Further clarification to the applicability or otherwise of this Governing Policy (GP) can be found in the tailoring guide.
Underpinning Policy
- JSP 899 – Logistics Process Roles and Responsibilities
.
- JSP 902 – Defence Logistics Sustainability
.
- Defence Strategic Guidance (DSG) (available from Directorate of Policy Planning Tel: +44 (0) 207 218 7743).
- Defence Programme Directory (available from Directorate of Defence Requirements and Plans Tel: +44 (0) 207 218 5717).
- Land Environment Sustainability Planning Assumptions (LESPAs), (available from DCI (A)-SO2 SPC1 Tel: +44 (0) 207 218 6889), SO2 Log Pol +44 (0) 207 218 7383).
- Naval Data book Issue 9 (available from DNRP-Plans Tel: +44 (0) 207 218 7404).
- Provisional Joint Logistic Sustainability Planning Assumptions (pJLSPAs), (available from D Def Log Ops Tel: +44 (0) 207 807 8598).
- RAF Management Plan Part 2 (available from DGRP D AIR RP-MPa Tel: +44 (0) 207 218 0077).
- The ‘Force Elements at Sustainability’ (FE@S) Metric (available from DGRP D RP Centre – 2 Maritime1 Tel: +44 (0) 207 218 3503).
Compliance Tool - Evidence Requirements
The Evidence Requirements for this GP can be found within the Compliance Tool.
The adopted Support Solution is to provide specific evidence in order to achieve compliance with the needs of this GP.
Variations from this evidence set may be possible and should be discussed with the Subject Matter Experts (SME) and the relevant Support Solutions Officer (SSO) at the earliest opportunity in order that risks (if any) and mitigation are clearly agreed and articulated in the Compliance Tool.
The adopted Support Solution is to meet the Front Line Command’s (FLC) Force Elements at Readiness (FE@R) requirements, as derived from the Departmental Plan, and be articulated in Joint Business Agreements (JBA).
The Support Solution is also to have fully engaged with the FE@S process to assess logistic sustainability against the requirements of the Defence Planning Assumptions (DPA) Concurrency Sets in DSG. Failure to comply could result in the FLC bearing an increased operational risk or unidentified costs once the equipment is in-service.
In order to assist with the development of evidence requirements please refer to the Evidence Requirements Guide (ERG) [26KB PDF]. The domain specific SME will be able to discuss this with the Project Team point of contact and will also have to hand a worked example (the worked example, due to its security classification, is not held on the Acquisition Operating Framework (AOF).
The ERG and worked example are designed to take the Project Team through the process from Initial Gate (IG) through Main Gate (MG) to Logistics Support Date (LSD) and ultimately In-Service Review (ISR), and are therefore to be used in conjunction with the compliance tool.
Supporting Information
The majority of this information is drawn from JSP 902 – Defence Logistics Sustainability
and is offered as background to this GP accordingly.
Logistics sustainability is about ensuring sufficient combat supplies, spares and consumables are available to Force Elements (FE) in a timely manner to meet extant Defence requirements. It should recognise that this does not just mean supporting operations; it includes support for standing Military Tasks (MTs), FE@R, and Contingent Operation Concurrency Sets detailed in DSG.
Force Elements at Readiness (FE@R) and Sustainability (FE@S)
- FE@R is an expression of military capability and is a Defence output.
- A FE can equate in the Land Environment to a sub unit, unit or formation, in the Maritime Environment to a ship or task force and in the Air Environment to an airframe or collection of airframes, which requires to be held at certain readiness levels.
- To be at immediate readiness, a FE must be fully trained and have all the stocks it needs to deploy available to it.
- FE not at immediate readiness will be held at various stages of preparation commensurate with their readiness level.
- Stocks required to support each FE should be identified and held at the same readiness as the FE.
- A FE at immediate readiness should have all its deployment stocks identified.
- A FE at low readiness does not need its stocks ready to deploy until such time as its warning time is reduced.
- FE@S is a measurement of sustainability for a given FE against a contingent operation.
- It is used to articulate sustainability in capability terms and sets targets in JBAs with the DE&S.
- FE@S is a top level, not an operational level, planning tool which aims to identify and have funded the stock that is required to enable a FE to be sustained within a contingent operation over a 180 day period.
Support to Standing MTs and the Operational Planning Cycle
Standing MTs - All 3 FLCs provide FEs to support Standing MTs on a daily basis and are assigned to these tasks in accordance with differing Single Service Procedures. Consequently, FLCs identify their requirements for each of the Standing MTs to which they contribute and ensure that this level of Logistics sustainability is articulated within their JBA with DE&S.
The Operational Planning Cycle – DSG 08 identifies an operational logistics cycle, which supports the operational planning cycle and consists of the following three areas:
- Logistics Readiness - The activity and resources required to train and maintain Force Elements (FE) at the Readiness state (FE@Rx) mandated by the Departmental Plan and that are required to generate these FE from Rx to R0 (where R0 is ready to deploy).
- When this logistics sustainability requirement is overlaid on the operational planning cycle (as detailed at Figure 3.4 below) it occupies the space between 12 o’clock and 5 o’clock.
- Sustainability Statement - The activity and the resources required to sustain those FE from R0 through deployment, in-theatre training and preparation, operations and redeployment / recovery.
- This is the in-theatre element of Logistics sustainability that is detailed in the Sustainability Statement (SUSTAT) for a given operation.
- It occupies the space between 5 ’oclock and 10 o’clock.
- Logistics Recuperation - The activity and resources required to recuperate the force structure following its use. It is the activity to return FE@Rx mandated by the Departmental Plan.
- It occupies the space between 10 o’clock and 12 o’clock.
Figure 3.4 - Logistics Sustainability around the Operational Planning Cycle
Logistics Operational Assurance – Assistant Chief of Defence Staff (Logistics Operations) (ACDS Log Ops), through the Logistics Operational Assurance (LOA) Team, provides a pan-Defence Logistic operational assurance function addressing both logistic risks and issues concerned with support to current and contingent operations.
LOA therefore has a role to play against GP1.1, notably in-service, to which the In-Service Review (ISR) element of the Compliance Tool takes due cognisance.
LOA policy is promulgated through the Defence Logistics Operational Assurance Handbook JSP 568
, and is made up of three integrated Work Strands:
- LOA in the FLCs
- Defence Logistics Risk Management
- Logistics Sustainability Assurance (LSA).
Project team outputs must be compliant with, or cognisant of:
- The LOA process in the FLCs which provides an evidence based view of Logistics Risks and Issues (R&Is) providing a common understanding for the MOD Unified Customer (MUC).
- This understanding, in turn, provides a critical decision support capability to improve E2E Logistics effectiveness and assist in making better informed Defence Logistics resource and planning decisions.
- This process is operated by the LOA Environmental Teams embedded within the FLCs.
- Data is sourced from a variety of other stakeholders including Customer Support Teams within Defence Equipment and Support (DE&S) and the Commitments area of Director Defence Logistics Operations (D Def Log Ops).
- The Defence Logistics Risk Management process which enables cross-cutting Logistic Risks and Issues across all environments to be reflected through the Defence Logistics Steering Group (DLSG) for DLB action.
- The LSA process which is the primary mechanism for analysing that the Force Elements at Sustainability (FE@S) requirements for FEs are being met.
For further details see JSP 568
.
Sponsoring Authority
The sponsoring authority for this GP is:
- ACDS(Log Ops) Hd Def Log Pol
General questions relating to the content of this Governing Policy should be directed to:
Subject Matter Experts (SME)
For all aspects of this KSA the initial POC is the SIT Lead.
On completion of tailoring, the following may be contacted for specialist advice.
GP1.1 SMEs are only authorised for this role by the KSA1 Owner’s Rep through a formal Induction Programme, held locally by the KSA1 Owner’s Rep.
| Title |
Scope |
Phone / Email |
| Maritime |
|
| Maritime |
|
| Land |
|
| Air - Fixed Wing |
|
| Air - Rotary Wing |
|
D ISS Gapped (Withdrawn initially through DE&S strategic resource rebalancing) – now under review |
|
Change History
Change History
Due to the significant number of changes contained within the SSE Version 5 update, ‘Change History’ will only reflect those amendments, inclusions or deletions which follow the launch of the website on 1st November 2008.
The SSE updated to Version 5.0.0 on 1st November 2008 following a full review of all documents and changes to a number of GPs. Individual document Change History pages will detail changes other than minor editorial amendments.
- 1 August 2010
- Removal of ‘Support Solution Assurance Guidance’ paragraph.
- Minor text change.
- 1 July 2010
- Minor text amendments.
- Sponsor details changed.
- SME details changed.
- 1 June 2010
- Heading amended.
- Content revised and updated.
- 1 April 2010
- Text changed to reflect that support assurance policy and guidance is now incorporated into JSP 899.
- SME details updated for CST (Fleet) Ops SO2.
- SME details deleted for CST (Land) SO2 Sustainment.
- 1 December 2009
- Hyperlink to JSP 899 inserted.
- 1 November 2009
- Contact details changed.
- Underpinning Policy changed.
- 1 October 2009
- Subject Matter Experts - New paragraph added.
- 1 August 2009
- SME email address deleted for gapped post.
- 1 July 2009
- Contact details changed.
- Support Solution Assurance Guidance paragraph added.
- 1 May 2009
- Minor text changes.
- ‘Support Improvement Team Officer’ changed to ‘Support Solutions Officer’.
- ‘IPT’ changed to ‘project team’.
- 1 April 2009
- ‘Engagement’ changed to ‘Support Improvement’.
- ‘General’ removed from the title ‘Director General’.
- 1 March 2009
- SME Contact details amended.
- 1 December 2008
- Contact details amended.
- 1 November 2008
- Major update.