W52P1J17R0059.pdf

SOLICITATION, OFFER AND AWARD 1. This Contract Is A Rated Order Under

DPAS (15 CFR 700)

Rating Page of Pages

2. Contract Number 3. Solicitation Number 4. Type of Solicitation 5. Date Issued 6. Requisition/Purchase Number Sealed Bid (IFB)

Negotiated (RFP)

7. Issued By Code 8. Address Offer To (If Other Than Item 7)

NOTE: In sealed bid solicitations ‘offer’ and ‘offeror’ mean ‘bid’ and ‘bidder’.

SOLICITATION

9. Sealed offers in original and copies for furnishing the supplies or services in the Schedule will be received at the place specified in item 8, or if handcarried, in the depository located in until (hour) local time (Date).

Caution - Late Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. For Information A. Name B. Telephone (No Collect Calls) C. E-mail Address

Call: Area Code Number Ext.

11. Table Of Contents

(X) Sec. Description Page(s) (X) Sec. Description Page(s)

Part I - The Schedule Part II - Contract Clauses A Solicitation/Contract Form I Contract Clauses

B Supplies or Services and Prices/Costs Part III - List Of Documents, Exhibits, And Other Attach.

C Description/Specs./Work Statement J List of Attachments D Packaging and Marking Part IV - Representations And Instructions E Inspection and Acceptance K Representations, Certifications, and F Deliveries or Performance Other Statements of Offerors G Contract Administration Data L Instrs., Conds., and Notices to Offerors H Special Contract Requirements M Evaluation Factors for Award

OFFER (Must be fully completed by offeror) NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within _____ calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. Discount For Prompt Payment 10 Calendar Days (%) 20 Calendar Days (%) 30 Calendar Days (%) Calendar Days (%) (See Section I, Clause No. 52.232-8)

