5_-_TO2_CDMA_Research_Environment_-_1-24-19.pdf

SAF/CDM ANALYTICAL AND TECHNICAL (A&T) SERVICES:

TASK ORDER - 02

1 FEB 2020

REQUIRING AGENCY: SAF/CDMA

TITLE: CDMA Research Environment TASK ORDER OBJECTIVE: The Contractor shall conduct RDT&E and associated maintenance to assist CDM’s Advanced Analytics and Technology Investments (CDMA) Directorate in maintaining leading-edge research and development capabilities.

1 TECHNICAL AREA

1.1 CDMA provides rapid capability development to support across many Defense mission domains by assessing new approaches and methodologies to advance data analytics, business intelligence, technology investment and immersive intelligence supporting Department of the Air Force and Department of Defense missions through assigned program offices. Within this task order, references to CDMA customers or partners can include: Federal government departments, organizations, agencies, offices, and military units. The largest supported sector of that community is within the Intelligence Community, Department of Defense, and Defense Intelligence Enterprise.

1.2 One subordinate program office under CDMA, the Intelligence Systems Support Office (ISSO) (CDMAI) acts as a continual agent of change for the Defense Intelligence Enterprise through rapid identification, application and transition of novel technologies, unique methodologies, and advancements in data analytics through experimentation, studies, prototyping, software development and integration. CDMA’s programs rely on the Research Environment supported by this task order to accomplish its functions.

1.3 The Defense Intelligence Enterprise (DIE) is facing an information explosion that overwhelms human capacity to derive timely, usable knowledge across all domains and intelligence disciplines. The DIE must continuously identify and embrace new technologies and leverage them to exploit and apply derived insight to enhance indication & warnings, avoid surprise, and achieve true decision advantage empowering operations.

The DIE has an ongoing need to develop and assess novel intelligence activity concepts and technologies. CDMA supports the DIE with research, development, test and evaluation (RDT&E) of innovative approaches to data collection, analysis, and tool applications in wide number of areas such as: counterintelligence, human intelligence, counterproliferation, counterterrorism, personnel vetting, technology forecasting, and supply change risk management.

1.4 The hallmark of CDMA value and success is innovation. To accomplish that innovation, CDMA must be enabled by a responsive, adaptive, reconfigurable, scalable, advancing research and development environment. The Contractor supports innovation by finding, demonstrating, applying, and implementing emerging technologies applicable to generating insight for decision makers. Technical innovation is usually proven within the context of CDMA projects.

1.5 CDMA is assigned projects by the Undersecretary of Defense for Intelligence (USDI) to meet immediate and longer-term requirements, which are directed and funded by higher Intelligence echelons, derived from National Security, Defense, and Intelligence strategies.

CDMA will be assigned a number of projects annually, both large and small, varying from year to year. Historically, CDMA receives between 58 larger projects, lasting about one to two years each, and 4-8 smaller projects which can range from a few days to a few months.

Because the nature of the work is R&D, innovation is key and part of every project and in between. Since CDMA conducts applied R&D, not basic research, project innovations will address real world challenges facing the Intelligence Community (IC). Every project provides an opportunity to incorporate novel techniques, old techniques applied in novel ways, novel combinations, and similarly in the case of tools.

1.6 By way of example, recent CDMA projects include: trailblazing implementation of accounts and R&D activities within the Air Force’s secure cloud domain; simultaneously conducting multiple project R&D activities across different clearance level cloud environments; installing leading edge hardware to expedite machine learning and neural networks R&D; and installing automation to facilitate rapid issuance of variable compute virtual environments to meet demands of nearly 50 users flexing to dynamic project requirements.

1.7 While CDMA hosts a research and development environment that advances capabilities to support the conduct of intelligence, CDMA has no authority to conduct Intelligence as a mission. Under no circumstances shall Contractor interpret or conduct any task in a way that could be construed to include the official conduct of intelligence – such as, human intelligence, counterintelligence, signals intelligence, measurements and signatures intelligence, geospatial intelligence, identity intelligence, or any national security operation.

