Survivability Test Stand (STS)

FA9101-26-R-B005

Attachment 4

FA9101-26-R-B005

Attachment 4

CUI

SECTION L

INSTRUCTIONS TO OFFERORS

IDIQ Ceiling: $125,000,000.00 Minimum Order Amount: $50,000.00 Maximum Order Amount: $90,000,000.00

L-1.0 GENERAL INSTRUCTIONS TO OFFERORS

L-1.1 The proposal instructions in this section are designed to assist Offerors in preparing a complete response that reflects a full understanding of the proposed approach to accomplish all contractual requirements. Attachment 5, Section M details how proposals will be evaluated. Offerors are expected to comply with all requirements of the Request for Proposal

(RFP).

L-1.2 Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors to be eligible for award. By submission of its offer, the Offeror consents and agrees to all solicitation requirements and identified constraints.

Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Non-conformance with the instructions provided may result in an unfavorable proposal evaluation, or rejection of an Offeror’s proposal, rendering it ineligible for award.

L-1.3 The Procuring Contracting Officer (PCO), Tyler Payne, is the sole point of contact for this acquisition. Address any questions or concerns to the PCO at tyler.payne.9@us.af.mil.

L-1.4 Cross-Teaming Restriction

The Government seeks to maximize competition among Offerors to ensure it receives proposals that are free from any Offeror incentives or disincentives that may favor one proposal over another. To help safeguard the integrity of the procurement process, Offerors who submit proposals as prime contractors for this contract, or as a member of a joint venture (JV) prime contractor, may not also serve as a subcontractor to another Offeror submitting a proposal as a prime contractor for this contract.

L-1.5 Use of Non-Government Advisors Offerors are advised that technical and cost/price data submitted to the Government in response to this solicitation may be released to non-government advisors for review and analysis. The non-government advisor’s support will be provided by:

Canvas Inc, LLC

Beyond New Horizons, LLC

Attachment 4

FA9101-26-R-B005

Offerors shall provide objections to disclosure in writing to the Contracting Officer within 10 days of RFP issuance. Include a detailed statement of the basis of objection and identification of the specific portions to the proposal the offeror objects to disclosure to non-government advisors.

L-2.0 SOURCE SELECTION METHODOLOGY

L-2.1 Competitive, Best Value Source Selection The Government intends to award one, firm-fixed-price (FFP), Single Award Indefinite Delivery Indefinite Quantity (IDIQ) Contract in accordance with (IAW) Federal Acquisition Regulations (FAR)16.504. The basic contract will have a five-year ordering period. Orders will consist of FFP contract line-item numbers (CLINs) and delivery periods that will be negotiated at the order level.

L-2.1.1 Offerors Best Terms The Government may award without discussions but reserves the right to enter into discussions.

Therefore, the Offeror’s initial proposal shall contain the Offeror’s best terms for Technical, Past Performance, and Price. If the Government contemplates award without discussions, the Offerors may be given the opportunity IAW FAR 15.306 to clarify certain aspects of its proposal (e.g., the relevance of an Offeror’s past performance information (PPI) and adverse PPI to which the Offeror has not previously had an opportunity to respond) or to resolve minor or clerical errors.

L-2.1.2 Competitive Range If discussions are to be conducted, the PCO will establish a competitive range (as set forth in FAR 15.306(c)) based on the ratings of each proposal against all evaluation criteria which will be approved by the Source Selection Authority (SSA). If the PCO determines that an Offeror’s proposal should not be included in the competitive range, the proposal will be eliminated from consideration for award and written notice of the decision will be provided to the unsuccessful Offeror IAW FAR 15.503.

If the PCO determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the PCO, with the approval of the SSA, may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

L-2.1.3 Final Proposal Revisions (FPRs) If discussions are deemed necessary with Offerors, upon completion of those discussions, the PCO will request that the Offeror provide an FPR. Revisions to any volume(s) shall be submitted by providing two versions, one “clean” version, and one “track changes” version.

The Offeror is advised that any changes to the proposal in the FPR shall be fully addressed and / or explained and reflected in the proposed Initial Order Price Proposal Volume. Failure to comply with this requirement can adversely influence the evaluation of the proposal. The PCO will establish a common due date and time for submission of the FPR.

Attachment 4

FA9101-26-R-B005

When FPRs are requested, any revisions or non-compliance with the contract terms and conditions submitted in the FPR may not be subject to further discussions and may render the offer unacceptable for the Government. This provision is not intended to restrict the Offeror’s opportunity to revise its proposal. Rather, it is intended to preclude any misunderstandings by the Government that could result if new or revised terms and conditions submitted in the FPR have not been fully disclosed, discussed, and understood during discussions. Hence, such new or revised terms and conditions are not solicited and, if submitted in the FPR, may render the offer unacceptable to the Government.

L-2.1.4 Debriefings The PCO will promptly notify Offerors of any decisions to exclude them from the competitive range whereupon, they may request and receive a debriefing IAW FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The PCO will notify unsuccessful Offerors in the competitive range of the source selection decision IAW FAR 15.503. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make a request IAW the requirements of FAR 15.505 or 15.506, as applicable.

L-2.1.5 Discrepancies If an Offeror believes that the requirements in these instructions contain errors, omissions, ambiguities, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale (no later than five business days after release of this solicitation), as well as the remedies the Offeror is asking the PCO to consider as related to the omission or error.

L-2.1.6 Evaluation Notices (ENs) The Government may need to conduct written exchanges with Offerors which will be in the form of an EN. Page format and limitations will be placed on responses to ENs in the event they are issued. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors.

L-2.1.7 RFP Revisions / Amendments The Government reserves the right to revise or amend any portion of this solicitation. Such revisions or amendments will be available on the System for Award Management (SAM) website as www.SAM.gov using Standard Form (SF) 30. If such amendments require material changes, the proposal due date may be extended at the discretion of the PCO and by enough days to enable an Offeror to revise its proposal. In such cases, the amendment will include an announcement of the new proposal due date and time. The Offeror shall provide acknowledgement in its proposal Volume I – Contract Documentation of all solicitation amendments issued by the Government.

L-2.1.8 Electronic Reference Documents

Attachment 4

FA9101-26-R-B005

All referenced documents for this solicitation are available on www.SAM.gov. Potential Offerors are encouraged to subscribe for real-time email notifications when information has been posted to the website for this solicitation.

L-2.1.9 Communications and Exchanges Exchanges of source selection information between the Government and Offerors will be controlled by the PCO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Controlled Unclassified Information and Source Selection Information – See FAR 2.101 and 3.104” in the Subject line. Otherwise, source selection information will be transmitted via other means as appropriate. The Government may use the Department of Defense (DoD) Safe Access File Exchange (SAFE), https://safe.apps.mil/, to transmit / receive source selection information. NOTE: Proposal submissions shall follow the instructions provided in L-2.4.

L-2.2 PROPOSAL CONTENT

To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors to be eligible for award. By submission of its offer, the Offeror consents and agrees to all solicitation requirements and identified constraints.

Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Non-conformance with the instructions provided may result in an unfavorable proposal evaluation, or rejections of an Offeror’s proposal, rendering it ineligible for award.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation by the Government and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government’s requirements but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements.

Offerors shall assume that the Government has no prior knowledge of its facilities and experience and will base its evaluation on the information presented in the Offeror’s proposal.

The Offeror’s proposal shall demonstrate that the Offeror possesses the technical expertise and past performance to perform all requirements of the Statement of Objectives (SOO) and its attachments.

The Offeror’s proposal shall include all the information requested and shall comply fully with these Section L instructions. Failure to do so may cause the Offeror’s proposal to be eliminated from consideration for award. Offerors are reminded to properly mark proposal documents which contain proprietary or restricted information.

NOTE: IF THE PROPOSAL IS NOT RECEIVED BY THE DUE DATE / TIME SPECIFIED,

THE OFFEROR’S PROPOSAL IS CONSIDERED LATE IAW FAR 52.215-1.

Attachment 4

FA9101-26-R-B005

No pricing information should appear in Volume II, Technical Proposal. The Government advises Offerors that taking exception to or deviating from any term or condition of the RFP may make an offer unacceptable and the Offeror ineligible for award.

The proposal acceptance period is specified in Block 8 of the solicitation. By signing in Block 30a of the SF1449, the Offeror acknowledges that the proposal is valid for a period of not less than 90 days from the proposal due date. The Offeror shall make a clear statement in its cover letter (see L-3.1.1.1) that the proposal is valid until the applicable date as referenced above and in the solicitation.

L-2.3 PROPOSAL ORGANIZATION

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the various technical approaches, as well as past performance and price, to be meaningfully evaluated without discussions. The offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems.

Elaborate brochures or documentation, detailed artwork, or other embellishments are unnecessary and are not desired.

Each Offeror shall submit one electronic copy for each volume. Include a cover sheet, clearly marked with the volume, title, RFP identification, and the Offeror’s name. Apply all appropriate markings, including those prescribed IAW FAR 52.215-1(e). Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. Proposal submissions via email will not be accepted. IAW FAR Subpart 4.8, Government Contract Files, the Government will retain an electronic copy of all unsuccessful proposals.

