SPECIAL NOTICE
99 -- Empire Challenge 2010 Special Notice
- Notice Date
- 10/15/2009
- Notice Type
- Special Notice
- NAICS
- 541330
— Engineering Services
- Contracting Office
- N00189 FISC NORFOLK, PHILADELPHIA OFFICE 700 Robbins Avenue, Building 2B, Philadelphia, PA
- ZIP Code
- 00000
- Solicitation Number
- N0018910TZ008
- Small Business Set-Aside
- N/A
- Description
- EC10Notice Type: Special Notice For Informational Purposes OnlySynopsis: This announcement is for the Empire Challenge 2010 (EC10) Event scheduled for live execution in September 2010. Empire Challenge is an Under Secretary of Defense for Intelligence (USD(I)) sponsored, U.S. Joint Forces Command (USJFCOM) executed joint/combined Intelligence, Surveillance and Reconnaissance (ISR) interoperability demonstration. EC10 will focus on improving the ability of the International Security Assistance Force (ISAF) Afghanistan to effectively and efficiently manage, access and use ISR to improve command and control (C2), and enhancing information sharing and situational understanding to improve the effectiveness of operations while minimizing collateral damage in a complex environment. This announcement is not a request for proposal; no contract award shall be made as a result of this announcement. EC10 Points of Contact are: John Kittle at (757) 836-0288 or Rodney Brickell at (757) 836-0287. Added: Empire Challenge 2010 1. Event DescriptionThis announcement is for Empire Challenge 2010 (EC10) scheduled for live execution in September 2010. EC10 will consist of a series of ISR interoperability events using a combination of modeling & simulation, laboratory and live-fly events to provide solutions-based assessments of the Distributed Common Ground/Surface System (DCGS) Enterprise, as well as multinational, multi-INT, capability based interoperability, Intel-Ops Fusion capabilities. EC10 will simulate elements of the ISAF command structure with an emphasis at the Regional Command (RC)-level and below in an operationally representative, "live-fly" environment augmented by virtual and constructive capabilities. 2. Joint Capability Threads and Objectives EC10 Joint Capability Threads (JCTs) are supported by associated objectives developed at the Concept Development Conference (CDC), based on inputs from USD/(I), Joint Staff J2, CENTCOM and SOCOM, the Services and Defense (DoD) Agencies, and the Coalition Community. The JCTs and baseline objectives reflect the following themes:a. C2 - ISR Data Integration to Support Operations in a Complex Environment1) Integrate CI/HUMINT Tools and data with the Distributed Common Ground/Surface System (DCGS) Enterprise and C2 architecture, and make accessible by multinational forces in a timely manner.2) Provide interoperable Unattended Ground Sensor (UGS) data with DCGS Enterprise and C2 architecture, and make accessible to multinational forces.3) Enable interoperability between the DCGS Enterprise and ISAF C2 networks to pass ISR data and receive operational reporting.4) Integrate ISR (assets, collection & tracks) and C2 tracks for display on C2 and ISR operational and tactical displays.5) Properly tag ISR and operational data to enable data sharing across multiple security domains, and between US and ISAF networks.b. C2 and ISR Management to Achieve Persistent Surveillance Over Key Terrain1) Refine collection and Tasking, Processing, Exploitation, Dissemination (TPED) management doctrine and tactics, techniques, procedures (TTPs) to enable tasking of ISAF ISR assets, providing persistent surveillance over key terrain for a specified period.2) Manage, store and disseminate large persistent data sets to the DCGS Enterprise and warfighter at the tactical edge.3) Automate/assist in the processing of persistent surveillance data to alert operators to potential targets of interest.4) Integrate multi-INT sensors and processing, exploitation, dissemination (PED) nodes to enable tipping and cuing to provide persistent surveillance.5) Provide the ability to search and discover ISR asset availability and location in support of persistent surveillance.c. ISR Support to Joint Close Air Support (JCAS)/Strike to Achieve Combat Effectiveness and Minimize Civilian Casualties and Fratricide1) Provide relevant, timely and accurate ISR and operational target information to JTACS/Fire Support Elements (FSEs) to include information on potential fratricide, collateral damage and civilian casualties.2) Provide accurate ISR target location data suitable for both mobile and static targets.3) Provide interoperable ISR data for close air support (CAS) suites.4) Provide/receive interoperable ISR data to support multi-national CAS.5) Provide sufficient bandwidth/throughput at the tactical edge to support common operational picture (COP) generation. d. Information sharing to support Multi-national / Whole of Government Interoperability1) Provide/receive interagency and partner information and data in support of Situational Awareness (i.e. Protection and Strategic Communications).2) Refine/develop information sharing capability and processes within each security domain to improve coordination across coalition operations.3) Assist in validating/defining data-tagging/requirements to support cross domain solutions, and enhance data sharing in compliance with established standards.4) Provide high bandwidth cross domain capabilities to support ISAF operations.5) Provide multi-domain, bi-directional, multi-lingual chat to support ISAF operations. 3. Coalition Participation Coalition participation is key to the success of EC10. The anticipated international participants include Australia, Canada, New Zealand, United Kingdom, and NATO member nations. C2 elements being simulated include: ISAF HQ; JIOC-A; CENTCOM JIOC Response Cell; an ISAF Regional Command; a Multi-National Combat Brigade TOC (Live); US, UK and Canadian Forward Operating Bases (FOBs) and multinational Provincial Reconstruction Teams (PRT); and, a Virtual Multi-national Combat Brigade Team. 4. MilestonesSubject to changes, the following milestones are to be used for planning purposes:a. Capabilities Submission Deadline: 13 Nov 09b. Capabilities Selection: 25 Nov 09c. Initial Planning Conference (IPC): 7-11 Dec 09, Tidewater area, VAd. Mid Planning Conference (MPC): 8-12 Mar 10, Tidewater Area, VAe. Final Planning Conference (FPC): 24-28 May 10, Tidewater Area, VA(Note: The Monday of each primary planning conference is dedicated to classified planning at a location TBA.) f. EC10 Execution (multiple locations in CONUS and overseas): Sep 105. A maximum of 20 Capability Insertions are expected for ultimate selection and participation in EC10. All submissions will undergo extensive adjudication based on the weighted requirements and preferences below. 6. Capability Requirementsa. Each participant must meet all the following criteria in order to be considered for participation in EC10: 1) Define how capability supports the EC10 objectives above2) Participate in EC10 spiral development events3) Have a government/agency sponsor4) Agree to provide information to coalition, multi-national and inter-agency partners5) Undergo a Net-Ready Assessment (or similar assessment type), depending on program maturity.6) Have obtained a minimum technical readiness level (TRL) of 4 (optimally 6 and/or Milestone B or higher) 7) Be self-funded8) Identify any existing International Traffic in Arms Regulations (ITAR) restrictions. b. Capabilities must provide defined concept of operations (CONOPS) and TTPs during the event planning process, preferably no later than the MPC. c. Capabilities must also work to ensure interoperability with the DCGS Enterprise.d. Documentation and information submitted to JFCOM by capabilities are considered and will be handled as "non-proprietary." e. Military or government civilian personnel will operate the capabilities during the execution phases. Required training and documentation will be provided by the capability at each EC10 event site (where technology is demonstrated). EC10 funds will not be provided for training.f. Capabilities will be required to provide on-site technical and operational representation throughout the EC10 planning and execution phases. EC10 funds will not be used to support this effort. g. Capabilities will be required to sign an Information and Data Sharing Understanding. The purpose of this document is to protect proprietary and sensitive information. 7. NetworksEC10 networks will simulate the current operational ISAF networks, to include bandwidth and other limitations, to the greatest degree possible. Additionally, EC10 will primarily execute on the multi-national network. EC10 will provide various configurations to support operations at SCI, U.S.-only SECRET, ISAF Mission SECRET and UNCLAS levels and associated networks. 8. Accreditation Candidates must use the DoD Information Assurance Certification and Accreditation Process (DIACAP), DoD Instruction 8510.01, to request and obtain Interim Authority to Test (IATT) on EC10 developmental networks for the execution phase of the event. Systems with an Authority to Operate (ATO), interim ATO (IATO) or IATT from a designated accreditation authority (DAA) will only need to submit accreditation documentation. Information Assurance (IA) controls addressed by enclave(s) are required to be published. The timeline for accreditation for network nodes will be completed no later than three (3) months prior to start of spirals. 9. Securitya. The following security requirements exist for all EC10 participants: 1) DoD SECRET clearance (at a minimum)2) NATO SECRET clearance (all those participating at the CJTF level)3) TS/SCI clearance (as applicable)b. All information and data will be handled in accordance with the Proper Use Memorandum (PUM) for ISR Derived Domestic GEOINT, Domestic Imagery Release (DIR) Policy, Freedom of Information Act (FOIA) and the various National Agency Distribution Guides. 10. Submission Format and Due Datea. Each proposed capability will submit a two-page white paper and a PowerPoint quad chart. The white paper (Arial, 12pt, 1" margins) must: 1) Describe capability functionality2) Identify specific support to JCTs and Objectives (paragraph 2 above)3) Provide answers to capability requirements (paragraph 6 above)4) Identify requirements for networks and communications, asset and personnel support5) Provide contact information for program and technical POCs.b. The quad chart must include a summary of white paper content (upper left); identification of JCT and Objectives support (lower left); a capability OV1 with information data flow (upper right); and, a description of capability maturity, funding status and support requirements (lower right).c. Classified capability submissions will be accepted. d. Capability submissions must be provided via email no later than 13 November 2009 to the POCs below: John Kittle: john.kittle@jfcom.mil; john.kittle.ctr@hq.jfcom.smil.mil; john.kittle@jfcom.ic.govRodney Brickell: Rodney.brickell.ctr@jfcom.mil; Rodney.brickell.ctr@hq.jfcom.smil.mil; Rodney.brickell@jfcom.ic.gov 11. This announcement is not a request for proposal; no contract award shall be made as a result of this announcement. EC10 Points of Contact are: John Kittle at (757) 836-0288 or Rodney Brickell at (757) 836-0287 or ec10@jfcom.mil.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVSUP/FISCDETPHILA/N0018910TZ008/listing.html)
- Record
- SN01986063-W 20091017/091015235109-ed08570f31db859aeaa2f90a06ec48f9 (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 |