City of Rome Year 2 (CPT Demos)

Arc18CapacityPlanning0701 release

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 A1-11.44 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.

Phase 2: City of Rome Water Utility deployment


CPT Workflow Loads Analysis: Water Utility deployment
Figure A1-11.45 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.

Figure A1-11.46 shows the CPT Calculator being used to generate performance targets for the City of Rome Water Utility deployment. Software technology performance factors are selected for a 2xMedium complexity ArcGIS Desktop Pro 2D workflow using vector tile basemaps and deployed on the Citrix VDI host platform tier.

Workflow recipes used to represent Water Utility operations. 
 * AGD wkstn ArcMap 2D V 2Med 100%Dyn 19x10 Feature
 * AGD wkstn Pro 2D V 2Med 40%Dyn 19x10 Feature +$$
 * AGD wkstn ArcMap 2D V Hvy 100%Dyn 19x10 Feature
 * AGD Citrix ArcMap 2D V Hvy 100%Dyn 19x10 ICA
 * AGD Citrix Pro 2D R Hvy 40%Dyn 19x10 ICA
 * AGD Citrix ArcMap 2D V 2Med 100%Dyn 19x10 ICA
 * AGD Citrix Pro 2D R 2Med 40%Dyn 19x10 ICA
 * AGD Citrix ArcMap 2D V Hvy 100%Dyn 19x10 ICA
 * AGS SOAP 2D VP Med 10%Dyn 13x7 Feature
 * AGS REST 2D V Med 40%Dyn 13x7 PNG24 +$$
 * AGS REST 2D V 2Med 40%Dyn 13x7 PNG24 +$$
 * AGS GeoEvent 2D V Med 100%Dyn 13x7 Feature

CPT project workflows: Water Utility deployment
Figure A1-11.47 shows the results of our City of Rome CPT workflow loads analysis. Project workflows are included on the CPT Workflow tab for use in our system design. Project workflows can be established from Standard Workflows located on the Workflow tab, or from Calculator Workflows generated from the CPT Calculator tab.

Project Workflows supporting City of Rome Water Utility deployment.
 * DeskEMapMed_AGD wkstn ArcMap 2D V Med 100%Dyn 19x10 Feature
 * DeskEMap2Med_AGD wkstn ArcMap 2D V 2Med 100%Dyn 19x10 Feature
 * DeskMapGP_AGD wkstn ArcMap 2D V Hvy 100%Dyn 19x10 Feature
 * CitrixEMapMed_AGD Citrix ArcMap 2D V Med 100%Dyn 19x10 ICA
 * CitrixEMapHvy_AGD Citrix ArcMap 2D V Hvy 100%Dyn 19x10 ICA
 * CitrixEMap2Med_AGD Citrix ArcMap 2D V 2Med 100%Dyn 19x10 ICA
 * CitrixPro2Med40%_AGD Citrix Pro 2D RP 2Med 40%Dyn 19x10 ICA
 * CitrixGeoBatch_AGD Citrix GeoBatch
 * MobileMed10%_AGS SOAP 2D VP Med 10%Dyn 13x7 Feature
 * DashMed40%_AGS REST 2D V Med 40%Dyn 13x7 PNG24 +$$
 * WebIn2Med40%_AGS REST 2D V 2Med 40%Dyn 13x7 PNG24 +$$
 * GeoEventSvr_AGS GeoEvent 2D V Med 100%Dyn 13x7 Feature

Each organization's solution will be different. 
 * The ArcGIS Water Solution templates provide a variety of maps and apps for review and evaluation.
 * Several decisions must be made during the design process before a final representation is collected in the capacity planning tool.
 * The process and discussion leading up to the final design should be documented as a record of decisions made during the design process.
 * Design documentation should clearly define the basis for the final workflow representation.

CPT Design requirements analysis: Water Utility deployment
The City of Rome Design includes local and public internet clients, plus clients from eight (8) remote sites. The CPT requirements analysis will be configured to support all user locations.

Figure A1-11.45 Operations and Water Utilities user needs summary is used as a reference to configure the Design requirements. User workflows and site locations include the Phase 1 ArcGIS Enterprise IOC workflows and the additional Phase 2 Water Utility operations.

