W52P1J15R0099-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 2015OCT23

W52P1J

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

BLDGS 60 & 62

MICHAEL DEBISSCHOP

EMAIL: MICHAEL.L.DEBISSCHOP.CIV@MAIL.MIL

W52P1J-15-R-0099

2015SEP30

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 23

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: MICHAEL DEBISSCHOP

Buyer Office Symbol/Telephone Number: CCRC-FE/(309)782-8018

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 02 to solicitation W52P1J-15-R-0099 is to accomplish the following:

1) Communicate the only acceptable proposal submission method for Offerors is through FedBizOPs as instructed at L.3 Proposal Submittal

Instructions.

2) Remove Section L paragraph L.3.10 Alternate Method of Proposal Submission.

3) Remove clause 52.214-4584, Hand-Delivered Bids, Quotes, or Proposals dated Aug/2014.

4) Add clause 252.209-7991, Representation by Corporations Regarding an Unpaid Delinquent Tax Liability or a Felony Conviction Under any

Federal Law--Fiscal Year 2016 Appropriations (DEV 2016-O0002).

5) As a result of this amendment the closing date and time remains unchanged at 12:00pm CT 30 Oct 2015. All other terms and conditions remain unchanged.

*** END OF NARRATIVE A0003 ***

2 23

W52P1J-15-R-0099 0002

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION K - REPRESENTATIONS, CERTIFICATIONS, AND OTHER STATEMENTS OF OFFERORS

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

K-1 ADDED 252.209-7991 REPRESENTATION BY CORPORATIONS REGARDING AN UNPAID DELINQUENT TAX OCT/2015

(DEV 2016- LIABILITY OR A FELONY CONVICTION UNDER ANY FEDERAL LAW¿FISCAL YEAR

O0002) 2016 APPROPRIATIONS (DEVIATION 2016-O0002)

(a) In accordance with section 101(a) of the Continuing Appropriations Act, 2016 (Pub. L. 114-53) and any subsequent FY 2016 appropriations act that extends to FY 2016 funds the same restrictions as are contained in sections 744 and 745 of division E, title

VII, of the Consolidated and Further Continuing Appropriations Act, 2015 (Pub. L. 113-235), none of the funds made available by this or any other Act may be used to enter into a contract with any corporation that--

(1) Has any unpaid Federal tax liability that has been assessed, for which all judicial and administrative remedies have been exhausted or have lapsed, and that is not being paid in a timely manner pursuant to an agreement with the authority responsible for collecting the tax liability, where the awarding agency is aware of the unpaid tax liability, unless the agency has considered suspension or debarment of the corporation and made a determination that this further action is not necessary to protect the interests of the Government; or

(2) Was convicted of a felony criminal violation under any Federal law within the preceding 24 months, where the awarding agency is aware of the conviction, unless the agency has considered suspension or debarment of the corporation and made a determination that this action is not necessary to protect the interests of the Government.

(b) The Offeror represents that--

(1) It is [ ] is not [ ] a corporation that has any unpaid Federal tax liability that has been assessed, for which all judicial and administrative remedies have been exhausted or have lapsed, and that is not being paid in a timely manner pursuant to an agreement with the authority responsible for collecting the tax liability,

(2) It is [ ] is not [ ] a corporation that was convicted of a felony criminal violation under a Federal law within the preceding

24 months.

(End of provision)

3 23

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 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 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 by the Contracting Officer. 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 Offers, modifications, revisions, or withdrawals of Offers 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(s) that are included in the Offeror's BOA Attachment 0002 - Team Arrangement at 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 EAGLE website at: http://www.acc.army.mil/contractingcenters/acc_ri/eagle/index.html. Offerors are advised to continuously monitor the EAGLE website for new information. Offerors are deemed to have knowledge of all documents that are posted to the EAGLE 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 in this RFP shall render the Offeror's proposal non-compliant. The proposal will not be_______________________________________________________________________________________________________________________________________ further 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: Do not lock or password protect any file (e.g. *.doc, *.pps, *.xls, *.txt, *.msg).

L.2.6 Adobe PDF (Portable Document Format) Files. Scanned documents must be legible and shall have the ability to be viewed in Adobe

Acrobat. Note: File formats that are identified as Text Searchable PDFs must be able to be searched for text. The Government will not accept scanned documents in lieu of this requirement and will not invoke the text recognition feature within Adobe.

L.2.7 Compressed files (e.g. *.zip) will be accepted only through www.FBO.gov. Compressed files (e.g. *.zip) will not be accepted via e-

4 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

mail.

L.2.7(a) Executable files (e.g. *.bat, *.exe, *.jar, *.vb, *.wsf) will NOT be accepted through www.FBO.gov or via e-mail.

L.2.8

Service Anticipated NTP Days in Transition Anticipated FOC

Logistics Support Services 3/01/2016 90 6/01/2016

PDTE 4/20/2016 30 5/22/2016

ASP/CIF 7/15/2016 60 9/15/2016

Installation Asset Management 7/15/2016 60 9/15/2016

TMP 12/05/2016 60 2/05/2017

The above table identifies the anticipated Notice to Proceed dates for each of the incumbent contracts that are transitioning to the Ft.

Bragg EAGLE Task Order. Offerors are requested to propose transition-in, labor and fee costs based on the above dates. If there are any delays, the NTP and FOC dates will be reestablished after contract award.

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 its permitted to abbreviate the Name of the Company field within the file name.

L.3.5 An Offeror submitting its proposal, as well as its Teammates or Subcontractors submitting cost/price information independently to the Government, should note for the Offeror's records the price quote number when submission is complete. 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 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.

Offerors should allow adequate time for submission completion.

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

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 MS Word or MS Excel 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 one proposal that addresses all of the requirements of this RFP. To be considered for this

5 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

requirement, the Offeror must submit a complete response to this RFP using the instructions provided in Section L. If the Offeror's _________________ proposal fails to meet the terms and conditions of the RFP or takes exception to any of the terms and conditions of the RFP, it shall______________________________________________________________________________________________________________________________________ render the Offeror's proposal non-compliant. The proposal will not be evaluated 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) Failure to provide the signed SF 33 and in compliance with L.5.1.1(a) through L.5.1.1(c) 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 contractor 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 contractor 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 USG and the contractor 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 should 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: In order for an Offeror/Teammate/Subcontractor/Managing Partner to request and sponsor an

6 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

individual employee's SECRET Security Clearance to perform the functions identified in the PWS Paragraph 1.3.12, the

Offeror/Teammate/Subcontractor/Managing Partner shall possess a SECRET Facility Clearance prior to this RFP closing date. Therefore, the

Offeror shall complete and submit Attachment 0015 - SECRET Facility Clearance. Attachment 0015 shall include a list of proposed

Teammates/Subcontractors/Managing Partner that shall require a SECRET Facility Clearance in accordance with PWS Paragraph 1.3.12. The

Offeror shall also include the name of its Company or Managing Partner of a partnership, Joint Venture, or Limited Liability Company that possesses the SECRET Facility Clearance if the Offeror is a newly formed partnership, joint venture, or limited liability company.

The Contracting Officer will verify the Offeror and the Teammates/Subcontractors/Managing Partner identified on Attachment 0015 possess a SECRET Facility Clearance via the Defense Security Services (DSS) Industrial Security Facilities Database (ISFD).

The CAGE code listed on Attachment 0015 shall be the CAGE code of the entity that possesses the Secret Facility Clearance. It is acceptable for the CAGE codes listed on Attachment 0010 and Attachment 0015 to differ, however 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's/Managing Partner's

CAGE code on Attachment 0010 differs from the CAGE code that holds the SECRET Facility Clearance. In this case, the Offeror shall identify its CAGE code or its Teammate's/Subcontractor's/Managing Partner's CAGE code that holds clearance. The Offeror shall also provide an explanation of the relationship between the CAGE code on Attachment 0010 and CAGE code identified on Attachment 0015. If the

CAGE code on the Attachment 0015 and Attachment 0010 are different, and represent separate legal entities, the Offeror's proposal will be found noncompliant. If the CAGE code for the Offeror, Managing Partner, Teammate or Subcontractor, stated on the Attachment 0015 __________________________________________________________________________________________________________________ does not possess a Secret Facility Clearance, the Offeror will be found noncompliant. The Offeror's proposal will not be evaluated and_______________________________________________________________________________________________________________________________________ will not be further considered for award._________________________________________

NOTE: If an Offeror/Teammate/Subcontractor/Managing Partner possesses an INTERIM SECRET Facility Clearance prior to the RFP Closing date, and that can be validated by the Defense Security Service (DSS), the INTERIM SECRET Facility Clearance is sufficient to meet the

