W52P1J17R0120-0002.pdf

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

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

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

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

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

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

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

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

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name And Title Of Signer (Type or print)

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

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

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

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

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Cost Plus Fixed Fee

0002 2017NOV16

W52P1J

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

BLDGS 60 & 62

JASON N. TANAMOR

EMAIL: JASON.N.TANAMOR.CIV@MAIL.MIL

W52P1J-17-R-0120

2017OCT19

X

X 2017NOV22 10:00am

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 19

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: JASON N. TANAMOR

Buyer Office Symbol/Telephone Number: CCRC-FB/(309)782-4344

Type of Contract 1: Cost Plus Fixed Fee

Type of Contract 2: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of Amendment 0002 to Request for Proposal (RFP) # W52P1J-17-R-0120 is to incorporate the following corrections:

1. Language was updated at L.5.2.1.1(a)(3). (Page Limit: 9 Pages)

2. The proposal response date and time of this RFP has been changed to 22 NOV 2017 at 1000 AM Central Standard Time.

3. All other terms and conditions remain unchanged.

*** END OF NARRATIVE A0004 ***

2 19

W52P1J-17-R-0120 0002

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

AMC-LEVEL PROTEST PROGRAM

If you have complaints about this procurement, it is preferable that you first attempt to resolve those concerns with the responsible

Contracting Officer. However, you can also protest to Headquarters, AMC. The HQ, AMC-Level Protest Program is intended to encourage interested parties to seek resolution of their concerns within AMC as an Alternative Dispute Resolution forum, rather than filing a protest with General Accounting Office or other external forum. Contract award or performance is suspended during the protest to the same extent, and within the same time periods, as if filed at the GAO. To be timely, protests must be filed within the periods specified in FAR 33.103. Send protests (other than protests to the Contracting Officer) to:

Headquarters U.S. Army Materiel Command

Office of Command Counsel-Deputy Command Counsel

4400 Martin Road

Rm: A6SE040.001

Redstone Arsenal, AL 35898-5000

Fax: (256) 450-8840 e-mail: usarmy.redstone.usamc.mbx.protests@mail.mil

The AMC-level protest procedures are found at:

http:// www. amc.army .mil/amc/commandcounsel.html

If Internet access is not available, contact the Contracting Officer or HQ, AMC Office of Command Counsel to obtain the AMC-Level

Protest Procedures.

L.1 GENERAL INSTRUCTIONS:

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

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

Fixed Fee / Firm Fixed Price (Transition-In CLIN only) Requirements contract with some non-fee bearing cost elements (e.g., Other Direct

Costs) which are ancillary to the services provided.

L.1.2 In accordance with FAR Clause 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 The proposal shall be valid for 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 in accordance with 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 FBO.gov website. Offerors are advised to continuously monitor the FBO.gov website for new information. Offerors are deemed to have knowledge of all information that is posted to the FBO.gov website.

L.2 PROPOSAL PREPARATION:

L.2.1 The proposal shall 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

3 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

descriptive literature for submission with the proposal. Adherence to the prescribed format is required. Failure to provide proposals _____________________________ in compliance with the instructions specified as COMPLIANCE REQUIREMENTS in Section L of this RFP and in compliance with ALL_____________________________________________________________________________________________________________________________ instructions in Section M.3 of this RFP shall render the Offeror's proposal non-compliant. The proposal will not be evaluated and will________________________________________________________________________________________________________________________________________ not be further considered for award.______________________________________

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

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

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

Commercial and Government Entity (CAGE) Code.

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

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

L.2.6 Adobe PDF (Portable Document Format) Files. Scanned PDF documents must be legible and shall have the ability to be viewed 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.

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 12 MAR 2018 as the Notice to Proceed (NTP) date. Proposal information shall reflect that NTP date.

L.3 PROPOSAL SUBMITTAL INSTRUCTIONS:

L.3.1 Offeror shall submit its proposal through the FedBizOpps (FBO.gov) system. The requirements and procedures for offer submission are found in the FBO Vendor User Guide located on the FBO webpage at: https:// www. fbo.gov/downloads/FBO_Vendor_Guide. pdf.

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

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

L.3.4 Digital file names 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.

L.3.5 Once the Offeror's proposal is submitted, it can be systematically revised prior to the solicitation response deadline. Refer to

Paragraph 4.3.2 of the FBO Vendor Guide titled "Reviewing / Editing an Electric Response" for detailed guidance on completing a revision to an electronic proposal submission. Note: the FBO bid response system will send an email to the email address on file for the user confirming the electronic submission.

Note: the Offeror must be logged in to the system to be able to submit / revise electronic responses.

L.3.5.1 For assistance and troubleshooting for the FBO electronic bid response system, contact the Federal Service Desk (FSD.gov).