The Offeror’s electronic copies shall be submitted in an un-compressed format readable and searchable by Microsoft (MS) Office 2016 (or later) applications (with the exception of PPI as described in L-3.3.3.2.). Submit SF 1449 and Contract Data Requirements Lists (CDRL) in portable document format (PDF). Use separate files to permit rapid location of all portions, exhibits, annexes, and attachments, if any.

L-2.3.1 Proposal Volumes The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table L- 2.3.1.1-1 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits as specified in Table L-2.3.1.1-1. The Offeror’s proposal shall consist of four separate volumes: Volume I – Contract Documentation, Volume II

– Technical Proposal, Volume III – Initial Order Price Proposal and Volume IV – Past Performance Information. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table L-2.3.1.1-1: Proposal Organization

Attachment 4

FA9101-26-R-B005

Volume ITO Paragraph Number

Volume Title Maximum Number of Pages

I L-3.1 Contract Documentation

NA

II L-3.2 Technical Proposal (Including CSOW)

III L-3.3 Initial Order Price Proposal

NA

IV L-3.4 Past Performance Information

See Note

Note: For Volume IV, Past Performance, each submitted performance reference is limited to a character count (excluding spaces) of no more than 27,000 characters combined for the PPI Tool fields of “Contract Information” and “Program Details.”

L-2.3.2 Page Limitations Page / character limitations shall be treated as maximums. If exceeded, the excess pages / characters will not be read or considered in the evaluation of the proposal and the Offeror will be notified. Each page shall be counted except the following: cover pages, tables of contents, table of figures, glossaries, Organizational Conflict of Interest (OCI) Mitigation Plan, National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171 Plan, Requirements Matrix, Technical Resources, Project Schedule, Small Business Subcontracting Plan and Small Business Participation Commitment Document.

L-2.3.3 Page Size and Format This section applies to Volume II Technical Proposal only.

(a) A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches, not including displays as defined in paragraph (b) below. Pages shall be single spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12-point Times New Roman font. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. In the event the Offeror creates an ambiguity, the Government may exercise its own discretion in counting pages.

These page size and format restrictions shall also apply to responses to ENs.

(b) Legible tables, charts, drawings, graphs, diagrams, schematics, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, and plans. These displays shall be uncomplicated, legible, shall not exceed 11 x 17 inches in size, and may only be used for large tables, charts, drawings, graphs, diagrams, schematics, and figures, not for pages of text. For these displays, the text shall be no smaller than 10-point font.

L-2.3.4 Cross-Referencing

Attachment 4

FA9101-26-R-B005

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume or has not been properly cross-referenced will be assumed to have been omitted from the proposal. Cross referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Offerors must ensure that pricing information is only included in Volume III. Do NOT include any price information in Volume II.

L-2.4 DISTRIBUTION

Offerors are responsible for submitting proposals, and any modifications or revisions, so as to reach the PCO by 9 March 2026 at 1400 MST. The Government requires proposal submissions be conducted via the Procurement Integrated Enterprise Environment (PIEE) Solicitation Module, https://piee.eb.mil. No other proposal submission method is authorized. Any proposal received after the specified time or by an unauthorized method is “late.” See paragraph L-2.2 and FAR 52.215-1. Only one proposal shall be submitted, per Offeror, in response to this requirement.

To initiate the proposal submission through PIEE, the Offeror must register as a proposal manager. Training on the solicitation module is available for proposal managers through PIEE.

In the Executive Summary, primes will provide a list of all major subcontractor team members.

For purposes of proposals only, a major subcontractor is defined as a subcontractor, other than the Offeror itself, that will perform 10 percent or more of the contract scope based on labor hours or total price. To be clear, the Offeror is solely responsible for ensuring its proposal is submitted in a complete and timely manner IAW paragraph L-2.2 and FAR 52.215-1. Pre-coordination is critical to submission of a complete and timely proposal.

Document file names shall follow this naming convention: “FA910126RB005 (Prime Contractor Name) Volume # Title.”

Please provide any feedback on the use of PIEE to the PCO 14 days prior to proposal submission.

L-3.0 SPECIFIC INSTRUCTIONS

L-3.1 VOLUME I – CONTRACT DOCUMENTATION

L-3.1.1 Volume I Organization The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file(s).

L-3.1.1.1 Cover Letter The cover letter shall include the business status / categories, Offeror primary and alternate points of contact with email / phone and who is authorized to contractually obligate the Offeror, Commercial and Government Entity (CAGE) Code, Unique Entity Identification (UEI), a statement that the Offeror understands the requirements specified and will meet the requirements

Attachment 4

FA9101-26-R-B005

therein, and a statement that the Offeror does or does not take exception to any of the requirements of this solicitation. The cover letter shall include an executive summary to summarize the Offeror’s business background and current customer base, emphasizing past success and significant projects.

L-3.1.1.2 Master Table of Contents The Offeror shall include a master table of contents of the entire proposal within the Contract Documentation Volume. This master table of contents shall contain a consolidation of the individual table of contents for all volumes.

L-3.1.1.3 Solicitation / Contract Standard Form (SF) 1449 Offerors are required to complete blocks 17 and 30 of the SF1449. Ensure any amendments to the solicitation are acknowledged. An official having the authority to bind the Offeror’s company contractually must sign and date the SF1449. By submission of its offer, the Offeror agrees to all solicitation requirements, including terms and conditions, as written in the RFP.

L-3.1.1.4.1 Section B – Supplies or Services and Costs / Prices Offerors are not required to complete Section B.

L-3.1.1.4.2 Sections G – I The Offeror shall complete fill-ins as applicable.

L-3.1.1.4.3 Section K – Representations, Certifications, and other Statements of Offeror Offeror shall complete and submit this section in its entirety in addition to completing the on-line Representations and Certifications at the SAM website (https://www.SAM.gov).

L-3.1.1.4 Exceptions or Assumptions to Solicitation Requirements Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and / or specific part of the solicitation to which the exception is taken. The Offeror shall provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table L-3.1.1.4-1.

Table L-3.1.1.4-1: Solicitation Exceptions Solicitation Document

Page / Paragraph Requirement / Portion

Rationale

SOO, SF1449, etc. Applicable page and paragraph numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can / will not be met

L-3.1.2 Other Information Required

Attachment 4

FA9101-26-R-B005

L-3.1.2.1 Small Business Subcontracting Plan If other than small business, the Offeror shall submit a Small Business Subcontracting Plan IAW FAR 52.219-9, Small Business Subcontracting Plan, that also identifies the extent of the Offeror’s commitment to the participation of small business, veteran-owned small business, service-disabled veteran-owned small business, HUBZone small business, small disadvantaged business, and women-owned small business concerns, whether as JV members, teaming arrangement partners, or subcontractors. The Small Business Subcontracting Plan will be reviewed for compliance with the “DoD Checklist for Reviewing Subcontracting Plans” IAW DFARS PGI 219.705-4 and shall be made a part of the resultant contract.

L-3.1.2.2 Government Furnished Property (GFP) and Base Support Requirements The Government plans to provide the items listed in Attachment 3 – STS GFP Listing as Government Furnished Property. If the Offeror requires the use of Government furnished items other than those specified, the Offeror shall provide a listing, including quantity, federal stock number, nomenclature, date needed and duration of availability, rental value per FAR 45.1 and 45.2, reason for need, and cross reference to the applicable SOO section. The Offeror shall also provide the written authorization from the cognizant ACO, as applicable. The Offeror shall supply this information in the format shown in Table L-3.1.2.2-1

Table L-3.1.2.2-1: Example Required Information for Using GFP / Base Support Quantity Federal

Stock No.

Nomen-clature

Duration of Need

Rental Value

Reason for Need

Cross Ref.

to Cost Prop

2 EA FS156-09-

ACG-1372

Time Counter

1 Oct 25 – 30 Sep 26

$1,000 Needed to calibrate 5 MHz/1pps

SATCOM

simulator offset

Volume IV, pages 23- 27, paragraph s A-C

L-3.1.2.3 OCI Plan This acquisition may create actual or potential conflicts of interest for Offerors, teaming partners, and / or prospective subcontractors. In assessing and addressing conflicts of interest, the Government will follow the guidance in FAR Subpart 9.5. Offerors are responsible for ensuring that both it and its proposed subcontractors are not restricted from participating in the Survivability Test Stand (STS) contract due to an OCI.

An Offeror’s failure to provide adequate information to avoid or mitigate an OCI may cause the Offeror to be determined non-responsible and relieves the Government of any further responsibility to resolve OCI issues. See FAR 9.504(e). Notices to Offerors of OCI and their responses thereto are not negotiations or discussions as those terms are used in FAR 15.306(d).

The Offeror must submit a Mitigation Plan that addresses all potential conflicts in adequate detail for the PCO to determine whether an OCI exists or has been mitigated. If an Offeror determines

Attachment 4

FA9101-26-R-B005

that an actual or potential OCI does not exist, it shall include a statement to that effect as part of its plan. The OCI Mitigation Plan shall specifically address the OCI disclosures required in this section and explain how the Offeror is in full compliance with the STS OCI provisions (see DAFFARS 5352.209-9001, Potential Organizational Conflict of Interest (Jul 2023)). As part of its Mitigation Plan, the Offeror must identify which contracts or subcontracts it will continue to support and those it intends to terminate to allow to lapse to eliminate any conflicts. The plan shall also address other OCI resolution and mitigation measures to include the divestment of business units. The OCI Mitigation Plan will be reviewed in conjunction with the PCO’s Responsibility Determination prior to award.

L-3.1.2.4 NIST SP 800-171 Plan IAW DFARS 252.204-7019 Notice of NIST SP 800-171 DoD Assessment Requirements, all offerors shall have a current assessment (not more than three years old) for each covered contractor information system that is relevant to the offer. Offerors with a summary level score of less than 110 shall include in Volume I associated plan(s) of action developed IAW NIST SP 800-171 and the date that all requirements are expected to be achieved.

An Offeror’s failure to provide adequate information may cause the Offeror to be determined non-responsible. Notices to Offerors of NIST SP 800-171 assessment and their responses thereto are not negotiations or discussions as those terms are used in FAR 15.306(d).

L-3.2 VOLUME II – TECHNICAL PROPOSAL

L-3.2.1 Volume II Organization

The Technical Proposal should be specific and complete. Legibility, clarity, and coherence are very important. Offerors’ responses will be evaluated against the Technical subfactors. Provide as specifically as possible the actual methodology you would use for accomplishing/satisfying the subfactors. Address your technical solution for meeting or exceeding the Government’s minimum performance or capability requirements of each technical subfactor. All the requirements specified in the RFP are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the RFP. Do not merely reiterate the objectives or reformulate the requirements specified in the RFP.

The Technical Volume shall be organized according to the following general outline:

Technical Factor:

Subfactor 1.1 Technical Approach Subfactor 1.2 Management Approach Subfactor 1.3 Integration Approach

L-3.2.2 Subfactor 1.1: Technical Approach Each Offeror shall submit its technical solution and conceptual design that demonstrates its technical understanding and approach to meet the requirements of the SOO. The technical approach shall address the Offerors’ technical solution for meeting or exceeding the

Attachment 4

FA9101-26-R-B005

Government’s minimum (threshold) performance requirements and discuss how the requirements will be accomplished IAW applicable laws, regulations, and governing documents.

The proposal shall be clear and concise with clearly annotated references to supporting details.

The Offeror shall address each requirement in the SOO, SOO Attachment 1, Use Cases, and SOO Attachment 2, Key Performance Parameters/Key System Attributes.

A SOO is provided as Attachment 1 to the solicitation. This SOO along with the SOO Attachment 1, Use Cases, and SOO Attachment 2, Key Performance Parameters/Key System Attributes represents the Government’s minimum objectives for the STS project. Offerors shall use the SOO and attachments to propose a Contractor Statement of Work (CSOW) which expands upon these minimum objectives to the extent necessary to conduct this acquisition. The proposed CSOW shall define the tasks required for the STS Preliminary Design Review (PDR) ensuring all minimum requirements of the Government provided SOO and attachments have been addressed. The proposed CSOW shall consist of tasking statements. Each tasking statement shall reference the CDRL items which will be delivered by that task, as applicable. Updated CSOW will be required with Critical Design Review (CDR) proposal.

CDRL Title Details A001 Monthly Status Report Due by the 5th of each month and does not include status of funds A002 Project Management Plan First plan is due within 90 days After Receipt of

Order (ARO) and then annually; data from the plan will be incorporated with Gov’t plan updates

A003 Systems Engineering Management Plan

First plan is due within 60 days ARO and then annually; data from the plan will be incorporated with Gov’t plan updates

A004 Risk Management Plan First plan is due within 60 days ARO and then annually; data from the plan will be incorporated with Gov’t plan updates; plan shall include a risk register and top cost, schedule and performance risk

A005 Risk Management Status Report

First report is due 100 days ARO and then updated quarterly; this provides quarterly updates to the risks identified in CDRL A004 and being tracked

A006 Life Cycle Support Plan Plan is due with the PDR documentation and shall include sparing data, maintenance requirements and other life cycle considerations for each design

A007 Safety Plan Plan is due with the PDR documentation and shall include safety considerations while determining the designs

A008 Configuration Plan Plan is due with the PDR documentation and includes the details of the documents supplied

A009 Work Breakdown Structure

(WBS)

Initial WBS is due 30 days ARO and at PDR. This includes the contractors’ WBS structure and is used in the Integrated Master Schedule

Attachment 4

FA9101-26-R-B005

A010 Integrated Master Schedule

(IMS)

Due by the 5th of each month and is delivered with the status report. This product correlates to the WBS (A010), Status Report (A001) and Software Documentation (A013)

A011 Presentation Material Contractor shall submit briefing/presentation packages no later than (NLT) 5 business days prior to the scheduled events/meetings. The events are detailed in the CDRL

A012 Software Development Plan Due NLT two weeks ARO and updated with each Program Management Review. This includes details on the subcontractors’ plans and progress updates.

A013 Software Documentation Due IAW the IMS software updates and delivery dates/updates are by mutual agreement

A014 Meeting Minutes Due within five business days following formal meetings/conferences such as PMRs, Kick-FF, SRR, Design Reviews

A015 Test Plans and Reports Due 30 days before planned system, component, and sub-component design evaluation tests, engineering tests, preliminary qualification tests, formal qualification tests, operational tests and acceptance test events

A016 Scientific and Technical Reports (Design Drawings and Design Review Packages)

Contractor shall deliver draft design drawings and drawing review packages five business days prior to SRR, PDR, CDR, Initial Operating Capability (IOC) and Final Operating Capability (FOC). Final design drawings and design review packages are due 10 business days after the review and included with the minutes (A014). Test reports are due 30 days after planned system, component, and sub-component design evaluation tests, engineering tests, preliminary qualification tests, formal qualification tests, operational tests and acceptance test events.

A017 Training Documentation Contractor shall deliver Training Data Products for the maintenance and operations of the STS system in conjunction with IOC or FOC (as appropriate).

The products and manuals shall be delivered in coordination with the in-person training identified on the IMS (A010).

L-3.2.3. Subfactor 1.2: Management Approach

Attachment 4

FA9101-26-R-B005

The Offeror shall submit a sound resource management approach that thoroughly describes anticipated subcontracts and how to manage them, as well as how the Offeror plans to recruit and retain qualified personnel who have the knowledge, experience, training, and technical expertise/certification/security clearances commensurate with the requirements for the design, development, and installation of the STS. The resource management approach shall include a complete personnel staffing plan that defines personnel qualification requirements, roles/responsibilities, relevant experience, and any special skills required.

The Offeror shall submit a Small Business Participation Commitment Document (SBPCD) describing its methodology to meet the Small Business Participation Commitment requirements as outlined in M-2.2.5.1; specifically describing how the Offeror will demonstrate a sound plan to meet the Minimum Quantitative Requirement (MQR). For evaluation purposes of the MQR, use 10% of $100M for the participation of small businesses in performance of the contract, whether as a JV, teaming arrangement, or subcontractor. A template for this document is provided as Attachment 4.8. Binding commitments in the SBPCD will become enforceable contractual requirements.

L-3.2.4. Subfactor 1.3: Integration Approach The Offeror shall submit a sound integration approach and strategic plan for STS that thoroughly describes how they will integrate all components and subcomponents for the STS system. The proposal shall address how the Offeror will effectively plan, implement, schedule, and execute the following:

(1) A business model that demonstrates a sound understanding of the STS technology diversity required to meet the Use Cases, Key Performance Parameters, Key System Attributes detailed in SOO Attachments 1 and 2.

(2) A description of developmental, test, and manufacturing resources required as they relate to the STS project.

(3) List of major components/subcomponents and how they will manage their successful integration to form a complete system.

L-3.2.6 Data Assertions If the Offeror makes any assertions when completing Section K (DFARS 252.227-7017(d)), the Offeror shall identify each assertion correlated to each individual item of intellectual property to be delivered, provided, or otherwise furnished to the Government during contract performance.

The Offeror shall do so by adding a parenthetical after its identification of each individual item of "Technical Data or Computer Software to be Furnished With Restrictions" in its completed DFARS 252.227-7017 representation that identifies the specific part of the contract (e.g., CDRL number, SOW paragraph) that will require the awardee to deliver, provide, or otherwise furnish that intellectual property to the Government

L-3.3 VOLUME III – INITIAL ORDER PRICE PROPOSAL

L-3.3.1 Volume III Organization

Attachment 4

FA9101-26-R-B005

The Initial Order Price Proposal Volume shall be organized according to the following general outline:

Table of Contents Price Narrative Attachment 4.7, Initial Order Pricing Sheet

L-3.3.2 Price Information This section is to assist you in submitting data other than certified pricing data that is required to evaluate the completeness, reasonableness, realism, unbalanced pricing, and total evaluated price (TEP) of your proposed price for the initial order. Note that unreasonably high proposed prices, initially or subsequently, may be grounds for eliminating a proposal from competition. Offers should be sufficiently detailed to demonstrate completeness and reasonableness. The burden of proof for credibility of proposed prices rests with the Offeror. Failure to comply with the RFP requirements for pricing information may result in an adverse assessment of an Offeror’s proposal, which may reduce or eliminate its chance for being selected for award. When an Offeror fails to completely and accurately provide all pricing information required by the RFP, the Offeror bears full responsibility for any adverse impact upon the evaluation of its proposal.

For proposal purposes, the estimated start date for the initial order is 15 June 2026.

Data beyond that required by this instruction shall not be submitted, unless the Offeror considers it essential to document or support its price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price Volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

L-3.3.3 General Instructions

L-3.3.3.1 The Initial Order Price Proposal Volume is comprised of two parts: (1) a price narrative which includes the Offeror’s basis of estimate, proposed additive rates, assumptions, basis for the assumptions, and other details required to assist the Government in performing a thorough evaluation of the Offeror’s proposed initial order price and (2) an individual price (rounded to the whole dollar) for the initial order using Attachment 4.7, Initial Order Pricing Sheet. Offers shall be complete, reasonable and not unbalanced.

L-3.3.3.2 The PCO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the PCO will review this determination and if, in the PCO’s opinion, adequate price competition exists no additional cost information will be requested and certification under FAR 15.406-2 will not be required. IAW FAR 15.403- 1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. If, after receipt of proposals, the PCO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit certified cost or pricing data.

Attachment 4

FA9101-26-R-B005

L-3.3.3.3 Attachment 4.7, Initial Order Pricing Sheet contains all the relevant inputs and outputs to populate a valid price proposal. While Offerors are permitted to make minor adjustments to meet the needs of their proposal procedures, ultimately it is the responsibility of the Offeror to submit a valid price proposal. Further, tab “Labor Categories” is required for completion for the purposes of evaluating the realism of proposed rates which may be used in the basis for future negotiations for the requirements of this solicitation.

L-3.3.4 Data The cost of producing data will not be separately priced in Section B of the solicitation. The cost required to produce each CDRL should be included in the Offeror’s proposed price for each CLIN at the order level.

L-3.4 VOLUME IV – PAST PERFORMANCE INFORMATION

L-3.4.1 Volume IV Organization The Past Performance Volume shall be organized according to the following general outline:

Table of Contents Summary – Not to exceed two pages. (See L-3.4.2) Past Performance References (See L-3.4.3.1) PPI Submission (See L-3.4.3.2) Relevant and Recency Determination (See L-3.4.3.4) Organizational Structure Change History (See L-3.4.3.6) Consent Letters – Consent letters executed by each JV partner, major subcontractor, and key management personnel authorizing release of adverse PPI to the offeror can respond to such information. A sample consent letter is provided as Attachment 4.5.

Client Authorization Letters – Client authorization letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the offeror’s performance. A sample consent letter is provided as Attachment 4.4.

List of Questionnaire Recipients (See L-3.4.3.2)

L-3.4.2 Summary Describe the roles of Offerors and all subcontractors, teaming partners, or JV partners requiring PPI IAW paragraph L-3.4.3.1.

L-3.4.3 PPI Sheets (See Attachment 4.1, PPI Tool)

L-3.4.3.1 Number of PPI References Offerors shall submit information in the PPI Tool –[see Attachment 4.1 - STS Past Performance Information (PPI) Tool Instructions] Relevancy Matrix, Consent Letters, Authorization Letters, and List of Questionnaire Recipients on contracts considered most relevant in demonstrating the

Attachment 4

FA9101-26-R-B005

ability to perform technical operations. This information is required for Offerors, major subcontractors, or JV partners considered relevant to overall successful performance. Offerors may submit no more than five recent and relevant contracts for the prime contractor and no more than three for each major subcontractor. For the purpose of proposals only, a major subcontractor is defined as a subcontractor that is awarded a subcontract that equals or exceeds 10 percent of the value of the contract, IAW DFARS 209.571-1, Definitions. A PPI reference is defined as a single contract. A single Order from an IDIQ contract will be considered a single contract reference for evaluation purposes. A basic IDIQ contract including its multiple Orders may be submitted as a single PPI reference. If a basic IDIQ is submitted as a reference, individual orders from that contract should not also be submitted as individual references; past performance will be reviewed for the overarching contract, not the individual orders. If the prime is a JV, Offerors may submit no more than three references per JV partner. Offerors are hereby notified that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the evaluation of past performance.

L-3.4.3.2 PPI Submission Offerors must use the PPI tool, which the offeror shall request by email to the contract specialist, charles.king.42@us.af.mil or brett.moore.6@us.af.mil, for their electronic proposal submittal of relevant past performance contract information. Offerors shall provide the pages generated from this tool as part of their Past Performance Volume. Offerors shall save the PPI database file as Offeror name-volume name (PPI)-STS.mdb (e.g., XYZ Company-Past Performance Volume- STS.mdb) to submit as part of the electronic copy of the Past Performance Volume. Once complete, PPI sheets and past performance questionnaires (PPQs) will be treated as fair opportunity selection information IAW FAR Part 3.104.

Offerors shall send PPQs on each identified contract to the points of contact for that contract. If the identified contract was a government effort, please send to the Program Manager and PCO.

This questionnaire and cover letter is contained in Attachment 4.2 - STS Past - Present Performance Questionnaire (PPQ) and Attachment 4.3 - STS PPQ Cover Letter. Provide a list of PPQ recipients to include points of contact (POCs) and phone numbers. Responses to PPQ are to be provided directly to the STS PCO no later than the due date of proposals.

PPI concerning subcontractor and teaming / JV partners cannot be disclosed to a private party without the subcontractor’s or teaming / JV partner’s consent. Because a prime contractor is a private party, the Government will need that consent before disclosing subcontractor / teaming / JV partner past performance assessments to the prime during exchanges. Therefore, the Offeror shall submit a consent letter executed by each teaming / JV partner and major subcontractor authorizing release of adverse PPI to the Offeror, so the Offeror can respond to such information.

For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror's performance.

L-3.4.3.3 Relevant Contracts and Recency Determination Offerors shall submit information in the PPI tool under the Program Details Tab on recent contracts deemed relevant in demonstrating the ability to perform the full range of capabilities IAW the STS SOO requirements and explain how / why the referenced contracts are relevant.

mailto:charles.king.42@us.af.mil mailto:brett.moore.6@us.af.mil

Attachment 4

FA9101-26-R-B005

The prime contractor may submit up to five recent contracts, and JV partners may submit up to three recent contracts per partner. Also provide PPI on up to three recent contracts for each major subcontractor partner. To be recent, the effort must be ongoing for at least one year or must have been completed during the past five years from the date of issuance of the RFP.

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and what aspects of the proposed effort in which they relate. This shall include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the Offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an Offeror has overcome past problems. Categorize the relevant information into the specific Technical subfactors and Price factor used to evaluate the proposal. As noted above in Table 2, these fields in the PPI Tool shall not exceed 27,000 characters. If the character limit is exceeded or if the information is not included in the identified fields, this information will not be considered.

L-3.4.3.4 Relevancy Matrix The Offeror shall provide a completed relevancy matrix (see Attachment 4.6 - STS Relevancy Matrix). Provide no more than five recent and relevant contracts for the prime contractor and no more than three for each major subcontractor. If the prime is a JV, provide no more than three references per JV partner. The relevancy matrix and other PPI will be used to establish the relevance of present and past efforts. For submitted references (efforts cited), please place a check mark into the rows for which the reference is applicable according to the row headings (which represent the evaluation factors and subfactors).

L-3.4.3.5 Organizational Structure Change History Many companies have acquired, have been acquired by, or otherwise merged with other companies or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant current or past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include a "roadmap" describing all such changes in the organization of the Offeror’s company, JV partner(s), and / or proposed major subcontractors.

As part of this explanation, show how these changes impact the relevance of any efforts identified for past performance evaluation / performance confidence assessment. Since the Government may consider present and PPI provided by other sources as well as that provided by the Offeror(s), the Offeror’s "roadmap" should be both specifically applicable to the efforts identified and general enough to apply to efforts on which the Government receives information from other sources.

Attachment 4

FA9101-26-R-B005

L-3.4.3.6 Client Authorizations Letters Client Authorization letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the Offeror’s performance. A sample Client Authorizations letter is provided as Attachment 4.4 - STS Client Authorization Letter.

L-3.4.3.7 Subcontractor Consent Letters Consent letters executed by each JV partner and major subcontractor authorizing release of adverse PPI so the Offeror can respond to such information. A sample subcontractor consent letter is provided as Attachment 4.5 - STS Subcontractor Consent Letter.

L-3.4.4 No Applicable PPI If an Offeror has no recent or relevant PPI, it should so state that in this volume. However, the Government reserves the right to determine whether any relevant PPI exists.

Attachments

4.1 PPI Tool

4.2 Past Performance Questionnaire (PPQ)

4.3 PPQ Cover Letter

4.4 Client Authorization Letter

4.5 Subcontractor Consent Letter

4.6 Relevancy Matrix

4.7 Initial Order Pricing Sheet

4.8 Small Business Participation Commitment Document