W52P1J17R0001-0001.pdf

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

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

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

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

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

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

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

12. Accounting And Appropriation Data (If required)

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

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

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

The Contract/Order No. In Item 10A.

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

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

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

D. Other (Specify type of modification and authority)

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

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

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

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

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

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

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

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

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Cost Plus Fixed Fee

0001 2017JAN09

W52P1J

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

BLDGS 60 & 62

KAREN M. MCELHINEY

EMAIL: KAREN.M.MCELHINEY.CIV@MAIL.MIL

W52P1J-17-R-0001

2016DEC14

X

X

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: KAREN M. MCELHINEY

Buyer Office Symbol/Telephone Number: CCRC-FA/(309)782-2201

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 0001 to Solicitation W52P1J-17-R-0001 is to:

1) Update Section J Exhibit A - TE 1 M-S-T-001 to remove the mandated 1880 hours.

2) Revise Section L paragraph L.5.1.9.1(b) so the date is 20 January 2012 to present.

3) Revise Section L paragraph L.5.4.1.1(b)(1) so there is no space in the Naming Convention of Offeror.

4) As a result of this amendment the closing date and time remains unchanged at 12:00 pm CT 20 January 2017. All other terms and conditions remain unchanged.

*** END OF NARRATIVE A0002 ***

2 19

W52P1J-17-R-0001 0001

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________________ ____________________________________________________________ _______________ ____________ _______________________________ ____________________________________________________________ _______________ ____________ _______________

Exhibit A TE 1 M-S-T-001 FUNCTIONAL LABOR CATEGORY 1 HOURS 01.09.17 09-JAN-2017 009

3 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 GENERAL INSTRUCTIONS:

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

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

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

Direct Costs) which are ancillary to the services provided.

L.1.2 In accordance with FAR Clause 52.215-1, Instructions to Offerors - Competitive Acquisition (Jan 2004), 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 Teammate is defined as a Joint Venture partner and/or Subcontractor that is included in the Offeror's BOA Attachment 0002 - Team Arrangement by the closing date of the Task Order RFP.

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 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. An authorized official of the firm shall sign the Standard Form (SF) 33, all signed amendment____________________________________ coversheets (SF30) and all certifications requiring original signature. Electronic signatures are acceptable.

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(a) 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

4 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

searchable text. All elements of the file to include tables, diagrams, charts, etc. 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 the following as the Notice to Proceed (NTP) date. Proposal information shall reflect that NTP date.

Service Anticipated Number of Days Anticipated Base Period

NTP Date in Transition FOC Date End Date

Log Support (Maint, Supply and Trans; except CIIP) 02 SEP 2017 60 01 NOV 2017 30 JUN 2018

CIIP 01 JUL 2017 31 01 AUG 2017 30 JUN 2018

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 Reserved

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

L.3.6(a) Note: the Offeror must be logged in to the system to be able to submit / revise electronic responses.

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

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

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

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

L.3.8 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.9 Instructions for Teammate/Subcontractor Cost proposal submission can be found in L.5.4.2.7.

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.

5 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 will be not acceptable and will not be further considered for award.__________________________________________________________________________________________________________________

L.4.1.3 The Offeror shall provide sufficient detail to substantiate the validity of all stated assertions. Proposals must not merely repeat the RFP requirements, but rather must provide convincing documentary evidence of how contract requirements will be met. Clarity and completeness are essential. 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 as part of the proposal, except for Past Performance

(see paragraph L.5.3.1).

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

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

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

L.5.1.2(c) Page Limit: none

L.5.1.3 Section I clauses that require Offeror completion.

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

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

L.5.1.3(c) Page Limit: none

L.5.1.4 Section K clauses that require Offeror certification.

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

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

L.5.1.4(c) Page Limit: none

L.5.1.5 Offeror Points of Contact (POC): The Government does not intend to conduct discussions prior to awarding this 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. 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 SECRET Facility Clearance: Offerors must possess a SECRET Facility Clearance by the RFP closing date, at the time of award, and throughout the life of the contract. Any and all Teammates and/or Subcontractors who will be performing contract requirements which

6 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

necessitate facility clearance must also have a SECRET Facility Clearance by RFP closing date, at the time of award, and throughout the life of the contract. In order for an Offeror/Teammate/ Subcontractor to request and sponsor an individual employee's SECRET Security

