|
Content
Key Support Area (KSA) 4 – Introduction: Logistic InformationPrefaceThe 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 Door ResponsibilityThe Defence Management Board (DMB) has designated Chief of Defence Materiel (CDM) the process owner for the end-to-end logistic process. The management and control of the information aspect of this is overseen by Director Defence Logistics Policy (D Def Log Pol) on his behalf. With effect from 30 October 2009 KSA 4 is owned by Head Logistics NEC Programme who is responsible for defining the scope and depth of its content and assists with:
ContextSuccessful logistics within Defence is dependant upon:
Consequently, decision making in a logistics support network is the centre of gravity for Defence Logistics. It is imperative that all areas supporting operational commanders, whether within MOD or in Industry, adopt and adhere to sound information management principles, recognising logistics information as a valued business asset in its own right. This KSA is applicable to all projects where logistics information is required to support the capability through life. Director Equipment Capability Command, Control and Information Infrastructure (DEC CCII) Command and Battle Management (CBM) Logistics Branch is responsible for setting the Logistics Capability Requirements Framework, which project teams must map their Logistics Information Systems / Information Technology (Log IS / IT) requirements against, to avoid duplication through the introduction of bespoke Log IS solutions. To assist, KSA 4 requires project teams to define and understand their Logistics Information needs to support their capability through life. Logistics Information Requirement Planning is the key to identifying all of the Information Exchange Requirements (IER) necessary to not only support fielded capability, but also support the essential business functions (performance management, finance etc). When managed correctly, logistics IERs can be presented to DEC CCII CBM, Director Information and Services (DISS), Head of Logistic Network Enabled Capability Programme (Log NEC) and Director Joint Support Chain (DJSC) to ensure coherence with their capability planning and delivery processes. The aim of KSA 4 is to ensure that capabilities are developed and delivered into service in a coherent and coordinated manner. This will include ensuring that all supporting Log IS, services and interfaces have been scoped, developed and costed into the solution. The outcome of this planning process and the final deliverable from KSA 4 will be a Logistics Information Plan (Log IP). The Log IP will clearly identify the essential IERs necessary to support the capability and also allow the through life cost of information to be articulated and captured in the project’s business case to the Investment Approvals Board (IAB). Governing PoliciesEach 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. Every Project is required to compile an Assurance Plan comprising applicable GPs and will ultimately be required to provide internal Ensurance or obtain independent Assurance against each of those GPs. Each GP consists of the following sections:
Points of ContactKSA Owners representative
For all aspects of this KSA the initial POC is the SIT Lead.
Change History
Change HistoryDue 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.
|