50310219R0016__AMEND_3_TRACK_CHANGES.pdf

SECTION G – SPECIAL CONTRACT REQUIREMENTS

SMALL BUSINESS RECERTIFICATION

For the purpose of this Contract, small businesses will be required to recertify their small business size status 90 days prior to the end of the fifth base year of the Contract and prior to exercising the option. If the option is exercised, the Government will move small business contractors to the unrestricted pool if they can no longer re-certify as a small business. A change in the size status does not change the terms and conditions of the contract except as provided. A small business contractor that moved to the unrestricted pool will be required to meet all then-current terms and conditions of the unrestricted pool, such as the requirement for a Small Business Subcontracting Plan, prior to receiving a Task Order in the unrestricted pool.

SECTION H - Special Contract Requirements

6013.00 COMMON SECURITY CONFIGURATIONS (23-MAR-09)

Common security configurations are published on NIST's web site http://checklists.nist.gov. NIST's Computer Security Division website is located at http://csrc.nist.gov. For more information about the security content automation program, see http://nvd.nist.gov/scap.cfm. NIST Special Publication 800-70, "Security Configuration Checklist Program for IT Products," is located at http://csrc.nist.gov/checklists/SP800-70- DRAFT.pdf https://nvlpubs.nist.gov/nistpubs/specialpublications/NIST.SP.800-70r4.pdf.

SECTION L – INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR

RESPONDENTS

L.1 PROVISIONS AND CLAUSES INCORPORATED BY REFERENCE

FAR TITLE DATE

52.204-7 SYSTEM FOR AWARD MANAGEMENT JUL 2013

52.204-16 COMMERCIAL AND GOVERNMENT ENTITY CODE

REPORTING

JUL 2015

52.204-18 COMMERCIAL AND GOVERNMENT ENTITY CODE

MAINTENANCE

JUL 2016

52.215-1 INSTRUCTIONS TO OFFERORS - COMPETITIVE

ACQUISITION

JAN 2004

52.216-27 SINGLE OR MULTIPLE AWARDS OCT 1995

52.222-24 PRE-AWARD ON-SITE EQUAL OPPORTUNITY

COMPLIANCE EVALUATION

FEB 1999

52.237-10 IDENTIFICATION OF UNCOMPENSATED OVERTIME MAR 2015

FAR 52.216-1 TYPE OF CONTRACT (APR 1984)

The Government contemplates award of Multiple Award Indefinite Delivery, Indefinite Quantity (IDIQ) contracts resulting from this solicitation that may include firm fixed price and time-and-material and labor-hour task orders.

(End of provision)

FAR 52.233-2 - SERVICE OF PROTEST (SEP 2006)

