FA8684-20-S-C001 Call 0012 One-Step Call for Proposals.pdf

PDF 3 MB Posted

Attached to
Rapid Sustainment Office (RSO) Commercial Solutions Opening (CSO)
Solicitation number
FA8684-20-S-C001
Issued by

About this file

This is a solicitation for a Rapid Sustainment Office (RSO) Commercial Solutions Opening (CSO) seeking innovative sustainment and operational solutions to reduce Air Force costs and improve readiness. The RSO will publish Calls via amendments to this CSO containing specific Areas of Interest related to reducing sustainment costs and improving readiness. Interested parties should monitor this notice and the RSO website for updated information and published Calls. This CSO functions as an umbrella solicitation through September 2022, with Calls containing details on required products/services, response dates, and evaluation criteria. Awards may be FAR contracts or Other Transaction Agreements. The Department of the Air Force is the contracting agency, seeking responses from traditional and non-traditional defense contractors as well as large/small businesses and research institutions.

View the file

Other files

Show all 19

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

DEPARTMENT OF THE AIR FORCE

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

WRIGHT-PATTERSON AIR FORCE BASE OHIO

04 January 2023

Federal Agency: Air Force Program Office: AFLCMC/RO “Rapid Sustainment Office (RSO)” Call Number: FA8684-20-S-C001, Amendment 01, Call 0012 Call Title: New Cold Spray Capability Development NAICS: 541330 – Engineering Services Call Type: One-Step, Closed Call One-Step Call for Proposals Release Date:

04 January 2023

Proposal Due Date: 03 February 2023

1. This Call seeks to solicit innovative solutions that meet the objectives detailed in Attachment 1 RSO CSO Call 0012 Proposal Instructions. The term innovative is defined as any technology, process, or method, including research and development that is new as of the date of proposal submission; or any new application of an existing technology, process or method as of the proposal date.

2. RSO CSO Call 0012 consists of three Lines of effort (LOEs). Offerors can submit proposals for one, two, or all three LOEs. The contract type shall be Firm-Fixed-Price (FFP). Exact details may be found in Attachment 1, RSO CSO Call 0012 Proposal Instructions.

2. In order to be considered for evaluation, all proposals shall be submitted to the Government Contracting Officer via DoD SAFE no later than 03 February 2023 at 8:00 PM EST. LATE PROPOSALS WILL NOT BE ACCEPTED. Prior to proposal submittal the Offeror shall request a DoD SAFE link from the RSO Contracting Officer listed in paragraph 13 below. The format for submission of proposals via DoD SAFE is one (1) unlocked PDF document that encompasses all required content (Volumes 1-4, as described in Section 6.0 of Attachment 1, RSO CSO Call 0012 Proposal Instructions). If a proposal is submitted after the stated time and date, it will not be reviewed. The RSO will not be responsible for any proposals that are late due to issues with Offeror or Air Force email systems, or DoD SAFE. It is the Offeror’s responsibility to insure the RSO receives the proposal by the specific due date and time. Classified proposals will not be accepted; therefore, proposals shall not contain any classified information or data.

3. If an adequate proposal is submitted by the stated due date, the RSO will evaluate the proposed technical solution(s) in accordance with the criteria stated in Attachment 1 – RSO CSO Call 0012 Proposal Instructions.

4. The RSO is not obligated to make any awards as a result of this Call and all awards are subject to the availability of funds and successful negotiations. The Government is not responsible for any monies expended by the Offeror prior to the issuance of any contract award. The RSO reserves the right to modify any proposal requirements. Any information contained in this One- Step Call for Proposals that could potentially be viewed as contradictory to this paragraph should not be interpreted as such.

5. If issues arise pertaining to this One-Step Call for Proposals that cannot be resolved to the satisfaction of the RSO, the Contracting Officer reserves the right to withdraw or cancel the One- Step Call for Proposals without award. In such an event, the Offeror will be notified, via letter or email, of the decision and this decision shall be final and conclusive and shall not be subject to the “Disputes” clause or the “Contracts Dispute Act.”

