City of Rome

Spring 2019 City of Rome 44th Edition

This chapter shares a process you can use to complete your own system design. This process brings together what has been discussed in the earlier chapters and demonstrates the value of the system architecture analysis in making informed design decisions.

System design provides a methodology for establishing hardware and network requirements that support the performance and communication needs of GIS application users. Hardware requirements should be established based on identified business needs. A fundamental understanding of user workflow requirements (business architecture) and the supporting GIS technology is required before one can identify the appropriate hardware and network requirements for supporting effective enterprise GIS operations. City of Rome is the name of the case study provided to demonstrate the planning process presented in a book by Roger Tomlinson called Thinking about GIS'': Geographic Information System Planning for Managers. Both his book’s chapter 9 and this chapter show standard templates that can be used for most enterprise design studies. The City of Rome case study is updated each year to represent current technology trends and ArcGIS migration strategies. In this chapter, we will use the Capacity Planning Tool as a framework to model user requirements and the system design for two planned phases of expansion and growth for the City of Rome.

Figure 11.1 shows a collection of photos representing City of Rome. The fictional City of Rome represents a typical organization, just right as a case study to demonstrate how you can use the capacity planning tool in your system design process. 

City of Rome case study
Phase 1 of the case study will implement an ArcGIS Enterprise solution to enhance the existing business operations.

"Best practice: No additional software licensing is required to upgrade existing ArcGIS operations to include ArcGIS Pro and ArcGIS Enterprise IOC capabilities."

The following phases will implement an ArcGIS Water Utility solution for City of Rome.

"Best practice: CPT will be used to complete the system design analysis." 

Pre-design efforts
Figure 11.2 shows the efforts completed in preparation for the system design. Business needs must be understood before you are ready to complete the system design.


 * Enterprise vision. GIS software deployment patterns are optimized to support your business needs:
 * Existing Business Architecture. Business architecture defines the current state of how you are meeting your business requirements.
 * Workflow loads analysis. User workflow loads analysis reviews the business processes to identify where and what is required to support business needs.

City of Rome deployment plan

 * Phase 1: ArcGIS Enterprise IOC deployment
 * Phase 2: Water Utilities COTS deployment
 * Phase 3: Web GIS Utility Network with Branch Versioning

System Design Process
Capacity Planning Tool (CPT) is used to support the system design analysis.

CPT workflow loads analysis
Figure 11.3 shows how to use the CPT in completing a project workflow loads analysis. Business needs (user requirements) establish a foundation for building a proper system design. Business requirements are represented by user workflows.
 * Calculator tab. The first step in completing a system architecture design is to select the appropriate software deployment patterns (project workflows) and identify the peak user workflow profiles loads.

 Once your software technology (project workflow) selection is complete, your selected workflow performance targets will be available at the top of the CPT workflow selection list for use in your system architecture design.
 * Workflow tab. The Project Workflows section on the CPT Workflow tab is located at the top of the workflow list. Project Workflows are selected from the Standard Workflows included on the CPT Workflow tab or custom workflows generated from the CPT Calculator or Test tabs - identifying your project workflows is the process referred to as your user workflow loads analysis.

CPT system architecture design analysis
Once you have identified your project workflows, you are ready to complete your system design. The CPT is developed for use based on a standard system architecture design process as shown in Figure 11.4. Each cycle of the system architecture design process includes the following steps:


 * Technical architecture strategy—High-level overview showing user site locations, network bandwidth connections, and central data center locations. User location information is collected during the user needs analysis.
 * User requirements analysis—CPT Requirements analysis section is configured to represent the site locations, user workflows, peak loads, and network bandwidth for the enterprise design solution.
 * Network suitability analysis—CPT Design completes the network suitability analysis and identifies any communication bottlenecks. Network bandwidth upgrades are identified to complete the network suitability analysis.
 * Platform architecture selection—CPT Design Platform tier is configured to represent the design solution. Identify platform tier nicknames, select platforms, and identify platform rollover settings.
 * Software configuration—CPT Design Software Configuration module is used to assign workflow software to supporting platform tier (software install) and make workflow data source selection.
 * Enterprise design solution—Once configured, the CPT Design tab completes the system architecture design analysis and provides the platform solution.

Phase 1: ArcGIS Enterprise IOC deployment
The System Architecture Design phase 1 analysis will review the following available deployment options. Figure 11.5 shows a summary of the cost impacts for each deployment.
 * Model existing City of Rome operations
 * ArcGIS Enterprise IOC architecture
 * ArcGIS Enterprise (Portal for ArcGIS and ArcGIS Data Store)
 * ArcGIS Pro workstation viewers


 * Vector tile base map architecture
 * 60% cached vector tile basemaps
 * 40%Dyn ArcGIS Pro and Web workflows


 * WebGIS Pro with feature caching
 * ArcGIS Pro workstation viewers with client feature caching


 * Citrix and Server host hardware platform upgrades
 * Enable traditional support for remote ArcMap and ArcGIS Pro desktops (editors and viewers)


 * Citrix editors with WebGIS Pro workstation viewers
 * Solution for traditional ArcMap and Pro editors and WebGIS Pro viewers

"Best practice: Deploying WebGIS Pro viewers with client feature caching will minimize operational cost." 

Phase 2 Water Utility solution (traditional versioning)
The ArcGIS Water Solutions include over 46 maps and apps that can be downloaded and used by customers to jumpstart their GIS operations. Figure 11.6 shows a preliminary cost estimate for the Phase 2 and 3 deployment options.

Initial deployment will include COTS solution using traditional ArcGIS Desktop ArcMap/Pro virtual desktop clients with traditional ArcGIS Desktop Geodatabase versioning.
 * ArcGIS Desktop clients will be deployed on virtual desktop host.
 * Traditional Geodatabase versioning will support ArcGIS Desktop edit operations.
 * City of Rome procurement costs will support pricing analysis.

Phase 3 Water Utility solution (Branch versioning)
Final deployment will include ArcGIS Solutions for Water Utilities with the ArcGIS 10.6 Utility Network with Branch Versioning and WebGIS Pro clients. 
 * Deploy ArcGIS Pro WebGIS workstation with client feature caching (Editors and Viewers).
 * Remote WebGIS Pro client access to Branch versioning geodatabase through ArcGIS Enterprise feature services.
 * City of Rome procurement costs will support pricing analysis.

City of Rome existing operations
For this case study, the existing City of Rome GIS Operations will first be modeled to establish a design baseline. Then the "existing operations" design will be expanded to include a Phase 1 ArcGIS Enterprise initial operational capability (IOC). This will be followed by review and deployment of a Phase 2 Water Utilities solution for City of Rome.

Workflow loads analysis: Existing operations
Figure 11.7 shows the City of Rome existing workflow loads analysis, providing a summary of user locations and peak user workflow loads.

The workflow loads analysis includes all the GIS workflow patterns identified during the business needs analysis.
 * A simple spreadsheet layout can show user locations by department and site location.
 * Common workflow technology patterns can be combined across site locations to simplify the display and design analysis.
 * The peak usage estimates represent a snapshot of a peak load profile that will be used for the system design.
 * Workflows represent the technology profiles that will be used during peak operations.
 * Peak loads will be used to identify hardware and network system design specifications.

"Best practice: CPT will be used to complete the system design analysis." 

User workflow display complexity: Existing operations
Figure 11.8 shows the workflow patterns identified for the City of Rome existing operations. User workflow patterns are normally a product of a user needs assessment and provide a reference for establishing workflow loads for the system design.