SECRET Facility Clearance requirement for proposal submission.

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

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

L.5.1.6(c) Page Limit: none

L.5.1.6(d) Failure to provide a completed SECRET Facility Clearance - Attachment 0015 and in compliance with L.5.1.6(a) through _____________________________________________________________________________________________________________________

L.5.1.6(c) 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 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 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, quality assurance, and property control systems. The Offeror shall

7 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 reference only. 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 a system of internal controls to manage (control, use, preserve, protect, repair and maintain) Government property in its possession accountable to the contract. The system of 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 control of Government property accountable to the contract, consistent with voluntary consensus standards and/or industry-leading practices and standards for Government property management except where inconsistent with law or regulation. Offerors shall provide a written plan detailing its system of internal controls to manage Government property in its possession. Offerors property management plan must address all elements under FAR 52.245-

1(f) Contractor plans and systems. This plan shall be submitted with the Offerors proposal. 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 update its property management plan specific to the place of performance sites.

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.7.3(d) Failure to provide a property management plan in accordance with L.5.1.7.3(a) through L.5.1.7.3(b) shall render the ____________________________________________________________________________________________________________________

Offerors proposal non-compliant. The proposal will not be evaluated and will not be further considered for award.___________________________________________________________________________________________________________________

L.5.1.8 Teaming Matrix (Attachment 0010): 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, basis of selection (competitive/non-competitive) and the cost proposal submittal method. The Offeror shall populate every column using the instructed fill-ins on the Attachment 0010 for itself, proposed Teammates and proposed Subcontractors.

Note: The total of Column F (Total estimated dollar value) provided on Attachment 0010 shall be equal to the ""Subtotal - Proposed

Contract Value"" found on Attachment 0005 - Cost/Price Matrix. Failure to provide these matching amounts shall render the Offerors proposal non-compliant.

- Teammate/Subcontractor Utilization: Offerors proposing the use of Teammate(s)/Subcontractor(s) shall do so in accordance with Section

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

L.5.1.8(a) Naming Convention: Offeror's_Name_Vol_1_Att0010

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

L.5.1.8(c) Page Limit: none

L.5.1.8(d) Failure to provide a fully completed Teaming Matrix - Attachment 0010 containing all of the required information (including ____________________________________________________________________________________________________________________________ populating every column), or failure to provide a Teaming Matrix - Attachment 0010 in compliance with L.5.1.8(a) through L.5.1.8(c)____________________________________________________________________________________________________________________________________ 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 Ammunition Supply Services 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 Offerors approach to ensure compliance with each of the General Safety Requirements described in Chapter 3 of the DoD Contractors 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.

8 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

However, the Offerors safety plan shall still address each of the General Safety Requirements described in Chapter 3 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 five (5) years prior to this RFP closing date 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: Offeror_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.9.1(g) Failure to provide the Pre-Award Safety Responsibility shall render the Offerors proposal non-compliant. The proposal will ___________________________________________________________________________________________________________________________ not be evaluated and will not be further considered for award.______________________________________________________________

L.5.1.10 Not Applicable

L.5.1.11 Small Business Subcontracting Plan: THIS REQUIREMENT APPLIES TO OTHER THAN SMALL BUSINESS OFFERORS ONLY AND IS IN ADDITION TO

THE SMALL BUSINESS PARTICIPATION REQUIREMENT IN PARAGRAPH L.5.5 BELOW. Other than Small Business Offerors must submit a Small Business

Subcontracting Plan as required by FAR 19.7, (FAR Clause 52.219-9). The Small Business Subcontracting Plan shall be consistent with proposed Small Business Participation.

L.5.1.11 (a) Naming Convention: Offeror's_Name_Vol_1_SB_Sub_Plan

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

L.5.1.11 (c) Page Limit: none

L.5.1.11 (d) For Other than Small Business Offerors, failure to provide a Small Business Subcontracting Plan and in compliance with _______________________________________________________________________________________________________________________

L.5.1.11 (a) through L.5.1.11 (c) 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

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

L.5.2.1.1(a)(3) Page Limit: 15 Pages

9 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 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) Failure to provide the Staffing and Management Plan and in compliance with L.5.2.1.1(a)(1) through L.5.2.1.1(a)(3)(iii) ________________________________________________________________________________________________________________________ shall render the Offeror's proposal non-compliant. The proposal will not be further evaluated and will not be further considered for______________________________________________________________________________________________________________________________________ award.______