Phone: 866-606-8220 or Web Form (https:// gsafsd.service-now. com/fsd-gov/login .do).

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

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

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

FAR 15.207(c).

L.3.8 Instructions for Subcontractor Cost proposal submission can be found in L.5.4.2.9.

4 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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, each page shall include the complete Offeror's name, volume number, file name, date, and solicitation number in a header and/or footer.

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

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

L.4.1.2 (a) Each Offeror shall submit the most current versions of 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 FedBizOpps.gov website (FBO.gov).

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. Clarity and completeness are essential. It is the Offerors obligation to submit an unambiguous proposal that clearly reflects the Offerors intended technical approach and establishes cost credibility. Any inconsistency, whether real or apparent, between promised performance and proposed cost must be adequately explained in the proposal. For example, if the use of new and innovative techniques is intended, the impact on cost must be explained. As another example, if a business policy decision to absorb a portion of the estimated cost was made, that approach shall be stated within the proposal (including any associated calculations). Failure to adequately explain an inconsistency between promised performance and cost may result in a finding of Technical Unacceptability or a finding that a proposed cost is unrealistic for work to be performed.

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 shall render the Offeror's proposal non-compliant. The proposal ______________________________________________________________________________________________________________________________ will not be evaluated and will not be further considered for award.___________________________________________________________________

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

5 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

L.5.1.3(c) Page Limit: None

L.5.1.4 Section K clauses that require Offeror certification.

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

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

L.5.1.4(c) Page Limit: None

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

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

POC 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 in accordance with 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

6 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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, total estimated dollar value for the total period of performance of 5 years, percent of participation, and the cost proposal submittal method. The Offeror shall populate every column using the instructed fill-ins on the

Attachment 0005, Tab 2 for itself, and proposed Subcontractors.

L.5.1.7(a) COMPLIANCE REQUIREMENT: The amount in the total of Column F (Total estimated dollar value) provided on Attachment 0005, Tab 2 ______________________________________________________________________________________________________________________________ shall match the amount of "Subtotal - Proposed Labor/Fee" found on Attachment 0005, Tab 1a (Cost Price Abstract). Failure to make these_________________________________________________________________________________________________________________________________________ two amounts match shall render the Offeror's proposal non-compliant. The proposal will not be evaluated and will not be further________________________________________________________________________________________________________________________________ considered for award._____________________

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

L.5.1.7(c) File Format: MS Excel

L.5.1.7(d) Page Limit: None

L.5.1.7(e) COMPLIANCE REQUIREMENT: Failure to provide a fully completed Teaming Matrix Attachment 0005, Tab 2 containing all of the __________________________________________________________________________________________________________________________ required information (including populating every column) shall render the Offeror's proposal non-compliant. The proposal will not be______________________________________________________________________________________________________________________________________ evaluated and will not be further considered for award._______________________________________________________

L.5.1.8 SECRET Facility Clearance: Not Applicable

L.5.1.8(a) Not Applicable

L.5.1.9 Pre-Award Safety Responsibility: Not Applicable

L.5.1.9.1 Not Applicable

L.5.1.9.1(a) Not Applicable

L.5.1.9.1(b) Not Applicable

L.5.1.10 Mission Essential Contractor Services (MECS): Not Applicable

L.5.1.11 Not Applicable

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 shall 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: 9 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 shall 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) shall 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 its approach to deliver services required in the RFP and PWS. The

7 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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. As the Government is utilizing the Service Contract Act (SCA) Directory of Occupations (5th Edition) and TE 1-G-005 Key & Specified Non-Key Positions for technical evaluation purposes, the Offeror must include appropriate duty descriptions for all position titles proposed that are NOT in the SCA Directory of Occupations (5th Edition) or Exhibit E TE 1-G-005 Key & Specified Non-Key Positions. The Offeror shall utilize the

SCA Directory of Occupations (5th Edition) or Exhibit E TE 1-G-005 Key & Specified Non-Key Positions when possible. The SMP MUST BE

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

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

L.5.2.1.1(b)(1)(i) The Offerors proposal must include a firm-fixed-price (FFP) portion of the effort that provides the required on-site staff for its Program Management Office (PMO) for this task order. The pre-populated, FFP PMO positions are determined to be material to the effort and must remain staffed throughout the duration of the contract. The required labor categories are identified as firm fixed price in Exhibit E TE 1-G-005 Key & Specified Non-Key Positions and are pre-populated in the Attachment 0002. Offeror must propose any additional PMO staffing, if required by the Offerors business processes to fully support the effort solicited within this

RFP. Additional positions proposed within the firm fixed-price portion of the effort must be identified as firm fixed-price in

Attachment 0002.

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

