BAA #01-06
Networked Embedded Software Technology (NEST)
Frequently Asked Questions

1.                  What is Time-Bounded synthesis?  
The size of NEST configurations, their tight integration with dynamic, non-stationary physical processes and limitations in component reliability make the use of self-assembly, self-configuration, self-repair and other forms of adaptation mandatory. These capabilities mean that synthesis of control sequences, schedules, processing configurations, resource maps, etc. – usually performed at design time – will become part of real-time (i.e. time-bounded) NEST operations. 

2.                  What is Group 1 and Group 2? 
Group 1 projects focus on the technical topic areas defined for the NEST programs:  (a) Application Independent Coordination Services, (b) Time-bounded Synthesis, (c) Service Composition and Adaptation, and (d) Other innovative approaches to the NEST problem. Group 2 projects develop open experimental platforms for the evaluation and integration of Group 1 technologies in real-life challenge problems. 

3.                  What are the typical NEST applications?
Many of the motivating applications are coming from MEMS research. See examples at the web site of DARPA-MTO’s MEMS program: http://www.darpa.mil/MTO/MEMS/index.html 

4.                  What is the amount of funding? 
Funding amounts will not be released. 

5.                  How many proposals will be funded? 
The number of proposals to be funded in the different technical topic areas is listed in the PIP. 

6.                  What kind of coordination exists between Group 1 and Group 2? 
There is no pre-proposal coordination between Group 1 and Group 2 projects. Coordination will be done during program execution. 

7.                  Can you have a foreign company on a proposal? 
DARPA’s decisions on working with foreign companies is made on a case by case basis. 

8.                  What is the view on Cost sharing?
There is no cost sharing expectations in Group 1 research.  It is expected that OEP proposals (Group 2 proposals) represent an “end-user” perspective for the NEST technologies. Industrial participation, teaming and cost sharing arrangements are strongly encouraged. 

9.                  Do you expect a proposal to address a single area in Group 1?
No. However, proposals addressing more than one of the areas described in the BAA and PIP should be structured with separable options. 

10.              What is the difference between NEST and MoBIES and PCES?
MoBIES focuses on design technology (tools, environments) for large-grain embedded applications. PCES will create new aspect-oriented programming support that enables the separation of design views using aspect code. NEST builds middleware for dependable, real-time, distributed, embedded applications comprising 10^2-10^5 computing nodes. 

11.              Are Micro/Nano Satellite applications relevant?
Yes, see answer to Q3. 

12.              OEP platform providers should own a distributed application area?
The program does not intend to invest heavily in the development of specific distributed control (or other relevant) applications. An “ideal” OEP platform provider is familiar with a particular NEST application category, has clear understanding of computational requirements and can leverage existing results in providing inexpensive, well instrumented and open experimental platform for technology projects. 

13.              Do you have any hard milestones in your mind? 
At this point the only hard requirement is that the first release of the OEP should occur no later than one year after the start of an award. 

14.              Is there any feeling to how many nodes the OEP shall require?
Should be in the range stated in the BAA and PIP.  The more scalable is the better. 

15.              Are we to assume that the Group 2 will include heterogeneous systems?
No restrictions exist in this sense.