W52P1J18R0010-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 2018MAY01

W52P1J

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

BLDGS 60 & 62

NANCY N. ANDREESEN

EMAIL: NANCY.N.ANDREESEN.CIV@MAIL.MIL

W52P1J-18-R-0010

2018APR11

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 32

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: NANCY N. ANDREESEN

Buyer Office Symbol/Telephone Number: CCRC-FC/(309)782-0112

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 for Proposal (RFP) # W52P1J-18-R-0010 is to incorporate the following corrections:

a. Update Section L language at L.5.2.1.1(c) by DELETING and ADDING the following:

DELETE: "identified at Exhibit A TE 1 M-S-T-001 Minimum Functional Labor Category 1 Hours and to meet all the PWS requirements."

ADD: "and the PWS requirements identified therein." and "It is further noted that the inclusion of only some of the PWS paragraphs in

Exhibit A (TE 1 M-S-T-001 Minimum Functional Labor Category 1 Hours) was for Technical evaluation purposes only. During contract execution, compliance with all PWS requirements is expected and required."

Section L.5.2.1.1(c) now reads:

L.5.2.1.1(c) Staffing/Labor Mix (Attachment 0002 - Staffing/Labor Mix): The Offeror must provide its proposed staffing mix/labor categories (skill sets / skill level, Functional Labor Category 1 (FLC1), Functional Labor Category 2 (FLC2), number of employees) in relation to the PWS requirements and the provided workload data (see applicable Technical Exhibits) for both the base period and option periods (fully operational capable 12-month periods (365 day periods)). The Offeror's proposal must present a staffing approach which demonstrates a thorough understanding of the effort and provides the skill sets / skill levels (including level of responsibility) that are necessary to successfully perform the specific workload requirements at Exhibit A TE 1 M-S-T-001 Minimum Functional Labor Category 1

Hours and the PWS requirements identified therein. 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 TE 1-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 TE 1-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 0016.

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 TE 1-G-005 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).

It is further noted that the inclusion of only some of the PWS paragraphs in Exhibit A (TE 1 M-S-T-001 Minimum Functional Labor Category

1 Hours) was for Technical evaluation purposes only. During contract execution, compliance with all PWS requirements is expected and required.

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

b. Update Section L language at L.5.2.1.1(c)(6)(i) by DELETING and ADDING the following:

DELETE: "the requirements of Exhibit"

ADD: ",specifically those that are both identified at Section 5 of the PWS."

Section L.5.2.1.1(c)(6)(i) now reads:

L.5.2.1.1(c)(6)(i) The Offeror must identify all of its proposed staffing required to support all PWS requirements and, specifically those that are both identified at Section 5 of the PWS and Exhibit A TE 1 M-S-T 001 Minimum Functional Labor Category 1 Hours in terms of FTEs and function labor category type (i.e. FLC1 or FLC2) on its Staffing/Labor Mix - Attachment 0002. The Government-required Key

Position labor categories (identified in TE1G-005 Key & Specified Non-Key Positions) and associated FTEs are prepopulated in Attachment

0002, as are the required PMO-related Specified Non-Key Positions (also identified in TE1G-005); however, the Offeror must identify all other "Specified Non-Key" positions required by TE1G-005 in its Attachment 0002 by including the designation of "(Non-Key)" within the labor category title being proposed in the column labeled "Position Title" (see "Example Tab" in Attachment 0002- Staffing/Labor Mix).

c. Update Section L language at L.5.2.1.1(c)(6)(vi)by DELETING AND ADDING the following:

2 32

W52P1J-18-R-0010 0001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

DELETE: "The Offeror must insert the proposed Offeror Position Title and it must match the labor category description found in either the CBA, SCA, Exhibit E TE 1-G-005 Key & Specified Non-Key Positions or be provided by the Offeror if Exempt (e.g., manager, supervisor)). If SCA is identified, the Offeror must also provide the corresponding SCA labor code in the Column indicated as SCA

Code). In the event the labor code and the Offeror Position Title do not match, the SCA labor code will take precedence over the

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

ADD: "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 E TE 1-G-005 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 E.)

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; a labor code shall not be identified if the position has been identified as a CBA 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."

Section L.5.2.1.1(c)(6)(vi) now reads:

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 E TE 1-G-005 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 E.)

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; a labor code shall not be identified if the position has been identified as a CBA 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.

d. Update Section L language at L.5.2.1.1(c)(6)(xi)by DELETING AND ADDING the following:

DELETE: "1864 hour per employee"

ADD: "1840 hours per employee"

Section L.5.2.1.1(c)(6)(xi) now reads:

L.5.2.1.1(c)(6)(xi) As identified at Attachment 0008, the maximum available work year for CBA employees is 1840 hours per employee.