Clearance to perform the functions identified in the PWS, the Offeror/Teammate/Subcontractor must possess a SECRET Facility Clearance by the RFP closing date. Possession of an INTERIM SECRET Facility Clearance will be sufficient to meet the requirement at time of proposal submission provided that it can be validated by the Defense Security Service (DSS); however, please note that access to classified

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

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

Security Clearances, the Offeror (i.e. the legal entity that is submitting the proposal and would be identified as the awardee of the contract) must possess a SECRET Facility Clearance itself and cannot rely solely on the clearance of a Teammate or Subcontractor. For a proposal submitted by a Joint Venture, the SECRET Facility Clearance must be granted under the name and CAGE code of the Joint Venture itself to meet this solicitation requirement; even if the managing partner of the Joint Venture has a SECRET Facility Clearance, or if all members of the Joint Venture have a SECRET Facility Clearance, the proposal will not be eligible for award unless the Joint Venture possesses the clearance under its own name and CAGE code.

L.5.1.6(a) The Offeror shall complete and submit Attachment 0015 - SECRET Facility Clearance. Attachment 0015 shall include a list of all proposed entities (i.e. Offeror and Teammates/Subcontractors/Subsidiaries/Multiple Facility Organizations) that require a SECRET

Facility Clearance in accordance with the PWS. The Contracting Officer will verify the Offeror and the

Teammates/Subcontractors/Subsidiaries/Multiple Facility Organizations identified on Attachment 0015 possess a SECRET Facility Clearance via the Defense Security Services (DSS) Industrial Security Facilities Database (ISFD).

L.5.1.6(b) The CAGE code listed on Attachment 0015 shall be the CAGE code of the entity that possesses the Secret Facility Clearance and shall match the CAGE code provided on Attachment 0005 Tab 2 (Teaming Matrix). However, it is acceptable, in some instances, for a CAGE code listed on Attachment 0015 to differ from the CAGE code listed on Attachment 0005 Tab 2 (i.e. Multiple Facility Organizations per

Chapter 2-108 of the NISPOM), but to be acceptable both of the CAGE codes MUST be from the SAME LEGAL ENTITY. The Offeror shall note on its Attachment 0015 if its CAGE code or its Teammate's/Subcontractor/Subsidiaries/Multiple Facility Organizations CAGE code on

Attachment 0005 Tab 2 differs from the CAGE code that holds the SECRET Facility Clearance, and in this case, the Offeror shall identify its CAGE code or its Teammate's/ Subcontractor's CAGE code that holds clearance. The Offeror shall also provide an explanation of the relationship between the CAGE code on Attachment 0005 Tab 2 and CAGE code identified on Attachment 0015 to demonstrate that the different CAGE codes are in fact for the same legal entity.

L.5.1.6(c) Naming Convention: Offeror's_Name_Vol_1_Att0015

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

L.5.1.6(e) Page Limit: none

L.5.1.6(f) COMPLIANCE REQUIREMENT: Failure to provide a completed SECRET Facility Clearance - Attachment 0015 shall render the _____________________________________________________________________________________________________________________ offeror's proposal non-compliant. The proposal will not be evaluated and will not be further considered for award. If the CAGE code______________________________________________________________________________________________________________________________________ for the Offeror or any Teammate/Subcontractor stated on the Attachment 0015 does not possess a Secret Facility Clearance, the offeror______________________________________________________________________________________________________________________________________ will be found non-compliant. The Offeror's proposal will not be evaluated and will not be further considered for award. If a CAGE code________________________________________________________________________________________________________________________________________ of the Offeror/Teammate/Subcontractor/Subsidiaries/Multiple Facility Organizations provided on Attachment 0015 is different than the_____________________________________________________________________________________________________________________________________

CAGE code provided on Attachment 0005 Tab 2 and the Offeror has not demonstrated that the different CAGE codes are from the same legal_______________________________________________________________________________________________________________________________________ entity, the Offeror's proposal will be found non-compliant. The offerors proposal will not be evaluated and will not be further_________________________________________________________________________________________________________________________________ considered for award._____________________

L.5.1.7 Business Systems Information:

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

7 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.7.1(a) Naming Convention: Offeror's_Name_Vol_1_AcctSys

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

L.5.1.7.1(c) Page Limit: none

L.5.1.7.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.7.2(a) Naming Convention: Offeror's_Name_Vol_1_BusSys

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

L.5.1.7.2(c) Page Limit: none