The software technology workflow patterns are identified during the workflow loads analysis. Follow these recommendations when performing a user workflow loads analysis:
 * Review each user business case to identify appropriate workflow categories.
 * Identify the required user workflows and solution architecture for each technology pattern.
 * Estimate the average complexity of each user workflow.

User workflow complexity is an estimate of the processing loads required for an average information product display transaction. The workflow complexity estimate will be used with the CPT to generate appropriate system design performance specifications.

"Best practice: A conservative workflow complexity will ensure an adequate system design solution" 

Workflow performance targets: Existing operations
Figure 11.9 shows the workflow performance targets selected for the City of Rome existing operations. The CPT can be used to generate appropriate workflow performance targets for the system design.

Workflow performance targets are generated by the CPT Calculator by selecting the appropriate software technology performance factors. The software technology profile and complexity identified during the user needs workflow loads analysis provide information needed to select the appropriate software technology performance factors for each use workflow.

The workflow definition provides a recipe that identifies the software technology performance factors used to generate each user workflow performance target.

"Best practice: The user needs workflow loads analysis summary and the user workflow performance targets are used by the CPT to generate traffic and processing loads on the CPT system design solution."

CPT project workflows: Existing operations


System design process: Existing operations
Figure 11.10 shows the process used to complete the system design. The initial effort for the City of Rome design is to establish a baseline planning environment. The standard system design process introduced in Chapter 1 will be used to model the existing City of Rome environment.

System design process: 
 * Technical architecture strategy. High-level network drawing showing user site locations, network bandwidth connections, and central data center locations. Drawing should match the user location information provided on the user requirements templates.
 * User requirements analysis: The CPT Requirements analysis section is configured to represent the site locations, user workflows, peak loads, and network bandwidth for the enterprise design solution.
 * Network suitability analysis: CPT Design completes the network suitability analysis and identifies any communication bottlenecks. Network bandwidth upgrades are identified to complete the network suitability analysis.
 * Platform architecture selection: The CPT Design Platform tier is configured to represent the design solution. Identify platform tier nicknames, select platforms, and identify platform rollover settings.
 * Software configuration: The CPT Design Software Configuration module is used to assign workflow software to supporting platform tier (software install) and make workflow data source selection.
 * Enterprise design solution: Once configured, the CPT Design tab completes the system design analysis and provides the platform solution.

Technical architecture: Existing operations
Figure 11.11 shows the City of Rome technical architecture providing a summary of the current user locations and network connectivity.

The GIS server machines are supported in the central IT data center in City Hall.
 * Windows Terminal Server host for remote ArcGIS Desktop users.
 * Web server machines for internal and public web services.
 * ArcGIS Server machines for mapping services.
 * Data server machines for GIS data sources.

City Hall data center remote network connections are as follows:
 * Data center—1000 Mbps LAN connection
 * Data center—90 Mbps WAN connection
 * Site 2 Operations facility—12 Mbps WAN connection
 * Site 3 Freeberg—45 Mbps WAN connection
 * Site 4 Willsberg—45 Mbps WAN connection


 * Data center—45 Mbps Internet connection
 * Public web services will connect through the data center Internet connection.

Current network cost (WAN/Internet Service) is provided for reference purposes ($7,836/month).

"Warning: The estimated network pricing used in the CPT is for demonstration purposes only." 

Network pricing model
Figure 11.12 shows the network service provider cost model used for demonstration purposes in this case study.

Network service provider costs should be considered when evaluating Enterprise level GIS design solutions.
 * Network bandwidth has an impact on remote user productivity with every GIS design.
 * Technology change (i.e., higher resolution clients) increase GIS workflow traffic requirements.
 * Dynamic feature services generate more traffic than standard mapping services.

"Warning: Network service rates can be a significant performance/cost consideration for an optimum design."

"Best practice: Network bandwidth upgrade recommendations must be coordinated with the network administrator and included in the network infrastructure upgrade budget." 

Platform architecture selection: Existing operations
Figure 11.13 shows City of Rome existing platform architecture components. Each server machine will be supported by a high-availability virtual server platform architecture.

The existing platform architecture includes the following virtual machines.
 * WTS tier: ArcGIS Desktop (ArcMap) remote clients supported by XenApp sessions on the Citrix host platform tier.
 * Web tier: A total of four (4) web servers (two internal and two public) support the high-availability Web tier architecture.
 * GIS tier: A total of four (4) ArcGIS Servers (separate internal and public GIS Server sites, each with two machines to support high-availability requirements).
 * DBMS tier: A total of four (4) DBMS servers (primary production and publication server machines each with a dedicated failover server to satisfy high-availability requirements).

"Best practice: A virtual server data center environment provides optimum flexibility for deploying and supporting GIS operations." 

Workflow performance summary: Existing operations
Figure 11.14 shows the CPT Design workflow performance summary for the existing GIS operations.

Establishing a baseline model of existing operations validates user needs estimates and provides quality assurance for supporting system design for future deployments.

Workflow performance summary provides the following:
 * Average processing and queue times for each user workflow.
 * Average difference in performance between each site location.
 * Average performance for shared public services.

Important to note that model shows average performance levels.
 * Some display response times can be lighter.
 * Other display response times will be slower.
 * Queue times will vary depending on random load profiles.

"Best practice: Workflow performance summary can be used to identify expected relative performance between remote locations and establish user experience expectations for the configured design solution." 

Enterprise design solution: Existing operations
Figure 11.15 shows the final platform design solution. After you finish configuring the CPT Design tab, Excel completes the system design analysis and provides a diagram of the platform solution.

CPT Design platform solution: Existing operations
This graphic shows the 4-tier virtual server platform architecture configuration along with the CPT generated host platform tier loads for the existing City of Rome GIS operations. The CPT Design analysis has loaded the selected platform solution with the peak user loads identified in the design.

The following host platform tier support the data center processing loads.
 * Citrix host platform: Three platform nodes at 34.0% utilization.
 * Server host platform: Three platform nodes at 31.6% utilization.

The physical host server environment is supported by six (6) existing 2011 Xeon X5687 8-core platforms. 

Phase 1 ArcGIS Enterprise IOC
The City of Rome initial software migration will deploy ArcGIS Enterprise components to establish an ArcGIS Enterprise Initial Operational Capability (IOC). This deployment will expand existing operations to include a system of engagement for existing users. The ArcGIS Enterprise IOC deployment will leverage existing hardware and ArcGIS user licensing. The ArcGIS Enterprise deployment will enable existing users to create content (web maps), collaborate and share ideas, and use configurable apps to empower more adaptive Web GIS operations.

Workflow loads analysis: ArcGIS Enterprise IOC
Figure 11.16 shows a projected user needs summary following the ArcGIS Enterprise deployment. Existing local web service transaction rates were increased by 10 percent to accommodate projected system of engagement Portal for ArcGIS feature services.

The ArcGIS Enterprise deployment will significantly expand existing capabilities.
 * Deploy Portal for ArcGIS for improved security and establish an enterprise system of engagement.
 * Enable business users to create web maps and build configurable web apps from existing business resources.
 * Leverage existing software licensing to significantly expand operational capabilities.

Expanded GIS operations
 * ArcGIS Pro can be used by GIS Desktop clients to create and share Portal content.
 * Named users within the Portal organization can create content and publish new web maps.
 * User needs include new Portal feature services shared internally from Portal content.

"Best practice: ArcGIS Enterprise deployment rapidly expands system capabilities with minimum deployment risk." 

Workflow performance targets: ArcGIS Enterprise IOC
Figure 11.17 shows the workflow performance targets defined for the ArcGIS Enterprise IOC deployment. The CPT can be used to generate appropriate workflow performance targets for the system design.

