W519TC23R0022-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offers 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 amendments: (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 ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: 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 data, 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.)

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)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Cost Plus Fixed Fee

0002 2023JUL19

W519TC

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

JOHNNY R. MARTINEZ

EMAIL: JOHNNY.R.MARTINEZ5.MIL@ARMY.MIL

W519TC-23-R-0022

2023JUN21

X

X 2023AUG04 12:00pm

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 23

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: JOHNNY R. MARTINEZ

Buyer Office Symbol/Telephone Number: CCRI-VAC/(309)782-0000

Type of Contract 1: Cost Plus Fixed Fee

Type of Contract 2: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of Amendment 0002 to Solicitation # W519TC-23-R-0022 is to:

1. Extend the due date of proposal submissions from 21 July 2023 to 04 August 2023. The deadline for questions has passed and is not extended.

2. Provide responses to industry questions (Attachment 0038 - Ft Campbell Q&A Responses dated 18 Jul 23)

3. Update Section L, paragraph L.5.1.8

FROM:

L.5.1.8 SECRET Facility Clearance: Offerors must possess a SECRET Facility Clearance by the RFP closing date, at the time of award, and throughout the life of the contract. All Subcontractors who will be performing contract requirements which necessitate facility clearance must also have a SECRET Facility Clearance by RFP closing date, at the time of award, and throughout the life of the contract.

In order for an Offeror/Subcontractor to request and sponsor an individual employee's SECRET Security Clearance to perform the functions identified in the PWS, the Offeror/ Subcontractor must possess a SECRET Facility Clearance by the RFP closing date. Possession of an

INTERIM SECRET Facility Clearance will be sufficient to meet the requirement at time of proposal submission provided that it can be validated by the Defense Security Service (DSS); however, please note that access to classified COMSEC information requires a FINAL US

Government Clearance at the appropriate level and therefore if contractor employee requires access to classified COMSEC the offeror will be required to possess a FINAL US Government Clearance at the appropriate level in order to perform after award, and throughout the life of the contract.

While it is acknowledged that the Offeror may form contractual relationships with additional legal entities (i.e. Prime/Subcontracts, Partnerships, etc.) in order to perform work under this contract, including the specific work which necessitates the SECRET Facility and

Security Clearances, the Offeror (i.e. the legal entity that is submitting the proposal and would be identified as the awardee of the contract) must possess a SECRET Facility Clearance itself and cannot rely solely on the clearance of a Subcontractor or other legal entity. Possession of a SECRET Facility Clearance will be determined by CAGE code. For a proposal submitted by a Joint Venture, a Secret

Facility Clearance must be held by either the joint venture itself or an individual partners name and CAGE code to meet the solicitation requirements.

TO:

L.5.1.8 SECRET Facility Clearance: Offerors must possess a SECRET Facility Clearance by the RFP closing date, at the time of award, and throughout the life of the contract. All Subcontractors who will be performing contract requirements which necessitate facility clearance must also have a SECRET Facility Clearance by RFP closing date, at the time of award, and throughout the life of the contract.

In order for an Offeror/Subcontractor to request and sponsor an individual employee's SECRET Security Clearance to perform the functions identified in the PWS, the Offeror/ Subcontractor must possess a SECRET Facility Clearance by the RFP closing date. Possession of an

INTERIM SECRET Facility Clearance will be sufficient to meet the requirement at time of proposal submission provided that it can be validated by the Defense Security Service (DSS); however, please note that access to classified COMSEC information requires a FINAL US

Government Clearance at the appropriate level and therefore if contractor employee requires access to classified COMSEC the offeror will be required to possess a FINAL US Government Clearance at the appropriate level in order to perform after award, and throughout the life of the contract.

While it is acknowledged that the Offeror may form contractual relationships with additional legal entities (i.e. Prime/Subcontracts, Partnerships, etc.) in order to perform work under this contract, including the specific work which necessitates the SECRET Facility and

Security Clearances, the Offeror (i.e. the legal entity that is submitting the proposal and would be identified as the awardee of the contract) must possess a SECRET Facility Clearance itself and cannot rely solely on the clearance of a Subcontractor or other legal entity. Possession of a SECRET Facility Clearance will be determined by CAGE code. For a proposal submitted by a Joint Venture, a Secret

Facility Clearance must be held by either the joint venture itself or an individual partners name and CAGE code to meet the solicitation requirements.

4. Update Section L, Paragraph L.5.2.1.1(b)(1)(ii)

FROM:

2 23

W519TC-23-R-0022

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Offeror's SMP must include a description of its capability to successfully implement the provided Surge Option workload in accordance with PWS 1.4.3.1 and Attachment 0029, TD-02.

TO:

The Offeror's SMP must include a description of its capability to successfully implement the provided Surge Option workload in accordance with PWS 1.4.3.1 and Attachment 0037, TD-12.

5. Update Section A, Paragraph A.4

FROM:

The Contracting Officer may authorize proceeding into FOC as various elements of transition are complete prior to the end of the 30 day

Transition period.

TO:

The Contracting Officer may authorize proceeding into FOC as various elements of transition are complete prior to the end of the 60 day

Transition period.

