MPE-S_RFP_AMD02.pdf

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 the amendment is to: (1) post the Government's responses to follow -up questions for clarif ication, (2) post the updated Attachment 6, Cost and Price Template, and (3) extend the proposal submission deadline to 20 September 2018 at 8:00 am EST.

Changes to the RFP are highlighted in green. Changes to Attachment 6 are noted in the responses. Please note the responses to Question #8 and Question #15, as the Government has changed the previous responses given to tw o of the questions in the f irst round of the Q&A (Question #120 and Question #61).

1. CONTRACT ID CODE PAGE OF PAGES

J 1 20

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

16C. DATE SIGNED

BY 13-Sep-2018

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 HC104718R4012

X 9B. DATED (SEE ITEM 11)

09-Aug-2018

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

13-Sep-2018

CODE

DEFENSE INFORMATION SYSTEMS AGENCY

P.O. BOX 549

FT. MEADE MD 20755

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HC104718R4012

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The Table of Contents has changed from:

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Attachment 1 AMD01 MPE-S RFP

Attachment 6 Cost and Price Template v3

Attachment 2 AMD01 MPE-S RFP Attachment 9 Sample Task Order to:

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Attachment 1 AMD02 MPE-S RFP

Attachment 6 Cost and Pricing

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

INFORMATION TO OFFERORS AND INSTRUCTIONS FOR PROPOSAL PREPARATION

L.1.0. Mission Partner Environment-Services (MPE-S), Indefinite Delivery, Indefinite Quantity (IDIQ) Contract

L.1.1. Contract Information

The following information is provided to guide proposal development:

L.1.1.1. This Request for Proposal (RFP) seeks competitive proposals, utilizing full and open competition and a best-value trade-off evaluation method (BVTO), to award a single Indefinite Delivery, Indefinite Quantity (IDIQ) Hybrid Firm-Fixed Price (FFP) and Cost Plus Fixed Fee (CPFF) Contract for MPE-S. The applicable North American Industry Classification System (NAICS) Code is 541512.

L.1.1.2. A Top Secret Facility Site Clearance from the Defense Security Service Facility Clearance Branch is required for this solicitation and contract. A DD254 will be issued with the RFP, Attachment 1. The work to be performed under this contract is up to the Top Secret (TS) level and will require Sensitive Compartmented Information (SCI) access eligibility for some personnel, to include subcontractors and Independent Consultants.

Personnel requiring TS/SCI clearance must possess a current INTERIM or FINAL TS/SCI security clearance granted by the U.S. Government. The Top Secret Facility Site Clearance is required at the time proposals are due. Any Offeror without this requirement will be removed from consideration and not evaluated. Please note that the Offeror named and submitting the proposal is required to possess the clearance. If the Offeror is a joint venture, partnership or other entity, that joint-venture, partnership or entity must possess the clearance to be eligible. It is not acceptable for each company in the joint-venture, partnership or entity to possess the clearance individually.

L.1.1.3. The Contractor shall be International Organization for Standardization (ISO)/ International Electrotechnical Commission (IEC) 20000-1:2011 certified. The Contractor shall be a self-certified Tier 3 Cybersecurity Service Provider (CSSP). The Contractor shall submit evidence of current certifications with their proposal submission in Volume I, Part E, Other Contract Documentation.

L.1.1.4. Places of performance are worldwide. Work performed may be in either secure or non-secure sites.

L.1.1.5. The purpose of these instructions is provide direction to Offerors regarding what to submit for evaluation.

The proposal shall describe the capability of the Offeror to perform the resulting Contract, shall be specific and complete in every detail, and shall be prepared simply and economically, providing a straightforward and concise description of capabilities to satisfactorily perform the Contract.

L.2.0. General Instructions

L.2.0.1. This section of the Information to Offerors provides general guidance for preparing proposals, as well as specific instructions on the format and content of the proposal. The Offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. The Offer shall be compliant with the requirements stated in this solicitation. Non-conformance with the instructions provided in this Solicitation may result in removal of the proposal from further evaluation.

L.2.0.2. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation solely on the information presented in the Offeror's proposal.

L.2.0.3. Elaborate brochures or documentation, detailed artwork or other embellishments are unnecessary and are not desired.

L.2.0.4. The proposal acceptance period is 180 days. The Offeror shall make a clear statement in Volume I- Contract Documentation that the proposal is valid through this date.

L.2.0.5. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain an electronic copy of all unsuccessful proposals.

L.2.1. General Information

L.2.1.1. Point(s) of Contact

