W52P1J21R0012-AMD0001.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

0001 2021JAN29

W52P1J

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

BLDGS 60 & 62

ROSEANNA M. MEYRER

EMAIL: ROSEANNA.M.MEYRER.CIV@MAIL.MIL

W52P1J-21-R-0012

2021JAN15

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 17

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: ROSEANNA M. MEYRER

Buyer Office Symbol/Telephone Number: CCRI-QH/(309)782-6742

Type of Contract 1: Firm Fixed Price

Type of Contract 2: Cost No Fee

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of Amendment 0001 to solicitation W52P1J-21-R-0012 is as follows:

1) Attachments were updated and added to Section J:

a) Updated Attachment 00003_Performance Questionnaire to include the correct solicitation number

b) Updated Attachment 00004_Letter of Consent to change the PCO name.

c) Updated Attachment 00007_DOL Wage Determinations by replacing WD 2015-5447 with WD 2015-5455.

d) Added Attachment 0019 - Q&A Responses_AMD01_28JAN2021 for clarification of RFP only

2) The following changes were made to Section L:

a) Updated Clause 52.233-2 to change the name of the PCO

b) Updated Compliance Requirements at section L.5.2.1.1(c)(4) to remove Years of Experience, Competencies, and PWS References from the requirement.

c) Added additional Compliance Requirements at section L.5.2.1.1(c)(6)(iv) to include that 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 and SCA.

d) Revised L.5.2.1.1(a)(3) to increase the pages allowed from four (4) to six (6).

3) Add final date for question submission to be 10 am CST 9 February 2021.

**All other terms and conditions not otherwise affected by this Amendment shall remain in full force and effect.**

*** END OF NARRATIVE A0002 ***

2 17

W52P1J-21-R-0012

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 0003 PERFORMANCE QUESTIONNAIRE_28JAN2021 28-JAN-2021

Attachment 0004 LETTER OF CONSENT_28JAN2021 28-JAN-2021

Attachment 0007 DOL WAGE DETERMINATIONS_28JAN2021 28-JAN-2021

Attachment 0019 QA RESPONSES_AMD01_28JAN2021 28-JAN-2021

3 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

Status Regulatory Cite Title Date Status Regulatory Cite Title Date _______ _______________ ______________________________________________________________________ ____________ _______ _______________ ______________________________________________________________________ ____________

L-1 CHANGED 52.233-2 SERVICE OF PROTEST SEP/2006

(a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the Government Accountability Office (GAO), shall be served on the Contracting Officer (addressed as follows) by obtaining written and dated acknowledgment of receipt from

Army Contracting Command - Rock Island

ATTN: Ryan Pierce, CCRI-QH

3055 Rodman Avenue

Rock Island, IL 61299-8000

(b) The copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO.

(End of Provision)

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

PriceRequirements contract.

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

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

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

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

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

L.1.7 Updates related to this Task Order RFP, to include the RFP, amendments, notices, and other information, will be made available on the 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 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 Offerors shall not specifically prepare samples or descriptive literature for submissions with the proposal. Adherence to the prescribed form is required. Failure to provide proposals in compliance with the instructions specified as COMPLIANCE REQUIREMENTS in Section L of this RFP and in compliance with ALL instructions in Section M.3 of this RFP shall render the Offeror's proposal non-compliant. The proposal will

4 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

not be evaluated and will not be further considered for award.

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

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

L.2.4 Offeror must be registered in the System for Award Management (SAM) and 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 30 March 2021 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 Roseanna.m.meyrer.civ@mail.mil and ryan.c.pierce.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-0055) - 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/downloaded prior to the closing of the RFP.

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

L.3.3 Reserved

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.

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

Subcontractors should allow adequate time for submission completion because the entire proposal (i.e. Offerors submission and all

Subcontractor(s) submissions) must be received by the due date and time for the proposal to be considered.

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

FAR 15.207(c).

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

5 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

in a header and/or footer.

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

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

L.4.1.2(a) Each Offeror shall submit the most current versions of Attachments 0002, 0003, and 0005 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 on the beta.SAM.gov website.

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

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

NOTE: Offerors must propose to the requirements of this Step 3 Task Order RFP. Possessing a BOA does not guarantee that an Offeror will be determined technically acceptable for the purposes of this solicitation. Therefore, Offerors must meet the requirements described in this solicitation in order to be eligible for award.

L.5 INFORMATION TO BE SUBMITTED:

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

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

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

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

L.5.1.1 c) Page Limit: None

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

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

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

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

L.5.1.2(c) Page Limit: None

L.5.1.3 Section I clauses that require Offeror completion.

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

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

L.5.1.3(c) Page Limit: None

L.5.1.4 Section K clauses that require Offeror certification.

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

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

L.5.1.4(c) Page Limit: None

6 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 the use of e-mail.

Therefore, the Offeror is required to provide at least two (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 The Contracting Officer will review the Offeror's accounting system status for determining contractor responsibility IAW FAR

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

(Attachment 0006) which contains the specific procedures that are considered part of an adequate system. Therefore, in order for an

Offeror to receive an award under this RFP, the successful Offeror will be required to demonstrate that the design of its accounting system can accomplish the specific SF 1408 procedures; as a result, the Offeror is required to provide in its proposal:

- Official documentation, from either a successful Defense Contract Audit Agency (DCAA) audit of the Offeror's accounting system; or

- A letter from the Defense Contract Management Agency (DCMA) documenting its approval/adequacy of the Offeror's accounting system; or

- Rationale for why documentation cannot be presented at proposal submission and a proposed date for which required documentation will be available. Absent an adequate accounting system, an apparent awardee cannot be determined responsible under FAR 9.104-5 and will be ineligible for award. Per FAR 9.104-5(b), an apparent awardee who does not furnish the certification or such information as may be requested by the Contracting Officer shall be given an opportunity to remedy the deficiency. Therefore, if an Offeror is unable to provide the certification with its proposal as required, it will be given another opportunity to present the required certification prior to award in the event it is determined to be the apparent awardee.

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

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

L.5.1.6.1(c) Page Limit: None

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

Offeror's_Name_Vol_1_BusSys

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

L.5.1.6.2(c) Page Limit: None

L.5.1.7 Teaming Matrix (Attachment 0005, Tab 2): The Offeror shall provide the full company name, CAGE code, role of participant, functional area(s) to be performed, (excluding the option to extend), and percent of participation. 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) RESERVED

7 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

L.5.1.7(c) File Format: MS Excel

L.5.1.7(d) Page Limit: None

L . 5 . 1 . 7 ( e ) COMPLIANCE REQUIREMENT: If an Offeror is proposing subcontractors, failure of the Offeror to populate all blue highlighted cells for itself and each of its proposed Subcontractor(s) on the Teaming Matrix (Attachment 0005, Tab 2) will render the

Offeror's proposal non-compliant. The proposal will not be evaluated and will not be further considered for award.

L.5.1.7(f) The compliance requirements of L.5.1.7 (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 Mission Essential Contractor Services (MECS)

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

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

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

L.5.1.10.1(c) Page Limit: 2 pages

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

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

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

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

L.5.1.11 RESERVED.

L.5.2 Technical 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: Six (6) 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 ) 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 Offerors approach, to include a visual representation

8 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(i.e.organizational diagram), to deliver services required in the RFP and PWS. The Offerors SMP must detail the overarching methodology used to determine the proposed skill sets / skill level; the SMP must also contain any assumptions used to support staffing decisions with any explanations needed to clarify staffing decisions. Additionally, the SMP shall detail its approach to creating its management structure from general staff oversight by first line supervisors through its company headquarters management. This approach shall detail the management and supervision structure related to executing this effort. As the Government will utilize the Service Contract

Act (SCA) Directory of Occupations (5th Edition) and TD-01 Historical Workload Data 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 on the Offerors Attachment 0002 Staffing/Labor Mix, the Offeror shall provide a labor category/title under the column ""Proposed Position Title / SCA Equivalent"" of a SCA equivalent position title if one can specifically found within the SCA

Directory of Occupations (5th Edition). If additional explanation is necessary beyond the definitions provided in the SCA Directory to describe the proposed skillset or capabilities of that labor category based on the Offerors unique business practices or staffing approach, then the SMP narrative shall provide supporting rationale to adequately explain the use of its proposed position title.

UNSCHEDULED ACTIVITIES: The historical installation logistics workload is provided in TD-01 Historical Workload Data. While this information is the best available at present, actual workload during the period of performance will vary. The Contractor shall consider fluctuations in workload in its contracted solution to account for the anticipated need to perform unscheduled events without the need for increased manpower or contract modification(s). See also Attachment 0001 Performance Work Statement, para 1.2.5.

The SMP MUST BE SUPPORTED BY THE OFFEROR'S ATTACHMENT 0002 STAFFING/LABOR MIX

L.5.2.1.1(b)(1) RESERVED

L.5.2.1.1(b)(1)(i) RESERVED

L.5.2.1.1(b)(1)(ii) RESERVED

L.5.2.1.1(b)(2) The Offeror must provide an Organizational Diagram to depict a comprehensive organizational overview that identifies the following:

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 Offerors Teaming Matrix (Attachment 0005, Tab 2).

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 Offerors Teaming Matrix (Attachment 0005, Tab 2). The command and control relationship must include identification of leadership positions (e.g., team leads, foremen, supervisors, deputies, managers) responsible for performing successful oversight of each of the primary task areas identified in Section C-5 of the PWS. FTE Counts are not required on the Organizational Diagram.

Proposed FTEs counts will only be evaluated on the Attachment 0002 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 independent quality control approach with direct coordination to the responsible corporate quality office.

L.5.2.1.1(c) Staffing/Labor Mix (Attachment 0002 - Staffing/Labor Mix): The Offeror must provide its proposed staffing mix/labor categories (skill sets / skill level, Functional Labor Category 1 (FLC1), Functional Labor Category 2 (FLC2), number of employees) in relation to the PWS requirements and the provided historical workload data (see applicable Technical Data) for both the base year and option years (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 in order to successfully perform the specific workload requirements identified at Exhibit A TD-01

Historical Workload Data and meet all the PWS requirements.

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

It is further noted that the inclusion of only some of the PWS paragraphs in Exhibit A (TD-01 Historical Workload Data) was 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

9 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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/Labor Mix.

L . 5 . 2 . 1 . 1 ( c ) ( 4 ) 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:

FLC1/FLC2; identification of SCA/CBA/Exempt; SCA Code; Proposed Position Title/SCA Equivalent; Position Description; and identification of Functional Area and CLIN references.

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): Positions determined by the Offeror and are the work hours available to perform a function in one year less holiday, sick leave and vacation hours. An employee who works all available compensable hours is one Full

Time Equivalent. 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 ) ( i i ) Functional Labor Category 1 (FLC1): Positions that directly accomplish the tasks/functions of the workload provided in Exhibit A TD-01 Historical Workload Data (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 ) ( i i i ) Functional Labor Category 2 (FLC2): Positions for the completion of RFP requirements, but do not directly perform the tasks / functions of the workload done by FLC1 positions. 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.

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 Shop or PWS requirement for this effort. For proposal purposes staffing must be constant for all years of performance. The Government intends to use the MS Excel program to analyze the data provided.

The following instructions pertain to the Staffing/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 Exhibit A TD-01 Historical Workload Data in terms of FTEs and FLC1 or FLC2 on the

Staffing/Labor Mix - Attachment 0002.

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

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 (e.g. 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/Labor Mix in all applicable locations (e.g. part time worker

(.20 FLC1) and part time supervisor (.80 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 FLC2. (See "Example Tab" contained in Attachment 0002 - Staffing/Labor Mix.).

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 and SCA.

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

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 SCA/CBA, or the SMP.

L.5.2.1.1(c)(6)(vii) The Offeror must insert the applicable functional area (i.e. Maintenance, Supply, or Transportation) in the

Column(s) indicated as "Fill in Functional Area." This column is intended to match or align with the Functional Areas listed in Exhibit

A TD-01 Historical Workload Data. The Offeror may add or delete columns as needed.

L.5.2.1.1(c)(6)(viii) The Offeror must insert the corresponding shop or PWS requirement in the cells labeled "Shop or PWS Requirement.

L.5.2.1.1(c)(6)(ix) The Offeror shall 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

10 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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

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

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 Offerors Teaming Matrix (Attachment 0005, Tab 2). The Government will verify the tasks each proposed subcontractor is expected to perform via the Offerors Teaming Matrix Attachment 0005, Tab 2 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 ) 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 Reference 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: Offerors_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

11 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.

L.5.3.1.4(b)(2) Line 2: The BOA Holder Offerors 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 Subcontractors 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.

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.

12 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 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 MM/DD/YYYY. If Column D states Subcontract, only provide the Period of Performance start date for the work performed specifically by the contractor listed in Column C.

L.5.3.1.4(b)(15) Column J: Shall enter the contract Period of Performance end date for the contract number listed in Column B. Ongoing contracts must use contract completion date (assuming all option periods are exercised). Required format is MM/DD/YYYY, To Present is not acceptable. If Column D states Subcontractor, only provide the Period of Performance end date for the work performed specifically by the contractor listed in Column C.

L.5.3.1.4(b)(16) Column K: Shall enter the Physical Place(s) of Performance for the contract number listed in Column B.

L.5.3.1.4(b)(17) Column L: Enter the Total Contract Value for the contract number listed in Column B. If option periods are available, assume all option periods will be exercised; include in the Total Contract Value.

L.5.3.1.4(b)(18) Column M: The total number of Months will be populated based on the information provided in Columns I (Start Date) and

J (End Date).

L.5.3.1.4(b)(19) Column N: The Average Annual Dollar Value (AADV) will be populated based on the information provided in Columns L

(Total Contract Value) and M (Number of Months).

L.5.3.1.4(b)(19)(i) AADV is the Total Contract Value (Column L) divided by the number of Months of performance, if all options are exercised (Column M) multiplied by 12.

L.5.3.1.4(b)(19)(ii) If the period of performance is less than 12 months, the AADV will equal the Total Contract Value (Column L).

L.5.3.1.4(b)(19)(iii) Example:

AADV Sample 1:

Contract Start Date: 05-Jun-11 Contract End Date: 20-Feb-14

Total Contract Value: $2,485,003.00

Months of Performance: 32

AADV: ($2,485,003.00 / 32) * 12 = $931,876.13

AADV Sample 2:

Contract Start Date: 01-Aug-12 Contract End Date: 01-Oct-12

Total Contract Value: $640,000.00

Months of Performance: 2 (Note: Less than 12)

AADV: $640,000.00 because the Months of Performance < 12

13 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.3.1.4(b)(20) Columns O and P: In each column, provide the name and contact information of a current Customer POC, to include valid title, complete phone number and current e-mail address, which can verify the information provided for the contract number listed in

Column B. The POC(s) provided should have direct knowledge of the work performed.

L.5.3.1.4(b)(20)(i) For a Government contract as a Prime, the POC(s) shall be a Government Contracting representative.

L.5.3.1.4(b)(20)(ii) For a private commercial contract as a Prime, the POC(s) shall be a representative of the entity with whom the private commercial contract terms were entered into.

L.5.3.1.4(b)(20)(iii) For a Government contract as a subcontractor, the POC(s) shall be a representative of the Prime contractor with whom the subcontract terms were entered into. The POC CANNOT be a Government Representative.

L.5.3.1.4(b)(21) Columns Q, R, and S: Shall list the work performed by the contractor to the corresponding functional area's performance tasks of this Task Order. These performance tasks can be found in Attachment 0001 on pages #-#, excluding the paragraphs marked as

"RESERVED".

EXAMPLE of list: Column Q

- Allied Trades

- Technical Inspections

- Production Control

L.5.3.1.4(b)(21)(i) If a list is annotated in reference to any corresponding functional area (Columns Q, R and/or S), the Offeror must submit either a PWS, Statement of Work (SOW), or Statement of Objectives (SOO) that was utilized for performance against the contract number provided in Column B of the Attachment 0011 Contract Reference Spreadsheet IAW L.5.3.1.4(b)(21)(ii)-(iv). The provided PWS, SOW, or SOO must include highlighted annotations of the actual work performed for each applicable functional area's performance tasks that are listed in the Attachment 0011 Contract Reference Spreadsheet (i.e. Columns Q, R and/or S) to support scope relevancy of the work to be performed for this Task Order solicitations requirements. The Offerors proposal shall adhere to the following:

L.5.3.1.4(b)(21)(ii) Naming Convention of Offeror:

Offeror_Name_Vol_3_SR_ContractReference#; or, Naming Convention of Subcontractors: Offeror_Name_Sub_Name_Vol_3_SR_ContractReference#

L.5.3.1.4(b)(21)(iii) File Format: MS Word or Adobe PDF

L.5.3.1.4(b)(21)(iv) Page Limit: None

L.5.3.1.4(b)(21)(v) Document Format: Provide each PWS/SOW/SOO in a separate document with appropriate headings that identifies the contract number provided in Column B of the Attachment 0011 - Contract Reference Spreadsheet.

L.5.3.1.4(b)(21)(vi) If the work was NOT performed in reference to the corresponding functional area (Columns Q, R and/or S), then annotate with "NO".

L.5.3.1.5 The Government reserves the right to determine whether the past performance provided is relevant.

L.5.3.2 The Government is under no obligation to search for additional information in…