14. Acknowledgment of Amendments (The offeror acknowledges Amendment No. Date Amendment No. Date receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

15A. Name and Code Facility 16. Name and Title of Person Authorized to Sign Offer Address of (Type or Print) Offeror

15B. Telephone Number 15C. Check if Remittance Address is 17. Signature 18. Offer Date Area Code Number Ext. Different From Above – Enter such

Address In Schedule

AWARD (To be completed by Government)

19. Accepted As To Items Numbered 20. Amount 21. Accounting And Appropriation

22. Authority For Using Other Than Full And Open Competition: 23. Submit Invoices To Address Shown In Item

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

24. Administered By (If other than Item 7) Code 25. Payment Will Be Made By Code

26. Name of Contracting Officer (Type or Print) 27. United States Of America 28. Award Date

(Signature of Contracting Officer)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION Standard Form 33 (Rev. 9-97) Previous edition is unusable Prescribed By GSA-FAR (48 CFR) 53.214(c)

W52P1J-17-R-0059 X

2017FEB02

2017MAR0610:00am

NONE

2017FEB02 SEE SCHEDULE

W52P1J

ARMY CONTRACTING COMMAND - RI

ROCK ISLAND, IL 61299-8000

BLDGS 60 & 62

HEATHER J. PETERSEN

(309)782-2456

CCRC-FB

HEATHER.J.PETERSEN.CIV@MAIL.MIL

1 23

X 1

X 5 X 6 X 10

X 11

X 20

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: HEATHER J. PETERSEN

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

Type of Contract 1: No Cost

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

Section A - Solicitation Executive Summary

1. The Enhanced Army Global Logistics Enterprise (EAGLE) program will be used to procure logistics support requirements related to Army

Materiel Maintenance Services, Retail/Wholesale Supply Services, or Transportation Support Services that are within the scope of and designated for the EAGLE program that emerge within the year after the annual synopsis is published. Current EAGLE Basic Ordering

Agreement (BOA) holders must propose against this solicitation to have the opportunity to continue within the EAGLE program. The annual

BOA RFP will be the only opportunity contractors will have to obtain an executed EAGLE BOA in order to propose on Task Order RFPs issued within that year, even for those emergent requirements that are not specifically identified in the annual synopsis.

2. The Government will procure the EAGLE requirements utilizing the multi-step procurement process outlined below.

Step One: A Pre-solicitation Notice was published under Solicitation Number W52P1J-12-R-2000 on 22 November 2011. A potential offeror is not precluded from submitting an offer in Step Two if it did not provide a submission in response to Step One. Note: this Step will not be repeated.

Step Two: BOA RFPs will be released once a year to allow interested contractors an opportunity to submit a proposal for evaluation to obtain an executed EAGLE BOA. The Government will execute no-cost BOAs to offerors whose proposals in response to those solicitations are found acceptable based on the criteria stated in the RFP. The BOAs will be valid for a period of five (5) years beginning from the effective date of the initial BOA execution.

An annual synopsis for requirements falling under the scope of the EAGLE program will be released in Federal Business Opportunities

(FBO). The annual synopsis will cover requirements related to Army Materiel Maintenance Services, Retail/Wholesale Supply Services, or

Transportation Support Services that are within the scope of and designated for the EAGLE program that emerge within the year after the annual synopsis is published. The Army will not conduct a separate BOA synopsis for any such emergent requirement prior to issuing the applicable competitive Step Three Task Order RFP.

NOTE: The annual BOA RFP will be the only opportunity contractors will have to obtain an executed EAGLE BOA in order to propose on Task

Order RFPs issued within the year; BOA proposals will not be solicited, accepted, and will not be executed, at any time other than during the annual BOA RFP, even for those emergent requirements not specifically identified in the annual synopsis. Therefore, if a contractor desires to participate in ANY future EAGLE task order that may arise within the year, it is imperative that the contractor submit a proposal in response to the annual BOA RFP.

Step Three: The Procuring Contracting Officer (PCO) will issue competitive Task Order RFPs for specific requirements falling under the scope of the EAGLE program. An Offeror must be a qualified BOA holder as of the closing date of a task order solicitation. The

Government will confirm that an Offeror is a qualified BOA holder by checking the effective date of an offerors BOA. Task Order RFPs will result in Requirements contracts. Section C of this RFP includes exceptions for requirements performed by Ability One or 8(a) contractors.

3. A synopsis of the EAGLE requirements anticipated for the upcoming year was released in Federal Business Opportunities (FBO) on 13

January 2017. The following is a list of the current known requirements:

Joint Base Lewis-McChord (JBLM), WA: The contractor will provide logistical support including, but not limited to, field and sustainment level maintenance on tactical and non-tactical equipment. This includes but is not limited to the following Army programs:

Life Cycle Management Command Maintenance Program, Field Level RESET program, Unit Maintained Equipment (UME), Pre-Deployment Training

Equipment (PDTE), routine tactical passback maintenance, container repair, and Unit augmentation to maintenance programs. The contractor will also provide support but not limited to National Maintenance Program such as resurface engine crank and camshafts. Transportation functions include providing a Transportation Motor Pool (TMP), Personal Property Shipping Office (PPSO), and freight service operations.

Contractor will provide support to Hazardous Material Management Program (HMMP): installation supply support activities (ISSA) (GCSS-

Army 2001 plant) or Hazardous Material Control Center/Control Point (HMCC/HMCP) and movement of used waste products. The estimated release date of the RFP is August 2017, with a closing date approximately 30 days after the release. The estimated task order award is

2nd Quarter FY 18. This requirement may be issued as a 100% Small Business Set Aside.

Ft. Leonard Wood, MO: The contractor will provide kitchen equipment maintenance; these services include, but are not limited to, requirements determination, creation of a maintenance plan, and the performance of scheduled, unscheduled and/or broke-fix maintenance.

The contractor will also provide sustainment level maintenance on tactical and non-tactical equipment. The estimated release date of the RFP is September 2017, with a closing date approximately 30 days after the release. The estimated task order award is 2nd Quarter

2 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

FY 18. This requirement will be issued as a 100% Small Business Set Aside.

Ft. Campbell, KY: The contractor will provide Field and limited Sustainment level maintenance support for both tactical and non-tactical equipment to Fort Campbell tactical units (Pass Back Maintenance) and government civilian activities (Base Ops Maintenance).

As required, maintenance support will also be provided for, but not limited to, the following Army programs: Unit Maintained Equipment

(UME), Field Level Reset, National Maintenance Program (NMP), and unit capability augmentation through the use of Maintenance Support

Teams(MSTs). Supply support services requirements include: Retail Supply Support Activity Management (Class of Supply include II, IIIP, IV, VII AND IX), Central Issue Facility (CIF) Operations, Ammunition Supply Operations/ Management (ASP), Installation Property

Book Management, Individual Chemical Equipment Warehouse Operations, Subsistence Supply Management, and Hazardous Material (HAZMAT)

Supply and Services. Transportation functions include providing Transportation Motor Pool (TMP), Personal Property Shipping office(PPSO) and freight service operations, Arrival/Departure Airfield Control Group (A/DACG), Unit Movements to include movement control team (MCT) operations, container and light set maintenance, repair and document control, rail crew support and general maintenance of locomotives and track reviews and management of Privately Owned Vehicles (POV) Storage Yard. The contract will have provisions to support our customers with contract augmentation in all supply, maintenance and transportation functions within the scope of the contract. The estimated release date of the RFP is January 2018, with a closing date approximately 30 days after the release.

The estimated task order award is 3rd Quarter FY 18. This requirement may be issued as a 100% Small Business Set-Aside. However, it is undetermined at this time.

Redstone Arsenal, Huntsville, AL: The contractor will provide field and sustainment level maintenance support to Redstone tenants and other DoD organizations. Transportation functions include providing TMP, Personal Property Processing Office (PPPO), Passport

Operations, Container Management, Passenger Movements, Material Movements, freight service operations, and Direct Procurement contract

Administrative Support. Supply requirements include: Supply Support Activity and Central receiving operations, CIF Operations, and

Asset Management Services. The estimated release date of the RFP is February 2018, with a closing date approximately 30 days after the release. The estimated task order award is 4th Quarter FY 18. This requirement will be issued as a 100% 8(a) set-aside.

Ft. Gordon, GA: The contractor will provide full scope of ground maintenance support including but not limited to the following Army programs: Life Cycle Management Command Maintenance Program, Field Level RESET program, UME, routine tactical maintenance back-up, and unit augmentation and back up maintenance programs. Transportation functions include providing TMP, PPSO and freight service operations. Supply requirements include Supply Support Activity Management (Classes of Supply include I, II, IIIP, IV, VII and IX), CIF

Operations, Property Accountability, ASP Management, and Installation Property Book and Equipment Management. The estimated release date of the RFP is June 2018, with a closing date approximately 30 days after the release. The estimated task order award is 1st

Quarter FY 19. This requirement will be issued as a 100% 8(a) set-aside.

As noted above, the synopsis also applies to any other EAGLE requirements that may emerge within the year. As a separate BOA synopsis will not be issued for those emergent requirements, offerors must first submit a proposal in response to this solicitation in order to compete and be considered for award for ANY of the upcoming EAGLE Task Orders that will be released within a year of the issuance date of this RFP.

4. Offerors must demonstrate the technical capability to perform all three functional areas. That technical capability may be achieved with or without subcontractors. In subsequent Step Three proposals (i.e. Task Order proposals), Offerors are not required to propose those subcontractors used to establish technical capability in Step Two (i.e. BOA process); however, an offeror shall propose itself and any subcontractors necessary to meet the evaluation criteria and successfully perform the requirements of each Task Order.

5. The Government will execute no cost BOAs to offerors whose proposal in response to the solicitation, W52P1J-17-R-0059, are found compliant with the instructions specified as COMPLIANCE REQUIREMENTS in Section L of the RFP and are found acceptable based on the criteria stated in Section M.

a. The offerors attention is directed to Section L and the submission requirements stated therein. Failure to provide a proposal in _________________________________ compliance with the instructions specified as COMPLIANCE REQUIREMENTS in Section L of this RFP shall render the Offerors proposal non-______________________________________________________________________________________________________________________________________ compliant. The proposal will not be evaluated and will not be further considered for receipt of an executed BOA.________________________________________________________________________________________________________________

Note: The Government reserves the right to waive the Compliance Review if it is in the Governments best interest to do so.

b. The Government will conduct technical evaluations of the offerors proposals by applying the evaluation factors and criteria detailed within Section M of the RFP. The Government intends to execute BOAs based upon the content of initial proposals and without negotiating with offerors after receipt of those initial proposals; as such, an offerors initial proposal should contain sufficient information to satisfy the technical requirements. The Government does reserve the right, however, to negotiate with offerors whose initial proposals are determined to be technically unacceptable if it is in the best interest of the Government to do so. If negotiations are determined to be in the Governments best interest, the Government will only negotiate with those offerors whose proposals do not contain significant informational deficiencies. The Government will not negotiate with offerors whose proposals are determined to contain significant informational deficiencies; those offerors will be precluded from receiving a BOA.

Note: Offerors are reminded that this BOA process (both the evaluation of proposals and the placement of BOAs), is not a competitive acquisition process; as such, the source selection policies and procedures of FAR 15.3 do not apply.

3 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

c. No pricing information is requested at this time.

d. The execution of a BOA does not guarantee that the Government will place future contracts or orders with the offeror.

e. This solicitation includes clauses in Attachment 0002 that may apply to future Task Order requirements. The clauses included in this BOA RFP do not require Offeror input. The Task Order RFP will provide all required provisions and clauses applicable to that specific requirement.

f. The EAGLE Execution Business Rules are located in Section C of this solicitation. The EAGLE Execution Business Rules will apply to

BOAs and Task Order competitions.

g. Offerors should review the narrative titled "Small Business Provisions, Joint Ventures, and Subcontracting" located in Section C for additional details regarding Small Business Administration (SBA) size eligibility standards.

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

7. The closing date and time for the BOA solicitation is identified on page one (1) of the solicitation. Offerors interested in submitting a proposal must respond to the solicitation by the closing date and time.

NOTE: Offerors must first submit a proposal in response to this RFP in order to compete and be considered for award for ANY of the upcoming EAGLE Task Orders that will be released within the year.

8. Only Army Contracting Command-Rock Island (ACC-RI) is authorized to execute, modify, and undertake annual reviews of BOAs resulting from this solicitation. With ACC-RIs approval, activities other than ACC-RI are authorized to execute task orders under the BOAs resulting from this solicitation.

*** END OF NARRATIVE A0001 ***

4 23

PIIN/SIIN

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

9999 SERVICE LINE ITEM _________________

CLIN added for administrative purposes only.

(End of narrative B001)

5 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 EAGLE Execution Business Rules

1. General

a) A BOA is not a contract pursuant to FAR 16.703(a)(3).

