SOURCES SOUGHT
A -- Mobility Command and Control Data Exchange (MC2DE) System
- Notice Date
- 3/11/2003
- Notice Type
- Sources Sought
- Contracting Office
- Department of the Air Force, Air Mobility Command, 305th CONS, 2402 Vandenburg, McGuire AFB, NJ, 08641
- ZIP Code
- 08641
- Solicitation Number
- Reference-Number-MC2DE-031103-1
- Archive Date
- 4/9/2003
- Point of Contact
- Michael Corson, Air Mobility Warfare Center - Senior Operations Analyst, Phone (609)754-7609, Fax (609)754-7651,
- E-Mail Address
-
michael.corson@mcguire.af.mil
- Description
- The US Air Force Air Mobility Battlelab plans to conduct a concept demonstration of a commercial/government off-the-shelf (COTS/GOTS) or emerging technology Mobility Command and Control Data Exchange (MC2DE) system. An MC2DE is needed to dynamically relate all of the information needed to plan and execute worldwide missions by creating publish/subscribe relationships between the information in disparate Air Force Command and Control (C2) systems, so that it appears or acts as if it were in a single shared database, or datacube. The datacube must be accessible by a multitude of users, from Mobility Air Forces (cargo and tanker aircraft) to Combat Air Forces (fighters and bombers) to civilian agencies and must update, in real-time, Notices to Airmen (NOTAMs), weather information, military operations data, and diplomatic clearance (DIPCLEAR) data. MC2DE must continuously compare the mission data with the global conditions data as well as with other missions through a publish/subscribe system. It must automatically notify the appropriate ground operators, whether in CONUS (i.e., Tanker/Airlift Control Center), or abroad (i.e., Combat Air Operations Center), or both, of potential conflicts before they occur. TECHNICAL DESCRIPTION: MC2DE must accept mission plans in a format consisting of spatial and temporal information of the right granularity to adequately describe when and where the missions/sorties will be at any given time. The mission array must also include additional attributes such as DIPCLEARs, aerial refueling, hazardous material, passengers, controlled takeoff time, controlled arrival or crossing times, etc. This collection of data must be published to a datacube, so that external agencies can see and subscribe to the data for changes (i.e., an air tasking order could subscribe to the sorties in the mobility cube and automatically be updated when a change in the sortie data occurs.) Data for each mission/sortie should subscribe to external data, whether formally published or not, so that a change in data, such as weather or a NOTAM at a corresponding time/place would trigger an update/action inside the domain to warn the user or automatically re-compute the flight plan, republish, and warn ground operators. Through this BAA, the Air Force is soliciting information concerning mature technologies, which meet the requirements previously stated, to be used in a Battlelab concept demonstration. The primary selection criteria for all submissions will be the most practical system readily available to support the requirements. All offerors are strongly encouraged to submit information supporting this request. Currently, there is only limited Battlelab funding identified for this program, however, if research indicates that the technology is available and transferable to the USAF, funding will be sought for prototype demonstration and recommended to Headquarters, Air Mobility Command. NOTICE TO FOREIGN OFFERORS: Foreign or foreign-owned offerors are advised that their participation is subject to foreign disclosure review procedures and restrictions that could preclude their participation in this announcement. SUBMISSIONS: Product Information may be submitted until COB EST 25 March 2003. Electronic responses shall be submitted in MS Word format or Adobe PDF file. Please use the following guidelines when submitting white papers: a) TECHNICAL APPROACH. Please provide a brief high-level technical description of the proposed Mobility Command and Control Data Exchange system (no more than 1-2 pages). Ideally, the technical approach should include a scenario illustrating the use of the proposed system. If applicable, pictures of the system are encouraged (soft copies preferred). b) RISKS. Briefly address all potential risks. Does the system rely on the performance of subcontractors? c) TRAINING REQUIREMENTS. Describe the type of training that will be required to operate your system? How long will the training take? Briefly summarize how personnel would deploy and operate the system. d) COMPATIBILITY. Explain system compatibility. e) ENVIRONMENTAL TESTING. State the type of environmental testing that has been performed on the system. What are the temperature and humidity limits within which the system will function properly? f) COST. What is the estimated cost or cost range of the proposed system, including low volume production numbers and high volume production numbers? g) AVAILABILITY. Provide system availability information. Is it available off-the-shelf right now? If not, how soon can it be made available? h) PREVIOUS WORK. Briefly explain any previous work you have done or are doing for military/civilian customers similar to what this BAA addresses (include demonstration information that supported that work). Refer technical questions and submit product information to the Air Mobility Battlelab?s technical representative: Mr. Ed Lillion of Concurrent Technologies Corporation via email at lillione@ctcnsc.com or mail to 100 CTC Drive, Johnstown, PA 15904-1935. The single point of contact concerning this Sources Sought Notice is Mr. Lillion . You may contact Mr. Lillion with any questions you may have at (814) 269-6516. Electronic submittals are strongly encouraged. GENERAL BAA INFORMATION: This notice itself constitutes the BAA as per FAR 6.102(d) (2). There shall be no formal RFP. The Air Force reserves the right to select for award, any, part of, all, or none of the proposals received. The Air Force may or may not purchase any of the technology demonstrated. This BAA is an expression of interest only and does not obligate the Air Force to pay any proposal preparation and prototype costs or to award any contracts, grants, cooperative agreements, or other transactions. Respondents are advised that only the Air Mobility Battlelab is legally authorized to commit the Government to the obligation of funds.
- Place of Performance
- Address: 100 CTC Drive, Johnstown PA
- Zip Code: 15904
- Country: US
- Zip Code: 15904
- Record
- SN00276743-W 20030313/030311213719 (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 |