6. Please note that 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. The RSO also cannot award a contract unless the successful Offeror has updated the FAR 52.204-26 representation in SAM to account for the update to the provision published in October 2020.

7. It is also important to note that RSO intends to include the clause FAR 52.242-15, Stop-Work Order, in any resulting contract award.

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

9. Embedded within this document are five (5) attachments, listed below the signature block.

Specific instructions regarding each are contained within the attachments.

10. If any conflicting information occurs between this One-Step Call for Proposals and other related solicitation documents, this One-Step Call for Proposals shall take precedence. However, for information not specified or contained in this One-Step Call for Proposals, the other related solicitation documents may still apply. Each Offeror is responsible for reviewing each document in its entirety.

11. This solicitation is only applicable for FA8684-20-S-C001, Amendment 01, Call 0012 entitled, “New Cold Spray Capability Development” and should not be considered for any other effort(s).

12. The Point of Contact for this effort is the Contracting Officer, Ethan Dale at ethan.dale@us.af.mil. The Offeror shall not contact any other Government personnel or offices regarding this Call. The government will only answer questions pertaining to the technology used to submit proposals (e.g. requests for a DoD SAFE link).

Attachments:

1. RSO CSO Call 0012 Proposal Instructions

2. SF 1449

3. Cost Volume Template

4. Proposal Coversheet Template

5. Contract Data Requirements List (CDRL) Package

Note: These documents are included as embedded attachments to this adobe file. They can be accessed using the paperclip function in this PDF. This PDF document must be downloaded and saved in order to access the embedded attachments.

Attachment 1 – Rapid Sustainment Office (RSO) Commercial Solutions Opening (CSO) Call 0012 Proposal

Instructions

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. This announcement is for a Technology Focus Area (TFA)/Area of Interest (AoI) under the RSO Commercial Solutions Opening FA8684-20-S-C001, Amendment 01. The TFA/AoI for this one-step call for proposals is Agile Manufacturing/ Mobile Cold Spray Capability.

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 and Cold Spray 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.

The authority to issue this One-Step, Closed Call is derived from AFLCMC/RO Commercial Solutions Opening, FA8684-20-S-C001, Amendment 01, dated 27-May-2022. The CSO authority is Section 879 of the National Defense Authorization Act for FY2017, Public Law 114- 328, and Class Deviation 2022-O0007

Federal Agency: Air Force Program Office: AFLCMC/RO “Rapid Sustainment Office (RSO)” Call Number: FA8684-20-S-C001, Amendment 01, Call 0012 Call Title: New Cold Spray Capability Development NAICS: 541330 – Engineering Services Call Type: One-Step, Closed Call One-Step Call for Proposals Release Date:

January 4, 2023

Proposal Due Date: February 3, 2023

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

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.

2.2 Evaluation of Proposed Lines of Efforts

A. Section 3.0, Statement of Objectives, describes three specific Lines of Effort (LOEs).

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

Each LOE 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, Cold Spray Process Monitoring, 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, Cold Spray Adhesion Testing, and reach a conclusion solely as to LOE Two. The evaluators will then use the criteria listed in Section 2.1 to evaluate LOE Three, Slat Track Repair, and reach a conclusion solely as to LOE Three.

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 all three LOEs, or to award one

LOE to two or more Offerors. This could result in three Offerors receiving a contract for only one LOE each, or it could result in one Offeror receiving a contract that includes all three LOEs.

D. Each Offeror can propose a solution for one LOE, two LOEs, or all three LOEs. If proposing more than one LOE, the offeror shall clearly differentiate the LOEs so that the RSO evaluation team can evaluate the LOEs independent of one another.

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 period of performance for LOE 1 shall not exceed 18 months. The period of performance for LOE 2 shall not exceed 12 months. The period of performance for LOE 3 shall not exceed 12 months. 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 12 months or 18 months after contract award depending on the LOE(s) proposed.

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.

