ADEPT -- Basic ARA (Final).pdf

6 December 2019

Advanced Research Announcement (ARA) with Calls

Overview Information

NAICS Code: The NAICS Code for this acquisition is 541714 (Research and Technology in Biotechnology (except Nanobiotechnology), and the small business size standard is 1,000 employees.

Federal Agency Name: Air Force Research Laboratory (AFRL), 711th Human Performance Wing, Airman Systems Directorate, Airman Bioengineering Division

(711 HPW/RHB)

ARA Title: Advanced Development for Enhanced Performance Technologies

(ADEPT)

ARA Type: This is the Initial Announcement.

ARA Number: FA8650-20-S-6009

THIS IS AN ADVANCED RESEARCH ANNOUNCEMENT (ARA) THAT WILL

SOLICIT REQUIREMENTS THROUGH CALLS FOR PROPOSALS. THIS

ANNOUNCEMENT POSTS THE BASIC ARA AND DOES NOT REQUIRE

PROPOSALS AT THIS TIME. THE BASIC ARA WILL REMAIN OPEN FOR

CALLS UNTIL 14 DEC 2024.

Calls (One-Step, See Section IV for instructions): Over the period of this ARA, Calls may be issued to request proposals for specific area(s) of interest. All Call annoucements will be for proposals (one-step). Each call will contain specific requirements and pertinent information. Proposals submitted in response to the Calls will be accepted as specified in the individual Calls and evaluated in accordance with the Proposal Instructions for each Call (section IV.2 of the Call).

Offerors should monitor the Federal Business Opportunities website at beta.SAM.gov in the event this announcement is amended or Calls are issued.

Proposal Due Dates and Times:

For all Calls (ONE-STEP)

PROPOSAL DUE DATE AND TIME: To be provided in Calls.

NOTE: Proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). Any proposal received at the Government office designated in this ARA after the exact time specified for receipt of offers is "late" and will not be considered except at the Contracting Point of Contact’s discretion. It should be noted that this installation observes strict security procedures to enter the facility. These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the stated date and time in the Call as a result of security delays will be considered "late." Furthermore, note that if offerors utilize commercial carriers in the delivery of proposals, the carriers may not honor time-of-day delivery guarantees on military installations. Be advised, if the U.S. Postal Service is used, this building only receives U.S. Postal Mail twice a week and delivery by that means may not meet the proposal due date and time. Early proposal submission is encouraged.

Submission: Proposals must be submitted to the Contracting Point of Contact (POC): Mr. Joseph Mizzi, AFRL/RAKHA, 2130 8th Street, Building 45, Wright- Patterson AFB, OH 45433-7541, joseph.mizzi@us.af.mil; and/or Marina Schemmel, AFRL/RAKHA, Bldg 45, 2130 8th St., Wright-Patterson AFB, OH 45433-7541, marina.schemmel@us.af.mil. The hard copy submittal will determine whether the proposal is submitted timely.

Hand Delivery: If interested, vendors must go to Building 45 in Area B. Once in the lobby, call either Marina Schemmel at (937) 713-9845 or Joseph Mizzi at (937) 713-9925 to arrange for pickup. If you do not have a rep with base access, you will need to have the Government submit a visit request for you at least 3 days in advance. Please email Marina Schemmel or Joseph Mizzi to request a visitor pass for that day. Hand delivery is not required.

Solicitation Request: The Air Force Research Laboratory (AFRL), 711th Human Performance Wing, Airman Systems Directorate, Airman Bioengineering Division, Wright-Patterson Air Force Base is NOT soliciting proposals on the overarching effort described below at this time. Specific requests will be issued as Calls that are within the scope of this ARA. Each Call will contain specific requirements pertinent to that particular Call. Unless otherwise stated in a specific Call, all other requirements are listed within this ARA.

Type of Contract/Instrument: The Air Force reserves the right to award Contract(s) and/or Other Transaction(s) pursuant to 10 U.S.C. § 2373, based on the instrument deemed most appropriate. It is anticipated that contracts awarded under this ARA will generally be Cost Plus Fixed Fee (CPFF) or Firm Fixed Price (FFP). REMINDER: Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.

NOTE: If proposing a Federal Acquisition Regulation (FAR) based contract, the FAR clause references in this ARA shall apply. This announcement incorporates FAR and supplement provisions and clauses by reference.

The full text of these provisions and clauses can be found at https://www.acquisition.gov.

If proposing an Other Transaction (OT) pursuant to 10 U.S.C. 2373, these FAR references and clauses would not apply. The terms and conditions of mailto:joseph.mizzi@us.af.mil mailto:marina.schemmel@us.af.mil https://www.acquisition.gov/ an OT agreement should be developed and negotiated on a case-by-case basis.

Estimated Program Cost: The total estimated program value is $49,800,000.00, with multiple awards ranging from $50,000.00 to $20,000,000.00 (the Government reserves the right to exceed this amount if necessary).

Anticipated Number of Awards: The Air Force anticipates awarding multiple awards for this announcement. However, the Air Force reserves the right to award zero, one, or more contracts for all, some or none of the solicited effort based on the offeror’s ability to perform desired work and funding fluctuations. There is no limit on the number of OTs or contracts that may be awarded to an individual offeror.

Brief Program Summary: The purpose of this effort is to develop, mature, validate, and ultimately transition technologies fostered under the 711 HPW/RHB Research, Development, Test & Evaluation (RDT&E) "Sensing and Assessment" product line. Envisioned technologies will provide the capability to monitor, assess, sustain, and enhance the performance and safety of Airmen in a variety of challenging Air Force mission sets. The goal of this acquisition is to provide Airmen physiological and cognitive performance sustainment and enhancement systems, personalized to the individual Airman, and appropriate for use in operational USAF environments.

The proposed acquisition would acquire advanced system experimentation, development, engineering, and integration skills needed to develop prototype systems for operational demonstration/assessment and eventual transition to acquisition programs for production and deployment. Envisioned RDT&E activities would encompass technology readiness levels (TRL) 5 through 7 to provide documentation and engineering analysis for acquisition program initial system design reviews.

Note: For TRL definitions see 2011 DoD Technology Readiness Assessment (TRA) Guidance, https://www.acq.osd.mil/ecp/DOCS/DoDGuidance/TRA2011.pdf.

Multiple products will be developed and matured for technology transition under this acquisition. Central to the Sensing and Assessment product line is the development/maturation of component sensing (sensor) technologies integrated with a data collection and processing platform and associated analytics for physiological and cognitive state assessment. Additional analytics are also included to alert operators of their current state and provide potential remediation/intervention actions if baseline performance has fallen below minimum thresholds. Each product will be unique in its own development, but the following management/development approach would generally apply to all products:

• Evaluate sensing technologies (commercial or government "off the shelf" (COTS or GOTS)) for applicability and maturity by subjecting sensors to lab tests for specification conformance, reliability, user acceptance, and technical adequacy https://www.acq.osd.mil/ecp/DOCS/DoDGuidance/TRA2011.pdf

• Down-select component technologies

• Conduct analysis to determine appropriate computational processing requirements, data collection/storage platform(s), and networking/communication protocols

• Develop algorithms and eventual software code for the data collection, data analytics, operator alert, and intervention/remediation protocols

• Integrate the sensor, data processing, and software elements into a system prototype

• Conduct verification tests on the system prototype (lab and simulated end use environment)

• Validate prototype in an appropriate end user environment (i.e., operational assessment)

Communication Between Prospective Offerors and Government Representatives: Dialogue between prospective offerors and Government representatives is encouraged until submission of proposals. Discussions with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the Government. If there is any doubt as to whether a response provides a competitive advantage, the answer will be posted publicly via an amendment to this ARA on beta.SAM.gov for all contractors to review.

Address technical questions to the Technical POC: Dr. James Christensen, 2215 1st Street, Building 33, Wright-Patterson AFB, OH 45433-7022, 937-904- 9551, james.christensen.7@us.af.mil.

Address contracting questions to the Contracting POC: Mr. Joseph Mizzi, AFRL/RAKHA, 2130 8th Street, Building 45, Wright-Patterson AFB, OH 45433-7541, 937-713-9925, joseph.mizzi@us.af.mil and/or Marina Schemmel, AFRL/RAKHA, Bldg 45, 2130 8th St., Wright-Patterson AFB, OH 45433-7541, marina.schemmel@us.af.mil.

mailto:james.christensen.7@us.af.mil?subject=Re:%20%20ADEPT%20ARA mailto:joseph.mizzi@us.af.mil?subject=Re:%20%20ADEPT%20ARA mailto:marina.schemmel@us.af.mil

Full Text Announcement

I. Program Description: Air Force Research Laboratory, 711th Human Performance Wing, Airman Systems Directorate, Airman Bioengineering Division (AFRL/711 HPW/RHB) is announcing its intent to solicit proposals under this ARA with Calls. Solicitations for proposals will accomplished via Calls. The Calls will encompass the following effort:

1. Statement of Objective/Description of Technical Area(s): See

Attachment 2, ADEPT Statement of Objectives (SOO).

2. OPSEC: All contractors shall participate in all activities associated with the disciplines of the organization’s Industrial Security, Information Security, Personnel Security, Operations Security (OPSEC), Antiterrorism, and Program Protection programs, following appropriate measures in each program as required for this particular contract. These are required in an effort to reduce program vulnerability from successful adversary collection, exploitation of critical information, and violations of export control requirements. The prime contractor will ensure that all subcontractors, if required, conform to these requirements as required by the prime contractor. Guidance can be provided by 711 HPW/OMS Security as needed.

3. Within Scope Modifications: Potential offerors are advised that due to the inherent uncertainty of research and development efforts, awards resulting from this announcement may be modified during performance to make within scope changes, to include but not limited to, modifications which increase overall contract ceiling amount.

4. Deliverable Items:

a. Data Items: DD Form 1423-1 Contract Data Requirements List (CDRL) will be utilized on contract awards. Other Transactions will specify data items on a case-by-case basis. Data items will be identified in each call.

b. Software: Deliverables to be determined for each Call, if applicable.

c. Hardware: Deliverables to be determined for each Call, if applicable.

d. Other: To be determined for each Call.

5. Schedule:

a. Overall effort: Overall program will run for 87 months. Schedule for each Call is to be determined.

b. Data Items: To be determined for each Call.

c. Software: To be determined for each Call.

d. Hardware: To be determined for each Call.

6. Other Requirements:

a. This announcement incorporates FAR and supplement provisions and clauses by reference. The full text of provisions and clauses can be found at https://www.acquisition.gov/.

b. Program security classification: It is anticipated that the majority of the awards will be Secret classification/safeguarding capability, but security classification will be determined for each award. A draft DD254 will be attached to this ARA, and attached to individual calls against the ARA as required. If a DD254 is applicable, offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil.

c. TEMPEST requirements: Not applicable.

d. OPSEC: See attached Statement of Objectives (SOO) for each Call.

e. Export Control: Information involved in Calls for this research effort may be subject to Export Control (International Traffic in Arms Regulation (ITAR) 22 CFR 120-131), or Export Administration Regulations (EAR) (15 CFR 710-774). If a Call effort may be subject to export control, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal.

f. Export-Controlled Items: This acquisition is expected to generate or require access to export controlled items. As prescribed by DFARS 225.7901-4, DFARS 252.225-7048, Export-Controlled Item (Jun 2013) is contained in this solicitation. This clause shall be contained in ALL resulting contracts.

g. Contractor Performance Assessment Reporting System (CPARS) will likely be applicable, but will be determined on a Call by Call basis in accordance with FAR 42.1502 and DFARS 242.1502. Interim and final evaluations of contractor performance for contract awards will be prepared in accordance with AFFARS 5342.1503. The final performance evaluation will be prepared at the time of completion of work. In addition to the final evaluation, interim evaluation(s) will be prepared annually. Awardees will be requested to provide a POC to receive notifications of the opportunity to provide feedback. The Contractor will be permitted 14 days to review the document and to submit additional information or a rebutting statement. If agreement cannot be reached between the parties, the matter will be referred to an individual one level above the Contracting Officer, whose decision will be final. Copies of the assessments, Contractor responses, and review comments, if any, will be retained as part of the contract file, and may be used to support future award decisions for other procurements.

h. Flight Test: To be determined for each Call. The Contractor will be furnished aircraft for the Call, if applicable.

7. Other Information:

a. Government Furnished Property (GFP) availability: To be determined for each Call.

In accordance with FAR 45.201(b), the Contractor is responsible for all costs related to making the property available for use, such as payment of all transportation, installation or rehabilitation costs.

If GFP is is included in the Call or requested in a proposal, the following clauses/provisions apply:

i. FAR 52.245-1 Government Property or FAR 52.245-1, Alt II if the resulting contract is with a nonprofit organization or applied research at nonprofit organizations (Apr 2012);

ii. FAR 52.245-9 Use and Charges (Apr 2012);

iii. DFARS 252.211-7007, Reporting of Government Furnished Property (Aug 2012);

iv. DFARS 252.211-7007, Tagging, Labeling and Marking of Government Furnished Property (Apr 2012);

v. DFARS 252.245-7002, Reporting Loss of Government Property (Apr 2012);

vi. DFARS 252.245-7003, Contractor Property Management System Administration (Apr 2012);

vii. DFARS 252.245-7004, Reporting, Reutilization, and Disposal (May 2013).

b. Base Support / Network Access: None anticipated.

c. Multiple awards subject to Fair Opportunity are not anticipated.

d. Data Rights Desired: Will be determined for each call. Data Rights desired by the contractor should be included with proposal submission as part of the Section K. Given their importance in the Peer or Scientific Review criteria, Contractors MUST clearly mark any data and/or software rights assertions in their proposals.

The Air Force Research Laboratory is engaged in the discovery, development, and integration of warfighting technologies for our air, space, and cyberspace forces. As such, rights in technical data and non-commercial software (NCS) developed or delivered under this contract are of significant concern to the Government. The Government will therefore evaluate any restrictions on the use of technical data, NCS, and NCS documentation which could result in transition difficulty or less-than full and open competition for subsequent development of this technology.

In exchange for paying for development of the data, the Government expects technical data, NCS, and NCS documentation developed entirely at Government expense to be delivered with Unlimited Rights.

Technical data, NCS, and NCS documentation developed with mixed funding are expected to be delivered with at least Government Purpose Rights (GPR). Offerors that propose delivery of technical data, NCS, or NCS documentation subject to GPR should fully explain how a portion of the data was developed at private expense. Specifically, offerors must explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated, how the incorporation will benefit the program, and address whether those portions or processes are segregable.

Offerors that propose delivery of non-commercial technical data with

Limited Rights, NCS with Restricted Rights, or NCS documentation with Limited Rights will be considered. Proposals should fully explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated and how the incorporation will benefit the program and whether those portions or processes are segregable.

Offerors shall include the data rights assertions as required by DFARS

252.227-7017, Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software. The assertions list is included in Section K and due at time of proposals. Assertions must be completed with specificity. Each assertion must identify the technical data or computer software to be delivered and the associated item, component, or process developed exclusively or partially at private expense to which it pertains. Nonconforming assertions lists will be rejected.

Terms used in this section are defined in the clauses at 252.227-7013, Rights in Technical Data-Noncommercial Items, and 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation.

THIRD PARTY SOFTWARE (COMMERCIAL AND NONCOMMERCIAL):

If any such software, noncommercial or commercial, is not reasonably identifiable at proposal submission, it must still be approved by the contracting officer prior to incorporation. This obligation to obtain pre-approval by the contracting officer, as described above, continues throughout contract administration.

Noncommercial Computer Software: DFARS 252.227-7014(d) describes requirements for incorporation of third party noncommercial copyrighted computer software and computer software documentation, and is incorporated as follows. The Contractor shall not, without the written approval of the Contracting Officer, incorporate any copyrighted computer software or computer software documentation in the software or documentation to be delivered under this contract unless the Contractor is the copyright owner or has obtained for the Government the license rights necessary to perfect a license or licenses in the deliverable software or documentation of the appropriate scope set forth in DFARS 252.227- 7014(b); and prior to delivery of such—

i. Computer software, has provided a statement of the license rights obtained in a form acceptable to the Contracting Officer; or

ii. Computer software documentation, has affixed to the transmittal document a statement of the license rights obtained.

In addition, all noncommercial computer software will receive the appropriate level rights set forth in DFARS 252-7014(b), which could include: Unlimited Rights, GPR, Restricted Rights, or specifically negotiated license.

Commercial Computer Software: For commercial computer software, the Government will neither accept nor execute a DD Form 250 for such software deliverables until the Contractor obtains from all third party software suppliers and/or vendors (Licensor) licenses for any commercial computer software to be delivered that are consistent with Federal Statutes, Federal Case Law, and Federal Regulations. The following terms and conditions, among others, should not be included in the terms and conditions of the commercial computer software license between the Licensor and the Government (Licensee):

i. The license shall not subject the Government to a contingent liability or a liability that is indefinite or indeterminate, including but not limited to: indemnification clauses, unilateral price increases, the right to attorney fees, automatic assessment of charges, or automatic renewal provisions, as these provisions may constitute obligations in advance or in excess of an appropriation and may violate the Anti- Deficiency Act.

ii. The license shall be governed by Federal Statutes, Federal Case Law, and Federal Regulations, and shall not be subject to the laws or jurisdiction of any municipality, state, or foreign country. The license shall not bind the Government to litigation in a particular forum or venue or require the Government to participate in arbitration.

iii. The license shall not include non-substitution language that would preclude or limit the Government from using another vendor/reseller and/or product to fulfill Government requirements.

iv. The Licensor shall not have the authority to unilaterally terminate the license. All remedies available shall be consistent with the Disputes and Termination Clauses in the underlying basic contract.

v. The Licensor shall not have the right to enter the premise or monitor Government networks for the purpose of auditing the use of the license.

vi. The Licensor shall not have the authority to control or otherwise influence any litigation between a third party and the Government.

vii. The Licensor shall not use the fact that the Government is using the Licensor's products in any notification or advertisement to the public (e.g., no publicity rights permitted).

Additionally, the Contractor may be required to obtain licenses that comply with the following terms and conditions, based on the Government’s needs:

i. The license shall not disclaim all warranties through use of an "as is" provision.

ii. The license shall neither restrict the Government from using the product at various sites nor limit use of the product by various Government agencies or third parties performing work on behalf of the Air Force under the ADEPT Program. In performance of the ADEPT Program, Government personnel as well as Government contractors may use the software.

iii. The license shall not limit the Government’s use of the software at other Government and Government contractor sites.

iv. The license shall not require automatic updates or give Licensor the authority to unilaterally replace the software.

v. The license shall not restrict the Government from copying or embedding elements of accessible code into other applications (e.g., nesting code, derivative works).

The Contractor may obtain agreement from the Licensor to insert the clause below in its respective software licenses intended to be transferred to the Government:

"In the event that any of the provisions of the [Software License] are determined to be inconsistent with Federal law or do not otherwise satisfy the Government's needs, the parties to the [Software License] hereby agree that such provisions shall be null and void as they pertain to the Government. Specifically, the following sections are hereby deleted from the [Software License] [and/or amended as indicated below]:

[Section X: deleted; Section Y: amended as follows […]"

If the Licensor will not agree to the terms and conditions cited herein and/or as contained in DFARS 227.72, the Contractor shall retain the current license on behalf of and for the benefit of the US Government if permissible under its license, and such use will not subject the

Government to the terms of the license. If the software in question is required to be delivered to the Government, the Licensor must grant the Government a sublicense that allows the Government to use the software to meet its requirements.

The Contractor shall provide documentation to clearly correlate or map any commercial computer software to be delivered to:

i. Contract Line Item Numbers (CLIN);

ii. Contract Deliverables (CDRLs);

iii. Paragraphs in the Statement of Work (SOW); and

iv. Portions of any functional block diagrams and/or system architecture diagrams, so that it can be readily determined where certain commercial computer software corresponding to certain software license agreement(s) are physically located on the system to be delivered under the contract.

II. Award Information

1. Anticipated Award Date: To be determined for each Call.

2. Anticipated funding: Each Call will include an anticipated funding profile/amount for that specific Call.

III. Eligibility Information

1. Eligible Offeror: This is an unrestricted solicitation. Businesses of all sizes are encouraged to propose on all or any part of this solicitation under each Call.

2. Cost Sharing or Matching: Not required.

3. Federally Funded Research and Development Centers: The following guidance is provided for Federally Funded Research and Development Centers (FFRDCs) contemplating submitting a proposal, as either a prime or subcontractor. FAR 35.017-1(c)(4) prohibits an FFRDC from competing with any non-FFRDC concern in response to a Federal agency request for proposal for other than the operation of an FFRDC (with exceptions stated in DFARS 235.017-1(c)(4)). There is no regulation prohibiting an FFRDC from responding to a solicitation. However, the FFRDC’s sponsoring agency must first make a determination that the effort being proposed falls within the purpose, mission, general scope of effort, or special competency of the FFRDC, and that determination must be included in the FFRDC’s proposal. In addition, AFRL must make a determination that the work proposed would not place the FFRDC in direct competition with domestic private industry. Only after these determinations are made, would a determination be made concerning the FFRDC’s eligibility to receive an award.

4. Government Agencies: If a Government agency is interested in participating in this program, contact the Technical POC identified in the applicable Call. If those discussions result in a mutual interest to pursue your agency's participation, the effort will be pursued independent of this announcement.

5. Other:

a. Foreign participation: Foreign Participation is not authorized at the Prime Contractor level. The U.S. Prime Contractor and/or Sub-Contractor may hire foreign nationals (FN) with prior Foreign Disclosure Office (FDO) approval; however, FNs will be limited to Public Domain information only.

Public Domain information is defined as information that is releasable to the general public and sometimes referred to as open source material.

Examples include but are not limited to newspapers, magazines and information posted on the Internet. Any proprietary information will have to be appropriately protected.

b. This acquisition involves data that are subject to export control laws and regulations. This determination will be made on a case-by-case basis and identified in each Call. If the data is determined to be subject to export control laws, only contractors who are registered and certified with the Defense Logistics Agency and have a legitimate business purpose may participate in this solicitation. Contact the U.S./Canda Joint Certification Program Office, Defense Logistics Agency, Logistics Information Services J34, HDI Federal Center, 74 Washington Avenue N., Battle Creek, Michigan 40937-3084, (1-800-352-3572) or the Joint Certification Program Office (JCO) at JCP-Helpdesk@dla.mil for further information on the certification process. You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with your proposal, if applicable.

c. There are no limits on the number of proposals an offeror may submit.

d. You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date as identified in each Call.

IV. Proposal and Submission Information

1. Overview: Proposals submitted under a Call shall be in accordance with the instructions provided both in the specific Call and this announcement. For individual calls, the Government intends to review resulting proposals and award all, some, or none of the proposal received without negotiations/discussions. However, the Government does reserve the right to negotiate with those offerors whose proposals have been selected for funding. Offerors should be alert for any ARA/Call amendments that may change proposal requirements or permit extensions to the proposals submission date.

mailto:JCP-Helpdesk@dla.mil

2. Proposal Instructions for Each Call:

a. General Instructions:

i. Offerors will submit a technical and cost proposal within TBD working days of the proposal request (to be determined for each Call). After receipt, proposals will be reviewed in accordance with the award criteria as defined in the Call. Proposals will be categorized and subsequently selected for negotiations.

ii. Technical/management and cost/business volumes should be submitted in separate volumes and must be valid for 180 days.

iii. Proposals must reference the announcement number FA8650-20-S- 6009 and relevant technical areas of interest.

iv. Offerors must submit one original and one hard copy of their proposals to the Contracting POC.

v. Offerors are advised that only Contracting Officers are legally authorized to contractually bind or otherwise commit the Government.

vi. The cost of preparing proposals in response to this ARA is not considered an allowable direct charge to any resulting or any other contract; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in FAR 31.205-18.

vii. No classified technical proposals or cost volumes are expected.

Offerors are encouraged to keep all elements of the proposal package unclassified. In the rare case where an offeror has a need to submit a classified appendix, please contact the Technical POC for delivery instructions.

b. Technical/Management Proposal To Be Solicited via Calls:

i. Page Limitations: The following describes proposal page limitations.

a) The Technical/Management Proposal shall be limited to (TBD for each Call) pages. Technical/Management proposals and SOWs must be provided in Microsoft Word (DOCX) format. Signed pages may be submitted in Adobe (PDF) format.

b) Font shall be standard 10-point business font Arial.

c) Character spacing must be "normal," not condensed in any manner.

d) Pages shall be double-spaced (must use standard double-space function in Microsoft Word), double sided (each side counts as one page), 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom.

e) All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items.

f) Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page (TBD for each Call). The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5 by 11 portion) tables, charts, appendices, attachments, resumes, etc.

g) The proposal page limit does not include the offeror’s proposed Statement of Work (SOW); however, the same formatting rules apply to the SOW, which is limited to (TBD for each Call) pages.

h) Please note: The Government will check the proposal and SOW for conformance to the stated requirements. Any pages in excess of the stated page limitation after the format check will not be considered for review purposes.

ii. The Technical/Management proposal(s) shall include a discussion of the nature and scope of the research and the technical approach.

Additional information on prior work in this area, descriptions of available equipment, use of base support (if desired), data and facilities and resumes of personnel who will be participating in this effort should also be included as attachments to the technical proposal. The volume(s) shall include a SOW(s) detailing the technical tasks proposed to be accomplished under the proposed effort and suitable for contract incorporation. Do not include any proprietary information in the SOW. In addition to the contractor proposed SOW, a Government generated SOW attachment containing additional contracting requirements will be included in any resulting contracts.

iii. Any questions concerning the technical proposal or SOW preparation shall be referred to the Contracting POC.

c. Cost/Business Proposal To Be Solicited Via Calls:

i. Separate the proposal into a business section and cost section.

Adequate price competition is anticipated.

a) A Model Contract for FAR-based contracts will be provided as an attachment for each Call. No sample is provided for Other Transactions. The Model Contract will provide examples of clauses that may be included in final contracts, and it will provide a basic contract structure. Contracts that are ultimately awarded against the individual Calls may vary based on individual program requirements, negotiated terms and conditions, etc.

b) The business section should contain all business aspects to the proposed contract, such as type of contract, any exceptions to terms and conditions of the Model Contract, any information not technically related, etc. Provide rationale for exceptions to any portion of the Model Contract.

c) Associate Contractor Agreements: Associate Contractor Agreements (ACAs) are agreements between contractors working on Government contracts that require them to share information, data, technical knowledge, expertise, or resources. The contracting officer may require ACAs when contractors working on separate Government contracts must cooperate, share resources or otherwise jointly participate in working on contracts or projects.

Prime contractor to subcontractor relationships do not constitute ACAs. For each award, the contracting officer will identify associate contractors with whom agreements are required.

d) Identify any technical data that will be delivered with less than unlimited rights.

e) Subcontracting Plans: For efforts to exceed $700,000, Subcontracting Plans shall be submitted in the cost/business proposal. Reference FAR 19.704, DFARS 219.704, and AFFARS 5319.704(a)(1) for subcontracting plan requirements. Small business concerns are exempt from this requirement.

f) Limitations on Pass-Through Charges: As prescribed in FAR 15.408(n)(1) & 15.408(n)(2), provisions 52.215-22, Limitations on Pass Through Charges- Identification of Subcontract Effort (Oct 2009), apply.

g) Completed Certifications and Representations will be sent when a proposal is requested and are due with the submission of the proposal. Offerors may also be required to submit updated or supplemental Certifications and Representations based on the specifics of their proposal. See Section K, Representations and Certifications, as included with the Call's Model Contract, and provide the completed Section K as part of the proposal package for each Call.

h) If an offeror proposes the use of Government Furnished Property (GFP), other than GFP identified in the ARA, the offer must specifically identify each piece of GFP in the Cost/Business Proposal and propose and substantiate a rental cost for evaluation purposes in accordance with FAR 45.202. Include the following information in the proposal:

(i) A list describing all Government property that the offeror or its subcontractors propose to use on a rent-free basis. The list shall identify the accountable contract under which the property is held and the authorization for its use (from the contracting officer having cognizance of the property);

(ii) The dates during which the property will be used and, for any property that will be used concurrently in performing two or more contracts, the amounts of the respective uses in sufficient detail to support prorating the rent;

(iii) The amount of rent that would otherwise be charged in accordance with FAR 52.245-9, Use and Charges; and

(iv) The voluntary consensus standard or industry leading practices and standards to be used in the management of Government property, or existing property management plans, methods, practices, or procedures for accounting for property.

ii Cost Element Breakdown: Clear, concise, and accurate cost proposals reflect the offeror's financial plan for accomplishing the effort contained in the technical proposal. As a part of its cost proposal, the offeror shall submit the information outlined below, together with supporting breakdowns. All direct costs (labor, material, travel, computer, etc.) as well as labor and overhead rates should be provided by contractor fiscal year (CFY). Detailed cost element breakdowns by Government Fiscal Year or calendar year are not required. The supporting schedules may include summary level estimating rationale used to generate the proposed costs. The cost element breakdown(s) should include the following if applicable.

a) Direct Labor: Direct labor should be detailed by number of labor hours by category of labor.

b) Labor and Overhead Rates: Direct labor hours, with their applicable rates, must be broken out and the bases used clearly identified. The source of labor and overhead rates and all pricing factors should be identified. For instance, if a Forward Pricing Rate Agreement (FPRA) is in existence, that should be noted, along with the Administrative Contracting Officer (ACO) name and telephone number. If the rates are based on current experience in your organization, provide the historical base used and clearly identify all escalation, by year, applied to derive the proposed rates. If computer usage is determined by a rate, identify the basis used and rationale used to derive the rate.

c) Material/Equipment: List all material/equipment items by type and kind with associated costs and advise if the costs are based on vendor quotes, data and/or engineering estimates; provide copies of vendor quotes and/or catalog pricing data.

d) Subcontractor Costs: Submit all subcontractor proposals and analyses with your cost proposal (See FAR 15.404-3(b)). If the subcontractor will not submit cost and pricing information to the offeror, this information must be submitted directly to the Government for analysis. On all subcontracts and interdivisional transfers, provide the method of selection used to determine the subcontractor and the proposed contract type of each subcontract.

An explanation shall be provided if the offeror proposes a different amount than that quoted by the subcontractor. The offeror’s proposal must:

(i) Identify principal items/services to be subcontracted.

(ii) Identify prospective subcontractors and the basis on which they were selected. If non-competitive, provide selected source justification.

(iii) Identify the type of contractual business arrangement contemplated for the subcontract and provide rationale.

(iv) Identify the basis for the subcontract costs (e.g., firm quote or engineering estimate, etc.).

(v) Identify the cost or pricing data submitted by the subcontractor.

(vi) Provide an analysis of the proposed subcontract in accordance with FAR 15.404-3(b). Provide an analysis concerning the reasonableness, realism and completeness of each subcontractor’s proposal. If the analysis is based on comparison with prior prices, identify the basis on which the prior prices were determined to be reasonable. The analysis should include, but not be limited to, an analysis of: materials, labor, travel, other direct costs and proposed profit or fee rates.

e) Special Tooling or Test Equipment: When special tooling and/or test equipment is proposed, attach a brief description of items and indicate if they are solely for the performance of this particular contract or project and if they are or are not already available in the offeror's existing facilities. Indicate quantities, unit prices, whether items are to be purchased or fabricated, whether items are of a severable nature and the basis of the price. These items may be included under Direct Material in the summary format.

f) Consultants: When consultants are proposed to be used in the performance of the contract, indicate the specific project or area in which such services are to be used. Identify each consultant, number of hours or days to be used and the consultant's rate per hour or day. State the basis of said rate and give your analysis of the acceptability of the consultant's rate.

g) Travel: Travel costs must be justified and related to the needs of the project. Identify the number of trips, the destination and purpose. Travel costs should be broken out by trip with number of travelers, airfare, per diem, lodging, etc.

h) Computer Use: Detail the amount and kind of computer usage, the cost, and how the costs were derived.

i) Facilities Capital Cost of Money: If Facilities Capital Cost of Money is proposed, a properly executed DD Form 1861 is required.

j) Project Funding Profile: Offerors should include a project funding profile by Government Fiscal Year (GFY) (1 Oct through 30

Sep) for budgetary purposes. This will enable the Government to easily identify program funding needs by GFY.

k) If an offeror takes exceptions to the requirements called out in the announcement (e.g., base support, Government-furnished property (GFP), CDRLs), the exceptions should be clearly stated in the cost proposal.

l) Forward Pricing Rate Agreements: Offerors who have forward pricing rate agreements (FPRAs) and forward pricing rate recommendations (FPRRs) should submit them with their proposal.

m) Cost/Business proposals have no page limitations.

e. Proposal Content Summary: You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date.

V. Proposal Review Information:

1. Peer or Scientific Review Criteria: Proposals will be reviewed using the criteria provided for each individual Call against the ADEPT ARA. The technical aspect, which is ranked as the first order of priority, shall be reviewed based on the following criteria that are of descending order of importance.

a. Technical:

i. The potential to transition the research and development deliverables to future government needs. This includes evaluation of proposed data rights.

ii. The offeror’s understanding of the scope of the technical effort.

iii. Soundness of the offeror’s technical approach, including whether the proposal identifies major technical risks, clearly defines feasible mitigation efforts, and demonstrates related experience and qualifications of technical personnel.

iv. Unique and innovative approach proposed to accomplish the technical objectives. New and creative solutions and/or advances in knowledge, understanding, technology, and the state of the art.

b. Cost/Price: The cost/price criterion includes the realism of the proposed cost. Cost/Price is a substantial factor, but ranked as the second order of priority. (If an offeror proposes the use of GFP other than any GFP identified in this ARA, and that proposed GFP provides the offeror an unfair competitive advantage, then FAR 45.202 requires rental equivalent be applied to the Cost Factor for evaluation purposes only).

2. Review and Selection Process:

a. Categories: Based on the Peer or Scientific Review, proposals will be categorized as Selectable or Not Selectable (see definitions below). The selection of one or more sources for award will be based on the Peer or Scientific Review, as well as importance to agency programs and funding availability.

i. Selectable: Proposals are recommended for acceptance if sufficient funding is available.

ii. Not Selectable: Even if sufficient funding existed, the proposal should not be funded.

Note: The Government reserves the right to award some, all, or none of proposals. When the Government elects to award only a part of a proposal, the selected part may be categorized as Selectable, though the proposal as a whole may not merit such a categorization.

b. No other criteria will be used.

c. Prior to award of a potentially successful offer, the Contracting Officer will make a determination regarding price reasonableness.

VI. Award Administration Information:

1. Award Notices: Offerors will be notified whether their proposal is recommended for award on or about 30 days after receipt of the proposal.

The notification is not to be construed to mean the award of a contract is assured, as availability of funds and successful negotiations are prerequisites to any award.

2. Administrative and National Policy Requirements: See ARA Section I.

3. Reporting: See ARA Paragraph I.4.a., Contract Data Requirements List

(CDRL).

VII. Other Information:

1. Acquisition of Commercial Items: Based upon market research, the Government is not using the policies contained in Part 12, Acquisition of Commercial Items, in this solicitation. However, interested offerors may identify to the Contracting Officer their interest and capability to satisfy the Government’s requirement with a commercial item within 15 days of this notice.

2. Support Contractors: Only Government employees will participate in Peer or Scientific Reviews. Offerors are advised that employees of commercial firms under contract to the Government may be used to administratively process proposals, monitor contract performance, or perform other administrative duties requiring access to other contractors' proprietary information. These support contracts include nondisclosure agreements prohibiting their contractor employees from disclosing any information submitted by other contractors or using such information for any purpose other than that for which it was furnished.

3. Informal Feedback Sessions: When requested, an informal feedback session will be provided. The process will follow the guidelines outlined in the notification letter.

4. Item Unique Identification and Valuation. It is DoD policy that contractors shall be required to identify the Government’s unit acquisition cost for all deliverable end items for which Item Unique Identification applies.

Therefore, proposals must clearly break out the unit acquisition cost for any deliverable items. See DFARS 211.274-3, Policy for Valuation, for more information. (Per DoD, "fully burdened unit costs" to the Government would include all direct, indirect, and G&A costs, and an appropriate portion of fee).

For more information, see the following website:

http://www.acq.osd.mil/dpap/pdi/uid/index.html.

5. Pre-Award Clearance: Pursuant to FAR 22.805, a preaward clearance must be obtained from the U.S. Department Of Labor, Employment Standards Administration, Office Of Federal Contract Compliance Program’s (OFCCP) prior to award of a contract (or subcontract) of $10,000,000 or more unless the contractor is listed in OFCCP’s National Preaward Registry https://ofccp.dol-esa.gov/preaward/pa_reg.html. Award may be delayed if you are not currently listed in the registry and the Contracting Officer must request a preaward clearance from the OFCCP.

6. Updates of Publicly Available Information Regarding Responsibility Matters: Any contract or assistance award that exceeds $550,000; and when the offeror checked “has” in paragraph (b) of the provision FAR 52.209-7, shall contain the clause/article FAR 52.209-9 “Updates of Publicly Available Information Regarding Responsibility Matters (JUL 2013)”

7. Proposal Content Checklist: You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date.

a. Proposals are due to the Contracting POC.

b. Proposals are due no later than the due date and time specified in the Call.

c. Proposal page limits are strictly enforced. See ARA Section IV.2.b for page limits.

d. If a contract is proposed, completed Certifications and Representations (Section K) are required. See Section K in the Model Contract as attached to the Call solicitation.

e. The Cost/Business Proposal must contain all information described in the Content and Form of Proposal Submission Section.

http://www.acq.osd.mil/dpap/pdi/uid/index.html https://ofccp.dol-esa.gov/preaward/pa_reg.html

f. For any subcontracts proposed, the Cost/Business Proposal must contain a subcontractor analysis IAW FAR 15.404-3(b).

g. Offerors other than small businesses must include a subcontracting plan in Microsoft Word format submitted via email, as well as a hard copy.

h. Proposals must be submitted in the format specified in ARA Section IV.

i. Offerors who have Forward Pricing Rate Agreements (FPRAs) or Forward Pricing Rate Recommendations (FPRRs) should submit them with their proposal.

j. If a DD254 is applicable, offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at http://www.dss.mil.

k. If effort is subject to Export Control, offerors must submit a Certified DD Form 2345, Militarily Critical Technical Data Agreement, with proposal.

http://…