L.5.1.7.3 In accordance with FAR 52.245-1(b) Property management, Offerors shall have internal controls to manage (control, use, preserve, protect, repair and maintain) Government property in its possession accountable to the contract. The internal controls shall be adequate to satisfy the requirements of this clause. In doing so, the successful Offeror shall initiate and maintain the processes, systems, procedures, records, and methodologies necessary for effective and efficient control of Government property accountable to the contract. The Offeror may employ customary commercial practices, voluntary consensus standards, or industry-leading practices and standards that provide effective and efficient Government property management that are necessary and appropriate for the performance of this contract (except where inconsistent with law or regulation). Offerors shall provide a written plan detailing its internal controls to manage Government property in its possession, to include the use of appropriate net-centric electronic applications (i.e. WAWF, iRAPT, IUID Registry, DCMA eTools...etc.) that are required for GFP traceability IAW DFARS clause 252.211-7007, Reporting of Government-

Furnished Property and DoDI 4161-02, Accountability and Management of Government Contract Property. The Offerors' property management plan must address all desired outcomes in FAR clause 52.245-1(f)(1), Contractor plans and systems, separately and specifically. The

Contracting Officer will review Offerors' property management plan as part of a responsibility determination in accordance with FAR

9.104-1.

Note: After award, the successful Offeror will be required to provide its property management system specific to the place of performance sites as specified in Exhibit AB CDRL PM-24 Property Management System Plan.

L.5.1.7.3(a) Naming Convention: Offerors_Name_Vol_1_PMP

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

L.5.1.7.3(c) Page limit: none

L.5.1.8 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, proposed Teammates and proposed Subcontractors.

L.5.1.8(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 1. 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.8(b) Teammate/Subcontractor Utilization: Offerors proposing the use of Teammate(s)/Subcontractor(s) shall do so in accordance with

Section C, paragraphs C.1 (d and e) of this RFP. The Government will verify that the Offeror's proposal includes approved Teammates by comparing the Offeror's Teaming Matrix (Attachment 0005, Tab 2) to the Offeror's BOA Attachment 0002 - Team Arrangement as of the closing date of the RFP.

L.5.1.8(c) Naming Convention: Offeror's_Name_Vol_4_Att0005

L.5.1.8(d) File Format: MS Excel

8 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.1.8(e) Page Limit: none

L.5.1.8(f) 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.9 Pre-Award Safety Responsibility

L.5.1.9.1 Offers shall demonstrate capability to comply with the contract safety requirements IAW DFARS Clause 252.223-7002, Safety

Precautions for Ammunition and Explosives, Clause 252.223-7003, Change in Place of Performance - Ammunition and Explosives and paragraph

5.19 of the PWS to be part of a responsibility determination. The following shall be submitted with the proposal:

L.5.1.9.1(a) A safety plan outlining the Offeror's approach to ensure compliance with each of the General Safety Requirements described in Chapter 3 of the DoD Contractor's Safety Manual For Ammunition and Explosives (4145.26-M) dated 13 March 2008. The Offeror may provide evidence of the development and implementation of a safety program used during the performance of Ammunition Supply Services under another Government contract which includes operational procedures intended to prevent ammunition and explosive related accidents.

However, the Offeror's safety plan shall still address each of the General Safety Requirements described in Chapter 3 of the DoD 4145.26-

M. If an offeror does not have an existing safety plan, it may submit a draft safety plan addressing each of the General Safety

Requirements described in Chapter3 of the DoD 4145.26-M.

L.5.1.9.1(b) A history of accident experience that meets the reporting requirements at DoD 4145.26-M C2.2 Reporting Criteria for any

Federal, State or Local Government contracts for any type of ammunition or explosive related services with performance between the dates of 20 January 2012 to present. If the Offeror has no history of accidents that meets the reporting requirements at DoD 4145.26-M C2.2, then the Offeror shall submit, with its proposal, a statement indicating it has no accident experience that meets the reporting requirements at DoD 4145.26-M C2.2.

L.5.1.9.1(c) Subcontractor information:

(1) Identification of all subcontractors proposed for the ammunition supply services.

(2) Proposed methods used to evaluate the capability of the subcontractor to comply with the requirements of DoD 4145.26-M.

(3) Propose methods used to ensure subcontractor compliance.

L.5.1.9.1(d) Naming Convention: Offerors_Name_Vol_1_Safety

L.5.1.9.1(e) File Format: Adobe PDF or MS Word

L.5.1.9.1(f) Page Limit: None

L.5.1.10 Offerors shall submit its Small Business Administration 8(a) Certification Letter as proof of being an 8(a) contractor.

L.5.1.10(a) Naming Convention: Offeror's_Name_Vol_1_8(a)cert.

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

L.5.1.10(c) Page Limit: none

L.5.1.10(d) COMPLIANCE REQUIREMENT: Failure to provide the Small Business Administration 8(a) Certification Letter 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 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 the following:

L.5.2.1(a) Staffing and Management Plan (SMP)

L.5.2.1(b) Mission Essential Contractor Services (MECS)

L.5.2.1(c) Organizational Diagram (OD)

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

9 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 and no more than 14 point font for all documents; however, for charts, tables, and diagrams, font size shall be no less than 8 point font and no more than 14 point font.

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)(2) ___________________________________________________________________________________________________________________ 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

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 F TE 1-G-005 Key & Specified Non-Key Positions. The Offeror shall utilize the