The ArcGIS Enterprise deployment includes new Portal workflows.
 * DeskProMed. ArcGIS Pro desktop use case (medium complexity) that will be used by GIS viewers to expand display and analysis capabilities for existing user workflows. ArcGIS Pro will enable GIS users to create new Portal content and share feature services from existing business resources.
 * PortalFsvc. Portal named users can create new web maps and apps and share new feature services. Performance target for these new feature services is heavy complexity with 20% dynamic layers (sharing limited number of new business layers over vector tile basemaps).

CPT project workflows: ArcGIS Enterprise IOC
The workflow definition provides a recipe that identifies the software technology performance factors used to generate each user workflow performance target.

"Best practice: User workflow performance targets are used by the CPT to generate traffic and processing loads on the CPT system design solution." <br style="clear: both" />

System design process: ArcGIS Enterprise IOC
Figure 11.18 shows the process used to complete the system design. The system design process will be used to evaluate the ArcGIS Enterprise IOC deployment.

System design process: <br style="clear: both" />
 * Technical architecture strategy. ArcGIS Enterprise IOC technical architecture will be the same user locations and network connectivity as the existing City of Rome infrastructure. Network traffic upgrades will impact technical architecture, and a summary of these impacts will be shared following the software configuration.
 * User requirements analysis.
 * Network suitability analysis.
 * Platform architecture selection.
 * Software configuration.
 * Enterprise design solution.

Platform architecture selection: ArcGIS Enterprise IOC
Figure 11.19 shows City of Rome ArcGIS Enterprise platform architecture components. Each server machine will be supported by a high-availability virtual server platform architecture.

The platform architecture for the ArcGIS Enterprise IOC includes the following virtual machines.
 * RDSH tier: ArcGIS Desktop ArcMap remote clients supported by XenApp sessions on Citrix virtual machines.
 * Web tier: A total of six (6) web servers (internal and public web servers and a new Portal server, each with two machines) support the high-availability Web tier architecture.
 * GIS tier: A total of six (6) ArcGIS Servers (separate internal and public GIS Server sites and a new internal hosting server site, each site with two machines to support high-availability requirements).
 * DBMS tier: A total of six (6) DBMS servers (primary production and publication server machines, and a new relational data store machine, each with dedicated failover machines to satisfy high availability requirements).

"Best practice: A virtual server data center environment provides optimum flexibility for deploying and supporting GIS operations."

Workflow performance summary: ArcGIS Enterprise IOC
Figure 11.20 shows the CPT Design workflow performance summary for the ArcGIS IOC operations. Graphics show before and after implementing the recommended bandwidth upgrades.

"Warning: ArcGIS Pro is not supported in a Citrix XenApp session terminal services environment."

ArcGIS Enterprise deployment with the existing network bandwidth will result in poor performance at the remote locations.
 * Remote ArcGIS Desktop viewers will need to use a local workstation install of ArcGIS Pro.
 * ArcGIS Pro feature services generate more traffic over the remote bandwidth connections.
 * ArcGIS Pro operations over higher latency connections increase response time delays.

"Best practice: The CPT Design network suitability analysis can be used to identify appropriate network upgrade requirements." <br style="clear: both" />

Enterprise design solution: ArcGIS Enterprise IOC
Figure 11.21 shows the ArcGIS Enterprise enterprise design solution. ArcGIS Enterprise IOC deployment replaces remote ArcGIS Desktop ArcMap viewers with an ArcGIS Pro workstation deployment.

CPT Design platform solution: ArcGIS Enterprise IOC
The following host platform tier support the data center processing loads. workstation access over WAN from remote locations.
 * Citrix host platform: Not supported for ArcGIS Pro clients.
 * Network bandwidth upgraded to support ArcGIS Pro
 * Server host platform: Three platform nodes at 34.3% utilization.

Server host platform load increased slightly (31.6% to 34.3%) to accommodate additional Portal for ArcGIS, ArcGIS Server host server, and relational data store processing loads. These additional loads also include accommodation for the additional hosted feature services included in the user needs projection.

The physical host server environment is supported by three (3) existing 2011 Xeon X5687 8-core platforms.

"Best practice: ArcGIS Enterprise IOC deployment has minimum impact on the existing host server processing loads." <br style="clear: both" />

Technical architecture: ArcGIS Enterprise IOC network upgrades
Figure 11.22 shows a summary of the City of Rome ArcGIS Enterprise IOC recommended network upgrades. Network bandwidth upgrades are required to support ArcGIS Enterprise IOC remote user workflow performance requirements.

Recommended network bandwidth upgrades
 * Data center—1000 Mbps LAN connection (no change)
 * Data center—upgrade 90 Mbps to 310 Mbps WAN connection
 * Site 2 Operations facility—upgrade 12 Mbps to 24 Mbps WAN connection
 * Site 3 Freeberg—upgrade 45 Mbps to 155 Mbps WAN connection
 * Site 4 Willsberg—upgrade 45 Mbps to 135 Mbps WAN connection


 * Data center—45 Mbps Internet connection (no change)
 * Public web services will connect through the data center Internet connection.

Projected network cost (WAN/Internet Service) increases from $7,836/ month to $12,289/month.

"Warning: The estimated network pricing used in the CPT is for demonstration purposes only." <br style="clear: both" />

Phase 1 Vector tile basemap deployment
The ArcGIS Enterprise deployment will enable ArcGIS Desktop users to leverage ArcGIS Pro capabilities to improve operational effectiveness. City of Rome plans to allow ArcGIS Desktop viewers to leverage ArcGIS Pro and their legacy ArcMap applications. ArcGIS Pro is not supported with the existing ArcGIS Desktop terminal services environment. Existing remote ArcGIS Desktop users must install ArcGIS Pro on their local workstations and access data sources over the existing WAN environment. Vector tile basemaps can be used by ArcGIS Pro and local Web applications to reduce bandwidth costs and improve display performance for remote users over the WAN.

Vector tile basemaps
Figure 11.23 shows a summary of the costs and benefits of using vector tile basemaps.

Vector tiles are created and delivered with much less processing.
 * Faster tile generation. World vector tiles generated in 8 hours versus world raster tiles generated in many weeks.
 * Reduced tile size: World vector tiles ~13 GB; world raster tiles ~20 TB.

For City of Rome, vector tile basemaps for the operational area could be generated in less than 1 hour with tile size less than 1 GB. Basemaps could be updated on a weekly basis to provide optimum operations support.

Vector tiles are published and consumed by ArcGIS client software.
 * Tile creation: ArcGIS Pro 1.2+ (geoprocessing services).
 * Published tile layers: ArcGIS Online; ArcGIS Server/Portal for ArcGIS 10.4+.
 * Client consumption: ArcGIS Runtime Quartz; ArcGIS Pro 1.3+, ArcGIS JavaScript 3.15+, and 4.0 APIs.

"Best practice: Vector tiles provide a single layer of files that can be dynamically displayed and styled." <br style="clear: both" />

For City of Rome, all existing Web apps and ArcGIS Pro clients would be able to leverage vector tile basemaps, significantly reducing network traffic impacts, improve client display performance, and significantly improve capacity of existing servers. <br style="clear: both" />

Workflow loads analysis: ArcGIS Enterprise IOC with vector tile basemaps
ArcGIS Enterprise IOC workflow loads analysis will remain the same with vector tile basemaps.

Workflow performance targets: ArcGIS Enterprise IOC with vector tile basemaps
Figure 11.24 shows the workflow performance targets defined for the ArcGIS Enterprise IOC deployment with vector basemaps. The CPT can be used to generate appropriate workflow performance targets for the system design.

ArcGIS Pro and the web services can leverage vector tile basemaps. Vector tile basemaps reduce display complexity by 60 percent.

"Warning: ArcMap is not able to use vector tile basemaps."

New Portal workflows for ArcGIS Enterprise IOC with vector tile basemaps.
 * DeskProMed40%. DeskProMed workflow with cached vector tile basemap.
 * WebInHvy40%. WebInHvy workflow with cached vector tile basemap.
 * WebPubMed40%. WebPubMed workflow with cached vector tile basemap.

The workflow definition provides a recipe that identifies the software technology performance factors used to generate each user workflow performance target.

"Best practice: Workflow performance targets are used by the CPT to generate traffic and processing loads on the CPT system design solution."

System design process: ArcGIS Enterprise IOC with vector tile basemaps
Figure 11.25 shows the process used to complete the system design. The system design process will be used to evaluate the ArcGIS Enterprise IOC deployment.

System design process: <br style="clear: both" />
 * Technical architecture strategy. ArcGIS Enterprise IOC with vector tile basemaps technical architecture will be the same user locations and network connectivity as the existing City of Rome infrastructure. Network traffic adjustments will impact technical architecture and infrastructure costs, and a summary of these impacts will be shared following the software configuration.
 * User requirements analysis.
 * Network suitability analysis.
 * Platform architecture selection.
 * Software configuration.
 * Enterprise design solution.

CPT Design requirements analysis: Vector tile basemap deployment
====CPT Design network suitability analysis: Vector tile basemap deployment====

Platform architecture selection: ArcGIS Enterprise IOC with vector tile basemaps
Figure 11.26 shows City of Rome ArcGIS Enterprise IOC platform architecture components with vector tile basemaps. Each server machine will be supported by a high-availability virtual server platform architecture.

The ArcGIS Enterprise IOC virtual platform configuration does not change. Vector tile basemaps will be deployed on a data center file share. Tiles will be downloaded to the client browser cache and displayed with the local application as required to support the display.

Negligible Web and GIS Server loads are required to support the client display tile cache downloads.

"Best practice: A virtual server data center environment provides optimum flexibility for deploying and supporting GIS operations." <br style="clear: both" />

Workflow performance summary: ArcGIS Enterprise IOC with vector tile basemaps
Figure 11.27 shows the CPT Design workflow performance summary for the ArcGIS IOC operations with vector tile basemaps. Graphics show network cost savings and client display performance improvements with the vector basemap deployment.

"Best practice: Vector tile basemaps significantly reduce network traffic and improve display performance."

ArcGIS Enterprise deployment with vector basemaps reduces network traffic and improves display performance.
 * Vector basemaps are downloaded once to the client browser cache.
 * Dynamic processing loads are reduced due to the basemap cached layers.
 * Latency impacts are reduced due to less dynamic layers (less chatter) in the display.

"Best practice: The CPT Design network suitability analysis can be used to identify appropriate network upgrade requirements." <br style="clear: both" />

Technical architecture: ArcGIS Enterprise IOC with vector tile basemaps
Figure 11.28 shows a summary of the benefits of deploying ArcGIS Pro and web services utilizing vector tile basemaps. Network traffic requirements are reduced for the ArcGIS Enterprise IOC deployment when leveraging vector tile basemaps.

Recommended network bandwidth savings
 * Data center—1000 Mbps LAN connection (no change)
 * Data center—reduce 310 Mbps to 135 Mbps WAN connection
 * Site 2 Operations facility—reduce 24 Mbps to 12 Mbps WAN connection
 * Site 3 Freeberg—reduce 155 Mbps to 90 Mbps WAN connection
 * Site 4 Willsberg—reduce 155 Mbps to 90 Mbps WAN connection


 * Data center—reduce 45 Mbps to 24 Mbps Internet connection
 * Public web services will connect through the data center Internet connection.

Projected network cost (WAN/Internet Service) decreases from $12,289/month to $9,570/month.

"Warning: CPT network pricing is used for demonstration purposes only." <br style="clear: both" />

Enterprise design solution: ArcGIS Enterprise IOC with vector basemaps
Figure 11.29 shows the ArcGIS Enterprise IOC enterprise design solution with vector basemaps. ArcGIS Enterprise IOC deployment replaces remote ArcGIS Desktop ArcMap viewers with an ArcGIS Pro workstation deployment. Vector basemaps reduce host server processing loads.

CPT Design platform solution: Vector tile basemap deployment
The following host platform tier support the data center processing loads.
 * Citrix host platform: Not supported for ArcGIS Pro clients.
 * Network traffic reduced from the initial IOC design due to leveraging vector tile basemaps.
 * Server host platform: Two (2) platform nodes at 30.3% utilization.

Server host platform load is reduced significantly (3 platforms at 34.3% utilization to 2 platforms at 30.4% utilization) supporting the same ArcGIS Enterprise IOC workflows.

The physical host server environment is supported by two (2) existing 2011 Xeon X5687 8-core platforms.

"Best practice: ArcGIS Enterprise IOC deployment has minimum impact on the existing host server processing loads." <br style="clear: both" />

Phase 1 WebGIS Pro with client feature caching
The ArcGIS Enterprise deployment will enable ArcGIS Desktop users to leverage ArcGIS Pro capabilities to improve operational effectiveness. City of Rome plans to allow ArcGIS Desktop viewers to leverage ArcGIS Pro and their legacy ArcMap applications. ArcGIS Pro is not supported with the existing City of Rome ArcGIS Desktop terminal services environment (would need to upgrade with an NVIDIA Grid card). Existing remote ArcGIS Desktop users must install ArcGIS Pro on their local workstations and access data through feature services over the existing WAN environment. ArcGIS Pro will leverage feature service access with local client feature caching to reduce bandwidth costs and improve display performance for remote users over the WAN.

WebGIS Pro with client feature caching
Figure 11.30 shows a summary of the costs and benefits when using WebGIS Pro clients (ProWkstnFSvc workflows) with feature caching.

ArcGIS Pro can cache feature services on the local client.
 * Reduces requirement to refresh existing features across the network with each display.
 * ArcGIS Pro can cache up to 80 percent of the features on the local client when supporting the City of Rome viewer workflows.

"Best practice: ArcGIS Pro feature caching can significantly reduce network traffic and server feature service loads." <br style="clear: both" />

For City of Rome, ArcGIS Pro analysts (data viewers) leveraging local client feature caching will reduce network traffic impacts, improve client display performance, and improve capacity of existing servers. <br style="clear: both" />

Workflow loads analysis: ArcGIS Enterprise IOC with WebGIS Pro feature caching
Figure 11.31 shows the City of Rome workflow loads analysis with WebGIS Pro feature caching, providing a summary of user locations and peak user workflow loads.

Workflow performance targets: ArcGIS Enterprise IOC with WebGIS Pro feature caching
Figure 11.32 shows the workflow performance targets defined for the ArcGIS Enterprise IOC deployment with WebGIS Pro feature caching. The CPT can be used to generate appropriate workflow performance targets for the system design.

ArcGIS Pro accessing web feature services can leverage client feature caching. Client feature caching will reduce display complexity by 80 percent with City of Rome viewer clients.

New Portal workflows for ArcGIS Enterprise IOC with ArcGIS Pro client feature caching.
 * DeskAPro$FsvcMed20%. DeskProMed workflow with WebGIS Pro client feature caching.

The workflow definition provides a recipe that identifies the software technology performance factors used to generate each user workflow performance target.

