life cycle logistics support - gdit · life cycle logistics support is an acquisition planning and...

Skip NavigationGlossary Acronyms Resources Plugins He

D

Life Cycle Logistics SupportLife Cycle Logistics Support

page 1 of 24

Long Description

Title screen for Module 4, Lesson 3: Technical Management, Life Cycle Logistics Support containing three photos of: professionals working at desktop computers, a woman working on heavy machinery and a CBP aircraft.


Introduction

Welcome to the Life Cycle Logistics Support lesson. Life Cycle Logistics Support is a critical acquisition discipline that provides for the operation and support of a deployed and fielded system over the course of its operational life.

In this lesson, you’ll be introduced to the following concepts:

• Integrated Logistics Support (ILS)

• The 10 traditional ILS elements

• Supportability and Sustainment

To print this lesson, select print.


page 2 of 24


Learning Objectives

Upon completion of this lesson, you will be able to:

• Identify the 10 logistics support elements

• Describe the common logistics support roles associated with an acquisition program

• Describe the importance of ILS planning and Supportability Engineering to ensuring system reliability,availability, and maintainability


page 3 of 24


Life Cycle Logistics Support is an acquisition planning and management function responsible for Integrated Logistics Support throughout an acquisition's life cycle.

Integrated logistics support (ILS)A management process, applied throughout the system's life that bases all programmatic decisions on the anticipated mission-related and economic benefits derived over the system's life cycle. Traditionally, ILS consists of 10 elements: Maintenance Planning; Manpower & Personnel, Training & Training Support; Supply Support; Support Equipment; Technical Data; Computer Resources Management; Facilities; PHS&T and Design Interface.

ILS is a proven way to strategically plan for and manage everything it takes to deploy, field, operate, and support a system cost-effectively over its entire life cycle.

What is Life Cycle Logistics Support?


page 4 of 24


The 10 Integrated Logistics Support Elements

ILS is generally considered to encompass 10 distinct elements, commonly called the Integrated Logistics Support Elements.

Select each element below for more information.


page 5 of 24

Design Interface

This is a family of activities introduced early in the life cycle intended to ensure a system (or equipment) is developed (or selected if a commercial or non-developmental item) to reduce the logistics burden/footprint while simultaneously meeting critical performance characteristics.

Manpower and Personnel','../..');

Manpower: This consists of those actions taken as early in acquisition or modification as feasible to insure the necessary administrative and procedural activities will be initiated to analyze, evaluate, determine and plan for manning realities, constraints and optimization opportunities.

Personnel: This area covers activities taken to insure procurement, design and modification fully consider individuals\' attributes and their relationship to the system, item, software, etc. Not only are any analyses designed toachieve the appropriate skill mix to maximize overall performance and personnel assignment included, but also taskssuch as identifying any special skills or physical characteristics personnel will be required to possess to effectively operate or maintain the system, item, software, etc.

Maintenance Planning

The action necessary to retain or restore an item to a specified condition and consists of Preventive Maintenance, Corrective Maintenance, Event Maintenance, and Scheduled Maintenance. It is initially based on a Maintenance Concept which addresses maintenance considerations, constraints, and plans for system operational support. This is often a major driver in designing the system/equipment and its required support structure. The Maintenance concept is usually followed by a Maintenance Plan. This is the detailed description of maintenance decisions on each repairable item candidate within the system Work Breakdown Structure (WBS) and is usually based on a Level of Repair Analysis (LORA).

Technical Data

Includes scientific/technical information recorded in any form or medium (such as manuals and drawings) necessary to operate and maintain a system. Computer programs and related software are not generally considered TD. Also excluded are financial data or other information related to contract administration.

Support Equipment

All equipment (mobile or fixed) required to support an acquisition\'s operation and maintenance. This includes associated multi-use support items, ground-handling and maintenance equipment, tools, meteorology and calibration equipment, and manual/Automatic Test Equipment (ATE). For these items, the acquisition of their ILS support is also included.

Supply Support

The process conducted to determine, acquire, catalog, receive, store, transfer, issue, and dispose of secondary items necessary for the support of end items and support items. This includes provisioning for initial support as well as replenishment supply support.

Packaging, Storage, Handling, and Transportation

