SPS Amendment 0004.pdf

N0002422NR92107

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 below :

1. CONTRACT ID CODE PAGE OF PAGES

S 1 31

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

16C. DATE SIGNED

BY 13-Jan-2023

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 N0002423R4107

X 9B. DATED (SEE ITEM 11)

23-Nov-2022

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

13-Jan-2023

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD, DC 20376-2030

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002423R4107

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION E - INSPECTION AND ACCEPTANCE

The following have been deleted:

52.246-16 Responsibility For Supplies APR 1984

SECTION F - DELIVERIES OR PERFORMANCE

The following have been added by reference:

52.242-15 Alt I Stop-Work Order (Aug 1989) - Alternate I APR 1984

The following have been deleted:

52.242-15 Stop-Work Order AUG 1989

SECTION G - CONTRACT ADMINISTRATION DATA

The following have been modified:

G-242-H001 GOVERNMENT CONTRACT ADMINISTRATION POINTS-OF-CONTACT AND

RESPONSIBILITIES (NAVSEA) (OCT 2018)

(a) The Government reserves the right to administratively substitute any of the points of contact listed below at any time.

(b) The contracting officer is the only person authorized to change this contract or orders issued thereunder. The Contractor shall not comply with any order, direction or request of Government personnel

- that would constitute a change - unless it is issued in writing and signed by the Contracting Officer or is pursuant to specific authority otherwise included as part of this contract. If, in the opinion of the contractor, an effort outside the existing scope of this contract is requested, the contractor shall promptly comply with the Notification of Changes clause of this contract.

(c) The points of contact are as follows:

(i) The Procuring Contracting Officer (PCO) is:

Name: Jerry Low

Address: NAVAL SEA SYSTEMS COMMAND SEA02

1333 ISAAC HULL AVE, SE

WASHINGTON NAVY YARD, DC 20376-2030

Phone: (202) 781-2397;

E-mail: jerry.low1@navy.mil

(ii) The Contract Specialist is:

Name: Jason Chan

Address: NAVAL SEA SYSTEMS COMMAND SEA02

1333 ISAAC HULL AVE, SE

WASHINGTON NAVY YARD, DC 20376-2030

Phone: (202) 781-2831;

E-mail: jason.chan1@navy.mil

(iii) The Administrative Contracting Officer (ACO) is: TBD

Name: Anthony Ramos

Address: 3755 BRINSER STREET SUITE 1

SAN DIEGO, CALIFORNIA 92136-5205

Phone: (619) 545-1574

E-mail: David.A.Ramos6.civ@us.navy.mil

(d) The Contracting Officer’s Representative (COR) is the contracting officer’s appointed representative for technical matters. The COR is not a contracting officer and does not have the authority to direct the accomplishment of effort which is beyond the scope of the contract or to otherwise change any contract requirements. An informational copy of the COR appointment letter, which provides a delineation of COR authority and responsibilities, will be provided upon award of this contract.

The Contracting Officer’s Representative (COR) is: TBD

Name: [ * ]

Address:

[ *Street ]

[ *City, State, Zip ]

Phone: (Area Code) xxx- [xxxx]; FAX: (Area Code) xxx- [xxxx]

E-mail: [ * ]

(e) The Alternate Contracting Officer’s Representative (ACOR) is responsible for COR responsibilities and functions in the event that the COR is unavailable due to leave, illness, or other official business. The ACOR is appointed by the contracting officer; a copy of the ACOR appointment will be provided upon award of this contract.

The Alternate Contracting Officer’s Representative (ACOR) is:

Address:

[ *City, State, Zip ]

(f) The Technical Point of Contact (TPOC) is the contracting officer’s representative for technical matters when a COR is not appointed. The TPOC is responsible for technical issues of contract administration, such as providing all items of Government Furnished Information (GFI), Government Furnished Material

(GFM) and Government Furnished Equipment (GFE) if specified in the contract as well as the inspection and acceptance of all contract deliverables.

The Technical Point of Contact (TPOC) is:

Address: [ *Street ]

[ *City, State, Zip ]

(g) The Alternate Technical Point of Contact (ATPOC) is responsible for TPOC responsibilities and functions in the event that the TPOC is unavailable due to leave, illness, or other official business.

The Alternate Technical Point of Contact (ATPOC) is:

Address:

[ *City, State, Zip ]

(h) The Ombudsman will review complaints from the contractors and ensure that all contractors are afforded a fair opportunity to be considered, consistent with the procedures in the contract.

The Ombudsman is:

Name: Ms. Cindy Shaver, Deputy Assistant Secretary of the Navy (Procurement)

Address: 1000 Navy Pentagon, Washington, DC 20350 Phone: (703) 614-9600

E-mail: NCAG@navy.mil

(i) The Authorized Ordering Person(s) for Per-Call Maintenance is responsible for issuing and maintaining records for any per-call orders for remedial maintenance placed under this contract. No per-call order shall be placed outside the scope of this contract and the cumulative total of all orders shall not be in excess of any not-to-exceed amount specified in the contract. Per-call orders shall not, in any way, modify any terms and conditions of the contract.

