ARDIS_ARA_FA8650-19-S-1110.pdf

08 Oct 2018

Advanced Research Announcement (ARA) with Calls

Overview Information

NAICS Code: The NAICS Code for this acquisition is 541715 and the small business size is 1,000 employees.

Federal Agency Name: Air Force Research Laboratory, AFRL/RY Sensors Directorate

ARA Title: Architecture Refinement, Demonstration and Integration Systems

(ARDIS)

ARA Type: This is the Initial Announcement

ARA Number: FA8650-19-S-1110

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 21 DEC 2023.

Calls (One-Step or Two-Step, See Section IV for instructions):

Over the period of this ARA, Calls may be issued to request white papers or proposals for specific area(s) of interest. It will be determined on a Call by Call basis whether or not the announcement is for white papers (two-step) or proposals (one-step). Each call will contain specific requirements and pertinent information.

White papers/Proposals submitted in response to the Calls will be accepted as specified in the individual Calls and evaluated in accordance with the Proposal Review Information (section IV.2. of the Call). Offerors should monitor the Federal Business Opportunities website at http://www.fbo.gov in the event this announcement is amended or Calls are issued.

Proposals Due Date and Time:

For ONE-STEP Calls

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

For TWO-STEP Calls

First Step: WHITE PAPER DUE DATE AND TIME: To be provided in Calls.

Second Step: PROPOSAL DUE DATE AND TIME: To be provided in the Requests for Proposals sent to offerors that submit White Papers considered to meet the needs of the Air Force.

NOTE: White Paper/proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). Any white paper or 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 Contract’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 or Request for Proposal letter as a result of security delays will be considered “late.” Furthermore, note that if offerors utilize commercial carriers in the delivery of proposals, they 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 white paper/proposal submission is encouraged.

Submission: White Papers and proposals must be submitted to a Contracting Point of Contact (POC): Cynthia Brockert, Contract Negotiator or Sarah Chaffe, Contracting Officer, AFRL/RQKSR, Bldg 45, 2130 8th St., Wright-Patterson AFB, OH 45433-7541.

Annual Updates: It is noted that for ease of reference this ARA will be republished at yearly intervals for updates.

Solicitation Request: Air Force Research Laboratory, AFRL/RY Sensors Directorate, Wright-Patterson Air Force Base is not soliciting white papers or proposals on the overarching effort described below. 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 Cost type contracts.

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 http://farsite.hill.af.mil

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 an OT agreement should be developed and negotiated on a case-by-case basis.

Estimated Program Cost: The total estimated program value is $688,500,000 with multiple awards ranging from $50,000.00 to $100,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 other transactions and/or 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 other transactions or contracts that may be awarded to an individual offeror.

Brief Program Summary: AFRL/RY has a need to explore sensor system integration across multiple sensor areas across multiple domains and/or cyber environments. DoD systems have become increasing complex over the years and our warfighter’s needs are continually changing to keep up with our adversaries.

More than ever the Air Force needs to develop new and novel concepts for sensor systems across multiple domains and spectrums that aid in Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR), targeting, combat identification, battlespace awareness, protection of airborne assets in contested environments, and reliable electronic components within our sensor systems. AFRL/RY has a need to integrate sensor systems, demonstrate mature sensor technologies, refine integration architectures, and explore and experiment to achieve integration of sensor technologies.

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. No guidance related to technical approach will be given. However, questions related to the objectives of the effort or prior similar efforts may be answered. 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 FedBizOpps for all contractors to review. For those white papers not selected to provide a full proposal, notification and feedback will be managed by the Contracting POCs.

Address technical questions to the Technical POC: Major Joseph Garn, 2241 Avionics Circle, WPAFB, OH 45433, 937-713-8517, joseph.garn@us.af.mil

Address contracting questions to the Contracting POC: Sarah E. P. Chaffe, Contracting Officer, AFRL/RQKSR, 2130 Eighth Street, Area B, Bldg. 45, Wright-

Patterson AFB, OH, 45433-7541, phone number: (937) 713-9952, e-mail address:

sarah.chaffe@us.af.mil or Cindy Brockert, Contract Negotiator, AFRL/RQKSR, 2130 Eighth Street, Area B, Bldg. 45, Wright-Patterson AFB, OH 45433-7541, phone number: (937) 713-9840, e-mail address: cynthia.brockert@us.af.mil.

mailto:sarah.chaffe@us.af.mil mailto:cynthia.brockert@us.af.mil

Full Text Announcement

I. Program Description: Air Force Research Laboratory, Sensors Directorate (AFRL/RY) is annoucingits intent to solicit proposals under this ARA with Calls.

Socilitations for white papers/proposals will accomplished via Calls. The Calls will encompass the following effort:

1. Statement of Objective/Description of Technical Area(s): The purpose of the ARA is to integrate multiple combinations of advanced sensors, processing, and exploitation capabilities focused on C4ISR onto various weapon systems.

Calls issued against this ARA will:

• Demonstrate and assess integrated sensor systems in operationally relevant environments, both through laboratory simulation and real-world flight testing.

• Experiment to refine integrated sensor systems architecture, including open architecture, adaptable interfaces, and system component technologies to determine the optimal architecture for systems of sensor systems.

• Perform experiments on integration methodologies involved with systems of sensor systems technologies to garner a better understanding on best practices and evaluation of performance profiles of combined sensor technologies.

Technologies will be broad-ranging, and will likely include programs from across RY. Calls to be issued against the ARDIS ARA must a) fall under at least one of the Sensor Areas of Interest detailed in paragraph I.1.a.

below, and 2) involve at least one of the types of work detailed in paragraph I.1.b. below.

a. Sensor Areas of Interest:

a.1 RADIO FREQUENCY (RF) SENSORS IN MULTIPLE ENVIROMENTS:

Focuses on all-weather ISR using non-traditional radar modes for persistent surveillance across permissive, contested, and highly contested boundaries in airborne, space, and ground-based radar systems.

a.2 EO SENSORS:

Focuses on surveillance, reconnaissance, and targeting using sensor technology throughout the optical to infrared (IR) regions of the electromagnetic spectrum. Experimentation and testing conducted under this area involves both active and passive, literal and non-literal sensing techniques.

a.3 PROTECTION OF AIRBORNE ASSETS UTILIZING SPECTRUM

WARFARE:

Focuses on resilient, adaptive multi-spectrum warfare technologies and techniques with the goal of ensuring unrestricted access to the airspace and the electromagnetic (EM) spectrum in contested and congested environments. This area of interest focuses on aircraft mission assurance – the protection of airborne platforms, manned and unmanned, in contested environments. This portion of the effort is threat driven, with a particular focus on the enduring challenge of defeating enemy integrated air defense systems. This area will procure the design of the countermeasures complement to the sensing mission of the Directorate, as well as Position, Navigation, and Timing (PNT) technologies and communications for military operations in contested and denied environments.

a.4 CYBER SECURE, TRUSTED, AND OPEN SENSOR SYSTEMS:

Focuses on the design/procurement of systems that are cyber secure and trusted with emphasis on open systems to improve ease of integration of multiple sensor systems. These designs will include both software and hardware solutions.

a.5 INCREASING BATTLESPACE AWARENESS WITH SENSOR

SYSTEMS:

Focuses on developing the battlespace understanding necessary to close the loop around multiple, multi-domain mission effects chains (MECs). This includes design and experimentation leading to machine learning for sensing autonomy, fusion for synthesis, target phenomenologies, denied and difficult target prosecution, and multi-domain strategies to orchestrate closed-loop sensing. This area will focus on both single and multi-INT systems and develop state-of-the-art fusion and exploitation algorithms and integration technologies for increasing battlespace awareness, including human-machine interfaces for sensor visualization and Command and Control (C2) to ensure maximum awareness. Understanding gained will be leveraged for models and tools geared toward modeling, simulation and analysis (MS&A).

a.6 SURVIVABLE AND RELIABLE SENSOR ELECTRONIC COMPONENTS:

Focuses on the design/procurement of electronics, electro-optics, photonics, and supporting technologies to increase a system’s survivability. These designs will focus on state-of-the-art electronic devices and material technologies.

b. Integration Efforts, Ground and Flight Tests/Demonstrations, Transition:

Various methods will be used to integrate sensor technologies into systems of systems. Systems of sensors systems will also undergo testing and demonstration through multiple methods and domains. The procurement of new and improved integration designs and technologies will also be conducted. Individual Calls under this solicitation may include some or all of the following activities and may tailor requirements as appropriate.

b.1 INTEGRATION ACTIVITIES:

The contractor shall integrate various sensor technologies into systems using various integration methods and tools. Integration methods may include, but will not be limited to, Models-Based Systems Engineering and other automated integration tools. Such tools and methods may be provided by the Government or designed by the contractor, and will vary by Call.

b 2 GROUND DEMONSTRATIONS / TESTS:

The contractor shall capture technology/test requirements for laboratory and ground demonstrations, tests, or exercises. The contractor shall identify test platforms and environments applicable to test objectives. The contractor shall draft and coordinate documents for each test (Federal Aviation Regulations (FARs), test cards, checklists). The contractor shall participate in periodic meetings (Configuration Control Board (CCB), Test Planning Working Group (TPWG), Safety Readiness Board (SRB), Test Readiness Board (TRB) and perform relevant actions as required. The contractor shall coordinate with any and all pertinent stakeholders and partners at the Government’s direction. The contractor shall document test reports.

b.3 FLIGHT TESTS:

The contractor shall coordinate flight operations and specific test approvals with proper officials. The contractor shall capture technology/test requirements for flight demonstrations, tests, or exercises. The contractor shall identify test platforms. The contractor shall draft and coordinate documents for each test (FAR, test cards, checklists). The contractor shall participate in periodic meetings (CCB, TPWG, SRB, TRB) and perform relevant actions as required. The contractor shall procure materials to collect, store, and retrieve sensory data and air/ground truth data. The contractor shall secure airworthiness and coordinate test ranges and collection targets.

The contractor shall supply airworthy aircraft. The contractor shall coordinate airspace, flight plans, permits, and frequency clearance with respective authorities. The contractor shall determine equipment configuration, setup, interconnections, and protocols, and integrate the system under test into a System Integration Laboratory and/or aircraft. The contractor shall hold Test Readiness Reviews (TRRs) and Flight Readiness Reviews (FRRs) as required.

The contractor shall perform ground and flight activities to include aircraft preflight checks, sensor initialization and checks, instrumentation checks, and aircraft launch and recovery. The contractor shall execute all steps described in test cards and checklists.

b.4 SENSORS INTEGRATION:

The contractor shall conduct experimentation into new and/or improved integration methods and technologies. This task includes the experimentation and refinement of integrated sensor systems architectures, including open architectures, adaptable interfaces, and system component technologies to determine the optimal architecture for systems of sensor systems. Potential areas include Models-Based Systems Engineering, Digital Thread, and other automated integration tools. Specific topics and requirements will vary by Call.

b.5 SOFTWARE DEVELOPMENT:

The contractor shall procure the development of software as required by Call.

Software development may include (but is not limited to) software such as sensor processing algorithms, software interfaces or software models.

b.6 SYSTEM TRANSITION/MATURATION:

The contractor shall perform system transition activities to include the following:

b.6.1 Procure software updates and maintenance for integration into operational systems.

b.6.2 Provide modeling and simulation tools, and database updates.

b.6.3 Develop transition plans, perform and execute assessments, data collections, and/or modeling and simulation activities for application of technology to production unit/systems(s).

b.6.4 Participate in system deployment, technical troubleshooting, required equipment upgrades, training, and technological input as needed.

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 AFRL/RYOY 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 that may increase overall contract ceiling amount.

4. Deliverable Items:

a. Data Items: DD Form 1423-1 CDRLs 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. A sample listing is attached to the Model Contract, attached to this ARA.

b. Software: Software deliverables to be determined (TBD) for each Call, if applicable.

c. Hardware: Hardware deliverables to be determined (TBD) for each Call, if applicable.

d. Other: To be determined for each Call.

5. Schedule:

a. Overall Period of Performance: To be Determined (TBD) for each Call.

b. Data Items: TBD on each Call.

c. Software: TBD on each Call.

d. Hardware: TBD on each Call.

6. Other Requirements:

a. Program Security Classification: It is anticipated that the majority of the awards will be Top Secret classification/safeguarding capability, but security classification will be determined for each award. A draft DD254 will not be attached to this ARA, but will be 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.

b. OPSEC: see Statement of Objectives for each individual Call.

c. Export Control: Information involved in this 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 effort is subject to export control, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal.

d. 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.

e. Contractor Performance Assessment Reporting System (CPARS) will likely be applicable, but will be determined on a Call by Call basis in accodrance 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. If an IDIQ contract is awarded as a result of a Call, CPARS will be conducted for each task order. 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.

http://www.dss.mil/

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: Base Support/Network Access will be determined for each Call.

c. Data Rights will be determined for each call. Data Rights desired by the contractor should be included with proposal submission as part of the Section K.

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 NCS developed or delivered under this contract are of significant concern to the Government. The Government will therefore carefully consider 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. Offers that propose delivery of technical data, NCS, or NCS documentation subject to Government Purpose Rights should fully explain how the data was developed at private expense. Specifically, offers 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 technical data, NCS, or NCS documentation subject to Limited Rights, Restricted Rights, or Specifically Negotiated License 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 both the data and each such item, component, or process listed. 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):

DFARS 252.227-7014(d) describes requirements for incorporation of third party computer software. Any third party software (commercial and noncommercial) to be incorporated into a deliverable must be clearly identified in the proposal.

Prior to delivery of any third party software, the contractor will obtain an appropriate license for the Government, and the written approval of the contracting officer.

Any third party software to be delivered to the Government that are not reasonably identifiable at proposal submission, must still be approved by the contracting officer prior to incorporation into a system deliverable. This obligation to obtain pre-approval by the contracting officer, as described above, continues throughout contract administration.

The Government will neither accept nor execute a DD Form 250 for the software deliverables until the Contractor obtains from all third party software suppliers and/or vendors (Licensor) licenses that comply with the following terms and conditions for the Government (Licensee):

1. The license shall not subject the Government to liability that is indefinite or indeterminate, such as an indemnification clause, as it would constitute an obligation in advance or in excess of an appropriation and violate the Anti- Deficiency Act.

2. The license shall not create a contingent liability for the Government. This includes, but is not limited to: unilateral price increases, automatic assessment of charges, and automatic renewal of the license.

3. The license shall be governed by Federal Statutes, Case Law, and Federal

Regulations, and shall not be subject to the laws or jurisdiction of any municipality, state, or foreign country.

4. 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.

5. The license shall not comment on entitlement to attorney fees.

6. The Licensor shall not have the authority to unilaterally terminate the license. All remedies available shall be consistent with the Disputes Clause in the underlying basic contract.

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

8. The Licensor shall not use any injunctive relief clauses as the Licensor cannot prevent the Licensee from performing mission operations.

9. The Licensor shall not have the authority to control any litigation between a third party and the Licensee.

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

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: Cost Sharing is 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 performing work, contact the Technical POC identified in the 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 will be considered on a case-by-case basis and identified in each Call. If it is determined that foreign participation is not allowed, the US Prime Contractor and/or Sub-Contractor may hire foreign national with prior 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 may involve data that is subject to export control laws and regulations. This determination will be made on a case-by-case basis and indentified 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 Services Center (DLSC) and have a legitimate business purpose may participate in this solicitation. Contact the Defense Logistics Services Center, 74 Washington Avenue N., Battle Creek, Michigan 40917- 3084 (1-800-352-3572) 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. Proposal Submissions: There are no limits on the number of white papers/proposals an offeror may submit.

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

IV. Proposal and Submission Information:

1. Overview: White papers and/or proposals submitted under a Call shall be in accordance with the instructions provided both in the specific Call and this announcement. Each Call will identify itself as a one-step or two-step process. For individual calls, the Government intends to review resulting white papers/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.

2. Proposal Instructions:

a. General Instructions:

(1) 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.

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

(3) Proposals must reference the announcement number FA8650-19-S-1110 and relevant technical area(s) of interest.

(4) Offerors must submit one-original and 1 hard copies of their proposals to the Contracting POC.

(5) Offerors must include 2 CDs in Microsoft Office or Adobe format containing all electronic versions of required submittals. All electronic versions must match the hard copies. If there is a discrepancy between hard copies and electronic copies, the hard copies will take precedence.

a) The cost file(s) spreadsheets must be in Microsoft Excel and include the formulas for calculating cost element bases (i.e., G&A, O/H, etc.) b) The CDs should be labeled with the company name and proposal title.

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

(7) 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.

(8) 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 Solicited via Calls:

(1) 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 Statements of Work must be provided in Microsoft Word. Signed pages may be submitted in Adobe.

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.

(2) The Technical/Management proposal(s) shall include a discussion of the nature and scope of 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. This 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.

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

c. Cost/Business Proposal Solicited Via Calls:

(1) Separate the proposal into a business section and cost section. Adequate price competition is anticipated for each Call.

a) The Model Contract for FAR-based contracts is provided as the

Attachment to this document. No sample is provided for Other Transactions. Note that this Model Contract provides examples of clauses that may be included in final contracts, and it provides 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. Not all terms and conditions in the Model Contract are applicable to all Calls/contracts.

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) Identify any technical data that will be delivered with less than unlimited rights.

d) 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.

e) 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.

f) 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 Model Contract, attached to this document, and provide the completed Section K as part of the proposal package for each Call.

g) 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.

(2) 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’s (ACO's) 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 Sept) 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 (FPRA’s) and forward pricing rate recommendations (FPRR’s) should submit them with their proposal.

m) Cost/Business proposals have no page limitations.

d. 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. Proposal Peer or Scientific Review Criteria: Proposals will be reviewed against the criteria provided for each individual Call against the ARDIS ARA.

2. Cost/Price: Proposals will be reviewed against the criteria provided for each individual Call against the ARDIS ARA.

3. PROPOSAL – 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.

(1) Selectable: Proposals are recommended for acceptance if sufficient funding is available

(2) 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 white paper is recommended to submit a full technical and cost proposal on or about 30 days after receipt of the white paper. 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 Section I.

3. Reporting: See ARA Paragraph I.3.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. 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, 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.

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

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

6. 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 http://www.dol-esa.gov/preaward.

http://www.acq.osd.mil/dpap/pdi/uid/index.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.

7. Associate Contractor Agreements: Associate Contractor Agreements (ACAs) are agreements between contractors working on Government contracts that specify requirements for 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.

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

a. White papers/proposals are due to the Contracting POC.

b. White…