PHS&T consists of those resources, processes, procedures, design considerations, and methods to ensure all system, equipment, and support items are preserved, packaged, handled, and transported properly. This includes environmental considerations, equipment preservation requirements for short- and long-term storage, and transportability.

Computer Resources Management

Encompasses the process of selecting computer hardware, software and firmware for specific systems and planning for their lifecycle support.

Training and Training Support

The processes, procedures, techniques, training devices, and equipment used to train personnel to operate and support a materiel system. Includes individual and crew training; new equipment training; initial, formal, and On-The-Job (OJT) training; and Integrated Logistics Support (ILS) planning for training equipment and training device acquisitions and installations.

Facilities

This is a process employed to identify, analyze and document those facilities required for the operation and maintenance of a system/equipment throughout its life cycle. It is achieved through translation of missions, tasks andfunctions into facilities requirements then comparing them with available assets to determine deficiencies and/or excesses. This includes, but is not limited to, training facilities, ranges, depots, storage, housing etc, and those related supporting utilities.

ILS

Integrated Logistics Support


This is the Predator, an unmanned aerial vehicle used by Customs and Border Protection (CBP) to monitor the US-Mexico border.

Depending on your background, you may be aware on some level of the things involved in fielding and operating an unmanned aerial vehicle, or its logistics footprint. But until you actually sit down to develop a system, you may not consider how those things come to exist, or who has to account for them.

Example: The Predator


page 6 of 24

Logistics Footprint

The combination of manpower, personnel, equipment, facilities, etc. required to support a fielded system


The Predator's Logistics Footprint

This is a graphical representation of the Predator's Logistics Footprint.

Select each element of the image below for more information.


page 7 of 24

Predator

The Predator is much more than an airframe.

Design Interface

The Predator uses the same type of engine commonly used in snowmobiles; uses common mechanical systems for power, fuel, and ignition; and breaks down into six pieces that can be transported in a huge crate called the coffin.

Manpower and Personnel

On the ground, a team of technicians, support personnel, pilots, and sensor operators operate and support the aircraft.One predator system takes about 82 personnel to run successfully.

Maintenance Planning

Once on site, a single Predator can be reassembled by a crew of four in less than eight hours. Field technicians can perform the majority of maintenance in the field with the proper supplies, thanks to the aircraft\'s simple design.

Technical Data

An example of the technical data that accompanies the Predator system are the schematics for the Rotax 914, four-cylinder, four-stroke, 101-horsepower engine that turns the aircraft\'s main drive shaft.

Support Equipment

In addition to four predator aircraft, a single predator system also includes a Ground Control Station, and a primary satellite link. Maintenance personnel also require tools to maintain and repair the aircraft.

Supply Support

Just like any other aircraft that contains a gasoline powered engine, the Predator requires consumables--oil, gasoline,ethylene glycol (a de-icer), etc.--and a supply of spare parts to continue to operate effectively.

Packaging, Storage, Handling, and Transportation

The entire Predator system was designed to be easy to transport. The aircraft in its coffin, the Ground Control Station, and the primary satellite link all fit in the cargo hold of a C-130 Hercules or C-141 Starlifter aircraft.

Computer Resources Management

The Ground Control Station (GCS) includes a variety of data terminals and equipment used to operate, monitor, and support the aircraft. The system also transmits data back to support technicians at computer terminals in a command center.

Training & Training Support

The majority of Predator pilots and sensor operators are trained on simulators and training aircraft at Creech Air Force Base in Nevada or March Air Reserve Base in California.

Facilities

Of course, facilities are required to house the personnel and equipment and to deliver the training classes--air force bases, command centers, hangars, etc.

Skip Navigation--> Glossary Acronyms Resources Plugins He

Knowledge Check

Match each of the ILS elements below with the example that best represents that element. When you are finished, select Submit.

Simulators, practice labsTraining & Training Support

Diagnostic toolsSupply Support

Skilled operatorsTraining & Training Support

Railcars, flatbed trucksFacilities

Lubricants, tires, partsSupply Support

Office laptopsSupport Equipment

Logistician on the Design IPTComputer Resources Management

Drawings, schematicsTechnical Data

Offices, aircraft hangarsFacilities

Organizational repair listTechnical Data

Submit


page 8 of 24

ILS


