A. SUMMARYThe Client is seeking proposals from prospective Offerors for two (2) Hybrid Data Architects/Engineers. TheHybrid Data Architects/Engineers will provide Data Warehouse Architect/Engineer services to serve as theprimary resource(s) responsible for designing and building a data warehouse solution and working withconventional data warehouse technologies to devise plans that support designing data warehouse solutionsin alignment with the Maryland Judiciary39;s initiatives.Offeror may propose no more than two (2) resources. Offeror shall propose resources for which they havethe right to represent. If multiple Offerors propose the same resource, the Client reserves the right to makesuch investigations, as it deems necessary, to confirm the representation of anyproposed resources, and rejectany Offeror39;s proposed resource. After any investigations, if the Client is unable to confirm the representationof any proposed resource, including a proposed resource who signed multiple right-to-represent letters, theClient reserves the right to reject the proposed resource from all applicable Offerors.B. BACKGROUND INFORMATIONThe Maryland Judiciary39;s Administrative Office of the Courts (Client) has a strategic initiative to establishcomprehensive data warehousing and analytics capabilities. The initial source for a Data Warehouse (DW)will be the Maryland Electronic Court (MDEC) database which uses Tyler Technologies39; Enterprise Justicesoftware. However, the Judiciary will expand the Data Warehouse to other source systems after addingMDEC. The Maryland Judiciary intends to use Azure services for the data warehouse. There is a ne ed tostore, process and manage large data sets in the cloud.The following two (2) foundational components below show a path to an integrated environment foradvanced query and reporting capabilities for both internal and external needs:Foundational Component OneThe implementation of a statewide case management system which contains judicial records used byall courts in all jurisdictions, known as MDEC (Maryland Electronic Courts This multi-yearundertaking is implementing Tyler Technologies39; Odyssey Case Management System. Whencomplete, information on all cases across all courts in the state will be housed in this SQL Serverdatabase. This achievement will provide a single source of data which can be fed into a DW structureconnected to data query, reporting, and analytics software tools. The Maryland Judiciary currentlyoperates several case management systems, each defining and housing data differently. Theconversion of these systems into Odyssey will be complete in May of 2024 and provide a base levelof data source consistency from which to proceed. While this is the initial target data source,additional data sources may be identified.Foundational Component TwoThe emergence of a set of data standards for court data published by the National Center for StateCourts (NCSC Called National Open Court Data Standards (NODS), it provides naming andcontent standards for state court data. Adoption of NODS will facilitate more accurate interpretationof data provided by the courts. The Client has mapped the data from the MDEC User Interface screensto the NODS structure, which may serve as the base for developing a DW model understandable tonon-technical users for analytics and reporting.C. OFFEROR & RESOURCE QUALIFICATIONS1. The Offeror shall have one(1) year of experience in providing recruitment, staffing, and/or otherwiseproviding professional consulting services.D. SCOPE OF WORKOfferor proposed resource(s) shall be responsible for the following:1. Participation in all aspects of DW and ETL process design, creation, and specification forcomponents.2. Providing the following services in coordination with technical, functional and managementrepresentatives 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 modelscurrently in use by JIS, and any related data sources identified as a result of initialplanning and assessments2) Creating a logical warehouse data design3) Collaboration with platform administration team, design an ETL process to movedata from the source system to the data warehouse, including, but not limited to, thefollowing: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 andfacilitate 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 logicaldesign 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 DWPhysical design including technical considerations for data quality and operationalefficiency.3. Collaborating with business and technology stakeholders to ensure data warehouse architecturedevelopment and utilization.4. All work completed by the proposed resource(s) shall be completed within regulatory compliancestandards 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, andd. Any additional reports as assigned by the supervising manager.