W519TC25R0021-0002 FINAL.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

Firm Fixed Price

0002 2025SEP12

W519TC

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

EILEEN M. GERARD

EMAIL: EILEEN.M.GERARD.CIV@ARMY.MIL

W519TC-25-R-0021

2025AUG13

X

X

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 24

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: EILEEN M. GERARD

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

Type of Contract 1: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of Amendment 0002 to the Request for Proposal (RFP) # W519TC-25-R-0021, Joint Personal Property Shipping Office at Fort

Belvoir, VA (JPPSO-MA); Joint Base Lewis-McChord, WA (JPPSO-NW); and Fort Hood, TX (JPPSO-Hood), is to incorporate the following:

1. Update Section M, Paragraph M.1.1.1

FROM:

M.1.1.1 A review of the Offeror's accounting system IAW FAR 16.301-3. Failure to provide the required documentation will impact the

Contracting Officer's responsibility determination. Absent an adequate accounting system, an Offeror cannot be determined responsible under FAR 9.104-5 and will be ineligible for award.

To:

M.1.1.1 RESERVED

2. Update Section M, Paragraph M.5.1.2(a)(2)

FROM:

M.5.1.2(a)(2) The Offeror adequately details a plan to successfully implement the Surge Requirement Capability by providing a realistic and feasible approach to onboarding the necessary workforce and achieving FOC within 21 days of receiving the NTP as required by PWS paragraph 1.4.3.1. The Offerors approach identifies the immediate steps that will be taken in response to the NTP from the PCO and provides a feasible and realistic plan for increasing the workforce, both addressing intended hiring practices and giving appropriate consideration to the temporary nature of the surge requirement and its potential impacts on recruitment and retention.

TO:

M.5.1.2(a)(2) RESERVED

3. Update all references in the RFP indicated as 'Attachment 0024 TD-02 Workload Data and Density List' to 'Attachment 0017 - TD-02

Workload Data and Density List."

4. Update Section J Attachment as follows:

a. Revised Attachment 0001 Performance Work Statement (PWS), dated 10SEP2025

5. Incorporate a revised Attachment 0029 - Government Responses to Industry, dated 11SEP2025 which provides responses to industry questions from the JPPSO Request for Proposal (RFP) questions 001 - 064.

6. Per Section A.14 of the RFP, 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.

7. All other terms and conditions remain in effect.

*** END OF NARRATIVE A0003 ***

2 24

W519TC-25-R-0021

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 PERFORMANCE WORK STATEMENT (PWS) 10-SEP-2025

Attachment 0029 GOVERNMENT RESPONSES TO INDUSTRY 11-SEP-2025

3 24

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 Firm Fixed Price

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(Nov 2021), 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.1.8 Notice to Offerors: Use of Artificial Intelligence (AI) tools in Proposal Evaluations.

L.1.8.1 Use of AI tools in Support of Evaluations: The Government may employ AI as a tool to assist in the analysis and review of

Offeror proposals. AI tools may be used to support tasks such as summarizing proposal content, identifying compliance with request for task order proposal/solicitation requirements, and highlighting areas of potential strength, weakness, or risk.

L.1.8.2 Maintaining Inherently Governmental Functions: Notwithstanding the use of AI tools to support the evaluation process, all final evaluation judgements, including the assignment or assessment of adjectival ratings, best value determinations, and source selection decisions, will be made exclusively by duly appointed Government personnel. The Government retains sole responsibility for all inherently governmental functions and will not delegate decision making authority to any AI tool.

L.1.8.3 Offeror Confidentiality and Data Protection: The AI tools utilized by the Government will be employed in a manner consistent with applicable regulations that govern the protection of proprietary and source selection information. The AI tool will be an output-only system. Any generated report data is not saved. No proposal data will be transmitted to or processed by external, non-Government systems without appropriate safeguards and authorizations in place.

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 "STRICT 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 Price information shall be included in any volume other than the Price Proposal volume. The Government is not required to and will not search other volumes for a missing file or missing information.

4 24

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 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 01 April 2026 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 eileen.m.gerard.civ@army.mil and larry.v.kemp.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-25-R-0021) 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 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., Offeror's 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.

