Hybrid Govt Data Architect with e-licensing/e-payments, COTS, evaluation/product recommendation, modernization, training experience

Job ID: MNSITE-2560 (90091220)3P

Hybrid Govt Data Architect with e-licensing/e-payments, COTS, evaluation/product recommendation, modernization, training experience

Location: St Paul MN (MDA)
Duration: 12 months
The work is expected to be hybrid. We would like the kick-off and closing meetings to be in person and on-site as needed for other meetings.

data architect Qualifications
The State is seeking a data architect with prior experience working with government agencies such as federal, state, cities, and counties. The data architect needs to show their experience with technical assessment, decision making and implementation of a solution.

Description of Project
The Minnesota Department of Information Technology Services (MNIT), partnering with the Minnesota Department of Agriculture (MDA), is seeking an implementation data architect to aid in the technical evaluation and delivery of a technical architecture that supports a 360-degree view of their interactions with the MDA and the ability to integrate with COTS solutions to support self-service transactions such as e-licensing and e-payments.

MNIT is seeking a data architect with demonstrable experience helping government organizations evaluate technology options against desired future state service delivery goals. The selected data architect must be able to facilitate decision making by applying expert knowledge of stakeholder engagement and decision-making techniques.

This work will be done in phases, with Phase 1 being the technical evaluation and product(s) recommendation. The key deliverable of this phase is a detailed blueprint with the current MDA technical architecture, including its structure, functionality and features, paired with an actionable plan for making the architecture improvements needed to support the design, configuration, implementation, and integration of future technologies that can be used to meet the MDA’s modernization goals.

Project Overview
Phase 1 includes a technical evaluation that will be used to determine a best-fit approach for the MDA to move forward with implementing new or adapted technical systems needed to support the MDA’s business goal of a customer account framework enabling a 360-degree view of stakeholder’s interactions with the Department. The evaluation will consider in-place technology, in-place technology integrated with other solutions, and replacing in-place technology with new technology. The chosen data architect will facilitate decision-making discussions by the MDA and MNIT on its best option.

MDA Goals
• To have and maintain a data system that acts as a single source of truth for customer contact information to avoid duplication and promote work efficiencies
• To design systems that better address customer needs and wants for conducting business transactions with the MDA.
• To ensure customers will have a better understanding of and access to all available MDA services.
• To provide the MDA staff with more visibility into all customer interactions across divisions and programs.
• To integrate business processes and systems with technical system improvements
• To provide customers a single point of access to their MDA information for performing tasks such as licensing, payments and submitting other applications.
• To develop data systems that support stronger reporting capabilities, so that the MDA staff have the information they need to make informed decisions.

MNIT Goals
• Modernized architecture and technical stack
o Positioned to meet MDA short and long-term service delivery goals
o Greater business functional ownership and self-service capabilities
 Leveraging low code/ no code tools
 Adding Citizen developer capabilities
 Self-service reporting and data analysis
 Defining MNIT role and responsibilities with low code/no-code technology platform
• Seamless Migration from Legacy to new architecture and applications
o Data and document migration
• Staff development and readiness plan to maintain, support and advance new technology

Guiding Values
1. Business Value as measured by the benefits accrued by stakeholders.
2. Quality as measured by the long-term viability of the system.

Phase 1 Details and Deliverables
Phase 1 is a technical evaluation and recommendation on the best plan to move forward with the technical improvements needed to support MDA’s business goals of creating a customer account framework that enables a 360-degree view of stakeholder interactions with the Department and supports electronic activities such as e-licensing, e-payments, and other applications. The evaluation will consider in-place technology, in-place technology integrated with other solutions and replacing in-place technology with new technology. The chosen data architect will facilitate decision-making by the MDA and MNIT on its best option.

Phase 1 Technical Evaluation: Activities
The State anticipates the selected data architect will:
• Discover high-level solution and integration requirements.
• Identify constraints.
• Conduct market and peer research.
• Identify in-place or new solution options and thoroughly evaluate each option.
• Consider inclusive design and accessibility requirements.
• Ensure compliance with MNIT security requirements.
• Facilitate selection of technical direction.

Non-Functional Requirements Include
Technical evaluation should also address non-functional requirements which ensure the viability of a given solution.
• Usability – how effectively a user can use, learn, or control the software
• Maintainability – can modifications be achieved quickly
• Scalability – gracefully meet the demands of increased use and functionality
• Availability – mean-time between failure
• Extensibility – software can be changed with (or without) code changes
• Security – resists unauthorized attempts at usage or modification
• Portability – ability to run on numerous platforms
• Upgradability – upgrade path relatively seamless and smooth
• User Experience – design, features, functionality, and accessibility

State Inputs
State will provide the selected data architect with inputs that must be used to evaluate the technical fit of any proposed solutions. These inputs include:
• Redapt, a Microsoft partner is assessing MDA’s key applications for cloud readiness. Deliverables are expected on/near November 30, 2022. Deliverables include:
o Cloud migration plan to modernize applications to a production ready Azure PAAS solution
o Deployable architecture design
• An IT systems inventory and summary of the technical environment that currently exists
• The MDA Steering Team which has collected data on stakeholder unmet needs and wishes (requirements) related to customer data and overall service delivery.

Snapshot of current licensing/certifications/inspections applications at the MDA include:
• USAFood Safety
• Water Quality certification
• SharePoint used for Meat Inspections
• OnBase used for Hemp Inspections
• LIS – custom built Java based licensing application
• CIS – custom built Java based inspection application
• AgBMP farm loan management program

Current in-place technical environment include:
• IIS middleware
• DB2 backend
• SQL backend
• SharePoint
• Access databases
• Excel spreadsheets

It is expected that the chosen data architect will need to conduct some discovery related to the business problem and goals. The data architect’s proposal should address its plan and timeline for the following types of deliverables:
• Identification and measurement of impacts of pain points/opportunities based on agency priorities and stakeholders.
• Identification of root-causes pain points or opportunities.
• Ideal processes and outcomes that matter most to the MDA and its stakeholders.
• A gap analysis between the current and future states.

Phase 1 Deliverables
• Documented decision of chosen technology
o Technical Evaluation Criteria
o Fit/Gap document
 Detailed pros and cons for each option
 List of any technical constraints and work needed prior to software implementation
 List of technical solution options related to data/application integration and CRM functions.
 List and description of each software’s product features
o High-level cost
 Initial implementation
 Long Term – TCO
• A service delivery blueprint detailing functionality, features, and enabling technology
o Potential barriers, constraints and opportunities to executing the blueprint
• High-level Technical Skills assessment for MNIT @ MDA and selected MDA staff
• High-level Risk assessment

RTR MN.docx

Leave a Reply





There’s no content to show here yet.

Discover more from innoSoul:

Subscribe now to keep reading and get access to the full archive.

Continue reading