The successful Offeror shall identify, demonstrate, integrate, and transition technologies, processes, and techniques to further establish organic Air Force capability to perform production CS repairs of aircraft components. The successful Offeror should contemplate the management of all efforts and provide associated reporting for the anticipated tasks included in, but not limited to, the following LOE descriptions. The successful Offeror is not limited to only this list in developing a proposal that sets forth an innovative solution. The proposal should address how each task shall be accomplished during the period of performance.

3.1 LOEs 1-3

LOE 1 – Cold Spray (CS) Process Monitoring

The scope of LOE 1 is described below (reference Deliverables Table 4.5).

a. Conduct market research on commercially available CS process monitoring technology and summarize in Technical Report

b. Perform down-selection on CS process monitoring technology that provides best value to AF and summarize in Technical Report

i. Can be COTS or can involve some development if TRL is 5 or higher to allow for establishing this capability throughout the AF within this PoP

c. Create Implementation Plan to establish process monitoring capability at DAF locations and summarize in Technical Report

d. Establish CS process monitoring capability through an integration effort of process monitoring sensor package with each site’s already existing CS equipment, per developed Implementation Plan at:

i. Ellsworth AFB, 28 MXG/AMF

ii. Tinker AFB, 76 PMXG

iii. Robins AFB, 402 CMXG

iv. ATTC-ERR

v. ATTC-MG

vi. Hill AFB, 309 CMXG

e. Create and conduct test series to demonstrate predictability of selected process monitoring system/techniques for adhesion quality, porosity, etc. This should be documented in a Test Plan and Test Report

f. Create implementation plan to reduce destructive testing requirements through use of CS process monitoring and Non-Destructive Inspection (NDI). Provide proposed comprehensive test series involving process monitoring, NDI, and destructive testing to be used for approval of CS repair for a non-structural, non-critical AF aircraft component. Summarize in Draft and Final Reports.

g. Provide a Final Report that describes the project’s efforts and conclusions.

i. Include a section that includes development of technical data for use and maintenance of equipment and training

ii. Include a section to outline computer resources required for use. Will this require an ATO or standalone computing or connection to NIPR

iii. Provide a list of equipment and costs requiring accountability

LOE 1 CDRL:

A001, DI-ADMN-81250C, Conference Meeting Minutes A002, DI-ADMN-81373, Presentation Material A003, DI-MGMT-80555A, Program Progress Report A004, DI-MISC-80048, Scientific and Technical Reports Summary A005, DI-SESS-80249B- Maintenance Test and Support Equipment List A006, DI-ILSS-80872, Training Materials A007, DI-NDTI- 80566A, Test Plan A008, DI-ADMIN-80447A, Contract Summary Report A009, DI-MISC-80508B, Technical Reports-Studies Services

A010, DI-MGMT-82001A, RMF Artifacts

LOE 2 – Cold Spray Adhesion Testing

The scope of LOE 2 is described below (reference Deliverables Table 4.5).

a. Utilize Design of Experiment (DoE) principles to develop an optimized test series, described in a Test Plan, to characterize adhesion of CS deposits on substrate materials with:

i. Fixed parameters representative of approved CS repairs for:

1. CS System – High Pressure, Fielded and in-use at AF location(s)

2. Gas Temperature

3. Gas Pressure

4. Gas Flow Rate

5. Nozzle Standoff Distance

6. Raster Spacing

ii. Variable parameters representative of approved CS repairs for:

1. Powder Feed Rate

2. Nozzle Spray Angle

3. Traverse Speed

iii. Provide all necessary information in the Test Plan to allow for the adhesion testing to be repeated by an outside agency.

b. Conduct Finite Element Analysis to better understand and/or improve upon the ram tensile testing method described in MIL-J24445A. Provide a Technical Report on this analysis and provide a recommendation for glue-less adhesion test methodology to test CS deposits on substrate material. Forces experienced by the CS deposited coupons and failure mechanisms should be identified and described.

