200000000971.pdf

���������������������� �!������������"�#$"���%�������&���$�������'��()��*+,-�'�.���$��'������/��*)�� �!0�123++&454�#�6�+--,7 �/��*)�� �!0�123-389:;<=8;�8>=:?@�:9;A8@%������B��)���B$�C����D��%��������B$�C����E=FGGGGGGGGHIJ

��� K'&L�0L/�0B%427K1�.�*�M��"�%��������4�'$)���1N-O)�����OL�,,K2,P�()��')�M���11+Q7-1Q-R,2�P�()�4*)�M���SK*���)��4���%O-K+7K,N ����� �TUVTWX �WYWVZT !��[�\����* ��!#NKRQ,1KQ7173\����*�+S!)��)���4��( UY]TŴ] �_XỲ̀a]TW]UT b$*�)��c����� ��!#NKRQ,13Q-13+c�����bKS�)��)���4��( ��������de��*���)���0�������)���'�f�M������"�'��()��*

�i���b$���K- �,-,N

�i����k�����b$���K- �,-,R��d�� �������BmL i�g h��d�� �������B���1N�g��� ������d�� �&Q%��" �)�����O�$�����n&o%p 5���� �j�� i�i���� �l�* B�� ����i�g h��d���q� ���� ��BmL i�� g� �j�� g� ��������j��

��h�g��s+ 7+, 3N-4-- h�g������ �s-4-- ��� ����i����������� ��h�g��s+ 7+, 3N-4--

������23--1**����- ��4-*���������*����� �����56�7�� ��-��1��������� ��1� ���������2 ����*����8��� ,��/��������������1� ������1���1�������*��9 ��#�6� ����1 ����:4; %%%#%%#�81����������� ��������������1!!��� <���������������!1��������� 01��

�� �����56�7�� ����������1�

Michigan.gov/MiProcurement

Version 2026-1 1 of 5

STATEMENT OF WORK -

IT CHANGE NOTICE

Project Title:

MGF Support

Period of Coverage:

July 1, 2026 – October 31, 2026

Requesting Department:

DTMB Center for Shared Solutions

Date:

June 24, 2026

Agency Program Manager:

Mark Holmes

Phone:

517-285-6592

DTMB Program Manager:

Tim Lauxmann

Phone:

517-898-5663

Brief description of services to be provided:

BACKGROUND:

This statement of work describes GIS support services Contractor will provide the DTMB Center for Shared Solutions with activities to support the Michigan Geographic Framework Data Gateway validation rules and workflow.

PROJECT OBJECTIVE:

Contractor will provide GIS support services to DTMB Center for Shared Solutions to ensure the Michigan Geographic Framework validations rules and workflows are maintained throughout this project.

SCOPE OF WORK:

Contractor has configured Commercial-Off-The-Shelf (COTS) software components to create the Michigan Geographic Framework (MGF) workflows. Support will cover the implementation of the workflows deployed by Contractor, ensuring the system continues to meet the acceptance requirements of the services contract.

Solution support scope includes:

• Diagnosis of solution defects

• Issues encountered during installation or upgrade

• Errors arising from the supported solution

• Solution configuration questions

• “How-to” questions*

*Note: How-to questions are limited to general inquiries about the supported application.

Workflow design, optimization, and best practices are considered outside of the scope of MGF Solution Support. If further assistance is needed, we recommend leveraging consulting through the Contractor Professional Service Team.

Contractor will support the following MGF solution packages under the MGF Solution Support Scope:

Version 2026-1 2 of 5

• Camunda Workflows

• MDOT to MGF Workflow

• Generic MGF Workflow

• 911 to MGF Workflow

• Camunda Step Configuration

• 1Data Gateway + 1Integrate Rule Packages

• MGF

• Census Block Aggregation

• Event Process

• ArcGIS Desktop Scripts

• Data Store Update Script – used to set the data connections in the environment (Dev, UAT, Prod)

Example In Scope Requests

• Camunda Workflow o Configure/Install Camunda for local environment.

o Configure REST connection to 1Integrate server.

o Configure SQL connection to Camunda Repository.

o Configure SQL connection to Staging database.

o Configure e-mail server.

o Configure Camunda User Permissions and Access.

o Add or remove e-mail addresses from existing workflow step.

o Diagnose/fix failure in Camunda Workflow step.

o Restart/Rewind Camunda workflow step.

• 1Integrate Session Errors o Diagnose/fix error in 1Integrate Session.

o Configure 1Integrate Data Store for local environment.

o Advice on how to configure and run 1Integrate Session not started by 1Data

Gateway or Camunda.

• Data Store Update Script o Diagnose/fix issues with Python Script installation tool that updates 1Integrate Sessions to use Data Stores from the local environment.

• Census Alignment Review Calls o Advice on how to configure and run Census Block Alignment Session.

o Advice on how to configure and run Census Block Validation Session.

o Advice on how to configure and run Census Block Aggregation Session.

Solution upgrades are outside of the scope of this contract.

Contractor will alert DTMB Center for Shared Solutions if a request to review or update the Michigan Geographic Framework Data Gateway will take over four hours. Any request under four hours will be processed and invoiced on the standard schedule described in the Payment Schedule section.

The following items are NOT in the scope of MGF Solution Support:

• Solution logic development or debugging

• Installation, migration, or configuration walkthroughs

Version 2026-1 3 of 5

• Workflow design or optimization

• System or network design

Solution defects and errors will be considered enhancements and out of scope if the overall workflow maintains the mutually agreed upon 99% conflation automation rate (or 95% automation rate for the MDOT workflow).

TASKS:

This is a services contract that is time and materials. As noted above any request that will take over four hours to complete will be discussed with DTMB Center for Shared Solutions.

