Example 3: Large Enterprise Company; Static Allocation And Concurrency; Summary - HP Bc1500 - BladeSystem - Blade PC Supplementary Manual

Example 3: Large Enterprise Company

The business in this example has 15,000 full time employees. It is a US-based tax preparation firm
with thousands of retail offices throughout the United States. This firm adds an extra 5,000 temporary
employees from January thru April to assist with preparing customer's tax documents. All employees
are asked to avoid taking vacation or any other type of leave in the critical months of January thru
April. This corporation feels that 79% of their total employees can migrate to CCI due especially to its
very low break/fix field costs and because no customer's personal files are stored on local devices.
All blades are located in NA, and accessible and usable from anywhere in the world over the
corporate WAN.
Table 3. Blade calculation for large enterprise company
Parameter
Number of employees using CCI
Percentage of employees using CCI at work at any given
day (80% between May and December, 95% between
January through April, so use 95%)
Lower concurrency due to forced logoff time set to 1 hour,
but rare that computers are not in use for more than 30
minutes, ("50" only 1%)
1% delta added for peak planning (low percentage due
to already near maximum utilization rate)
Calculated MCU percentage rate
Number of blades needed
Number of blades ordered

Static Allocation and Concurrency

With a static allocation model of CCI, individual employees have a dedicated blade that they return
to every time they log on. This is comparable to having a reserved parking place in a parking lot – no
matter how many or few of the other parking spots are taken, one spot is designated for a particular
person with their name on it. This means that there will be a parking spot for every car, even if not
always filled. With the static version of CCI, there must be a blade for every end user whether they
are logged on or not. If the corporation plans to migrate 2,000 users to CCI in a static model, then
2,000 blade PCs are needed.
In the static model, HP recommends that customers add 1% to be designated as standby hardware in
case a blade PC fails, resulting in a calculated MCU of 101%. So in this example of a static
allocation, the total number of blades ordered and put into production should be 2,020.

Summary

The intent of this white paper was to provide information on how HP has concluded 70% maximum
concurrency as a baseline for CCI implementations, and include some general guidance and
information on how MCUs could be estimated for CCI implementations. Though some examples and
basic guidelines were presented here, every enterprise is different. CCI architects should work with
the customer's HP account team and HP Service to calculate the MCU, and consequently their
hardware needs for a CCI solution.
Value
15,000 active users
14,250 active users
14,108 active users
14,249 active users
95%
14,249 blades
14,260 blades
6