Peak concurrent users or throughput rates are entered for each user workflow in columns C and D.

Figure A1-11.48 (section 1) shows results of the City of Rome CPT Design requirements analysis for the first 4 locations. 
 * City of Rome City Hall LAN
 * Operations
 * Freeberg
 * Willsberg

Figure A1-11.49 (section 2) shows the results of the City of Rome CPT Design requirements analysis. Following locations are included in this analysis:
 * Perth
 * Wawash
 * Jackson
 * Petersville
 * Rogerton
 * Public Internet clients

While the CPT Design requirements are configured, Excel compares peak site traffic with available bandwidth and completes a network suitability analysis (RED cells identify traffic bottlenecks). Network bandwidth must be updated to support Phase 2 business requirements. 

CPT Design network suitability analysis: Water Utility deployment
Data center and remote site bandwidths were identified by the network administration and provided in the City of Rome technical architecture: Water Utility deployment diagram.

While configuring the requirements analysis and selecting the network bandwidth, the CPT Design tab completes the network suitability analysis. Network utilization (column I) shows reasonable capacity for all locations, and display performance (column V) looks good for workflows at all site locations.

Figure A1-11.50 (section 1) shows the results of the network suitability analysis and recommended network bandwidth upgrades. Following locations and network connections are included in this analysis:
 * Data Center LAN = 1000 Mbps (10% peak utilization)
 * Data Center WAN = 310 Mbps (79% peak utilization)
 * Operations = 90 Mbps (80% peak utilization)
 * Freeberg = 45 Mbps (80% peak utilization)
 * Willsberg = 45 Mbps (80% peak utilization)



Figure A1-11.51 (section 2) shows the results of the network suitability analysis and network bandwidth upgrades. Following locations and network connections are included in this analysis:
 * Additional Data Center WAN sites
 * Perth = 12 Mbps (12% peak utilization)
 * Wawash = 45 Mbps (50% peak utilization)
 * Jackson = 24 Mbps (47% peak utilization)
 * Petersville = 45 Mbps (75% peak utilization)
 * Rogerton = 45 Mbps (75% peak utilization)


 * Data Center Internet clients = 135 Mbps (73% peak utilization)

Estimated network cost is generated from the network pricing model and shown below the network selections (column H). City of Rome network service charges following the Phase 2 Water Utility deployment is $19,444/month. 

CPT Design generic 4-tier platform configuration: Water Utility deployment
Figure A1-11.52 shows how the CPT Design tab was configured for the Phase 2 generic 4-tier virtual server platform architecture. The GeoEvent server is configured on a dedicated virtual tier to minimize deployment risk.

The City of Rome Figure 11.56 phase 2 platform architecture diagram is used to identify the minimum number of server machines for each platform tier. A minimum of two virtual machines will be deployed for each virtual server to support high-availability requirements. Three 2-core virtual machines will be deployed for the GeoEvent tier.

Generic 4-tier platform architecture selection
 * WTS platform tier. ArcGIS Desktop deployed on the Citrix virtual host platform tier, with VDI and 6 core/node for the virtual desktop configuration (column I).
 * GeoEvent platform tier. GeoEvent server role is configured on a dedicated virtual server tier deployed on the Server virtual host platform tier.
 * Web platform tier. Supports separate internal and external Web and Portal sites deployed on the Server virtual host platform tier (column I selection).
 * GIS platform tier. Supports separate internal and external ArcGIS Server publishing and hosting sites deployed on the Server virtual host platform tier (column I selection).
 * DBMS platform tier. Supports production and publication geodatabase servers, internal and public relational data stores, and public geospatial big data store all deployed on the Server virtual host platform tier (column I selection).

"Best practice: The generic 4-tier generic platform virtual server configuration can be used to generate a proper virtual host platform recommendation."

"Warning: Accurate number of machines (fixed nodes) on each virtual tier is needed to generate proper virtual host platform memory recommendations.'" 