c. Perform materials characterization for adhesion per developed, optimized test series (from a. above) using glue-less adhesion test method (from b. above) to include, but not limited to, the following powder and substrate combinations:

i. Solvus Global DARC-AL6061-G1H1/2 on Al 2024 substrate using nitrogen as the carrier gas

ii. Solvus Global DARC Al 7075 on Al 7075 substrate using nitrogen as the carrier gas

d. Provide a Test Report with all materials characterization data along with analysis and conclusions drawn from the results of testing.

LOE 2 CDRL:

A003, DI-MGMT-80555A, Program Progress Report A004, DI-MISC-80048, Scientific and Technical Reports Summary A007, DI-NDTI- 80566A, Test Plan

LOE 3 – Slat Track Repair

The scope of LOE 3 is described below (reference Deliverables Table 4.5).

a. Develop on-wing, hand-spray repair of slat tracks. Provide all repair recipe data in Technical Data Package.

b. Create a Test Plan with descriptions of all testing required to provide assessment of repair quality in terms of adhesion strength, porosity, hardness, wear, shear strength, etc.

c. Perform testing per developed Test Plan and provide all data, results, analysis, and conclusions in a Test Report.

d. Support working this repair from design through approval to allow it to move into organic AF production. This involves qualification for CS system used, powder/substrate material characterization, and operator training.

e. Provide complete Technical Data Package for the repair along with training to AF operators to allow them to perform production repair.

i. Include safety procedures for dust hazards, masking, FOD, and PPE required to perform on wing repair

LOE 3 CDRL:

A003, DI-MGMT-80555A, Program Progress Report

A004, DI-MISC-80048, Scientific and Technical Reports Summary

A006, DI-ILSS-80872, Training Materials

A007, DI-NDTI- 80566A, Test Plan

3.2 Program Management Information and Assumptions

The information in subsection 3.2 should be used to inform LOEs 1-3, as applicable.

The successful Offeror shall execute program management responsibilities. The successful Offeror shall plan to execute a project kickoff no later than 30 days after contract award and shall plan to support recurring and ad hoc technical interchange meetings, demonstrations, test events, and other engagements at Government’s and successful Offeror’s facilities as required (A001- A010).

Any assumption made by the successful Offeror contrary to this shall be clearly articulated as a term/condition in the successful Offeror’s proposal.

A003, DI-MGMT-80555A, Program Progress Report A004, DI-MISC-80048, Scientific and Technical Reports Summary A005, DI-SESS-80249B- Maintenance Test and Support Equipment List A006, DI-ILSS-80872, Training Materials A007, DI-NDTI- 80566A, Test Plan

A009, DI-MISC-80508B, Technical Reports-Studies

3.3 System Security Engineering Information and Assumptions

The information in subsection 3.3 should be used to inform LOEs 1-3, as applicable.

The Offeror shall conduct cybersecurity assessments and generate and deliver required Risk Management Framework (RMF) artifacts to support an Authority-to-Operate Package for any delivered equipment. The successful Offeror’s efforts to support these activities include, but are not limited a Security Plan, an Assessment and Authorization Project Plan, a Plan of Action and Milestones, vulnerability scans, security technical implementation guides, a system assessment, an Information System Continuous Monitoring Plan, and an IT Categorization and Selection Checklist.

A010, DI-MGMT-82001A, DoD RMF Package Deliverables

The successful Offeror shall participate in System Security Engineering practices to characterize the system, identify security vulnerabilities, assess system and operational risks, and develop mitigations. The successful Offeror’s efforts to support these activities include, but are not limited to:

Establish and maintain a program protection and security program to control and protect defense information and technical data associated with the execution and performance of this contract

Report Cyber incidents to the government IAW DFAR Clause 252.204-7012 (Safeguarding Covered Defense Information), DFARS 252.204-7008, (Compliance with Safeguarding Covered Defense Information Controls). In addition, provide a root-cause, corrective-action report and 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.

