W52P1J-19-R-0101 Amendment 0007.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

0007 2019NOV19

W52P1J

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

BLDGS 60 & 62

MATTHEW WARD

EMAIL: MATTHEW.A.WARD58.CIV@MAIL.MIL

W52P1J-19-R-0101

2019SEP11

X

X 2019NOV26 03:00pm

/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: MATTHEW WARD

Buyer Office Symbol/Telephone Number: CCRI-VG/(309)782-3752

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 this amendment is to do the following.

1) Due to issues with the FBO.gov conversions to SAM.gov, the Government will NOT utilize FedBizOps for proposal submissions. Offerors shall submit its proposal under this solicitation via email submission.

a) The offeror shall submit its proposal to BOTH of the following email addresses:

tracey.l.pickett.civ@mail.mil matthew.a.ward58.civ@mail.mil

b) Please be aware you may need to split your proposal into multiple emails to ensure the size of each email is below 10MB. Email submissions greater than 10MB may not be processed by the Governments email server.

c) Offerors shall send a seperate email requesting Government receipt of its proposal.

d) Additional submission instructions have been updated under Section L.3 of the Section L Narrative.

2) To provide clarification to Section L.5.1.2. In accordance with L.5.1.2, Offerors must acknowledge receipt of all amendments.

Because there are only four (4) slots for amendments in Section 14 of the RFP coversheet, Offerros may either submit multiple signed copies of the cover sheet to account for every amendment. OR - Offerors may sign and submit amendment coversheets for each issued amendment.

3) The proposal submission deadline date is hereby extended to 26 November 2019 by 3:00pm Central Time.

4) All other terms and conditions remain unchanged.

*** END OF NARRATIVE A0008 ***

2 21

W52P1J-19-R-0101

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 and PMO CLINs only) Requirements contract with some non-fee bearing cost elements

(e.g., Other Direct Costs) which are ancillary to the services provided.

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

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

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

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

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

L.1.7 Updates related to this Task Order RFP, to include the RFP, amendments, notices, and other information, will be made available on the FBO.gov/beta.SAM.gov website. Offerors are advised to continuously monitor the FBO.gov/beta.SAM.gov website for new information.

Offerors are deemed to have knowledge of all information that is posted to the FBO.gov/beta.SAM.gov website.

L.2 PROPOSAL PREPARATION:

L.2.1 The proposal must be prepared in a clear and legible manner. In addition, the Offeror shall write the proposal in English and the proposal must be specific and complete as described in these instructions. Offerors shall not specifically prepare samples or descriptive literature for submission with the proposal. Adherence to the prescribed format is required. Failure to provide proposals in ________________________________ compliance with the instructions specified as COMPLIANCE REQUIREMENTS in Section L of this RFP and in compliance with ALL instructions_______________________________________________________________________________________________________________________________________ in Section M.3 of this RFP shall render the Offeror's proposal non-compliant. The proposal will not be evaluated and will not be further_________________________________________________________________________________________________________________________________________ considered for award._____________________

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

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

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 Microsoft (MS) Word files and MS Excel files must be compatible with Microsoft Office 2013.

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

L.2.6 Adobe PDF (Portable Document Format) Files. Scanned PDF documents must be legible and must be viewable in Adobe Acrobat.

L.2.6.1 Text Searchable Adobe PDFs: File formats that are identified as Text Searchable Adobe PDF must be formatted to contain searchable text. All elements of the file must be able to be searched for text. The Government will not accept scanned or image-only PDF files in lieu of this requirement and will not invoke the text recognition feature within Adobe Acrobat.

3 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.2.7 Compressed files (e.g. *.zip) and Executable files (e.g. *bat, *.exe,*.jar, *.vb, *.wsf) will NOT be accepted. Refer to Attachment

0010 - Blocked File Extensions for a complete list of non-acceptable file types.

L.2.8 For the purposes of proposal preparation and evaluation only, the Offeror shall use 01 March 2020 as the Notice to Proceed (NTP) date. Proposal information shall reflect that NTP date.

L.3 PROPOSAL SUBMITTAL INSTRUCTIONS:

L.3.1 Offerors shall submit its proposal via email submission.

L.3.2 Offerors shall submit its proposal to BOTH of the following email addresses:

tracey.l.pickett.civ@mail.mil matthew.a.ward58.civ@mail.mil

L.3.3 Offerors should be aware that proposal submissions my need to be split into multiple emails to ensure the size of each email is below 10MB. Email submissions greaters than 10MB may not be processed by the Government's email server.

L.3.4 Offerors shall send a seperate email to both email addresses requesting the Government confirmation of proposal receipt.

L.3.5 Proposal revisions are possible and permitted via email submission until the solicitation response deadline. Offerors shall send a seperate email to both email addresses requesting the Government confirmation of proposal receipt.

L.3.6 Do not assume submission via email will be instantaneous. File size, number of files, and number of emails to be sent will be factors to consider. Offeror/ Subcontractors should allow adequate time for email submission completion because the entire proposal

(i.e. Offerors submission and all Subcontractor(s) submissions) must be received by the due date and time for the proposal to be considered.

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

FAR 15.207(c).

L.3.8 Submission Instructions for Subcontractor Cost proposal can be found in L.5.4.2.10.

L.4 PROPOSAL STRUCTURE:

L.4.1 The Offeror must submit a proposal IAW the guidelines below.

L.4.1.1 For all documents, each page shall include the complete Offeror's name, volume number, file name, date, and solicitation number in a header and/or footer.

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

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

L.4.1.2(a) Each Offeror shall submit the most current versions of Attachments 0002, 0003, and 0005 required for this RFP. The Government will verify that the Offerors submission contains the most current RFP Attachments 0002, 0003 and 0005 that were provided via email.

L.4.1.2(b) COMPLIANCE REQUIREMENT: Failure to provide the most current versions of the RFP Attachments 0002, 0003, or 0005 shall render _____________________________________________________________________________________________________________________________ the Offeror's proposal non-compliant and will not be further considered for award.__________________________________________________________________________________

L.4.1.3 A proposal is presumed to represent the Offeror's best efforts to respond to the RFP. The Offeror must provide adequately detailed information that complies with the solicitation requirements, allows for meaningful review by the Government evaluators, and affirmatively demonstrates the merits of its proposal. The Offeror shall provide sufficient detail to substantiate the validity of all stated assertions and must not merely repeat the RFP requirements, but rather must provide convincing documentary evidence of how contract requirements will be met. Data not submitted with the proposal, but submitted previously, or presumed to be known (i.e., previous projects performed for the United States Government (USG)) will not be considered. Clarity and completeness are essential. It is the Offeror's obligation to submit an unambiguous proposal that clearly reflects the Offeror's intended technical approach and establishes cost credibility. Any inconsistency, whether real or apparent, between promised performance and proposed cost must be adequately explained in the proposal. For example, if the use of new and innovative techniques is intended, the impact on cost must be explained. As another example, if a business policy decision to absorb a portion of the estimated cost was made, that approach must be stated within the proposal (including any associated calculations). Failure to adequately explain an inconsistency between promised performance and cost may result in a finding of Technical Unacceptability or a finding that a proposed cost is unrealistic for work to be performed.

4 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

L.5 INFORMATION TO BE SUBMITTED:

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

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

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

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

L.5.1.1 c) Page Limit: None

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

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

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

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

L.5.1.2(c) Page Limit: None

L.5.1.3 Section I clauses that require Offeror completion.

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

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

L.5.1.3(c) Page Limit: None

L.5.1.4 Section K clauses that require Offeror certification.

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

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

L.5.1.4(c) Page Limit: None

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

However, any exchanges to include clarifications between the Government and the Offeror will be conducted through the use of e-mail.

Therefore, the Offeror is required to provide at least two (2) company individuals whose responsibilities will include reading and responding to Evaluation Notices (ENs) through e-mail. For example, the Offeror's Contract Manager, as an agent of the company might be the main agent responsible, but a second agent shall be available in case of the main agent's unavailability. The agents' names, company titles, telephone numbers, facsimile numbers, and e-mail addresses should be provided, and it is the Offeror's responsibility to keep the information updated throughout the competition; submission of updated POC information will not constitute a proposal revision. A

Title Page is allowable to provide for the restriction or disclosure and use of data as specified in FAR Clause 52.215-1.

L.5.1.5(a) Naming Convention: Offeror's_Name_Vol_1_POCs

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

L.5.1.5(c) Page Limit: None

L.5.1.6 Business Systems Information:

L.5.1.6.1 The Contracting Officer will review the Offeror's accounting system status for determining contractor responsibility IAW FAR

16.301-3; a cost-reimbursement type contract may be used only when the contractor's accounting system is adequate for determining costs applicable to the contract. An adequate system is a system that can separately accumulate costs under a Government contract and has the