(a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the Government Accountability Office (GAO), shall be served on the Contracting Officer (addressed as follows) by obtaining written and dated acknowledgment of receipt from:

U.S. Securities and Exchange Commission Attn: Anke Taylor, Contracting Officer 100 F Street, NE Washington, DC 20549

(b) The copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO.

(End of provision)

FAR 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this/these address(es):

http://farsite.hill.af.mil/ https://www.acquisition.gov/browsefar

(End of provision)

L.1 INSTRUCTIONS TO OFFERORS

L.1.1 CONTRACT INFORMATION

For consideration in developing your proposal, the following information is provided.

The current SOO represents a total of seven (7) individual Service Channels. Small Business Offerors must cover (i.e. be able to provide support to) all 7 service channels. Any company proposing to be either the Prime Contractor or a Subcontractor on a team may only be a part of one (1) team: (a) Offerors cannot be the prime on one team and a subcontractor on another and (b) a company cannot be a subcontractor on multiple teams.

Once OneIT IDIQ awards are made, the government reserves the right to permit subcontracting between the restricted and unrestricted pool of OneIT IDIQ holders on OneIT task orders provided it does not conflict with FAR 52.219-14, Limitations on Subcontracting and is in the best interest of the government.

L.1.2 PROPOSAL SUBMISSION INSTRUCTIONS

The following instructions are for the preparation and submission of proposals. The purpose of this section is to establish requirements for the format and content of proposals so that proposals contain all essential information and can be evaluated equitably.

Offerors are instructed to read the entire solicitation document, including all attachments in Section J, prior to submitting questions and/or preparing your offer. Omission of any information from the proposal submission requirements may result in rejection of the offer.

The Offeror, either through its parent, affiliates, subsidiaries, business units, joint venture, or any other type of business organizational structure shall submit, as part, of only one proposal. Failure to comply with this single submission requirement, shall render a proposal non-responsive at any point during the acquisition process.

And if determined to be non-compliant post award, the relevant contract will be terminated as appropriate.

Existing OneIT contract holders, either through their parent, affiliates, subsidiaries, business units, joint ventures, or any other type of business organizational structure, are not eligible to participate in this On- Ramping event.

Experience or past performance of a parent or affiliated company can be submitted and will be considered only where the firm's proposal demonstrates that resources of the parent or affiliate will be provided and the parent or affiliate will have meaningful involvement in contract performance. If relying on this type of experience, a Letter of Commitment must be submitted.

All information within the page limitations of the proposal is subject to evaluation. The Government will evaluate proposals in accordance with the evaluation criteria set forth in Section M of this solicitation.

Offerors may make minor formatting changes to Section K templates used in proposal submission. For example, minor formatting changes include such things as adjusting page breaks, adding corporate identification logos, identifying proposal volume identifiers in the headers and footers, including disclaimers of proprietary information.

Offerors shall not make content and formatting changes (i.e. font type, size, etc.) to Section J templates provided for use in the proposal submission. However, Offerors may add identifying proposal volume identifiers in the headers and footers, including disclaimers of proprietary information, and adjust the Cost/Price template if necessary, etc.

The electronic solicitation documents, as posted on http://www.fbo.gov, shall be the "official" documents for this solicitation.

The Government will not reimburse Offerors for any cost incurred for the preparation and submission of a proposal in response to this solicitation.

All proposal information is subject to verification by the Government. The Offeror is required to ensure all proposal information submitted is verifiable. If the SEC Source Selection Team detects a high degree of unverifiable, contradictory or unsubstantiated information submitted in an Offeror’s proposal, the Government reserves the right to end the proposal evaluation, and the Offeror may be removed from being considered for award. Falsification of any proposal submission, documents, or statements may subject the Offeror to civil or criminal prosecution.

NOTE: This solicitation instructs Offerors to provide support documentation for all scored evaluation criteria. An Offeror shall provide the form of documentation for validation purposes that is required per Section L.

L.1.3 OFFICIAL LEGAL BIDDING ENTITY

All the evaluation elements an Offeror is claiming credit for in accordance with Section L.3, Volumes 1 through 6, must be in the Offeror’s name or as further defined in L.3 Restricted and Unrestricted Pools as submitted in Block 15A on the Standard Form (SF) 33, Solicitation, Offer and Award, with a corresponding DUNS Number in SAM.GOV that matches the Offeror name on the SF 33, Block 15A. (See Section L.3.1.1).

L.1.4 MERGERS, ACQUISITIONS, NOVATIONS, AND CHANGE-OF-NAME AGREEMENTS, AS

APPLICABLE

By the closing date of this solicitation, if a company has acquired another company, the transferor and transferee company may claim credit for the same Service Channel Relevant Experience Projects under Section L.3.2.2, under the following condition:

In the event of a Government approved novation of a U.S. Federal contract from one Contractor to another, the transferor Contractor may claim credit for the above mentioned projects inasmuch as that contractor was awarded and assumed responsibility for that project up until the merger/acquisition while the transferee may claim credit for the same project in as much as that contractor has assumed responsibility for the totality of the project from the point of the merger/acquisition.

For any claimed evaluation element identifying a different name than that of the offeror; due to a merger, acquisition, novation, or change-of-name agreement; the offeror has the burden to establish that the claimed evaluation element should be attributed to the offeror. To do so, the offeror must provide evidence of the merger, acquisition, novation, or change-of-name agreement, as well as a justification demonstrating how the evaluation element being claimed is applicable to the offeror.

L.1.5 INVERTED DOMESTIC CORPORATIONS

Inverted Domestic Corporations are not eligible for award under this solicitation.

“Inverted Domestic Corporation”, as defined in FAR 52.209-10, means a foreign incorporated entity which is treated as an inverted domestic corporation under 6 U.S.C. 395(b), i.e., a corporation that used to be incorporated in the United States, or used to be a partnership in the United States, but now is incorporated in a foreign country, or is a subsidiary whose parent corporation is incorporated in a foreign country, that meets the criteria specified in 6 U.S.C. 395(b), applied in accordance with the rules and definitions of 6 U.S.C. 395(c). An inverted domestic corporation as herein defined does not meet the definition of an inverted domestic corporation as defined by the Internal Revenue Code at 26 U.S.C.7874.

L.1.6 PROPOSAL DUE DATE AND EMAIL ADDRESS

Unrestricted Pool: There will be no on-ramping in the Unrestricted Pool.

Restricted Pool: Proposals are due NLT 12:01PM ET on 16 September31 October 2019.

Proposals shall be emailed to: ONEOIT@sec.gov

L.1.7 SOLICITATION QUESTIONS

Interested parties shall utilize the file, Attachment 3 “OneIT Question Template,” provided with the RFP to organize and present any questions NLT 10:00AM ET on 18 August 2019, directing them to the ONEOIT@sec.gov email address, otherwise questions might not be received and/or considered. The Government reserves the right to respond or not respond to questions, and to consolidate similar questions.

Please thoroughly review the solicitation in its entirety, including all attachments, prior to submitting questions.

The official location for responses to questions is an attachment associated with this solicitation on www.fbo.gov.

The Government will not provide acknowledgement notices for the receipt of questions submitted.

L.2 PROPOSAL FORMAT

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 maximum allowable file size for email submissions is 10MB. The email Subject Line shall include: OneIT 50310219R0016 - NAME OF THE OFFEROR. The proposal submission should be in one email unless it exceeds the maximum allowable file size for email submission. In this case, the Offeror shall clearly denote in the subject line the Volumes and the number of emails for the proposal submission: OneIT

50310219R0016 - NAME OF THE OFFEROR - VOLUME X - EMAIL Y OF Z.

All proposal documents shall be in Adobe (pdf) format except for Attachment 12 - Pricing Worksheet and Attachment 14 Document Verification and Self Scoring Worksheet (Restricted. The Document Verification and Self Scoring Worksheet and Pricing Worksheet shall be in Microsoft Office Excel format.

The Offeror’s proposal shall be formatted into six (6) separate zipped electronic folders (in the .zip extension) by Volume Number and Title as follows:

Volume 1 – General Volume 2 – Relevant Experience Volume 3 – Past Performance for Relevant Experience Projects Volume 4 – Certifications Volume 5 – Risk Assessments Volume 6 – Price

Folder naming convention: NAME OF THE OFFEROR –VOLUME X

Small Business Offerors proposing as part of a contractor teaming arrangement, in accordance with the requirements of L.3.1.3, may submit separate submissions for Volume 2 – Relevant Experience (when sensitive or proprietary information is contained within required documents) and Volume 3 – Past Performance for Relevant Experience Projects to ONEOIT@sec.gov if required by the team member. The email body shall include the Solicitation Number 50310219R0016, Volume Number (2 and 3), Name and DUNS Number of the Offeror, along with the Name and DUNS Number of the Team Member submitting the documents. The email

Subject Line shall include: OneIT 50310219R0016 - NAME OF THE OFFEROR - NAME OF THE

SUBMITTING TEAM MEMBER.

L.2.1 PROPOSAL FORMAT TABLE

The following Proposal Format Table is to assist Offerors in organizing their proposal submission documents to ensure the government can easily identify which documents apply to which criteria for evaluation purposes.

Offerors must adhere to the Volume Numbers, Format and/or Templates, and Page Limitations (if any) provided in the Proposal Format Table. Offerors must include their company name or company name abbreviation and Volume Number in the filename. For example, the filename for the SF-33 submitted by XY Incorporated under Volume 1 would be “XY.VOL1.SF33.pdf.” If Relevant Experience Projects are submitted by a subcontractor/team member, the filename shall include the names of both companies. For example, if subcontractor/team member AB Incorporated submits relevant experience projects for XY Incorporated, the filename would be as follows: XY.AB.VOL2.REP.SC1.Pr1.pdf.

VOL

SEC # TITLE FORMAT/

TEMPLATE

PAGE LIMIT EXAMPLE FILE NAME

1 L.3 Cover Page/Letter

Cover Page/Letter to include Company POC information (only include in Volume 1)

Free Format

One (1) page for the Cover Page

Cover Page is not included in the page count for Volume 1

XY.VOL1.CP.pdf

1 L.3 Table of Content for all 6 volumes

Free Format

Content of each Volume

No page limit for the Table of Content

Table of Content is not included in the page count for each Volume

XY.VOL1.TOC.pdf

XY.VOL2.TOC.pdf

XY.VOL3.TOC.pdf

XY.VOL4.TOC.pdf

XY.VOL5.TOC.pdf

XY.VOL6.TOC.pdf

1 L.3.1.1 SF 33

SF30

SF 33

SF30

Limited to SF 33 and SF30 amendments in one single pdf

XY.VOL1.SF33SF30.pdf

1 L.3.1.2 Document Verification and Self Scoring Worksheet

Attachment 14 (Restricted)

Limited to the template (one (1) per proposal submission from Prime Offeror).

No page limitation.

XY.VOL1.SelfScoringWorks heet.xls (required) and XY.VOL1.SelfScoringWorks heet.pdf (optional)

1 L.3.1.3.1 Joint Venture or Partnership Agreement

Font type and size 10 to 12 point

No page limitation. If not submitting a JV, XY.VOL1.JV.pdf no file need be submitted

1 L.3.1.3.2 Subcontractor Letter(s) of Commitment, if applicable

See L.3.1.3.2 No page limitation.

The submission is limited to the requested information in L.3.1.3.2 If not submitting with proposed subcontractors, no file need be submitted.

Must be submitted if claiming points for Small Business Participation (L.3.5.34)

XY.AB.VOL1.SubLOC1.pdf XY.CD.VOL1.SubLOC2.pdf

1 L.3.1.4

L.3.1.3.2

Representations and Certifications

Representations and Certifications

- Subcontractor

Submit Section K Limited to Section K.

No page limitation

Limited to Section K.

No page limitation, if not proposing with subcontractors, no file need be submitted

XY.VOL1.RC.pdf

XY.AB.VOL1.RC.pdf

1 J

Non-Disclosure Agreement – Contractor Entity

Attachment 5 Limited to the NDA – Contractor Entity

Complete and Signed Non-Disclosure Agreement for the Company ONLY

XY.VOL1.NDA.pdf

2 L.3.2

Relevant Experience Projects

Documents shall be submitted in the following order:

1. Attachment 16, Relevant Experience Project Template

2. Email Notification to CO if CO signature is unattainable

Relevant Experience Verification Document limited to template space provided; narrative limited:

-SC 1: 12 pages -SC 2: 6 pages -SC 3: 4 pages -SC 4: 6 pages -SC 5: 12 pages

XY.VOL2.REP.SC1.Pr1.pdf XY.VOL2.REP.SC1.Pr2.pdf XY.VOL2.REP.SC1.Pr3.pdf

XY.VOL2.REP.SC2.Pr1.pdf

Or

XY.AB.VOL2.REP.SC1.Pr1.

pdf

Etc.

3. CPAR if period of performance less than one year and that period of performance is complete

Supporting Information Related to a Merger, Acquisition, Novation, or Change of Name, if applicable

-SC 6: 6 pages -SC 7: 4 pages

12 font

No Page limitations for supporting documents

XY.VOL2.REP.SC1.Pr1.CO Email.pdf

Etc.

XY.AB.VOL2.REP.SC1.Pr1.

CPAR.pdf

(Where “SC” = Service Channel, and “Pr” = Project)

3 L.3.3

Past Performance for Relevant Experience Projects

1. Same projects submitted for Relevant Experience

2. Documents shall be submitted in a single .pdf per Service Channel in the following order:

1. Attachment 17, Past Performance Relevant Experience Form and

2. Email Notification to CO if CO signature is unattainable

Supporting Information Related to a Merger, Acquisition, Novation, or Change of Name, if applicable

Template limited to space provided; 12 font

No Page limitations for supporting documents

XY.VOL3.PP.SC1.pdf XY.VOL3.PP.SC2.pdf XY.VOL3.PP.SC3.pdf

Or

XY.AB.VOL3.PP.SC1.pdf

XY.VOL3.PP.SC1.COEmail.

pdf

Or

XY.AB.VOL3.PP.SC1.COE

mail.pdf

4 L.3.4 Certifications Copy of Certification Body

Limited to verification requirements (NTE 1

XY.VOL4.ISO9001.pdf XY.VOL4.ISO20000.pdf verification/appro val page per certification) and for POC information, page numbers and paragraph references (NTE 1 page per certification). If not including certifications, no files need be submitted.

XY.VOL4.ISOIEC27000.pdf

4 L.3.4 CMMI Appraisal

Copy of Appraisal verification/appro val

Limited to verification requirements:

1) Published Appraisal results or 2) the Appraisal Disclosure Statement (ADS) and a Final Findings Report.

POC information, page numbers and paragraph references (NTE 1 page). If not including appraisal, no files need be submitted.

XY.CMMI.pdf

5 L.3.5.1 Risk Assessment, Number of Service Channels Covered

Based on documentation submitted under Relevant Experience

No additional submission is required

5 L.3.5.2 Risk Assessment, Multiple Award Contracts

Award Forms with FPDS Records that reflect Multiple Award contracts

Limited to two (2) Award Forms with respective FPDS Record

XY.VOL5.TO1.pdf

XY.VOL5.TO1.FPDS.pdf

XY.VOL5.TO2.pdf

XY.VOL5.TO2.FPDS.pdf

5 L.3.5.3 Risk Assessment, Small Business Participation

Attachment 18 Small Business Participation Commitment Document

Restricted Only

Limited to the Small Business Participation Commitment Document

XY.VOL5.SBPCD.pdf

L.3 PROPOSAL CONTENT

All projects as defined in Section L.3.2.1 and past performance for relevant experience submitted in response to this solicitation shall have been performed as follows:

For the restricted pool:

Projects and past performance for relevant experience can be submitted by:

- The Prime Offeror (or Joint Venture Team Member that is part of the Prime Offeror) as the prime or subcontractor on the prior project. For instance, if company XY, Inc. is the Prime Offeror under OneIT, then they must submit relevant experience wherein the company XY, Inc. performed as the prime contractor or as a substantive subcontractor on the prior project.

- A OneIT Subcontractor as the prime contractor on the prior project. Projects performed by a OneIT Subcontractor as a Subcontractor on the prior project will not be accepted.

“Prime Contractor” means the Contractor has privity-of-contract with the Government for all contractual obligations under a mutually binding legal relationship with the Government. In other words, when the Government awards a Contract to a Contractor, the Contractor is considered the “Prime Contractor.” For example, “Prime Contractors” are identified as such on the cover page of contracts or task orders such as:

● Standard Form (SF) 1449 – Solicitation/Contract/Order for Commercial Items – (Block 17a identifies the Prime Contractor)

● SF 26 – Award/Contract – (Block 7 identifies the Prime Contractor)

● SF 33 – Solicitation, Offer, and Award – (Block 15A identifies the Prime Contractor)

● Department of Defense (DD) 1155 – Order for Supplies or Services (Block 9 identifies the Prime Contractor)

● Optional Form 307 – Contract Award (Block 7 identifies the Prime Contractor)

● GSA Form 300 – Order for Supplies and Services (Block 6 identifies the Prime Contractor)

● Commercial Award Form (Must explicitly identify the Prime Contractor, Awarding Entity, the Effective Date, and the date the Authorized Representative signed)

When a Prime Contractor awards a contract to a Contractor, the Contractor is considered a “Subcontractor.”

Projects and Past Performance for Relevant Experience Submission Overview:

Restricted Pool Prime Offeror/

JV Team Member Offeror (prior effort as Prime)

Prime Offeror/JV Team Member Offeror (prior effort as Subktr)

Proposed Subcontractor (prior effort as Prime)

Proposed Subcontractor (prior effort as Subktr)

6 L.3.6 Pricing Pricing Template Pricing: Limited to the Pricing template Attachment 12

XY.VOL6.PRICE.xlsx

Credit for Channel Experience/Past Performance

YES YES YES NO

Certifications YES N/A YES N/A Number of Service Channels Covered YES NO NO NO Experience Multiple Award Vehicles (such as IDIQ)

YES NO NO NO

Small Business Participation Plan YES N/A N/A N/A

L.3.1 VOLUME 1 – GENERAL

To be eligible for award, the Offeror must adhere to the directions and submit the following information under Volume 1 – General.

L.3.1.1 STANDARD FORM (SF) 33

“Offeror” means the official legal bidding entity identified in Block 15A on the Standard Form (SF) 33, Solicitation, Offer and Award.

Using the SF 33 form, Solicitation, Offer and Award, posted as page 1 of the solicitation in http://www.fbo.gov, the Offeror shall fill out blocks 12 through 18 accordingly;

1. The Government requires a minimum acceptance period of not less than 180 calendar days. The Offeror shall complete Block 12 of each SF 33 submitted with full cognizance of the minimum acceptance period of 180 calendar days. "Acceptance Period” means the number of calendar days available to the Government for awarding a Contract from the date specified in this solicitation for receipt of offers. Your offer may only specify a longer acceptance period than the Government's minimum requirement.

2. If any amendments to the solicitation are issued, the Offeror must acknowledge each amendment number and date in Block 14 of the SF 33 or complete Blocks 8 and 15 of the SF 30 for each amendment.

3. The Offeror’s Legal Name and Address in Block 15A on the SF33 must match the information for the Offeror in SAM.GOV at http://www.sam.gov, including the corresponding Commercial and Government Agency (CAGE) Code Number and Data Universal Numbering Systems (DUNS) Number (Note: the address listed in Block 15A will be the official mailing address used by the Government for letter correspondence, if necessary).

4. The Name, Title, Signature and Date identified in Block 16, 17, 18, must be an authorized representative with authority to commit the Offeror to contractual obligations. Offers submitted in the name of a Joint Venture must be signed in accordance with the terms and conditions specified in the joint venture agreement as evidenced in the proposal.

5. Failure to comply with any of the instructions contained in this solicitation may result in the proposal being removed from consideration for award.

L.3.1.2 DOCUMENT VERIFICATION AND SELF SCORING WORKSHEET

The Offeror shall submit Attachment 14 titled, “Document Verification and Self Scoring Worksheet.” No other format or additional proposal documentation will be considered.

1. Do not alter rows, columns, or formulas of the Document Verification and Self Scoring Worksheet.

2. The Offeror shall enter their name in Cell BC4.

3. The Offeror must select the box in Column E for each applicable scoring element being claimed unless otherwise stated.

4. If the Offeror selected the box in Column E, the Offeror shall enter the file name in Column H (Technical Narrative Reference) for each associated supporting document submitted. Reference the file naming structure provided in L.3.1, Proposal Format Table, e.g. XY.VOL2.REP.SC1.Pr1.pdf or XY.AB.VOL2.REP.SC1.Pr1.pdf for a teaming partner. Points will not be validated if a filename is not provided in Column H.

L.3.1.3 CONTRACTOR TEAMING ARRANGEMENT, IF APPLICABLE

Contractor teaming arrangement (CTA) means an arrangement in which –

1. Two or more companies form a partnership or joint venture to act as a potential prime contractor; or

2. A potential prime contractor agrees with one or more other companies to have them act as its subcontractors under a specified Government contract or acquisition program.

L.3.1.3.1 PARTNERSHIP OR JOINT VENTURE, IF APPLICABLE

Two or more companies may form a partnership or joint venture, hereafter referred to as a joint venture, to submit a proposal in the restricted pool in response to this solicitation.

Each offeror is responsible for compliance with the SBA's regulations on joint ventures and size status, including regulations pertaining to 8(a) joint ventures, HUBZone joint ventures, and mentor-protégé joint ventures, when applicable. Provide copies of all applicable signed joint venture agreements.

Offerors submitting as a Joint Venture in the restricted pool may submit a proposal under this solicitation subject to the following conditions:

1. The Joint Venture itself and all members of the Joint Venture must be registered in SAM.GOV and have a corresponding DUNS Number.

2. The Joint Venture meets the definition of a Joint Venture for size determination purposes (FAR 19.101(7)(i)).

3. A Joint Venture shall submit elements identified in Section L.3, Volumes 1 through 6 as follows:

Volume 1 - The Joint Venture must fill out and submit the Representations and Certifications in

Section K. Each member of the Joint Venture must also submit their individual Representations and Certifications in Section K. All other elements submitted for Volume 1 must be in the name of the joint venture.

Volume 2 – Relevant experience projects may be in the name of the Offeror (or JV member) as the

Prime or Subcontractor on the prior project (or in the name of any proposed Subcontractor as the Prime on the prior project).

Volume 3 – Past performance relevant experience examples may be in the name of the Offeror

(or JV member) as the Prime or Subcontractor on the prior project (or in the name of any proposed Subcontractor as the Prime on the prior project).

Volume 4 – Any certifications claimed within section L.3.4 may be in the name of the Prime Offeror (or JV member) or in the name of any proposed subcontractor.

Volume 5 – Risk assessment elements may be in the name of the Offeror as the Prime on the prior project or in the name of an individual member of the joint venture as the Prime on the prior project.

Volume 6 – The cost/price proposal shall be for the joint venture, not individual members.

4. The Offeror must submit a complete copy of the Joint Venture agreement between the Prime Offeror joint venture members, that includes the information required in 13 C.F.R. 125.8(b).

5. Additionally, if not already included in the agreement, the Offeror must submit with the Joint Venture agreement supplemental information addressing the below items:

Clearly identifies the entities which make up the joint venture, including disclosure of the primary point of contact and DUNS Number for each of the members.

Addresses the circumstances and procedures for replacement of joint venture members, including the managing venturer. The JV agreement or supplemental document should address that in order to replace members, including the managing venturer, Government approval is required.

Addresses the duration of the Joint Venture, including when it became effective, when it expires, and the basis for termination.

Signature by a Corporate Officer/Official for each member of the joint venture accepting all terms of the agreement.

Failure to provide the Government with the requested documentation establishing the joint venture will be considered a material nonconformity and will result in the Offer being rejected.

L.3.1.3.2 PROPOSED SUBCONTRACTORS, IF APPLICABLE

An Offeror may agree with one or more other companies to have them act as its subcontractors.

Offerors submitting a proposal that includes proposed subcontractors may submit a proposal under this solicitation subject to the following conditions:

1. The offeror and all proposed subcontractors must be registered in SAM.GOV and have a corresponding DUNS Number.

