N6852025R0001_Final RFP_LOGEN II_AMEND 0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

See Section A - Solicitation Amendment 0001

1. CONTRACT ID CODE PAGE OF PAGES

S 1 25

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 29-May-2025

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X N6852025R0001

X 9B. DATED (SEE ITEM 11)

22-May-2025

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

29-May-2025

CODE

COMFRC PROCUREMENT GROUP

47038 MCLEOD ROAD; BUILDING 448

PATUXENT RIVER MD 20670

N68520 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N6852025R0001

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been modified:

CONTRACT INFORMATION

Block 3-N6852025R0001 Contract Specialist Name: Sarah Metcalf Email: sarah.e.metcalf2.civ@us.navy.mil

Procuring Contracting Officer Name: Beverley Rhamdeow Email: beverley.s.rhamdeow.civ@us.navy.mil

This procurement is to support the COMMANDER, FLEET READINESS CENTER (COMFRC) with LOGISTICS AND ENGINEERING SUPPORT Level of Effort (LOE) services, known as LOGEN II. This competitive solicitation is a small business set aside. The Government intends to award a single award Indefinite Delivery Indefinite Quantity (IDIQ) contract.

PMT PID: N68520-24-RFPREQ-F000000-0016

Solicitation Amendment 0001:

The pupose of this amendment is provide guidance on submitting questions and specify the deadline for submission.

Section L is being revised as follows:

1. Section L, Part A, Paragraph 4.0 - Proposal Submission and Packaging- to include Subparagraph 4.2 Solicitation Questions Submission.

2. Table G-2 Section L List of Attachments was revised to include Attachment P1_ Final RFP N6852025R0001_QandA

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

PART A GENERAL INSTRUCTIONS

1. GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to assess the Offeror’s capability to perform all requirements. The Offeror’s proposal must be sufficient in detail and scope to provide evaluators with a clear understanding of the Offeror’s approach, expertise, and capability as required by the solicitation.

The Offeror’s proposal must demonstrate that the Offeror has a thorough understanding of all requirements and associated risks and is able, willing, and competent to devote the resources necessary to meet all requirements. The Offeror shall arrange its proposal as described in the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror.

The Government advises Offerors that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government, into the final contract, with or without discussions. Alternate or streamlined proposals are not acceptable.

In presenting material in the proposal, the Government advises the Offeror that the quality of information is more important than the quantity. Offerors shall emphasize clarity, brevity, and logical organization when preparing proposals. Offerors are responsible for presenting enough information to allow the Government to evaluate the Offeror’s proposal without discussions.

The Government considers unsubstantiated statements that the prospective Offeror understands, can or will comply with the specifications or paraphrasing the requirements or parts thereof inadequate and such statements may adversely affect the proposal’s rating.

The Offeror shall include any data necessary to illustrate the adequacy of its various assumptions, approaches, and solutions to problems. There is no need to repeat information in more than one volume. The Offeror shall include detailed information in the most logical place and summarize or reference the information in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

Offerors are expected to comply with all requirements of the solicitation. The Government advises Offerors that taking exception or deviation from any term or condition of the solicitation may make an offer unacceptable, and the Offeror ineligible for award. The Government may consider any exception or deviation to any term or condition of the solicitation that is not expressly authorized by the solicitation to be a deficiency, as defined in Federal Acquisition Regulation (FAR) 15.001. A proposal assessed to contain a deficiency is considered unawardable.

Throughout these instructions, the “Offeror” is the prime contractor with its Commercial and Government Entity (CAGE) code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement that meets the requirements of the Small Business Administration and that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a Joint Venture. The term “entity” refers to any of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different (CAGE) Code/System for Award Management (SAM) Unique Entity ID (UEID) than the Offeror). The Government will only evaluate principal entities in the Past Performance evaluation. Principle entities are defined in Section M and the Government advises Offerors that in order to demonstrate work commitment, Offeror’s must identify each principal entity in Volume 4 Cost/Price with a commensurate dollar amount that relates to the proposed work effort.

Incumbent Information: The incumbent contractors are:

Site/Program: Contract Number: Incumbent:

FRCSE, FRCE, FRCSW LOGEN N6852023D0001 Fleet JV, LLC Cage 98NH1 FRCE Logistics N6852021D0002 LTM INC. Cage 06WH5

2. PROPOSAL FORMATING

2.1 Electronic Formatting and Applications

This section provides information to the Offeror on the electronic format and the appropriate software for drafting and submitting proposals. Using the software and procedures described in this section will ensure that the Offeror’s proposal is suitable for reading electronically. The Offeror shall format proposals as follows:

A page is defined as one side of sheet, 8 1/2″ × 11″, with at least one inch margins on all sides, using a Times New Roman 12-point regular font with the following Advanced options (100% Scale, Normal Spacing, Normal Position, No Ligatures and default OpenType Features). In addition, Line and Paragraph spacing shall be no less than 0 point before and after with single line spacing. The following are excluded from the page count: Title pages, table of contents, pages marked as intentionally left blank, and acronym lists. Volume 3 (Cost) is not page limited.

