SOURCES SOUGHT
A -- WEAPON DATA LINK NETWORK
- Notice Date
- 2/23/2004
- Notice Type
- Sources Sought
- NAICS
- 541990
— All Other Professional, Scientific, and Technical Services
- Contracting Office
- Department of the Air Force, Air Force Materiel Command, AAC - Air Armament Center, AAC/PK 205 West D Avenue, Suite 433, Eglin AFB, FL, 32542-6864
- ZIP Code
- 32542-6864
- Solicitation Number
- Reference-Number-YEC-RFI-01
- Response Due
- 3/8/2004
- Archive Date
- 3/23/2004
- Point of Contact
- Craig Pope, Contracting Officer, Phone (850)882-3075, Fax (850)882-1873, - Craig Pope, Contracting Officer, Phone (850)882-3075, Fax (850)882-1873,
- E-Mail Address
-
craig.pope@eglin.af.mil, craig.pope@eglin.af.mil
- Description
- SPECIAL NOTICES OFFICE ADDRESS: AAC/YEC 207 West D Ave, Ste 301, Eglin AFB, FL 32542-5417 SUBJECT: WEAPON DATA LINK NETWORK DESC: This is a Request for Information (RFI) concerning weapon connectivity to networks. Responses to this RFI will be used by the Government to plan a possible future Advanced Concept Technology Development (ACTD) effort. THE GOVERNMENT DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS OF THIS RFI OR TO OTHERWISE PAY FOR THE INFORMATION SOLICITED. The Air Armament Center, Armament Enterprise Program Office, Concept and Technology Development Division is seeking information regarding technology challenges and solutions involved in dynamically connecting weapons to networks (including Intelligence, Surveillance and Reconnaissance (ISR,) Command and Control (C2) nodes, strike assets, etc.) that enable improved precision, responsiveness, impact indications and battlespace awareness. Several weapons will soon need to adopt datalinks that would enable these functions, but currently there is no standard approach to integrating weapons into C2 networks. A solution is desired for implementing the following capabilities: - In-Flight Target Updates (post aircraft weapon release) from any network participant: Refine Target Location Uncertainty (TLU) for targets during weapon ingress. - Bomb Impact Assessment (BIA): Transmit to network just prior to impact. - Weapon In-Flight Tracking: Provide weapon’s location and status to the network. - Re-targeting: Attack pop-up targets while en route. - Abort on Command: To avoid collateral effects. Current networks provide good connectivity, but available network standard terminals are not small enough to integrate into weapons (and other terminals are not widely fielded). This size issue is being addressed by the Air Force Research Lab (AFRL) but will take several years to complete. Network architecture issues must be resolved to facilitate future integrations, while also accommodating datalink solutions using UHF SATCOM. A network weapons Interface Control Document (ICD) will be developed with a goal of benefiting the joint services. A potential ACTD is planned to address the following issues: - Standardize weapon message set and information exchange requirements - Standardize uses and meanings of weapon data within message sets - Standardize network/time slot allocation process for weapons - Explore Combined Air Operations Center (CAOC) and network design requirements for weapon control - Explore limits of network for handling numerous weapons simultaneously - Explore Concept of Operations for networked weapons and network design This ACTD will design and exercise a realistic tactical network that enables network-centric weapon operations, demonstrating the following: - Allocation of network time slots to weapons - UHF messaging via gateway to network - Inclusion of other network participants (e.g., CAOC, ground forward air controller, shooter) - Information transfer required to implement desired datalink benefits—BIA, re-targeting, etc. This ACTD will reduce risk for the integration of network-centric weapons in general, by defining architectures, interfaces, messages and tactics needed to allow weapons to function within the networks of today and tomorrow. Respondents will also be asked to provide a recommendation for an appropriate weapon Software Communication Architecture (SCA) compliance definition. As part of this recommendation, the respondent should identify the main cost drivers for SCA implementation in weapons applications. The Air Force contemplates an arrangement in which the winning contractor will have responsibility for all integration tasks via Associate Contractor Agreements with those firms which developed and maintain other elements of the Weapon Data Link Network system of systems. These elements are expected to include: - Weapon Data Link brassboard provided by AFRL or other suitable solution - Combined Air Operations Center software and systems integration - Tactical Air Control Party radios and associated software - Flight test aircraft (slow-moving, non-military airplane of convenience) - Weapon prime contractors (JASSM-ER, WCMD-ER, SDB Increment 2, JSOW C, Harpoon 21, Tactical Tomahawk, etc.) - Weapon surrogate
- Web Link
-
Link to FedBizOpps document.
(http://www.eps.gov/spg/USAF/AFMC/AAC/Reference-Number-YEC-RFI-01/listing.html)
- Record
- SN00528984-F 20040225/040223225516 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |