25-191 Electric GIS Utility Network Implementation and Migration.PDF

DISCLAIMER - Document Distribution The City of Naperville Procurement Services and its service provider DemandStar by Onvia (www.demandstar.com) are the only authorized sources of bidding documents/proposal forms. Bidding documents/proposal forms obtained from any other source may be an incomplete set of documents. Reproduction of these documents without the express permission of the City of Naperville is prohibited.

REQUEST FOR PROPOSALS (RFP)

Procurement Number:

25-191

Procurement Title:

Electric GIS Utility Network Implementation and Migration Advertisement Date:

Friday, September 5, 2025 Closing Date and Time:

Thursday, October 9, 2025 at 2:00 p.m. (local time)

PROJECT OVERVIEW

The City of Naperville Electric Utility (EU) is soliciting proposals from experienced and qualified organizations to perform an Esri Utility Network design, implementation and migration. The EU’s GIS data currently resides in an ArcGIS/ArcFM 10.8.1a sp3 Geometric Network model, with the target environment planned to be ArcGIS Enterprise 11.x and ArcFM XI.

PROCUREMENT CONTACT

Shanel Gayle, Procurement Officer gayles@naperville.il.us

QUESTIONS

All questions concerning the RFP shall be submitted in writing via email to the Procurement Contact no later than five (5) business days prior to the Closing Date and Time. A written response in the form of an addendum may be issued as appropriate. No contact with any other City employee or Selection Team member shall be made during the RFP process.

DELIVERY INSTRUCTIONS

Proposals must be submitted electronically. Downloading documents and responding electronically requires registration with the City’s online e-bidding platform Demandstar. The City maintains an OPEN ACCESS subscription with Demandstar. This means that all City documentation is accessible to all entities registered with Demandstar regardless of subscription plan. If you are not registered with Demandstar, you may sign up any time for a FREE AGENCY SUBSCRIPTION to the City of Naperville. If you are registered, but subscribed to another agency, you DO NOT need to modify your subscription. With Open Access, you may search for City of Naperville and access all City bidding information and documentation under your current subscription plan. To sign up with Demandstar or to login to an existing account, visit: https://www.demandstar.com/app/login.

Any incomplete submittals may be rejected as non-responsive. Infrequent or first-time users of electronic bidding are encouraged to load their bids 24 hours prior to the Closing Date and Time

NO BID

If you choose not to respond, please fill out the enclosed NO BID form and return it to the City as soon as possible.

http://www.demandstar.com/ mailto:gayles@naperville.il.us https://www.demandstar.com/app/login

TABLE OF CONTENTS

GENERAL INFORMATION

SCOPE OF SERVICES

GOAL

TERM OF THE AWARD

PROBLEM DESCRIPTION

OUTCOMES DESIRED

MINIMUM QUALIFICATIONS AND EXPECTATIONS

SELECTION CRITERIA AND PROCESS

PROCUREMENT SELECTION TEAM

SELECTION CRITERIA

SELECTION PROCESS

TENTATIVE SCHEDULE

TECHNICAL PROPOSAL ELEMENTS

PRICING ELEMENTS AND ASSUMPTIONS FOR PROPOSERS

INSTRUCTIONS FOR SUBMITTING RESPONSES

APPENDIX A – Response Checklist

APPENDIX B – Detailed Scope of Work

APPENDIX C – Current Environment

APPENDIX D – City General Terms and Conditions

APPENDIX E – Professional Services Agreement

APPENDIX F – Procurement Forms

RFP 25-191: Electric GIS Utility Network Implementation and Migration

GENERAL INFORMATION

The City of Naperville Electric Utility (EU) is soliciting proposals from experienced and qualified organizations to perform an Esri Utility Network design, implementation and migration. The EU’s GIS data currently resides in an ArcGIS/ArcFM 10.8.1a sp3 Geometric Network model, with the target environment planned to be ArcGIS Enterprise 11.x and ArcFM XI.

SCOPE OF SERVICES

The selected vendor will be responsible for designing, implementing and deploying the new GIS platform at the Utility, and migrating existing data to the new system. The deployment also must maintain GIS integrations to other systems to support business needs. During the design phase the selected vendor will work with EU and the City’s IT department to ensure that data, integration, system functionality and infrastructure requirements are met.

More details are provided in Appendix B – Detailed Scope of Work.

GOAL

The goal of this procurement is for the Electric Utility to have the next generation of Esri GIS implemented in Production, which the vendor calls Utility Network.

TERM OF THE AWARD

The project shall proceed within 90 days of the Notice to Award. The schedule and the expectation of the city staff participation in the timeline and deliverables shall be outlined in the proposal and agreed upon in the contract.

The project has an anticipated completion date of June 30, 2027.

At the end of any contract term, the City reserves the right to extend this contract for a period of ninety

(90) days for the purpose of issuing a new solicitation.

PROBLEM DESCRIPTION

The Electric Utility serves 64,000+ residential, commercial and industrial customers, via 16 substations.

The City is approximately 39 square miles in area and the Electric distribution system the Utility maintains is 93% underground.

The Electric Utility began using ArcInfo and ArcFM in the late 1990s in the coverage based system.

Migration to the ArcGIS/ArcFM 8.x geodatabase system was performed in 2002. Since then, ArcFM extensions Designer, Conduit Manager, Fiber Manager and Responder have been added.

Since 2002, the Electric Utility has used ArcMap (with ArcFM extensions) as its primary resource for mapping its data. This Esri based product will reach end-of-life in March of 2028, therefore the EU needs to have its data and integrations migrated to Esri’s next generation of GIS, the Utility Network. A number of other business processes and systems are dependent on data from GIS, so these integrations must be maintained.

OUTCOMES DESIRED

This project will be successful if the following outcomes are achieved:

• The Utility has a fully functioning Utility Network GIS in Production for its Electric and Fiber datasets, for staff who edit data, as well as read-only users.

• Ensure compliance with cybersecurity best practices.

• Ensure that existing integrations to other systems function as required once the Geometric

Network model is migrated to Utility Network model in Production.

• The Utility’s Production GIS is compliant with the City’s version of GIS, and its datasets can be viewed by other departments, and Utility staff can view other department’s datasets.

MINIMUM QUALIFICATIONS AND EXPECTATIONS

The following minimum qualifications and expectations must be met by the proposer in order to be considered:

Proposer:

• Vendor is required to be an ESRI partner that has received Utility Network Management specialist designation by ESRI.

• They are also required to be a partner of Schneider Electric.

Staffing:

• A dedicated project manager will be provided for the duration of the contract term who will be responsible for day-to-day communications and coordination. The Project Manager will have at least 3 years’ experience.

• Experienced and dedicated Utility Network technical consultants will be provided for the duration of the project to ensure that the scope of work has been met at the project’s conclusion.

• Consultants are required to have worked on at least two Utility Network migrations from ArcGIS for Electric Distribution utilities.

• Project Manager and Primary Consultant are required to be US-based.

Availability:

• The proposer shall be available to begin work on the project within 90 days of the Notice to

Award.

• The Project Manager shall be assigned to this project until all contract work is complete.

• Major implementation milestones shall be conducted on site.

SELECTION CRITERIA AND PROCESS

PROCUREMENT SELECTION TEAM

A selection committee comprised of City staff from the Electric Utility and City IT Department will review, evaluate and score all proposals and interviews based on the criteria and weights defined below.

In addition to the selection committee members, non-scoring subject matter experts (SME) may also participate in the proposal review and/or attend the interviews/demonstrations to provide SME perspective to the selection committee members regarding the procurement.

The selection committee may conduct discussions with any proposer who submits an acceptable or potentially acceptable proposal. Proposers shall be accorded fair and equal treatment with respect to any opportunity for discussion and revision of proposals. During the course of such discussions, the selection committee shall not disclose any information derived from one proposer to any other proposer.

SELECTION CRITERIA

CRITERIA PERCENTAGE

Capability, Capacity and Qualifications of the Proposer 40 Suitability and Quality of the Approach/Methodology 40 Milestones and Deliverables 20

TOTAL: 100

SELECTION PROCESS

The awarded proposer will be selected based on a three-phase evaluation process.

Phase 1 – Technical Proposal Evaluation This phase will serve to shortlist the responding proposers to enter into the interview phase. The selection committee will review, evaluate and score all of the proposals based upon the information provided in the proposal using the criteria and weights defined above. The top proposers with the highest qualification scores may be invited to interview with the selection committee.

Phase 2 – Interviews If the City decides to conduct interviews, the shortlisted proposers will be scheduled to attend interviews with the selection committee (and SMEs, if applicable). Project Manager, as named in the proposals, are required to be in attendance. Other key team members are strongly encouraged to be present as well.

Following the interviews, the shortlisted candidates may be re-scored by the committee using the criteria and weights defined above to finalize the qualification scores.

Phase 3 – Scope and Contract Negotiations The proposer with the highest qualification score will be invited to enter into negotiations with the City regarding the scope of services and contract. Failure to reach consensus will result in the proposer not being considered further; the City may elect to begin negotiations with the proposer with the second highest qualification score or conduct a new procurement.

Following the completion of this phase, City staff will recommend the selected proposer for City Council/City Manager approval.

TENTATIVE SCHEDULE

9/5/2025 RFP issued to vendors.

10/2/2025 Last day to ask questions. All questions must be received via email to gayles@naperville.il.us by 12:00 p.m.

10/9/2025 Proposals should be submitted to the City by 2:00 p.m.

The contents of the response are listed under Technical Proposal Elements.

Week of 11/2/2025 Selected proposers will be notified that they have been chosen to be interviewed.

Week of 11/16/2025 Interviews will be conducted with each of the shortlisted proposers.

November 2025 Firm selected for award will be notified to begin negotiations.

January 2026 City Manager/City Council award.

January 2026 Notice to Proceed

TECHNICAL PROPOSAL ELEMENTS

The Technical Proposal outlines the proposer’s qualifications and proposed plan for addressing the requested item or service. Technical Proposals should specifically address each of the following elements. Proposers should present their proposal in the same sequence and with the same numbering scheme and headings shown in this section. If the proposer believes that a subject has been adequately addressed in another part of the Technical Proposal, then a cross-reference to the appropriate part of the narrative must be provided.

1. CAPABILITY, CAPACITY AND QUALIFICATIONS OF THE OFFEROR (40%)

1.1 Overview of the Responding Organization.

Please provide an overview of the company including but not limited to the company’s legal name and corporate structure, location of headquarters, technical staff and field offices, number of years in business and providing the requested services, and bankruptcy filings in the last five (5) years.

High scoring proposals will be able to demonstrate longevity of the company and principals with more than one successfully completed ArcGIS to Utility Network project for Electric Distribution Utilities.

1.2 Staffing.

High scoring proposals will provide an organizational chart that identifies the key team members by name and role, including the individuals proposed as the Project Manager and the Utility Network consultants. If any portions of the project will be subcontracted, please indicate which team members are subcontractors. Resumes of all identified team members shall be provided to outline their experience in this type of work.

RFP 25-191: Electric GIS Utility Network Implementation and Migration mailto:gayles@naperville.il.us

High scoring proposals will be able to demonstrate that the proposed Project Manager and other key staff members have experience in performing projects of a similar size and scope.

If a subcontractor is being used, high scoring proposals will demonstrate that the team members have worked together on similar projects in the past.

1.3 Subcontracting.

Please provide detailed information about any subcontractors you intend to use on this project. If no subcontractors will be used, please state so.

1.4 References.

Please provide at least three (3) references demonstrating experience working on projects with a similar scope of services for Electric Utilities. The references should include client name, contact person, phone number, email address, scope of services provided, and length of time services were provided.

If any aspect of the project is subcontracted, please provide at least three (3) references for each subcontractor. The references should include client name, contact person, phone number, email address, scope of services provided, and length of time services were provided.

High scoring proposals will provide references that include successful projects of similar scope and complexity for Electric Utilities.

2. SUITABILITY AND QUALITY OF THE APPROACH/METHODOLOGY (40%)

2.1 Project Approach/Plan.

Please provide your company’s project management methodology and a project approach for the scope of work. High scoring proposals will demonstrate a comprehensive understanding of the major tasks and sub-tasks, identify responsible staff, associated deliverables and any assumptions or risks that could impact the scope or timeline. High scoring proposals will also include functional milestones.

2.2 Pricing Proposal.

Please provide your pricing proposal. All costs must be included, the City will not pay separately for travel-related costs etc, so those expenses must be built into your pricing. High scoring proposals will provide milestone-based pricing. The City will not accept proposals that are based on hours worked.

3. MILESTONES AND DELIVERABLES (20%)

3.1 Milestones and Deliverables.

Provide a project schedule based upon the project approach provided in Section 2, which indicates the key milestones and deliverables associated with this project. High scoring proposals will indicate key milestones and deliverables.

3.2 Deliverables.

High scoring proposals will provide examples of deliverables that will be provided to meet the proposed milestones, as well as payment amounts for each.

3.3 Project Schedule.

Please provide a project schedule that is synchronized with the milestones and deliverables that were described above. High scoring proposals will include all milestones and deliverables.

PRICING ELEMENTS AND ASSUMPTIONS FOR PROPOSERS

Cost information is expected to be broken out into milestones and include the total cost to the City for the project based upon the Final Scope of Work. The proposal should include all anticipated costs for the consultant. There is no method for payments beyond what is outlined in the response, other than a change order, which the City strongly wishes to avoid.

Pricing element will be scored as part of section 2 Suitability and Quality of The Approach/Methodology/ Program.

INSTRUCTIONS FOR SUBMITTING RESPONSES

Proposals are due no later than 2:00 p.m. local time on 10/9/2025.

Your response must be received by the date and time specified. Proposals must be submitted electronically. All necessary documents are available through the City’s web-site. Downloading documents and submitting proposals requires registration with “Demandstar,” the City’s service provider since 2000. If you aren’t already a member, you can get a FREE AGENCY SUBSCRIPTION to the City of Naperville account by going to www.demandstar.com/register.rsp. Any incomplete submittals may be rejected as non-responsive. Infrequent or first time users of electronic bidding are requested to load their bids 24 hours prior to bid opening and the city will be available to help with any issues or questions up until 10/8/2025 at 2:00 p.m.

Proposals shall not be accepted after the designated response due date and time. It is the responsibility of proposers to submit proposals on or before the response due date and time.

Appendices

• A – Response Checklist

• B – Detailed Scope of Work

• C – Current Environment

• D – City General Terms and Conditions

• E – Professional Services Agreement

• F -- Procurement Forms

RFP 25-191: Electric GIS Utility Network Implementation and Migration http://www.demandstar.com/register.rsp

APPENDIX A – RESPONSE CHECKLIST

The following items should be included in the Proposer’s response to the RFP:

☐ Proposal Submittal Form Submit completed electronic copy of the Proposal Submittal Form.

☐ Technical Proposal Response Submit one (1) electronic copy (PDF format), which shall include the following sections:

☐ Capability, Capacity and Qualifications of the Proposer ☐ Suitability and Quality of the Approach/Methodology ☐ Milestones and Deliverables

☐ Redacted Technical Proposal Response Submit one (1) electronic copy (PDF format) of the Technical Proposal Response with information that may be exempt from disclosure under FOIA redacted. See the Illinois Freedom of Information Act section of the City’s General Terms and Conditions on page 20 for additional information regarding what can be redacted.

☐ Exceptions to the City’s General Terms and Conditions Submit one (1) electronic copy (PDF format) of any exceptions to the City’s terms, conditions or requirements set forth in Appendix D of this RFP. Such exceptions may be considered in the evaluation and award processes. The City will be the sole determiner of the acceptability of any exception. Any exceptions submitted may render the submission as non-responsive to the requirements listed.

☐ Exceptions to the City’s Professional Services Agreement Submit one (1) electronic copy (PDF format) of any exceptions to the City’s Professional Services Agreement set forth in Appendix E of this RFP. Such exceptions may be considered in the evaluation and award processes. The City will be the sole determiner of the acceptability of any exception. Any exceptions submitted may render the submission as non-responsive to the requirements listed.

☐ Procurement Forms Submit one (1) electronic copy (PDF format) of the following documents:

☐ Proposal Form ☐ Affidavit of Compliance ☐ No Bid Form

APPENDIX B – Detailed Scope of Work

1. System Assessment and Design:

• Meet with City staff for requirements gathering, reviewing the Electric Utility's current geodatabase model, customizations, extensions, integrations, and data readiness.

• Identify any potential risks associated with the migration process, including data discrepancies, and maintenance of existing customizations and integrations.

• Review City’s ESRI and ArcFM licensing plans for the Utility Network, and if necessary provide recommendations for updates to the plan.

• The City’s IT team will have the core Enterprise Esri GIS setup. Consultant is expected to review the City’s system architecture design for the Electric department’s Utility Network implementation, including capactiy and security requirements, and provide feedback on the design.

• For ArcFM XI and its extensions, provide guidance on the architecture, design, configuration and implementation where appropriate for the City’s IT team, including integration to Schneider Electric’s standard Designer XI hybrid cloud services deployment.

• Verify versions of ArcGIS Enterprise and ArcGIS Pro for compatibility with Utility Network and ArcFM versions, and City environment.

• Build Test software environment using City provided architecture.

• Evaluate mobile GIS needs for EU field crews, and develop a plan for this in the new environment. Currently crews VPN into the City’s network and connect to ArcGIS/ArcFM Viewer via virtual desktops (VDI), so no mobile specific software is in use. It is understood that VDI would not be a good solution in the new environment, so a plan needs to be developed for the best way for crews to access the data and view/query tools.

• Related to the above item, currently office staff that access GIS read-only (except for Control Room), do so via VDI as well, so there is no GIS software installed on their machines. Vendor will need to develop a plan for the best way for these users to access GIS and its tools, taking into account system speed and maintenance effort. It may, or may not, be the same solution as what will be used for the field crews.

• Identify target Utility Network data model/asset package for implementation, taking into account the ArcFM products in use by the EU, which should be the driver of this decision.

• Meet with EU staff and make updates to the chosen Utility Network data model to ensure required data and layers (including CAD reference) can be migrated to the new system, and integrations maintained to meet business needs. This includes related table records, as well as relationship class definitions, some of which are not based on Object ID but rather a unique ID generated by a SQL Server stored procedure.

• Include in the data model any fields needed to enhance the user experience while working in Designer XI for basic tasks like device searches etc.

• Include in the data model fields/classes needed to support EU’s new ADMS (comprising SCADA/OMS/DERMS) that will be implemented in parallel. Assume standard ADMS functionality requirements.

• Also, include in the UN data model the annotation expressions defined in the current geodatabase model.

• Work with EU staff to plan mapping of existing features and fields to target features and fields in UN model, to be used during data migration.

• Consult with Schneider Electric on ArcFM XI series current functionality and modeling requirements for Fiber Manager, Conduit Manager and Designer. Plan migration process for Compatible Units, Favorites, Composite Favorites and ArcFM Map Books.

• Configure and implement the ArcFM components and editing tools listed above.

• Plan editing workflow for Designer and the other ArcFM extensions.

• In the Utility Network model, work with EU to configure attribute rules and contingent values as needed.

• Configure the model to allow for Designer XI partial push functionality.

• Work with EU to plan detailed data migration paths from EU’s existing GN data model to the newly developed UN model.

• Review legacy mapping and data modeling and plan for any required data editing to be performed as part of the migration phase. Also, include any items identified here that need to be included in the UN data model. More details on legacy modeling issues are provided in Appendix C.

• Review the existing symbology and System Stored Displays used in GIS maps and develop a plan for transitioning to views in the new system. This includes detailed analysis of existing Unique Value renderers, using more than one value field, to support EU staff expectations for mapping as well as construction prints. This needs to be implemented for subtypes in the Utility Network data model that correlate to feature classes in EU’s existing Geometric Network model.

• Work with EU staff to plan for creation of Distribution maps and Duct Bank maps in target system that meet EU’s requirements. Duct Bank maps are currently created using out of the box ArcFM Map Books. Distribution maps are created using an internally developed customization that is needed to meet EU’s requirements.