5 24

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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 - 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) STRICT COMPLIANCE REQUIREMENT: FAILURE TO PROVIDE THE MOST CURRENT VERSIONS OF THE RFP ATTACHMENTS 0002, 0003, OR 0005 SHALL

RENDER THE OFFEROR'S 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 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 three-step 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) STRICT 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

6 24

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

L.5.1.6 Business Systems Information:

L.5.1.6.1 RESERVED

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-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. 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) STRICT 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) STRICT 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 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 strict 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 RESERVED

L.5.1.9 RESERVED

L.5.1.10 RESERVED

L.5.1.11 RESERVED

7 24

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.

L.5.2.1.1(a)(4) STRICT 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)(II) 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 Offeror's approach to deliver services required in the RFP and

PWS. The Offeror's SMP must detail the overarching methodology used to determine the proposed skill sets / skill level; the SMP must also contain any rationale 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.), to include a detailed narrative of innovations and efficiencies.

Rationale for innovations and efficiencies must be clearly identified, by placing under a separate header, in the SMP and confirmed within the Attachment 0017 - TD-02 Workload Data and Density List. The Government will NOT accept methodologies previously utilized under a different EAGLE Task Order or any other similar service contract, Government or otherwise, as supporting rationale for this requirement. The methodology shall be independent to this RFP only. As the Government will utilize the Service Contract Act (SCA)

Directory of Occupations (5th Edition) and Attachment 0017 - 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 Offeror's 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 Offeror's 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 an Offeror designates a position as "Exempt" on

