2026_46_Attachment_C_Functional_Technical_Requirements.docx

52 KB Posted

Attached to
RFP - IT - Utility Network Enterprise Deployment
Solicitation number
0000004201
Issued by
Hennepin County, Minnesota

About this file

Written by GovTribe AI ·

This document is Attachment C: Functional/Technical Requirements for the City of Minneapolis's RFP for IT Utility Network Enterprise Deployment, which addresses the migration of ESRI applications used by the Surface Water and Sewer (SWS) and Water Distribution (WD) departments to ESRI's Utility Network architecture. The requirements span thirteen functional categories encompassing project management, process preservation, schema implementation, data migration, attribute rules development, services deployment, database validation, datum transformation, third-party integrations, process optimization, and performance optimization. The consultant must establish formal project governance with defined meeting frequency and transparent decision-making processes, develop comprehensive project plans with weekly progress tracking, create and maintain RAID matrices and RACI documentation, and implement centralized issue-tracking mechanisms. The scope requires managing implementations across three schemas—Water Distribution using ESRI's Foundational Model and Surface Water and Sewer using ESRI's Foundation Expanded Model—with deployment across Development, QA, Pre-Production, and Production environments, along with two data migrations per dataset (six total).

The consultant must preserve mission-critical business processes including FID generation, PDF map production, automated workflows, water quality modeling, data preparation pipelines, Cognos-based reporting, and Python-based workflows for service publication. Requirements include developing and implementing attribute rules, providing nine services (three per database), conducting comprehensive testing including System Integration Testing and User Acceptance Testing, and delivering role-based training to SWS and WD staff on ESRI best practices. The consultant must perform datum transformations supporting both current and legacy non-HARN coordinates with MicroStation file output, validate third-party integrations with Maximo, Granite, Trimble, and modeling platforms, and establish documented performance optimization procedures with baseline and target benchmarks across desktop, web, and mobile scenarios. All City data must reside within the continental United States, remote access must utilize BeyondTrust Privileged Remote Access, and no permanent vendor network connection to production is permitted.

View the file

Other files

File Type Posted
2026_46_Attachment_E_Data_Privacy.docx DOCX document
RFP_-_IT_-_Utility_Network_Enterprise_Deployment.pdf PDF
2026_46_Attachment_D_Cost_Fee_Template.xlsx XLSX spreadsheet
eSupplier_Bidding_Guide.pdf PDF
2026_46_Attachment_F_References.docx DOCX document
2026_46_Attachment_G_QA.docx DOCX document
0_2026_46_4201_RFP_IT_Utility_Network_Enterprise_Deployment.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file
Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

ATTACHMENT C

FUNCTIONAL/TECHNICAL REQUIREMENTS

1. Consultant must respond to each individual requirement by entering an ‘X’ in one of the columns provided. Select the appropriate response using the following guidelines below.

Yes (process/procedure)
· Consultant has a process/procedure to meet the requirement.
No (process/procedure)
· Consultant does not have a process/procedure to complete the work required to be performed

2. Consultant to provide an explanation of how the requirement will be satisfied.

Describe
· If requirement is met by more than one process, Consultant must list which process/procedure is to be used to satisfy the requirement.

· Consultant may also include screen shots, diagrams, samples, for any requirement listed.

· If unable to meet the requirement, Consultant must offer a brief explanation or propose an alternative way to meet the requirement.

Ref. No
Category
Requirement
Yes
No
Describe

A.

Project Management

1.
Project Governance and Cadence
Establish and maintain a formal project governance cadence, including defined meeting frequency, agendas, and participant
2.
Project Governance and Cadence
Meetings shall support transparent decision-making, issue resolution, risk management, and progress reporting throughout Phase One.
3.
Planning, Roles, and Control Framework
Identify, scope, and sequence key project milestones, interim deliverables, and dependencies aligned to the requirements defined in this Scope of Work
4.
Planning, Roles, and Control Framework
Define and document approval benchmarks and acceptance criteria for major deliverables
5.
Planning, Roles, and Control Framework
Develop and maintain a RACI matrix (or equivalent) clearly defining roles, responsibilities, decision authority, and escalation paths across business, technical, and vendor participants
6.
Planning, Roles, and Control Framework
The consultant shall develop and maintain a detailed, integrated project plan for WD and SWS that includes:

· Work packages, tasks, subtasks, and activities

· Assigned resources, roles, and responsibilities

· Start and completion dates

· Percent complete tracking updated on weekly basis

· Review schedule by the City’s stakeholder (IT GIS, WD, and SWS)

· Defined deliverables and milestones

· Formal gate reviews and approval points

