Sample Project Proposal - Dynamic Server

Dynamic Server System
Project Proposal
Point of Contact Name [Email]

Team Members' List
TABLE OF CONTENTS
LETTER OF TRANSMITTAL ........................................................................................................................ ii

EXECUTIVE SUMMARY ..............................................................................................................................iii
1.0 INTRODUCTION..................................................................................................................................... 1
1.1 Problem ............................................................................................................................................... 1
1.2 Solution ............................................................................................................................................... 1
1.3 Project Mission .................................................................................................................................... 1
2.0 PURPOSE & OBJECTIVES .................................................................................................................... 2
2.1 Purpose ............................................................................................................................................... 2
2.2 Objectives ........................................................................................................................................... 2
2.2.1 Corporation .................................................................................................................................. 2
2.2.2 Consumer ..................................................................................................................................... 2
3.0 TECHNICAL OVERVIEW ....................................................................................................................... 3
4.0 IMPLEMENTATION PLAN ...................................................................................................................... 5
4.1 WBS .................................................................................................................................................... 5
4.2 Schedule ............................................................................................................................................. 5
4.3 Responsibility Chart ............................................................................................................................ 5
4.4 Stakeholders ....................................................................................................................................... 6
5.0 EXECUTION PLAN ................................................................................................................................. 7
5.1 Project Monitoring ............................................................................................................................... 7
5.2 Project Control .................................................................................................................................... 8
5.3 Project Auditing ................................................................................................................................... 8
5.4 Project Termination ............................................................................................................................. 9
6.0 RISK ASSESSMENT MANAGEMENT PLAN ....................................................................................... 10
7.0 FINANCIAL PLAN WITH BUDGET ....................................................................................................... 12
7.1 High-Level Summary......................................................................................................................... 12
7.1 Resource Allocation .......................................................................................................................... 12
8.0 TEAM CREDENTIALS .......................................................................................................................... 13
APPENDICES ............................................................................................................................................. 14
Appendix A: Work Break-down Structure ............................................................................................... 14
Appendix B: Project Schedule................................................................................................................. 16
Appendix C: RACI Matrix ........................................................................................................................ 17
Appendix D: Budget Justification ............................................................................................................ 20
Appendix E: Resource Allocation Plan ................................................................................................... 22
Project Proposal – Team Two
LETTER OF TRANSMITTAL
Date
Dr. ….
Northeastern Graduate School of Engineering
130 Snell Engineering
360 Huntington Avenue
Boston, MA 02115
Dear Dr. ….,
Please find enclosed submittal of a project proposal for the development of the current data storage system. The new
designed Dynamic Server System will improve network performance that adjusts the power usage and satisfies the
consumer needs.
This proposal first presents a data consumption problem and a creative idea to solve this problem. The technical
overview elucidates the feasibility of the dynamic server system to balance energy usage with consumer
requirements. The following implementation plan and execution plan illustrate the schedule and allocation of
various resources. The preliminary risk analysis and budget justification are also set up to ensure a successful
management of this project.
We hope that you find this proposal to be effective and persuasive. We greatly appreciate your instruction and
constructive comments throughout the course in developing this project and in molding us as potential future project
managers.
Sincerely,
Team Members
ii
EXECUTIVE SUMMARY
The team at Northeastern University Servers (NUS) has developed a product that will enhance the
way people consume data. The team at NUS plans to provide an innovative technical solution to
overcome the data bandwidth limitation problem seen in today’s digital universe. The proposal is to
design a Dynamic Server System that adjusts power usage based on user demand to save energy
during non-peak times.
The Dynamic Server System is going to be superior to any product on the market currently because
NUS is going to identify the characteristics and capabilities of current systems to ensure they are not
only matched, but also surpassed. In addition, a critical objective of this design is to develop a reliable
product. It doesn’t matter how many bells and whistles a system has if it is not up and running all day,
every day. Some key benefits of the Dynamic Server System are it will drastically decrease the
operational costs of running a data center as well as enable the ability to make data more affordable
for the consumer.
These ambitious goals will be accomplished by leveraging the state of the art hardware available
including the Broadwell CPUs by Intel and 12G SSDs. NUS even takes the small details into
consideration such as ensuring the mechanical structure of the server is designed to direct maximum
airflow over the hottest components. The greatest value can be seen in the software that is going to be
developed in house. This software is going to allow the Dynamic Server System to communicate with
individual drives, fans, and CPUs. This is important because it gives the server many different
components to turn off when the system senses there is a load data demand. In addition, the Dynamic
Server System will be designed to operate in high heat data center environments. This is beneficial
because it means the server does not have to cool itself as vigorously, thereby operating the fans less
often and at lower RPMs.
The implementation plan for this project is broken into four different phases: Initiation, Planning,
Execution, and Closing. Initiation and Planning are expected to take a combined three months with
the primary goal of defining objectives and roles, obtaining requirements, and identifying procurement
strategy. The majority of work is expected to take place during the execution phase where the team
will develop, test, and deploy the Dynamic Server System. Lastly, Closing will be used to monitor
performance and close out the project.
Project responsibilities are divided up into Product Management, Financial Management, Program
Management, and Resource Management with at least one team member assigned to each position.
This ensures all major tasks are accounted for and will be executed on time.
The total proposed budget for a project of this scale is expected to be $745,959.06. This budget
includes labor, material, miscellaneous, and a 7% contingency to ensure we can rapidly handle any
difficulties or changes throughout the process.
In closing, not only will the Dynamic Server System save our customers money, it will allow our
customers to gain market share. Market share can be gained by being able to lower the cost of
services provided to consumers because the operating costs will now be greatly reduced by using the
Dynamic Server System designed and implemented by NUS.
iii
1.0 INTRODUCTION
1.1 Problem
Every second of everyday people are on their mobile devices streaming videos, music, news, gaming,
checking their emails, doing their banking, and checking their fantasy teams. In the time it took to read the
beginning of this proposal, over 100,000 tweets were sent, 204 million emails, and $272,000 was spent on
web shopping1. What do all of these people have in common? They are using the Internet. With more
people connected to the Internet than ever before we are also expanding the “digital universe” that we live
in. Each day we are creating and consuming more data than the day before.
“From 2005 to 2020, the digital universe will grow by a factor of 300, from 130 exabytes
to 40,000 exabytes, or 40 trillion gigabytes (more than 5,200 gigabytes for every man, woman,
and child in 2020). From now until 2020, the digital universe will about double every two years.” 2
This study conducted in 2012 by IDC analysts, summarizes the rise in data creation and consumption we
are witnessing. The problem we face is that data is all around us and everyone wants to consume this data
at lower cost and faster than ever before. Expecting to increase data use to new extremes while also paying
low costs is a demanding task that will require our company to decrease our costs as well.
1.2 Solution
The solution to this problem is to create a data storage system that is able to dynamically adjust to demand.
This would include switching from high power for fast streaming during peak hours into a low power
conservation state during idle time and off peak hours. At the conclusion of the project we will have a
product that we can sell to a variety of industries that are struggling to deal with the increased bandwidth
demands of its users. These industries are primarily telecommunications and Internet service providers. We
are going to succeed in tackling this problem where others have failed by working with an interdisciplinary
team of engineers and project managers. The engineers on our team understand what it takes to make a
professional grade product. Our project managers have had experience in similar technical areas so they
know the details of the issue we are trying to resolve. The potential payoff for such a solution is immense.
The IDC’s Worldwide Server Tracker estimates that the worldwide server revenue for 2014 was $50.2
billion dollars. Our product could improve that number, making us an attractive option for a massive
industry.
1.3 Project Mission

The mission of this project is to grow our customer’s capabilities of handling the increasing demand in
network storage and realize the advantages for both the consumer (performance when needed) and the
corporation (low power state = saving money and decreased carbon footprint).
1
How much Data is consumed every minute? (www.zdnet.com/article/how-much-data-is-consumed-every-minute/)
2
The Digital Universe in 2020h (see http://www.emc.com/collateral/analyst-reports/idc-the-digital-universe-in-2020.pdf)
1
2.0 PURPOSE & OBJECTIVES

2.1 Purpose
The purpose of this project is to provide an innovative technical solution to overcome the data bandwidth
limitation problem seen in today’s digital universe. The technology developed will allow consumers to
have a non-stop, fast and satisfactory data utilization experience. By employing green technology our
product will have the ability to adjust the power usage and respond to consumer needs. The technology also
allows corporations to remain competitive as demand grows into the future as a result of the reduced energy
costs.
2.2 Objectives
One of the main objectives of this project is to research the general use of energy in network storage as well
as a dynamic capability to alternate between usage amounts. A second objective is to research our current
customer population in order to identify their usage characteristics and obtain their inputs on how to
improve the current system. The ultimate objective of this project is to design a dynamic server system that
improves upon the current system and meets customer and demand requirements.
The objectives of this project can be divided in corporate and consumer objectives as listed below:
2.2.1 Corporation
 Implement 20% energy saving server
 Create a system that doesn’t lose performance with added energy savings feature
 Dominate the Telecom industry and become the market leader
 Sell our product with a 15% profit margin
2.2.2 Consumer
 Make data more affordable to users
 Minimize delay from system request to system deliver
 Improve performance during high demand time periods
 Guarantee customer satisfaction
2
3.0 TECHNICAL OVERVIEW

The technical overview provides an in depth understanding of how the Dynamic Server System will be able
to save energy, while also providing higher power based on bandwidth usage. The project is broken down
into the major components that will provide a higher level of detail in order to convey the feasibility of this
project.
Hardware (Electrical)
The hardware design for the product is going to leverage the latest technology available. It is more
beneficial to go with 2.5” SSDs over the conventional 3.5” HDDs because of the performance benefits and
smaller form factor. In addition, the Dynamic Server System is going to use the exotic PTFE PCB material
that will provide decreased voltage drop across the boards. This is a benefit because reducing voltage drop
means the server will have slightly smaller power supplies. The smaller power supplies will then help keep
customers thermal footprint lower and thereby help them save power. For CPUs, the Haswell generation by
Intel will provide us the performance we need.
Mechanical Structure
The server structure design must allow for maximum airflow so that the system can be cooled at maximum
efficiency. The design solves this problem by having many slots in the front panel and fans in the back.
This design allows the server to pull air from the front of the system over the components and drives that
are stored in the middle. The air is then expelled through the back of the system as hot air. In addition to
cooling concerns it is necessary to make sure that the system is rigid enough to hold its shape, even when
empty of drives and compute blades. To accomplish the necessary rigidity, the design includes a grid of
vertical and horizontal supports to brace the heavy outer walls.
Cooling
Cooling this design should be easier than most considering it is not expected to be running at full power
100% of the time. Based on project research, it is best if the server system can operate at full power for 10
hours of continuous high demand. To do this, the cooling system will use three 15mm dual fans to pull cool
air over all components. To ensure critical electronics do not over heat, a heat sink will be secured to
components such as the CPU, Board Management Controller (BMC), and Point of Loads (POLs). These
components will consume the most current and therefore and most likely to overheat.
Software
The software required for this project will be the backbone of the system. Application programming
interface (API) will be developed in house that will allow the client to contact individual drives, fans, and
CPU nodes. This API will be leveraged by using the Intelligent Platform Management Interface protocol.
IPMI is an industry standard that has existing reference codes capable of being expanded upon. Applying
standard protocols will help keep the project on schedule as a result of less custom development.
Protocols
There are a multitude of storage protocols that the industry currently uses including Serial-Attached-SCSI
(SAS), Ethernet, Infiniband, and SATA. To keep costs down and due to the recent technological
improvements, utilizing the Ethernet has determined to be most effective. The Ethernet protocol has
recently made improvements that allow for speeds of up to 100 Gigabits per second. Another advantage to
using Ethernet is that it allows for easy installation since many corporations already use high speed
Ethernet as the backbone to their network.
Server Environment
Another advantage that the Dynamic Server System will have is the ability to operate in high heat
environments. Recently, there has been a large push for allowing servers and storage to run at higher
temperatures to reduce cooling costs of large data centers. These standards are maintained by the American
Society of Heating, Refrigerating, and Air-conditioning Engineers (ASHRAE), which set different level of
operating conditions that specify how hot data centers can run on a normal basis. On average, most data
3
centers have an operating temperature between 68 -72 degrees Fahrenheit, some even as cold as 55
degrees. Based on research that has been done by industry leaders, servers are actually much more durable
than previously thought. By enabling the Dynamic Server System to operate in these harsher environments
customers can expect to save 24% on energy bills. This does not even account for the additional energy
saving features implemented in the server.
4
4.0 IMPLEMENTATION PLAN

4.1 WBS
The Work Breakdown Structure (WBS) defines the complete set of activities to successfully develop the
Dynamic Server System. The activities in the WBS are hierarchically organized based on the 8/80 rule
where the majority of the tasks will take over eight hours, but no more than eighty hours.
The four major phases highlighted in the WBS are: project initiation, project planning, project execution
and project closing.
1. Project Initiation Phase

Involves all activities associated with project concept, ultimate goal and project objectives
definition. Additionally, leadership role assignments are evaluated based on project team
members’ experience.
2. Project Planning Phase

Includes all activities needed to identify both customer, and product requirements, in addition this
phase involves supply chain identification, component procurement, and risk management
planning.
3. Project Execution Phase

Focuses on all activities associated with solution development, including hardware, software
design and simulations. This phase is also responsible for conducting testing, training,
deployment, and marketing of the system.
4. Project Closing Phase

Involves all activities associated with management and control to monitor the solution
performance and resolve any technical problem previously presented. Final report is generated to
conclude the project.
Refer to Appendix A for the complete Work Breakdown Structure (WBS).
4.2 Schedule
In order to ensure the successful completion of this project, a schedule was developed as a tool to monitor
and control project activities. Activity durations were held to two weeks or less based on previous
experiences in similar projects.
The schedule is housed in Microsoft Project. This allows the project manager to update task durations
throughout the project and depict accurate progress using the Gantt chart tool. The baseline project Gantt
chart can be found in Appendix B.
4.3 Responsibility Chart

The responsibility chart organizes the roles of each stakeholder as related to each task in the work
breakdown structure. The chart, known as a RACI matrix, takes the work breakdown structure format and
specifies the responsible, accountable, consulted, and informed parties on each of the tasks. See Appendix
C for the matrix. Determining the responsibility of different parties is imperative to visualize how different
positions are associated with the project deliverables. The RACI Matrix also ensures that one person does
not shoulder too much responsibility and determines who is responsible for each task that has been
outlined.
5
4.4 Stakeholders
The following list is a short overview of those interested parties that are mentioned throughout this report.
Project Team
 Financial Managers
Team Member Name
 Product Managers
Team Member Name
 Program Manager
Team Member Name
 Resource Managers
Team Member Name
See section 8.0 for team members’ credentials.
Principal Engineers
The team of Principal Engineers in charge of hardware and software development is composed of:
 Electrical Engineers
 Mechanical Engineers
 Software Engineers
Marketing Team
The Marketing team is composed of:
 Marketing and Sales Specialists
 Financial Analysts
Vendors and Manufacturers

Below is the list of Vendors and Manufacturers:
 Emco Industrial Plastics
 The Platt Brothers and Company
 Johnson Controls, Inc.
 Foxconn
 Jabil
Customer
Our target customer is Verizon Wireless, the largest U.S. Wireless communications service provider.
Inspection Team
……
6
5.0 EXECUTION PLAN

5.1 Project Monitoring
The purpose of project monitoring is to guarantee the successful completion of the Dynamic Server System
on time and within budget, by identifying risks and implementing solutions in a timely fashion to ensure
the quality of the product and to ensure customer satisfaction. Based on the Work Breakdown Structure
and RACI Matrix, a report system will be designed to monitor the following key factors and indicators
throughout the life of the project.
Costs: All costs associated with the project will be monitored, including project funding, budgeting and
expenditures. Estimated costs, bills, receipts, and payable amounts to employees, vendors and
manufacturers will be appropriately tracked in the reporting system.
Schedules: The schedules will be monitored to track the status of the project and to guarantee that the
deadline of the project is met accordingly. The Work Breakdown Structure was used as the foundation to
develop the schedule of activities, the team will monitor the schedules on a weekly basis, and some of the
indicators that will be monitored include:
 Start and end dates for each activity, these dates will be compared to the expected durations
previously defined
 Dates when contracts are signed
 Dates when manufacturing products are received
 Dates when hardware and software designs are completed
 Dates when product tests are implemented and finished
Staff: Based on the RACI Matrix, the project will monitor staff acquisition, staff contract agreements, role
or responsibility, number of staff required, staff training, staff availability and length of time each role will
be required to complete their respective functions.
Quality: Internal procedures and standards will be created to ensure proper coordination between project
teams and to guarantee a high quality Dynamic Server System. The following documents and standards
will be implemented: Manufacturing design standard, software coding standard, and testing procedure
standard.
Additionally, lessons learned will be documented and quality audits will be implemented quarterly and
monthly.
Changes: It is expected that during the lifecycle of the project, changes would need to be implemented, for
this reason we will implement a procedure to properly track and handle the project changes.
Changes to the project will incur changes in the scope, budget, or schedule. Our tracking and monitoring
procedure will record change requests, generate change impact assessment, coordinate change approval,
and monitor change implementation.
7
5.2 Project Control

Throughout the project, feedback control will be used. There will be biweekly meetings in which each
management sector will report out on the various factors being monitored. The table below summarizes
which management sector is responsible for each key factor.
Key Factor Sector Responsible

Cost Financial Management
Schedule Program Management
Staff Resource Management
Quality & Changes Product Management
The meetings act as a sensor to the ongoing functions of the project. If any sector of the project veers out of
control, the management team discusses corrective actions that will be implemented by the responsible
sector.
5.3 Project Auditing

Project audits are done regularly to make sure the project is on schedule, within the given scope and cost
thereby making sure the clients are kept up to date and satisfied. Audits are usually conducted to go over
the development of the project by assessing both, the team and the individual performance based on
contribution and positive development. Audits are conducted with the completion of a milestone, with the
intention of trying to achieve the three phases that an audit usually consists of namely research preparation,
in depth research and report development. In this project, as mentioned above, audits are done after the
completion of a phase. The following are the audits that this project will be following:
Technical Overview
During the designing phase, all technical decisions will be reviewed together. Technical audits will
comprise of:
 Listing different requirements

 Designing cooling system
 Designing Mechanical Structure
 Designing the Software
 Product Assemble
 Testing of system
Project Status Overview

Project status might change as the initial project cost and schedule might differ from the costs that we
might we actually incur. The status update will include necessary changes to the budget and schedule to
include the proposed scope changes to aid the project team. Status updates are given out during:
 Completion of design of different systems
 Completion of integrated design
 Test plan completion
 Completion of in house testing
 Post deployment of Dynamic Server system
 Post Pilot consumer deployment
 Completion of training
 Completion of Project
8
Final Audit
A final audit is conducted to make sure the following points have been taken into consideration:
 Budget has been followed strictly
 Schedule has been followed and milestones have been met
 Technical overview/requirements has been completed
 Customer satisfaction
 Quality of deliverables has been met
 Cooperation amongst team members
 Contribution and professionalism of team members
 Accuracy of end result and successful deployment of system
5.4 Project Termination

As the Dynamic Server System is designed, manufactured, and distributed, the team will ensure
that the scope, budget, and schedule stay on track as much as possible. As the project enters termination, a
major question will be if all of the planning for the projects life was accurate. That means did the product
get developed to the scope requirements and not only was it on budget, but did it sell to the expectations
that were profitable? In the end was this project worth doing to the company goals and if not what would
have changed that result?
Going forward in future projects, information on project successes and failures is very important for a
company’s survival in a market. If the project is successful, this will be a proposal to emulate as NUS
progresses in the market, while if there are areas of failure the company will know where to focus attention
in the future.
9
6.0 RISK ASSESSMENT MANAGEMENT PLAN
6.1 Identification and Analysis of Risks

As with any forefront in innovation, there will be a certain level of risk associated with several facets
of this endeavor. It is essential that the team attempts to identify these risks so that a plan can be put
in place to develop a response. After identifying the risks, a matrix was created to compare each
risk’s probability to its level of impact on a scale ranging from low to high. An identifier was then
associated with each step on this scale as a basis for brainstorming contingency policies in each of
these situations.
Internal Risks:
 Lack of funding
 Loss of essential stakeholders
 Off schedule deliverables
 Insufficient training of pilot users
 Unforeseeable circumstances amongst management
 Failure to innovate to meet customer demands
 Lack of worker competencies
 Over budget
Design Risks:
 Competitor technical breakthrough
 Malfunctioning hardware
 Design not meeting appropriate specifications
 Insufficient data produced by Pilot
 Quality requirements not being met
 Product is difficult to adapt to different platforms
 Government imposed constraints on product
Manufacturing Risks:
 Collapse in supply chain
 Fail to meet facility requirements
 Noncompliance with safety standards
 Poor tooling quality
 Privacy concerns related to security breach
 Uncooperative client
 Conflict due to U.S. manufacturing costs
10
6.2 Risk Management Plan

After identifying an exhaustive list of potential risks, the level of each risk was characterized using the
Borda method. A management team will be in place to take corrective action against each of the above
risks. Potential hazards that are of low impact and of low probability can be accepted, as the limited
resources available can be better utilized elsewhere. Any risk of either medium impact or medium
probability, will be monitored to ensure the probability of occurrence does not increase. Risks in the next
stage above will be avoided as best as possible. At the control level, these factors will be a constant focus
by the management team, with regular updates on how they are being handled and what the contingencies
will be. At the highest stage, “reject,” the risk team will be tasked mitigate the risk at all feasible cost, and
prevent further damage from occurring to the project.
6.3 Continuous Risk Assessment

The process of identifying and regulating risks will be a continuous effort and this process will need to be
repeated several times throughout the project in order to foresee potential issues and maintain control over
the project. NUS intends to remain on time and on budget by their ability to be prepared and involved with
the work being done.
11
7.0 FINANCIAL PLAN WITH BUDGET

7.1 High-Level Summary
This project is focused on designing a dynamic server system that improves upon the current system and
meets customer and demand requirements. However, this is not possible without a financial component. A
budget must be established and tracked to ensure a successful management of this project. Below is the
project’s Budget Summary, refer to Appendix D for the complete budget justification.
Budget Summary
Resources Total Cost
Labor $682,848.00
Materials & Equipment $11,485.00
Miscellaneous $2,825.00
7% Contingency $48,801.06
Total $745,959.06
Table 7-1 Budget Summary
2% 0% 7%
Labor
Materials & Equipment
Miscellaneous
7% Contingency
91%
Table 7-2 Budget Summary Chart
7.1 Resource Allocation

The Resource Allocation Plan takes into account the overhead costs of our company including labor,
machinery, and general and administrative costs that will be used during the project. Factoring in time
requirements and rates, it develops an overall Contract Value to our organization. We will use testing and
research and development machinery in the development and simulations of our product. We have also
accounted for a 7% contingency cost to provide leeway for unexpected difficulties that will arise
throughout the project. View Appendix E for a more detailed view.
12
8.0 TEAM CREDENTIALS

Here is an Example of what you can include in the Team Credentials section for each team
member:
Sam Smith
Sam is a graduate student pursuing Engineering Management at Northeastern University.
Prior to this, he worked in XYZ Consulting Services as an Assistant Software Engineer,
pursuing both testing and developing. He has a background in Electronics Engineering with
internships successfully completed in areas related to Software efficiency and development.
Apart from core technical skills, he has served in various student chapters, which has given
him an upper hand in leadership and efficiency in working as a team.
13
APPENDICES
Appendix A: Work Break-down Structure
ID Task
DYNAMIC SERVER SYSTEM
1 1.0 Project Initiation Phase
2 1.1 Hold Project Kickoff Meeting
3 1.1.1 Define objectives, ultimate goal and assign leadership roles
4 2.0 Project Planning Phase
5 2.1 Define Requirements
6 2.1.1 Customer Requirements
7 2.1.1.1 Interview customers, determine capability, and validate needs
8 2.1.2 Product Requirements
9 2.1.2.1 Electrical Requirements
10 2.1.2.1.1 Determine storage type, PCB Material, and CPU to use
11 2.1.2.2 Mechanical Requirements
12 2.1.2.2.1 Investigate material and how to distribute weight
13 2.1.2.3 Software Requirements
14 2.1.2.3.1 Investigate server components to shut down, and monitor temperature of drives and CPU
15 2.2 Supply Chain and Component Procurement Financial Evaluation
16 2.2.1 Search multiple vendors for vital components
17 2.2.2 Select most cost efficient manufacturer
18 2.2.3 Schedule lead times on all parts and assembly
19 2.3 Risk Management
20 2.3.1 Develop risk management plan
21 3.0 Project Execution Phase
22 3.1 Develop Dynamic Server System
23 3.1.1 Design Cooling System
24 3.1.1.1 Simulate cooling of system
25 3.1.1.2 Implement to best case simulations
26 3.1.2 Design Electrical System
27 3.1.2.1 Simulate electrical load on system
29 3.1.3 Design Mechanical Structure
30 3.1.3.1 Simulate structural integrity
32 3.1.4 Design Software
33 3.1.4.1 Simulate Software on Virtual Machines
34 3.1.4.2 Implement software on real hardware
35 3.1.5 Build Developed System
36 3.1.5.1 Send specifications to manufacturer to spin PCBs and perform product assembly
37 3.2 Test Dynamic Server System
14
38 3.2.1 Develop test plan

39 3.2.2 Conduct In-House Testing
40 3.2.2.1 Validate system meets all required specifications
41 3.2.2.2 Perform corrective action if needed
42 3.2.2.3 Conduct retest
43 3.3 Deployment of Dynamic Server System
44 3.3.1 Conduct Pilot Consumer Deployment
45 3.3.1.1 Implement pilot test and validate results
46 3.3.1.2 Perform corrective action if needed
47 3.3.1.3 Conduct retest
48 3.4 Training
49 3.4.1 Develop training material for sales department
50 3.4.2 Conduct training
51 3.5 Develop Marketing Plan
52 3.5.1 Performance evaluation, reliability and economic analysis
53 4.0 Project Closing Phase
54 4.1 Management and Control
55 4.1.1 Monitor customer acceptance
56 4.1.2 Monitor performance
57 4.1.3 Resolve technical problems
58 4.1.4 Hold project status meetings
59 4.2 Audit Procurement
60 4.2.1 Close out vendor and manufacturer contracts
61 4.3 Final Report
15
Appendix B: Project Schedule
16
Appendix C: RACI Matrix

Project Team Members
(Financial Management)
(Financial Management)
(Resource Management)
(Resource Management)
(Program Management)
(Product Management)
(Product Management)
Principal Engineers
Team Member 1
Team Member 3
Team Member 4
Team Member 5
Team Member 6
Team Member 2
Team Member 7
Professor
ID Task
Dynamic Server System
1 1.0 Project Initiation Phase
2 1.1 Hold Project Kickoff Meeting
1.1.1 Define objectives, ultimate goal
3 R R R R R R R I
and assign leadership roles
4 2.0 Project Planning Phase
6 2.1.1 Customer Requirements
2.1.1.1 Interview customers, determine
7 R R C C C R,A R,A
capability, and validate needs
8 2.1.2 Product Requirements
9 2.1.2.1 Electrical Requirements
2.1.2.1.1 Determine storage
10 R,A R,A C C I R
type, PCB Material, and CPU to use
11 2.1.2.2 Mechanical Requirements
2.1.2.2.1 Investigate
12 R,A C C I R
material and how to distribute weight
13 2.1.2.3 Software Requirements
2.1.2.3.1 Investigate server
14 components to shut down, and monitor R,A R,A I R
temperature of drives and CPU
2.2 Supply Chain and Component
15
Procurement Financial Evaluation
2.2.1 Search multiple vendors for vital
16 I I R,A R,A
components
17
2.2.2 Select most cost efficient

17 R,A R,A I C C
manufacturer
2.2.3 Schedule lead times on all parts and
18 C C C C R,A I
assembly
19 2.3 Risk Management
20 2.3.1 Develop risk management plan C C C C R C C A
21 3.0 Project Execution Phase
23 3.1.1 Design Cooling System
24 3.1.1.1 Simulate cooling of system R,A R,A
3.1.1.2 Implement to best case
25 R R A
simulations
26 3.1.2 Design Electrical System
3.1.2.1 Simulate electrical load on
27 R,A R,A
system
28 R R A
simulations
29 3.1.3 Design Mechanical Structure
30 3.1.3.1 Simulate structural integrity R,A R,A
31 R R A
simulations
32 3.1.4 Design Software
3.1.4.1 Simulate Software on Virtual
33 R,A R,A
Machines
3.1.4.2 Implement software on
34 R R A
real hardware
35 3.1.5 Build Developed System
3.1.5.1 Send specifications to
36 manufacturer to spin PCBs and perform A A I R R
product assembly
38 3.2.1 Develop test plan C C C C R C C
39 3.2.2 Conduct In-House Testing
3.2.2.1 Validate system meets all
40 R,A R,A I
required specifications
18
3.2.2.2 Perform corrective action if

41 R,A R,A I
needed
42 3.2.2.3 Conduct retest R R A
3.3 Deployment of Dynamic Server
43
System
3.3.1 Conduct Pilot Consumer
44
Deployment
3.3.1.1 Implement pilot test and validate
45 I I I I A R R
results
3.3.1.2 Perform corrective action if
46 R R A
needed
47 3.3.1.3 Conduct retest A R R
48 3.4 Training
3.4.1 Develop training material for sales
49 R,A
department
50 3.4.2 Conduct training A R R
51 3.5 Develop Marketing Plan
3.5.1 Performance evaluation, reliability
52 R,A I
and economic analysis
53 4.0 Project Closing Phase
55 4.1.1 Monitor customer acceptance I I A R,A R,A
56 4.1.2 Monitor performance R R I I A
57 4.1.3 Resolve technical problems R R I I A R
58 4.1.4 Hold project status meetings C C C C R,A C C
59 4.2 Audit Procurement
4.2.1 Close out vendor and manufacturer
60 R,A R,A A
contracts
61 4.3 Final Report R R R R R R R
R Responsible
A Accountable
C Consult
I Inform
19
Appendix D: Budget Justification

Project Name: Dynamic Server System
Total Budget $697,158.00
Estimated Start time: December 14th, 2015
Resources
Labor Materials& Equipment Task total
ID Task description
Number Miscellaneous cost
Working Hourly Estimated Unit Estimated
of Quantity
hours rate cost price cost
people
1 1 Project Initiation Phase
2 1.1 Hold Project Kickoff Meeting 7 8 $80.00 $4,480.00 3 $60.00 $180.00 $4,660.00
Phase total cost $4,660.00
4 2 Project Planning Phase
6 2.1.1 Customer Requirements 3 40 $53.00 $6,360.00 1 $1,250.00 $1,250.00 $125.00 $7,735.00
8 2.1.2 Product Requirements 1 $1,250.00 $1,250.00 $1,250.00
9 2.1.2.1 Electrical Requirements 5 80 $64.00 $25,600.00 $25,600.00
11 2.1.2.2 Mechanical Requirements 5 80 $64.00 $25,600.00 $25,600.00
13 2.1.2.3 Software Requirements 5 80 $64.00 $25,600.00 $25,600.00
2.2 Supply Chain and Component Procurement
15
Financial Evaluation
2.2.1 Search multiple vendors for vital
16 3 24 $59.00 $4,248.00 $250.00 $4,498.00
components
17 2.2.2 Select most cost efficient manufacturer 3 24 $59.00 $4,248.00 $4,248.00
2.2.3 Schedule lead times on all parts and
18 3 16 $59.00 $2,832.00 $2,832.00
assembly
19 2.3 Risk Management 5 40 $74.00 $14,800.00 $14,800.00
21 3 Project Execution Phase
23 3.1.1 Design Cooling System 4 240 $52.00 $49,920.00 1 $1,540.00 $1,540.00 $10.00 $51,470.00
20
26 3.1.2 Design Electrical System 4 240 $55.00 $52,800.00 20 $80.00 $1,600.00 $35.00 $54,435.00
29 3.1.3 Design Mechanical Structure 4 240 $53.00 $50,880.00 1 $2,245.00 $2,245.00 $53,125.00
32 3.1.4 Design Software 4 240 $74.00 $71,040.00 1 $300.00 $300.00 $35.00 $71,375.00
35 3.1.5 Build Developed System 6 40 $56.00 $13,440.00 1 $150.00 $150.00 $13,590.00
38 3.2.1 Develop test plan 6 80 $67.00 $32,160.00 $32,160.00
39 3.2.2 Conduct in-house testing 3 120 $64.00 $23,040.00 $23,040.00
43 3.3 Deployment of Dynamic Server System
44 3.3.1 Conduct Pilot Consumer Deployment 5 400 $65.00 $130,000.00 $130,000.00
48 3.4 Training
3.4.1 Develop training material for sales
49 3 80 $53.00 $12,720.00 10 $1.00 $10.00 $12,730.00
department
50 3.4.2 Conduct training 3 160 $68.00 $32,640.00 3 $60.00 $180.00 $32,820.00
51 3.5 Develop Marketing Plan 6 80 $67.00 $32,160.00 $1,750.00 $33,910.00
53 4 Project Closing Phase
55 4.1.1 Monitor customer acceptance 3 80 $47.00 $11,280.00 1 $1,300.00 $1,300.00 $200.00 $12,780.00
56 4.1.2 Monitor performance 3 80 $47.00 $11,280.00 1 $1,300.00 $1,300.00 $420.00 $13,000.00
57 4.1.3 Resolve technical problems 2 80 $68.00 $10,880.00 $10,880.00
58 4.1.4 Hold project status meetings 7 6 $80.00 $3,360.00 3 $60.00 $180.00 $3,540.00
59 4.2 Audit Procurement 5 40 $77.00 $15,400.00 $15,400.00
61 4.3 Final Report 6 40 $67.00 $16,080.00 $16,080.00
Materials&
Labor total cost $682,848.00 $11,485.00 $2,825.00 $697,158.00
Equipment total cost
7% Contingency $48,801.06
Total cost $745,959.06
21
Appendix E: Resource Allocation Plan

Client Verizon
Project Dynamic Server System
Budget Hours 9,165
Contract Value $ 682,848
Project Start Date 1/1/2016
Resource Type Company Role Effort (Hours) Rate/Hour % Allocation

Team Member 1 Labor NUS Resource Manager 755 $ 80.00 100%
Team Member 2 Labor NUS Resource Manager 755 $ 80.00 100%
Team Member 3 Labor NUS Product Manager 1076 $ 80.00 100%
Team Member 4 Labor NUS Program Manager 1159 $ 80.00 100%
Team Member 5 Labor NUS Financial Manager 612 $ 80.00 100%
Team Member 6 Labor NUS Product Manager 1076 $ 80.00 100%
Team Member 7 Labor NUS Financial Manager 612 $ 80.00 100%
Principal Engineers Labor NUS Hardware Development 494 $ 120.00 20%
Associate Engineers Labor NUS Engineer 1145 $ 40.00 100%
Interviewees Labor Verizon Usage Inputs 40 $ 25.00 100%
Lab Accessories Material Stryker Design - -
Testing Equipment Material Techtronics Design/Reliability - -
Design Materials Material Stryker Design - -
Pilot Consumers Labor Verizon Testing 402 $ 25.00 100%
General & Administrative Material N/A General 1039 $ 80.00 10%
EAC (hours) Contingency Total (Hours)

7,683 7% 9,165
**Resource Allocation used for planning purposes only as a general guideline of labor distribution
22

Sample Project Proposal - Dynamic Server

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Sample Project Proposal - Dynamic Server

Hochgeladen von

Copyright:

Verfügbare Formate

Dynamic Server System

Point of Contact Name [Email]

LETTER OF TRANSMITTAL ........................................................................................................................ ii

Dear Dr. ….,

1.3 Project Mission

2.0 PURPOSE & OBJECTIVES

3.0 TECHNICAL OVERVIEW

4.0 IMPLEMENTATION PLAN

1. Project Initiation Phase

2. Project Planning Phase

3. Project Execution Phase

4. Project Closing Phase

4.3 Responsibility Chart

See section 8.0 for team members’ credentials.

Vendors and Manufacturers

5.0 EXECUTION PLAN

5.2 Project Control

Key Factor Sector Responsible

5.3 Project Auditing

 Listing different requirements

Project Status Overview

5.4 Project Termination

6.0 RISK ASSESSMENT MANAGEMENT PLAN

6.1 Identification and Analysis of Risks

6.2 Risk Management Plan

6.3 Continuous Risk Assessment

7.0 FINANCIAL PLAN WITH BUDGET

Table 7-2 Budget Summary Chart

7.1 Resource Allocation

8.0 TEAM CREDENTIALS

38 3.2.1 Develop test plan

Appendix B: Project Schedule

Appendix C: RACI Matrix

2.2.2 Select most cost efficient

3.2.2.2 Perform corrective action if

Appendix D: Budget Justification

Appendix E: Resource Allocation Plan

Resource Type Company Role Effort (Hours) Rate/Hour % Allocation

EAC (hours) Contingency Total (Hours)

Das könnte Ihnen auch gefallen