Fall 2015 MicroBiped WBS – Team

/in , , /by

WORK BREAKDOWN STRUCTURE 
(Team Members Schedule)

By Paul Oo (Project Manager)
Approved by Paul Oo (Project Manager)
Approved by Railly Mateo (Systems Engineer)

Table 1 – Project Manager

Operation Duration Start Finish Resource Name
Project μBiPed 162 days 8/31/15 12/10/15 Paul Oo
Project Management 155 days 9/10/15 12/10/15 Paul Oo
Mission Objective 21 days 9/10/15 10/1/15 Paul Oo
Program Req. 21 days 9/10/15 10/1/15 Paul Oo
Work Allocation 21 days 9/10/15 10/1/15 Paul Oo
PDD 8 days 9/23/15 10/1/15 Paul Oo
PDR 7 days 10/1/15 10/8/15 Paul Oo
CDD 21 days 10/8/15 10/29/15 Paul Oo
CDR 7 days 10/29/15 11/5/15 Paul Oo
Documentation 168 days 8/24/15 12/9/15 Paul Oo
Final Presentation 35 days 11/5/15 12/10/15 Paul Oo
Project Video 70 days 10/1/15 12/10/15 Paul Oo

The table above (Table 1) shows the schedule created for the Project Manager. This schedule has been made to fit Fall 2015’s 400 D timeline and milestones. Furthermore, the schedule has been broken down according to program tasks (Mission Objective, Work Allocation, & Documentation). To improve this schedule, along with other members’, project managers should view this document from the first day of being assigned to their position.

Table 2 – Systems Engineer

Operation Duration Start Finish Resource Name
Systems Engineering 155 days 9/10/15 12/10/15 Railly Mateo
Project & Level 2 Req 13 days 9/10/15 9/23/15 Railly Mateo
System Block Diag. 8 days 9/23/15 10/1/15 Railly Mateo
Instructions Pamphlet 8 days 10/8/15 10/15/15 Railly Mateo
Hardware 14 days 9/23/15 10/7/15 Railly Mateo
Fritzing – System 8 days 9/23/15 10/7/15 Railly Mateo
Interface Design 2 days 10/6/15 10/7/15 Railly Mateo
Software 34 days 9/17/15 10/21/15 Railly Mateo
Arduino IDE 14 days 9/17/15 10/1/15 Railly Mateo
Bluetooth 4 days 10/8/15 10/11/15 Railly Mateo
Arxterra App 10 days 10/11/15 10/21/15 Railly Mateo
Testing 70 days 10/1/15 12/9/15 Railly Mateo
Subsystem/Syst. TP 70 days 10/1/15 12/9/15 Railly Mateo

The table above (Table 2) shows the schedule created for the Systems Engineer. The schedule has been broken down according to project tasks (Project & Level 2 Requirements, Hardware, Software, & Testing). To improve this schedule, along with other members’, system engineers should view this document from the first day of being assigned to their position. Systems engineers must be able to provide startup/error support to any subsystem.

Table 3 – Manufacturing Engineer

Operation Duration Start Finish Resource Name
Manufacturing 155 days 9/10/15 12/10/15 Michael Balagtas
Subsystem & L 2 Req. 13 days 9/10/15 9/23/15 Michael Balagtas
Design 14 days 9/23/15 10/7/15 Michael Balagtas
AutoCAD 3D Model 21 days 9/23/15 10/15/15 Michael Balagtas
EagleCAD High Level 2 days 10/6/15 10/7/15 Michael Balagtas
Production 44 days 10/1/15 11/15/15 Michael Balagtas
Fast-Prototype 15 days 10/1/15 10/15/15 Michael Balagtas
CNC Structure 8 days 10/15/15 10/22/15 Michael Balagtas
PCB Circuit board 38 days 10/8/15 11/15/15 Michael Balagtas
Testing 70 days 10/1/15 12/9/15 Michael Balagtas
Structure 70 days 10/1/15 12/9/15 Michael Balagtas
Electronics 70 days 10/1/15 12/9/15 Michael Balagtas

The table above (Table 3) shows the schedule created for the Manufacturing Engineer. The schedule has been broken down according to project tasks (Subsystem & Level 2 Requirements, Design, Production, & Testing). To improve this schedule, along with other members’, manufacturing engineers should view this document from the first day of being assigned to their position. Systems engineers must be able to provide startup/error support to any subsystem. In return, the subsystem engineers must be able to effectively produce level 2 requirements that meets project requirements.

Table 4 – Controls Engineer

Operation Duration Start Finish Resource Name
Controls & Process 155 days 9/10/15 12/10/15 Brian Walton
Subsystem & L 2 Req. 13 days 9/10/15 9/23/15 Brian Walton
Performance 21 days 9/23/15 10/15/15 Brian Walton
Arduino IDE Code 21 days 9/23/15 10/15/15 Brian Walton
EagleCAD Low Level 2 days 10/6/15 10/7/15 Brian Walton
Troubleshoot 37 days 10/7/15 11/15/15 Brian Walton
LTSPICE Simulations 37 days 10/7/15 11/15/15 Brian Walton
PID Control 37 days 10/7/15 11/15/15 Brian Walton
Testing 70 days 10/1/15 12/9/15 Brian Walton
Structure 70 days 10/1/15 12/9/15 Brian Walton
Electronics 70 days 10/1/15 12/9/15 Brian Walton

The table above (Table 4) shows the schedule created for the Controls Engineer. The schedule has been broken down according to project tasks (Subsystem & Level 2 Requirements, Performance, Troubleshoot, & Testing). To improve this schedule, along with other members’, controls engineers should view this document from the first day of being assigned to their position. Systems engineers must be able to provide startup/error support to any subsystem. In return, the subsystem engineers must be able to effectively produce level 2 requirements that meets project requirements.