(j) The Authorized Ordering Person(s) for Per-Call Maintenance is:

Address:

[ *Street ]

[ *City, State, Zip ]

Phone: (Area Code) xxx- [xxxx];

(k) The Contractor's point of contact for performance under this contract is:

Title: [ * ]

Address:

[ *Street ]

[ *City, State, Zip ]

[ * ] To be completed at contract award

(End of text)

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

1.0 GENERAL

Complete proposals submitted in response to the Request for Proposal (RFP) shall be received prior to the date specified in block 9 of the Standard Form (SF) 33 (solicitation document).

2.0 GENERAL CONTENT REQUIREMENTS

The Offeror’s proposal is the sole basis for evaluating the technical merits of what is being offered, the degree to which the Offeror’s claims of performance capability and capacity are supported, and the ability of the Offeror to perform In Accordance With (IAW) the requirements. Proposals submitted shall be sufficiently detailed as to clearly demonstrate that the Offeror has a thorough comprehension of all requirements, including all special provisions of the RFP, to enable Government personnel to make a thorough evaluation of the proposal and to arrive at a sound determination as to whether the prospective Offeror will be able to perform IAW the requirements of the RFP.

Offerors are advised to submit proposals that are complete, clear, and consistent in all respects without the need for additional explanation or information. Offerors are cautioned against the use of general, vague, or unsubstantiated statements which prevent concise proposal evaluation.

The format and content of the proposal shall contain a response to the topics of discussion noted below. Information presented shall appear in the same order as outlined. A master table of contents identifying major subsections by number, title, page number and volume shall be provided in each volume.

The Offeror’s proposal shall address the entire RFP and all of its amendments and attachments. The proposal shall constitute an offer and will indicate the Offeror’s unconditional assent to the terms and conditions in this RFP. Any objection to any of the terms and conditions will constitute a deficiency which may make the offer unacceptable.

Alternate proposals will not be considered and shall not be submitted.

The Offeror shall not submit the Security Classification Specification as a part of the proposal. The DD Form 254 will, however, become a material part of any resultant contract.

Documents, exhibits, and other attachments that form a part of this RFP and will become part of any resultant contract are identified in Section J. The following RFP sections listed below (which also form a part of this RFP), will not become a part of any resultant contract:

Section K – Representations, Certifications and Other Statements of Offerors

Section L – Instructions, Conditions, and Notices to Offerors

Section M – Evaluation and Award Factors

Offerors are expected to reach a reasonable understanding of the requirements of this RFP by careful study

(particularly Section C—Descriptions/Specifications and Section J—List of Documents, Exhibits, and Other

Attachments) and by the application of qualified knowledge and experience. If such a review establishes the need for correction or clarification, such need should immediately be brought to the attention of the Contract Specialist and Procuring Contracting Officer (PCO), noted above, so that the matter can be resolved and so that, if necessary, official dissemination of such correction or clarification can be made to all Offerors.

The Government intends that all work authorized for the contemplated repairs and alterations be compatible with the duration of the scheduled performance period for each availability. The Offeror should, therefore, inform the

Government prior to the due date for proposals of any work item or sum of work items that appears to require a longer period.

3.0 SUBMISSION OF PROPOSALS

PROPOSALS ARE DUE AT 1700 EASTERN STANDARD TIME ON TUESDAY, 31 JANUARY 2023 AT THE

NAVAL SEA SYSTEMS COMMAND.

The Offeror’s proposal shall be detailed, specific, and complete to enable a thorough evaluation of the proposal and a sound determination that the proposal will meet or exceed the requirements and objectives set forth in the RFP.

Proposals shall be submitted in accordance with the instructions herein, and non-conformance with the specified required content may be cause for rejection of the proposal.

If it is determined that an offer is not in compliance with the page limitation of that volume of the proposal, Offerors are cautioned that pages above the specified page limit within each volume will be removed and not evaluated (i.e. if the maximum page limit is 30 and 35 pages are submitted, pages 31 through 35 will not be evaluated). Offerors are cautioned that some factors have additional page limitation criteria, specific to that section (SB Plan/SB participation). The page count shall not include cover pages, title pages, table of contents, or tab pages. NOTE:

Unless specifically excluded above, all pages will count towards the page limitations, including all required plans.

Exhibits/Diagrams/Charts are allowable but shall have type no smaller than 8-point font size and 1 inch margins, and should be viewable/distinguishable by the average person with the naked eye. The narrative material in the proposal shall be single spaced, with type no smaller than 10-point font size and have 1 inch margins.

The proposal shall be valid for no less than 180 days from the date of RFP closing. The proposal shall provide comprehensive responses to the areas provided for in this section. The proposal shall be a complete response to the

Statement of Work (SOW) and the requirements of this RFP.

