Project Summary | Project Information |
---|---|
The Autonomous People Mover (APM) is an electric, self-driving golf cart that can transport people from one location to another while avoiding obstacles in its way. Using a variety of different cameras and sensors, the APM can detect objects and terrain, and safely transport passengers around campus. Once complete, the APM will be summoned via a text message, after which it would drive itself to the customer’s location, pick them up, and determine a destination using voice recognition. Ultimately, the purpose of the APM is twofold: to provide accessibility to campus goers, and to act as a platform for research and refinement of autonomous vehicle technologies. |
|
Team Members
From left to right: Anthony Luciano, Gregory Mullin, Thomas Harten, Jeff Barker, Noah LoConte, Robert Relyea
Member | Major | Role | Contact |
---|---|---|---|
Thomas Harten | IE | Project Manager | tbh3470@rit.edu |
Robert Relyea | CE | Lead Engineer | rer3378@rit.edu |
Anthony Luciano | EE | Lead Engineer | axl5567@rit.edu |
Jeff Barker | CE | Facilitator | jdb2438@rit.edu |
Gregory Mullin | CE | Communications | gbm4016@rit.edu |
Noah LoConte | EE | Purchasing | ntl6965@rit.edu |
Information
Content Guidelines: Use these links below to guide you in populating your website. A few points to consider:
- Be aware of any information that your sponsor might not want publicly available. You can use the directory for this information, and it will be available only to those users with Guest access to your site.
- Do not post any files on your site that are not yours, unless you are certain that they are in the public domain or you have received permission to post them. Examples of files that you should avoid posting are copies of published papers, standards documents, textbook chapters/excerpts, or copyrighted images. If you have received a .pdf of a paper through Interlibrary Loan, or purchased an ASTM or ISO standard, you may post it in the private directory, where only your team and guide will have access to it.
- If you are including contact information for people that would otherwise not be publicly available, make sure you have their permission. For example, your faculty advisor's email address and office phone number are already publicly available on the KGCOE website, and is fine to post. However, if he or she has provided a cell phone number to the team, that is most likely not public information and should not be posted without explicit permission.
- Comment out this text once you've read it.
Work Breakdown: By Phase
MSD I & II | MSD I | MSD II |
---|---|---|
Integrated System Build & Test Customer Handoff & Final Project Documentation (Verification & Validation) |
Work Breakdown: By Topic
Use this space to link to live/final documents throughout the project. Your team should customize this as-needed, with input from your guide and customer. The example below will address most of what most teams need to capture.
Project Management | Design Tools | Design Documentation | Implementation | Validation | Presentation & Dissemination |
---|---|---|---|---|---|
PRP Requirements Schedule Cost Risk Management Problem Management Communication & Minutes |
Use Cases Benchmarking Functional Decomposition Morphological Chart Pugh Concept Selection |
BOM Mechanical Drawings Electrical Schematics Software Diagrams Facility Layout Manuals |
Mockups Test Fixtures Prototyping Test Plans |
Analysis Results Simulations Test Results |
Design Review Documents Technical Paper Poster Imagine RIT Exhibit |
Acknowledgements
- Be sure to include any relevant sponsor acknowledgement throughout your site.
- Acknowledge any other support you have received from people at RIT or elsewhere.