1.8 CDMA currently employs a mix of research and development (R&D) networks within its research environment. The research environment is currently extended to support two geographically separated locations, the CDMA Tampa office and an office in the National Capital Region which includes (numbers are subject to change):

1.8.1 An unclassified network supporting R&D activities that use unclassified publicly available information.

R&D Unclassified 1 – up to FOUO Number of users in general: 215; Windows Number of workstations: 60 Number of virtual machines: 75

1.8.2 An unclassified network secured to a higher standard to support processing unclassified but restricted information not releasable to the public.

R&D Unclassified 2 Number of users in general: 160; Windows Number of workstations: 93 Number of virtual machines: 176

1.8.3 An unclassified network supporting unclassified, but potentially risky R&D activities.

R&D Unclassified 3

Number on other networks in general: 20; varied OPSYS--project dependent, but mostly Windows Number of workstations: 20 Number of virtual machines: 0

1.8.4 A classified network accredited to support R&D activities that use TOP SECRET/SCI information.

R&D Classified 1- up to TS/SCI Number of radon users in general: 85; Windows, others--project dependent Number of workstations:85 Number of virtual machines: 125

1.8.5 Virtual Private Clouds on commercially-provided, classified and unclassified government-accredited clouds are implemented and operated for cloud-based R&D activities at their respective classification levels. Cloud services being used or considered for acquisition include: Amazon Web Services and C2S, Microsoft Azure Cloud Services, GovCloud, and MilCloud.

Cloud Unclassified Cloud users: 24; varied OPSYS--project dependent Classified Cloud users: 10; varied OPSYS--project dependent Number of virtual machines: 22

2 GENERAL REQUIREMENTS

2.1 Non-Personal Services – See basic contract PWS

2.2 Business Relations – See basic contract PWS

2.3 Contract Administration and Management – See basic contract PWS

2.4 Subcontract Management – See basic contract PWS

2.5 Contractor Personnel, Disciplines, and Specialties – See basic contract PWS

2.6 Location of Services – See paragraph A.5 below

3 TASK ORDER REQUIREMENTS

3.1 Capability Survey: Within sixty (60) days of award, the Contractor shall survey, compile, and deliver a list of government, commercial, and open source emerging capabilities (including, but not limited to hardware, software, processes, and methods) that will advance CDMA’s information technology enviornment. The survey must identify each capability as it applies to CDMA R&D activities and assigned projects and be updated quarterly. The Contractor shall apply their unique expertise in this process to ensure the demonstrable relevance of specific capabilities going beyond a simple survey. The government seeks quality in thought on the application over quantity of capabilities identified. While the Government will provide R&D topics to guide the survey content, the intent is not to limit the survey results. R&D topics may include: generalized and specialty areas of artificial intelligence, machine learning, quantum computing, automation of data wrangling, AI/ML PaaS, complex event processing, novel compute hardware, brain-computer/machine interfaces, API marketplaces, conversational user interfaces, or advanced machine language translation and natural language processing.

3.2 Capability Survey Demonstration: Upon CO or COR direction, the Contractor shall apply and demonstrate selected items from the list. Successful applications and demonstrations may lead to implementation within CDMA or transitioned to supported organizations across the DIE. The Contractor shall document and deliver demonstration plans, technology implementation process and use flow charts, detailed descriptions of technical capabilities, to support use by CDMA and its customers.

3.3 Capability Maintenance: At the direction of CDMA, the Contractor shall operate and maintain successfully demonstrated capabilities that are relevant to RDT&E project activities. Maintenance activities may require adjustment of working hours to accommodate minimizing impact to daily operations, e.g., one day per week conduct maintenance after typical business hours. Infrequent and unexpected building incidents affecting ability to maintain continuous operations of the networks may also require off hour support.