Each Offeror must (1) submit an offer, (2) submit written information that pertains to its capability, and (3) submit supporting cost data. When evaluating an Offeror’s capability to perform the prospective contract, the Government will consider how well the Offeror complied with these instructions. The Government will consider an Offeror’s noncompliance with these instructions to be indicative of the type of conduct that it may expect from the Offeror during contract performance.

The first page of each volume shall be in accordance with FAR 52.215-1 Instructions to Offerors – Competitive

Acquisition. The Offeror shall identify any restrictions to the disclosure of its proposal by marking the proposal

IAW paragraph (e) of FAR Provision 52.215-1.

Formal Submission: Initial proposals and any modifications thereto are to be submitted to the Contract Specialist on or before the closing date and time cited elsewhere in this solicitation (Note 1, below). Faxes, hard copy, and/or responses through Navy Electronic Commerce Online (NECO) are not acceptable. One (1) electronic submission of each volume shall be sent through the Procurement Integrated Enterprise Environment (PIEE) website Solicitation module of the complete proposal. The PIEE website is as follows: https://piee.eb.mil. To register, click the

“Register” button and agree to the Privacy Act Statement; select “Vendor” as the type of user you are; choose “User

ID \Password” as how you will be accessing the PIEE applications and create a User ID and Password; choose security questions and answers; complete the user profile; enter company information; in the Roles screen, select

“SOL – Solicitation” under Application and “Proposal Manager” under role and press the “+Add Roles” button;

Roles summary will pop up and enter your CAGE under Location Code / CAGE (a Contract Administrator must be in System of Award Management (SAM) prior to entering this information); complete the justification (example:

required for proposal submission); and sign the Statement of Accountability Agreement. It is highly recommended that the PIEE Solicitation Module account be established and the communication path confirmed well in advance of the proposal submission deadline. As the PIEE system is just being set up, and if issues arise, vendors may submit their proposals via their standard submission process, if they have a system in place that allows for secure proposal transmission. Alternate systems shall be tested with the submission points of contact (Jerry Low and Jason Chan) prior to the proposal submission date to ensure operability and timely submission. Failure of an alternate submission method may render the offer unawardable.

https://piee.eb.mil/

Electronic Submissions of the proposal, as indicated below, shall be submitted to the Contract Specialist, Jason Chan at jason.chan1@navy.mil and the PCO, Jerry Low at jerry.low1@navy.mil No Later Than (NLT) 1700, Eastern

Standard Time (EST), on Tuesday 31 January 2023. Responses not received at the time specified above will be considered late and not considered for award. The Offeror is responsible for the condition of its delivered proposal.

Timely submission to PIEE does not constitute complete submission. As such, Offerors are strongly encouraged to submit early to allow time to confirm receipt of the proposal materials with the PCO or Contract Specialist.

Although the Government will consider minor proposal deadline extensions to accommodate PIEE transmission issues, the Government may not approve such extension requests very close to the submission deadline. Offerors should contact the PCO and Contract Specialist by email as soon as they are aware of any technical difficulties.

Note 1: Hand-carried and mail delivered proposals will not be accepted. Submission of e-mail offers is not authorized for this solicitation. The PIEE website is the only acceptable method of submission, unless an alternate vendor secure proposal submission process is arranged with the Government.

Electronic proposal submissions and supporting information shall be suitable for reading in the standard Microsoft

Windows suite, in accordance with 252.215-7012 REQUIREMENTS FOR SUBMISSION OF PROPOSALS VIA

ELECTRONIC MEDIA (JAN 2018). Submitted electronic files shall not be compressed. Included files shall be created/prepared using Microsoft Office 2010 compatible applications. Spreadsheets, worksheets, and workbooks shall be prepared using Microsoft Excel compatible applications. Schedules shall be created and submitted using

Microsoft Project compatible applications, in addition the Offeror shall submit schedule as a higher level

PDF. Graphics, photographs, and other data beyond the capability of Microsoft Office 2010 compatible applications may be submitted in Adobe Acrobat format. Electronic spreadsheets shall not be compiled or password protected;

and all cells and formulas shall be visible, editable, and unprotected. Formulas shall be maintained in each Excel sheet to permit verification of calculations, and revision of output(s) through variation of inputs(s). Any tables contained within submitted narrative shall be capable of being edited (i.e. not embedded pictures or screenshots). Submitted files shall not reference external data. The Offeror shall screen all proposal submission and supporting information for computer viruses prior to submittal. Submitted electronic files shall be limited to the following extensions:

.docx Microsoft Word

.xlsx Microsoft Excel

.pptx Microsoft PowerPoint

.pdf Adobe Acrobat

.mmpx Microsoft Project

Acceptance of Terms and Conditions: The submission to the Government in response to the RFP -- i.e., the

Offeror’s offer, including the entire RFP and all of its attachments -- will constitute an offer and will indicate the

Offeror’s unconditional assent to the terms and conditions in this RFP. An objection or exception to any of the terms and conditions will constitute a deficiency which may make the offer unacceptable.

Offerors shall allow the maximum practicable opportunity for Small Business to participate in contract performance and shall submit a Small Business Subcontracting Plan as required by FAR 19.702 with the Cost Proposal.

