AMENDMENT 0002 EXTENSION.pdf

0011328345

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to extend the offeror due date to allow time to post answ ers to questions received in response to the soliciation. As a result, the offeror due date is extended to Wednesday, 5 February 2020 at 12:00 PM Local Time, Fort Belvoir, Virginia.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 16

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 27-Jan-2020

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W91QV119R0012

X 9B. DATED (SEE ITEM 11)

23-Dec-2019

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer 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 1 copies of the amendment; (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 APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) 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 date, 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.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

27-Jan-2020

CODE

MICC-FORT BELVOIR

9410 JACKSON LOOP

BLDG. 1425

FORT BELVOIR VA 22060-5116

W91QV1 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W91QV119R0012

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 29-Jan-2020 12:00 PM to 05-Feb-2020 12:00 PM.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

SECTION L

1.0 GENERAL INSTRUCTIONS AND INFORMATION

1.0.1 This section provides general guidance, as well as specific instructions on format and content, for preparing proposals. The Offeror’s proposal must include all information requested and must be submitted in accordance with these instructions. Compliance with these instructions is mandatory and failure to furnish a complete proposal, at the time of proposal submission, may result in the proposal being unacceptable to the Government and may eliminate the Offeror from further consideration for award. It is the Offeror's responsibility to ensure the completeness of the proposal submitted. Evaluation of a proposal will be conducted solely on the basis of the information contained within it and the Government will not assume that an Offeror possesses any capabilities not specified. Inconsistencies among the parts of each proposal shall be explained. Any unexplained inconsistency may raise a fundamental question of the Offeror's understanding of the requirement and/or ability to perform. Offerors are advised that their proposals are presumed to represent their best efforts and must complete responses to this Request for Proposal (RFP). Proposals that simply reiterate the contents of this RFP, or contain only superficial responses, may be considered unacceptable. Evidence of experience, capability, and qualifications that clearly demonstrate and support the Offeror’s claims are essential. The absence of such evidence will adversely influence the evaluation of the proposal. Instructions contained herein, prescribe the format for the proposal and describe the approach for the development and presentation of proposal data. These instructions are designed to ensure the submission of necessary information to provide for the understanding and comprehensive evaluation of proposals.

1.1 POINT OF CONTACT

All questions, concerns, or clarifications shall be addressed to the Procuring Contracting Officer (PCO) listed below as the sole point of contact for this acquisition. All inquiries must be made in writing and submitted electronically to the Contract Specialist with a copy to the PCO. The SUBJECT LINE shall be “W91QV1-19-R-0012, Question. . . ATTN: Daniel Quinn.”

Offerors will receive a notice of receipt, but if they do not, it is their responsibility to follow-up electronically with the points of contact listed below:

Contract Specialist:

Nekia Williams Email: nekia.l.williams.ctr@mail.mil

Procuring Contracting Officer:

Daniel M. Quinn Email: Daniel.m.quinn1.civ@mail.mil

1.2 PROPOSAL CLARITY

The proposal shall be clear, concise, and include sufficient detail enabling effective evaluation to substantiate the validity of stated claims. The proposal shall not simply rephrase or restate the Government’s requirements, but shall provide convincing rationale to address how the Offeror intends to meet the requirements. The Government will consider statements and phrases such as “standard procedures will be employed” or “well known techniques will be used", etc.

unacceptable. The Offeror shall assume that the Government has no prior knowledge of the Offeror’s capabilities or experience; and as such, the Government will base its evaluation solely on the information presented in its proposal and information obtained through sources identified in past performance. As set forth in FAR 52.215-1 Alternate I (f)(4), the Government intends on conducting discussions with offerors whose proposals have been determined to be in the competitive range.

1.3 RESTRICTIONS ON DISCLOSURE AND USE OF PROPOSAL

A proposal may include data, such as technical designs or concepts, financial data, or management plans that the Offeror does not want disclosed to the public for any reason, or used by the Government for any purpose other than proposal evaluation and contract award. If the Offeror wishes to restrict the proposal, the Offeror shall mark it in accordance with FAR 52.215- 1(e).

1.4 DISPOSITION OF PROPOSALS

In accordance with FAR Subpart 4.8, Government Contract Files, the Government will retain the “original” copy of all proposals and supplemental documents provided. Unless the Offeror requests otherwise, at the completion of this acquisition the Government will destroy all extra copies of proposals and additional documents submitted.

