FIA2T_AtchL-SB_Sample_Task_for_Set-Aside_20150923.rtf

FA8307-16-R-0049

FIA2T Section L Attachment L-SB - Sample Task for Set-Aside 21 Sep 2015 Attachment SB Capability Development Document (CDD) Study Objectives for Sample Task SB Mission Data (MD) Cryptographic Modernization (CM) Information Assurance (IA) System file_0.png file_1.wmf

9/21/2015

Prepared by:

Cryptologic and Cyber Systems Division (AFLCMC/HNC) 250 Hall Blvd., Suite 132 Lackland AFB, TX 78243

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

THIS PAGE INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

SCOPE

General This document describes the objectives for a Capability Development Document (CDD) study for a fictional mission data information assurance (IA) system. This document will be the basis of a potential Offeror’s study approach and cost information in support of the Flexible Information Assurance Acquisition Tool (FIA2T) Multiple Award Indefinite Delivery/Indefinite Quantity (MA IDIQ) proposal preparation for the small business set-aside pool. The task section, Section 4, includes a set of requirements for the study.

Description Mission Data (MD) Top Secret and Below (TSAB) COMSEC equipment has been the historical material solution employed to provide secure transmission of collected, unprocessed sensor data from air mission packages to ground stations for processing and subsequent distribution.

Document Conventions The documentation conventions for the CDD study are as follows:

The word "shall" is used whenever a specification expresses a provision that is binding.

“Shall” statements that are not explicitly marked as objective requirements are threshold requirements.

The words "should" and "may" are used wherever non-mandatory provisions are specified.

The word "will" is used to show purpose.

APPLICABLE DOCUMENTS

Cryptographic Modernization Mission Area Initial Capabilities Document (ICD) (fictional) Mission Area ICD (or equivalent) and CDD for Global Information Grid (fictional) NSA/CSS Policy Number 3-9, Cryptographic Modernization Initiative Requirements for Type 1 Cryptographic Products, dated 28 Mar 03 CJCSI 3170.01H Joint Capabilities Integration and Development System, dated 10 Jan 2012

CJCSI 3170.01H Operation of the Joint Capabilities Integration and Development System, dated 10 Jan 2012 CJCSI 6212.01F Interoperability and Supportability of Information Technology and National Security Systems, dated 21 Mar 2012 DOD Architecture Framework, version 2.02, 31 January 2015 DODI 8580.1 Information Assurance (IA) in the Defense Acquisition System, 9 July 2004 Electronic Key Management System (EKMS) Standard Key Management Infrastructure (KMI) Standard End Information Assurance Unit (EIAU) Management Standard Cryptographic Modernization Study:

Final Report: System Operational Needs (fictional) Final Report: Analysis of Future COMSEC Products (fictional) MD specifications for current equipment suite

STUDY PURPOSE AND SEQUENCING

The purpose of the MD study is to develop the information that will be used to populate a draft Capability Development Document (CDD) that will delineate the general requirements for the next generation of MD COMSEC equipment, and specifically identify the top level requirements set for the initial acquisition increment. The general process in developing this CDD is twofold: first, users of the current generation of MD equipment will be surveyed/interviewed to identify their projected last usage dates for this equipment, which will be compared against a sustainment and performance assessment to identify any basis for modification or replacement with modernization; secondly, future requirements beyond the capability of the current MD equipment suite will be similarly identified by survey/interview of the user community, to include the projected timing of these requirements. Other anticipated requirements for future MD equipment can be expected from the crypto modernization requirements required by NSA and potential communication architecture requirements of the Global Information Grid – with the associated timing for requirements implementation for both. Other organizations representing these additional requirements sets, for possible inclusion in MD capability, will also be surveyed/interviewed.

The information captured from the survey/interview process of individual user and policy communities will be collected, tabulated and analyzed to prepare draft inputs for a CDD that will be presented to a government team comprised of representatives of the entire MD user/policy community. This team will determine the final requirements set for inclusion in a draft CDD which will be vetted through a joint service/agency user community and the Joint Requirements Oversight Council (JROC) for formal requirement validation. Support to the government team and JROC comments resolution process is included in the CDD study effort. An additional task will be to conduct an Analysis of Systems (AoS) to assess the potential application of existing/in development/modified TSAB crypto processing devices for MD application versus new development of the capabilities.

TASKS

Draft CDD The contractor shall provide the information required to complete a draft CDD supporting user requirement validation for acquisition Increment One. The information required to complete the draft CDD is that required by CJCSI 3170.01E, Joint Capabilities Integration and Development System (JCIDS) (see outline at attachment 1 to this study), as derived from canvassing the applicable user/operator/support and policy communities for current MD TSAB crypto equipment, both aerospace vehicle (AVE) and ground operating equipment (GOE)

Draft As-Is/To-Be Architecture Views

Requirements shall be time-phased, based on operator/user/support and policy organization need dates to allow aggregation/segregation into increments for current (Increment One) and future acquisition increments. The contractor shall recommend criteria/strategies to stratify user requirements for preliminary identification of initial and subsequent acquisition increments to be presented to the government. Draft CDD architecture (CDD appendix A) shall also be time-phased to capture the as-is and to-be communication architecture for current and future increment(s), and shall include the required architecture framework view products developed from integrated architectures, developed and formatted IAW the DOD Architecture Framework (DODAF). The required views for both the as-is and to-be architectures are: AV-1, OV-1, OV-2, OV-4, OV-5, OV-6C, SV-2, SV-4, SV-5, SV-6, TV-1, NCOW Reference Model Compliance Statement, Initial Interconnectivity and Interoperability Capability (IIC) Profile (Interconnectivity Profile), NR-KPP statement, IA Statement of Compliance and Key Interface Profile (KIP) Declaration. Additional views that may be considered are: OV-7, SV-11 and TV-2. The architectures shall address all as-is/to-be interfaces internal and external to the MD crypto system, to include key fill (EKMS and KMI), interoperability with GIG standards and interoperability with End Information Assurance Unit (EIAU) management standards.

Current MD equipment to be assessed for replacement/upgrade shall include, but not limited to, both fielded products (10 models) and new products (2 models).

US Navy

Space and Naval Warfare Systems Command (SPAWAR)

US Army

Communications Electronics Research and Development Engineering Center, Space & Terrestrial Communications Directorate (CERDEC, S&TCD)

Defense and Other Agencies

National Reconnaissance Office (NRO)

National Geospatial-Intelligence Agency (NGA)

Life Cycle Cost Estimate.

The contractor shall generate a life cycle cost estimate for the government-identified requirements set for Increment One acquisition for AVE, GOE and Special Test Equipment (STE) that supports the Program Affordability section (section 15) of the CDD.

Requirements Traceability Matrix The contractor shall deliver a Requirements Traceability Matrix (in Microsoft Excel) identifying the following for each potential CDD requirement:

Analysis of Systems (AoS) In parallel with the requirements identification process through user survey/interview, the contractor will conduct an Analysis of Systems (AoS) to assess the potential application of existing/in development/modified TSAB crypto processing devices, both AVE and GOE, for MD application versus new development of the capability. The government will identify a candidate list of systems to the contractor for characterization of system performance parameters/capabilities and system attributes. These candidates will be compared with potential MD Increment One requirement baselines for determination of degree of satisfaction of user requirements.

Government Team and Meetings Support The contractor shall provide support to the government team, to include reach-back support and/or actual participation with the government team to be convened after study completion to draft/finalize the MD CDD. Follow-on support may include participation to resolve questions/actions required by JROC review.

Other Meeting Support

In addition to the customer interview process (Section 4.1.3) and government team support (Section 4.4.1), the contractor will be required to support the following:

The contractor shall conduct an initial (Kickoff Meeting), interim and final Program Review with the core government management team (CPSD, AFCA/ECA and NSA). Program Review locations are at CPSD. The initial Program Review (Kickoff Meeting) will be held within 2 weeks (14 calendar days) after contract award. Program Reviews shall have announced agendas and shall be documented in minutes, to include a list of outstanding actions and planned closure dates.

The contractor shall support a User’s Conference at TBD location which will serve to introduce/overview the government team to potential CDD requirements prior to convening of the formal government team. The Users Conference is assumed to take place after completion of both the survey/interview process of Section 4.1.3 and Interim Program Review of Section 4.4.2.1.

Reporting The contractor shall monitor and report study progress and expenditures.

ADMINISTRATIVE REQUIREMENTS

Security Offeror shall consider for this fictional task that contractor personnel conducting customer interviews to gather customer requirements, and personnel performing architecture documentation, do NOT need to possess current TS/SCI clearances. Security-related requirements and handling shall NOT be addressed in the proposal response, as if all equipment and information involved were unclassified.

Software The contractor shall possess the software media necessary for compatibility with the government team, consisting of current versions of Microsoft Office Professional (Word, PowerPoint, Excel and Access), Microsoft Project Standard and Adobe Acrobat Reader. An appropriate commercial industry standard system architecture software of the contractor’s choice, will be used to develop/produce all required architecture views. A software license for this software will be provided by the government for the period of the study.

Travel Contractor travel will be as authorized in writing by CPSD, to support customer requirements interviews, User Conference, government Program Reviews, government team meeting, or other technical meetings or conferences. Contractor reimbursement for travel expenses (without added fee) will be at the rates provided in the Joint Travel Regulations (JTR). Contractor travel shall not exceed $50,000.

Period of Performance Period of Performance will be 10 months.

GOVERNMENT FURNISHED INFORMATION (GFI) AND EQUIPMENT (GFE)

The government will make available the GFI reference material identified in Section 2. The government will provide the system architect software license for the contractor chosen software for the period of the study.

CDD OUTLINE

Capabilities Development Document (CDD) Outline (from CJCSI 3170.01I, 23 Jan 2015, Appendix A to Enclosure F, pp F-A-1 through F-A-8)

Executive Summary Revision History Table of Contents Points of Contact

1. Capability Discussion

2. Analysis summary

3. Concept of Operations Summary

4. Threat summary

5. Program summary

6. System Capabilities Required for the Current Increment

7. Family of System and System of System Synchronization.

8. Information Technology and National Security Systems Supportability

9. Intelligence Supportability

10. Electromagnetic Environmental Effects (E3) and Spectrum Supportability

11. Assets Required to Achieve Initial Operational Capability (IOC)

12. Schedule and IOC and Full Operational Capability (FOC) Definitions

13. Other DOTMLPF and Policy Considerations

14. Other System Attributes

15. Program Affordability

Mandatory Appendices Appendix A CRD Crosswalk Appendix B Architecture Products Appendix C References Appendix D Acronyms Other Appendices or Annexes