Attachment 3 - Instructions Conditions and Notices to Offerors.pdf

Source Selection Information – See FAR 2.101 and 3.104

Section L - Instructions, Conditions and Notices to Bidders (Addendum to FAR 52.215-1)

GENERAL INFORMATION

L1.0 Objectives.

The Government intends to award a single five-year Basic with one six-month option Indefinite Delivery/Indefinite Quantity (ID/IQ) contract for Contractor Logistic Support (CLS) sustainment services on the AN/FPS-117 radar program. Award will be made to the Offeror that provides the best value to the Government In Accordance With (IAW) Section M, Evaluation Factors for Award. At a minimum, the Government intends to obligate funds at time of award utilizing the following base period Contract Line Item Numbers (CLINs):

a. 0001 Data

b. 0002 Program Management

c. 0004 Engineering Technical Support Services

d. 0007 ACC Emergency Depot Level Maintenance (EDLM)

e. 0009 Air National Guard EDLM

f. 0024 Shipping

g. 0025 Travel

h. 0026 Diminishing Manufacturing Sources and Material Shortages (DMSMS)

L1.1 General.

L1.1.1 This section provides guidance for preparing proposals as well as instructions on the format and content of the proposal. The proposal must include all data and information requested and must be submitted in accordance with (IAW) these instructions; incomplete proposals may be considered non-responsive and determined not eligible for award. Taking exception to or failing to meet any of the requirements specified in this solicitation may result in the proposal being found unacceptable. Do not merely reiterate the Performance Work Statement (PWS) or reformulate the requirements specified in the solicitation. In no case shall words like “we will comply with the requirements of the contract,” or equivalent statements, be acceptable to meet the requirements of this Request for Proposal (RFP). If a joint venture arrangement exists for this acquisition, the Offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission.

Offerors shall submit only one proposal for the AN/FPS-117 CLS program as the Government will review only one proposal per Offeror. The Government will not provide reimbursement for any cost incurred during proposal submission. Proposals must be complete, self-sufficient, and respond directly to the requirements of the solicitation.

Any commitments made in the proposal may become part of the resultant contract.

L.1.1.2 Offerors are advised that the Government may incorporate all beneficial aspects of the awardee’s proposal and all above threshold (minimum) attributes, performance levels, or capabilities into the awarded contract document.

L1.2 Proposal Format and Content.

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

L1.2.2 Proposals shall be submitted in Microsoft Word or searchable PDF format (MS Office 2016 compatible). The proposal when printed must fit on 8.5 x 11 size paper, in 12 point, Times New Roman, single line spacing, with one-inch margins. Page limits apply to each side of a page if printed double-sided. Tables, charts, graphs and figures shall be used when necessary to depict organizations, systems and layout, implementation schedules, plans, etc. and shall be restricted to the 8.5 X 11 size paper and shall be no smaller than 10 point, Times New Roman. At a minimum, each volume shall be submitted as a separate file.

L1.2.3 Titles and contents of the volumes shall be provided as defined in Table L.1. If page limits in Table L.1 are exceeded, the excess pages will not be read or considered in the evaluation of the proposal. The following will be exempt from page limitations for the RFP: Requested attachments, Cover sheets; Table of Contents; Lists of Tables;

Lists of Drawings; Glossaries; Acronym List; Compliance Matrix; Subcontractor Consent Letters; and Client Authorization Letters.

Table L.1

PARA. VOLUME TITLE COPIES PAGE LIMIT

L1.13 Cross Reference Matrix 1 No page limit

L-2 Volume I – Factor 1, Cost/Price Proposal 1 No page limit

L2.2 Total Evaluated Price (TEP) No page limit

L2.3 Cost or Pricing Information Requirements No page limit

L2.3.4.2.3 Pre-award Survey for Prospective Contractors No page limit

L2.4 Professional Employee Compensation Plan (PECP) No page limit

L-3 Volume II – Factor 2, Technical Proposal 1 Limit to 30 pages

L3.2 Subfactor 1: Technical Knowledge and Experience Contractors discretion within L-3 page limit

L3.3 Subfactor 2: Logistics and Asset Availability Contractors discretion within L-3 page limit

L3.4 Subfactor 3: Quality Control and Training Contractors discretion within L-3 page limit

L3.5 Subfactor 4: Contractor Resources and Stakeholder Engagement Contractors discretion within L-3 page limit

L-4 Volume III – Factor 3, Past Performance Proposal 1 Limit to 25 pages

L4.1.1 Early Proposal Information No page limit

L4.1.2 Past Performance Summary No page limit

L4.1.3 Past Performance Information Sheet Summary Table No page limit

L4.1.4 Past Performance Information Sheets (Attachment

8) No page limit

L4.1.5 Small Business Compliance In Past Performance No page limit

L4.1.6 Subcontractor/Teaming Member Consent Letter No page limit

L4.1.7 Adverse Past Performance or Discrepancy No page limit

L-5 Volume IV – Factor 4, Small Business Participation Submission No page limit

L5.1.2 Format and Specific Content No page limit

L-6 Volume V - Factor 5, Administrative and Responsibility Material 1 No page limit

L6.1.2 Small Business Subcontracting Plan No page limit

