WRTG100 NAU Improved Seatbelt Gantt Chart Creation Gantt Chart Creation: 1. Download or use one of the following: a. GanttProject b. Microsoft Gnatt Projec

WRTG100 NAU Improved Seatbelt Gantt Chart Creation Gantt Chart Creation:
1. Download or use one of the following:
a. GanttProject
b. Microsoft Gnatt Project
c. Gantter in google docs
2. Enter the team WBS information into the software.
3. Create a team project file (depending on software used)
4. Include these for full credit:
a. At least one milestone to represent major due dates and completion dates
b. Indentations to represent different WBS levels
c. Multiple task dependency / link (all obvious dependencies should be linked)
5. Task notes for each task
a. this would be a good place to put in your definitions
6. Different bar colors for at least some of the lower entries
7. Specified start or end time for at least one task (this task will bound your project)
8. Resources applied to tasks – including personel, time, etc
a. Make sure no personel are overworked as a resource
In the body of this section of the report, you must describe the Gantt chart results by building on
the WBS descriptions in the previous section and in a way to completely describe to your reader
how your project time and resources will be managed.
Page 4 of 4
 This Progress Report will likely be multiple pages in length; one or more pages will be
clear images of the Gantt Schedule, in a bar chart format.
 Your , Gantter, GanttProject or MS Project file will also be uploaded by that date.
 This Progress Report and the scheduling software file is to be uploaded to BBlearn.
Note: I will be opening the attached files to check to see if you have completed the above
requirements.
Some useful links:
GanttProject:
– http://www.ganttproject.biz/
Gantter:
– Gantter and google drive –

– Gantter and google docs –

– Gantter Overview –

– Extended Gantter Features –

– Advanced Gantter Features – Week
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Date
1/14
1/16
1/18
1/21
1/23
1/25
1/28
1/30
2/1
2/4
2/6
2/8
Lecture
L1
L2
TW1
2/11
2/13
2/15
2/18
2/20
2/22
2/25
2/27
3/1
3/4
3/6
3/8
3/11
3/13
3/15
3/18
3/20
3/22
3/25
3/27
3/29
4/1
4/3
4/5
4/8
4/10
4/12
4/15
4/17
4/19
4/22
4/24
4/26
4/29
5/1
IM2
Seminar
TW5
L7
IM3
TW6
L8
L9
TW7
IM4
L10
L11
IM5
IM6
TW8
L3
TW2
L4
IM1
TW3
L5
L6
TW4
Topic
In-Class Activity
Class Introduction, Syllabus
Projects Intro, Teaming & Conflict Resolution
Writing in Engineering Presentation
NO CLASS – MLK Day
Project Teams, Team Meeting Principles
Organized Writing
Problem Definition
In-Class Meeting – Prob. Def., QFD, and Project Manag.
IEEE Formatting & Library Resources
State of the Art (SOTA) Literature Review 1
State of the Art (SOTA) Literature Review 2
Revising, Editing, Proofreading
In-Class Meeting- Concept Generation & Selection
Engineering Seminar 1
Proposal Outline
Individual
Assignments (HW)
Project Sign-up
Memo
Assignments Due Dates
TW 1 – Sign-up Memo: Jan 20
Team Contract
Flow and Coherence
QFD/Prob. Def/Proj. Ma
IEEE
Revising &Editing
Dream Team
Problem Definition,
QFD, and Project
Management Report
SOTA 1 – Research
Summary Memo
TW 2 – Meeting Guidelines: Jan 30
HW1 – Dream Team: Feb 3
TW3 – Proposal Outline: Feb 5
THW1 – Problem Def. and QFD: Feb 10
6,3,5 – Pugh Chart
HW2 – SOTA 1: Feb 14
SOTA
SOTA Workshop
Detailed Design: Engineering Analysis of Design
In-Class Meeting- Engineering Analysis in Design
Passive and Active Voices
Material Selction and Design with Material 1
Material Selction and Design with Material 2
TW Workshop 1 (Concept Gen and Selection)
In-Class Meeting- Material Selection
Design for Manufacturing & Assembly (DFMA) 1
Design for Manufacturing & Assembly (DFMA) 2
In-Class Meeting- DFMA
In-Class Meeting- Preliminary Design and Presentation
Technical Writing Workday
SOTA 2 – Literatue
Review Final
TW Workshop 1
Intro Workshop
Material Selection
DFMA
Presentation Tips
TW Workday
TW 4 – SOTA Workshop: Feb 19
Concept Generation &
Selection Report
HW3 – SOTA 2: Feb 24
THW 2 – Concept Gen and Sel: March 1
Engineering
Analysis of Design
Report
TW 5 – Passive and Active Voice: March 8
Material Selection &
DFMA Report
HW 4 – Eng. Analysis: March 17
SPRING BREAK
TW9
PR
PR
L12
L13
Quiz – IM7
L14
L15
IM8
L16
L17
TW10
IM9
Seminar
IM10
PR
PR
TW Workshop 2 (MS & DFMA Report)
PRELIMINARY DESIGN PRESENTATIONS
PRELIMINARY DESIGN PRESENTATIONS
Engineering Economics
Cost Analysis 1
Quiz / In-Class Meeting- Catch up
Cost Analysis 2
Cost Analysis 3
In-Class Meeting- Cost Analysis
Ethics Day 1
Ethics Day 2
TW Workshop 3 (Cost Analysis)
In-Class Meeting- Ethics
Engineering Seminar 2
Instructor/TA Meetings on Final Designs
FINAL PRESENTATION DAY 1
FINAL PRESENTATION DAY 2
15
TW Workshop 2
THW 3 -Mat Sel. And DFMA: March 25
THW4 – Prelim Presentation: March 26
Prposal Introduction
THW 5 – Proposal Intro: April 7
Cost Analysis
TW Workshop 3
Ethics
Cost Analysis Report
Ethics of Your
Design Report
Final Design Review
Final Peer Eval
5/3
Team Assignments
(THW)
PR
FINAL PRESENTATION DAY 3
THW 6-Cost Analysis: April 19
Final Proposal Include
Final Design, Cost
Analyses, DFM , &
Ethics
HW 5 – Ethics: April 26
THW 7 -Final Presentation: April 28
THW 8 -Final Report: May 3
THW 9 -CAD File: April 28
THW 10 -3D Printed Part: May 3- In CLass
Improved Seatbelt
Northern Arizona University
TEAM 2-SAFE:
ROBERT STEVENSON
RYAN MEYER
MARLON CORTEZ
STEPHON LANE
MOHAMMED ALSHAMMARI
CLIENT:
DR. HESAM MOGHADDAM
2/5/2019
Table of Contents
Executive Summary:
3
Introduction:
3
Problem Definition:
3
QFD Development:
3
Customer Requirements:
3
Table 1: Customer need results
3
Engineering Characteristics:
3
Table 2: Engineering requirements
3
Benchmarking:
3
Figure 1: House of Quality
3
Project Management:
3
Work Breakdown Structure:
3
Figure 2: WBS
3
Gantt Chart:
3
Figure 3: Gantt Chart
3
Work Cited:
3
Appendices:
3
1
Executive Summary:
Car safety has become a paramount importance in all modern day cars. The problem assigned to this
team is to make an improve car safety feature, that will decrease the chances of injuries or fatalities
when in car collisions. Due to the fact that seatbelts have not been improved since their addition to cars,
improving this feature will be the most effective way to reduce injuries in vehicle collisions. Client
interviews were conducted client interviews to understand what people expected from their current
seat belt and what alterations would be acceptable if implemented in future car models. This
information gave us the customer needs and engineering requirements necessary to create a house of
quality diagram(QFD). The QFD weighs the importance of each need and requirement, so we can create
the most effective seatbelt for the greatest percentage of car owners. After determining what changes
we were going to make to the seat belt from our QFD,
Introduction:
The seat belt has been a standard safety instrument in automobiles for several years. Its design has also
remained basically identical since its development. Its purpose is to protect the driver and passengers in
avehivld during a collison. However, it’s flawed design causes the seatbelt to cause other injuries to the
user.
Problem Definition:/
The client, Dr. Hesam Moghaddam, tasked the team to develop a vehicle safety feature that either
improved an existing system or create an original system that could be integrated into an existing
automobile. Each member of the team also conducted interviews with stakeholders to determine what
needs the project design should meet. After interviewing several stakeholders, the team concluded that
the seatbelt design should include a secondary highway harness as well as a more effective and
comfortable belt strap. It also requires an buckling mechanism that is easier to use than conventional
seatbelts. The goal of the project is to develop an improved seatbelt design that can be implemented
into a automobile during the manufacturing process. The project scope is to develop some designs,
develop prototypes, test the prototypes, then create a working final design along with a CAD model of it.
Based on the goal and needs for the project, the final design needs to meet the requirements that the
client and stakeholders placed for the seatbelt redesign. the three main engineering objectives that
must be addressed for the final design are impact force, shear force, and rate of deceleration. Based on
figure #, the highest ranking engineering objective is to find a way to disperse the impact force during a
collision more effectively than standard seat belts. The metric for this objective will be newtons of force.
The third ranking objective is to use a material that can withstand a sufficient amount of shear force
during a collision. This will be measured using Newtons per meter squared. the third ranked engineering
requirement is to find a way to make the rate of deceleration enough to reduce injuries such as whiplash
2
during a collision. The top three design constraints based on figure # are cost, time, and deformation. In
terms of design restraints,keeping the cost to a minimum is the most important based on its absolute
technical importance. This metric will be measured on U.S dollars. The next constraint is to develop a
material that will deform under a certain amount of force in order to reduce injuries that occur during
high speed collisions. This metric will be measured in millimeters of distance. The third ranking
constraints is to produce a system that can respond within a miniscule time frame during a collision. this
will be measured in seconds. Some of these restraints may conflict with the objectives listed above. For
instance, the cost of the design may require the team to resort to lower cost materials and that may
compromise the other objectives such a reducing impact force. Throughout the design, process some
criteria may need to be revised in order for any conflicts to be avoided with the objectives and
constraints.
Table #: Project Objectives and Restraints
Table #: Projects objectives and restraint, based on QFD, figure #
Rank
Objective
Restraint
1
Impact Force (N)
Cost ($)
2
Shear Force (N/m^2)
Deformation (mm)
3
Rate of
Time (s)
Deceleration(m/s^2)
QFD Development:
Customer Requirements:
/
Table 1: Customer need results
Table 1: Customer needs interpreted from customer interviews, task 1.3.1.2 in the WBS.
3
Customer Need
Amount
Ranking (1-5)
Functionality
10
5
Comfortability
9
5
Improved Restraint
10
5
Head-On/Rear-End Restraint
6
4
Broadside Restraint
5
4
Vertical Restraint
3
2
Convenience
5
3
Additional Restraints
7
4
Engineering Characteristics:
/
Table 2: Engineering requirements
Table 2: Engineering requirements found in task 1.3.1.3 of the WBS.
Engineering Requirement
Unit
Impact Force
N
Shear Force
N/m^2
Rate of Deceleration
m/s^2
Mobility
mm
4
Deformation
mm
Force Dispersion
Time
s
Actuation Force
N
Belt Area
m^2
Adjustability
mm
Cost
$
Benchmarking:
/
House of Quality:/
/
5
Figure 1: House of Quality
Figure 1: House of Quality for car safety Feature, task 1.3.1 in the WBS.
Project Management:
Work Breakdown Structure:/
A work breakdown structure (WBS) is an effective way to organize a project from beginning to end. For
the car safety feature project this was accomplished by first determining what the milestones are
required throughout the length of the project. The milestones pertaining to the car safety project are
the ten team homework assignments due throughout the spring 2019 semester. Each team homework
assignment can be divided into sub task, which in turn can be divided into more subtask. Sub task were
determined primarily from the assignment requirements. Figure # shows the WBS task and subtask for
the car safety project in its entirety. Due to the scale of the project figures #-# are enlarged portions of
figure #. Details concerning each task can be found in table #.
6
Figure #: Work Breakdown Structure
Figure #: Work breakdown Structure displaying task and subtask of entire car safety project.
WBS completed:
The left side of the WBS contains what the team has completed to date and can be viewed in detail in
figure #. The completed section has the most detail because the requirements for task 1.0 THW1 were
known at the time the WBS was created. The completed task are marked with a greendot to make them
easily identifiable as completed. The sub task for 1.0 THW1 are broken down into three sub categories.
The first 1.1 Set Team Guidelines, involved having the first team meeting and introductions. Task 1.2
involved narrowing down what safety feature the team should focus on improving.
Figure #: WBS completed
Figure #: Work breakdown structure for completed task.
7
WBS Upcoming task:
The middle of the WBS, task 2.0 through task 10.0 was created using hard deadlines found in the
tentative schedule for CENE-386w. Further details for upcoming assignments will become available
closer to the due dates.What details are known can be seen in Table # in the grey section. Until further
information is received containing the requirements for each upcoming assignment the team member
responsibilities and and time durations are labeled entire team or TBD, meaning to be determined.
Figure #: WBS Upcoming
Figure #: Work breakdown structure of upcoming task.
WBS Predicted:
The rightmost portion of the WBS, enlarged in figure #, contains predictions for task if the car safety
project went past the end of the semester. These task are hypothetical and have made up deadlines that
can be found in the blue section of table #. If the team continued work on the car safety feature testing
would have to be done to prove that the seat belt design was functional and safe for real world use.
Once the design was determined safe it could then be installed in the clients car.
8
Figure #: WBS predicted
Figure #: Work breakdown structure of predicted task if the team continued work after final class
deadline
Table #: WBS task responsibilities table
Table #: WBS task descriptions, assigned team member(s), and estimated time duration to complete.
Task
Number
Task Name
Description
Required Team
Time
resources Member(s) (h)
Deadline
1.0
THW1 Project
Def and QFD
Current Report
Google
Docs,
Word
1.1
Set team
guidelines
1.1.1
1.2
Team
27
2/14/19
Discuss team guidelines and
problem statement
Team
1
1/30/19
Have first
meeting
In person meeting in Rm 112
EGR building at 11:00am
Team
1
Decide on
feature
Team brainstorming for car
safety feature ideas
Team
1
9
1.2.1
Meet with
client
See client in Room 122k
during office hours for
details
Client
Team
1
1.3
Write report
Assign report sections to
individual members
Google
Docs,
Word
Marlon,
Ryan
4
1.3.1
Make QFD
Use CN’s and EGR
requirements to make QFD
White
board
Stephon
4
1.3.1.1
Create Gantt
chart
Use WBS to create a Gantt
chart
Gantter.c
om
Mohamed
4
1.3.1.1.1
Make WBS
Create a WBS using the
tentative schedule
BBL, Excel Rob
4
1.3.1.2
Find customer
needs
Rate customer needs in a
table
CN data
Stephon
1
1.3.1.2.1
Conduct
interviews
Interview customers and
interpret needs
Customer
s
Team ind.
5
1.3.1.3
Find
engineering
requirements
Discuss engineering
requirements as a team
White
board
Team
1
2.0
THW2 Concept
generation and
selection
Report requirements are not
available at this time
Team
TBD
2.1
Select concept
Hold meeting to vote on
best concept
White
board
Team
1
2.1.1
Have team
compare
concepts
Hold meeting to compare or
combine concepts
White
board
Team
2
2.1.1.1
Create
individual
concepts
Each Team member creates
three or more concepts
Team ind.
2
3.0
THW3 Material
selection and
Report requirements are not
available at this time
Team
TBD
2/9/19
3/1/19
3/25/19
10
DFMA
3.1
Write report
3.1.1
Receive
assignment
4.0
THW4 Prelim
presentation
4.1
Write report
4.1.1
Report requirements are not Google
available at this time
Docs,
Word
Team
TBD
Team
TBD
Presentation requirements
are not available at this time
Team
TBD
Report requirements are not Google
available at this time
Docs,
Word
Team
TBD
Receive
assignment
Team
TBD
5.0
THW5 proposal Report requirements are not
Intro
available at this time
Team
TBD
5.1
Write report
Team
TBD
5.1.1
Receive
assignment
Team
TBD
6.0
THW6 Cost
analysis
Report requirements are not
available at this time
Team
TBD
6.1
Write report
Report requirements are not Google
available at this time
Docs,
Word
Team
TBD
6.1.1
Receive
assignment
Team
TBD
7.0
THW7 Final
presentation
Team
TBD
Report requirements are not Google
available at this time
Docs,
Word
Report requirements are not
available at this time
3/26/19
4/7/19
4/19/19
4/28/19
11
7.1
Practice
presentation
Team should practice
presentation for timing and
flow
Team
TBD
7.1.1
Receive
assignment
Team
TBD
8.0
THW8 Final
report
Report requirements are not
available at this time
Team
TBD
8.1
Write report
Report requirements are not Google
available at this time
Docs,
Word
Team
TBD
8.1.1
Receive
assignment
Team
TBD
9.0
THW9 Cad file
CAD requirements are not
available at this time
Team
TBD
9.1
Model part
Model part in Solidworks
9.1.1
Receive
assignment
10.0
THW10 3D
printed part
Report requirements are not
available at this time
10.1
Print 3D part
Print Solidworks part at the
Cline Library
11.0
Test design
11.1
Solidwork Marlon,
s
Stephon
5/3/19
4/28/19
TBD
Team
TBD
Team
TBD
Cline
library
Mohamed
TBD
Test feature for safety
lab
Team
100
Build
prototypes
Build prototypes based off
final concept
Lab,
tools
Team
30
11.1.1
Assemble parts
Put all the parts together to
create
Tools
Stephon,
Rob
10
11.1.1.1
Gather
materials
Collect all needed materials
to build prototype
Ryan,
Mohamed
10
5/3/19
11/3/19
12
11.2
Build testing
equipment
Testing may require custom
testing equipment
11.2.1
Design testing
equipment
11.2.1.2
Find lab for
testing
Testing will need to be done
in a controlled environment
12.0
Install in
client’s vehicle
Feature will be installed in
client’s vehicle
Lab
Lab
Rob,
Marlon
30
Team
20
Mohamed
10
Team
10
12/25/19
Gantt Chart: /////
/write body in here
Figure 3: Gantt Chart
insert clear gantt chart here, see comments for requirements
Conclusion:
Work Cited:
Appendices:
13

Purchase answer to see full
attachment

"Order a similar paper and get 100% plagiarism free, professional written paper now!"

Order Now