HYPERLOOP TUBE BREACH CONTINGENCY (HTBC)
SYSTEM PROJECT REPORT
Version 1.1
10/27/2015
ENG 2001 E
Prof. Regina Lee
Project Manager: Simin Lin
Budget Lead: Cameron Boyce
Technical Lead #1: Mohammad Afaneh
Technical Lead #2: Tai Dinh
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
2
Contents
1.0 Overview .......................................................................................................................................................... 3
1.1 Project Summary ......................................................................................................................................... 3
1.2 Purpose, Objectives, and Scope .................................................................................................................. 3
1.3 Assumptions and Constraints ...................................................................................................................... 4
1.4 Project Deliverables ..................................................................................................................................... 5
1.5 Schedule ...................................................................................................................................................... 5
1.6 Evolution of the Plan ................................................................................................................................... 5
2. References ......................................................................................................................................................... 6
3. Definitions.......................................................................................................................................................... 6
4. Project Work Plan .............................................................................................................................................. 6
4.1 Measure of Success and Future Plans ......................................................................................................... 6
4.2 Roles and Responsibilities ........................................................................................................................... 7
4.3 Project Charter ............................................................................................................................................ 8
4.4 Risk Management Plan ................................................................................................................................ 9
4.5 Communications & Reporting Plan ........................................................................................................... 10
4.6 Work Breakdown Structure ....................................................................................................................... 11
4.7 AON Diagram & Gantt Chart ..................................................................................................................... 12
4.8 Master Budget ........................................................................................................................................... 13
4.9 Task Responsibility .................................................................................................................................... 13
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
3
1.0 Overview
In 2013, entrepreneur Elon Musk proposed a Hyperloop transportation system to replace the high speed rail
project proposed in the state of California. The Hyperloop system is a transportation system in which a pod
(‘capsule’ used interchangeably) travels in a low pressure environment within a steel tube near the speed of
sound.
This is a proposal for the tube breach contingency response system for the Hyperloop transportation system. We define a breach in the Hyperloop system as a physical rupture of the tube resulting in an immediate
increase in pressure. The causes of such a breach may include the following:
Natural disaster (earthquake, hurricane, etc.)
External stimuli
Internal stimuli (i.e., electrical fire)
Pod-pod/pod-tube collision
The HTBC System must implement a response mechanism for pods greater than 37 km away from the breach
zone (defined as area of affected pressure loss) at time of breach in accordance with the requirements of
SpaceX Corporation.
1.1 Project Summary
This section of the HTBC Project presents an overview of project’s purpose, scope, and objectives. It also outlines our assumptions, constraints, project deliverables, and budget summary.
1.2 Purpose, Objectives, and Scope
The purpose of this proposal is to outline the processes that will be implemented throughout the evolution of
the project to ensure that its requirements are satisfied in alignment with those stipulated by design entities,
SpaceX Corporation and Tesla Motors. The HTBC project will also detail the activities, resources, schedules, and management strategies needed for maintaining the safety of passengers and any existing infrastructure
within the Hyperloop transportation system during a tube breach scenario.
Our principal design objectives are outlined below:
Ensure safety of all on-board passengers
Minimize or eliminate damage to Hyperloop components (pods/tube)
Maintain uninterrupted operation of unaffected pods
Minimize cost of system implementation
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
4
Table 1: Matrix of upper level objectives.
Safety Damage Operation Cost Score
Ensure safety of all on-board
passengers - 1 1 1 3
Minimize or eliminate damage to
Hyperloop components (pods/tube) 0 - 1 1 2
Maintain uninterrupted operation of
unaffected pods 0 0 - 0 0
Minimize cost of system
implementation 0 0 1 - 1
A “1” denotes that the objective in the row is perceived to be of greater importance that the objective in the
column. A “0” represents an objective in the row that is of lesser importance than the objective in the column.
The scope of the HTBC system is exclusively limited to tube breach scenarios which do not involve the following:
Pod malfunction (i.e., loss of power etc.)
Vehicles within 37 km of breach zone (defined as area of affected pressure loss) at time of breach
1.3 Assumptions and Constraints
These quantitative limitations serve to guide our design process toward the most suitable solution for our
target user.
Table 2: Quantitative Design Constraints
Objective Weight Measurement or Estimation Constraint
Ensure safety of all onboard
passengers, bring capsules to a
safe stop
10% Stopping distance calculated as the distance
separating capsules in km, D
D < 37 km
Maintain uninterrupted
operation of unaffected pods
20% Air pressure environment in tube to ensure pod
lift is sustained measured by air pressure
sensors in kPa, P
P < 5.6 kPa
Ensure safety of all onboard
passengers
35% G-force acting on passengers estimated by rate
of deceleration, G
G < 5g
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
5
Minimize or eliminate
damage to Hyperloop
components (pods/tube)
5% Measured distance between Hyperloop capsule
and enclosing tube to deploy braking
mechanism, X
X < 0.70 m
Minimize or eliminate
damage to Hyperloop
components (pods/tube)
5% Weight of pod braking mechanism, W W < 600 kg
Minimize cost of system
implementation
20% Estimated budget comprised from the sum of
component parts for entire fleet of Hyperloop
pods, B
B < $5.3 million
Minimize or eliminate
damage to Hyperloop
components (pods/tube)
5% Speed of pod at breaking mechanism
deployment, S
S < 160km/h
1.4 Project Deliverables
The HTBC team will produce a finalized concept design of the Hyperloop tube breach contingency system that
satisfies the design and budget specifications of the client, SpaceX Corporation. The design report will be
delivered to the client no later than October 27, 2015 and a final report/presentation will be given to ENG2001 audience on October 15, 2015.
1.5 Schedule
Table 3: HTBC project milestones and due dates:
Project Milestone Due date
Project start September 10, 2015
Project proposal September 22, 2015
Phase 1 completion September 29, 2015
Phase 2 completion October 06, 2015
Phase 3 completion October 13, 2015
Phase 4 completion and final presentation October 15, 2015
Project Final report October 27,2015
1.6 Evolution of the Plan
Any modifications to the HTBC project plan will be under version control. The updated document will be made available to all project members and interested stakeholders. The most recently modified version of the document will be made available on the HTBC project web page.
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
6
2. References
Musk, Elon. “Hyperloop Preliminary Design Study.” SpaceX Corporation, 12 Aug. 2013. 10 Sep. 2015.
3. Definitions HTBC - Hyperloop Tube Breach Contingency System
4. Project Work Plan
4.1 Measure of Success and Future Plans
The HTBC project is considered complete and successful when final modifications to the concept design of
the HTBC system have met all the design specifications, objectives, and constraints stipulated by SpaceX
Corporation. Passengers’ safety are to be ensured; damage to the Hyperloop system is to be minimized.
Additionally, the team will be successful when submission of the final report takes place within the target
period: on or prior to the final deadline of October 27, 2015.
As stated in the overview, the HTBC system is designed specifically for tube breach incidents caused by
natural disasters, external and internal stimuli, and pod/tube collision. However, there are other scenarios
where passengers’ safety could be comprised while onboard a Hyperloop capsule. In the future, Team
Hyperloop plans to develop a Loss of Power Contingency system for Hyperloop in the same manner it has
developed the HTBC. The new system will feature secondary power-generation devices and emergency cabin
pressurization system to ensure the passengers’ safety when the pod stops unintendedly.
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
7
4.2 Roles and Responsibilities
Table 4: Team member roles and responsibilities
Roles List of Responsibilities
Project Manager Help the team divide the tasks and resolve issues.
Liaison between clients and team members.
Allocate available resources to maximize group efficiency.
Ensure deliverables are completed by project deadline.
Motivate the team members to perform their tasks.
Budget Lead
Develop breakdown of component costs.
Appropriate budget for each component/subsystem
Communicate with Technical Leads to ensure subsystem design specifications are met within financial resources
Communicate with Project Manager to ensure the team is meeting
the budget guidelines.
Technical Lead #1 (Design)
Develop component designs to satisfy objectives/constraints of
project.
Plan and design subsystems of HTBC
Prioritize relative importance of components and communicate information with Budget Lead.
Communicate with Project Manager to ensure they are meeting
project guidelines.
Technical Lead #2
(Testing & Implementation)
Perform calculations on components to satisfy the objectives / constraints of project.
Communicate with Technical Lead#1 by providing numerical details required for implementation.
Perform simulation and software testing.
Communicate with Project Manager to ensure they are meeting
project guidelines.
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
8
4.3 Project Charter
Goals
Ensure safety of all on-board passengers Minimize or eliminate damage to Hyperloop components (Pod/Tube)
Maintain uninterrupted operation of unaffected pods
Scope Management Plan The scope of our project includes:
Outline the processes that will be implemented throughout the evolution of the project to ensure that its requirements are satisfied in alignment with those stipulated by design entity, SpaceX Corporation.
The HTBC project will also detail the activities, resources, schedules, and management strategies needed for maintaining the safety of passengers and any existing infrastructure within the Hyperloop transportation system during a tube breach scenario.
The scope of the HTBC system is exclusively limited to tube breach scenarios which do not involve the following:
Pod malfunction (i.e., loss of power etc.)
Vehicles within 37 km of breach zone (defined as area of affected pressure loss) at time of breach.
Key Stakeholders
Client SpaceX Corporation
Project manager Simin Lin
Project team members Cameron Boyce , Mohammad Afaneh, Tai Dinh
Project Milestones Start date of the project: September 10, 2015
Completion of technical design: September 27, 2015
Completion of tube breach response plan: October 6, 2015
Completion of system testing: October 26, 2015
End date of the project: October 27, 2015
Project Budget Estimated Budget of our project is $ 5.3 million.
Constraints, Assumptions, Risks and Dependencies
Constraints Stopping distance, Air pressure, G-force on passengers, Weight of the pod
Assumptions The project is based on the following assumption: The Hyperloop is working in the ideal condition.
Risks and Dependencies Pressure sensor malfunction, Natural disasters, Staff mismanagement
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
9
Approval Signatures
SpaceX corporation Simin Lin
Project Client Project Manager
4.4 Risk Management Plan
Team Hyperloop has identified five principal aspects of risk associated with this project: project staffing,
environment, definition, management and the nature of the project.
As a conceptual design for Hyperloop, the HTBC system design is not defined by the client, SpaceX
Corporation. What is defined are the specifications and associated constraints. Additionally, such a system has
yet to be designed and implemented elsewhere. Thus, Team Hyperloop, faces the same challenge associated
with any inaugural project such as a lack of research data and prior experience of team members. The
resources and support associated with the project are therefore limited, making it more risky than working on
a subsystem of a well-established system. Furthermore, as Hyperloop will be built in California, USA, Team Hyperloop must also comply with international laws regarding transportation safety.
Project staffing also poses significant risk. As it is only Mr. Lin’s second project as manager, he is
inexperienced at managing a team. While the team members have worked on a prior design projects in ENG
1102, they did not address aspects of formal project management.
Project environment, definition, and management constitute the remaining 40% of project risk. Team Hyperloop recognizes that this project lacks the support of a feasibility study, thus the basis of the project may be unreliable.
Figure 1: Project Risk Management category percentage breakdown.
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
10
Table 4: Risk Assessment Form
Risk event Likelihood Impact Detection Difficulty When
Breach Detection failure 4 5 3 airflow into the tube
Server failure 3 4 3 Software freeze
Decelerator 4 4 2 Pod in motion
Levitation failure 5 3 3 Pod in motion
Table 5: Risk Response Matrix
Risk Event Response Contingency Plan Trigger Who is responsible
Breach Detection
failure
Reduce Install backup
sensors
Not solved within
24h hours
Tai Dinh
Server failure Reduce Reinstall OS Still frozen after
one hour
Server controls
Decelerator Increase Install backup
decelerator
Not solved within
24h hours
Mohammad
Levitation failure Increase Install backup down
force airflow under
the pod
Not solved within
24h hours
Tai Dinh
4.5 Communications & Reporting Plan
The Communications & Reporting plan discloses the interactions between team members, project manager,
the client, and project stakeholders. Internally, the HTBC team follows a proposed meeting schedule so that
the progress of current tasks can be evaluated to ensure the team is on pace to produce project deliverables by milestone deadlines. Any modifications to the HTBC project plan are placed under version control. The
updated document will be made available to all project members and interested stakeholders. The most
recently modified version of the document will be made available on the HTBC project web page.
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
11
Table 4: Communications & Reporting Plan
When What Who Comments
September 10, 2015 Defining project and determining objectives Simin Completed
September 11, 2015 Assigning Tasks Simin Completed
September 14, 2015 Obtaining Quantitative Data Mohammad,Tai Completed
September 27, 2015 Designing Decelerator Cameron, Mohammad, Tai Completed
September 27, 2015 Designing Levitation System Cameron, Mohammad, Tai Completed
September 27, 2015 Designing Braking Mechanism Cameron, Mohammad, Tai Completed
October 6, 2015 Breach Detection Response Cameron, Mohammad, Tai Completed
October 14, 2015 Server Acquisition & Implementation Simin, Cameron, Mohammad, Tai Completed
October 26, 2015 System testing Cameron, Simin, Mohammad, Tai Completed
October 27, 2015 Project delivery and team reassignment Simin, Cameron Completed
4.6 Work Breakdown Structure
The project Work Breakdown Structure (WBS) describes the actual work to be done. The hierarchical structure
provides a framework for managing the project, and facilitates evaluation of the time, cost, resources and
technical performance at all levels. Our project is broken down into main deliverables: the final design
concept of the HTBC System and the final design report and presentation. Project subdeliverables include the
Pod, Tube, and Control subsystems of the Hyperloop transportation system. The lowest level subdeliverables
are the pressure sensor array, pressure control, sensor control of the Beach Detection Response subsystem. Work packages are identified at the bottom of the diagram.
Figure 2: WBS for HTBC Project
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
12
4.7 AON Diagram & Gantt Chart
From the WBS, project task dependencies were identified allowing for the construction of the AON diagram.
The critical path highlighted in figure 3 help and identifies project tasks with a slack of zero days. The final
output of the AON diagram is the Gantt chart (shown in figure 4).
Figure 3: AON Diagram and critical path identified by shaded path.
Figure 4: HTBC Project Gantt Chart
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
13
4.8 Master Budget
The budget for the HTBC Project was allocated to be $5.3 million USD as stipulated by the client, SpaceX
Corporation. The subdeliverable component costs were summed at each level of the budget diagram to ensure that proposed HTBC design was feasible and within proposed constraints.
Figure 3: Budget Diagram outlining component costs of all deliverables.
4.9 Task Responsibility
The task responsibility matrix is a visual representation of team members’ project task responsibilities. Tasks
were distributed equitably to ensure that the team functioned at a high-level of efficiency throughout all stages of the project.
HYPERLOOP TUBE BREACH CONTINGENCY SYSTEM (HTBC) PROJECT REPORT
10/27/2015
14
Table 5: Team member Responsibility Matrix
Resource Responsibility R - Primary Responsibility C - Contributes A - Advises
Sim
in L
in
Cam
ero
n B
oyc
e
Mo
ham
mad
Afa
neh
Tai
Din
h
Define Objectives R C C C
Assigning Tasks R A A A
Obtain Quantitative Data A C R
Decelerator
Decelerator Design A R A
Decelerator Testing A A R
Decelerator Budget R
Levitation
Levitation Design C R A
Levitation Testing A C A R
Levitation Budget R
Braking Mechanism
Braking Mechanism Design A R
Braking Mechanism Testing C A A R
Braking Mechanism Budget R A
Breach Detection Response
Pressure Sensor/Control Design C R C
Pressure Sensor/Control Testing A A R
Pressure Sensor/Control Budget C R
Server Acquisition & Implementation
Acquisition C R
Server Testing A C C R
Server Setup R C A
Testing A C R
Project Delivery & Team Re-assignment
R C