The Contracting Officer (KO) and the Contracting Specialist(s) (CS) are the sole points of contact for this procurement. Address any questions or concerns you may have to the KO & CS. Written requests for clarification must be sent to the Brian Leyda at brian.k.leyda.civ@mail.mil, Andriani Buck at andriani.buck.civ@mail.mil, and Samantha Kelly at samantha.a.kelly8.civ@mail.mil. Oral communications are not permissible.

L.2.1.2. Debriefings

The KO will notify Offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The KO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing.

Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

L.2.1.3. 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 KO 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; therefore, the Offeror’s initial proposal should contain the Offeror’s best terms from a cost/price and technical standpoint.

L.2.1.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fedbizopps.gov. Potential Offerors are encouraged to subscribe to FedBizOpps, for real-time e-mails notifying interested parties that solicitation information has been posted to the website. The Government shall communicate all formal information regarding this solicitation via the FedBizOpps website. This is the only mechanism by which Offerors will have access to solicitation documentation released by the Government. It is the exclusive responsibility of interested/prospective Contractors to gain access to and retain an account with FedBizOpps. Any and all technical, connectivity, or other access-related issues (electronic or physical) regarding FedBizOpps must be directed to the FedBizOpps systems administrators, Federal Service Desk (FSD) by phone at 1- 866-606-8220. The KO for this solicitation has no influence over FedBizOpps regulations, policy and protocol.

L.2.1.5. Communications

Exchanges of source selection information between Government and Offerors will be controlled by the KO. Email may be used to transmit such information to Offerors and will include “Source Selection Information – See FAR

2.101 & 3.104” in the Subject line.

L.2.1.6. Competitive Range Determination

The Government reserves the right to make award without discussions or establishment of a competitive range. In the event a competitive range is established and the KO 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 KO may limit the number of proposals in the competitive range to the greatest number that will permit efficient competition. In accordance with FAR Part 15.306(c)(2), Offerors are advised that the competitive range may be reduced for purposes of efficiency.

L.2.1.7. Special Notice to Offerors

The Government's obligation under this Contract for all option periods is contingent upon the availability of funds from which payment for contract purposes can be made. No legal liability on the part of the Government for any payment may arise until funds are made available to the KO for this Contract and until the Contractor receives notice of such availability, to be confirmed in writing by the KO. The Government reserves the right to begin services for the contract based upon funds availability. The award will be based on the successful Offeror's proposal submitted in accordance with Section L herein and evaluated based on Section M.

L.2.2. Organization/Number of Copies/Page Limits http://www.fedbizopps.gov/

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1.1 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified. The contents of each proposal volume are described in Section L.3 – L.6.

Instructions for Preparation of Proposal Content as noted in the table below.

Table 1.1 - Proposal Organization

VOLUME

RFP

PARAGRAPH

REFERENCE

VOLUME TITLE PAGE LIMIT

I L.3.0 Contract Documentation

Part A L.3.1 Coversheet Shall not exceed 2 pages

Part B L.3.2 Master Table of Contents No Limit Part C L.3.3 EEO Pre-Award Information No Limit Part D L.3.4 Compliance Statement No Limit Part E L.3.5 Other Contract Documentation No Limit

II L.4.0 Technical/Management Volume Part A L.4.2.2.1 Table of Contents and List of Tables and Drawings No Limit Part B L.4.2.2.2 Executive Summary 2 pages

Part C L.4.2.2.3

Technical / Management Approach, Contract Management Plan (CMP) Servioce Management

Plan (SMP), and Resume of Key Personnel - Contract Program Manager

Technical / Management

Approach shall not exceed 40 25 pages.

The SMP CMP shall not exceed 25 8 pages and is included in the 40 25 page limit. Resumes shall not exceed 3 pages and are not included towards the 40 25 page count for the

Technical / Management

Approach page limitations.

Part D L.4.2.2.5 Small Business Participation No Limit III L.5.0 Past Performance Volume

Part A L.5.4.1 Summary Shall not exceed 2 pages per reference

* Part B L.5.4.2 Past Performance Information for Recent and Relevant Contracts

2 Contracts max; For each reference there shall be: 1 PP Description, 1

CPARS, 1 PPQ. Max 3 pages of performance recognition documents per reference. No limits on CPARS or PPQ*.

Part C L.5.4.3 Consent Letters No Limit

Part D L.5.4.4 Organizational Structure Change History 2 pages IV L.6.0 Cost/Price Volume

Part A L.6.2.2 1 Cost/Price Narrative No Limit

Part B L.6.2.3 2 Government Provided Excel Workbook Estimating System No Limit

Part C L.6.2.6 3 Sanitized Proposal Purchasing System No Limit

Part D L.6.2.4 Accounting System No Limit Part E L.6.2.5 Explanation of Estimating Methods Used No Limit Part F L.6.2.6 Price Summary Spreadsheet No Limit Part G L.6.2.7 Sanitized Proposal No Limit

*For Past Performance Volume II, Part B, Offerors shall provide a maximum of two (2) references. For each reference, the Offeror may submit one (1) Past Performance Description which is Attachment 3 (page limit = 1), one CPARS (no page limitation), one PPQ (no page limitation) and Performance Recognition documentation (page limit = 3). If the Task Order numbers and values cannot fit in the one page Past Performance Description, the Task Order numbers and associated values may be included as an addendum to the Part B Past Performance Description. The addendum should be limited to the Task Order numbers and associated values only. For multiple award IDIQs/BPAs, identification of Task Orders should be limited to the Task Orders the Offeror performed, unless the reference is for a subcontractor in which case the identification should be limited to Task Orders the subcontractor performed.

L.2.2.1. 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. Should the Government engage in discussions with Offerors, page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Page limitations shall not be circumvented by including inserted text boxes/pop-ups or internet links to additional information; such inclusions are not acceptable and will not be considered part of the proposal. The Government reserves the right to not consider any proposal for award that does not adhere to the administrative requirements of this solicitation. Each page shall be counted except as identified above. Pages shall be numbered per volume.

L.2.2.2. Page Size and Format

L.2.2.2.1. A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single spaced with space between paragraphs. Except for the reproduced sections of the solicitation document and the RFP Attachments, the text size shall be no less than 11 point Arial or Times New Roman font for all text. RFP Attachment text size shall be no less than 10 point Arial or Times New Roman font for all text. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least one inch margins on the top and bottom and side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs. These limitations shall apply to electronic proposals.

L.2.2.2.2. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. For tables, charts, graphs, figures, headers, and footers the text shall be no smaller than 8 point Arial or Times New Roman font for all text included in a table. It is the Offeror’s responsibility to ensure the information is readable.

L.2.2.3. Pricing Information

All pricing information shall be addressed ONLY in the Cost/Price Proposal Volume.

L.2.2.4. Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

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

L.2.2.6. Labeling

Each volume of the proposal should be separately labeled. A cover sheet should be provided in each volume, clearly marked as to the volume number, title, solicitation identification, and the Offeror’s name. The Contractor shall apply all appropriate markings including those prescribed in accordance with FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

L.2.2.7. Glossary of Abbreviations and Acronyms

A glossary of all abbreviations and acronyms used, with an explanation for each shall be provided as part of the executive summary. Glossaries of Abbreviations and Acronyms do not count against the page limitations.

L.2.2.8. Classified Information

Your response should not include classified information. If an Offeror believes its response must include classified information in order to be responsive to this solicitation, the Offeror shall immediately notify the KO and CS in writing with specific rationale.

L.2.3. Questions

Questions regarding this RFP shall be submitted using the Blank Question and Response template, Attachment 7.

All questions (technical or otherwise) must be submitted via email (subject line: “Questions HC1047-18-R-4012”) to brian.k.leyda.civ@mail.mil, andriani.buck.civ@mail.mil, and samantha.a.kelly8.civ@mail.mil at any time but no later than 8:00 AM EST., on August 20, 2018. Questions and/or comments received after the specified date/time may not be addressed by the Government. Once addressed, all timely questions and Government answers will be published to the FedBizOpps portal. No oral communications are permissible.

L.2.4. Electronic Submission of Offer

In order to respond to this solicitation, electronic proposals are to be submitted in lieu of paper copies. It is the Offeror’s responsibility to assure its complete proposal is received by the date and time specified in the solicitation.

Responses received after the time and date for which proposals are due will be considered late and will not be evaluated. Responses must be submitted electronically to the following:

Brian Leyda at brian.k.leyda.civ@mail.mil Andriani Buck at andriani.buck.civ@mail.mil Samantha Kelly at samantha.a.kelly8.civ@mail.mil

The Offeror’s proposal submission will be considered complete when all volumes are received.

The content and page size of electronic copies must be as described in Section L. If the Offeror sends more than one email for their proposal, they must state as such in each email (“Email 1 of 2”). The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2010 or compatible, MS Office Excel 2010 mailto:brian.k.leyda.civ@mail.mil mailto:andriani.buck.civ@mail.mil mailto:samantha.a.kelly8.civ@mail.mil or compatible, and/or Adobe XI or compatible. Attachment 6 Cost and Pricing Template must be submitted in the format provided. Other attachments may be submitted in the format provided or other approved formats listed above. Offerors shall provide one copy of each file.

To ensure delivery, no single email should exceed 15MB and no single file should exceed 5MB. Multiple emails and/or multiple files are acceptable to ensure delivery. File attachment types with extensions other than .doc, .docx, .xls, .xlsx, or .pdf may be blocked by email security protocols, and any emails quarantined as a result of restricted file types will preclude the proposal from being evaluated. Compressed files are not permitted given that zip files may be stripped from emails in accordance with DISA’s security policy. No zipped files will be evaluated. Efforts by the Government to clarify or expedite installation of electronic proposal submissions, in accordance with FAR 15.207(c), will not be considered discussions. The Government is under no obligation to seek clarification regarding electronic proposal submissions if submissions cannot be opened or accessed.

The following is how the files shall be submitted:

• Volume I: Shall be sent as one file labeled as follows:

o Company Name – Volume I – Contract Documentation

• Volume II: Shall be sent as three four files labeled as follows:

o Company Name – Volume II – Part A, B o Company Name – Volume II – Part C o Company Name – Volume II – Part D o Company Name – Volume II – Part E

• Volume III: Shall be sent as three files labeled as follows:

o Company Name – Volume III – Part A, C, D o Company Name – Volume III – Part B – Reference 1 o Company Name – Volume III – Part B – Reference 2

• Volume IV: Shall be sent as three four files labeled as follows:

o Company Name – Volume IV – Part A o Company Name – Volume IV – Part B, C, D, E o Company Name – Volume IV – Part C Part F o Company Name – Volume IV – Part G

It is the sole responsibility of the Offeror to ensure that the electronic files submitted are virus free and can be opened and read by the Government. Proposal submissions shall not be locked, encrypted, or otherwise contain barriers to opening. The Government strongly recommends that the Offeror test the files on more than one internal machine and more than one machine type or platform to ensure proposals are entirely virus free and accessible to the Government on any platform. In the event any file is corrupted or un-openable, the Offeror’s proposal may be rejected. In the event any email is quarantined for security reasons, the Offeror’s proposal may be rejected.

PROPOSAL DUE DATE: See Block 9 of the solicitation

L.3.0. Volume I: CONTRACT DOCUMENTATION

In the Contract Documentation Volume, the Offeror shall provide the following information:

L.3.1. Part A – Coversheet

L.3.1.1. The Offeror shall include the following information on the coversheet:

1) DUNS number, CAGE code and Taxpayer Identification Number (TIN);

2) Company name and mailing address;

3) Date submitted and proposal expiration date;

4) All of the above-cited information for each entity on the proposed team, if a team is proposed;

5) Type of Company (i.e., small business, 8(a), woman owned, veteran owned, etc.) as validated via the System for Award Management (SAM). All Offerors must be registered in SAM at the time the proposal is submitted and at the time of award, which is located at http://www.sam.gov/.

6) Company Point of Contact, Phone and Email Address

L.3.1.2. The Offeror shall also include the following information for Authorized Negotiators:

The Contractor represents that the following persons are authorized to negotiate on its behalf with the Government in connection with the request for proposals (RFP). The only individual(s) authorized to bind the Company is/are marked with an “*”. The Contractor shall provide, at no additional cost to the Government, updated listings of authorized negotiators (names, titles, email addresses and telephone numbers) as soon as changes are made.

Name Title Phone Number Email Address

L.3.2. Part B – Table of Contents

Include a master table of contents of the entire proposal.

L.3.3. Part C – EEO Pre-Award Information

This information is only required for the Prime Offeror. Indicate whether the Office of Federal Contract Compliance Programs (OFCCP) has conducted an evaluation and found the prospective Contractor to be in compliance with Executive Order 11246, and if so, provide the date of that determination.

L.3.4. Part D – Compliance Statement

The Offeror is required to sign and certify that all items submitted in the proposal comply with the RFP requirements and any differences, deviations or exceptions must be stated and explained in this section.

Offerors are required to complete the statement and submit it with their proposals. Even if there are no differences, deviations or exceptions, the Offeror must submit the signed Compliance Statement stating that no differences, deviations or exceptions exist.

Furthermore, the Offeror shall state in the compliance statement that its proposal is valid for no less than 180 days from the date of submission of its’ proposal response to the RFP.

Sample: Statement of Compliance: This Offeror hereby certifies this proposal is in compliance with the solicitation and its requirements. There are no exceptions, deviations or differences and the proposal is valid for 180 days from the date of submission.

L.3.5. Part E – Other Contract Documentation

L.3.5.1. Representations and Certifications

The purpose of this part is to provide information to the Government for preparing the contract document and supporting file. The Offeror's proposal must include a signed copy of the solicitation (to include all subsequent amendments) and completion of Sections A through K; refer to the specific submission instructions for Sections A- K below.

L.3.5.2. Section A - Solicitation/Contract Form http://www.sam.gov/

Completion of blocks 12, 14, 15A/B and 16 and signature and date for blocks 17 and 18 of the Standard Form (SF)

33. Signature by the Offeror on the SF 33 constitutes an Offer, which the Government may accept and should be signed by authorized individuals of the Offeror. Offerors must also submit signed copies of each SF 30 which acknowledges receipt of every RFP Amendment.

L.3.5.3. Section B - Supplies or Services and Costs/Prices

No submission is required.

L.3.5.4. Section F - Deliveries or Performance

No submission is required.

L.3.5.5. Section G - Contract Administrative Data

See Section G.

L.3.5.6. Section H - Special Contract Requirements

See Section H. Please note Section H.15. Key Personnel requires Offerors to fill-in the name of the proposed Contract Program Manager.

L.3.5.7. Section I - Contract Clauses

The Offeror shall fill-in all clauses specified in the RFP. The Offeror shall comply clauses and provisions provided herein. Please note that many clauses require the prime Contractor to include the same or similar clause in contracts with subcontractors.

L.3.5.8. Section K - Representations, Certifications, and other Statements of Offerors

See RFP. Offerors shall provide a copy of the “FAR and DFARS Report” found in the Representations and Certifications section of the System for Award Management (SAM) website. In addition, Offerors shall comply with the clause in Section I – 52.204-7 entitled “System for Award Management.” The Contracting Officer will check the System for Award Management (SAM) for those Offerors who have been determined to be within the competitive range. An Offeror shall be determined ineligible for contract award if not registered within SAM at the time of proposal submission and at the time of award. Offerors are also required to complete additional representations, certifications, acknowledgments and statements reflected in Section K of this solicitation.

L.3.5.9. DD254 Security Classification

All prime Contractors shall include in the proposal a completed Form DD254. Offerors shall complete Blocks 6, 7 and 8 of the DD254 with the appropriate information for their company. A separate DD254 shall be completed for each subcontractor, if applicable. Failure to present an acceptable DD254 with the proposal will deem the proposal non-responsive and it may be removed from further consideration. See Attachment 1.

L.3.5.10. Small Business Subcontracting

A subcontracting plan is required (FAR 52.219-9) for Other than U.S. Small Businesses only (i.e. Large Businesses). ONLY OTHER THAN U.S. SMALL BUSINESS OFFERORS ARE REQUIRED TO SUBMIT A SUBCONTRACTING PLAN. Offerors are required to submit either an individual subcontracting plan, an approved commercial plan, or a negotiated DoD Comprehensive Test Program subcontracting plan. In addition, Offerors are required to complete the DISA Subcontracting Review Checklist (Attachment 8) by inserting dollar values and percentages from your subcontracting plan as applicable for items 1 and 2, and also items 3 through 19 by completing the paragraph and page number columns.

The subcontracting plan is the organization’s business plan for the inclusion of small businesses within their capture/contracting processes. An individual subcontracting plan highlights the general “potential” for subcontracting opportunities within a specific procurement. The contract awardee has the “life of the contract” to make a “good faith effort” to ensure that subcontracted dollars will go to small businesses. Although distinct and different from each other, the small business participation plan is complementary to a subcontracting plan.

Subcontracting plans shall reflect and be consistent with the commitments presented in the small business participation plan.

Other than U.S. Small Business Offerors (i.e., Large Businesses) must submit a subcontracting plan that meets the requirements of FAR 19.704, FAR Clause 52.219-9 (Alternates and Deviations) and DFARS 252.219-7003 (or DFARS 252.219- 7004 if the Offeror has a DoD Comprehensive Test Program subcontracting plan).

The contracting officer will review subcontracting plans on an acceptable or unacceptable basis for compliance with FAR 19.704, FAR Clause 52.219-9 (Alternates and Deviations), and the applicable DFARS clause. A subcontracting plan is unacceptable if it does not clearly meet the requirements of FAR 19.704, FAR Clause 52.219- 9 (Alternates and Deviations) and DFARS 252.219-7003 (or DFARS 252.219- 7004 if the Offeror has a DoD Comprehensive Test Program subcontracting plan). Subcontracting plans will only be reviewed for acceptability for the Offeror deemed to be an apparent awardee.

The subcontracting plan shall be included in the offer, and the approved subcontracting plan shall be incorporated into the contract under Section J.

L.3.5.11. ISO/IEC 20000-1:2011 and CSSP certifications All prime Contractors shall include in the proposal evidence of current ISO/IEC 20000-1:2011 and CSSP certifications. The prime Contractor shall include Cybersecurity Service Provider (CSSP) self-certification.

L.4.0. Volume II: TECHNICAL/MANAGEMENT VOLUME

L.4.1. General

The Technical/Management Volume should be specific and complete. Legibility, clarity, and coherence is very important. Your responses will be evaluated against the technical/management criteria defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying the subfactors. All the requirements specified in the solicitation are mandatory. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

L.4.2. Format and Specific Content

L.4.2.2. Volume Organization

The Technical/Management Volume shall be organized according to the following general outline:

Part A Table of Contents and List of Tables and Drawings Part B Executive Summary Part C Technical / Management Approach

Part D Small Business Participation Plan

L.4.2.2.1. Part A – Table of Contents and List of Tables and Drawings

Submit a Table of Contents for Volume II and also include a list of Tables and Drawings utilized throughout the Technical / Management Volume.

L.4.2.2.2. Part B- Executive Summary

The Executive Summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. It shall define direct lines of control, responsibility, functional relationships, and authority among the organizational elements, including proposed teaming partners, subcontractors, and joint venture arrangements. An organizational chart may be included to illustrate the lines of control and relationships. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

The Offeror should explain and provide their overall approach and supporting rationale for how they will execute the requirements of the contract.

L.4.2.2.3. Part C –Technical / Management Approach

The Offeror’s Technical / Management approach should affirm the capabilities to execute all tasks specified in Section 6 of the attached Performance Work Statement (PWS). It should clearly describe the approach to fully meet or exceed the requirements of the PWS. Additionally the Offeror shall describe how the Offeror plans on executing the work and their capabilities/experience in executing work in this arena. The Offeror’s proposal in response to this factor should also describe where the Offeror sees risk and how they would solve, mitigate or reduce risks.

Proposals should clearly show how the Offeror will accomplish the tasks and why they have chosen that particular course. Do not merely reiterate the objectives or reformulate the requirements specified in the PWS. If the Offeror’s proposal details prior experience or an approach, methodology, tool, or plan utilized on a prior effort, the relation to the current effort should be explicitly stated. The evaluation will be limited to the current requirements. Therefore, prior experience will only be considered if it is clear how the Offeror is proposing to leverage its prior experience for the current requirement.

The Offeror’s proposal shall describe how the Offeror intends to meet or exceed the requirements detailed in the Notional Task Order (Attachment 9, Notional Task Order). The Offeror shall include an estimate of the personnel hours, by labor category and level, required for each task and subtask included in the Notional Task Order.

L.4.2.2.3.1. Subfactor 1: Design, Development, and Transition of MPE Services, Programs, Releases and Projects (PWS 6.2, Task Area 2)

The Offeror’s proposal should describe their capabilities to design, develop and transition MPE services, programs, releases and projects. The Offeror’s proposal should demonstrate the ability to develop a business case and technical proposals for new services, releases or projects. The Offeror’s proposal should describe their capabilities to prototype, develop, test and demonstrate services or projects, in cooperation with the lead Operational Test Agency (OTA), the Joint Interoperability Test Command (JITC) or similar government Operational Test Agencies/Facilities.

The Offeror’s proposal should describe how they would transition or deploy and operationally test a service or project. The Offeror’s proposal should demonstrate the ability to operate and maintain a service or project on an interim or permanent basis. The Offeror’s proposal should describe how they would provide on-demand a full-range of state-of-the-art hardware and software, and “as-a-service” offerings on a pay-for-use basis.

L.4.2.2.3.2. Subfactor 2: Steady State Operation of the MPE (PWS 6.3, Task Area 3)

The Offeror’s proposal should describe their capabilities to operate and maintain MPE networks and systems. The Offeror’s proposal should demonstrate the ability to provide Tier 2 and Tier 3 services, and create and maintain a knowledge management environment. The Offeror’s proposal should demonstrate a routine, institutionalized use of the ISO/IEC 20000 Plan/Do/Check/Act (PDCA) methodology to achieve continuous and measurable improvements.

The Offeror’s proposal should describe how they track and execute information assurance and cybersecurity requirements and their ability to provide cryptologic and key management services.

L.4.2.2.3.3. Subfactor 3: Contract Management and Task Order Management (PWS 6.1, Task Area 1)

The Offeror’s proposal should demonstrate a complete understanding of the scope, objectives and tasking outlined in the overarching IDIQ PWS. The Offeror’s proposal shall include an appropriate mix of labor categories, labor skill mix and the number of labor hours to meet the requirements of the Notional Task Order PWS. The Offeror’s proposal should provide a brief narrative for the labor categories proposed that describes the function of each labor category proposed and explains how each labor category proposed meets the Government’s requirements. clearly define and describe the function of each labor category proposed. The Offeror shall include an Offeror’s Service Management Plan (SMP) and Key Personnel that meet or exceed the requirements of the PWS. The Offeror’s proposal should describe their approach that shows a control process to ensure management visibility and effective coordination from task order startup through the cost-effective delivery of high quality services and task order transition and closeout. The Offeror should describe their management approach and address how they will track and manage all resources to support the efforts outlined in the PWS.

The Offeror shall provide a generic resume for the Contract Program Manager, in lieu of a specific individual’s resume. The resume shall not exceed three (3) pages and does not count towards the volume page limitations. The resume should include applicable certifications, education and experience. The resume shall clearly describe experience in terms of years, skills, positions, and levels (senior, junior, entry level) but shall not include a named individual.

The Contract PM shall oversee Contractor personnel, serve as the primary point-of-contact for matters related to Contract performance, and brief the Government as required by the PWS and as required by the Government for emergent issues. The minimum qualifications for this position are:

i. 15 years experience in the last 20 years managing systems or IT functions in a Federal government, multinational or joint service environment, with 5 years experience as a PM or senior technical project manager on an IT system implementation.

ii. 10 years experience in an IT technical discipline – that is, information assurance/cybersecurity, systems design and architecting; network engineering, or IT systems engineering.

iii. Certification as Project Management Professional (PMP), or as Defense Acquisition Workforce Improvement Act (DAWIA) Level II in Program Management within 120 days of onboarding.

iv. Relevant undergraduate degree (e.g., Business, Computer Science, IT or Engineering).

L.4.2.2.4. Part D – Small Business Participation Plan

All offerors, including small business, that submit proposals as a prime contractor are required to propose on the extent of their inclusion of small businesses in the performance of the contract, including: small business, small disadvantaged business, women-owned small business, HUBZone small business, and service-disabled veteran-owned small business. Small business participation is a separate and distinctly different requirement from the FAR

19.704 requirement for the Contracting Officer to review and accept an offeror’s subcontracting plan. The small business participation plan is an actual commitment document that addresses the extent of small business utilization in the performance of a contract as outlined in DFARS 215.304(c)(i). The small business participation plan outlines the "specifics" or the "how" or the "details" of the Offeror’s firm intentions to maximize the utilization of small businesses within this acquisition. The Offeror shall articulate small business contributions to contract performance at the prime contract through first tier subcontract levels. Second and third tier small business subcontractors will not be considered towards the total small business participation percentage. The utilization of small business, as expressed in the small business participation plan, will be evaluated on an Acceptable/Unacceptable basis.

Offerors shall must demonstrate their proposed approach as to how they will meet all stated small business participation requirements for this contract. The Small Business Participation Plan shall not reference the Subcontracting Plan or any other volume for information. In determining whether a plan is acceptable, the Government will consider the extent, as expressed by the percentage of the total acquisition value (TAV), of small business participation.

The Offeror’s proposed small business participation plan shall address the extent of participation of small business firms (including those in socioeconomic categories as defined in FAR Part 19) in terms of the percentage of the total acquisition value (TAV). The Offeror shall propose goals for the following categories. Goals proposed are at the discretion of the Offeror.

Small Business: X% of the total acquisition value Small Disadvantaged Business: X% of the total acquisition value Women-Owned Small Business: X% of the total acquisition value Service Disabled Veteran Owned Small Business: X% of the total acquisition value Historically Underutilized Business Zone: X% of the total acquisition value

If zero percent goals are submitted they must be supported with a detailed explanation and/or a mitigation plan to address how the Offeror will achieve participation where zero goals are cited.

L.5.0. Volume III: PAST PERFORMANCE VOLUME

L.5.1. General

Each Offeror shall submit past performance information with its proposal in accordance with the instructions below.

Offerors are cautioned that the Government will use data provided by each Offeror and data obtained from other sources in the evaluation of past performance.

