|
COMMERCE BUSINESS DAILY ISSUE OF DECEMBER 7,1999 PSA#2490Defense Advanced Research Projects Agency (DARPA), Contract Management
Directorate (CMD), 3701 N. Fairfax Dr., Arlington, VA 22203-1714 A -- DYNAMIC ASSEMBLY FOR SYSTEMS ADAPTABILITY, DEPENDABILITY, AND
ASSURANCE 9DASADA) SOL BAA 00-20 DUE 020100 POC Dr. John Salasin,
DARPA/ISO, Fax (703) 696-2203 or Contractual POC: Ms. Algeria Tate, Fax
(703) 696-2208 WEB: http://www.darpa.mil, http://www.darpa.mil. E-MAIL:
BAA00-20@darpa.mil, BAA00-20@darpa.mil. DARPA is soliciting proposals
to develop and demonstrate technology that will enable systems to meet
complex needs under a program called Dynamic Assembly for System
Adaptability, Dependability and Assurance (DASADA). As military
software systems become more complex, it is evident that they must be
able to change themselves by swapping or modifying components, changing
component interaction protocols, or changing topology. They must do
this dynamically, while the system is operating. Outputs from this
program will ensure that the critical properties of complex,
heterogeneous software systems are maintained during and after
composition, adaptation and deployment. Emphasis is on developing
gauges to assess the suitability of components including commercial
government off the shelf (GOTS), open source, or other codes for
insertion and use in a specific system. System complexity results from
the following: a) Partial understanding of the relationship between
physical structure and behavior of the system; b) Multiple, essential,
interdependent behaviors (e.g. to support functional, safety,
reliability, security requirements and c) Dynamic behavior in both
component behavior and topology. Survivability and changing operating
conditions require adaptation and self-correction. It is not feasible
to completely model these increasingly complex systems. Therefore,
since successful system implementation is based on having models that
are accurate with respect to critical properties, we cannot understand
them, predict them, control them, or automatically compose or adapt
them. While better modeling techniques are needed, we also need to
combine these techniques with an ability to adapt systems (and the
models) based on observing the behavior of running systems.
Particularly for critical military systems, we need to make changes
predictably to ensure safety and reliability. DASADA will build on
previous technology efforts in the areas of: a) Design -- to assess the
suitability of existing or new, off the shelf or automatically
generated components for insertion in a system before assembly,
allowing automated (controlled) assembly and on-the-fly transformations
that produce predictable, safe systems; b) Coordination -- to assess
the correctness of a composition operation during assembly, allowing
reconfigurations to be conducted safely across heterogeneous,
distributed dynamic systems and; c) Validation -- to allow continual,
run-time validation of critical system properties. To achieve this
vision, we have to create (through design or recovery) a description of
a system's architecture, a specification of critical properties (which
may or may not be supported by the present system), and requirements
for change. Previous work in several DARPA programs, most recently the
"Evolutionary Design of Complex Software (EDCS)" has provided useful
lessons, languages, and techniques. More information is available at:
a) http://www.darpa.mil/ito/research/edcs/index.html, b)
http://www.if.afrl.af.mil/programs/edcs, and c)
http://www.if.afrl.af.mil/programs/edcs/demo-days-99/EDCS-99-Demos-Ind
ex.html. PROGRAM OBJECTIVE: The DASADA Program objective is to develop
dynamic gauges or measures of component composability or
interoperability. These gauges should: a) Determine the suitability of
components for insertion / (re)use in a given system; b) Enable safe
run-time composition and deployment; c) Enable continual monitoring of
the system to guide adaptation and d) Ensure that critical (user
defined) properties are maintained during and after composition,
adaptation, and deployment. PROGRAM SCOPE: The DASADA Program will
develop new technology to support software composability and will
transition technology to a limited number of system application
experiments. The program is anticipated to proceed in two overlapping
phases: a) technology development projects to be conducted in two (2)
cycles of 22-24 months each, and b) large scale service-led experiments
to demonstrate key results and /or new ideas generated by the
technology development phase in a more realistic setting. Only the
first cycle of phase one will be addressed by this BAA. ADDITIONAL
CONSIDERATIONS: Offerors should identify the specific area(s) they are
addressing. In their proposals, they should describe the requirements
of the area from their perspective, describe the key technical
challenges and identify why they are a challenge. They should describe
their approach and outline the key attributes that may lead to
success. Proposals that address greater parts of the problem space,
through innovative integration of component technologies, are highly
desired. Technologies with application to DoD systems are also
preferred and will receive higher priority for funding in the
experiment phase. Technology developers are strongly encouraged to form
teams and to share technologies. FUNDING SUMMARY: Funding will be
available in late FY00, however, it is anticipated that the majority of
work will be done in FY01-FY02. It is estimated that 10-12 technology
projects, with durations of 22 to 24 months each, may be funded at a
total cost of $500K to $1 million per project. GENERAL INFORMATION:
DARPA will not accept classified proposals to BAA 00-20. Proposers must
submit an original and three (3) hard copies of full proposals, i.e.,
Technical -- Volume I and Cost -- Volume II; and three electronic
copies of the complete proposal on separate floppy disks. Proposals
must be submitted to DARPA by 4:00 PM local time on 01 February 2000,
in order to be considered. Proposers must obtain the BAA 00-20 Proposer
Information Pamphlet (PIP) that provides further information on the
areas of interest, submission, evaluation, funding processes, and full
proposal formats. The PIP may be obtained by electronic mail, world
wide web, or mail request to the administrative contact address given
below, as well as at URL address: http://www.darpa.mil/baa00-20.
Proposals not meeting the format described in the PIP may not be
reviewed. This Commerce Business Daily notice, in conjunction with the
Proposer Information Pamphlet, constitutes the total BAA. No
additional information is available, nor will a formal RFP or other
solicitation regarding this announcement be issued. Requests for same
will be disregarded. Proposals submitted by fax will be disregarded.
The Government reserves the right to select for award all, some, or
none of the proposals received. All responsible sources capable of
satisfying the Government's needs may submit a proposal that shall be
considered by DARPA. Historically Black Colleges and Universities
(HBCU) and Minority Institutions (MI) are encouraged to submit
proposals and join others in submitting proposals. However, no portion
of this BAA will be set aside for HBCU and MI participation due to the
impracticality of reserving discrete or separable areas of this
research for exclusive competition among these entities. EVALUATION
CRITERIA: Evaluation of proposals will be performed using the following
criteria in order of importance: (1) Overall scientific and technical
merit. Consideration will be given to both the technology planned to be
produced and the approaches to be used to ensure that the technology
does (or can) produce the benefits claimed. (2) Understanding of
problem and relevance of research effort to DASADA objectives.
Evaluation of projects will be based on the extent to which they
support dynamic assembly (or re-assembly) of components and on the
specificity with which they define "gauges" to assess properties of
components and systems. These gauges should have the capability of
assuring critical properties of "off the shelf" or "open source"
components with respect to the requirements of a given system. (3)
Capabilities, related experience, and qualifications of proposed
project personnel. Teaming is encouraged. (4) Stated contribution and
relevancy to DoD application. Evaluation of projects will be based on
the extent to which they show a match between the technology/gauges
they develop and DoD system requirements, where the requirements are
relevant to a family of systems, as opposed to a narrow niche. (5) Cost
realism/reasonableness or best value. The overall estimated cost to
accomplish the effort should be clearly shown as well as the
substantiation of the costs for the technical complexity described. The
evaluation will consider the value to Government of the research and
the extent to which the proposed management plan will effectively
allocate resources to achieve the capabilities proposed. Teaming among
technology developers to share technologies is strongly encouraged.
ORGANIZATIONAL CONFLICT OF INTEREST: Awards made under this BAA are
subject to the provisions of the Federal Acquisition Regulation (FAR)
Subpart 9.5, Organizational Conflict of Interest. All offerors and
proposed subcontractors must affirmatively state whether they are
supporting any DARPA technical office(s) through an active contract or
subcontract. All affirmations must state which office(s) the offeror
supports and identify the prime contract number. Affirmations shall be
furnished at the time of proposal submission. All facts relevant to
the existence or potential existence of organizational conflicts of
interest, as that term is defined in FAR 9.501, must be disclosed. This
disclosure shall include a description of the action the Contractor has
taken, or proposes to take, to avoid, neutralize or mitigate such
conflict. If the offeror believes that no such conflict exists, then it
shall so state in this section. Restrictive notices notwithstanding,
proposals may be handled, for administrative purposes only, by the
support contractor, Schafer Corporation. The support contractor is
prohibited from competition in DARPA technical research in DARPA /ISO
and is bound by appropriate non-disclosure requirements. Only
Government officials will evaluate the proposals. Posted 12/03/99
(W-SN405687). (0337) Loren Data Corp. http://www.ld.com (SYN# 0004 19991207\A-0004.SOL)
A - Research and Development Index Page
|
|