City of Rome Year 2 (CPT Demos 39th Edition)

Fall 2016 City of Rome Year 2 (CPT Demos) 39th Edition Arc16CapacityPlanning0701 release

This section shares the CPT analysis supporting the City of Rome Year 2 system architecture design. The City of Rome case study brings together what has been discussed in the earlier chapters and demonstrates the value of the system design analysis in making informed design decisions. 

City of Rome System Architecture Design: Year 2
Figure A1-11.22 provides an overview of the system architecture design process used to determine requirements for the City of Rome System Architecture Design (Year 2).

System architecture design process: 
 * Technical architecture strategy. High-level network drawing showing user site locations, network bandwidth connections, and central data center locations.
 * Workflow loads 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 architecture design analysis and provides the platform solution.

Technical architecture strategy: Year 2
Figure A1-11.23 shows the City of Rome year 2 technical architecture strategy.

A server-based architecture in the central IT data center will be expanded to support the year 2 implementation. 
 * Server platforms will include a Windows Terminal Server farm to support the remote ArcGIS for Desktop users.
 * ArcGIS for Server to support the Internal and Public web services. Web Internal services will be registered with Portal for ArcGIS.
 * A central GIS data server to support the enterprise geodatabase.

User requirements analysis: Year 2
Figure A1-11.24 shows an overview of the peak business requirements for City of Rome Year 2. The City Hall data center hardware design will be configured in the first analysis.
 * Four project workflows on the LAN network (GISDeskEditor, GISDeskView, GISDeskBA, and WebPortal).
 * Three remote sites on the WAN network (Operations, Freeberg, Willsberg).
 * Operations has two project workflows (RemoteGISView, WebPortal).
 * Freeberg and Willsberg each have two project workflows (RemoteGISView, WebPortal).
 * Public Web Services and five remote sites on the Internet network (WebPublic, Perth, Wawash, Jackson, Petersville, Rogerton)
 * One Web Services project workflow for the public internet clients (WebPublic).
 * Two project workflows for each remote site (RemoteGISView, WebPortal)

The user requirements analysis is completed by configuring the CPT Design tab to represent the business requirements identified in the user needs summary. Figure A1-11.23 shows the CPT Design tab requirements analysis module configured to represent City of Rome Year 2 requirements.
 * BatchAdmin project workflow was included on the LAN configuration to reserve capacity for executing one administrative batch process during peak operations.
 * Project workflows were updated in column B to represent the user needs. The WebInternal workflow was replaced by the WebPortal composite workflow to incorporate Portal for ArcGIS implementation during the Year 2 deployment. ArcGIS for Server internal services will be registered with Portal for ArcGIS and Web applications will consume Portal Webmaps created and shared in the Portal organization.
 * Peak users for each workflow were identified in column C.
 * Peak throughput (TPH) were included for Web services in column D.
 * Existing network bandwidth was included in column H for each network gateway.

Network suitability analysis: Year 2
Figure A1-11.25 shows the Year 2 CPT Design workflow configuration. To simplify configuration effort, start with a copy of the Year 1 CPT Design tab (HA physical server platform configuration) and add the Year 2 workflows to complete the business needs analysis.

While you configure the user requirements and site locations in the CPT, and update the site traffic summation ranges to include all site workflow traffic going over the network connections (these CPT configuration procedures were discussed in Chapter 6), Excel will complete the network suitability analysis.

Several performance problems are identified in the existing design due to network traffic bottlenecks.
 * Red cells in columns F:G identify traffic bottlenecks.
 * Recommend network upgrades to about twice the identified network traffic. These upgrades are normally coordinated with the network administrator based on the identified network traffic.

Recommended network upgrades: 
 * Data center WAN from 90 Mbps to 135 Mbps
 * Site 2 from 12 Mbps to 90 Mbps
 * Site 4 from 24 Mbps to 45 Mbps
 * Data center Internet from 24 Mbps to 310 Mbps
 * Site 5 from 1.5 Mbps to 6 Mbps
 * Site 6 from 1.5 Mbps to 45 Mbps
 * Site 7 from 1.5 Mbps to 24 Mbps
 * Site 8 from 1.5 Mbps to 90 Mbps
 * Site 9 from 1.5 Mbps to 90 Mbps

Figure A1-11.26 shows the Year 2 network suitability upgrades. Results of the network suitability analysis should be shared with the Network Administrator, and together identify upgrades for the year 2 network infrastructure to support the year 2 design. Recommended network upgrades are included in column H.

The RESET/ADJUST function in Column T must be reset and returned to SAVE to recalculate batch process productivity for the new configuration.

CPT Design shows network bottlenecks are resolved. 
 * Workflow performance summary shows relative user display performance for each workflow at each site location.

CPT Design Software configuration
Figure A1-11.27 shows the CPT software configuration module selections for year 2. The Year 2 internal Web services (WebPortal) workflows will include a Portal for ArcGIS software install on the Webin server tier (column M). Software configuration and data source will remain the same as Year 1 for all other workflows. 

Enterprise design solution: Year 2
Figure A1-11.28 shows the solution architecture pattern alternatives identified for City of Rome Year 2 system architecture design evaluation.

