FA8684-20-S-C001 - Call 0010 Amendment 01.pdf

Page | 1

Rapid Sustainment Office (RSO) Commercial Solutions Opening (CSO) Call 0010 Proposal Instructions for Request for Proposal

1.0 INTRODUCTION

These proposal instructions provide specific guidelines for submitting a proposal for evaluation and potential award. The Offeror must ensure its proposal meets all requirements of these proposal instructions.

The Air Force Life Cycle Management Center Rapid Sustainment Office (RSO) specializes in identifying new and disruptive technologies, applying them to real-world Air Force sustainment challenges, and scaling best of breed capabilities across the enterprise. The RSO approach is characterized by three distinct but overlapping phases: Identify, Apply, and Scale. Each phase represents an increase in investment and maturity as successful projects continue and underperforming projects are allowed to end. Conceptually, this process is like a funnel that is continuously filled during the Identify phase and iteratively filters down, as best of breed technology solutions are developed and delivered at Scale to the sustainment and logistics enterprise.

The Department of the Air Force established the Advanced Manufacturing Program Office (AMPO) within the RSO to scale organic capability. Advanced Manufacturing is targeting cost-effective manufacturing processes such as Additive Manufacturing, Cold Spray, and Reverse Engineering to address supply chain and mission readiness challenges. This solicitation seeks an innovative methodology to mature technology solutions and/or materials, mitigate risk and produce fieldable results aiding in the scale of the organic capability.

It is important to note, that the Government is not obligated to make any award as a result of these proposal instructions and all awards are subject to the availability of funds and successful

Federal Agency: Air Force Program Office: AFLCMC/RO “AM Program Office” Call Number: FA8684-20-S-C001, Amendment 01: Call 0010

Amendment 01 Call Title: Additive Manufacturing w/Integrated Digital

Engineering NAICS: 333249 - All Other Industrial Machinery Manufacturing Call Type: One-Step, Closed Call Call Release Date September 26, 2022 RFP Release Date:

Call 0010 Amendment 01 Release Date:

September 26, 2022

October 25, 2022

Proposal Due Date: November 18, 2022, at 5:00 PM EDT

Page | 2 negotiations. The Government is not responsible for any monies expended by the Offeror prior to the issuance of a contract award.

The RSO reserves the right to modify any of the proposal requirements and/or proposal instructions at any time.

If any conflicting information occurs between this RFP and the overarching solicitation document (FA8684-20-S-C001, Amendment 01), this RFP shall take precedence. However, for information not specified or contained in this RFP, then the information in the overarching solicitation may still apply. Each Offeror is responsible for reviewing each document in its entirety.

2.0 FRAMEWORK FOR EVALUATION & AWARD

Section 2.0 describes the methodology for evaluating the proposal and the subsequent contract award, should an award be made.

2.1 Evaluation Criteria

The Offeror’s proposed solution for an innovative methodology to mature technology solutions and prepare them to Scale will be evaluated using the following criteria:

Technical:

o The soundness and technical merit of the proposed solution to adequately address the RSO's stated Areas of Interest (AoI) need(s) that relate directly to the Technology Focus Areas.

o The demonstrated feasibility of the proposed solution to address the AoI is mid-maturity (i.e. objectives are 5 or greater for TRL, MRL, SRL, but disruptive technologies are exceptions)

Importance to Agency Programs/Commercial Innovation: The degree to which the proposed concept provides an innovative, unique and/or previously under-utilized capability for government application

Funds Availability Price: Price shall be considered to the extent appropriate, but at a minimum, to determine that the price is fair and reasonable.

Technical reviewers will base their conclusions only on information contained in the written proposal. It cannot be assumed that reviewers are acquainted with the Offeror or any information regarding the Offeror not contained in the proposal. Relevant supporting data such as journal articles, literature, including Government publications, etc., may be included or referenced in the proposal.

Proposed solutions shall be evaluated based on the merit of the Offeror’s proposed innovative solution, not against other proposed solutions of other Offerors.

Page | 3

2.2 Evaluation of Proposed Lines of Effort

A. Section 3.0, Statement of Objectives, describes two specific Lines of Effort (LOE).

Additional information as to the anticipated scope, tasks, and desired deliverables are also provided in detail.

Each Line of Effort shall be evaluated independent of the other.

This means that the evaluators will use the criteria listed in Section 2.1 to evaluate LOE One, Rapid Comparison Analysis, and reach a conclusion solely as to LOE One. The evaluators will then use the criteria listed in Section 2.1 to evaluate LOE Two, Research and Development – Jet Engine and Aircraft Heat Exchangers, and reach a conclusion solely as to LOE Two.

The proposal instructions are designed to allow for the Offeror to compose a proposal submission that allows for each LOE to be evaluated independent of each other.

2.3 Impact of Evaluation Approach on Contract Award

The independent evaluation of each LOE has the following impacts on the potential contract award:

A. The RSO reserves the right to award a contract for all, part, or none of the LOEs described in

Section 3.0.

B. The RSO reserves the right to award a contract to one, some, or none of the Offerors.

C. The RSO reserves the right to select one Offeror to perform both LOEs, or to award one LOE to two or more Offerors. This could result in two Offerors receiving a contract for only one LOE each, or it could result in one Offeror receiving a contract that includes two LOEs.

D. Each Offeror shall propose a solution for one LOE or both LOEs for the proposal to be considered adequate and eligible for evaluation by the RSO.

2.4 Contract Type and Period of Performance

Regardless of whether there is one or more than one contract award, if an award is made the resulting contract award(s) shall be FAR 12, Firm Fixed-Price.

The contract(s), if awarded, shall have a 18 month period of performance for each LOE. If more than one LOE is awarded to one offeror the LOEs shall be executed concurrently. The period of performance shall start the date of contract award and shall conclude 18 months after contract award.

3.0 STATEMENT OF OBJECTIVES

The implementation of this effort will enhance the delivery of capabilities to the Department of the Air Force (DAF) and will be shared with the Military Departments (MILDEPs) as a potential common solution.

Page | 4

3.1 Lines of Effort:

The scope of this effort includes Rapid Comparison Analysis, and Research and Development – Jet Engine and Aircraft Heat Exchangers. As stated in Section 2.0 the anticipated scope is reflected in two LOEs. Each are described herein:

A. Line of Effort One: Rapid Comparison Analysis Rapid Comparison Analysis - the project goals are to develop sustainment pathways using lessons learned from other airframes such as C-5 to scale Additive Manufacturing (AM) applications to other aircraft platforms such as KC-135, B-52, B-1, and E-3.

1) Develop standard characteristics and use cases for polymer and metal printed parts that are approved or are in the approval processes.

2) Deliver an innovative solution that will assist with development of an organic additive manufacturing capability utilizing commercial airworthiness certified printing processes, methods, and procedures allowing full use of developed material processing information and repeatability as required.

3) Perform analysis of Oklahoma City-Air Logistics Complex (OC-ALC) managed aircraft listed above and deliver a list of comparable items from additive manufacturing processes that could reduce Diminishing Manufacturing Sources and Material Shortages (DMSMS) and reduce lead-time on parts with obsolescence issues.

B. Line of Effort Two: Research and Development – Jet Engine and Aircraft Heat

Exchangers Research and Development (R&D) - Jet Engine & Aircraft Heat Exchangers (HE), conduct research and select an AM printer/material combination with sufficient supporting information such as mechanical and physical property data, geometry capabilities, and post build processing requirements to design, develop and prototype an AM HE.

1) Assess multiple types of HEs and develop analysis supported by modeling and simulation for AF review and selection.

2) Develop technical data package(s), manufacturing and production plans for a prototype heat exchanger

3) Develop prototypes addressing airworthiness consideration required by USAF

Cognizant Engineering Authorities.

4) Demonstrate the ability to verify that no loose or partially sintered powder remains in the HE.

5) Demonstrate HE capability to hold required pressures and meet leak rate and other performance requirements.

Page | 5

6) Validate HE performance predictions of Section 3.1.B.1 on printed heat exchanger.

3.2 Anticipated Tasks for LOE One

The following objectives and tasks shall be met during the contract period of performance:

A. A report of commercial products, qualification levels, and materials used in additive manufacturing as a substitute for parts with an airworthiness consideration.

A001 (DI-MISC-80048, Scientific and Technical Reports Summary)

B. A report/product with use cases identifying and comparing supply chain remedies/cost saving that can be applied to KC-135, B-52, B-1 and E-3 airframes based on delivered TDP content and DAF material/printers.

3.3 Anticipated Tasks for LOE Two

The following objectives and tasks shall be met during the contract period of performance:

A. Associated Material/Printer specification used in HE prototyping B. Industry specification(s) as available C. AM based Design allowables as required for HEs D. Report outlining business case and ROI E. Report outlining the HE replacement boundaries (size, shape, materials, operating characteristics i.e. mode of heat transfer, flow regime, etc) of this effort F. Develop, test, and deliver a functional AM prototype heat exchanger comparable to those used in common engine and airframe applications and all associated manufacturing, inspection, testing, materials, and Model-based definition (MBD) technical data packages

3.4 Technical Environment Information and Assumptions

The Offeror shall use the following information and assumptions regarding the technical environment. The information in subsection 3.4 should be used to inform LOE One and LOE Two, as applicable.

The Contractor will be required to access DoD systems, these may include, but are not limited to:

a. Integrated Maintenance Data System (IMDS) - Air Force system for consolidation of current and historical maintenance data currently stored in other data systems

b. Integrated Logistics Supply System (ILSS) - Functions as the avenue to capture supply logistics activity (e.g., part request, status, and inventory)

c. Enhanced Technical Information Management System (ETIMS)

d. Joint Engineering Data Management Information and Control System (JEDMICS)

e. FLIS Data Files

In addition to the above, the Contractor may request access to additional information. Non-disclosure agreements or other formalized procedures related to data sharing may be required prior to sharing certain Air Force or RSO project data with the successful Offeror depending on sensitivity of the data and arrangements with RSO technology providers.

Page | 6

3.5 Program Management Information and Assumptions

The information in subsection 3.5 should be used to inform LOE One and LOE Two, as applicable.

The successful Offeror shall execute program management responsibilities. The Offeror shall plan to execute a project kickoff no later than 14 days after contract award at a Government facility, and two Program Management Reviews (PMRs). The first PMR shall be held no more than 180 days after contract award. Locations of the PMRs shall be split between a Government and a successful Offeror location. In addition, the Offeror shall plan to support recurring and ad hoc technical interchange meetings, site visits, test events, planning activities, capability releases, and other engagements at Government and successful Offeror facilities as required.

Each Offeror is advised that in the event that more than one contract award is made, the RSO expects that a kickoff meeting and PMRs will be attended by each successful Offeror per contract. Any assumption made by the Offeror contrary to this shall be clearly articulated as a term/condition in the Offeror’s proposal.

The successful Offeror shall submit a Quarterly Report that provides program status progress for the subsequent 3-month reporting period. The report shall include progress made, any results obtained, any problem areas, and plans for activities during the next reporting period. Also include an Integrated Master Schedule that tracks project progress.

The Offeror shall deliver a Contract Summary Report. The Contract Summary Report shall be a project summary, identifying the purpose of the work, providing a brief description of the effort accomplished. It shall contain, but is not limited to the following: project objectives met, work completed, results obtained, and technical feasibility estimates. The report shall incorporate any corrections, requested edits, and/or changes identified during the Government’s review.

A002, DI-ADMN-81249B, Conference Agenda A003, DI-ADMN-81373, Presentation Material A004, DI-ADMN-81250C, Conference Minutes A005, DI-ADMN-80447A, Contract Summary Report A006, DI-ADMN-80555A, Program Progress Report

3.6 Information Security Information and Assumptions

The information in subsection 3.6 should be used to inform LOE One and LOE Two, as applicable.

The successful Offeror shall ensure External Certificate Authority (ECA) digital certificates is obtained by all contractor/sub-contractor personnel who require access to DoD computer networks/systems to perform tasks under the contract.

The successful Offeror shall ensure a Common Access Card (CAC) is obtained by all contractor/sub-contractor personnel who require access to DoD computer networks/systems and DoD installations to perform tasks under the contract. The successful Offeror shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The successful Offeror shall provide a list of Contractor (and/or subcontractor) personnel who require a CAC and other

Page | 7 related artifacts to support the investigation(s). The successful Offeror shall assume that all related artifacts and supporting documentation required as part of this scope be due to the Government within 90 days after any resulting contract.

An authorized user for the purposes of FAR 52.204-21 Basic Safeguarding of Covered Contractor Information Systems (Jun 2016) is limited to U.S. Citizens. The successful Offeror shall ensure non-US Citizens are not given access to data.

Additionally, the successful Offeror shall comply with Air Force standards for storing, processing, marking, and handling unclassified and/or Controlled Unclassified Information (CUI) and systems (see FAR 52.204-21, DFARS Provision 252.204-7008, and DFARS 252.204- 7012). Additionally, all resources (e.g. publication/instructions) provided by the Government to assist the successful Offeror in the performance of their contract shall be surrendered at the end of contract performance or upon Government request.

Finally, the successful Offeror shall exhibit and support the capability to deliver a Program Protection Implementation Plan (PPIP) and integrate the PPIP activities in IMS. The successful Offeror shall derive requirements from the PPIP and put into specification(s), trace, and verify through the Systems Engineering Processes. Program Protection includes the following areas:

Cybersecurity to include Trusted Systems and Networks (TSN), Cyber Resiliency, Anti-Tamper, and Information Protection.

All paragraphs below shall be contained in the PPIP. The government shall be able to participate in all testing. In addition, the successful Offeror shall allow the Government time in the laboratories and with the weapon system to conduct Penetration testing. The Offeror shall conduct its own penetration testing and provide the test plan, procedures and reports.

The successful Offeror shall perform a Program Protection / System Security Risk Assessment of the requirements per section 1.10 Risk Management of the USAF System Security Engineering Acquisition Guidebook, utilizing the System Security Working Groups. These risks shall be part of the program risks. In addition, the contractor shall provide courses of action with cost details to mitigate all risks to program office accepted risk level.

The successful Offeror shall report Cyber incidents (for all sections in the SOO/SOW) to the government IAW DFAR Clause 252.204-7012 (Safeguarding Covered Defense Information and Cyber Incident Reporting) via CDRL/DID and to the Defense Cyber Crime Center (DC3) via the DIBNet. In addition, provide a root-cause, corrective-action report. The successful Offeror shall establish and maintain an incident response infrastructure with identified membership and operating procedures to facilitate rapid response to cybersecurity incidents as documented in the Security Plan/Security Assessment Plan.

The successful Offeror shall participate in the government-led IPTs or government-led System Security Working Group (SSWG) [Quarterly, Monthly, 60 days prior to any System Engineering Technical Review (SETR), etc.] to provide technical input to the Government’s program protection planning and SSE activities.

Page | 8

The successful Offeror shall perform an Attack Path Analysis. The Offeror shall identify and analyze the cyber-attack surface by listing any hardware, software, connection, data exchange, service, removable media, or any other system attribute that may expose it to exploitation to determine likely avenues of cyber-attack. The Offeror shall perform a covert channel analysis to identify those aspects of communications within the weapon system that are potential avenues for covert storage and/or timing channels.

3.7 Operational Security Information and Assumptions (OPSEC)

The information in subsection 3.7 should be used to inform LOE One and LOE Two, as applicable.

The successful Offeror shall ensure OPSEC is incorporated into the appropriate area of the contract IAW DoD Directive 5205.02E, DoD Operations Security (OPSEC) Program and AFI 10-701 Air Force OPSEC Program, to include protection of Critical Information (CI). CI is defined as specific facts about friendly intentions, capabilities, or activities needed by adversaries to plan and act effectively against friendly mission accomplishment.

3.8 Personnel Security

The information in subsection 3.8 should be used to inform LOE One and LOE Two, as applicable.

The successful Offeror shall ensure applicable successful Offeror personnel have security clearances at the appropriate level for proper accomplishment of contract/order requirements.

The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. Successful Offeror personnel whose clearances have been suspended or revoked shall immediately be denied access to classified information and/or CUI and classified items.

IT level positions are defined in DoDM5200.02_AFMAN16-1405, Procedures for the DoD Personnel Security Program (PSP)/Air Force Personnel Security 16-1405, Section 3. Some IT systems may require IT-Level I and IT-Level II positions which require T5 and T3 investigations. Some performance of duties, which do not require IT-Levels I or II access, only require a favorably completed Personnel Security Investigation also known as a trustworthiness determination; they do not result in clearance eligibility and are known as a Tier-1 (T1). The Tier-5 (T5) and Tier-3 (T3) investigations are submitted through the contractor’s FSO as authorized by a DD-254. The T1 investigations are submitted through the government Security Manager.

For successful Offeror personnel whom will require military installation access and/or privilege access to the Air Force networks: the successful Offeror shall ensure all personnel, who are authorized users of an information technology system, hold a favorably completed Tier-3 (T3) investigation, or National Agency Check with law and credit (NACLC), or Access National Agency Check and Inquiries (ANACI) with collateral level access and receive a current periodic reinvestigation in accordance with DCSA guideline for access levels. Authorized users with a privileged or admin role will also need proper 8570 credentials.

Page | 9

3.9 Security Management

The information in subsection 3.9 should be used to inform LOE One and LOE Two, as applicable.

If issued for privileged level Information Technology access, the successful Offeror shall comply with the security requirements specified in the successful Offeror’s DD Form 254, Contract Security Classification Specification. The successful Offeror shall flow down the security requirements to subcontractor, as applicable.

4.0 TECHNICAL VOLUME

The Technical Volume should set forth the Offeror’s innovative solution and shall address the scope and anticipated tasks outlined in Section 3.0.

The Offeror shall provide one technical volume that contains a section dedicated to any or all LOEs. Each Offeror shall propose a technical volume that addresses any or all LOEs in order for the proposal to be considered adequate and to be evaluated by the RSO.

There is a strict limit of 15 pages for the technical volume for each LOE. The LOE One technical volume shall not exceed 15 pages. The LOE Two technical volume shall not exceed 15 pages. If one LOE’s technical volume is under 15 pages, the Offeror shall not attempt to use the unused page count of one LOE to expand the other LOE’s technical volume page count.

Content beyond the set page limit of any technical volume shall not be reviewed by the Government evaluation team.

The Offeror shall include all (if any) assumptions, conditions, or exceptions with any of the work scope, anticipated tasks, or terms and conditions of the Statement of Objectives (SOO) detailed in Section 3.0, the required deliverables detailed in Section 4.5, or the Contract Data Requirements List (CDRL) in Attachment 1. If no technical assumptions are noted in the Technical Volume submitted with the proposal it is assumed that there are no technical assumptions, and that the Offeror takes no exceptions. It is not the responsibility of the Government to seek out and identify assumptions, conditions, or exceptions buried within the submission. The Government reserves the right to negotiate any assumptions, conditions or exceptions that impact or effect the Government’s rights under the resulting contract.

4.1 Table of Contents

Include a table of contents in the Technical Volume. The table of contents shall not count against the page limit per Technical Volume.

4.2 Glossary

Include a glossary of acronyms and abbreviations used in the proposal in the Technical Volume.

The glossary shall not count against the page limit per Technical Volume.

Page | 10

4.3 Technical Solution

Describe how the proposed solution addresses the RSO’s stated objectives in Section 3.0. This section should summarize how the Offeror plans to achieve the stated objectives and identify key results and success metrics that performance can be measured upon. State specific time periods when appropriate and be unambiguous about anticipated results. The technical solution shall count towards the page limit per Technical Volume.

4.4. Statement of Work

The Offeror shall provide a Statement of Work in response to the Statement of Objectives in Section 3.0. The proposed technology solution shall include an explanation of how the Contractor will manage the Additive Manufacturing with Integrated Digital Engineering LOE. The Statement of Work shall include the Contractor’s methodology for assessing risks and issues, plans for coordinating with other RSO Contractors, strategy for working with the RSO technology pipeline, and identifying, integrating, (and where applicable, sourcing) enabling technologies and non-RSO technology solutions. The statement of work shall not count against the page limit per Technical Volume.

4.5. Deliverables

Include a section clearly describing all deliverables, to include schedules and quantities. The successful Offeror shall ensure proper control and coordination of all deliverables as proposed and shall be responsible for timely deliveries. The deliverables shall count against the page limit per Technical Volume.

The Offeror shall assume that the Government will review deliverables and notify the successful Offeror of findings within 15 workdays. The successful Offeror shall be prepared to meet with the Government team as necessary to review status and other deliverables.

The Offeror shall assume that each required deliverable shall be provided with a license for government unlimited/unrestricted rights.

Required Deliverables The deliverables listed below are required deliverables for the specified LOE(s). The Offeror may propose additional deliverables or slightly alter the deliverables proposed below. However, the deliverables must cover the objectives detailed in Section 3.0 and must clearly articulate the proposed data rights license.

Contract Data Requirements List

Deliverable(s) CDRL Frequency Details LOE

Test Report A001 Initial Test Reports shall be delivered 15 calendar days prior to each applicable testing event. Subsequent reports shall be delivered 30 calendar days after Government comments.

Upon completion of test events, the Contractor shall document using the RSO Test Report template on the outcome of testing activities, to include comparisons between expected and observed outcomes. Identification of, and recommendations to resolve, any identified issues will be included in the test report.

One (1) and Two (2)

Page | 11

Conference Agenda

A002 ASREQ The Contractor shall provide an agenda no later than 5 business days prior to the Kickoff Meeting and no later than 15 business days prior to the PMRs.

ONE

(1), Two (2)

Presentation Materials

A003 ASREQ The Contractor shall submit presentation material NLT 5 calendar days prior to the date and time of the presentation/event.

ONE

(1), Two (2)

Conference Minutes

A004 ASREQ The Contractor shall submit meeting minutes NLT 7 calendar days after conclusion of the meeting or conference.

ONE

(1), Two (2)

Contract Summary Report

A005 End of Period of Performance The Contractor shall deliver the first delivery of the final report NLT 30 calendar days prior to contract end date. Subsequent delivery shall occur NLT 15 calendar days after government comments are received (if applicable)

ONE

(1), Two (2)

Quarterly Reports

A006 Quarterly; First submission due 90 days after contract award

The Contractor shall provide reports on a quarterly (every 3 months) basis.

These shall be concise documents describing progress in implementing the LOE(s) scope of work. Each status report shall not be longer than 15 slides.

ONE

(1), Two (2)

4.6 Data Assertions (if applicable)

Offerors may propose data rights other than unlimited/unrestricted data rights for the required deliverables in Section 4.5. Pricing for each deliverable should include and reflect the data rights asserted for each deliverable.

If an Offeror chooses to assert data rights more restrictive than unlimited /unrestricted rights for the required deliverables, the table below must be completed and submitted with the Technical Volume. The table should also be used if less than unlimited/unrestricted rights is anticipated for any additional deliverable proposed for delivery under a CDRL, or for any informal deliverables expected to be provided during contract performance.

The assertion table must conform to DFARS 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions.

The addition of a data assertion table shall not count against the 15-page limit per Technical Volume. The data assertion table shall be submitted in the exact format provided below. All assertions are subject to successful negotiations and acceptance by the Government.

Technical Data or Computer Software to be Furnished With Restrictions

Basis for Assertion None, Developed exclusively at private expense, Developed partially at private expense

Asserted Rights Category None, Government Purpose Rights Limited Rights (Technical Data) Restricted Rights (Software) Specifically Negotiated License

Name of Person Asserting Restrictions

Page | 12

Rights in SBIR Data

5.0 COST VOLUME

Complete the Cost Volume using Attachment 3 - Cost Volume Template provided in the RFP package as a template. This should encompass the complete cost and profit associated with the effort and equal the amount of all LOEs proposed. The Cost Volume shall be broken down per LOE and per year. Each LOE shall contain its own tab with all applicable elements (e.g. direct labor, overhead, direct material, other direct costs, G&A and profit). A summary tab that encompasses all LOEs with all applicable cost elements is also required. The Contractor shall submit the Cost Volume as an unlocked Excel document embedded within the proposal PDF document. The Offeror should not include a section of Volume 3 within the proposal PDF, only the Excel version embedded within.

Some items in the cost volume template attachment may not apply. If that is the case, there is no need to provide information for each and every section. There shall be enough information provided to allow the RSO to understand the basis for the proposed price. The Cost Volume must be sufficient detail to enable RSO personnel to determine the purpose, necessity, and reasonability of the inputs that comprise the proposed price.

The Offeror should provide as much substantiating information as reasonably necessary to justify the cost volume. This can include, but is not limited to: basis of estimate, comparable historical costs, invoices to commercial customers, quotes for material, catalog pricing, equivalent efforts or other substantiating evidence. Further documentation may be requested/required by the Contracting Officer to substantiate costs. All substantiating documentation should be included within Volume 4 - Supporting Documents. Pricing information from non-defense commercial customers is likely proprietary and should be marked as such.

Information included in the Cost Volume includes, but is not limited to:

Direct Labor Costs: Identify key personnel by name and labor category. If specific names are not available, the Contractor shall at least include the labor category (Ex: Software Engineer II). Include the relevant years of experience, number of hours, labor overhead, fringe benefits and actual hourly rates for each individual. For all direct labor proposed, the Offeror shall include a basis of estimate to support the proposed hours.

Direct Material Costs: Justify cost for materials, parts, and supplies with an itemized list containing types, quantities, pricing and where appropriate, purpose. If proposing direct material costs, include justification information (Ex: vendor quotes, historical costs, catalog pricing, etc.) to the greatest extent possible/practical.

Other Direct Costs: This category of costs includes specialized services such as machining, milling, special testing analysis or cost incurred in obtaining temporary use of specialized equipment. When including leased hardware, the proposal must provide an adequate lease vs. purchase justification or rationale. If proposing other direct costs, include justification information (Ex: invoices, leasing quotes, historical costs, etc.) to the greatest extent possible/practical.

o Travel: Include estimated travel costs within the other direct costs section of the Cost Volume. Travel costs must relate to the needs of the project. When proposing travel cost, break out the estimated costs by using the “Travel Cost Template”

Page | 13 located within Attachment 3 – Cost Volume Template provided in the RFP package as a guide.

o Subcontracts: Include subcontractor/consultant costs within the other direct costs section of the Cost Volume. Support all subcontract costs with copies of the subcontract agreements and any other relevant information. The supporting agreement documents must adequately describe the work to be performed. At a minimum, an offeror must include a Statement of Work (SOW) with a corresponding detailed Cost Volume for each planned subcontract.

o Consultants: Provide a separate agreement letter for each consultant. The letter should briefly state what service or assistance will be provided, the number of hours required and hourly rate. Support all consultant costs with copies of the agreements.

o Special Tooling and Test Equipment and Material: The inclusion of equipment and materials will be carefully reviewed relative to need and appropriateness of the work proposed. The purchase of special tooling and test equipment must, in the opinion of the Contracting Officer, be advantageous to the Government and relate directly to the specific effort. They may include such items as innovative instrumentation and/or automatic test equipment. Title to property furnished by the Government or acquired with Government funds will be vested with the AF, unless it is determined that transfer of title to the contractor would be more cost effective than recovery of the equipment by the AF. Include justification information to the greatest extent possible/practical.

6.0 ADDITIONAL PROPOSAL INFORMATION

6.1 Proposal Layout Content

The proposal shall contain four (4) volumes that encompass all required information necessary to evaluate the proposed innovative solution. These volumes shall be submitted via the method described in Section 6.4.

Required Volumes:

Volume 1, Proposal Coversheet: Use Attachment 4 provided in the RFP package as a template.

Volume 2, Technical Volume: As detailed in Section 4.0, Offerors shall include a Technical Volume for each LOE. Each Technical Volume has a strict page limit of 15 pages per LOE. See Section 4 for additional information.

Volume 3, Cost Volume: The Cost Volume should be submitted as an embedded excel attachment within the proposal PDF document. Use Attachment 3 provided in the RFP package as a template.

Volume 4, Supporting Documentation: As detailed in Section 7.0, Offerors shall include all required supporting documentation.

Formatting: The font used shall be no smaller than 10 point on standard 8-1/2" x 11" paper with one-inch margins. All graphics should be distinguishable in both black and white and full color in the event the proposals are printed. Offerors are discouraged from including promotional and non-programmatic items.

Page | 14

6.2 Proprietary Information

Information constituting a trade secret, commercial or financial information, confidential personal information, or data effecting national security must be clearly marked. It shall be treated in confidence to the extent permitted by law. This restriction does not limit the Government's right to use information contained if it is obtained from another source without restriction. The RSO assumes no liability for disclosure or use of unmarked data and may use or disclose such data for any purpose.

If an Offeror is awarded a contract as a result of or in connection with the submission of proprietary data in the proposal, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting contract.

6.3 Identification of Non-U.S. Citizens

Identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants. For these individuals, please provide countries of origin, type of visas or work permits under which they are performing, and explanation of their anticipated level of involvement in the project.

Proposals including the involvement of foreign nationals should include this table:

Full Name Foreign National (Yes or No)

Country of Origin

Type of Visa or Work Permit

Description of Involvement (specific task(s) in the Statement of Work)

(Enter Data Here)

(Enter Data Here)

(Enter Data Here)

(Enter Data Here)

(Enter Data Here)

6.4 Proposal Submittal Details

Proposals must be submitted directly to the RSO contracting team via DoD SAFE by the stated deadline. Prior to submittal the Offeror shall request a DoD SAFE link from the POC listed in section 9.0. After request the Offeror will receive a DoD SAFE link for drop-off email and instructions from the RSO. Questions regarding DoD SAFE may be directed to the POCs listed in section 9.0.

The format for submission of proposals to the RSO is one (1) unlocked PDF document that encompasses all of the required volumes and content. Please virus-check all submissions.

6.5 Solicitation Timeline

Milestone Due Date

Request for Proposal (RFP) Issued 26 Sep 2022 Questions Due Date 11 Oct 2022 Q&A Posted to SAM.gov 25 Oct 2022 Proposal Due 18 Nov 2022 Target Contract Award 06 Feb 2023

*The RSO reserves the right to alter or change any of the due dates listed above.

The RSO reserves the right to disqualify a proposal at any time due to non-compliance with the requirements detailed in this RFP.

Page | 15

The proposal validity date shall be at least 180 days after proposal submission.

7.0 SUPPORTING DOCUMENTS

Supporting Documents shall be submitted with proposal submission. All sections (7.1-7.4) of the Supporting Documents are important components of the proposal and should not be overlooked.

7.1 Additional Cost Information

Any additional cost information to supplement “Volume 3 - Cost Volume” should be included in this section of the supporting documentation. These may include, but are not limited to: basis of estimate, invoices, quotes, catalog pricing, historical costs, subcontractor or consultant agreements and other comparable cost documentation to support one’s proposed costs. This is an important part of the proposal and should be included to the greatest extent possible.

7.2 Standard Form (SF) 1449 Requirements

Review Attachment 2 – SF 1449 contained in the RFP package in its entirety. This document contains a list of applicable provisions that apply to this solicitation. However, please note that the Contracting Officer reserves the rights to negotiate all terms and conditions of any contract before award.

Additionally, each Offeror is required to fill out the required representations, certifications and any other required information (e.g. FAR 52.204-26) in the SF 1449 and include it in this section of the supporting documentation.

7.3 Subcontracting Plan

Unless otherwise exempt, subcontracting plans shall be submitted with the proposals. Reference FAR 19.704 and DFARS 219.704 for subcontracting plan requirements.

7.4 Other Documentation

If the Offeror wishes to submit additional documentation that does not fit under previous sections they can include it in this section of the supporting documents.

8.0 ADMINISTRATIVE INFORMATION

8.1 Definitions

8.1.1 Controlled Unclassified Information (CUI):

Any information that law, regulation, or government wide policy requires to have safeguarding or disseminating controls, excluding information that is classified under Executive Order 13526, Classified National Security Information, December 29, 2009, or any predecessor or successor order, or the Atomic Energy Act of 1954, as amended.

