MTEMC’s State 0 Changes With 1700+ Versions Intact

Esri User Conference 2016

Agenda

Introductions Business Drivers Solution Overview Results

IntroductionsAn-Louise De Klerk| Middle Tennessee Electric Membership Corporation• GIS Coordinator• Manages All Aspects of the GIS Department• Facilitates Interaction Between IT and the Business Users• PMP & ICP Certified• 2016 Special Achievement in GIS (SAG) Award

Skye Perry | SSP Innovations• Principal Consultant• Esri & Schneider Electric Technical Architect• Utility-Focused ArcGIS Online Specialty Partner• Began work with MTEMC in 2013

Business Drivers

MTEMC is a Heavy User of Utility GIS Esri Core ArcFM + Designer for Editing Custom Web Viewer for Back Office Viewing ArcFM Viewer for Field Viewing + Inspections Responder for Outage Management

This project was used as a catch all for three types of changes: Data Model Changes Mass Data Updates Various System Changes for Performance Improvement

Business DriversDesigner Uses Versioning for Long Transactions

Typically 1700 – 2000 versions at any given time Versions exist from initial design through to as-builts

(weeks, months, or even years)

Versioning makes applying these types of changes difficult Some changes could be made in a versioned environment but would result in large

numbers of edits Other changes cannot be made in a versioned environment

A few examples…

Create Related Records OH & UG Secondary Utilize a Quantity Field Instead of Related Conductor Info

Records Designer only sees a run of “1” conductor (regardless of the value)

Desire to create related records for consistency with Primary & to better support WMS Integration using OOTB Designer

Business Drivers

Similar Issues for: Fault Indicators Span Guys

Business DriversDuplicate/Split Records

Designer does not support a Quantity field via Work Function Tool If you need to remove an Assembly with QTY=3, you have to first create three Assembly

Records and add Remove CU’s to them individually

Split out all existing data for Assemblies into individual records

Business DriversData Updates

Transformer Bank – Rated KVA: Based on sum of unit KVA values Pole – Joint Use Count: Updated based on number of attachments OH/UG Primary – Update Child Label Fields OH Primary – Neutral Ownership Field for shared neutrals Switch Unit – Populate Data from Parent Switch

NOTE: In several cases, AutoUpdaters were maintainingcurrent data, but significant missing data was in placeprior to adding the AutoUpdaters to the system.

Business DriversData Model Updates

Add Solar Farm Data as Generator Feature Class Remove Unused Fields Across the Data Model Convert Some Classes to SQL Server Geometry Type Implement ArcFM Voltage Levels

Business DriversSingle Geodatabase Merge

MTEMC Had Multiple SQL Server databases supporting GIS Esri recommendation to merge to a single database

Use individual schemas within the single database

Business Challenge A lot of change in the geodatabase(s) Changes range from hard to perform with versions to impossible to

perform with versions

The Solution

Engaged with SSP Innovations to Utilize All Edits State 0 Technology

Extracts All Versions to an SSP Format Includes Adds, Deletes, Updates, Anno, etc.

Delete All Versions & Compress to State 0 Perform State 0 Tasks Recreate Versions from SSP Format

Created with Same Version Name Resynchronize Designer XML with Replayed Edits

All Edits State 0

Standard SSP Workflow Works with:

Spatial Reprojection Network Updates Conflation Updates

BUT the Single GDB Merge essentially required a completely new geodatabase New class names New class IDs

MTEMC Process

Version Extraction & Model Updates

All Edits State 0 Standard Process Copied Production to Test Instance

Prod remained online – read only Extracted All Versions to SSP Format

Includes Adds, Deletes, Updates, Anno, etc. Delete All Versions & Compress to State 0 State 0 Processing – Scripted Processes:

Data Model Changes Data Updates

Single GDB Merge

Create a New Geodatabase New (2nd) GDB Created Data Copied from other Databases into New GDB

GIS Data Copied Using Python Non-GIS Data Scripted via SQL Scripts (i.e. PX Framework)

All Edits MetaData Updates Update Table Names for New GDB Ex:

MTEMC_Mobile.GISAdmin.CustomerPoint MTEMC_GIS.GISAdmin.CustomerPoint

New Custom Code Installer

Code Updated to Handle Database Rename ArcGIS / ArcFM GIS Client Responder GIS Client Nightly Batch Code ArcGIS Online Collection Routines

Bring the Versions Back to Life

All Edits State 0 Standard Process Recreated 1700+ Esri Versions Data Model Changes / Data Updates Applied Inline Designer XML Updated for Any Class Name Changes + Object IDs

Update ArcFM Configuration

Reconfigure Configuration for Single GDB Pre-

Exported From Previous Test Instance

Matched New Table Names Design CU Library Updated for New

Related Tables (per model changes)

Implement Voltage Levels

Apply Changes to Enable Voltage Levels with Feeder Manager 2.0

ReclosingDevices::CircuitSwitcher Becomes Ultimate Source ReclosingDevices::CircuitBreaker Becomes Sub Source Data Model & Configuration Changes Applied Manually Establish Data Connectivity in a Version to Test

Transmission Busbar connected to Circuit Switcher

**Custom Feeder Sync AU Created to Apply Sub Source Feeder ID to FeederID, FeederID2

Bring the New GDB Online

Copy the Validated new GDB from Test to Prod Loaded the New GDB into Production Replaced System Stored Displays with Single GDB

Versions Installed Updated Software Released to the Users

Power Users Applied Substation Updates Connected Busbar Validated Connectivity from Ultimate Source & Sub

Sources

What About Responder?Some Challenges But it Worked! Had to Update All Internal Class IDs to Match New GDB Based on Voltage Level Config It was Able to Use the New Circuit

Switchers Updated Configuration Updated Custom Code Brought Services Back Online Existing Incidents Were Kept Intact

Only Item that Did Not Come Across Correctly was the Existing Jumpers (only 2 of them and the users redrew them after Responder was online)

What About ArcFM Viewer? New Replicas Created

New Initial Extract Replication verified multiple times

Included new substation data Tests Included Tracing and Other Network Analysis

Clients Picked Up New Data On Next Sync

Project Success Deployed Over the Course of 6 Days (Tuesday-Sunday)

Included Separate Environments for Designer & Responder Included Disaster Recovery for both Designer & Responder Environments

Several Test Runs Until Everything Worked as Expected Included Validation Checks for All Updates to the System (counts, QA, etc.)

Worked with our Partner True North on the Web Components they Support

System Was Back Online Monday morning Users able to open Designs without issue Users able to manage Responder outages without issue

Questions?

Skye PerryPrincipal Consultant

SSP Innovationsskye.perry@sspinnovations.com

An-Louise De KlerkGIS Coordinator

Middle Tennessee EMCan-louise.DeKlerk@mtemc.com

MTEMC’s State 0 Changes With 1700+ Versions Intact

Esri User Conference 2016