b) IAW FAR 16.703(c)(2), a BOA shall be reviewed annually before the anniversary of its effective date and revised as necessary to conform to the changing requirements of the FAR and other applicable statutes and regulations. BOAs shall be changed only by modifying the agreement itself and not by individual orders issued under it. Modifying a BOA shall not retroactively affect orders previously issued under it. The terms of the BOA may need to be revised before the annual review due to changes in mandatory requirements.

c) Prior to the annual review and renewal, the PCO will notify the contractor in writing informing it of the review and confirming that the contractor wishes to have its BOA renewed. As BOAs are not contracts, either the Government or the Contractor may elect not to renew the BOA at the annual review. The Government reserves the right to cancel the BOA if doing so is considered to be in the

Government's best interest.

d) A Task Order becomes a binding contract at the time of the Government's acceptance of a Task Order proposal and award of a Task

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

e) BOA RFPs will be released once a year to allow interested contractors an opportunity to submit a proposal for evaluation to obtain an executed EAGLE BOA. The Government will execute no-cost BOAs to offerors whose proposals in response to those solicitations are found acceptable based on the criteria stated in the RFP. The BOAs will be valid for a period of five (5) years beginning from the effective date of the initial BOA execution.

An annual synopsis for requirements falling under the scope of the EAGLE program will be released in Federal Business Opportunities