DELIVERABLES:

Deliverables will not be considered complete until the Agency Project Manager has formally accepted them. Deliverables for this project include:

The services provided under this SOW will be GIS services to technical support and expertise for the Michigan Geographic Framework Data Gateway and data aggregation workflows. Deliverables will be in the form of support hours. There may be documents provided such as workflow procedures, metadata about the system or datasets, etc. however, due to the time and materials nature of this project they are not a required deliverable.

PROJECT CONTROL AND REPORTS:

A monthly progress report must be submitted to the Agency and DTMB Project Managers throughout the life of this project. This report may be submitted with the billing invoice. Each monthly progress report must contain the following:

1. Hours: Indicate the number of hours expended during the past month, and the cumulative total to date for the project. Also state whether the remaining hours are sufficient to complete the project.

2. Accomplishments: Indicate what was worked on and what was completed during the current reporting period.

3. Funds: Indicate the amount of funds expended during the current reporting period, and the cumulative total to date for the project.

SPECIFIC DEPARTMENT STANDARDS:

Agency standards, if any, in addition to DTMB standards.

PAYMENT SCHEDULE:

Payment will be made on a time and materials basis. DTMB will pay Contractor upon receipt of properly completed invoice(s) which will be submitted to the billing address on the State issued purchase order not more often than monthly. DTMB Accounts Payable area will coordinate obtaining Agency and DTMB Project Manager approvals. All invoices should reflect actual work completed by payment date and must be approved by the Agency and DTMB Project Manager prior to payment. The invoices will describe and document to the State’s satisfaction a description of the work performed, the progress of the project, and fees. When expenses are invoiced, receipts will need to be provided along with a detailed breakdown of each type of expense.

Version 2026-1 4 of 5

Payment will be considered timely if made by DTMB within forty-five (45) days after receipt of properly completed invoices.

Contractor proposes to perform the above-described scope of services for the estimated not to exceed fee of $15,000. These services will be provided on a time and material basis per the standard Schedule of Rates and per the terms and conditions of Contract No. 200000000971.

Professional fees for each staff level are quoted as hourly rates.

Rate Table:

Position Rate

GIS Analyst 3 $220

GIS Analyst 4 $240

Senior Software Engineer $280

Senior Project Manager $280

Director of Products and Technology $350

Monthly invoices will be submitted based on actual hours incurred. The invoices will identify the staff involved and the number of hours spent by task. Payment will include a reference to the Contractor project number and invoice number

EXPENSES:

The State will NOT pay for any travel expenses, including hotel, mileage, meals, parking, etc.

PROJECT CONTACTS:

The designated Agency Project Manager is: To Be Determined

Mark Holmes DTMB Center for Shared Solutions eMichigan/Geospatial Services Romney Bldg 10th Floor 111 S. Capitol Ave Lansing, MI 48933 517-285-6592 Holmesm3@michigan.gov

The designated DTMB Project Manager is:

PROJECT CONTACTS:

Tim Lauxmann DTMB Center for Shared Solutions eMichigan/Geospatial Services Romney Bldg 10th Floor 111 S. Capitol Ave Lansing, MI 48933 517-898-5663 mailto:Holmesm3@michigan.gov

Version 2026-1 5 of 5

Holmesm3@michigan.gov

The designated Contractor Project Manager is:

Name: Claygee Da Silva Address: 8614 Westwood Center Dr City/State/Zip: Vienna VA 22182 Phone Number: 256-616-2227 Email Address: claygee.dasilva@1spatial.com

AGENCY RESPONSIBILITIES:

LOCATION OF WHERE THE WORK IS TO BE PERFORMED:

Consultants will work at:

1Spatial office 8614 Westwood Center Dr Suite 350 Vienna, VA 22182

EXPECTED CONTRACTOR WORK HOURS AND CONDITIONS:

Work hours are not to exceed eight (8) hours a day, forty (40) hours a week. Normal working hours of 8:00 am to 5:00 pm ET are to be observed unless otherwise agreed to in writing.

No overtime will be permitted.

This Statement of Work is hereby made part of and incorporated by reference into that certain Contract Number 200000000971 executed by and between Contractor and the State, the terms of which remain unchanged except as may be expressly provided herein

PROJECT PLAN: Not Applicable mailto:Holmesm3@michigan.gov

STATE OF MICHIGAN

ENTERPRISE PROCUREMENT

Department of Technology, Management, and Budget 320 S. Walnut Street 2nd Floor Lansing, MI 48933

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

CONTRACT SUMMARY

Geospatial Integration Software and Services

INITIAL EFFECTIVE DATE INITIAL EXPIRATION DATE INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

June 10, 2020 June 10, 2025 5 - 12 Months June 10, 2025

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

MINIMUM DELIVERY REQUIREMENTS

N/A

P-Card Direct Voucher (PRC) Other Yes No

8614 Westwood Center Dr. Suite 450

Vienna VA 22182

Sheila Steffenson

210-863-4948

Sheila.Steffenson@1spatial.com

CV0136125

1SPATIAL, INC.

C O

N

TR

A C

TO

R

517-241-6469

Holmesm3@Michigan.gov

Jeremy Lyon

517-230-2858

DTMB

Mark Holmes DTMB lyonj5@michigan.gov

C ontract

A dm inistrator Program M anagerSTA

TE

Net 45N/A

Change Notice Number 4

Contract Number MA200000000971 to

DESCRIPTION OF CHANGE NOTICE

OPTION EXTENSIONLENGTH OF OPTION LENGTH OF EXTENSION REVISED EXP. DATE

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

24 Months June 10, 2027

$3,407,950.00 $225,000.00 $3,632,950.00

