Loren Data's SAM Daily™

FBO DAILY ISSUE OF JULY 11, 2008 FBO #2419
DOCUMENT

A -- Mobile Ad hoc Interoperability Network GATEway (MAINGATE) - Q&As

Notice Date

7/9/2008
 

Notice Type

Q&As
 

NAICS

541712 — Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology)
 

Contracting Office

Other Defense Agencies, Defense Advanced Research Projects Agency, Contracts Management Office, 3701 North Fairfax Drive, Arlington, Virginia, 22203-1714
 

ZIP Code

22203-1714
 

Solicitation Number

BAA08-21
 

Response Due

5/29/2009
 

Archive Date

6/13/2009
 

Point of Contact

BAA08-21,,
 

E-Mail Address

BAA08-21@darpa.mil
 

Small Business Set-Aside

N/A
 

Description

Amendment 2 to BAA08-21 Mobile Ad hoc Interoperability Network GATEway (MAINGATE) The purpose of Amendment 2 to BAA08-21 Mobile Ad hoc Interoperability Network GATEway (MAINGATE) is to make the following changes: 1. Page 10, Section 1.1.1 entitled Technical Description, under the heading “Wireless IP Network”, the sixth sentence is revised to read as follows: It also is envisioned that the higher frequency bands can exploit directional antennas and thus the goal is to increase the information rate to 100 Mbps using a gateway, and a high data rate disk data link system like Common Data Link (CDL) or Tactical Common Data Link (TCDL). 2. Pages 12-14, replace sections 1.1.2 through 1.1.4 in its entirety with the following: 1.1.2 MAINGATE Demonstration Plan Description The proposer is to provide a detailed demonstration plan with the proposal. The final demonstration will include the operation and evaluation of MAINGATE units and capabilities in simulated missions conducted by military, public safety, and coalition personnel. The venue will be at a CONUS location such as Ft. Benning GA, or Ft. Hunter-Leggitt CA, that provides complex urban and rural tactical environments. The proposed plan should include periods for equipment checkout and user training, estimated at 4 weeks, followed by independent user operations and assessments, estimate 4 weeks. A one-day VIP demonstration will also be conducted following the user assessments and should be provided in the proposed plan along with sufficient time for preparation. The final demonstration will showcase the comprehensive capabilities of the MAINGATE units and networks. It will include 13 MAINGATE units (mobile ground and airborne platforms) with the following characteristics providing interoperability among all specified legacy radios, SATCOM, and the GIG infrastructure: •One HQ Node •2 Airborne – include all aircraft safety and certification requirements •10 SUVs or similar vehicles •SUVs should contain the MAINGATE node with the following expectations: ­One MAINGATE system will contain the 6 radio interoperability capability ­9 SUVs will contain, at a minimum, 2 radio interoperability capabilities ­NOTE: specific radio types will be determined during demonstration preparation and execution. Interoperability for each of the eighteen radio types and one pair of SATCOM radios will be required. •A minimum of two additional radios for each of the eighteen radio types to be external to the MAINGATE nodes are required for experimentation and evaluation. •The proposal should describe quality of service types and enhancements to be incorporated •The proposer should include procurement of the combined, coalition, first responders/public safety, and similar radios in their proposal. NOTE: The proposer should consider appropriate spare MAINGATE systems, i.e. two, in their proposal to allow the best probability of success of the 13 node demonstration. The MAINGATE units are to provide reliable voice, video, and other data services (e.g. chat) in the range of tactical environments while under OTM and ATH conditions. They will be configured and operated by military personnel with the possibility of operation by coalition, first responder, and public safety users following a contractor-led training period. The scenarios conducted by the users will stress-test the MAINGATE units and capabilities to evaluate their ability to meet mission goals. The users will conduct the scenario operations with no contractor interaction and utilize automated network management. The scenarios will provide for an assessment of the interoperability of the combined, coalition, first responders/public safety, and similar types of radios described in Appendix A. The MAINGATE network should be able to support advanced tactical applications critical to modern tactical battlefield needs. It is anticipated that the transport of real-time video streams from networked analog and digital sensors to dismounted soldiers, maneuver force elements, and tactical operations centers will be a key element. The MAINGATE network should accommodate a minimum of 20 simultaneous video streams at a rate of 384 kbps as well as other applications such as voice, chat, situational awareness (e.g. FALCON View, C2PC), and network management. 1.1.3 MAINGATE Experimentation Plan Description The final product of the MAINGATE program will meet a TRL 6 prototype assessment per the guidance in Appendix B (i.e. and informal laboratory testing to a level consistent with operational environments). The proposal should provide sufficient detail regarding how that assessment will be accomplished to ensure consistency with the guidance provided in Appendix B. In addition to the TRL 6 assessment, proposers should provide a detailed experimentation plan for the evaluation of developed capabilities and performance. The plan must include a minimum of two (2) interim field experiments, estimated at 2-4 weeks each, as well as a final experiment. They are to be conducted at a CONUS location such as Ft. Benning GA, that provides complex urban and rural tactical environments. The duration and planned activities should facilitate a test-fix-test approach to equipment field checks as the contractors are expected to assess the capabilities and performance of the MAINGATE units under operational conditions, make appropriate changes, and conduct additional experiments with the new configurations. Each of the two requisite interim experiments will include 13 MAINGATE prototypes including two (2) units hosted on airborne platforms. Each unit will contain a LAN, WAN, MANET, and legacy network interfaces. Experimental scenarios will be conducted by contractor teams with some user participation. The proposed plan must specify the quantity of field experiments to be conducted, their planned dates of occurrence, duration, purpose, and performance metrics to be achieved. The plan should seek to achieve the final program metrics in a comprehensive scenario early in the program. The first of the two required interim experiments should occur early in the program. It should provide for interoperability between at least 11 legacy radios with any mix of radio types (analog and digital). Nine (9) of the MAINGATE ground mobile units are to support at least one (1) legacy network each, and at least one (1) of the MAINGATE ground mobile units is to support at least two (2) legacy networks. The proposed plan should include voice and data traffic types and specify the quantities of each. The experiments should include mobility, LOS, and NLOS/BLOS networking for the MANET. The MANET should support a mix of unicast and multicast traffic with variable data rates. The second of the two required interim experiments should occur mid program and provide for greater scope and performance than the first experiment, approaching or matching that of the target program metrics. It should provide for interoperability between eight (8) radio types plus SATCOM, including digital and analog radio types. Nine (9) of the MAINGATE ground mobile units are to support at least one (1) legacy network each, and at least one (1) of the MAINGATE ground mobile units is to support at least six (6) legacy networks. The proposed plan should include voice and data traffic types and specify the quantities of each. The experiments should include full mobility, LOS, and NLOS/BLOS networking for the MANET as well as SATCOM networking between multiple MAINGATE units. The MANET should support a mix of unicast, multicast, and broadcast traffic with variable data rates. In addition to the interim experiments, a final experimentation effort must be included in the proposal that provides for the comprehensive assessment of the final MAINGATE configuration, capability, and performance. The experiments should reflect the scenarios, legacy networks, network traffic, tactical environment, and operational characteristics specified in Appendix A and which are supportive of the TRL 6 assessment. The experiments will include the simultaneous operation of all 13 MAINGATE units as well as the requisite legacy radios. Nine (9) MAINGATE units will support two (2) legacy radio networks each, and one (1) MAINGATE unit will support six (6) legacy networks. The experiments will be conducted to assess interoperability between the 18 radio types plus SATCOM and include the ground mobile, airborne, and HQ MAINGATE units. As with all field activities, the final experimentation is to be conducted at a location such as Ft. Benning GA that provides complex environments. The proposer should plan for sufficient time to conduct test-fix-test operations, and allow sufficient lead time for the final demonstration. If appropriate, the proposer may plan to transition directly from the final experiments to the final demonstration efforts described above. 1.1.4 Government and Contractor Furnished Items for Demonstrations and Experiments The Government Shall Provide the Following •Operational scenario •Opposing force, as required •Spectrum survey, as required •Field facilities and logistics support as required for final demo •Allied radios, as required •Ground/Air platforms for design, as required The Proposer Shall Provide the Following •Satellite access/Frequency authorization as required •Applications like FALCONVIEW, and transport layer software, documentation, integration support, laptops and ancillary equipment required to support the applications •Test applications, laptops and ancillary equipment required to support the test applications •Test Director •Application and test application integration support for lab and field tests •Flight safety certification as required •Field facilities and logistics support as required for interim demo •SATCOM and/or ISR Feed of same type, Legacy Radios, commercial radios, and First Responder Radios •Test Vehicles Ground/Air vehicles, including drivers/pilots 3. Page 15, section 1.1.6 Deliverables, under subtitle Reports and Documentation, replace with the following to specify the use of Earned Value Management techniques: Reports and Documentation: •Phase requirements and architecture description document describing the gateway design •A documented unit production cost estimate that is consistent with the final design projections and discuss the path ahead for achieving the projected unit cost •A complete project schedule including milestones •Monthly reports including monthly cost, schedule, and status reporting using commercially accepted Earned Value Management techniques. •Test and evaluation plans for the two interim demonstrations, final demonstration, and associated experimentation and risk reduction activities •Final test reports detailing test results 4. Pages 15, replace section 1.1.8 entitled Oral Presentation and Demonstration Expectations, in its entirety with the following: The proposer is requested to plan for an oral presentation in Washington, DC, which include a discussion of all testing and experimental results showing technical maturity of their proposed hardware, based on the TRL guidance in Appendix A, in support of the technical and cost proposal evaluation. This event will occur not later than 60 days following proposal submittal, or a time negotiated between DARPA and the proposer. The oral presentation and demonstration are limited to 6 (six) hours each. The oral presentations should address at a minimum, discussions of TRL assessments, supportive documentation, and determination of the proposed components. Test data for TRL 6 components/subsystems should be documented in sufficient detail and in a form that the review team can assess the testing methods, statistical significance of the tests, and results for each component/subsystem proposed for the MAINGATE node. This information should follow the guidance given in Appendix A. This oral presentation time is not for discussion or clarification of the full proposal. However, the government may ask questions on proposals to help clarify any issues brought up during initial proposal review. The oral presentations and demonstrations should show that the proposer has met the basic program entry criteria to prove the proposed equipment, algorithm, network, etc. are mature enough to enter this program. The oral presentation also shall address an initial projection of the unit production cost estimate and discuss the path ahead for achieving the projected unit cost. See Appendix A for the appropriate TRL level description." 5. Page 22, Section 4.3.2.1 Volume I, Technical and Management Proposal, Section III, Detailed Proposal Information, G is revised as follows to address EVM: G. {3} Risk assessment and mitigation of key technical approaches and risk-based program management (i.e. EVM). 6. Page 27, Evaluation Section 5.1.4 entitled Proposer’s Experimentation and Demonstration Technical Approach, Schedule, Execution Plan, and Risk Description, replace in its entirety with the following to include EVM: 5.1.4 Proposer’s Experimentation and Demonstration Technical Approach, Schedule, Execution Plan, and Risk Description. The proposers’ description of technical integration and system design will be analyzed with respect to demonstrated ability to execute an experiment and demonstration plan. The plan should describe how the program metrics, schedule, documentation, and execution will lead to providing appropriate reporting. The proposer’s abilities to aggressively pursue performance metrics in the shortest timeframe and to accurately account for that timeframe will be evaluated, as well as proposer’s ability to understand, identify, and mitigate any potential risk in schedule. The following will be evaluated based on contents of the proposal. •The proposer’s experiment and demonstration plan, objectives, technical detail, and metrics •The proposed program schedule/milestones and the development schedule/milestones and whether they will result in a system capability that meets or exceeds the MAINGATE vision and objectives •Relationship of demonstration to transition objectives •Resource requirements and associated risk for critical items •Proposer’s ability to understand, identify, and mitigate any potential risk in cost and schedule managed by EVM techniques. •The plan to validate and demonstrate the network performance objectives (i.e., scalability, interoperability, robustness, etc.) of the network technologies 7. Page 43, the following replaces the “Test Site” and “Test Duration” entries in the table in Appendix A, Test Sites Interim Test Site Final Test Site Interim Test site to be proposed by performer (terrain similar to Ft. Benning) Final Test Site expected to be Ft Benning/Hunter Leggitt, subject to negotiation. Test Duration Interim: 2 x 2-4 week periods Final: 10 weeks Inclusive of setup, personnel training, testing, and demonstrations 8. Solicitation questions and answers are attached.
 

Web Link

FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=8a7733d135723d4b8dbd29ed1cb418c0&tab=core&_cview=1)
 

Document(s)

Q&As
 

File Name: (maingate_baa_qna_as_of_7july___public__3_.pdf)

Link: https://www.fbo.gov//utils/view?id=5ac34f5a910a2a2b6c1c17fb13615711

Bytes: 35.06 Kb
 

Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 

Record

SN01610350-W 20080711/080709222740-8a7733d135723d4b8dbd29ed1cb418c0 (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 |