(FBO). The annual synopsis will cover requirements related to Army Materiel Maintenance Services, Retail/Wholesale Supply Services, or

Transportation Support Services that are within the scope of the EAGLE program and designated for performance under the EAGLE program which emerge within the year after the annual synopsis is published. The Army will not conduct a separate BOA synopsis for any such emergent requirement prior to issuing the applicable competitive Step Three Task Order RFP.

NOTE: The annual BOA RFP will be the only opportunity contractors will have to obtain an executed EAGLE BOA in order to propose on Task

Order RFPs issued within the year; BOA proposals will not be solicited, accepted, and will not be executed, at any time other than during the annual BOA RFP, even for those emergent requirements not specifically identified in the annual synopsis. Therefore, if a contractor desires to participate in any future EAGLE task order that may arise within the year, it is imperative that the contractor submit a proposal in response to the annual BOA RFP.

f) Only Army Contracting Command-Rock Island (ACC-RI) is authorized to execute, modify, and undertake annual reviews of BOAs resulting from this solicitation. With ACC-RIs approval, activities other than ACC-RI are authorized to execute task orders under the BOAs resulting from this solicitation.

g) The execution of a BOA does not guarantee that the Government will place future task orders with the offeror.

2. Step Two Executed BOAs

Step Two Offerors are required to demonstrate the technical capability to perform all three functional areas of Maintenance, Supply, and

Transportation. That technical capability may be achieved with or without subcontractors.

3. Step Three Task Order Requests

a) Task Orders will only be competed amongst contractors that received a BOA in Step Two. An Offeror must be a qualified BOA holder as of the closing date of a Task Order RFP. The Government will confirm that an Offeror is a qualified BOA holder by checking the effective date of an Offerors BOA. Period of Performance for task orders issued against the BOA will be established in each task order and are effective for up to five (5) years from the Task Order effective dates.

b) Offerors are NOT required to propose those subcontractors used to establish technical capability in Step Two (i.e. BOA process);

however, Offerors shall propose themselves and/or subcontractors that can meet the evaluation criteria and successfully perform the requirements of each Task Order.