DESCRIPTION

8/14/2024, this change is to utilize two option years and add funding for $225,000 while we continue leveraging the 1Spatial contract, including the annual maintenance renewals.

CENTRAL PROCUREMENT SERVICES

Department of Technology, Management, and Budget

320 S. WALNUT ST., LANSING, MICHIGAN 48933

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

Change Notice Number 3 to

200000000971Contract Number

Holmesm3@Michigan.gov

Mark Holmes

Sean Regan sheila.steffenson@1spatial.com

Sheila Steffenson

Vienna, VA 22182

1SPATIAL, INC.

CV0136125

210-863-4948

8614 Westwood Center Dr. Suite 450

(517) 284-6993 S

T A

T E

P ro g ra m

M a n a g e r

C o n tra ct

A d m in istra to r

C O

N T R A C T O

R

517-241-6469

DTMB

regans@michigan.gov

$2,900,000.00

June 10, 2020 June 10, 2025

GEOSPATIAL INTEGRATION SOFTWARE AND SERVICES

June 10, 2025

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

5 - 1 Year

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

☐ P-Card ☐ PRC ☐ Other ☒ Yes ☐ No

MINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

OPTION LENGTH OF OPTION EXTENSION LENGTH OF EXTENSION REVISED EXP. DATE

☐ ☐ June 10, 2025

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$507,950.00 $3,407,950.00

Effective 7/19/22, this change notice will reflect the addition of the next phase of the project which is to implement Workflow and Notification functionality to improve the integration of GIS data aggregations. This change will be in the amount of $507,950.00.

Please see attached SOW for further review.

All other terms, conditions, specifications, and pricing remain the same. Per contractor and agency agreement, DTMB Central Procurement Services approval, and State Administrative Board approval on 7/19/2022.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

CONTRACT SUMMARY

DTMB

8614 Westwood Center Dr., Suite 450

Vienna, VA 22182-2278 USA

Phone: 703-444-9488

Fax: 703-444-4922

June 27, 2022

Mark Holmes Geospatial Services Manager State of Michigan – DTMB - Center for Shared Solutions Romney Building, 10th Floor, 111 S. Capitol Ave. Lansing, MI 48933

Executive Summary

1Spatial has worked with Michigan’s Department of Technology, Management, and Budget’s (MTDB) Center for Shared Solutions (CSS) to implement and optimize 1Integrate Enterprise for the Michigan Geographic Framework (MGF). This effort greatly improved the stability of the rules engine and provided improved performance of 1Integrate For ArcGIS.

MGF provides a central repository of spatial data for Michigan state, regional, and local agencies. CSS also provides a submission and workflow platform to update MGF. The platform consists of Esri and 1Spatial technology highlighted in Table 1.

Table 1:Software Components of MGF Submission Workflow

Software Description

Esri’s ArcGIS Server and Portal for ArcGIS Provides the submission portal and permissions (this is being replaced by 1Data Gateway)

Esri’s Workflow Manager (extension of ArcGIS Server)

Provides an interface to build and process jobs

1Spatial’s 1Integrate Provides the rules engine to validate and process submissions

1Spatial Inc., 8614 Westwood Center Dr, Suite 450, Vienna, VA 22182-2278

CSS has experienced reliability issues with Esri’s Workflow Manager. These issues include the following:

• large submissions timing out

• active workflows timing out

• workflow steps failing

Additionally, Esri’s Workflow Manager restricted the number of submissions to the number of CPU Cores. In production this means only 8 submissions can be running at any given time. The 9th and subsequent submissions are rejected. CSS has expressed the desire to replace Esri’s Workflow Manager with a technology better fitting the requirements of the MGF system.

As part of this change order, 1Spatial proposes to replace Esri’s Workflow Manager with Camunda’s Enterprise Workflow Platform and supporting products. Camunda’s Enterprise Workflow Platform uses industry standard definitions and supports large companies across many industries including banking, mobile, transportation, and entertainment. Camunda provides the ability to have multiple jobs processing through one or multiple workflows with minimal resources which should reduce the hardware and license footprint of the current system. A Camunda instance with 2 CPU and 8-16 GB Memory would be able to start 100 jobs/second where the current architecture is limited to starting a single job for each available CPU. Additionally, the connection between Camunda and 1Integrate will use product libraries rather than python scripts reducing the maintenance with future software releases.

Additionally, the change order includes other enhancements to MGF that have been identified by CSS to include updating the NG911 workflow to support data roll up into the MGF system and additional rule development to enhance the MGF workflow in supporting MDOT roads submissions.

1Spatial Summary

1Spatial is a software solutions provider and global leader in managing geospatial data. We work with our clients to deliver real value by making data current, complete and consistent through the use of automated processes - ensuring that decisions are always based on the highest quality information available.

Our unique, rules-based approach delivers enterprise-scale, cross-platform, automation to all stages of the data lifecycle. It builds confidence in the data while reducing the time and cost of stewardship.

Our global clients include utility and telecommunications businesses, national mapping and land management agencies, government departments, emergency services, defense, census bureaus and transportation organizations.

As a leader in our field, we have a wealth of experience and a record of continual innovation and development. We partner with some of the leading technology vendors including Esri, Oracle, and SAP.

For more information visit www.1spatial.com.

1Integrate Summary

1Spatial’s 1Integrate Commercial off the Shelf (COTS) products stand apart from all other data QA/QC packages for several reasons. The 1Spatial COTS rules engine is unique in its flexibility and configurability to handle a variety of data challenges such as undershoots, overshoots, gaps, overlaps, attribution errors, alignment issues, etc. Our rules-based, automated engine goes beyond just locating errors as it also allows for “action” rules that can automate repairs to the data.

Traditionally, 1Integrate has been used in the following scenarios:

• Validation – rules define how the data should exist. The engine identifies any feature that does not conform to the standard.

• Correction – rules define how data should be changed to conform to the standard.

• Integration – rules define how data sets should be combined to meet the standard including:

o Change detection – identifying how multiple datasets depict the same location. Changes can be identified between different providers, multiple vintages of the same provider, or multiple vintages from different providers.

o Data Integration – apply changes identified during change detection to update one or more datasets.

o Data Fusion – combining multiple siloed datasets to create a new dataset with information unavailable in an individual silo.

o Schema Transformation – applying rules to transform between schema definitions and identifying what the source does not provide but is needed by the target.

Additionally, 1Integrate utilizes our proprietary object-oriented cache which was developed to handle both large volumes of data as well as complex data processing tasks. The object-oriented nature of the cache provides for scalable performance even when the complexity of the rules or actions increases.

1Integrate leverages the object-orientated cache to provide the flexibility to work with a variety of schemas and file types, making 1Integrate client agnostic.

Camunda Summary

Camunda Process Automation software enables some of the most competitive organizations around the world to orchestrate and automate complex processes in a new way. A way that helps them overcome technology, organization, and infrastructure roadblocks, so they can lay the foundation for a new digital enterprise and follow the vision of automating any process, anywhere.

Workflow Enterprise Platform Summary

Camunda’s Enterprise Workflow Platform executes processes that are defined in Business Process Model and Notation (BPMN), the global standard for process modeling. With BPMN, you can automate your most complex business processes using an easy-to-adopt visual modeling language.

Processes are complex and include many different steps, components, and endpoints across different technologies. The Workflow Engine orchestrates processes that span APIs, microservices, business decisions and rules, human work, IoT devices, RPA bots, and more, so you have complete control and visibility for your most critical business processes.

Workflow Enterprise Workflow Platform consists of

• Workflow Engine – provides process orchestration

• Cockpit – provides a real-time view of processes

• Tasklist – provides interface for manual step progression

• Modeler – provides an interface to author workflows which can be promoted to the Workflow

Engine

Project Methodology

1Spatial implements projects using a combination of the IBM Rational Unified Process (RUP) and Agile concepts. RUP consists of 4 phases (Inception, Elaboration, Construction, and Transition).

1. Inception begins with a project kick off and the establishment of project management

2. Elaboration focuses on building out the environment and high-level project design

3. Construction consists of rule and test case authoring

4. Transition focuses on provision of documentation and any remaining project components to the customer

Following Agile processes, weekly sprint meetings will be held with the customer to review:

1. Work completed (may include demonstrations)

2. Issues encountered

3. Plans for the next set of priorities

These weekly meetings may be extended to a bi-weekly basis after the first two weekly meetings if deemed appropriate by all involved.

1Spatial will also conduct daily internal standups with the rule implementation team. The daily standups will focus on similar topics on a smaller scale and members of MI DTMB maybe be invited if their input is required.

The following activities & deliverables have been identified for this project:

Project Activities

Inception

1Spatial will work with the CSS IT Support team to ensure the server architecture (Attachment 2 – System Design) is updated to support Camunda in the development environment. As shown in the architecture diagram in the System Design Document, Camunda will leverage the existing architecture for the MGF environment. 1Spatial will also confirm remote access (RDP) to the workflow server.

1Spatial will install the Camunda Enterprise Platform software on the workflow server in CSS’s development environment. 1Spatial will configure Camunda to authenticate via LDAP. This includes configuring Camunda to use CSS’s SQL Server for storing the metadata for workflow definitions and progress. 1Spatial will provide CSS with the required software specifications including

• SQL Server database size and permissions.

• Java 11

During the installation, 1Spatial will create an Install Guide for Camunda specific to the CSS environment. This document will be used to configure the UAT/QA and Production environments by

CSS.

CSS will setup the environment to provide (in the Michigan hosted Development environment)

1. Esri Feature Services for the MGF Prod database

2. SQL Server Spatial database with the MGF Prod schema

1Spatial will perform performance tests from 1Integrate reading and writing to both options. 1Spatial will then provide those metrics to CSS to determine if the Prod database will be Esri Enterprise Geodatabase (SDE) or SQL Server Spatial. Based on the selection, 1Spatial will configure 1Integrate MGF Data Stores to use the desired target. If Esri Enterprise Geodatabase (SDE) is selected, 1Spatial will use ArcGIS Server 10.9.1. The implementation of Camunda as well as the testing of the Camunda workflow will test the datastores for the selected target.

1Spatial will upgrade 1Integrate and 1Data Gateway to the most recent versions in the development environment. 1Spatial will configure the capability for 911 contributors to load Exceptions in 1Data Gateway and 1Integrate after upgrade.

Elaboration

After the workflow server has Camunda installed in CSS’s development environment, 1Spatial will start configuring Camunda for supporting the MGF system. Camunda provides the capability to view workflows and jobs currently running in those workflows and see how many jobs are at each step in the workflow. The licensing provided in the Billing table allows for up to 25 users to monitor jobs. This is intended to provide the CSS team the ability to review jobs.

Configure Camunda to send emails

The current workflow system provides email alerts to CSS staff as well as external users. Camunda has an optional plugin for Workflow Engine to provide this same functionality. 1Spatial will enable the optional plugin and work with the CSS staff to configure the plugin to connect to the CSS mail (SMTP) server. During the construction phase, 1Spatial will add tasks to send emails using the configured plugin.

Review requirements for 911 integration into MGF

