Capacity Planning Tool 36th Edition

Spring 2015 Capacity Planning Tool 36th Edition Capacity Planning Tool updates

This Capacity Planning Tool appendix shares CPT demonstrations used to identify system design requirements and model performance and scalability of proposed GIS operations.

The CPT demonstrations expand on the design concepts discussed in the primary System Design Strategies chapters, where hyperlinks to this appendix demonstrate how the CPT can be used to reinforce core system design concepts introduced in the primary documentation.

The CPT provides a framework for integrating business, data, applications, and technical architecture needs required to design, deploy, and manage successful enterprise GIS operations. This appendix can be used as a resource for learning how to use and apply the CPT in addressing your system architecture design needs.

Each section in this appendix includes a series of videos that demonstrate how the CPT can be used to collect business requirements, select the right software technology, identify the proper platform solution, and model Enterprise system performance and scalability.

This first section will introduce the Capacity Planning Tool and show how the CPT is used in the System Design Process.

=System Design Process=

The Capacity Planning Tool (CPT) simplifies business requirements data collection and automates system design analysis tasks associated with each phase of the development cycle. This section will introduce the CPT and show how the tools are used to complete a system architecture design.

The system design process starts with a business workflow loads analysis, identifying your GIS workflows and estimating the complexity of your business processes. 
 * Business workflow requirements are identified during a user needs assessment.
 * Project workflows are selected to identify appropriate workflow loads for the CPT design analysis.
 * User locations and network connectivity are configured for the CPT system requirements analysis.
 * The CPT network suitability analysis identifies required network bandwidth connectivity.
 * Platform architecture is selected to represent your data center hardware configuration.
 * Software is configured to represent your specific workflow installation.
 * The CPT completes the system architecture design analysis, identifies the required platform solution, and generates a projected average workflow performance summary.
 * Hardware/Software cost analysis supports the final design selection.

Workflow loads analysis
Figure A-1.2 shows the first steps in preparing for the design process. A clear understanding of your organization is critical in building successful GIS operations. Business planning starts with establishing an enterprise GIS vision, and building an implementation strategy that takes full advantage of your existing business architecture. Identifying the business workflows within your organization that can benefit from GIS information products is an essential ingredient for getting started on the right path to a successful system architecture design. Business needs (user requirements) establish the foundation for selecting a proper system design. Business requirements in the CPT are represented by project workflows.

The first step in completing a system architecture design is to select appropriate project workflows to represent your business requirements. Your selected project workflows identify the processing loads that must be supported by your selected hardware solution to satisfy your business needs. 

CPT User Needs summary: Business workflow requirements
The user needs template shown in Figure A-1.3.1 can be used to summarize a user needs analysis that identifies project workflows, user locations, and estimated user transaction loads required to satisfy peak business requirements. The template can be modified as required to support your specific business needs.

The user needs summary provides a snapshot of required business requirements for each deployment phase, establishing business requirements that must be supported by the system architecture design solution.
 * Identifies data center network connections and available bandwidth for each user location.
 * Shows business workflow patterns by location to be used in completing the system architecture design.
 * Identifies peak system loads (users or throughput) for each deployment phase (Year 1, Year 2).

The user needs summary should represent the current enterprise vision and goals for the GIS implementation. Building a GIS in multiple system deployment phases can reduce deployment risk and optimize operations as new technology is introduced over time. Business requirements should be reviewed and updated on a periodic basis, with planned reviews before each implementation phase. Business requirements and technology will change over time, and selecting the right technology can improve return on investment when implemented at the right time.

Management should be directly involved in reviewing and approving peak workflow requirements based on reasonable staffing levels and projected business needs, since these workflow load estimates contribute directly to the overall architecture selection and cost of the final system design.

"Best practice: Enterprise level user needs assessment should be completed and approved before starting the System Architecture Design. " 

CPT Calculator tab: Custom workflow loads analysis
The Calculator shown in Figure A-1.3 provides a group of drop-down lists for workflow software technology selection (software, map document, density, percent data cache, complexity, display resolution, output format). A proper software technology selection will generate appropriate GIS workflow performance targets (service times) for use in your system architecture design.

The CPT Calculator can also be used to complete the system architecture design for a selected workflow. There is an option (cell C30) available to select your workflow source (Calculator or Workflow tab).

"Warning: Capacity Planning Tool color scheme: Inputs to the Capacity Planning Tool are provided in the white cells (most inputs are drop-down lists). Formulas for the analysis are included in the colored cells. You should not change the colored formula cells."

"Note: CPT Calculator tab is discussed in more detail in the CPT section on Software performance." 