Additionally, the Offerors independent quality section must be identified in accordance with its BOA submission.

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(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 workload data (see applicable Technical Exhibits) for both the base period and option periods (fully operational capable 12-month periods (365 day periods)). The Offeror's proposal must present a staffing approach which demonstrates a thorough understanding of the effort and provides the expected skill sets / skill level of each position, to include level of responsibility in order to successfully perform the specific workload requirements identified at Exhibit A TE 1 M-S-T-001

Minimum Functional Labor Category 1 Hours 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 and Exhibit E

TE1-G-005 Key & Specified Non-Key Positions or Offeror provided definitions to determine if the proposed labor category is consistent with the task(s) proposed. Proposed position titles not identified in the SCA Directory of Occupations (5th Edition) or Exhibit E TE1-G-

005 Key & Specified Non-Key Positions must be defined by the Offeror in its SMP (see L.5.2.1.1(b)).

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

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

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

L.5.2.1.1(c)(3)(i) The Offeror shall not add or remove any tabs (other than the example tab) to the Attachment 0002 Staffing/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: proposed hours per FTE for________________________________________________________________________________________________________________________________________ both the base period and option periods 1-4; FLC1/FLC2; identification of SCA/Exempt; SCA Code; Offeror Position Title; and____________________________________________________________________________________________________________________________ identification of Functional Area.__________________________________

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

L.5.2.1.1(c)(5)(i) Full Time Equivalents (FTEs): Compensable hours are determined by the Offeror and are the work hours available to ____________________________ perform a function in one year less holiday and vacation hours. An employee who works all available compensable hours is one 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.

8 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.2.1.1(c)(5)(ii) Functional Labor Category 1 (FLC1): Contract or task order level positions that are specifically identified to __________________________________ directly accomplish the tasks/functions of the workload provided in Exhibit X TE 5-M-S-T-001 (e.g. mechanic / shop supply clerk in support of the maintenance effort). Note: Leads may be proposed as solely FLC1, if applicable.

L.5.2.1.1(c)(5)(iii) Functional Labor Category 2 (FLC2): Contract or task order level positions required for the completion of RFP __________________________________ requirements, but do not directly perform the tasks / functions of the workload provided in Exhibit X TE 5-M-S-T-001. FLC2 positions may be required by the RFP, regulation, or the Offeror's business practices, but are not directly supporting the workload (e.g. project manager, supervisory functions, and administrative assistant). Additionally, all managers must be proposed as solely FLC2; supervisors may be split FLC1 and FLC2 with the FLC2 portion proposed commensurate with the level of supervisory duties assigned.

NOTE: FLC2 positions also include the Program Management Office (PMO) positions which are identified at TE1-G-005 Key & Specified Non-

Key Positions.

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

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

The following instructions pertain to the Staffing/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 and Exhibit A TE 5-

001 M-S-T Minimum Functional Labor Category 1 Hours in terms of FTEs and FLC1 or FLC2 on the Staffing/Labor Mix - Attachment 0002. The

Government required Key Position labor categories and associated FTEs are prepopulated as identified at TE1-G-005 Key & Specified Non-

Key Positions. The Offeror's Attachment 0002 must identify the required Specified Non-Key positions using "(Non-Key)" following the

Offeror Position Title; see example tab in Attachment 0002.

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

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

FTE (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 FLC2)) with the appropriate percentage of hours applicable to each labor category expressed as a decimal (not to exceed two decimal places to the right of the whole number). Additionally, supervisors must, by definition, have a portion of their proposed time proposed 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, SCA.

L.5.2.1.1(c)(6)(v) Proposed FLC1 FTEs, when multiplied by the associated annual hours per year by employee type proposed for the option periods, shall be equal to or greater than the total minimum hours of: Maintenance - 20,504, Supply - 7,456, as provided at Exhibit A

TE 5-001 M-S-T Minimum Functional Labor Category 1 Hours. The proposed FLC2 FTEs (i.e., FLC2 portion of proposed supervisors, if applicable) are not to be included in the total Proposed FLC1 Hours by Functional Area.

L.5.2.1.1(c)(6)(vi) The Offeror must insert the proposed Offeror Position Title and it must match the labor category description found in either the SCA, TE1-G-005 Key & Specified Non-Key Positions or be provided by the Offeror if Exempt (e.g., manager, supervisor)). If

SCA is identified, the Offeror must also provide the corresponding SCA labor code in the Column indicated as SCA Code). In the event the labor code and the Offeror Position Title do not match, the SCA labor code will take precedence over the Offeror Position Title.

Additionally, the Offeror may insert the "Duty Title" in order to better identify the functional nature of the position.

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 TE 5-001 M-S-T Minimum Functional Labor Category 1 Hours. 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 must insert the number of FTEs (or less than full time equivalents expressed as FTEs) within the applicable FTE Count column. The Offeror's staffing must be rounded to the nearest hundredth decimal (i.e. two decimal places to the right of the whole number). Formatting the cells to display only two decimal places is not considered rounding; the values entered in each cell should only contain two decimal places. FTEs entered by the Offeror with greater than two decimal places will be rounded by the Government to the nearest hundredth decimal (two decimal places to the right of the whole number) using the Microsoft Excel formula

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

9 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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

Proposed FLC1 Hours by Functional Area" by correctly calculating its total proposed FLC1 hours for Maintenance, Supply and

Transportation. Calculations must correctly multiply total proposed FLC1 FTEs by the Offeror provided Hours per Year applicable to the specific employee type. The calculated total proposed FLC1 hours must be equal to or greater than the minimum required hours as stated in Exhibit A.

L.5.2.1.1(c)(6)(xi) Note: Available hours for the base year shall be adjusted to reflect the transition-in period associated with this solicitation.

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 this factor, 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).

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

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

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

L.5.3.1.4(b) Attachment 0011 Information:

10 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.

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

11 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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

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

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

Required format is…