MOD Crest
AOF Support Solutions Envelope

Policy, information and guidance on the Support Solution aspects of UK MOD Defence Acquisition

version 5.12.0 - August 2010

Content

Key Support Area 3 (KSA 3) – Introduction: Supply Chain Management

Responsibility

The Head of Supply Chain Management (SCM-Hd) is responsible for defining the scope and depth of Key Support Area 3 (KSA 3) content.

Responsibility for the content of KSA 3 and its underpinning policy in JSP 886External link to Ministry of Defence Intranet content - the Defence Logistic Support Chain Manual - is delegated to SO1 Supply Chain Development.

Project teams must engage with the appropriate SIT Support Solutions Officer (SSO).

The SSO provides project teams with an authoritative single point of contact (POC) for advice and guidance on all policy contained within KSA 3.

  • This provides customers with an integrated service from the outset of a project, working in conjunction with Governing Policy (GP) Sponsors and Subject Matter Experts (SMEs), particularly in cases where detailed technical knowledge needs to be applied.
  • This approach should ease the administrative burden on project teams and expedite progression of support solutions through the whole process, and through-life.

The SSO will:

  • Represent Director Joint Support Chain (D JSC) in his Functional Assuror roles.
  • Provide Through Life Assurance for GP 3.1 – Supply Chain Management.
  • Provide ‘focal point’ engagement for all KSA 3 GPs referring questions or issues that require deep technical expertise to the appropriate GP SME and where necessary, facilitating their attendance at Logistic Support meetings and working groups.
  • Direct project teams which KSA 3 GPs require assurance by tailoring the Support Solutions Envelope (SSE) Compliance Tool.
  • Advise project teams on all Supply Chain aspects of their support solution.
  • Identify and resolve KSA 3 non-compliance issues. Where they cannot be resolved, quantify the risk in terms of the impact on the operational effectiveness on the Front Line Command (FLC(s)) and / or the Supply Chain.
  • Before Initial Gate, Main Gate, Logistic Support Date and any In-service reviews, provide single POC ‘sign off’ by providing KSA 3 input for the Support Solution Statement and provide the D JSC assurance statement.

As early as possible in the development of the support solution project teams must seek advice and guidance on the application of KSA 3 GPs from the appropriate SSO POC detailed below.

In addition, project teams must engage as early as possible in the Concept Phase with:

  • SCM Inventory OptimisationExternal link to Ministry of Defence Intranet content in order that they can provide guidance on the creation of an inventory plan. See GP 3.3 for contact details.
  • The Partnering Support GroupExternal link to Ministry of Defence Intranet content; in order that they can be provided with guidance on the accounting options for which the project team have to deliver a value for money solution. See GP 3.5 for contact details.

Context

KSA 3 is based upon the JSC BlueprintExternal link to Ministry of Defence Intranet content (JSP 886 Volume 1 Part 2) which provides the framework upon which all Supply Chain Management (SCM) activity is based and describes the main SCM policy and processes that apply to all new, legacy and UOR equipment and Information System (IS) enabled projects.

It is important to note that the completion of KSA 3 contributes directly to the higher level assurance of the JSC element of the Defence Equipment and Support (DE&S) Assurance Plan.

The maintenance and operation of an efficient Supply Chain requires the integration of all activities associated with the two-way flow of materiel and relevant information from industry to the end-user in order to sustain military capability. It includes:

  • Provisioning
  • Receipting
  • Storage
  • Issue
  • Distribution
  • Return of repairable items as well as unwanted materiel.

As an End-to-End (E2E) activity, the SCM cuts across the boundaries of process owners. Its performance can have a significant effect on Defence outputs. Consequently, the creation and maintenance of an effective Supply Chain is a key enabler in the delivery of military capability and requires the robust application of appropriately endorsed policy.

As Logistics Process Owner, Chief of Defence Materiel (CDM) has tasked D JSC with the delivery of an effective and efficient Joint Support Chain including the ownership and development of relevant processes. As such, D JSC is responsible for the formulation, endorsement and ratification of underpinning JSC policy.

The benefits of fully complying with KSA 3 include:

  • Support to D JSC Functional Assurance.
  • The through life supportability of equipment / platforms / systems will be improved.
  • Contractors’ Supply chains (both physical and the associated information flows) will interface seamlessly with the JSC.
  • Units, bases and ships will operate the same supply chain whether they are in their home base, or deployed on operations or exercise.
  • Commanders will have a single view of the Supply Chain and be able to prioritise and if necessary, intervene in the flow of materiel to and from operations.
  • The logistic footprint will be reduced on operations.
  • Confidence in the JSC will be increased.

Contractor Logistic Support

Contractor Logistic Support (CLS) is recognised as an option for through life support that has developed an increased impetus under the Smart Acquisition initiative, and for which detailed guidance is available in Part 2 - Contractor Logistic Support of JSP 886 Volume 3External link to Ministry of Defence Intranet content.

There is however, a real danger that the accumulative risk that non-compliant, but individually approved, CLS support solutions will compromise the SCM’s ability to provide effective and coherent support to military operations.

As part of their consideration of CLS support solutions, project teams are required to ensure that contractor’s processes and IS, interface seamlessly with the JSC, and current and future Log IS are used for the management of base, in transit and deployed inventory.

CLS policy applies to aspects of the majority of SSE GPs across all of KSAs.

Governing Policies

Each KSA contains a number of support area topics called Governing Policies (GPs). These GPs identify specific, required MOD policy with which, unless specifically tailored out, a project team’s proposed support solution must comply.

Each GP consists of the following sections:

  • Scope – The requirement for the policy, including the benefits it brings to the MOD and project teams.
  • Applicability – A single paragraph outlining which types of project the GP will apply to.
  • Underpinning Policy – The title of the documents that underpin the compliance tests within the GP.
  • Compliance Tool – Evidence Requirements – Evidence requirements (that must stem directly from the underlying policy document) are contained within the SSE Compliance Tool and must be measurable, consistent and objective.
  • Supporting Information – Hyperlinks to relevant references and supporting information that will assist projects in achieving compliance
  • Sponsoring Authority – Title and contact details of the sponsor of the GP.
  • Subject Matter Experts (SME) – A list of those nominated personnel who are qualified, responsible and resourced for providing authoritative advice and guidance for Ensurance and Assurance activity to the project team, KSA Owner’s representative and Support Improvement Team.

Points of Contact

KSA Owners representative

Title Scope Phone / Email
Supply Chain Policy Development KSA 3 Owner POC

For all aspects of this KSA the initial POC is the SIT Lead.

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 changes.
Point of Contact details changed.
1 April 2010
Text changed to reflect that support assurance policy and guidance is now incorporated into JSP 899.
Points of Contact details updated.
1 February 2010
Points of Contact telephone number changed.
1 December 2009
Email address changed.
1 October 2009
Email address changed.
1 September 2009
Change of name from ‘Joint Supply Chain’ to ‘Supply Chain Management’ and associated text changes.
1 July 2009
Minor text changes.
Support Solution Assurance Guidance paragraph added.
POC details amended.
1 June 2009
Minor text changes.
1 May 2009
Minor text changes.
‘Support Improvement Team Officer’ changed to ‘Support Solutions Officer’.
IPT’ changed to ‘project team’.
Hyperlinks added.
1 April 2009
Title amended.
Reference to ownership by ACDS (Log Ops) deleted.
JSP 886 Hyperlink added.
Hyperlink updated.
‘General’ removed from the title ‘Director General’.
References to SCS Sp Solns replaced by SIT.
SME details updated.
Change of Paragraph heading from ‘Ownership’ to ‘Responsibility’.
1 November 2008
Major update.