darpa baa 10 86 mil draft

8/3/2019 DARPA BAA 10 86 mil DRAFT

1/32

1

Broad Agency Announcement

vehicleforge.mil

Tactical Technology Office

DARPA-BAA-10-86

XX August 2010


2/32

2

Table of Contents:

Part I: Overview Information.5Part II: Full Text of Announcement

Sec. I: FUNDING OPPORTUNITY DESCRIPTION...................................7Sec. II: AWARD INFORMATION.7Sec. III: ELIGIBILITY INFORMATION..9

A. Eligible ApplicantsB. Cost Sharing/MatchingC. Other Eligibility Criteria

Sec. IV. APPLICATION AND SUBMISSION INFORMATION11A. Address to Request Application PackageB. Content and Form of Application

SubmissionSec. V. APPLICATION REVIEW INFORMATION...24

A. Evaluation CriteriaB. Review and Selection ProcessSec. VI. AWARD ADMINISTRATION INFORMATION..26

A. Award NoticesB. Administrative and National Policy RequirementsC. ReportingD. Electronic Systems

Sec. VII. AGENCY CONTACTS.32Sec. VIII. OTHER INFORMATION..33

A. Intellectual PropertyB. Non-Procurement Contract Proposers Noncommercial and

Commercial Items (Technical Data and Computer Software)C. All Proposers Patents


3/32

3

Part I: Overview Information

Federal Agency Name Defense Advanced Research Projects Agency (DARPA),Tactical Technology Office (TTO)

Funding Opportunity Title vehicleforge.mil

Announcement Type Initial Announcement Funding Opportunity Number Broad Agency Announcement (BAA) 10-86

Catalog of Federal Domestic Assistance Numbers (CFDA) Not Applicable

Dateso Posting Date:o Deadline for Questions: [+10 days from posting]o Proposal Due Date: [+60 days from posting]

Concise description of the funding opportunity Development and operation of anopen source development collaboration environment and website for the creation oflarge, complex, cyber-electro-mechanical systems by numerous unaffiliateddesigners.

Total amount of money to be awarded $12.85 million

Anticipated individual awards Multiple awards are anticipated

Types of instruments that may be awarded Procurement Contract or OtherTransaction

Agency contacto Point of Contact

The BAA Coordinator for this effort can be reached at, fax: (703) 248-1861,electronic mail: [email protected]. Or by mail:DARPA/TTOAttn: BAA 10-86

3701 North Fairfax DriveArlington, VA 22203-1714
mailto:[email protected]:[email protected]


4/32

4

Part II: Full Text of Announcement

I. FUNDING OPPORTUNITY DESCRIPTIONThe Defense Advanced Research Projects Agency often selects its research effortsthrough the Broad Agency Announcement (BAA) process. The BAA will appear first onthe FedBizOpps website, http://www.fbo.gov. The following information is for thosewishing to respond to the BAA.

Background

The development of complex software systems has benefitted significantly from theability to leverage crowd-sourced innovation in the form of open source codedevelopment. Open source software hosting sites, a key enabler to the success of thisdevelopment paradigm, facilitate collaborative development, source tree maintenance,

and version control while allowing participation by a large number of independentprogrammers. Examples include SourceForge, Google Code, and GNU Savannah.1 Theapplication of open source methods to the development of electromechanical systems hasbeen more limited. And while one can identify several successful examples, they arelargely confined to the development of relatively simple products (e.g., Quirky2 forconsumer product design), or have required significant back-end engineering effort toturn product concepts into detailed designs (e.g., Local Motors3 for custom cars).

DARPA has launched a portfolio of programs that aims, among other objectives, todemocratize the design process for complex cyber-electro-mechanical systems4 such asdefense and aerospace vehicles. The goal is to enable large numbers of unaffiliated

developers to participate in the design of militarily-relevant systems such as groundvehicles, airplanes, rotorcraft, and space systems. To that end, DARPA is solicitingproposals for the development ofvehicleforge.mil, an open source hosting site for thecollaborative development of these systems. The principal technical challenge associatedwith this capability is a general representation language that is rich enough to describe abroad range of cyber-electro-mechanical systems, yet formal enough that the system canbe compiled or verified in some manner when a design change is made to someelement or aspect of it.

The present vehicleforge.mil solicitation is part of a broader portfolio of programs thatalso includes META5 and META-II,6 as well as iFAB,7 Manufacturing ExperimeNT &

1 http://www.sourceforge.net, http://savannah.gnu.org, http://code.google.com/hosting/2 http://www.quirky.com3 http://www.local-motors.com4 By cyber-electro-mechanical systems we mean the general class of systems that contain software,electronic, and mechanical components.5 https://www.fbo.gov/spg/ODA/DARPA/CMO/DARPA-BAA-10-21/listing.html6 https://www.fbo.gov/spg/ODA/DARPA/CMO/DARPA-BAA-10-59/listing.html7 https://www.fbo.gov/spg/ODA/DARPA/CMO/DARPA-BAA-10-85/listing.html


5/32

5

OutReach (MENTOR),8 and the future Fast, Adaptable Next-Generation (FANG) GroundCombat Vehicle effort. META and META-II seek, among other objectives, thedevelopment of precisely the kind of metalanguage to represent a broad range of cyber-electro-mechanical systems, as described above, along with design and verification toolsto facilitate its use. To the extent that this capability enables the model-based

development and verification of systems that are correct-by-construction (at least in aprobabilistic sense), this is tantamount to a generalization of the fab-less design capabilitythat exists today for relatively narrow classes of systems such as integrated circuits. iFAB(Instant Foundry Adaptive through Bits), then, seeks the development of a foundry-stylemanufacturing capability that is bitstream-reconfigurable to manufacture a broad range ofelectro-mechanical systems. MENTOR is an analogous effort to iFABalbeit at asmaller scaleto deploy elements of a distributed computer-numerically-controlled(CNC) manufacturing capability across a number of high schools throughout the U.S. andengage in collaborative design and manufacturing to help develop a future cadre ofinnovators in this area. And finally, FANG, as presently envisioned, will be a series ofprize-based design challenges leading to the development of a next-generation infantry

fighting vehicle for the U.S. Army.

Program Scope, Structure, and Technical Objectives

The principal objective of the vehicleforge.mil effort is to generate an open sourcedevelopment collaboration environment and website for the creation of large, complex,cyber-electro-mechanical systems by numerous unaffiliated designers. The initial phaseof the program will last 12 months and culminate in the operational deployment ofvehicleforge.mil. The following capabilities are desired:

1. Hosting of large, complex, cyber-electro-mechanical system representation

models in one or more metalanguages which are being developed by META andMETA-II performers. For proposal development purposes, offerors should planand demonstrate compatibility with at least SysML (Systems ModelingLanguage) and AADL (Architecture Analysis & Design Language).

2. Hosting of multiple projects, including: public projects for which access is notlimited; semi-public projects for which access is based on verification of U.S.person status for export control purposes; and private projects for which access islimited to a fixed set of individuals or entities.

3. A version control system, enabling check-out and check-in, reversion, bug/issue

tracking, and other features that enable effective collaborative development andproject maintenance.

4. Public and private version branching.

8 https://www.fbo.gov/spg/ODA/DARPA/CMO/DARPA-BAA-10-88/listing.html


6/32

6

5. Collection of metrics and statistics on access patterns, user activity, and design(re)use.

6. Collaboration tools including a wiki, message board, mailing lists, and otherfeatures that enable effective collaborative development.

7. User registration and U.S. person status verification for export controlcompliance.

8. Information assurance controls sufficient to protect export controlled andcontractor proprietary information in accordance with Department of Defense,Department of State, Department of Commerce, and any other statutory orregulatory requirements or best practices.

9. Support for information assurance testing, certification, and accreditationactivities.

10.Public hosting and dissemination of electronic materials and announcementsassociated with a series of Adaptive Make Challenges.

11.Documentation appropriate in scope and quality to enable effective developmentand maintenance of the vehicleforge.mil code base by third parties unaffiliatedwith the proposer.

12.Domain name registration, hosting, and upkeep. DARPA will supply thenecessary government approval for compliance with DoD Instruction 8410.01.

13.All servers, Internet connectivity, software, and services needed to develop,deploy, and operate the above-enumerated capabilities.

Proposers may choose to develop the necessary capability from a fresh code base, ordevelop the capability as a derivative of an existing product. In the latter case, proposersshould be especially mindful of the intellectual property restrictions that may be imposedby the licenses associated with the existing code base.

Proposers should also offer a series of three sequential priced options to support andoperate vehicleforge.mil for increments of one year in duration (i.e., for a total of threeyears). The following support and operations activities are desired:

1. Maintenance of the vehicleforge.mil code base, to include bug fixes, addition andmodification of minor features, and other routine code maintenance.

2. On-demand technical support to users. The proposed level, means, medium, andcapacity of technical support should be described.


7/32

7

3. User registration, including U.S. person status verification for access to export-controlled projects and information.

4. Collection of metrics and statistics on access patterns, user activity, and design(re)use.

5. Support for information assurance testing, certification, and accreditationactivities.

6. Domain name hosting and upkeep. DARPA will supply the necessary governmentapproval for compliance with DoD Instruction 8410.01.

7. All servers, Internet connectivity, software, and services needed to develop,deploy, and operate the above-enumerated capabilities. The proposer should planfor steady traffic loads consistent with several thousand concurrent users.Assumptions about traffic loads should be explicitly laid out in the proposal.

8. Public hosting and dissemination of electronic materials and announcementsassociated with a series of Adaptive Make Challenges. For planning purposes, theproposer should assume that a 200 Mb dataset will need to be hosted for publicdownloading associated with each challenge. Burst traffic loads of up to 100,000downloads over 24 hours should be accommodated over brief periods.

Potential offerors are advised that awardees under this BAA may be precluded fromparticipating as competitors or team members in the planned Adaptive Make Challengesstaged under the FANG program. As presently planned, these Adaptive Make Challenges

will include a series of prize-based design challenges supporting the design of a next-generation infantry fighting vehicle for the U.S. Army.

Deliverables

Offerors should propose an appropriate schedule of reviewable milestones, along withappropriate criteria by which progress can be assessed, to occur on a monthly basis. Inaddition to milestone-specific criteria, general technical and financial progress will beassessed at these reviews. Some subset of these reviews (approximately on a quarterlybasis) will be held in the form of joint principal investigator (PI) meetings with otherperformers and performers from other programs (e.g., META, META-II, iFAB, andFANG). Domestic travel will be required for these PI meetings.

DARPA desires to receive complete, fully functional algorithms, source code,documentation, binaries, and test use cases implementing the capability described above.The final version of these deliverables must be supplied to the Government no later thanthe end of the base period of performance and any time modifications are made during


8/32

8

the option periods. The delivery of interim versions as milestone deliverables is stronglyencouraged.

DARPA desires Unlimited Rights to all deliverables (except commercially or freelyavailable software, e.g., compilers, web servers, etc.) to enable their industry-wide

promulgation in the course of this program. Intellectual property rights are a proposalevaluation criterion and proposers should structure their development accordingly,especially where proprietary technical data or computer software is offered.

Offerors should propose, as part of their work plan, affirmative steps for the open sourcepromulgation of all source code, executables, documentation, and test use cases foroperating vehicleforge.mil. The specific open source license will be specified by DARPAin course of the period of performance.

No later than the end of each period of performance, the performer shall deliver a finalreport in the form of: (1) a technical manuscript of publishable quality and suitable for

publication in a journal or conference proceedings documenting their technical progressand results achieved in significant detail, and (2) a programmatic final report containingfinancial data and other information not suitable for publication but appropriate forprogram documentation and planning.

DARPA anticipates funding this effort with RDT&E Budget Activity 2 (6.2), AppliedResearch funds enabling academic institutions performing work on campus to participatewithout pre-publication review restrictions.

II. AWARD INFORMATIONMultiple awards are anticipated. The amount of resources made available under this BAAwill depend on the quality of the proposals received and the availability of funds.DARPA tentatively anticipates making up to $9.85 million available for multiple awardsfor the base effort, and up to $1 million available for a single option award each year forthree years. A total of $12.85 million is available under this BAA.

The Government reserves the right to select for negotiation all, some, one, or none of theproposals received in response to this solicitation, and to make awards withoutdiscussions with proposers. The Government also reserves the right to conductdiscussions if it is later determined to be necessary. If warranted, portions of resultingawards may be segregated into pre-priced options. Additionally, DARPA reserves theright to accept proposals in their entirety or to select only portions of proposals for award.In the event that DARPA desires to award only portions of a proposal, negotiations maybe opened with that proposer. The Government reserves the right to fund proposals inphases with options for continued work at the end of one or more of the phases.

Awards under this BAA will be made to proposers on the basis of the evaluation criterialisted below (see section labeled Application Review Information, Sec. V.), and


9/32

9

program balance to provide overall value to the Government. Proposals identified fornegotiation may result in a procurement contract, grant, cooperative agreement, or othertransaction depending upon the nature of the work proposed, the required degree ofinteraction between parties, and other factors. The Government reserves the right torequest any additional, necessary documentation once it makes the award instrument

determination. Such additional information may include but is not limited toRepresentations and Certifications. The Government reserves the right to removeproposers from award consideration should the parties fail to reach agreement on awardterms, conditions and cost/price within a reasonable time or the proposer fails to timelyprovide requested additional information.

As of the date of publication of this BAA, DARPA expects that program goals for thisBAA may be met by proposers intending to perform 'fundamental research,' i.e., basicand applied research in science and engineering, the results of which ordinarily arepublished and shared broadly within the scientific community, as distinguished fromproprietary research and from industrial development, design, production, and product

utilization the results of which ordinarily are restricted for proprietary or national securityreasons. Notwithstanding this statement of expectation, DARPA is not prohibited fromconsidering and selecting research proposals that, while perhaps not qualifying as'fundamental research' under the foregoing definition, still meet the BAA criteria forsubmissions. In all cases, the contracting officer shall have sole discretion to select awardinstrument type and to negotiate all instrument provisions with selectees.

Note that awardees under this BAA will be precluded from participating as competitorsor team members in subsequent Adaptive Make Challenges staged under the FANGprogram. As presently envisioned, these Adaptive Make Challenges will consist of aseries of prize-based design challenges culminating in the design of a next-generation

infantry fighting vehicle for the U.S. Army.

III. ELIGIBILITY INFORMATIONA. Eligible Applicants

All responsible sources capable of satisfying the Government's needs may submit aproposal that shall be considered by DARPA. Historically Black Colleges andUniversities (HBCUs), Small Businesses, Small Disadvantaged Businesses and MinorityInstitutions (MIs) are encouraged to submit proposals and join others in submittingproposals; however, no portion of this announcement will be set aside for theseorganizations participation due to the impracticality of reserving discrete or severableareas of this research for exclusive competition among these entities.

Federally Funded Research and Development Centers (FFRDCs) and Governmententities (Government/National laboratories, military educational institutions, etc.) aresubject to applicable direct competition limitations and cannot propose to this BAA inany capacity unless they address the following conditions. FFRDCs must clearly


10/32

10

demonstrate that the proposed work is not otherwise available from the private sectorAND must also provide a letter on letterhead from their sponsoring organization citingthe specific authority establishing their eligibility to propose to government solicitationsand compete with industry, and compliance with the associated FFRDC sponsoragreement and terms and conditions. This information is required for FFRDCs proposing

to be prime or subcontractors. Government entities must clearly demonstrate that thework is not otherwise available from the private sector and provide writtendocumentation citing the specific statutory authority (as well as, where relevant,contractual authority) establishing their ability to propose to Government solicitations. Atthe present time, DARPA does not consider 15 U.S.C. 3710a to be sufficient legalauthority to show eligibility. While 10 U.S.C. 2539b may be the appropriate statutorystarting point for some entities, specific supporting regulatory guidance, together withevidence of agency approval, will still be required to fully establish eligibility. DARPAwill consider eligibility submissions on a case-by-case basis; however, the burden toprove eligibility for all team members rests solely with the Proposer.

1. Procurement Integrity, Standards of Conduct, Ethical Considerations, andOrganizational Conflicts of Interest

Current federal employees are prohibited from participating in particular mattersinvolving conflicting financial, employment, and representational interests (18 USC 203,205, and 208.). The DARPA Program Manager for this BAA is Paul Eremenko. Once theproposals have been received, and prior to the start of proposal evaluations, theGovernment will assess potential conflicts of interest and will promptly notify theproposer if any appear to exist. (Please note the Government assessment does NOTaffect, offset, or mitigate the proposers own duty to give full notice and plannedmitigation for all potential organizational conflicts, as discussed below.)

All Proposers and proposed subcontractors must affirm whether they are providingscientific, engineering, and technical assistance (SETA) or similar support to anyDARPA technical office(s) through an active contract or subcontract. All affirmationsmust state which office(s) the Proposer supports and identify the prime contract numbers.Affirmations shall be furnished at the time of proposal submission. All facts relevant tothe existence or potential existence of organizational conflicts of interest (FAR 9.5) mustbe disclosed. The disclosure shall include a description of the action the Proposer hastaken or proposes to take to avoid, neutralize, or mitigate such conflict. In accordancewith FAR 9.503 and without prior approval or a waiver from the DARPA Director, aContractor cannot simultaneously be a SETA and Performer. Proposals that fail to fullydisclose potential conflicts of interests and/or do not have plans to mitigate this conflictwill be rejected without technical evaluation and withdrawn from further considerationfor award.

If a prospective Proposer believes that any conflict of interest exists or may exist(whether organizational or otherwise), the Proposer should promptly raise the issue withDARPA by sending Proposer's contact information and a summary of the potentialconflict by email to the mailbox address for this BAA at DARPA-BAA-10-


11/32

11

[email protected], before time and effort are expended in preparing a proposal andmitigation plan. If, in the sole opinion of the Government after full consideration of thecircumstances, any conflict situation cannot be effectively mitigated, the proposal may berejected without technical evaluation and withdrawn from further consideration for awardunder this BAA.

B. Cost Sharing/MatchingCost sharing is not required for this particular program; however, cost sharing will becarefully considered where there is an applicable statutory condition relating to theselected funding instrument (e.g., for any Other Transactions under the authority of 10U.S.C. 2371). Cost sharing is encouraged where there is a reasonable probability of apotential commercial application related to the proposed research and development effort.

C. Other Eligibility Criteria1.

Collaborative Efforts

Collaborative efforts/teaming are encouraged.

IV. APPLICATION AND SUBMISSION INFORMATIONA. Address to Request Application Package

This solicitation contains all information required to submit a proposal. No additionalforms, kits, or other materials are needed. This notice constitutes the total BAA. No

additional information is available, nor will a formal Request for Proposal (RFP) oradditional solicitation regarding this announcement be issued. Requests for same will bedisregarded.

B. Content and Form of Application Submission1. Security and Proprietary Issues

NOTE: If proposals are classified, the proposals must indicate the classification level

of not only the proposal itself, but also the anticipated award document

classification level.

The Government anticipates proposals submitted under this BAA will be unclassified.However, if a proposal is submitted as Classified National Security Information asdefined by Executive Order 13526 as amended, then the information must be marked andprotected as though classified at the appropriate classification level and then submitted toDARPA for a final classification determination.


12/32

12

Proposers choosing to submit a classified proposal from other classified sources mustfirst receive permission from the respective Original Classification Authority in order touse their information in replying to this BAA. Applicable classification guide(s) shouldalso be submitted to ensure the proposal is protected at the appropriate classificationlevel.

Classified submissions shall be appropriately and conspicuously marked with theproposed classification level and declassification date. Submissions requiring DARPA tomake a final classification determination shall be marked as follows:

CLASSIFICATION DETERMINATION PENDING. Protect as though classified(insert the recommended classification level: (e.g., Top Secret, Secret or Confidential)

Classified submissions shall be in accordance with the following guidance:

Confidential and Secret Collateral Information: Use classification and marking

guidance provided by previously issued security classification guides, the InformationSecurity Regulation (DoD 5200.1-R), and the National Industrial Security ProgramOperating Manual (DoD 5220.22-M) when marking and transmitting informationpreviously classified by another Original Classification Authority. Classifiedinformation at the Confidential and Secret level may be mailed via appropriate U.S.Postal Service methods (e.g., (USPS) Registered Mail or USPS Express Mail). Allclassified information will be enclosed in opaque inner and outer covers and doublewrapped. The inner envelope shall be sealed and plainly marked with the assignedclassification and addresses of both sender and addressee. The inner envelope shall beaddress to:

Defense Advanced Research Projects AgencyAttn: TTOReference: BAA 10-863701 North Fairfax DriveArlington, VA 22203-1714

The outer envelope shall be sealed with no identification as to the classification of itscontents and addressed to:

Defense Advanced Research Projects AgencySecurity & Intelligence Directorate, Attn: CDR3701 North Fairfax DriveArlington, VA 22203-1714

All Top Secret materials: Top Secret information should be hand carried by anappropriately cleared and authorized courier to the DARPA CDR. Prior to traveling,the courier shall contact the DARPA CDR at 571 218-4842 to coordinate arrival anddelivery.


13/32

13

Special Access Program (SAP) Information: SAP information must be transmittedvia approved methods. Prior to transmitting SAP information, contact the DARPASAPCO at 703-526-4052 for instructions.

Sensitive Compartmented Information (SCI): SCI must be transmitted via approvedmethods. Prior to transmitting SCI, contact the DARPA Special Security Office (SSO)at 703-248-7213 for instructions.

Proprietary Data: All proposals containing proprietary data should have the coverpage and each page containing proprietary data clearly marked as containingproprietary data. It is the Proposers responsibility to clearly define to the Governmentwhat is considered proprietary data.

Security classification guidance via a DD Form 254, DoD Contract SecurityClassification Specification, will not be provided at this time since DARPA is soliciting

ideas only. After reviewing the incoming proposals, if a determination is made that theaward instrument may result in access to classified information a DD Form 254 will beissued and attached as part of the award.

Proposers must have existing and in-place prior to execution of an award, approvedcapabilities (personnel and facilities) to perform research and development at theclassification level they propose. It is the policy of DARPA to treat all proposals ascompetitive information, and to disclose their contents only for the purpose ofevaluation. Proposals will not be returned. The original of each proposal received willbe retained at DARPA and all other non-required copies destroyed. A certification ofdestruction may be requested, provided the formal request is received at this office

within 5 days after unsuccessful notification.

2. Proposal InformationProposers are required to submit full proposals by the time and date specified in the BAAin order to be considered during the initial round of selections. DARPA may evaluateproposals received after this date for a period up to one year from date of posting onFedBizOpps. Ability to review late submissions remains contingent on availability offunds.

The typical proposal should express a consolidated effort in support of one or morerelated technical concepts or ideas. Disjointed efforts should not be included into a singleproposal.

Restrictive notices notwithstanding, proposals may be handled, for administrativepurposes only, by a support contractor. This support contractor is prohibited fromcompetition in DARPA technical research and is bound by appropriate nondisclosurerequirements. Proposals may not be submitted by fax or e-mail; any so sent will bedisregarded.


14/32

14

Proposals not meeting the format described in the BAA may not be reviewed.

Proposers must submit an original and five (5) hard copies of the full proposal and two(2) electronic copies of the full proposal as a single Adobe PDF or Microsoft Word file

on a CD-ROM. Each copy must be clearly labeled with BAA 10-86, name of proposerorganization, proposal title (short title recommended), and Copy x of 6.

All administrative correspondence and questions on this solicitation, including requestsfor information on how to submit proposal to this BAA, should be directed to one of theadministrative addresses below; e-mail is preferred.

DARPA/TTOAttn: BAA-10-863701 North Fairfax DriveArlington, VA 22203-1714

Email: [email protected]

DARPA intends to use electronic mail for correspondence regarding BAA 10-86.Proposals may not be submitted by fax or e-mail; any so sent will be disregarded.DARPA encourages use of the Internet for retrieving the BAA and any other relatedinformation that may subsequently be provided.

3. Full Proposal Format

All full proposals must be in the format given below. Proposals not meeting the formatdescribed in this BAA may be rejected without review. The proposal shall be delivered in

a single volume including both technical and cost information.

The proposal shall include the following sections, each starting on a new page (where a"page" is 8-1/2 by 11 inches with type not smaller than 12 point, charts may use 10 pointfont, margins not smaller than 1 inch, and line spacing not smaller than single-spaced).Fold-outs up to 11 by 17 inches may be used but will be counted as two pages. Allsubmissions must be in English. Individual elements of the proposal shall not exceed thetotal of the maximum page lengths for each section as shown in braces { } below.

Proposals should cover the base period as well as option phases.

Ensure that each section provides detailed discussion of the proposed work necessary toenable an in-depth review of the specific technical and managerial issues. Explicitattention must be given to addressing both risk and payoff of the proposed work thatmake it desirable to DARPA.

Proposal Section 1. Administrative

1.1 Cover Sheet {no page limit}


15/32

15

BAA number;

Technical area(s);

Lead organization submitting proposal;

Type of business, selected among the following categories:

o WOMEN-OWNED LARGE BUSINESS,o OTHER LARGE BUSINESS,o SMALL DISADVANTAGED BUSINESS [identify ethnic group from

among the following: Asian-Indian American, Asian-Pacific American,Black American, Hispanic American, Native American, or Other],

o WOMEN-OWNED SMALL BUSINESS,o OTHER SMALL BUSINESS,o HBCU,o MI,o OTHER EDUCATIONAL,o OTHER NONPROFIT, OR

o FOREIGN CONCERN/ENTITY; All other team members (if applicable and including second- and lower-tier

subcontractors and independent consultants) and type of business for each;

Proposal title;

Technical point of contact to include: salutation, last name, first name, streetaddress, city, state, zip code, telephone, fax, and electronic mail;

Administrative point of contact to include: salutation, last name, first name, streetaddress, city, state, zip code, telephone, fax, and electronic mail;

Award instrument requested: cost-plus-fixed-free (CPFF), cost-contractno fee,cost sharing contract no fee, or other type of procurement contract (specify), orother transaction;

Place(s) and period(s) of performance; Summary of the costs of the proposed research, including total base cost,

estimates of base cost in each year of the effort, estimates of itemized options ineach year of the effort, and cost sharing if relevant;

Name, address, and telephone number of the offerors cognizant Defense ContractManagement Agency (DCMA) administration office (if known);

Name, address, and telephone number of the offerors cognizant Defense ContractAudit Agency (DCAA) audit office (if known);

Date proposal was prepared;

DUNS number;

TIN number;

Cage Code;

Proposal validity period (minimum 180 days).

1.2 Table of Contents {no page limit}

1.3 Organizational Conflict of Interest Affirmations and Disclosure {no page limit}


16/32

16

Per the instructions in Section III.A.1 above, if the offeror or any proposed sub ISproviding SETA support, as described, to any DARPA technical office(s) through anactive contract or subcontract (regardless of which DARPA technical office is beingsupported), they must provide documentation: 1) stating which office(s) the offeror, suband/or individual supports, 2) identify the prime contract numbers AND 3) include a

description of the action the offeror has taken or proposes to take to avoid, neutralize, ormitigate the conflict.

If the offeror or any proposed sub IS NOT currently providing SETA support asdescribed, then the offeror should simply state NONE.

Proposals that fail to fully disclose potential conflicts of interests or do not haveacceptable plans to mitigate identified conflicts will be rejected without technical

evaluation and withdrawn from further consideration for award.

1.4 Human Use {no page limit}For all proposed research that will involve human subjects in the first year or phase of theproject, the institution must provide evidence of or a plan for review by an InstitutionalReview Board (IRB) upon final proposal submission to DARPA. For further informationon this subject, see Section VI.B.4 below. If human use is not a factor in a proposal, thenthe offeror should state NONE.

1.5 Animal Use {no page limit}For submissions containing animal use, proposals must briefly describe plans forInstitutional Animal Care and Use Committee (IACUC) review and approval. For furtherinformation on this subject, see Section VI.B.5 below. If animal use is not a factor in aproposal, then the offeror should state None.

1.6 Statement of Unique Capability Provided by Government or Government-

Funded Team Member {no page limit}Per section III.A. Eligible Applicants, proposals which include Government orGovernment-funded entities (i.e., FFRDCs, National laboratories, etc.) as prime, sub orteam member, shall provide a statement which clearly demonstrates the work beingprovided by the Government or Government-funded entity team member is not otherwiseavailable from the private sector. If none of the team members belongs to a Governmentor Government-funded entity, then the offeror should state Not Applicable.

1.7 Government or Government-funded Team Member Eligibility {no page limit}Per section III.A. Eligible Applicants, proposals which include Government orGovernment-funded entities (i.e., FFRDCs, National laboratories, etc.) as prime, sub orteam member shall provide documentation citing the specific authority which establishesthey are eligible to propose to Government solicitations: 1) statutory authority; 2)contractual authority; 3) supporting regulatory guidance; AND 4) evidence of agencyapproval. If no such entities are involved, then the offeror should state None.

Proposal Section 2. Technical Details


17/32

17

2.1 PowerPoint Summary Chart {1 page}:Provide a one slide summary of the proposal in PowerPoint that effectively andsuccinctly conveys the main objective, key innovations, expected impact, proposer team,and other unique aspects of the proposal.

2.2 Innovative Claims for the Proposed Research {4 pages}:This page is the centerpiece of the proposal and should succinctly describe the uniqueproposed approach and contributions. This section may also briefly address the followingtopics:

a. Problem Description. Provide a concise description of the problem areasaddressed. Make this specific to your approach.

b. Research Goals. Identify specific research goals. Goals should address thetechnical challenges of the effort.

c. Expected Impact. Describe and justify the expected impact of your research.

2.3 Technical Approach {15 pages}:

Provide a detailed description of the technical approach. This section will serve as theprimary expression of the offerors scientific and technical ideas. It should also includethe offerors understanding of the state of the art approaches and the limitations thatrelate to each topic addressed by the proposal. Describe and analyze state of the artresults, approaches, and limitations within the context of the problem area addressed bythis research. Demonstrating problem understanding requires not just the enumeration ofrelated efforts; rather, related work must be compared and contrasted to the proposedapproach.2.4 Intellectual Property {No page limit}Per section VI.B.2 below, offerors responding to this BAA must submit a separate list ofall technical data or computer software that will be furnished to the Government withother than unlimited rights. The Government will assume unlimited rights if offerors failto identify any intellectual property restrictions in their proposals. Include in this sectionall proprietary claims to results, prototypes, deliverables or systems supporting and/ornecessary for the use of the research, results, prototypes and/or deliverables. If norestrictions are intended, then the offeror should state NONE.

2.5 Management Plan {5 Pages}:Describe formal teaming agreements that are required to execute this program, a briefsynopsis of all key personnel, and a clearly defined organization chart for the programteam (prime contractor and subcontractors, if any). Provide an argument that the teamsize and composition are both necessary and sufficient to meet the program objectives.Provide detailed task descriptions, costs, and interdependencies for each individual effortand/or subcontractor. To the extent that graduate and postdoctoral students are involvedin individual efforts, describe their role and contribution. This section must cover thefollowing:

a. Programmatic relationship of team members;b. Unique capabilities of team members;c. Task responsibilities of team members;d. Teaming strategy among the team members;


18/32

18

e. Key personnel along with the amount of effort to be expended by eachperson during each year; and

f. Government role in project, if any.

2.6 Personnel, Qualifications, and Commitments {5 pages}:

List key personnel, showing a concise summary of their qualifications. Provide adescription of any previous accomplishments or similar efforts completed/ongoing in thisor closely related research area, including identification of other Government sponsors, ifany.

Indicate the level of effort in terms of hours to be expended by each person during eachcontract year and other (current and proposed) major sources of support for them and/orcommitments of their efforts. DARPA expects all key personnel associated with aproposal to make substantial time commitment to the proposed activity and the proposalwill be evaluated accordingly. It is DARPAs intention to put key personnel clauses intothe contracts, so offerors should not bid personnel whom they do not intend to employ on

the contract.

Include a table of key individual time commitments as follows:

Key Individual Project Pending/Current 2010 ... 2014

Jane Doe Program Name Proposed X hours Y hours Z hours

Project 1 Current n/a n/a n/a

Project 2 Pending 100 hours n/a n/a

John Deer Program Name Proposed

2.7 Schedule and Milestones {6 pages}:

This section should include:a. {2 pages} Schedule Graphic. Provide a graphic representation of project schedule

including detail down to the individual effort level. This should include but not belimited to a coherent development plan, which demonstrates a clear understandingof the proposed research; and a plan for periodic and increasingly robust testsover the project life that will show applicability to the overall program concept.Show all project milestones. Use x months after contract award designations forall dates.

b. {2 pages} Detailed Task Descriptions. Provide detailed task descriptions for eachdiscrete work effort and/or subcontractor in schedule graphic.

c. {2 pages} Cost Summary. Provide a top level total cost summary for the entire

program. Show each major task and subtask by month and delineate prime andmajor subcontractor efforts.

2.8 Statement of Work (SOW) {no page limit}:In plain English, clearly define the technical tasks/subtasks to be performed, theirdurations, and dependencies among them. For each task/subtask, provide:

A general description of the objective (for each defined task/activity);


19/32

19

A detailed description of the approach to be taken to accomplish each definedtask/activity);

Identification of the primary organization responsible for task execution(prime, sub, team member, by name, etc.);

The completion criteria for each task/activitya product, event or milestone

that defines its completion; Define all deliverables (reports, data, software, hardware, prototypes, etc.) to

be provided to the Government in support of the proposed researchtasks/activities. Include expected delivery date for each deliverable.

Do not include any proprietary information in the SOW or include any markings

placing limitations on distribution on the pages containing the SOW.

Proposal Section 3. Cost

3.1 Detailed Cost Breakdown {no page limit}

Provide: (1) total program cost broken down by major cost items (direct labor, includinglabor categories; subcontracts; materials; other direct costs, overhead charges, etc.) andfurther broken down by task and phase; (2) major program tasks by fiscal year; (3) anitemization of major subcontracts and equipment purchases; (4) an itemization of anyinformation technology (IT) purchase9; (5) a summary of projected funding requirementsby month; and (6) the source, nature, and amount of any industry cost-sharing; (7)identification of pricing assumptions of which may require incorporation into theresulting award instrument (e.g., use of Government FurnishedProperty/Facilities/Information, access to Government Subject Matter Expert/s, etc.) and8) provide appropriate cost or price analyses of subcontractor proposals, IAW FAR15.404-3, to establish the reasonableness of proposed subcontract prices.

The prime contractor is responsible for compiling and providing all subcontractorproposals for the Procuring Contracting Officer (PCO). Subcontractor proposals shouldinclude Interdivisional Work Transfer Agreements (ITWA) or similar arrangements.Where the effort consists of multiple portions which could reasonably be partitioned for

9 IT is defined as any equipment, or interconnected system(s) or subsystem(s) of equipment that is used inthe automatic acquisition, storage, manipulation, management, movement, control, display, switching,interchange, transmission, or reception of data or information by the agency. (a) For purposes of thisdefinition, equipment is used by an agency if the equipment is used by the agency directly or is used by acontractor under a contract with the agency which (1) Requires the use of such equipment; or (2)Requires the use, to a significant extent, or such equipment in the performance of a service or the

furnishing of a product. (b) The term information technology includes computers, ancillary, software,firmware and similar procedures, services (including support services), and related resources. (c) The terminformation technology does not include (1) Any equipment that is acquired by a contractor incidentalto a contract; or (2) Any equipment that contains imbedded information technology that is used as anintegral part of the product, but the principal function of which is not the acquisition, storage, manipulation,management, movement, control, display, switching, interchange, transmission, or reception of data orinformation. For example, HVAC (heating, ventilation, and air conditioning) equipment such asthermostats or temperature control devices, and medical equipment where information technology isintegral to its operation, is not information technology.


20/32

20

purposes of funding, these should be identified as options with separate cost estimates foreach. NOTE: for IT and equipment purchases, include a letter stating why the offerorcannot provide the requested resources from its own funding.

Any negotiations and/or awards will use procedures under FAR 15.4, Contract Pricing, as

specified in the BAA. Provide supporting cost and pricing information in sufficient detailto substantiate the summary cost estimates above. Include a description of the methodused to estimate costs and supporting documentation. Note: cost or pricing data asdefined in FAR Subpart 15.4 shall be required if the offeror is seeking a procurementcontract award of $650,000 or greater unless the offeror requests an exception from therequirement to submit cost or pricing data. Cost or pricing data are not required if theofferor proposes an award instrument other than a procurement contract (e.g., a grant,cooperative agreement, or other transaction). All proprietary subcontractor proposaldocumentation, prepared at the same level of detail as that required of the prime, shall bemade immediately available to the Government, upon request, under separate cover (i.e.,mail, electronic/email, etc.), either by the offeror or by the subcontractor organization.

For prototype system development proposals, the Government may award either aFederal Acquisition Regulation (FAR) based contract or an Other Transaction Authorityfor Prototypes (OTA) agreement. Offerors interested in receiving an OTA are asked tosubmit proposal responses that accommodate both options. For information on 845 OtherTransaction Authority for Prototypes (OTA) agreements, refer tohttp://www.darpa.mil/cmo/other_trans.html. The Government will evaluate all OfferorsFAR based proposals in accordance with the established evaluation criteria. After awardselection based on the FAR based proposals, the Government will evaluate the selectedawardees Other Transaction proposal with the intent of selecting the program approachoffering the most benefit to the Government. The intent of this evaluation approach is to

prevent contractors with greater financial flexibility from reducing the proposed cost tothe Government by providing a large cost share or extra effort beyond that of a contractorwith less financial capability. In this approach all proposals are evaluated based upontheir technical merits and ability to realistically price their proposed technical scope.

All proposers requesting an 845 Other Transaction Authority for Prototypes (OTA)agreement must include a detailed list of milestones. Each such milestone must includethe following: milestone description, completion criteria, due date, payment/fundingschedule (to include, if cost share is proposed, contractor and Government shareamounts). It is noted that, at a minimum, such milestones should relate directly toaccomplishment of program technical metrics as defined in the BAA and/or the offerorsproposal. Agreement type, fixed price or expenditure based, will be subject to negotiationby the Agreements Officer; however, it is noted that the Government prefers use of fixedprice milestones with a payment/funding schedule to the maximum extent possible. Donot include proprietary data. If the proposer requests award of an 845 OTA agreement asa nontraditional defense contractor, as so defined in the OSD guide entitled OtherTransactions (OT) Guide For Prototype Projects dated January 2001 (as amended)(http://www.acq.osd.mil/dpap/Docs/otguide.doc), information must be included in thecost proposal to support the claim. Additionally, if the offeror requests award of an 845
http://www.darpa.mil/cmo/other_trans.htmlhttp://www.darpa.mil/cmo/other_trans.htmlhttp://www.acq.osd.mil/dpap/Docs/otguide.dochttp://www.acq.osd.mil/dpap/Docs/otguide.dochttp://www.acq.osd.mil/dpap/Docs/otguide.dochttp://www.acq.osd.mil/dpap/Docs/otguide.dochttp://www.darpa.mil/cmo/other_trans.html


21/32

21

OTA agreement, without the required one-third (1/3) cost share, information must beincluded in the cost proposal supporting that there is at least one non-traditional defensecontractor participating to a significant extent in the proposed prototype project.

4. Submission Address, Date, and Time

The full proposal (original and designated number of hard and electronic copies) must besubmitted to:

DARPA/TTOAttn: BAA 10-863701 North Fairfax DriveArlington, VA 22203-1714

on or before 1:00pm, local time, [+60 days from posting], in order to be consideredduring the initial round of selections; however, proposals received after this deadline may

be received and evaluated up to one year from date of posting on FedBizOpps. Fullproposals submitted after the due date specified in the BAA may be selected contingentupon the availability of funds.

DARPA will post a consolidated Question and Answer response after [+15 days fromposting], before final full proposals are due. In order to receive a response to yourquestion, submit your question by [+10 days from posting] to [email protected].

DARPA will acknowledge receipt of complete submissions via e-mail and assign controlnumbers that should be used in all further correspondence regarding proposals.

Failure to comply with the submission procedures may result in the submission not beingevaluated.

5. Intergovernmental Review

Not applicable.

6. Funding Restrictions

Not applicable.

V. APPLICATION REVIEW INFORMATIONA. Evaluation Criteria

Evaluation of proposals will be accomplished through a scientific/technical review ofeach proposal using the following mandatory criteria: (a) Overall Scientific and


22/32

22

Technical Merit; (b) Potential Contribution and Relevance to the DARPA Mission; (c)Intellectual Property; and (d) Cost Realism. Proposals will not be evaluated against eachother since they are not submitted in accordance with a common work statement.DARPAs intent is to review proposals as soon as possible after they arrive; however,proposals may be reviewed periodically for administrative reasons.

The following are descriptions of the evaluation criteria:

(a) Overall Scientific and Technical MeritThe proposed technical approach is innovative, feasible, achievable, complete andsupported by a proposed technical team that has the expertise and experience toaccomplish the proposed tasks. The expertise and experience of the offerors proposedtechnical team will be evaluated based upon the qualifications of the key personnelproposed for the effort and their previous accomplishments on similar efforts.

(b) Potential Contribution and Relevance to the DARPA Mission

The potential contributions of the proposed effort with relevance to the nationaltechnology base will be evaluated. Specifically, DARPAs mission is to maintain thetechnological superiority of the U.S. military and prevent technological surprise fromharming our national security by sponsoring revolutionary, high-payoff research thatbridges the gap between fundamental discoveries and their application.

(c) Intellectual PropertyThe extent to which intellectual property (IP) rights limitations on the proposerstechnology and deliverables comport with DARPAs objectives or create a barrier totechnology transition will be evaluated.

(d) Cost RealismThe objective of this criterion is to establish that the proposed costs are realistic for thetechnical and management approach offered, as well as to determine the proposerspractical understanding of the effort. The proposal will be reviewed to determine if thecosts proposed are based on realistic assumptions, reflect a sufficient understanding ofthe technical goals and objectives of the BAA, and are consistent with the proposerstechnical approach (to include the proposed Statement of Work). At a minimum, this willinvolve review, at the prime and subcontract level, of the type and number of labor hoursproposed per task as well as the types and kinds of materials, equipment and fabricationcosts proposed. It is expected that the effort will leverage all available relevant priorresearch in order to obtain the maximum benefit from the available funding. For effortswith a likelihood of commercial application, appropriate direct cost sharing may be apositive factor in the evaluation. The evaluation criterion recognizes that undue emphasison cost may motivate proposers to offer low-risk ideas with minimum uncertainty and tostaff the effort with junior personnel in order to be in a more competitive posture.DARPA discourages such cost strategies.

B. Review and Selection Process


23/32

23

Award(s) will be made to proposers whose proposals are determined to be the mostadvantageous to the Government, all factors considered, including the potentialcontributions of the proposed work to the overall research program and the availabilityof funding for the effort. DARPAs intent is to review proposals as soon as possibleafter they arrive; however, proposals may be reviewed periodically for administrative

reasons.

It is the policy of DARPA to ensure impartial, equitable, comprehensive proposalevaluations and to select the source (or sources) whose offer meets the Government'stechnical, policy, and programmatic goals. Pursuant to FAR 35.016, the primary basis forselecting proposals for acceptance shall be technical, importance to agency programs, andfund availability. In order to provide the desired evaluation, qualified Governmentpersonnel will conduct reviews and (if necessary) convene panels of experts in theappropriate areas.

Proposals will not be evaluated against each other since they are not submitted in

accordance with a common work statement. For evaluation purposes, a proposal is thedocument described in Proposal Information, Section IV.B. Other supporting orbackground materials submitted with the proposal will be considered for the reviewer'sconvenience only and not considered as part of the proposal.

Restrictive notices notwithstanding, proposals may be handled for administrativepurposes by support contractors. These support contractors are prohibited fromcompetition in DARPA technical research and are bound by appropriate non-disclosurerequirements.

Subject to the restrictions set forth in FAR 37.203(d), input on technical aspects of the

proposals may be solicited by DARPA from non-Government consultants /experts whoare strictly bound by the appropriate non-disclosure requirements.

It is the policy of DARPA to treat all proposals as competitive information and todisclose their contents only for the purpose of evaluation. No proposals will be returned.After proposals have been evaluated and selections made, the original of each proposalreceived will be retained at DARPA and all other copies will be destroyed.

VI. AWARD ADMINISTRATION INFORMATIONA. Award Notices

As soon as the evaluation of a proposal is complete, the proposer will be notified that 1)the proposal has been selected for funding pending contract negotiations, or 2) theproposal has not been selected. These official notifications will be sent via United StatesPostal Service to the Technical POC identified on the proposal coversheet.

B. Administrative and National Policy Requirements


24/32

24

1. Meeting and Travel RequirementsThere will be a program kickoff meeting and all key participants are required to attend.Performers should also anticipate monthly reviews, PI meetings across several related

programs, and periodic site visits at the DARPA Program Managers discretion.

2. Human UseAll research involving human subjects, to include use of human biological specimens andhuman data, selected for funding must comply with the federal regulations for humansubject protection. Further, research involving human subjects that is conducted orsupported by the DoD must comply with 32 CFR 219, Protection of Human Subjectshttp://www.access.gpo.gov/nara/cfr/waisidx_07/32cfr219_07.html) and DoD Directive3216.02, Protection of Human Subjects and Adherence to Ethical Standards in DoD-Supported Research (http://www.dtic.mil/whs/directives/corres/pdf/321602p.pdf).

Institutions awarded funding for research involving human subjects must providedocumentation of a current Assurance of Compliance with Federal regulations for humansubject protection, for example a Department of Health and Human Services, Office ofHuman Research Protection Federal Wide Assurance (http://www.hhs.gov/ohrp). Allinstitutions engaged in human subject research, to include subcontractors, must also havea valid Assurance. In addition, personnel involved in human subjects research mustprovide documentation of completing appropriate training for the protection of humansubjects.

For all proposed research that will involve human subjects in the first year or phase of the

project, the institution must provide evidence of or a plan for review by an InstitutionalReview Board (IRB) upon final proposal submission to DARPA. The IRB conducting thereview must be the IRB identified on the institutions Assurance. The protocol, separatefrom the proposal, must include a detailed description of the research plan, studypopulation, risks and benefits of study participation, recruitment and consent process,data collection, and data analysis. Consult the designated IRB for guidance on writing theprotocol. The informed consent document must comply with federal regulations (32 CFR219.116). A valid Assurance along with evidence of appropriate training all investigatorsshould all accompany the protocol for review by the IRB.

In addition to a local IRB approval, a headquarters-level human subjects regulatoryreview and approval is required for all research conducted or supported by the DoD. TheArmy, Navy, or Air Force office responsible for managing the award can provideguidance and information about their components headquarters-level review process.Note that confirmation of a current Assurance and appropriate human subjects protectiontraining is required before headquarters-level approval can be issued.

The amount of time required to complete the IRB review/approval process may varydepending on the complexity of the research and/or the level of risk to study participants.


25/32

25

Ample time should be allotted to complete the approval process. The IRB approvalprocess can last between one to three months, followed by a DoD review that could lastbetween three to six months. No DoD/DARPA funding can be used towards humansubjects research until ALL approvals are granted.

3.

Animal Use

Any Recipient performing research, experimentation, or testing involving the use ofanimals shall comply with the rules on animal acquisition, transport, care, handling, anduse in: (i) 9 CFR parts 1-4, Department of Agriculture rules that implement theLaboratory Animal Welfare Act of 1966, as amended, (7 U.S.C. 2131-2159); (ii) theguidelines described in National Institutes of Health Publication No. 86-23, "Guide forthe Care and Use of Laboratory Animals"; (iii) DoD Directive 3216.01, Use ofLaboratory Animals in DoD Program.

For submissions containing animal use, proposals should briefly describe plans for

Institutional Animal Care and Use Committee (IACUC) review and approval. Animalstudies in the program will be expected to comply with the PHS Policy on Humane Careand Use of Laboratory Animals, available at http://grants.nih.gov/grants/olaw/olaw.htm.

All Recipients must receive approval by a DoD certified veterinarian, in addition to anIACUC approval. No animal studies may be conducted using DoD/DARPA funding untilthe USAMRMC Animal Care and Use Review Office (ACURO) or other appropriateDoD veterinary office(s) grant approval. As a part of this secondary review process, theRecipient will be required to complete and submit an ACURO Animal Use Appendix,which may be found athttps://mrmc-www.army.mil/index.cfm?pageid=Research_Protections.acuro&rn=1.

4. Publication ApprovalIt is the policy of the Department of Defense that the publication of products offundamental research will remain unrestricted to the maximum extent possible. Thedefinition of Contracted Fundamental Research is:

Contracted Fundamental Research includes [research performed under] grantsand contracts that are (a) funded by budget category 6.1 (Basic Research),whether performed by universities or industry or (b) funded by budget category6.2 (Applied Research) and performed on-campus at a university. The researchshall not be considered fundamental in those rare and exceptional circumstanceswhere the applied research effort presents a high likelihood of disclosingperformance characteristics of military systems or manufacturing technologiesthat are unique and critical to defense, and where agreement on restrictions havebeen recorded in the contract or grant. Such research is referred to by DARPAas Restricted Research.


26/32

26

Pursuant to DoD policy, research performed under grants and contracts that are (a)funded by budget category 6.2 (Applied Research) and NOT performed on-campus at auniversity or (b) funded by budget category 6.3 (Advanced Technology Development)does not meet the definition of fundamental research. Publication restrictions will beplaced on all such research.

It is anticipated that awards for both Fundamental and Non-Fundamental Research maybe made as a result of this BAA depending on the nature of the performer and place ofperformance. Appropriate clauses will be included in resultant awards for Non-Fundamental Research to prescribe publication requirements and other restrictions, asappropriate. DARPA does not anticipate applying publication restrictions of any kind toFundamental Research to each individual award that may result from this BAA.

Proposers are advised if they propose grants or cooperative agreements, DARPA mayelect to award other award instruments due to the need to apply publication or otherrestrictions. DARPA will make this election if it determines that the research resulting

from the proposed program will present a high likelihood of disclosing performancecharacteristics of military systems or manufacturing technologies that are unique andcritical to defense. Any award resulting from such a determination will include arequirement for DARPA permission before publishing any information or results on theprogram and will be considered Restricted Research.

For certain research projects, it may be possible that although the research beingperformed by the Prime Contractor is Restricted Research, a subcontractor may beconducting Contracted Fundamental Research. In those cases, it is the Prime Contractorsresponsibility to explain in their proposal why its subcontractors effort is ContractedFundamental Research.

The following same or similar provision will be incorporated into any resultant RestrictedResearch or Non-Fundamental Research procurement contract or other transaction:

There shall be no dissemination or publication, except within and between theContractor and any subcontractors, of information developed under this contractor contained in the reports to be furnished pursuant to this contract without priorwritten approval of DARPAs Public Release Center (DARPA/PRC). Alltechnical reports will be given proper review by appropriate authority todetermine which Distribution Statement is to be applied prior to the initialdistribution of these reports by the Contractor. With regard to subcontractorproposals for Contracted Fundamental Research, papers resulting fromunclassified contracted fundamental research are exempt from prepublicationcontrols and this review requirement, pursuant to DoD Instruction 5230.27 datedOctober 6, 1987.

When submitting material for written approval for open publication, theContractor/Awardee must submit a request for public release to the PRC andinclude the following information: 1) Document Information: document title,


27/32

27

document author, short plain-language description of technology discussed in thematerial (approx. 30 words), number of pages (or minutes of video) and documenttype (briefing, report, abstract, article, or paper); 2) Event Information: event type(conference, principle investigator meeting, article or paper), event date, desireddate for DARPA's approval; 3) DARPA Sponsor: DARPA Program Manager,

DARPA office, and contract number; and 4) Contractor/Awardee's Information:POC name, e-mail and phone. Allow four weeks for processing; due dates underfour weeks require a justification. Unusual electronic file formats may requireadditional processing time. Requests can be sent either via e-mail [email protected] or via 3701 North Fairfax Drive, Arlington VA 22203-1714,telephone (571) 218-4235. Refer to http://www.darpa.mil/prc for informationabout DARPA's public release process.

5. Export Control

The following clause will be included in all procurement contracts, and may be included

in Other Transactions as deemed appropriate:

(a)Definition. Export-controlled items, as used in this clause, means items subjectto the Export Administration Regulations (EAR) (15 CFR Parts 730-774) or theInternational Traffic in Arms Regulations (ITAR) (22 CFR Parts 120-130). Theterm includes:

1) Defense items, defined in the Arms Export Control Act, 22 U.S.C.2778(j)(4)(A), as defense articles, defense services, and related technical data,and further defined in the ITAR, 22 CFR Part 120.

2) Items, defined in the EAR as commodities, software, and technology,terms that are also defined in the EAR, 15 CFR 772.1.

(b) The Contractor shall comply with all applicable laws and regulations regardingexport-controlled items, including, but not limited to, the requirement for contractors toregister with the Department of State in accordance with the ITAR. The Contractor shallconsult with the Department of State regarding any questions relating to compliance withthe ITAR and shall consult with the Department of Commerce regarding any questionsrelating to compliance with the EAR.

(c) The Contractor's responsibility to comply with all applicable laws and regulationsregarding export-controlled items exists independent of, and is not established or limitedby, the information provided by this clause.

(d) Nothing in the terms of this contract adds, changes, supersedes, or waives any of therequirements of applicable Federal laws, Executive orders, and regulations, including butnot limited to

(1) The Export Administration Act of 1979, as amended (50 U.S.C. App.


28/32

28

2401, et seq.);

(2) The Arms Export Control Act (22 U.S.C. 2751, etseq.);

(3) The International Emergency Economic Powers Act (50 U.S.C. 1701, et seq.);

(4) The Export Administration Regulations (15 CFR Parts 730-774);

(5) The International Traffic in Arms Regulations (22 CFR Parts 120-130); and

(6) Executive Order 13222, as extended;

(e) The Contractor shall include the substance of this clause, including this paragraph (e),in all subcontracts.

6. Subcontracting

Pursuant to Section 8(d) of the Small Business Act (15 U.S.C. 637(d)), it is the policy ofthe Government to enable small business and small disadvantaged business concerns tobe considered fairly as subcontractors to contractors performing work or renderingservices as prime contractors or subcontractors under Government contracts, and toassure that prime contractors and subcontractors carry out this policy. Each proposer whosubmits a contract proposal and includes subcontractors is required to submit asubcontracting plan in accordance with FAR 19.702(a) (1) and (2) should do so with theirproposal. The plan format is outlined in FAR 19.704.

7. Electronic and Information Technology

All electronic and information technology acquired through this solicitation must satisfythe accessibility requirements of Section 508 of the Rehabilitation Act (29 U.S.C. 794d)and FAR Subpart 39.2. Each proposer who submits a proposal involving the creation orinclusion of electronic and information technology must ensure that Federal employeeswith disabilities will have access to and use of information that is comparable to theaccess and use by Federal employees who are not individuals with disabilities andmembers of the public with disabilities seeking information or services from DARPAwill have access to and use of information and data that is comparable to the access anduse of information and data by members of the public who are not individuals withdisabilities.

8. Employment Eligibility Verification

As per FAR 22.1802, recipients of FAR-based procurement contracts must enroll asFederal Contractors in E-verify and use E-Verify to verify employment eligibility of allemployees assigned to the award. All resultant contracts from this solicitation willinclude FAR 52.222-54, Employment Eligibility Verification. This clause will not beincluded in grants, cooperative agreements, or Other Transactions.


29/32

29

C. ReportingThe number and types of reports will be specified in the award document, but willinclude as a minimum monthly financial and technical status reports. The reports shall be

prepared and submitted in accordance with the procedures contained in the awarddocument and mutually agreed on before award. Reports and briefing material will alsobe required as appropriate to document progress in accomplishing program metrics. AFinal Report that summarizes the project and tasks will be required at the conclusion ofthe performance period for the award, notwithstanding the fact that the research may becontinued under a follow-on vehicle. At least one copy of each report will be delivered toDARPA and not merely placed on an internet site.

D. Electronic Systems

1. Central Contractor Registration (CCR)Selected proposers not already registered in the Central Contractor Registry (CCR) willbe required to register in CCR prior to any award under this BAA. Information on CCRregistration is available at http://www.ccr.gov.

2. Representations and CertificationsIn accordance with FAR 4.1201, prospective proposers shall complete electronic annualrepresentations and certifications at http://orca.bpn.gov.

3. Wide Area Work Flow (WAWF)Unless using another approved electronic invoicing system, performers will be requiredto submit invoices for payment directly via the Internet/WAWF at http://wawf.eb.mil.Registration to WAWF will be required prior to any award under this BAA.

4. i-EdisonAll required invention and patent reporting shall be accomplished, as applicable, usingthe i-Edison.gov reporting website at http://s-edison.info.nih.gov/iEdison.

VII. AGENCY CONTACTSThe preferred method of communication in regard to this BAA is e-mail. Administrative,technical, or contractual questions should be sent via e-mail [email protected]. If e-mail is not available, fax questions to (703) 248-1861, Attn: BAA 10-86. All requests must include the name, email address, and phonenumber of a point of contact.
http://www.ccr.gov/http://orca.bpn.gov/http://orca.bpn.gov/http://www.ccr.gov/


30/32

30

Postal correspondence should be addressed to:

DARPA/TTOAttn: BAA 10-863701 North Fairfax Drive

Arlington, VA 22203-1714

The websites for this solicitation where this BAA and related information may beretrieved are:

http://www.darpa.mil/tto/solicitations/index.htmlhttps://www.fbo.gov/spg/ODA/DARPA/CMO/DARPA-BAA-10-86/listing.html

VIII. OTHER INFORMATIONA.

. Intellectual Property

1. Procurement Contract Proposers

a. Noncommercial Items (Technical Data and ComputerSoftware)

Proposers responding to this BAA requesting a procurement contract to be issued underthe FAR/DFARS shall identify all noncommercial technical data and noncommercialcomputer software that it plans to generate, develop, and/or deliver under any proposedaward instrument in which the Government will acquire less than unlimited rights, and to

assert specific restrictions on those deliverables. Proposers shall follow the format underDFARS 252.227-7017 for this stated purpose. In the event that proposers do not submitthe list, the Government will assume that it automatically has unlimited rights to allnoncommercial technical data and noncommercial computer software generated,developed, and/or delivered under any award instrument, unless it is substantiated thatdevelopment of the noncommercial technical data and noncommercial computer softwareoccurred with mixed funding. If mixed funding is anticipated in the development ofnoncommercial technical data and noncommercial computer software generated,developed, and/or delivered under any award instrument, then proposers should identifythe data and software in question, as subject to Government Purpose Rights (GPR). Inaccordance with DFARS 252.227-7013 Rights in Technical Data - NoncommercialItems, and DFARS 252.227-7014 Rights in Noncommercial Computer Software andNoncommercial Computer Software Documentation, the Government will automaticallyassume that any such GPR restriction is limited to a period of five (5) years in accordancewith the applicable DFARS clauses, at which time the Government will acquireunlimited rights unless the parties agree otherwise. Proposers are admonished that theGovernment will use the list during the evaluation process to evaluate the impact of anyidentified restrictions and may request additional information from the proposer, as maybe necessary, to evaluate the proposers assertions. If no restrictions are intended, then


31/32

31

the proposer should state NONE. It is noted an assertion of NONE indicates that theGovernment has unlimited rights to all noncommercial technical data andnoncommercial computer software delivered under the award instrument, in accordancewith the DFARS provisions cited above. Failure to provide full information may result ina determination that the proposal is not compliant with the BAA resulting in

nonselectability of the proposal.

A sample list for complying with this request is as follows:

NONCOMMERCIAL

Technical Dataomputer Software Tobe Furnished With

Restrictions

Summary ofIntended Use in the

Conduct of theResearch

Basis for Assertion Asserted RightsCategory

Name of Person AssertinRestrictions

(LIST) (NARRATIVE) (LIST) (LIST) (LIST)

b. Commercial Items (Technical Data and ComputerSoftware)Proposers responding to this BAA requesting a procurement contract to be issued underthe FAR/DFARS shall identify all commercial technical data and commercial computersoftware that may be embedded in any noncommercial deliverables contemplated underthe research effort, along with any applicable restrictions on the Governments use ofsuch commercial technical data and/or commercial computer software. In the event thatproposers do not submit the list, the Government will assume that there are no restrictionson the Governments use of such commercial items. The Government may use the listduring the evaluation process to evaluate the impact of any identified restrictions and

may request additional information from the proposer, as may be necessary, to evaluatethe proposers assertions. If no restrictions are intended, then the proposer should stateNONE. Failure to provide full information may result in a determination that theproposal is not compliant with the BAA resulting in nonselectability of the proposal.

A sample list for complying with this request is as follows:

COMMERCIAL

Technical DataComputer Software To

be Furnished With

Restrictions

Basis for Assertion Asserted RightsCategory

Name of Person AssertingRestrictions

(LIST) (LIST) (LIST) (LIST)

B. Non-Procurement Contract Proposers Noncommercial andCommercial Items (Technical Data and Computer Software)

Proposers responding to this BAA requesting a Grant, Cooperative Agreement,Technology Investment Agreement, or Other Transaction for Prototype shall follow the


32/32

applicable rules and regulations governing these various award instruments, but in allcases should appropriately identify any potential restrictions on the Governments use ofany Intellectual Property contemplated under those award instruments in question. Thisincludes both Noncommercial Items and Commercial Items. Although not required,proposers may use a format similar to that described in Paragraphs 1.a and 1.b above. The

Government may use the list during the evaluation process to evaluate the impact of anyidentified restrictions, and may request additional information from the proposer, as maybe necessary, to evaluate the proposers assertions. If no restrictions are intended, thenthe proposer should state NONE. Failure to provide full information may result in adetermination that the proposal is not compliant with the BAA resulting innonselectability of the proposal.

C. All Proposers PatentsInclude documentation proving your ownership of or possession of appropriate licensing

rights to all patented inventions (or inventions for which a patent application has beenfiled) that will be utilized under your proposal for the DARPA program. If a patentapplication has been filed for an invention that your proposal utilizes, but the applicationhas not yet been made publicly available and contains proprietary information, you mayprovide only the patent number, inventor name(s), assignee names (if any), filing date,filing date of any related provisional application, and a summary of the patent title,together with either: 1) a representation that you own the invention, or 2) proof ofpossession of appropriate licensing rights in the invention.

1. All Proposers Intellectual Property RepresentationsProvide a good faith representation that you either own or possess appropriate licensingrights to all other intellectual property that will be utilized under your proposal for theDARPA program. Additionally, proposers shall provide a short summary for each itemasserted with less than unlimited rights that describes the nature of the restriction and theintended use of the intellectual property in the conduct of the proposed research

darpa baa 10 86 mil draft

Documents