The National Archives and Records Administration (NARA) CUI Registry (http://www.archives.gov/cui/registry/category-list.html) identifies approved CUI categories and subcategories, provides general descriptions for each, identifies the basis for controls, and sets out procedures for the use of CUI.

Page | 16

8.1.2 Data:

Means recorded information, regardless of form or method of recording, which includes but is not limited to, technical data, computer software, computer software documentation, and mask works. The term does not include financial, administrative, cost, pricing or management information and does not include subject inventions.

8.1.3 Technical Data:

Means recorded information, regardless of the form or method of the recording, of a scientific or technical nature (including computer software documentation). The term does not include computer software or data incidental to contract administration, such as financial and/or management information.

8.1.4 Form, fit and function data:

Means data that describes the required overall physical, functional and performance characteristics (along with the qualification requirements, if applicable) of an item, component, or process to the extent necessary to permit identification of physically and functionally interchangeable items.

8.1.5 Computer software:

Means computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae, and related material that would enable the software to be reproduced, re-created, or recompiled. Computer software does not include computer databases or computer software documentation.

8.1.6 Computer software documentation:

Means owner's manuals, user's manuals, installation instructions, operating instructions, and other similar items, regardless of storage medium, that explain the capabilities of the computer software or provide instructions for using the software.

8.1.7 Foreign Entity:

The term foreign entity means any branch, partnership, group or sub‐group, association, estate, trust, corporation or division of a corporation, or organization organized under the laws of a foreign state if either its principal place of business is outside the United States or its equity securities are primarily traded on one or more foreign exchanges.

8.1.8 Foreign Nationals:

Foreign Nationals (also known as Foreign Persons) as defined by 22 CFR 120.16 means any natural person who is not a lawful permanent resident as defined by 8 U.S.C. § 1101(a)(20) or who is not a protected individual as defined by 8 U.S.C. § 1324b(a)(3). It also means any foreign corporation, business association, partnership, trust, society or any other entity or group that is not incorporated or organized to do business in the United States, as well as international organizations, foreign governments and any agency or subdivision of foreign governments (e.g., diplomatic missions).

Page | 17

“Lawfully admitted for permanent residence” means the status of having been lawfully accorded the privilege of residing permanently in the United States as an immigrant in accordance with the immigration laws, such status not having changed.

"Protected individual’’ means an individual who (A) is a citizen or national of the United States, or (B) is an alien who is lawfully admitted for permanent residence, is granted the status of an alien lawfully admitted for temporary residence under 8 U.S.C.

§ 1160(a) or 8 U.S.C. § 1255a(a)(1), is admitted as a refugee under 8 U.S.C. § 1157, or is granted asylum under Section 8 U.S.C. § 1158; but does not include (i) an alien who fails to apply for naturalization within six months of the date the alien first becomes eligible (by virtue of period of lawful permanent residence) to apply for naturalization or, if later, within six months after November 6, 1986, and (ii) an alien who has applied on a timely basis, but has not been naturalized as a citizen within 2 years after the date of the application, unless the alien can establish that the alien is actively pursuing naturalization, except that time consumed in the Service's processing the application shall not be counted toward the 2-year period.

8.1.9 Firm-Fixed-Price Contract Type:

A contract where a vendor is paid a negotiated amount regardless of incurred expenses.

8.1.10 Freight on Board (FOB) Destination:

This means the seller will incur the delivery expense to get the goods to the destination. With terms of FOB destination, the title to the goods usually passes from the seller to the buyer at the destination.

8.1.11 Freight on Board (FOB) Origin:

This means that the buyer must pay to get the goods delivered. (The buyer will record freight-in and the seller will not have any delivery expense.) With terms of FOB origin, the title to the goods usually passes to the buyer at the shipping point.

8.1.12 System for Award Management (SAM):

Offerors must be registered in the System for Award Management (SAM). SAM replaced the Central Contractor Registration (CCR), Online Representations and Certifications Application (ORCA), and the Excluded Parties List System (EPLS). SAM allows firms interested in conducting business with the federal government to provide basic information on business capabilities and financial information. To register, visit www.sam.gov. Follow instructions found on the SAM Web site on how to obtain a Commercial and Government Entry (CAGE) code and an Unique Entity ID.

8.2 Requirement to Perform Work in the United States

All research or research and development work must be performed by the Offeror and/or its subcontractors (if applicable) in the United States.

8.3 Conflicts of Interest

Contract awards to firms owned by or employing current or previous Federal Government employees could create conflicts of interest for those employees which may be a violation of

Page | 18 federal law. Identify any conflict of interest or appearance issues which may be a potential Organizational Conflict of Interest (OCI) in accordance with FAR 9.5, as supplemented.

Contractors are responsible for immediately notifying the Contracting Officer (CO) should any potential conflict of interest arise at any time prior to and/or after contract award. An unmitigated OCI may render a proposal ineligible for award.

8.4 Classified and Export-Controlled Proposals

Classified proposals will not be accepted under this solicitation. If proposals require classified work, the Offeror must have a facility clearance in order to perform the work. For more information on facility and personnel clearance procedures and requirements, please visit the Defense Security Service Website at: http://www.dss.mil/index.html.

Depending on the proposal, it may be subject to Export Control (International Traffic in Arms (ITAR) 22 CFR 120-131, or Export Administration Regulations (EAR) 15 CFR 710-774). If the effort is subject to export controls, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposals. DFARS 252.225-7048, "Export-Controlled Item (JUN 2013)" clause shall be contained in all resulting contracts.

Approval of the DD Form 2345 will be verified if the proposal is chosen for award. If applicable, the DD Form 2345 should be included within Volume 4 – Supporting Documents.

8.5 Feedback Requests

Any feedback requests must be submitted in writing within 10 calendar days after receipt of notification of non-selection. Written requests for feedback must be submitted via email to the RSO Contracting Officer. Requests for feedback should include the company name and the telephone number/e-mail address for a specific point of contact, as well as an alternate.

Additionally, include the solicitation number under which the proposal was submitted, and the proposal title. Feedback requests received more than 10 calendar days after receipt of notification of non-selection will be fulfilled at the Contracting Officer’s discretion. Unsuccessful Offerors are entitled to no more than one feedback response for each proposal.

8.6 Registrations and Certifications

Offerors must have an Unique Entity ID and must register in the System for Award Management (SAM) prior to receiving an award or agreement. Offerors must be determined to be responsible by the Contracting Officer and must not be suspended or debarred from award by the Federal Government nor be prohibited by Presidential Executive Order and/or law from receiving an award.

In accordance with DFARS 252.204-7019, the RSO cannot award a contract unless the successful Offeror has a current NIST SP 800-171 DoD assessment completed and posted in the Supplier Performance Risk System (SPRS) – see DFARS 252.204-7019 and DFARS 252.204- 7020 for more information regarding the requirements.

8.7 WAWF Registration

Offerors must be registered in the prescribed government invoicing system (Wide Area Work Flow: https://wawf.eb.mil/xhtml/unauth/registration/notice.xhtml).

Page | 19

8.8 Fraud and False Statements

Knowingly and willfully making any false, fictitious, or fraudulent statements or representations may be a felony under the Federal Criminal False Statement Act (18 U.S.C. Sec 1001), punishable by a fine of up to $10,000, up to five years in prison, or both.

8.9 Facilities Environmental Concern

The facilities where the proposed work will be performed shall meet all environmental laws and regulations of federal, state, and local Governments for, but not limited to, the following groupings: airborne emissions, waterborne effluents, external radiation levels, outdoor noise, solid and bulk waste disposal practices, and handling and storage of toxic and hazardous materials.

8.10 Government Furnished Property (GFP)

No GFP is anticipated for this effort.

8.11 Non-Government Advisors and Sensitive Information

Non-government advisors may participate in the evaluation of all submissions and shall have signed a non-disclosure agreement (NDA) with the Government. Non-government advisors may also serve in administrative & assistance support capacities.