1.5 POST AWARD NOTICES & DEBRIEFINGS

Post-award notices and debriefings will be conducted in accordance with FAR 15.506. The PCO will notify unsuccessful Offerors in accordance with FAR 15.503. Upon such notification, unsuccessful Offerors may request and receive a debriefing in accordance with FAR 15.505 or

15.506. Offerors desiring debriefings must make their requests in accordance with the requirements of FAR 15.505 or 15.506 as applicable.

1.6 RESTRICTIONS OF CONTACTS

Concurrent with the release of this RFP, appropriate offices will be advised that a source selection action is in progress for the proposed award and that contact by participating Offerors on the subject of this RFP is inappropriate. Recipients of this RFP shall not attempt contact with other parties apart from the PCO and Contract Specialist identified in paragraph 1.1 during this period.

1.7 RESERVED

1.8 DISCREPANCIES

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

1.9 RESERVED

1.10 EVALUATION

The selection of a source for award purposes will be conducted using source selection (negotiated) procedures as delineated in FAR Part 15.3. Proposals will be evaluated IAW Section M of the RFP, Evaluation Factors for Award. The Offeror’s responses to this RFP will be used as a validation tool for the Offeror’s capabilities in reference to, and understanding of, the mission capability factors. Failure to comply with the RFP will render the proposal unacceptable, and may eliminate the proposal from consideration for contract award.

1.11 NOTICE OF PRE-PROPOSAL CONFERENCE/SITE VISIT

1.11.1 A site visit will be held at 2055 Boulders Road, Charlottesville, VA on 8 January 2020 beginning 10:00 am local time. There will be a tour of facilities and short briefing conducted during the site visit. The purpose of the site visit is to allow Offerors to see the site and to allow Offerors to make notes of questions for submission to the Contracting Officer at a later date.

Prospective Offerors are highly encouraged to attend the site visit. Remarks and explanations provided during the site visit shall not change the terms of the RFP. Any change to the RFP terms will be conveyed through an amendment to the RFP. Failure to attend the site visit will not disqualify the Offeror; however, the Offeror acts at its own risk and will not be relieved from complying with the terms and conditions of any resultant contract by reason of such failure. In no event will a failure to inspect the site constitute grounds for a claim after award of a contract.

1.11.2 Offerors are limited to two (2) attendees per firm due to room space limitations. Offerors must notify Daniel M. Quinn, Contracting Officer, by electronic mail (daniel.m.quinn1.civ@mail.mil) not later than 12:00 pm local time, Fort Belvoir, Virginia on 30 December 2019, if attending the site visit. Include in the Subject Line: “W91QV1-19-R-0012, Site Visit.” Notification shall include full name, company, email address and phone number. If no response is received, the conference may be cancelled. No other pre-proposal conference will be scheduled. Attendance is at the expense of the Offerors. The Government cannot guarantee access to Rivanna Station at any other time.

To gain access inside the Nicholson Facility, which is location of site visit and primary building tour, all Offeror Representatives are required to populate the Form 21 for purposed of the Nicholson Facility Security Office conducting a background check can be performed. The populated Form 21 must be provided to Daniel M. Quinn, Contracting Officer, by electronic mail (daniel.m.quinn1.civ@mail.mil) not later than 12:00 pm local time, Fort Belvoir, Virginia on 30 December 2019 to allow sufficient time to perform the check and select an alternate if needed.

The Form 21 must include the two representative’s full name (first, middle, last), date of birth and driver’s license number. All Offeror’s will be notified if access is granted or if another Representative must be selected.

1.11.3 Attendees must arrive on time to be included in the site visit. The visit will start promptly at 10:00 a.m. local time, Fort Belvoir, Virginia and anyone arriving after that time will be denied admission. Be advised that Rivanna Station is a limited access installation, and people entering its gates are subject to entrance requirements and possible search. Attendees must arrange their travel to accommodate for these procedures. It is the responsibility of the Offeror to gain access to the Government installation. Unless some form of Department of Defense identification is provided, all drivers must provide a valid photo driver’s license, current vehicle registration, proof of vehicle insurance and enter through Rivanna Station Main Gate.