However, this section is to be strictly limited to cost and price information. Information that can be construed as belonging in one of the other sections of the proposal will be so construed and counted against that section's page limitation. In the event of discussions, separate page limitations will be specified in the Government’s request for additional information. Likewise, if final proposal revisions are requested, separate page limitations will be specified in the Government’s request for that submission. Pages submitted in excess of the limitations specified in Table G-1 will not be evaluated by the Government. All proposal pages shall include a volume number and page number. Offerors shall mark all proposal information as Controlled Unclassified Information/ Source Selection using “CUI//SSEL” and “Source Selection Information-See FAR 2.101 and 3.104” to comply with FAR 3.104-4. Offerors shall include any additional marking instructions, as applicable."

Table G-1 identifies the proposal structure, file naming conventions and page counts for each volume.

2.1.1 Operating System and Applications

The Government uses Microsoft Windows 10 Operating System to access proposals. Offerors shall submit proposal information using the following applications: Microsoft Word 2016, Microsoft Excel 2016, Microsoft PowerPoint 2016, and Microsoft Project 2016. However, Offerors shall provide letters and other signed documents as fully searchable Portable Document Format (.pdf) files. Unless expressly authorized, the use of other application software for submission of proposals is unacceptable.

2.1.2 Hyperlinks

Offerors shall not use hyperlinks within documents and volumes.

2.1.3 Virus Free Electronic Submission

Offerors shall ensure that its electronic proposal is virus free. The Government will disqualify any Offeror who submits documents that contains a virus or malicious code from the competition.

2.1.4 Multimedia

The Offeror shall not embed sound or video (e.g., MPEG) files within its proposal submission.

2.1.5 Graphics

To avoid the need for extensive computer system resources to view graphics, Offerors shall:

a. Simplify the color palette when creating figures and minimize the use of color print or graphics to the maximum extent possible;

b. Minimize size of graphics files; and

c. Avoid scanned images.

3. PROPOSAL CONTENT AND VOLUMES

The Offeror shall present its proposal information in a manner that facilitates a one for one comparison between the information presented in the proposal volume and the Section L proposal instructions. The Offeror shall structure proposal information such that its paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier sub paragraphs.

Offerors shall not include Cost/price information for this proposed effort, (e.g., dollar values and/or hourly rates) in any volume other than Volume 1 Contract Administration and Volume 4 Cost/Price.

The Offeror shall follow the basic structure of the file naming convention in Table G-1 for electronic file submissions (e.g., proposal volumes, attachments, appendices), where “#” represents the sequential numbering of files and shall preface files with an abbreviated company name. Offerors shall keep the file name as short as possible (i.e., under 40 characters) to ensure file accessibility on Government SharePoint systems or shared drives. Files with longer names often become corrupt or inaccessible.

Table G-1 Offeror Electronic File Naming Convention and Proposal Structure

Volume Number

Section Volume Title File naming convention Page Count

1 Contract Administration Vol 1 CA#.docx As Needed

2 Technical Understanding of the Work

2.1 & 2.2

NTE 40

Pages in total

Table G-2 lists the attachments provided to the Offeror within Section L.

Table G-2 Section L List of Attachments

Section L Attachment Number

Electronic File Title Attachment Name

L-1 Att L-1 Vol 1 KA Tables Table KA-1: Offeror Summary

2.1 Engineering Approach Vol 2 Book1.docx

2.2 Logistics Approach Vol 2 Book2.docx

2.3 Management Approach Vol 2 Book 3.docx 2.3.2 & 2.3.3-

2.3.3.4

NTE 15

Pages in total

2.3.1 Key Personnel NTE 3 page

limit/per resume

2.3.2 Teaming and Subcontractor

Management

2.3.3 Transition Plan

2.3.3.1 Subcontracts

2.3.3.2 Incoming Personnel

2.3.3.3 Communication

2.3.3.4 OPSEC, Facility Clearances, and

Base/Building Access

2.3.4 System Security 3 pages

3 Past Performance Vol 3 PP#.docx NTE 15 pages

4 Cost/Price Vol 4 Cost-Price#.docx No Page Limit

Annexes

Annex A

Joint Venture and Teaming Agreements per HTXT.215-9505

AnnA JVTA#.pdf As Needed

Annex B

DCAA/DCMA Reports, Audits, and Determinations

AnnB DCAA#.pdf As needed

Annex C

Model Contract AnnC Model Contract.pdf or .docx

As needed

Annex D

Final Versions of Previous SOW/PWSs for Past Performance

AnnD Rel SOW PWSs_Contract Reference #.pdf OR .docx

As needed

Annex E Release of Adverse Past Performance Authorization Letters; and/or Past Performance Point of Contact Information