CPT Design generic 4-tier software configuration: Water Utility deployment
For the generic virtual server platform tier configuration, the software assignment for each software component can be assigned from the top default configuration (LAN row, columns J through Q). All virtual server workflow software components are selected as default, assigned from the LAN default selection.

The generic 4-tier software configuration will assign workflow processing loads to the proper virtual server tier, and those loads will be sent to the selected virtual host platform tier. CPT Design platform sizing analysis will select the proper virtual host platform processor solution, while the proper number of machines on each virtual tier is needed to generate the final memory recommendations.

Figure A1-11.53 (section 1) shows the CPT Design generic 4-tier virtual server software configuration for the City of Rome Water Utility deployment. Following sites and workflows are included in this analysis:
 * Data Center LAN = 10 local workflows
 * Data Center WAN sites
 * Operations = 9 workflows
 * Freeberg = 6 workflows
 * Willsberg = 6 workflows



Figure A1-11.54 (section 1) shows the CPT Design generic 4-tier virtual server software configuration for the Phase 3 City of Rome Water Utility deployment. GeoEvent Server role will be deployed on a separate virtual server tier to minimize deployment risk. Following sites and workflows are included in this analysis:
 * Data Center WAN sites
 * Perth = 4 workflows
 * Wawash = 4 workflows
 * Jackson = 4 workflows
 * Petersville = 4 workflows
 * Rogerton = 4 workflows
 * Data Center Public Internet clients = 6 web service workflows and GeoEvent ingestion workflow transactions.

GeoEvent workflow SOC load is assigned to the GeoEvent platform tier. The GeoSpatial data store is part of the virtual DBMS platform tier.

"Best practice: The generic 4-tier generic platform configuration simplifies software configuration. " 

CPT Design generic 4-tier platform solution: Water Utility deployment
Figure A1-11.55 shows the recommended platform solution for City of Rome Phase 2 Water Utility deployment.

The following steps should be followed to configure the ArcGIS Desktop VDI tier and the supporting Citrix virtual host platform. "Best practice: Xeon Gold 6132 28 core (2 chip) 2600 MHz with NVIDIA Tesla GRID video card is the recommended VDI Host platform for 25 concurrent ArcGIS Pro clients."
 * Select VDI (virtual desktop infrastructure) with 6 core/node for WTS tier virtualization architecture (column I).
 * Select new Xeon Gold 6132 28 core (2 chip) 2600 MHz Citrix virtual host platform (Column B). WTS VDI platform tier must be same selection.
 * Set WTS tier fixed nodes to 167 (column H). Total remote ArcGIS Desktop clients is 167, and clients will use a mix of ArcMap and ArcGIS Pro applications.  ArcGIS Pro loads are significantly heavier than ArcMap due to more efficient project workflow and concurrent batch processing jobs. City estimates peak load would be represented by 167 concurrent ArcGIS Pro users.
 * With WTS fixed nodes > 0 and no batch jobs, column AF identifies required Citrix virtual host platforms (7 host platforms). CPT Design high availability configuration is N+1; City decides 7 host servers supporting 167 ArcGIS Pro clients (25 virtual desktops per node) is adequate to meet their high availability requirements.
 * Set Citrix virtual host tier fixed nodes = 7. Cost of the NVIDIA Tesla video cards with 25 virtual desktops/node for the Citrix virtual host tier is shown in column AF just below the Citrix virtual host tier ($140,000).
 * Estimated additional ArcGIS Pro concurrent batch jobs supported with the current configuration is identified in the Citrix virtual host tier in column AF (top cell - 112 concurrent batch jobs).

