DRAFT-RFP Attachment 1-Section L-Instruction to Offerors-8JUL24.pdf

AUTOMATIC TEST SYSTEMS ACQUISITION – I (ATSA-I)

SECTION L

INSTRUCTIONS TO OFFERORS

RFP: FA8533-24-R-0002

L-900. INSTRUCTIONS TO OFFERORS

I. PROPOSAL INSTRUCTIONS

A. General

The following instructions cover the preparation and submittal of the Offeror’s proposal for this Request for Proposal (RFP). Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined unacceptable and therefore not eligible for award. Offerors shall submit only one proposal for the ATSA-I Multiple Award Contract (MAC) Indefinite-Delivery Indefinite- Quantity (IDIQ) effort as the Government will review only one (1) proposal per Offeror. Proposals must be received by the following contracting team members listed below via email or DoD SAFE (Department of Defense Secure Access File Exchange) no later than the date and time specified in Block 8 on the face page of the RFP:

Procuring Contracting Officer (PCO) (Sandra E. Harvey, sandra.harvey.2@us.af.mil)

Contract Specialist (Jonathan R. Riggins, jonathan.riggins.2@us.af.mil)

Contract Specialist (LaToya V. Williams, latoya.williams.13@us.af.mil)

The Government intends to award without discussions but reserves the right to conduct discussions if determined necessary. However, if during the evaluation period, it is determined to be in the best interest of the Government to conduct discussions with an Offeror, the PCO will notify the Offeror. Should discussions be conducted, Evaluations Notices (ENs) will be issued in writing.

To streamline and shorten the process, the Government may elect to conduct oral discussions via telephone or virtual conference.

The Government intends to award multiple contracts under this RFP. However, the Government reserves the right not to award any contracts and may do so without prior notice to Offerors. If the Government determines not to award a contract, the Government will not be liable for costs incurred by Offerors.

B. Communications

Exchanges of source selection information between Government and Offerors will be controlled by the PCO. Email may be used to transmit such information only if the email can be sent encrypted, and must include “SOURCE SELECTION INFORMATION – SEE FAR 2.101 and 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via DoD SAFE. In order to facilitate the sending and receiving of encrypted emails, Offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit your source selection information via encrypted email, you will need to contact the PCO/Contract Specialist indicated in Section A above prior to that first submittal in order to exchange certificates used for encryption. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information).

If an Offeror’s computer system cannot support encryption technology, DoD SAFE at https://safe.apps.mil is the preferred alternative method of electronic submissions. The Offeror should send an unencrypted email, including “SOURCE SELECTION INFORMATION – SEE FAR 2.101 and 3.104” in the subject line, requesting a Drop Link for transmission purposes. When submitting source selection information via email (to include DoD SAFE), file suppression utilities, to include but not limited to zip files, will not be accepted.

NOTE: When sending files via encrypted email, please note there is a size limit of 20MB.

NOTE: When sending files via DoD SAFE, please note there is a size limit of 8GB, as well as a 25 files number limit. Offerors shall advise the PCO and Contract Specialist of any submissions that will be outside of these limitations so that multiple DoD SAFE drop-off request links can be sent. A formal notice must be sent to the PCO and Contract Specialist for a drop off link to be sent.

Drop off request/links sent to companies by the Government are only valid for 14 days.

Additionally, drop off request/links are only good for one submittal per use.

If the Offeror chooses not to utilize encrypted email or DoD SAFE, the Offeror shall send the PCO and Contract Specialist correspondence at the time that it submits the proposal stating that it accepts the risk of sending and receiving unencrypted electronic mail.

When submitting source selection documentation, Offerors shall contact the names in Section A above via email to advise of information submittal and obtain acknowledgement of receipt.

II. VOLUME ORGANIZATION

A. General

Proposals shall be submitted to the Government in three (3) separate volumes as set forth below:

ATSA-I Proposal Organization:

VOLUME PAGE

LIMIT

DESCRIPTION

I N/A Completed RFP (Includes Cover Letter and Small Business Subcontracting Plan)

II 30 Technical Proposal ATSA-I Self-Scoring Matrix [1 Page]

Work Sample(s) [Maximum of 3] o Work Sample Cover Sheet(s) [2 Page Max per Work Sample] o Work Sample Contract Front Page(s) [1 Page per Work Sample] o Work Sample Artifacts III N/A Small Business Participation