Past Performance shall be organized according to the following general outline:

L.5.1.1. Part A – Summary

In accordance with the page limitations set forth in Table 1.1, Offerors shall provide a summary of the past performance references they are providing and explain what aspects of those Contracts/Orders they deem relevant and to what specific Task Areas of the proposed effort they relate. The summary should be organized in a manner that makes it clear which Task Area(s) the effort falls under and the specific work performed under each Task Area.

The Offeror shall also describe the roles of the Offeror, TA members, subcontractors, and/or joint venture partners.

The work completed by each party should be clearly delineated so it is unambiguous which member of a team completed the work.

L.5.1.2. Part B – Past Performance Information for Recent and Relevant Contracts

In accordance with the page limitations set forth in Table 1.1, Offerors shall provide information requested in the Past Performance Information Template, Attachment 3, for each reference. The information provided will be used to help determine relevancy.

The Offeror shall provide three formal performance evaluations if available. Formal performance evaluations are those within the Contractor Performance Assessment Reporting System (CPARS). If the formal evaluation has been inputted into CPARS, it shall be included, and the most recent evaluation shall be provided. If a CPARS is included, a Past Performance Questionnaire (PPQ) is not required. If a formal evaluation is unavailable, submit information using the format contained in Attachment 4, Past Performance Questionnaire and Cover Letter. Offerors shall submit Past Performance Information on recent (active within the past three years from the date of this solicitation) Contracts/Task Orders that the Offeror considers most relevant in demonstrating their ability to perform the proposed effort. The total of Past Performance Information references shall not exceed two. A minimum of one reference must be for the prime Offeror or the designated team lead for teaming arrangements (TA). A maximum of one recent and relevant Contract performed by an Offeror’s significant teaming partner or a significant subcontractor may be submitted. The Government considers a significant subcontractor or teaming partner to be a company which:

(1) provides 20% or more of the support required, (2) provides a critical portion of the effort required, or (3) influences the results of performance. References for proposed subcontractors not considered significant are not desired and will not be considered relevant. Total page count for this Past Performance volume is annotated above in Table 1.1.

Note: IDIQs or BPAs may be submitted as one past performance reference if all recent Task/Call Orders are described and presented. IDIQs, BPAs, and GSA Schedule contracts without any associated Task/Call Orders will not be considered in the past performance evaluation.

Past performance reference shall include rationale supporting your assertion of relevance. Pursuant to DoD Source Selection Procedures, the Government uses degrees of relevancy when assessing recent, relevant Contracts. The past performance evaluation team will consider the performance quality of relevant and recent efforts for the second aspect of the past performance evaluation. Finally, the past performance evaluation team will review past performance information and determine the overall rating at the factor level as it applies to the performance confidence assessment. Ratings are identified in Section M.

If submitting the Past Performance Questionnaire, the Offeror shall complete all PPQ Section I fields and send it to the assessing official. The Offeror shall not, however, complete any other section of the Past Performance Questionnaire. Questionnaires shall be sent back to the Offeror for inclusion in the proposal. Past Performance Questionnaires submitted for any Offeror’s team members shall clearly indicate the name of the Offeror within the questionnaire. The Government may contact the POCs to verify the accuracy of the Questionnaire.

Similar contracts may include efforts in a variety of sizes, a variety of disciplines, and varying degrees of technical complexity.

Similar efforts should demonstrate as many of the task area types included in the PWS (either individually or in combination thereof) as possible. Contracts or Task/Call Orders that provided multiple types of support for durations of multiple years will be more relevant. Similar efforts may include the following:

• Contracts or Task/Call Orders that provided support in the Task Areas of this PWS.

• IDIQ contracts or BPAs that provided support in related Task Areas with multiple Task/Call Orders issued.

• IDIQ contracts or BPAs that provided support multinationally.

• Contracts or Task/Call Orders in excess of $50M. Either: (1) a single Contract or Task/Call Order or (2) multiple Task/Call Orders on the same IDIQ or BPA may be combined to reach the $50M contract value.

All Task/Call Order contract numbers and the value of each individual Task/Call Order must be provided in order for multiple Task/Call Orders to be considered in excess of $50M.

• Contracts or Task/Call Orders providing support to the Department of Defense

The Offeror may submit other types of efforts, but shall explain the relevancy of those efforts to the type of work being solicited in this RFP.

Offerors may include performance recognition documents received within the last three years such as awards, award fee determinations, customer letters of commendation, and any other forms of performance recognition. Such performance recognition documents will not be considered unless they existed prior to 30 June 2018.

In…