Once the CPT Design tab is configured properly, and workflow software components assigned to the appropriate platform tier, excel completes the system architecture design analysis for the configured business state.


 * Virtual platform tier
 * WTS Platform tier: 167 6-core/node virtual desktops on Citrix virtual Host tier.
 * GeoEvent Platform tier: Three (3) 2-core/node virtual servers.
 * Web Platform tier: Eight (8) 2-core/node virtual servers.
 * GIS Platform tier: Eight (8) 2-core/node virtual servers.
 * DBMS Platform tier: Eleven (11) 2-core/node virtual servers.


 * Virtual Host Platforms
 * Citrix virtual host tier: Eight (8) Xeon Gold 6132 28 core (2 chip) 2600 MHz platforms
 * 529 GB RAM recommended memory per server node (167 concurrent ArcGIS virtual desktops).
 * 11.5 percent utilization during peak loads (no batch jobs - 167 concurrent ArcGIS virtual desktops)
 * Up to 167 concurrent ArcGIS Desktop (ArcMap and ArcGIS Pro) virtual desktops, with no more than 175 concurrent desktops using ArcGIS Pro
 * Supports up to 112 concurrent batch jobs
 * Server virtual host tier: Two (2) Xeon Gold 5115 20 core (2 chip) 2400 MHz platforms
 * 425 GB RAM recommended memory per server node (estimate 30 2-core virtual server machines)
 * 36.9 percent utilization during peak loads

"Warning: Accurate number of machines (fixed nodes) on each virtual tier is needed to generate proper virtual host platform memory recommendations."

Phase 3: City of Rome Water Utility deployment
Figure A1-11.56 shows the CPT Calculator being used to generate performance targets for the City of Rome Water Utility deployment. Local and remote ArcGIS Desktop workflows will be supported by ArcGIS Pro workstations, accessing a branch versioned GeoDatabase through ArcGIS Server feature services. ArcGIS Pro client feature caching will reduce remote service queries by 80 percent, resulting in 20 percent dynamic requests to the server. Vector tile cache basemap will be used to enhance client feature caching.

New Phase 3 Workflow recipes used to represent Water Utility operations. 
 * AGD wkstn$ FSvc Pro 2D VP Med 20%Dyn 19x10 Feature +$$
 * AGD wkstn$ FSvc Pro 2D VP Hvy 20%Dyn 19x10 Feature +$$
 * AGD wkstn$ FSvc Pro 2D VP 2Med 20%Dyn 19x10 Feature +$$

CPT project workflows: Water Utility deployment
Figure A1-11.57 shows the results of our City of Rome CPT workflow loads analysis. New Project workflows are included on the CPT Workflow tab for use in our Phase 3 system design analysis.

New Phase 3 Project Workflows supporting City of Rome Water Utility deployment.
 * 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$Pro2Med20%_AGD wkstn$ FSvc Pro 2D VP 2Med 20%Dyn 19x10 Feature +$$
 * DeskProGP_AGD wkstn$ FSvc Pro 2D VP Hvy 20%Dyn 19x10 Feature +$$

Each organization's solution will be different. 
 * The ArcGIS Water Solution templates provide a variety of maps and apps for review and evaluation.
 * Several decisions must be made during the design process before a final representation is collected in the capacity planning tool.
 * The process and discussion leading up to the final design should be documented as a record of decisions made during the design process.
 * Design documentation should clearly define the basis for the final workflow representation.

CPT Design requirements analysis: Water Utility deployment
The City of Rome Design includes local and public internet clients, plus clients from eight (8) remote sites. The CPT requirements analysis will be configured to support all user locations.

Figure A1-11.45 Operations and Water Utilities user needs summary is used as a reference to configure the Design requirements. User workflows and site locations include the Phase 1 ArcGIS Enterprise IOC workflows and the additional Phase 2/3 Water Utility operations.

Peak concurrent users or throughput rates are entered for each user workflow in columns C and D.

Figure A1-11.58 (section 1) shows results of the City of Rome CPT Design requirements analysis for the first 4 locations. 
 * City of Rome City Hall LAN
 * Operations
 * Freeberg
 * Willsberg

Figure A1-11.59 (section 2) shows the results of the City of Rome CPT Design requirements analysis. Following locations are included in this analysis:
 * Perth
 * Wawash
 * Jackson
 * Petersville
 * Rogerton
 * Public Internet clients

While the CPT Design requirements are configured, Excel compares peak site traffic with available bandwidth and completes a network suitability analysis (RED cells identify traffic bottlenecks). Network bandwidth does not change to support the Phase 3 business requirements. 

CPT Design generic 4-tier platform configuration: Water Utility deployment
Figure A1-11.60 shows how the CPT Design tab was configured for the Phase 2 generic 4-tier virtual server platform architecture. The GeoEvent server is configured on a dedicated physical tier to minimize deployment risk.

The City of Rome Figure 11.61 phase 3 platform architecture diagram is used to identify the minimum number of server machines for each platform tier. A minimum of two virtual machines will be deployed for each virtual server to support high-availability requirements. Three 2-core machines will support the GeoEvent Server tier.

Generic platform architecture selection
 * GeoEvent platform tier. GeoEvent server role is configured on a dedicated virtual server tier assigned to the Server virtual host platform tier.
 * Web platform tier. Supports separate internal and external Web and Portal sites deployed on the Server virtual host platform tier (column I selection).
 * GIS platform tier. Supports separate internal and external ArcGIS Server publishing and hosting sites deployed on the Server virtual host platform tier (column I selection).
 * DBMS platform tier. Supports production and publication geodatabase servers, internal and public relational data stores, and public geospatial big data store all deployed on the Server virtual host platform tier (column I selection).

"Best practice: The generic 4-tier generic platform virtual server configuration can be used to generate a proper virtual host platform recommendation."

"Warning: Accurate number of machines (fixed nodes) on each virtual tier is needed to generate proper virtual host platform memory recommendations.'" 

CPT Design generic 4-tier software configuration: Water Utility deployment
For the generic virtual server platform tier configuration, the software assignment for each software component can be assigned from the top default configuration (LAN row, columns J through Q). All virtual server workflow software components are selected as default, assigned from the LAN default selection.

The generic 4-tier software configuration will assign workflow processing loads to the proper virtual server tier, and those loads will be sent to the selected virtual host platform tier. CPT Design platform sizing analysis will select the proper virtual host platform processor solution, while the proper number of machines on each virtual tier is needed to generate the final memory recommendations.

Figure A1-11.61 (section 1) shows the CPT Design generic 4-tier virtual server software configuration for the City of Rome Water Utility deployment. Following sites and workflows are included in this analysis:
 * Data Center LAN = 10 local workflows
 * Data Center WAN sites
 * Operations = 9 workflows
 * Freeberg = 6 workflows
 * Willsberg = 6 workflows

<br style="clear: both" />

Figure A1-11.62 (section 1) shows the CPT Design generic 4-tier virtual server software configuration for the City of Rome Water Utility deployment. GeoEvent Server role will be deployed on a separate dedicated physical server tier to minimize deployment risk. Following sites and workflows are included in this analysis:
 * Data Center WAN sites
 * Perth = 4 workflows
 * Wawash = 4 workflows
 * Jackson = 4 workflows
 * Petersville = 4 workflows
 * Rogerton = 4 workflows
 * Data Center Public Internet clients = 6 web service workflows and GeoEvent ingestion workflow transactions.

GeoEvent workflow SOC load is assigned to the GeoEvent platform tier. The GeoSpatial data store is part of the virtual DBMS platform tier.

"Best practice: The generic 4-tier generic platform configuration simplifies software configuration. " <br style="clear: both" />

CPT Design generic 4-tier platform solution: Water Utility deployment
Figure A1-11.63 shows the recommended platform solution for City of Rome Water Utility deployment.

Once the CPT Design tab is configured properly, and workflow software components assigned to the appropriate platform tier, excel completes the system architecture design analysis for the configured business state.


 * Virtual platform tier
 * GeoEvent Platform tier: Three (3) 2 core/node virtual servers.
 * Web Platform tier: Eight (8) 2 core/node virtual servers.
 * GIS Platform tier: Eight (8) 2 core/node virtual servers.
 * DBMS Platform tier: Eleven (11) 2 core/node virtual servers.


 * Virtual Host Platforms
 * Server virtual host tier: Two (2) Xeon Xeon Gold 5115 20-core (2 chip) 2400 MHz platforms
 * 425 GB RAM recommended memory per server node (estimate 30 2-core virtual server machines)
 * 38.7 percent utilization during peak loads

"Warning: Accurate number of machines (fixed nodes) on each virtual tier is needed to generate proper virtual host platform memory recommendations."

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