c) Specific evaluation criteria will be identified in the Task Order RFP. Evaluation factors may include Technical, Past Performance, Cost/Price, and Small Business Participation. Task Order source selections may be executed based on: evaluation of price alone; lowest price, technically acceptable (LPTA); or, best value tradeoff process.

6 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

d) A Performance Work Statement specific to the Task Order requirement and the associated Performance Requirements Summary will be provided at the Task Order level. A Task Order issued against the BOA will be issued as a Requirements contract.

e) Pricing information will only be required at the Task Order level. Task Orders may vary in contract type from Firm-Fixed-Price, Cost, or a combination of both, or Time and Material. The contractor shall adhere to the prices proposed and agreed to in each individual task order issued against the BOA. The contractor is not authorized to begin work on an order issued against the BOA until prices have been established. In the event that the Contracting Officer requires work to begin prior to establishment of pricing, failure to reach agreement on price may be disputed under the Disputes clause.

f) Offerors will certify business size standards at the Task Order level.

g) The following sections submitted by the Offeror with its BOA proposal will be carried forward and incorporated by reference into subsequent Step Three EAGLE Task Order contracts unless specifically noted otherwise in a particular Task Order RFP:

L.5.1.5 Property Management Plan

L.5.2.1(c) Resource / Task Order Management

L.5.2.1(d) Flexible Staffing Approach

L.5.2.1(e) Transition-in Approach

L.5.2.3(b)(3) Identification of an onsite independent quality control

h) Failure to comply with any term of the Task Order, to include meeting small business subcontracting goals, may result in negative past performance, which could negatively impact an Offerors ability to be successful in future Task Order competitions.

i) The Contractor may be required to enter into an Associate Contractor Agreement (ACA) with another contractor as part of task order performance.

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

*** END OF NARRATIVE C0001 ***

C.2 Small Business Provisions, Joint Ventures, and Subcontracting

(1) Set-Asides

Per FAR 19.502-2(b)(1) and (2), the contracting officer shall set aside any acquisition over $150,000 for small business participation when there is a reasonable expectation that offers will be obtained from at least two (2) responsible small business concerns and award will be made at a fair market price.

a) Task Order competitions will be set aside for small businesses based on the Governments estimated value of the Annual Requirement of the logistics effort.

b) It has been determined that for the annual requirements estimated at or below $38.5M annually, there is a reasonable expectation that two (2) or more responsible small businesses will submit offers and will be capable of providing these services; as such, in Step

Three, those requirements will be set aside for small business participation (SBSA) by those small businesses that have been determined to be acceptable under Step Two of this multi-step solicitation process.

i. If two (2) or more proposals are not received from responsible small businesses with the capacity and capability to perform the requirement at a fair and reasonable price, the competition will be opened up to all contractors that have been determined acceptable in

Step Two (BOA Holders).

ii. If a requirement has been estimated at or below $38.5M annually and therefore set aside for small business, but the proposals come in over $38.5M, the "Rule of 2" will be applied. If two (2) or more proposals are received from responsible, capable small businesses at a fair and reasonable price, the evaluation will proceed and the contract will be awarded in accordance with the evaluation terms of that Task Order. However, if two (2) or more proposals are not received from responsible small businesses with the capacity and capability to perform the requirement at a fair and reasonable price, the competition will be opened up to all contractors that have been determined acceptable in Step Two (BOA Holders).

c) Market Research will be performed prior to Task Order competitions in Step Three for those requirements expected to exceed $38.5

7 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

million per year. Market Research will consist of competition data received from BOA Holders in response to Task Order RFP submissions and resultant Task Order awards. Based upon this data, if it is determined that there is a reasonable expectation that two (2) or more proposals will be received from responsible small business BOA Holders with the capacity and capability to perform the requirement at a fair and reasonable price, under the "Rule of 2" the requirement will be solicited as a SBSA. If not, proposals will be solicited from all BOA Holders determined to be acceptable under Step Two.

(2) Size Standards

a) SBA's size eligibility standards are found in Title 13 of the Code of Federal Regulations (CFR) Part 121 (13 CFR Part 121). In order to ensure that an Offeror qualifies as an eligible small business, prospective Offerors are encouraged to review this regulation

(which was substantially revised in 2016) in its entirety. 13 CFR 121.103 in particular may assist a prospective offeror in assessing whether affiliation could apply; a finding by the SBA of affiliation between entities may result in a determination that the Offeror is other than a small business and therefore ineligible for the SBSA Task Order award. An offeror with questions regarding size eligibility standards should contact its legal counsel and/or SBA Office of Government Contracting personnel; 8(a) Program participants may consult the cognizant SBA Business Opportunity Specialist.

