The Obtain Phase. Long Description

Transcription

1 D page 1 of 32 Long Description Title screen for Module 1, Lesson 4: System Acquisition Life Cycle the Obtain Phase with three photos: an assembly line manufacturing items, a person working on a large engine, and a person reading blueprints and looking at a computer screen.

2 Introduction During the Obtain Phase, the Program Office develops the system (based on the preferred alternative selected during the Analyze/Select Phase) to deliver capability to meet a mission need. The system might include software and/or hardware components, as well as all of the support elements needed to keep it up and running. As the system is developed and tested, the Program Office also prepares for the final Produce/Deploy/Support Phase. includes development of the Test and Evaluation Master Plan (TEMP), which will guide the process for verifying that the system meets the requirements as specified in the Operational Requirements Document and is effective and suitable for the end user. In addition, key program documents that were first developed in the Analyze/Select Phase will be refined and updated, such as the Integrated Logistics Support Plan (ILSP), Life Cycle Cost Estimate (LCCE), and Acquisition Program Baseline (APB). For hardware systems, it may also involve Low Rate Initial Production (LRIP) to prove out the production process, support operational testing, and ramp up to full-rate production. You will be introduced to the following concepts in this lesson: Systems Engineering Life Cycle (SELC) Tailoring The Test and Evaluation Master Plan (TEMP) Developmental Test & Evaluation (DT&E) Operational Assessment (OA) Low Rate Initial Production (LRIP) Operational Test & Evaluation (OT&E) Full Rate Production (FRP) Initial Operational Capability (IOC) Full Operational Capability (FOC) To print this lesson, select print. page 2 of 32

3 Learning Objectives Upon completion of this lesson, you will be able to: Describe the acquisition program activities conducted during the Obtain Phase to plan for system development, verify performance, and execute systems acquisition Identify the requirements and planning documents associated with the Obtain Phase Explain the importance of updating and expanding the Acquisition Plan (AP), Acquisition Program Baseline (APB), Integrated Logistics Support Plan (ILSP), and Life Cycle Cost Estimate (LCCE) Differentiate between, Low Rate Initial Production (LRIP), Full Rate Production (FRP), Initial Operational Capability (IOC), and Full Operational Capability (FOC) page 3 of 32

4 T&D page 4 of 32 Transcript and Long Description [The four phases of the ALF appear, and the six yellow diamonds representing the ADEs in the ALF appear from behind the phases and settle into place. The four phases disappear, then all the yellow ADE diamonds fade EXCEPT for ADE-2A, which moves over to the left of the frame.] Narrator: The purpose of the Obtain Phase is to develop, build, integrate, and test the optimum system based on the Government s preferred alternative concept. To do so, the program office must resource and plan projects, manage system design and development, prepare for production, ensure production readiness, and demonstrate the system s operational readiness. [A blue arrow stretches out of ADE-2A labeled: CONOPS, ORD, AoA/AA, ILSP, LCCE, APB, AP. A bubble appears to the right of the blue arrow, and fills with text incrementally as the narrator narrates.]

5 Narrator: The key activities that must be accomplished during the Obtain Phase are: Expand planning down to the project/acquisition type level Develop a Systems Engineering Life Cycle (SELC) Tailoring Plan Develop a Test & Evaluation Master Plan (TEMP) Refine existing acquisition documentation Conduct the major activities and reviews of the SELC Conduct Developmental Test & Evaluation (DT&E), one or more Operational Assessments (OAs), and Operational Test & Evaluation (OT&E) Plan for the production, deployment, and support of the system [The bubble fades out and is replaced (left half) by a yellow diamond labeled ADE-2B.] Narrator: Depending on the system, the Obtain Phase may include one or more ADE-2Bs, at which subprojects or types of acquisition are approved... [A blue arrow stretches out of ADE-2B, and another yellow diamond appears labeled ADE-2C.] Narrator:...and an ADE-2C, at which the Acquisition Decision Authority (ADA) assesses the program s readiness for Low Rate Initial Production (LRIP). [As the ADE-2B and 2C diamonds fade and the bubble reappears, a third blue arrow stretches out to the right of the bubble (labeled: OT&E Reports, Other Docs), and a fourth yellow diamond appears labeled ADE-3.] Narrator: Along with the quality and maturity of the program office s production, deployment, and support planning, the results of OT&E factor heavily in the ADA s ADE-3 decision whether or not to commit the Department s resources and authorize Full Rate Production (FRP). [All four diamonds return to their original locations, and the four phases of the ALF reappear.]