All proposal information shall be submitted in electronic form via email or DoD SAFE. The Government will not accept hard copy deliveries of the proposal. Electronic files must be virus scanned by the Offeror prior to submitting to the Government.

In addition to the page limitations set forth above, all proposal volumes shall comply with the following format:

a) Each volume shall be marked with the RFP number, Offeror’s name and address, and the number of the Volume, i.e. I, II, or III. Each volume within the proposal shall be separately tabbed and identified. Each page within a volume shall be numbered consecutively. Proposals shall be in the English language.

b) Print shall be no smaller than a font size of 12. Paper size shall be 8 1/2” X 11”, excluding any charts, graphs, drawings, diagrams, and/or supporting illustrations, spreadsheets, etc. Charts, graphs, drawings, diagrams, and/or supporting illustrations, spreadsheets, etc. shall not be greater than 11” x 17”.

Multiple charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc. may be submitted on paper that are either 8 1/2” X 11” or 11” X 17”. No paper shall be larger than 11” x 17”. Margins shall be no smaller than 1 inch. Neither elaborate formats nor color presentations are desired or required.

c) The page limitation for Volume II, Technical Proposal is thirty (30) pages.

The page limitation for Volume III, Small Business Participation is ten (10) pages. The page limitations include any executive summaries, company introductions, cover letters, charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc. Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and retained in the contract file without being considered in the evaluation.

d) Page limitations may be placed on responses to ENs, if issued. The specified page limits for EN responses will be identified in the letters forwarding the ENs to Offerors or on the EN form itself.

e) Each page containing proprietary information should be so marked.

f) Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION - SEE FAR 2.101 and 3.104

CUI

B. Volume I, Completed RFP

1. General:

The Completed RFP is required from all Offerors in a separate volume labeled “Volume I – Completed RFP”. Volume I, Completed RFP shall consist of the completed and signed RFP, to include any amendments issued, with a cover letter delineating any exceptions taken to the RFP terms and conditions with accompanying rationale. The Government reserves the right to independently identify exceptions taken to the terms and conditions of the RFP outside of those identified in the Offeror’s cover letter. However, Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award. Offerors shall ensure that all clauses and provisions that require “fill-in” information are appropriately completed.

2. Small Business Subcontracting Plan:

The small business subcontracting plan required by FAR 52.219-9, as supplemented by the Defense Federal Acquisition Regulation Supplement (DFARS) and Department of the Air Force Federal Acquisition Regulation Supplement (DAFFARS), shall be submitted by large business Offerors only. The plan shall set forth the Offeror’s plan for subcontracting with small businesses to the maximum extent practicable, in accordance with FAR 52.219-9 as supplemented by the DFARS and DAFFARS. The small business subcontracting plan shall include the information required by FAR 19.7, DFARS 219.7, and all associated clauses within this RFP. Large businesses are not required to submit total planned dollars in the Offeror’s small business subcontracting plans in accordance with approved deviation to FAR 19.704(a)(2); however, the remainder of the requirements of FAR 19.704(a) are required to be addressed. At the order level, the contracting officer may establish goals wherein the negotiated goals and dollars will be reflected in an amendment to the existing subcontracting plan. For all awardees without a comprehensive subcontracting plan, the basic level subcontracting plan will be amended to include updated goals and dollars as orders are executed.

C. Volume II, Technical Proposal

1. General:

The Technical Proposal is required from all Offerors in a separate volume labeled “Volume II – Technical Proposal”. The Volume II, Technical Proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. The technical proposal shall not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the Offeror meets the requirements described below. Offerors shall assume the Government has no prior knowledge of their capabilities, work processes, facilities, and experience and will base its evaluation on the information presented in the Offeror’s technical proposal. The burden of proof to substantiate the Offeror’s self-score from the RFP Attachment 3 - ATSA-I Self-Scoring Matrix rests with the Offeror. Unsubstantiated or misleading claims could result in the Government determining that the Offeror’s proposed self-score is artificially inflated.

2. Format and Specific Content:

The following information shall be provided in the technical proposal and will be evaluated to assess technical acceptability in accordance with RFP Attachment 2 - Section M-900, Evaluation Basis for Award. The Technical Proposal shall consist of the RFP Attachment 3 - ATSA-I Self- Scoring Matrix completed and a maximum of three (3) recent/relevant work samples as substantiating documentation. All work samples shall their own cover sheet. Do not submit one