3.4 Capability Transition Plans: The Contractor shall prepare and implement transition plans for capabilites as designated by CDMA. Transiton plans shall be tailored to the specific capability and receiving organizations for transition, and may require demonstrating and supporting the capability with project customers. Transition plans are intended to ensure receiving organizations understand the resource and operational environment implications of accepting a new capability. In some cases, this could be as simple as training, in others it could involve receiving, installing and sustaining software/harware for short periods until the receiving organization can take over for themselves. The contractor can anticipate developing at least two transition plans per year and conducting at least three demonstrations per year.

3.5 Domain Expertise: This task requires the Contractor to maintain domain experts in the conduct of information technology research, which includes primary source (owners of the information) and secondary source (redistributors of primary source information) research and inquiries. This task is not intended to drive the requirement for a large stable of underutilized experts, but rather to provide the Contractor the ability to address how they will identify and gain access to best of industry experts to address short duration research on a specific capability outside the Contractor’s primary area of expertise. The Contractor shall assess the validity and reliability of all secondary sources and commercially/publicly available data sources used in the research. This includes attributing research findings to underlying source documents; providing original source data where possible, including all citations of material referenced.

3.6 Subject Matter Expertise (SME): The Contractor shall have the capability to leverage subject matter experts, as required, in support of projects and partners on relevant emerging information technology. This implies the ability to rapidly establish the necessary business-to-business or business-to-individual relationships required to bring talent to a problem or task quickly. The SME may be needed to support a day of meetings or 6-months full time on a project.

3.7 The Contractor shall develop reports and presentations in formats required by CDRL, the results of all RDT&E efforts, processes, recommendations, and lessons-learned at the end of each demonstration.

3.8 The Research Environment:

3.8.1 The Contractor shall support (1) implementation of the user-facing platform components including web-based tools that enable the collaborative documentation, refinement and prioritization of common user needs; (2) enable the monitoring of platform usage and enable the registration and linking of solutions proposed and hosted by 3rd parties. Tools currently in use could be changed to explore newer capabilities. This requirement is tool agnostic, and seeks a continuous R&D approach.

3.8.2 The Contractor shall support integration of software tools and capabilities into commercial and government provided, classified and unclassified (up to TS/SCI) cloud-based infrastructures to support increased availability, reliability and scalability. Tools currenlty in use include simple scripts, apps, desktop tools, cloud microservices, and extending to enterprise capabilities, as well as databases. Cloud services currently in use include commercial and Government cloud services.

3.8.3 The Contractor shall work with the Government to establish, document, and annually maintain a life cycle replacement plan and a road map to consolidate equipment in the Research Environment at CDMA locations.

3.8.4 The Contractor shall develop, complete, and at a minimum anually maintain current the minimum collection of documents recommended under the Department of Defense Architecture Framework for the research environment as coordinated with the COR and CDMA IT personnel. Capability implementations may require out of cycle updates to the documents.

3.8.5 The Contractor shall develop, complete, and at a minimum anually maintain current the minimum collection of documents required by the appropriate Designated Approving Authority for operating the capabilities at the clearance levels required.

3.8.6 The Contractor shall provide technical operations and maintenance support and coordination for the incorporation of enterprise services on CDMA networks.

These enterprise services may include, but are not limited to: on-premise collaboration suites, dynamic media presentation suites, natural language processors, virtual machine deployments and management, visualization, data processing and machine learning.

3.8.7 The Contractor shall implement, deliver, maintain, and document within security accreditation standards Enterprise Services to CDMA networks . The contractor shall provide surge support, if required, to ensure that CDMA meets proposed DIA timelines for the re-accreditation of the classified network. The following specialized reports apply: Network Architecture Documents; Presentation Briefs;

DOD Information Assurance Certification and Accreditation Process (DIACAP), and Risk Management Framework (RMF) for DoD Information Technology (IT) (DoDI 8510.01 July 2017) Deliverable Data [DI-MGMT-82000].

