W52P1J20R0052-0001.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

No Cost

0001 2020APR13

W52P1J

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

BLDGS 60 & 62

ZACK A. LUNDQUIST

EMAIL: ZACK.A.LUNDQUIST.CIV@MAIL.MIL

W52P1J-20-R-0052

2020MAR27

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 11

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: ZACK A. LUNDQUIST

Buyer Office Symbol/Telephone Number: CCRI-VE/(309)782-5781

Type of Contract 1: No Cost

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of Amendment 0001 to Solicitation is as follows:

1. To update Section L Narrative L.5.1.3(a) Required File Name:

From: OfferorName_Att0006_POCs

To: OfferorName_Att0005_POCs

2. To update the size limit for proposal transmission through email to 10 MB

*** END OF NARRATIVE A0002 ***

2 11

W52P1J-20-R-0052

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 they emphasize the significant areas to be addressed in the proposal. Review the Performance Work Statement (PWS) (Attachment 0001) contained in this Request for Proposal (RFP) for further insight into the areas that shall be addressed within the proposal. Include sufficient information to enable the Government evaluators to 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 execute Basic Ordering Agreements (BOAs) to offerors who are qualified by receiving an Acceptable rating for Technical. Past Performance and Cost/Price evaluations will not be performed at the

BOA level.

L.1.2 The Government intends to execute BOAs based upon the content of initial proposals and without negotiating with offerors after receipt of those initial proposals; as such, an offerors initial proposal should contain sufficient information to satisfy the technical requirements. Offerors are cautioned to examine this solicitation in its entirety to ensure that its proposal contains all necessary information, provides all required documentation, and is 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 or to cure problems it finds in proposals. The Government does reserve the right, however, to negotiate with offerors whose initial proposals are determined to be technically unacceptable if it is in the best interest of the Government to do so. If negotiations are determined to be in the

Governments best interest, the Government will only negotiate with those offerors whose proposals do not contain significant informational deficiencies. The Government will not negotiate with offerors whose proposals are determined to contain significant informational deficiencies; those offerors will be precluded from receiving a BOA and will be notified in writing.

Offerors are reminded that this BOA process (both the evaluation of proposals and the placement of BOAs), is not a competitive acquisition process; as such, the source selection policies and procedures of FAR 15.3 do not apply.

L.1.3 The proposal shall be valid for 180 days from the required submission date.

L.1.4 Late proposals will not be accepted.

L.1.5 For the purposes of this BOA RFP:

L.1.5(a) An offeror is defined as the prime contractor or Joint Venture (JV) that proposes an organizational capability for consideration for an executed BOA.

L.1.5(b) A 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.6 Updates to the solicitation, to include the RFP, amendments, notices, and other information, will be made available on the betaSAM

(beta.SAM.gov) website. Offerors are advised to continuously monitor the beta.SAM.gov website for new information. Offerors are deemed to have knowledge of all information that is posted to the beta.SAM.gov website.

L.2 PROPOSAL PREPARATION

L.2.1 The proposal shall be prepared in a clear, legible, practical manner. In addition, the offeror shall write the proposal in

English and shall be specific and complete as described in these instructions. Adherence to the prescribed format is required. Failure ________ to provide a proposal in compliance with the instructions specified as COMPLIANCE REQUIREMENT in Section L of this RFP shall render the________________________________________________________________________________________________________________________________________ offeror's proposal non-compliant. The proposal will not be evaluated and will not be further considered for receipt of an executed BOA.________________________________________________________________________________________________________________________________________

The Government is not obligated to engage in any exchanges with an offeror who fails to provide all of the required documents for evaluation.

L.2.1(a) Note: The Government reserves the right to waive the Compliance Review if it is in the Government's best interest.

L.2.2 No classified material shall appear anywhere within the proposal.

L.2.3 The 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.4 Digital MS Word and MS Excel files, where requested and required pursuant to provisions of this RFP, shall be compatible with

Microsoft (MS) Office 2013.

