Please open the Capacity Management Analysis PDF file. It contains the performance data of main systems by MobileMusic. You are asked to create a graph showing the utilization of the main file server cluster CPU at peak times. Please also provide list of recommendations to mitigate the potential incidents.

Hints:

1. The graph should be easy to understand, appropriately labeled, etc

2. F&P and Billing services are run on the mainframe.

3. Is the OS CPU usage relevant here?

4. Typical recommendations could be: adding additional capacity, split jobs, etc. but make sure they are appropriate in this context.

tSMF-USA Academic Committee: Curriculum Subcommittee Capacity Management (Demand Management) based on the MobileMusic (MM) Case Study To prepare for the upcoming consolidation of the regional datacenters, MobileMusic (MM) is working to understand the overall usage of the current technologies and to ensure there is enough capacity during and after the datacenter consolidation. Below are performance data from the main systems. 1. Using the data below, create a graph showing the utilization of the main file server cluster CPU at peak times. Note that the manufacturer of the large file servers suggested that anything in excess of 75% (225% for the three clustered servers) will create performance issues. The operating system uses approximately 10% of the CPU. 2. ldentify when Incidents are likely to occur. 3. Provide recommendations regarding actions to be taken to resolve any performance Incidents. Service ld Service Name: 0001 SUB MGT (SM) Service ld: Service Name: Service Type: CUST MGT DAILY Batch Update System Daily 24hr 06:00-10:00: 105% 10:00-12:00: 60% 12:00-14:00: 70% 14:00-16:00: 90% 16:00-18:00:105% 18:00-20:00: 95% 20:00-06:00: 40% Run Frequency: Run Time: Average Processor Utilization Run Time: Average Processor Utilization 20:00 22:00 90% Service id: Service Name: Service Type Run Frequency: Run Time: Average Processor Utilization CUST MGT ARCHIVE 22:00 24:00 85% Service ld Service Name: Service T Run Frequency: Run Time: Service ld: Service Name: Service Type: 0007 FP Online Internal Financial System Daily Mon-Fri 08:00 18:00 08:00-10:00:55% 10:00-12:00: 80% 12:00-14:00: 35% 14:00-16:00: 75% 16:00-18:00: 40% SUB MGT DAILY Batch Update 20:00 22:00 Run F Run Time: Average Processor Utilization Service ld Service Name: ervice Type: Run Frequency: Run Time: 0003 SUB MGT ARCHIVE Back-up Job 22:00 24:00 85% Service ld: Service Name: Service Type Run Frequency: Run Time: 0008 FP DAILY Daily Batch Update Daily Mon-Fri 19:00 22:00 55% Average Processor Utilization Service ld Service Name: Service Type: Run Frequency: Run Time: Average Processor Utilization 0004 CUST MGT (CM) Customer Database Average Processor Utilization 06:00-10:00: 105% 10:00-12:00: 12:00-14:00: 70% 14:00-16:00:90% 16:00-18:00:105% 18:00-20:00: 95% 20:00-06:00: 40% Service id: Service Name: Service T Run Frequency: Run Time: Average Processor Utilization 0009 FP ARCHIVE Back-up Jab Daily Mon-Fri 22:00 24:00 45% 60% Service ld: Service Type: Third-party logistics Average Processor Utilization 70% Average Processor Utilization 08:00-10:00: 05% 10:00-11:00: 15% 11:00-12:00: 10% 12:00-14:00: 05% Run Frequency: 16:00-18:00: 05% Average Processor Utilization 08:00-10:00: 15% Servic 12:00-14:00:15% 14:00-16:00: 20% Service Type: Run Frequency: Average Processor Utilization 25% requency Service Type Roun Frequency: Average Processor Utilization 15% requency Daily Mon-Fri WEEKLY Outcome: There are two expected outcomes: a graph of the performance and a list of recommended actions to mitigate any potential incident tSMF-USA Academic Committee: Curriculum Subcommittee Capacity Management (Demand Management) based on the MobileMusic (MM) Case Study To prepare for the upcoming consolidation of the regional datacenters, MobileMusic (MM) is working to understand the overall usage of the current technologies and to ensure there is enough capacity during and after the datacenter consolidation. Below are performance data from the main systems. 1. Using the data below, create a graph showing the utilization of the main file server cluster CPU at peak times. Note that the manufacturer of the large file servers suggested that anything in excess of 75% (225% for the three clustered servers) will create performance issues. The operating system uses approximately 10% of the CPU. 2. ldentify when Incidents are likely to occur. 3. Provide recommendations regarding actions to be taken to resolve any performance Incidents. Service ld Service Name: 0001 SUB MGT (SM) Service ld: Service Name: Service Type: CUST MGT DAILY Batch Update System Daily 24hr 06:00-10:00: 105% 10:00-12:00: 60% 12:00-14:00: 70% 14:00-16:00: 90% 16:00-18:00:105% 18:00-20:00: 95% 20:00-06:00: 40% Run Frequency: Run Time: Average Processor Utilization Run Time: Average Processor Utilization 20:00 22:00 90% Service id: Service Name: Service Type Run Frequency: Run Time: Average Processor Utilization CUST MGT ARCHIVE 22:00 24:00 85% Service ld Service Name: Service T Run Frequency: Run Time: Service ld: Service Name: Service Type: 0007 FP Online Internal Financial System Daily Mon-Fri 08:00 18:00 08:00-10:00:55% 10:00-12:00: 80% 12:00-14:00: 35% 14:00-16:00: 75% 16:00-18:00: 40% SUB MGT DAILY Batch Update 20:00 22:00 Run F Run Time: Average Processor Utilization Service ld Service Name: ervice Type: Run Frequency: Run Time: 0003 SUB MGT ARCHIVE Back-up Job 22:00 24:00 85% Service ld: Service Name: Service Type Run Frequency: Run Time: 0008 FP DAILY Daily Batch Update Daily Mon-Fri 19:00 22:00 55% Average Processor Utilization Service ld Service Name: Service Type: Run Frequency: Run Time: Average Processor Utilization 0004 CUST MGT (CM) Customer Database Average Processor Utilization 06:00-10:00: 105% 10:00-12:00: 12:00-14:00: 70% 14:00-16:00:90% 16:00-18:00:105% 18:00-20:00: 95% 20:00-06:00: 40% Service id: Service Name: Service T Run Frequency: Run Time: Average Processor Utilization 0009 FP ARCHIVE Back-up Jab Daily Mon-Fri 22:00 24:00 45% 60% Service ld: Service Type: Third-party logistics Average Processor Utilization 70% Average Processor Utilization 08:00-10:00: 05% 10:00-11:00: 15% 11:00-12:00: 10% 12:00-14:00: 05% Run Frequency: 16:00-18:00: 05% Average Processor Utilization 08:00-10:00: 15% Servic 12:00-14:00:15% 14:00-16:00: 20% Service Type: Run Frequency: Average Processor Utilization 25% requency Service Type Roun Frequency: Average Processor Utilization 15% requency Daily Mon-Fri WEEKLY Outcome: There are two expected outcomes: a graph of the performance and a list of recommended actions to mitigate any potential incident