P19123: Lockheed Amelia Drone/public/
Planning & Execution
Table of Contents
Intellectual Property Considerations
- All IP generated during the course of the project belong to the project’s sponsor, Lockheed Martin.
- In the event that Lockheed Martin patents any of the IP generated during the course of this project, the team member’s names will be included as inventors on the patent.
- Bryan Bausinger
- Mechanical Engineering BS/ME
- Team lead - Manage project schedule, ensure all project deadlines are met, verify all tasks are completed
- Specializing in vibrations
- 3 rotations with GE Aviation in roles of project engineering, design engineering, and test engineering
- Noah George
- Mechanical Engineering BS
- Manufacturing Lead - Interfaces with the machine shop and the manufacturing of physical systems
- Specializing in machining and CAD modeling
- 8 months with Harris as a test engineer and mechanical design engineer
- Zach Stewart
- Electrical Engineering BS
- Scribe - Records meeting notes and action items
- Communications Lead - Point of contact for interactions with people outside the team
- 13 months with GE Aviation performing software, supply chain, and systems verification engineering
- Jacob Kenin
- Computer Engineering BS
- Purchasing Lead - Point of contact for all purchasing and budget management
- Systems Lead - Point of contact for top level definition of the interfaces between modules
- Specializing in autonomous UAS
- 4 rotations at Aurora Flight Sciences (now a subsidiary of Boeing) developing autonomy systems for small and large drones
- John Cowan
- Computer Engineering BS
- Software Lead - Primary developer for base station software
- EDGE Specialist - Maintains EDGE documentation
- 6 months with Quest Global as a programmer including Graphical User Interface (GUI) project
Team Values and Norms
- On time to meetings
- 1 - Missing multiple meetings without giving the team any notice
- 3 - Arrives at meeting time and ready to discuss material
- 5 - Ready to start meeting on time and provided information before
- Delivering on Deadlines
- 1 - Missing multiple deadlines
- 3 - Hitting deadlines or informing team with plenty of time of issues hitting deadline
- 5 - Hitting all deadlines despite issues and keeping the team informed on progress
- 1 - Lying about work and progress made
- 3 - Letting the team know with ample time about issues and being transparent about work progress
- 5 - Telling the team ASAP if there’s an issue and being honest about it
- 1 - Communicating a problem at the deadline
- 3 - Telling the team about any problems when they occur
- 5 - Forewarning the team about a potential problem that could occur before it even happens
- 1 - No deliverables or deliverables serve little purpose to the project
- 3 - Presentation ready and covers all points in rubric
- 5 - Having a commercial ready product that could be put on the shelf
- 1 - Making excuses and never taking the blame for anything
- 3 - Owning up to issues
- 5 - Owning up to issues and being proactive about getting past them
Project Plans & Schedules
- Detailed schedule for Gantt chart
Risk Assessment and Growth Curves
For the full Risk Assessment file
Other Team Resources
- Meeting Schedule
- Tuesday: 11:00 AM to 1:45 PM in the MSD meeting room
- Wednesday: 1:00 AM to 2:00 PM in the ME lab or library
- Thursday: 11:00 AM to 1:45 PM in the MSD meeting room
- Planned build and test space
Meeting Minutes, Notes, & Actions
- Notes from Customer Interviews/Meetings
- Zach Stewart will be responsible for taking notes during meetings and collecting other team members notes and uploading them to our shared drive.
- Customer communication
- We are to send a bi-weekly status update via email to Jim Melby covering the work accomplished since the last check in.
- Whenever we have questions, we are to contact Jim Melby. From there Jim Melby can either answer our questions himself or direct us to the someone from Lockheed Martin who can.
- All communications with the customer (Lockheed Martin) are to have our faculty guide Gary Werth CCd.
- All general communications between the team and the customer will be handled by Zach Stewart.
- Jim Melby has expressed interest in participating in our phase reviews. He will be remotely attending the upcoming Phase 1 review.
- Intra-team communication
- For simple real-time group communication we will use a group chat based on the application GroupMe.
- For asynchronous communications or communication involving transferring documents we will use our school emails.
- For urgent communication or communication that is more involved we have all exchanged phone numbers, so we can be immediately reached via text or call.
- All email communications regarding team progress, questions, or work are to have Gary Werth CCd.