The current implementation has focused on updating the MGF data directly from contributors. A second project using 1Data Gateway and 1Integrate allowed providers to contribute their 911 data into a separate data repository just for emergency services. During this project 1Spatial will work with CSS to add another workflow that pushes 911 contribution data into MGF after updating the emergency services data repository, if desired. During elaboration 1Spatial will gather the requirements for the workflow and design the Camunda workflow definition as well as the rule updates for handling data from the 911 contributors.

Construction

1Spatial will perform the following consulting actions during the project:

Configure 1Integrate to trigger a workflow in Camunda

In the current implementation, 1Spatial has created a component to call the existing workflow software to create and start a job (an individual running instance of a workflow). 1Spatial will update this component to call Workflow Engine to create and start a job.

Build 1Integrate Camunda library

1Spatial, for the earlier phases, created a Python library to communicate with the 1Integrate REST API.

This library focused on creating and running jobs (sessions). With the move to Camunda, 1Spatial will transition this library to Java for integration with Camunda. This move will provide tighter integration between Camunda and 1Integrate in the MGF environment. This library will have the ability to

• Clone Sessions and Data Stores

• Create Data Stores

• Run Sessions

• Retrieve the status of Sessions

• Delete Sessions and Data Stores

The library will be incorporated into the core 1Integrate product, reducing the effort to maintain and update the system with each new 1Integrate release.

Build MGF Camunda library

In addition to the 1Integrate Python library, 1Spatial built an MGF library in Python using the ArcPy library to handle workflow specific components like

• Creating the necessary transition tables for a job

• Defining the Data Stores and Sessions

• Tracking the job performance

Each workflow uses staging tables to pass data between workflow tasks. These tables are currently stored in Esri’s Enterprise Geodatabase. To create and delete the tables, the workflow uses python scripts with ArcPy. Esri’s ArcGIS technology uses an entire server cpu core per each ArcPy instance running.

The current process contains unnecessary overhead, server specification and licensing that can be significantly reduced if these stagging tables are moved from SDE into SQL Server’s native spatial tables (SQL Server Spatial). To further improve the architecture, 1Spatial will update the tasks to create tables to use SQL Server Spatial from Camunda. CSS already has the capability to read and write data from SQL Server Spatial. 1Spatial will update the data store templates which read and write the staging tables to use SQL Server Spatial.

1Spatial will migrate the MGF Python library to integrate with Camunda and the 1Integrate Camunda library. Camunda Workflow engine will call out to the MGF Camunda to perform the necessary steps to create SQL tables and 1Integrate sessions for the current job.

Configure Contributor Workflows in Camunda’s Workflow Engine

The existing MGF system uses two workflow definitions. All contributors, aside from MDOT, use the General Contributor workflow. MDOT which submits road, trail, and railroad updates has a separate workflow to allow for tighter collaboration between CSS and MDOT.

Configure General Contributor Workflow Most contributors work fully disjoint from CSS. These contributors submit their data on an irregular schedule. The General Contributor Workflow definition in Camunda’s Workflow Engine will follow the existing Esri Workflow Manager definition shown in Appendix A. 1Spatial will build the definition through the use of Camunda’s Modeler.

Configure MDOT Contributor Workflow

MDOT and CSS work closely together to create statewide products. The MDOT contributor workflow takes advantage of the state agency to state agency relationship and extends the General Contributor workflow providing MDOT, as a contributor, the opportunity to review the changes proposed to the MGF system.

1Spatial will transfer the tasks currently in the Esri Workflow Manager MDOT definition (Appendix B) through Camunda’s Modeler into the workflow definition.

Configure 911 Contributor Workflow in Camunda’s Workflow Engine

CSS provides a second data submission partnership, also leveraging 1Data Gateway, for 911 contributions. Two 911 layers, Road and Address, are represented in MGF as well as 911 and currently the two submissions are not linked. This section takes the next step to allow 911 submissions to flow directly into the 911 contribution and MGF contribution workflows automatically. There are two options, the first leverages the 911 Vintage over Vintage change detection to pass the delta features through to MGF, skipping the Contributor Load and Contributor Validate as those were completed during the 911 workflow. The second option passes the entire road file to the MGF as a regular contributor and will run the MGF Contributor Load and Validate steps.

Option 1 Pass 911 Submission to MGF Step 3

As part of another project, 1Spatial configured 1Data Gateway and 1Integrate to accept data (Roads, Addresses, PSAPs) for the Michigan emergency services data repository. The data submitted for the 911 portal (1Data Gateway) also needs to be brought into the MGF repository. This task is to configure a workflow that takes the updates from the emergency services data repository and pushes those same updates to the MGF Repository. This will allow data providers to submit data to one program while supporting multiple programs.

Some contributors who were willing to share with the emergency services data repository will not be willing to contribute to MGF. 1Spatial will build a SQL Server lookup table, which will be maintained by CSS through their partnership agreements with contributors, to define which contributions will be merged into MGF. Only contributions from contributors identified in the lookup table will execute the workflow merging the updates into MGF.

The existing business rules for non MDOT contributions assume a full road network or address layer. The emergency services contribution workflow performs a Vintage over Vintage (VoV) Change Detection and application process. The VoV works on the assumption of a single provider (for a given layer and location), but the MGF workflow will have multiple contributors, including MDOT, for the road layer.

1Spatial will configure new business rules to take the delta created during the 911 VoV. The new business rules will use the results (Proposals) from the emergency service workflow and compare them to identify the changes required for the MGF data (specifically Road and Address)

Option 2 Pass 911 submission to MGF Step 1 1Spatial will update the existing 911 1Integrate sessions to call Camunda to create and start a workflow instance automatically at the end of the submission. In this second option the entire dataset provided by the contributor will be passed into the Road or Address workflow.

Additional Improvements to the Business Rules

Through the initial phases of the project additional requirements were identified but tabled for post-production release enhancements. 1Spatial will implement the two improvements identified below.

• Removing Redundant Nodes – identify intersections where only two roads met. If the two roads have the exact same key attribute values, then the roads should be merged into a single road.

• Event Submission – Expand the existing MDOT workflows to handle updating the Event data. In the current implementation, the MDOT Events are handled manually as they are only updated once each year. MDOT is working to streamline their processes to keep Events more in sync with the linear network.

Transition

1Spatial will perform initial testing of the system in Michigan’s Development Environment. Test will include submitting MDOT Roads and Ultra Priority boundaries layers through the workflow.

To test the 911 workflows, 1Spatial will submit sample Road and Address data from 3 counties.

This will test the MDOT, General Contributor and 911 Workflows.

During the test 1Spatial will ensure the following steps complete as expected.

• Submitting via 1Data Gateway

• Ensure the Camunda workflow start

• Ensuring emails alerts are sent properly

• Watching the Camunda trigger 1Integrate session for Change Detection

• Ensuring users can manually trigger the workflow to move to Update

• Watching Camunda received the ‘complete’ notice from Update and starting MGF

Validate

• Ensuring the Camunda workflow pauses if Errors are identified in MGF Validate

• Ensuring the contribution (timing and conformance) metrics are populated

1Spatial will simulate a network outage by

1. shutting down the 1Integrate machine to ensure that the updated libraries fail and pause the job in Camunda Workflow Engine.

2. restarting the 1Integrate machine and attempting to restart the job from the failed step (restarting this step from the beginning).

1Spatial will finalize the documentation on

• viewing workflows in progress

• advancing workflows through the interface

Delivery

All artifacts created during the construction phase will be turned over MI DTMB.

On-going Project Activities

1. Project Management

a. Throughout the project, 1Spatial will provide project management to ensure on time deliveries and raise concerns quickly. 1Spatial uses a combination of the Rational Unified Process and AGILE project management to create and maintain a plan for delivery.

b. During this project we suggest using weekly status reporting to ensure that the team (both 1Spatial and MI DTMB members) are in constant contact and do not duplicate efforts. 1Spatial plans for meetings to demonstrate progress at times and dates convenient to MI DTMB

2. Test Case Documentation

a. 1Spatial will document the test cases in two ways.

i. Populate the Description field visible on the Rule Authoring Interface

ii. Create test cases with input scenarios and expected output.

b. The tests cases will be provided as an Esri File GeoDatabase for future user.

Risks

1. Lack of access to Michigan’s infrastructure – to mitigate we need to complete on boarding during the inception. Invitations will be extended to all relevant parties to attend inception meetings. This will include any Mi DTMB staff who will be responsible for the security and maintenance of Mi DTMB’s IT infrastructure.

Pre-requisites

1. Example data to be provided by MI DTMB prior to the beginning of work.

2. Remote Desktop access to be provided by MI DTMB before the Elaboration phase

Assumptions

1. 1Spatial will train MI DTMB staff for using Camunda in relation to the MGF Workflows configured during the project

a. View in progress jobs

b. Advance or pause existing jobs

c. Cancel jobs

2. Availability of MI DTMB Staff to regularly utilize 1Integrate and Camunda to become adept in maintaining the system

3. CSS will perform all the updates to the architecture across environments

4. CSS will perform all the installations in UAT and Production environments

5. CSS will provide access to 1Spatial to install Camunda on the development server

6. 1Spatial will install Camunda in development environment

7. 1Spatial will provide support to install Camunda in UAT and Production environments

8. CSS will create the required Esri Feature Services and manage the ArcGIS Server software and configuration (if Esri Feature Services is chosen)

Test Strategy

User acceptance testing will be performed by MI DTMB using rules and scripts provided by 1Spatial during the delivery phase. Support as part of MI DTMB current support arrangement will be provided, however additional rule creation and updates to the solution will be considered out of scope. These may be handled by an agreement for additional work detailed by a future SOW.

MI DTMB has 3 weeks to test the General Contributor and MDOT workflows. The 911 workflow is a new workflow and MI DTMB is expected to complete testing of the Workflow 3 weeks after delivery of all components (business rules and workflow definition)

Project Timeline and Billing

Task Description Estimate Delivery Price

Camunda Installation Architecture Design, Installation, Configuration, Documentation

2 weeks (after Award) $30,800

Evaluate Esri Enterprise vs SQL Server Spatial

Perform read and write load test against potential targets.

Provide comparison results to CSS for final decision

3 weeks $10,000

Camunda Software*See Attachment 3)

Software Licensing

• 5,000 jobs/year

2 weeks $53,625

• 25 task users

MGF Camunda Library Library ensuring existing contribution metrics are populated

8 weeks $59,000

MGF General Contributor Workflow

Migrate the general workflow from Esri WMX to Camunda

4 weeks $57,000

MGF MDOT Workflow Delivery

Migrate the MDOT from Esri WMX to Camunda

8 weeks $61,000

MGF Camunda Library and Workflows Acceptance

CSS Acceptance of the migrated workflows

11 weeks $90,000

Subtotal $361,425

911 Workflow Delivery Create a new workflow in Camunda for 911

12 weeks $49,375

911 Workflow Acceptance

CSS Acceptance of the new workflow

15 weeks $49,375

Subtotal $98,750

Business Rule Improvements

Additional business rules to maintain the MGF database

4 weeks $51,400

Total: $507,950

Attachment 1 – General Contributor Workflow

This is the workflow used by all but one contributor (MDOT shown below). The Workflow Software (Esri’s Workflow Manager - WMX) stores information about each job in a database table. The database consists of 3 key tables

• Contributor – a table of potential contributors

• ContributorLayer – a table mapping contributors to layers they can submit

• Contribution – a table of jobs submitted. This contains all the metadata for a job. The current status, step, timing information (actually a referenced table), number of features, path to the disk, path to 1Integrate Schema Mapping.

MDOT Tracking

Michigan Department of Transportation (MDOT) is interested in specific layers. This step reads a table in a database, hosted in MDOT’s environment, to determine if the data submitted has a (MGF) target layer that MDOT wants to review. The decision becomes a flag on the Job record and used during the ‘Export Deltas’ decision point

Contributor Load

WMX calls Python script that returns success (0) or failure (1). This portion of the Python script 1) creates the resources needed by the rest of the workflow and 2) transfers the contributor data from the Upload EGDB to the Staging EGDB.

The resources created for this step are those that are needed by 1Integrate to perform the job. All feature classes needed for this job are created during this step. This includes the Staging feature class, the Proposal feature class, and the Report feature classes. All 1Integrate data stores needed for this job are created during this step. All tables are created with a JOB<ID>_.

The script calls 1Integrate to

1. copy a session template to process the job

2. run the session

3. get the session status

4. pull down timings (when complete)

The session (specified in the WMX Job table) transfers the submitted data into the Staging EGDB.

NOTE: Schema mapping and data validation is done via 1DataGateway.

Change Detection

WMX calls Python script that returns success (0) or failure (1).

The session compares data submitted (loaded from staging EGDB) against the MGF target layer (production EGDB). Proposals are created for identified changes. Changes have a type and status which are used in the review step

Proposal Review

This is a manual step. Once Change Detection completes an email notification is sent to specific people.

Users review the proposals inside ArcMap/ArcGIS Pro connecting to the staging EGDB.

When complete the user (or a admin user) needs to manually complete the step in WMX. When marked as done, WMX automatically will start the next step.

These steps are repeated for each 1Integrate step

MGF Update

WMX calls Python script that returns success (0) or failure (1).

The session applies changes to the MGF target layer (production EGDB).

MGF Validation

WMX calls Python script that returns success (0) or failure (1).

The session validates the production EGDB performing cross validations with the target layer and companion layers. I.e. a road is contained within a boundary. Issues are written to spatially enabled reports.

Edit Data

This is a manual step. If MGF Validation identifies issues, this step is started. Users can review spatially enable reports of the issues and correct the MGF data. Once the data is corrected Validation is run until 0 Errors exist (there are multiple levels of report Error, Warning, Information).

Export Tables

When MDOT Tracking is enabled, the proposals are copied from the staging EGDB into the MDOT EGDB for review and investigation.

Delete Tables

Staging tables for a specific job are deleted.

Calculate Workflow Processing Times

Calculate Processing Times and metadata which is used inside the dashboard (or will be used inside a dashboard)

Workflow Complete (Terminal Status)

MGF System Failure (Terminal Status)

Appendix B - MDOT Workflow

The MDOT workflow follows many of the same steps as above. The addition here is that Proposal Review is done with the MDOT team.

Attachment 2 – System Design Document

The 1Spatial/State of Michigan Camunda Architecture diagram (found below) illustrates a high-level overview of incorporating the software Camunda into the current State of Michigan infrastructure.

The diagram depicts three distinct environments – Development, User Acceptance Testing, and Production. Each environment has a three-tier approach which aligns with what the State of Michigan has provided.

Within each environment 1Spatial has provided recommendations on which software and functionality to add and or remove. Those are as follows:

DEV:

• Remove ESRI Workflow Manager (WMX) from ArcGIS Server

• Install Camunda on ArcGIS Server o Any additional third-party libraries needed for functionality with Camunda

• Add an additional VIP to the F5 for 1Integrate. Create DNS “1Integratedev.state.mi.us”

• Create an SSL Certificate for 1Integrate VIP

UAT:

• Remove ESRI Workflow Manager (WMX) from Private ArcGIS Server

• Install Camunda on ArcGIS Server o Any additional third-party libraries needed for functionality with Camunda

• Add an additional VIP to the F5 for 1Integrate. Create DNS “1Integrateqa.state.mi.us”

• Create an SSL Certificate for 1Integrate VIP

PROD:

• Remove ESRI Workflow Manager (WMX) from both Private ArcGIS Servers

• Install Camunda on both Private ArcGIS Server for High Availability (HA) o Any additional third-party libraries needed for functionality with Camunda

• Add an additional VIP to the F5 for 1Integrate. Create DNS “1Integrate.state.mi.us”

• Create an SSL Certificate for 1Integrate VIP

DEV Diagram

UAT Diagram

PROD Diagram

Attachment 3 - Camunda Platform Pricing -

USD

Process Instances

Tier P-XS P-S P-M P-L P-XL P-XXL max. Process Instances per year

5.000 35.00

245.00

1.700.0

12.000.0

85.000.0

Price $49,5

$69,3

$97,02

$134,64

$190,080 $269,280

Maximum volume discount 10% 12% 15% 20% 25% 30%

Decision Instances

Tier D-XS D-S D-M D-L D-XL D-XXL max. Decision Instances per year

50.00

350.0

2.450.0

17.150.

120.050.

840.350.

Price $27,5

$38,5

$53,90

$75,460 $105,644 $147,902

Maximum volume discount 10% 12% 15% 20% 25% 30%

Task Users

Tier T-XS T-S T-M T-L T-XL T-XXL max. Task Users per year 25 100 300 600 1.000 2.500

Price $4,12

$14,8

$39,60

$64,350 $82,500 $144,375

Maximum volume discount 10% 12% 15% 20% 25% 30%

Upgrade Options Price

Advanced SLA

20% markup on the tier total price

Additional Named Contact per Year $6,600

Remote Consulting per hour $290

Department of Technology, Management, and Budget

320 S. WALNUT ST., LANSING, MICHIGAN 48933

P.O. BOX 30026 LANSING, MICHIGAN 48909

CONTRACT CHANGE NOTICE

Change Notice Number 2 to

200000000971Contract Number

Holmesm3@Michigan.gov

Mark Holmes

Sean Regan sheila.steffenson@1spatial.com

Sheila Steffenson

Vienna, VA 22182

1SPATIAL, INC.

CV0136125

210-863-4948

8614 Westwood Center Dr. Suite 450

(517) 284-6993 S

T A

T E

P ro g n a g e r

C o n tra ct

A d m in istra to r

C O

N T R A C T O

R

517-241-6469

DTMB

regans@michigan.gov

$2,900,000.00

June 10, 2020 June 10, 2025

GEOSPATIAL INTEGRATION SOFTWARE AND SERVICES

June 10, 2025

INITIAL AVAILABLE OPTIONS EXPIRATION DATE

BEFORE

5 - 1 Year

PAYMENT TERMS DELIVERY TIMEFRAME

ALTERNATE PAYMENT OPTIONS EXTENDED PURCHASING

☐ P-Card ☐ PRC ☐ Other ☒ Yes ☐ No

MINIMUM DELIVERY REQUIREMENTS

DESCRIPTION OF CHANGE NOTICE

OPTION LENGTH OF OPTION EXTENSION LENGTH OF EXTENSION REVISED EXP. DATE

☐ ☐ N/A

CURRENT VALUE VALUE OF CHANGE NOTICE ESTIMATED AGGREGATE CONTRACT VALUE

$0.00 $2,900,000.00

Effective 5/31/2022, the following amendment is hereby incorporated into the Contract to develop workflows to merge in the new 2020 Census block, blockgroups, tracts and new legislative districts to match the MGF municipal civil divisions and counties.

Total estimated cost is $76,500. No additional funding is needed at this time; existing funds are adequate to support this change.

All other terms, conditions, specifications, and pricing remain the same. Per contractor, agency and DTMB procurement.

INITIAL EXPIRATION DATEINITIAL EFFECTIVE DATE

DESCRIPTION

May 3, 2022

Mark Holmes

Michigan Center for Shared Solutions

Executive Summary

1Spatial is pleased to submit this proposed Statement of Work (SOW) to Michigan in response to the request to assist Michigan with the implementation of an automated workflow to perform alignment of the US Census Block feature to the Michigan legal boundaries and Roads. The State of Michigan has indicated that their legal boundaries and roads no longer align to the US Census Block features that were generated after the 2020 census. 1Spatial has found that this is a common occurrence with many organizations and has built automated business rules within 1Integrate to assist in the realignment, either to the US Census or aligning to the US Census data. For the State of Michigan, we are proposing re-aligning the Block Groups to the Michigan Boundaries. As part of the re-alignment, 1Spatial will do a pre-cursory set of validation checks to identify existing issues with the US Census data and/or the State of Michigan data. 1Spatial will then configure their existing rulesets to perform the data alignment with a goal of automating the alignment of 95% of the block groups. The remaining 5% will be for the State to determine how they would like to proceed with the cleanup effort.

1Spatial Summary

1Spatial is a software solutions provider and global leader in managing geospatial data. We work with our clients to deliver real value by making data current, complete and consistent through the use of automated processes - ensuring that decisions are always based on the highest quality information available.

Our unique, rules-based approach delivers enterprise-scale, cross-platform, automation to all stages of the data lifecycle. It builds confidence in the data while reducing the time and cost of stewardship.

Our global clients include utility and telecommunications businesses, national mapping and land management agencies, government departments, emergency services, defense, census bureaus and transportation organizations.

As a leader in our field, we have a wealth of experience and a record of continual innovation and development. We partner with some of the leading technology vendors including Esri, Oracle, and SAP.

1Integrate Summary

1Spatial’s 1Integrate Commercial off the Shelf (COTS) products stand apart from all other data QA/QC packages for several reasons. The 1Spatial COTS rules engine is unique in its flexibility and configurability to handle a variety of data challenges such as undershoots, overshoots, gaps, overlaps, attribution errors, alignment issues, etc. Our rules-based, automated engine goes beyond just locating errors as it also allows for “action” rules that can automate repairs to the data.

Traditionally, 1Integrate has been used in the following scenarios:

• Validation – rules define how the data should exist. The engine identifies any feature that does not conform to the standard.

• Correction – rules define how data should be changed to conform to the standard.

• Integration – rules define how data sets should be combined to meet the standard including:

o Change detection – identifying how multiple datasets depict the same location. Changes can be identified between different providers, multiple vintages of the same provider, or multiple vintages from different providers.

o Data Integration – apply changes identified during change detection to update one or more datasets.

o Data Fusion – combining multiple siloed datasets to create a new dataset with information unavailable in an individual silo.

o Schema Transformation – applying rules to transform between schema definitions and identifying what the source does not provide but is needed by the target.

Additionally, 1Integrate utilizes our proprietary object-oriented cache which was developed to handle both large volumes of data as well as complex data processing tasks. The object-oriented nature of the cache provides for scalable performance even when the complexity of the rules or actions increases.

1Integrate leverages the object-orientated cache to provide the flexibility to work with a variety of schemas and file types, making 1Integrate client agnostic.

For these reasons, we are unique in the market and are unaware of any other packages that have all these capabilities without the requirement of custom development by a software engineer.

Project Methodology

1Spatial implements projects using a combination of the IBM Rational Unified Process (RUP) and Agile concepts.