7.
Planning, Roles, and Control Framework
The consultant shall develop and maintain a RAID Matrix (Risks, Assumptions, Issues, and Dependencies), including mitigation strategies, ownership, and status tracking, and shall review this log regularly with the IT Project Manager on a weekly.
8.
Issue and Change Management
Partner with the IT Project Manager to plan, configure, and implement a centralized issues-tracking mechanism for the duration of the implementation.
9.
Issue and Change Management

The consultant shall document the issue management process, including severity classification, escalation procedures, and resolution timelines, and shall train relevant staff in SWS, WD, and IT GIS on its use.

B.

Process Preservation

10.

Process Preservation
The implementation consultant shall ensure continuity of mission-critical business processes throughout the Utility Network (UN) transition
11.
Process Preservation
SWS team capability to generate FIDs
12.
Business Process Continuity and Validation
The consultant shall test, document, and perform all work necessary to ensure continued functionality—without material regression
13.
Business Process Continuity and Validation
SWS Operations team’s capability to generate consultant-ready PDF map products using ArcGIS templates and predefined map views
14.
Business Process Continuity and Validation
SWS automated workflows for generation and email distribution of Locator Map PDFs
15.
Business Process Continuity and Validation
SWS Regulatory team’s Water Quality modeling workflows built on the Stormwater database
16.
Business Process Continuity and Validation
SWS Operations team’s schema transformation and data preparation pipelines
17.
Business Process Continuity and Validation
SWS Cognos-based reporting consuming Stormwater and Sanitary GIS datasets
18.
Business Process Continuity and Validation
WD’s ability to edit related tables using ArcGIS Field Maps which in turn will update parent feature symbology based on defined attribute rules
19.
Business Process Continuity and Validation
WD’s Python-based workflows used to publish service line inventory and hydrant layers to ArcGIS Online for public access and authorized external partners (e.g., University of Minnesota)
20.
Business Process Continuity and Validation
Develop and implement an ETL process that preserves WD’s capability to generate MicroStation deliverables in the legacy non-HARN coordinate system, ensuring compatibility with internal departments that continue to operate in this datum.

For each preserved process, the contractor shall:

· Document current-state and future-state workflows

· Identify UN-related risks or changes

· Execute end-to-end regression testing (System Integration Testing, and User Acceptance Testing)

· Obtain formal business sponsor sign-off prior to production deployment

21.
Field Workflow Architecture Decisions
Partner with SWS, WD, IT GIS, and the IT PMO to evaluate and document trade-offs for field workforce workflows operating in ArcGIS Online versus ArcGIS Enterprise (Portal).
22.
Training and Enablement
Provide role-based training to SWS and WD staff on Esri best practices for ArcGIS Field Maps in a Utility Network-enabled environment, including editing behaviors, validation rules, and operational impacts.

C. Schema

23.
Schema
Managing the implementation of three schemas: Stormwater, Sanitary Sewer, and Water Distribution as part of a coordinated Citywide Utility Network rollout.

· Water Distribution shall use Esri’s Foundational Model

· Surface Water and Sewer shall use Esri’s Foundation Expanded Model

24.
UN Package Implementation
Using Esri-provided documentation, tools, and lessons learned from prior UN pilot efforts, implement the Utility Network package (including schema and attribute rules) for Water Distribution, Stormwater, and Sanitary Sewer datasets across Development, QA, Pre-Production, and Production environments.
25.
Schema Governance
Establish and document formal processes, including standardized documentation formats, for future schema changes, including version control, impact analysis, testing, approval, and deployment.

D Data Migration

26.
Data Migration
Perform two (2) data migrations QA and Production per dataset (six total):

· Initial migration to remediate issues identified during pilot or QA activities

· Final migration supporting production readiness

· Where required, perform additional migrations, UN asset package rebuilds, or re-implementations to regularize changes identified through validation, SIT, or UAT cycles.

· All migrations shall include documented validation, reconciliation, and formal acceptance prior to go-live.

E Attribute Rules

27.
Existing Rules
Integrate or re-implement existing attribute rules provided by WD and SWS, validating compatibility with Utility Network architecture.
28.
New Rules Development
Develop, document, and implement rules governing lines, points, and polygons as well as define grade-point and event-point creation (e.g., angle, elevation, or functional changes)
29.
New Rules Development
Under direction of designated SWS and Water subject matter experts, develop, test, QA, and operationalize attribute rules that enhance data quality in Stormwater, Sanitary, and Water datasets.
30.
Lifecycle Management
Plan and document processes for ongoing attribute rule development, testing, regression validation, and deployment.

F Services