3.8.8 The Contractor shall provide technical support and coordination to more efficiently complete recurring technology tasks within the CDMA networks where Enterprise Services are not cost effective. The following specialized reports apply: Network Architecture Documents; Presentation Briefs.

3.8.9 The Contractor shall provide technical support and coordination for the implementation of a CDMA service migration from the Research Environment to the Cloud, leveraging the Commercial and Government Clouds to reduce on premise infrastructure needs.

3.8.10 The Contractor shall create, develop, implement, document and maintain the hosting on CDMA network services to the cloud. This migration may include, but is not limited to the following service migrations to the commercial and government provided, classified and unclassified cloud-based services within security accreditation standards; file servers, active directory, patch repository, and elastic compute. The following specialized reports apply: System Design Documents;

Network Architecture Documents; Presentation Briefs.

3.8.11 The Contractor shall maintain, enhance, develop, integrate, and deploy computing resources using commercial and government provided, classified and unclassified cloud-based services for CDMA directed activities.

3.8.12 The Contractor shall provide technical support and coordination for accreditation information and activities required by cloud providers; commercial and government provided, classified and unclassified cloud based services, to support CDMA directed activities.

3.8.13 The contractor shall maintain the current baseline of systems and provide software changes and fixes as required. Activities include, but are not limited to:

3.8.13.1 Maintenance of existing legacy systems and environments in accordance with disciplined engineering practices.

3.8.13.2 Maintaining applications, databases, and interfaces in compliance with applicable AF/DoD standards.

3.8.13.3 Conducting software installations, software security, web services installation and maintenance, web services testing, smart phone or other IT device applications and testing, security layer integration.

3.8.14 On-Premise Collaboration Suite - The Contractor shall serve as the Information Knowledge Manager and communicate directly with stakeholders on all matters related to knowledge management, business process re-engineering, and management strategies to utilize effectively the IT environment to accomplish business objectives. The Contractor shall examine government-provided knowledge and data strategies and make recommendations for improvements to existing frameworks, methodologies, and processes. The Contractor shall develop IT-based analytical tools to enable collecting, monitoring, measuring and reporting organizational performance and effectiveness information. The Contractor shall coordinate closely with the SAF/CDM Enterprise IT team to ensure optimal information access, retrieval, classification, storage, and tracking conditions are met including: Document Management, Records Management, Digital Asset

Management, Forms Management, eDiscovery and Search, Report Management, Knowledge Sharing and Collaboration, Data Governance, Data Quality; Data Processing and Advanced Visualizations.

4 SPECIAL REQUIREMENTS

4.1 Security and Safety – See basic contract PWS

4.2 Government Furnished Materials – See basic contract PWS

4.3 Environmental Requirements – See basic contract PWS

4.4 Quality – See basic contract PWS

4.5 Organizational and Consultant Conflicts of Interest (OCI) – See basic contract PWS

4.6 Period of Performance – See paragraph A.1 below

4.7 Travel and Other Direct Costs (ODCs) – See paragraph A.6 below

4.8 Minimum TO Proposal Submittals - N/A

4.9 Small Business Participation Goals - Calculated at IDIQ level

4.10 On Ramps - N/A

4.11 Off Ramps - N/A

4.12 Cross Teaming – See basic contract PWS

4.13 Documentation and Data Rights – See basic contract PWS

5 Competition and Ordering Process

5.1 Competition Selection Process for TOs – See basic contract PWS

5.2 General Order Process for TOs – See basic contract PWS

5.3 Authorized Ordering Offices – See basic contract PWS

5.4 Individual Task Order Clauses – See basic contract PWS

6 DELIVERABLES

6.1 The Contractor shall create, maintain, and update the deliverables in the performance of this task order as indicated below. Any deliverable defined in this task order shall be submitted by the corporate Program Manager to the COR in a mutually agreed upon format unless otherwise noted.

6.2 Monthly Contract Cost Tracking Report: See basic contract PWS (CDRL A001)