AnnE Rel Ad PP Ltr#.pdf;

and/or PP POC Info#.docx

As needed

Table KA-2: Offeror Information Table KA-3: Business System Status Table KA-4: Terms and Conditions

L-2 Att L-2 Vol 3 PPQ Past Performance Questionnaire

L-3 Att L-3 Vol 3 PP-2 PP Con Data Table PP-2 Past Performance Contract Data

P1 Final RFP QandA Final RFP N6852025R0001_QandA

P6 Cost Summary Cost Summary Spreadsheet P7 Fully Burdened Rates Annual Fully Burdened

Labor

4. PROPOSAL SUBMISSION AND PACKAGING

All Proposals shall be UNCLASSIFIED.

4.1 ELECTRONIC PROPOSAL SUBMISSION (Unclassified Data Only)

Note: All proposals shall be valid for 180 days.

The Offeror shall submit its unclassified proposal volumes electronically through the Solicitation Module of the Procurement Integrated Enterprise Environment (PIEE) at https://piee.eb.mil. The Offeror shall not use any other method to submit its initial proposal including any postal delivery service, hand-carried, or other electronic systems (e.g., DOD SAFE). All proposal information shall be marked with “CUI//SSEL” and “Source Selection Information – See FAR 2.101 and 3.104.” Offerors are encouraged to review the instructions on how to post an offer, using the Posting Offer demonstration on the PIEE website:

https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf.

It is the Offeror’s responsibility to follow the registration instructions found on the PIEE website.

The Government advises all potential prime Offerors and their subcontractors to register the proper company points of contact in PIEE based on their CAGE codes with correctly roles assigned well in advance of the solicitation closing date. Subcontractors shall register in PIEE if they intend to submit proprietary proposal information to the Government, separate from the prime offer. Subcontractors that submit documents directly to the Government must include the prime contractor’s name, CAGE, and RFP number on the first page of the document.

Offerors are responsible for submitting proposals, and any modifications or revisions, to reach the Government office designated in this solicitation by the date and time specified. While Offerors are encouraged to submit documents early, any submission, modification, or revision received at the Government office after the exact date and time specified is “late” and will not be evaluated or considered for award. In the event there is acceptable evidence to establish that the submission, and any modifications or revisions were received at the Government installation designated for receipt of offers and was under the Government’s control prior to the date and time set for receipt of offers, the Procuring Contracting Officer (PCO) may accept the submission. It is also the Offeror’s responsibility to confirm receipt of proposals and all electronic communications. The Government advises Offerors to take screen shots of its submission to validate submission acceptance in the PIEE system against this solicitation. The Government will not search for proposals in PIEE submitted incorrectly.

The date and time specified in Block 9 of the SF 33 of the RFP is the submission date for all proposal Volumes.

4.2 SOLICIATION QUESTIONS SUBMISSION

Questions regarding the solicitation shall be submitted via email with the use of Attachment P1- Final RFP N6852025R0001_QandA to Contract Specialist, Sarah Metcalf at sarah.e.metcalf2.civ@us.navy.mil and PCO, Beverley Rhamdeow at beverley.s.rhamdeow.civ@us.navy.mil. Please do not include any proprietary information in your questions, as the Government will share both the questions and answers with all potential Offerors.

All questions must be submitted NO LATER than 2:00 PM Eastern Time on June 9, 2025.

Questions received after this deadline may be answered at the Government’s sole discretion.

5. CHANGES TO SOLICITATION

For any changes and additional information to the solicitation, please go to website:

https://sam.gov/content/opportunities or https://piee.eb.mil Search the database for the solicitation number N6852025R0001

PART B SPECIFIC INSTRUCTIONS

1. VOLUME 1 – CONTRACT ADMINISTRATION

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-1 Table KA-1: Offeror Summary Table KA-2: Offeror Information Table KA-3: Business System Status Table KA-4: Terms and Conditions

The purpose of the Contract Administration Volume is to provide the Government the ability to assess the Offeror’s compliance with the information specified within the solicitation. This information is to facilitate the PCO’s responsibility determination and any need to discuss information related to an Offeror’s responsibility does not constitute discussions. The Offeror shall complete all Tables (KA-1, KA-2, KA-3, and KA-4) as separate tabs in Attachment L-1, according to the instructions within the attachment, and submit Attachment L-1 as a separate electronic file.

The Offeror shall divide the Contract Administration volume into the Sections outlined below:

a. Offeror Summary Table KA-1

(1) The Offeror shall complete Table KA-1 (Offeror Summary) to summarize the Offeror and its entities’ pertinent information by CAGE code/SAM UEID including the proposed type and level of work to indicate a commitment of work for entity identified. Offerors shall demonstrate the proposed work commitment for each entity in Table KA-1 (Offeror Summary) in Volume 4 (Cost/Price) by associating a dollar value commensurate with the Percent of Total Proposed Cost/Price reflected in Table KA-1 (Offeror Summary).

The Offeror shall ensure that each CAGE code/SAM UEID is correctly associated to the entity proposed.

The Offeror may submit a detailed explanation that describes the distinct roles and responsibilities for entities with different CAGE codes /SAM UEID at the same physical location if the different CAGE code / SAME UEID was a result of a corporate acquisition, reorganization, merger, or other administrative reason. The Offeror shall explain how the changes affect the relevance of any contract references provided. The Government may consider the past performance information regarding predecessor companies in accordance with FAR 15.305 (2)(iii), as applicable.

(2) For Joint Venture arrangements, the Offeror shall submit the legal document that established the Joint Venture and provide the associated agreements detailing the roles/responsibilities of each member of the JV. Note: All proposed Joint Ventures shall provide the Joint Venture legal document with agreement(s) in Annex A (Joint Venture Teaming Agreement(s)). If none, indicate none in this section.

(3) Additionally, Prime Offerors shall provide a copy of all teaming arrangements in accordance with Section H Clause HTXT.215-9505. Offerors shall provide all teaming arrangements in Annex A (Joint Venture Teaming Agreement(s)). If none, indicate none in this section.

b. Offeror Representatives and Information Table KA-2

The offeror shall complete table KA-2 (Offeror Information). Offerors shall provide the name, title, phone number and email address of the Offeror’s principal point of contact for the solicitation. In addition, the Offeror shall identify those individuals authorized to negotiate with the Government and contractually bind the Offeror. The Offeror shall provide its company/division’s street address, county and facility code; CAGE code; UEI; size of business (large or small); and labor surplus area designation.

Offerors shall provide the mailing address, telephone, fax numbers, email address, and facility codes for the Offeror’s local Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office. In addition, provide the name, telephone number, fax number, and email address for the Administrative Contracting Officer (ACO) at DCMA

c. Offeror Business Systems Table KA-3

The Offeror shall complete Table KA-3 (Business Systems Status) showing the current status and or determinations regarding its business systems. If any item is not applicable to the Offeror or for contract performance, so state and justify. The Offeror shall outline the potential impact on contract execution, mitigation plan, and correction plan for any system considered inadequate or not approved by DCMA. The Offeror shall submit relevant DCAA/DCMA reports, audits, and determinations in Annex B (DCAA/DCMA Reports, Audits, and Determinations).

d. Terms and Conditions:

The Offeror shall complete Table KA-4 (Terms and Conditions). An exception to the terms and conditions or proposed deviation is a deficiency. A deficiency renders the Offeror’s proposal unawardable. An exception occurs if/when an Offeror states it will not comply with a solicitation requirement, usually involving contract terms and conditions. A deviation is where an Offeror states it will not comply with a solicitation requirement but proposes an alternative to meet the intent of the requirement, usually involving a PBWS requirement

The Offeror shall provide one of the following two statements in Table KA-4 (Terms and Conditions). If the Offeror takes any exceptions or deviations to the provisions of the solicitation and its applicable documents, the Offeror shall provide the following statement:

“All exceptions and deviations taken from the solicitation terms, conditions or requirements, including any applicable documents, are included in this section”. If the Offeror does not take any such exceptions or deviations, then the Offeror shall provide the following statement: “No exceptions or deviations are taken to the terms and conditions or any requirement of the solicitation.”

If proposing an exception or deviation, the Offeror shall provide a detailed description for each in this section. Indicate the difficulty with the applicable requirement and the proposed solution. Specifically identify the portion of the solicitation and the proposal, which are affected. Also, identify any proposed H-clauses containing unique contract terms and conditions not covered by clauses in this solicitation and associated with an exception or deviation identified in this section.

e. Model Contract Documents:

The model contract (inclusive of Sections A through K) shall be provided as an Annex C.

The Offeror shall ensure the Model Contract includes:

(a) Original signed SF33 (Solicitation, Offer, and Award) cover page of the solicitation and a signed SF30 cover page of each amendment (as applicable) with all applicable Blocks completed and acknowledgement of receipt of each amendment (as applicable) to this solicitation. The SF-33 Block 12 “fill-in” (proposal validity date) shall be completed;

(b) Section B with proposed pricing;

(c) A complete copy of all FAR, DFARS, NAVAIR, and special clauses and provisions requiring contractor fill-ins, and;

(d) Section H (including any other proposed clauses). All Offeror proposed H Clauses, or other contract additions, in full text, if applicable. If an Offeror proposes to perform work above or not included in this solicitation (e.g., including, but not limited to, an aspect of a proposal that the Offeror believes the Government should evaluate as a strength), the Offeror must include contractually binding language for inclusion in the awarded contract. These additions may be H clauses, additions to the SOW, additions to the CDRLs (if data is to be delivered), or other additions. For the H clause, it must state as a minimum: a) the Offeror’s performance responsibilities; b) the performance periods, including delivery dates, if applicable; and, c) the financial responsibilities and liabilities of the Offeror. The Offeror’s proposal should include information regarding any Government performance and financial responsibilities incurred as a result of any proposed H clause or other proposed language for inclusion in the awarded contract.

For evaluation purposes, in the event there is any discrepancy between these contracts documents and any other volume, Volume 1 (Contract Administration) shall take precedence.

2. VOLUME 2 - TECHNICAL

Note: This volume shall not contain any reference to cost or price aspects of the offer.

This volume consists of three books: 1) Engineering Approach, 2) Logistics Approach, and 3) Management Approach. In each volume, provide the information described below:

The Offeror shall complete and submit Table T-1 (Technical CRM) within each book of Volume 2 (Technical). The Technical CRM is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements.

Table T-1: Technical Cross Reference Matrix

Section L - Proposal Instructions Volume and Paragraph Title

Requirements document reference (e.g., SOW, PWS, SPEC, QASP)

Other RFP Reference (e.g., CLIN, Section F, Section M)

Offeror’s Proposal Reference (Volume / Paragraph)

2.0 Volume 2 – Technical N/A N/A

2.1 Engineering Approach SOW sections;

3.3.1 Engineering Data,

3.3.3 Engineering Investigations, Health/Hazard Material and Quality Deficiency Reports of New and Existing Production Systems and Components,

3.3.4 Reliability and Affordable Readiness

Tasks (RAAT), including subparagraphs within

3.3.5 Computer Aided Design and

Manufacturing,

3.3.9 Analyses and Technical Studies, including subparagraphs within

3.3.18 Electronic Work Package (EWP)

Readiness, including subparagraphs within

Provide reference to Offerors’ Proposal Volume 2 – Technical. Refer to appropriate page number in Offerors’ written proposal

2.2 Logistics Approach SOW sections;

3.4.1.1 Level of Repair Analysis (LORA), 3.4.3.1, 3.4.3.12, 3.4.3.13, 3.4.3.13.3,

3.4.3.13.4 Maintenance Planning (MP), 3.4.4.1, 3.4.4.3, 3.4.4.4 Logistics Support Analysis (LSA) Database and Reports, and 3.4.7.1, 3.4.7.5 - 3.4.7.5.3 Supply Support

2.3 Management Approach

2.3.1 Key Personnel SOW section 4.0

2.3.2 Teaming and

Subcontractor Management

2.3.3 Transition Plan

2.3.3.1 Subcontracts

2.3.3.2 Incoming Personnel

2.3.3.3 Communication

2.3.3.4 OPSEC, Facility

Clearances, and Base/Building Access

IAW SOW Security Section 3.2; 3.2.3.2, 3.2.4, 3.2.5

2.3.4 Security Requirements IAW SOW sections 3.2; 3.2.2, 3.2.2.1, 3.2.3.3

Throughout the Technical Volume, if applicable, the Offeror shall identify any proposed capability, approach or feature that exceeds a requirement or provides merit associated with a performance or operational benefit to the Government. Additionally, if applicable, the Offeror shall identify any proposed capability, approach or feature that reduces risk inherent in the program. Specifically, the Offeror shall explain the benefits to the Government in technical terms and the degree of impact. Any aspects of the Offeror’s proposal may be included in the resultant contract within the proposed price.

Simply stating that the Offeror understands and will perform the listed tasking areas is inadequate.

Paraphrasing the SOW is similarly inadequate. The offeror shall not assume that the Government evaluators possess any knowledge or familiarity with their company or approach in their proposal.

Specifically, the offeror shall provide a comprehensive and detailed response describing their approach to fulfilling the engineering and logistics requirements outlined below in 2.1 & 2.2 in support of fleet support teams (FSTs) and Maintenance Repair and Overhaul (MRO) functions for the sustainment and modification of Naval type/model/series (T/M/S) aircraft, systems, and associated support equipment, across fleet readiness centers (FRCs) Southeast, East, and Southwest to ensure seamless support. The response must demonstrate a clear understanding of the technical and logistical challenges, operational constraints, and mission critical support functions necessary to ensure fleet readiness.

Responses shall include the following:

2.1 Engineering Approach – Book 1

Provide a written narrative demonstrating a thorough detailed understanding of the work and engineering approach. Offerors shall structure their responses addressing each of the following areas:

Provide a detailed written narrative methodology and application for executing the engineering support requirements details in the SOW sections listed below including the assessment, analysis, and implementation of engineering solutions to sustain and modify Naval T/M/S aircraft.

In response to the below detailed SOW sections describe how your engineering processes and expertise will be applied to produce engineering sustainment products directly in support of in-service Naval T/M/S aircraft.

In response to the below detailed SOW sections identify key risks associated with engineering tasks and outline risk mitigation strategies.

For the SOW task areas specified below:

3.3.1 Engineering Data,

3.3.3 Engineering Investigations, Health/Hazard Material and Quality Deficiency Reports of New and Existing Production Systems and Components,

3.3.4 Reliability and Affordable Readiness Tasks (RAAT), including subparagraphs within

3.3.5 Computer Aided Design and Manufacturing,

3.3.9 Analyses and Technical Studies, including subparagraphs within, and

3.3.18 Electronic Work Package (EWP) Readiness, including subparagraphs within

2.2 Logistics Approach – Book 2

Provide a written narrative demonstrating a thorough detailed understanding of the work and logistics approach. Offerors shall structure their responses addressing each of the following areas:

Provide a detailed written narrative methodology and application for executing the logistics support requirements detailed in SOW section listed below including support planning that includes all integrated product support elements.

In response to the below detailed SOW sections describe how your logistics processes tools and expertise will be applied to enhance system performance, reliability, maintainability, and life cycle sustainment.

In response to the below detailed SOW sections identify key risks associated with logistics tasks and outline risk mitigation strategies.

In response to the below detailed SOW sections explain an understanding of the NAVAIR and DoD national logistics processes and their applications

For the SOW task areas specified below:

3.4.1.1 Level of Repair Analysis (LORA), 3.4.3.1, 3.4.3.12, 3.4.3.13, 3.4.3.13.3, 3.4.3.13.4 Maintenance Planning (MP), 3.4.4.1, 3.4.4.3, 3.4.4.4 Logistics Support Analysis (LSA) Database and Reports, and 3.4.7.1, 3.4.7.5 - 3.4.7.5.3 Supply Support

2.3 Management Approach – Book 3

2.3.1 Key Personnel

The Offeror shall propose Key personnel that meet or exceed all labor category requirements as specified in the Statement of Work. Key personnel must possess, at a minimum, an interim Secret security clearance. However, all Key Personnel must possess a fully adjudicated Secret security clearance granted in accordance with (IAW) the standards and procedures outlined in the DD Form 254 and applicable security regulations before commencing any work, classified or unclassified, related to this contract. No work shall be performed by any Key Personnel until their fully adjudicated Secret clearance is granted.

The following definitions apply to this section:

- A “contingent hire” is an individual who has committed, under a signed letter of intent, to being employed by the Offeror if the Offeror receives award of the contract.

- A “prospective hire” is an individual that the Offeror has committed to hiring if the Offeror receives award of the contract whose identity may not be known until after contract award.

- A "current employee" is an individual who is currently employed by the identified company.

The Offeror shall provide the following information:

If the “Key” employee is a contingent hire, the Offeror shall submit a corresponding letter of intent in Volume 4, and shall include an agreement of salary and benefits. The letter of intent is a separate written agreement signed by the potential employee(s) to work for the Offeror effective at the contract award. Key personnel employed by subcontractors and other JV team members shall provide letters of intent separately or included with the prime contractor’s proposal submission.

For all proposed Key Personnel, the Offeror shall provide a resume of the accomplished work assignments, training, etc. that demonstrates the required education, experience, and approved security clearance level. The number of Key Personnel resumes required for submission with an Offeror’s proposal are as follows:

# Of Resumes

Labor Category

2 Aerospace Engineer, Sr.

2 Electrical Engineer, Sr.

2 General Engineer, Sr.

2 Logistics Analyst, Sr.

2 Acquisition Logistics Manager, Sr.

1 Program Manager, Sr.

1 Logistics Specialist, Sr

Resumes shall contain, at a minimum, the following information:

(i) Employee name

(ii) Employment experience in chronological order with position title, corresponding beginning and ending dates (month and year), narrative description of duties and responsibilities

(iii) Current position, title, and employer and corresponding beginning date (month and year)

(iv) Educational history

(v) Institution name, degree or certification earned, and year for all degrees or certifications earned

(vi) Current level of security clearance and status (final, interim, or pending) The Government may use information other than that provided by the Offeror in their proposals to check educational background and verify degrees or certifications received.

2.3.2 Teaming and Subcontractor Management

The Offeror shall provide an outline of how the SOW tasking across multiple sites will be assigned for performance within the Offerors’ Prime corporate entity and among the proposed subcontractors, ensuring compliance with the Limitation of Subcontracting clause 52.219-14. (Note: Failure to comply with this may make the offer unawardable). The Offeror shall describe how their subcontractors will be managed to ensure cohesive integration across all task order performance requirements into the overall management approach. Offerors’ shall also explain their teaming approach and include a description of the experience, knowledge, and skills the Offeror will be acquiring through each subcontract and how the Offeror will leverage each subcontractor’s strengths to ensure corporate teaming expertise is available through technical leadership, quality assurance, and process improvement for each FRC site.

2.3.3 Transition Plan

The services under this solicitation are vital to the Government and must be continued without interruption to current operations at each FRC site. The Offeror is required to submit a written narrative delineating a transition-in plan, in which will be incorporated into the contract award as Section J Attachment 4, based on a 30-day period after award that ensures a smooth workplace changeover from an incumbent with no loss of service and minimal loss of corporate contract management. Upon completion of the 30-day transition-in period, the Government anticipates approximately 10 task orders will be awarded within the first two months of the ordering period for task order performance to commence. The plan should include a detailed Plan of Action & Milestones (POA&M), including dates and measurable elements. In addition, the plan should take into consideration the following elements as well as any additional elements deemed necessary by the Offeror to commence performance:

2.3.3.1 Subcontracts: The Offeror shall provide a plan of action to ensure that all proposed subcontract agreements are signed within the 30 day transition in period.

2.3.3.2 Incoming Personnel: The Offeror shall provide a preliminary staffing plan to ensure that all personnel are able to begin their corporate-level work duties during the transition-in period, and at the task order level upon issuance of task orders following the 30-day transition-in period. The proposed plan should include a schedule for hiring ramp up and a timeframe for completion of staffing actions.

2.3.3.3 Communication. The Offeror shall provide a plan of action for maintaining effective coordination and communication with the Government and the incumbent Contractor personnel, including weekly status meetings, during the transition-in period to ensure a seamless transition.

2.3.3.4 OPSEC, Facility Clearances, and Base/Building Access: The Offeror shall provide a plan to implement the required security clearances and badging requirements during the transition period so that service is not interrupted upon task order award.

2.3.4 Security Requirements

2.3.4.1 The offeror shall show, or provide a plan to show, that they have the capability to meet the security requirement minimum criteria. The Offeror shall provide a valid Defense Security Service (DSS) SECRET security facility clearance (See Note below). Alternatively, the offer shall provide a plan to possess, within 30 days of contract award, a valid Defense Security Service (DSS) SECRET facility clearance.

2.3.4.2 The Offeror shall provide a plan that demonstrates its capability to achieve a DSS TOP SECRET facility clearance within 6 months of contract award. The offeror may assume a safeguarding of None within its proposal response. Alternatively, the offeror may provide a valid DSS TOP SECRET facility clearance as evidence of its capability (see Note below).

Note: If providing a valid facility clearance for either SECRET or TOP SECRET, it is the Offerors responsibility to ensure its information is accurate and complete in the National Industrial Security System. Additionally, the Offeror shall ensure the CAGE code provided in Section L, Att L-1, Volume 1, Table KA is consistent with its CAGE code in the National Industrial Security System.

3. VOLUME 3 - PAST PERFORMANCE

Note: This volume shall not contain any reference to the cost or price aspects of the offer.

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-2 Past Performance Questionnaire (PPQ)

Attachment L-3 Past Performance Contract Data

For this volume, the Offeror shall identify all relevant contracts (where for the purpose of these instructions the term contract also refers to delivery order or task order), or those portions of a relevant contract, where performance meets the definition of recency (defined in Section M) for the principal entities, identified in Table KA-1 (Offeror Summary). The relevant contracts provided for each principal entity shall be relative to its proposed role and responsibilities identified in Table KA-1 (Offeror Summary). Offerors shall also identify relevant contracts that meet the definition of recency (defined in Section M) that had any show-cause notices, cure notices, or termination for default.

The Offeror shall complete the Table PP-1 (Relevant Contract Summary) for the principal entities proposed contract references (CRs) for Past Performance references performed within three years of the solicitation issuance date. The Offeror shall submit no more than three (3) Past Performance Information as the Prime Contractor, no more than two (2) for each principal subcontractor, and/or no more than two (2) for each JV team member. The Offeror shall label CRs consistently throughout its proposal volumes and tables.

The offeror may modify Table PP-1 to align with their proposed teaming arrangements by adding or deleting individual rows. (For example, delete rows for JV Team members if not proposing a JV teaming arrangement) however, do not provide any information beyond what is requested within the column headers.

Table PP-1 Relevant Contract Summary

Offeror:

Entity Name Contract Reference

Contract Number

Contract Type Contract Title

Prime or Joint Venture Company

P1 P2 P3

JV team member A (where applicable)

T1 T2

JV team member N (where applicable)

T3 T4

Subcontractor A S1

S2

Subcontractor B S3 S4

In Annex D (Final Versions of Previous Statement of Work (SOW)/Performance Work Statement (PWS)/Other Supporting Documentation for Past Performance), the Offeror shall provide an electronic copy of the contractually executed final version of the statement of work (SOW) or Performance work statement (PWS), and any other elements of the contract (e.g. specification, CDRLS) that support the relevancy criteria from each contract or delivery/task order reference identified in Table PP-1

(Relevant Contract Summary). For CRs that contain delivery/task orders, the Offeror shall additionally provide the work description for each specific delivery/task order. For CRs where the Offeror performed as a subcontractor, the Offeror shall also provide a complete electronic copy of the SOW/PWS or other documentation of the agreement between the prime and subcontractor that clearly defines the portions of the work effort of the Prime’s SOW/PWS that the Offeror performed as a subcontractor.

For all contracts identified that do not have an assessment Report in CPARS, or where the last assessment for an active contract in CPARS is more than 12 months old, the Offeror shall forward a copy of Attachment L-2 Past Performance Questionnaire to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM); or commercial contractor equivalents. Please forward all questionnaires within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond.

Note: The Offeror should not reference this solicitation’s number when distributing the past performance questionnaires to customers. The Offeror should include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to beverley.s.rhamdeow.civ@us.navy.mil and sarah.e.metcalf2.civ@us.navy.mil . The Offeror shall ensure that all points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to this questionnaire, other than to confirm receipt by the recipient. The Government may contact customers identified by the Offeror to obtain follow-up Past Performance Information as needed.

Offerors are reminded that the Government reserves the right to use information to evaluate past performance obtained from sources other than those identified by the Offeror. The Government may send additional questionnaires and/or obtain information from sources identified by the Government evaluation team.

3.2 Authorization Letter(s)

The Offeror should submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from each principal entity (including JV team members), authorizing the release of adverse past performance information to the Offeror. The signed letter(s) should be provided in Annex E. This authorization letter allows the Government to coordinate past performance issue(s) with the Prime Offeror. For any principal entity (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 principal entity. This contact information shall include a name, address, phone number, and email address (including JV team members), with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if it does not submit the Release of Adverse Past Performance Authorization Letters with written consent, then the Government will address any past performance issues directly with the principal entity (including JV team members), and the Offeror will forfeit the opportunity to participate in any related discussions.

3.2 Relevant Contract Data

For each contract identified for past performance in Table PP-1 (Relevant Contract Summary), the Offeror shall complete attachment L-3 (Past Performance Contract Data), according to the instructions within the attachment and submit it as a separate electronic file. Please note that this form is a summary of the principal entities’ relevant contract data. All detailed information and comparative analysis of the past performance CRs to this solicitation’s requirements shall be provided in Volume 3 (Past Performance), Section 3.3 (Contract Reference Data), of the Offeror’s proposal. The contract references designated in Table PP-1 (Relevant Contract Summary) shall be used in completing Volume 3 (Past Performance) and all CRs shall be numbered the same throughout all of the Offeror’s proposal volumes (i.e., the contracts identified as P1, S1, T1, C1 etc.)

If a contract has delivery order (D.O.s) or task orders (T.O.s), provide a separate CR and separate PP-2 tab for each D.O/T.O. The Offeror may use one reference number/PP-2 tab for multiple D.O.s/T.Os if they are the same work effort and performed under the same CPAR; however, identify the dollar amount and period of performance for each. Do not provide a CR to the basic contract.

If the Offeror is proposing as a JV, the Offeror should provide the relevant contracts for the JV as a whole, and for each team member of the JV.

3.3 Contract Reference Data

The burden of providing thorough and complete past performance and systemic improvement information remains with the Offeror.

For each contract identified in Table PP-1 (Past Performance Contract Data), the Offeror shall provide contract data regarding relevancy, past performance information, and demonstrated systemic improvement, as described below, organized by contract reference. For any contract references where the principal entities are aware of problems, the Offeror shall describe the issues in section 3.3.b (Past Performance Information). For each past performance problem identified, describe the status of the systemic improvement efforts in section 3.3.c (Demonstrated Systemic Improvement).

a. Relevancy: Offerors are required to explain what aspects of the CRs are deemed relevant, as defined by Section M, to this solicitation’s requirements. To facilitate the Government’s relevancy analysis, Offerors shall provide a comparative analysis for each CR to explain how the CR is relevant to the requirements. Within the comparative analysis, Offerors should identify the relevant portions (sections, paragraphs, and page numbers) of the referenced contract’s SOW/PWS (Annex D) to clearly identify how past efforts performed are similar to this solicitation’s requirements. In addition, the referenced sections only need to be identified and the full text does not need to be broken out separately from the complete SOW/PWS.

The reference contract(s) provided should be relative to each principal entity’s proposed role/responsibility identified in Table KA-1 (Offeror Summary) versus relative to the whole solicitation. For example, a subcontractor who is being proposed to perform only software has a past contract whose total work is software. Even though the software effort is only 10% of the hypothetical solicitation’s effort, the previous contract relates to 100% of the subcontractor proposed effort for the hypothetical solicitation.

For a discussion on CAGE Code /SAM UEID, refer to section 1.0 Volume 1 (Contract Administration). Offerors should be advised that the CAGE Code /SAM UEID for each referenced contract is considered as part of the Relevancy determination, which determines if the contract reference will be included in the Past Performance evaluations. Note: Any information regarding CAGE Code /SAM UEID should be included within Volume 1 (Contract Administration) and does not need to be repeated here.

Offerors are advised that contracts assessed as not relevant by the Government will not be considered in the Past Performance assessments.

b. Past Performance Information: For each CR the Offeror shall provide a brief description of its performance…