L.5.2.1.1(b) The Offeror's Staffing and Management Plan must detail an approach to deliver services required in the RFP and PWS, 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 a realistic approach to creating its management structure from general staff oversight by first line supervisors through its company headquarters management. This approach must include adequate details of chain of command structure and methodology, internal controls for problem resolution.

L.5.2.1.1(b)(2) Staffing rationale and assumptions: Offeror's overarching methodology for determining its proposed skill set(s) / skill level(s) by Functional Area and assumptions supporting staffing decisions or explanations needed to clarify staffing decisions made in order to ensure proper execution of the effort.

L.5.2.1.1(b)(3) Flexible Staffing Approach: The Offeror's ability to effectively and efficiently: cross-utilize, temporarily reallocate, and rapidly increase and decrease its workforce. The Offeror must adequately identify how this approach will be executed during surges in effort and during periods of protracted reductions in workload without sacrificing quality of services provided.

Additionally, the Offeror must adequately demonstrate its ability to effectively and efficiently cross utilize personnel when possible to better support short term requirement changes; provide better and timelier 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)(4) Transition-in Approach: Realistic and feasible time-phased approach to transitioning-in all of the PWS requirements with key milestones from Notice to Proceed (NTP) to successfully reaching a fully operational capability (FOC) within the time allotted in the table found in L.2.8 for all services which demonstrates, at a minimum:

L.5.2.1.1(b)(4)(i) Approach to ensure open communication with incumbent contractor and the Government to include periodic meetings documenting progress.

L.5.2.1.1(b)(4)(ii) Approach to ensure compliance with Executive Order 13495 - Hiring of qualified incumbent workforce.

L.5.2.1.1(b)(4)(iii) Approach to ensure proper, timely requisition / issuance of (as required): Contractor Common Access Cards (CAC) / access badges and security clearances.

L.5.2.1.1(b)(4)(iv) Approach to assuming accountability of Government Furnished Property (GFP) / Government Furnished Equipment (GFE)

(including joint inventory with incumbent contractor) with all actions up to and including reconciliation completed prior to the end of transition-in.

L.5.2.1.1(c) Staffing/Labor Mix (Attachment 0002 - Staffing/Labor Mix): The Offerors must provide its proposed staffing/labor mix 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 proposed approach must present a staffing approach which demonstrates an understanding of this effort and provides its expected skill level, to include level of responsibility, to properly perform all of 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 TE 1G-005 Key and Specified Non-Key

Requirements positions to determine if the proposed labor category is consistent with the task(s) proposed.

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) Failure to provide the Staffing/Labor Mix Attachment 0002 in the Government provided format as of the closing date of ______________________________________________________________________________________________________________________ the RFP, and in compliance with L.5.2.1.1(c)(2) through L.5.2.1.1(c)(3)(i), or to provide the following required information: proposed________________________________________________________________________________________________________________________________________ labor category descriptions; proper identification of SCA/Exempt; FLC1/FLC2; applicable SCA code(s); proposed hours per FTE including______________________________________________________________________________________________________________________________________

10 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

total FLC1 hours by functional area; proper identification of Functional Area; and Shop or PWS Requirement shall render the Offeror's______________________________________________________________________________________________________________________________________ proposal non-compliant. The proposal will not be further 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) FTEs: Contract or task order level employees that are specifically identified to __________________________________________ directly accomplish the tasks/functions of the workload provided in Exhibit A TE 1 M-S-T-001 Functional Labor Category 1 Hours Fort

Bragg (e.g. mechanic / shop supply clerk in support of the maintenance effort). Note: Leads may be proposed as solely FLC1, if applicable. Labor classification (i.e. SCA, Exempt) in accordance with the SCA directives is at the sole discretion of the Offeror. __

L.5.2.1.1(c)(5)(iii) Functional Labor Category 2 (FLC2) FTEs: 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 Functional

Labor Category 1 Hours Fort Bragg. 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, administrative assistant). Labor classification

(i.e. SCA, Exempt) in accordance with the SCA is at the sole discretion of the Offeror. 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 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 FLCs along with proposed staffing levels in terms of Full Time