SCA Directory of Occupations (5th Edition) or Exhibit F 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)(2) Flexible Staffing Approach: The Offeror must provide its approach to effectively and efficiently support short-term fluctuations in effort (increase/decrease), long-term increase to workload, and long-term decrease to the effort by addressing:

L.5.2.1.1(b)(2)(i) Cross-utilization / temporary reallocation - effectively and efficiently make use of existing staffing to better support short-term requirement changes; provide better and more timely support; and reduce costs through more efficient staffing. Cross utilization must address an approach to ensuring safety, training, and certification requirements are met and must not impact or appear to impact quality of the effort.

L.5.2.1.1(b)(2)(ii) Rapid increase - an effective and efficient approach during surges in effort to both long-term and short-term increases in workload where cross-utilization or temporary reallocation is not appropriate.

L.5.2.1.1(b)(2)(iii) Responsible reduction in staffing - address an effective and efficient approach to reduce staffing to levels commensurate with decreased requirements during periods of protracted reductions in workload.

L.5.2.1.1(b)(3) Transition-in Approach: Offeror must provide its time-phased approach to transitioning-in the effort from Notice to

Proceed (NTP) to successfully reaching a fully operational capability (FOC) within the time allotted in M.1.1, by addressing:

L.5.2.1.1(b)(3)(i) Open communications - approach to open communications including timely periodic meetings with the incumbent contractor and the Government documenting progress of transition (i.e., GFP/GFE inventories, hiring actions.)

L.5.2.1.1(b)(3)(ii) Hiring actions - approach to proper and timely hiring actions which include: pre-employment drug screening;

qualification verification; requisition and issuance of contractor Common Access Cards (CAC) / access badges (as required); and processing of required security clearances (as required) to ensure no impact to current operations.

L.5.2.1.1(b)(3)(iii) Accountability of Government Furnished Property (GFP) / Government Furnished Equipment (GFE) - approach to proper and timely assumption of accountability of GFP / GFE that includes properly conducting a joint inventory, to include reconciliation

(prior to end of transition), with incumbent contractor while ensuring no impact to current operations.

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, FLC1, 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.

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

10 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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: proposed hours per FTE for______________________________________________________________________________________________________________________________________ both the base period and option periods 1-4; option period total proposed FLC1 Hours by Functional Area; FLC1/FLC2; identification of______________________________________________________________________________________________________________________________________

SCA/Exempt; SCA Code; Offeror Position Title; and identification of Functional Area 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(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.

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 A TE 1 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 A TE 1 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.

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 1 M-

S-T-001 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 are prepopulated as identified at TE1-G-005 Key & Specified Non-Key Positions; the

Offeror must identify its associated FTEs for the pre-populated 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 and 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 - 257,560, Supply - 144,760, and Transportation -

127,840 as provided at Exhibit A TE 1 M-S-T-001 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

11 19

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 1 M-S-T-001 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 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.2 Mission Essential Contractor Services (MECS):

L.5.2.1.2(a) The Offeror's MECS proposal shall adhere to the following:

L.5.2.1.2(a)(1) Naming Convention: Offeror's_Name_Vol_2_MECS, L.5.2.1.2(a)(2) File Format: Text Searchable Adobe PDF, L.5.2.1.2(a)(3) Page Limit: 2 pages, L.5.2.1.2(a)(3)(i) Page limit excludes cover page, table of contents, and glossary of…