• Simulators, practice labs: Training & Training Support• Diagnostic tools: Support Equipment• Skilled operators: Manpower & Personnel• Railcars, flatbed trucks: Packaging, Handling, Storage and Transportation• Lubricants, tires, parts: Supply Support• Office laptops: Computer Resources Management• Logistician on the Design IPT: Design Interface• Drawings, schematics: Technical Data• Offices, aircraft hangars: Facilities• Organizational repair list: Maintenance Planning


Recap: Integrated Logistics Support Elements

Review the key concepts introduced in this topic.

• Integrated logistics support (ILS) is an integrated approach to logistics management which involvesdeveloping logistics support requirements and addressing supportability early in the acquisition.

• The goal of ILS is to create systems that last longer, require less support, and have a smaller logisticsfootprint, increasing the Government's return on investment as a result.

• A system's logistics footprint is much larger than just the system itself; it includes the 10 ILS Elements.

• ILS is traditionally considered to encompass 10 distinct elements:

◦ Design Interface

◦ Manpower and Personnel

◦ Maintenance Planning

◦ Technical Data

◦ Support Equipment

◦ Supply Support

◦ Packaging, Storage, Handling, and Transportation

◦ Computer Resources Management

◦ Training and Training Support

◦ Facilities

The next topic is Supportability & Sustainment.


page 9 of 24


Introduction to Supportability & Sustainment

Experienced logisticians will tell you that a program office must consider ILS up front and often in a program, because a successful ILS strategy depends entirely on the work done during planning. Without careful planning, the program will have trouble achieving its goals.

Remember, the goal of ILS is to create systems that last longer, require less support, and have a smaller logistics footprint, because doing so increases the value the Government receives from its investment in those systems.

That translates into the program goals of supportability and sustainment.


page 10 of 24

ILS



So what is supportability, and how do you address it during system design?

Supportability is a program design characteristic, influenced by factors such as reliability and maintainability, which defines a system's ability to be sustained in an operating environment with adequate availability of required support elements. As a key component of availability, supportability includes design; technical support data; supply chain design; and maintenance procedures to facilitate detection, isolation and timely repair and/or replacement of system components. These maintenance procedures may include diagnostics, prognostics, real-time maintenance data collection, etc.

How easy is the system to operate? How easy is the system to repair and maintain? How reliable is the system? The answers to these questions indicate how supportable a system is.

Supportability


page 11 of 24


Supportability engineering is an engineering discipline that ensures supportability is considered during system design and development. You will also see the terminology "design for supportability."

An Integrated Product/Project Team (IPT) that includes a logistician will work within the Systems Engineering process to design for supportability, i.e., to influence the design and development process to account for ILSconsiderations in the design itself.

As part of the Systems Engineering process, the team will:

• Design for ease of operations and maintenance(e.g., ensure maintenance areas are easilyaccessible)

• Reduce the system's logistics footprint (e.g.,reduce the number of parts and required tools)

• Identify the equipment, skills, personnel, facilities,services, supplies, and procedures required tostore, supply, and maintain the system

Design interface is the ILS Element that links Supportability Engineering to the other nine ILS elements.

Supportability Engineering


page 12 of 24

ILS



Supportable Designs

Select an image below to reveal the results of designing for supportability.

These are just a few examples. There's a lot more to supportability than just maintenance—reliability, data collection, data availability, supply chain design, etc. are all part of supportability.


page 13 of 24

Badge Holder

A 1-part badge holder instead of a 10-part assembly (reduced part counts)

Helicopter

A helicopter designed with maintenance areas accessible without ladders, stands, lifts, or creepers (ease of maintenance)

Six Hand Tools

An aircraft engine designed to be fully maintainable with six hand tools (smaller logistics footprints)

Boeing 777

The Boeing 777\'s captive fasteners, which cannot be separated from the object they fasten; it would be hard for maintenance personnel wearing gloves to find the fuselage access panel fasteners if they drop into the January snow at O\'Hare airport, for example (ease of maintenance)

Gas Cap

Retaining straps on automobile gas caps; since the environmental systems in modern automobiles depend on a vacuum in the gas tank to operate effectively, leaving the gas cap on the pump at the station is no longer just an annoyance, it can shut down your vehicle (ease of operation, reliability)


Reliability, Maintainability, & Availability

