GEMS 2.0

Revised 10/12/18 1 of 5 SPD-PS014

State of Georgia State Entity: Georgia Technology Authority – EPMO

Request for Information

Event Name: RFI GEMS 2.0

RFI (Event) Number: 98000-GTA-EPMO-RFI-FY22-201

1. Introduction

1.1. Purpose of Procurement

This Request for Information (“RFI”) is being issued to solicit information from interested suppliers with respect to the Georgia Enterprise Management Suite (GEMS) 2.0, for the Georgia Technology Authority’s

(GTA) – Enterprise Portfolio Management Office (EPMO) (hereinafter, “the State Entity” or “GTA - EPMO”) as further described in this RFI. GTA - EPMO will use the information generated by this RFI in conjunction with other information available to GTA - EPMO to determine the solution that it is in the best interests of GTA - EPMO to fulfill this need.

The EPMO supports the technology investment decisions of State of Georgia agencies from idea to implementation and project archival currently using manual, disparate tools that contain static data. The EPMO is seeking information from suppliers who have the ability to architect a solution(s) across this Project Investment Lifecycle to optimize EPMO operations. Upon completion, this cloud-first approach called GEMS 2.0, will enable the EPMO to more efficiently track all technology project investment data collected, store, access, update and share this data as information in reporting and analytics dashboards, and position use of artificial intelligence to streamline workflows and predict project investment outcomes at scale.

Realizing that multiple responding suppliers to this RFI will have the capabilities that can address the EPMO’s use cases, we are seeking information on the ‘best fit’ solution in consideration of our existing licensing, collaboration, and document management systems. The ultimate success of GEMS 2.0 will be measured in the deployment of a forward-leaning ecosystem, (infrastructure, application suite, document repository, data management framework and reporting/analytics and dashboards) that is scalable and does not create technical debt from licensing duplicate IT solutions.

1.2. Overview of the RFI Process

The objective of the RFI is to gather information to assist GTA - EPMO in its consideration of available resources/methods to fulfill the need/goal identified above. The RFI method is not a competitive solicitation method and, as a result, does not satisfy the requirement for competitive bidding. The RFI method is no more than an information gathering tool and such information gathered may or may not be used by GTA -

EPMO to develop a competitive solicitation. Suppliers are not required to respond to an RFI and a supplier’s failure to respond to an RFI will not prohibit the supplier’s participation in any competitive solicitation that may result from the RFI. However, suppliers are strongly encouraged to respond to RFIs as this is a great way to ensure GTA - EPMO is aware of the suppliers’ available goods and services.

1.3. Schedule of Events

The schedule of events set out herein represents GTA - EPMO’s best estimate of the schedule that will be followed. However, delays to the procurement process may occur which may necessitate adjustments to the proposed schedule. If a component of this schedule, such as the close date, is delayed, the rest of the schedule may be shifted as appropriate. Any changes to the dates up to the closing date of the RFI will be publicly posted prior to the closing date of this RFI. After the close of the RFI, GTA - EPMO reserves the right to adjust the remainder of the proposed dates on an as needed basis with or without notice.

Revised 10/12/18 2 of 5 SPD-PS014

Description Date Time

Release of RFI As Published on the Georgia

Procurement Registry (“GPR”)

Supplier RFI Written Questions Due to GTA July 1, 2022 5:00 p.m. ET

GTA Responses to Supplier Written Questions

July 8, 2022 5:00 p.m. ET

Deadline for Submitting Responses July 15, 2022 See GPR

1.4. Official Issuing Officer (Buyer)

1.5. Nikki Tucker

procurement@gta.ga.gov

1.6. Definition of Terms

Please review the following terms:

Supplier(s) – companies desiring to do business with the State of Georgia.

State Entity – the governmental entity identified in Section 1.1 “Purpose of Solicitation” of this RFI.

2. Instructions to Offerors

By submitting a response to the RFI, the Offeror is acknowledging that the Offeror:

1. Has read the information and instructions,

2. Agrees to comply with the information and instructions contained herein.

2.1. General Information and Instructions

2.1.1. Team Georgia Marketplace™ Registration System

The Department of Administrative Services (“DOAS”) requires all companies and/or individuals interested in conducting business with the State of Georgia to register in the State’s web-based registration system, through Team Georgia Marketplace™. Registration is free and enables the registering company to gain access to certain information, services and/or materials maintained in

Team Georgia Marketplace™ at no charge to the registering company. All registering companies must agree to be bound by the applicable terms and conditions governing the supplier’s use of

Team Georgia Marketplace™. In the event DOAS elects to offer certain optional or premium services to registered companies on a fee basis, the registered company will be given the opportunity to either accept or reject the service before incurring any costs and still maintain its registration. Companies may register at https://fscm.teamworks.georgia.gov/psc/supp/SUPPLIER/ERP/c/NUI_FRAMEWORK.PT_LANDING

PAGE.GBL?&

2.1.2. Submitting Questions

All questions concerning this RFI must be submitted in writing via email to the Issuing Officer identified in Section 1.4 “Issuing Officer” of this RFI.

2.1.3. State’s Right to Amend and/or Cancel the RFI

GTA - EPMO reserves the right to amend this RFI. Any revisions must be made in writing prior to the RFI closing date and time. By submitting a response, the supplier shall be deemed to have accepted all terms and agreed to all requirements of the RFI (including any revisions/additions made in writing prior to the close of the RFI whether or not such revision occurred prior to the time the supplier submitted its response) unless expressly stated otherwise in the supplier’s response.

THEREFORE, EACH SUPPLIER IS INDIVIDUALLY RESPONSIBLE FOR REVIEWING THE

REVISED RFI AND MAKING ANY NECESSARY OR APPROPRIATE CHANGES AND/OR

ADDITIONS TO THE SUPPLIER’S RESPONSE PRIOR TO THE CLOSE OF THE RFI. Suppliers https://fscm.teamworks.georgia.gov/psc/supp/SUPPLIER/ERP/c/NUI_FRAMEWORK.PT_LANDINGPAGE.GBL https://fscm.teamworks.georgia.gov/psc/supp/SUPPLIER/ERP/c/NUI_FRAMEWORK.PT_LANDINGPAGE.GBL

Revised 10/12/18 3 of 5 SPD-PS014 are encouraged to frequently check the RFI for additional information. Finally, GTA - EPMO reserves the right to cancel this RFI at any time.

2.1.4. Costs for Preparing Responses

Each response should be prepared simply and economically, avoiding the use of elaborate promotional materials beyond those sufficient to provide a complete presentation. The cost for developing the response and participating in this RFI process is the sole responsibility of the supplier. The State will not provide reimbursement for such costs.

2.1.5. ADA Guidelines

The State of Georgia adheres to the guidelines set forth in the Americans with Disabilities Act.

Suppliers should contact the Issuing Officer at least one day in advance if they require special arrangements when attending the Informational Conference (if any). The Georgia Relay Center at

1-800-255-0056 (TDD Only) or 1-800-255-0135 (Voice) will relay messages, in strict confidence, for the speech and hearing impaired.

2.1.6. Public Access to Procurement Records

Solicitation opportunities will be publicly advertised as required by law and the provisions of the

Georgia Procurement Manual. GTA - EPMO is allowed to assess a reasonable charge to defray the cost of reproducing documents. A state employee should be present during the time of onsite inspection of documents. PLEASE NOTE: Even though information (financial or other information) submitted by a supplier may be marked as "confidential", "proprietary", etc., the State will make its own determination regarding what information may or may not be withheld from disclosure.

2.1.7. Registered Lobbyists

By submitting a response to this RFI, the supplier hereby certifies that the supplier and its lobbyists are in compliance with the Lobbyist Registration Requirements in accordance with the Georgia

Procurement Manual.

2.2. Submittal Instructions

Listed below are key action items related to this RFI. The Schedule of Events in Section 1.3 identifies the dates and time for these key action items. This portion of the RFI provides instructions regarding the process for reviewing the RFI, preparing a response to the RFI and submitting a response to the RFI.

2.2.1. RFI Released

The release of this RFI is formally communicated through the posting of this RFI on the Georgia

Procurement Registry, which is accessible online as follows:

http://ssl.doas.state.ga.us/PRSapp/PR_index.jsp

2.2.2. RFI Review

The RFI consists of the following:

1. This document, entitled “RFI - GEMS 2.0”,

2. “RFI - GEMS 2.0 Scope of Work”,

3. “RFI - GEMS 2.0 DETAILED Requirements”

4. Any and all documents provided by GTA - EPMO as attachments to the RFI or links contained within the RFI or its attached documents.

Please carefully review all information contained in the RFI, including all documents available as attachments or available through links. Any difficulty accessing the RFI or opening provided links or documents should be reported immediately to the Issuing Officer (See Section 1.4).

2.2.3. Preparing a Response

When preparing a response, the supplier must consider the following instructions:

1. Ensure its response is accurate and readily understandable.

http://ssl.doas.state.ga.us/PRSapp/PR_index.jsp

Revised 10/12/18 4 of 5 SPD-PS014

2. Clearly label attachments so that GTA - EPMO can easily organize and navigate the supplier’s response.

2.2.4. Electronic Copies Required

Supplier must provide one (1) emailed response to procurement@gta.ga.gov.

2.2.5. Electronic Copies

1. Use caution in creating electronic files (i.e., make sure files do not contain viruses, etc.).

2. Use commonly accepted software programs to create electronic files. GTA - EPMO has the capability of viewing documents submitted in the following format: Microsoft Word or WordPad, Microsoft Excel, portable document format file (PDF), and plain text files with the file extension noted in parentheses (.txt).

3. GTA – EMPO reserves the rights to reject any responses not in a readable format as listed above.

3. Requested Information

The Georgia Technology Authority (GTA) is seeking to provide more value to its stakeholders. This includes focusing on providing more transparency to valuable project investment information to State of Georgia agencies and citizens. One of many ways in which GTA plans to provide more value is through its own Enterprise Portfolio Management Office (EPMO).

The EPMO is interested in the following information:

Potential Supplier Capabilities:

For each of the following EPMO use cases, (Custom Business Applications, Business Workflow Automation & Collaborative App Dev), describe how your company address these capabilities:

1. Software Development Lifecycle (SDLC)- How does your company support professional developers in building applications faster?

2. User Experience Design- How does your company support the design, development and testing of user journeys, rich mobile and web interfaces, continuous user experience and other user interfaces?

3. Development Productivity- How does your company enable professional developers, citizen developers, business technologists or fusion teams to collaboratively develop applications?

4. Business Logic and Workflow- How does your company support the design, development and testing or simulation of stateful and stateless business processes; the choreography of human workflows, services, documents and user experiences; and the business logic for controlling processes and making business decisions?

5. Integration and APIs- How does your company support back-end integration with local and cloud services, service repositories and databases? How does it provide and manage application programming interface (APIs) for the external consumption of the data and business logic in applications built with the platform?

6. Platform Ecosystem- How does your company support developer ecosystems, including app stores, domain-specific data models and processes, user experience (UX) component and back-end service sharing, access to third-party assistance and training services?

7. Governance- How does your company support the governance of application development and deployment (including development metrics and KPIs) and meet deployed application SLAs for distributed professional developers, citizen developers and fusion teams?

8. Security and Quality of Service (QoS)- How does your company secure applications and data? How does the platform support service quality concepts such as scalability, low-latency practices, and disaster recovery, including global coverage of data centers?

Potential Supplier Experience:

With the following EPMO use cases in mind, (Custom Business Applications, Business Workflow Automation &

Revised 10/12/18 5 of 5 SPD-PS014

Collaborative App Dev), describe your firm’s experience on actual client projects:

1. Background- Please provide a summary of the history of your company/organization. Please limit response to no more than one page, maximum.

2. Implementation Examples- Based on examples of actual client implementations and feedback, list top three successes and why. Please limit response to no more than two pages, maximum.

3. Roadmap Vision- Please describe your company/organization’s future roadmap for Low Code

Application Platform (LCAP) capabilities, including Artificial Intelligence. Please limit response to no more than one page, maximum.

4. LCAP Clients- What percentage of your companies’ current clients have implemented your LCAP solution services and licensing?

5. Document Management- With your company’s current document management capabilities in mind, describe how your clients address satisfy document management requirements with your solution.

Where will our current documents have to be stored to leverage your document management solution? Please limit your response to one page.

6. Licensing- Using the “RFI - GEMS 2.0 Scope of Work” and “RFI - GEMS 2.0 DETAILED Requirements”

Excel spreadsheet as a basis, provide best estimate possible of the type and quantity of licensing required for GEMS 2.0.

7. Implementation Cost- Using the “RFI - GEMS 2.0 Scope of Work” and “RFI - GEMS 2.0 DETAILED

Requirements” Excel spreadsheet as a basis, provide best estimate possible of implementation costs for all requirements as well as those identified as Phase #1 for GEMS 2.0 separately.

8. Implementation Partners- Using the “RFI - GEMS 2.0 Scope of Work” and “RFI - GEMS 2.0

DETAILED Requirements” Excel spreadsheet as a basis, identify your preferred implementation partners to implement GEMS 2.0.

9. Implementation Timeline- How long will it take your company to implement a project like GEMS 2.0?

Would your company be available to begin before calendar year Q4 2022 (Fiscal Year Q2 2023)?

4. Additional Information

GTA - EPMO may, at its discretion, ask one or more suppliers to provide additional information and/or meet with GTA - EPMO to further discuss the supplier’s information.

5. List of RFI Attachments

The following documents make up this RFI. Please see Section 2.2.2 “RFI Review” for instructions about how to access the following documents. Any difficulty locating or accessing the following documents should be immediately reported to the Issuing Officer.

A. State Entity RFI, “RFI - GEMS 2.0” (this document) B. “RFI - GEMS 2.0 Scope of Work” C. “RFI - GEMS 2.0 DETAILED Requirements”