Equivalents (FTEs) on the Staffing/Labor Mix - Attachment 0002 (to include identifying key and specified non-key positions). Staffing must be based on all of the PWS requirements and the workload data (see applicable Technical Exhibits) for the identified base period and all option periods (four identical fully operational capable 12-month periods (365 day periods)). The Offeror's Attachment 0002 must identify Key and Specified Non-Key positions using "(Key)" and "(Non-Key)" following the Offeror's position description or description; see example tab in Attachment 0002. 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 work center/shop for the base period and each option period.

L.5.2.1.1(c)(6)(ii) The FTEs proposed for FLC1, when multiplied with the associated labor hours per year proposed, for the option periods ("FTE Count Option Periods 1-4" tab) shall be equal to or greater than the total minimum hours of 389,760 for Maintenance, 376,320 for Supply, and 524,160 for Transportation as provided in the attached workload data, Exhibit A TE 1 M-S-T-001 Functional Labor

Category 1 Hours Fort Bragg.

L.5.2.1.1(c)(6)(iii) The FTEs proposed for FLC2 shall not be included in the total minimum hours for Maintenance, Supply, and

Transportation provided in the attached workload data, Exhibit A TE 1 M-S-T-001 Functional Labor Category 1 Hours Fort Bragg (i.e. FLC2 portion of proposed supervisors, if applicable).

L.5.2.1.1(c)(6)(iv) The Government intends to use the MS Excel program to analyze the data provided; therefore, the Offeror is required to supply this data to the Government in the MS Excel file format (.xls or .xlsx) provided with this RFP.

L.5.2.1.1(c)(6)(v) FTE numbers are to be consistent throughout the base period and all option periods. Do not assume any change in requirements. Additionally, the Offeror shall not add or delete any tabs to the Attachment 0002 - Staffing/Labor Mix (other than the example tab). Workload data provided is for a 12-month period (365 day period). Fully Operational Capability staffing must support the provided workload data and all PWS requirements and must be demonstrated in the Offeror's Attachment 0002 - Staffing/Labor Mix. The proposed labor hours must correlate to the period being staffed (i.e., all tabs shall have the same staffing with the appropriate annual hours (by employee type) for the base period (less transition-in) and option periods). Adding or deleting tabs to Attachment 0002

(other than the example tab) shall render the Offeror's proposal non-compliant. The proposal will not be further evaluated and will not be further considered for award.

L.5.2.1.1(c)(6)(vi) Under the 'FTE Count Base Period Only' tab, the Offeror must provide the hours proposed per position per FTE within column C (Base Period Hours) on Attachment 0002 - Staffing/Labor Mix. Hours per position per FTE must be commensurate with the period of performance and the employee type (SCA, Exempt). This will be used to identify and propose hour's specific to the transition-in date as not all portions of this effort will start at the same time. See L.2.8 for more information. Under the 'FTE Count Option Periods 1 -

4', the Offeror must provide its proposed labor hours per year by employee type in the Hours Per Year column for Exempt and SCA in the

Offeror's Attachment 0002 - Staffing/Labor Mix.

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

11 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.2.1.1(c)(6)(viii) Additionally, the Offeror must insert the SCA or Exempt labor code in the SCA/Exempt column for all proposed labor categories. The following is provided for example purposes only:

FLC1 = Direct Support of TE 1 M-S-T-001 Functional Labor Category 1 Hours Fort Bragg

SCA 01011 = SCA Labor Code

Accounting Clerk I = SCA Labor Category Description

L.5.2.1.1(c)(6)(ix) The Offeror must insert the proposed labor category description and it must match the labor category description found in the SCA 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 event the labor code and labor category description do not match, the SCA labor code will take precedence over the labor category description. Additionally, the Offeror may insert the "Offeror Position Title" in order to better identify the functional nature of the position.

L.5.2.1.1(c)(6)(x) The Offeror must insert the applicable functional area (i.e. PMO, 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 Functional Labor Category 1 Hours Fort Bragg. The Offeror may add or delete columns as needed within the limitations provided in accordance with L.5.2.1.1(c)(3)(i).

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

The shop or PWS requirement provided must correspond to the workload data and/or PWS requirements provided in the RFP; the Offeror may add/delete columns as needed within the limitations provided in accordance with L.5.2.1.1(c)(3)(i).

L.5.2.1.1(c)(6)(xii) The Offeror must insert number of FTEs (or less than full time equivalents expressed as FTEs)…