Read The Caseadvantage Energy Technology Data Center Migrati

Read The Caseadvantage Energy Technology Data Center Migration Par

Read The Case" Advantage Energy Technology Data Center Migration - Part A" at the end of the chapter 6 and response to the following questions: 1. Generate a priority matrix for AET's system move. 2. Develop a WBS for Brian's project. Include duration (days) and predecessors 3.Using a project planning tool, generate a network diagram for this project.

Note: Base your plan on the following guidelines: eight-hour days, five-day weeks except for when Brian moves the network components over a weekend, no holiday breaks, March 1, 2010, is the project start date. Ordering Ventilation System, New Racks, and Power Supplies/Cables takes only one actual day of work. The remaining days are the time necessary for the vendors to fill and ship the order to Brian. So use Finish to Start lags here. Assume that five days after the start of the Renovation of the Data Center that the raised floor will be ready for inspection (a Start-to-Start lag).

Paper For Above instruction

Read The Caseadvantage Energy Technology Data Center Migration Par

Analysis of Data Center Migration: Priority Matrix, WBS, and Network Diagram

Introduction

The migration of data center operations is a complex project requiring meticulous planning and coordination. This paper analyzes the case of Advantage Energy Technology's (AET) data center migration, focusing on generating a priority matrix, developing a Work Breakdown Structure (WBS), and constructing a network diagram to facilitate effective project management. Through this, we aim to optimize resource allocation, adhere to timelines, and ensure a smooth transition with minimal operational disruption.

Priority Matrix for AET's System Move

The first step in the project planning process involves identifying critical activities and their importance relative to project success. The priority matrix helps distinguish tasks requiring immediate attention versus those that can be deferred without impacting overall project delivery.

The primary activities include procurement of hardware (ventilation system, racks, power supplies/cables), renovation work, inspection, and actual migration activities. Tasks like ordering equipment are high priority, since delays would cause significant downstream delays, especially considering vendor fill and shipping times. The renovation and inspection phases are also critical to ensure the data center environment is prepared for migration.

Based on urgency and impact, activities are categorized as follows:

- High Priority: Ordering of equipment (ventilation, racks, power supplies), renovation start, network component movement

- Medium Priority: Inspection of raised floor, vendor fill and shipping, network testing

- Low Priority: Documentation updates, staff training post-migration

This matrix ensures focus on tasks that directly influence project timelines and system availability, enabling proactive management of risks tied to delays or resource shortages.

Work Breakdown Structure (WBS) for Brian's Project

The WBS decomposes the project into manageable components, establishing tasks, durations, and dependencies.

The key components include:

1. Project Initiation

- 1.1 Define scope (1 day, predecessor: none)

- 1.2 Procure ventilation system (1 day, predecessor: 1.1)

- 1.3 Procure racks (1 day, predecessor: 1.1)

- 1.4 Procure power supplies/cables (1 day, predecessor: 1.1)

2. Vendor Fills and Shipments

- 2.1 Ventilation system (shipment timing, starting after procurement)

- 2.2 Racks (shipment timing)

- 2.3 Power supplies/cables (shipment timing)

3. Data Center Renovation

- 3.1 Prepare site for renovation (duration: 5 days, starting after project initiation)

- 3.2 Renovation work (duration: 10 days, predecessor: 3.1)

- 3.3 Inspection of raised floor (start-to-start lag: 5 days after renovation start)

4. Equipment Installation

- 4.1 Install ventilation system (2 days, predecessor: shipment completion)

- 4.2 Install racks (2 days, predecessor: shipment completion)

- 4.3 Install power supplies/cables (2 days, predecessor: shipment completion)

5. Network Migration

- 5.1 Move network components (3 days, predecessor: installation completion)

6. Testing and Validation

- 6.1 System testing (3 days, predecessor: network migration completion)

- 6.2 Final validation and go-live (1 day, predecessor: testing completion)

The total project duration, considering all dependencies and logical sequences, approximates 40 working days excluding weekends, aligned with the start date of March 1, 2010.

Network Diagram for the Project

Utilizing project planning software such as Microsoft Project allows for the visualization of task dependencies and critical paths. The network diagram visually represents tasks as nodes, linked by dependencies such as Finish-to-Start (FS), Start-to-Start (SS), and Finish-to-Finish (FF) relationships, with lag periods applied.

The initial nodes include procurement and renovation activities. Supplies procurement feeds into shipment delays, which in turn influence installation tasks. The renovation process, constrained by the 5-day SS lag to inspection readiness, overlaps with procurement shipping times. Equipment installation follows the completion of shipments, leading into migration activities, with testing completing the process.

The resulting network illustrates the project’s critical path, primarily driven by procurement, renovation, and installation sequences, highlighting activities that could delay the entire project if postponed.

Conclusion

Effective project management for AET's data center migration hinges on meticulous planning of task prioritization, structured work breakdown, and visual representation of dependencies through a network diagram. The priority matrix ensures focus on critical tasks, the WBS facilitates resource allocation and scheduling, and the network diagram provides a comprehensive view of task sequences and dependencies. Implementing these tools helps mitigate risks, manage timelines, and ensure a successful migration with minimal disruption to operations.

References

  1. Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. John Wiley & Sons.
  2. PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide). Project Management Institute.
  3. Snyder, C. S. (2009). Project Management for Dummies. Wiley Publishing.
  4. Lientz, B., & Rea, K. (2009). Project Management for the Unofficial Project Manager. Elsevier.
  5. Meredith, J. R., & Mantel, S. J. (2014). Project Management: A Managerial Approach. Wiley.
  6. Leach, L. P. (1999). Critical Chain Project Management. Artech House.
  7. Chapman, C., & Ward, S. (2011). Project Risk Management: Approach, Methods and Tools. Wiley.
  8. Heldman, K. (2018). Project Management JumpStart. Wiley.
  9. Burke, R. (2013). Project Management: Planning and Control Techniques. Wiley.
  10. Wysocki, R. K. (2014). Effective Project Management. Wiley.