SUBCONTRACT INFORMATION

In requesting proposals from prospective subcontractors, Offerors shall provide all necessary information for the contemplated purchase. The Government will not advise prospective subcontractors as to the requirements of their transactions with Offerors, nor will the Government respond to direct inquiries from prospective subcontractors concerning clarifications of specification or solicitation requirements. ALL SUCH REQUESTS FOR

CLARIFICATION MUST BE SUBMITTED TO THE GOVERNMENT THROUGH THE PRIME

CONTRACTOR (OFFEROR).

The Notional Work Package(s) (NWPs), Non-Nuclear Technical Specifications and the Chief of Naval Operations

(CNO) Availability Schedule (Attachments J-1, J-3 and J-5) will not be posted as a separate attachment to the

Solicitation on www.sam.gov. Offerors’ interested in receiving a copy of the NWP are required to submit a request http://www.sam.gov/ via email to the Contract Specialist, Jason Chan jason.chan1@navy.mil and the PCO, Jerry Low at jerry.low1@navy.mil and a copy will be provided via email.

3.1 PROPOSAL OVERVIEW

A. Evaluation Categories

The Government shall evaluate Non-Cost and Cost factors.

The Technical evaluation is comprised of three (3) Non-Cost factors: (A) Management Approach; (B)

Technical Approach; and (C) Resource Capabilities.

The Past Performance evaluation is a Non-Cost factor.

The Cost is a Cost factor.

B. Proposal Structure

(1) Paragraph Numbering. Paragraph numbering shall conform to the following system:

Volume I. SF33 Solicitation Set

Volume II. Technical

A. Management Approach

B. Technical Approach C. Resource Capabilities

Volume III. Past Performance

Volume IV. Cost

(2) The Offeror shall structure the Proposal so information provided for each section is as comprehensive as possible. The information provided for each section should be sufficiently self-contained to minimize the need to refer to other Proposal sections for evaluation purposes. If cross-references are needed, page and paragraph numbers shall be included.

(3) Section M of this solicitation provides the relative importance of the evaluation factors.

(4) Four separate volumes: Volume I (SF33 Solicitation Set), Volume II (Technical), Volume III

(Past Performance), and Volume IV (Cost) are required. The page limitations are identified in table L1 below. The Offerors shall ensure consistency, defined as “free from variation”, between the technical proposal and cost proposal. During the course of evaluating the technical and cost proposals, the PCO will validate that the technical proposal and cost proposal are consistent.

Specifically, the costs proposed will be evaluated and verified using historical and current market information to confirm costs proposed are within reason and consistent with the technical approach. Any inconsistencies between the technical and cost proposals may be viewed as weaknesses and/or risks in the proposals, and the offer may, at the Government’s discretion, be considered unacceptable and eliminated from competition for award.

Table L1- Volume Descriptions

VOLUME/

SECTION

TITLE PAGE LIMITATIONS Electronic via PIEE mailto:jerry.low1@navy.mil

Note- The RFP response must be submitted in four (4) separate volumes (each Volume is a separate e-file if it fits in the 1.9GB size but can be separated into individual files if needed) as delineated above, with any sub-headings divided and easily recognizable upon viewing within each volume, within the specified page limitations. No additional volumes or pages will be reviewed. Sub-heading are for organization purposes, vendors must still address entire Section L.

(5) Offerors are cautioned that, in accordance with the clause “Instruction to Offerors-Competitive

Acquisitions” (FAR 52.215-1), the Government intends to award a contract on the basis of initial proposals received, without discussions. Therefore, each proposal shall contain the Offeror’s best terms from a cost and technical standpoint.

(6) Proposal Outline: The proposal submission shall be accompanied by a cover letter that contains the information outlined in FAR 52.215-1 (c)(2). The cover letter shall also affirmatively state that the accompanying proposal:

1. Is for all requirements as stated in the solicitation (including all attachments, appendices, and amendments thereto)

I SF33 SOLICITATION SET No Page Limit 1 i Cover & Title Page No Page Limit ii Table of Contents No Page Limit

1.1 Offer (items identified in L 3.4.1) No page Limit

1.2 General Information (items identified in L 3.4.2) No page Limit

II TECHNICAL CAPABILITY NTE 125 PAGES 1

i Cover & Title Page No Page Limit ii Table of Contents No Page Limit iii Introduction Part of the 125 pg count

1.0 Factor 1: Management Approach

1.1 Overall Management Approach/Management Plan (items identified in L 3.5.2)

Part of the 125 pg count

1.2 Organization Plan Part of the 125 pg count

1.3 Transition Plan Part of the 125 pg count

1.4 Subcontract Management Plan No page limit

1.5 Small Business Participation No page limit

2.0 Factor 2: Technical Approach

2.1 Overall Technical Approach/Technical Plan (items identified in L

3.5.3)

Part of the 125 pg count

3.0 Factor 3: Resource Capabilities

3.1 Overall Resource Plan Part of the 125 pg count