1.11.4 Comments and/or questions are prohibited to be asked during the site visit. Offerors shall submit all comments and/or questions in writing to be answered at a later date. This will ensure all Offerors have the same opportunity to receive a correct and accurate answer. This also removes any risk of an incorrect answer being provided verbally without first verifying its accuracy. All comments and/or questions must be submitted via a SINGLE email per Offeror, preferably in a Microsoft Word document attached to the e-mail. Submit to the point of contact in paragraph 1.11.2 above no later than 4:00 p.m. local time, Fort Belvior, Virginia on 15 January 2020.

1.11.5 At the site visit, there will be no cameras, audio recordings, or videotaping or other recordings allowed except that done by the Government. Cellular phones with cameras are allowed but no pictures are permitted to be taken. Cellular phones will not be allowed while touring the Nicholson Facility, which is the location of the site visit meeting.

2.0 PROPOSAL FORMAT AND PREPARATION INSTRUCTIONS

2.1 PROPOSAL FORMAT

In order to maximize efficiency and minimize the time for proposal evaluation, the electronic and paper proposal submissions shall meet format requirements. The proposal shall be limited to the submission of the volumes specified in Table 3.1.1 below. Each volume shall be separately bound in three-ring loose-leaf binders, within the required page limits, and with the specified number of copies.

2.1.1 TEXT

Text type shall be Times New Roman. Except for the reproduced sections of the RFP document, the text size (font) shall be no less than 12-point with normal proportional spacing. Text lines shall have 1.5 line spacing. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software.

2.1.2 PAGE LIMITATIONS

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will not be returned to the Offeror. For electronic CD-ROM submission, no hidden fields, macros, comments will be read.

All information shall be written clearly and be easily accessible. Page limitations may also be placed on ENs, if required. The page limitations for ENs, if any, will be identified in the correspondence forwarding the ENs to the Offerors. When both sides of a sheet of paper display printed material, it shall be counted as two pages. Each volume shall contain a detailed table of contents to delineate what is in the respective volume, which will not be counted in the page limits. In addition, the following will also not be counted in the maximum page limits: cover pages, tabs, cross-reference matrix, and glossaries. The page limitations specified in Table 3.1.1 shall be treated as maximum limits to assist in the evaluation of each proposal.

2.1.3 PAGE SIZE

A page is defined as each face of an 8 ½ x 11-inch sheet of paper containing information (excludes such things as blank pages, title pages, table of contents, tabs, dividers, glossaries, and indices). Page margins shall be a minimum of 1-inch each for the top, bottom and sides. All material must be contained within the page limits identified for each volume or appendix. The background color of each page of the proposal submission shall be white or ivory paper only. If Final Proposal Revisions (FPR) are required, the same initial proposal page limitations apply for each volume or appendix. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs, and to both electronic and hard copy proposals.

2.1.4 TABLES, CHARTS, GRAPHS, AND FIGURES

Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and/or task layout, schedules, plans. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size when printed. Foldout pages shall fold entirely within the volume and count as two (2) pages. For tables, charts, graphs and figures, the text shall be no smaller than Times New Roman 10 point. Text lines in all tables, charts, graphs, and figures shall have single (1) line spacing. All tables, charts, graphs and figures will be included in the page count. Any tables, charts, graphs and/or figures containing smaller than Times New Roman 10 point font will be disregarded. This restriction applies to both electronic and hard copy proposals. Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

2.1.5 TAB INDEXING

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Tabs/indexes will not count against the page limitations for the respective volume.

2.1.6 GLOSSARY OF TERMS

Each volume shall contain a glossary of all abbreviations, acronyms and/or terms used, with explanation corresponding definition for each. Glossaries do not count against the page limitations for their respective volumes.

2.1.7 BINDING AND LABELING

Each volume shall be separately bound and labeled in standard three-ring, loose leaf binders, and clearly identified on the front and side. The binders should permit the volume to lie flat when open, and allow for easy removal and replacement of pages. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, RFP number and the Offeror's name. The same identifying data should be placed on the spine of each binder. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and 3.104-4, Disclosure, Protection, and Marking of Offeror Bid or Proposal Information and Source Selection Information.

2.1.8 ELECTRONIC MEDIA OFFERS AND SUBMISSION

2.1.8.1 To enable the Government to successfully view the proposals electronically, the Offerors shall submit their proposals in Microsoft Office, i.e. Microsoft Word or Microsoft Excel format.

