ISA 201 Intermediate Information Systems Acquisition

Lesson 2 Joint Capabilities Integration Development System (JCIDS) Lesson Point of Contact: Name: Kevin Corcoran Phone: 619-524-4656 Email: Kevin.Corcoran@dau.mil Read Ahead: None Length of Presentation: Presentation: 1.25 hours Exercise: .75 hours TLO: Given a Department of Defense (DoD) Information Technology (IT) acquisition scenario, learner will assess whether objectives in planning documents are stated clearly enough to support IT capability development. (BL 5) ELO(s): ELO 7.1.3 Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. (Quiz)   MT3 - Capability planning is used to establish user requirements MT4 - “Getting the requirement right” at the front end is key to successful acquisition MT5 - The “IT Box” model to provide greater flexibility to incorporate evolving technologies, achieve faster responses from requirement validation and reduce subsequent trips to the JROC ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition (performance and critical) requirements from program outset. (Achieved in lesson exercise and practicum) MT6 - Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. MT7 - Key System Attributes (KSA) are considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). ELO 7.1.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. ELO 7.1.1.2 Presented an overview of the Defense Business System (DBS) Business Capability Definition Phase, identify the three principal questions the Functional Sponsor will define. Quiz Questions : 1. Which of the following describe how capability planning is key to successful acquisition? a. Capability planning establishes user requirements and helps “get the requirement right” (Correct – see slides 6 and 19) b. Capability planning builds a Systems Engineering Plan (SEP) and results in good engineering planning c. Capability planning creates the Life Cycle Sustainment Plan (LCSP) and helps manage “should cost” d. Capability planning is a way to conduct the Analysis of Alternatives (AOA) and determine the best value alternatives 2. What benefits does the Information Technology (IT) Box provide for the Program? a. Greater Flexibility to incorporate evolving technologies and achieve faster responses from the requirements validation (Correct – see slide 13) b. A footprint to build the next generation of communication equipment and incorporate best practices for IT systems c. An international standard collection (box) of lessons learned in developing and sustaining IT systems d. A method to manage limited flexibility through a highly structured methodology and a series of more and more onerous requirements validation process Which one of the following is a capability planning (JCIDS) document? TEMP BCD CDD IT Box Which of the following represents a Defense Business System? DoD financial system DoD National Security System Defense Commissary System Morale, Welfare, and Recreation system supporting the DoD Lesson 2 Joint Capabilities Integration Development System (JCIDS)

Today we will learn to: Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. Given a description of an Information Technology (IT) acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. Explore recent changes to DoD information technology systems capabilities management policies and procedures. Analyze the JCIDS impact on the development and acquisition of information technology systems from both weapon systems and business systems perspectives. Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. SLIDE INFORMATION***************************************************************************************Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.3 Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. *Policy / Directive / Standard / DTM ID: ********************************************************************************************************* Key Points: Competency 7 – Capability Planning MT3 - Capability planning is used to establish user requirements MT4 - “Getting the requirement right” at the front end is key to successful acquisition MT5 - The “IT Box” model to provide greater flexibility to incorporate evolving technologies and achieve faster responses from requirement validation MT6 - Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. MT7 - Key System Attributes (KSA) are considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). JCIDS & BCD

JCIDS Process Review Lesson Plan Information System (IS) Initial Capability Document (ICD) and the “IT Box” IT Box Exercise Capability Requirements Net-Ready (NR) Key Performance Parameter (KPP) Exercise Summary SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Content (Content or Exercise) *Supporting ELOs ID: *Policy / Directive / Standard / DTM ID: ********************************************************************************************************************************************************** Key Points: Lesson Overview – will begin with a JCIDS Process Review Key Questions to Ask and Anticipated Answers: How many have taken ACQ 101 within the last 12 months? For those who have taken it recently, you may recall that there were 68 lesson pages devoted to learning about the JCIDS Process. The next 6 slides will review the key processes, documents, and intentions for JCIDS. Then we will get into new material to discuss the unique aspects of JCIDS for Information Systems Then Capability Requirements Terms \ Definitions \ Acronyms: JCIDS & BCD

Department Process Interactions SLIDE INFORMATION ********************************************************************************* Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. *Policy / Directive / Standard / DTM ID: CJCSI 3170 ********************************************************************************** Key Points: The capability requirement portfolios managed under the JCIDS process inform and are informed by other processes and activities across the department. This chart stresses that JCIDS is central to the DoD process for developing future warfighting capabilities. Of the interacting processes and activities, requirements (JCIDS), acquisition (DAS), and resources (PPBE) are the most tightly interactive and must work in concert to ensure consistent decision making while delivering timely and cost effective capability solutions to the Warfighters. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: CONOPS – Concept of Operations CONPLAN – Contingency Plan DAS – Defense Acquisition Strategy DPG- Defense Planning Guidance GEF – Guidance for Employment of the Force GFM Global Force Management JOPES - Joint Operation Planning and Execution System NDS – National Defense Strategy NMS – National Military Strategy NSS – National Security Strategy OPLAN – Operational Plan PPBE – Planning, Programming, Budget and Execution QDR – Quadrennial Defense Review Capability requirement portfolios managed through JCIDS process inform and are informed by other processes and activities across the department. JCIDS & BCD

