WebGIS Pro Electric Utility benchmark

Arc19CapacityPlanning0201 release

ArcGIS 6.0 release included a major Enterprise Geodatabase upgrade, providing a new data model designed to improve capabilities for remote Web client access to a centralized GIS data source. Migration to a service-oriented data model has been in work for several years, beginning with the ArcGIS 10.1 release supporting Web client editing through published ArcGIS Server feature services.

ArcGIS Pro software was developed as an integral path toward replacing ArcMap to complete the migration to a complete Web Services architecture. ArcMap was designed to access the Enterprise Geodatabase through a direct connect architecture. ArcGIS Pro was designed to access Enterprise Geodatabases through a Web service connection. ArcGIS Pro capabilities include local feature caching, which reduces the amount of Web traffic required for remote connections to a centralized Enterprise Geodatabase.

The ArcGIS 10.6 Utility Network Enterprise Geodatabase data model introduced branch versioning, including the capability for remote ArcGIS Pro editors to create edit versions within the Enterprise Geodatabase through a Web feature service connection. Initial testing of the new WebGIS architecture demonstrated that up to 80 percent of the features would be cached by the remote ArcGIS Pro clients. New 20 percent dynamic workflows with client feature caching were included in the Capacity Planning Tool and used for capacity planning. This new ArcGIS Pro remote desktop deployment patterns were introduced in the SDSwiki content to demonstrate options with the new branch versioned Enterprise Geodatabase.

Several Electric Utility customers have implemented the new Utility Network data model, and this section will share some of the feedback received from testing in these new environments. The Electric Utility customers have adopted GIS technology since the 1990s for managing their electric power network infrastructure. The data models for supporting the Electric Utility networks are relatively complex compared to most Enterprise Geodatabase environments. With traditional versioning, the Electric Utility facility management system architecture design would typically use workflows that range from 2 to 3 times the complexity of a local government or typical business deployment.

ArcGIS Pro deployment patterns (Calculator)
The ArcGIS Pro deployment patterns were introduced in the GIS Product Architecture chapter.
 * ArcGIS Pro local direct connections. ArcGIS Pro supports local direct connection to an ArcGIS Enterprise Geodatabase.  This architecture supports edit operations with the traditional versioning data model introduced with the ArcGIS 8.0 release.
 * ArcGIS Pro remote desktop virtualization services. This architecture provides a virtual desktop infrastructure for hosting ArcGIS Pro application sessions in the central data center. The VDI architecture provide remote client access for display and control of applications hosted in the central data center.  This architecture supports edit operations with the traditional versioning data model introduced with the ArcGIS 8.0 release.
 * ArcGIS Pro remote Web feature services. Remote ArcGIS Pro clients access central Enterprise Geodatabase through ArcGIS Server Web feature services with an ArcGIS Enterprise Geodatabase branch versioned data source.  This architecture supports edit operations with the branch versioning data model introduced with the ArcGIS 10.6 release.



Local ArcGIS Pro direct connect to traditional Enterprise Geodatabase
The ArcGIS Enterprise Geodatabase versioning data model introduced with the ArcGIS 8.0 release required a direct connection between ArcGIS Desktop and the Geodatabase.
 * ArcGIS Desktop workflow connections with the Geodatabase required hundreds of sequential SQL requests to complete a typical map display transaction.
 * ArcGIS Desktop workstation database connect workflows required local low-latency connections for acceptable display transaction performance.

Remote ArcGIS Pro direct connect to traditional Enterprise Geodatabase
Figure UN_2 shows the traditional way to support remote ArcGIS Desktop editors, deploying desktop applications in the data center as virtual application sessions or virtual desktop infrastructure (VDI) deployments.
 * ArcGIS Pro deployments would be supported through a VDI solution.
 * ArcGIS Pro VDI deployments are expensive and limit ArcGIS Pro geoprocessing capabilities.
 * Host platforms must include NVIDIA GRID GPU cards.
 * High capacity host platforms (recommendation for 28-core server for 24 concurrent VDI sessions) to support concurrent ArcGIS batch processing jobs.
 * Performance risk in limiting number of batch jobs in a shared Host platform environment (batch jobs quickly consume available host resources, impacting performance of all users in the shared environment).

Traditional ArcGIS Pro VDI deployment (100 concurrent clients) 
 * Five 28-core host platforms; estimated cost $256,156
 * Five NVIDIA P40 GPU; estimated cost $76,460
 * No ArcGIS Enterprise licensing

ArcGIS Desktop Pro feature service with client feature caching


Figure UN_3 shows an ArcGIS Pro feature service workflow with client feature caching based on Electric Utility complexity and our initial WebGIS Pro performance assumptions.
 * ArcGIS Pro can access Web feature services and render display on workstation client.
 * ArcGIS Server supports data query with local connection to Enterprise Geodatabase.
 * Display features are delivered to remote client using efficient Web protocols.
 * ArcGIS Pro feature caching can reduce required feature traffic flow and minimize latency impacts delivering optimum remote client display performance.
 * ArcGIS 10.6 release introduced the Enterprise Geodatabase branch versioning data model, supporting ArcGIS Pro editor workflows through Web feature services (WebGIS Pro workflows).
 * WebGIS Pro workflows reduce cost, improve display performance, and reduce deployment risk (no longer require VDI architecture for ArcGIS Pro remote client workflows).

WebGIS Pro 20% Dynamic 2xMed complexity deployment (100 concurrent clients)
 * One Xeon Gold 5122 8-core host platform; estimated cost $23,648
 * ArcGIS Enterprise licensing; estimated cost $12,000/yr

"Warning: The WebGIS Pro project workflow used in this analysis assumes no ArcGIS Server geoprocessing (simple map displays) and optimum service workflow loads distributed between the ArcGIS Pro workstation, GIS Server, and the Enterprise Geodatabase." 

Electric Utility Network workflow loads analysis
The initial WebGIS Pro workflows used in the CPT were based on mobile service editing and ArcGIS Pro feature caching benchmarks. Web feature service loads were used for the Web, GIS Server, and database service times and desktop rendering loads were used for the ArcGIS Pro workstation client service times. The display complexity would vary depending on the complexity of the Enterprise Geodatabase data model.

Electric power companies have used GIS to manage their utility networks since the 1990s, and over the years their workflows and data models have evolved to support a variety of capabilities to support their facility management operations. With traditional versioned workflows, the utility CPT workflow service times would typically be 2 to 3 times more complex than typical local government workflows, due the the complexity of the utility data model and geoprocessing functions used during the utility network workflows.

Recently we received some preliminary results from an Electric Utility network benchmark, and Figure UN_4 shows the components evaluated during the benchmark evaluation. The following operations were included in the benchmark analysis. 
 * New Version Window
 * Create New Version
 * Navigational Bookmark
 * Pan & Zoom
 * Select By Attribute
 * Trace
 * Pan & Zoom (cache)
 * Edit 1: Create PriResidentialUG / Transformer / Meter
 * Pan & Zoom
 * Pan & Zoom (cache)
 * Edit 2: Create PriResidentialUG / Transformer / Meter
 * Pan & Zoom
 * Pan & Zoom (cache)
 * Edit 3: Create PriResidentialUG / Transformer / Meter
 * Validate
 * Save
 * Close Pro

Electric Utility Network Editor composite workflow analysis
The CPT Workflow tab includes a Composite Workflow Analysis that computes a composite workflow from a group of selected workflow operations, based on the percentage of time each operation transaction is included in the workflow display.
 * The UN benchmark measured the service loads for each workflow operation.
 * Benchmark analysis identified the sequence and number of transactions for each operation included in a typical UN workflow.
 * The percentage of transactions for each operation (number of transactions per operations/total transaction) along with the operation transaction service loads were used to complete the CPT Composite Workflow Analysis.

Figure UN_5 shows the Composite Workflow Analysis for the Electric Utility Network Editor workflow. 
 * All Electric Utility workflow operations were included in the Editor workflow analysis.
 * Average Electric Utility Editor (ElecUNEdit) composite workflow loads were generated by the CPT Composite Workflow Analysis.

Electric Utility Network viewer composite workflow analysis


A similar composite workflow loads analysis was completed for Electric Utililty Network viewer workflows

Figure UN_6 shows the Composite Workflow Analysis for the Electric Utility Network view workflow. The viewer workflow excluded all operations that were unique to the editor workflow. The following operations were excluded.
 * New version window
 * Create new version
 * Edit 1: Create PriResidentialUG / Transformer / Meter
 * Edit 2: Create PriResidentialUG / Transformer / Meter
 * Edit 3: Create PriResidentialUG / Transformer / Meter
 * Validate
 * Save

Average Electric Utility Viewer (ElecUNEdit) composite workflow loads were generated by the CPT Composite Workflow Analysis. 

Electric Utility Network composite workflows
Figure UN_7 shows the Electric Utility Network composite workflows included in the CPT Workflow tab.

The following composite workflows will be used for our capacity planning analysis.
 * ElecUNEdit_AGD wkstn$ FSvc Pro 2D VP UNEdit 19x10 Feature
 * ElecUNview_AGD wkstn$ FSvc Pro 2D VP UNView 19x10 Feature

"Warning: The Electric Utility Network workflows identified in this analysis are much heavier than the preliminary WebGIS Pro branch versioning workflows we have used in our initial System Design Strategies and System Architecture Design Strategies analysis. We believe these Electric Utility Network benchmark results represent a very conservative loads analysis. Based on our consulting experience and existing customer deloyments, we would expect actual customer ArcGIS 10.6 WebGIS branch versioning workflow loads to fall between the two extremes shown in this appendix."

The project workflow complexity is a function of the business process operations and the complexity of the data source.

"Best practice: Project workflow performance targets validated by benchmark testing with planned business operations using the supporting operational Enterprise Geodatabase data source will provide the most accurate capacity planning analysis." 

Electric Utility Network editor workflow solution


Figure UN_8 shows the CPT Calculator capacity planning analysis for 100 concurrent editors based on the Electric Utility Network editor workflow performance targets (ElecUNEdit).

ElecUNEdit_AGD wkstn$ FSvc Pro 2D VP UNEdit 19x10 Feature deployment (100 concurrent clients)
 * Two Xeon Gold 6132 28-core host platform; estimated cost $78,441
 * ArcGIS Enterprise licensing; estimated cost $96,000/yr

"Best Practice: Business cost is less than the traditional VDI deployment. " 

Electric Utility Network viewer workflow solution


Figure UN_9 shows the CPT Calculator capacity planning analysis for 100 concurrent editors based on the Electric Utility Network viewer workflow performance targets (ElecUNView).

ElecUNEdit_AGD wkstn$ FSvc Pro 2D VP UNEdit 19x10 Feature deployment (100 concurrent clients)
 * Two Xeon Gold 6144 16-core host platform; estimated cost $62,501
 * ArcGIS Enterprise licensing; estimated cost $60,000/yr

"Best Practice: Business cost is less than the traditional VDI deployment. " 

ArcGIS Pro deployment business needs
Figure UN_10 shows ArcGIS Enterprise GIS business requirements with ArcGIS Pro editors and viewers.

This is the same business needs analysis completed in the GIS Product Architecture Enterprise data center deployment strategies section.

In this section we will review the solution using the more conservative performance estimates based on the Electric Utility branch versioning benchmark. 

Electric Utility Network Project workflows
The ArcGIS Enterprise IOC project workflows used in the GIS Project Architecture chapter used a heavy complexity workflow for desktop editors and a medium complexity workflow for Desktop Viewers.
 * CitrixProEdit_AGD Citrix Pro 2D R Hvy 100%Dyn 19x10 ICA
 * CitrixProView_AGD Citrix Pro 2D R Med 100%Dyn 19x10 ICA

The Electric Utility workflows are based on 2x medium complexity. Figure UN_11 shows two additional Utility Network workflows converted from the Electric Utility benchmark results.
 * UNEdit workflow loads = 75 percent of the ElecUNEdit workflow loads (heavy = 75 percent of 2x medium)
 * UNview performance target loads = 50% of the ElectUNview workflow loads. (medium = 50 percent of 2x medium)

The UNEdit and UNview workflows will be used for the Utility Network Enterprise IOC design analysis. 

Pro VDI ArcGIS Enterprise design requirements and network suitability


Figure UN_12 shows CPT Design tab requirements section configured to support ArcGIS Enterprise business requirements with ArcGIS Pro VDI workflows.

This matches the Pro VDI ArcGIS Enterprise design requirements and network suitability discussion in the GIS Product Architecture chapter. 

ArcGIS Pro VDI host platform configuration


Figure UN_13 shows CPT Design tab functions and process for configuring the ArcGIS Pro VDI host platform. This matches the ArcGIS Pro VDI host platform configuration shared in the GIS Product Architecture chapter. 

Pro VDI with ArcGIS Enterprise virtual datacenter solution (Workflow Separation)
Figure UN_14 shows CPT Design tab general ArcGIS Enterprise virtual server platform solution with ArcGIS Pro workflows applying workflow separation best practices. The VDI host supports up to 85 ArcGIS Pro background geoprocessing jobs with 87 peak concurrent ArcGIS Pro client sessions.

Traditional ArcGIS Pro VDI deployment 
 * Five Xeon Gold 6132 28-core Citrix host platforms; estimated cost $204,478
 * Five NVIDIA P40 GPU; estimated cost $76,460
 * Two Xeon Gold 6128 12-core Server host platforms; estimated cost $54,048
 * Data Center virtualization software; estimated cost $69,930
 * ArcGIS Enterprise licensing; estimated cost $60,000/yr

Remote Pro Web GIS ArcGIS Enterprise design requirements and network suitability


Figure UN_15 shows CPT Design tab requirements section configured to support ArcGIS Enterprise business requirements with ArcGIS Pro Web GIS (Portal feature service) workflows.

This matches the Pro workstation ArcGIS Enterprise design requirements and network suitability discussion in the GIS Product Architecture chapter. 

Generic remote Pro Web GIS ArcGIS Enterprise virtual datacenter solution (Workflow Separation)
Figure UN_16 shows CPT Design tab generic ArcGIS Enterprise virtual server platform solution with remote Pro workstation Web GIS Portal feature service connections.

Remote Pro Web GIS ArcGIS Enterprise virtual datacenter solution
 * Two Xeon Gold 6128 12-core Server host platforms and virtualization; estimated cost $74,028.
 * ArcGIS Enterprise licensing $60,000/yr

"Best Practice: Business cost is less than the traditional VDI deployment. " 

Remote Pro Electric Utility Network Enterprise design requirements and network suitability
Figure UN_17 shows CPT Design tab requirements section configured to support ArcGIS Enterprise business requirements with ArcGIS Pro Web GIS (Portal feature service) workflows.

Utility Network workflows replace the DeskPro workflows.
 * UNEdit_AGD wkstn$ FSvc Pro 2D VP Hvy 19x10 Feature
 * UNview_AGD wkstn$ FSvc Pro 2D VP Med 19x10 Feature

Network traffic is roughly the same as the initial DeskPro$FSvc20% workflows.

<br style="clear: both" />

Pro Electric Utility Network ArcGIS Enterprise virtual datacenter solution (Workflow Separation)
Figure UN_18 shows CPT Design tab generic ArcGIS Enterprise virtual server platform solution with Utility Network Pro workstation WebGIS Portal feature service connections.

The virtual server CPT Design was expanded to four tiers to separate the production GIS Server (system of record) from the GIS2 server tier (system of engagement). The ArcGIS Pro editors and viewers required additional ArcGIS Server resources, and separating the two tiers ensures the appropriate capacity for the GIS Production servers is included in the design.

Utility Network Pro WebGIS ArcGIS Enterprise virtual datacenter solution
 * Three Xeon Gold 5115 20-core Server host platforms and virtualization; estimated cost $105,542.
 * ArcGIS Enterprise licensing; estimated cost $96,000/yr.

"Best Practice: Business cost is less than the traditional VDI deployment. " <br style="clear: both" />