These file formats shall be exact duplicates of the paper copies. The Government will use the electronic copies in the evaluation process. The Government may use the electronic/CD proposal for all purposes; however, there is no requirement for the Government to compare or verify the consistency of the electronic proposal to the paper proposal. In the case of an identified dispute or variation in content, the electronic submitted proposal shall be deemed and treated as the official version for all purposes. Each CD-ROM case and the CD-ROM itself must be labeled as to the Offeror and numbered sequentially in the required number of copies.

2.1.8.2 File Preparation. All text, including table and figure identifiers, shall be indexed and 100% searchable text using Microsoft Word. All text shall be displayed as a font and not displayed as a bitmap in any proposal volume or appendix to facilitate the ability to copy and paste to another document.

2.1.8.3 Font and Page Setup. Text font and layout shall be as stated for paper copies.

2.1.8.4 Other Requirements. The Offeror shall not embed sound or video files into the proposal files. Minimize the use of scanned images and keep embedded graphics as simple as possible.

2.1.8.5 Proposal Format and Structure. Each volume of the electronic proposal shall be in its own subdirectory on the CD-ROM, sequentially labeled Volume I through Volume III. Volume IV, Price, shall be submitted on a separate CD-ROM.

2.1.8.6 Proposal Table of Contents file. This file serves as a table of contents for the proposal information. Also, include the list of key terms used in the proposal with their definitions, and a list of acronyms and abbreviations used in the proposal.

2.1.8.7 Viewing Environment. The Government anticipates viewing the electronic submittals with the following computer software and hardware: 1) IBM-compatible systems, 4.0 GB of RAM, nominal 19 inch color monitors, and standard CD ROM readers, 2) Windows 10 operating system, 3) Microsoft Office 2013, and Internet Explorer 8.0.

2.1.9 ELECTRONIC REFERENCE DOCUMENTS

All referenced documents for this RFP are available at the beta SAM website at https://beta.sam.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.1.10 PRICE INFORMATION

All price information shall be addressed ONLY in the Price and/or the Contract Documentation Volumes. References to work hour estimates and material may be addressed in other volumes only as appropriate for justifying labor hours and material.

3.0 PROPOSAL PREPARATION INSTRUCTIONS

3.1 VOLUMES

Offers will consist of four (4) separate proposal volumes: General and Contract Documentation, Mission Capability, Past Performance, and Price.

3.1.1 PROPOSAL VOLUMES ORGRANIZATION, NUMBER OF COPIES, AND

PAGE LIMITS

The Offeror shall prepare the proposal as set forth in Table 3.1.1 and these instructions. The titles and contents of the volumes shall be in accordance with Table 3.1.1. “Original” designates paper/printed submission. In the event that Final Proposal Revisions are required, the Offer shall clearly indicate the revision number within the Volume Name. (Revision X with X indicating the number of the revision.)

Table 3.1.1 – Proposal Organization

VOLUME VOLUME TITLE NO. OF

HARD

COPIES

NO. OF

DIGITAL

COPIES

PAGE

LIMIT

DIGITAL

FORMAT

I General and Contract Documentation

1 Original 1 No Limit

MS Word

II Mission Capability

- Key Personnel

- Workflow Execution

- Organization and

Staffing

1 Original + 3 Copies

1 50 pages total

MS Word

III Past Performance 1 Original + 3 Copies

1 See Para 7.0

MS Word

IV Price 1 1 No Limit

MS Excel

4.0 RECEIPT OF PROPOSALS

4.1 Proposals are due 12:00 p.m. LOCAL TIME, FORT BELVOIR, VIRGINIA on 5 February 2020 and shall be submitted in accordance with the instructions herein. Late proposals may be rejected from consideration IAW FAR 15.208. It is the Offeror’s responsibility to confirm the Government has received the proposal.

4.2 All proposals delivered in response to this RFP shall reflect the following in the address label:

RFP Number: W91QV1-19-R-0012 The Legend. “TO BE DELIVERED UNOPENED TO THE CONTRACTING

OFFICER,” and The volume copy numbers contained in the each box.

4.3 Proposals shall be submitted prior to the closing date and time identified on SF33 to the following address:

Regular mail/Express Carrier/Hand Carried:

Mission and Installation Command (MICC) ATTN: Daniel M. Quinn 9410 Jackson Loop, Building 1425 Fort Belvoir, VA 22060

4.4 Electronic submissions via email or facsimile will not be accepted. Offers shall be mailed through a commercial/Government carrier or hand carried.

5.0 VOLUME I – GENERAL & CONTRACT DOCUMENTATION

5.1 Volume I must be clearly marked “VOLUME I - GENERAL & CONTRACT DOCUMENTATION, RFP W91QV1-19-R-0012.” Offerors are required to submit a completed SF 33 (Solicitation, Offer and Award) (including acknowledgment of all Amendments), Section B, Section K. All final monetary extensions shall be in whole dollars only (to include unit prices). The General Volume shall be organized as follows and contain the identified information.

5.1.1 TAB A EXCEPTIONS OR ASSUMPTIONS TO TERMS AND CONDITIONS (IF

REQUIRED)

Exceptions/Assumptions (if required) - Identification and explanation of any exceptions or deviations. Additionally, any assumptions used in the proposal preparation must be identified.

Also, include any other data the Offeror chooses to bring to the attention of the PCO. See paragraph 10.0 of Section L – Instruction, Conditions and Notices to Offerors.

5.1.2 TAB B, Solicitation, Offer and Award - The SF33 shall be submitted fully completed.

The Offeror is cautioned that the SF33 must contain an original signature in block 17 of the form. The Offeror shall acknowledge any amendments to the RFP in accordance with the instructions on the SF33 and with Section L, FAR 52.215-1(b), Instruction to Offerors— Competitive Acquisition. The Offeror shall provide the name, title and telephone number of the company/division point of contact regarding decisions made with respect to the Offeror’s proposal and who can obligate the Offeror’s company contractually. Also, identify those individuals authorized to negotiate with the Government.

5.1.3 TAB C, RFP Section B (Supplies or Services and Prices) - Section B of the RFP shall be submitted fully completed and error free. Offerors shall propose a firm fixed price for each FFP CLIN in Section B. For CLIN X003, Maintenance Support Services, the offeror shall price this CLIN utilizing sub-CLIN X003AD contained in the Pricing Matrix Addendum.

5.1.5 TAB D, RFP Section K (Representation, Certifications, and Other Statements of Offerors) – The Offeror shall ensure that Section K of the RFP is submitted thoroughly completed with all blocks in each certification/representation completed truthfully and completely.

6.0 VOLUME II – MISSION CAPABILITY

6.1 GENERAL

Volume II must be clearly marked “VOLUME II – MISSION CAPABILITY, RFP W91QV1- 19-R-0012.” The Mission Capability Volume shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims in the offeror’s proposal. Your responses will be evaluated against the Mission Capability Factor and Subfactors defined in Section M, Evaluation Factors for Award. Offeror’s are cautioned that “parroting” of the technical requirements or the PWS with a statement of intent to perform does not reflect an understanding of the requirement or the capability to perform. Statements that the offeror understands, can, or will comply with the PWS and phrases such as, “standard procedures will be employed” or “well know techniques will be used” etc, will be considered unacceptable.

Offeror’s are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal. Offerors shall assume that the Government has no prior knowledge of their technical capabilities and past experience, and will base its evaluation on the information presented in the Offeror’s proposal.

6.2 FORMAT AND SPECIFIC CONTENT

The proposal will be evaluated against the Mission Capability Factor and Subfactors defined in Section M, Evaluation Factors for Award. The section will be prepared in an orderly format and in sufficient detail to enable the Government to make the full evaluation of the contractor’s technical competence and ability to comply with the contract task requirements specified in the PWS. In the Mission Capability volume, Offerors shall address their proposed approach to meeting the requirements of each evaluation subfactor.

6.3 VOLUME ORGANIZATION

The Mission Capability volume shall be organized according to the following general outline:

Table of Contents List of Table and Drawings Cross Reference Matrix Glossary

TAB A: Subfactor 1 – Key Personnel TAB B: Subfactor 2 – Workflow Execution TAB C: Subfactor 3 – Organization and Staffing

6.3.1 TAB A, SUBFACTOR 1: KEY PERSONNEL

Offerors shall provide the following information for key personnel (see PWS paragraphs

2.1.7.1.1. and 2.1.7.1.2.). Key personnel shall include the Project Manager and GFEBs Manager

a. Project Manager (PM): The contractor shall identify the PM by name. The Offeror shall provide the following information for the PM: the duties and responsibilities to be performed, the PM's experience and capabilities to perform assigned duties and responsibilities.

b. GFEBS Manager: The contractor shall identify the GFEBS Manager by name. The Offeror shall provide the following information for the GFEBS Manager: the duties and responsibilities to be performed, the GFEBS Manager's experience and capabilities to perform assigned duties and responsibilities.

6.3.2 TAB B, SUBFACTOR 2: WORKFLOW EXECUTION. The Contractor shall delineate their specific processes for executing all Maintenance Services Workload.

For PMOs, the Contractor shall fully explain how they will develop their PMO plan (i.e.

equipment verification, equipment identification, maintenance task identification, frequencies, etc.) and how their PMO Plan will be entered into GFEBS in accordance with Overarching PWS, paragraph 2.2.5. Additionally, offeror’s shall provide their workflow process for how they utilize their PMO plan in GFEBS to execute all PMO workload (i.e. reports, scheduling, tracking, marking, and closing PMOs etc.).

For DMOs, the offerors shall describe their workflow process for how they will execute all DMO workload (reference overarching PWS, paragraph 2.2.4). Their process shall entail from the time a service order is identified, opened, how it is prioritized, shop assignment, recorded in GFEBS, get the actual work executed and closed out in GFEBS.

6.3.3 TAB C, SUBFACTOR 3: ORGANIZATION AND STAFFING.

The Offeror shall submit a detailed organizational chart that depicts its proposed organizational structure. The Contractor’s organizational chart shall include each organizational element (i.e., Management/Division/ Branch/Team). The organizational chart shall include a narrative that identifies what work each element is responsible for managing and accomplishing; where decision making authority lies within the organization; and describe the work performed by teaming partners. The Offeror shall describe and explain its proposed interface (vertical and horizontal communication) between on-site project management and off-site corporate management to accomplish the mission. Additionally, it shall describe and explain its interface with the Government (corporate, project teams, Government project managers, contracting officials, inspectors, and users) to ensure smooth mission accomplishment and cooperation with all team members.

The staffing plan shall include the following: proposed staffing by labor categories to perform the required services in each Common Level of Service (CLS) contained in the PWS. Offerors shall utilize the Staffing Matrix contained in Section J for depicting their staffing. In addition, offeror's shall clearly identify and explain their methodology for accommodating fluctuating workloads and explain any proposed cross-utilization of personnel.

7.1 VOLUME III – FACTOR 2: PAST PERFORMANCE

7.2 Volume III must be clearly marked “VOLUME III – PAST PERFORMANCE, RFP W91QV1-19-R-0012.” The Past Performance evaluation will be accomplished by reviewing aspects of an Offeror's recent and relevant Past Performance, focusing on and targeting performance that is relevant to the effort as it directly relates to the work being procured under this solicitation and as defined in Section M.

7.2.1 Content of Past Performance Volume.

The Offeror’s Past Performance Volume shall contain the following and be within the specified page constraints. Additional detail for submission requirements is included in para 7.3.2.

Item Page Limit Exclusions From Page Limitation

Table of Contents Glossary

No Page Limit None

Summary Page Describe the role of the Offeror and each subcontractor, teaming partner, and/or joint venture partner.

Five (5) pages None

Organizational Structure Change History Three (3) pages

Pre-published items such as brochures, flyers, reference articles, etc. are excluded

Consent/Client Authorization Letters No page limit None Specific Relevant Contract Reference Sheets Five (5) pages each None

List of Questionnaire Recipients No page limit None

7.2.2 Early Proposal Information. In order to expedite evaluations, Offerors are encouraged, but not required, to submit their Past Performance Volumes any time prior to the closing of the RFP, to the Contracting Officer at the address specified in paragraph 4.3.

7.3 Past Performance information described herein is required on the Offeror and all subcontractors, teaming partners, and/or joint venture partners proposed to perform 10% or greater of the proposed effort based on the total proposed price. The Offeror shall submit, along with the information required in this paragraph, a consent letter, executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror's performance.

7.3.1 The Offeror shall include documentation regarding their relevant past performance as it directly relates to the work being procured under this solicitation. The Offeror SHALL NOT go back any farther than three (3) years for the submitted data from the date in Block 6 of the SF33.

The past performance data shall document a successful history of past contract performance.

7.3.2 Submission Requirements. The Offeror shall submit a Past Performance Volume containing the following:

7.3.2.1 Table of Contents

7.3.2.2 Summary Page describing the role of the Offeror and each subcontractor, teaming partner, and/or joint venture partner that the Offeror is required to provide Past Performance Specific Relevant Contract Reference Sheets for the past performance experience in accordance with Past Performance Attachment.