2. An offeror with proposed subcontractors shall submit elements identified in Section L.3, Volumes 1 through 6 as follows:

Volume 1 – The Offeror must fill out and submit the Representations and Certifications in

Section K. Each proposed Subcontractor must also submit their individual Representations and Certifications in Section K. All other elements submitted for Volume 1 must be in the name of the Offeror.

Volume 2 – Relevant experience projects may be in the name of the

Offeror (or JV member) as the Prime or Subcontractor on the prior project or in the name of any proposed Subcontractor as the prime on the prior project.

Volume 3 – Past performance relevant experience examples may be in the name of the Offeror (or JV member) as the Prime or Subcontractor on the prior project or in the name of any proposed subcontractor as the Prime on the prior project.

Volume 4 – Any certifications claimed within section L.3.4 may be in the name of the Prime Offeror (or JV member) or in the name of any proposed subcontractor.

Volume 5 – Risk assessment elements may only be in the name of the Prime Offeror (or JV member) as the Prime on the prior project.

Volume 6 – The cost/price proposal shall be for the Offeror. Specific subcontractors and separate subcontractor pricing shall not be included in the cost/price proposal.

3. The offer must submit a Subcontractor Letter of Commitment for each proposed subcontractor (to include proposed small business subcontractors in the Small Business Participation Plan). The Government has the right to accept those letters of commitment at face value. The intended use of such letters is to permit Government validation of any subcontractor experience or past performance an offering prime identifies in response to this solicitation. The information identified below is required for any Subcontractor Letter of Commitment. No other information will be considered from any Letters of Commitment. The Government will not consider experience or past performance from subcontractors identified by offerors for which there is not a conforming Subcontractor Letter of Commitment. Each Subcontractor Letter of Commitment must include the following information:

a. A statement of commitment by the proposed subcontractor to support the offeror in performance of OneIT task orders;

b. A statement by the proposed subcontractor authorizing use of their relevant experience and past performance in support of the offering prime contractor’s proposal;

c. A statement of understanding that at least 50 percent of the cost of contract performance incurred for personnel shall be expended for employees of the concern in accordance with FAR 52.219-14. It is the intent of the SEC to consider all closed, active and potentially awarded task orders under OneIT in determination of the most accurate percentage labor totals for the proposed team;

d. Offering prime contractor’s legal name and DUNS number

e. Proposed subcontractor’s legal name and DUNS number;

f. Name, phone number, and email address of the subcontractor’s representative able to commit the subcontractor and validate the letter’s content; and

g. Signatures of a Corporate Officer/Official for both the Offeror and proposed subcontractor.

Identification of proposed subcontractors does not result in approval of them for any particular task order; rather it addresses this evaluation factor. Approval of subcontractors will still be needed on individual task orders in accordance with SEC 6004.00 Approval of Subcontracts.

L.3.1.4 REPRESENTATIONS AND CERTIFICATIONS

The Offeror shall complete and submit all Representations and Certifications in accordance with the instructions in Section K.

L.3.2 VOLUME 2 - RELEVANT EXPERIENCE

Relevant Experience is divided into seven Service Channels.

Service Channel 1: Application Development and Management (PLATFORM) Service Channel 2: Business Solutions Delivery (NON-PLATFORM) Service Channel 3: IT Infrastructure Operations and Management Service Channel 4: Information Security Service Channel 5: Data Management Service Channel 6: IT Governance Service Channel 7: Technology Business Management

The Offeror shall submit documents and attach verification documents in accordance with L.3.2 by utilizing Attachment 16, “Relevant Experience Project Template.” Any other format will be rejected as a material non-conformity. The Offeror must substantiate all the information through one of the verification methods identified in Section L.3.2.2.1.1.

L.3.2.1 RELEVANT EXPERIENCE PROJECTS

A Relevant Experience “project” is defined as (1) a single contract (excluding master Indefinite Delivery contracts, Blanket Purchase Agreements (BPAs), Basic Ordering Agreements, and other agreements that do not obligate the seller to furnish supplies or services); (2) a single task order awarded under a Multiple Award contract (as defined below); (3) a single task order awarded under a master Single-Award Indefinite Delivery task order contract (Definite Quantity, Requirements, or Indefinite Quantity contract) in accordance with FAR 16.5; (4) a single task order placed under a Federal Supply Schedule contract in accordance with FAR 8.405-2;

or (5) a single task order placed under a master BPA in accordance with FAR 8.405-3. When an Indefinite Delivery task order contract or a BPA’s requirements are well defined, for a specific purpose, and task orders are issued on a recurring basis, a collection of task orders placed under such a contract or BPA may be combined and submitted as a single project. This must be clearly identified in Attachment 16, “Relevant Experience Project Template” by annotating the Indefinite Delivery Contract or BPA number as well as all applicable task order numbers. A project can be used to demonstrate experience across multiple Service Channels.

A “Task Order” is defined as an order for services placed against an established contract.

A combination of U.S. Federal Government and Non-Government (commercial) projects awarded from the private sector can be submitted:

Project work can be performed by either the Prime Offeror (or JV member) as the prime or subcontractor on the prior project or by the proposed Subcontractor as the Prime on the prior project.

L.3.2.2 SERVICE CHANNEL RELEVANT EXPERIENCE

Using the Relevant Experience Project Template, in accordance with the instructions herein:

The Offeror can submit up to a maximum of twenty-five (25) Projects, performed by either (i) the Prime Offeror as the prime or subcontractor on the prior project, or (ii) a proposed subcontractor as the prime contractor on the prior project. If the Prime Offeror submits a project for which the Prime Offeror performed as a subcontractor, the verification signature block in the Relevant Experience Project Template must be signed by the prime contractor on the prior contract as the Corporate Official, as the Government has no privity of contract.

The submitted Service Channel relevant experience shall meet the following minimum conditions:

1. Each project must have included significant performance of the type of work covered by the claimed scoring element for which it is being provided. The performance of the work demonstrating experience with the claimed scoring element must have been integral to the performance of the project; projects where the relied upon performance was ancillary to the overall project are excluded (such as the services provided by a Value-Added- Reseller of Hardware or Software). Additionally, the overall project must have been primarily for IT services, as opposed to a project that included small or limited amounts of IT services as part of a larger non-IT project.

The demonstrated experience must satisfy the scoring element. Additionally, the requirement of each scoring element must be understood within the context of its particular Service Channel. (E.g. “End user Application Support” under Service Channel 1 is different than “End User and Customer Support” under Service Channel 3).

2. A single project can be used to demonstrate experience across multiple Service Channels. If a project covers relevant experience areas of more than one Service Channel, one Attachment 16 shall be submitted under each of these Service Channels to substantiate the experience relevant to this particular Service Channel only. A signature by the verifying authority will be required for each of the Attachments submitted. E.g., a project covers certain tasks under Service Channel 1 and Service Channel 2: Two Attachments 16 shall be submitted;

one to substantiate the relevant experience under Service Channel 1 and one to substantiate the relevant experience under Service Channel 2. Each submission will count towards the maximum number of references per service channel.

3. Column H in the Self Scoring Worksheet may reference only one (1) Relevant Experience Project per scoring element. If multiple Relevant Experience Projects are listed, only the first one will be validated.

4. The maximum number of reference projects that may be submitted for each Service Channel is as follows, and the Maximum Number of Points are based on the Self-Scoring Worksheet:

Service Channel Maximum

Number of References

Maximum Number of Points (Restricted)

1- Application Management and Development (PLATFORM) 6 2,000 2 - Business Solutions Delivery (NON-PLATFORM) 3 1,700 3 - IT Infrastructure and Operations Management 2 1,800 4 - Information Security 3 1,875 5 - Data Management 6 1,300 6 - IT Governance 3 1,600 7 - Technology Business Management 2 1,000

The project(s) shall be the same for Relevant Experience and Past Performance for Relevant Experience.

5. Each Service Channel Relevant Experience Project must be ongoing or have been completed within three (3) years from the date proposals are due. The Offeror must have completed at least one (1) year of performance for each project/contract unless one of the following situations exist:

a. The project has an Interim or a Final CPAR record. If relying on this exception, the Interim or Final CPAR record must be submitted with Attachment 16, Relevant Experience Project Template, in a single .pdf document.

b. The project had a base period of performance less than one year and that period of performance is complete.

If relying on this exception, the base period of performance must be clearly identified on Attachment 16 in addition to listing the overall period of performance.

Offerors must use the original proposal due date 16 September 2019 for the requirement that projects must be ongoing or have been completed within three (3) years from the date proposals are due. Offerors may use any extended proposal due date for the requirement that projects/contracts must have completed at least one (1) year of performance.

L.3.2.2.1 SERVICE CHANNEL RELEVANT EXPERIENCE PROJECT SUBMISSION

For each Service Channel claimed, Offerors must submit the information required in Attachment 16, Relevant Experience Project Template.

L.3.2.2.1.1 VERIFICATION OF SERVICE CHANNEL EXPERIENCE SUBMISSION

The maximum number of projects that may be submitted for each Service Channel are as follows:

Service Channel Maximum Number of

References 1- Application Management and Development (PLATFORM) 6 2 - Business Solutions Delivery (NON-PLATFORM) 3 3 - IT Infrastructure and Operations Management 2 4 - Information Security 3 5 - Data Management 6 6 - IT Governance 3 7 - Technology Business Management 2

In order to receive points associated with each Relevant Experience Project, Offerors must provide verification as follows:

Attachment 16, Relevant Experience Project Template must be completed as follows:

a) For a U.S. Federal Government project for which the Prime Offeror (or JV Member) or Proposed Subcontractor was a Prime on the prior project, the completed Relevant Experience Project Template must be signed by a Contracting Officer (CO) with cognizance over the submitted project. The citation must include the CO’s point-of-contact information (POC) that includes direct telephone number and direct email address.

If access to the Contracting Officer is unattainable, the Government will accept the signature of the

Contracting Officer’s Representative (COR) or Federal Program Manager (PM) directly associated with the project provided both of the following are submitted:

(1) The COR/Federal PM and the CO’s point-of-contact information (POC) with direct telephone numbers and email addresses; and

(2) COR/Federal PM email notification to the CO with completed Attachment 16, Relevant Experience Project Template. This email notification to the CO is to provide verification that the CO was made aware of the COR’s/ Federal PM’s concurrence with the Relevant Experience Project Template.

b) For a U.S. Federal Government project or Commercial (non-government) project for which the Prime Offeror (or JV Member) was a subcontractor to the project, the verification signatures in the Relevant Experience Project Template must be signed by a Corporate Official of the prime contractor on the prior project who has privity of contract for the submitted project.