"Best practice: Workflow performance targets are used by the CPT to generate traffic and processing loads on the CPT system design solution."

System design process: ArcGIS Enterprise IOC with WebGIS Pro feature caching
Figure 11.33 shows the process used to complete the system design. The system design process will be used to evaluate the ArcGIS Enterprise IOC deployment with WebGIS Pro feature caching.

System design process: <br style="clear: both" />
 * Technical architecture strategy. ArcGIS Enterprise IOC with WebGIS Pro feature caching technical architecture will be the same user locations and network connectivity as the existing City of Rome infrastructure. Network traffic adjustments will impact technical architecture and infrastructure costs, and a summary of these impacts will be shared following the software configuration.
 * User requirements analysis.
 * Network suitability analysis.
 * Platform architecture selection.
 * Software configuration.
 * Enterprise design solution.

CPT Design requirements analysis: WebGIS Pro feature caching
====CPT Design network suitability analysis: WebGIS Pro feature caching====

Platform architecture selection: ArcGIS Enterprise IOC with WebGIS Pro feature caching
Figure 11.34 shows City of Rome ArcGIS Enterprise IOC platform architecture components with WebGIS Pro feature caching. Each server machine will be supported by a high-availability virtual server platform architecture.

The ArcGIS Enterprise IOC virtual platform configuration does not change. Remote ArcGIS Desktop ArcMap editors will be supported by application sessions on the Windows Terminal Server host machines. Remote ArcGIS Desktop viewers will use ArcGIS Pro installed on their local workstation accessing Web features services across the WAN network.

"Best practice: A virtual server data center environment provides optimum flexibility for deploying and supporting GIS operations." <br style="clear: both" />

Workflow performance summary: ArcGIS Enterprise IOC with WebGIS Pro feature caching
Figure 11.35 shows the CPT Design workflow performance summary for the ArcGIS IOC operations with WebGIS Pro feature caching. Graphics show network cost savings and client display performance improvements with the WebGIS Pro feature caching.

"Best practice: WebGIS Pro feature caching significantly reduce network traffic and improve display performance."

ArcGIS Enterprise deployment with WebGIS Pro feature caching reduces network traffic and improves display performance.


 * Dynamic processing loads are reduced due to the WebGIS Pro client feature caching.
 * Latency impacts are reduced due to less dynamic layers (less chatter) in the display.

"Best practice: The CPT Design network suitability analysis can be used to identify appropriate network upgrade requirements." <br style="clear: both" />

Technical architecture: ArcGIS Enterprise IOC with WebGIS Pro feature caching
Figure 11.36 shows a summary of the benefits of deploying ArcGIS Pro and web services utilizing vector tile basemaps. Network traffic requirements are reduced for the ArcGIS Enterprise IOC deployment when leveraging WebGIS Pro feature caching.

Recommended network bandwidth savings
 * Data center—1000 Mbps LAN connection (no change)
 * Data center—reduce 135 Mbps to 90 Mbps WAN connection
 * Public web services will connect through the data center Internet connection.

Projected network cost (WAN/Internet Service) decreases from $10,147/month to $7,780/month.

"Warning: CPT network pricing is used for demonstration purposes only." <br style="clear: both" />

Enterprise design solution: ArcGIS Enterprise IOC with WebGIS Pro feature caching
Figure 11.37 shows the ArcGIS Enterprise IOC enterprise design solution with WebGIS Pro feature caching. ArcGIS Enterprise IOC deployment replaces remote ArcGIS Desktop ArcMap viewers with an WebGIS Pro feature caching. WebGIS Pro feature caching reduce server processing loads.

CPT Design platform solution: WebGIS Pro feature caching
The following host platform tier support the data center processing loads.
 * Citrix host platform: Not supported for ArcGIS Pro clients.
 * Network traffic reduced from the initial IOC design due to leveraging WebGIS Pro feature caching.
 * Server host platform: Three (3) platform nodes at 21.7% utilization.

Server host platform load increases slightly from (3) platforms at 19.7% utilization to 3 platforms at 21.7% utilization) supporting the same ArcGIS Enterprise IOC workflows.

The physical host server environment is supported by three (3) existing 2011 Xeon X5687 8-core platforms.

"Best practice: ArcGIS Enterprise IOC deployment has minimum impact on the existing host server processing loads." <br style="clear: both" />

Phase 1 Upgrade WTS host platform tier to support remote ArcGIS Pro clients
ArcGIS Pro can be supported in a hosted virtual desktop environment, which would improve remote ArcGIS Pro display performance and further reduce network cost. Upgrading the WTS host platform tier to support ArcGIS Pro clients would require new hardware purchases.

ArcGIS Pro Windows Terminal Server host platform requirements
Figure 11.38 shows ArcGIS Pro display performance when supported in a local workstation or host server remote desktop host environment. GRID GPU graphics must be included with the host server configuration to support ArcGIS Pro display performance.

Host platform must include Tesla P40 GPU graphics hardware and NVIDIA GRID concurrent user licensing
 * NVIDIA Tesla P40 GPU
 * NVIDIA GRID licensing for remote desktop sessions (up to 24 concurrent workstation clients)

ArcGIS Pro reference sites were provided in the GIS Product Architecture chapter.

"Warning: ArcGIS Desktop Citrix XenDesktop deployment with raster imagery included in the display requires much higher client traffic. Pro 3D remote client displays can experience significantly more client traffic than what is experienced with 2D displays." <br style="clear: both" />

Workflow loads analysis: ArcGIS Pro Citrix remote clients
Figure 11.39 shows the remote viewers that would be hosted on the new ArcGIS Pro virtual desktop server. Display performance for the remote ArcGIS Pro desktop users can be improved by upgrading the Citrix host platform tier with NVIDIA GRID graphics.

Business requirements identify up to 62 remote ArcGIS Pro clients.
 * Remote DeskMed clients currently use ArcMap applications.
 * ArcGIS Enterprise workflows will expand capabilities to use ArcGIS Pro.
 * Existing ArcMap client licenses include authorization to use ArcGIS Pro.

Workflow performance targets: ArcGIS Pro Citrix remote clients
Figure 11.40 shows Workflow performance targets defined for the ArcGIS Enterprise IOC deployment with vector basemaps and ArcGIS Pro remote desktop clients. The CPT can be used to generate appropriate workflow performance targets for the system design.

ArcGIS Pro remote desktop workflow (40% dynamic) will leverage the vector tile basemaps.

The ArcGIS Enterprise IOC with vector basemaps includes new ArcGIS Pro workflows.
 * CitrixProMed40%. Remote ArcGIS Pro clients using host Citrix remote desktop host tier and vector basemaps.
 * CitrixBatch. ArcGIS Pro workflows include a variety of geoprocessing capabilities that users can leverage within the remote desktop workflows. CitrixBatch workflow provides batch loads on the Citrix server for each geoprocessing instance.

The workflow definition provides a recipe that identifies the software technology performance factors used to generate each user workflow performance target.

"Best practice: The user needs workflow loads analysis summary and the user workflow performance targets are used by the CPT to generate traffic and processing loads on the CPT system design solution."

=
CPT project workflows: ArcGIS Pro Citrix remote clients deployment===== <br style="clear: both" />

System design process: ArcGIS Pro Citrix remote clients
Figure 11.41 shows the process used to complete the system design. The system design process will be used to evaluate the ArcGIS Enterprise IOC deployment.