The Offerors proposed hours per year for CBA positions shall not exceed the maximum hours established by Attachment 0008. Note:

Available hours for the base year shall be adjusted to reflect the transition-in period associated with this solicitation.

e. Update Section M language at M.5.1.2(c)(1) by DELETING AND ADDING the following:

DELETE: "Demonstrates an adequate understanding of the effort by providing appropriate staffing that is realistic and feasible to successfully perform all of the PWS requirements. Staffing level support workload requirements, the PWS requirements and Exhibit A TE 1

M-S-T-001 Minimum Functional Labor Category Hours for both the base period and the option periods (fully operational capable 12-month /

365 day periods. Note: For Technical evaluation purposes only, the Government will utilize the labor category definitions provided in

Attachment 0008 Collective Bargaining Agreement (CBA), the SCA Directory of Occupations (5th Edition), TE 1G-005 (Key and Specified Non-

Key Positions, and/or the SMP narrative (for proposed Exempt positions not otherwise found in TE 1G-005, or for additional explanation provided for Non-Exempt positions) to determine the skill set/skill level being proposed and to determine whether the proposed laborer can perform the required task(s). A cross-walk between the CBA and the SCA is provided in Attachment 0016."

ADD: "Demonstrates an adequate understanding of the effort by providing appropriate staffing that is realistic and feasible to successfully perform the specific workload requirements in Exhibit A TE 1 M-S-T-001 Minimum Functional Labor Category 1 Hours and the

PWS requirements identified therein. Staffing levels support the provided workload requirements for both the base period and option periods (fully operational capable 12-month / 365 day periods).

Note: For Technical evaluation purposes only, the Government will utilize the labor category definitions provided in Attachment 0008

Collective Bargaining Agreement (CBA) (if any provided), the SCA Directory of Occupations (5th Edition), TE 1G-005 (Key & Specified Non-

3 32

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Key Positions), and/or the SMP narrative (for proposed "Exempt" positions not otherwise found in TE 1G-005, or for additional explanation provided for "Non-Exempt" positions) to determine the skill set / skill level being proposed and to determine whether the proposed laborer can perform the required task(s). A cross-walk between the CBA and the SCA is provided in Attachment 0016 to aid in determining applicable skill sets.

It is further noted that the inclusion of only some of the PWS paragraphs in Exhibit A (TE 1 M-S-T-001 Minimum Functional Labor Category

1 Hours) was for Technical evaluation purposes only. During contract execution, compliance with all PWS requirements is expected and required."

Section M.5.1.2(c)(1) now reads:

Demonstrates an adequate understanding of the effort by providing appropriate staffing that is realistic and feasible to successfully perform the specific workload requirements in Exhibit A TE 1 M-S-T-001 Minimum Functional Labor Category 1 Hours and the PWS requirements identified therein. Staffing levels support the provided workload requirements for both the base period and option periods

(fully operational capable 12-month / 365 day periods).

Note: For Technical evaluation purposes only, the Government will utilize the labor category definitions provided in Attachment 0008

Collective Bargaining Agreement (CBA) (if any provided), the SCA Directory of Occupations (5th Edition), TE 1G-005 (Key & Specified Non-

Key Positions), and/or the SMP narrative (for proposed "Exempt" positions not otherwise found in TE 1G-005, or for additional explanation provided for "Non-Exempt" positions) to determine the skill set / skill level being proposed and to determine whether the proposed laborer can perform the required task(s). A cross-walk between the CBA and the SCA is provided in Attachment 0016 to aid in determining applicable skill sets.

It is further noted that the inclusion of only some of the PWS paragraphs in Exhibit A (TE 1 M-S-T-001 Minimum Functional Labor Category

1 Hours) was for Technical evaluation purposes only. During contract execution, compliance with all PWS requirements is expected and required.

f. Add Section I FAR 52.222-43 clause.

g. Update Section J RSA Attachment 0015 - Subcontractor Cost Information Submission, dated 1May2018, to correct the document title heading from "0016" to "0015."

2. The proposal response date and time of this RFP remains unchanged.

3. All other terms and conditions remain unchanged.

*** END OF NARRATIVE A0002 ***

4 32

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION I - CONTRACT CLAUSES

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

I-1 ADDED 52.222-43 FAIR LABOR STANDARDS ACT AND SERVICE CONTRACT LABOR STANDARDS--PRICE MAY/2014

ADJUSTMENT (MULTIPLE YEAR AND OPTION CONTRACTS)

5 32

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 0015 CONTRACTOR COST INFORMATION SUBMISSION 01-MAY-2018 001

6 32

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 PWS contained in this 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 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. IAW 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 IAW FAR 52.215-1.

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

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

L.1.7 Updates related to this Task Order RFP, to include the RFP, amendments, notices, and other information, will be made available on the FBO.gov website. Offerors are advised to continuously monitor the FBO.gov website for new information. Offerors are deemed to have knowledge of all information that is posted to the FBO.gov website.

L.2 PROPOSAL PREPARATION:

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

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

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

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

Commercial and Government Entity (CAGE) Code.

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

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

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

Acrobat.

L.2.6.1 Text Searchable Adobe PDFs: File formats that are identified as Text Searchable Adobe PDF must be formatted to contain searchable text. All elements of the file must be able to be searched for text. The Government will not accept scanned or image-only

PDF files in lieu of this requirement and will not invoke the text recognition feature within Adobe.

7 32

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

L.3 PROPOSAL SUBMITTAL INSTRUCTIONS:

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

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

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

L.3.4 Digital file names shall use the required naming convention for each specific proposal document identified below. Filenames must be 40 characters or less and must not contain single quotes, spaces and pound or percent signs. If an Offeror's file name is too long

(more than 40 characters), it is permitted to abbreviate the Name of the Company field within the file name.

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

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

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

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

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

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

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

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

FAR 15.207(c).

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

L.4 PROPOSAL STRUCTURE:

L.4.1 The Offeror shall 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, it shall render the Offeror's proposal unacceptable and will not be further considered for award.__________________________________________________________________________________________________________________________________

L.4.1.2 (a) Each Offeror shall submit the most current versions of Attachments 0002, 0003, and 0005 required for this RFP. The

Government will verify that the Offerors submission contains the most current RFP Attachments 0002, 0003 and 0005 that were posted on the FedBizOpps.gov website (FBO.gov).

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

L.4.1.3 A proposal is presumed to represent the Offerors best efforts to respond to the RFP. The Offeror must provide adequately detailed information that complies with the solicitation requirements, allows for meaningful review by the Government evaluators, and affirmatively demonstrates the merits of its proposal. The Offeror shall provide sufficient detail to substantiate the validity of all stated assertions and must not merely repeat the RFP requirements, but rather must provide convincing documentary evidence of how

8 32

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 USG) will not be considered. Clarity and completeness are essential. It is the Offerors obligation to submit an unambiguous proposal that clearly reflects the Offerors intended technical approach and establishes cost credibility. Any inconsistency, whether real or apparent, between promised performance and proposed cost must be adequately explained in the proposal.

For example, if the use of new and innovative techniques is intended, the impact on cost must be explained. As another example, if a business policy decision to absorb a portion of the estimated cost was made, that approach shall be stated within the proposal

(including any associated calculations). Failure to adequately explain an inconsistency between promised performance and cost may result in a finding of Technical Unacceptability or a finding that a proposed cost is unrealistic for work to be performed.

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

L.5 INFORMATION TO BE SUBMITTED:

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

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

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

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

L.5.1.1(c) Page Limit: None

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

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

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

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

L.5.1.2(c) Page Limit: None

L.5.1.3 Section I clauses that require Offeror completion.

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

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

L.5.1.3(c) Page Limit: None

L.5.1.4 Section K clauses that require Offeror certification.

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

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

L.5.1.4(c) Page Limit: None

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

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

Therefore, the Offeror is required to provide at least two (2) company individuals whose responsibilities will include reading and responding to Evaluation Notices (ENs) through e-mail. For example, the Offeror's Contract Manager, as an agent of the company might be the main agent responsible, but a second agent shall be available in case of the main agent's unavailability. The agents' names, company titles, telephone numbers, facsimile numbers, and e-mail addresses should be provided, and it is the Offeror's responsibility to keep the 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 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

9 32

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 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, and cost proposal submittal method, indicate whether the participant requires a SECRET

Facility Clearance, and indicate which particpants 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) 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 (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.

10 32

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 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 252.223-7002 - Safety

Precautions for Ammunition and Explosives, 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 the 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:

11 32

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.

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 Offerors shall submit its Small Business Administration 8(a) Certification Letter as proof of being an 8(a) contractor.

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

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

L.5.1.11(c) Page Limit: None

L.5.1.11(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 its Staffing and Management Plan (SMP).

L.5.2.1.1 Staffing and Management Plan (SMP):

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

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

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

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

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

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

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

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

L.5.2.1.1(b) The Offeror's Staffing and Management Plan must detail the Offeror's 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 TE 1-G-005 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 E TE 1G-005 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

12 32

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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

Attachment 0002.

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

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

L.5.2.1.1(b)(2)(ii) Identification of the command and control relationship among the Offeror, all proposed subcontractor(s) as identified on the Offerors Teaming Matrix (Attachment 0005, Tab 2).