DoD Decision Support Systems JCIDS CJCS 3170.01 23 Jan 2015 SLIDE INFORMATION ********************************************************************************************************** *Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. *Policy / Directive / Standard / DTM ID: Key Points: A high level slide used to provide an overview of how the DAS, JCIDS and PPBE systems are intended to overlap and must work in concert to ensure consistent decision making. Capability planning requires DoD systems are developed by the effective interaction among three decision support systems:  The Joint Capabilities Integration and Development System (JCIDS) The Defense Acquisition System (DAS) The Planning, Programming, Budgeting, and Execution (PPBE) Process The Joint Capabilities Integration and Development System, which is "owned" and managed by the users of the systems being developed. JCIDS, DAS and PPBE systems must work together for the development of effective systems for the war fighting users. Within JCIDS process the war fighting users identify, document, and validate their desired joint warfighting capabilities. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: JCIDS - Joint Capabilities Integration and Development System; DAS – Defense Acquisition System; PPBE – Planning, Programming, Budgeting and Execution. PPBE DODD 7045.14 25 Jan 2013 DAS DODI 5000.02 07 Jan 2015 JCIDS, Defense Acquisition System (DAS), and PPBE are the most tightly interactive and must work in concert to ensure consistent decision making while delivering timely and cost effective capability solutions JCIDS & BCD

JCIDS and Acquisition (DoDI 5000.02, Jan 2015) SLIDE INFORMATION ********************************************************************************** *Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. *Policy / Directive / Standard / DTM ID: Key Points: DON’T SPEND TOO MUCH TIME ON THIS SLIDE. The key point is JCIDS touches DAS at each milestone. With the intention of getting the requirements right throughout the development, engineering and production process. The documents ICD, CDD, CPD will be discussed in the next slide. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: ICD – Initial Capabilities Document; CDD – Capability Development Document; CPD - Capability Production Document; MS - Milestone JCIDS & BCD 7

Law and Policy Title 10 Responsibilities (as modified by 2009 Weapon System Acquisition Reform Act and 2011 National Defense Authorization Act) The Joint Requirements Oversight Council (JROC) shall assist the VCJCS in making cost, schedule, and performance trades and prioritizing joint military requirements The JROC must: Consider input from Combatant Commanders on joint requirements Consider cost, schedule and performance tradeoffs in establishing requirements Set an Initial Operational Capability (IOC) schedule objective for each requirement SLIDE INFORMATION *********************************************************************************************** *Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. *Policy / Directive / Standard / DTM ID: ******************************************************************************************************** Key Points: The JCIDS Capability Planning process is grounded in Law. And is governed by Joint Requirements Oversight Council (JROC). The JROC is charged with shaping the force through prioritizing joint military requirements. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Joint Requirements Oversight Council (JROC) More Than Any Other Body … the JROC is charged with shaping the force JCIDS & BCD

JROC Desired End-State Take the Lead in Shaping the Force Debate the difficult issues and make difficult choices earlier Provide better upfront fidelity on cost/ schedule/ performance tradeoffs Provide more analytic rigor and risk/ portfolio analysis Provide stronger emphasis on prioritizing capability requirements Provide better end-to-end traceability to facilitate decision making: Missions—Requirements—Acquisition and DOTmLPF-P—Budget. Provide more dynamic/iterative process throughout a program’s lifecycle. (e.g., shifts, threat changes, etc.) SLIDE INFORMATION *********************************************************************************************** *Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. *Policy / Directive / Standard / DTM ID: ******************************************************************************************************** Key Points: The JROC is charged with shaping the joint forces, and need to make difficult choices throughout the requirements continuum Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Joint Requirements Oversight Council (JROC) Make the difficult choices throughout the requirements continuum… JCIDS & BCD

JCIDS Development Documents Joint Document Change Request (DCR)—DOTmLPF-P Change Recommendation – when a Joint Non-Materiel Solution is appropriate Initial Capabilities Document (ICD) (Milestone A)—Documents Capability Gaps and Identifies relevant operational performance attributes Capability Development Document (CDD) (Milestone B)—Defines Performance Requirements to Achieve the Capability Capability Production Document (CPD) (Milestone C)—Documents Authoritative, Testable Capabilities SLIDE INFORMATION *********************************************************************************** Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. *Policy / Directive / Standard / DTM ID: CJCSI 3170.01H ********************************************************************************** Key Points: JCIDS capability requirements documents serve as a means for Sponsors to document new or modified capability requirements and associated capability gaps, along with other relevant information, for review and validation. The ICD will describe the initial Operational performance attributes. The CDD will define the performance requirements (e.g. KPPs, KSAs, etc.) and the CPD will document the testable capability to be delivered. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Key Performance Parameter (KPP) – discussed in a later slide Key System Attribute – discussed in a later slide JCIDS & BCD

Lesson Plan Status JCIDS Process Review Information System (IS) Initial Capability Document (ICD) and the “IT Box” IT Box Exercise Capability Requirements Net-Ready (NR) Key Performance Parameter (KPP) Exercise Summary SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Content (Content or Exercise) *Supporting ELOs ID: *Policy / Directive / Standard / DTM ID: ********************************************************************************************************************************************************** Key Points: Lesson Overview – will begin with a JCIDS Process Review Key Questions to Ask and Anticipated Answers: How many have taken ACQ 101 within the last 12 months? For those who have taken it recently, you may recall that there were 68 lesson pages devoted to learning about the JCIDS Process. The next 6 slides will review the key processes, documents, and intentions for JCIDS. Then we will get into new material to discuss the unique aspects of JCIDS for Information Systems Then Capability Requirements Terms \ Definitions \ Acronyms: JCIDS & BCD