(1) work sample cover sheet for all work samples.

The three (3) work samples shall represent contracts/orders of work performed for the United States Government and be within the last five (5) years from the proposal due date. Using the instructions provided below, the Offeror shall substantiate their self-score from the matrix by providing, as specifically as possible, the actual deliverables for the accomplished work that are detailed in the work samples. Each work sample shall demonstrate the Offeror’s experience for any of the three (3) identified Focus Area Categories where points are being claimed on the self-score matrix so that the Government can validate the Offeror’s submitted self-score. One work sample equals one contract/order. A work sample may be comprised of multiple artifacts. A work sample artifact represents evidence/information/documentation submitted as a deliverable to a Contract Data Requirements List (CDRL) for its work sample. The Offeror needs only to include the relevant portions of artifacts from the Work Sample that clearly show the Government that the Offeror has experience in the Focus Area Categories for which points are claimed.

If the Offeror was a subcontractor on a contract/order for the United States Government, the Offeror may only use artifacts they produced for the Prime as substantiating documentation.

However, the Work Sample Cover Sheet must be populated using information from the Prime’s contract with the Government. In addition to the information described in RFP Attachment 1 - Section L – Instructions to Offerors for the Substantiation section of the Work Sample Cover Sheet, the Offeror shall also explain their role on the Prime’s contract and how the Offeror provided ATS support indirectly to the Government.

In order to maximize the Offeror’s self-score matrix, the Government recommends that each submitted work sample shows expertise across multiple Focus Area Categories. The Offeror must show experience in at least one element of a Focus Area Category in order to get a point on the self-score matrix. The maximum self-score that an Offeror can claim for any given work sample is three (3) points: one for each Focus Area Category. The Government reserves the right to contact the Government POCs identified in the work samples or any other resources deemed necessary for any or all evaluation criteria during validation of self-scores.

In addition, the Offeror shall:

a) Demonstrate traceability between the evaluation criteria and submitted evidence so that the Government can make a clear connection;

b) Provide documented evidence that clearly supports the evaluation criteria—if the Government cannot conclusively align the evidence to support the requirement, it may result in decremented points, and

c) Ensure that the proposed evidence guides the Government to a validated conclusion—if the evidence is unclear and/or the Government cannot make the connection, points will be decremented..

ATSA-I Focus Area Categories

a) ATS Sustainment/Logistical Support

This Focus Area Category represents the capability of the Offeror to perform sustainment/logistical support activities in support of Automated Test Systems (ATS).

Example activities which could be used to demonstrate a proficiency include (but are not limited to) the following:

ATS supportability studies

ATS reverse engineering efforts

ATS logistics data analysis

ATS deficiency investigations

ATS System Contract Logistics Support (CLS), Interim Contractor Support (ICS), and Performance Based Logistics (PBL) contracts, which would include supply chain management, maintenance management, and sustainment engineering efforts

Implementing form, fit, function solutions for ATS to mitigate system obsolescence

b) ATS Integration/Development

This Focus Area Category represents the capability of the Offeror to identify automatic test solutions and design/develop hardware and software to integrate them in new or existing ATS. Example activities which could be used to demonstrate a proficiency include (but are not limited to) the following:

Designing ATS hardware interface cabling and compatible software layers

Providing ATS solutions at DoD locations for all maintenance levels including Depot or Field (Intermediate or Organizational), as well as developmental testing in systems integration labs

Developing ATS technical data packages and thoroughly documented software build projects including all source code to provide Government-owned products and solutions

Developing technical orders for ATS technical content and operations

Implementing cybersecurity controls in ATS controller operating systems

Developing ATS product documentation including system requirements specifications, interface control documents, system product specifications, and software version descriptions

Designing service life extension projects to meet existing capabilities of obsolete ATS

Presenting ATS design reviews and periodic status updates

c) ATS Digital Engineering/Innovation

This Focus Area Category represents the capability of the Offeror to apply an integrated digital approach that uses authoritative sources of systems' data and models as a continuum across disciplines to support lifecycle activities from concept through disposal for ATS.

Example activities which could be used to demonstrate a proficiency include (but are not limited to) the following:

Defining ATS requirements, specifications, and deliverables accurately using digital engineering methods such as the System Modeling Language (SysML)

Maintaining and modifying ATS system models using SysML tools to reflect the technical baseline for a system on contract and be able to provide Engineering Change Proposals (ECPs) that include anticipated system modifications from the SysML reference architecture

Designing ATS hardware using modern tools for modeling and simulation

Developing ATS software in accordance with the DoD DevSecOps Reference Architecture

3. What Not To Submit:

Elaborate brochures or documentation, detailed artwork, or other embellishments are unnecessary and are not desired. The Government will NOT accept discretely generated documentation for the sole purpose of point validation. Discretely generated documentation is defined as documentation that is newly generated expressly for the purpose of responding to this RFP and was in no way a product of the work sample.

4. What To Submit:

Offerors shall submit their Volume II Technical Proposal as a single combined PDF which includes one (1) RFP Attachment 3 - ATSA-I Self-Scoring Matrix and each work sample (including its cover sheet, contract/order front page, and artifacts). As stated in the table of Section II.A, this combined Technical Proposal PDF shall not exceed 30 pages.

5. ATSA-I Self-Scoring Matrix:

The Offeror shall complete one (1) RFP Attachment - ATSA-I Self-Scoring Matrix in PDF format for up to a maximum of three (3) work samples. As described below, the Offeror shall substantiate their self-score for each evaluation criterion for the Government to validate the Offeror’s self-score.

6. Work Sample Substantiating Documentation:

The Offeror shall submit a maximum of three (3) work samples to substantiate their self-score from the matrix. Offerors may highlight sections of the work sample artifacts without inserting text notes. Highlighting must not adversely impact the legibility of the artifact. Offerors should explain on the cover sheet for each work sample how the work sample artifacts substantiate the self-score. All work samples require their own cover sheet. Do not submit one (1) work sample cover sheet for all work samples. Work samples should be arranged such that each segment is readily identifiable allowing for ease of searching.

Each work sample shall include:

ATSA-I Work Sample Cover Sheet

Work Sample Number: WS-

Company Name: XYZ Corporation

Work Sample Name: (i.e. contract name associated with work sample) ATS Refresh

Work Sample Contract/Order Number: FA1234-24-D-5678

Work Sample Period of Performance: 1 Jan 2020 – 30 Jun 2023

Focus Area Categories Claimed: (i.e. category/categories for which points are being claimed by this work sample) o ATS Sustainment and Logistical Support o ATS Integration and Development o ATS Digital Engineering/Innovation

Work Sample Government Point of Contact (x2):

o FirstName1 LastName1, 123-456-7890, FirstName1.LastName1@us.af.mil o FirstName2 LastName2, 987-654-3210, FirstName2.LastName2@us.af.mil

Substantiation: Provide an explanation of this work sample and how it demonstrates experience in support of one or more Focus Area Categories for which points are being claimed on the self-score matrix. Within the explanation, the Offeror shall identify each artifact supporting the category/categories claimed and its location within the work sample, describe what each artifact is, and explain how each is being used to substantiate the proposed self-score.

a) Contract/Order Front Page

b) Work Sample Artifacts: Evidence/information (produced by this work sample) used to substantiate points claimed on the self-score matrix.

Evidence proposed must be submitted in the original format as it was originally delivered. Names that have been manually inserted into substantiating documentation and were not part of the original document will not be used to validate experience.

D. Volume III, Small Business Participation

1. General:

The Small Business Participation proposal is required from all Offerors in a separate volume labeled “Volume III – Small Business Participation”. The Small Business Participation proposal shall fully address in an overall plan each of the following elements:

a) Provide detailed narrative with at least three methods identified and explained regarding how the Offeror intends to ensure small businesses* have equitable opportunities to compete on all task/delivery orders.

b) Provide detailed narrative with at least three methods identified and explained regarding how the Offeror will develop subcontracting goals to meet and exceed Air Force small business* goals in all task/delivery orders.

c) Provide detailed narrative with at least two outreach methods the Offeror intends to utilize in locating small businesses* for subcontracting on all task/delivery orders.

*Small Businesses include service-disabled veteran-owned small business concerns, HUBZone small businessconcerns, small disadvantaged business concerns, and women-owned small business concerns.