III Factor 4: PAST PERFORMANCE Required 3 efforts 1 i Cover & Title Page No Page Limit ii Table of Contents No Page Limit

1.0 Past Performance Example 1 No Page Limit

2.0 Past Performance Example 2 No Page Limit

3.0 Past Performance Example 3 No Page Limit

IV Factor 5: COST PROPOSAL NO PAGE LIMIT 1 i Title Page, Cover Letter, Table of Contents No Page Limit

1.0 Prime Contractor Cost Exhibits (Exhibit L-3) No Page Limit

2.0 Subcontractor Cost Data (Exhibit L-3) No Page Limit

3.0 Contractor Estimating Rationale/Cost Proposal Narrative No Page Limit

4.0 Other Data No Page Limit

2. Is made without qualification or exception to any terms and conditions appearing in the solicitation

3. Is valid for a period of 180 days from the date established for the receipt of proposals

Offerors shall address any exceptions to solicitation’s requirements/terms/conditions PRIOR to proposal submission and NOT within its submission. Any exceptions taken to the terms of the solicitation that are not adjudicated through an amendment to the solicitation, or otherwise adjudicated, may render proposal submissions as unacceptable.

The proposal shall be organized and tabbed in accordance with the Volume, Factor, and layout detailed in the following outline:

Each of Volumes I, II, III, and IV shall contain the following items in addition to the Offeror’s proposal data required by this RFP:

a. Cover & Title Page

The cover and Title page shall include the following:

Title of Proposal

Volume number and title

RFP number

Name, Point of Contact Information, address, telephone number, and email address of the Offeror

The following statement: “The Offeror confirms that it will comply with the requirements of N00024-23-R-4107, as amended, regardless of 1) any references in

Volumes I, II, III, and/or IV to request a waiver to an RFP requirement; and 2) any references in Volumes I, II, III, and/or IV to data requested to be provided by the

Government post-award.”

Signature and Date

b. Master Table of Contents

The table of contents shall provide sufficient detail, including page numbers, so that factors and sections can be easily located.

C. Solicitation Responsiveness

Offerors are advised to submit proposals that are complete, clear, and consistent in all respects without the need for additional explanation or information. Offerors are cautioned against the use of general, vague, or unsubstantiated statements, which prevent concise proposal evaluations. Each factor will be evaluated on how well the response meets the requirements of the solicitation. The response that completely addresses all of the solicitation requirements may be judged superior to the response that minimally addresses solicitation requirements.

D. Offerors Compliance

Offerors must comply with specific information submission requirements found below under Paragraph III entitled, “Instructions for Technical Proposal Preparation” and paragraph IV entitled, “Instructions for Cost

Proposal Preparation.” Failure of the Offeror to comply with all aspects of solicitation requirements located within the “Technical Proposal” or “Cost Proposal” section may, at the Government’s discretion, render the proposal unacceptable, and the Offeror may be eliminated from competition for award.

E. Competitive Range

If an award is not made on the basis of initial proposals, the PCO will make the determination as to which proposals are in the “competitive range.” The competitive range shall be determined based on the results of the evaluation of initial technical and cost proposals, considering all evaluation criteria, and shall include the most competitive proposals. The number of proposals within the competitive range may also be reduced if the PCO determines the number of most competitive proposals that might otherwise be included within the competitive range exceeds the number at which an efficient competition can be conducted.

F. Discussions/Final Proposal Revision (FPR)

(1) If discussions are held, all Offerors selected to participate in discussions shall be advised of weaknesses and risks in their proposals, and shall be offered a reasonable opportunity to correct or resolve such weaknesses and risks and to submit such technical and cost information, or other revisions to their proposal, that may result from such discussions.

(2) The PCO intends to make award without conducting discussions. At his or her discretion, the PCO may determine the competitive range and elect to conduct either verbal or written discussions, or both.

If the PCO elects to conduct discussions, the PCO reserves the right to conduct oral discussions, consisting of presentations of discussion question responses followed by a question-and-answer session. At such time, the PCO will also provide the Offerors with information as to the format, length and rules which will govern the conduct of oral presentations of discussion question responses. The content of these presentations will be in response to questions the PCO may submit to the Offeror during the discussion period. The purpose and goal of presentations of discussion question responses is to clarify and gain a better understanding of questions asked the Offeror by the Government and the

Offeror’s responses. The execution of oral discussions will not constitute part of the Offer. Written answers to discussion questions will become part of the proposal only if subsequently specifically referenced in the FPR. When discussions are completed, the PCO will close discussions and request

FPRs.

3.2 CROSS REFERENCING

Each volume shall be written to the greatest extent possible on a stand-alone basis so that its content may be evaluated with a minimum amount of cross-referencing to other volumes of the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal.

Each volume shall contain a glossary of all abbreviations and acronyms used.

Glossaries do not count against the page limitations for their respective volumes.

3.3 COMMUNICATIONS WITH NAVSEA

3.3.1 Solicitation and Amendments

Solicitation information and amendments will be made available through the Government Contract