6.3 Electronic Subcontract Reporting System (eSRS): See basic contract PWS (CDRL

A002)

6.4 TO Post-Award Orientation Slides: (IAW CDRL A003)

6.5 Program Management Plan: (IAW CDRL A004)

6.6 Monthly Status Report: (IAW CDRL A005)

6.7 Final Report: (IAW CDRL A006)

6.8 Contract Manpower Reporting (CMR): (IAW CDRL A007)

6.9 Specialized Reports: The Contractor shall deliver following specific reports (IAW

CDRL A008):

6.9.1 Demonstration and/or Summary Briefings: As required by PM/COR, provide demonstrations of emerging capabilities and deliver summary briefings to CDMA or supported customer.

6.9.2 Monthly Research Environment Operations and Maintenance Summary Reports: Regarding the operational state of the CDMA research environment.

6.9.3 Project RDT&E Activity Compilations: For each capability project compile RDT&E activities and results, findings, processes, recommendations, lessons-learned, and other project-defined and generated reportable output, at the end of each project. Deliverable formats may vary from summaries, succint presentations, to detailed, in-depth transition materials, e.g., workflows, guides.

6.9.4 Life Cycle Replacement Plan and Road Map: An initial life cycle replacement plan and a road map, then followed with annual updates to ensure timely upkeep of the research environment.

6.9.5 Research Environment Architecture Documents: Minimum collection of documents recommended under the Department of Defense Architecture Framework.

6.9.6 Accreditation Documents: Collection of documents required by the appropriate Designated Approving Authority for operating the capabilities at the clearance levels required.

6.9.7 Intelligence Oversight Plan: Documenting compliance with intelligence oversight requirements.

6.9.8 Additional Specialized Reports:

6.9.8.1 System Design Documents (DI-IPSC-81432A)

6.9.8.2 Network Architecture Documents (DI-MGMT-81644B)

6.9.8.3 OV1/OV3 Diagrams (DI-MGMT-81644B)

6.9.8.4 Data Flow Diagram (DoDAF SvcV-4)

6.9.8.5 Functional Flow Documents (DoDAF SvcV-4)

6.9.8.6 Hardware and Configuration Physical Layouts (DI-IPSC-81436A)

6.9.8.7 Topology Diagrams (DI-IPSC-81436A)

6.9.8.8 Software Code (DI-IPSC-81441A)

6.9.8.9 Interface Design Description (DI-IPSC-81436A)

6.9.8.10 Software Version Description (DI-IPSC-81442A)

6.9.8.11 Software Installation Plan (DI-IPSC-81428A)

6.9.8.12 Software Test Plan (DI-IPSC-81438A)

6.9.8.13 Software Test Report (DI-IPSC-81440A)

6.9.8.14 System Administration Manual (DI-IPSC-81446A)

6.9.8.15 Presentation Briefs (DI-ADMN-81373)

6.9.8.16 DOD Information Assurance Certification and Accreditation Process

(DIACAP) and Risk Management Framework (RMF) Deliverable Data

[DI-MGMT-82000]

6.10 Inventory Report: The Contractor shall deliver a full inventory report for all items acquired or developed within the task order activities and period, maintained current at a minimum annually.

7 SERVICES DELIVERY SUMMARY

7.1 Nonconformance of contract requirements by the Contractor preventing performance of mission, reducing the usability of services or technical data for their intended purpose, or amendments to schedules, or performance periods may require consideration and negotiation between the Contractor, COR, and Contracting Officer (CO).

# Performance Objective

A001 Monthly Contract Cost Tracking Report - submit invoices by the 10th calendar day of each month for work accomplished the previous month. Invoices may be submitted with the monthly status reports.

A002 Electronic Subcontract Reporting System (eSRS) (large businesses only). The Contractor shall submit electronic individual subcontract plan reports as required pursuant to FAR Clause 52.219-9, Alternate II, Jan 2017.