31.
Services
Provide three services per database (viewer, editor, and one business-defined service) are anticipated, totaling nine services.
32.
Service Publishing Enablement
Train and support IT GIS in publishing Utility Network services and document standards for service lifecycle management across environments.
33.
Dependency and URL Management
Perform anticipatory assessments of operational impacts due to service URL changes and partner with IT GIS, WD, and SWS to mitigate impacts across applications, scripts, and devices.
34.
Operational Capabilities
Plan, develop, test, QA, document, and train WD, SWS on UN-enabled valve tracing and water main isolation workflows
35.
Transition Planning
Support WD, SWS in transitioning from existing service architectures to the new three-service model through service inventory mapping and phased rollout planning.
36.
UI Refinement
Work collaboratively with IT GIS, WD, and SWS teams within the QA environment to refine and re-implement user interface elements of map and feature services using tools available in the City’s Esri Portal environment (e.g., Field Maps Designer, Map Viewer).

G Database validation and reconciliation

37.
Operational Enablement
Document and provide hands-on training for WD, SWS, and IT GIS staff on utility network editing, validation, and reconciliation procedures and the application and interpretation of network rules to ensure consistent and reliable production operations.

H Datum Transformation

38.
Datum Transformation
Plan, develop, test, and document ETL pipelines supporting datum transformations (between current and legacy, non-Harn coordinates), ensuring consistency across operational, analytical, and regulatory workflows. The outcome of this pipeline must include a Microstation file; this tool can be created after UN implementation.

I Integrations

39.
Integrations
Partner with system owners to produce necessary documentation and proactively communicate with external vendors to preserve the following third-party application integrations impacted by UN migration:

A) Maximo – Ensure GIS-side integration continuity and lifecycle alignment

b) Granite – Validate continued integration integrity

c) Asset Lifecycle Alignment – Coordinate UN changes with SWS asset management practices d) Trimble – Validate two-way field integration continuity

e) Modeling Platforms (InfoWater Pro, PCSWMM, Flowlink, Optimatics) – Assess impacts, execute regression testing, and document integration updates

J Process Optimization

40.
Process Optimization
Partner with WD and SWS Operations teams to map current-state business processes across Esri applications and to design, document, develop, test, and integrate optimized future-state workflows that leverage Utility Network capabilities and Esri-provided templates.
41.
Process Optimization
Process optimization efforts shall focus on improving efficiency, usability, data quality, and cross-team consistency, and shall be validated through user testing prior to adoption.
42.
Process Optimization
Partner with WD and SWS teams to expand Utility Network–specific usage of ArcGIS Field Maps, including advanced editing workflows, validation behavior, and role-based field enablement.

K Schema Iteration

43.
Schema Iteration
Enhance and iterate schema and attribute structures to enable selected assets to be represented and managed both:

· In aggregated groupings for planning, reporting, or program-level analysis, and

· As discrete assets for operational, inspection, or maintenance use cases

44.
Schema Iteration
Schema iterations shall be designed to support flexible consumption while maintaining data integrity, Utility Network rules, and downstream integration compatibility.

L Data Refinement

45.
Data Refinement
Under the direction of designated SWS subject matter experts, partner to develop, test, and operationalize tools and processes for remediating data quality issues within the SWS Sanitary Sewer and Stormwater datasets, with particular emphasis on spatial geometry accuracy.

Data refinement activities shall include:

· Defined data quality benchmarks

· Testing and validation procedures

· Mutually agreed-upon milestones with SWS stakeholders

M Performance Optimization

46.
Performance Optimization
In collaboration with IT GIS, SWS, and WD stakeholders, the implementation consultant shall establish, document, and execute a structured performance optimization approach to ensure Utility Network-enabled applications meet City operational standards.
47.
Performance Optimization
Define baseline and target performance benchmarks for ArcGIS application viewing, tracing, and editing workflows across representative operational scenarios, including desktop, web, and mobile use cases.

Benchmarks and testing procedures shall:

· Reflect Esri-recommended best practices for Utility Network performance

· Include normal, peak-load, and field-based usage scenarios

· Be executed across Development, QA, and Production environments

48.
Performance Optimization
Performance testing and remediation activities shall be incorporated into the overall project milestone schedule defined in the Project Management section. Performance results, remediation actions, and acceptance outcomes shall be documented and reviewed with IT GIS and business stakeholders prior to production go-live.

N Technical Requirements

49.
Cybersecurity
Consultant must ensure all City data, resides within the continental United States.
50.
Vendor Remote Access
Consultant must use remote access for support and implementation purposes using BeyondTrust Privileged Remote Access (PRA).
51.
Vendor Remote Access
Consultant must not require a permanent vendor network connection to the production environment.

File details come from the government source that posted it. Updated .