System design and architecture analysis to identify internal and external features, interactions, information segregation, and possible vulnerabilities

Functional thread analysis to identify Safety Critical Functions and Mission Critical functions

Development of a Supply Chain Risk Management (SCRM) plan to assess supply chain vulnerabilities and mitigation needs

Support software assurance verification planning and execution Requirements and Test and Evaluation plans analysis for inclusion of systems security and cyber resiliency allocations 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 government led IPTs. 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 participate in the government-led IPTs to provide technical input to the Government’s program protection planning and SSE activities.

The contractor and government entities will work together to build assessments and artifacts for any required cyber and security certifications required for full fielding of the technology solutions. Security Classification Guides can be provided as GFI to the successful Offeror upon request during contract performance.

3.4 Information Security Information and Assumptions

The information in Section 3.4 should be used to inform LOEs 1-3, 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 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 offeror shall ensure non-US Citizens are not given access to data. The offeror shall adhere to DFARS 252.225.7048.

Authorized users with a privileged or admin role will need NIST 8570 credentials and hold a favorably completed Tier-3 (T3) investigation in accordance with Defense Counterintelligence and Security Agency (DCSA) guideline for access levels.

Access to federal facilities and computer systems require the offeror's personnel to submit to a federal criminal background check which include an FBI fingerprint check. The offeror's personnel shall comply with any additional local requirements specific to the facility location, or system, of access.

Additionally, the Contractor 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 and DFARS 252.204-7012). The Contractor shall comply with DoDI 5200.48, Controlled Unclassified Information, AFI 16-1404 Air Force Information Security Program, Air Force Guidance Memorandum 2020-16-01, Air Force Guidance Memorandum for CUI, 23 July 2020, and DoDM 5400.07-Air Force Manual 33-302, DoD Freedom of Information Act (FOIA) Program. The Contractor shall monitor CUI aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information. CUI, OPSEC, and Anti-Terrorism Annual training is mandatory for all Air Force Contractors. The CUI training is available via the CDSE website: https://securityhub.usalearning.gov/index.html.

Additionally, all resources (e.g. publication/instructions) provided by the Government to assist the Contractor in the performance of their contract shall be surrendered at the end of contract performance or upon Government request.

3.5 Operational Security Information and Assumptions (OPSEC)

The information in Section 3.5 should be used to inform LOEs 1-3, as applicable.

The Contractor shall support the USG by developing/updating the contractor’s program security / OPSEC Management structure, including relationships with corporate hierarchy and program subcontractors and suppliers.

The Contractor shall support the USG in the application of Operations Security (OPSEC) in their management of the Program IAW AFI 10-701 Operations Security, the OPSEC Plan, and program’s Critical and Emerging Technologies List provided by the Government program office.

The Contractor shall support the USG by developing/updating an OPSEC Plan which incorporates development, planning, training, assessment, surveys, and readiness training.

Including the results of the five-step OPSEC analysis: Identifying CPI, Analyzing Threats, Analyzing Vulnerabilities, Assessing Risk, and Applying Countermeasures, including those aspects of the foreign intelligence threat that are applicable to the specific contract, only use if no separate OPSEC deliverable is required elsewhere.

3.6 Personnel Security

The information in Section 3.6 should be used to inform LOEs 1-3, 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; they do not result in clearance eligibility. 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 privilege access to Air Force, or DoD computer systems: the Contractor shall ensure all personnel, who are authorized users of an information technology system, hold a favorably completed Tier-1 (T1), or 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 NIST 8570 credentials.

4.0 TECHNICAL VOLUME

Refer to subsection 6.1 of this document for additional formatting instructions.

The Technical Volume should set forth the Offeror’s innovative solution and shall address the statement of objectives and deliverables outlined in Section 3 (3.0-3.6), and section 4.5.

There is a strict limit for the Technical Volume. The LOE One technical volume shall not exceed 15 pages. The LOE Two technical volume shall not exceed 10 pages.