Information Systems (IS) Requirements Acquisition Process SLIDE INFORMATION ************************************************************************************************************* Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. *Policy / Directive / Standard / DTM ID: JCIDS Manual ************************************************************************************************************ KEY Point: Information System (IS) ICDs implement the “IT Box” model, discussed later, to provide IS programs greater flexibility to incorporate evolving technologies, and achieve faster responses from requirement validation processes than is typical for other kinds of materiel or non-materiel solutions. Once Information Systems (IS) ICD approved, then program office manages Capability Drops (CD) to deliver the capability in “chunks” Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: (1) IS ICDs implement the “IT Box” model, outlined in this section, to provide IS programs greater flexibility to incorporate evolving technologies, and achieve faster responses from requirement validation processes than is typical for other kinds of materiel or non-materiel solutions. (2) The “IT Box” model calls for fewer iterations of validating documents through the JCIDS process by describing the overall IS program in the IS ICD, and delegating validation of detailed follow-on requirement and solution oversight to a flag-level organization other than the JROC or JCB. (a) Using identified measures of effectiveness (MOEs), initial minimums are used instead of thresholds/objectives, allowing for rapid capability development within specified funding limits. (b) CDDs and CPDs are not required as successor documents to an IS ICD. An example of Sponsor documents used for managing follow-on efforts is provided later in this section, but is not intended to limit potential flexibilities provided by the IS ICD, or a previously validated ICD or CDD which the validation authority has approved for transition to the IT Box model. (3) IS ICDs are used to document capability requirements and associated capability gaps where the intended solution approach involves research, development, and acquisition of applications system software, and the projected software development costs exceed $15 million. IS with development costs less than $15 million are not subject to JCIDS process. The Initial Capabilities Document (ICD) is developed in a new format tailored to Information System (IS) capabilities Following the Materiel Development Determination (MDD), one or more Requirements Definition Packages (RDPs) are developed to further refine the requirements for the needed capabilities The RDP is further broken down into Capability Drops (CDs) to deliver individual “chunks” of capability The results of the CD development are released incrementally through Fielding Decisions JCIDS & BCD

IS Requirements/Acquisition Process SLIDE INFORMATION ***********************************************************************************************************Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. *Policy / Directive / Standard / DTM ID: ********************************************************************************************************** KEY Point: Another view to show the JROC approves the Information Systems (IS) ICD, then program office manages Capability Drops (CD) through their Component Program provides further definition of capabilities through Requirements Definition Packages (RDP) / Capability Drops (CD) Acronyms: CD – Capability Drop; CP – Capability Package; RDP – Requirement Development Package JCIDS & BCD

“IT Box” applied to IS ICD SLIDE INFORMATION******************************************************************* *Slide Type: Content (Content *Supporting ELOs ID: ELO 7.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. *Policy / Directive / Standard / DTM ID: JCIDS Manual ********************************************************************************************************************************************************** KEY Points: The IT Box Purpose: The purpose of the “IT Box” is to describe the overall bounds of an IT program in order to facilitate program initiation, greater flexibility to incorporate evolving technology, and achieve faster responses from the requirements validation (by reducing subsequent return trips to the JROC / managing requirements at service level) The IT Box boundaries describe: 1. Identify the flag-level oversight body, the chair, and the organizations represented. 2. Define the proposed Capability Requirements in terms of Measures of Effectiveness (MOEs). Also, define proposed capability gaps in terms of the difference between the proposed capability and similar existing capabilities, if any. 3 / 4. Show estimated sustainment, development and integration costs for the life cycle of the program. Break out into annual estimates for Hardware and Software. Key Points of the IT Box are. it allows for no need to return to JROC unless new core capabilities expenditures exceed ROM estimate by xx% or fail to meet performance requirements further definition of capabilities through Rqmts Definition Packages (RDP) / Capability drops Additional Info: This is the initial effort by the users / war fighters to refine the JCIDS process for Information Technology in recognition of the rapid changes / improvements (a good time to talk about Moore’s Law – every 18-24 months speed doubles) The four sides of the “IT Box” are intended to present and frame the complete program for JCB and JROC members using one slide. The information covers organization and oversight of the program, hardware refresh and system enhancements, integration, application and system software development, and KPP. These four areas should provide a clear understanding to the JCB and JROC that the program has an oversight body providing governance and protection of stakeholder interests; has anticipated milestones for insertion of improved technology, is fully funded for hardware and software development over the lifecycle of program, and has appropriate, measurable and testable KPPs. a. Key Performance Parameters (KPPs). The KPPs should represent the initial level of performance required for the entire IT program. b. Requirements Organization and Oversight. The objective is to ensure appropriate requirements governance throughout the lifecycle of the program. This body will determine the schedule and content of the releases of capability based on collaboration between the users and the program manager. (1) Name the Flag-level body that holds authority over and provides governance for requirements for this IT program. (2) Identify the Chair of the oversight body. (3) Identify the organizations represented on this body. This should include all stakeholders to ensure all interests are represented, including the acquisition community to provide advice on technical feasibility, cost and schedule. c. Hardware Refresh and System Enhancements & Integration: (1) Identify the total planned program cost for delivering the capability. (2) Identify the plan and potential cost for hardware and system integration. Identify the plan and cost for technology refresh per fiscal year. d. Applications and System Software Development and Acquisition: (1) Identify the level of effort funding which will be used for the software development effort per fiscal year. (2) Identify the total program costs for application and system software development and/or integration. Do not describe as fiscal year since these items should be a flat rate over the lifetime of the program, i.e., $8M per year. (3) Identify how often new releases will be delivered for enhanced or new capabilities. The RDP is a first level decomposition of one or more capability requirements in the IS ICD, and is co-developed between the operational user (or representative) and the program office. The purpose of the “IT Box” is to describe the overall bounds of an IT program in order to facilitate program initiation, greater flexibility to incorporate evolving technology, and achieve faster responses from the requirements validation. No Return to JROC unless new core capabilities Return if expenditures exceed ROM estimate by xx% or fail to meet performance requirements Further definition of capabilities through Rqmts Definition Packages / Capability Drops JCIDS & BCD

Applicability of the JCIDS IT Box Efforts where an IT Box may be considered: JROC Gatekeeper oversight (Life cycle program costs ≥ $15 million) Hardware: All hardware associated with an IS-ICD must be COTS/GOTS. Hardware modifications are restricted to those necessary for system integration and enhancements to meet capability requirements. Includes periodic refresh through lifecycle. Software : Development, integration, and acquisition of customized applications, including commercial IS capability solutions with integrated, DoD-specific performance characteristics/standards. Includes continued development and deployment through lifecycle IT Box is NOT appropriate where: Software is embedded as a subset of a capability solution developed under other validated capability requirement documents. IT capability gap is better addressed by DBS process SLIDE INFORMATION ************************************************************************************************************* *Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.1 Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. *Policy / Directive / Standard / DTM ID: CJCS 3170 JCIDS Manual **************************************************************************************************************** KEY Points: (From JCIDS Manual page D-29 to D-30) -- The purpose of an IS-ICD is focused on facilitating more efficient and timely software development efforts. (1) The purpose of an IS-ICD is focused on facilitating more efficient and timely software development efforts, and is not appropriate for hardware development efforts or capturing capability requirements which span a broad scope of combined hardware, software, and/or DOTmLPF-P efforts. (a) The IS-ICD is a variant of the regular ICD, implementing the “IT Box” model outlined in this section. IS-ICDs streamline the requirements process relative to IS efforts by delegating requirements oversight and document formats for subsequent documents as identified in the IS-ICD. This provides IS programs greater flexibility to incorporate evolving technologies and achieve faster responses from requirement validation processes than is typical for other kinds of materiel or non-materiel solutions. (b) The document serves as the basis for validation by the appropriate validation authority identified in Enclosure F of this manual. Applicability of any potential streamlining of acquisition processes is at the discretion of the MDA in accordance with references aa and bb. (2) IS-ICDs are appropriate for: (a) The procurement or modification of GOTS/COTS IS products from domestic or international sources, or the development of dual-use technologies. (b) The additional production or modification of previously developed U.S. and/or allied /partner-nation / other US government agency/department IS products. (c) Development, integration, and acquisition of customized application software, including commercial IS capability solutions with integrated, DoD-specific performance characteristics/standards. (d) All hardware associated with an IS-ICD must be COTS/GOTS. Hardware modifications are restricted to those necessary for system integration and enhancements to meet capability requirements specified in the IS-ICD, and hardware refresh due to obsolescence. (e) Approaches where the capability solution involves research, development, and/or acquisition of applications systems software, and the projected life cycle costs exceed $15 million. IS-ICDs with life cycle costs less than $15 million may be submitted for review and validation if validated requirements are needed to support budgetary requests or other purposes. (3) IS-ICDs are NOT appropriate for: (a) Software embedded as a subset of a capability solution developed under other validated capability requirement documents. In this case, the software requirements are validated as part of the capability requirements for the overall capability solution. (b) Software requiring a host platform, such as a manned or unmanned vehicle, which does not yet have validated capability requirement documents. In this case, the software requirements can be included in the capability requirements of the host platform, or as a separate IS-ICD submitted after validation of the host platform capability requirement documents. (c) Increases in quantities of previously fielded IS without modification, which are not addressed by an IT Box. These increased quantities may be addressed by a DCR. Increases in quantity which remain within the scope of a previously validated IT Box, may be accomplished without revalidation. (d) Requirements for DBS capabilities defined and acquired in accordance with references bb and lll. (4) In cases where the potential for use of the IT-Box construct is unclear or in dispute, the Joint Staff Gatekeeper, in consultation with the validation authority as needed, will determine whether an ICD or IS-ICD will be used. JCIDS & BCD

JTAMS IT Box Read JCIDS Manual page D-29-33 (10 minutes) Individually teams obtain consensus on the significance of their side of the box (5 minutes) Team 1—Organization and Oversight; What is the purpose? What is the significance to a program? Team 2 —Capabilities and Initial Minimum Values; What is the purpose? What is the significance to a program? Team 3—Hardware Refresh and System Enhancements & Integrated Cost Controls; What is the purpose? What is the significance to a program? Team 4—Application and Software Development Cost Controls; What is the purpose? What is the significance to a program? Team 5—Answer: What does the IT Box provide the program? Discuss (10 minutes) SLIDE INFORMATION *********************************************************************************************************Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: ELO 7.1.3 Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. MT3 Capability planning is used to establish and track user requirements MT4 “Getting the requirement right” at the front end is key to successful acquisition MT 5 The “IT Box” model to provide greater flexibility to incorporate evolving technologies and achieve faster responses from requirement validation *Policy / Directive / Standard / DTM ID: ******************************************************************************************************** Purpose: Expose students to scenario and IT Box / IS ICD; and critically think about “why” boundaries being used Team 1 – Flag Oversight = Identify the proposed flag-level oversight body, the chair of that body, and the organizations represented on the body to receive delegated requirements oversight duties, including approval of increases to capabilities above initial minimum values within the bounds of the IT Box. – (Discussion point - group more adaptable to changing requirement priorities) Team 2 – KPPs / KSA = NR KPP, System Availability, Materiel Availability – (Discussion point - key requirements for the user / war fighter - The IT Box model uses initial minimum values in place of initial objective values so that the baseline capability is clearly specified, and the delegated oversight body has flexibility to further develop capabilities without revalidation of the capability requirement document.) Team 3 – Estimated Sustainment Cost = Discussion point - bound cost, put in other terms war fighting community values this capability but not at any cost Team 4 – Software Development & Integration = Discussion point - bound cost, put in other terms war fighting community values this capability but not at any cost Team 5 – Answer: What does the IT Box provide the program? Answer = Greater Flexibility to incorporate evolving technologies and achieve faster responses from the requirements validation (Also a quiz question) JCIDS & BCD

IT BOX Exercise SLIDE INFORMATION*******************************************************************************************Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: ELO 7.1.3 Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. MT3 Capability planning is used to establish user requirements MT4 “Getting the requirement right” at the front end is key to successful acquisition MT 5 The “IT Box” model to provide greater flexibility to incorporate evolving technologies and achieve faster responses from requirement validation *Policy / Directive / Standard / DTM ID: JCIDS Manual page D-30-33 ************************************************************************************************************ Purpose: Expose students to scenario and IT Box / IS ICD; and critically think about “why” boundaries being used Team 1 – Flag Oversight = Identify the proposed flag-level oversight body, the chair of that body, and the organizations represented on the body to receive delegated requirements oversight duties, including approval of increases to capabilities above initial minimum values within the bounds of the IT Box. – (Discussion point - group more adaptable to changing requirement priorities) Team 2 – KPPs / KSA = NR KPP, System Availability, Materiel Availability – (Discussion point - key requirements for the user / war fighter - The IT Box model uses initial minimum values in place of initial objective values so that the baseline capability is clearly specified, and the delegated oversight body has flexibility to further develop capabilities without revalidation of the capability requirement document.) Team 3 – Estimated Sustainment Cost = (Discussion point - bound cost, put in other terms war fighting community values this capability but not at any cost) Team 4 – Software Development & Integration = $13.9M – (Discussion point - bound cost, put in other terms war fighting community values this capability but not at any cost) Team 5 – Answer: What does the IT Box provide the program? Answer = Greater Flexibility to incorporate evolving technologies and achieve faster responses from the requirements validation (Also a quiz question) JCIDS & BCD

Capability Requirements Lesson Status Plan JCIDS Process Review Information System (IS) Initial Capability Document (ICD) and the “IT Box” IT Box Exercise Capability Requirements Net-Ready (NR) Key Performance Parameter (KPP) Exercise Summary SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Content (Content or Exercise) *Supporting ELOs ID: *Policy / Directive / Standard / DTM ID: ********************************************************************************************************************************************************** Key Points: Lesson Overview – will begin with a JCIDS Process Review Key Questions to Ask and Anticipated Answers: How many have taken ACQ 101 within the last 12 months? For those who have taken it recently, you may recall that there were 68 lesson pages devoted to learning about the JCIDS Process. The next 6 slides will review the key processes, documents, and intentions for JCIDS. Then we will get into new material to discuss the unique aspects of JCIDS for Information Systems Then Capability Requirements Terms \ Definitions \ Acronyms: JCIDS & BCD

Requirements Why discuss requirements? Where do we get requirements? ICD, IS-ICD, CDD, IS-CDD (User defined) Policy (e.g. JCIDS Manual, Cybersecurity) Others? SLIDE INFORMATION ************************************************************************************************************ Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. MT6 Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. MT7 Key System Attributes (KSA) are considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). *Policy / Directive / Standard / DTM ID: ***********************************************************************************************************Questions: Why discuss requirements? --- goal is to let the students lead themselves into the so-what for an IT Acquisition person to know the requirements early in a program. Suggested resources: 1. “Positive and Negative Innovations in Software Engineering”, 24 Dec 2006, Capers Jones is an abstract that shows the cost of not understanding the requirements. In the abstract, Capers Jones lists Thirty Software Engineering Issues that have stayed constant for 30 years. The top 3 are: 1. Initial requirements are seldom more than 50% complete. 2. Requirements grow at about 2% per calendar month during development. 3. About 20% of initial requirements are delayed until a second release. 2. MAJOR AUTOMATED INFORMATION SYSTEMS: Selected Defense Programs Need to Implement Key Acquisition Practices (GAO-14-309) What GAO Found Of the 15 selected Department of Defense (DoD) major automated information system (MAIS) programs, 13 had cost information available (2 did not, due to revisions to requirements and changes in scope). Of these 13 programs, 11 experienced changes in their cost estimates, including 7 that experienced increases ranging from 4 to 2,233 percent and 4 that experienced decreases ranging from 4 to 86 percent. Two programs remained unchanged in their cost goals. Additionally, of 14 programs that had schedule information available (1 did not due to revisions to requirements), 13 experienced schedule changes—including 12 that had slippages ranging from a few months to 6 years, and 1 that accelerated its schedule. One program remained on schedule. Further, of 11 programs that had system performance data available, 3 programs met their system performance targets, while 8 did not fully meet their targets. What GAO Recommends GAO recommends that DoD direct the programs to address respective weaknesses in their risk management, requirements management, and project monitoring and control practices. Where do we get requirements? 1. User defined … should be able to tie back to our discussion of IT Box 2. Policy such as JCIDS Manual (link will take you to the JCIDS Web Page – NOTE: will need a CAC to be able to access) -- page D-A-2 discusses six (6) “Mandatory” KPPs Force Protection (FP). Survivability. Sustainment. Net-Ready (NR). Training. Energy. GAO reports that selected MAIS programs had significant cost and schedule changes and “recommends that DoD direct the programs to address respective weaknesses in their risk management, requirements management.” GAO 14-309 JCIDS & BCD