5 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

ability to generate the specific cost information required under the anticipated contract. An SF 1408 has been attached to this RFP

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

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

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

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

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

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

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

L.5.1.6.1(c) Page Limit: None

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

L.5.1.6.2(a) Naming Convention: Offeror's_Name_Vol_1_BusSys

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

L.5.1.6.2(c) Page Limit: None

L.5.1.7 Teaming Matrix (Attachment 0005, Tab 2): The Offeror shall provide the full company name, CAGE code, role of participant, functional area(s) to be performed, proposed labor/fee for each participant for the entire period of performance (excluding ODC's and the option to extend), percent of participation, cost proposal submittal method, indicate whether the participant requires a SECRET

Facility Clearance, and indicate which participants will perform in the ASP. The Offeror shall populate every column using the instructed fill-ins on the Attachment 0005, Tab 2 for itself, and proposed Subcontractors.

L.5.1.7(a) COMPLIANCE REQUIREMENT: The amount in the total of Column F (Total estimated dollar value) provided on Attachment 0005, Tab 2 ______________________________________________________________________________________________________________________________ shall match the amount of 'Subtotal - Proposed Labor/Fee" found on Attachment 0005, Tab 1a, Cell I21'. Failure to make these two amounts_________________________________________________________________________________________________________________________________________ match shall render the Offeror's proposal non-compliant. The proposal will not be evaluated and will not be further considered for___________________________________________________________________________________________________________________________________ award.______

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

L.5.1.7(c) File Format: MS Excel

L.5.1.7(d) Page Limit: None

L.5.1.7(e) COMPLIANCE REQUIREMENT: If an Offeror is proposing subcontractors, failure of the Offeror to populate all blue highlighted ___________________________________________________________________________________________________________________________ cells for itself and each of its proposed Subcontractor(s) on the Teaming Matrix (Attachment 0005, Tab 2) will render the Offeror's____________________________________________________________________________________________________________________________________ proposal non-compliant. The proposal will not be evaluated and will not be further considered for award.________________________________________________________________________________________________________

L.5.1.7(f) The compliance requirements of L.5.1.7 (a) and (e) do not apply to an Offeror performing 100% of the requirement by itself with no subcontractors.

L.5.1.8 SECRET Facility Clearance: Offerors must possess a SECRET Facility Clearance by the RFP closing date, at the time of award, and throughout the life of the contract. Any and all Subcontractors who will be performing contract requirements which necessitate facility clearance must also have a SECRET Facility Clearance by RFP closing date, at the time of award, and throughout the life of the contract.

In order for an Offeror/Subcontractor to request and sponsor an individual employee's SECRET Security Clearance to perform the functions identified in the PWS, the Offeror/ Subcontractor must possess a SECRET Facility Clearance by the RFP closing date. Possession of an

INTERIM SECRET Facility Clearance will be sufficient to meet the requirement at time of proposal submission provided that it can be validated by the Defense Security Service (DSS); however, please note that access to classified COMSEC information requires a FINAL US

6 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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

Security Clearances, the Offeror (i.e. the legal entity that is submitting the proposal and would be identified as the awardee of the contract) must possess a SECRET Facility Clearance itself and cannot rely solely on the clearance of a Subcontractor or other legal entity. Possession of a SECRET Facility Clearance will be determined by CAGE code. For a proposal submitted by a Joint Venture, the

SECRET Facility Clearance must be granted under the name and CAGE code of the Joint Venture itself to meet this solicitation requirement; even if the managing partner of the Joint Venture has a SECRET Facility Clearance, or if all members of the Joint Venture have a SECRET Facility Clearance, the proposal will not be eligible for award unless the Joint Venture possesses the clearance under its own name and CAGE code.

L.5.1.8(a) The Offeror shall complete Column I on Tab 2 of Attachment 0005 (Teaming Matrix) for any and all listed entities (i.e.

Offeror and Subcontractors, Subsidiaries, or other affiliates) that require a SECRET Facility Clearance for their proposed performance of requirements IAW the PWS. The Contracting Officer will verify that all entities designated as YES possess a SECRET Facility

Clearance; the verification will be conducted through a CAGE code search performed on the Defense Security Services (DSS) Industrial

Security Facilities Database (ISFD).

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.22 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 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 within three years of the closing date of this RFP. 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:

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

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

L.5.1.9.1(c)(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 Mission Essential Contractor Services (MECS)

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

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

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

L.5.1.10.1(c) Page Limit: 2 pages

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

7 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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

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

L.5.1.11 NOT APPLICABLE

L.5.2 Technical Factor:

L.5.2.1 The Offeror shall demonstrate mission capability by detailing its proposed technical approach to meet the requirements specified in the PWS and this RFP by providing its Staffing and Management Plan (SMP).

L.5.2.1.1 Staffing and Management Plan (SMP):

L.5.2.1.1(a) The Offeror's SMP proposal must adhere to the following:

L.5.2.1.1(a)(1) Naming Convention: Offeror's_Name_Vol_2_SMP

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

L.5.2.1.1(a)(3) Page Limit: Nine (9) Pages

L.5.2.1.1(a)(3)(i) Page limit excludes cover page, table of contents, and glossary of abbreviations and acronyms.

L.5.2.1.1(a)(3)(ii) Pages larger than 8.5 inches x 11 inches will be counted as two pages.

L.5.2.1.1(a)(3)(iii) The font size must be no less than 10 point font for all documents, to include charts, tables, and diagrams.

L.5.2.1.1(a)(4) COMPLIANCE REQUIREMENT: Failure to provide the Staffing and Management Plan and in compliance with L.5.2.1.1(a)(3) ___________________________________________________________________________________________________________________ through L.5.2.1.1(a)(3)(ii) will render the Offeror's proposal non-compliant. The proposal will not be evaluated and will not be further_________________________________________________________________________________________________________________________________________ considered for award._____________________

L.5.2.1.1(b) The Offeror's Staffing and Management Plan must detail the Offerors approach to 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 will utilize the Attachment 0008 Collective Bargaining Agreement (CBA), Service Contract Act (SCA) Directory of Occupations (5th

Edition) and Exhibit A TD-06 Key & Specified Non-Key Positions for technical evaluation purposes, the Offeror shall utilize those sources whenever possible to determine which labor categories/position titles to propose as part of its proposed staffing.

For all positions identified as "Non-Exempt" on the Offerors Attachment 0002 Staffing/Labor Mix, the Offeror shall provide a labor category/title under the column "Position Title" that is specifically found within the CBA, SCA Directory of Occupations (5th Edition), or Exhibit A TD-06 Key & Specified Non-Key Positions. If additional explanation is necessary beyond the definitions provided in the CBA, SCA Directory, or Exhibit E to describe the proposed skillset or capabilities of that labor category based on the Offerors unique business practices or staffing approach, then the SMP narrative must include an adequate duty description for that position which will enable the Government to evaluate the skill set / skill level that is being proposed (this requirement is in addition to any supplemental description the offeror can include under the "Duty Title" column on its Attachment 0002).

For positions identified as "Exempt" on Attachment 0002, if the Offeror is providing a labor category/title under the column Position

Title that is not specifically found within Exhibit A TD-06 (Key & Specified Non-Key Positions) or that is a pre-populated labor category, then the SMP narrative must include an adequate duty description for that position which will enable the Government to evaluate the skill set / skill level that is being proposed (this requirement is in addition to any supplemental description the offeror can include under the "Duty Title" column on its Attachment 0002).

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

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

L.5.2.1.1(b)(1)(i) The Offeror's proposal must include a firm-fixed-price (FFP) portion of the effort that provides the required on-site staff for its Program Management Office (PMO) for this Task Order. The pre-populated, FFP PMO positions are determined to be material to

8 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

the effort and must remain staffed throughout the duration of the contract. The required labor categories are identified as firm fixed price in Exhibit A TD-06 Key & Specified Non-Key Positions and are pre-populated in the Attachment 0002. Offeror must propose any additional PMO staffing, if required by the Offeror's business processes to fully support the effort solicited within this RFP.

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

0002.

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

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

L.5.2.1.1(b)(2)(i) Identification of the tasks to be performed by the Offeror and all proposed subcontractor(s) (if applicable) as identified on the Offeror's Teaming Matrix (Attachment 0005, Tab 2).

L.5.2.1.1(b)(2)(ii) Identification of the command and control relationship among the Offeror, all proposed subcontractor(s) as identified on the Offeror's Teaming Matrix (Attachment 0005, Tab 2). The command and control relationship must include identification of leadership positions (e.g., team leads, foremen, supervisors, deputies, managers) responsible for performing successful oversight of each of the primary task areas identified in Section C-5 of the PWS. FTE Counts are not required on the Organizational Diagram. Proposed

FTEs counts will only be evaluated on the Attachment 0002 and will not be evaluated as part of the Organizational Diagram.

L.5.2.1.1(b)(2)(iii) RESERVED

L.5.2.1.1(c) Staffing and Labor Mix (Attachment 0002): The Offeror must provide its proposed staffing mix/labor categories (skill sets / skill level, Functional Labor Category 1 (FLC1), Functional Labor Category 2 (FLC2), number of employees) in relation to the PWS requirements and the provided workload data (see applicable Technical Exhibits) for both the base period and option periods (fully operational capable 12-month periods (365 day periods)). The Offeror's proposal must present a staffing approach which demonstrates a thorough understanding of the effort and provides the expected skill sets / skill level of each position, to include level of responsibility in order to successfully perform all the PWS requirements.

Exhibit A TD-01 Workload does not list every single detail/task required in PWS Section 5. TD-01 Workload provides the Minimum

Functional Labor Category 1 hours required to perform all PWS Section 5 paragraphs. During contract execution, the preponderance of

FLC1 hours proposed will support the respective task/descriptions associated with the identified PWS paragraph numbers identified in TD-

01 Workload. During contract execution, it is expected offerors will cross utilize labor categories to support ancillary tasks required by the PWS (e.g. locksmith tasks). Exhibit A TD-01 Workload DOES NOT take into account FLC1 or FLC2 hours required to perform all the

PWS (e.g. Sections, 1, 2, 3, 4, 6) or to meet all the contract terms and conditions.

NOTE: For Technical evaluation purposes only, the Government will utilize the Attachment 0008 Collective Bargaining Agreement (CBA), the Service Contract Act (SCA) Directory of Occupations (5th Edition) labor category definitions and Exhibit A TD-06 Key & Specified Non-

Key Positions to determine if the proposed labor category has the skill set / skill level necessary to perform the required task(s) as identified in L.5.2.1.1(b).

A cross-walk between the CBA and SCA is provided in Attachment 0016.

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

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

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

L.5.2.1.1(c)(3)(i) The Offeror shall not add or remove any tabs (other than the example tab) to the Attachment 0002 Staffing/Labor Mix.

L.5.2.1.1(c)(4) COMPLIANCE REQUIREMENT: Failure to provide the Staffing/Labor Mix Attachment 0002 in the Government provided format, in ________________________________________________________________________________________________________________________ compliance with L.5.2.1.1(c)(3) and L.5.2.1.1(c)(3)(i), and to provide the following required information, shall render the Offeror's______________________________________________________________________________________________________________________________________ proposal non-compliant, and the proposal will not be evaluated and will not be further considered for award: proposed hours per FTE for________________________________________________________________________________________________________________________________________ both the base period and option periods 1-4; FLC1/FLC2; identification of CBA/SCA/Exempt; SCA Code; Offeror Position Title; and________________________________________________________________________________________________________________________________ identification of Functional Area.__________________________________

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

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

Equivalent. If an employee works less than the total compensable hours for one year, that is considered a fractional FTE. Fractional

FTEs are determined by dividing the hours scheduled for that employee by the total available compensable hours.

L.5.2.1.1(c)(5)(ii) Functional Labor Category 1 (FLC1): Contract or task order level positions that are specifically identified to

9 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

directly accomplish the tasks/functions of the workload provided in Exhibit A TD-01 Workload (e.g. mechanic / shop supply clerk in support of the maintenance effort). Note: Leads may be proposed as solely FLC1, if applicable.

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

NOTE: FLC2 positions also include the Program Management Office (PMO) positions which are identified at Exhibit A TD-06 Key & Specified

Non-Key Positions.

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

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

The following instructions pertain to the Staffing/Labor Mix - Attachment 0002:

L.5.2.1.1(c)(6)(i) The Offeror must identify all of its proposed staffing required to support all PWS requirements on the FHAZ

Attachments Portfolio Staffing and Labor Mix attachment. The Government required "Key" Position labor categories and associated FTEs are prepopulated as identified at Exhibit A TD-06 Key & Specified Non-Key Positions. The Offeror's Attachment 0002 must identify the required Specified Non-Key positions using "(Non-Key)" following the Offeror Position Title; see example tab in Attachment 0002.

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

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

FTE (e.g. supervisor) is applicable to an FLC1 labor category and a portion of the same FTE is also applicable to an FLC2 labor category. These positions must be listed on the Attachment 0002 - Staffing/Labor Mix in all applicable locations (e.g. part time worker

(.20 FLC1) and part time supervisor (.80 FLC2)) with the appropriate percentage of hours applicable to each labor category expressed as a decimal (not to exceed two decimal places to the right of the whole number). Additionally, supervisors must, by definition, have a portion of their proposed time proposed FLC2. (See "Example Tab" contained in Attachment 0002 - Staffing/Labor Mix.). As noted in

L.5.2.1.1(c)(5)(iii), supervisors can only be cross-utilized if the CBA does not preclude it.

L.5.2.1.1(c)(6)(iv) The Offeror must provide its proposed annual labor hours by employee type in the Hours Per Year column (in both the

Base Period and Option Periods 1 - 4) for Exempt, CBA and SCA.

L.5.2.1.1(c)(6)(v) Proposed FLC1 FTEs, when multiplied by the associated annual hours per year by employee type proposed for the option periods, shall be equal to or greater than the total minimum hours of: Maintenance: 11,182, Supply: 43,338, and Transportation: 78,288 as provided at Exhibit A TD-01 Workload. The proposed FLC2 FTEs (i.e., FLC2 portion of proposed supervisors, if applicable) are not to be included in the total Proposed FLC1 Hours by Functional Area.

L.5.2.1.1(c)(6)(vi) The Offeror must insert the proposed labor category/position title, and it must match the labor category description found in either the CBA, SCA, Exhibit A TD-06 Key & Specified Non-Key Positions, or the SMP (if the position is an Exempt position, such as a manager or supervisor not otherwise identified in Exhibit A.)

The Offeror must insert either SCA, "CBA" or Exempt in the column titled SCA/CBA/Exempt. If SCA is identified, the Offeror must also provide the corresponding SCA labor code in the Column indicated as SCA Code. An SCA labor code shall only be provided if the position has been identified as a SCA position. In the event the labor code and the Position Title do not match, the SCA labor code will take precedence over the Position Title provided, and the description applicable to the given SCA Labor Code will be used to determine and evaluate the skill set / skill level being proposed. Additionally, the Offeror may provide the "Duty Title" in order to better identify the functional nature of the position.

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

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

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

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

L.5.2.1.1(c)(6)(ix) The Offeror must insert the number of FTEs (or less than full time equivalents expressed as FTEs) within the applicable FTE Count column. The Offeror's staffing must be rounded to the nearest hundredth decimal (i.e. two decimal places to the right of the whole number). Formatting the cells to display only two decimal places is not considered rounding; the values entered in

10 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

each cell should only contain two decimal places. FTEs entered by the Offeror with greater than two decimal places will be rounded by the Government to the nearest hundredth decimal (two decimal places to the right of the whole number) using the Microsoft Excel formula

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

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

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

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

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

L.5.2.1.1(c)(6)(xi) As identified in the Attachment 0008 Collective Bargaining Agreement (CBA), the maximum available work year for CBA employees is 1864 hours per employee. The Offerors proposed hours per year for CBA positions shall not exceed the maximum hours established by the Attachment 0008 Collective Bargaining Agreement (CBA). Note: Available hours for the base year shall be adjusted to reflect the transition-in period associated with this solicitation.

L.5.2.1.1(c)(6)(xii) COMPLIANCE REQUIREMENT: Proposing in excess of the maximum hours identified in L.5.2.1.1(c)(6)(xi) shall render the ____________________________________________________________________________________________

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

L.5.3 Past Performance Factor:

L.5.3.1 The Government will consider the recent past performance references that were provided with the Offeror's task order proposal in response to this RFP as well as references obtained from sources other than those identified by the Offeror.

L.5.3.1.1 Definitions:

L.5.3.1.1(a) Offeror, as used in this factor, is a BOA Holder Prime Contractor submitting a proposal for this task order RFP.

L.5.3.1.1(b) Joint Venture (JV) Partner, as used in this factor, is one or more entities comprising the JV BOA Holder Offeror.

L.5.3.1.1(c) Subcontractor(s), as used in the Past Performance factor, means those who are expected to perform 20% or more of the

Offeror's total estimated dollar value as found in column F of the Offeror's Teaming Matrix (Attachment 0005, Tab 2) or who are expected to perform a critical performance task. For purposes of this factor, the tasks which are considered "critical performance tasks" are

Ammunition Supply Point (ASP) (PWS 5.22); as such, any proposed subcontractor who will be performing any of…