• Work with EU staff to evaluate existing custom components, including ArcObjects solutions, AutoUpdaters, custom tools, and commands to determine those that will need to be ported to the new system. For those items identified to be moved forward, plan process for porting them to the new system while maintaining the current level of functionality.

o For one example, EU needs to continue to have Work Locations in designs created automatically with the correct EU Site Location Number when a device is added for install. This is an existing customization that should not be lost due to the move to the Utility Network.

• Plan for recreating existing integrations with other systems: MDMS, Cityworks, Irth Utilisphere, and customer database, to maintain business continuity at go-live.

• For Cityworks, Naperville has custom integrations on both the Designer and Cityworks sides.

No changes in software are planned for Cityworks as part of this project. For Designer, Schneider wrote the customizations and EU owns the source code. Selected vendor can either subcontract with Schneider for this update, or make any needed changes themselves and test, in which case EU will provide the current source code.”

• Identify tools that can be used within ArcFM XI and Designer to produce construction prints that meet the EU’s requirements.

• While the large majority of data errors that could impact the UN model (identified by a recent vendor readiness assessment) have already been cleaned up by EU staff, run checks for any remaining errors and plan any remediation, if necessary. Categorize items to be remediated as either updates in the source data, or updates that should be made during the migration.

• Work with Naperville to plan Change Management, to be implemented in the following phase.

• Note that SQL backup files of the existing system, as well as symbology files and lists of existing customizations and integrations can be provided to planholders that have signed a Non-disclosure agreeement.

2. Implementation and Migration:

• Build Production software environment using City provided infrastructure.

• In all stages, work with City staff to conduct user and system acceptance testing.

• Conduct first test migration of data, assess the results and plan for second test migration.

• Design, build and test integrations as identified in previous phase.

• Design, develop and test customizations that will need to be carried over to the new environment as agreed upon in previous phase.

• In parallel, EU will be implementing a new, advanced utility management ADMS system that includes SCADA/OMS/DERMS etc. functionality. Any GIS configuration needed within the out of the box GIS tools for exporting the distribution network model for that system will be performed and tested.

• Conduct second test migration of data, assess the results and finalize the plan for Production migration, which should include keeping system downtime to a minimum.

• Perform manual edits to data as scoped during data model and legacy mapping assessment in previous phase.

• Implement editing tools and workflow for ArcFM Designer, Conduit Manager and Fiber Manager.

• Implement the mobile GIS access plan that will be used by field crews, as well as read-only access for office staff, that were planned for in previous phase.

• Conduct acceptance testing with Naperville prior to Production migration, and plan for any necessary changes to the process based on test results.

• Provide Naperville with a detailed data migration QA/QC and remediation plan for approval.

• In preparation for Production system cutover:

o Work with City’s IT department to ensure required ArcGIS Enterprise and ArcFM XI web services are deployed correctly and working prior to Production migration.

o Load EU’s existing Designer Compatible Units and Favorites into Designer XI.

o Migrate EU symbology, ArcFM Stored Displays, Composite Favorites and Map Books to their ArcFM XI equivalents.

• Migrate Data to Production Utility Network environment, including:

o Electric Distribution and Transmission, Conduit (maintaining compatability with Conduit Manager XI), and Fiber (maintaining compatability with Fiber Manager XI) data, based on data mapping plan developed in previous project phase.

o Existing SDE database versions, maintaining ties of Designer versions to their designs in the new Production environment.

o Perform data edits that were categorized in previous phase for completion during data migration process.

o Re-project data to NAD83 HARN, for consistency with other City datasets.

o Execute QA/QC plan provided earlier, and remediation if necessary.

o Production cutover must keep business day downtime to an absolute minimum, since

T&D Engineers, field crews, line locators, and Control staff rely on GIS in their day to day work. Respondents need to include in their proposals the number of business days downtime that they will schedule for cutover.

• Ensure that the role of GIS in business processes is maintained, including existing GIS custom tools, integrations and AutoUpdaters.

• Assist City IT if any problems arise with ArcGIS Enterprise or Portal in the new Production environment as part of the migration process.

• Work with City staff on system performance testing and provide direction on improvements, if necessary.

• Work with Naperville to implement Change Management plan agreed upon in previous phase.

• Conduct training as part of Change Management plan, both for users and administrators of

ArcGIS Pro/ArcFM XI and its extensions. For EU administrators, include training on ArcGIS Portal management and publishing in the new environment.

• Fix any data errors introduced as part of the migration process.

• Be available for remote support for sixty days after successful Production cutover.

• Note that source database contains 11 non-versioned tables owned by the process user with a naming convention that starts with “NPV_”. These are used by custom applications and cannot be discarded. Moving these to another database (or leaving them where they are), can be negotiated with the City during the project. This is a minor, but not unimportant item for EU.

APPENDIX C – Current Environment

Management of the backend servers and databases is handled by the City’s IT department. The version of ArcGIS Pro/Utility Network to be used at EU is required to be compatible with City’s ArcGIS Enterprise (planned to be 11.x), since it will reside in that database environment and EU needs to be able to view and interact with other department’s datasets. Note that the Water Utility is currently in process for deploying the Utility Network.

The EU’s current ArcFM geodatabase is a separate geodatabase from other City departments. Citywide, the departments use a common landbase, and are able to reference (read-only) each other’s datasets, some of which is very important for the EU, including the landbase, Public Works Street light data and three Water Utility datasets. This project’s focus is on the Electric Utility’s modeling, its data migration to UN, and integrations and customizations that are used to support key Utility business processes.

The different systems that the current geodatabase has integrations with include Cityworks, MDMS (via BizTalk), Customer database (SQL Server), irth Utilisphere (via map services) and Synergi Electric. The Synergi Electric integration changes needed for the Utility Network will be planned and executed separately by DNV and are not in scope for this project. Data requirements for Synergi will need to be accounted for during data modeling for UN. The EU has in its possession a spreadsheet from DNV containing these items, which will be provided to contracted implementation vendor.

EU Geodatabase Model Key information about the current geodatabase in use at Electric is outlined below.

Electric Distribution dataset Contains a number of feature and relationship classes that make up the 12kV Distribution Network, as well as supporting structures, and a variety of other classes of non-Electric items that are relevant to the Utility operations. Note that there are some classes that are currently empty, but this does not mean they shouldn’t be accounted for in the UN model.

Items that can be dropped from the model are:

• Communication Cable – this was used for Fiber cables prior to Fiber Manager implementation. It is no longer needed.

• Streetlight – these are managed in Public Works geodatabase, so this class is not needed.

• Test – this class can be dropped.

• Field called ‘TAG’ – this exists in a number of classes, it was a Unique ID in the original Coverage system and was migrated to the Geodatabase. It is not needed now and can be dropped. This applies for all feature classes and tables in the geodatabase, not just the ones in this dataset.

There are a set of Duct Anno classes (example, FiberDuctAnno) that are empty but are required in GN model for Conduit Manager to manage data and relationships. It is unclear to EU at this time if these will be needed in UN model, so that will have to be determined in Phase 1 of this project.

There are also a few classes that are used for graphic depiction purposes with Conduit Manager data like Breakout and Foreign Duct. The data they are depicting will need to be carried over to the new system in some form.

The dataset also includes a couple of classes that are part of the GN but are not directly representative of actual devices in the field, Isolation Point and Termination Point. Isolation Point is used in a couple of scenarios for status Open/Closed. How this data will be carried over and modeled in the UN will have to be discussed with EU.

Distribution Geometric Network ArcFM’s Feeder Manager 1.0 is used by EU to manage its 12kV Feeder System. The ElectricDstNetwork class in the Distribution dataset is what this is built upon. Circuits have connectivity from the 12kV Feeder Breakers in the Breaker class down to the customer meters, which are represented by the Electric Service Bank class and the Electric Service related table, which allows the depiction of Meter Banks and individual Meter sockets in the model. The Geometric Network currently has no multi-feeds or loops, and this is the normal state in the Default version of the database. EU always endeavors to maintain this network data quality in the Default version and expects that this should be the case when the current model is given to the contracted consultant.

While we consider the network to be clean in the context of the GN/Feeder Manager 1.0, it is understood by EU that the UN has different and stricter requirements which will probably require changes to rules, and edits of the network data. The data has over history migrated from AutoCAD to Coverages to Geodatabase so the data model is non-standard and there are legacy holdovers from the past in how some portions of the network are modeled that will need to be addressed during the planning and execution of the UN migration. The transition from Overhead to Underground at a Riser Pole is an example of one such scenario. Known legacy data modeling items have been identified previously by EU and a consultant, and are described later in this section under “Known Legacy Items”.

Electric Transmission dataset Contains a small set of classes representing a simplistic view of the 34kV and 138kV conductors that connect substations. There is also a geometric network class defined although its use is limited. The Line Numbers on the conductors are maintained in user entered fields. This data doesn’t change frequently. The main value is in the relationships the conductors have to the Conduit System, and their representation in Conduit Manager cross-sections. Equipment in Substations upstream of the 12kV Feeder Breakers is currently not depicted in EU’s GIS. A planned future state for adding more Substation equipment in the model post-migration will be taken into consideration, but adding the data is not planned to be part of the migration process.

Fiber dataset Contains Fiber Manager classes and network for managing EU’s Fiber data. All Fiber usage by EU is to provide high speed communications for our own equipment and buildings, as well as Non-Utility City-owned buildings.

Map Production Dataset Contains map grid and other classes used for producing the department’s hardcopy maps.

NED Annotation Address and Road Name non-feature linked annotation classes.

Designer Dataset Classes used by ArcFM Designer.

Note, the SSP_Replay dataset can be dropped, as well as any standalone tables with REPLAY in their name.

Tables Database contains a number of business tables, as well as tables needed for ArcFM extensions.

Note, the table XFMRLOAD can be dropped.

Versioning Due to the architecture of ArcFM Designer in ArcMap, EU must maintain ArcSDE versions over a long period of time containing engineering design data. Currently there are over 250 ArcSDE versions in the database. While EU will delete unneeded versions at time of migration, this gives a ballpark idea of the version migration that will be required. The vendor that performs the production implementation and data migration will be expected to transition this data to the target system without loss of connection to their work requests and designs.

Symbology EU has long established symbology used in its hard copy maps and GIS. The symbology files in use with GIS will be provided and transitioning to the target system will be part of the migration project. Line style, font, symbol and a custom font file are currently in use to represent the EU’s data in GIS and hardcopy maps.

Extensions EU uses Schneider Electric’s ArcFM, Designer, Conduit Manager, Fiber Manager and Responder, and plans to continue with XI series vesions of each, except for Responder which does not have an XI version.

Customizations Having been in Production with ArcGIS geodatabases since late 2002, EU has a mature system which makes extensive use of custom components, including the ArcFM AutoUpdater framework, for customizations that are used for maintaining data quality, adherence to data requirements in GIS, and integration with other systems, such as Cityworks. EU uses both out of the box ArcFM AutoUpdaters, as well as a significant number of custom AutoUpdaters. Documentation on AutoUpdater assignments are maintained by EU. The functionality of the AutoUpdaters will need to be ported over to the new system, using technology that is appropriate there, and which is capable of maintaining the same level of functionality.

Custom tools and commands using ArcObjects are also used for a variety of tasks in ArcMap to provide users with easy to use functionality for items like searches, reporting, and maintaining data integrity.

There are also a number of standalone applications that make use of ArcObjects for tasks like reporting, batch reconciling, exports for MDMS, and Hosting Capacity data studies etc.

Some of the ArcFM and ArcObjects customizations also make extensive use of .NET Framework classes for a variety of tasks. One example is use of the SqlClient class for accessing non-SDE database data and stored procedures. In the Utility Network/ArcGIS Pro environment EU will still require the ability to make use of .NET Framework classes as it has throughout time in the ArcGIS 8.x, 9.x, 10.x environments.

EU’s custom codebase includes nearly 40 ArcObjects solutions and at least 17 AutoUpdater solutions.

There are also custom toolbars, as well as custom installers so that not every class has to be installed separately. If respondents require more information about EU’s customizations for planning purposes only, that can be provided. A large majority of the customizations were developed in-house, and even for those that were developed by vendors EU owns and maintains the source code.

Integrations As mentioned earlier, EU has a mature GIS environment, and this includes custom integrations with other systems to support key business processes. Following are required to be ported to the new system.

MDMS – EU’s Meter Data Management System is Harris SmartWorks (formerly called MeterSense). EU developed a standalone, custom ArcObjects application that exports network data in text files that are compliant with SmartWorks flat file upload format. The application checks out an ArcGIS license, reads the Default version of the Electric geodatabase, and exports the MDMS text files. It is run nightly (on business days) via a Windows scheduled task.

Cityworks – As part of a citywide standardization, EU transitioned to using Cityworks as its work order system in mid-2023. Custom integrations exist for the following facets of Cityworks with GIS.

• GIS Asset management – ten custom AutoUpdaters that were developed in-house (inlcuded in the solution count above) are currently assigned to 32 classes to populate fields with values that are used to enable integration with Cityworks, as well as querying GIS data within Cityworks. Any required updates to these for UN are in scope for this project.

• Work Orders – custom applications were written by Schneider to call Cityworks web-services for the integration between ArcFM Designer and Cityworks Work Orders, for Work Order creation in Cityworks and Estimate transfers from Designer to Cityworks. Any required updates to these for UN are in scope for this project.

• Compatible Units/Inventory – Cityworks was also transitioned to be the system of record for utility compatible units, and thus the source for Designer compatible units. Access-based customizations were developed by Schneider for analyzing differences between the CUs in the two systems, and with user input, updating the CU definitions and usage in Designer.

• If any updates are needed on the ArcFM Designer XI side of this CU customization then that is in scope for this project.

Irth Utilisphere – is used by the Operations division in the daily management of locate tickets and includes display of GIS data via map services. According to Irth support, they have no specific ArcGIS Enterprise requirements for software versions etc. Consultant is expected to work with City IT department to ensure new map services are created that meet Utilisphere requirements.

Customer Data – there is not a direct integration to the City’s DB2 based CIS system, however data about customers and their meters is used in a number of GIS related custom applications, including but not limited to OMS. Data is stored in a standard SQL Server database and is accessed using standard .NET Framework functionality. This data will need to continue to be accessible from GIS applications after the migration to Utility Network/ArcGIS Pro. Note that daily updates of this customer/meter database is handled outside of GIS and is not in scope for this project.

Synergi – Synergi Electric is used for engineering analysis tasks. A custom ArcObjects DataPrep add-in was written by DNV to generate csv files that can be loaded into Synergi for modeling. DNV will be contracted separately by EU to plan and code the integration with the Utility Network model, so this is not in scope for this project.

Known Legacy Items

Items below have been identified previously either by EU or assessment consultant and will need to be considered for possible resolution before or during data migration. Generally speaking, EU prefers rule updates over mass data changes, given the Designer SDE versions present in the geodatabase and the need to reconcile/post them once they reach the As-Built stage of their lifecycles. Pros and cons of how these items can be handled will need to be reviewed and discussed by vendor and EU, prior to EU making a final decision on them.

• Risers are represented in a Table called Riser in EU’s model rather than a Feature Class. It has a relationship to the Pole feature class, which shows a different symbology for Pole locations that have Risers. The result of this is that at Pole locations where there is a Primary Conductor transition from overhead to underground, these two cable types are directly connected to each other, since there is no riser cable feature class with geometry. If the underground branch off is fused, there is a Fuse feature with a subtype of OHFuse (code =

1) on the underground conductor near the Pole, for clarity of map viewing. While this is not a problem for Geometric Network or Feeder Manager 1.0, it is understood this may be an issue with the Utility Network. Similar scenario exists at OH to UG transitions with Switches on 3 phase Primary conductors. Readabililty of hardcopy maps and GIS still needs to be accounted for.

• Termination Points in general (both on OH Primary and Secondary) need to be evaluated, currently they are part of Geometric Network, this may not be what we want to do in UN, although at the end of OH conductors we do want to continue to show a similar symbol indicating the end of an OH line at the Pole.

• There are some locations where there is a UG Service conductor fed by the OH system, either an OH Secondary conductor, or directly from OH Transformer Bank.

• Another similar case is OH Service conductor fed by an UG Transformer.

• Normally Open Transformers have an attribute of Open in GN connectivity model, which also can be used for querying. They have an Elbow on the closed side Primary conductor and an Isolation Point on the Open side of the Primary. Isolation Point will probably be migrated to an Open Elbow in the UN model. It is understood that having the Transformer itself with a status of Open in the UN network will cause customers to be unfed (not the case in GN model), so these values will need to be altered to Closed in UN migration, and an extra field will need to be added to indicate the device is normally Open, for querying and reporting.

• Existing GN relationships that Electric Service records have to Transformer Bank and Electric Service Bank feature classes must be maintained in UN. Electric Service records represent meters in the data, and Electric Service Banks represent meter banks. It is also critical to maintain the Transformer Bank – Electric Service relationship. The Electric Service records cannot lose their attributes from the source GN data. These relationships and data support key business processes in other systems.

• DER locations are modeled in GN the same as other service points, with a Subtype designation indicating DER status, for symbology. Modeling of these locations and their attributes will need to be accounted for in UN model, and note that all DER types need to be handled, not just solar.

• There are places in the GN network where conductor features connect directly to each other, which are not data errors that need to be corrected. For example, a change in size from 750 to 1000 in a Manhole or Handhole without an electric device. This is not an error in GN, but is not a part of the standard UN data model. A decision will have to be made about how these should be handled in UN, whether through data edits, or custom rules.

• In GN, BusBar (subtype of Connector class) is used as part of Pad-mounted Swtichgears and should be migrated as such. Note that BusBar features connect to each other in the internals of the Switchgears without a device between them, which is correct. This may require a custom rule in the UN to allow for this.

• In GN, Jumper (subtype of Connector class) is a legacy from the migration from Coverages into the Geodatabase model. Some items weren’t physically connected in the source, so Jumpers were added automatically by the migration vendor where needed to meet GN’s physical connectivity requirements. Also, OH Conductors have always been shown in EU’s mapping as offset from Transformers they connect to, so Jumpers were added in these cases as well. These result in linear to linear connections without a device present. A rules decision will need to be made by vendor and EU on how to handle this in the move to UN.

• At Pedestals, it’s been noted that there could be stacking issues in UN with our current Pedestal placements in GN. Clarification is needed on this and a mutual decision on if anything really needs to be done. They are not part of the network anyway, so possibly this could be handled through a rule.

• Some Pad-Mounted Switchgears have unused Fuse and/or Switch compartments, currently in these cases we show just the Bank features with no Phase or Status, and no related unit records. These are for future use and are placed automatically as part of Composite Favorites.

This speeds up both the placement of Switchgears, and future additions since no graphic features have to be placed individually and connected up correctly by users. Need to determine if these can be migrated as-is into UN.

APPENDIX D – CITY GENERAL TERMS AND CONDITIONS

BY SUBMITTING A RESPONSE, THE PROPOSER AGREES TO BE BOUND BY THESE TERMS AND

CONDITIONS. PROPOSERS OR THEIR AUTHORIZED REPRESENTATIVES ARE EXPECTED TO

FULLY INFORM THEMSELVES OF THE CONDITIONS, REQUIREMENTS, AND SPECIFICATIONS

BEFORE SUBMITTING PROPOSALS, FAILURE TO DO SO WILL BE AT THE PROPOSER'S OWN

RISK AND HE CANNOT SECURE RELIEF ON THE PLEA OF ERROR.

RFP PROCESS

EQUAL OPPORTUNITY

The City will make every effort to ensure that all proposers are treated fairly and equally throughout the entire advertisement, review and selection process. The procedures established herein are designed to give all parties reasonable access to the same basic information.

PROPOSAL FORMS

Proposals must be accompanied by a fully executed Proposal Form and Affidavit of Compliance, provided in this package, and shall be submitted on the forms provided or in an identical format typed by the proposer, properly signed in the appropriate places, and submitted in accordance with Instructions for Submitting Responses.

QUESTIONS

All…