The impact of ILS is often measured in terms of metrics such as reliability, maintainability, and availability. You will sometimes see these abbreviated "RAM," or "RM&A." These are systems engineering concepts that are considered during supportability engineering as part of the design interface.

Select each tab for additional information.


Supportability engineering and the concepts of reliability, maintainability, and availability are part of an involved technical discipline. They are presented at a high-level here with example formulas to give you an idea of what's involved in this acquisition function. There are many ways to design for, calculate (different formulas), and track each of these metrics.

page 14 of 24

Maintainability Availability

Reliability is the probability that an item will perform its intended function under stated conditions for either a specified interval or over its useful life. Reliability attempts to answer the question, "How likely is it that the system will complete a mission without breaking down?"

Mean time between failures (MTBF), which calculates the average time between system failures, is a common way to measure system reliability. To calculate MTBF, divide the total number of failures by the total number of fielded systems to determine the average number of failures per system. Then divide the average annual operating hours per system by the average number of failures per system.

MTBF = (average annual operating hours/system) / ((# failures) / (# fielded systems))

Reliability

ILS


Reliability

Reliability is the probability that an item will perform its intended function under stated conditions for either a specified interval or over its useful life. Reliability attempts to answer the question, "How likely is it that the system will complete a mission without breaking down?"

Mean time between failures (MTBF), which calculates the average time between system failures, is a common way to measure system reliability. To calculate MTBF, divide the total number of failures by the total number of fielded systems to determine the average number of failures per system. Then divide the average annual operating hours per system by the average number of failures per system.

MTBF = (average annual operating hours/system) / ((# failures) / (# fielded systems))

Availability

Availability is the degree to which an item is in the operable state at the start of a mission when the mission is called for at a random time. Availability attempts to answer the question, "How likely is it that the system will be available and mission ready when needed?"

A general calculation for availability is "up time" divided by total time ("up time" plus "down time").

A = (up time) / (up time + down time)

Maintainability

Maintainability is an item's ability to be retained in, or restored to, a specified condition when maintenance is performed by skilled personnel using the correct procedures and resources. Maintainability attempts to answer the questions, "How easy is it to fix the system when it breaks?" and "How quickly can it be repaired?"

Mean time to repair (MTTR), which calculates the average time it takes to repair the system, is a common way to measure maintainability. To calculate MTTR, divide the total number of hours spent on corrective maintenance by the total number of corrective maintenance actions.

MTTR = (hours spent on corrective maintenance) / (# of corrective maintenance actions)


Sustainment

Sustainment is another program design characteristic that consists of those planned support resources, system design characteristics' capabilities, and activities required to maintain fielded systems at intended levels of performance and meet contingency usage requirements. Consequently, sustainment is a function of providing for and maintaining those levels of ready forces and materiel necessary to support the mission.

Sustainment encompasses efforts to cost-effectively field a support program that meets operational support performance requirements by sustaining the system to a level consistent with operational tempo and duration. This may include such items as supply chain management, sustaining engineering, data management, anti-tamper provisions, and interoperability functions.

The purpose of sustainment planning is to balance cost, schedule, and performance requirements within the program's Integrated Logistics Support (ILS) framework to ensure cost-effective sustainment of the system over its entire life cycle.


page 15 of 24


The Importance of Cost-effective Support

Why is it important to create systems that have smaller logistics footprints? Remember, the Operations & Support (O&S) cost for a deployed, hardware-centric system typically represents 60-70% of the total life cycle cost of the system. O&S cost includes operators, maintenance personnel, training, spare parts, support equipment, facilities, etc. In other words, the 10 ILS elements.

D

It's commonly said, "Ninety percent of your budget is spent before metal is bent or code is written." That means by the time you get around to producing and supporting the system, there is increasingly less latitude in making decisions that impact the program's bottom line.

To reduce O&S cost you must address supportability during system design. It's nearly impossible to achieve significant O&S cost savings once a system is in production. Failure to consider O&S during planning and design may ultimately lead to depletion of program funds or early system retirement.


page 16 of 24

Long Description

Graph illustrating O&S costs represent 70% of program cost. Percentage of program cost by phase: Disposal (smallest percentage), R&D, Production & Deployment, Operating and Support cost (largest percentage).

ILS



Knowledge Check

For each description below, select the appropriate role or term from the drop-down list provided. When you are finished, select Submit.

A program design characteristic which defines a system's ability to be sustained in an operating environment with adequate availability of required support elements.Availability

Providing for and maintaining levels of support resources, capabilities, and activities necessary to maintain fielded systems at intended levels of performance and meet contingency usage requirements.Availability

The probability that an item will perform its intended function under stated conditions for either a specified interval or over its useful life.Availability

An item's ability to be retained in, or restored to, a specified condition when maintenance is performed by skilled personnel using the correct procedures and resources.Availability

The degree to which an item is in the operable state at the start of a mission when the mission is called for at a random time.Availability

Submit


page 17 of 24

• Supportability is a program design characteristic which defines a system's ability to be sustained in anoperating environment with adequate availability of required support elements.• Sustainment is providing for and maintaining levels of support resources, capabilities, and activitiesnecessary to maintain fielded systems at intended levels of performance and meet contingency usage requirements.• Reliability is the probability that an item will perform its intended function under stated conditions foreither a specified interval or over its useful life.• Maintainability is an item's ability to be retained in, or restored to, a specified condition whenmaintenance is performed by skilled personnel using the correct procedures and resources.• Availability is the degree to which an item is in the operable state at the start of a mission when themission is called for at a random time.


Recap: Supportability & Sustainment

Review the key concepts introduced in this topic.

• Supportability is a program design characteristic, influenced by factors such as reliability andmaintainability, which defines a system's ability to be sustained in an operating environment with adequateavailability of required support elements.

• Supportability engineering is an engineering discipline that ensures supportability is considered duringsystem design and development. You will also see the terminology "design for supportability."

• The impact of ILS is often measured in terms of metrics such as reliability, maintainability, and availability.These are systems engineering concepts that are considered during supportability engineering as part ofthe design interface.

• Sustainment is a function of providing for and maintaining levels of support resources, capabilities, andactivities necessary to maintain fielded systems at intended levels of performance and meet contingencyusage requirements.

The next topic is ILS Planning in the Acquisition Life Cycle Framework.


page 18 of 24


Introduction to ILS Planning in the Acquisition Life Cycle Framework

Now that you know what Integrated Logistics Support (ILS) is, why it's critical to program success, and how it relates to supportability and sustainment, let's take a quick look at how ILS is integrated with the Acquisition Life Cycle Framework (ALF).

The following concepts are introduced in this topic:

• Logistics-related roles and responsibilities

• The Integrated Logistics Support Plan (ILSP)

• ILS events that are integrated into the ALF


page 19 of 24


Logistics Roles & Responsibilities

Let's take a look at the common logistics support roles in an acquisition program.

Select each tab for additional information.


page 20 of 24

ILS Manager ILS Management Team

The Program Manager (PM) has the overall responsibility for acquiring and fielding the initial support capability for the system. He or she:

• Ensures an ILS strategy is fully incorporated into program planning, scheduling, and execution

• Designates an ILS Manager to assist in planning, formulating, coordinating, and implementing aneffective ILS strategy

Program Manager

ILS


ILS planning

The formal acquisition management document that describes the management approach for obtaining a highly supportable capability with an affordable and effective support structure.

Program Manager

The Program Manager (PM) has the overall responsibility for acquiring and fielding the initial support capability for the system. He or she:

• Ensures an ILS strategy is fully incorporated into program planning, scheduling, and execution• Designates an ILS Manager to assist in planning, formulating, coordinating, and implementing an effective

ILS strategy

ILS Manager

The ILS Manager is a Subject Matter Expert (SME) selected by the PM to develop and implement an effective ILS strategy for the program. He or she:

• Designs, develops, implements, reviews, and manages an ILS strategy for the program• Forms the ILS Management Team (if one will be employed by the program)

ILS Management Team

The ILS Management Team is an Integrated Product/Project Team (IPT) comprising functional experts selected by the ILS Manager to represent their respective functional areas during ILS planning. They:

• Flesh out and recommend enhancements to the ILS strategy and planning.• Ensure planning is comprehensive, with each member accomplishing any necessary planning activities within

their functional area• Implement the ILS strategy


Integrated Logistics Support Plan

The PM, ILS Manager, and ILS Management Team all provide input for the ILSP.

Select the ILSP tab for more information.

D


page 21 of 24

Long Description

Interactive three ring binder with selectable tabs.

PM

Program Manager

ILS


Integrated Logistics Support Plan Purpose The ILSP documents the overall planning undertaken to support the ILS strategy and the infrastructure that the fielded system will require in order to remain available and ready to operate once fielded. The ILSP should address cost, schedule, and performance. Prepared by The program's Life Cycle Logistics Manager prepares the ILSP with oversight from the PM, and often with the support of an IPT. Appendix Instruction/Guidebook 102-01-001 Appendix J: Supportability and Sustainment contains guidance on developing an ILSP. Approval The ILSP is approved by the ADA at ADE-2A and updated as required.

Test & Evaluation Master Plan Purpose The Test & Evaluation Master Plan (TEMP) is a living, high-level planning document for all T&E-related activities that describes the program office's Developmental Test & Evaluation (DT&E) and Operational Test & Evaluation (OT&E) strategy; defines test parameters, attributes, and methods; summarizes T&E resource requirements; and allocates T&E responsibilities. Prepared By The TEMP is prepared by the Operational Test Agent (OTA) and Test & Evaluation IPT with oversight from the PM. Appendix DHS Instruction/Guidebook 102-01-001, Appendix L contains guidance and a sample template for the TEMP. Approval The TEMP is endorsed by the OTA and approved by the Director of Operational Test & Evaluation (DOT&E) at or prior to ADE-2B.

SELC Tailoring Plan Purpose The purpose of the SELC Tailoring Plan is to inform DHS leadership about how the SELC will be adapted to fit the needs of a specific acquisition project. The plan identifies the major activities and reviews that will be conducted, as well as the technical management artifacts that will be prepared for the project. Prepared By The Program Manager (PM) is responsible for preparing the SELC Tailoring Plan in accordance with the guidance outlined by the Program Accountability and Risk Management (PARM). Guidance The DHS Systems Engineering Life Cycle (SELC) Tailoring Plan Guide, prepared by the PARM and the Office of the Chief Information Officer (CIO), provides guidance and a sample template. Approval The Component Acquisition Executive (CAE) or the Acquisition Decision Authority (ADA) approves the SELC Tailoring Plan prior to ADE-2B.

Acquisition Plan Purpose The AP answers the question, "How can we strategically acquire this capability?" The AP contains the overarching acquisition strategy, and is used to inform and integrate activities across the acquisition, including acquisition planning and integrated support planning. The AP should provide: A clear statement of the desired acquisition outcomes A comprehensive description of the business environment An assessment of the potential supplier base for desired goods and services A top-level strategy for sustainment and support Recommendations for the overall acquisition approach and types of acquisition (e.g., asset acquisitions, services acquisitions, IAAs) Prepared by The Acquisition Plan is prepared by the PM and Contracting Specialists in the PMO. Appendix

Instruction/Guidebook 102-01-001: Appendix E points users to the DHS Acquisition Planning Guide for guidance in developing an Acquisition Plan. Programs should contact the PARM for tailoring guidance of the specific sections and AP content based on the unique conditions of each acquisition. Approval The AP is a living document that spans the life of the acquisition, and will be updated and expanded over time. The PMO starts developing the AP after ADE-1, and updates it to support ADE-2A and 2B. The Chief Procurement Officer approves the AP at ADE-2A.

Acquisition Program Baseline Purpose The purpose of the APB is to define the cost, schedule, and performance parameters for the program that the PMO will be accountable for in quantitative, measurable, testable terms. The APB serves as the PMO's "contract" with the customer and DHS headquarters. The APB must: Relate to the need expressed in the MNS Track the KPPs detailed in the ORD in terms of thresholds and objectives Be consistent with the program's LCCE Align with the resources programmed in the Future Years Homeland Security Program (FYHSP) Prepared By The PMO prepares the APB. Appendix Instruction/Guidebook 102-01-001 Appendix K: Acquisition Program Baseline provides guidance on APB development, including a sample template. Approval The ADA approves the APB at ADE-2A.

Life Cycle Cost Estimate Purpose An LCCE answers the question, "How much will the system cost over its life cycle?" A program’s LCCE serves as the cost input for acquisition decisions, programming, and budget requests to Congress. The Planning, Programming, Budget and Execution (PPBE) process is the gateway for getting resources allocated to the program, and the LCCE is used much further upstream than just the budget year in

the process. The LCCE must be comprehensive (i.e., include planning, research & development, testing & evaluation, acquisition, personnel, facilities, deployment, operations, maintenance, disposal, etc.). Prepared by Acquisition Financial Managers and Cost Analysts supporting the PMO prepare the LCCE using inputs from a variety of sources, including the results of the AoA analysis and the ILSP. Appendix Instruction/Guidebook 102-01-001 Appendix I: Life Cycle Cost Estimate points acquisition professionals to the GAO Cost Estimating and Assessment Guide: Best Practices for Developing and Managing Capital Program Costs (available online) for guidance on creating an LCCE. Approval The Component approves the LCCE at ADE-2A, and the PMO will continue to update it throughout the acquisition life cycle.

Concept of Operations Purpose The CONOPS contrasts from the user's perspective the current way the sponsoring organization operates to execute the assigned mission with future methods of operating using potential capability solutions. The CONOPS defines the capability in greater detail than the MNS and CDP and supports development of the AoA/AA and ORD. Prepared by The User/Sponsor develops the CONOPS in parallel and interactively with the AoA/AA and ORD. Process To develop the CONOPS, the User/Sponsor:

• Begins with a baseline CONOPS that describes current operating methods • Describes the deficiencies and gaps in the "as-is" operations (referring back to the MNS and

CDP) • Gathers data to identify potential new ways to respond to future threats and conditions and

eliminate current deficiencies • Feeds those new ideas into the AoA/AA for technical and cost analysis • Updates the CONOPS as alternatives are analyzed (AoA/AA) and develops more detailed

capability needs from identified scenarios • Finalizes the CONOPS using the preferred solution(s) from the AoA/AA

Appendix Instruction/Guidebook 102-01-001 Appendix F: Concept of Operations contains CONOPS development guidance and a sample template.

Operational Requirements Document Purpose The ORD captures the User/Sponsor’s Key Performance Parameters (KPPs) and other operational requirements. Operational requirements are high-level requirements that describe the mission, objectives, and capabilities in operationally relevant terms. The requirements documented in the ORD should be traceable to the MNS and CDP. Prepared By The User/Sponsor develops the ORD in parallel and interactively with the AoA/AA and CONOPS, with support from the PMO and SMEs as required. Process To develop the ORD, the User/Sponsor:

• Uses the parameters from the AoA/AA and CONOPS analyses to populate the ORD (the final ORD should reflect the parameters of the preferred alternative)

• Identifies and documents Critical Operational Issues (COIs) that describe what the capability must be able to do in its operational environment to meet the mission need

• Identifies and documents KPPs that must be satisfied by the capability. The minimal acceptable level for each KPP (threshold) and the maximum desired level (objective) should be provided

Appendix Instruction/Guidebook 102-01-001 Appendix H: Operational Requirements Document contains ORD development guidance and a sample template. Approval The ADA approves the ORD at ADE-2A.

Capability Development Plan Purpose The purpose of the Capability Development Plan (CDP) is to serve as the agreement between the Component Head, the Program/Project Manager (PM), and the Acquisition Decision Authority (ADA) on the activities, cost, schedule, and performance boundaries of the work to be performed in the Analyze/Select phase. This critical period leading up to ADE-2A develops the knowledge used by the ADA to make informed decisions on the performance, schedule, and cost of the program that will effectively deliver capabilities to users. Prepared by The PM prepares the CDP with input from the User/Sponsor, cost analysts, logisticians, and other subject matter experts (SMEs). Appendix

Instruction/Guidebook 102-01-001 Appendix D: Capability Development Plan contains guidance and a sample CDP template. Approval The ADA approves the CDP at ADE-1.

Mission Needs Statement Purpose The MNS describes a specific functional capability required by users to accomplish a Component mission or objective. The MNS:

• Describes the problem, NOT the solution • Is a formal description of a strategic need for investment • Initiates acquisition program management process • Is the basis for submitting a Resource Allocation Plan (RAP) to request funding

Prepared by The MNS is prepared by the User/Sponsor that identifies the need. Appendix Instruction/Guidebook 102-01-001 Appendix C: Mission Needs Statement contains guidance and a sample MNS template. Approval The MNS is approved by the ADA at ADE-1. Example For example, a MNS identifying a gap in Customs and Border Protection’s capability for ensuring the security of the US-Mexico border might describe a need to enhance agents’ ability to detect people entering the country illegally.

Preliminary Missions Need Statement Purpose The purpose of the P-MNS is to state the need at a top-level, clearly and accurately, as a basis for developing a Mission Needs Statement (MNS) and submitting a Resource Allocation Plan (RAP) to request funding for a future acquisition.

Prepared by The P-MNS is prepared by the User/Sponsor that identifies the need. Appendix The P-MNS is drafted using the same format as for a MNS, which is located in Instruction/Guidebook 102-01-001 Appendix C: Mission Needs Statement. The User/Sponsor only completes those sections for which knowledge is available. Approval The P-MNS is approved by the Component at ADE-0 and sent to the ADA for review. Additional Information The P-MNS is not a formal requirement; if the Component desires, it may develop a MNS directly without developing a P-MNS first.


ILS in the Acquisition Life Cycle Framework

By walking through the Acquisition Life Cycle Framework, we can see the ILS-related activities that occur (approximately) in each phase. This is a generic representation of the sequence of events that might take place throughout a program's life cycle. The earlier the planning is done, the better.

D


page 22 of 24

Long Description

Four phases of the Acquisition Life Cycle Framework with sample ILS-related activities listed below particular phases.

The Analyze/Select Phase includes:

1. Identify logistics-related reuirements and constraints.2. Develop an Integrated Logistics Support (ILS) strategy.3. Draft an Integrated Logistics Support Plan (ILSP).

The Obtain Phase includes:

4. Design for supportability, reliability, maintainability, availability, etc.5. Develop the support infrastructure.6. Develop and award support contracts (if necessary).

The Produce/Deploy/Support Phase includes:

7. Operate and support the system.8. Dispose of the system.


Knowledge Check

For each description below, select the appropriate role or term from the drop-down list provided. When you are finished, select Submit.

Has the overall responsibility for acquiring and fielding the initial support capability for the system.ILS Management Team

Subject Matter Expert (SME) selected to develop and implement an effective ILS strategy for the program.ILS Management Team

An Integrated Product/Project Team (IPT) comprising experts that represent their respective functional areas during Integrated Logistics Support (ILS) planning.ILS Management Team

Documents the planning undertaken to support the ILS strategy and the support infrastructure that the fielded system will require.ILS Management Team

Submit


page 23 of 24

• The Program Manager has the overall responsibility for acquiring and fielding the initial support capability for the system.• The ILS Manager is the Subject Matter Expert (SME) selected to develop and implement an effective ILS strategy for the program.• The ILS Management Team is an Integrated Product/Project Team (IPT) comprising experts that represent their respective functional areas during Integrated Logistics Support (ILS) planning.• The ILSP documents the planning undertaken to support the ILS strategy and the support infrastructure that the fielded system will require.


Lesson Summary

Review the key concepts introduced in this lesson.

Integrated logistics support (ILS) is an integrated approach to logistics management which involves developing logistics support requirements and addressing supportability early in the acquisition. There are 10 ILS elements that must be carefully planned for as part of a programs ILS strategy, well before the system is deployed.

The goal of ILS is to create systems that last longer, require less support, and have a smaller logistics footprint, increasing the Government's return on investment as a result.

This translates into the program goals of:

• Supportability, a program design characteristic which defines a system's ability to be sustained in anoperating environment with adequate availability of required support elements

• Sustainment, providing for and maintaining levels of support resources, capabilities, and activitiesnecessary to maintain fielded systems at intended levels of performance and meet contingency usagerequirements

Supportability must be addressed during system design through Supportability Engineering in order to have a significant impact on the fielded system's logistics footprint and the program's Operations & Support cost. Three related Supportability Engineering concepts which are used to gauge the impact of a program's ILS strategy post-deployment are: reliability, maintainability, and availability.

The Program Manager, ILS Manager, ILS Management Team, and Support Contractor all work together to design an ILS strategy and implement a comprehensive Integrated Logistics Support Plan (ILSP).

You have reached the end of Life Cycle Logistics Support. To continue, select the next lesson from the Table of Contents.

To print this lesson, select print.


page 24 of 24