City of Rome Year 2 solution architecture patterns.
 * High-availability physical server configuration.
 * High-availability Virtual Server configuration.
 * Amazon Web Public Services hosting option
 * High-availability Virtual Server configuration with no WebPublic services
 * High-availability hosted Amazon Machine Instances (AMI) for WebPublic project workflows.

CPT Design analysis for high-availability physical server platform configuration: Year 2


Confirm the platform tier configuration:
 * The Workflow Configuration sheet was copied from the Year 1 high-availability physical server configuration and should have the proper hardware platform configuration set.
 * Once you confirm the proper hardware configuration, Excel completes the system architecture design analysis.
 * The E5-2637v4 4-core physical server platforms provide the lowest cost hardware solution for the Year 2 deployment.

Figure A1-11.29 shows the physical server platform requirements for the Enterprise HA physical server configuration.

The RESET/ADJUST function in Column T must be reset and returned to SAVE to recalculate batch process productivity for the new configuration.

City of Rome Year 2 HA physical server platform configuration: 
 * Five (5) E5-2637v4 4-core WTS physical servers, 57 GB RAM.
 * Two (2) E5-2637v4 4-core WebIn servers, 12 GB RAM.
 * Two (2) E5-2637v4 4-core WebPub servers, 12 GB RAM.
 * One (1) E5-2637v4 4-core DBMS server plus failover, 57 GB RAM.

CPT Design analysis for high-availability Virtual Server platform configuration: Year 2
A copy of the CPT Design for the Year 2 HA physical platform configuration can be updated to build the Year 2 high-availability virtual platform configuration.

Select Virtual Server configuration in column I.
 * Select Vserver for each virtual tier.
 * Select 2 core/node for each virtual tier.
 * Select Host platform assignment for each virtual tier.

Select Xeon E5-2699v4 44 core 2200 MHz server as the host platform. The Xeon E5-2699v4 server provided the lowest cost hardware solution for this configuration.

Once the Platform Tier are configured, Excel completes the system architecture design analysis and provides the platform solution. Figure A1-11.30 shows the high-availability virtual server platform solution for year 2.

"Warning: Virtual Server tier platform much match the assigned Host Platform selection. "

The RESET/ADJUST function in Column T must be reset and returned to SAVE to recalculate batch process productivity for the new configuration.

HA Virtual Server and host platform configuration:
 * Three (3) E5-2699v4 44 core 2200 MHz, 380 GB RAM host platforms.
 * WTS tier increased to 4-core servers for simpler administration and improved display performance.


 * Six (6) 4-core WTS Virtual Servers, 39 GB RAM.
 * Two (2) 2-core WebIn Virtual Servers, 6 GB RAM.
 * Two (2) 2-core WebPub Virtual Servers, 6 GB RAM.
 * One (1) 4-core DBMS Virtual Server plus failover, 39 GB RAM.
 * DBMS server increased to 4-core to support capacity requirements.

"Best practice: Host platform configuration must have N+1 servers for high availability." 

CPT Design analysis for data center without hosting public Web services
Copy previous high availability virtual platform configuration — Year 2 solution on separate tab and delete WebPublic peak throughput from column D. Once you remove the WebPublic peak throughput, Excel completes the system architecture design analysis.

The CPT hardware cost analysis showed the E5-2699v4 44 core platform provide the lowest overall hardware cost for the City of Rome data center once the public web services were removed. Once you confirm the proper hardware configuration, Excel completes the system architecture design analysis. 

Figure A1-11.32 shows the virtual server and host platform requirements for the Enterprise HA City Hall data center virtual server configuration after removing the Web Public service loads. The Web Public services will be deployed on Amazon Web services.

HA Virtual Server and host platform configuration:
 * Two (2) E5-2699v4 44 core (2 chip) 2200 MHz, 368 GB RAM host platforms.
 * Six (6) 4-core WTS Virtual Servers, 39 GB RAM.
 * Two (2) 2-core WebIn Virtual Servers, 6 GB RAM.
 * One (1) 4-core DBMS Virtual Server plus failover, 39 GB RAM.

"Best practice: Publishing public services on the Amazon Cloud removes requirements to host these services in your data center environment. " 

CPT Calculator analysis for Amazon Cloud public services configuration
Figure A1-11.33 shows the CPT Calculator used to compute web public server platform solution. CPT Calculator can be used for completing a single workflow system architecture design sizing analysis.

Enter the Web public peak throughput and data source selections.
 * Peak throughput = 100,000 TPH
 * Select Small FGDB data source (you will use geodatabase replication services to publish data updates to the Amazon machine instances).

Amazon AMI Platform Selection:
 * Select AMI m4.large (2vc) 24 core (2400 MHz) 8 GB as the platform selection.

"Best practice: The AMI m4.large (2vc) 24 core (2400 MHz) 8 GB virtual server machine was one of Amazon’s highest performing 2-core server configuration based on information Amazon shares for AMI instance performance. "


 * Identify a single-tier high-availability configuration.

Amazon Cloud platform solution:
 * Two (2) m4.large (2vc) 24 core (2400 MHz) 8 GB Amazon Machine Instances.
 * Data source: File geodatabase.

Amazon AMI pricing (based on pricing model):
 * Fixed cost for three-year term = $1,291 per AMI
 * No Variable cost
 * Total cost per server = $1,291
 * Cost for two servers = $3,020

"Best practice: Use ArcGIS for Server Cloud Builder to deploy services on the Amazon EC2 site." 

User requirements analysis: Year 2
Figure A1-11.34 shows an overview of the peak business requirements for City of Rome Police Department.
 * Two project workflows on the Police LAN network (GISDeskEditor, GISDeskView).
 * One Mobile Service project workflow for the Police WAN network (MobileService).

The user requirements analysis is completed by configuring the CPT Design tab to represent the business requirements identified in the user needs summary. Figure A1-11.33 shows the CPT Design tab requirements analysis module configured to represent City of Rome Police Year 2 requirements.
 * BatchAdmin project workflow was included on the LAN configuration to reserve capacity for executing one administrative batch process during peak operations.
 * Project workflows were updated in column B to represent the user needs.
 * Peak users for each workflow were identified in column C.
 * Peak throughput (TPH) were included for Web services in column D.
 * Existing network bandwidth was included in column H for each network gateway.

Network suitability analysis
Figure A1-11.35 shows the City of Rome Police Department CPT Design requirements configuration.

The RESET/ADJUST function in Column T must be reset and returned to SAVE to recalculate batch process productivity for the new configuration.

The CPT Design shows no network bottleneck issues. 

CPT Platform architecture selection
Figure A1-11.36 shows the Police hardware configuration. Separate single core VMs were established for the system administration batch process (BatchAdmin) and the mobile synchronization service (MobileService). The SDE geodatabase would be deployed on a single database server (DBMS).

Police HA Virtual Server platform solution:
 * Host platform: Xeon E5-2637v4 4-core servers.
 * Batch tier: 1-core virtual servers, 80 percent rollover.
 * GIS tier: 1-core virtual servers, 80 percent rollover.
 * DBMS tier: 2-core virtual servers, 80 percent rollover.

Xeon E5-2637v4 4 core (1 chip) 3500 MHz servers were selected as the host platforms. The E5-2637v4 processor had a SPECrate_int2006 benchmark of 60.0 per core, one of the faster machines available in the 2016 procurement period.

Platform selection: 
 * Client workstation: Intel Core i7-6700 4-core (1 chip) 3400 MHz selected to represent the client workstation environments.
 * Data center server tier: Xeon E5-2637v4 4 core (1 chip) 3500 MHz platform selected for the virtual host server platforms based on highest performing best buy 4-core server configuration.
 * 80 percent rollover selected for all server platform tier.

CPT Design software configuration
Figure A1-11.37 shows the software and virtual machine configurations. For each workflow, assign software to the appropriate platform tier and select appropriate data source.

Default Row 5 software assignment:
 * Client software set to client
 * Web software set to GIS
 * SOC software set to GIS (Mobile synchronization services)
 * DS/MDS software set to Direct Connect
 * DBMS software set to DBMS

Batch workflow software assignment (row 6):
 * Web software set to Batch (batch virtual machine)
 * SOC software set to Batch (batch virtual machine)
 * DBMS software set to Default (Police DBMS geodatabase)

All remaining workflow software assignments set to default platform.

Data source assignment DB_DBMS for all workflows. 

CPT Design analysis for high availability virtual platform configuration
Once the platforms and workflow software are configured, Excel completes the system architecture design analysis and provides the platform solution. Figure A1-11.38 shows the CPT Design Police virtual platform solution.

The RESET/ADJUST function in Column T must be reset and returned to SAVE to recalculate batch process productivity for the new configuration.

HA virtual platform solution: 
 * Two (2) Xeon E5-2637v4 4-core (2 chip) servers, 72 GB RAM for failover configuration
 * Two (2) 1-core Batch virtual servers, 3 GB RAM.
 * Two (2) 1-core WebMap virtual servers, 3 GB RAM.
 * One (1) 2-core DBMS virtual server with failover, 29 GB RAM

City of Rome business case summary: Year 2
Figure A1-11.39 shows the Rome City Hall Year 2 server deployment alternatives. The business case summary shows deployment in a high-available Virtual Server configuration would cost addition $60,000 over deploying in a physical server configuration. •	Opportunity to consolidate servers and reduce hardware costs. •	More adaptive and manageable server environment. •	Better server provisioning and recovery capabilities. Deploying the WebPublic services on Amazon EC2 servers would increase cost over the virtual solution by another $10,000.

Hardware for the Police department was $20,000.

Management may decide to move ahead with the Amazon deployment scenario, recognizing the increased flexibility and experience gained in expanding IT operations to leverage Cloud based Infrastructure as a Service capability. The decision between hosting all Web services internally or expanding operations to include the Amazon deployment can be based on the results of the system architecture design balanced with other organization priorities. Both solution patterns will performance equally well in supporting user workflow requirements.

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