If a OneIT Prime Offeror relies on its prior subcontracting experience in Attachment 16 and believes that the prime contractor on the prior project is withholding its validation or otherwise failing to cooperate to gain a strategic advantage on the OneIT acquisition, the OneIT Prime Offeror shall bring this fact to the attention of the Contracting Officer as soon as possible and include it in its proposal if the situation persists at that time. Under such circumstances, the Contracting Officer shall have the right to contact the prime contractor on the prior project to inquire, and may rely on alternative sources to validate the Prime Offeror’s prior subcontracting experience in the event validation is unfairly withheld by the former prime contractor. As a condition to competing on the OneIT acquisition, all Offerors and team members are required to cooperate and act in good faith if asked to validate Attachment 16 subcontracting experience of another OneIT Offeror. Failure to do so may be considered by the agency in its responsibility determination of the non-cooperating offeror or team member.

c) For a Commercial project (non-government) for which the Prime Offeror (or JV Member) or Proposed Subcontractor was a Prime on the prior project, the completed Relevant Experience Project Template, must be signed by a Corporate Officer/Official of the commercial entity with cognizance over the submitted project. The citation must include the Corporate Officer’s/Official’s point-of-contact information (POC) that includes direct telephone number and direct email address.

NOTE: If Attachment 16, Relevant Experience Project Template requires a signature for verification and is not signed by the appropriate party (or parties) as indicated throughout Section L, points shall not be earned. It is incumbent upon the Offeror to demonstrate their experience within the narrative in an easily recognizable manner to make verification and validation unambiguous and straightforward. If the Offeror includes internal headings within the Relevant Experience Project document for various scoring elements, the Government will rely on the relevant identified sections to validate each scoring element, and will not necessarily review sections identified by headings that appear to not be relevant to a particular scoring element. The Government has no obligation to conduct reference checks and may subtract claimed points if verification based on the submitted documentation alone is not possible.

NOTE: Foreign, state, and local government projects are not acceptable as relevant experience.

L.3.3 VOLUME 3 –PAST PERFORMANCE FOR RELEVANT EXPERIENCE PROJECTS

Past performance for relevant experience will be evaluated using projects submitted under L.3.2.2 Service Channel Relevant Experience. A past performance assessment shall be submitted for each relevant experience project submitted under L.3.2.2.

The maximum number of projects that may be submitted for each Service Channel are as follows:

Service Channel Maximum Number of

References 1- Application Management and Development (PLATFORM) 6 2 - Business Solutions Delivery (NON-PLATFORM) 3 3 - IT Infrastructure and Operations Management 2 4 - Information Security 3 5 - Data Management 6 6 - IT Governance 3 7 - Technology Business Management 2

Past Performance Relevant Experience projects shall be the same as the project submitted for Relevant Experience. A single past performance can be submitted for a project that covers more than one Service Channel. The Past Performance Relevant Experience projects shall be consolidated into one .pdf document per Service Channel. A single past performance can be submitted for a project that covers more than one Service Channel. If a single past performance is submitted for a project that covers more than one Service Channel, it shall be submitted in the consolidated .pdf document under each of the respective Service Channels. Acceptable forms of past performance assessments are detailed below in L.3.3.1 and L.3.3.2.

Projects must be ongoing or have been completed within three (3) years from the date proposals are due. The Offeror must have completed at least one (1) year of performance for each project/contract unless one of the following situations exist:

Offerors must use the original proposal due date 16 September 2019 for the requirement that projects must be ongoing or have been completed within three (3) years from the date proposals are due. Offerors may use any extended proposal due date for the requirement that projects/contracts must have completed at least one (1) year of performance. :

a. The project has an Interim or a Final CPAR record. If relying on this exception, the Interim or Final CPAR record must be submitted with Attachment 16, Relevant Experience Project Template, in a single .pdf document.

b. The project had a base period of performance less than one year and that period of performance is complete.

If relying on this exception, the base period of performance must be clearly identified on Attachment 17, Past Performance Relevant Experience Form, in addition to listing the overall period of performance.

Offerors must use the original proposal due date 16 September 2019 for the requirement that projects must be ongoing or have been completed within three (3) years from the date proposals are due. Offerors may use any extended proposal due date for the requirement that projects/contracts must have completed at least one (1) year of performance.

For the relevant past performance references, Offerors are strongly cautioned that inability of the Government to contact past performance references directly associated to any survey; or past performance information is not entered into the Past Performance Information Retrieval System (PPIRS) database; or project(s) are without a record of past performance, Projects without a record of past performance will not be rated favorably or unfavorably on past performance.the Offeror will not be evaluated favorably or unfavorably on past performance.

If qualifying CPAR information is available and is no older than one (1) year from date of proposal submission for any given relevant project, it shall be submitted for the Past Performance evaluation. Only in the event PPIRS qualifying CPAR information is not available or is older than one (1) year from date of proposal submission will an Offeror be allowed to substitutesubmit a Past Performance Relevance Experience Form similar to the CPARS format Part III of Attachment 17, Past Performance Relevant Experience Form in lieu of the CPAR record. If PPIRS information is available and is no older than one (1) year from date of proposal submission for any given relevant project, it shall be submitted for the Past Performance evaluation.

L.3.3.1 PAST PERFORMANCE (PPIRS CPAR INFORMATION EXISTS AND IS LESS THAN ONE

(1) YEAR OLD)

If the Government has qualifying interim or final ratings in PPIRSCPARS, the Offeror shall provide submit a copy of this ratingthe CPAR record with their proposaltogether with Parts I and II of Attachment 17. The CPAR shall be attached in lieu of completing Part III. For ongoing projects, a qualifying CPAR is one that is less than one (1) year old as of the date of proposal submission.