6. Update Attachment 0001 - PWS dated 17 Jul 23

7. Update Attachment 0002 - Staffing and Labor Mix dated 31 Aug 22

8. Update Attachment 0005 - Cost Price Matrix dated 18 Jul 23

9. Update Attachment 0007 - Department of Labor Wage Determinations-SCA dated 27 Dec 22

10. Update Attachment 0011 - Contract References Spreadsheet dated 18 Jul 23

11. Update Attachment 0015 - Subcontractor Cost Information Submission dated 18 Jul 23

12. Update Attachment 0029 - TD-02 Workload Data and Density List FCKY dated 14 Jun 23

13. Update Attachment 0037 - TD-12 Mobilization Support Services FCKY dated 01 Aug 22

*** END OF NARRATIVE A0003 ***

THIS RFP WILL BE COMPETED AMONGST ONLY THOSE OFFERORS THAT HOLD AN ENHANCED ARMY GLOBAL LOGISTICS ENTERPRISE (EAGLE) BASIC ORDERING

AGREEMENT (BOA) BY THE CLOSING DATE OF THIS RFP. THIS ACQUISITION IS A SMALL BUSINESS SET-ASIDE AND ONLY BOA HOLDERS WHO CAN CERTIFY

PARTICIPATION IN THE SMALL BUSINESS ADMINISTRATION (SBA) UNDER NORTH AMERICAN INDUSTRY CLASSIFICATION SYSTEM (NAICS) CODE 561210 BY THE

CLOSING DATE OF THIS RFP WILL BE CONSIDERED FOR AWARD.

A.1 The U.S. Army Fort Campbell, KY (FCKY) has a requirement for logistics support services, including maintenance, supply, and transportation support.

A.2 This is an official RFP and supporting documentation for the FCKY requirement.

A.3 This RFP is a 100% small business set-aside and will be competed among those Offerors that hold an EAGLE Program BOA who can certify small business status under NAICS Code 561210 by the closing date of this RFP.

This RFP will result in a Cost Plus Fixed Fee (Firm Fixed Price Transition In) task order with 1, 12 month base period, to include a 60-day transition in period, 4, 1-year options, and 1, 6-month option period in accordance with (IAW) Federal Aquisition Regulation (FAR)

52.217-8 for a total of 5-years and 6-months if all options are exercised. The evaluated option periods, which will be awarded at the

Government's sole discretion, will be based on need and performance of the contractor.

A.4 The period of performance for each Contract Line Item Number (CLIN) from Notice to Proceed (NTP) through 1830 Days after NTP is identified below:

CLIN SERVICE PERIOD OF PERFORMANCE:

Base Year (including 60 days Transition-In): CLINs 0001 - 0010, NTP - 365 days after NTP

Option Year 1: CLINs 1001 - 1010, 366 days after NTP - 730 days after NTP

Option Year 2: CLINs 2001 - 2010, 731 days after NTP - 1095 days after NTP

Option Year 3: CLINs 3001 - 3010, 1096 days after NTP - 1461 days after NTP

3 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Option Year 4: CLINs 4001 - 4010, 1462 days after NTP - 1826 days after NTP

Option Period IAW FAR 52.217-8: CLINs 5001-5010, 1827 days after NTP - 2007 days after NTP.

Transition and Fully Operational Capability (FOC) efforts are part of a single requirement and period of performance. All Transition efforts are still required to be completed within the first 60 days of performance; however, transition to FOC is part of a seamless process. The Contracting Officer may authorize proceeding into FOC as various elements of transition are complete prior to the end of the 60 day Transition period.

A.5 This Best Value source selection process will include an evaluation of the following three factors: (1) Technical, (2) Past

Performance, and (3) Cost/Price. A Task Order award under this EAGLE competition will be made to the Offeror determined to be responsible IAW FAR subpart 9.1 whose proposal conforms to the RFP requirements and is determined to be the lowest evaluated (fair and reasonable) priced proposal that is determined technically Acceptable with Substantial Confidence in Past Performance.

A.6 The Offeror's proposal shall be valid for 180 days from the closing date of the RFP.

A.7 The incumbent contractor is Amentum Services, Inc, (formerly known as URS Federal Services, Inc.) W52P1J-17-G-0091.

A.8 NOT APPLICABLE

A.9 Government Furnished Facilities and Equipment are identified in the Exhibits/Attachments in Section J of this RFP and identified in the Performance Work Statement (PWS).

A.10 Please note that this RFP contains a Section B, "Supplies or Services and Prices/Costs"; however, Offerors are required to complete and submit the Cost/Price Matrix identified as Attachment 0005.

A.11 The Government intends to conduct a Post Award Conference with the awardee following Task Order award.

A.12 This RFP should not be discussed with any Government employee except the Procuring Contracting Officer (PCO), Ms. Michelle Lund, or

Contract Specialist, MAJ Johnny Martinez, may be contacted respectively at michelle.m.lund3.civ@army.mil and johnny.r.martinez5@army.mil.