DoD Definitions and Explanations Requirement—A capability which is required to meet an organization’s roles functions, and missions in current or future operations. Note: a requirement is considered ‘draft’ or ‘proposed’ until validated by the appropriate authority. And is established through the capability planning process. Capability—The ability to execute a specific course of action. Capability Gap—The inability to execute a specified course of action. SLIDE INFORMATION ***********************************************************************************************************Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. MT6 Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. MT7 Key System Attributes (KSA) are considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). *Policy / Directive / Standard / DTM ID: ********************************************************************************************************** Key Points: This slide provides an understanding of the ‘bread & butter’ of what JCIDS is all about. 1) Requirement -- this is the actual ‘capability’ required (or requested) to execute the specified course of action (BLACK LINE ABOVE) Capability -- this is the current ability to execute the specified course of action (BLUE LINE ABOVE). Sometimes the requirement & capability are co-equal. In most cases, however, they are not co-equal and thus the JCIDS process works to fill that ‘capability gap’  the difference btw the current capability and the necessary requirement. Capability Gap -- this is the inability to execute the specific course of action (GREEN LINE ABOVE). Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: JCIDS & BCD

Operational Performance Attributes Attributes Necessary to Design a Proposed System Establish a Performance Baseline Guide Development and Demonstration Guide Development of Key Performance Parameters (KPPs) for Inclusion in Capabilities Development Document SLIDE INFORMATION ***************************************************************************************************************Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. MT6 Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. MT7 Key System Attributes (KSA) are considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). *Policy / Directive / Standard / DTM ID: JCIDS Manual PD-A-1 **************************************************************************************************************Key Points: The ICD must describe capability requirements in terms of the required operational attributes with appropriate qualitative parameters and metrics, e.g., outcomes, time, distance, effect (including scale), obstacles to be overcome, and supportability. Indicate the minimum value below which the capability will no longer be effective. “TBD” values are not allowed. These operational attributes are “mission” related, not specific to a certain solution. These attributes are uses as measures of effectiveness (MOE) during the AoA to compare alternative solutions. Those associated with the preferred solution, or the solution selected by the acquisition milestone decision authority, will evolve into more detailed KPPs for inclusion in the CDD during the Technology Development phase. The CDD provides the operational performance attributes necessary for the acquisition Program Manager and the acquisition community to design a proposed system and establish a program baseline. The CDD identifies the performance attributes, including Key Performance Parameters (KPPs), that will guide the development and demonstration of any proposed increments in the acquisition strategy. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: JCIDS & BCD

Key Performance Parameters (KPPs) Performance Attributes of a System Critical To Develop an Effective Military Capability KPPs Must be Measurable, Testable, and Quantifiable in a Practical and Timely Manner Enable feedback from T&E; support decision making Mandatory KPPs Force Protection, Survivability, Sustainment, Net Ready, Training, Energy SLIDE INFORMATION *************************************************************************************************************Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. MT6 Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. MT7 Key System Attributes (KSA) are considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). *Policy / Directive / Standard / DTM ID: JCIDS Manual Page D-A-1 ************************************************************************************************************Key Points: Performance attributes of a system considered critical to the development of an effective military capability. The number of KPPs identified by a Sponsor should be kept to a minimum to maintain program flexibility. Failure of a system to meet a validated KPP threshold/initial minimum rescinds the validation, brings the military utility of the associated system(s) into question, and may result in a reevaluation of the program or modification to production increments. The JROC validates KPPs for JROC Interest documents. The JCB validates KPPs for JCB Interest documents. The Sponsor (DoD Component) validates KPPs for Joint Integration, Joint Information, and Independent documents. In cases where it is necessary to change validated KPPs, such as for cost, technology, production, development, or other issues that prevent meeting the threshold of the KPP, the Sponsor may request changes to the previous validation by contacting the Gatekeeper. In some cases, the original validation will specify if there is a delegated validation authority for post-validation KPP or KSA changes. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: Failure to Meet a KPP Brings the Military Utility of the System into question. JCIDS & BCD

