Hybrid Data Architects/Engineers

A. SUMMARY The Client is seeking proposals from prospective Offerors for two (2) Hybrid Data Architects/Engineers. The Hybrid Data Architects/Engineers will provide Data Warehouse Architect/Engineer services to serve as the primary resource(s) responsible for designing and building a data warehouse solution and working with conventional data warehouse technologies to devise plans that support designing data warehouse solutions in alignment with the Maryland Judiciary's initiatives. Offeror may propose no more than two (2) resources. Offeror shall propose resources for which they have the right to represent. If multiple Offerors propose the same resource, the Client reserves the right to make such investigations, as it deems necessary, to confirm the representation of anyproposed resources, and reject any Offeror's proposed resource. After any investigations, if the Client is unable to confirm the representation of any proposed resource, including a proposed resource who signed multiple right-to-represent letters, the Client reserves the right to reject the proposed resource from all applicable Offerors. B. BACKGROUND INFORMATION The Maryland Judiciary's Administrative Office of the Courts (Client) has a strategic initiative to establish comprehensive data warehousing and analytics capabilities. The initial source for a Data Warehouse (DW) will be the Maryland Electronic Court (MDEC) database which uses Tyler Technologies' Enterprise Justice software. However, the Judiciary will expand the Data Warehouse to other source systems after adding MDEC. The Maryland Judiciary intends to use Azure services for the data warehouse. There is a ne ed to store, process and manage large data sets in the cloud. The following two (2) foundational components below show a path to an integrated environment for advanced query and reporting capabilities for both internal and external needs: Foundational Component One The implementation of a statewide case management system which contains judicial records used by all courts in all jurisdictions, known as MDEC (Maryland Electronic Courts). This multi-year undertaking is implementing Tyler Technologies' Odyssey Case Management System. When complete, information on all cases across all courts in the state will be housed in this SQL Server database. This achievement will provide a single source of data which can be fed into a DW structure connected to data query, reporting, and analytics software tools. The Maryland Judiciary currently operates several case management systems, each defining and housing data differently. The conversion of these systems into Odyssey will be complete in May of 2024 and provide a base level of data source consistency from which to proceed. While this is the initial target data source, additional data sources may be identified. Foundational Component Two The emergence of a set of data standards for court data published by the National Center for State Courts (NCSC). Called National Open Court Data Standards (NODS), it provides naming and content standards for state court data. Adoption of NODS will facilitate more accurate interpretation of data provided by the courts. The Client has mapped the data from the MDEC User Interface screens to the NODS structure, which may serve as the base for developing a DW model understandable to non-technical users for analytics and reporting. C. OFFEROR & RESOURCE QUALIFICATIONS 1. The Offeror shall have one(1) year of experience in providing recruitment, staffing, and/or otherwise providing professional consulting services. D. SCOPE OF WORK Offeror proposed resource(s) shall be responsible for the following: 1. Participation in all aspects of DW and ETL process design, creation, and specification for components. 2. Providing the following services in coordination with technical, functional and management representatives from JIS and the Client. a. Source Data Model to DW Logical Design ERD (1) Understanding the general structure of the MDEC data and star schema models currently in use by JIS, and any related data sources identified as a result of initial planning and assessments. (2) Creating a logical warehouse data design. (3) Collaboration with platform administration team, design an ETL process to move data from the source system to the data warehouse, including, but not limited to, the following: i Outlining the ETL process, setting the borders of data processing. ii Providing system architecture for each element and the whole data pipeline. iii Documenting the requirements of the system, manage its development and facilitate necessary knowledge transfer. iv Assisting in the actual development/implementation of ETL tools. v Conducting testing of the tools and data pipelines.

b. DW Schema (1) Developing effective DW model(s) representing the data entities of the logical design based on functional analytic, reporting and bulk data requirements.

c. DW Physical Design (1) Collaborating with platform administration to assist their efforts in creating a DW Physical design including technical considerations for data quality and operational efficiency.

3. Collaborating with business and technology stakeholders to ensure data warehouse architecture development and utilization. 4. All work completed by the proposed resource(s) shall be completed within regulatory compliance standards to protect sensitive data. 5. Reporting as follows: a. Weekly progress report on programs and project, b. Weekly report communicating project progress and status, c. Weekly time reporting on JIS provided forms, and d. Any additional reports as assigned by the supervising manager.