The document summarizes a presentation on Stevens Shuttle 2.0, which proposes improvements to the student shuttle system. The current system is inefficient with unreliable wait times and not enough seats. Stevens Shuttle 2.0 would implement updated GPS, shuttle capacity tracking in a new app, and measure fuel savings. It outlines the solution, operation details, proposed schedule, budget, risks, assumptions, and stakeholders. The presentation argues the new system could save costs while providing a more reliable transportation option for students.

1. Stevens Shuttle 2.0
Presenters
Chinonso Oham
Rohan Waghere
Akash Dhotre
Yash Raje
Devaun Armstrong

2. Agenda
● Stevens Shuttle 1.0
● Problems
● Solution (Stevens Shuttle 2.0)
● Logistics

3. Current commute to Stevens
Students
come to
the shuttle
stop
Check a
third-
party app
for
“estimated
wait time”
Shuttle
picks
students
and drives
them to
Stevens

4. Problems with the current system
• Inefficiency:
• Not enough seats during peak hours
• Unreliable tracking system
• Non-value rides

5. Solution
● Updated GPS Modules
● Handshake and Shuttle Capacity
● Generic Model

6. Operation & Limitation
Shuttle Routes
Solution Limitations
• Updates
• Beneficiary Satisfaction
Index

7. Estimated Fuel Savings
Efficiency
Summary
Parameters Red (6) Green (2) Gray (6) Blue (12)
Potential Save
Value
Total Cost for
NVR/Semester $216.36 $68.34 $227.52 $569.16 $1,081.38
Annual Costs on
NVR $649.08 $205.02 $682.56 $1,707.48 $3,244.14
% Costs for
NVR/Annually 15.00% 5.00% 15.00% 30.00% 17.38%
Stevens Shuttle 2.0
Total
Costs/Semester $1,442.40 $1,366.80 $1,516.80 $1,897.20 $6,223.20
Annual Costs $4,327.20 $4,100.40 $4,550.40 $5,691.60 $18,669.60
Current Fuel Costs
NVR – Non-Value Rides

8. Proposed Schedule
● Approx 123 days
● Latest Finish: 131 days
● Total slack time: 8 days
(131-123= 8 days)

9. Proposed Schedule
Launch first
survey
Survey results
Begin app
development
Register app on
Google Play/App
Store
Beta test
Advertise the app
Establish
maintenance
schedule for app
Calculate BSI

10. Proposed Schedule
● Each stage will be monitored to
ensure that the project is on track.
● Each team member is responsible for
certain activities
● Communication and changes will
be on to the project lead.
● The updates will be distributed in the
progress reports that will be sent out
on a bi-weekly basis.

11. Proposed Budget
● Activity costs: $17,805
● Material costs: $150
● Allowance for extra
costs: $1,800
● Total budget: $19,755

12. Risks facing Stevens Shuttle 2.0
Risk Impact
Not enough students respond to
the surveys
Smaller response sample,
responses not reflective of the
whole population
App development takes longer
than projected schedule
Milestones not delivered on time,
delayed project completion
Budget doesn’t cover the entire
project
App quality may be compromised

13. Risks facing Stevens Shuttle 2.0
Risk Impact
Inaccuracy in shuttle arrival times
shown in the app
Passengers delayed
Hacks/cyber attacks App not working as intended,
accounts compromised
Unexpected shutdown in the app Students unable to notify drivers of
their locations / track locations of
shuttles

14. Assumptions
● Budget is estimated correctly
● Estimates for schedule and milestones are tangible
● Facilities/resources we need to work will be available when
required
● Risks, their severities, and mitigation plans have been properly
defined.

15. Assumptions
● We would have a sufficient sample in the surveys to calculate
the Beneficiary Satisfaction Index
● The solution proposed will save operational costs involved in
shuttle services
● The shuttles use an average of 17 miles per gallon
● Requirements are clearly understood by the software
development team

16. Stakeholders:
● Project Team
● Students
● Administration:
○ President,
○ Software developer,
○ Shuttle riders

17. Thank you!