Operation
& Systems Support
Hardware
Ninjas
CIS 162 Summer 2011
Module
3
Dong-uh Choi
Pam Bolton
Pavel Panteleyev
Vlad Vasilenko
Zoran Knezevic
Table
of Contents
Project Scenario –
Module 3..................................................... 3-4
Hardware Ninja
Project Standards............................................... 5
Feasibility Study........................................................................ 6-9
Profit & Loss Statement..................................................... 10
Work Breakdown
Structure (WBS) Outline................................. 11
Project Manager ..................................................... Vlad Tab
Operations
new site plan
OSS
new site plan
Old
OSS site plan
Layout.................................................................... Zoran Tab
Hardware – Identify existing.................................... Pam
Tab
Scope of existing hardware
Move existing hardware
New Equipment................................................. Dong-uh Tab
Deploy.................................................................... Pavel Tab
Introduction: Module Three
Fly By Night
Inc. is growing rapidly. Because of this
growth, two departments - the Operations department and your department,
Operations Systems & Support (herein “OSS”), have both outgrown their
spaces.
The CEO, Maryanna VanDhyke, has given her
approval to authorize the Operations department to move to the 5th
floor of the building which was recently vacated by another company. She has also authorized OSS to move into
Operations old space which is double the size OSS has now. The old OSS space will, of course, be used
for storage of old office equipment. Because
both departments report to the CEO, she has charged OSS with complete
responsibility for the move. She wants
the move to happen simultaneously so that no other groups grab the vacant
space.
OSS has been
notified that the move will begin in 6 weeks and, because of your expertise in
moving computer equipment, that OSS is in charge of planning and executing the
move and responsible for successfully completing this move without snags by the
deadline. Here are the requirements:
v
Get
the new floor ready to accept 35 workstations and 3 printers
v
All
workstations’ PCs and printers must be on the network
v
Operations
has 30 PCs and needs 5 new PCs are to be purchased and set-up by the deadline
v
All
30 existing PCs need to be upgraded from Windows ME to Windows XP and the 5 new
PCs must also use Windows XP
v
All
35 PCs will need to have their Internet Explorer service packs upgraded.
v
All
35 PCs will now need to have Microsoft Project loaded since everyone now wants
to do project management (except for this move!).
v
Operations
has 5 new people
starting on Tuesday after the move.
v
OSS
has hired 4 new people to start on Tuesday after the move.
v
OSS
may order the new PCs,
v
The
3 printers are all different (1 color laser jet, 1 b&w
daisy wheel, 1 linefeed printer)
v
OSS
has 4 existing workstations with PCs and will buy 4 more PCs so that 4 more
workstations will be added to OSS. OSS
has 2 printers.
v
The
move is to take place at the end of week 6 starting on a Friday. It is also a 3-day weekend, so the CIO wants
OSS to complete the move for everyone in 4 days! On Friday, the Operations staff will pack the
stuff in their drawers into boxes and move them to the location indicated for
them. The PIB will do a walk-through
with the CEO at 8 a.m. on Tuesday morning to show him how successfully “he
planned and executed his plan” for this move.
v
OSS
has complete power to:
o
Contact
and oversee facilities to:
§
Get
the new Operations space ready (but the specifications/ floor plan must come
from OSS in agreement with Operations management).
§
Get
the new OSS space ready (providing the specifications/ floor plan).
§
Perform
the moving tasks (desks and cabinets) for both Operations and OSS, but each
group must be supervised by an OSS person.
However, moving PCs and Printers to the correct user’s location and
hooking them up must be done by OSS.
§
Perform
the phone line change-overs. By the way, everyone wants to keep their same
phone extension.
v
Hmmm,
who’s going to order those new workstations for the new Operations and new OSS
people?
v
Hmmm,
will all the new people in Operations and OSS have phones to use on Tuesday?
v
Because
OSS is a group of planners and doers, everything will be documented so that
absolutely nothing goes wrong with this move.
They are so extraordinary that they even have a contingency plan for
some of the things that could possibly go wrong.
HARDWARE
NINJAS PROJECT STANDARDS
All documents will be created in Word 2010, Visio 2010, and Excel 2010 in company approved format with the company logo and the watermark.
OSS Team
functions
- Supervising the move: Pam and Dong-uh
- Hardware analysts: Pam and Zoran
- Deploy upgrades: Pavel
- Project manager: Vladimir
- Facility/Maintenance: Vladimir
- Layout plan: Zoran
- Order new equipment: Dong-uh
Any changes to the documentation must be approved by the Project Manager Pavel Panteleyev and the documents version table updated accordingly. OSS will meet every Monday and Wednesday until project is complete.
FEASIBILITY REPORT
Department: Operations Systems & Support
Product or Process: Install 35 workstations and 3 printers on 5th floor
Install
9 workstations in old Operations area
Create
storage area in old OSS area
Document Owner: Operations & Systems Support Staff
Project or Organization Role: Developer / Technician
|
Version |
Date |
Author |
Change Description |
|
1 |
07/18/11 |
Pamela Bolton |
Created Document |
|
2 |
07/25/11 |
Pamela Bolton |
Revisions |
|
3 |
08/01/11 |
Pamela Bolton |
Final Revision |
Project Feasibility Report Audit Log
|
Record Name |
Responsibility |
Approval Authority |
Distribution |
|
Version 1 |
Pamela Bolton |
Vladimir Vasilenko |
OSS |
|
Version 2 |
Pamela Bolton |
Vladimir Vasilenko |
OSS |
|
Version 3 |
Pamela Bolton |
Vladimir Vasilenko |
OSS |
Project Feasibility Report Purpose
A Project Feasibility Report is a controlling document that incorporates the goals, strategies, and methods for performing a project. The Project Feasibility Report describes all aspects of the risk identification, estimation, evaluation, and control processes. The purpose of developing such a plan is to determine the approach for cost-effectively performing the project.
Stakeholder Roles and Responsibilities
|
Role |
Project Feasibility Responsibilities |
Assignment |
|
Project Manager |
The Project Manager is responsible for the Project Feasibility Report being implemented and for reporting to the CEO of Fly By Night Inc. |
Vladimir Vasilenko |
|
Moving supervisors |
Is responsible for insuring move feasibility and organizing labor. |
Pamela Bolton
|
Project Feasibility Report Process and Activities
|
Risk Management Activity |
Risk Management Task Description |
Ownership (Participants) |
|
Ordering |
Will order all materials and equipment needed to perform the move in a safe and effective manor |
Dong-Uh Choi |
|
Moving & Installation |
Reports to Moving Supervisor for all necessary details. Carries out all roles assigned by Moving Supervisor in a quick, efficient, and safe manner. |
Pamela Bolton Zoran Knezevic Pavel Panteleyev Dong-Uh Choi |
|
Analyst |
Responsibilities include proper material requisitions to include hardware and cable requirements. |
Dong-Uh Choi |
|
Wire Schematic/Office Floor Plan |
Detailed plot of office layout for wires, furniture and personnel |
Zoran Knezevic |
|
Installing Cables |
Will install all necessary cables as deemed necessary by the Wire Schematic/Office Floor Plan |
Facilities |
|
Hardware Installation |
Will ensure
all hardware components are installed as per the Wire Schematic/Office Floor
Plans. This includes all workstations, telephones, and printers |
Zoran Knezevic Pavel Panteleyev
|
|
Network Connections |
Will ensure all hardware is properly hooked up to the company network and all connections are in proper working order |
Zoran Knezevic Pavel Panteleyev |
Risk Assessment and Management Table
|
Risk Type |
Description of Risk & Steps to Minimize Risk |
Risk Chance |
Risk Impact |
Risk Priority |
Risk Owner |
||||
|
Personnel Injuries |
Injury to team members due to negligence or improper training Pamela will hold a short training class with team members to instruct on proper lifting and moving techniques |
Medium |
High |
High |
Vladimir Vasilenko |
||||
|
Damage to Equipment |
Unnecessary and unforeseen damage to equipment could cause more monetary loss than estimated Proper lifting and moving techniques in training class |
Low |
Low |
Low |
Vladimir Vasilenko |
||||
|
Network Vulnerability |
Company network open during installation of new computers All contractors will be escorted while in working area |
Low |
High |
Medium |
Vladimir Vasilenko |
||||
|
|
|
|
|
|
|||||
Economic Feasibility (see Profit & Loss Statement
page 10)
|
|
||||||||
|
Moving equipment |
·
Operations to 5th floor ·
OSS to old Operations location ·
Create storage area |
||||||||
|
New furniture & equipment |
See RFP, Dong-uh Choi |
||||||||
|
Other |
·
Welcome balloons ·
Food |
||||||||
|
Training needs |
·
Outsourcing Windows XP ·
In-house training as indicated |
||||||||
Schedule Feasibility
|
Activity |
Completion Date / Process |
Ownership (Participants) |
|
Wire Schematic/Office Floor Plan |
July 18 Schematic will be done and approved so ordering can be completed by July 20 |
Zoran Knezevic Pavel Panteleyev |
|
Ordering |
July 20 All necessary components and parts will be ordered by this date so we can ensure everything is present at the time of install |
Dong-Uh Choi |
|
Installing Cables |
September 2 All cables (power, Ethernet, telephone, coax) will be installed by this date so as to not hamper the move in schedule |
Facilities Pamela Bolton coordinator |
|
Moving & Installation
|
Commence on September 3, completed no later than September 5. Rooms and equipment will be ready for move on this date. All equipment will be moved and installed. All scheduled events will be completed and running by the end of business on September 5. |
Pamela Bolton - Supervisor School Team - Moving Coworkers - Moving Zoran Knezevic - Installation Pavel Panteleyev - Installation |
|
Walk-through |
September 6, 8am – Operations September 6, 10am – OSS site |
CEO, Maryanna
Vanhdyke Project Manager |
Risk Management Plan Approvals
Prepared by:
Zoran Knezevic
For Project Manager, Vlad Vasilenko
Approved by:
Maryanna VanDhyke
Project Sponsor
Maryanna VanDhyke CEO
Executive Sponsor
|
FLY-BY-NIGHT, INC. |
||
|
For the January 1, 2010 ending
December 31, 2010 |
||
|
|
||
|
|
||
|
Total Income |
|
28,987,000,000 |
|
Operating Expenses |
||
|
Sales and Marketing
Expenses |
|
2,000,000,000 |
|
General and Adminstrative |
||
|
Wages and salaries |
|
8,000,000,000 |
|
Computer Hardware |
|
2,000,000 |
|
Office equipment |
|
1,000,000 |
|
Administrative (Rent, telephone,
utilities, insurance |
|
10,000,000 |
|
Training (outsource) |
|
5,000,000 |
|
Total General and Adminstrative Expenses |
|
8,018,000,000 |
|
Total Operating Expenses |
|
18,036,000,000 |
|
Net Profit |
|
10,951,000,000 |
Work Breakdown Structure Outline
|
Role |
Tasks July 24 to September 5 (3,4,5) |
Comments |
|
Project manager Vlad |
Facility/Maintenance New Staff Requirements |
|
|
Zoran |
Layout |
|
|
Pam/Zoran |
Hardware – Identify existing |
|
|
Pam/Dong-uh |
Move existing hardware, desks, cabinets |
|
|
Dong-uh |
Order new equipment/RFP |
|
|
Pavel |
Deploy upgrades |
|