6 From ADE-2A to ADE-2B Between ADE-2A and ADE-2B, the program office prepares documentation for each type of acquisition the program requires (e.g. capital investment projects, enterprise services procurements) in preparation for ADE-2B. When acquiring services, the program office implements Service Level Agreements (SLAs) to specify what services the service provider will perform. When acquiring capital assets, the program office updates the APB to add cost, schedule, and performance targets for each project. The APB will contain a subsection for each project required to meet the capability need. With guidance from the DHS Office of the Chief Procurement Officer (OCPO), the program office will expand the Acquisition Plan (AP) to include the details of each acquisition project. At the same time, the program office prepares two new documents: the TEMP, which outlines the activities needed to verify system performance, and a SELC Tailoring Plan, which identifies the technical reviews and documentation required to manage the technical activities of the program. (A preliminary version of these documents may be drafted prior to ADE-2A.) page 5 of 32 ADE Acquisition Decision Event

7 The Systems Engineering Life Cycle The DHS SELC is a guiding framework that provides a common vocabulary, order, and description of system engineering activities for all DHS programs. Acquisition Management 001 The DHS Systems Engineering Life Cycle Guidebook ( ), establishes DHS's systems engineering methodology and its application. It also describes the SELC and its relationship to other DHS enterprise-wide processes (e.g., Acquisition Life Cycle Framework (ALF), Capital Planning and Investment Control (CPIC). The SELC is broken down into 9 major activities and includes several typical technical reviews. Select each major activity to learn more. Click here to view an enlargement. D Key SPR: Study Plan Review SER: Solution Engineering Review PPR: Project Planning Review SDR: System Definition Review PDR: Preliminary Design Review CDR: Critical Design Review IRR: Integration Readiness Review PRR: Production Readiness Review OTRR: Operational Test Readiness Review ORR: Operational Readiness Review PIR: Post Implementation Review An SELC Tailoring Plan must be developed that defines what major activities, tasks, and artifacts will be completed for the project. The SELC Tailoring Plan should reflect the unique characteristics of the project and provide the best opportunity to deliver the system effectively. Each major activity of the SELC includes a defined set of tasks that represent a logical unit of work. Each major activity has associated artifacts that capture the results of the tasks performed. The first major activity of the SELC, executed prior to the Obtain Phase, focuses on the larger acquisition program, whereas the remainder focus on the individual projects and systems associated with the program. Long Description page 6 of 32 The ALF consists of four phases: Need, Analyze/Select, Obtain, and Produce/Deploy/Support. Included in the four phases are six acquisition decision events (ADEs), numbered: 0, 1, 2A, 2B, 2C, and 3.

8 The SELC runs in parallel with the ALF and consists of one recommended, and nine major activities: Needs Analysis (a recommended pre-selc activity), Solution Engineering, Planning, Requirements Definition, Design, Development, Integration and Test (I&T), Implementation, Operations and Maintenance (O&M), and Disposition. Included are eleven technical reviews: SPR, SER, PPR, SDR, PDR, CDR, IRR, PRR, OTRR, ORR, and PIR. The SELC Solution Engineering activity aligns with the ALF Analyze/Select phase. The SELC major activities Planning, Requirements Definition, Design, Development, Integration and Test (I&T), and Implementation align with the ALF Obtain phase. SELC major activities are often iterative or concurrent in nature and are not strictly performed in a stepwise or sequential manor, hence the recursive loop shown for Requirements Definition, Design, Development and Integration and Test. SELC major activities Operations and Maintenance and Disposition align with the ALF Produce/Deploy/Support phase. Solution Engineering Engineer the program solution to ensure all alternatives are considered Planning Plan the project and acquire resources needed to achieve solution Requirements Definition Analyze user needs and document functional requirements Design Transform requirement into detailed system design Development Convert the system design into system Integration and Test Integrate with other systems; develop Certification & Accreditation Implementation System moved to production environment; production data has been loaded Operations and Maintenance The system is operated to carry out intended function Disposition The system is disposed

9