A.13 This RFP and any amendments to this RFP shall be issued electronically. Because of this, the Government is under no obligation to maintain an Offerors mailing list. Any EAGLE BOA holders interested in this requirement must periodically access Contract Opportunities located at https://.SAM.gov . Failure to provide proposals in accordance with the instructions/format specified in this RFP shall render the Offerors proposal non-compliant. The proposal will not be evaluated and will not be further considered for award.

A.14 The Government is not obligated to provide responses to any questions submitted by Offerors, but will consider them and incorporate changes into the RFP as deemed necessary.

A.15 The closing date and time for this RFP is identified on page 1 of this RFP, the Local Time is Central Time. All proposal documents are due at the time set forth in this RFP.

A.16 Proposals shall be submitted electronically to johnny.r.martinez5@army.mil and michelle.m.lund3.civ@army.mil. Due to file size restrictions, proposals may be submitted through Department of Defense (DOD) Secure Access File Exchange (SAFE), http://safe.apps.mil/

. Note that only 25 files can be submitted with one upload. Multiple drop-off codes may be requested from the Contract Specialist or

Contracting Officer, if necessary. Non-CAC users will have to request a drop-off request from the Contract Specialist or Contracting

Officer. Please visit the website for more details and instructions for its use. Cloud Services and third party drop boxes are not acceptable for proposal submission.

Emailed proposals shall state the following in the subject line: Proposal for solicitation number (W519TC-23-R-0022) - Add company name.

It is highly recommended that the Offeror request a Return Receipt or other form of acknowledgement to verify that the proposal submission was received prior to the closing of the RFP.

A.17 The DD254 Security Form is provided as Attachment 0012. The Offeror / Subcontractor(s) identified on Attachment 0005, Tab 2 shall have a SECRET Facility Clearance prior to this RFP closing date. In addition, the Offeror / Subcontractor(s) must have a Facilities

Clearance in order for personnel within the company to obtain a SECRET Clearance.

A.18 The Government will compare the Offeror's proposal to Section L in order to perform a compliance review. Failure to provide proposals in accordance with the instructions/format specified in this RFP shall render the Offerors proposal non-compliant. The proposal will not be further evaluated and will not be further considered for award. The Government reserves the right to waive the

Strict Compliance Review if it is in the Government's best interest.

A.19 Not Applicable.

4 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

A.20 The Army Sustainment Command (ASC) may employ the services of a support contractor to assist in the management and oversight of ASC contracts. The contracted support provided by a support contractor is technical in nature, and in no way supplants the Governments exclusive responsibility for the decision making regarding contract management and oversight. The contract with ASCs support contractor prohibits the unauthorized use or disclosure of any of the information and data associated with ASC contracts in support of management and oversight responsibilities.

In the event ASC determines it will use a support contractor for management and oversight assistance, awardees shall work with the

Contracting Officer and support contractor to establish appropriate agreements and proper protections (see FAR 9.505-4(b)) allowing permission for the support contractor to have necessary access to information and data to assist ASC in its management and oversight for any associated contracts.

A.21 Organizational conflict of interest (OCI) means a situation in which-

