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

Governing Policy (GP) 4.1 – Logistic Information Requirements Planning

Preface

The Logistics NEC Programme change process took effect on the 30th October 2009.

The Change Process has to provide assurance that the Logistic Information element of the Support Solution Envelope of all DE&S projects is sound. This requirement stems from Head Logistics NEC Programme’s responsibility as Owner of Key Support Area 4 (KSA 4), within Director Joint Support Chain’s (D JSC) Support Solution Envelope (SSE).

For further information on the Logistics NEC Change Process contact Mil: 9679 81317 or Civ: +44 (0) 30 679 81317.

Revised Governing Policies will be produced to reflect that the Logistics NEC Programme - Front DoorExternal link to Ministry of Defence Intranet content will be used as the initial point of contact for KSA 4 advice and guidance.

Scope

Logistic Information Requirements Planning (LIRP) will enable project teams to understand their logistics information needs to support their capability through life. It ensures that projects align with MOD Logistics Information Policy and aids understanding of how information systems and services can best support their business.

By treating information as a key asset, LIRP provides the clarity needed for effective through life decision making, by assessing the cost and utility of logistics information and reducing operational risk.

To achieve consistency in LIRP, MOD and Industry have developed a modelling approach, which is to be adopted by all projects supporting capability across Defence and Industry.

The final deliverable from the LIRP process will be a project specific Logistics Information Plan (Log IP) tailored to meet the needs of the project team and Industry by identifying the critical logistics information triggers and exchanges necessary to ensure the support solution functions effectively.

The Log IP identifies who owns and delivers the logistic information needed to support their capability through life, and when complete shall form part of the contracting schedule for the project.

The benefits of developing the Log IP are:

  • A clear picture of information exchange requirements between MOD and Industry to support the capability through life.
  • Identifies logistics information needs, owners, costs, roles and responsibilities ensuring they are contracted for up-front.
  • Project teams will be able to identify the costs of exchanging logistics information with industry and interfacing with the Defence Infrastructure.
  • The project has assurance that their support solution is interoperable with the defence logistics information systems and services.
  • Alignment with current MOD policy for Information Management and Architecture.
  • The project team will be able to identity operational risk and understand the implications of failing to comply with Logistics Information Policy.
  • Enables shared situational awareness to the end user and industry to enable effective logistics decision support.

Applicability

This governing policy will apply to all projects.

To ensure the maximum benefit, Log IP development should be started during the early stages of the project and contact made with the Key Support Area 4 (KSA 4) owner’s representative prior to Initial Gate. It requires close project team and Industry collaboration throughout, and where appropriate is facilitated by the KSA 4 GP 4.1 Subject Matter Experts (SMEs).

Underpinning Policy

JSP 602 LeafletsExternal link to Ministry of Defence Intranet content Each leaflet is a stand alone document and identifies the Communication Information Systems (CIS) Interoperability (IO) policy and standards relevant to each topic area:

  • 1001 Application Architecture
  • 1007 Database Services
  • 1008 Information Coherence Environment
  • 1009 Directory Services
  • 1010 File Services
  • 1012 Information Interchange
  • 1014 Legislation
  • 1027 Time Services
  • 1028 Asset Identification
  • 1032 Cryptography and Key Management
  • 1036 Security Architecture
  • 1040 MODAF

JSP 329External link to Ministry of Defence Intranet content:

  • Chapter 3 – Corporate Reference Information
  • Chapter 4 – Data exchange policy.

Compliance Tool – Evidence Requirements

The Evidence Requirements for this GP can be found within the SSE 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) or the relevant Support Solutions Officer (SSO) at the earliest opportunity.

Any risks associated with this variance will be agreed with the KSA Owner’s representative and SSO for the project team to manage or mitigate.

Any costs associated with this risk mitigation may potentially fall to the project team to fund the integration of a non-compliant solution.

Supporting Information

An assessment of the following policies for their applicability and compliance is required by the project team.

Sponsoring Authority

  • Log NEC Prog Business and Information Architecture (BIA) Team
  • Cedar 1c
  • DE&S Abbey Wood
  • Bristol, BS34 8JH
  • Mil: 9679 81412
  • Civ: +44 (0) 30 679 81412

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.

Title Scope Phone / Email
BIA Engagement (Air) Air
BIA Engagement (Land) Land
BIA Engagement (Sea) Sea
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.
SME details updated.
1 July 2010
Minor text changes.
Sponsor and SME details updated.
LCIA Hyperlink updated.
1 April 2010
Text changed to reflect that support assurance policy and guidance is now incorporated into JSP 899.
Preface: Telephone numbers changed.
1 March 2010
SME details changed (due to office move).
1 November 2009
Preface introduced.
1 October 2009
Scope: 5th paragraph, Line 2: ‘should’ replaced with ‘shall’.
1 September 2009
JSP 602–1008: New title.
JSP 602–1031: Deleted (Subsumed into JSP 602-1008)
1 July 2009
Support Solution Assurance Guidance paragraph added.
SME details amended.
1 May 2009
Minor text changes.
‘Support Improvement Team Officer’ changed to ‘Support Solutions Officer’.
IPT’ changed to ‘project team’.
1 April 2009
‘Underpinning Policy’ and ‘Supporting Information’ contents revised.
Hyperlinks to individual leaflets removed.
‘Engagement’ changed to ‘Support Improvement’.
‘Representative’ added to KSA owner.
1 November 2008
Major update.