L6.1.3 Contract Forms and Certifications No page limit

L6.1.4 Exception to Solicitation Requirements No page limit

L6.1.5 Contractor Team Arrangement No page limit

L6.1.6 Authorized Offeror Personnel No page limit

L6.1.7 Organizational Conflicts of Interest No page limit

L1.3 Electronic Proposal Submission.

L1.3.1 Offeror shall submit its proposal electronically in Procurement Integrated Enterprise Environment (PIEE) (https://piee.eb.mil/) via the Solicitation Module. For instruction on posting an offer, please refer to the “Submitting an Offer” instruction within the Solicitation Module under the “Documentation” selection at the top:

https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf. It is the Offeror’s responsibility to follow the registration instruction found on the PIEE website. It is advised that all potential prime Offerors and their subcontractors ensure the proper company points of contact are registered in the site based on their CAGE codes and have the proper roles assigned well in advance to the solicitation closing date. Subcontractors or teaming partners are only required to register in PIEE if they want to submit their proprietary proposal information separate from the prime Offeror.

Documents submitted by the subcontractor or teaming partner directly to the Government must have the prime contractor’s name, CAGE, and RFP number on the first page of the document.

Large File Notice: Follow PIEE instructions for uploading files larger than 10MB. If needed, break the file down into smaller sections in order to upload it to the system. PROPOSALS SUBMITTED THROUGH OTHER MEANS, NOT SPECIFIED, WILL NOT BE ACCEPTED. Clearly mark the description for each uploaded document by Offeror Name, Solicitation Number and Volume number. Proposals submitted electronically will be considered late unless all proposal documents are transmitted to and successfully uploaded to PIEE prior to the closing date and time for receipt of proposals (See L1.4). The Government is not responsible for technical difficulties associated with the transmission of any electronic files to the website. The Offeror is responsible for ensuring the successful electronic delivery of its proposals. Offerors are encouraged to submit proposals with sufficient time to ensure all proposal documents are successfully uploaded to the website prior to the closing date and time. It is also the Offeror’s responsibility to confirm receipt of proposals and all electronic communications.

Screen shots of the submission should also be taken to validate a submission was accepted in the PIEE system.

Please be advised timelines are determined by the date and time an Offeror’s proposal is received by the Government, not when an Offeror attempted transmission.

L1.3.2 In the event of a PIEE System outage within 24 hours of the proposal due date that prevents the Offeror from submitting a timely proposal, the Contractor shall immediately notify the Contracting Officer. This notification shall occur prior to the proposal submission deadline and shall be made in writing. The notification may be in conjunction with verbal notification, but verbal notification alone shall not be sufficient. The Offeror shall obtain written approval from the Contracting Officer to submit the proposal via an alternate method. The only alternative methods the Government will consider is either using email or a submission by mail, using separate CD-Rs to segregate proposal volumes. Offerors will be notified which method will be allowed in the event of a PIEE system outage. If this is required, the Government will provide a minimal extension window (no more than 2-3 business days) and a mailing address for delivery. In the event the Contractor does not provide notification to the contracting officer until after the closing date and time, the contracting officer will follow the procedures identified in the Federal Acquisition Regulation (FAR) 15.208.

L.1.3.3 Offerors submitting Early Proposal Information in accordance with L2.3.4.2.3 and L4.1.1 are requested to transmit documents via e-mail. E-mails shall be no larger than 10MB and sent to the following email addresses:

christopher.jarman@us.af.mil and cameron.tucker.6@us.af.mil. Emails used to transmit proposal information must include “Source Selection Information – See FAR 2.101 and 3.104 “Controlled Unclassified Information” in the header of the document and solicitation number in the subject line of the email.

L1.4 Proposal Due Date/Time: 28 July 2025 / 1:00 PM MST

L1.4.1 Late proposals will only be considered IAW FAR 15.208

L1.5 Proposal Validity.

L1.5.1 All proposals submitted in response to this solicitation shall be binding on the Offeror for a minimum of 365 days. The Offeror shall make a clear statement in Section A of the proposal documentation volume the proposal is valid for a minimum of 365 days from solicitation closing.

https://piee.eb.mil/ https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf mailto:christopher.jarman@us.af.mil mailto:cameron.tucker.6@us.af.mil

L1.6 Discrepancies.

L1.6.1 If an Offeror believes the requirements in these instructions contain an error or omission the Offeror shall immediately notify the Procuring Contracting Officer (PCO) and Contracting Specialists (CS) in writing with supporting rationale.

L1.7 Government Contract Files.

L1.7.1 IAW FAR Subpart 4.8, Government Contract Files, the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

L1.8 Oral Presentations.

L1.8.1 Oral presentations will not be allowed.

L1.9 Point of Contact.

L1.9.1 Exchanges of source selection information between the Government and Offerors will be controlled by the PCO and the CS. Exchanges of source selection information after submission of the initial proposal packages between the Government and Offerors will be controlled by the PCO or CS. 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”, “Controlled Unclassified Information” in the subject line of the email. The PCO and the CS are the sole points of contact for this acquisition. Offeror shall address any questions or concerns they may have to the PCO or CS.

Contracting Officer Contracting Specialist

AFLCMC/HBDK AFLCMC/HBDK

Attn: Chris Jarman Attn: Cameron Tucker 6039 Wardleigh Rd 6039 Wardleigh Rd Hill AFB, UT 84056 Hill AFB, UT 84056 christopher.jarman@us.af.mil cameron.tucker.6@us.af.mil

L1.10 Amendments to Solicitation.

L.10.1 If this RFP is amended, all terms and conditions that are not amended remain unchanged. If the RFP is amended prior to proposal delivery, Offerors shall acknowledge each amendment by signing and returning the front page of each amendment with the proposal submission. If the RFP is amended after proposal submission, Offerors shall respond by the date and time specified in the amendment to include a signed front page of the amended RFP.

Offerors who fail to acknowledge RFP amendment(s) may be considered non-responsive and may be eliminated.

L1.11 Proposal Withdrawal.

L1.11.1 Proposals may be withdrawn by written notice received at any time before award. Proposals may also be withdrawn in person by an Offeror or an authorized representative, if the identity of the person requesting the withdrawal is established and the person signs a receipt for the proposal before award.

L1.12 Title Page.

L1.12.1 The title page of each volume must show:

1) Solicitation Number