System design process: <br style="clear: both" />
 * Technical architecture strategy. ArcGIS Enterprise IOC with vector tile basemaps and remote ArcGIS Pro virtual desktops technical architecture will be the same user locations and network connectivity as the existing City of Rome infrastructure. Network traffic adjustments will impact technical architecture and infrastructure costs, and a summary of these impacts will be shared following the software configuration.
 * User requirements analysis.
 * Network suitability analysis.
 * Platform architecture selection.
 * Software configuration.
 * Enterprise design solution.

====CPT Design requirements analysis: ArcGIS Pro Citrix remote clients deployment==== ====CPT Design network suitability analysis: ArcGIS Pro Citrix remote clients deployment====

Platform architecture selection: ArcGIS Enterprise IOC
Figure 11.42 shows City of Rome ArcGIS Enterprise IOC platform architecture components with vector tile basemaps and support for ArcGIS Pro remote desktop clients. Each server machine will be supported by a high-availability virtual server platform architecture.

The technical platform architecture for the ArcGIS Enterprise IOC with vector tile basemaps and ArcGIS Pro remote desktops include the following additional virtual machines.
 * WTS tier: ArcGIS Desktop ArcMap and ArcGIS Pro remote desktop clients.

"Best practice: A virtual server data center environment provides optimum flexibility for deploying and supporting GIS operations." <br style="clear: both" />

City of Rome hardware price list
Figure 11.43 shows the 2018 host hardware platform options and associated vendor pricing for City of Rome procurement. City of Rome management requests that you complete a cost analysis for the various platform architecture patterns being proposed for this study. For this analysis, City of Rome provided their hardware price list for platforms under consideration for this design.

Esri recommends a 28-core server platform with NVIDIA GRID graphics to support 25 concurrent ArcGIS Pro clients. High-capacity server is required to support the batch geoprocessing jobs performed by clients during typical ArcGIS Pro workflows. Geoprocessing needs will determine server capacity requirements.

"Warning: Customer price lists can vary based on vendor arrangements and contract agreements. It is important to validate pricing and update platform pricing on the CPT Hardware Pricing tab if you want to include pricing in your analysis."

====CPT Design platform configuration: ArcGIS Pro Citrix remote clients deployment==== ====CPT Design software configuration: ArcGIS Pro Citrix remote clients deployment====

Workflow performance summary: ArcGIS Pro Citrix remote clients
Figure 11.44 shows display performance summary for the ArcGIS Enterprise IOC with ArcGIS Pro remote desktop workflows.

"Best practice: ArcGIS Pro remote desktop performance is a significant improvement over remote ArcGIS Pro workstation clients accessing the database over the WAN network."

ArcGIS Enterprise deployment with ArcGIS Pro remote desktop clients improves display performance.
 * ArcGIS Pro application is supported in the data center with local data sources.
 * ArcGIS Pro clients have display and control of the application from their remote site location.
 * Network traffic is reduced because only the final display is sent to the client.
 * Latency impacts are reduced due to less chatter with the remote desktop display.

"Best practice: The CPT Design network suitability analysis can be used to identify appropriate network upgrade requirements." <br style="clear: both" />

Technical architecture: ArcGIS Pro Citrix remote desktop traffic improvements
Figure 11.45 shows a summary of the benefits of ArcGIS Pro remote desktop deployment. Network traffic requirements are reduced for the ArcGIS Enterprise IOC deployment when leveraging ArcGIS Pro remote desktops.

Recommended network bandwidth savings
 * Data center—1000 Mbps LAN connection (no change)
 * Data center—90 Mbps WAN connection (no change)
 * Site 2 Operations facility—24 Mbps to 18 Mbps
 * Site 3 Freeberg—45 Mbps WAN connection (no change)
 * Site 4 Willsberg—24 Mbps WAN connection (no change)


 * Data center—45 Mbps Internet connection (no change)
 * Public web services will connect through the data center Internet connection

Projected network cost (WAN/Internet Service) decreases from $7,780 /month to $7,571/month.

"Warning: CPT network pricing is used for demonstration purposes only." <br style="clear: both" />

Enterprise design solution: ArcGIS Pro Citrix remote clients
Figure 11.46 supports up to 72 concurrent ArcGIS Pro remote desktop clients.

The Citrix host platform
 * New Xeon Gold 6132 28-core server with two NVIDIA GRID Tesla P40 video cards.
 * Citrix tier solution on the left (3.6% utilization) does not include any ArcGIS Pro geoprocessing jobs.
 * Citrix tier solution on the right (79.1% utilization) includes 47 concurrent batch jobs.

=
CPT Design platform solution: ArcGIS Pro Citrix remote clients deployment=====

The Server host platform
 * Xeon Gold 5122 8-core servers.
 * Two (2) platform nodes at 18.2% utilization.

"Best practice: ArcGIS Pro background geoprocessing needs dictate host platform capacity." <br style="clear: both" />

Phase 1 ArcGIS Enterprise IOC baseline design solution
Figure 11.47 shows an ArcGIS Enterprise IOC hardware upgrade baseline solution (includes 2018 Server host platform upgrade).

Figure 11.48 provides a business cost summary supporting the available Phase 1 City of Rome GIS deployment options.

====CPT Phase 1 ArcGIS Enterprise IOC baseline design (ArcGIS Pro Citrix remote editor, Web GIS Pro viewer) solution====

The Citrix host platform (upgraded in the previous slide)
 * New Xeon Gold 6132 28-core server with two NVIDIA GRID Tesla P40 video cards.
 * Citrix tier solution on the left (3.0% utilization) does not include any ArcGIS Pro geoprocessing jobs. Column AF identifies the capability to support up to 35 concurrent batch jobs in conjunction with the client loads.
 * Citrix tier solution on the right (77.7% utilization) includes 31 concurrent batch jobs.

The Server host platform (new 2018 hardware) <br style="clear: both" />
 * Xeon Gold 5122 8-core server.
 * Two (2) platform nodes at 20.4% utilization.

Phase 2 Water Utility Solution
For Phase 2, City of Rome plans to deploy the ArcGIS Water Utility Solution with templates available on the Esri Web site.

Figure 11.49 shows the ArcGIS Water Solutions template. ArcGIS Solutions include ready-to-use maps and apps to jumpstart your work. Phase 2 leverages ArcGIS Solutions to implement an upgrade of the City of Rome water utility operations.

The ArcGIS Water Solutions include over 46 maps and apps that can be downloaded and used by customers to jumpstart their GIS operations. Solutions include water-specific information products supported by the following applications:
 * ArcGIS Desktop - 11
 * Collector for ArcGIS - 13
 * ArcGIS GeoEvent Server - 4
 * Operations Dashboard for ArcGIS - 4
 * Web AppBuilder for ArcGIS - 8
 * Web Applications - 20

Solutions also include a model organization template for ArcGIS Online and Portal for ArcGIS.

These ArcGIS solutions are samples used for typical Water Delivery, Sewer Collection, and Stormwater Conveyance operations.

Technical architecture: Phase 2 Operations and Water Utilities existing operations
Figure 11.50 shows a summary of the Phase 2 user locations and existing network connectivity.

City Hall data center remote network connections (Phase 1 baseline) are as follows:
 * Data center—1000 Mbps LAN connection
 * Data center—45 Mbps WAN connection
 * Site 2 Operations facility—12 Mbps WAN connection
 * Site 3 Freeberg—24 Mbps WAN connection
 * Site 4 Willsberg—24 Mbps WAN connection
 * Site 5 Perth—1.5 Mbps WAN connection
 * Site 6 Wawash—1.5 Mbps WAN connection
 * Site 7 Jackson—1.5 Mbps WAN connection
 * Site 8 Petersville—1.5 Mbps WAN connection
 * Site 9 Rogerton—1.5 Mbps WAN connection


 * Data center—24 Mbps Internet connection
 * Public services connect through Internet connection

Reference network cost ($8,935/month)

Workflow loads analysis: Water Utilities solution
The workflow loads analysis identifies the workflow patterns supporting user business requirements, establishes a display complexity (performance target) for each workflow, and identifies user locations (local or remote) and peak concurrent system loads (users or transaction rates) for each workflow pattern.

Workflow display complexity: Water Utilities solution
Figure 11.51 shows workflow patterns identified for the Water Solutions. Display complexity is identified for each of the Water maps and apps, and workflows are grouped by technology pattern and display complexity.

Display complexity should be reviewed and updated for the City of Rome Geodatabase.
 * Review Water Solution map performance with City of Rome Geodatabase.
 * Adjust complexity estimates for remaining Water Solutions based on measured performance.

User workflow complexity is an estimate of the processing loads required for an average information product display transaction. The workflow complexity estimate will be used with the CPT to generate appropriate system design performance specifications.

"Best practice: A conservative workflow complexity will ensure an adequate system design solution." <br style="clear: both" />

Water user needs template
Figure 11.52 shows a Water Solutions user needs template that can be used as a framework for gathering business requirements.

Template groups ArcGIS Water solutions based on relative display complexity.
 * Desktop: medium, heavy, 2xmedium, and batch processing complexity
 * Collector: light and medium processing complexity
 * Dashboard: light and medium complexity
 * Web Apps: light, medium, heavy, 2xmedium, and GeoEvent feeds
 * GeoEvent Server: events per second

"Best practice: A Water user needs template is used for workflow loads analysis."

The Water user needs template is modified to show the City of Rome user needs.
 * Location along with department and network connectivity (Columns A-D).
 * Total Water maps and apps users (column E).
 * Peak user loads for each application category (column F-CT).

"Best practice: Identify peak load estimates by software technology and complexity." <br style="clear: both" />

Phase 2 Operations and Water Utilities user needs
Figure 11.53 shows results of the City of Rome Phase 2 user needs assessment. Results of the Water user needs analysis provides information needed to complete a composite user needs summary for the Phase 2 Operations and Water Utilities deployment.

The Phase 2 deployment will initially leverage the Water Solutions maps and apps.
 * Delivers rapid deployment with COTS maps and apps.
 * Minimizes deployment risk.

Water maps and apps can be expanding to support custom business requirements.
 * System design is based on generic performance targets.
 * Custom Water applications can be deployed in same categories.
 * Water Solutions performance categories support typical Water deployments.

"Best practice: User needs analysis and system design based on the Water Solutions templates reduces implementation risk and accelerates return on investment." <br style="clear: both" />

Workflow performance targets: Water Utility deployment
Figure 11.54 shows the workflow performance targets selected for the City of Rome Phase 2 deployment. The CPT can be used to generate appropriate workflow performance targets for the system design.

Phase 2 builds on the Phase 1 deployment.

New ArcGIS Desktop workflows
 * DeskEMapMed. ArcMap workstation Medium workflows.
 * DeskEMap2Med. ArcMap workstation 2xMedium workflows.
 * DeskMapGP. Desktop ArcMap workstation geoprocessing services.
 * CitrixEMapMed. ArcMap remote desktop Medium workflows.
 * CitrixEMapHvy. ArcMap remote desktop Heavy workflows.
 * CitrixEMap2Med. ArcMap remote desktop 2xMedium workflows.
 * CitrixPro2Med40%. Pro remote desktop 2xMedium workflows.
 * CitrixGeoBatch. ArcMap and Pro remote desktop batch services.

New Collector, GeoEvent, and Operations Dashboard workflows
 * MobileMed10%. Collector for ArcGIS mobile client workflow.
 * GeoEventSvr. GeoEvent streaming services.
 * DashMed40%. Operations Dashboard clients.

New Web Application workflows
 * Webin2Med40%. New Webinternal 2xMedium workflows.

CPT project workflows: Water Utility deployment
<br style="clear: both" />

System design process: Phase 2 Water Utilities deployment
Figure 11.55 shows the process used to complete the system design. The system design process will be used to evaluate the Phase 2 Water Utilities deployment.

System design process: <br style="clear: both" />
 * Technical architecture strategy. Figure 37 shows City of Rome Phase 2 technical architecture strategy. Network traffic adjustments will impact technical architecture and infrastructure costs, and a summary of these impacts will be shared following the software configuration.
 * User requirements analysis.
 * Network suitability analysis.
 * Platform architecture selection.
 * Software configuration.
 * Enterprise design solution.

Platform architecture selection: Phase 2 Water Utilities deployment
Figure 11.56 shows The Phase 2 Operations and Water Utilities platform architecture.

The Phase 2 Operations and Water Utilities platform architecture includes the following.
 * RDSH tier: ArcGIS Desktop ArcMap and Pro remote desktop clients.
 * Web tier: Internal and public web and Portal servers.
 * GIS tier: Internal and public GIS publication and hosting server sites, plus GeoEvent server machines.
 * DBMS tier: Production and Publication geodatabase, internal and external relational data store, and public geospatial data store.

Each platform environment must be configured to support high-availability requirements.

"Best practice: A virtual server data center environment provides optimum flexibility for deploying and supporting GIS operations."

CPT Design network suitability analysis: Water Utility deployment
<br style="clear: both" />

Workflow performance summary: Phase 2 Water Utilities deployment
Figure 11.57 shows the CPT Design Phase 2 workflow performance summary.

Workflow performance summary provides the following representation.
 * Average processing and queue times for each user workflow.
 * Average difference in performance between each site location.
 * Average performance for shared public services.

Important to note that the CPT model shows average performance levels.
 * Some display response times can be lighter.
 * Other display response times will be slower.
 * Queue times will vary depending on random load profiles.

"Best practice: Workflow performance summary can be used to identify realistic performance expectations." <br style="clear: both" />

Technical architecture: Phase 2 Water Utilities deployment (network bandwidth upgrades)
Figure 11.58 shows a summary of the Phase 2 user locations and network connectivity. Network traffic will require bandwidth upgrades to support the identified Phase 2 user requirements.

Phase 2 network upgrades.
 * Data center—1000 Mbps LAN connection (no change)
 * Data center WAN—upgrade 45 Mbps to 310 Mbps
 * Site 2 Operations facility WAN—upgrade 12 Mbps to 90 Mbps
 * Site 3 Freeberg WAN—upgrade 24 Mbps to 45 Mbps
 * Site 4 Willsberg WAN—upgrade 24 Mbps to 45 Mbps
 * Site 5 Perth WAN—upgrade 1.5 Mbps to 12 Mbps
 * Site 6 Wawash WAN—upgrade 1.5 Mbps to 45 Mbps
 * Site 7 Jackson WAN—upgrade 1.5 Mbps to 24 Mbps
 * Site 8 Petersville WAN—upgrade 1.5 Mbps to 45 Mbps
 * Site 9 Rogerton WAN—upgrade 1.5 Mbps to 45 Mbps


 * Data center Internet—upgrade 24 Mbps to 135 Mbps
 * Public services connect through Internet connection

Current network cost (WAN/Internet Service) increases from $8,935/ month to $19,444/month.

"Warning: CPT network pricing is used for demonstration purposes only."

====CPT Design generic 4-tier platform configuration: Water Utility deployment==== ====CPT Design generic 4-tier software configuration: Water Utility deployment==== ====CPT Design generic 4-tier platform solution: Water Utility deployment==== <br style="clear: both" />

Enterprise design solution: Phase 2 Water Utilities deployment
Figure 11.59 shows the recommended platform solution for the City of Rome Phase 2 Operations and Utilities deployment.

The following host platform tier support the data center processing loads.

The Citrix host platform: Xeon Gold 6132 28-core servers
 * 7 platform nodes at 10.6% utilization.
 * Maximum of 168 ArcGIS Pro remote desktop sessions (graphics card limitation).
 * Capacity to support up to 100 concurrent ArcGIS Pro background jobs.

Server host platform: Xeon Gold 5115 20-core servers
 * Two platform nodes at 36.4% utilization.

"Best practice: Proper system design promotes implementation success." <br style="clear: both" />

Phase 3 Water Utility Network, Web GIS, and ArcGIS Pro Branch Versioning
Phase 3 will implement the ArcGIS 10.6 Utility Network with Branch Versioning and ArcGIS Pro Feature Editing. ArcGIS Pro clients will leverage ArcGIS Pro feature cache for optimum client display performance.

ArcGIS Pro workflow performance targets: Water Utility deployment
Figure 11.60 shows the ArcGIS Pro workflow performance targets selected for the City of Rome Phase 2 deployment. The CPT can be used to generate appropriate workflow performance targets for the system design.

Phase 3 builds on the Phase 2 deployment.

New ArcGIS Desktop workflows
 * DeskE$ProMed20%_AGD wkstn$ FSvc Pro 2D VP Med 20%Dyn 19x10 Feature +$$
 * DeskE$ProHvy20%_AGD wkstn$ FSvc Pro 2D VP Hvy 20%Dyn 19x10 Feature +$$
 * DeskE$Pro2Med_AGD wkstn$ FSvc Pro 2D VP 2Med 20%Dyn 19x10 Feature +$$
 * DeskProGP_AGD wkstn$ FSvc Pro 2D V Hvy 20%Dyn 19x10 Feature +$$

System design process: Phase 3 Water Utilities deployment
System design process: <br style="clear: both" />
 * Technical architecture strategy.
 * User requirements analysis.
 * Network suitability analysis.
 * Platform architecture selection.
 * Software configuration.
 * Enterprise design solution.

Platform architecture selection: Phase 3 Water Utilities deployment
Figure 11.61 shows The Phase 3 Operations and Water Utilities platform architecture.

The Phase 3 Operations and Water Utilities platform architecture includes the following.
 * Web tier: Internal and public web and Portal servers.
 * GIS tier: Internal and public GIS publication and hosting server sites, plus GeoEvent server machines.
 * DBMS tier: Production and Publication geodatabase, internal and external relational data store, and public geospatial data store.

Each platform environment must be configured to support high-availability requirements.

"Best practice: A virtual server data center environment provides optimum flexibility for deploying and supporting GIS operations."

CPT Design analysis for the Phase 3: City of Rome Water Utility deployment
<br style="clear: both" />

Workflow performance summary: Phase 3 Water Utilities deployment
Figure 11.62 shows the CPT Design Phase 3 workflow performance summary.

Workflow performance summary provides the following representation.
 * Average processing and queue times for each user workflow.
 * Average difference in performance between each site location.
 * Average performance for shared public services.

Important to note that the CPT model shows average performance levels.
 * Some display response times can be lighter.
 * Other display response times will be slower.
 * Queue times will vary depending on random load profiles.

"Best practice: Workflow performance summary can be used to identify realistic performance expectations." <br style="clear: both" />

Technical architecture: Phase 3 Water Utilities deployment (network bandwidth upgrades)
Figure 11.63 shows a summary of the Phase 3 user locations and network connectivity. Network traffic will require bandwidth upgrades to support the identified Phase 3 user requirements.

Phase 3 network upgrades.
 * Data center—1000 Mbps LAN connection (no change)
 * Data center WAN—upgrade 310 Mbps (no change)
 * Site 2 Operations facility WAN—90 Mbps (no change)
 * Site 3 Freeberg WAN—upgrade 45 Mbps (no change)
 * Site 4 Willsberg WAN—upgrade 45 Mbps (no change)
 * Site 5 Perth WAN—12 Mbps (no change)
 * Site 6 Wawash WAN—upgrade 45 Mbps (no change)
 * Site 7 Jackson WAN—upgrade 24 Mbps (no change)
 * Site 8 Petersville WAN—upgrade 45 Mbps (no change)
 * Site 9 Rogerton WAN—upgrade 45 Mbps (no change)


 * Data center Internet—135 Mbps (no change)
 * Public services connect through Internet connection

Current network cost (WAN/Internet Service) $19,444/month (no change).

"Warning: CPT network pricing is used for demonstration purposes only."

<br style="clear: both" />

Enterprise design solution: Phase 3 Water Utilities deployment
Figure 11.64 shows the recommended platform solution for the City of Rome Phase 3 Operations and Utilities deployment.

The following host platform tier support the data center processing loads.

Server host platform: Xeon Gold 5115 20-core servers
 * Two platform nodes at 38.3% utilization.

"Best practice: Proper system design promotes implementation success." <br style="clear: both" />

City of Rome system design cost analysis summary
Figure 11.65 provides a final business cost summary supporting the available City of Rome GIS deployment options.

Phase 1 deployment options
 * ArcGIS Enterprise IOC deployment
 * Operational cost increase due to network traffic ($50,584 annual increase)


 * Implement vector tile basemaps
 * Operational cost savings due to reduced network traffic ($16,582 annual increase)


 * Implement WebGIS Pro client feature cache
 * Operational cost savings due to reduced network traffic ($11,814 savings)


 * Implement Citrix upgrade (traditional VDI deployment)
 * Operational cost savings due to reduced network traffic ($24,318 savings)
 * Host server upgrade costs (225,011 increase)


 * Implement Citrix upgrade (WebGIS Pro viewers with client feature caching)
 * Operational cost savings due to reduced network traffic ($34,308 savings)
 * Host server upgrade costs (145,772 increase)

Phase 2 Water Utilities deployment (traditional versioning)
 * Estimated hardware server cost= $510,001
 * Estimated virtualization pricing = $89,910/year
 * Estimated GPU pricing = $140,000
 * Estimated network pricing = $233,324/year

Phase 3 Utility Network Branch Versioning
 * Estimated hardware server cost= $60,386
 * Estimated virtualization pricing = $19,980/year
 * Estimated network pricing = $233,324/year

"Warning: Pricing models in CPT are used for demonstration purposes only and should be updated with actual costs for each customer system design analysis." <br style="clear: both" />

Choosing a system configuration
The best solution for a given organization depends on the distribution of the user community and the type of operational data in use. User requirements determine the number of machines necessary (to support the operational environment), the amount of memory required (to support the applications), and the amount of disk space needed (to support the system solution). The system design models provide target performance metrics to aid in capacity planning. The capacity planning tool incorporates standard templates representing the sizing models and provides a manageable interface to help in enterprise-level capacity planning efforts. The CPT can be a big help in applying the results of the user needs assessment.

User needs change as organizations change, so this assessment not only identifies platform and infrastructure specifications and sets performance targets for the initial implementation, it is also part of the process going forward. System upgrades, new technology solutions, tuning and optimizing performance--every implementation or change is like a new launch, insofar as you need to plan for it. Planning provides an opportunity to establish performance milestones that can be used to manage a successful GIS implementation. Performance targets used in capacity planning can provide target milestones to validate performance and scalability throughput deployment of the system.

=CPT Capacity Planning videos=

Previous Editions
City of Rome 43rd Edition

Page Footer Specific license terms for this content System Design Strategies 26th edition - An Esri ® Technical Reference Document • 2009 (final PDF release)