Do you know what your custom code does?

A Conscious step toward COTS

Kyle F. Erickson Brittany Wall

APS Background

• Arizona Public Service was incorporated in 1886 ‒ affiliate of Pinnacle West Capital

Corp. • APS generates, delivers, buys,

and sells electricity • APS Serves in 11 of Arizona’s 15

counties • ~35K square miles of service

territory • ~30K miles of T&D lines • APS Statistics:

– ~1500 Feeders – ~5M network features – ~1.2M meters

Major T&D Applications

• Maximo 7.0 - Work and Asset Management

• ArcGIS 10/ArcFM 10 - GIS • PeopleSoft - Accounting & HR systems • Autodesk 2013 products – T&D Design • ABB NDMS v47– Distribution Operations

Management • CIS – IBM with heavy customizations

APS Application History • 1999 – Power Tools

‒ ESRI v7 - arcstorm ‒ M&M v7

• 2002 – ArcGIS/ArcFM

‒ ESRI 8 ‒ ArcFM 8

• 2003 – ArcGIS/ArcFM

‒ ESRI 8.3 ‒ ArcFM 8.3

• 2006 – ArcGIS/ArcFM

/ArcIMS ‒ ESRI 9.3 ‒ ArcFM 9.3

• 2008 – ArcGIS/ArcFM/ArcGIS Server ‒ ESRI 9.3.1 ‒ ArcFM 9.3.1

• 2010 – ArcGIS Server

‒ ESRI 10.0 ‒ ArcFM 10.0

• 2012 – ArcGIS/ArcFM

‒ ESRI 10.0 ‒ ArcFM 10.0

Stats on Custom Code

• Obsolete (17%): 18 VB6 Standalone Programs • Obsolete (46%): 67 VB6 libraries/executables • .Net (37%): 40 C#.Net libraries/executables • ~850k lines of code

Problem

• Upgrades too complex, take too long, always something is breaking

• Issues always get through to production • Upcoming projects like DOMS, Smart Grid,

and DMS require GIS • All the people that knew why we did

things are gone • Everything we did was reactive instead of

proactive

Solution

• Move towards a COTS GIS • Gather requirements • Evaluate all custom code • Evaluate all core products (what has changed

that we can use instead of our custom code) • Evaluate data model • Create / Update test cases • Create / Update documentation (Biz and IT)

Approach

• Requires support, fresh thinking, communication, follow through, and leadership

• Need good vendor relationships – establish ELAs and maintenance contracts

• Focus on business goals instead of functional requirements

• Users have to consider new business processes

• Document everything

Approach

• Use more QA/QC rules prior to posting • Keep in the mind the tradeoffs of

customizations – Scalability – Extendibility – Inadequate documentation – End of life or unsupported technology – Resource skill sets – Component dependencies

Approach

• Re-evaluate the data model – Purpose driven, end goals clearly stated and

reinforced • COTS demonstrations with use cases • Testing is a must from users with a variety of

roles • Agile approach is best

– Small, incremental changes on ongoing basis – Scheduled/predictable release cycles

• Get it to the users and let them put it to work – System will continually evolve and improve – Make sure you plan your budget

Benefits

• Minimal cost for implementation and upgrades

• New workflow capabilities based on industry standards and best practices

• Reduced risk • Application breaks it is a Defect with the

vendor • Faster deployment with immediate value • Wider range of qualified staff

COTS Examples

• Conduit Manager – break out in phases instead of number of conductors

• Session Manager • Batch Reconcile and Post • Line directions

Conduit Manager

Line Directions

Session Manager

Batch Reconcile and Post

Non-COTS Examples

• Set Selectable Layers (not user friendly) • QA/QC rules (not enough out-of-the-box) • Snapping (subtype to subtype)

Set Selectable Layers

QA/QC Rules Validation Rule Type Description

ArcFM Gas Valve Diameter Field This field validation rule ensures that the diameter of a gas valve matches the diameter of the pipe to which it is snapped.

ArcFM Sewer Valve Diameter Field This field validation rule ensures that the diameter of a sewer valve matches the diameter of the pipe to which it is snapped.

ArcFM Water Valve Diameter Field This field validation rule ensures that the diameter of a water valve matches the diameter of the pipe to which it is snapped.

Check Required Fields Object This object validation rule ensures that required fields do not contain null values.

Duplicate Feature Object This object validation rule ensures that duplicate features are

not created when you commission design feature classes in Designer Express.

Electric Connectivity Object This object validation rule ensures that electric features are properly connected.

Feeder Info and Trace Weight Comparison Object This object validation rule compares the trace weight value to the Feeder Info field setting to verify that both fields have the same phases energized.

Gas Connectivity Object This object validation rule ensures that gas features are properly connected.

Phase of Bank Unit Field This field validation rule ensures that the phase value of a transformer unit is A, B, or C.

Phase on Transformer bank Field This field validation rule ensures that the phase value of a transformer is a subset of a connected primary conductor.

Rated kVA on Transformer Object This object validation rule ensures that the rated kVA of a transformer is equal to the total kVA of all the related transformer units.

Snapping

Conclusion

• Will never be 100% COTS • Work with the vendors • Create and maintain use cases

Questions?