Opportunities website found at: www.sam.gov, as well as PIEE.

The solicitation, which will include related files (i.e., RFP and Section J attachments) listed under the solicitation number, can then be downloaded directly to your workstation. Offerors are required to periodically check for responses to questions and any issued amendments.

3.3.2 Questions Concerning the Solicitation

Offerors may submit questions requesting clarification of RFP requirements by electronic mail to Jason

Chan at jason.chan1@navy.mil and Jerry Low at jerry.low1@navy.mil using Attachment L-1.

http://www.sam.gov/ mailto:Rickeyea.Singleton.civ@us.navy.mil mailto:jerry.low.1@navy.mil

Offerors shall use the subject heading for the email correspondence: N00024-23-R-4107 RFP Bidder

Questions.

Only questions submitted by electronic mail will receive a response. Questions and responses will be distributed electronically via www.sam.gov to all potential Offerors as an amendment to the solicitation and will not be attributed to any individual or organization. Questions/comments must contain at a minimum: the document name, document date, specific page, paragraph, clause, or other definitive citation requiring clarification, in addition to the question posed. Questions should not include proprietary or otherwise protected information of the Offeror.

3.4 VOLUME I – SF33 SOLICITATION SET

3.4.1 Offer

The offer is the document that will be used to make an award to the successful Offeror and must include the following:

a. Standard Form 33, “Solicitation, Offer and Award”, with blocks 12 through 18 completed by the Offeror.

b. Solicitation Amendment(s) (if any) – The Offeror shall submit a signed complete copy of each amendment(s).

c. RFP Sections B through J - The Offeror shall submit Sections B through J with all appropriate information required by the RFP completed.

d. RFP Section K, “Representation, Certifications and Other Statements of Offerors”, completed by the

Offeror or a statement verifying the information has been completed in the System for Award Management with the date the registration remains valid.

e. Exhibit(s), Attachments, and Schedules – The Offeror shall submit a copy of or provide written acknowledgement and acceptance of all Exhibits, Attachments, and Schedules, which will form a part of any resultant contract. All Exhibits, Attachments, and Schedules that require the Offeror to provide information shall be completed in their entirety.

f. Small Business Subcontracting Plan as required by FAR 19.702. The proper completion and submission to the Government of the above items will constitute an offer and will indicate the Offeror’s unconditional assent to the terms and conditions in this RFP in any attachments hereto. Any objection to any of the terms and conditions of this RFP will constitute a deficiency which may make the offer unacceptable. An Offeror may correct a deficiency only through discussions (see FAR 15.306). The Government intends to award a contract without discussions, as permitted by FAR 15.306(a) and 52.215-1. However, the Government reserves the right to conduct discussions and to permit Offerors to revise their offers.

g. Miscellaneous: In the event that any portion of the technical proposal is written by someone who is not a bona fide employee of the Offeror who is submitting the proposal, a certificate to this effect shall be signed by a responsible officer of the Offeror and shall show the person's name, employment capacity, the name of his/her firm, the relationship of that firm to the Offeror’s, and the portion of the technical proposal written by that person.

3.4.2 General Information

Offerors shall provide the source of approval, the latest dates, and the current status in which the Offeror had the following:

http://www.sam.gov/

a. Accounting System. Offerors are cautioned that this contract contains cost reimbursement provisions and a cost reimbursable contract may only be awarded to an Offeror that meets the limitations set forth in FAR

16.301-3;

b. Purchasing System;

c. Estimating System;

d. Adequacy of the Offerors Disclosure Statement pursuant to FAR 30.201-3 and FAR 52.230-1.

Offerors shall identify the cognizant Administration Office (POC name, phone number, email address, and physical address) and provide copies of the letters transmitting the approvals of the above identified systems with its proposal submission.

Offerors shall provide a summary of this information in the following format:

Table L2: General Information

Business System Current Status

Review Date

ACO/Cognizant Administration Office

POC

Telephone Number

Email Address

Accounting System

Purchasing System

Estimating System

Disclosure Statement Adequacy

3.5 VOLUME II – TECHNICAL APPROACH

3.5.1 INSTRUCTIONS FOR TECHNICAL PROPOSAL PREPARATION

In responding to the Technical Factors of Management Approach, Technical Approach and Resource

Capabilities below, Offerors shall demonstrate they have a thorough understanding and capability to perform the efforts in the SOW cited in Section C. The Offeror shall also utilize the NWPs for CIA and

PIA Work Items and the availability schedule in Attachment J-1/J-5 for repair and modernization labor hour estimate projections in responding to the Technical Proposal requirement. Solely for the purposes of developing Technical Proposals, Offerors shall assume the CNO availabilities listed in Attachment J-5 of this solicitation as well as three (3) CMAV per year. The actual number of CMAVs, as well as the duration of and work to be accomplished during any individual CMAV, will vary depending on operational schedules and other contingencies.

A technical proposal is required from each Offeror and will be evaluated as specified in Section M. The