L.2.4(a) Note: The offeror shall not lock or password protect any file (e.g. *.doc, *.pps, *.xls, *.txt. *.msg).

L.2.5 Adobe Portable Document Format (PDF) Files: Scanned PDF documents, where requested and required pursuant to provisions of this

RFP, must be legible and must be viewable in Adobe Acrobat.

3 11

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.2.5(a) Text Searchable Adobe PDFs: File formats that are identified as Text Searchable Adobe PDF must be formatted to contain searchable text. Note: All Narrative 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.

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

Attachment 0004 for a complete list of non-acceptable file types.

L.3 PROPOSAL SUBMITTAL INSTRUCTIONS:

L.3.1 Proposals shall be submitted electronically to usarmy.ria.acc.mbx.eagle@mail.mil and lana.r.graw.civ@mail.mil. Due to file size restrictions, Proposals may be submitted through Department of Defense (DOD) Secure Access File Exchange (SAFE), http://safe.apps.mil/

. 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 (W52P1J-20-R-0052) - Add company name.

In the body of the email state how many emails and attachments are part of the proposal submission.

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 ten (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 shall 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. The abbreviation used for the name of the company should be consistent across all file names found within the proposal.

L.3.5 Proposal revisions are possible and permitted until the solicition response deadline.

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

Offerors should allow adequate time for submission completion because the entire proposal must be received by the due date and time for the proposal to be considered timely.

L.3.7 To avoid rejection of an offer, the offeror shall make every effort to ensure its electronic submission is virus free.

Submissions or portions thereof submitted and which the automatic system detects the presence of a virus or which are otherwise unreadable will be treated as unreadable pursuant to FAR 15.207(c).

L.4 PROPOSAL STRUCTURE:

L.4.1 The offeror shall submit a proposal in accordance with the guidelines below.

L.4.1.1 For all documents with the exception of the Attachment 0003 Experience Matrix, each page shall include the complete offeror's name, offeror's CAGE Code, BOA RFP number, and proposal submission date 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 BOA, the offeror must submit a complete response to this RFP using the instructions provided in Section L. 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,_______________________________________________________________________________________________________________________________________ the offeror's proposal will not be acceptable and will not be further considered for execution of a BOA.________________________________________________________________________________________________________

L.4.1.3 The offeror shall provide sufficient detail to substantiate the validity of all stated assertions. The proposal must not merely repeat the RFP requirements, but rather must provide narrative evidence in support of any statements relating to proposed capabilities or relevant experience. Data not submitted with the proposal and presumed to be known (i.e., previous projects performed for the United

States Government) will not be considered as part of the proposal.

L.5 INFORMATION TO BE SUBMITTED:

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

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

4 11

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.1.1(a) Required File Name: OfferorName_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 by an authorized agent shall render the offeror's proposal non- ___________________________________________________________________________________________________ compliant, and it will not be evaluated nor considered for award of an executed BOA.____________________________________________________________________________________

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 with block fourteen (14) completed.

L.5.1.2(a) Required File Name: OfferorName_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 Offeror Points of Contact (POC): The offeror(s) are required to provide two (2) company individuals whose responsibilities will include reading and responding to Government proposal inquiries 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 should be available in case of the main agents unavailability. The two (2) agents names, titles, telephone numbers, email addresses, and mailing addresses shall be provided in

Attachment 0005.

L.5.1.3(a) Required File Name: OfferorName_Att0005_POCs

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

L.5.1.3(c) Page Limit: none

L.5.1.4 JV Information: In order for the Government to review the JV partnership, if applicable, the offeror shall submit the following information:

L.5.1.4(a) A signed legal JV agreement prepared by an attorney, which clearly explains the responsibilities of each party to the JV agreement. In addition, the agreement shall clearly explain the formation of the JV and procedures for acceptance of product and payment. The JV agreement shall clearly identify the team lead company and the team lead company's point of contact, as well as their responsibilities explained in detail. In addition, company names, POCs, business size, number of employees (including all affiliates), and description of work to be performed by members of the JV shall be provided as part of the JV agreement.

L.5.1.4(b) Any updates to the JV agreement shall be submitted to the EAGLE mailbox within seven calendar days after the JV agreement is signed.

L.5.1.4(c) A signed copy of any other agreements, either formal or informal, that identify the roles and responsibilities of each business concern in the JV.

L.5.1.4(d) If other than a small business concern is part of the JV, a copy of the Small Business Administration (SBA) approved SBA

Mentor-Protege Agreement. The offeror should be aware of the SBAs regulations regarding affiliations to determine business size.

Affiliation regulations are especially important for determining the size of JVs.

L.5.1.4(d)(i) Required File Name: Offerors Name_JV

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

L.5.1.4(d)(iii) Page Limit: none

If an offeror is not proposing a JV, the file Offerors Name_JV is not required.

L.5.1.5 Property Management Plan. In accordance with FAR 52.245-1(b) Property management, Offerors shall have internal controls to manage (control, use, preserve, protect, repair and maintain) Government property in its possession accountable to the contract. The internal controls shall be adequate to satisfy the requirements of this clause. In doing so, the successful Offeror shall initiate and maintain the processes, systems, procedures, records, and methodologies necessary for effective and efficient control of Government property accountable to the contract. The Offeror may employ customary commercial practices, voluntary consensus standards, or industry-leading practices and standards that provide effective and efficient Government property management that are necessary and appropriate for the performance of this contract (except where inconsistent with law or regulation). Offerors shall provide a written plan detailing its internal controls to manage Government property in its possession, to include the use of appropriate net-centric

5 11

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

electronic applications (i.e. WAWF, iRAPT, IUID Registry, DCMA eTools...etc.) that are required for Government-Furnished Property (GFP) traceability IAW DFARS clause 252.211-7007, Reporting of Government-Furnished Property and DoDI 4161.02, Accountability and Management of Government Contract Property. The Offerors' property management plan must address all desired outcomes in FAR clause 52.245-1(f)(1), Contractor plans and systems, separately and specifically. The Contracting Officer will review Offerors' property management plan in accordance with FAR 9.104-1.

Note: Task Order awardees will be required to provide its property management system specific to the place of performance sites as specified in the Task Order CDRL Property Management System.

L.5.1.5 (a) Naming Convention: Offerors_Name_PMP

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

L.5.1.5 (c) Page limit: none

L.5.2 Technical Factor:

In order for the Government to have a reasonable expectation of an offerors ability to successfully perform on subsequent efforts, the

Offeror must demonstrate technical capability by detailing its proposed technical approach to meet the requirements specified in the PWS and this RFP by providing the following:

L.5.2(a) Technical Capability Statement (TCS)

L.5.2(b) Representative Support Element (RSE)

L.5.2(c) Corporate Organizational Structure

L.5.2(d) Experience

L.5.2.1 Technical Capability Statement (TCS) ____________________________________

L.5.2.1(a) The offeror's proposed TCS must adhere to the following:

L.5.2.1(a)(1) Required File Name: Offerors Name_TCS

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

L.5.2.1(a)(3) Page limit for the TCS is twenty (20) pages.

L.5.2.1(a)(4) Page limit excludes cover page, table of contents, and glossary of abbreviations and acronyms.

L.5.2.1(a)(5) Pages larger than 8.5 inches x 11 inches will be counted as two (2) pages.

L.5.2.1(a)(6) The font size shall be no less than 10 point font for all documents, to include charts, tables, and diagrams.

L.5.2.1(a)(7) COMPLIANCE REQUIREMENT: Failure to provide a TCS shall render the offeror's proposal non-compliant, and it will not be _______________________________________________________________________________________________ evaluated nor considered for award of an executed BOA.________________________________________________________

L.5.2.1(b) Technical Capability Statement (TCS). The offeror shall provide a TCS specific to the EAGLE effort that identifies the offerors core competencies, demonstrates how those cited core competencies relate to the EAGLE effort and the ability to create a dynamic organization fully capable of supporting the Government's requirements by applying those core competencies. In order to demonstrate its technical capability, as related to the EAGLE effort, the offeror must specifically address the following four elements:

L.5.2.1(b)(1) Team Identification / Self-Performance. The offeror shall provide a TCS that describes, in detail, its processes for mission analysis and application of cited core competencies and previous experience which allow the offeror to properly determine which

(or all) of the EAGLE functional areas (Maintenance, Supply, and Transportation) it can self-perform without the use of subcontractors.

An offeror that cannot self-perform one or more functional area(s) must clearly identify its subcontractors, by company and supported functional area.

If the offeror is citing the core competencies and previous experience of a parent or affiliate company as part of the identification of its own core competencies and previous experience, the offeror shall explain how the resources of the parent or affiliate company will be utilized in performance of the proposed effort.

L.5.2.1(b)(2) The offeror must identify its process of identifying, vetting, partnering, and leading subcontractors, as well as the offerors process for replacing and adding subcontractors if necessary due to non-performance or operational changes to the effort.

6 11

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.2.1(c) Resource / Task Order Management. The offeror shall provide a TCS that describes, in detail, the methods that it will employ to manage future task order requirements from time of award to completion of the effort. Note: This section will be incorporated into subsequent Step Three EAGLE Task Order contracts. In describing its resource / task order management, the offeror must provide, at a minimum:

L.5.2.1(c)(1)The offerors approach for planning, allocating, and controlling resources and costs for awarded task orders.

L.5.2.1(c)(2) The offerors process for scheduling, budgeting, and accumulating expenditures (hours and dollars); identifying expenditures and schedule problems; and tracking task order performance.

L.5.2.1(c)(3) The offerors process for accounting and collecting expenditure data for an extensive CLIN structure characterized by increasing number of subCLINs for multiple tasks.

L.5.2.1(c)(4) The offerors process for timely incorporation of subcontractor technical, schedule and financial performance data into the offeror's monthly reports for individual task orders.

L.5.2.1(c)(5) The offerors approach to ensuring proper training, licensing, certifications, and safety measures for the execution of

EAGLE logistics services.

L.5.2.1(d) Flexible Staffing Approach. The offeror shall provide a TCS that describes, in detail, the offerors approach to effectively and efficiently support short-term fluctuations in effort (increase/decrease), long-term increase to workload, and long-term decrease to workload for future cost-plus-fixed-fee type efforts. Note: This section will be incorporated into subsequent Step Three EAGLE Task

Order contracts; however, if a Step Three EAGLE Task Order has more specific requirements relating to surges in effort, the Task Order

RFP will address those requirements and a proposed approach submitted in response thereto will take precedence. In describing its flexible staffing approach, the offeror must address each of the following:

L.5.2.1(d)(1) Cross-utilization / temporary reallocation: An effective and efficient approach to making use of existing staffing to better support short-term requirement changes; provide better and more timely support; and, reduce costs through more efficient staffing. Cross-utilization must address an approach to ensuring safety, training, and certification requirements are met in a manner that would not impact quality of the effort.

L.5.2.1(d)(2) Rapid increase: An effective and efficient approach to rapidly increase staffing during surges in effort, for both long-term and short-term increases in workload, where cross-utilization or temporary reallocation is not appropriate. However, if a Step

Three EAGLE Task Order has more specific requirements relating to surges in effort, the Task Order RFP will address those requirements and a proposed approach submitted in response thereto will take precedence.

L.5.2.1(d)(3) Responsible reduction in staffing: An effective and efficient approach to reduce staffing to levels commensurate with decreased requirements during periods of protracted reductions in workload while also ensuring retention of qualified employees.

L.5.2.1(e) Transition-in Approach: The offeror shall provide a TCS that describes the offerors generalized approach to providing seamless transition of requirements applicable to future task orders. The offerors approach must address transitioning efforts with outgoing contractors from Notice to Proceed (NTP) to successfully reaching a fully operational capability (FOC). Note: This section will be incorporated into subsequent Step Three EAGLE Task Order contracts. The transition-in approach must address, at a minimum:

L.5.2.1(e)(1) Open communications, including timely, periodic meetings with the incumbent contractor and the Government; documenting progress of transition-in tasks; and conducting inventories IAW applicable Army regulations and SOPs. Inventories must include GFP/GFE.

L.5.2.1(e)(2) Proper hiring actions to include pre-employment drug screening, qualification verification, and requisition/issuance of

Department of the Army Contractor Common Access Cards (CAC), access badges, and security clearances that will ensure no impact to current operations.

L.5.2.2 Representative Support Element (RSE) ____________________________________

L.5.2.2(a) The offeror's proposed RSE must adhere to the following:

L.5.2.2(a)(1) Required File Name: Offerors Name_RSE

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

L.5.2.2(a)(3) Page Limit: fourteen (14) pages

L.5.2.2(a)(4) Page limit excludes cover page, table of contents, and glossary of abbreviations and acronyms.

L.5.2.2(a)(5) Pages larger than 8.5 inches x 11 inches will be counted as two (2)pages.

7 11

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.2.2(a)(6) The font size shall be no less than 10 point font for all documents, to include charts, tables, and diagrams.

L.5.2.2(a)(7) COMPLIANCE REQUIREMENT: Failure to provide the RSE shall render the offeror's proposal non-compliant, and it will not be _________________________________________________________________________________________________ evaluated nor considered for award of an executed BOA._______________________________________________________

L.5.2.2(b) The offeror shall provide a RSE in a narrative format based on the information provided in its TCS and in support of the PWS requirements. The RSE narrative must clearly identify and detail an approach relative to each of the functional areas noted below as well as provide any assumptions used in determining the specific staffing to include definitions of Offeror-developed position titles in accordance with paragraph L.5.2.2(c). Additionally, the RSE must be supported by the offerors Labor Basis of Estimate (BOE).

L.5.2.2(b)(1) Project Management Office (PMO): The RSE narrative must detail a realistic and feasible approach to project management and control. The offeror shall adequately detail its approach to providing the appropriate staffing with the required knowledge, experience, and skills using the appropriate tools and techniques needed to effectively manage all aspects of all three functional areas as well as the required human resources functions.

L.5.2.2(b)(2) Maintenance Functional Area: The RSE narrative must detail the offerors approach to plan, organize, facilitate, direct, control and execute maintenance operations specifically associated with the sample equipment density listing provided at Exhibit A

Equipment Density Listing. The offerors RSE narrative must adequately detail an approach for carrying out preventive maintenance checks and services (PMCS); performing equipment classification; and accomplishing scheduled as well as unscheduled field and sustainment level maintenance on the density identified in Exhibit A Equipment Density Listing. The narrative must include details on the offerors technical inspection process (initial and final) as well as its quality control process/procedures with an emphasis on achieving a successful first time pass rate. Additionally, the RSE narrative must accurately address the specific Army Logistics Information

Systems (LIS)(BOA PWS para 2.1.19) being utilized, proper accountability, security and other regulatory requirements specific to sensitive items including controlled cryptographic items (CIIC 9), weapons, and night vision devices (CIIC 7).

L.5.2.2(b)(3) Supply Functional Area: The RSE narrative must detail the offerors approach to deliver services consistent with a Unit

Supply Support Activity (SSA) and a cognizant Property Book Office (PBO)by providing inventory management, asset accountability and asset visibility through proper operation of the appropriate LIS (BOA PWS para 2.2.10.2). The SSA approach must accurately address proper accountability, security and other regulatory requirements specific to sensitive items including controlled cryptographic items

(CIIC 9), weapons, and night vision devices (CIIC 7).

L.5.2.2(b)(4) Transportation Functional Area: The RSE narrative must detail the offerors approach to delivering Personal Property and

Transportation Motor Pool (TMP) operations. This approach must address briefings to customers regarding personal property entitlements and responsibilities, preparation of required documentation to initiate and schedule personal property shipments in accordance with

Joint Travel Regulation (JTR), Defense Transportation Regulation DoD 4500.9-R (DTR) Part IV, Personal Property Consignment Instruction

Guide (PPCIG) and Service Supplements. Additionally, the RSE narrative must accurately address appropriate LIS(BOA PWS para 2.3.9).

This approach must also address regulatory requirements specific to TMP operations and services to include general administration, dispatching and control of the fleet.

L.5.2.2(c) Labor Basis of Estimate (BOE): The offeror must provide its labor basis of estimate, in narrative format, in relation to the

BOA PWS requirements associated with the PMO, maintenance, supply, and transportation functional areas identified at L.5.2.2(b)(1) through L.5.2.2(b)(4). The offeror's BOE must demonstrate a thorough understanding of the effort through its analysis of the effort, realistic assumptions and staffing decisions in order to successfully perform the PWS requirements associated with the PMO, maintenance, supply, and transportation functional areas identified at L.5.2.2(b)(1) through L.5.2.2(b)(4). The BOE must address specific labor categories (Fair Labor Standards Act (FLSA) exempt and non-exempt) required to perform the effort, the rationale for their selection, and must fully support the proposed Corporate Organizational Structure.

NOTE: For Technical evaluation purposes only, the Government will utilize the SCA Directory of Occupations (5th Edition) labor category definitions and offeror-provided position titles to determine if the proposed position title is appropriate for the PMO, maintenance, supply and transportation functional area elements identified at L.5.2.2(b)(1) through L.5.2.2(b)(4). Proposed position titles not identified in the SCA Directory of Occupations (5th Edition) must be defined by the offeror in its RSE (see L.5.2.2(b)).

Offeror's proposed Labor BOE shall adhere to the following:

L.5.2.2(c)(1) Naming Convention: Offeror's_Name_BOE

L.5.2.2(c)(2) File Format: MS Word

L.5.2.2(c)(3) Page Limit: four (4) pages

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

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

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

8 11

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.2.2(c)(7) COMPLIANCE REQUIREMENT: Failure to provide the LABOR BOE shall render the Offeror's proposal non-compliant and it will _______________________________________________________________________________________________ not be evaluated nor considered for award of an executed BOA.______________________________________________________________

L.5.2.3 Corporate Organizational Structure. __________________________________

L.5.2.3(a) The offeror's proposed Corporate Organizational Structure must adhere to the following:

L.5.2.3(a)(1) Required File Name: Offerors Name_COS

L.5.2.3(a)(2) File Format: Adobe PDF

L.5.2.3(a)(3) Page Limit: six (6) pages

L.5.2.3(a)(4) Page limit excludes cover page, table of contents, and glossary of abbreviations and acronyms.

L.5.2.3(a)(5) Pages larger than 8.5 inches x 11 inches will be counted as two (2) pages.

L.5.2.3(a)(6) The font size shall be no less than 10 point font for all documents, to include charts, tables, and diagrams.

L.5.2.3(a)(7) COMPLIANCE REQUIREMENT: Failure to provide the corporate organizational structure shall render the offeror's proposal non- __________________________________________________________________________________________________ compliant, and it will not be evaluated nor considered for award of an executed BOA.______________________________________________________________________________________

L.5.2.3(b) Corporate Organizational Structure: The offeror shall provide a corporate organizational structure narrative (which can include charts, tables, and diagrams) that demonstrates a comprehensive, realistic and feasible organizational overview based on the following:

L.5.2.3(b)(1) Identification of which tasks in the RSE will be performed by the offeror and which tasks will be performed by each proposed subcontractor (if applicable).

L.5.2.3(b)(2) Identification of the command and control relationships within the offerors organization as well as the command and control relationship between the offeror and each proposed subcontractor in the RSE (if applicable). Demonstration of the command and control relationships must include identification of leads, supervisors, managerial and executive leadership positions responsible for performing successful oversight of each of the primary task areas identified in Section 2.0 of the PWS as well as overseeing the execution of the overall effort. Management positions must indicate responsibility/role in responding to issues that may arise during execution of the effort (e.g., assigned ISO 9001:2015 management function).

L.5.2.3(b)(3) Identification of a quality control organization that is onsite but which operates independently by reporting directly to the corporate quality office. Note: If the offerors Corporate Organizational Structure is depicted through charts, tables, and/or diagrams, appropriate identifiers/ markers/legends/keys must be provided to adequately demonstrate that the quality control organization reports directly to the corporate quality office and operates independently of the Project Management Office, the Project Manager, and/or any supervisors responsible for the direct oversight of a primary task area.

L.5.2.4 Experience __________

L.5.2.4(a) The offeror's Experience Matrix (Attachment 0003) must adhere to the following:

L.5.2.4(a)(1) Required File Name: Offeror's_Name_Attachment_0003

L.5.2.4(a)(2) File Format: Fillable PDF

L.5.2.4(a)(3) COMPLIANCE REQUIREMENT: Failure to provide the Attachment 0003 Experience Matrix in the Government-provided format will _________________________________________________________________________________________________ render the offeror's proposal non-compliant, and it will not be further evaluated nor considered for award of an executed BOA.________________________________________________________________________________________________________________________________

L.5.2.4(b) Experience: The offeror must provide its recent and relevant experience, as a measure of the likelihood to ensure proper execution, of all three functional areas (Maintenance, Supply and Transportation) as identified at L.5.2.2(b)(2) through L.5.2.2(b)(4).

Experience shall be provided on the Attachment 0003 Experience Matrix. [The Government does not require additional documentation for experience other than a completed Attachment 0003 Experience Matrix; additional documentation, if submitted, will not be evaluated by the Government]. Offerors shall identify no less than one (1), and no more than three (3), recent and relevant contracts for EACH functional area (Maintenance, Supply and Transportation), for a total of no more than nine references per proposal. At least one of the contract references submitted must have been performed by the offeror. If the offeror is relying upon a reference for its parent or an affiliate company to satisfy this requirement, in accordance with L.5.2.1(b)(1) and M.2.3(a)(1), the offeror must explain how the resources of the parent or affiliate company will be utilized in performance of the proposed effort. If an offeror identifies experience of another company/legal entity with a CAGE code different than its own (whether it be a parent company, an affiliate, or a company being proposed as a subcontractor), the offeror shall certify that it has permission from an authorized agent of that other company to

9 11

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

submit the contract reference information as part of the offerors Experience Matrix; said certification is provided by signing the applicable line on Attachment 0003.

L.5.2.4(b)(1) Recent is defined as a measure of time that has elapsed since the contract reference occurred. Recent is generally expressed as a time period during which contract references are considered relevant. For the purpose of this requirement, recent is any contract under which any performance, delivery, or corrective action has occurred within the following time standards: three (3) years prior to this RFP closing date, regardless of the award date.

L.5.2.4(b)(2) Relevant is defined as similar in scope and complexity to this effort, which are defined as follows:

L.5.2.4(b)(2)(i) Scope: The type of requirements/tasks performed under the contract.

L.5.2.4(b)(2)(ii) Complexity: Two or more simultaneous efforts being performed within the SAME functional area (e.g., field level maintenance, technical inspections, and production control).

L.5.2.4(c) Instructions for completing the Attachment 0003 Experience Matrix are as follows:

L.5.2.4 (c) (1) Cover page - self-certification: If the contract reference identified at L.5.2.4(c)(4)(line 3) was performed by a company other than the offeror (i.e. the company has a CAGE code different than the offerors CAGE code, whether it is a parent company, an affiliate, or a company being proposed as a subcontractor), the offerors authorized agent shall provide his/her signature certifying that the other entity granted the offeror permission, either in writing or verbally, to submit the contract reference information as part of the offerors Experience Matrix (Attachment 0003).

L.5.2.4(c)(2) Line 1: The offeror shall enter the name of the Prime offeror submitting a proposal for a BOA and the respective CAGE

Code, as identified in SAM. The CAGE Code consists of five (5) alphanumeric digits and does not begin with the letter O.

L.5.2.4(c)(3) Line 2: The offeror shall enter the contractors name (only name one) that performed the requirements of the contract number listed at line 3 and the respective CAGE Code, as identified in SAM (i.e. Parent Company, Affiliate Company, or Subcontractor).

If the Prime offeror performed the requirements of the contract number listed at line 3, enter N/A. The CAGE Code consists of five (5) alphanumeric digits and does not begin with the letter O.

L.5.2.4(c)(4) Line 3: The offeror shall provide the recent contract number and program title which demonstrates recent and relevant experience to this RFP. Each contract reference provided must have been performed under Government (Federal, state, local) or commercial contracts. 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.2.4(c)(4)(i) For services performed as a Prime contractor on a Government contract, enter one (1) recent Government contract number

(and one (1) corresponding task order number, if applicable, that best illustrates individual mission requirement) which demonstrated recent and relevant experience to this RFP for the offeror or subcontractor; OR, L.5.2.4(c)(4)(ii) For services performed as a Prime contractor on a private sector contract, enter one (1) recent and relevant private sector contract number which demonstrated recent and relevant experience to this RFP for the offeror or subcontractor; OR, L.5.2.4(c)(4)(iii) For services as a subcontractor on a Government contract or a private sector contract, enter one (1) recent and relevant subcontract number which demonstrated recent and relevant experience to this RFP for the offeror or subcontractor (DO NOT enter the Prime Government contract number). Note: The contract number given for a subcontract contract reference is the private sector commercial contract number held between the subcontractor and the Prime, not the contract number between the Government and the Prime.

L.5.2.4(c)(5) Line 4: The offeror shall enter the contract total dollar value in US dollars. If option periods are available, assume all option periods will be exercised and included in the contract total dollar value.

L.5.2.4(c)(6) Line 5: The offeror shall enter the contract award date and period of performance, to include the contract end date for the contract number listed on line 3. Ongoing contracts must use contract completion date (assuming all option periods are exercised).

The required format is MM/DD/YYYY; simply writing To Present is not acceptable. If line 6 indicates that the experience cited was gained as a subcontractor, only provide the Period of Performance end date for the work performed specifically by the contractor listed at line 2.

L.5.2.4(c)(7) Line 6: The offeror shall select the appropriate box if the contractor listed on line 1 or 2 performed the work as a

Prime Contractor or Subcontractor for the contract number listed at line 3.

L.5.2.4(c)(8) Line 7: If subcontractor is selected at Line 6, provide the name of the prime contractor the effort was awarded to.

L.5.2.4(c)(9) Line 8: The offeror shall provide the customer name (requiring activity or prime contractor, if subcontractor indicated at line 6) and address.

10 11

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.2.4(c)(10) Line 9: The offeror shall enter the applicable contracting officials name, telephone number and email address for the contract listed at line 3. The PCO must be able to verify the information provided for the contract. For a Government contract as a

Prime, the POC shall be a Government Contracting Representative. For a private commercial contract as a Prime, the POC shall be a representative of the entity with whom the private commercial contract terms were entered into. For a Government contract as a subcontractor, the POC shall be a representative of the Prime Contractor with whom the subcontractor terms were entered into; the POC cannot be a Government representative.

L.5.2.4(c)(11) Line 10: The offeror shall enter the applicable Government or commercial activity technical representative, or COR, name, telephone number and email address for the contract listed at line 3. The POC provided should have direct knowledge of the work performed.

L.5.2.4(c)(12) Line 11: The offeror shall enter examples of the tasks performed under the effort listed at line 3. Examples should identify tasks relevant to the BOA PWS in order to assist the Government in determining the relevance of the cited effort (see definition at L.5.2.4(b)(2)). The offeror may copy/paste directly from the contract documentation; however, note that this field is limited to 2,600 characters.

*** END OF NARRATIVE L0002 ***

11 11