10 The Project Planning Review Technical reviews are held at appropriate points in the SELC to validate that technical risks are well managed and the acquisition is ready to advance. Defined entrance and exit criteria provide a basis for assessing progress at each SELC Review. For most programs, the first review conducted during the Obtain Phase is the Project Planning Review (PPR), conducted during the Planning Activity (prior to and in support of ADE-2B). The purpose of Planning is to validate that sufficient analysis and planning have been conducted to move to the Requirements activity of the SELC. All facets of the project are analyzed to ensure that the cost, scope, and schedule are technically feasible and acceptable to stakeholders. The PPR focuses on the foundational elements of the program (e.g., Work Breakdown Structure (WBS), Concept of Operations (CONOPS)), taking into account the executability of the program and the continuity and completeness of the program's acquisition documentation. The result of this review is an assessment of the program's readiness to proceed into the Requirements Definition activity. Click here to view an enlargement. D page 7 of 32 Long Description The ALF consists of four phases: Need, Analyze/Select, Obtain, and Produce/Deploy/Support. Included in the four phases are six acquisition decision events (ADEs), numbered: 0, 1, 2A, 2B, 2C, and 3. The SELC runs in parallel with the ALF and consists of one recommended, and nine major activities: Needs Analysis (a recommended pre-selc activity), Solution Engineering, Planning, Requirements Definition, Design, Development, Integration and Test (I&T), Implementation, Operations and Maintenance (O&M), and Disposition. Included are eleven technical reviews: SPR, SER, PPR, SDR, PDR, CDR, IRR, PRR, OTRR, ORR, and PIR. The SELC Solution Engineering activity aligns with the ALF Analyze/Select phase. The SELC major activities Planning, Requirements Definition, Design, Development, Integration and Test (I&T), and Implementation align with the ALF Obtain phase. SELC major activities are often iterative or concurrent in nature and are not strictly performed in a stepwise or sequential manor, hence the recursive loop shown for Requirements Definition, Design, Development and Integration and Test. SELC major activities Operations and Maintenance and Disposition align with the ALF Produce/Deploy/Support phase.

11 SELC Systems Engineering Life Cycle ADE Acquisition Decision Event

12 SELC Tailoring For one systems engineering life cycle framework to apply to all DHS programs, it must be flexible enough to adapt to the unique characteristics of each project (e.g., size, scope, complexity, risk). This flexibility comes from tailoring. The objective of tailoring is to effectively apply the SELC to a specific project or program in a way that balances the need for documentation and reviews with programmatic and technical risks. SELC tailoring can take several forms and may include the following: Combining SELC reviews and/or artifacts Creating new technical reviews (that are comparable to the typical ones) Scaling back the size and content of SELC artifacts Accepting existing or creating new documents with similar content in place of SELC artifacts Eliminating SELC artifacts that are not applicable Incorporating additional processes, tasks (to include technical reviews), or artifacts not required by the SELC, but needed for a specific project To develop the SELC Tailoring Plan, the Program Manager must interface with many stakeholders, including the program sponsor, the Program Accountability and Risk Management (PARM) Office, and, for information technology programs, the Chief Information Officer (CIO). The SELC Tailoring Plan is approved by the Executive Director, PARM, and the DHS CIO. Some documents are required by federal policy and may not be omitted during SELC tailoring. SELC Systems Engineering Life Cycle page 8 of 32

13 The SELC Tailoring Plan The results of tailoring are captured in the SELC Tailoring Plan. Select the "SELC TP" tab within the binder to learn more about the SELC Tailoring Plan. D page 9 of 32 Long Description Interactive three ring binder with selectable tabs. SELC Systems Engineering Life Cycle

14 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

15 Instruction/Guidebook : 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 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,

16 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 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. 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 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. 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

17 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 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 Appendix H: Operational Requirements Document contains ORD development guidance and a sample template.

18 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 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

19 Instruction/Guidebook 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 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.

20 Test & Evaluation and the TEMP As part of the Systems Engineering Process, one of the key program activities during the Obtain Phase is T&E. T&E is a vital part of a comprehensive strategy to reduce risk and measure progress. It is the principle tool used to verify system performance during development. That data gathered during T&E provides vital support for acquisition decisions. T&E is complex, time consuming, and critically important activity that requires careful planning. The results of a program's T&E planning are captured in the TEMP. Select the "TEMP" tab within the binder to learn more about the Test & Evaluation Master Plan (TEMP). D Long Description Interactive three ring binder with selectable tabs. page 10 of 32

21 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 , 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.

22 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

23 Instruction/Guidebook : 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 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,

24 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 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. 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 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. 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

25 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 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 Appendix H: Operational Requirements Document contains ORD development guidance and a sample template.

26 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 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

27 Instruction/Guidebook 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 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.

28 Updating Existing Acquisition Documentation In addition to SELC Tailoring plan and the TEMP, acquisition documents developed for earlier life cycle phases are updated and expanded during the Obtain Phase. Select each tab for additional information. AP ILSP LCCE APB Acquisition Plan (AP) The program's AP is expanded to include the tactical specifics for each project or service. The program office works with CPO or the Component Contracting Office to tailor the sections and content of the AP based on the unique conditions of each acquisition. The contracting officer ultimately will need to review the AP and accept or approve it before implementation. page 11 of 32 AP Acquisition Plan (AP) The program's AP is expanded to include the tactical specifics for each project or service. The program office works with CPO or the Component Contracting Office to tailor the sections and content of the AP based on the unique conditions of each acquisition. The contracting officer ultimately will need to review the AP and accept or approve it before implementation. ILSP Integrated Logistics Support Plan (ILSP) The ILSP must be rigorously updated as the system evolves through development, because the program office begins to implement the ILSP during the Obtain Phase. The updated ILSP also guides the assessment of the program's logistics readiness during ADEs as the program progresses through the Acquisition Review Process (ARP).

