W52P1J16R0082-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 2016AUG25

W52P1J

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

BLDGS 60 & 62

WESLEY N. BASKOVIC

EMAIL: WESLEY.N.BASKOVIC.CIV@MAIL.MIL

W52P1J-16-R-0082

2016AUG11

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 21

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: WESLEY N. BASKOVIC

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

Type of Contract 1: Cost Plus Fixed Fee

Type of Contract 2: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

1. The purpose of Amendment 0001 to Request for Proposal (RFP) # W52P1J-16-R-0082 is to incorporate the following:

a. Updated Attachment 0002 - Staffing Labor Mix (see Section J for details).

b. Moved Section H paragraphs to Section C (see Section C for details).

c. Revised Section L, paragraph L.5.1.8(b) to reflect Section C paragraphs.

2. The proposal response date remains due at 4:30PM CT on 12 September 2016.

3. All other terms and conditions remain unchanged.

*** END OF NARRATIVE A0004 ***

2 21

W52P1J-16-R-0082 0001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 EAGLE BUSINESS RULES - STEP THREE TASK ORDER REQUEST

(a) An Offeror must be a qualified BOA holder by the closing date of the Request for Proposal (RFP). The Government is under no obligation to place an order against an EAGLE BOA.

(b) A Task Order becomes a binding contract at the time of the Government's acceptance of a task order proposal and award of a Task

Order per FAR 16.703(c)(1)(iv).

(c) This Task Order is being competed among EAGLE BOA holders who hold a BOA at the time of the closing date of the RFP. No extensions to the RFP will occur for purposes of allowing interested Offerors additional time to become an EAGLE BOA holder.

(d) BOA holders were required to demonstrate the capability to perform all three functional areas in Step Two. That capability may have been achieved with or without Teammates. The Offeror shall propose itself and/or approved Teammates listed in the Offeror's current BOA

Attachment 0002 - Team Arrangement when submitting a proposal in Step Three. The Government will verify that the Offeror's proposal includes approved Teammates by comparing the Offeror's proposal to its BOA Attachment 0002 - Team Arrangement as of the closing date of the Step 3 Task Order RFP. Offerors may propose Subcontractors in addition to what is listed in their BOA Attachment 0002 - Team

Arrangement if that Subcontractor is being proposed for the purpose of meeting the Offeror's Small Business Participation Proposal in accordance with Sections L and M of the Step 3 Task Order RFP.

In Task Order Execution, the awardee shall utilize itself and/or approved Teammates listed in the Offeror's current BOA Attachment 0002 -

Team Arrangement. If the awardee has a proposed task order change, the Government will verify that the awardee's proposed task order change, includes approved Teammates by comparing the awardee's proposal to its BOA Attachment 0002 - Team Arrangement as of the submission date of the task order change proposal. Awardees may propose Subcontractors in addition to what is listed in their BOA

Attachment 0002 - Team Arrangement if that Subcontractor is being proposed for the purpose of meeting the subcontracting goals during

Task Order Execution. Deviations from an Offerors current BOA Attachment 0002 Team Arrangement will only be permitted for specialized, irregular or intermittent requirements and will require approval by the PCO.

(e) If BOA holders demonstrated organizational capability in all three functional areas without the reliance of Teammates in Step Two, then the Offeror is not precluded from proposing Subcontractors in all three functional areas for Step 3 Task Order RFPs and in Task

Order Execution. BOA holders who demonstrated organizational capability in one or two of the functional areas without the reliance of

Teammates in Step Two may propose Subcontractors for those respective functional area(s) in Step Three Task Order RFPs and in Task Order

Execution.

For example, if a BOA holder demonstrated organizational capability in Maintenance without the reliance of Teammates in Step Two, then in Step 3 Task Order RFPs and in Task Order Execution, the Offeror may propose/utilize Subcontractor(s) in Maintenance but shall only propose/utilize itself and/or approved Teammates listed in the Offeror's BOA Attachment 0002 - Team Arrangement for Supply and

Transportation.

(f) The contractor shall adhere to the prices proposed and agreed to in this resultant task order issued against their BOA. The contractor is not authorized to begin work on an order issued against the BOA until prices have been established. In the event that the

Contracting Officer requires work to begin prior to establishment of pricing, failure to reach agreement on price may be disputed under the Disputes clause.

(g) Offerors will certify size standards at the Task Order level.

(h) Failure to comply with any term of the Task Order may result in negative past performance that could negatively impact the BOA holder's ability to be successful in future Task Order competitions.

(i) Responsibility determinations will be made at Step Three. An otherwise successful Offeror may not be eligible for award if it cannot be determined responsible for any of the reasons in FAR 9.104, including capacity.

C.2 CONTRACTOR PERFORMANCE MANAGEMENT REVIEW

(a) All tasks under this contract will be subject to periodic (not less than quarterly) performance management reviews (PMR). The performance reviews will be written in the form of a Contractor Performance Assessment Report (CPAR) in accordance with the DoD

Contractor Performance Assessment Reporting System (CPARS). The PMR can be either positive, outlining best practices or cost savings, or negative in the event the contractor fails to perform as outlined in the PWS, applicable regulations, or PCO direction. PMRs will be provided to the contractor not less than quarterly or as deemed necessary by the COR, Government Program Manager or PCO. The Contractor will receive briefings on the PMR reports and be allowed the opportunity to submit a response. Contract Deficiency Reports (CDRs) and/or

Corrective Action Request (CARs) will be reviewed during the PMR, if the Government deems them material. The contractor will present its independent assessment of performance during the PMR. Contractor's presentation will consist of work accomplished, evaluation of work against applicable program metrics (to include schedule), cost savings, lessons learned, forecasted staffing requirements based on anticipated workload, self-evaluations/inspection results, corrective actions, funding levels/contractor performance report (financial), contractor-employee utilization rates and must address all CARs, CDRs or other notices issued by the PCO.

3 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(b) Contractor Performance Assessment: Currently, the Government uses an escalating system of deficiency reporting: local (on-site) and

PCO issued contract discrepancy report (CDR; DA Form 5479). Local deficiency reporting consists of: verbal notification and corrective action requests (CAR). Verbal notification is primarily used for non-repeating, minor nonconformance/discrepancies of tasks that can be re-performed at no additional cost to the government and with minimal impact to the effort. A CAR will be issued by COR/COTR/QAE when previous verbal notifications failed to result in corrective actions or when more/major non-conformance or significant deficiencies exist/occur. The CAR will be issued to the contractor by the COR and forwarded to the PCO through the government program management office/COR for tracking/action. Un-resolved CARs or significant deficiencies will result in the PCO issuing a formal Contractor

Discrepancy Report (CDR). CDRs are provided to the contractor's corporate office(s) for action with an assigned suspense date. CDRs are a significant indicator of performance and will be used to substantiate the Government's Contractor Performance Assessment Reporting

System (CPARS) input. Performance deficiencies may include any government-identified noncompliance with contract requirements; an activity or action did not take place, or did not take place to the standards of timeliness or quality required. Note, that while the contractor will be given the opportunity for re-performance when possible, significant deficiencies will nevertheless be documented. Use of this escalating deficiency reporting procedure does not, in any way, limit the Government's ability to take corrective action up to and including termination.

(c) Contractor's Fixed Fee will be assessed for validated negative PMRs, unresolved CDRs or as determined by the PCO IAW FAR 52.246-5 using the following schedule:

Critical Nonconformance - Contractor's fee will be assessed not less than 10% (ten percent) of the monthly fixed fee in which the critical nonconformance occurred. PCO determination will address the exact fee decrement based on severity, impact to the effort, contractor willingness to resolve and any other factors as deemed relevant by the PCO.

Unresolved CDRs - Contractor's fee will be assessed not less than 5% (five percent) of the daily fixed fee starting with first day of delinquency in resolution. Fee reduction percentages are assigned as follows; however, the PCO has the discretion to apply whatever percentage it deems reasonable based on severity, impact to the effort, contractor willingness to resolve and any other factors as deemed relevant by the PCO:

Percentage of Fee:

Critical: 10% and above (monthly)

Major: 7-10% (daily)

Minor: 5-7% (daily)

The Contractor will be given the opportunity to comment and respond to issued CARs and/or CDRs during the PMR prior to the Government executing a fee decrement.

Definitions:

Critical nonconformance - a nonconformance that is likely to result in hazardous or unsafe conditions for individuals using, maintaining, or depending upon the supplies or services; or is likely to prevent performance of a vital agency mission. Repeated or unresolved major nonconformance will result in re-designation as critical nonconformance.

Major nonconformance - a nonconformance, other than critical, that is likely to result in failure of the supplies or services, or to materially reduce the usability of the supplies or services for their intended purpose. Repeated or unresolved minor nonconformance will result in re-designation as major nonconformance.

Minor nonconformance - a nonconformance that is not likely to materially reduce the usability of the supplies or services for their intended purpose, or is a departure from established standards having little bearing on the effective use or operation of the supplies or services.

Unresolved CDR- a CDR remaining unresolved, or unacknowledged, past the PCO established suspense date. May be re-designated as minor, major or critical based on the PCO independent determination.

Daily Fee - The yearly fixed fee amount divided by 12 months divided by 30 days.

C.3 PURCHASING AND INVOICING PROCEDURES

(a) The Government and Contractor shall utilize the procedures outlined in the Purchasing and Invoicing Guide (Attachment 0009). This guide details the process that the United States Government (USG) will use to conduct and oversee contractor purchasing and invoicing on this task order. Each step in the process will be described in detail along with the responsibilities of each individual position. It is the intent of the Government that the process will be sufficient for detailed cost accounting and approval without negatively impacting the contractor's ability to provide Maintenance, Supply, and Transportation services at U.S. Army Fort Wainwright, Fort Greely, and

Joint Base Elmendorf Richardson (JBER). If the process is found to negatively impact operations it will be re-evaluated by the USG and updated appropriately to achieve the desired effect.

4 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(b) Final invoice for the Transition-In CLIN shall be submitted no later than 7 days after the end of CLIN 0001's period of performance.

C.4 GOVERNMENT PROPERTY

In the event that Government property accountable to this contract is lost, damaged, destroyed or stolen, the Contractor shall promptly perform an investigation and provide a report to the Contracting Officer or the Contracting Officers representative IAW FAR 52.245-

1(f)(1)(vi) and DFARS 252.245-7002 Reporting Loss of Government Property. The Contracting Officer shall review the Contractor's report and, if the Contracting Officer deems necessary, may perform an additional independent investigation in accordance with FAR 52.245-1

(g). In accordance with FAR 52.245-1 (g) (3) should it be determined by the Government that the Contractors (or subcontractors) property management practices are inadequate or not acceptable for the effective management and control of Government property under this contract, or present an undue risk to the Government, the Contractor shall prepare a corrective action plan and take all necessary corrective actions as specified by the schedule within the corrective action plan. The Contracting Officer may, in writing, revoke the

Governments assumption of risk for loss, theft, damage or destruction, due to a determination under FAR 52.245-1 (g) that the

Contractors property management practices are inadequate, and/or present an undue risk to the Government, and the Contractor failed to take timely corrective action. If the Contracting Officer revokes the Government's assumption of liability and holds the Contractor liable, the Contractor may not charge the Government for the loss, theft, damage or destruction of Government property or any costs associated thereof except as provided in accordance with FAR 52.245-1 (h) (1) (iii). The Contracting Officer may delegate the investigation to an appropriate Government representative of the Contracting Officer's choosing.

C.5 CAPPED INDIRECT RATES:

If the Offeror and/or Teammate(s)/Subcontractor(s) proposals include indirect expense rate(s) which were determined by the Government to be not fully supported, those rates will be capped at the proposed rates for evaluation purposes and contract execution.

The following rate(s) is/are hereby capped from the Offeror's and/or Teammate(s)/Subcontractor(s) Cost/Price proposal dated DD MONTH

YYYY for the life of this task order:

Offeror's: TBD

Capped Rate(s): (Insert applicable capped rate(s) at XX%, i.e., Overhead, G&A, Business Unit Overhead)

Teammate/Subcontractors(s) Name(s): TBD

Capped Rate(s): (Insert applicable capped rates(s), are capped as provided in proposal dated DD MONTH YYYY.

C.6 AbilityOne Program Contracts

(a) Notwithstanding the inclusion of FAR 52.216-21 in this this task order, any maintenance, supply, and transportation tasks currently being performed by an AbilityOne contractor at U.S. Army Fort Wainwright, Fort Greely, and Joint Base Elmendorf Richardson (JBER), or subsequently determined appropriate for performance by an AbilityOne contractor, are not included within the scope of this EAGLE requirements task order.

C.7 POST - AWARD CONFERENCE:

The Contractor agrees to attend any post-award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation subpart 42.5.

*** END OF NARRATIVE C0001 ***

5 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION J - LIST OF ATTACHMENTS

List of Number List of Number

Addenda Title Date of Pages Transmitted By Addenda Title Date of Pages Transmitted By________________ ____________________________________________________________ _______________ ____________ _______________________________ ____________________________________________________________ _______________ ____________ _______________

Attachment 0002 STAFFING LABOR MIX 24-AUG-2016 002

6 21

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

7 21

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

Service Anticipated NTP Days in Transition Anticipated FOC

LSS 2/1/2017 60 4/2/2017

ICEMP 1/31/2018 - 2/1/2018

HAZMAT 1/31/2018 - 2/1/2018

DFAC Maint 4/30/2017 - 5/1/2017

The above table identifies the anticipated Notice to Proceed dates for each of the contracts that are transitioning to the Alaska 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 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.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 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

8 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

considered for this 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 be not 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) 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

9 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.5.1.6 SECRET Facility Clearance: NOT APPLICABLE

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

10 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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 12 September 2011 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:

11 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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: 11 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 Attachment 0008 - Collective Bargaining Agreement (CBA), Service Contract Act (SCA) Directory of Occupations (5th Edition) and Exhibit E 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 CBA, SCA Directory of Occupations (5th Edition) or Exhibit E TE 1-G-

005 Key & Specified Non-Key Positions. The Offeror shall utilize the CBA, SCA Directory of Occupations (5th Edition) or Exhibit E TE 1-

G-005 Key & Specified Non-Key Positions when possible. The SMP MUST BE SUPPORTED BY THE OFFEROR'S ATTACHMENT 0002 STAFFING/LABOR MIX, and at a minimum, must address the following elements:

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

L.5.2.1.1(b)(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.

12 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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. NOTE: For Technical evaluation purposes only, the Government will utilize the Attachment 0008 Collective Bargaining

Agreement (CBA), Service Contract Act (SCA) Directory of Occupations (5th Edition) labor category definitions and Exhibit E TE1-G-005

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

005 Key & Specified Non-Key Positions must be defined by the Offeror in its SMP (see L.5.2.1.1(b)). A cross-walk between the CBA and the SCA is provided in Attachment 0017.

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