Key System Attributes (KSAs) Attributes or Characteristics Considered Essential to Achieving a Balanced Solution Not Critical Enough to be Selected as a KPP Must be Measurable, Testable and Quantifiable Identified by the Sponsor; Should be Kept to a Minimum Sponsor Senior Leadership can Change a KSA SLIDE INFORMATION ***************************************************************************************************************Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. MT6 Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. MT7 Key System Attributes (KSA) are considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). *Policy / Directive / Standard / DTM ID: JCIDS Manual Page D-A-1 **************************************************************************************************************Key Points: Attributes or characteristics considered essential to achieving a balanced solution/approach to a system, but not critical enough to be designated a KPP. KSAs must be measurable, testable, and quantifiable. KSAs are specified by the Sponsor. The number of KSAs identified by a Sponsor should be kept to a minimum to maintain program flexibility. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: JCIDS & BCD

Requirements Tradeoffs Finding the balance between: CCMD near-term requirements to support CONPLANs and current missions and Services’ long range vision & investment plans Versatile, joint systems Systems optimized for service missions Growing demands Fiscal & political constraints Geographic specificity Worldwide applicability Ambitious requirements Achievable acquisition strategy Quantity matters Quality (High-end capabilities) COST PERFORMANCE (acceptable risk) SLIDE INFORMATION ***************************************************************************************************************Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. MT6 Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. MT7 Key System Attributes (KSA) are considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). *Policy / Directive / Standard / DTM ID: ************************************************************************************************************** Key Points: Bottom Line: JCIDS is the process by which DoD identifies, assesses, and prioritizes what capabilities the military requires to fulfill its mission. Requirements identified through JCIDS can be addressed in a number of ways, including changes in doctrine, training, organization, or the acquisition of a new system. Risk – defined as likelihood of an occurrence and the consequence of the occurrence. The JCIDS Manual (page D-A-2) defines Tradespace as the difference between threshold and objective values sets trade space for balancing multiple KPPs, KSAs, and APAs while remaining above the threshold values. Advances in technology or changes in approved Service and joint concepts may result in proposals to change threshold and objective values in future increments of a capability solution. Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: CCMD – Combatant Commander CCMD: Combatant Command CONPLAN: Contingency Plans JCIDS & BCD

Net Ready KPP Exercise You have been asked to draft the Net Ready (NR) KPP, and your industrious “new guy” found a previous version of the NR KPP as a starting point Review the CONOPS (in the IS ICD) and as a team identify 2 recommended changes to the NR-KPP SLIDE INFORMATION *************************************************************************************************************Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: ELO 7.1.3 Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. MT4 “Getting the requirement right” at the front end is key to successful acquisition ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. MT6 Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. MT7 Key System Attributes (KSA) are considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). *Policy / Directive / Standard / DTM ID: ************************************************************************************************************ Mandatory KPPs. In addition to KPPs, KSAs, and APAs essential to the capability solution being developed, Sponsors shall address the KPPs detailed in the JCIDS Manual pages D-A-2 to D-A-5 JCIDS & BCD

JTAMS MRES NR KPP Attributes Threshold Objective Enter and be Managed in the Network: Network: SIPRNET —Measure: Time to connect to an operational network from power up —Communication Connectivity —2 minutes —Continuous —2 Days Exchange Information Information Element: Target Data —Measure: Dissemination of Mission Information and physical data —Measure: Latency of mission information and physical data —10 hours —5 seconds —5 hours —2 seconds *** SEE INSTRUCTOR ONLY SLIDE INCLUDED (HIDDEN) AND THE NOTES BELOW*** SLIDE INFORMATION ************************************************************************************************************Slide Type: Exercise (Content or Exercise) *Supporting ELOs ID: ELO 7.1.3 Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. MT4 “Getting the requirement right” at the front end is key to successful acquisition ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. MT6 Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. *Policy / Directive / Standard / DTM ID: *********************************************************************************************************** Elements of JTAMS MRES Net Ready KPP extracted from the RDP From CONOPS Summary (page 1 of JTAMS MRES IS ICD) JTAMS. JTAMS is an integral system within JRATS. JTAMS shall provide interoperable, integrated, Near Real Time (NRT) logistics management capabilities for the Joint Command and Control System (JCCS), Joint Unmanned Ground Vehicle (JUGV) and the Joint Unmanned Air Vehicle (JUAV). In addition JTAMS shall provide integrated training and mission rehearsal which allows operators to practice missions in an environment that replicates their real world operations.   JTAMS - MRES. MRES is an integral system within JTAMS. MRES shall provide integrated training and mission rehearsal which allows operators to practice missions in an environment that replicates their real world operations. MRES shall provide for stand-alone mission practice for individual systems and integrated tactical rehearsal for multiple unmanned systems. There are at least 4 issues (use build to walk through each issue): “2 Days” Objective should be a better (or equal to) “quality” goal than the Threshold (“2 minutes” ) … 2. “Continuous” might be ambiguous … and may be very expensive. PSM recommendation is to use "continual" versus "continuous". Continual means "frequently recurring; always happening" while continuous is "forming an unbroken whole; without interruption". So, you will not be communicating every second, but frequently and regularly. 5 hours to exchange information would not be considered Near Real Time (NRT) 10 hours to exchange information would not be considered NRT 5. (BONUS DISCUSSION if there is time) - Communication is something that is very hard to measure. Any measure tends to be about how many communication events, which is not necessarily meaningful (I can have lots of notices/emails/meetings - they can actually detract from productivity if they are not useful). A communication measure should be about communicating useful, relevant info in a timely manner. Really, really hard to measure. JCIDS & BCD