2) Company name, address, Commercial and Government Entity (CAGE) Code and Unique Entity Identification (UEID) Number.

3) Primary point of contact name, telephone number and email address

4) Volume number and name (e.g., Volume I, Price)

L1.13 Cross-Reference Matrix.

L1.13.1 Each volume shall be written on a stand-alone basis so 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 mailto:christopher.jarman@us.af.mil mailto:cameron.tucker.6@us.af.mil in its designated volume will be assumed to have been omitted from the proposal. The Offeror shall fill out the cross-reference matrix in the RFP Attachments indicating where in its proposal the information can be found as it relates to the RFP. The cross-reference matrix will be utilized as a tool to show critical interrelationships and dependencies among the technical requirements document Performance Work Statement (PWS), Section L (Instructions, Conditions, and notices to Offerors), and Section M (Evaluation Factors for Award). The cross-reference matrix will help an Offeror ensure it has responded to all the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. Additionally, to the extent the matrix discloses details as to the manner by which the Government intends to evaluate the Offeror’s proposals for award, Section M references in the matrix are for informational purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with Section M of the solicitation.

L1.14 Indexing.

L1.14.1 Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume.

Tab indexing shall be used to identify sections.

L1.14.2 Include an indexed list of tables and figures. Tables and figures do not count against the page limitations for their respective volumes.

L1.14.3 Glossary of Abbreviations and Acronyms – Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

L1.15 Debriefings:

L1.15.1 Pre-Award Debriefings

L1.15.1.1 The PCO will promptly notify Offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with FAR 15.505.

L1.15.2 Post Award Debriefings

L1.15.2.1 The PCO will notify unsuccessful Offerors included in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing.

L1.15.2.2 Successful Offerors will be notified of the source selection decision and may also request a debriefing IAW the requirements of FAR 15.506.

VOLUME I – FACTOR 1, COST/PRICE PROPOSAL

L2.1 General Instructions:

In the price Volume, the Offeror shall provide the following information in addition to the pricing in the Pricing Matrix Workbook (Section J Attachment 6). These instructions are to assist you in submitting information required to evaluate the reasonableness, balance and realism of the proposed pricing.

As defined in Section M of the RFP, which will be assessed from the information provided in this volume, the pricing criteria will be as follows:

1) Completeness

2) Reasonableness

3) Balance

4) Realism

5) Total Evaluated Price (TEP)

6) Cost or Pricing Information Requirements

7) Professional Employee Compensation Plan (PECP)

Offerors should review Section M criteria to ensure the minimum requirements are met.

L2.2 Total Evaluated Price (TEP):

L2.2.1 Offerors shall input all fully burdened rates (excluding profit/fee) for all labor categories and years into the pricing matrix worksheet (Section J Attachment 6), following the provided instructions. Fully burdened rates shall include all base labor rates for each labor category, as well as fringe benefits, overhead, G&A, and FCCOM.

Additionally, specify the proposed fee and profit rates applicable to Cost-Plus Fixed Fee (CPFF) and Firm Fixed Price (FFP) pricing arrangements. Any profit/fee rates associated with alternative pricing arrangements will be negotiated and evaluated separately on the applicable future contracting action. These proposed rates shall be utilized as a Not To Exceed (NTE) ceiling for proposing future contracting actions and modifications within the scope of this acquisition. All proposed rates are contractually binding.

L2.2.2 Offerors shall also input pricing for the base year and each option year for the following CLINs within the “Awardable Task Order” tab included in Attachment 6, Pricing Matrix Worksheet. Pricing these CLINs will be based off the requirements outlined in Attachment 11, “Awardable Task Order PWS”.

a. 0002-5002 Program Management

b. 0004-5004 Engineering Technical Support Services

c. 0007-5007 ACC Emergency Depot Level Maintenance (EDLM)

d. 0009-5009 Air National Guard EDLM

e. 0026-5026 Diminishing Manufacturing Sources and Material Shortages (DMSMS)

L2.2.3 Submit a completed Pricing Matrix Worksheet in Volume I – Factor 1, Price, in a Microsoft Excel editable format (non-PDF format).

L2.2.4 The TEP will be calculated by applying notional hours to the proposed labor and profit/fee rates provided in the “Labor Rate Matrix” and adding the values proposed in the “awardable Task Order” tab.

While the specific notional hours used for evaluation will not be disclosed to maintain a fair competitive environment, they represent a reasonable estimate of the overall level of effort anticipated for the contract. Proposed rates will be evaluated based on their competitiveness against this estimated workload.

L2.3 Cost or Pricing Information Requirements:

L2.3.1 IAW FAR 15.402, 15.403-1(b) and 15.403-3(a), information other than certified cost or pricing data may be required to support price reasonableness. If after receipt of proposals, the CO determines there is insufficient information available to determine the reasonableness of the proposed pricing the Offeror may be required to submit additional information other than certified cost or pricing data. If, during the source selection process, the CO determines adequate competition no longer exists and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submitted additional cost and pricing data in accordance with FAR clause 52.215-20.

L2.3.2 Rounding:

L2.3.2.1 All dollar amounts provided shall not extend beyond two decimal places.

L2.3.3 Pricing Assumptions:

L2.3.3.1 Summarize all significant pricing assumptions, scope limitations and/or qualifications of the Volume I – Factor 1, Cost/Price Proposal.

L2.3.4 Estimating Techniques and Methods:

L2.3.4.1 Offerors shall use generally accepted estimating techniques to develop their estimates for the proposed rates.

L2.3.4.2 Accounting System

L2.3.4.2.1 The Offeror shall indicate whether it has Government approval of its accounting system and if so, provide evidence of such approval.

L2.3.4.2.2 The Offeror shall also identify any deviations from its standard procedures in preparing this proposal.

L2.3.4.2.3 If the Offeror does not have a Government accepted accounting system, you must complete and submit the Pre-award Survey for Prospective Contractors (Attachment 7 to the solicitation). To avoid delays, we strongly encourage you to submit the Pre-award Survey as soon as possible. Refer to Section L1.3.3 of this solicitation for instructions on submitting information prior to your formal proposal.

L2.3.4.2.4 The Offerors shall provide cognizant DCAA and DCMA office contact information.

L2.3.5 Contract Data Requirements Lists (CDRLs)

L2.3.5.1 CDRLs will not be separately priced. Cost required to produce each CDRL should be included in the Offeror’s proposed labor in accordance with the applicable order.

L2.4 Professional Employee Compensation Plan (PECP) The professional employee compensation plan required by FAR 52.222-46 shall be submitted as a part of Volume I.

The plan shall set forth salaries and fringe benefits proposed for professional employees and include supporting information, such as recognized national and reginal compensation surveys and studies of professional, public and private organizations, used in establishing the total compensation structure. This will enable the Government to review the proposed salaries and fringe benefits in accordance with FAR 52.222-46. Note: The compensation plan pertains to the Offeror only. However, if a populated joint venture is formed (a joint venture in which the employees are employed by the joint venture itself and not by any individual joint venture partner), the joint venture must submit the professional employee compensation plan for the joint venture. If an unpopulated joint venture is formed, each individual joint venture partner must submit its own professional employee compensation plan.

VOLUME II – FACTOR 2, TECHNICAL PROPOSAL

L3.1 General Information:

L3.1.1 The Technical Volume shall be clear, specific, complete and include sufficient detail for effective evaluation.

Legibility, clarity, and coherence are very important. The Offeror’s responses will be evaluated against the Technical Subfactors defined in Section M, Evaluation Factors for Award. Offerors shall review Section M criteria to ensure the minimum requirements are met. Provide as specifically as possible the actual methodology the Offeror would use for accomplishing/satisfying each subfactor. There will be no reference to rates or price in this volume.

Offerors shall assume the Government has no prior knowledge of their experience or certifications and will base its evaluation on the information presented in the Offeror’s proposal. All the requirements specified in the solicitation are mandatory. By the Offeror’s proposal submission, the Offeror is representing the company/firm will perform ALL the requirements specified in the solicitation (including PWS); it is not necessary or desirable to state this specifically in the proposal.

L3.1.2 The Offeror’s approach shall address all requirements IAW the paragraphs and sub-paragraphs of the PWS unless otherwise noted.

L3.1.3 Adequate Responses:

L3.1.3.1 It is imperative the Offeror fully describe and provide details as to how the Offeror shall meet the subfactor requirements. Do not merely copy and paste, rephrase or restate the objectives or reformulate the requirements specified in the solicitation. Evidence (which clearly demonstrates and supports the Offeror’s claims) is essential.

The absence of such evidence may result in a deficient proposal.

L3.1.4 Volume Organization:

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

1) Table of Contents

2) List of Table and Drawings

3) Glossary

4) Cross Reference Matrix

5) Subfactor 1 – Technical Knowledge and Experience

6) Subfactor 2 – Logistics and Asset Availability

7) Subfactor 3 – Quality Control and Training

8) Subfactor 4 – Contractor Resources and Stakeholder Engagement

L3.2 Subfactor 1: Technical Knowledge and Experience