b) The SBA is the sole authority for making determinations of small business status for small business programs; such determinations are binding on the Offeror and on the Contracting Officer.

c) Generally, SBA determines the size status of a concern (including affiliates) as of the date the concern submits a written self-certification that it is small to the procuring agency as part of its initial offer including price. This determination will be done at the Task Order level (Step Three) and will apply for the term of the Task Order NTE five (5) years. For task orders that exceed five

(5) years, FAR 52.219-28, Post-Award Small Business Program Representation, applies. The Government will not inquire into the size status of an offeror during Step Two.

i. Joint Ventures (JVs). Due to the complexity and the wide range of capabilities required by the contracts that will be solicited for at the Task Order level (Step Three), JVs may be utilized. A JV must be an approved BOA holder from Step Two in order to propose as a Prime on a Task Order solicitation at Step Three, and the JV must comply with the applicable requirements of Title 13 of the CFR (see

Parts 121.103(h), 124.513, 125.15, 126.616, and 127.506).

Entities proposing as a joint venture (JV) are encouraged to specifically review 13 CFR 121.103, "How Does SBA Determine

Affiliation? subparagraph (h) (Affiliation based on joint ventures) prior to submitting a proposal. 13 CFR 121.103 provides several examples that may assist a prospective offeror in assessing whether affiliation could be applied to its JV.

Note: In accordance with 13 CFR 121.103, a JV of two (2) or more business concerns may submit an offer as a small business without regard to affiliation so long as each concern is small under the size standard for NAICS 561210. In order for this affiliation exception to apply, however, the following conditions must be met: there must be a written JV agreement, the JV must do business under its own name and be identified in the System for Award Management (SAM), and the JV must not have been awarded more than three (3) contracts within a two-year period from the date of award of the first contract (i.e. as of the date that it submits an initial offer that leads to the award of a contract, the JV must not have been awarded any more than two (2) contracts in the previous two (2) years).

As part of its BOA proposal at Step Two, a JV offeror will be required to submit a copy of its written JV agreement.

ii. Subcontracting Arrangements. Offerors proposing subcontracting arrangements at the Task Order level (Step Three) are encouraged to specifically review 13 CFR 121.103, "How Does SBA Determine Affiliation? (subparagraph (h)(4)) prior to submitting a proposal. A finding by the SBA of affiliation between an offeror and its subcontractor(s) may result in a determination that the Offeror is other than a small business and therefore ineligible for the SBSA Task Order award.

For SBSA solicitations, Offerors proposing subcontracting arrangements at the Task Order level (Step Three) may be required to explain which of its subcontractors are similarly situated subcontractors pursuant to the definition provided in 13 CFR 125.1 for purposes of determining whether the arrangement includes the use of any ostensible subcontractors and thus treated as a JV and the entities considered affiliated.

There is no restriction on the number of JVs or subcontracting opportunities that an Offeror may participate in.

(3) Limitations on Subcontracting (Subject to Change)

Offerors must be cognizant of Federal Acquisition Regulation (FAR) Clause 52.219-14, "Limitations on Subcontracting." This clause is mandatory for all set-aside acquisitions. When an Offeror self-certifies in Section K of the solicitation that it is a small business, the Offeror is also self-certifying it will comply with FAR Clause 52.219-14, which means that with the submission of an offer and execution of a contract, the offeror agrees that in the case of a contract for Services, at least percent fifty (50%) of the cost of contract performance incurred for personnel shall be expended for employees of the concern. Any indication on the face of the proposal that the offeror will not or cannot comply with the Limitations on Subcontracting clause will render the proposal unacceptable and the offeror ineligible for award; that is a decision that will be made during the evaluation of the proposal, not during a responsibility

8 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

determination, and thus does not go to the SBA for final review.

*** END OF NARRATIVE C0002 ***

C.3 Ability One Program Contracts and/or 8(a) Contracts

Notwithstanding the inclusion of FAR 52.216-21 in future task orders, any maintenance, supply and transportation tasks currently being performed by an Ability One contractor or an 8(a) contractor at task order locations, or subsequently determined appropriate for performance by an Ability One contractor or an 8(a) contractor, will not be included within the scope of the EAGLE requirements task orders. It should be noted, however, some EAGLE task orders will be issued as an 8(a) set-aside; therefore 8(a) work will be included on those task orders.

*** END OF NARRATIVE C0003 ***

9 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION J - LIST OF ATTACHMENTS

