Explorer

• What's New
• Introduction
  • Overview
  • Use of the SSE
  • SSE Compliance Process
  • Key Roles and Responsibilities
  • SSE Points of Contact
  • SSE Introductory Presentation
  • Frequently Asked Questions
• Resources
  • Resource Overview
  • Compliance Tools
  • Tailoring Guide
  • Glossary
  • Archived Version of SSE
• Key Support Areas and Governing Policies
  • KSA 1 – Logistics Readiness and Sustainability
    • KSA 1 – Introduction
    • GP 1.1 – Logistics Readiness and Sustainability Requirements
    • GP 1.2 – Contractors on Deployed Operations (CONDO)
    • GP 1.3 – Support Continuity
    • GP 1.4 – Deleted
  • KSA 2 - Supportability Engineering
    • KSA 2 – Introduction
    • GP 2.1 – ILS Process and Support Solution Development
    • GP 2.2 – Reliability
    • GP 2.3 – Obsolescence Management
    • GP 2.4 – Automatic Test Systems and Test and Measurement Equipment
    • GP 2.5 – Configuration Management of Defence Materiel
    • GP 2.6 – Technical Documentation
    • GP 2.7 – Disposal
    • GP 2.8 – Training and Training Equipment
    • GP 2.9 – Manpower and Human Factors Integration
  • KSA 3 - Supply Chain Management
    • KSA 3 – Introduction
    • GP 3.1 – Supply Chain Management
    • GP 3.2 – Codification and Item Ownership
    • GP 3.3 – Inventory Planning
    • GP 3.4 – Packaging and Labelling
    • GP 3.5 – Materiel and Financial Accounting
    • GP 3.6 – Fuels, Lubricants and Industrial Gases
    • GP 3.7 – Equipment Transportability
  • KSA 4 - Logistic Information
    • KSA 4 – Introduction
    • GP 4.1 – Logistics Information Requirements Planning
    • GP 4.2 – Information Systems and Services Requirements Planning
• GPs Amendment or Development
  • Overview

Content

Support Solutions Envelope (SSE) Frequently Asked Questions

What is a Governing Policy?

Each Key Support Area (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 teams 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 those types of project to which the GP will apply.
• 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 documents) are contained within the Support Solutions Envelope (SSE) Compliance Tool and must be measurable, consistent and objective.
• Supporting Information – Contains 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 (SMEs) – 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 representatives and Support Improvement Team.

How is a GP ‘tailored out’?

The SSE should be tailored to meet the requirements of a particular project, as agreed with the Through Life Support (TLS) Support Improvement Team (SIT) Support Solutions Officer (SSO) in conjunction with relevant stakeholders.

How do I contact the Support Improvement Team?

Contact details for the SIT Lead can be found in the SSE, or you can find full contact details and process instructions on the TLS Support Improvement Team website.

Can I give the SSE to Industry ?

Yes. The SSE can be given to contractors as part of the Invitation to Tender (ITT). The website can be accessed through the Internet, although some documents are not available due to their security classification.

The SSE will be useful to a contractor in setting out the context of the support process and how it relates to operational capability.

The SSE is not to be passed, or portrayed to Industry, as a box into which their support solution must fit, as this may stifle innovation and the future development of policy.

Is the use of the Compliance Tool mandatory?

No. It is recognised that project teams and projects are different and that some may wish to record their compliance assessment activities in another way or adapt the compliance tool for their own use.

The important aspect is for a project team’s compliance assessment to record the necessary level of detailed evidence and for it to be communicated to the relevant stakeholders.

Consultation with the appropriate SSO is critical in order to ensure that any proposed alternative tool will meet the requirements of the assurance process and avoid nugatory work for a project team.

How does the Support Options Matrix (SOM) relate to the SSE?

The relationship between Integrated Logistic Support (ILS) and the SOM has led to some confusion. The SOM and SSE are not related; therefore, the SSE does not require measurement against or application of the SOM. The reasons are outlined below:

• The SOM was developed by the Equipment and Support Continuous Improvement Team (ESCIT) to support the Defence Logistics Transformation Programme (DLTP).
• The SOM is a mechanism which was specifically created to analyse and apply the ‘Leaning’ process to legacy support.
• The requirement for the SOM arose because in-service and legacy support arrangements were designed before the adoption of ILS.

In the past, ILS has focused on future equipment while ESCIT has looked at In-service delivery.

Many In-service projects do not have ILS plans to review and for these projects in particular, the SOM provides a proven framework for redesigning their support solution.

However, the issue from the perspective of support coherence is that ‘Leaning’ an isolated support chain could create problems elsewhere if not fully integrated across the business.

In addition, support reappraisal projects that are subject to the Smart Approvals process require SSE assessment and assurance which, in turn, requires the application of ILS principles.

As a result, In-service project teams could find themselves being forced to apply ILS through the SSE and at the same time being directed to use the SOM by ESCIT.

Is the SSE applicable to UOR projects?

Yes. The requirement to assess a support strategy against the SSE for equipments developed under the Urgent Operational Requirement (UOR) process is clearly stated in Smart Approvals Guidance.

The Business Case must demonstrate the maturity of a proposed Support Solution, and its coherence and consistency with the logistic policies outlined in the SSE.

Given the pressing nature of UORs, the SSE tailoring process should be applied using the UOR specific Compliance Tool to produce a Through-Life Support Assurance Strategy Plan.

This process should be applied with project stakeholder awareness and in consultation with the project’s SSO.

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 November 2009

Minor text changes.

1 May 2009

IPT replaced by project team.

SITO replaced by SSO.

Minor text changes.

1 April 2009

Minor text changes.

Hyperlink amended.

‘Engagement’ changed to ‘Support Improvement’.

1 November 2008

Major update.