Attachment 0002 Staffing and Labor Mix and the position title provided does not match an existing SCA labor category, the Offeror must include a detailed description of the duties for that position in the SMP narrative. This will allow the Government to evaluate the proposed skill set / skill level. (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 Offeror's 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)(2) The Offeror must provide an Organizational Diagram to depict a comprehensive organizational overview that identifies the following:

8 24

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.2.1.1(b)(2)(i) Identification of the tasks to be performed by the Offeror and all proposed subcontractor(s) (if applicable) as identified on the Offeror's Teaming Matrix (Attachment 0005, Tab 2-Teaming Matrix).

L.5.2.1.1(b)(2)(ii) Identification of the command-and-control relationship among the Offeror, all proposed subcontractor(s) as identified on the Offeror's Price Matrix (Attachment 0005, Tab 2-Teaming Matrix). The command-and-control relationship must include identification of leadership positions (i.e., team leads, foremen, supervisors, deputies, managers, etc.) responsible for performing successful oversight of each of the primary task areas identified in Section C-5 of the PWS.

Note: FTE Counts are not required on the Organizational Diagram. Proposed FTEs counts will only be evaluated on the Attachment 0002, Staffing and Labor Mix and will not be evaluated as part of the Organizational Diagram.

L.5.2.1.1(b)(2)(iii) The Offeror must clearly identify its onsite quality control approach with direct coordination to the responsible corporate quality office.

L.5.2.1.1(c) Staffing and Labor Mix (Attachment 0002 - Staffing and Labor Mix): The Offeror must provide its proposed labor categories

(skill sets / skill level, number of employees) in relation to the PWS requirements and Attachment 0017 TD-02 Workload Data and Density

List for both the base period and option periods (fully operational capable 12-month periods (365-day periods)).The Offeror's proposal must present a staffing approach which demonstrates a thorough understanding of the effort and provides the expected skill sets / skill level of each position, to include level of responsibility to successfully perform the specific workload requirements identified in

Attachment 0017 TD-02 Workload Data and Density List and meet all the PWS requirements.

OFFERORS SHALL NOT INCLUDE STAFFING FROM MOBILIZATION SUPPORT SERVICES.

NOTE: For Technical evaluation purposes only, the Government will utilize the Service Contract Act (SCA) Directory of Occupations (5th

Edition) labor category definitions to determine if the proposed labor category has the skill set / skill level necessary to perform the required task(s) as identified in L.5.2.1.1(b).

NOTE: It is further noted that the inclusion of only some of the PWS paragraphs in Attachment 0017 (TD-02 Workload Data and Density

List) is for Technical evaluation purposes only. During contract execution, compliance with all PWS requirements is expected and required.

L.5.2.1.1(c)(1) Offeror's proposal shall adhere to the following:

L.5.2.1.1(c)(2) Naming Convention: Offeror's_Name_Vol_2_Att0002

L.5.2.1.1(c)(3) File Format: MS Excel

L.5.2.1.1(c)(3)(i) The Offeror shall not add or remove any tabs (other than the example tab) to the Attachment 0002 Staffing and Labor

Mix.

L.5.2.1.1(c)(4) STRICT COMPLIANCE REQUIREMENT: FAILURE TO PROVIDE THE STAFFING/ LABOR MIX ATTACHMENT 0002 IN THE GOVERNMENT PROVIDED

FORMAT, IN COMPLIANCE WITH L.5.2.1.1(C)(3) AND L.5.2.1.1(C)(3)(I), AND TO PROVIDE THE FOLLOWING REQUIRED INFORMATION, SHALL RENDER THE

OFFEROR'S PROPOSAL NON-COMPLIANT, AND THE PROPOSAL WILL NOT BE EVALUATED AND WILL NOT BE FURTHER CONSIDERED FOR AWARD: PROPOSED HOURS

PER FTE FOR BOTH THE BASE PERIOD AND OPTION PERIODS 1-4; FLC1/FLC2; IDENTIFICATION OF SCA/EXEMPT; SCA CODE; OFFEROR POSITION TITLE; AND

IDENTIFICATION OF FUNCTIONAL AREA.

L.5.2.1.1(c)(5) Definitions relating to Staffing/Labor Mix:

L.5.2.1.1(c)(5)(i) Full Time Equivalents (FTEs): Compensable hours are determined by the Offeror and are the work hours available to perform a function in one year less holiday and vacation hours. An employee who works all available compensable hours is one FTE. If an employee works less than the total compensable hours for one year, that is considered a fractional FTE. Fractional FTEs are determined by dividing the hours scheduled for that employee by the total available compensable hours.

L.5.2.1.1(c)(5)(ii) Functional Labor Category 1 (FLC1): Contract or Task Order level positions that are specifically identified to directly accomplish the tasks/functions of the workload provided in Attachment 0017 TD-02, Workload Data and Density List (e.g., mechanic / shop supply clerk in support of the maintenance effort). Note: Leads may be proposed as solely FLC1, if applicable.

L.5.2.1.1(c)(5)(iii) Functional Labor Category 2 (FLC2): Contract or Task Order level positions required for the completion of RFP requirements, but do not directly perform the tasks / functions of the workload provided in Attachment 0017 TD-02, Workload Data and

Density List. FLC2 positions may be required by the RFP, regulation, or the Offeror's business practices, but are not directly supporting the workload (e.g., project manager, supervisory functions, and administrative assistant). Additionally, all managers must be proposed as solely FLC2; supervisors may be split as FLC1 and FLC2, with the FLC2 portion proposed commensurate with the level of supervisory duties assigned.

9 24

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

NOTE: FLC2 positions also include the Program Management Office (PMO) positions.

L.5.2.1.1(c)(6) The purpose of Staffing/Labor Mix - Attachment 0002 is to provide the Government with a complete picture of each

Offeror's staffing and total proposed labor hours for each CLIN and PWS paragraph requirement for this effort. For proposal purposes staffing must be constant for all periods of performance. The Government intends to use the MS Excel program to analyze the data provided.

The following instructions pertain to the Staffing and Labor Mix - Attachment 0002:

L.5.2.1.1(c)(6)(i) The Offeror must identify all of its proposed staffing required to support all PWS requirements, specifically those that are both identified at Section 5 of the PWS and Attachment 0017 - TD-02 Workload Data and Density List in terms of FTEs and FLC1 or

FLC2 on the Staffing/Labor Mix - Attachment 0002. See example tab in Attachment 0002.

L.5.2.1.1(c)(6)(ii) The Offeror must insert FLC1 or FLC2 for all proposed labor categories. Please note: The hours associated with FLC2 positions (including managers proposed as FLC1 and supervisors proposed solely as FLC1), in whole or part, will not count toward the total FLC1 hours specified in L.5.2.1.1(c)(6)(v), and positions incorrectly identified as FLC1 will not count toward the total FLC1 hours specified in L.5.2.1.1(c)(6)(v).

L.5.2.1.1(c)(6)(iii) The Offeror must clearly identify all FTEs that are cross utilized FTEs, or, in other words, when a portion of an

FTE (i.e., supervisor) is applicable to an FLC1 labor category and a portion of the same FTE is also applicable to an FLC2 labor category. These positions must be listed on the Attachment 0002 - Staffing and Labor Mix in all applicable locations (e.g., part time worker (.20 FLC1) and part time supervisor (.80 FLC2)) with the appropriate percentage of hours applicable to each labor category expressed as a decimal (not to exceed two decimal places to the right of the whole number). Additionally, supervisors must, by definition, have a portion of their proposed time proposed as FLC2.

L.5.2.1.1(c)(6)(iv) The Offeror must provide its proposed annual labor hours by employee type in the Hours Per Year column (in both the

Base Period and Option Periods 1-4) for Exempt or SCA positions.

L.5.2.1.1(c)(6)(v) Proposed FLC1 FTEs, when multiplied by the associated annual hours per year by employee type proposed for the option periods, shall be equal to or greater than the estimated hours of each functional area as provided in Attachment 0017 - TD-02 Workload

Data and Density List.The proposed FLC2 FTEs (i.e., FLC2 portion of proposed supervisors, if applicable) are not to be included in the total Proposed FLC1 Hours by Functional Area.If the specified hours are not met due to an Offeror choosing to utilize innovative and efficient methodologies (e.g., cross utilization of specific labor categories, dual hatted positions, etc.) the methodology must be clearly identified within the SMP to include but not limited to how the lack of service hours will be accounted for to ensure the service(s) is fully mission capable. Simply stating that cross utilization of specific labor categories or dual hatted positions will be utilized is not considered an acceptable method.

L.5.2.1.1(c)(6)(vi) The Offeror must insert the proposed labor category/position title, and it must match the labor category description found in either the CBA, SCA, or the SMP (if the position is an Exempt position, such as a manager or supervisor).

The Offeror must insert either "SCA" or "Exempt" in the column titled "SCA/CBA/Exempt." If "SCA" is identified, the Offeror must also provide the corresponding SCA labor code in the Column indicated as "SCA Code." An SCA labor code shall only be provided if the position has been identified as a SCA position. In the event the labor code and the "Position Title" do not match, the SCA labor code will take precedence over the "Position Title" provided, and the description applicable to the given SCA Labor Code will be used to determine and evaluate the skill set / skill level being proposed. Additionally, the Offeror may provide the "Duty Title" to better identify the functional nature of the position.

L.5.2.1.1(c)(6)(vii) RESERVED

L.5.2.1.1(c)(6)(viii) RESERVED

L.5.2.1.1(c)(6)(ix) The Offeror must insert the number of FTEs (or less than full time equivalents expressed as FTEs) within the applicable FTE Count column. The Offeror's staffing must be rounded to the nearest hundredth decimal (i.e., two decimal places to the right of the whole number). Formatting the cells to display only two decimal places is not considered rounding; the values entered in each cell should only contain two decimal places. FTEs entered by the Offeror with greater than two decimal places will be rounded by the Government to the nearest hundredth decimal (two decimal places to the right of the whole number) using the Microsoft Excel formula

"=ROUND (number, num_digits)" IAW generally accepted rounding methods, i.e. numbers 5 through 9 are rounded up to the next whole number;

numbers 1 through 4 are rounded down to the next whole number.

L.5.2.1.1(c)(6)(x) The Offeror must complete the section of the Attachment 0002 - Staffing/Labor Mix marked "Option Period Total

Proposed FLC1 Hours by Functional Area" by correctly calculating its total proposed FLC1 hours for Transportation. Calculations must correctly multiply total proposed FLC1 FTEs by the Offeror provided Hours per Year applicable to the specific employee type. The calculated total proposed FLC1 hours must: either be equal to or greater than the estimated hours as provided in Attachment 0017 - TD-02

Workload Data and Density List, or; a narrative of the specific innovation or efficiency used to reduce the estimated hours must be provided. If the specified hours are not met due to an Offeror choosing to utilize innovative and efficient methodologies (e.g., cross

10 24

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

utilization of specific labor categories, dual hatted positions, etc.) the methodology must be clearly identified within the SMP to include but not limited to how the lack of service hours will be accounted for to ensure the service(s) is fully mission capable. Simply stating that cross utilization of specific labor categories or dual hatted positions will be utilized is not considered an acceptable method.

L.5.3 Past Performance Factor:

L.5.3.1 The Government will consider the recent past performance references that were provided with the Offeror's Task Order proposal in response to this RFP as well as references obtained from sources other than those identified by the Offeror.

L.5.3.1.1 Definitions:

L.5.3.1.1(a) Offeror, as used in this factor, is a BOA Holder Prime Contractor submitting a proposal for this Task Order RFP.

L.5.3.1.1(b) Joint Venture (JV) Partner, as used in this factor, is one or more entities comprising the JV BOA Holder Offeror.

L.5.3.1.1(c) Subcontractor(s), as used in the Past Performance factor, means those who are expected to perform 20% or more of the

Offeror's total estimated dollar value as found in column F of the Offeror's Price Matrix (Attachment 0005, Tab 2-Teaming Matrix). The

Government will verify the tasks each proposed subcontractor is expected to perform via the Offeror's Price Matrix Attachment 0005, Tab

2-Teaming Matrix, Column J.

L.5.3.1.1(d) Predecessor, as used in this factor, means an entity that is replaced by a successor and includes any predecessors of the predecessor.

L.5.3.1.1(e) Successor, as used in this factor, means an entity that has replaced a predecessor by acquiring the assets and carrying out the affairs of the predecessor under a new name (often through acquisition or merger). The term "successor" does not include new offices/divisions of the same company that only changes its name. The extent of the responsibility of the successor for the liabilities of the predecessor may vary, depending on State Law and specific circumstances.

L.5.3.1.2 The Offeror shall provide a Letter of Consent for each Subcontractor and JV Partner, using the Letter of Consent template provided in Attachment 0004 Letter of Consent. This letter allows the release of the Subcontractors' and JV Partners' present and past performance information to the Offeror. Failure to include written consent from each Subcontractor and JV Partner will result in the

Government's inability to contact the Offeror to communicate the findings from its Subcontractor(s) and JV Partner(s) references. A

Letter of Consent from another Task Order is not relevant to this Task Order RFP. A new Letter of Consent is required and shall adhere to the following:

L.5.3.1.2(a) Naming Convention: Offeror's_Name_Vol_3_Att0004

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

L.5.3.1.2(c) Page Limit: None

L.5.3.1.2(d) STRICT COMPLIANCE REQUIREMENT: FAILURE TO PROVIDE A COMPLETED LETTER OF CONSENT FOR EACH SUBCONTRACTOR AND JV PARTNER WILL

RENDER THE OFFEROR'S PROPOSAL NON-COMPLIANT. THE PROPOSAL WILL NOT BE EVALUATED AND WILL NOT BE FURTHER CONSIDERED FOR AWARD.

L.5.3.1.3 The Offeror is afforded the opportunity to provide past performance contract references for itself, Joint Venture Partner(s) and for each proposed subcontractor but is not required to do so.

L.5.3.1.4 If the Offeror chooses to submit any contract references for itself, JV Partner(s) and/or proposed subcontractors, the Offeror must do so by submitting an individual Attachment 0011 Contract References Spreadsheet for each entity. Each individual Attachment 0011 must be completed in the following format with the following information:

L.5.3.1.4(a) Attachment 0011 Format:

L.5.3.1.4(a)(1) Naming Convention: Offeror's_Name_Vol_3_Att0011; or, Naming Convention for Subcontractors:

Offeror's_Name_Sub's_Name_Vol_3_Att0011

L.5.3.1.4(a)(2) File Format: MS Excel

L.5.3.1.4(a)(3) Page Limit: None

L.5.3.1.4(b) Attachment 0011 Information:

L.5.3.1.4(b)(1) Line 1: The BOA Holder Offeror Name.

11 24

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.3.1.4(b)(2) Line 2: The BOA Holder Offeror's CAGE Code, as identified in SAM. The CAGE Code consists of five alphanumeric digits and does not begin with the letter O.

L.5.3.1.4(b)(3) Line 3: If applicable, the Subcontractor Name.

L.5.3.1.4(b)(4) Line 4: If applicable, the Subcontractor's CAGE Code, as identified in SAM. The CAGE Code consists of five alphanumeric digits and does not begin with the letter O.

L.5.3.1.4(b)(5) Line 5: The specific Task Order Solicitation number.

L.5.3.1.4(b)(6) Line 6: The proposal submission date. Date shall include the month, day, and year.

L.5.3.1.4(b)(7) Column B: Shall provide recent contract numbers which demonstrate relevant past performance to this Task Order proposal submission. All contract references provided must have been performed under Government (Federal, State, and Local) and/or commercial contracts (subcontracts). Please note that references provided on classified contracts cannot be verified and will not be evaluated. The contract reference number shall fall under one of the three categories below:

L.5.3.1.4(b)(7)(i) For services performed as a Prime contract on a Government contract, provide its recent Government contract number

(and one corresponding Task Order number, if applicable, that best illustrates individual mission requirement) which demonstrated relevant past performance to this Task Order proposal submission;

OR,

L.5.3.1.4(b)(7)(ii) For services performed as a Prime contractor on a private sector contract, provide its recent private sector contract number which demonstrated relevant past performance to this Task Order proposal submission;

OR,

L.5.3.1.4(b)(7)(iii) For services as a subcontractor on a Government contract, provide its recent subcontract number which demonstrated relevant past performance to this Task Order proposal submission (DO NOT provide the Prime Government contract number). Note: The contract number given for a subcontract contract reference is the private section commercial contract number held between the subcontractor and the Prime, not the contract number between the Government and the Prime.

L.5.3.1.4(b)(8) Column C: Shall enter one name (as identified in SAM) for the contractor who performed the requirements of the contract number listed in Column B.

l

Predecessor company references may be provided in Column C. However, the Government reserves the right to determine whether the past performance of the predecessor company is relevant past performance for the contractor based on the justification in Column H as to why the contractor can claim the past performance.

L.5.3.1.4(b)(9) Column D: Shall enter one corresponding CAGE Code (as identified in SAM) for the contractor who performed the requirements of the contract number listed in Column B.

L.5.3.1.4(b)(10) Column E: Shall select from the dropdown box if the contractor listed in Column C performed the work as a Prime or

Subcontractor for the contract number listed in Column B.

L.5.3.1.4(b)(11) Column F: Shall select from the dropdown box if the work performed by the contractor listed in Column C is a Joint

Venture company to the contractor submitting this document. Select YES if the work was performed by a Joint Venture company or NO if the work was not performed by a Joint Venture company. Note: If work was performed by a Joint Venture company, the contractor submitting the document shall provide the justification in Column H as to why it can claim the experience of the Joint Venture Company.

L.5.3.1.4(b)(12) Column G: Shall select from the dropdown box if the work performed by the contractor listed in Column C is a predecessor company to the contractor submitting the document. Select YES if the work was performed by a predecessor company or NO if the work was not performed by a predecessor company. Note: If work was performed by a predecessor company the contractor submitting the document shall provide the justification in Column H as to why it can claim the past performance of the predecessor company.

L.5.3.1.4(b)(13) Column H: If the contract number in Column B is for a Joint Venture or predecessor company of the contractor submitting the document, it shall:

L.5.3.1.4(b)(13)(i) Provide the name of the contractor who is claiming the past performance in Column B.

L.5.3.1.4(b)(13)(ii) Provide a description of the relationship between the Joint Venture or predecessor company listed in Column C to the contractor that is claiming the past performance in Column B.

L.5.3.1.4(b)(13)(iii) Provide a justification as to why the contractor can claim the past performance of work in Column B by explaining

12 24

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

how the contractor will draw upon the past performance from the Joint Venture or predecessor company, and shall demonstrate that the resources (e.g. workforce, management, facilities, or other resources) of the Joint Venture or predecessor company will be transferred to the contractor or provided or relied upon for contract performance, such that the Joint Venture or predecessor company will have meaningful involvement in contract performance.

Note: If the past performance provided in Column B was not performed by a Joint Venture or predecessor company (i.e., NO was selected in

Column F and G), a justification will not be required in Column H and the associated cell will automatically format black.

L.5.3.1.4(b)(14) Column I: Shall enter the contract Period of Performance start date for the contract number listed in Column B.

Required format is…