P19319: Lockheed ATLAS II

Planning & Execution

Table of Contents

Team Setup

Wyatt Morris

Major: Electrical Engineering
Role: Project Manager
Description: Create and maintain schedules to keep team aligned toward project goals and deadlines. Follow through with each team member to meet project expectations.
Skills: Microsoft Office, LabVIEW, LabWindows CVI, C/C++, System Integration/ Troubleshooting, Assembly
Experiences: Previously created test software with LabWindows CVI in robotic arm system. Also used LabVIEW to adjust previous archive system used for microstrip filters. System integration for air traffic control systems from serial to Ethernet system-wide.

Ndeye Fatou Diop

Major: Mechanical Engineering
Role: Mechanical Lead
Description: Responsible for mechanical hardware modeling, design and fabrication.
Skills: MATLAB, Solidworks, AutoCAD, PTC Creo, ANSYS, LabVIEW, Microsoft Excel & VBA/Macros programming, Microsoft Office, intermediate machining
Experiences: Have completed co-ops in roles involving Manufacturing engineering, Systems engineering and repair engineering. Additional experience in product design, systems integration, process improvement and root cause analysis.

Matt Harvey

Major: Electrical Engineering
Role: Electrical Lead
Description: Responsible for managing the power/electrical systems for the addition of camera & cycle time modifications.
Skills: Microsoft Office, MATLAB, Draftsight CAD software, Code Composer Studio, PSPICE
Experiences: Created new electrical drawings; modified and updated old drawings using Draftsight CAD software. Performed machine testing and minimal PLC programming.

Christopher Hart

Major: Mechanical Engineering
Role: Systems Integration Lead, EDGE Manager
Description: Responsible for overseeing the integration of each subsystem into the complete design. Also responsible for working with the mechanical lead on all mechanical engineering components and ensuring the EDGE site is comprehensive and of high quality.
Skills: Microsoft Office, MATLAB, PTC Creo, AutoCAD, LabVIEW, Microsoft Excel with VBA, machining experience.
Experiences: Created lighting, electrical, and fire alarm device floor plans for buildings and complexes using AutoCAD. Modified and updated previously created AutoCAD drawings.

Earl Sharkey

Major: Computer Engineering
Role: Software Lead, Team Facilitator
Description: Responsible for existing software optimization as well as camera algorithm integration to existing software and hardware design.
Skills: PSPICE, MATLAB, Multi-language programming, Software quality, Software process, troubleshooting.
Experiences: Web and mobile software quality, managed quality of releases for third part developed websites and mobile apps. Mobile app automation testing, Writing automation tests as part of an existing automation framework for Snap Inc.

Skill Gaps

Team Values and Norms

Each team member will be prompt and arrive at the team meetings with a 10 minute grace period. Team members will avoid recurring tardiness without prior notice. If an unexpected conflict comes up, the absent team member will notify at least one team-mate prior to the expected absence. An absent team-member should confirm that a team-mate has received their message (in person, voice mail, email, etc).
Each team member will complete their tasks thoroughly and completely, so that the work does not have to be re-done by a peer on the team. If a member does not know how to complete a task, feels overwhelmed, or needs assistance then the member notifies peers, and seeks assistance either from a peer, the faculty guide, a faculty consultant, or another person.
Each team member completes their work accurately and in a way that can be easily checked for accuracy by peers and the faculty guide. All work is fully documented and easy to follow.
Professional and Ethical
Each team member gives credit where credit is due. All work completed includes citations to appropriate literature, or sources of assistance. If a team member has gotten assistance from a publication or individual, then that assistance or guidance is fully documented in the reports prepared. Each team member is honest and trustworthy in their dealings with their peers.
Each team member will contribute an equal share to the success of the project.

Project Plans & Schedules

The master schedule below highlights the plan for the ATLAS project throughout MSD I. The schedule will be updated for MSD II and when goals are completed.
Master Schedule

Master Schedule

The list will be updated as needed and can be found here.

Risk Assessment and Growth Curves

This table will be used to track and assess possible risks throughout the project duration.
Risk Management Table

Risk Management Table

Meeting Minutes, Notes, & Actions

A Task/Status List will be used to keep track of meetings and assignments for MSD I.

Master Task List

Master Task List

The list will be updated as needed and can be found here.

Peer Reviews

Peer reviews will be created at the end of Week 3. Peer reviews will be based on the team values and norms. Each team member will be responsible for filling in the peer reviews for each remaining team member at the conclusion of each phase.

The peer review rubric can be found here.


Customer Information

Communication Plan

Inter-Team Communication

Intellectual Property Considerations

As this project is sponsored and funded by Lockheed Martin, all IP will be assigned to Lockheed Martin.

Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation