ARDIS CALL 2_DOS posting.pdf

Advanced Research Announcement (ARA)

FA8650-19-S-1110 Call 2

Database Optimization and Sustainment (DOS)

Overview Information

NAICS Code: No change to ARDIS ARA, See Overview, page 1 of 24 of ARDIS ARA.

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

ARA Title: Database Optimization and Sustainment (DOS) to Advanced Research Announcement (ARA) entitled, “Architecture Refinement, Demonstation and Integration Systems (ARDIS) Program.

ARA Type: This is the initial Announcement for Call 2.

ARA Number: FA8650-19-S-1110 Call 2

THIS IS A SOLICITATION FOR CALL 2. THIS SOLICITATION IS A ONE-STEP

CALL ISSUED UNDER Architecture Refinement, Demonstration and Integration Systems (ARDIS).

One Step: PROPOSAL DUE DATE AND TIME: 16 April 2020, 3:00 PM EST (Wright-Patterson AFB Time)

NOTE: Proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). Any Call proposal received at the Government Office designated in this ARA Call 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 above stated date and time 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 established herein. Early proposal submission is encouraged.

Submission: Proposals must be submitted to a Contracting Point of Contact (POC): (Primary) Jerry Brown, Contract Negotiator or (Alternate) Barry Kain, Contracting Officer, AFRL/RYKS, Bldg 45, 2130 8th St., Wright-Patterson AFB, OH 45433-7541. PLEASE NOTE: Submission and Receipt of Classified Proposals, to include any addendums, are not anticipated.

However, if an offeror determines the need to submit a classified proposal either in whole or in part, please contact the Contracting POC’s listed in this Call for approval to do so. If a classified submission either in whole or in part is approved, the offeror IS NOT to deliver any classified proposal submissions to the Contracting POC’s and Contracting location specified in this Call. Rather, delivery of any classified proposal submission will have to be arranged through the Technical POC listed in this Call i.e., Andrew Freeman.

Any classified proposal submittals either in whole or in part count against the Technical and Management Proposal and SOW page counts specified elsewhere in this call. In addition, offerors are reminded that they have to meet all proposal instructions in this call e.g., Delivery Date and Time.

Delivery info for classified submissions/addendums:.

Outer Label:

AFRL/RYZT Attn: Security 2241 Avionics Circle

WPAFB, OH 45433

Inner Label:

AFRL/RYZT Andrew Freeman 2241 Avionics Circle

WPAFB, OH 45433)

Solicitation Request: Air Force Research Laboratory, AFRL/RY Sensors Directorate, Wright-Patterson Air Force Base is soliciting proposals on the research effort described below.

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 awards under this Call 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 the full ARA announcement shall apply. The 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 an OT agreement should be developed and negotiated on a case-by-case basis.

Estimated Program Cost: The total estimated research program value for Call 2 is $19,497,000.00 with an anticipated technical effort of 60 months plus 3 months for final report.

Anticipated Number of Awards: The Air Force anticipates awarding up to three (3) contracts valued at $6.499M each as a result of 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. PLEASE NOTE: There are two (2) primary technical focus https://www.acquisition.gov/ areas specified in SOO paragraph 3 and as further discussed in SOO paragraph 4 that are valued at $6.499M each. If an offeror were selected to receive an award in each primary technical focus area, those focus area selected awards would be combined into one award.

Brief Program Summary: Air Force Research Laboratory, Sensors Directorate is soliciting technical and cost proposals under this announcement that support the needs of the Sensors Directorate. AFRL/RY is seeking to develop/adapt technologies that continue to advance database generation techniques and combat ID algorithms that can rapidly incorporate new target information for immediate use. DOS will have two primary technical focus areas: air target modeling and exploitation, and ground target modeling and exploitation.

Technologies to be explored include but are not limited to: on the fly model generation, limited knowledge/access model generation, hierarchical classifiers, out of library extension, synthetic signature prediction, and salient features. Improvements in these areas may involve and include technical assessments, prototype hardware and software modifications and development, systems engineering development, performance simulations, system integration, laboratory demonstrations, flight demonstrations, and participation in large demonstrations/exercises.

Communication Between Prospective Offerors and Government Representatives: No change from ARDIS ARA Overview. See page 3 of 24.

Address technical questions to the Technical POC: Andrew Freeman, 2241 Avionics Circle, WPAFB, OH 45433, 937-713-8158, andrew.freeman.6@us.af.mil

Address contracting questions to the Contracting POC: Barry E. Kain, Contracting Officer, AFRL/RYKS, 2130 Eighth Street, Area B, Bldg. 45, Wright- Patterson AFB, OH, 45433-7541, phone number: (937) 713-9986, e-mail address: barry.kain@us.af.mil or Jerry Brown, Contract Negotiator, AFRL/RYKSR, 2130 Eighth Street, Area B, Bldg. 45, Wright- Patterson AFB, OH 45433-7541, phone number: (937) 713-9985, e-mail address:

jerry.brown.16@us.af.mil.

Full Text Announcement

I. Program Description:

Air Force Research Laboratory, Sensors Directorate (AFRL/RY) will be soliciting technical and cost proposals for the following research effort:

1. Statement of Objectives (SOO) – See Attachment 1.

2. Within Scope Modifications: No change to ARDIS ARA. See ARDIS ARA Full Text Announcement. See page 9 of 24.

3. Deliverable Items:

a. Data Items: reference paragraph 6.0 - Deliverables of the SOO, Attachment 1, for applicable CDRLs. CDRLs are exhibit A of the ARDIS model contract.

b. Software: See SOO, paragraph 6.0 – Deliverables/Outputs.

c. Hardware: See SOO, paragraph 6.0 – Deliverables/Outputs.

mailto:jerry.brown.16@us.af.mil

4. Schedule:

60 months of technical effort plus 3 months for Final Report.

5. Other Requirements:

Program Security Classification: The Security Classification for DOS is Secret classification/safeguarding capability. A DD254 is attached to this DOS Call. Offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil.

a. Export Control: Information involved in this research effort is subject to Export

Control (International Traffic in Arms Regulation (ITAR) 22 CFR 120-131, or Export

Administration Regulations (EAR) 15 CFR 710-774). A Certified DD Form 2345, Militarily Critical Technical Data Agreement will be required to be submitted with proposal.

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

c. Safety: The following safety requirements will be incorporated into the award:

Must comply with all Air Force, federal, state and local safety and environmental regulations. Must comply with system safety requirements contained in MIL-STD 882E, Section 4 "Other Requirements" for any deliverable systems or hardware.

d. Contractor Performance Assessment Reporting System (CPARS): N/A

6. Other Information:

a. Government Furnished Property (GFP) Availability: None anticipated. GFP use may be considered if proposed and found to be in the best interest of the Government. 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.

Clauses referenced in the ARDIS ARA, Full Text Announcement, Section I, Program Description, Section 7, Other Information, subsection a are applicable. See page 11 of 24.

b. Base Support – None anticipated.

c. Data Rights – Unlimited rights for technical data, non-commercial software (NCS) and NCS documentation are desired by the Government. For commercial computer software, customary license rights are desired by the Government.

Offerors shall include their data rights assertions within Section K’s DFARS Provision 252.227-7017, Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer http://www.dss.mil/

Software. If an offeror wishes to take exceptions to the Government desired rights, the offeror should include with its proposal submission as part of the Section K, what rights are proposed to be furnished to the Government. Those exceptions may be subject to further negotiations prior to any contract award. See ARDIS ARA, Section I, Program Description. Section 7, subsection C. For additional info and details on data rights, see pages 11-13 of 24 of ARDIS ARA.

II. Award Information:

1. Anticipated Award Date: 31 July 2020

2. Anticipated funding

FY 20 21 22 23 24 25 Total For Each Award

$1.0M $1.0M $1.33M $1.33M $1.33M $0.5M $6.499M

*This funding profile is an estimate only and not a contractual obligation for funding. All funding is subject to change due to Government discretion and availability. Potential offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.

III. Eligibility Information:

1. Eligible Offeror: No change to ARDIS ARA Section III.1. See page 13 of 24.

2. Cost Sharing or Matching: No change to ARDIS ARA Section III.2. See page 13 of 24.

3. Federally Funded Research and Development Centers: No change to ARDIS ARA Section III.3. See page 14 of 24.

4. Government Agencies: No change to ARDIS ARA Section III.4. See page 14 of 24.

5. Other:

a. Foreign Participation: Foreign Participation is not authorized at the Prime contractor level based on restrictions listed in AFMC Form 191. DoD solicitation provisions for 22 CFR Parts 120-130 and 15 CFR Parts 730-799 apply. Only U.S. persons are eligible for award. Use of non U.S. persons by the contractor, including subcontract arrangements, are subject to aforementioned statutes. 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 involves data that is subject to export control laws and regulations. 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.

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

IV. Proposal and Submission Information:

1. Proposal Instructions:

a. General Instructions:

(1) Offerors will submit a technical and cost proposal within 30 working days of the DOS proposal request is issued. After receipt, proposals will be reviewed in accordance with the award criteria in Section V. below.

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 Call

2 and relevant technical focus area(s).

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

b. Technical/Management Proposal:

(1) Page Limitations: The following describes proposal page limitations:

a) The Technical/Management Proposal shall be limited to 20 pages for each of the two Primary Technical Focus Areas listed in the SOO paragraph 3. If an offeror elects to submit a Technical and Management Proposal for both Primary Technical Focus Areas listed in SOO Paragraph 3., the proposal page limitation is a total of 40 combined i.e., 20 pages for each focus area. Technical/Management proposals and Statements of Work must be provided in Microsoft Word. Signed pages may be submitted in Adobe. PLEASE NOTE: An offeror is only required to submit a technical/management proposal for one (1), not both of the two primary technical focus areas discussed under SOO paragraph 3. Primary objectives, and as further discussed and detailed under SOO paragraph 4. Specific technical objectives, which apply to both primary technical focus areas.

However, an offeror may submit a technical/management proposal for both primary technical focus areas. Each primary technical focus area is valued at $6.499M each.

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 20 if only submitting a proposal for one of the primary technical focus areas specified in SOO Paragraph 3 or no greater than Page 40 if submitting a proposal for both primary technical focus areas specified in SOO Paragraph 3. 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 6 pages if only submitting a proposal for one of the primary technical focus areas specified in SOO Paragraph 3 or limited to 12 pages if submitting a proposal for both primary technical focus areas specified in SOO Paragraph 3.

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

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

a) 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 announcement, any information not technically related, etc. Provide rationale for exceptions.

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

c) Subcontracting Plans: For efforts to exceed $700,000, Subcontracting Plans shall be submitted in the cost/business proposal. Reference FAR

19.704 and DFARS 219.704 for subcontracting plan requirements. Small business concerns are exempt from this requirement.

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

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

f) If an offeror proposes the use of Government Furnished Property (GFP), other than GFP identified in this Call, the offeror 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: PLEASE NOTE: Each of the two primary technical focus areas discussed in SOO paragraph 3 are valued at $6.499M each. 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. Supporting documentation should also include past or current Government prime or subcontracts where the direct and indirect rates proposed under DOS are the same or similar to what is being proposed under DOS. Please provide Government points of contact (POC’s) for those contracts and subcontracts. 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.

n) 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 listed below. The technical aspect, which is ranked as the first order of priority, shall be reviewed based on the following criteria that are of equal order of importance.

i. Technical:

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

(2) The offeror’s understanding of the scope of the technical effort.

(3) Soundness of the offeror’s technical approach including whether the proposal identifies major technical risks, clearly defines feasible mitigation efforts, and demonstrates recent and relevant experience and qualifications of technical personnel.

(4) The potential to transition the research and development deliverables to future Government needs. Any proposed restriction on technical data or computer software will be considered.

ii. 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 Call, 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. 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:

Award Notices: Offerors will be notified whether their proposal is recommended for award on or about 45 days after receipt of the proposal. The notification is not to be construed to mean the award of a contract or agreement 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 Contract Data Requirements Lists (CDRLs) attached to DOS Call 2.

VII. Other Information: There are no changes to ARDIS ARA section VII, subsections 1,2,3,4, 5,6, and 7. See pages 22 and 23 of the ARDIS ARA. The following are applicable to this DOS call.

1. Wide Area Work Flow: NOTICE: Any contract award resulting from this solicitation will contain the clause at DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports (DEC 2018) which requires electronic submission of all payment requests. Any contract resulting from this solicitation will establish a requirement to use WAWF-RA for invoicing and receipt/acceptance, and provide coding instructions applicable to this contract via the clause at DFARS 252.232-7006, Wide Area Workflow Payment Instructions (DEC 2018). Contractors are encouraged to take advantage of available training (both web-based and through your local DCMA office), and to register in the WAWF-RA system. Information regarding WAWF-RA, including the web-based training and registration, can be found at https://wawf.eb.mil. Note: This WAWF-RA requirement does not apply to Universities that are audited by an agency other than DCAA.

2. Limitations on Pass-Through Charges. As prescribed in FAR 15.408(n)(1) & 15.408(n)(2), provision 52.215-22, Limitations on Pass Through Charges – Identification of Subcontract Effort (OCT 2009), and clause 52.215-23, Limitations on Pass-Through Charges (OCT 2009), are contained in this solicitation by reference. Any contract valued greater than the threshold for cost or pricing data threshold, except fixed price contracts awarded on the basis of adequate price competition, resulting from this solicitation, shall contain the Clause at FAR 52.215-23 (or Alt I).

3. Post-Award Small Business Program Rerepresentation: As prescribed in FAR 19.309(d), FAR Clause 52.219-28, Post-Award Small Business Program Rerepresentation (JUL 2013), is incorporated by reference in this solicitation. This clause will be contained in any contracts resulting from this solicitation. This clause requires a contractor to rerepresent its size status when certain conditions apply. The clause provides detail on when the rerepresentation must be complete and what the contractor must do when a rerepresentation is required.

4. Employment Eligibility Verification: As prescribed by FAR 22.1803, FAR Clause 52.222-54, Employment Eligibility Verification (OCT 2015), is hereby incorporated by reference in this solicitation. Any contract awarded as a result of this ARA that is above the Simplified Acquisition Threshold, and contains a period of performance greater than 120 days, shall include this clause in its contract. This clause provides the requirement of contractors to enroll as a Federal Contractor in the E-Verify program within 30 days after contract award.

5. Reporting Executive Compensation and First-Tier Sub-contract/Sub- recipient Awards: Any contract valued at $30,000 or more, excluding classified contracts or contractors with individuals, must contain FAR 52.204-10, Reporting Executive Compensation and First-Tier Subcontract Awards (JUL 2013).

6. Updates of Publicly Available Information Regarding Responsibility Matters: Any contract or agreement award that exceeds $550,000; and when 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 (OCT 2018).”

7. Accelerated Payment to Small Business Subcontractors: As prescribed in FAR 32.009-2, FAR 52.232-40, Providing Accelerated Payments to Small Business Subcontractors (DEC 2013), is hereby incorporated by reference.

8. Terms of Service, Open-Ended Indemnification and Unenforceability of Unauthorized Obligations: As prescribed in FAR 32.706-3, FAR 52.232-39, Unenforceability of Unauthorized Obligations (JUN 2013), is hereby incorporated by reference.

9. Whistleblower Protections: As prescribed in DFARS 203.970, DFARS 252.203- 7002, Requirement to Inform Employees of Whistleblower Rights (SEP 2013), is hereby incorporated by reference.

10. Contractor Business Systems: As prescribed in DFARS 242.7001, DFARS 252.242-7005, Contractor Business Systems (FEB 2012), is hereby incorporated by reference. This clause does not apply to contracts or agreements with educational institutions, Federally Funded Research and Development Centers (FFRDCs), or University Affiliated Research Centers (UARCs).

11. Safeguarding of Unclassified Controlled Technical Information: As prescribed in DFARS 204.7303, DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (DEC 2019), is hereby incorporated by reference.

12. Ombudsman: As prescribed in 5301.9103, The Ombudsman clause, AFFARS 5352.201-9101 Ombudsman (OCT 2019) will be contained in any contracts or agreements resulting from a Call for Proposals. The AFRL Ombudsman is Rosalind Harper the Director of Contracting, AFRL/PK, (937) 904-9700, email: rosalind.harper@us.af.mil.

13. Proposal Reminders: 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 this announcement.

c. Proposal page limits are strictly enforced.

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

e. Offerors other than small businesses must include a subcontracting plan.

f. Proposals must be submitted in the format specified.

g. Offerors who have Forward Pricing Rate Agreements (FPRA’s) or Forward

Pricing Rate Recommendations (FPRR’s) should submit them with their proposal.

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

i. If effort is subject to export control, offerors must submit a Certified DD

Form 2345, Militarily Critical Technical Data Agreement, with proposal.

mailto:rosalind.harper@us.af.mil http://www.dss.mil/

ATTACHMENT:

NOTE: ARDIS ARA attachment model contract is hereby referenced for this call.

1 – DOS Statement of Objectives

2 - DD254 Contract Security Classification Specification for FA8650-19-S-1110 CALL 2, DOS

3 – Government Furnished Information (GFI)

4 – Contract Data Requirements List (CDRL)

5 - Section K (Local Certs and Reps)P

Database Optimization & Sustainment (DOS)

STATEMENT OF OBJECTIVES

FA8650-19-S-1110 Call 2

Attachment 1

1. BACKGROUND

On the battlefield situational awareness is critical to making good decisions. Threats come in various sizes, shapes, colors, and materials and can sometimes change in very short periods of time. The Air Force needs to be able to incorporate known threats as well as new and emerging ones into their target databases as soon as they come available.

Unfortunately current database updates tend to only happen every few years when a major software update is performed. This process is far too slow when a new target model can be ready in a couple of days or less.

Most ATR algorithms are data-driven, requiring extensive testing to train, validate, and characterize performance. These algorithms may break down when new targets, backgrounds, or operating conditions are introduced. These systems have long logistic tails and proprietary issues when it comes to improvements, updates, and maintenance.

This inherently makes it difficult, time consuming and costly to taxpayers for cradle-to-grave combat identification (CID) weapon systems.

Several aircraft are in the process of upgrading their sensor hardware with high speed connectivity between the sensors and aircraft computer systems. This new architecture presents USAF weapons system teams with unique opportunities to migrate CID databases out of their platforms sensor suite and into another aircraft computer/avionics component which can be quickly updated via the aircraft data transfer device (DTD).

The U.S. Air Force is interested in developing algorithms and databases which can readily adapt to new emerging threats. This database optimization & sustainment (DOS) research program seeks database methods to quickly incorporate new targets based on the latest intelligence community analysis of threat system characteristics/capabilities.

We are also interested in algorithms that have a way to characterize new unknown targets in the air and ground domains. Previous work in these areas include the Compact

Automatic target recognition for the Sustainable Environment (CASE), Air to Air

Hydravision (AAHV), and Air to Ground Hydravision (AGHV) programs.

The US Air Force Research Laboratory’s CID program is chartered to develop and mature cooperative and non-cooperative combat ID technologies. These technologies are designed to enable successful mission execution of US Air Force aircraft and spacecraft, but have potential applicability to other platforms. The program’s charter encompasses activities including the following:

- Cooperative and non-cooperative systems

- Radar, IR, EO, and multi/hyperspectral sensors

- Single sensor/single mode to multi-sensor/multi-mode

- Sensor architectures enabling the modes to adapt to feature availability

The CID program focuses on exploiting features derived from these activities that reveal target characteristics; or developing specific sensor operating modes designed to highlight specific ID features.

Representative technologies developed by the Sensors Directorate include those that increase situational awareness, improve target detection, enhance precision targeting, increase survivability, and improve information processing. The CID program focuses on exploiting features derived from these activities that reveal target characteristics; or developing unique sensor operating modes designed to highlight ID features of targets.

2. SCOPE

The scope of this effort is research that includes Advanced Technology Development through Demonstration specifically for combat identification. Technology Readiness

Level (TRL) at the commencement of the research effort will be at a minimum 3 but preferred to be 4. Expected and Anticipated TRL at the completion of the research effort will be 5. O&M funded work may be added via an in scope modification to demonstrate the R&D in a real world environment and on an operational platform. Procurement funded work may be added via an in-scope modification to aid transition from lab to production unit/system(s).

3. PRIMARY OBJECTIVE

This DOS research program seeks to develop/adapt technologies that continue to advance database generation techniques and combat ID algorithms that can rapidly incorporate new target information for immediate use. DOS will have two primary technical focus areas: air target modeling and exploitation, and ground target modeling and exploitation. Technologies to be explored include but are not limited to: on the fly model generation, limited knowledge/access model generation, hierarchical classifiers, out of library extension, synthetic signature prediction, and salient features.

Improvements in these areas may involve and include technical assessments, prototype hardware and software modifications and development, systems engineering development, performance simulations, system integration, laboratory demonstrations, flight demonstrations, and participation in large demonstrations/exercises.

A significant focus of this effort will be developing/adapting modeling techniques for air and ground targets across multiple phenomenologies and generating the necessary databases. The availability of multiple sensors onboard a single platform is growing but a lack of coincident data has hampered development of multi-sensor fusion. As model generation matures the focus will shift towards algorithm development. The algorithms should be capable of high confidence identification with limited need for retraining by subject matter experts (SME) when new targets are introduced to the database. The algorithms are expected to be able to retrieve a mission load/update by way of a DTD rather than a full operational flight program (OFP) update. As operational hardware may not be available for demonstration of this update process surrogate hardware can be used.

Database and algorithm development will take place up to TRL 5 during the performance of this contract. Once proven in a laboratory setting the contractor is expected to support the integration and demonstration in an operationally relevant platform/surrogate showing TRL 6 can be executed. This will include all aspects of flight test planning, preparation, and execution. This includes, but is not limited to, a test readiness review

(TRR) and support of all Government-sponsored flight test meetings and processes such as safety review board (SRB) and technical review board (TRB). Following the flight test, the results and lessons learned will be documented and reported in a test report.

Synthetic or real data may be used to aid design and development. Government furnished data relevant to this effort may be provided at the discretion of the program manager (PM) and the agency controlling the data. However any selected contractor should not depend on access to this data as it may not yet exist or be at a higher classification level than intended for this effort. Processing of classified data is anticipated up to the SECRET level.

Multiple laboratory demonstrations are anticipated to show technical progress and verify system maturity. The technology developed will follow a disciplined systems engineering approach, including Preliminary Design Review (PDR), Critical Design

Review (CDR), quarterly technical reviews, documentation of system design, and lab demonstrations. At the conclusion of development and testing everything must be detailed in the final report.

The contract will be a 60 month effort, plus 3 months for completion/submission of a final report. As mentioned in the scope above the government may decide upon an in-scope add work to aid the integration, demonstration, and transition from the lab to an operational platform. If an add work is executed delivery of the final report will be deferred until completion of the add work.

Throughout the effort, a disciplined, validated and efficient capability to exercise, analyze, and evaluate solutions for CID of targets will be maintained.

4. SPECIFIC TECHNICAL OBJECTIVES: APPLIES TO BOTH TECHNICAL

FOCUS AREAS

4.1. Prototype Software/Algorithm Development. Develop rapid database and modeling techniques, develop signal processing techniques, develop and apply automatic target recognition algorithms, and generate software that enables the sensor suite to identify air and/or ground targets. Incorporate a method for updating database without needing subject matter expert (SME) support.

Investigate advanced waveforms that will exploit target features.

Software/algorithms developed should follow Open Mission Systems (OMS) guidance so as to be transferrable to multiple platforms

4.2. Hardware Development. NOTE: This program will NOT perform major hardware development activities. Objectives do include: Modifying existing sensors for the purpose of providing enhanced CID capability and interfacing with aircraft

DTDs. Modifications are anticipated to be software/firmware only to generate a desired input/output.

4.3. Performance Analysis. Model the capabilities of the technology developed

(hardware and/or software). The modeling will be used to evaluate standalone technology performance improvements; performance improvements/impact to other subsystem components; performance improvements/impact to the system for which the technology is part of; or mission-level performance improvements attributed to the technology. Conduct analyses to accomplish risk reduction goals with the appropriate hardware, software, and/or level of operator interaction as required. Conduct other trade studies to further analyze key technology factors.

4.4. Ground Demonstrations/Tests. Evaluate the developed technologies at the completion of a development milestone to demonstrate how requirements are being met. TRL may be proven up to Level 5 using ground based hardware/software.

4.5. Evaluations. Develop technology or capability evaluation criteria for the technology or capabilities developed and coordinate with the Government. This includes criteria for data collections, hardware/software testing, and field/flight testing.

4.6. Other Test Objectives. Conduct all required elements of ground and flight test planning, instrumentation, coordination, test conduct, signature collection, data reduction, and performance assessment.

4.6.1. Provide materials (i.e. portable hard drives, remote/contact sensors) to collect, store, and retrieve CID technology signatures as well as air truth and ground truth information.

4.6.2. Identify and coordinate availability of test ranges and test targets as included in test planning, resource and funding commitments, and completion of demonstration/test objectives. Flight/ground testing requirements may involve the use of contractor-owned/operated or government owned/operated assets.

4.6.3. Accomplish evaluations of the technology with respect to meeting specified mission objectives and requirements.

4.7. Flight Demonstrations/Tests. Upon successful completion of a TRL 5 demonstration provide technical expertise and support for integration and testing on operationally relevant hardware (i.e. test aircraft).

4.8. System Maturation. Perform system transition activities.

4.8.1. RESERVED O&M objectives related to system maturation and transition may be added via a future in-scope contract modification.

4.8.2. RESERVED Procurement objectives to aid transition from lab to production unit/system(s) may be added via a future in-scope contract modification.

5. MANAGEMENT OBJECTIVES

5.1. Management objectives include maintaining clear government visibility into program schedule, performance, and risk while allowing the contractor maximum flexibility and innovation to manage the effort. This would include program schedule, cost, performance, risks, associate contractor agreements, subcontracts and data to meet contract objectives that satisfies all technical requirements.

5.2. Attend and Conduct Meetings. Host a post-award conference at the selected contractor facility within 30 days of contract award. Conduct program management reviews and technical interchange meetings. Develop agendas for all meetings jointly with the government.

5.3. Systems Engineering. Incorporate a disciplined systems engineering approach tailored to meet the Program and Contract Objectives to provide an integrated development program.

5.4. Training. Conduct training for the customers and users of the technology to effectively use the capabilities of the technology, including pilot-vehicle interfaces (PVI).

5.5. Flight Test, Field Test and Data Collection. Test plan preparation to support technical and safety reviews, system safety and hazard identification, and flight or field test certification will be required. Participation in mishap investigations as required. Provide all air worthiness certifications for test hardware and associated systems prior to flight testing.

5.6. Sustainment and Logistics Planning.

Provide planning for the management of software and hardware items relative to life cycle costs, database sustainment, spiral upgrade integration procedures, maintenance and configuration management, training, documentation, facilities requirements, staffing, and other factors is critical to transitioning onto various platforms.

6. DELIVERABLES/OUTPUTS

- See CDRL’s, Exhibit A (Attachment X) of the Model contract attached to this

Call.

As part of the technical and management objectives, provided above, the selected contactor shall deliver prototype hardware, software, and materials as follows:

Prototype Hardware: Deliver any developed and/or any modified hardware, to include data transfer devices, during the course of the effort.

Prototype Software: Deliver any developed and/or any modified software, to include computer software or databases, during the course of the effort.

Materials: Deliver and procure materials, to include portable hard drives and test equipment, to accomplish objectives outlined in this SOO.

7. OPSEC

General Operations Security (OPSEC) procedures, policies and awareness are required in an effort to…