L3.2.1 Offeror shall summarize the successful application of technical knowledge and ability with use of resources (e.g. human and computer based) in development/repair/reverse engineering of broad scale (i.e. multiple engineering fields) projects/tasks. Evidence should emphasize subject matter areas required for AN/FPS-117 system support (e.g. electrical/electronic engineering, mechanical engineering, computer/software engineering, RF/Radar engineering) and execution. Summary descriptions of real-world projects can be used that identify the year, purpose, goals, disciplines involved, challenges and how they were addressed, outcomes, and lessons learned/knowledge gained.

Describe the approach to development and application of training (both at engineering and technician level) to support installation/sustainment/maintenance of replacement systems/Line Replaceable Units (LRU)/components of the AN/FPS-117 Radar System.

Offeror shall include a test plan (as a separate attachment) for a prior project that contains contents similar to DI- SESS-81704 Test Plans/Test Procedures section 3.2. This example will be no longer than 5-10 pages in length and include a Requirements Traceability Verification Matrix (RTVM) for the selected example using DI-MGMT-82133 Requirements Traceability Verification Matrix (RTVM) for guidance. This plan should be related to the engineering disciplines needed for successful AN/FPS-117 sustainment and support as identified in the first paragraph of this section. If engineering/technical personnel involved in the provided examples will be supporting the AN/FPS-117 program, identify what their role was, and what role they will play within the AN/FPS-117 CLS contract. (Reference CDRL paragraphs 2.7, 3.3.5, 3.3.6, 3.5.1, and 3.6.3)

L.3.2.2 Demonstrate the approach to detect, assess, and mitigate cybersecurity threats by providing a comprehensive summary of their cybersecurity capabilities, including their threat detection and response strategies, risk assessment methodologies, and mitigation techniques. The summary shall include, at a minimum, a description of their cybersecurity framework and governance structure, their approach to identifying and mitigating vulnerabilities, and their procedures for responding to and containing cybersecurity incidents. The Offeror's summary shall also include relevant certifications, accreditations, or compliance with the DOD Risk Management Framework DoDI 8510.01, as well as any relevant experience or case studies demonstrating their cybersecurity expertise. (Reference PWS paragraphs 3.3.13)

L.3.2.3 The Offeror shall provide examples of programs where Technical Data Packages (TDP’s) (e.g. DI-SESS- 80776B Technical Data Package) were produced. Summary descriptions of real-world projects can be used that identify the year, purpose, goals, disciplines involved, documentation produced and outcomes. At least one example should include a project/program where a TDP level three (3) package was produced along with T.O’s/Manuals.

• A TDP level 3 package is defined as the following: Product design data- Engineering design data which describes the complete physical and/or performance characteristics of an item or component in sufficient detail to ensure that an item or component produced in accordance with this data will be essentially identical to the original item or component.

Offerors shall provide examples of how the Offeror developed technical documentation that meets industry standards, such as S1000D, MIL-STD-38784, or ISO 9001. Written examples should also indicate if T.O.’s or manuals for engineering/technician use were produced. (Reference PWS paragraphs 3.3.5.2, and 3.3.8)

L3.2.4 Offerors shall provide examples where Modeling and Simulation (M&S) and/or Model Based System Engineering (MBSE) was used by the Offeror for project support. Summary descriptions of real-world projects can be used to identify the year, purpose, goals, disciplines involved, basic information on the types of simulations/models produced and the software packages used should be included. If MBSE experience is cited, indicate what MBSE software package was used (e.g. Cameo, Rhapsody, PTC Integrity Modeler, etc.) and to what level the system was modeled (e.g. Subsystem, Assembly, LRU, component) (Reference PWS paragraphs 3.3.4)

L3.3 Subfactor 2: Logistics and Asset Availability.

L3.3.1 The Offeror shall provide a summary of their intended procedures for supplying and sustaining spare hardware related to the AN/FPS-117 system. This summary should include their processes and protocols for procuring spare components and assemblies, including the identification of qualified suppliers, negotiation of contracts, and management of lead times. The Offeror should also outline their steps for replacing faulty or damaged components and assemblies, including removal of defective parts, installation of new or refurbished parts, and testing to ensure proper functionality. Additionally, the summary should cover inventory management, including tracking stock levels, monitoring usage rates, and forecasting future demands. (Reference PWS paragraphs 3.2, 3.5, 3.7)

L3.3.2 The Offeror shall summarize their approach to mitigating risks associated with Diminishing Manufacturing Sources and Material Shortages (DMSMS) in their proposed solution. This includes identifying potential DMSMS risks, developing strategies to address these risks, and implementing plans to ensure the continued availability of critical components and materials.

The Offeror shall provide a detailed description of their DMSMS management approach, including how they will monitor and track component availability, identify alternative sources, and develop mitigation plans to minimize the impact of DMSMS on the program. The Offeror's approach shall also include a description of their logistics and supply chain management processes, including how they will manage inventory and relevant tools, software and firmware obsolescence, cost avoidance, track shipments, alert notifications, continuous monitoring, and approach to ensure timely delivery of materials and components. (Reference PWS paragraphs 3.2.6)

L3.3.3 The Offeror shall summarize their approach to performing Test, Teardown, and Evaluation (TT&E) and repair services, including a description of their troubleshooting and repair processes that will be used to repair or replace failed System or Sub-System parts and components for the AN/FPS-117 both internally and at a radar site.

The Offeror shall summarize their approach for ensuring that all repaired/retrofitted items are configured and perform in accordance with the requirements of the Specification Control Drawing and Acceptance Test Plan (ATP).

(Reference PWS paragraphs 3.6)

L3.3.4 The Offeror shall summarize their procedures for avoiding, detecting, mitigating, and disposing of counterfeit parts of the AN/FPS-117 system, to include equipment, spares, repair, and replacement parts supplied to the USAF/DoD for successful AN/FPS-117 sustainment. Summary shall include policies and procedures for:

• Detecting and identifying counterfeit parts

• Mitigating the risks associated with counterfeit parts

• A description of the Offeror's counterfeit prevention strategy and how it will be implemented to ensure that all work is performed during this effort. The Offeror shall use DI-MISC-81832 for guidance.

Summarize the Offeror’s approach to implement and enforce these policies and procedures and demonstrate their commitment to ensuring the authenticity and reliability of the parts supplied to the USAF/DoD. (Reference PWS paragraphs 2.9, 3.5, 3.6)

L3.3.5 The Offeror shall summarize their approach in providing emergency engineering support services to address urgent software or hardware issues and obtain time-critical information, to include the following elements:

• The Offeror’s approach to provide emergency support at any radar location within Alaska, Hawaii, and Canada, including a commitment to have a representative on-site within 72 hours of PMO authorization (if needed)

• A description of their facilities, parts, materials, equipment, and services that will be used to inspect and restore an Assembly or Sub-Assembly to serviceable condition

The Offeror shall also provide evidence of their ability to perform the required work, including relevant experience, qualifications, and certifications. (Reference PWS paragraphs 3.4)

L3.4 Subfactor 3: Quality Control

L3.4.1 Describe the approach to implement quality metrics and monitoring processes, including key performance indicators, frequency and methodology for collecting and analyzing quality data, and procedures for identifying and addressing trends or anomalies in quality data. Additionally, the Offeror shall describe its configuration management process, supply chain quality control, corrective action and continuous improvement process, and experience and qualifications in implementing and maintaining quality control programs for similar radar systems or complex electronic systems. (Reference PWS paragraphs 2.10)

L3.4.2 The Offeror shall describe the Offeror’s quality control procedures, including the qualifications and experience of key personnel (Reference PWS paragraph 2.7)

L3.4.3 Provide examples of quality control processes and procedures used in previous contracts, including any relevant certifications or awards received

L3.4.4 The Offeror shall summarize their quality control processes to ensure that all work is performed to the highest standards for fabricated/repaired/retrofitted are supplied in serviceable like new condition. (Reference PWS paragraphs 2.24, 3.1.8, 3.2.3.2, 3.3, 3.3.10, 3.3.11.7, 3.3.14, 3.5.1, and 4.1.36)

L3.5 Subfactor 4: Contractor Resources and Customer Engagement

For Contractor Resources and Customer Engagement, the Offeror shall provide a written summary with written examples of the Offeror’s resources and customer engagement plans to support the AN/FPS-117 system, including descriptions of:

L3.5.1 The Offeror’s comprehensive contractor resource strategy. Include a description of the Offeror’s resources, such as: equipment and facilities and core personnel, and sub-contractors. Address potential growth and explain the Offeror’s plan on having a core team assigned and what their roles and responsibilities would be. (Reference PWS paragraphs 2.6, 2.7, and 3.1)

L3.5.2 The Offeror’s plan to communicate with the Government for ensuring transparency and compliance, including a description of the plans for meetings, monthly status reports (MSR), and Integrated Master Schedule (IMS) CDRLs. (Reference PWS paragraphs 3.1)

VOLUME III – FACTOR 3, PAST PEFORMANCE PROPOSAL

L4.1 Past Performance Contents. Submit information on the contracts considered the most recent and relevant which demonstrate the company’s ability to perform the requirements identified in the PWS. The Government will use this information and information obtained from other sources for an overall evaluation of past performance.

The Government will not evaluate personal references.

L4.1.1 Early Proposal Information. Each Offeror is requested to submit the Past Performance Proposal (Volume III) for each relevant contract citation 15 days prior to the date set for receipt of proposals. Submittal procedures in L1.3.3 apply for early proposal information of Volume III. Failure to submit early proposal information will not result in Offeror disqualification.

L4.1.1.1 As soon as practicable, the Offeror shall complete Attachment 10, Past Performance Questionnaire, and e-mail it and the associated Past Performance Questionnaire to all points of contracts (POCs) the Offeror has listed in the PPI (Attachment 8). The Offeror shall ensure all POCs are current. The POCs shall complete the questionnaires and forward them directly to the PCO and CS identified in L1.9. RESPONDENTS TO THE

QUESTIONNAIRES SHALL NOT SEND THE COMPLETED INFORMATION SHEETS BACK TO THE

OFFEROR. The Offeror shall not conduct follow-up actions with regards to the questionnaire, other than to confirm receipt by the recipient. The PCO and CS will conduct any other necessary follow-up actions with the identified POCs.

L4.1.2 Past Performance Summary. Provide a summary describing the role of the Offeror and each subcontractor, teaming partner, and/or contractor team arrangement partner. Include rationale supporting the assertion of relevance, but note, the Government is not bound by the Offeror’s opinion of relevancy. Clearly link past performance to the Technical Volume areas identified in Section L3 as they relate to supporting the types of requirements listed in the PWS; explain what aspects of the contracts are deemed relevant to the proposed effort. This may include a discussion of efforts accomplished by the Offeror to resolve problems encountered with prior contracts as well as past efforts to identify and manage program risk.

L4.1.3 Past Performance Information Sheet Summary Table: The Offeror shall submit a table summary of their past performance information sheets, and include the project name, project dates, if the example is from the prime or Contractor Team Arrangement Partner, and the project’s customer point of contact information.

L4.1.4 Past Performance Information Sheets (Attachment 8). The Offeror shall submit a minimum of two and a maximum of three Past Performance Information (PPI) Sheets with an emphasis on the prime Offeror or contractor team arrangement managing partner. The Offeror shall populate the template provided in Attachment 8 – Past Performance Information (PPI) Sheet for each of their citations. In the case of an Offeror without a record of relevant and/or recent past performance or for whom information on past performance is not available, the Offeror may not be evaluated favorably or unfavorably on the factor of past performance (see FAR 15.305[a][2][iv]). In this case, the Offeror’s past performance is unknown (or “neutral”) past performance. Offerors must submit information for those contracts which are relevant to demonstrate the ability to perform the work identified in the

PWS.

L4.1.4.1 A minimum of one PPI sheet shall be submitted by the prime Offeror and, if proposing as a contractor team arrangement, at least one of the remaining PPI sheets shall be from the partner. If proposing as a prime with more than one partner, a PPI sheet shall be submitted for each partner. Note: in the event more than three partners exist, submit one PPI sheet per each partner which is an allowable exception to the three maximum PPI sheet limitation listed in L4.1.4. A Government determination of “Not Relevant” for the minimum of one prime PPI sheet and one partner(s) PPI sheet, if proposing as a contractor team arrangement, will automatically be assigned a rating of “Not Relevant”.

L4.1.4.2 Prime Offeror past performance may be as a Prime or subcontractor. Subcontractor, teammate, or partner past performance may be as a Prime or subcontractor. All past performance as a subcontractor shall have been as a first-tier subcontractor.

L4.1.4.3 Past performance may be submitted at the contract or task order level. Offerors who submit a PPI sheet at the contract level shall clearly identify the actual performance they provided to the contract, in both dollar amount and personnel provided.

L4.1.5 Small Business Compliance In Past Performance: On the contracts submitted in Volume III, Past Performance, include relevant information in the PPI Sheet concerning the Offeror’s/joint venture member’s and/or critical subcontractor’s compliance with FAR 52.219-8, Utilization of Small Business Concerns or FAR 52.219-9, Small Business Subcontracting Plan, if these clauses are or were contained in the contract. (Please note that FAR 52.219-8 does apply to ALL businesses, whereas FAR 52.219-9 only applies to large businesses.) When subcontracting possibilities existed on the contracts submitted by the Offeror/joint venture member and critical subcontractor, address whether or not the Offeror/joint venture member and critical subcontractor awarded subcontracts to small business concerns, veteran-owned small business concerns, service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns to the fullest extent consistent with efficient contract performance. If none of the submitted contracts included these clauses, whenever subcontracting possibilities existed in the performance of these contracts, address whether or not it was the Offeror/joint venture member and critical subcontractor’s policy to utilize small business concerns, veteran-owned small business concerns, service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns to the fullest extent consistent with efficient contract performance.

L4.1.6 Subcontractor/Teaming Member Consent Letter. The Offeror must submit a consent letter executed by each of its proposed teaming member(s), joint venture partners, and/or critical subcontractors authorizing release of adverse past performance information to the prime Offeror to allow the prime Offeror an opportunity to respond. The consent form shall be completed by the team member(s), joint venture partners, and/or critical subcontractors identified in your proposal. The completed consent forms shall be submitted as part of your Past Performance Volume III. For any teaming member(s) (including JV team members) that does not provide an authorization letter with such written consent, the Offeror shall provide point of contact information for each entity. This contact information shall include a name, address, phone number, and email address, with whom the Government may coordinate any issues and obtain responses as needed.

Offerors are advised that if it does not submit the Subcontractor/Teaming Member Consent Letter with written consent, then the Government will address any past performance issues directly with the teaming member, JV team member, and/or subcontractor, and the Offeror will forfeit the opportunity to participate in any related discussions.

L4.1.7 Adverse Past Performance or Discrepancy: Offerors shall be given an opportunity to address adverse past performance information if the Offeror, joint venture member and/or critical subcontractor has not had a previous opportunity to respond to the information. Recent contracts will be examined to ensure that corrective measures have been implemented. The past performance evaluation assessment will consider issues including but not limited to the number and severity of the problems, the appropriateness and/or effectiveness of any corrective actions taken including planned or promised, and the overall work record. Prompt corrective action in isolated instances may not outweigh overall negative trends.

L4.2 Recency: Recency will be determined based on contract references reflecting past and present performance over the past five years from the date of proposal submission. The Offeror shall submit documentation for each PPI sheet to meet the five-year recency requirement.

L4.3 Relevant Contracts. The Government will perform an independent analysis in determining the relevancy of a contract based on the data provided and/or obtained. The Government will use the AN/FPS-117 requirements as a baseline for relevancy, as further detailed in attachment 9 – Past performance Relevancy Baseline. When making relevancy determinations, the definitions in Table L.4 will be utilized.

Table L.4 Past Performance Relevancy Rating

Adjectival Rating Description

Very Relevant Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.

Relevant Present/past performance effort involved similar scope and magnitude of effort and complexities this solicitation requires.

Somewhat Relevant Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.

Not Relevant Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires.

L4.3.1 For the prime Offerors, relevancy is defined as contracts that are most similar to this effort; contract type, dollar value, period of performance, types of services provided, complexity required on the contract being reviewed when compared to those of the AN/FPS-117 CLS requirements.

L4.3.2 For proposed subcontractors/teaming partners, relevancy is defined by that which reflects experience in the area of expertise the subcontractor is projected to perform under the program, (i.e., specific functional areas in the

PWS).

L4.3.3 In the case of a newly formed business entity or in contractor teaming arrangements where the company is relying mostly on the past performance and experience of its key personnel, partners on the team, or on a major subcontractor(s), the proposal must clearly explain "whose" past performance, and "how" that past performance is relevant to the procurement. Resumes or letters of recommendation are not a valid past performance submission.

VOLUME IV – FACTOR 4, SMALL BUSINESS PARTICIPATION SUBMISSION

L5.1 General.

A Small Business Participation Submission is required from all Offerors, including small businesses and companies with Master, Individual, commercial subcontracting plans and/or comprehensive subcontracting plans.

The Offeror/joint venture member and each proposed critical subcontractor shall include only the first tier of subcontractors for this effort. Offerors are advised that the Small Business Participation Submission is not the same as the Small Business Subcontracting Plan required by FAR 52.219-9. Large business Offerors shall not utilize the Small Business Subcontracting Plan in place of the Small Business Participation Submission. Small Business Participation will be evaluated on an Acceptable/Unacceptable basis; Offerors must be rated Acceptable for the Small business Participation factor to be eligible for award.

L5.1.2 Format and Specific Content The Offeror shall submit a Small Business Participation Submission for itself and any joint venture member, as well as each proposed critical subcontractor in a separate volume labeled “Volume IV – Small Business Participation Submission”. The Small Business Participation Submission shall address each of the following elements in the proposed performance of this resultant contract:

L5.1.2.1 The extent of participation of proposed Small Businesses (SB) when subcontracting possibilities exist, including the company names with CAGE codes the Offeror plans to use in the performance of this resultant contract; and, L5.1.2.2 The description of the subcontracted work these proposed firms are to perform; and, L5.1.2.3 The associated goals expressed in terms of percentages of the total planned subcontracted dollars. If limited or no subcontracting possibilities exist for these socio-economic entities, provide rationale for such.

Offerors are cautioned against only acknowledging a goal is not met, if applicable. Rather, adequate rationale includes specific reasons why a goal is unmet, and any actions being taken to increase any unmet goals.

Additionally, if the Offeror/joint venture member/critical subcontractor is a small business concern, it should include the work it will be performing when calculating the goals for your Small Business Concern Participation information.

VOLUME V – FACTOR 5, ADMINISTRATIVE AND RESPONSIBILITY MATERIAL

L6.1 General.

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file; as well as assisting the PCO in making a responsibility determination. Offerors shall provide the following additional documentation.

L6.1.2 Small Business Subcontracting Plan If the Offeror is other than a small business, the Offeror shall provide its individual Small Business Subcontracting Plan conforming to the requirements of FAR 19.7, DFARS 2019.7, and FAR 52-219-9, Small Business Subcontracting Plan, that separately addresses and specifies the extent of the Offeror’s commitment to the participation of SB, VOSB, SDVOSB, HUBZone, SDB, and WOSB concerns. The Offeror shall submit its Subcontracting Plan as part of this volume. If the proposed goal for any category is zero, the Offeror shall provide rationale within this section. The Subcontracting Plan of the successful Offeror will be reviewed and approved by the PCO prior to receiving the contract award. See FAR 19.702(a) (1) Statutory Requirements, regarding failure of the apparent successful Offeror to negotiate and submit a Subcontracting Plan acceptable to the PCO. The successful Offeror’s approved Subcontracting Plan will be incorporated into the resultant contract and the performance will be monitored by the Government and reported on CPARS during contract execution to include performance against subcontracting goals. Large Business Offerors are advised that while the SB Subcontracting Plan must be submitted to be eligible for award, the acceptability of the content of that plan is part of the responsibility determination assessment and not part of the evaluation.

L6.1.3 Contract Forms and Certifications.

L6.1.3.1 Proposal cover page which includes the Offeror company name, Commercial and Government Entity (CAGE) Code, Unique Entity Identifier (UEI), as well as the primary point of contact name(s), office phone numbers, cell phone numbers, and email addresses for individuals who are authorized to discuss the proposal with

Government personnel on behalf of the Offeror.

L6.1.3.2…