A003 TO Post-Award Orientation Slides - submit no later than 10 days after post-award orientation meeting.

A004 Program Management Plan - submit initial plan 15 days after TO award.

A005 Monthly Status Report - submit every thirty days following contract award, by the 10th calendar day of each month for work accomplished the previous month; include all supporting documentation via appropriate channels.

A006 Final Report - submit no later than 10 working days prior to the conclusion of the period of performance.

A007 Contract Manpower Reporting (CMR) - submit as required.

A008 Specialized reports, memoranda, and/or briefings - submit as required.

8a Capability Demonstrations and Summary Briefings - submit throughout the task order as required.

8b Monthly Summary RE-Ops Reports regarding the operational state of the CDMA research environment operations and maintenance - submit monthly.

# Performance Objective

8c Initial and recurring survey results and list of government, commercial, open source emerging capabilities - submit initial versions within sixty (60) days of task order award, providing an updated list quarterly.

8d Life Cycle Replacement Plan and Road Map - submit an initial version within 3 months of task order award, followed by annual updates.

8e Research Environment Architecture Documents - submit within 3 months of task order award, and maintain current annually at a minimum, or as new capabilities are implemented affecting that architecture.

8f Inventory Report - must meet content requirements coordinated with the COR at the kickoff of the task - submit as required, but not less than once annually, and prior to the end of the POP.

8g Transition plan - must meet the content requirements coordinated with the COR at the start of each project - submit as required.

8h Intelligence Oversight Plan - submit within 30 days of award for legal review and approval.

8i Trip Reports - submit no later than one week after completion of travel.

8j Contractor Signed NDA - submit as appropriate to assigned projects.

8k Contractor Performance Issues - submit written response to the COR when requested.

ADMINISTRATIVE

A.1. PERIOD OF PERFORMANCE: The period of performance for this task shall be up to 60 months consisting of one 12 month base period from date of award and four 12 month options.

A.2. SECURITY LEVEL OF TASKING REQUIREMENT: Work related to these tasks shall require TOP SECRET/SCI clearances.

A.3. KEY PERSONNEL: As a minimum, the Contractor will designate a Project Manager for this task order. Individuals designated as key personnel cannot be substituted or replaced without the written agreement of the Contracting Officer (unless the individual’s employment with the company is terminated for any reason). The Contractor shall do everything possible to ensure continuity of effort by minimizing key personnel turnover throughout the period of the task order. However, if an individual leaves the Contractor before the contract expires, the Contractor must provide the Government with an individual of comparable qualifications, security clearances, and acceptable standards of moral and ethical conduct.

A.4. INDIVIDUAL QUALIFICATIONS: The Contractor shall submit security SCI nomination request of each prime and sub-contractor individual proposed to work on this task order.

Personnel must meet any minimum security, experience and educational requirements specified in the Base Contract, unless waived. Any exceptions or waivers shall be reviewed on a case-by-case basis in accordance with the Basic Contract by the COR.

A.5. PLACE OF PERFORMANCE: The majority of the work under this task order will be accomplished at CDMA’s facility located at 500 E Zack St, 7th Floor, R. L. Timberlake Jr.

Federal Building, Tampa, FL, 33602

A.6. MEETING ATTENDANCE/TRAVEL REQUIRED:

Meetings: The Contractor shall contact the COR within five (5) business days of TO award to schedule Kick-Off meeting.

Travel Requirements: Travel is anticipated for this effort and is estimated at 1 person/trip, 3 days/trip, 1 trip per month Tampa to DC, 1 trip per month Tampa to San Francisco (not actual, used for estimate). Travel may be required to attend relevant conferences and partner engagements anticipate two people per trip twice a quarter CONUS. International travel may be required.

A.7. GOVERNMENT FURNISHED FACILITIES AND INFORMATION: The government shall provide the Contractor with access to the desks, chairs, computers, phones, and copiers to accomplish work required under this task order.