List of Number List of Number

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

Exhibit A EQUIPMENT DENSITY LISTING 23-SEP-2016 001

Attachment 0001 PERFORMANCE WORK STATEMENT 25-JAN-2017 029

Attachment 0002 EAGLE BOA CLAUSES 25-JAN-2017 002

Attachment 0003 EXPERIENCE MATRIX 25-JAN-2017 003

Attachment 0004 BLOCKED FILE EXTENSIONS 21-JAN-2016 001

Attachment 0005 GOVERNMENT POCS 25-JAN-2017 001

Attachment 0006 OFFERORNAME_ATTACH0006_POCS 01-JAN-2016 001

10 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 GENERAL INSTRUCTIONS

L.1.1 These instructions are a guide for preparing a proposal. These instructions describe the type and extent of information required, and they emphasize the significant areas to be addressed in the proposal. Review the Performance Work Statement (PWS) (Attachment 0001) contained in this Request for Proposal (RFP) for further insight into the areas that shall be addressed within the proposal. Include sufficient information to enable the Government evaluators to 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 execute Basic Ordering Agreements (BOAs) to offerors who are qualified by receiving an Acceptable rating for Technical. Past Performance and Cost/Price evaluations will not be performed at the

BOA level.

L.1.2 The Government intends to execute BOAs based upon the content of initial proposals and without negotiating with offerors after receipt of those initial proposals; as such, an offerors initial proposal should contain sufficient information to satisfy the technical requirements. Offerors are cautioned to examine this solicitation in its entirety to ensure that its proposal contains all necessary information, provides all required documentation, and is 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 does reserve the right, however, to negotiate with offerors whose initial proposals are determined to be technically unacceptable if it is in the best interest of the Government to do so. If negotiations are determined to be in the Governments best interest, the Government will only negotiate with those offerors whose proposals do not contain significant informational deficiencies.

The Government will not negotiate with offerors whose proposals are determined to contain significant informational deficiencies; those offerors will be precluded from receiving a BOA and will be notified in writing.

Offerors are reminded that this BOA process (both the evaluation of proposals and the placement of BOAs), is not a competitive acquisition process; as such, the source selection policies and procedures of FAR 15.3 do not apply.

L.1.3 The proposal shall be valid for 180 days from the required submission date.

L.1.4 Late proposals will not be accepted.

L.1.5 For the purposes of this BOA RFP:

L.1.5(a) An offeror is defined as the prime contractor or Joint Venture (JV) that proposes an organizational capability for consideration for an executed BOA.

L.1.5(b) A 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.6 Updates to the solicitation, to include the RFP, amendments, notices, and other information, will be made available on the