7.3.2.3 Consent Letters executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing the release of past performance information so the Offeror can respond to such information. A sample consent letter is attached.

7.3.2.4 Client Authorization Letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the Offeror’s performance.

7.3.2.5 Organization Structure Change History— Organizational Structure Change History.

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant present or past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider present and past performance information provided by other sources as well as that provided by the Offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

7.3.2.6 Specific Relevant Contract Reference Sheet - Sheets shall be in accordance with the Past Performance Questionnaire Attachment and are limited to five (5) pages per reference. The Offeror shall provide documentation outlining the Offeror’s past performance with contracts, as a prime or major subcontractor, which is the same or similar in nature of work, size, scope and complexity to the services being procured under this Solicitation. The submittal shall include rationale supporting your assertion of relevance and how it was determined that the work performed previously was the same or similar in nature, size, scope and complexity to the work specified by this solicitation. Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort, and to what aspects of the proposed effort they relate.

The Offeror shall submit a minimum of five (5) but no more than a total of eight (8) Specific Relevant Contract Reference Sheets identifying active or completed contracts, either Government or commercial. Limits on Specific Relevant Contract Reference Sheets are as follows:

7.3.2.6.1 Three (3) sheets identifying active or completed contracts, either Government or commercial, for the prime, team, and/or joint venture (within the same division or cost center).

7.3.2.6.2 Two (2) sheets from each subcontractor who will be completing 10% or more of the technical work.

7.3.3 Past Performance Questionnaire - (Past Performance Questionnaire Attachment), Past Performance Questionnaire. For the contracts identified on each Specific Relevant Contract Reference, the Offeror shall forward a copy of the Past Performance Questionnaire to the points of contact responsible for monitoring performance under such contracts. The points of contact shall return the questionnaires directly to Daniel Quinn, Contracting Officer, not later than the proposal due date and time. Any questionnaires not returned directly to the Contracting Officer will not be reviewed and evaluated. The information contained in the questionnaires will be used to evaluate the Offeror’s past performance. New entities that have no past customers shall annotate on the Summary Page that they have had no previous clients and that questionnaires cannot be provided.

7.3.3.1 Offerors shall provide a summary list of questionnaire recipients to include POCs and phone numbers.

8.1 VOLUME IV – FACTOR 3: PRICE

8.2 GENERAL

The separate price proposal shall be submitted utilizing the Pricing Worksheet Matrix provided (Section B Addendum) and the proposed markup rate for CLIN X003.

8.2.1 PRICE INFORMATION

All information relating to the proposed price including all required supporting documentation must be included in the section of the proposal designated as the Price volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

8.2.2 PRICING INFORMATION REQUIREMENTS

8.2.2.1 A request for Certified Cost or Pricing Data is not anticipated for the award of this contract since adequate price competition is expected; however, the Government reserves the right to request such information should it become necessary consistent with Federal Acquisition Regulation (FAR) Subpart 15.4, Contract Pricing.

8.2.2.2 Only CLIN and Sub-CLIN level pricing information is required to be entered into the Pricing Matrix (Section B Addendum); however, if reasonableness cannot be established based on price analysis, then other than certified cost and pricing data may be required. Specifically, offerors shall include the following pricing data:

a. Submit a completed Pricing Matrix (Section B Addendum) for all CLINs and Sub- CLINs. For pricing the Maintenance Services CLIN (CLIN X003) in Section B, offerors shall use pricing from CLIN X003AD identified in the Pricing Matrix (Section B, Addendum).

b. For the SubCLINs identified in the Pricing Matrix (Section B Addendum), prices shall include all material costs (i.e. bench stock, repair parts, etc.).

c. For the PWO CLIN (CLIN X004) in Section B, the offeror shall provide proposed markup rates that would be applicable to future PWOs accomplished by subcontract effort. Such markup rates shall be an all-inclusive material handling, G&A and profit rate applicable for the proposed period for negotiated PWOs containing subcontract effort. For Clarity, the proposed rates will be a binding rate captured in the contract award and shall be applied solely to subcontract efforts accomplished as part of a

PWO.

8.2.3 Department of Labor Wage Determinations

The offeror is informed that Department of Labor Wage Determinations are applicable to this requirement, see Davis Bacon Building Attachment, Davis Bacon Heavy Attachment, Davis Bacon Highway Attachment, Davis Bacon Residential Attachment, and Wage Rate Determination Attachment.

(End of Summary of Changes)