P19123: Lockheed Amelia Drone
/public/

Gate Reviews

Table of Contents

Problem Statement

Current State of Design

Engineering Requirement Breakdown

Engineering Requirement Breakdown

Contraint Breakdown

Contraint Breakdown

Hardware Diagram

Hardware Diagram

Software Diagram

Software Diagram

Bill of Materials

Bill of Materials

P19123 ER Validation

P19123 Constraint Validation

Design Activities Open

Software Status

Software goals over winter break

Harness Status

Machining/Software

Manufacturing

Software

Project Plan Comparison From MSD I

ACCOMPLISHMENTS

SHORTCOMINGS

LESSONS LEARNED

Project Plan for Phase I

Main Objectives for MSD II Phase I:

MSD II Phase 1 Project Plan Page 1

MSD II Phase 1 Project Plan Page 1

MSD II Phase 1 Project Plan Page 2

MSD II Phase 1 Project Plan Page 2

MSD II Phase I Microsoft Project File

MSD II Phase I PDF

Risk Assessment

Previous Risks

Previous Risks

Previous Risks

Current Risks

CurrentRisks

CurrentRisks

Vendor Return Policies

Vendor Return Policies

Current Risk Mitigation

Current Risk Mitigation

Current Risk Mitigation

Individual Reflection

Category Bryan Bausinger Noah George Zach Stewart John Cowan Jake Kenin
Responsibilities
  • Project plan
  • Mechanical Engineering support (heat transfer)
  • Testing Documentation
  • Design and manufacture of harness
  • Power supply calculations
  • Graphic Maker
  • Conference call note taker
  • Lead to designing Software
  • Hardware selection
  • High level systems design
  • Secondary software developer
Project Plan Accuracy
  • Many dates slipped
  • Did not meet reach goals
  • Complete overall design
  • Bumpy road with good final design
  • Slow in making selections
  • Hardware selection fell behind schedule
Obstacles
  • Learning new hardware and technology
  • Design challenges not originally seen
  • Fitting together moving parts
  • Learning new software applications
  • Learning about niche network hardware
  • Solving a complex problem with budget constraints
Changes for MSD II
  • Hold tighter deadlines and continue action items
  • Test harness early to allow time for changes
  • Proactive work, not reactive
  • Start work earlier to avoid cutting it close
  • Contact SMEs as soon as possible
  • Change requirements instead of changing budget

Readiness to move to Build & Test

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