Amendment #2

RFP # BPM044685

Agile Digital Experience Product Transformation (ADEPT)

July 15, 2024

This Amendment is issued to amend and clarify certain information contained in the above-referenced Request for Proposals (RFP). All information contained herein is binding on all Offerors who respond to this RFP. The following changes/additions are listed below; new language has been double underlined and marked in red bold (ex: new language) and language deleted has been marked with a strikeout (e.g., language deleted). COMAR 21.05.03 requires Offerors to acknowledge all amendments.

1. Table of Contents – RFP

Attachment O. DHS Hiring Agreement Attachment P. Prime Contractor List of All Subcontractors Appendix 1. – Abbreviations and Definitions ....................................................112 113 Appendix 2. – Offeror Information Sheet ..........................................................117 118 Appendix 3. – Digital Maturity Self-Score Matrix………………………….………….………118119 Appendix 4 – Labor Categories………………………………………………….………………….………120

2. The following attachment and appendix have been added to the RFP:

Attachment P. Prime Contractor List of All Subcontractors Appendix 4 – Labor Categories

3. Attachment B - Financial Proposal Form ADEPT – A revised Financial Proposal Form has been uploaded to eMMA that includes the revised job categories listed in Appendix 4.

4. Economic Benefit Factor requirements listed below have been removed from the RFP:

Section 5.3.2 K. Economic Benefit Factors (Submit under TAB J) (Page Limit: 2 pages, including tables & figures) This entire section has been removed.

Section 6.2.3 Economic Benefit to State of Maryland (See RFP § 5.3.2.K) This evaluation criterion has been removed from Section 6.2.

5. Section 1.1. Offeror Minimum Qualifications

To be considered reasonably susceptible for award, the Offeror must document in its Proposal that the following Minimum Qualifications have been met: The minimum qualifications required for consideration are designed to ensure that potential offerors possess the necessary expertise, experience, and maturity in digital services. Only those Offerors that meet all minimum qualification criteria shall be eligible for proposal evaluation. Offerors not satisfying each of the criteria below will be found not reasonably susceptible for award. Subcontractor qualifications cannot be used to meet minimum qualifications.

6. Minimum Qualifications, Section 1.1.1 Required Experience, Offerors must:

A. Possess at least three (3) years of experience in designing and developing plain language content, information architecture, website design, and development, as well as designing and implementing digital services applications and software for public sector customers a government entity (Federal, State, or Local) or similarly regulated industry. Accumulative knowledge will not be accepted.

7. Minimum Qualifications, Section 1.1.2 Required Documentation:

B. Submit artifacts for the Technical Qualifications tab in each of the categories listed in the columns in the Matrix sheet. to further demonstrate the scored capability. Artifacts may be submitted in various formats including but not limited to text files, PDF documents, or image files. However, artifacts must be in human-readable data formats; artifacts submitted in machine-readable formats (e.g., CSV, JSON, XML) will not be considered. Artifacts may include client deliverables, code (provided in a human-readable format), and/or screenshots. For example, Offerors may include a screenshot of a webpage or copy site code into a text file. Multiple screenshots may be submitted as a single artifact as long as they are related to a single case study. Artifacts may be attached to the TAB D (See RFP § 5.3.2.E) and do not count as part of the page limit. Artifacts may be submitted to eMMA in a zip file.

8. Minimum Qualifications, Section 1.1.2. C. Required Documentation: Provide three (3) references from the past five (5) years attesting to the Offeror’s experience in providing digital services within the scope of this solicitation. At least two (2) references must be from public sector customers a government entity (Federal, State, or Local) or similarly regulated industry.

9. Preferred Offeror Experience, Sections 3.11.1.A and 3.11.1B, Required Documentation

As proof of meeting this requirement, the Offeror shall provide with its Proposal:

1. At least three (3) references from the past five (5) years that are collectively able to attest to the Offeror’s required years of similar experience providing digital services. Reference information must include the following:

1. Name of client organization;

2. Name, title, telephone number, email address, of the point of contact for client organization; and

3. The total dollar value of the contract and/or business with the organization, type of contract, its duration, and a description of services provided.

10. Section 5.3.2. E Minimum Qualifications

Replace:

Section 5.3.2. E. Minimum Qualifications Documentation (Submit under TAB D) Minimum (Page Limit: 5 pages, including tables & figures):

The Offeror shall submit any Minimum Qualifications documentation that may be required, as set forth in RFP Section 1. If references are required in RFP Section 1, those references shall be submitted in this section and shall contain the information described in both Section 1.

With this:

Section 5.3.2. E. Minimum Qualifications Documentation (Submit under TAB D) (Page Limit: 5 pages, including references, tables & figures, list of artifacts with filename or link and which Dimension of Digital Maturity Self-Score Matrix it supports)

The Offeror shall submit any Minimum Qualifications documentation that may be required, as set forth in RFP Section 1. If references are required in RFP Section 1, those references shall be submitted in this section and shall contain the information described in both Section 1.