(1) A Government contract requires a contractor to exercise judgment to assist the Government in a matter (such as in drafting specifications or assessing another contractor's proposal or performance) and the contractor or its affiliates have financial or other interests at stake in the matter, so that a reasonable person might have concern that when performing work under the contract, the contractor may be improperly influenced by its own interests rather than the best interests of the Government; or

(2) A contractor could have an unfair competitive advantage in an acquisition as a result of having performed work on a Government contract, under circumstances such as those described in paragraph (1) of this definition that put the contractor in a position to influence the acquisition.

(3) If the Contractor identifies an OCI, the Contractor shall make a prompt and full disclosure in writing to the PCO. OCI that arise during performance of the contract, as well as newly discovered conflicts that existed before contract award, shall be disclosed.

A.22 Notice of Organizational Conflict of Interest (OCI): ASCs support contractor, and any affiliates, subsidiaries, or subcontractors and any affiliates, subsidiaries, or subcontractors have OCIs, and are precluded from offering a proposal as either a prime or a subcontractor, or from participating as a member of any team competing for this contract and/or any other resultant contracts stemming from this RFP. The Government reserves the right to reject any offer it considers to represent an OCI. Offerors are directed to FAR 9.5 for further information on OCIs for detailed OCI contract restrictions/requirements.

A.23 This is a Requirements Contract IAW FAR 52.216-21 for the services specified in the PWS and workload data, and effective for the period of performance identified in Paragraph A.4.

A.24 The Estimated Total Contract Value (ETCV) is TBD (at award). The ETCV amount is NOT a ceiling price, but rather an ESTIMATE of the total 5 and a half years of performance under this contract.

A.25 NOT APPLICABLE

A.26 If an Amendment is deemed necessary for this RFP, the Amendment notice will be posted to Contract Opportunities as stated in

Section A, Paragraph A.13. Please be advised that when an Amendment is posted to Contract Opportunities it will be listed on the bottom of the RFP notice.

A.27 All Clauses and Provisions identified within the EAGLE BOA are incorporated by reference to this RFP.

*** END OF NARRATIVE A0001 ***

5 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION J - LIST OF ATTACHMENTS

List of Number List of Number

Addenda Title Date of Pages Transmitted By Addenda Title Date of Pages Transmitted By________________ ____________________________________________________________ _______________ ____________ _______________________________ ____________________________________________________________ _______________ ____________ _______________

Attachment 0001 PWS 17-JUL-2023

Attachment 0002 STAFFING AND LABOR MIX 31-AUG-2022

Attachment 0005 COST PRICE MATRIX 18-JUL-2023

Attachment 0007 DEPARTMENT OF LABOR WAGE DETERMINATIONS-SCA 27-DEC-2022

Attachment 0011 CONTRACT REFERENCES SPREADSHEET 18-JUL-2023

Attachment 0015 SUBCONTRACTOR COST INFORMATION SUBMISSION 18-JUL-2023

Attachment 0029 TD-02 WORKLOAD DATA AND DENSITY LIST FCKY 14-JUN-2023

Attachment 0037 TD-12 MOBILIZATION SUPPORT SERVICES_FCKY 01-AUG-2022

Attachment 0038 FT CAMPBELL Q&A RESPONSES 18-JUL-2023

6 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 GENERAL INSTRUCTIONS:

L.1.1 These instructions are a guide for preparing a proposal. These instructions describe the type and extent of information required and emphasizes the significant areas to be addressed in the proposal. Review the Performance Work Statement (PWS) contained in this

Request for Proposal (RFP) for further insight into the areas that must be addressed within the proposal. Include detailed information sufficient to enable the Government evaluators to conduct a meaningful review and make a determination relative to the Offeror's understanding of the requirements in each of the evaluated areas. It is the Government's intent to award a single combination Cost-Plus

Fixed Fee / Firm Fixed Price (Transition-In CLIN and PMO CLINs only) Requirements contract with some non-fee bearing cost elements

(e.g., Other Direct Costs) which are ancillary to the services provided.

L.1.2 In accordance with (IAW) FAR 52.215-1, Instructions to Offerors - Competitive Acquisition (Jan 2017), the Government intends to award a contract without discussions. Offerors are cautioned to examine this RFP in its entirety and to ensure that proposals contain all necessary information, provide all required documentation, and are complete in all respects. The Government is not obligated to make another request for the required information nor does the Government assume the duty to search for data to cure problems it finds in proposals. The Government reserves the right to conduct discussions in the evaluation process and to permit Offerors to revise proposals, if deemed necessary. During the evaluation process, the Government may request clarifications as needed. Clarifications do not constitute discussions and an Offeror is not allowed to change its proposal in response to a request for clarification. In accordance with FAR 15.306(c)(2), if the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals. Any Offeror eliminated from further consideration will be notified in writing.

L.1.3 Offerors shall submit proposals that will remain valid for not less than 180 days from the required submission date.

L.1.4 Proposals, modifications, revisions, or withdrawals of proposals received after the date established in this RFP for receipt of proposals will be handled IAW FAR Clause 52.215-1.

L.1.5 An Offeror is defined as the prime BOA Holder submitting a proposal under this RFP.

L.1.6 For the purposes of this Task Order RFP, a Joint Venture (JV) is defined as a team of two or more firms that have entered into a legally binding JV agreement. A firm proposing as a JV will be referred to as the Offeror.

L.1.7 Updates related to this Task Order RFP, to include the RFP, amendments, notices, and other information, will be posted to Contract

Opportunities as stated in Section A, Paragraph A.13. Offerors are advised to continuously monitor Contract Opportunities website for new information. Offerors are deemed to have knowledge of all information that is posted to Contract Opportunities.

L.2 PROPOSAL PREPARATION:

L.2.1 The proposal must be prepared in a clear and legible manner. In addition, the Offeror shall write the proposal in English and the proposal must be specific and complete as described in these instructions. Offerors shall not specifically prepare samples or descriptive literature for submission with the proposal. Adherence to the prescribed format is required. Failure to provide proposals ______________________________ in compliance with the instructions specified as COMPLIANCE REQUIREMENTS in Section L of this RFP and in compliance with ALL_____________________________________________________________________________________________________________________________ instructions in Section M.3 of this RFP shall render the Offeror's proposal non-compliant. The proposal will not be evaluated and will________________________________________________________________________________________________________________________________________ not be further considered for award.____________________________________

L.2.2 All information pertaining to a particular volume shall be confined to that volume. For example, no Cost/Price information shall be included in any volume other than the Cost/Price Proposal volume. The Government is not required to and will not search other volumes for a missing file or missing information.

L.2.3 The proposal must not contain any classified material.

L.2.4 Offeror must be registered in the System for Award Management (SAM) and have a Marketing Partner Identification Number (MPIN) and

Commercial and Government Entity (CAGE) Code.

L.2.5 Digital Microsoft (MS) Word files and MS Excel files must be compatible with Microsoft Office 2013.

L.2.5.1 Please Note: The Offeror shall not lock or password protect any file (e.g. *.doc/.docx, *.pps/.pptx, *.xls/.xlsx, *.txt, *.msg).

L.2.6 Adobe PDF (Portable Document Format) Files. Scanned PDF documents must be legible and must be viewable in Adobe Acrobat.

L.2.6.1 Text Searchable Adobe PDFs: File formats that are identified as Text Searchable Adobe PDF must be formatted to contain searchable text. All elements of the file must be able to be searched for text. The Government will not accept scanned or image-only

7 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

PDF files in lieu of this requirement and will not invoke the text recognition feature within Adobe Acrobat.

L.2.7 Compressed files (e.g. *.zip) and Executable files (e.g. *bat, *.exe,*.jar, *.vb, *.wsf) will NOT be accepted. Refer to Attachment

0010 - Blocked File Extensions for a complete list of non-acceptable file types.

L.2.8 For the purposes of proposal preparation and evaluation only, the Offeror shall use 14 February 2024 as the Notice to Proceed

(NTP) date. Proposal information shall reflect that NTP date.

L.3 PROPOSAL SUBMITTAL INSTRUCTIONS:

L.3.1 Proposals shall be submitted electronically to johnny.r.martinez5.mil@army.mil and michelle.m.lund3.civ@army.mil. Due to file size restrictions, proposals may be submitted through Department of Defense (DOD) Secure Access File Exchange (SAFE), https://safe.apps.mil/

. Note that only 25 files can be submitted with one upload. Multiple drop-off codes may be requested, if necessary. Non-CAC users will have to request a drop-off request from the Contract Specialist or Contracting Officer. Please visit the website for more details and instructions for its use. Cloud Services and third party drop boxes are not acceptable for proposal submission.Emailed proposals shall state the following in the subject line: Proposal for solicitation number (W519TC-23-R-0022) Add company name.It is highly recommended that the Offeror request a Return Receipt or other form of acknowledgement to verify that the proposal submission was received prior to the closing of the RFP.

L.3.2 The proposal submittal method used for this solicitation is the electronic response via document upload method.

L.3.3 Offerors should enter a description for every file uploaded. For files over 10 megabytes (MB) the "Large Upload (JAVA)" button must be utilized. The combined file size limit for upload using "Large Upload (JAVA)" is 100MB. If needed, the Offeror can break single files over 100MB into smaller files or use the upload utility multiple times if files exceed the 100MB size limit.

L.3.4 Digital file names must use the required naming convention for each specific proposal document identified below. Filenames must be 40 characters or less and must not contain single quotes, spaces and pound or percent signs. If an Offeror's file name is too long

(more than 40 characters), it is permitted to abbreviate the Name of the Company field within the file name.

L.3.5 Proposal revisions are possible and permitted until the solicitation response deadline. Note: The Offeror must be logged in to the system to be able to submit / revise electronic responses.

L.3.6 Do not assume submission will be instantaneous. File size and number of files to be uploaded will be factors to consider.

Offeror/ Subcontractors should allow adequate time for submission completion because the entire proposal (i.e., Offerors submission and all Subcontractor(s) submissions) must be received by the due date and time for the proposal to be considered.

L.3.7 To avoid rejection of an offer, the Offeror must make every effort to ensure its electronic submission is virus-free. Proposals, or portions thereof, submitted with the presence of a virus or which are otherwise unreadable will be treated as unreadable pursuant to

FAR 15.207(c).

L.3.8 Submission Instructions for Subcontractor Cost proposal can be found in L.5.4.2.10.

L.4 PROPOSAL STRUCTURE:

L.4.1 The Offeror must submit a proposal IAW the guidelines below.

L.4.1.1 For all documents, each page shall include the complete Offeror's name, volume number, file name, date, and solicitation number in a header and/or footer.

L.4.1.2 Each Offeror shall submit ONLY one proposal and that proposal shall address all of the requirements of the RFP. To be considered for this requirement, the Offeror must submit a complete response to this RFP using the instructions provided in Section L.

COMPLIANCE REQUIREMENT: If the Offeror's proposal fails to meet the terms and conditions of the RFP or takes exception to any of the_____________________________________________________________________________________________________________________________________ terms and conditions of the RFP, will render the Offeror's proposal unacceptable and will not be further considered for award._____________________________________________________________________________________________________________________________

L.4.1.2 (a) Each Offeror shall submit the most current versions of Attachment 0002 - Staffing and Labor Mix, Attachment 0003 -

Performance Questionnaire, and Attachment 0005 - Cost Price Matrix required for this RFP. The Government will verify that the Offerors submission contains the most current RFP Attachments 0002, 0003 and 0005 that were posted to Contract Opportunities as stated in Section

A, Paragraph A.13.

L.4.1.2 (b) COMPLIANCE REQUIREMENT: Failure to provide the most current versions of the RFP Attachments 0002, 0003, or 0005 shall render _____________________________________________________________________________________________________________________________ the Offerors proposal non-compliant and will not be further considered for award.________________________________________________________________________________

L.4.1.3 A proposal is presumed to represent the Offerors best efforts to respond to the RFP. The Offeror must provide adequately detailed information that complies with the solicitation requirements, allows for meaningful review by the Government evaluators, and affirmatively demonstrates the merits of its proposal. The Offeror shall provide sufficient detail to substantiate the validity of all

8 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

stated assertions and must not merely repeat the RFP requirements, but rather must provide convincing documentary evidence of how contract requirements will be met. Data not submitted with the proposal, but submitted previously, or presumed to be known (i.e., previous projects performed for the United States Government (USG)) will not be considered. Clarity and completeness are essential. It is the Offerors obligation to submit an unambiguous proposal that clearly reflects the Offeror's intended technical approach and establishes cost credibility. If the use of new and innovative techniques is intended, the impact on cost must be explained. As another example, if a business policy decision to absorb a portion of the estimated cost was made, that approach must be stated within the proposal (including any associated calculations). NOTE: Offerors must propose to the requirements of this Step 3 Task Order RFP.

Possessing a BOA does not guarantee that an Offeror will be determined technically acceptable for the purposes of this solicitation.

Therefore, Offerors must meet the requirements described in this solicitation to be eligible for award.

L.5 INFORMATION TO BE SUBMITTED:

L.5.1 General Documents: The Offeror shall include the following:

L.5.1.1 One executed signed copy of the RFP coversheet titled "Solicitation, Offer and Award" (SF33).

L.5.1.1(a) Naming Convention: Offeror's_Name_Vol_1_SF33

L.5.1.1(b) File Format: Adobe PDF or MS Word

L.5.1.1(c) Page Limit: None

L.5.1.1(d) COMPLIANCE REQUIREMENT: Failure to provide the signed SF 33 will render the Offeror's proposal non-compliant. The proposal _____________________________________________________________________________________________________________________________ will not be evaluated and will not be further considered for award.___________________________________________________________________

L.5.1.2 EITHER all signed amendment coversheets titled "Amendment of Solicitation/ Modification of Contract" (SF30) or one executed signed copy of the RFP coversheet (SF 33) with block fourteen (14) completed.

L.5.1.2(a) Naming Convention: Offeror's_Name_Vol_1_SF30(Amends)

L.5.1.2(b) File Format: Adobe PDF or MS Word

L.5.1.2(c) Page Limit: None

L.5.1.3 Section I clauses that require Offeror completion.

L.5.1.3(a) Naming Convention: Offeror's_Name_Vol_1_Iclauses

L.5.1.3(b) File Format: Adobe PDF or MS Word

L.5.1.3(c) Page Limit: None

L.5.1.4 Section K clauses that require Offeror certification.

L.5.1.4(a) Naming Convention: Offeror's_Name_Vol_1_Kclauses

L.5.1.4(b) File Format: Adobe PDF or MS Word

L.5.1.4(c) Page Limit: None

L.5.1.5 Offeror Points of Contact (POC): The Government does not intend to conduct discussions prior to awarding this Task Order.

However, any exchanges to include clarifications between the Government and the Offeror will be conducted through e-mail. Therefore, the

Offeror is required to provide at least 2 company individuals whose responsibilities will include reading and responding to Evaluation

Notices (ENs) through e-mail. For example, the Offeror's Contract Manager, as an agent of the company might be the main agent responsible, but a second agent shall be available in case of the main agent's unavailability. The agents' names, company titles, telephone numbers, facsimile numbers, and e-mail addresses should be provided, and it is the Offeror's responsibility to keep the information updated throughout the competition; submission of updated POC information will not constitute a proposal revision. A Title

Page is allowable to provide for the restriction or disclosure and use of data as specified in FAR Clause 52.215-1.

L.5.1.5(a) Naming Convention: Offeror's_Name_Vol_1_POCs

L.5.1.5(b) File Format: Adobe PDF or MS Word

L.5.1.5(c) Page Limit: None

9 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.1.6 Business Systems Information:

L.5.1.6.1 The Contracting Officer will review the Offeror's accounting system status for determining contractor responsibility IAW FAR

16.301-3; a cost-reimbursement type contract may be used only when the contractor's accounting system is adequate for determining costs applicable to the contract. An adequate system is a system that can separately accumulate costs under a Government contract and has the ability to generate the specific cost information required under the anticipated contract. An SF 1408 has been attached to this RFP

(Attachment 0006) which contains the specific procedures that are considered part of an adequate system. Therefore, for an Offeror to receive an award under this RFP, the successful Offeror will be required to demonstrate that the design of its accounting system can accomplish the specific SF 1408 procedures; as a result, the Offeror is required to provide in its proposal: - Official documentation, from either a successful Defense Contract Audit Agency (DCAA) audit of the Offeror's accounting system; or- A letter from the Defense

Contract Management Agency (DCMA) documenting its approval/adequacy of the Offeror's accounting system; or- Rationale for why documentation cannot be presented at proposal submission and a proposed date for which required documentation will be available. Absent an adequate accounting system, an apparent awardee cannot be determined responsible under FAR 9.104-5 and will be ineligible for award.

Per FAR 9.104-5(b), an apparent awardee who does not furnish the certification or such information as may be requested by the

Contracting Officer shall be given an opportunity to remedy the deficiency. Therefore, if an Offeror is unable to provide the certification with its proposal as required, it will be given another opportunity to present the required certification prior to award in the event it is determined to be the apparent awardee.

L.5.1.6.1 (a) Naming Convention: Offeror's_Name_Vol_1_AcctSys

L.5.1.6.1 (b) File Format: Adobe PDF or MS Word

L.5.1.6.1 (c) Page Limit: None

L.5.1.6.2 The Offeror shall provide its current Government approval status of the following business systems: billing (internal controls), estimating, budget and financial control, purchasing and quality assurance. The Offeror shall provide official Government approval documentation for any systems that have Government approval. The approval status and approval documentation will not be evaluated and is for Government contract administration. If approval of any of these business systems is not available, provide a statement of such and a brief rationale as to why these systems have not been approved.

L.5.1.6.2 (a) Naming Convention: Offeror's_Name_Vol_1_BusSys

L.5.1.6.2 (b) File Format: Adobe PDF or MS Word

L.5.1.6.2 (c) Page Limit: None

L.5.1.7 Attachment 0005-Cost Price Matrix, Tab 2-Teaming Matrix: The Offeror shall provide the full company name, CAGE code, role of participant, functional area(s) to be performed, proposed labor/fee for each participant for the entire period of performance (excluding

ODC's and the option to extend), percent of participation, and cost proposal submittal method, indicate whether the participant requires a SECRET Facility Clearance. The Offeror shall populate every column using the instructed fill-ins on the Attachment 0005, Tab 2 for itself, and proposed Subcontractors.

L.5.1.7 (a) COMPLIANCE REQUIREMENT: The amount in the total of Column F (Total estimated dollar value, Cell F9) provided on Attachment ___________________________________________________________________________________________________________________________

0005, Tab 2 shall match the amount of 'Subtotal - Proposed Labor/Fee" found on Attachment 0005, Tab 1a, Cell I22'. Failure to make____________________________________________________________________________________________________________________________________ these two amounts match shall render the Offeror's proposal non-compliant. The proposal will not be evaluated and will not be further______________________________________________________________________________________________________________________________________ considered for award._____________________

L.5.1.7 (b) Naming Convention: Offeror's_Name_Vol_4_Att0005

L.5.1.7 (c) File Format: MS Excel

L.5.1.7 (d) Page Limit: None

L.5.1.7 (e) COMPLIANCE REQUIREMENT: If an Offeror is proposing subcontractors, failure of the Offeror to populate all blue highlighted ____________________________________________________________________________________________________________________________ cells for itself and each of its proposed Subcontractor(s) on the Cost Price Matrix (Attachment 0005, Tab 2-Teaming Matrix) will render________________________________________________________________________________________________________________________________________ the Offeror's proposal non-compliant. The proposal will not be evaluated and will not be further considered for award._______________________________________________________________________________________________________________________

L.5.1.7 (f) The compliance requirements of L.5.1.7(a) and (e) do not apply to an Offeror performing 100% of the requirement by itself with no subcontractors.

L.5.1.8 SECRET Facility Clearance: Offerors must possess a SECRET Facility Clearance by the RFP closing date, at the time of award, and throughout the life of the contract. All Subcontractors who will be performing contract requirements which necessitate facility clearance must also have a SECRET Facility Clearance by RFP closing date, at the time of award, and throughout the life of the contract.

In order for an Offeror/Subcontractor to request and sponsor an individual employee's SECRET Security Clearance to perform the functions identified in the PWS, the Offeror/ Subcontractor must possess a SECRET Facility Clearance by the RFP closing date. Possession of an

10 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

INTERIM SECRET Facility Clearance will be sufficient to meet the requirement at time of proposal submission provided that it can be validated by the Defense Security Service (DSS); however, please note that access to classified COMSEC information requires a FINAL US

Government Clearance at the appropriate level and therefore if contractor employee requires access to classified COMSEC the offeror will be required to possess a FINAL US Government Clearance at the appropriate level in order to perform after award, and throughout the life of the contract.

While it is acknowledged that the Offeror may form contractual relationships with additional legal entities (i.e. Prime/Subcontracts, Partnerships, etc.) in order to perform work under this contract, including the specific work which necessitates the SECRET Facility and

Security Clearances, the Offeror (i.e. the legal entity that is submitting the proposal and would be identified as the awardee of the contract) must possess a SECRET Facility Clearance itself and cannot rely solely on the clearance of a Subcontractor or other legal entity. Possession of a SECRET Facility Clearance will be determined by CAGE code. For a proposal submitted by a Joint Venture, a Secret

Facility Clearance must be held by either the joint venture itself or an individual partners name and CAGE code to meet the solicitation requirements.

L.5.1.8 (a) The Offeror shall complete Column I on Tab 2-Teaming Matrix of Attachment 0005-Cost Price Matrix for all listed entities

(i.e., Offeror and Subcontractors, Subsidiaries, or other affiliates) that require a SECRET Facility Clearance for their proposed performance of requirements IAW the PWS. The Contracting Officer will verify that all entities designated as YES possess a SECRET

Facility Clearance; the verification will be conducted through a CAGE code search performed on the Defense Security Services (DSS)

Industrial Security Facilities Database (ISFD).

L.5.1.9 NOT APPLICABLE.

L.5.1.10 Mission Essential Contractor Services (MECS)

L.5.1.10.1 The Offeror's MECS proposal shall adhere to the following:

L.5.1.10.1(a) Naming Convention: Offeror's_Name_Vol_1_MECS

L.5.1.10.1(b) File Format: Text Searchable Adobe PDF

L.5.1.10.1(c) Page Limit: 2 pages

L.5.1.10.1 (c)(1) Page limit excludes cover page, table of contents, and glossary of abbreviations and acronyms.

L.5.1.10.1 (c)(2) Pages larger than 8.5 inches x 11 inches will be counted as two pages.

L.5.1.10.1 (c)(3) The font size shall be no less than 10-point font for all documents, to include charts, tables, and diagrams.

L.5.1.10.2 Mission Essential Contractor Services (MECS): The Offeror shall provide its MECS Plan that details its approach as to how it will continue to perform the essential contractor services listed in Attachment 0013 - Mission Essential Contractor Services by specifically addressing each part of the DFARS 252.237-7024 (b)(2)(i through v).

L.5.1.11 NOT APPLICABLE.

L.5.2 Technical Management Factor:

L.5.2.1 The Offeror shall demonstrate mission capability by detailing its proposed technical approach to meet the requirements specified in the PWS and this RFP by providing its Staffing and Management Plan (SMP).

L.5.2.1.1 Staffing and Management Plan (SMP):

L.5.2.1.1(a) The Offeror's SMP proposal must adhere to the following:

L.5.2.1.1(a)(1) Naming Convention: Offeror's_Name_Vol_2_SMP

L.5.2.1.1(a)(2) File Format: Text Searchable Adobe PDF

L.5.2.1.1(a)(3) Page Limit: 15 Pages

L.5.2.1.1(a)(3)(i) Page limit excludes cover page, table of contents, and glossary of abbreviations and acronyms

L.5.2.1.1(a)(3)(ii) Pages larger than 8.5 inches x 11 inches will be counted as two pages

L.5.2.1.1(a)(3)(iii) The font size must be no less than 10-point font for all documents, to include charts, tables, and diagrams.

11 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.2.1.1(a)(4) COMPLIANCE REQUIREMENT: Failure to provide the Staffing and Management Plan and in compliance with L.5.2.1.1(a)(3) ___________________________________________________________________________________________________________________ through L.5.2.1.1(a)(3)(iii) will render the Offeror's proposal non-compliant. The proposal will not be evaluated and will not be___________________________________________________________________________________________________________________________________ further considered for award._____________________________

L.5.2.1.1(b) The Offeror's Staffing and Management Plan must detail the Offerors approach to deliver services required in the RFP and

PWS. The Offerors SMP must detail the overarching methodology used to determine the proposed skill sets / skill level; the SMP must also contain any rational used to support staffing decisions with any explanations needed to clarify staffing decisions (e.g., cross utilization of specific labor categories, dual hatted positions, etc.). As the Government will utilize any applicable Collective

Bargaining Agreement (CBA), the Service Contract Act (SCA) Directory of Occupations (5th Edition) and TD-02 Workload Data and Density

List for technical evaluation purposes, the Offeror shall utilize those sources whenever possible to determine which labor categories/position titles to propose as part of its proposed staffing.

For all positions identified as "Non-Exempt" on the Offerors Attachment 0002 Staffing/Labor Mix, the Offeror shall provide a labor category/title under the column "Position Title" that is specifically found within the SCA Directory of Occupations (5th Edition)). If additional explanation is necessary beyond the definitions provided in the SCA Directory to describe the proposed skillset or capabilities of that labor category based on the Offerors unique business practices or staffing approach, then the SMP narrative must include an adequate duty description for that position which will enable the Government to evaluate the skill set / skill level that is being proposed (this requirement is in addition to any supplemental description the offeror can include under the "Duty Title" column on its Attachment 0002- Staffing and Labor Mix).

For positions identified as "Exempt" on Attachment 0002 Staffing and Labor Mix, if the Offeror is providing a labor category/title under the column Position Title that is not specifically found within the SMP narrative must include an adequate duty description for that position which will enable the Government to evaluate the skill set / skill level that is being proposed (this requirement is in addition to any supplemental description the offeror can include under the "Duty Title" column on its Attachment 0002 Staffing and Labor

Mix).

The SMP MUST BE SUPPORTED BY THE OFFEROR'S ATTACHMENT 0002 STAFFING/LABOR MIX and, at a minimum, must address the following elements:

L.5.2.1.1(b)(1) Staffing and organization of the required effort by providing its approach to creating its management structure from general staff oversight by first line supervisors through its company headquarters management. This approach must detail the management and supervision structure related to executing this effort.

L.5.2.1.1(b)(1)(i) The on-site FFP PMO positions are determined to be material to the effort and must remain staffed throughout the duration of the contract. The required labor categories are identified as firm fixed price. Offeror must propose PMO staffing, if required by the Offerors business processes to fully support the effort solicited within this RFP. Additional positions proposed within the firm fixed-price portion of the effort must be identified as firm fixed-price in Attachment 0002, Staffing and Labor Mix.

L.5.2.1.1(b)(1)(ii) The Offeror's SMP must include a description of its capability to successfully implement the provided Surge Option workload in accordance with PWS 1.4.3.1 and Attachment 0037, TD-12.