Welcome

EGUG 2013 San Antonio

§ Service area -1,566 sq miles

§ Electric customers -740,000

§ Natural gas customers -330,000

§ Regular employees - 3,400

Our Service Area

EGUG 2013 San Antonio

Our Region

CPSE Electrical Stats

§ Total UG cables in linear miles

§ 4,863 miles UG Primary

§ 5,333 miles UG Secondary 10,196 Total Miles of UG

§

§ Total OH cables in linear miles

§ 7,731 miles OH Primary

§ 5,748 miles OH Secondary

§ 13,471 Total Miles of OH

§ Total Conduits/trench in linear miles

§ 7,940 Total Miles of Conduit

§ # Manholes/Cable chambers/Handholes

§ 158,433 Total UndergroundStructures

§ #Transformers

§ 219,038 Total Transformers

§ # Poles

§ 426, 246 Total SupportStructures

SDE Versions: A Traveler’s Tales

SDE Geodatabases Good qMany editors at once

q RDBMS querying

q RDBMS platform choices

q Geometric networks

Bad q Added tiers

q Object/row mismatch

q Reconcile/post of versions

q Forbidden changes

Versions (3/2013)

Implementing a forbidden change: geometric network creation with

versions

Underground Geometric Network

v It enables tracing the structural connections between conduits and facilities like manholes.

v It is a prerequisite for ArcFM Conduit Manager.

Someone forgot to create one in 2006!

vCreating the UG network would have taken about five minutes in 2006.

vWhen creating a geometric network, all participating feature classes must be unversioned.

vBy 2011 there were thousands of versions representing electrical designs.

No warranty-voiding fun

vWe use methods vetted and accepted by our contractors: Schneider Electric, ESRI, ABB…

vIn addition, we must always maintain the integrity of GIS integration with SAP, ARM WM, ABB OM, CYMDIST…

There must be a well-established method, right?

vProbably not at 9.3.1 in 2011.

vDevelopment required.

vMinimal loss of work required.

Formal project initiated

§ Schneider Electric to provide the process and supporting software.

§ ESRI to advise Schneider Electric.

§ CPS Energy to perform extensive acceptance testing and implement the process.

Project began July 2011 and ended January 2013

Project Duration

• Similar to the gestation time of the sperm whale…

How to create the UG network

1. Determine which versions contain conduit and underground structure changes.

2. Clean out as many such versions as possible.

3. Report conflict details for them prior to reconciling.

4. Reconcile all of the remaining “UG” versions with their immediate parents.

5. Export delta XMLs representing these versions.

6. Delete them. Unversion the UG network feature classes.

7. Create the UG network. Version the UG feature classes.

8. Import the exported deltas to re-create their versions.

9. Hope that this process can be reused.

Implementation

§ Oracle SQL and PL/SQL querying the geodatabase schema.

§ Windows console apps, written by Schneider leveraging standard ArcGIS Objects for versions, distributed geodatabases, etc.

Acceptance testing rounds

Ø Initial unit testing starting July 2011.

Ø FAT at Schneider, December 2011 to January 2012.

ØTesting prior to onsite FAT at CPS, February 2012 to August 2012.

ØOnsite FAT at CPS, August 2012 to September 2012.

Ø SAT at CPS, September 2012 to November 2012.

Acceptance testing content

Ø Integration with the following systems: ARM WM, SAP, OMS, CYMDIST, Synergee, mobile laptops.

Ø Integrity of the newly created UG geometric network.

These tests were repeated for each CPS testing round.

ArcFM DesigneróARM WM integration tests were by far the most time-consuming.

Consequences of testing

v Switch from 9.3.1 to 10.0 for the “cutover”.

v Addition of global ids (guids) for the duration of the process.

v Keeping the global ids was incompatible with ArcFM/Designer customizations.

v Removing the global ids prevented imports from being made after SDE was returned to service.

v Preservation of work location object IDs—they are used in another system, ARM WM, for designs.

v SDE compression step after the UG versions were deleted.

v Network rebuild utility app to run after the import.

More consequences of testing.

v Procedures to run parallel processes when possible.

v Training of three GIS analysts on all steps, to enable running 24/7.

v Creation of monitoring utilities by Schneider to notify analysts when processes hanged or failed.

vMerger of the UG network creation with local GIS software upgrades, to take advantage of all the acceptance testing and downtime.

Results vThe main cutover steps were performed

in production from December 19 to 24, 2012.

vEnd users were allowed back into the system on January 9 after system upgrades, burn-in, and rebuilding of geometric networks in imported versions

vAbout 5% of design versions did not make it through the importation step.

The Lessons Ø Measure twice, cut once. This started with a tiny

SDE configuration omission!

Ø Automate configuration tasks as much as possible.

Ø Use global ids.

Ø Don’t take the shortcut of abusing OIDs.

Ø Do be more careful than we were about cleaning up geometries before imposing a geometric network on them.

???