Capability Requirements Lesson Plan Status JCIDS Process Review Information System (IS) Initial Capability Document (ICD) and the “IT Box” IT Box Exercise Capability Requirements Net-Ready (NR) Key Performance Parameter (KPP) Exercise Summary SLIDE INFORMATION*************************************************************************************************************************** *Slide Type: Content (Content or Exercise) *Supporting ELOs ID: *Policy / Directive / Standard / DTM ID: ********************************************************************************************************************************************************** Key Points: Lesson Overview – will begin with a JCIDS Process Review Key Questions to Ask and Anticipated Answers: How many have taken ACQ 101 within the last 12 months? For those who have taken it recently, you may recall that there were 68 lesson pages devoted to learning about the JCIDS Process. The next 6 slides will review the key processes, documents, and intentions for JCIDS. Then we will get into new material to discuss the unique aspects of JCIDS for Information Systems Then Capability Requirements Terms \ Definitions \ Acronyms: JCIDS & BCD

Review of the Deliberate JCIDS Process Materiel Solutions Initial Capabilities Document (ICD) Information System (IS) ICD Capability Development Document (CDD) Capability Production Document (CPD) Non-Materiel Solutions—Joint DOTmLPF-P Change Recommendation (DCR) Operational Requirements Development is a Team Effort; All Stakeholders Should be Involved; Involve the User in Technical Requirements Development SLIDE INFORMATION *************************************************************************************************************Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.3 Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. MT3 Capability planning is used to establish user requirements MT4 “Getting the requirement right” at the front end is key to successful acquisition MT 5 The “IT Box” model to provide greater flexibility to incorporate evolving technologies and achieve faster responses from requirement validation *Policy / Directive / Standard / DTM ID: ************************************************************************************************************Key Points: This is the summary slide. Key Questions to Ask and Anticipated Answers: 1. What is the purpose of Capability planning? (ELO 7.1.3 --- quiz) To establish user requirements 2. What are characteristics of a Key System Attributes (KSA)? (ELO 7.1.4 --- quiz) a. Considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). Terms \ Definitions \ Acronyms: JCIDS & BCD

Conclusions on JCIDS Provides an enhanced methodology to identify and describe capabilities gaps and redundancies Helps to prioritize capability proposals Facilitates broad review of capability proposals independent of ACAT (Acquisition Category) Engages the acquisition community early Improves the identification of non-materiel alternatives Improves collaboration with other departments and agencies SLIDE INFORMATION ************************************************************************************************************** Slide Type: Content (Content or Exercise) Supporting ELOs ID: ELO 7.1.3 Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. MT3 Capability planning is used to establish user requirements MT4 “Getting the requirement right” at the front end is key to successful acquisition MT 5 The “IT Box” model to provide greater flexibility to incorporate evolving technologies and achieve faster responses from requirement validation *Policy / Directive / Standard / DTM ID: **************************************************************************************************************Key Points:JCIDS provides an enhanced methodology to identify and describe capability gaps and redundancies Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: JCIDS & BCD

Today we learned to: Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. Given a description of an Information Technology (IT) acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. Explore recent changes to DoD information technology systems capabilities management policies and procedures. Analyze the JCIDS impact on the development and acquisition of information technology systems from both weapon systems and business systems perspectives. Given an overview of the DoD capability planning processes, its objectives and expected results, identify capability planning documents from a list. SLIDE INFORMATION***************************************************************************************Slide Type: Content (Content or Exercise) *Supporting ELOs ID: ELO 7.1.3 Given an overview of the DoD capability planning processes, its objectives and expected results, identify at least two benefits of these processes. ELO 7.1.4 Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset. *Policy / Directive / Standard / DTM ID: ********************************************************************************************************* Key Points: Competency 7 – Capability Planning MT3 - Capability planning is used to establish user requirements MT4 - “Getting the requirement right” at the front end is key to successful acquisition MT5 - The “IT Box” model to provide greater flexibility to incorporate evolving technologies and achieve faster responses from requirement validation MT6 - Key Performance Parameter (KPP) is the performance attributes of a system considered critical to the development of an effective military capability. MT7 - Key System Attributes (KSA) are considered most critical or essential for an effective military capability but not selected as Key Performance Parameters (KPPs). JCIDS & BCD

References Title 10, United States Code, sections 153, 163, 167, and 181 Manual for the Operation of the Joint Capabilities Integration and Development System (JCIDS), 12 February 2015 CJCSI 3170.01I JCIDS, 23 January 2015 DoDD 5000.01, 12 May 2003, “The Defense Acquisition System” DoDI 5000.02, 07 January 2015, “Operation of the Defense Acquisition System” DoDD 7045.20, 25 September 2008, “Capability Portfolio Management” CJCSI 5123.01G, 12 February 2015, “Charter of the Joint Requirements Oversight Council (JROC)” DTM 11-009, 23 June 2011 Acquisition Policy for Defense Business Systems SLIDE INFORMATION *********************************************************************************************************** *Slide Type: Content (Content or Exercise) *Supporting ELOs ID: Identify and define the key statutory and regulatory documents for systems acquisition *Policy / Directive / Standard / DTM ID: Key Points: Plethora of policy guidance. This lesson will focus on the guidance provided in JCIDS Manual and CJCSI 3170.01 JCIDS Instruction as it affects development of the IT Systems. Please point out Reference i. DTM 11-009, Acquisition Policy for Defense Business Systems which directs separate policy guidance for business systems. The Defense Business Systems Management Committee has validation authority for defense business systems (DBS). Key Questions to Ask and Anticipated Answers: Terms \ Definitions \ Acronyms: JCIDS & BCD