FedBizOpps (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, legible, practical manner. In addition, the offeror shall write the proposal in

English and shall be specific and complete as described in these instructions. Adherence to the prescribed format is required. Failure ________ to provide a proposal in compliance with the instructions specified as COMPLIANCE REQUIREMENT in Section L of this RFP shall render the________________________________________________________________________________________________________________________________________ offeror's proposal non-compliant. The proposal will not be evaluated and will not be further considered for receipt of an executed BOA.________________________________________________________________________________________________________________________________________

The Government is not obligated to engage in any exchanges with an offeror who fails to provide all of the required documents for evaluation.

L.2.1(a) Note: The Government reserves the right to waive the Compliance Review if it is in the Government's best interest.

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

L.2.3 The 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.4 Digital MS Word and MS Excel files, where requested and required pursuant to provisions of this RFP, shall be compatible with

Microsoft (MS) Office 2013.

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

L.2.5 Adobe Portable Document Format (PDF) Files: Scanned PDF documents, where requested and required pursuant to provisions of this

11 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

RFP, must be legible and must be viewable in Adobe Acrobat.

L.2.5(a) Text Searchable Adobe PDFs: File formats that are identified as Text Searchable Adobe PDF must be formatted to contain searchable text. Note: All elements of the file to include tables, diagrams, charts, etc. must be able to be searched for text. The

Government will not accept scanned or image-only PDF files in lieu of this requirement and will not invoke the text recognition feature within Adobe.

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

Attachment 0004 for a complete list of non-acceptable file types.

L.3 PROPOSAL SUBMITTAL INSTRUCTIONS:

L.3.1 The offeror shall submit its proposal through the 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 ten (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. The abbreviation used for the name of the company should be consistent across all file names found within the proposal.

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.

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

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

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

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

Offerors should allow adequate time for submission completion because the entire proposal must be received by the due date and time for the proposal to be considered timely.

L.3.7 To avoid rejection of an offer, the offeror shall make every effort to ensure its electronic submission is virus free.

Submissions or portions thereof submitted and which the automatic system detects the presence of a virus or which are otherwise unreadable will be treated as unreadable pursuant to FAR 15.207(c).

L.4 PROPOSAL STRUCTURE:

L.4.1 The offeror shall submit a proposal in accordance with the guidelines below.

L.4.1.1 For all documents, each page shall include the complete offeror's name, offeror's CAGE Code, BOA RFP number, and proposal submission date 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 BOA, the offeror must submit a complete response to this RFP using the instructions provided in Section L. If the _______ offeror's proposal fails to meet the terms and conditions of the RFP or takes exception to any of the terms and conditions of the RFP,_______________________________________________________________________________________________________________________________________ the offeror's proposal will not be acceptable and will not be further considered for execution of a BOA.________________________________________________________________________________________________________

L.4.1.3 The offeror shall provide sufficient detail to substantiate the validity of all stated assertions. The proposal must not merely repeat the RFP requirements, but rather must provide narrative evidence in support of any statements relating to proposed capabilities or relevant experience. Data not submitted with the proposal and presumed to be known (i.e., previous projects performed for the United

States Government) will not be considered as part of the proposal.

L.5 INFORMATION TO BE SUBMITTED:

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

12 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

L.5.1.1(a) Required File Name: OfferorName_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 by an authorized agent shall render the offeror's proposal non- ___________________________________________________________________________________________________ compliant, and it will not be evaluated nor considered for award of an executed BOA.____________________________________________________________________________________

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

L.5.1.2(a) Required File Name: OfferorName_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 Offeror Points of Contact (POC): The offeror(s) are required to provide two (2) company individuals whose responsibilities will include reading and responding to Government proposal inquiries through e-mail. For example, the offeror's Contract Manager, as an agent of the company might be the main agent responsible, but a second agent should be available in case of the main agents unavailability. The two (2) agents names, titles, telephone numbers, email addresses, and mailing addresses shall be provided in

Attachment 0006.

L.5.1.3(a) Required File Name: OfferorName_Att0006_POCs

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

L.5.1.3(c) Page Limit: none

L.5.1.4 JV Information: In order for the Government to review the JV partnership, if applicable, the offeror shall submit the following information:

L.5.1.4(a) A signed legal JV agreement prepared by an attorney, which clearly explains the responsibilities of each party to the JV agreement. In addition, the agreement shall clearly explain the formation of the JV and procedures for acceptance of product and payment. The JV agreement shall clearly identify the team lead company and the team lead company's point of contact, as well as their responsibilities explained in detail. In addition, company names, POCs, business size, number of employees (including all affiliates), and description of work to be performed by members of the JV shall be provided as part of the JV agreement.

L.5.1.4(b) Any updates to the JV agreement shall be submitted to the EAGLE mailbox within seven calendar days after the JV agreement is signed.

L.5.1.4(c) A signed copy of any other agreements, either formal or informal, that identify the roles and responsibilities of each business concern in the JV.

L.5.1.4(d) If other than a small business concern is part of the JV, a copy of the Small Business Administration (SBA) approved SBA

Mentor-Protege Agreement. The offeror should be aware of the SBAs regulations regarding affiliations to determine business size.

Affiliation regulations are especially important for determining the size of JVs.

L.5.1.4(d)(i) Required File Name: OfferorName_JV

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

L.5.1.4(d)(iii) Page Limit: none

If an offeror is not proposing a JV, the file OfferorName_JV is not required.

L.5.1.5 Property Management Plan. In accordance with FAR 52.245-1(b) Property management, Offerors shall have internal controls to manage (control, use, preserve, protect, repair and maintain) Government property in its possession accountable to the contract. The internal controls shall be adequate to satisfy the requirements of this clause. In doing so, the successful Offeror shall initiate and maintain the processes, systems, procedures, records, and methodologies necessary for effective and efficient control of Government property accountable to the contract. The Offeror may employ customary commercial practices, voluntary consensus standards, or industry-leading practices and standards that provide effective and efficient Government property management that are necessary and appropriate

13 23

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

for the performance of this contract (except where inconsistent with law or regulation). Offerors shall provide a written plan detailing its internal controls to manage Government property in its possession, to include the use of appropriate net-centric electronic applications (i.e. WAWF, iRAPT, IUID Registry, DCMA eTools...etc.) that are required for Government-Furnished Property (GFP) traceability IAW DFARS clause 252.211-7007, Reporting of Government-Furnished Property and DoDI 4161-02, Accountability and Management of Government Contract Property.