ESC/AC. Combat Air Forces C2 Systems, 50 Griffiss Street Hanscom AFB, MA 01731-1642

D -- TIME CRITICAL TARGETING (TCT) CELL DESIGN AND FIELDING SOL F19628-00-R-0063 DUE 081800 POC Ms. Carol Quinlan, (781) 271-8499 WEB: ESC Business Opportunities Web Page, http://www.herbb.hanscom.af.mil. E-MAIL: Click Here to E-mail the POC, QuinlanC@hanscom.af.mil. This is a Sources Sought Synopsis in support of a market survey being conducted by the Air Force to determine interest and capabilities of potential sources. This synopsis is for informational and planning purposes only and does not constitute a solicitation, or a synopsis of a solicitation, or a commitment on the part of the government to later publish a solicitation. The government will not reimburse the costs of preparing or submitting a response to this synopsis. Any information submitted in response to this sources sought synopsis is strictly voluntary. Any questions should be submitted to the contracting officer listed above. The Electronic Systems Center, Combat Air forces Command and Control Directorate, serving as the Executive Agent for the Aerospace Command, Control, Intelligence, Surveillance and Reconnaissance Center (ASC2ISRC), seeks to develop and field a Time Critical Targeting (TCT) Cell. The TCT Cell will enable the Combat Air Force's (CAF) Air Operations Centers (AOCs) to greatly reduce the timeline to find, fix, track, target, engage, and assess TCTs. A Time Critical Target (TCT) is defined as a time sensitive target with an extremely limited window of vulnerability or opportunity, the attack of which is critical to ensure successful completion of the Joint Force Commander's operations. By definition, TCTs rank high on the Joint Integrated Prioritized Target List. A successful TCT Cell will incorporate intelligence preparation of the battlespace applications, terrain analysis applications, target development and nomination applications, weapon-target pairing applications and other applications and data as may be appropriate to yield an integrated capability. The integrated capability thus created will successfully identify TCTs and make knowledge-based weapon tasking recommendations within the threshold timelines outlined in the Draft Time Critical Targeting (TCT) Cell Operational Requirements Document (ORD) dated 20 Jun 00. The ORD will be available upon request. The TCT Cell will interface with Theater Battle Management Core System (TBMCS) [Lockheed Martin contract] services and become an integral part of the AOC Combat Operations Division. TCT Cell will be an essentially dependent configuration of integrated software applications on common workstations, servers, and necessary modules to interface with new or organic, existing communications of the supported Air Operations Center. TCT component parts will feature "plug and play" capability to draw from the C2 node's existing support infrastructure for power, connectivity, and data support. The TCT Cell will conform to the rapidly deployable, small footprint construct of the Expeditionary Air Force (EAF). At the same time, an accommodation must be made for graceful degradation in TBMCS or other support to TCT Cell (particularly NRT database segments on TCT servers, alternate communication paths to receive Moving Target Indicator (MTI) feeds or to task assets, etc.). This will allow continued processing of available TCT information as the operator may see fit to employ and to satisfy key performance parameters (KPPs) outlined in the Draft TCT ORD (referenced above). Following successful operational test of the first system, it is envisioned that software and hardware to support TCT Cell will be deployed at an additional four operational locations worldwide. A prototype TCT Cell, known as the Software Interoperability Facility for TCTs (SWIFT), has been developed by a contracting team led by Zel Technologies, LLC and including ALPHATECH and TRW. The SWIFT, currently operating at the Electronic Systems Center, Hanscom AFB, MA, consists of a UNIX-based COTS hardware suite configured with a baseline set of TCT applications running on the TBMCS v 1.0.1, build 2.1.3.5 and the Defense Information Infrastructure Common Operating Environment (DII COE) v. 3.3.0.0. The current SWIFT effort integrates the following TCT applications: Automated Assistance with Intelligence Preparation of the Battlespace (A2IPB). Time Critical Targeting Aid (TCTA) FY 97 Plus,Attack Operations Decision Aid (AODA) and Joint Terrain Analysis Toolkit (JTAT). Additional enhancements and software application interfaces are envisioned to be added to the production TCT Cell to meet objective operational requirements as outlined in the Draft TCT ORD (above). Examples include the ability to manage Intelligence, Surveillance and Reconnaissance assets via an interface to ISR Battle Management (ISR BATMAN) prototype software. Another example is to provide theater missile event and warning information via an interface to Launch and Impact Prediction software (Enhanced Early Warning software application [E2W]) as well as an interface to Nuclear, Biological, Chemical Dispersion Prediction software. The production design will consider these and other applications with a plan and timetable for insertion into the production system. TCT Cell is intended to augment existing TBMCS hardware and software capabilities. TCT Cell software applications and hardware will fall under the same maintenance management and support concept employed for TBMCS. A contract will be awarded in FY01 to include elements for design, development, integration test and deployment of a fielded TCT capability at five locations, software enhancements through FY 07 and a training and support package for the life of the system. The five TCT Cell systems will be delivered over a 3 year period beginning in FY 03. Interested contractors should submit a qualification package to the contracting officer named above not later than 5 Sep 00. The qualification package should outline the following: a. Experience and familiarity with theater and tactical battle management command and control systems and architectures, including communications systems and interfaces; b. Specific development and integration experience with time critical targeting software applications and/or near real time software applications; c. Experience in developing Defense Information Infrastructure Common Operating Environment (DII COE) and Joint Technical Architecture (JTA) compliant systems; d. Experience with Theater Battle Management Core Systems (TBMCS) Software Developer's Kit (SDK) and TBMCS application segment development; e. System administration experience with a multi-server, multi-client system; f. Knowledge of intelligence preparation of the battlespace, terrain and mobility analysis, ground target detection and development, and weapon-to-target pairing functionalities; g. Proven capabilities in design, development, integration and test of software applications; h. Approved capability to handle, store and process classified information via current US Secret facility clearance (see provisions of DOD-5220.2-M, DOD-5220.22-R); i. Specific experience in systems fielding, operator training and systems support. All respondents must supply the following: Company name, address, CAGE code, point of contact (POC) for information, size of business, US or foreign owned. The following Command and Control system documentation is available at the website addresses as shown: Specifications Version 4.0, CM-28667, October 1999 http://dod-ead.mont.disa.mil/cm/irts/current/I&; RTS4.0.zip DII COE User Interface Specifications v 4.0, CM-27986, 06 October 1999 http://dod-ead.mont.disa.mil/cm/uis/Final/uis.zip JMTK API Descriptions JMVSDK Programmer's Guide and Reference Manual (Draft) Version 4.2.0.0, CM-31557, 22 March 2000 http://dod-ead.mont.disa.mil/cm/dii42/icsf_cd/PGRM_JMV/doc/jmvpg.htm Appendix A, Zm Application Program Interface (API) to above http://dod-ead.mont.disa.mil/cm/dii42/icsf_cd/PGRM_JMV/doc/jmvpg_a.htm NOTE: JMA, JMS, and JMU API documentation for Version 4.2.0.0 not currently available on public sites. JMA and JMS documentation for Version 4.1.0.0 is available as listed below: Application Program Interface Reference Manual (APIRM) JMTK Analysis SDK (jmaSDK) v 4.1.0.0, CM-26845, 06 AUG 99 http://dod-ead.mont.disa.mil/cm/dii/jmtk_segmnts_(jmasdk)/v4100_sol7_nt_hp /26845_apirm.pdf Application Program Interface Reference Manual (APIRM) for JMTK SDBM SDK (jmsSDK) v 4.1.0.0, CM-26873, 06 AUG 99 http://dod-ead.mont.disa.mil/cm/dii/jmtk_sdbm_sdk_(jmasdk)/v4100_sol 7/26873_apirm.pdf Other Associated Documentation Integrated C4I System Framework (ICSF) Version 4.2.0.0 Documentation (Contents include documentation for: ICSF, AFW, IFL, JMV, TMS, TMSV, UCP, AFWSDK, IFLSDK, JMVSDK, TMSSDK, UCPSDK), CM-31501, 22 March 2000 http://dod-ead.mont.disa.mil/cm/dii42/icsf_cd/ICSFDocs.html DII COE Visualization Services Software Requirements Specification (SRS) (Draft), February 9, 1999 http://diicoe.disa.mil/coe/srs/srs_base/viz399.doc Documents on password protected JMTK FTP site To access this site, request username and password by contacting Mr. Mel Wagner at (202) 264-5500; e-mail: wagnerm@nima.mil. DII COE Software Requirements Specification (SRS) for Mapping, Charting, Geodesy, and Imagery (MCG&I) Version 4.1, 29 February 2000 ftp://ftp.jmtk.org/cots/SRS.doc DII COE Commercial Mapping Certification Program, Pilot Program Draft -- Version 0.2, 31 December 1998 ftp://ftp.jmtk.org/cots/DISA_COTS_Plan.pdf (W-146 SN458692)!!***** An Acquisition Ombudsman, Colonel Joseph B. Magnone, Director, Commander's Staff, has been appointed to hear concerns from offerors or potential offerors during proposal development. You should only contact the Ombudsman with issues or problems you cannot satisfactorily resolve with the program manager and/or contracting officer. The Ombudsman role is to hear concerns, issues, and recommendations and communicate these to the appropriate government personnel. The Ombudsman will maintain strict confidentiality if desired. The Ombudsman does not evaluate proposals or participate in source selection. You can contact the Ombudsman at (781) 377-5106. See Note 26. Posted 08/02/00 (D-SN481064). (0215)

Loren Data Corp. http://www.ld.com (SYN# 0049 20000804\D-0020.SOL)

| D - Automatic Data Processing and Telecommunication Services Index  |  Issue Index |