Offerors shall provide the required copies of their technical proposals as specified in Section L, “Submission of Proposals”, containing information organized under the following:

Management Approach

Technical Approach

Resource Capabilities

Past Performance

The required content for the technical proposal is described below.

The PCO reserves the right to request such additional information regarding scheduling, manpower, facilities, and management organization and capabilities as may be necessary to determine the Offeror’s qualifications for award of a contract, to determine the relative merit of the Offeror’s proposal, or to otherwise clarify any aspect of the proposal.

Offerors should note that if awarded a contract based upon this solicitation, the Offeror’s technical proposal or portion thereof may be incorporated into the contract by reference.

Release of Technical Information: All technical information submitted pursuant to this solicitation is for the exclusive use of Government representatives, and will be treated as business confidential and will not be publicly disclosed, provided that, where a request for disclosure of such technical information is submitted to the Government pursuant to the Freedom of Information Act (5 U.S.C. 552a), the Government will not disclose the Offeror’s technical information if public disclosure of information would substantially harm the Offeror in its competitive position. In order to help ensure non-disclosure, the title page of the technical proposal and other sheets of proposal data should be marked with restrictive legends contained in the Solicitation Instruction in Section I entitled “VALIDATION OF RESTRICTIVE MARKINGS ON

TECHNICAL DATA,” and the technical proposal should be enclosed in a sealed envelope marked

“TECHNICAL INFORMATION – NOT TO BE PUBLICLY DISCLOSED”.

CAUTION: The technical proposal should contain brief statements of fact rather than wordy, generalized narratives.

The technical proposal shall consist of no more than 125 pages. Offerors are cautioned that no more than the first 125 pages of technical proposal will be evaluated. Any portion of a technical proposal which exceeds the 125 pages will not be evaluated and will be treated in the same manner as late proposals or modifications in accordance with the Section L clause in this solicitation entitled, “Instructions to Offerors-

Competitive Acquisitions” (FAR 52.215-1). The technical proposal should be properly paginated, with the appropriate page number marked on each page.

Each single side of a piece of paper (if printed) shall be counted as one page toward the 125-page limit, with the exception of the following items:

(a) The first page of the technical proposal, which shall consist of a single title page containing only the following basic information: volume number and category name; the solicitation number; the name of the contract; Offeror’s name; the full name and address designation of the Naval Sea Systems Command

(NAVSEA); and the Offeror’s position regarding disclosure of proposal data. No pages placed before this title page will be evaluated.

(b) The table of contents for the technical proposal, which shall immediately follow the title page described in item (a) above.

(c) Any pages in the proposal used solely for the purpose for separating sections of the proposal, or as tabs.

(d) The resume(s) shall not exceed three (3) pages for each individual(s). Pages in excess of three (3) will be counted toward the 125-page limit for the technical proposal. It is the intention of this contract to not include a key personnel list due to the completion nature of this effort. The Government has requested resume(s) for one (1) labor category only, the Program/Project Manager.

(e) Up to ten (10) pages of exhibits included in the technical proposal. If printed, each single side of a piece of paper (if printed) in excess of the ten (10) page allowance for exhibits will count as one (1) page towards the 125-page limit for the technical proposal. Exhibits/Diagrams/Charts are restricted to standard 8-

1/2”×11” paper, with judicious use of 11”×17” paper Z-folded to 8-1/2”×11” size for items such as facility layout, and organizational charts permitted as necessary. Exhibits/Diagrams/Charts must not contain any text other than simple explanations pertinent to the exhibit.

(f) Letters of commitment from major subcontractors, as described below in Section C. “Resource

Capabilities”.

(g) Past performance information, as described below in “Past Performance”.

3.5.2 VOLUME II – FACTOR 1: MANAGEMENT APPROACH

This part of the proposal should provide a systematic approach that demonstrates a comprehensive understanding and application of management techniques, methods and procedures required to efficiently execute the requirements of this solicitation. Offerors should address the following areas taking into account all the Offeror’s current Government and commercial efforts under contract, the proposed effort under this solicitation and any other submitted proposals.

1. Describe the program management organization to be used for this effort and how it will contribute to the planning and execution of work requirements.

2. Describe the formation, function and responsibilities of the project organizations and information-sharing techniques to be utilized. Specifically discuss the information-sharing techniques between

Government Agencies, the prime contractor and its significant contractors during the production availability.

3. Describe the organization’s plan for management control of subcontractor effort including a comprehensive description of the roles and responsibilities for each major subcontractor and the rationale for selecting each major subcontractor. Major subcontractor as defined in this RFP, both the certified cost or pricing data threshold and ten percent (10%) of the value of the contract under which the subcontract is awarded.

4. Provide the plan to integrate and familiarize all subcontractors to the prime contractor’s Private Sector

Maintenance (PSM) contract execution philosophy and strategy.

5. Provide the total allocation of work that will be accomplished by the prime, by each major subcontractor and by other subcontractors, and describe the basis and computation for which the work allocation was developed (total labor hours, dollars, production hours, etc.). The work allocation percentages must be traceable to the cost proposal and shall be consistent with supporting cost documentation such as Total Proposal Contract Value Summary and Contract Line Item Number