29 LCCE Life Cycle Cost Estimate (LCCE) The program office revises the LCCE to reflect changes to the program, analyze the impact of those changes, and make adjustments for differences between estimated and actual costs. APB Acquisition Program Baseline (APB) The APB is updated to include refined logistics and funding parameters based on the evolution of the ILSP and LCCE.

30 ADE-2A/2B: Approve the Acquisition ADE-2A/2B is a decision authorizing the execution of one or more of the program's acquisition projects. The ADA approves the updated APB and AP, ensuring there are sufficient resources (staffing and funding) and an appropriate schedule to execute the remainder of the Obtain Phase with acceptable risk. Any proposed services procurements will be checked against the following criteria by the Chief Information Officer (CIO) and/or the Chief Procurement Officer (CPO) at ADE-2B: Alignment with DHS strategic objectives, including the DHS Enterprise Architecture (EA) Common understanding of the service objectives between DHS and the Component Determination that the proposed acquisition does not duplicate other DHS services/acquisitions IOC and FOC dates are also established at ADE-2B (in the APB schedule). In some rare cases, multiple ADE-2B or ADE-3 reviews might be required, depending on the types of acquisition projects involved in the program. For example, an early, usable, deployable increment of a program may require its own ADE-3 prior to production. For stand-alone enterprise services acquisitions, ADE-1 and ADE-2A are not required. For acquisition programs, ADE-2A and ADE-2B may be combined (with approval) if appropriate. Each program will have one ADE-2A, but it may have multiple ADE-2Bs. page 12 of 32 ADE Acquisition Decision Event ADA Acquisition Decision Authority APB Acquisition Program Baseline AP Acquisition Plan

31 ADE-2B Approve projects within the program APB Acquisition Program Baseline ADE-3 Decide to produce and deploy the system ADE-1 Validate the need ADE-2A Approve the program

32 Knowledge Check For each description below, select the appropriate term to fill in the blank from the drop-down list provided. When you are finished, select Submit. The decision whether or not to authorize one or more of the program's acquisition projects. Acquisition Decision Event (ADE) 2B The guiding systems engineering framework for all DHS programs. Systems Engineering Life Cycle (SELC) Identifies the SELC major activities and technical management artifacts that will be prepared for the project. SELC Tailoring Plan Examines the program's foundation, including whether or not it can be executed as designed, and the completeness of its acquisition documentation. Project Planning Review Describes the activities that will be conducted to assess the system's technical performance and limitations. Test & Evaluation Master Plan Show my answer page 13 of 32 SELC System Engineering Life Cycle The Acquisition Decision Event (ADE)2B is the decision whether or not to authorize one or more of the program's acquisition projects. The Systems Engineering Life Cycle (SELC) is the guiding systems engineering framework for all DHS programs. The SELC Tailoring Plan identifies the SELC major activities and technical management artifacts that will be prepared for the project. The Project Planning Review examines the program's foundation, including whether or not it can be executed as designed, and the completeness of its acquisition documentation. The Test & Evaluation Master Plan describes the activities that will be conducted to assess the system's technical performance and limitations.

33 Recap: From ADE-2A to ADE-2B Review the concepts introduced in this topic: The DHS Systems Engineering Life Cycle (SELC) is a guiding framework that provides a common vocabulary, order, and description of system engineering activities for all DHS programs. The objective of SELC tailoring is to effectively apply the SELC to a specific project or program in a way that balances the need for oversight with programmatic and technical risks; the results of tailoring are captured in the SELC Tailoring Plan. Test & Evaluation (T&E) is part of a program's strategy to reduce risks and inform acquisition decisions, and it is the principle tool used to measure progress and verify system performance. T&E is a complex, time consuming, and critical activity that requires careful planning; the results of which are captured in the Test & Evaluation Master Plan (TEMP). Also updated and expanded during this phase: the Integrated Logistics Support Plan (ILSP), Life Cycle Cost Estimate (LCCE), Acquisition Program Baseline (APB), and Acquisition Plan (AP). The next topic is From ADE-2B to ADE-3. page 14 of 32

34 Introduction: From ADE-2B to ADE-3 The bulk of the development work is completed between ADE-2B and ADE-3. This includes: Contracting Design and Development SELC Reviews Prototyping Developmental Test & Evaluation (DT&E) Operational Assessment(s) Low Rate Initial Production (LRIP) (optional) Operational Test & Evaluation (OT&E) ILSP Implementation Production Planning The program office oversees these activities, typically through one or more development contracts, services contracts, and Inter Agency Agreements (IAAs). All acquisition documentation continues to evolve throughout this portion of the Obtain Phase to reflect decisions and changes in requirements and available resources. The LCCE is updated, the ILSP is finalized, and the bulk of the SELC Reviews are conducted. page 15 of 32 ADE-2B Approve projects within the program ADE-3 Decide to produce and deploy the system SELC Systems Engineering Life Cycle ILSP Integrated Logistics Support Plan

35 LCCE Life Cycle Cost Estimate

36 Contracting The program office works in conjunction with contracting to develop, solicit, award, and manage contracts. Design and Development Once the prime development contract is awarded, the contractor gets to work designing, prototyping, developing, testing, and evaluating the system. page 16 of 32

37 More SELC Reviews The following SELC Reviews are generally conducted during this portion of the Obtain Phase, between ADE-2B and ADE-3: Project Planning Review (PPR) System Definition Review (SDR) Preliminary Design Review (PDR) Critical Design Review (CDR) Integration Readiness Review (IRR) Production Readiness Review (PRR) Operational Test Readiness Review (OTRR) Operational Readiness Review (ORR) Each review evaluates technical readiness to move through the life cycle. These reviews give senior decision makers valuable technical insight so they can make more fully-informed acquisition decisions. Click here to view an enlargement. D Long Description page 17 of 32 The ALF consists of four phases: Need, Analyze/Select, Obtain, and Produce/Deploy/Support. Included in the four phases are six acquisition decision events (ADEs), numbered: 0, 1, 2A, 2B, 2C, and 3. The SELC runs in parallel with the ALF and consists of one recommended, and nine major activities: Needs Analysis (a recommended pre-selc activity), Solution Engineering, Planning, Requirements Definition, Design, Development, Integration and Test (I&T), Implementation, Operations and Maintenance (O&M), and Disposition. Included are eleven technical reviews: SPR, SER, PPR, SDR, PDR, CDR, IRR, PRR, OTRR, ORR, and PIR. The SELC Solution Engineering activity aligns with the ALF Analyze/Select phase. The SELC major activities Planning, Requirements Definition, Design, Development, Integration and Test (I&T), and Implementation align with the ALF Obtain phase. SELC major activities are often iterative or concurrent in nature and are not strictly performed in a stepwise or sequential manor, hence the recursive loop shown for Requirements Definition, Design, Development and Integration and Test. SELC major activities Operations and Maintenance and Disposition align with the ALF Produce/Deploy/Support phase.

38 SELC Systems Engineering Life Cycle ADE-2B Approve the projects within the program ADE-3 Decide to produce and deploy the system Project Planning Review (PPR) At the Project Planning Review (PPR), reviewers evaluate the team\'s planning products and the program\'s readiness to proceed to the Requirements Definition major activity of the SELC. System Definition Review (SDR) At the Systems Definition Review (SDR), reviewers evaluate the completeness of the system requirements and the program\'s readiness to proceed to the Design major activity of the SELC. Preliminary Design Review (PDR) At the Preliminary Design Review (PDR), reviewers assess the integrity of the high-level system design and ensure the team is ready to proceed to detailed design. Critical Design Review (CDR) At the Critical Design Review (CDR), the program office must demonstrate that its system design is complete and accurate. Reviewers examine the initial product baseline to make their determination. Integration Readiness Review (IRR) At the Integration Readiness Review (IRR), reviewers examine the results of the Development major activity, and ensure the system is ready to proceed to Integration & Test. Production Readiness Review (PRR) At the Production Readiness Review (PRR), reviewers validate that the system, as developed, meets the user\'s requirements, as defined. The PRR supports the Acquisition Decision Event-2C (ADE-2C) decision whether or not to authorize Low Rate Initial Production (LRIP). Operational Test Readiness Review (OTRR) At the Operational Test Readiness Review (OTRR), reviewers ensure the system is ready to begin Operational Test and Evaluation (OT&E).

39 Operational Readiness Review (ORR) At the Operational Readiness Review (ORR), reviewers examine the results of OT&E to determine whether the system is ready to move into production and (eventually) operation in the field.

40 Developmental Test & Evaluation DT&E is conducted throughout the engineering, design, and development process to assess progress towards meeting technical performance requirements. DT&E answers the question, "Did we build it right?" DT&E is usually performed by the contractor in a laboratory or test facility using components, assemblies, subsystems, and full scale prototypes. DT&E also helps identify and manage design risks, validate manufacturing process requirements, and certify readiness to proceed with OT&E. Though the contractor conducts DT&E in a controlled environment, the PM signs the TEMP in concurrence with the T&E strategy. page 18 of 32 PM Program Manager T&E Test and evaluation

41 Operational Assessment(s) Another tool for gauging a program's readiness for OT&E is an OA. An OA is an evaluation of a system's operational effectiveness and suitability, made by an independent operational test agent, based on test articles that are not fully representative of the final production version. This gives operational testers an opportunity to observe and influence the system as it develops. The OA is conducted prior to LRIP using prototypes, simulations, mockups, or engineering development models. An OA is one component of a program's overall test strategy, NOT a substitute for OT&E. It is typically used to gauge the program's readiness for OT&E. A program may choose to conduct more than one OA during development. page 19 of 32 OT&E Operational Test & Evaluation

42 ADE-2C (Optional) and LRIP If the acquisition involves large quantities of hardware or incremental deliveries of software (with capabilities), an additional decision event, ADE-2C, may be held to approve LRIP. LRIP is a phase of production in which a small initial batch of units is produced, allowing the user/sponsor to thoroughly test the system prior to FRP. At ADE-2C, the ADA reviews the results of DT&E to support the decision to move forward with LRIP. The ADA must also be convinced that the program office is adequately prepared and resourced to conduct LRIP, and that any exit criteria and/or actions specified in the ADE- 2B Acquisition Decision Memorandum have been satisfied. LRIP enables the contractor to obtain the tools, materials, and skills needed to prove out the production process. It generates production-representative articles, which are essential for valid operational testing. It also allows for smooth, continuous ramp-up from low rate to FRP after ADE-3 approval is obtained. page 20 of 32 DT&E Developmental Test & Evaluation ADE-2B Approve the projects within the program ADE-3 Decide to produce and deploy the system

43 Operational Test & Evaluation OT&E is a series of independent field tests conducted with typical users on full-scale, production-representative systems, under actual conditions, in a realistic environment. These tests are conducted to validate the system meets the user's performance requirements, key performance parameters (KPPs) as specified in the ORD, and is operationally effective and suitable. Rather than members of the program office, an independent Operational Test Agent (OTA) plans, coordinates, and conducts OT&E to guarantee the integrity of the results. This includes supervising development of the Operational Test and Evaluation section of the TEMP. The reports capturing the results of OT&E are used to evaluate the degree to which the system meets the user's requirements and can operate in the real world, and they factor heavily into the ADA's decision whether or not to authorize FRP at ADE-3. page 21 of 32 OT&E Operational Test & Evaluation TEMP Test & Evaluation Master Plan ADA\'s Acquisition Decision Authority\'s FRP Full Rate Production

44 ADE-3 Decide to produce and deploy the system

45 CHEM-Bot Program Progress Let s check on the progress of our CHEM-Bot program since the Analysis of Alternatives (AoA). Based on the report compiled by the AoA Study Team, Dr. Jeffries, CHEM-Bot PM, weighed the cost, schedule, technical performance tradeoffs, and associated risks of the three alternatives: the Joint Unmanned Ground Vehicle (JUGV), SENTRY, and ZeppelinBot. Dr. Jeffries recommendation was to integrate a state-of-the-art chemical sensor onto a track-mounted robot (based on the JUGV). Based on this preferred alternative, the CHEM-Bot program office prepared an Integrated Logistics Support Plan (ILSP), Life Cycle Cost Estimate (LCCE), Acquisition Program Baseline (APB), and Acquisition Plan (AP) while the U.S. Customs and Border Protection (CBP) sponsoring activity finalized an Operational Requirements Document (ORD) and Concept of Operations (CONOPS). Given the maturity of the program office s planning and the completeness of their acquisition documentation, the ADA granted the CHEM-Bot program approval to enter the Obtain Phase at ADE-2A in January Fiscal Year (FY) 12. page 22 of 32 ADE-2A Approve the program

46 Operational Effectiveness and Suitability The goal of OT&E is to determine whether the system is operationally effective and operationally suitable. Operational effectiveness is the ability of a system to accomplish a mission when operated by typical users in its planned operational environment. It answers the question, 'Can the system perform its intended tasks?' The CHEM-Bot, for example, is being acquired to detect airborne contaminants in U.S. seaports. If the CHEM-Bot's sensor is unable to accurately distinguish specified chemicals from other contaminants in the air in cargo holds of ships entering the ports, then the system will not be considered operationally effective. Operational suitability is the degree to which a system is deployable and sustainable in its operational environment. It takes into account personnel and logistics support considerations such as reliability, availability, maintainability, training, and safety. For example, the CHEM-Bot's intended operational environment is a U.S. seaport. If the robot's components are susceptible to the corrosive effects of sea water, then the system will not be operationally suitable. page 23 of 32 OT&E Operational Test & Evaluation

47 CHEM-Bot T&E Planning For each parameter below, select either Operationally Effective or Operationally Suitable from the drop-down list provided. When you are finished, select Submit. Require a crew of not more than 2 people to operate Operationally Suitable Achieve 95% accuracy detecting 18 chemical compounds Operationally Effective Operate in rain and fog Operationally Effective Ascend a 15 degree incline Operationally Effective Be transportable in a pickup truck Operationally Suitable Mean Time Between Failure (MTBF) of 32 hours Operationally Suitable Show my answer page 24 of 32 Operationally Effective Operational effectiveness is the ability of a system to accomplish a mission when operated by users in the planned operational environment. It answers the question, "Can the system perform its intended tasks?" Operationally Suitable Operational suitability is the degree to which a system is deployable and sustainable in its operational environment. It takes into account personnel and logistics support considerations such as reliability, availability, maintainability, training, and safety. Require a crew of not more than 2 people to operate: Operationally Suitable. Achieve 95% accuracy detecting 18 chemical compounds: Operationally Effective Operate in rain and fog: Operationally Effective Ascend a 15 degree incline: Operationally Effective Be transportable in a pickup truck: Operationally Suitable Mean Time Between Failure (MTBF) of 32 hours: Operationally Suitable

48 Acquisition Documentation A large number of acquisition documents must be prepared or updated throughout the Obtain Phase in preparation for the various ADEs, including ADE-3. The table below summarizes the required acquisition documentation throughout the life cycle. To see the latest information regarding the Acquisition Management Instruction/Guidebook, please visit the PARM website. Note, this is located behind the DHS firewall and is not accessible unless you are on DHSConnect. DHS APPROVED COMPONENT APPROVED Pre Acquisition Preliminary Mission Need Statement (P-M NS) For ADE 1 "Validate the Need" Capital Asset and Services Mission Need Statement (MNS) **** Capability Development Plan (CDP) Acquisition Documentation For ADE 2A "Approve the Acquisition" Capital Asset and Services Acquisition Program Baseline (APB) Integrated Logistics Support Plan (ILSP) Acquisition Plan * Life Cycle Cost Estimate (LCCE) *5 Operational Requirements Document (ORD) **** Concept of Operations (CONOPS) Analysis of Alternatives (AoA) or Alternatives Analysis (AA) For ADE 2B "Approve the Acq Types" Capital Asset Services For ADE 3 "Approve Production, Deployment and Support" Capital Asset Only APB APB APB ILSP Acquisition Plan * Life Cycle Cost Estimate (LCCE) *5 Test Evaluation Master Plan (TEMP) *** SELC Tailoring Plan ** Acquisition Plan * Service Level Agreement ILSP Acquisition Plan* LCCE *5 * AP Guide Sections: See Homeland Security Acquistion Manual (HSAM) for details ** SELC Tailoring Plan approved by the DHS OCIO and DHS APMD *** The TEMP is approved by the DHS Director Operational Test and Evaluation **** Non-Major MNS and ORDs (or equivalent) must be provided to the Office of Strategic Plans for information *5 LCCEs are validated by the Cost Analysis Division, Cost Estimating Baseline Documents are reviewed by CAD as part of LCCE development ADEs Acquisition Decision Events page 25 of 32 ADE-3

49 Decide to produce and deploy the system AP Acquisition Plan SELC System Engineering Life Cycle TEMP Test and Evaluation Master Plan MNS Mission Needs Statement LCCEs Life Cycle Cost Estimates

50 ADE-3: Approve Production, Deployment, and Support Once the program office has prepared all the required acquisition documentation, and successfully demonstrated the system through OT&E, the program may proceed to ADE-3. Questions to be answered at ADE-3: Has the system been tested in an operational environment? Have the requirements been met, the shortfalls addressed, and the system deemed operationally effective and suitable? Are the intended users trained and ready to accept the capability? Are the production processes mature? Are transition plans (if required) adequate? Is the system supportable? Has the program's sustainment and support planning been certified adequate (by the CAE)? Are resources available to support the execution of the plan? Is the program sufficiently resourced to accomplish the objectives in the APB and other implementation plans? Based on the results of technical reviews, OT&E, and a review of all required acquisition documents, the ADA may authorize the program to proceed to the Produce/Deploy/Support Phase. For hardware systems, full-rate production is authorized at ADE-3. For IT, the ADE grants the authority to deploy the system to the enterprise. If the system is not ready for deployment, the ADA will determine the actions required to make it ready and issue these in an Acquisition Decision Memorandum (ADM). page 26 of 32 OT&E Operational Test & Evaluation ADE-3 Decide to produce and deploy the system CAE Component Acquisition Executive APB Acquisition Program Baseline

51 ADA Acquisition Decision Authority IT Information Technology

52 Initial Operational Capability, Full Operational Capability, and Full Rate Production You've probably seen the terms Initial Operational Capability (IOC), Full Operational Capability (FOC), and Full Rate Production (FRP) in this course, but you may not be exactly sure what they mean or how they are related to each other. Select each tab for additional information. Full Rate Production Initial Operational Capability Full Operational Capability Following a successful ADE-3 for a hardware-centric system, the system is produced at full production rate and deployed to the field or fleet. This is known as Full Rate Production (as opposed to LRIP). FRP overlaps with operations and support activities conducted during the Produce/Deploy/Support Phase, since fielded systems are operated, supported, and sustained while FRP is ongoing. page 27 of 32 ADE-3 Decide to produce and deploy the system LRIP Low Rate Initial Production APB Acquisition Program Baseline APB Acquisition Program Baseline

53 Full Rate Production Following a successful ADE-3 for a hardware-centric system, the system is produced at full production rate and deployed to the field or fleet. This is known as Full Rate Production (as opposed to LRIP). FRP overlaps with operations and support activities conducted during the Produce/Deploy/Support Phase, since fielded systems are operated, supported, and sustained while FRP is ongoing. Initial Operational Capability IOC is one of at least two major program deployment milestones scheduled in the APB. IOC is attained when some fielding units and/or organizations scheduled to receive a system have received it and have the ability to use and maintain it. It's the point at which the first users begin using the system in the field. The date at which IOC is achieved often serves as the date the system is considered in service. The system may be fielded to a limited number of users with plans to roll out to all users over time. In some cases, IOC is achieved with LRIP units. Full Operational Capability FOC is another major program deployment milestone documented in the APB. In general, FOC is attained or declared when all fielding units and/or organizations scheduled to receive a system (by agreement between the program office and the user) have received it and have the ability to use and maintain it. In other words, when the program office has successfully deployed all the units it intended to deploy, it can declare FOC. This does not preclude additional users from obtaining the capability after FOC.

54 Knowledge Check For each description below, select the appropriate term to fill in the blank from the drop-down list provided. When you are finished, select Submit. At, the Acquisition Review Board (ARB) wants to see that the program office is ready to start LRIP and the results of DT&E support the decision to move forward. Acquisition Decision Event (ADE) 2C Once the program office has completed all necessary preparations for deployment and demonstrated system effectiveness and suitability through OT&E, the program may proceed to. Acquisition Decision Event (ADE) 3 is a phase of production in which a small initial batch of units is produced, allowing the user/sponsor to thoroughly test the system prior to FRP. Low Rate Initial Production (LRIP) is conducted in a controlled environment throughout the engineering, design, and development process to assess progress towards meeting technical performance requirements. Developmental Test & Evaluation (DT&E) is a series of independent field tests conducted by system users/operators with full-scale, productionrepresentative systems under actual conditions and in a realistic environment. Operational Test & Evaluation (OT&E) Operational Assessment (OA) overlaps with operations and support during the Produce/Deploy/Support Phase, since fielded systems are already being operated, supported, and sustained. Full Rate Production (FRP) Show my answer page 28 of 32 LRIP Low Rate Initial Production DT&E Development Test and Evaluation OT&E Operational Test and Evaluation

55 FRP Full Rate Production At Acquisition Decision Event (ADE) 2C, the Acquisition Review Board (ARB) wants to see that the program office is ready to start LRIP and the results of DT&E support the decision to move forward. Once the program office has completed all necessary preparations for deployment and demonstrated system effectiveness and suitability through OT&E, the program may proceed to Acquisition Decision Event (ADE) 3. Low Rate Initial Production (LRIP) is a phase of production in which a small initial batch of units is produced, allowing the user/sponsor to thoroughly test the system prior to FRP. Developmental Test & Evaluation (DT&E) is conducted in a controlled environment throughout the engineering, design, and development process to assess progress towards meeting technical performance requirements. Operational Test & Evaluation (OT&E) is a series of independent field tests conducted by system users/ operators with full-scale, production-representative systems under actual conditions and in a realistic environment. An Operational Assessment (OA) is an in-progress (any time during development) assessment of operational effectiveness and suitability. Full Rate Production (FRP) overlaps with operations and support during the Produce/Deploy/Support Phase, since fielded systems are already being operated, supported, and sustained.

56 CHEM-Bot's Obtain Phase Progress It's now August FY12, and the CHEM-Bot Program is progressing steadily through the Obtain Phase toward ADE-2B. If granted approval at ADE-2B to proceed, the RFP for a Cost-Plus-Incentive-Fee contract to provide the robot and integrate it with the chemical sensor will soon be released. After they have thoroughly analyzed the technical requirements, the prime contractor will develop prototypes of the subsystems, which will be available for early developmental testing an estimated three to six months after contract award. The first CHEM-Bot system will be deployed in the fourth quarter of FY15, along with all the necessary personnel who will be trained, ready, and equipped to operate and maintain it. Ultimately, a total of 500 systems will be produced and deployed to ports around the country. page 29 of 32 ADE-2B Approve projects within the program RFP Request for Proposal