SPECIAL NOTICE
B -- CYBERQUEST2017
- Notice Date
- 7/12/2016
- Notice Type
- Special Notice
- NAICS
- 541990
— All Other Professional, Scientific, and Technical Services
- Contracting Office
- Department of the Army, Army Contracting Command, MICC, MICC - Fort Gordon, 419 B St., Bldg 29718, 3rd Floor, Fort Gordon, Georgia, 30905-5719, United States
- ZIP Code
- 30905-5719
- Solicitation Number
- CYBERQUEST2017
- Archive Date
- 9/15/2016
- Point of Contact
- Tara L. McAdoo, Phone: 7067911831
- E-Mail Address
-
tara.l.mcadoo.civ@mail.mil
(tara.l.mcadoo.civ@mail.mil)
- Small Business Set-Aside
- N/A
- Description
- 1. Background: HQDA EXORD 057-14 established the U.S. Army Cyber Center of Excellence (CCoE) and designated the CCoE CG as the Force Modernization Proponent for Cyberspace Operations, Signal Communications Networks and Information Services (Signal), and Electronic Warfare (EW); and established the Signal and Cyber Schools. The EXORD further directed the CCoE to partner with the Intelligence Center of Excellence (ICoE) for institutional intelligence support to Cyberspace Operations. To that end the CG directed the establishment of an annual Prototyping Experiment to help go after innovative solutions to specifically close critical capability gaps to address Army Warfighting Challenge # 7: a. Conduct Space and Cyber Electromagnetic Operations and Maintain Communications - How to assure uninterrupted access to critical communications and information links (satellite communications [SATCOM], positioning, navigation, and timing [PNT], and intelligence, surveillance, and reconnaissance [ISR]) across a multi-domain architecture when operating in a contested, congested, and competitive operating environment. 2. Intent: The CCoE will conduct an annual Cyberspace Operations, Signal, and EW Prototyping Experiment called Cyber Quest to assess emerging technologies against associated Army required capabilities in order to inform current capability development and doctrine writing efforts, validate concepts, and better understand doctrine, organization, training, materiel, leadership and education, personnel and facilities (DOTMLPF) impacts for those concepts under evaluation. Cyber Quest will also serve as a risk mitigation event that Army acquisition and capability development proponents can leverage to validate selected candidate solutions for participation in Army/Joint exercises and experiments (i.e. Army Warfighting Assessments (AWA), the Army Expeditionary Warrior Experiment (AEWE), the Joint Users Interoperability Communications Exercise (JUICE) and Network Integration Experiment (NIE)). 3. Cyber Quest 2017: The CCoE is looking to government, industry, and academia to present Cyberspace Operations, Signal, and/or EW solutions for considering during Cyber Quest 2017 (CQ '17). CQ '17 will present an operational scenario with opportunities to highlight innovative potential solutions within a live, virtual or constructed (LVC) environment. The challenges facing our warfighters are too complex to make concept and acquisition decisions based upon a static display (demonstration) of capability. Therefore, the intent of this event will be to discourage inert demonstrations of solutions in a stovepiped, prestine manner. Instead, solutions will be integrated with existing systems and live data feeds to drive outcomes and concepts toward wartime realism. CQ '17 is meant to encourage collaboration with other industry, government, and academic partners to drive results oriented, positive outcomes and solutions. Furthermore, this event will allow solution providers to integrate components into existing Army capabilities within an operationally relevant environment, realistic scenarios and substantive data injects. Yet, the scenarios are not the primary focus of the event, nor is the desired endstate capturing of a specific scenario objectives. The scenario is simply the backdrop to enable an operational evalution of concepts and learning demands in real-time. Therefore, the intent is to establish operational realism but maintain a "No Fear of Failure" environment for these early and innovative concepts. CQ ‘17 will be executed leveraging an Infantry Brigade Combat Team (IBCT) Tactical Operations Center (TOC). This TOC will be placed into a Combined Joint Task Force (CJTF) wartime scenario overlay to drive at Joint and Coalition contextual learning demands. IBCT, CJTF, Joint and Coalition staff role players will be incorporated to establish operational realism. This will enable scenarios to use live, virtual, and constructive injects to drive capability learning impacts with as much realism as possible. 4. Capability Areas of Interest: The following capabilities and concepts are of interest for CQ '17,and are broken out by TRADOC Capability Manager Office (TCM) Interest Areas. a. Cyberspace Interest Area i. Forensics and Malware Detection, Analysis and Reverse Engineering - provide cyber defenders the capability to employ defeat mechanisms to collect, process, search, and analyze evidence from portable electronic devices, removable media, and system hard drives and random access memory in reaction to cyberspace threats. Forensics/Malware Analysis will consist primarily of a software-based set of solutions, and in some cases supporting hardware, that will enable the cyber defender to perform global discovery, readiness and mission support by assisting with protecting cyberspace key terrain, conducting comprehensive reviews of an organization's mission critical assets that focus on network security, and assessing an organization's security posture and processes to identify areas of vulnerability or inadequate security. ii. Insider Threat (InT) Detection - a software-based, scalable tool that proactively identifies and mitigates internal risks associated with the theft or misuse of critical, mission essential data. InT Detection enables the establishment of an InT Protection and Detection Program that utilizes full-spectrum solutions to assess, deter, deny, defend, defeat, and evolve against the InT. InT detection facilitates a policy driven InT program development, endpoint activity monitoring and control, the capturing and analysis of user actions (with the ability to replay), investigations, and the adaptation of an organization's InT countermeasures. It can identify individuals who are at higher risk for being targeted by foreign intelligence or those who are more likely to misuse access privileges to protected information. InT Detection provides cyberspace defenders with a picture of the insider threat risk profile across an organization iii. Defensive Cyber Operations (DCO) Mission Planning (DCOMP) - software-based scalable, secure solution for DCO planning at the global, regional, and local levels which offers a presentation layer for cyber workflow management. DCOMP integrates network security requirements, intelligence, and vulnerability analyses, with the outputs of mission analysis, other military decision making process outputs, and the six DCO planning steps in order to identify cyberspace key terrain, determine probable attack vectors, and produce a set of relevant internal defense measures, triggers, and decision points. The result is the automated generation of the appropriate OPORD appendix, which is then war-gamed in a simulation engine for evaluation and improvement, and then the final OPORD to rapidly provision the necessary platforms so that cyberspace defenders can execute mission in near real-time. Cyberspace defenders will use DCOMP to provide input to the operations process and assist commanders in prioritizing support, as well as directing and synchronizing actions b. Electronic Warfare Interest Area i. Tactical Electronic Warfare Sensors at Battalion, Company and Platoon level Army echelons planned and deployed by Cyber Electromagnetic Activities (CEMA) Situational Understanding (SU) Management Tool at the Brigade and Battalion echelons. CEMA SU Management Tool has control to send and command remote role changes to the sensor platforms (Mounted, Dismounted or Airborne). Role changes consist of Electronic Attack (Deny, Disrupt, Degrade, and Manipulation) and Electronic Warfare Support (Precision Geo-Location and Direction Finding). The CEMA SU Management Tool at Brigade and Battalion can also have the ability to remotely activate/deactivate the sensor platforms. ii. Tactical Sensors alert on an unidentified Emitter and sends information to the Brigade and Battalion CEMA SU Management Tool. CEMA SU Management Tool quickly analyzes sensor report and once the Signal of Interest (SOI) is identified as use by enemy emitter, emitter location is then sent to the Ground Force SA (GSA) Tool. Tactical Sensors alert on target SOI from a preloaded Target List and sends information to the Brigade and Battalion CEMA SU Management Tool. CEMA SU Management Tool Near Real Time sends target of interest to GSA tool. CEMA SU Management Tool should utilize Joint Military Symbology (Mil Std-2525D). iii. CEMA SU/Management Tool analyzes EW battle damage assessment (BDA) effect on targeted emitters. Determines from assessment the effects had on the targeted emitter. iv. Brigade and Battalion using CEMA SU Management Tool coordinates EW effects with Joint and Coalition Partners and updates the Commanders COP. c. Network and Services Interest Area i. Integrated Network Operations (NETOPS) Capabilities to manage both Uper Tactical Internet (UTI) as well as the Lower Tactical Internet (LTI). 1. Obtain, troubleshoot and recommend solutions of network/account information/settings, operating systems and applications information.(IT asset management/ discovery) 2. Obtain troubleshoot and recommend solutions of device operation, network, performance and application information 3. Rapidly and dynamically adjust unit task organization and network configurations to meet mission requirements. ii. Information Services 1. Content Delivery - Content Delivery is the intelligent movement of information based upon network conditions and user applied data parameters for "who, what, where, when, and why." Commanders and operational managers require the ability to dynamically tailor these parameters to control data movement and transmission in order to maximize data throughput. Prioritize network resources dynamically to meet mission requirements. 2. Storage Infrastructure- Storage is the physical storage of data for users in such a fashion as to be accessible by others (e.g., indexed, cataloged, searchable). There is local user storage and network storage on network servers. Storage service makes copies of data if marked critical by user. Eg.Dynamic Application Hosting infrastructure. 3. Share Infrastructure - Share is the data advertising, publishing, searching, subscribing, meta-data creation, and meta-data registries. Meta-data only is physical moved via Content Delivery and stored via storage in order to minimize data traffic on the network. iii. Cybersecurity - To better assist the BCT/DIV/Corps/Theater and Enterprise Information Assurance (IA) sections, an automated threat detection tool/software that will not only alert the cell of intrusion, but also provided background data on what type of issues exists and how to combat this issue. Content Staging; the ability to prioritize data travelling over the network to get the right package at the right place at the right time to the right person. iv. Network capacity and reach - There is a need to store more data at the tactical and enterprise level and to extend the range of the network utilizing terrestrial and other transmission capabilities. How to transmit more data at greater distances in current and future systems, while reducing size, weight, power and complexity. v. Alternatives to current commercial solutions for classified program (CSfC), that can be delivered with lower complexity, are less expensive and more effective. vi. Identity and Access Management (IdAM) The Army requires a means to manage and integrate digital identities (for both human and non-human entities (NPE) to securely access systems/devices/networks/applications and services in all security enclaves). Additionally managing the accounts provisioning, synchronizing directory services (or an association of various identities/attributes), while supporting a service against which users can authenticate using a single identity 1. A federated IdAM infrastructure that enables authentication of Personal Entity (PE) and NPEs across the enterprise regardless of security boundaries; thereby making IdAM look and operate like a single service implementation. 2. Leverage the Defense Manpower Data Center's (DMDC's) Enterprise Directory Service (EDS) to enable a single digital identity for multiple personas. 3. Decouple applications from reliance on local or dedicated directories for Authentication and Authorization. 4. Integrate workflow of IdAM business process by adding automated verification for account provisioning and access functions d. Tactical Radio Interest Area i. Network integration and management solution between the current Army LTI (Battlefield Communications Network for Echelons at Division and below) and the Upper Tactical Internet (Battlefield Communications Network for Echelons at Corps to Brigade) ii. Protection methodologies and capability to reduce the risks from current and future radio system vulnerabilities iii. Cyber Security concepts and capabilities applied to the LTI. Visibility provided at the Brigade Command Tactical Operations Center as well as incorporation with the UTI network management capabilities for visibility and remediation actions. Of particular interest is packet inspection for LTI networks, alerting and remediation methodologies based upon results of that packet inspection. e. Operational Interest Area i. Cyber Situational Understanding (SU) - Cyber Quest 2016 took the initial steps to review Cyber SU at the tactical edge. Information is generally overwhelming at the Command Post. We will continue to look for solutions that can aggregate disparate information from Command and Control systems and disparate sensors to help drive more efficient and/or accurate Commander decisions. ii. Big Data Analytics at the tactical edge - Big data collection at the tactical edge (i.e. Brigade Command Post) is a concept that we desire to further pursue. Aggregation of disparate data and creating correlations that are then displayed on Situational Understanding tools with an intent to drive more efficient and/or accurate commander decisions. These data analytic components need to be flexible enough that staff functions within the tactical edge can manage correlation opportunities as mission needs demand. iii. Defend critical manned and unmanned, aerial and terrestrial, information collection systems and sensor/payload capabilities' requirements. iv. Improve the defense of critical commanders communication and command and control systems within the tactical command post. v. Improve the survivability and utility of electronic systems in an EMSO congested and/or positioning, navigation and timing denied environment. vi. Improve Army operational data sharing and efficiency between Joint and Coalition partners within a Combined Joint Task Force (CJTF) operational construct. vii. Determine means to improve the efficiency of decisions and delivery cycle of Cyberspace effects utilizing EW assets. Increase cross compatibility and collaboration between EW SU management tool and cyber planning tools. viii. Improve the efficiency of using sensor packages or tactical radios to enable sensors and data collection at the Soldier level (Soldier as a Sensor). ix. Convergence: As complexity increases in a command post, commanders are overwhelmed by spurious pecies of information that fail to help them make informed decisions. Furthermore, stovepiped data, networks and organizational structures lack the flexibility to tackle the problems of the future. Therefore, Data, Transport and/or Organizational convergence solutions are desired. Furthermore, solutions presented to address other concerns should provide flexibility to flatten the command post of the future. 5. Learning Demands: a. How can the Army engineer the tactical network to reduce user complexity, improve capacity, increase resiliency, maximize bandwidth efficiency, enable dynamic reconfiguration, improve cybersecurity, while becoming expeditionary? b. What is the optimal way for the Army to organize the activities associated with Cyberspace Operations to maximize cyber capabilities across the Army Warfighting Functions while minimizing required resources? c. What is the optimal way to employ cyber capabilities with the elements of traditional combat power to support Unified Land Operations (ULO) and deliver the effects required by Commanders at all echelons? d. How can the Army better prepare its leaders and soldiers to operate in denied, degraded, and disrupted space operating environments (D3SOEs)? e. What effects must Army space forces deliver to assure overmatch and freedom of action for Army and joint forces? f. What capabilities do Army forces need to rapidly establish a space architecture that enables an expeditionary and globally deployed Army? g. In what ways can Army space forces and capabilities be integrated with special operations forces to improve both Army and special forces effectiveness? h. How does the Army develop and maintain situational understanding across the range of military operations to win in a complex world? 6. Key Events: Vendors interested in participating in Cyber Quest 2017 should submit white papers in accordance with paragraph 8. Selected vendors will be invited to brief their capabilities in front of a technology selection committee 27 - 29 Sep 16. Vendors whose technologies have been selected for participation in Cyber Quest 2017 will be officially notified by email NLT 3 Oct 16. a. Technology Call published - 11 Jul 2016; b. Cyber Quest Industry Day - TechNet 2-4 Aug 2016; (Currently scheduled for Tuesday, 2 Aug 2016, 1:20 - 6:00 PM Engagement Theater Session 2. Room Olmstead A/B Augusta Marriott at the Convention Center Augusta, Georgia Convention Center. Please check the following website for more information about TechNet: http://events.afcea.org/Augusta16/Public/enter.aspx) c. Deadline for White Paper submissions - 31 Aug 16; d. Technology/Paper Down Select Panel - 14 - 15 Sep 16 e. Invitation to Technology Selection Board- 27 - 29 Sep 16; f. Vendor notifications - 3 Oct 16; g. Initial Planning Review - 18 - 20 Oct 16; h. Coordinated Working Group #1 - 6 - 8 Dec 16 i. Coordinated Working Group #2 - 7 - 9 Feb 17; j. Coordinated Working Group #3 - 11 - 13 Apr 17; k. Technology Integration - 29 May - 30 Jun 2017; l. Pilot/Practice mission week - 26 - 30 June 2017; m. Cyber Quest Execution - 10 - 28 July 2017. 7. White Paper Submissions: The following organizations may submit white papers: colleges and universities, non-profit research institutions, commercial firms, small business, small disadvantaged business concerns, historically black colleges and universities, and minority business enterprises and institutions. Collaboration among vendors and academia is encouraged. 8. White Paper Requirements: White papers will be evaluated against the criteria listed in section 8c below. Preference will be given to submissions that address multiple areas of interest, have technologies that are at a Technology Readiness Level (TRL) of 6 or higher, and have been integrated with tactical mission command or radio systems (as appropriate). White papers will be the sole criteria used to select vendors that will be invited to the CDID-ED to brief their capabilities in front of the technology selection committee. a. Vendors may respond to one or more of the areas listed in sections four (4) through six (6) in a single whitepaper with a discrete description of each area of interest addressed. b. Format: The white paper should be a maximum of 5 pages in length, including figures, charts, and tables. It should be single-sided, single line spaced, utilize one (1) inch margins and utilize Times New Roman 12 pitch font. The cover page shall be excluded from the page count and shall be marked with the BAA number, any required security markings, and the submitter's Commercial and Government Entity (CAGE) Number. Submitters should mark their white paper with a protective legend IAW FAR 52.215-1(e). All White papers must be unclassified. The white paper shall be prepared in Microsoft Word or Adobe PDF electronic file format. The document must be print-capable and not password protected. White papers submitted via email must not exceed 5MB. White papers longer than 5 pages will be rejected. c. Based on the areas of interest, a high-level description of the capability being addressed in the white paper should include the following topics (as appropriate): (1) Hardware description. i. Quantity / per unit cost / per bundle cost. ii. Physical interfaces. iii. Expected performance parameters. iv. Documentation/manuals/specifications/etc. v. Information Assurance status and/or Certifications. vi. Size, weight, and power (SWaP). vii. Antenna information. viii. Frequency Bands. (2) Software description. i. Operating system. ii. Platform. iii. Software interfaces. iv. Base Station Controller. v. Information Assurance and/or Certifications. vi. Compatibility with existing commercial protocols. vii. Interoperability with commercial protocols. viii. Application Programming Interface (API). ix. Portability of software solutions. x. Documentation/manuals/specifications/etc. xi. How will the discrete technology delivered under this topic be sufficiently innovative and flexible to be able to be integrated with other technologies or into other Command and Control (C2) systems? (2) Software Supportability and Sustainability i. Licensing model: Is licensing per device, per user, etc. Is the license one-time or recurring (e.g. annual)? ii. Patching model: How are security updates published? Is a recurring (e.g. annual) support and/or maintenance fee required to access updates? What technical data is included with security updates (e.g. what vulnerability was mitigated or corrected, and the method of mitigation or correction)? iii. Product roadmap: Is a product roadmap available with target dates for future releases / milestones, planned features, and end-of-life for specific versions? iv. Data rights: Are government data rights (e.g. source code and technical data) available, either included with the license or at additional cost? v. Third Party Software: Is any third party software either required or optional for full functionality (e.g. Operating Systems, hardware drivers, database, other applications, or plugins)? Provide data for 1-4 for each third party software requirement (if available). (3) Functionality provided by the capability. (4) Operational Architecture View (OV-1) depiction. (5) Technology Readiness Level (TRL). All responders must state the TRL of their technology (see attachment 1 for a definition of levels). (6) International Traffic in Arms Regulations (ITAR) restrictions if applicable (7) Security Classification requirements applicable to or pertaining to solutions (if known) (8) Expected or perceived Use Cases for concept or capability proposed 9. Vendor and Academic Community Notification: Selected vendors will be notified telephonically by 1700 EST 3 Oct 2016 and given follow-on instructions via email. Not all submitters will be invited to brief or demonstrate their capabilities to the Technology Selection Panel or participate in all key events. 10. Vendor and Academic Community Participation: Vendors are not required to provide a turnkey solution for all areas of interest. Niche systems that provide a critical capability in the key areas of interest will be considered. Vendors will be required to sign a Vendor Demonstration Agreement (VDA) and support Cyber Quest 2017 planning and execution events at their own cost. 11. DOD Participation: The Cyber Battle Lab, Army Cyber Command (ARCYBER), Cyber Protection Brigade (CPB), TRADOC Capabilities Manager (TCM) Cyber, TCM Electronic Warfare (EW), TCM Tactical Radio (TR), TCM Network and Services (N&S), Requirements and Integration Division (RID), Capabilities and Analysis Division (CAD), Program Manager (PM) community and other appropriate organizations will be participating in this effort. Other federal and non-federal organizations may be invited to observe Cyber Quest 2017 as well. 12. US Government is not obligated by this BAA. This notice does not obligate the Government to award a contract or otherwise pay for the preparation or information provided in the white papers. The Government reserves the right to use information provided by respondents for any legal purpose deemed necessary. Any organization responding to this notice should ensure that its response is complete and sufficiently detailed; the information provided will be used to assess the respondent's ability to address the capabilities called for in this BAA. Respondents are advised that the Government is under no obligation to acknowledge receipt of the information received or provide feedback to respondents with respect to any information submitted. This is not an announcement of an acquisition solicitation. 13. Technology/Paper Down Select Panel: All properly submitted white papers and proposals that conform to the BAA requirements will be evaluated by a review panel comprised of technical experts drawn from organizations that represent the Army operational, institutional, capabilities development, and acquisition communities. All government personnel are bound by public law to protect proprietary information. 14. The Government may use selected support contractor personnel to provide administrative assistance to federal employees regarding all aspects of any actions ensuing from this announcement, including the evaluation of white papers and subsequent proposals. However, federal employees will be responsible for actual reviews and evaluations. These support contractors will be bound by appropriate non-disclosure agreements (NDA) to protect proprietary and source-selection information and are not permitted to release any source-selection information to third parties, including others in their organization. By submission of a White Paper and/or subsequent Proposal, offerors are hereby consenting access to financial, confidential, proprietary, and/or trade secret markings in the White Paper and/or subsequent Proposal to support contractor personnel. 15. Points of contact: ALL SUBMISSIONS AND ANY QUESTIONS ON THE OBJECTIVES OR PREPARATION OF THE WHITE PAPER SHOULD BE ADDRESSED TO Major Stephen Roberts (stephen.a.roberts3.mil@mail.mil), Major Andrew Stannard (andrew.d.stannard.fm@mail.mil) or Mr. Horace Carney (horace.r.carney.ctr@mail.mil), Cyber Battle Lab, Bldg 19901, 850 East 13th Street, Fort Gordon, GA 30905. Only questions pertaining to the BAA electronic posting are to be directed to Ms. Tara L. McAdoo, Mission and Installation Contracting Command, Fort Gordon GA, tara.l.mcadoo.civ@mail.mil (706)791-1825.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/7a6f5e56ce47ea0eaaabc813e28b472d)
- Record
- SN04179662-W 20160714/160712235207-7a6f5e56ce47ea0eaaabc813e28b472d (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |