C4ISR Conference 11/13/02 - Frequently Asked Questions
1. Q) You stated there would be a common API for all software packages. Do you have a common API now or do you plan to develop it?
A. We will release API Spec with the draft Specs and final RFP's.
2. Q) Will the C4ISR computing resource be generically applied to all FCS platforms? Is it the same as the vehicle management computer? Are the operator displays part of the C4ISR subsystem?
A. C4ISR computing resources will be applied across all platforms. The Vehicle Mgmt computer will not necessarily be the same as the C4ISR core computer. Operator display is part of the C4ISR subsystems.
3. Q) For C2 subsystems, will proposal evaluation be focused on proposed "product" or the "process" for selection of service providers?
A. Both - the performance of the "product" is dependent on the services.
4. Q) COMPUTERS - What Operating System will FCS use? Windows? VX Works? Lynxos? Linux? Other?
A. FCS C4ISR has selected the Linux OS.
5. Q) Which program will supply Radios for UAV's, UGV's sensor gateways, etc?
A. These radios will be procured through existing GOV'T programs. These are networked radios. Data link radios will be procured via industry.
6. Q) In your networked communications specification do you assure that this networked communications specification controls the WIN-T architecture and specifications or vice versa?
A. WIN-T is an external interface. There is an on going interface control working group to provide reach back req's out of the UoA. A common set of protocol and interface standards will be jointly developed between FCS & WIN-T.
7. Q) Will there be block 2 or 3 requirements for the ground vehicle multi-function radar to incorporate a Ka Band communication system. If so will this be separate from the baseline JTRS?
A. Yes, that is the current plan, No, it will not be separate from JTRS. The plan is for JTRS to have the high band capability.
8. Q) How do small businesses locate industry parties in areas where they feel they can make a significant contribution in a specific technical area?
A. Review website - submit unsolicited proposal. Proposals will be routed to the appropriate IPT. We have posted the BIA 1 and BIA 2 award recipients; we will post the list of Industry day participants also. We recommend you review that list.
9. Q) Are the presentation slides going to be available on the Website soon? A. Yes, They will be posted on the website by Wednesday, 11/20/02.
10. Q) Do you plan to have any special considerations for foreign companies to participate in FCS? The window of response thus far have been 2 weeks for BIA 1, 20 days (during August - European Holiday) for BIA 2 and less that a week for questionnaires.
A. No, Foreign companies have been given the same time consideration as domestic suppliers. To date we have several international vendors participating on the FCS program.
11. Q) How many winners for each C2 subsystems competitive packages in the SDD phase?
A. At least one; we may elect to award more based on funding and other considerations.
12. Q) How will the C2 RFP be structures? 1 RFP and multiple CLINS? How many suppliers will be selected?
A. There will be multiple RFP's to cover the six packages.
13. Q) How will the SDD procurement Process to executed: 1) Will the RFP's be electronically posted? 2) Will the responses to the RFP's be electronically transmitted in a manner similar to BIA responses? 3) What/Who will evaluate proposals - IPT leads, procurement managers?
A. 1) No, RFP's will be transmitted to those qualified bidders; 2) No, the bidders to their respective supplier mgmt. focal point will transmit response; 3) These will be evaluated by LSI engineering in conjunction w/their govmnt. counter parts. Source selections boards will be developed to include the LSI & govmnt. PMO.
14. Q) How can a company with COTS and/or GOTS in the information management area make those capabilities known to Boeing for consideration within Boeing development/integration?
A. Contact Boeing Supplier Management via the FCS website FAQ or unsolicited proposal mailbox.