(CLIN) Cost element breakdown in the cost proposal.

6. Discuss the organization’s lines of communication and authority with the Government as well as major subcontractor. Discuss the percentage of time proposed labor mix identified that will be dedicated, on an annual basis, to this effort as well as to existing and other currently submitted proposed work.

7. Provide one (1) resume for prime and one (1) resume for each major subcontractor (as defined in item 3, above), for proposed Program Manager(s). Provide cross-referential information and/or definitions of company-unique personnel titles proposed above and beyond the Program Manager(s), if applicable.

8. Identify any Offeror and/or major subcontractor labor agreements that expire during this stated PSM contract Period of Performance (POP) and contingency plans for labor strikes.

9. Describe the Offeror and major subcontractor cost reporting systems for compiling internal costs and subcontractor costs, and discuss how costs are budgeted, monitored and controlled. Describe how costs are reported to the Accounting Classification Reference Number (ACRN) level and how growth funding and incurred costs will be tracked.

10. Discuss the data deliverable requirements of the contract including execution planning and availability progress reports and project completion reports to the Government.

11. Describe the Offeror’s method for tracking actual progress versus planned progress and processes to regain planned progress when variance occurs.

12. Approach: Offeror shall address their overall management approach and ability to plan, manage, and execute all efforts required by the SOW under this solicitation, including, but not limited to, controlling personnel, controlling utilization of resources, tracking deliverables, monitoring performance and obtaining Government feedback. Offeror shall describe processes to be used by Delivery Order technical leadership to ensure specific subtasks are being performed effectively and efficiently.

13. Organization Plan: Offeror shall provide an organization chart that demonstrates the location of this work in the Offeror’s organization and demonstrate how this effort will receive sufficient corporate-level attention during performance. The plan shall describe the Offeror’s corporate structure and ability to manage a high- performing team, describe the procedures in place for monitoring and controlling costs, and also demonstrate that the Offeror will be successful in undertaking these management and cost control efforts.

14. Transition Plan: The Offeror shall describe the transition process in detail including all steps the

Offeror intends to take in order to assume responsibility from the incumbent Contractor, if applicable, within forty-five (45) days upon contract award. Offeror shall address how personnel are properly trained and skilled with adequate security clearances; and how the Offeror will assume responsibility for support of current programs without discontinuity of work flow or loss of integrity of the programs' current operation. The Offeror shall demonstrate its ability to meet the facility clearance requirement and safeguarding capability requirement identified in the DD254 attached in Section J herein. If the Offeror does not currently possess the required facility clearance, the Offeror shall demonstrate its completion of the preparatory steps necessary to be granted the facility clearance in a timely manner upon contract award. The Offeror shall provide a plan for hiring personnel after contract award. The proposed plan should include a schedule for hiring ramp up and a timeframe of when staffing actions will be completed and any risk mitigation strategies. Staffing actions shall be completed NLT forty-five (45) days after contract award. The plan shall include, but not be limited to: start date, end date, and detailed Plan of Action & Milestones (POA&M) with measurable elements. The Transition Plan shall be consistent with the Offeror’s Technical Approach and Cost proposal. Specific elements to consider include:

a) Transition Team Responsibilities - Offerors shall describe its start-up plan with a detailed explanation regarding how full performance will be achieved on the first day of contract performance. Offerors shall describe their intended mode of establishing management and project staffs, assuming responsibility for support of the programs’ current operation without discontinuity of work flow or loss of integrity of the program’s current operation, and creating interfaces for technical and contract administration. Identify the risks in accomplishing transition of this requirement in a seamless manner and identify specific risk mitigation measures that will be implemented. Costs unique to the implementation of the proposed transition plan shall be clearly identified in the cost proposal.

b) Work Turnover - The Offeror shall provide a plan of action to effectively transfer tasks that are in process at the expiration of the current Contract from the incumbent Contractor, including how the awardee will coordinate communications with the incumbent

Contractor and how it will ensure uninterrupted workflow during the transition process.

c) Incumbent Capture – If the Offeror intends to hire incumbent personnel, the Offeror shall address how the Offeror will transition incumbent personnel and discuss risk mitigation if the Offeror is unable to the incumbent personnel.

d) Security Requirements – The Offeror shall provide a discussion regarding OPSEC, facility clearances, and base access. The Offeror shall provide a plan to implement the required security clearances and physical access requirements of the Contract during the transition period so that service is not interrupted.

e) Quality Assurance - The Offeror shall provide a plan of action to ensure continuation of quality review processes during the transition period from the incumbent to the successful

Offeror.

f) Training - The Offeror shall provide a plan of action to implement personnel training needed during the transition period to ensure continuity between the services provided by the incumbent to the successful Offeror.

g) Archived Material - The plan shall address proposed procedures, tools, and processes for the transfer and storage of all archived programmatic documentation and the establishment of accounts and roles for access to data held…