The LOE Three technical volume shall not exceed 10 pages. If one LOE’s technical volume is under the page limit, the Offeror shall not use the unused page count of one LOE to expand the other LOE’s technical volume page count. LOE(s) being proposed shall be clearly identified.

Content beyond the 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 Statement of Objectives (SOO) detailed in Sections 3.0-3.6, the required deliverables detailed in Section 4.5, or the Contract Data Requirements List (CDRL) in Attachment 5. 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 affect 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 for the 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 for the Technical Volume.

4.3 Technical Solution

Describe how the proposed solution addresses the RSO’s stated objectives in Section 3. 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 for the Technical Volume.

4.4. Statement of Work

The Offeror shall provide a Statement of Work in response to the Statement of Objectives in Sections 3.0-3.6. The proposed technology solution shall include an explanation of how the successful Offeror will manage the effort, to include addressing all tasks related to Identification, Demonstration, and Transition of technologies, processes, and techniques. The Statement of Work shall include the Contractor’s methodology for assessing risks and issues and for integrating and, where applicable, sourcing enabling technologies along with associated processes and techniques for organic AF production repair capability. The statement of work shall not count against the page limit for the 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 for the 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 unlimited data rights.

Required Deliverables The deliverables listed below are required deliverables for requirements. The Offeror may propose additional deliverables or alter the deliverables proposed below. However, the deliverables must cover the objectives detailed in Sections 3.0-3.6 and must clearly articulate the proposed data rights license.

Deliverables

Deliverable(s) CDRL Frequency Details Section LOEs

Project Kick off Meeting

(DI-ADMN-

81250C)

A001 Minutes shall be submitted- no later than 7 calendar days after the meeting or conference

The Contractor shall present overall contracting plan and details on deliverable achievement. No more than 10 slides for presentation

3.1-3.2 1-3

Technical Deep Dive

(DI-ADMN-81373)

A002 Deliver Presentation Material NLT 5 calendar days prior to the date and time of the presentation/events

LOE 1: every 6 months for Technical Deep Dive (3 for 18-month PoP)

LOE 2: every 6 months for Technical Deep Dive (2 for 12-month PoP)

LOE 3: every 6

The contractor shall provide a review of work performed with a focus on how technical requirements and deliverables were met.

An overview of the capabilities should be provided.

3.1.-3.2 1-3 months for Technical Deep Dive (2 for 12-month PoP)

Monthly Project Update

(A003, DI-

MGMT-80555A,

Program Progress Report)

A003 Monthly; First delivery due 60 days after contract award; Subsequent delivery shall occur monthly after first delivery provide status updates for work accomplished and upcoming work planned. Briefing materials shall be delivered NLT one day prior to the Monthly Project Update.

Technical Report/Data Package

(DI-MISC-80048)

A004 LOE 1: Due NLT 180 days after contract award.

LOE 2: Due NLT 120 days after contract award.

LOE 3: Due NLT 30 days prior to end of PoP.

LOE 1: this should report on the market research effort and conclusions;

down-selection and/or optimization of process monitoring technology;

and implementation plan to establish this capability at DAF locations

LOE 2: this should report on the Finite Element Analysis;

recommended adhesion test methodology;

characteristics of the test including what conclusions can be drawn from it; and all information required to allow an outside agency to repeat the testing

LOE 3: Technical Data Package that contains all data required to perform the repair.

Deliver a functional prototype

(DI-SESS-80249B)

A005 One time per location; due NLT 30 days before the end date. To be aligned with A006 for LOE 1.

LOE 1: The contractor shall deliver, integrate, and install all sensors and equipment required to establish process monitoring capability per developed

3.1 1

Implementation Plan at each specified location.

Perform operational checks to confirm proper functioning.

Develop & Conduct Training

(DI-ILSS-80872)

A006 One time per location; due NLT 30 days before the EOC. To be aligned with A005 for LOE 1.