CPT Workflow tab: Workflow loads definition
Figure A-1.4 shows the CPT Workflow tab. A list of Standard Workflows is maintained in the Workflow tab for simple selection of the most common workflow performance targets. Custom workflows configured on the CPT Calculator tab include an output to the CPT Workflow tab (Calculator Workflow section).

The Project Workflows section is established at the top of the workflow list by including a copy of standard or custom workflows in your project workflow list – selection of your project workflows completes your workflow loads analysis. Once your workflow loads analysis is complete, your selected workflow performance targets will be available at the top of the workflow selection list for use in your system architecture design.

The composite workflow analysis section located at the bottom of the Workflow tab is used to calculate average service times for a use-case that combines two or more component workflows. A demonstration of a composite workflow loads analysis is included in the Greek Citizen Declaration case study at the end of Chapter 4.

"Note: The CPT Workflow tab is discussed in more detail in the CPT section on GIS software technology." 

System architecture design
Once you have identified your project workflows, you are ready to complete your system design. The CPT follows a standard system architecture design process as shown in Figure A-1.5. Each cycle of the system architecture design process includes the following steps:


 * Technical architecture strategy—High-level network diagram 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.

The system design process includes the user requirements analysis, network suitability assessment, platform architecture selection, software configuration (installation), and the Enterprise design solution. The CPT was designed to complete the analysis. Once the CPT is properly configured and business requirements are defined, the CPT will complete the system architecture design analysis and display the platform solution. 

CPT Design tab: User requirements 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. 

Once you identify your business workflows, you are ready to complete a user system loads analysis. The CPT Design tab includes a Requirements Analysis module where you can identify user locations and peak throughput loads.

Figure A-1.7 shows the CPT Design tab Requirements Analysis module. The gray rows represent the data center network connections (LAN, WAN, Internet) while the green rows represent remote site network connections. Workflows for WAN users are located under the data center LAN network. Remote user workflows are located below each remote site network, based on user work locations.

Peak concurrent users and workflow productivity establish system throughput loads that drive the system architecture design. These loads include network traffic that must travel between the user display location and the central data center. Location of the workflow users and how their locations are connected with the central data center can directly impact software technology selection.

"Warning: Capacity Planning Tool color scheme: Inputs to the Capacity Planning Tool are provided in the white cells (most inputs are drop-down lists). Formulas for the analysis are included in the colored cells. You should not change the formula cells."

"Note: An example of an Enterprise user requirements analysis was provided in Chapter 12: City of Rome." 

CPT Design tab: Network suitability analysis
Network suitability analysis—CPT Design completes the network suitability analysis and identifies any communication bottlenecks. Network bandwidth upgrades are identified and upgrades are entered to resolve identified network contention. 

Once you configure the CPT Design tab to reflect your user requirements and identify the network connections, the CPT completes a network suitability analysis. The CPT analysis evaluates network bandwidth and latency to ensure adequate capacity to accommodate peak traffic flow loads. You can then increase network bandwidth as required to accommodate peak traffic loads. Figure A-1.9 shows the business workflow, peak loads, and network bandwidth inputs needed to complete the network suitability analysis. 

Once the business requirements analysis is complete (user locations, peak workflow loads) available bandwidth for each network must be entered in column H. The CPT completes the network suitability analysis, and identifies associated design conflicts (user productivity and network traffic). Analysis results provide information needed to complete the network design. Figure A-1.10 shows the network suitability analysis results once the network upgrades are made.

Once bandwidth upgrades are made, the traffic flow and productivity conflicts are removed.

"Warning: Capacity Planning Tool color scheme: Inputs to the Capacity Planning Tool are provided in the white cells (most inputs are drop-down lists). Formulas for the analysis are included in the colored cells. You should not change the formula cells."

"Note: Network Suitability Analysis was discussed in Lesson 6: Network communications." 

CPT Design tab: Platform architecture selection
Platform architecture selection—CPT Design Platform tier is configured to represent the data center platform architecture structure. Identify platform tier nicknames, select platforms, and identify platform rollover settings.  Figure A-1.12 shows the CPT Design Platform Configuration module. The platform selection (column B) is normally configured first, and platform nicknames followed by a colon can be identified for each tier just above the platform selection in column B. You can also set a rollover setting in column H, telling the Capacity Planning Tool when to add new platforms.

Platform selection is a critical decision in any design process. The selected platform directly contributes to user display performance, platform capacity, and software licensing cost. A faster processor core (column F) improves user performance and reduces license cost. Higher capacity servers (column G) reduce the total number of server machines required to satisfy business requirements.

"Warning: Platform selection directly impacts overall system cost."

Once the platform names are set, you can complete the system install in the Software Configuration section.

"Note: CPT Design: Platform selection is discussed in more detail in Chapter 8: Platform performance." 

CPT Design tab: Software configuration
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. 

Figure A-1.14 shows the CPT Design Software Configuration module. Once you establish your platform architecture, you are ready to install the workflow software. Software install is defined in the Software Configuration section (columns J through R) for each user workflow.

Workflow software components you must install are identified by colored blocks in the software configuration section.


 * Client workflow software can be installed on any data center platform tier from a drop-down list selection (the drop-down list includes a Default value, as well as nicknames for each of the 10 platform tiers). The Default platform for each column is identified in row 5. You can install each software component individually on each workflow row, or install all rows on the default platform. This provides flexibility to install workflow software in any data center hardware configuration.
 * Data source selection for each workflow is identified in column R.

"Note: CPT Design software configuration patterns are discussed in more detail in the CPT product architecture section." 

CPT Design tab: Enterprise system design
Enterprise design solution—once configured, the CPT Design tab completes the system architecture design analysis and provides the platform solution.

The final system architecture design will represent the network and platform solution that satisfies your identified business requirements. The final hardware selection will directly impact workflow performance, user productivity, and overall system cost.

Hardware cost will vary greatly depending on available platform selection and procurement options. Hardware performance can directly impact software licensing costs. Hardware configuration strategy can impact both performance and cost. Hardware cost and system performance must both be considered to identify the optimum system architecture design. 

CPT HWPricing tab: Hardware procurement costs
Figure A-1.16.1 provides a hardware pricing lookup table for use with your final CPT Design analysis. Hardware pricing will vary based on the platform configuration and selected vendor procurement options. Platform performance and capacity contributes directly to both hardware and software procurement costs. A review of proper hardware vendor candidate platform configuration options are discussed in the following SDS Platform Performance sections.
 * Platform Performance.
 * 2014 Intel processor performance.
 * ArcGIS for Server platform selection
 * ArcGIS Platform sizing section.

Platform selection candidates can be included in the CPT and selected on the HWPricing tab to support an integrated HW/SW cost analysis for each CPT Design solution. Hardware cost will vary depending on the selected CPU configuration and platform memory. Platform memory recommendations will be generated in the CPT Design analysis, and the selected platform configuration must include sufficient memory to satisfy peak business loads identified during the design analysis.
 * Select platform processor configuration in column B.
 * Enter available vendor memory options for each platform in column C.
 * Enter vendor price for each platform configuration in column F.
 * VM pricing lookup table is included for virtual server host configurations.

The CPT Design tab includes a hardware/software cost analysis section for use with each design solution, which will use the HWPricing tab lookup table for appropriate pricing and configuration input.

<br style="clear: both" />

CPT Design tab: Enterprise system design
Figure A-1.16 shows the resulting Enterprise system design. Once you make your platform selections and install workflow software components (software configuration), the CPT will complete the platform sizing and show the required server configuration (number of platforms and peak utilization levels for each platform tier).

The Design tab provides a snapshot view of your user requirements and associated platform solution as a single integrated information product.


 * User workflow requirements show the user location, the peak throughput for each workflow (peak users or transactions per hour); the network bandwidth connecting each user site with the central data center; results of the network suitability analysis showing workflow traffic, site traffic, and network utilization; and the relative display response time for each workflow at each user location (Workflow performance summary).
 * The platform selection area shows your physical or virtual server configurations, along with a diagram of the final platform solution (number of platforms per tier and peak server utilization).

"Note: Chapter 12 provides a case study for the City of Rome, demonstrating how to use the CPT to complete an enterprise system architecture design." <br style="clear: both" />

CPT Design tab: Hardware/Software cost analysis
Figure A-1.16.3 shows the hardware/software (HW/SW) cost analysis included on the CPT Design tab below the platform selection. The HW/SW cost analysis generates system cost information based on the selected design solution and the information contained within the HWPricing tab.
 * Physical Hardware Configuration section
 * > Physical hardware configuration (platform configuration and memory) is selected in column B.
 * >>Hardware selections must be included on the HWPricing tab.
 * > Shows pricing for any physical platform tier included in the CPT Design tab solution in column C.
 * >>Default hardware memory requirements are included on the HWPricing tab.
 * > Shows software license cost (column H) when per core pricing is identified in column I (physical or virtual).


 * Virtual Hardware Configuration
 * > Physical host platform hardware configuration (platform configuration and memory) is selected in column B.
 * >>Host platforms must match assigned virtual platform tier.
 * >>Hardware selections must be included on the HWPricing tab.
 * > Shows pricing for any host platform tier included in the CPT Design tab solution in column C.
 * > VMware pricing (column C) is generated based on per chip cost identified on the HWPricing tab.
 * > Shows software license cost (column H) when per core pricing is identified in column I (based on host platform core).


 * Total solution shows final hardware and software pricing based on selected solution.

Note: Selected physical hardware configuration must match platform and minimum memory requirements. <br style="clear: both" />
 * Columns B and E show red if the hardware configuration does not match the platform tier selection.
 * Columns B and F show red if the hardware configuration does not satisfy minimum memory requirements.
 * Physical Hardware Configuration Max Memory Template can be used to reset hardware default selections

CPT Hardware tab: Platform performance
Platform performance metrics are pulled from the Hardware tab, shown in Figure A-1.17. The Hardware tab provides a list of available platform configurations each with the following information:
 * Platform processor
 * Number of cores
 * Cores per chip
 * Processor MHz
 * Vendor-published SPEC baseline benchmark value
 * SPEC baseline per-core value

Benchmark results are collected from the SPEC benchmark site for each vendor platform configuration. This platform performance information is used by the CPT to complete the system architecture design analysis.

"Note: CPT hardware tab and performance benchmarks is discussed in more detail in Lesson 8: Platform performance." <br style="clear: both" />

CPT Test tab: Performance validation
Figure A-1.18 identifies opportunities for measure performance compliance when deploying your GIS operations.

Measuring performance during the system build and deployment reduces implementation risk. System design is only the beginning of the process; then you need to build a system that performs within the system architecture design performance targets. If measured performance loads exceed planned budgets, adjustments can be made to workflow complexity during the build process to deliver services within initial performance targets.

The CPT Test tab was designed to help with the validation process, and includes several tools that can be used to translate performance measurements to equivalent workflow service times. <br style="clear: both" />

Figure A-1.19 shows the measured performance analysis tools available on the CPT Test tab.

There are four Test tools that you can use during system deployment.
 * Measured desktop map display rendering time is used to estimate deployed map service times (validate display complexity is within performance budgets during initial authoring of the map).
 * Measured map service render time is used to estimate map service times (check of map service performance during initial deployment).
 * Measured throughput and utilization is used to estimate map service times (this is the most accurate performance measure).
 * Peak users and productivity are used to estimate throughput. Throughput (peak users x productivity) and utilization are then used to estimate map service times.

'Best practice:
 * Evaluate performance compliance during initial prototype testing.
 * Validate system performance goals are met during initial production deployment.
 * Establish periodic performance validation milestones throughout production. '

"Note:Test tab is discussed in more detail in the CPT section on Performance validation" <br style="clear: both" />

Platform Capacity Calculator (Hardware tab)
Figure A-1.18 shows the CPT Platform Capacity Calculator. The Platform Capacity Calculator is located at the bottom of the CPT Hardware tab.

The Platform Capacity Calculator provides a peak throughput range for a list of selected Workflows, showing medium complexity output in blue and light complexity output in red. This simple tool answers many of the most important questions customers have when purchasing Esri software (What throughput can I expect from the selected hardware?).

The Platform Capacity Calculator is simple to use.
 * Platform selection is entered in the top white cell at left of the calculator (column A).
 * You can select whether you want the output in transactions per hour (TPH) or concurrent users (users) in cell C450.
 * You can identify whether you want results based on a physical server configuration, or for virtual server configurations deployed on the selected physical server.
 * Platform capacity is calculated for both light and medium complexity workflows, providing a performance range that applies for most server deployments.

Workflow candidates on the left of the chart can be modified to represent any workflow listed on the CPT workflow tab, including your project workflows. Simply slide the graphic to the side and the workflow selection cells are available directly behind the chart. The total number of workflow candidates can be increased or decreased to by expanding or contracting the workflow rows to satisfy your reporting needs. <br style="clear: both" />

CPT Capacity Planning videos
Chapter 1 Capacity Planning Video introduces the Capacity Planning Tool and provides an overview of the System Architecture Design process. The next section shows CPT software technology patterns discussed in Chapter 2: GIS Software Technology.

Previous Editions
Capacity Planning Tool 35th Edition Capacity Planning Tool 34th Edition Capacity Planning Tool 33rd Edition Capacity Planning Tool 32nd Edition Capacity Planning Tool 32nd Edition Capacity Planning Tool 31st Edition Capacity Planning Tool 30th Edition Capacity Planning Tool 29th Edition Capacity Planning Tool 28th Edition Capacity Planning Tool 27th Edition

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