Artifacts may be attached to the TAB D and do not count as part of the page limit.

11. Appendix 3 - Digital Maturity Self-Score Matrix – A revised appendix has been uploaded to eMMA to reflect the following change listed below.

In the Technical Qualification tab cell A13 replace the following:

Supporting Artifacts (please include file name or link to submitted artifacts for each category.

With:

Supporting Artifacts may be attached to TAB D (See RFP 5.3.2.E) and do not count as part of the page limit.

12. Section 5.3.2.F., Offeror Response to RFP Requirements (Submit under TAB E) (Page Limit: 7 13 pages including tables and figures and index of artifacts with filename or link, which factor(s) artifact supports, and if the artifact comes from the prime offeror or subcontractor):

Section 5.2.3. F. 1, This section must encompass the following elements:

Offeror Qualifications and Capabilities: The Offeror shall include information on past experience with similar projects and services including information in support of the Preferred Offeror Experience criteria in Section 3.11.1. The Offeror shall provide a statement that describes how its organization can meet the requirements of this RFP to support the activities in 2.3.B, 2.3.1, and 2.3.2 and shall also include the following information: …

13. Section 5.3.F.7. Case Studies, Offeror Response to RFP Requirements (Submit under TAB E)

Offerors shall submit two (2) relevant case studies with at least one (1) case study from the prime.

Relevant case studies must demonstrate recent (within the past three (3) years) performance of tasks related to digital service or digital transformation efforts within the scope of this solicitation.

This must include but is not limited to: user research and user story collaboration, emerging technologies, agile software development, DevOps, DevSecOps, accessibility design, strategic marketing for digital transformation, cybersecurity related to digital transformation, or human centered design.

Case Studies shall demonstrate adherence to practices found within the Digital Services Playbook (https://playbook.cio.gov/).

Case Studies shall reflect work completed for Government clients a government entity (Federal, State, or Local) or similarly regulated industry.

Each Case Study submission is limited to two (2) three (3) pages. Page count should include a table of artifacts with file name or link, which factor(s) the artifact supports, and if the artifact comes from prime or subcontractor. No more than one project should be represented within a single Case Study.

14. Section 5.3.2, G. Financial Capability (Submit under TAB F) (Page Limit: 2 5 pages, including tables & figures)

15. Section 6.5.2.C.ii. Down-Select Procedure, Orals will be conducted consistent with Section 4.11 Section 4.10 for all Offerors proceeding to the oral presentation round. A technical ranking will be performed for all such Offerors. Orals will be ranked from highest to lowest for technical merit based on the quality of the oral presentation and interviews;

16. Section 5.3.2.I. Subcontractors (Submit under TAB H) (Page Limit: 2 pages, including tables & figures)

The Offeror shall provide a complete list of all subcontractors that will work on the Contract if the Offeror receives an award, including those utilized in meeting the MBE and VSBE subcontracting goal(s), if applicable. If applicable, subcontractors utilized in meeting the established MBE participation goal(s) for this solicitation shall be identified as provided in the appropriate attachment(s) of this RFP and include the teaming rationale and delineate the skill sets that will come from each of the subcontractors.

17. Section 7, Table 1: RFP ATTACHMENTS AND APPENDICES

Applies?

When to Submit Label Attachment Name

TBD at the Work Order Level

With Proposal

With Work Order G

Federal Funds Attachments (see link at http://procurement.maryland.gov/wp-http://procurement.maryland.gov/wp-content/uploads/sites/12/2018/04/AttachmentG-FederalFundsAttachment.pdf http://procurement.maryland.gov/wp-content/uploads/sites/12/2018/04/AttachmentG-FederalFundsAttachment.pdf http://procurement.maryland.gov/wp-content/uploads/sites/12/2018/04/AttachmentG-FederalFundsAttachment.pdf content/uploads/sites/12/2018/04/AttachmentG- FederalFundsAttachment.pdf)

The following row has been added to Table 1.

Applies?

When to Submit Label Attachment Name

Y With Proposal P Prime Contractor List of ALL Subcontractors procurement.maryland.gov/rfp/

18. Attachment G. Federal Funds Attachments

This Contract may contain Federal funds. The programmatic conditions per the link below hereto may apply in the event funding for a Work Order contains federal funding. Information regarding federal funding will be supplied in a Work Order request, as applicable.

See link at https://procurement.maryland.gov/wp-content/uploads/sites/12/2018/05/AttachmentH-Conflict-of-InterestAffidavit.pdf http://procurement.maryland.gov/wp-content/uploads/sites/12/2018/04/AttachmentG- FederalFundsAttachment.pdf

19. 5.3 Volume I - Technical Proposal

5.3.1 In addition to the instructions below, responses in the Offeror’s Technical Proposal shall reference the organization and numbering of Sections below in the RFP (e.g., “Section 2.2.1 Response . . .; “Section 2.2.2 Response . . .,”). (e.g., “Section 5.3.2.A Response . .; 5.3.2.B Response . .; 5.3.2.C Response . .; “S”). All pages of both Proposal volumes shall be consecutively numbered from beginning (Page 1) to end (Page “x”).

5.3.2 The Technical Proposal shall include the following documents and information in the order specified as follows.

The Technical Proposal shall be in Times New Roman font, 11-point, 8.5” x 11”, with 1” borders all around, and each section of the Technical Proposal shall be separated by a TAB as detailed below.

All Tables and Graphics shall be in Calibri font, 10-point.

http://procurement.maryland.gov/wp-content/uploads/sites/12/2018/04/AttachmentG-FederalFundsAttachment.pdf http://procurement.maryland.gov/wp-content/uploads/sites/12/2018/04/AttachmentG-FederalFundsAttachment.pdf https://procurement.maryland.gov/rfp/ https://procurement.maryland.gov/wp-content/uploads/sites/12/2018/05/AttachmentH-Conflict-of-InterestAffidavit.pdf https://procurement.maryland.gov/wp-content/uploads/sites/12/2018/05/AttachmentH-Conflict-of-InterestAffidavit.pdf http://procurement.maryland.gov/wp-content/uploads/sites/12/2018/04/AttachmentG-FederalFundsAttachment.pdf http://procurement.maryland.gov/wp-content/uploads/sites/12/2018/04/AttachmentG-FederalFundsAttachment.pdf

Note: If a Proposal exceeds the page limit requirements listed in the sections below, the Proposal will be evaluated only on the information in the pages that are within the required page limits. Any information presented beyond the required page limits will not be considered for evaluation.

20. Section 6.2 Technical Proposal Evaluation Criteria

6.2.2 Offeror Qualifications and Capabilities, including proposed subcontractors (See RFP § 5.3.2. E and G E and I)

21. Section 5.3.2, D. Executive Summary (Submit under TAB C) (Page Limit: 5 pages, including tables & figures)

The Offeror shall condense and highlight the contents of the Technical Proposal in a separate section titled “Executive Summary” and include the teaming rationale and delineate the skill sets that will come from the prime versus those from any subcontractor(s).

In addition, the Summary shall indicate whether the Offeror is the subsidiary of another entity, and if so, whether all information submitted by the Offeror pertains exclusively to the Offeror. If not, the subsidiary Offeror shall include a guarantee of performance from its parent organization as part of its Executive Summary (see Section 4.17 4.16 “Offeror Responsibilities”).

22. Attachment M. Contract, Section 4.1, second paragraph, the total payment under a fixed price Contract or the fixed price element of a combined fixed price – time and materials Contract shall be the firm fixed price submitted by the Contractor in its Work Order Financial Proposal submission.

23. VSBE Goal, Section 4.27 item 4.27.1 B, A certified Veteran-Owned Small Business Enterprises (VSBE) must be verified by the State Department of Veterans Affairs or US Department of Veteran’s Affairs Vets First Verification Program (VetBiz) and registered as a VSBE on the State's eProcurement platform, eMaryland Marketplace Advantage (eMMA). The listing of VSBEs is available through the “Vendor Search” on eMMA.

24. Section 3.17.3, page 41, Source Code Escrow

Source Code Escrow applies to the Contract. The Contractor shall perform source code escrow as described herein.

A. The State will be named as a beneficiary under an escrow agreement (“Escrow Agreement”) that shall be entered into between the Contractor and an escrow agent (“Escrow Agent”) within 60 days of the Contract Effective Date hereof pursuant to which Contractor shall deliver a Source Code Escrow Package to Escrow Agent. IF REQUIRED UNDER A WORK ORDER, the State will be named as a beneficiary under an escrow agreement (“Escrow Agreement”) that shall be entered into between the Contractor and an escrow agent (“Escrow Agent”) within 60 days of the WORK ORDER Date hereof pursuant to which Contractor shall deliver a Source Code Escrow Package to Escrow Agent. The term “Source Code Escrow Package” means: a) a complete copy in machine-readable form of the source code and executable code of the software licensed to the State under the Contract; b) a complete copy of any existing design https://emma.maryland.gov/page.aspx/en/usr/login?ReturnUrl=%2fpage.aspx%2fen%2fbuy%2fhomepage documentation and user documentation; and/or c) complete instructions for compiling and linking every part of the source code into executable code for purposes of enabling verification of the completeness of the source code as provided below. The Escrow Agreement shall govern the maintenance and release of the Source Code Escrow Package, and Contractor agrees to update, enhance, or otherwise modify such Source Code Escrow Package promptly upon each release of a new version of any component thereof.

Issued by:

Office of State Procurement Maryland Department of General Services 45 Calvert Street Annapolis, MD 21401 Hanta Ralay OSP-DGS Procurement Officer

25. Section 4.8.2 is revised as follows:

4.8.2 Offerors are advised that, upon request for this information from a third party, the Procurement Officer is required to make an independent determination whether the information must be disclosed. However, Offerors are also advised that the Department deems Offeror artifacts as confidential and proprietary, and Offeror information related to artifacts or samples provided in response to this RFP shall not be released in response to a PIA request.