LOE 1: The Contractor shall conduct required training to provide personnel with capability at each receiving location. The approach should be transferable to the government to allow for organic training of new personnel.

LOE 3: The Contractor shall conduct required training to provide personnel with capability to perform production repair.

3.1-3.2 1 and 3

Test Plan

(DI-NDTI- 80566A)

A007 LOE 1: Due NLT 120 days after contract award.

LOE 2: Due NLT 180 days after contract award.

LOE 3: Due NLT 90 days after contract award.

LOE 1: The Contractor shall deliver a Test Plan that provides a plan to conduct a test series that will show how process monitoring can be used to predict performance of CS deposits.

LOE 2: The Contractor shall deliver a Test Plan that uses an optimized, glue-less adhesion test to characterize adhesion strength of CS deposits for specified powder and substrate combinations.

LOE 3: The Contractor shall deliver a Test Plan that provides a plan to conduct a test series to provide CS deposition quality results for designed repair to support approval.

Test Report

(DI-ADMIN-

80447A)

A008 LOE 1: Due NLT end of PoP.

LOE 2: Due NLT 30 days prior to end of PoP.

LOE 3: Due NLT end of PoP.

deliver a Test Report that provides all data, results, analysis, and conclusions from the conducted test series.

Final Report

(DI-MISC-80508B

A009 Draft and Final.

Draft report due 60 days prior to end of PoP. Final Report due 15 days prior to end of PoP.

deliver a final report that details work accomplished and provides recommendations on implementing lessons learned throughout the AF Sustainment enterprise.

RMF Artifacts

(DI-MGMT-

82001A)

A010 Due NLT 90 calendar days prior to the end of the contract period of performance

A best effort will be made to meet the timeline proposed by the USAF but is subject to change depending on the timing of the external assessments coordinate with the government Security point-of-contact on the appropriate format and templates for approval and the performer can expect to submit a Security Plan, an Assessment and Authorization Project Plan, a Plan of Action and Milestones, vulnerability scans, security technical implementation guides, a system assessment, an Information System Continuous Monitoring Plan, and an IT Categorization and Selection Checklist

3.3 1

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 following table 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 30-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 Rights in SBIR Data

Name of Person Asserting Restrictions

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

5.0 COST VOLUME

Complete the Cost Volume using Attachment 3 - Cost Volume Template provided in the One- Step Call for Proposals package as a template. Offerors shall submit one cost volume per LOE proposed. This should encompass the complete cost and profit associated with the effort and equal the amount of all CLINs proposed. The Cost Volume shall be broken down per CLIN and per year. Each CLIN 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 CLINs 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” located within Attachment 3 – Cost Volume Template provided in the One-Step Call for Proposals 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 One-Step Call for Proposals package as a template.

•Volume 2, Technical Volume: As detailed in Section 4.0, Offerors shall include a Technical Volume for objectives. The Technical Volume has a strict page limit. See Section 4.0 for additional information.

•Volume 3, Cost Volume: The Cost Volume should be submitted as an embedded excel attachment within the proposal PDF document. See Section 5.0 for complete details.

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

Formatting: The font used shall be Times New Roman and 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.

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)

6.4 Proposal Submittal Details

The Point of Contact for this effort is the RSO Contracting Officer, Mr. Ethan Dale. The Offeror shall not contact any other Government personnel or offices regarding this Call. The government will only answer questions pertaining to the technology used to submit proposals (e.g. requests for a DoD SAFE link).

Proposals must be submitted directly to the RSO Contracting Officer via DoD SAFE by the stated deadline. Prior to submittal the Offeror shall request a DoD SAFE link from the RSO Contracting Officer listed below.

Position Name Email RSO Contracting Officer Mr. Ethan Dale ethan.dale@us.af.mil

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

One-Step Call for Proposals Issued 04-Jan-2023 Target Contract Award 14-Apr-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 One-Step Call for Proposals.

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 One-Step Call for Proposals 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…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .