Mission Control Procedures - PRP
- Project Name
- METEOR Mission Control Procdedures
- Project Number
- Project Family
- P07100 - METEOR
- Aerospace Systems and Technology Track
- Start Term
- End Term
- Faculty Guide
- Dr. Dorin Patru (EE)
- Faculty Consultant
- Dr. Jeffrey Kozak (ME)
- Primary Customer
- Dr. Dorin Patru (EE)
- Customer contact information
- Dr. Dorin Patru
METEOR, Microsystems Engineering and Technology for the Exploration of Outer Space Regions, is a university-based project, whose short-term goal is to launch and place small payloads in low earth orbit, and whose long-term goal is to place such payloads on near earth asteroids and lunar surfaces. The mission of this student team is to deliver the mission control procedures for the sub-ortibal launch scheduled for the Summer of 2007. The mission control procedures will be an electronic system that contains descriptions of pre-launch, launch, and post-launch activities. This electronic system will be able to present nominal, or expected, procedures and contingency, or uncertainty, procedures in real time. The electronic system will allow students to enter results of pre-launch testing or any issue with the rocket that may arise and the system will respond with the action to be taken and will automatically re-route the procedures accordingly. Information such as documentation of all necessary tools and equipment needed for the launch will also be included. Along with the Mission Control Procedures, this project involves creating a training program for students to physically simulate the launch. In the simulation the students will use the electronic system to physically simulate all activities leading up to the launch. Unexpected situations will be interjected into the simulation allowing the students to practice using the contingency aspect of the electronic system. Below is a schematic of METEOR's current design.
|Team Member||Discipline||Role / Skills||email address|
|Dorin Patru||EE||Faculty Guide, Will work closely with the team on an on-going basis to facilitate firstname.lastname@example.org|
|Jeffrey Kozak||ME||Faculty Consultant, Will provide ME discipline technical email@example.com|
|Jon Klenovic||ME||Project Team Leader. Mechanical Lead. Function as the expert when interfacing with other METEOR teams in mechanical situations. Establish structure of the firstname.lastname@example.org|
|Jeffrey Sullivan||EE||Electrical Lead. Function as the expert when interfacing with other METEOR teams in electrical situations. Establish structure of the training email@example.com|
|Alberto Lopez Samper||IE||Determine multiple presentation styles of the electronic system. Establish the document control firstname.lastname@example.org|
Continuation, Platform, or Building Block Project Information
The mission of the Aerospace Systems and Technology track is provide several families of projects devoted to students in the Aerospace option, or with an interest in Aeronautical systems, aircraft design, spacecraft design, launch and recovery vehicles, and space exploration. Air and Space craft may have a lot of overlap with other vehicle systems, but also have unique aspects related to flight. Along with METEOR, the other Family of Projects in this track is the Micro Air Vehicle Family. The accomplishments of the track will be used in a variety of education, research and development and outreach applications within and beyond the RIT KCGOE.
This is a test this only a test. Do not adjust your television.
METEOR is a hands-on, multi-phase, multi-disciplinary, teaching and research program for investigation and developing micro-systems engineering, science, and technologies for the exploration of outer space. This project will provide the students and faculty at RIT, and the scientific community at large, the opportunity to obtain small payload volumes for conducting micro-systems and other scientific experiments in outer space. Meteor will accommodate and promote these multi-disciplinary collaborations. The project provides research opportunities for both undergraduate and graduate students. More about the METEOR program can be found at the METEOR Website.
METEOR is a project within the Aerospace Systems and Technology Track, to develop a fully comprehensive electronic system to describe all activites leading to a successful launch.
A number of other projects are intimately related to this project, as summarized in the list below.
|Related Project||Title||Start Term||End Term|
|P07102||METEOR Space Environment Test Stand||2006-1||2006-2|
|P07103||METEOR Instrumentation Platform||2006-1||2006-3|
|P07104||METEOR RITSAT1 Satellite||2006-1||2006-3|
|P07105||METEOR Launch Vehicle||2006-2||2006-3|
|P07106||METEOR Inertial Navigation and Guidance||2006-2||2006-3|
|P07108||METEOR Gliding Instumentation Platform||2006-2||2006-3|
Principle Sponsor or Sponsoring Organization
This project is supported by a gift from the Rochester Institute of Technology. The Institute has an interest in continued education through hands on experience and the goal is the development of space technology. The project has also recieved a large donation from Harris RF Corporation and donations in kind from 11 companies. Harris RF Corp is an international communications and information technology company serving government and commercial markets in more than 150 countries. The company's operating divisions serve markets for government communications, RF communications, broadcast communications, and microwave communications.
Detailed Project Description
Interactions with Customer
First Customer Interview
- Interviewers: Jon Klenovic, Student
- Customer: Dr. Dorin Patru, Professor, EE
- September 22, 2006, Dr. Dorin Patru's Office
- Interviewer: Hello Dr. Patru, I am Jon Klenovic. As I mentioned in my email to you earlier this week I am currently enrolled in Design Project Management with Dr. Edward Hensel and Dr. Marcos Esterman. I have selected the Mission Control Procedures as the project that I will be developing the Project Readiness Package for and that I will be involved with in Senior Design I and II. I would like to ask you a few questions today about the Mission Control Procedures Project and about the METEOR Project as a whole to help me develop the PRP.
- Customer: Okay, what are your questions?
- Interviewer: I have spent some time on the METEOR website gathering some information on the project. Is there anything you can tell me about the METEOR Project that I wouldn't have gotten from the website?
- Customer: The METEOR Project started in 2004 and we are currently working on its 4th version. We have a short term goal of sub-orbital launch and a long term goal of orbital launch. We eventually hope to place small payloads on near Earth objects. Sub-orbital launch, which we hope to accomplish this summer is any launch that travels 100KM above sea level. The sub-orbital launch is expected to take place in the Gulf of Mexico and orbital launch in Hawaii. I expect there to be 4 teams working on the METEOR project this winter, two of which will be working on the rocket itself.
- Interviewer: What is the goal of the Mission Control Procedures Project?
- Customer: The team will consist of a small group of 2-3 students, who will interface with all teams working on the METEOR Prjoect to understand what has to be done to make this time frame of sub-orbital launch by the Summer of 2007 happen. A procedures manual will be set up that includes a laundry list of tools and equipment that is needed for the launch. The manual should address "What happens if?" scenarios. It will include what equpiment goes with the team to the launch and what stays home. The manual should say what tests need to be performed prior to launch and what those tests should show. If the tests do not show what they should, what is the next step? Can it be fixed? Should we launch? It should describe what has to happen for a successful launch, what should be done if something fails.
- Interviewer: Are there any secondary goals of the project?
- Customer: A secondary goal would be to set up a training scheme to prepare the individuals for launch. It would be an operations simualtion that sets up scenarios for the student controllers. Also an additional Mission Control Procedures needs to be developed for orbital flight.
- Interviewer: Who is the primary customer for the project?
- Customer: The project is both internally and externally funded however I am representing the METEOR Family of Projects.
- Interviewer: What do you, the customer, hope to obtain from the Mission Control Procedures Project?
- Customer: Necessary and sufficient documentation describing the activites leading to a successful orbital flight.
- Interviewer: Are there any secondary customers?
- Customer: No. Well, public access maybe. Information to post on the website.
- Interviewer: Are there any regulatory, academic or safety constraints on the project?
- Customer: There are liscensing and safety requirements that will have to be addressed for the launch. (Hands interviewer FAA regulations manual) We have identified the FAA regulations that we must comply with but we have to figure out any other regulations to test for such as state regulations.
- Interviewer: What disciplines are involved in this project?
- Customer: It will be a small group of students, probably 2-3. This is mainly an IE project but ME's and EE's will be needed to have a detailed knowledge of the system. So most likely 1 IE, 1 ME, 1 EE.
- Interviewer: What equipment or labratories are being used for the METEOR Project?
- Customer: In building 17, in the northwest corner, there is a lab that is devoted to METEOR and intended for in flight mission control.
- Interviewer: Well, that is about all I have for now. I will review this information and figure out where the holes are and then I will contact you again through email to set up a time to meet again.
- Customer: Okay sounds good.
- Interviewer: Thank you Dr. Patru.
- Customer: Thanks.
Second Customer Interview
- Interviewers: Jon Klenovic, Student
- Customer: Dr. Dorin Patru, Professor, EE
- October 4, 2006, Dr. Dorin Patru's Office
- Interviewer: Hello Dr. Patru, thanks for meeting with me again.
- Customer: No problem, how are things coming?
- Interviewer: Good. I sat down and looked over the information from last time and I've indentified some areas that I have more questions.
- Customer: Okay.
- Interviewer: Who is the principle sponsor for the project and why are they interested?
- Customer: I would say that RIT is the principle sponsor. They have donated $69,000, $33,000 of which went to the antenna platform and $36,000 went to materials, components, and equipment. The project has recieved approximately $10,000 in kind from almost a dozen companies. Harris Corporation has promised $100,000 but we have no seen the money yet. The Gleason fund has also donated. All of the sponsors are interested for educational purposes. For RIT, it provides the students with hands on experience in space technology development. It is also promising for future income through profited reinvestment into research.
- Interviewer: What are the Roles of those involved? (Dr. Patru, Dr. Kozak, Dr. Hensel, Dr. DeBartolo, Dr. Amuso)
- Customer: I am the leading of the METEOR Family of Projects. I came up with the idea. I also serve as the faculty guide and the principle EE advisor. Dr. Kozak would be considered to be on the same level as me. He is a faculty guide and serves as the principle ME advisor. Dr. Hensel is a co-investor into the project and he has helped previously with thermal and structural analaysis. Dr. DeBartolo has been involved by helping students with fatigue calculations. Dr. Amuso in the past has been involved with the EE students, assisting them with Digital Signal Processing and algorithms. However since he has now become the EE department head, he has taken on a larger roll by being involved with the money aspect.
- Interviewer: I would like to try and break down exactly what the Mission Control Procedures is going to need to contain.
- Customer: The manual should include both nominal and contingency procedures. I would like to see the training program for the students and that should also set up nominal and contingency scenarios. It also must address federal, state, local and international regualtions.
- Interviewer: Okay great. The first question I have is about materials and equipment. Are there any materials or equipment that we will be using for this project.
- Customer: Well the only materials you will need is stationary and you will have printing privelages for that. However in the EE Senior Design lab there is a computer that is dedicated solely to the METEOR Project. You will be able to use that to save all of your work.
- Interviewer: For this year, what is the budget for the entire METEOR Project?
- Customer: The budget for this years METEOR Project will be $50,000.
- Interviewer: How about a budget for the Mission Control Procedures?
- Customer: We will allocate approximately $1,000 dollars to this project. There will be a budget estimation due for this project at the end of week 6. You may need more you may need less. There will be some give and take but I have a pretty good idea of which projects will be going over budget and which we be under budget.
- Interviewer: In the PRP there is a section that pertains to engineering specifications. For a project like this, what kind of information would be included there?
- Customer: This sounds like a place where you would talk about the the procedures breakdown. Discuss the pre-launch, launch and post-launch groupings and then divide those groups up into nominal and contingency procedues, etc.
- Interviewer: Okay that takes care of everything. I don't suspect that I will have many more questions so rather than meeting again I will probably just send you an email if a specific question arises.
- Customer: Okay that is a good idea. And I've heard that your class is going to be presenting these next week. I believe I will be available on Wednesday.
- Interviewer: Okay that will be fine. Thanks
Interpretation of Raw Data into Customer Needs
- The electronic system must include procedures for pre-launch, launch and post-launch activites.
- The electronic system must include nominal, or expected procedures.
- The electronic system must contain contingency, or uncertainty procedures.
- The electronic system must contain documentation of all tools and equipment necessary for launch.
- The electronic system must include all appropriate pre-launch and post-launch testing for the platform and the criteria for determing if the launch will take place.
- The electronic system must take into account all local, state, federal and international regulations with regards to space flight activites into the procedures.
- The electronic system must include a training program that allows the student controllers to simulate a launch that contains nominal and contingency scenarios.
Hierarchical Customer Needs
Need 1- The manual must include
- Need 1.1 - Pre-Launch
- Need 1.2 - Launch
- Need 1.3 - Post-Launch
Need 2- The manual must include
- Need 2.1 - Pre-Launch
- Need 2.2 - Launch
- Need 2.3 - Post-Launch
Need 3- The manual must have
documentation of all tools and equipment necessary for
- Need 3.1 - Pre-Launch
- Need 3.2 - Launch
- Need 3.3 - Post-Launch
Need 4 - The manual must include all
appropriate testing for the launch.
- Need 4.1 - Pre-Launch test and criterion
- Need 4.1a - Actions for passing criteria
- Need 4.1b - Actions for failing criteria
- Need 4.2 - Launch tests and criterion
- Need 4.2a - Actions for passing criteria
- Need 4.2b - Actions for failing criteria
- Need 4.3 - Post-Launch tests and criterion
- Need 4.3a - Actions for passing criteria
- Need 4.3b - Actions for failing criteria
- Need 4.1 - Pre-Launch test and criterion
Need 5 - The manual must take into
account all rules, regulations, policies and standards
for space flight.
- Need 5.1 - Regulations
- Need 5.1a - Local
- Need 5.1b - State
- Need 5.1c - Federal
- Need 5.1d - International
- Need 5.2 - Policies
- Need 5.2a - RIT Policies
- Need 5.2b - KGCOE Policies
- Need 5.3 - Industry Standards
- Need 5.1 - Regulations
Need 6 - The manual must include a
training program for student controllers.
- Need 6.1 - Nominal Scenarios
- Need 6.2 - Contingency Scenarios
Relative Importance of the Customer Needs
|Need||The Product||Needs to||Importance|
|Need 1.1||Mission Control Procedures||Include the nominal procedures for pre-launch activities||9|
|Need 1.2||Mission Control Procedures||Include the nominal procedures for launch activites||9|
|Need 1.3||Mission Control Procedures||Include the nominal procedures for post-launch activities||9|
|Need 2.1||Mission Control Procedures||Include the contingency procedures for pre-launch activites||9|
|Need 2.2||Mission Control Procedures||Include the contingency procedures for launch activites||9|
|Need 2.3||Mission Control Procedures||Include the contingency procedures for post-launch activities||9|
|Need 3.1||Mission Control Procedures||Include documentation of all tools and equipment needed for pre-launch activites||9|
|Need 3.2||Mission Control Procedures||Include documentation of all tools and equipment needed for launch activites||9|
|Need 3.3||Mission Control Procedures||Include documentation of all tools and equipment needed for post-launch activites||9|
|Need 4.1a||Mission Control Procedures||Include pre-launch testing to be performed and actions to be taken for passing criterion||9|
|Need 4.1b||Mission Control Procedures||Include pre-launch testing to be performed and actions to be taken for failing criterion||9|
|Need 4.2a||Mission Control Procedures||Include launch testing to be performed and actions to be taken for passing criterion||9|
|Need 4.2b||Mission Control Procedures||Include launch testing to be performed and actions to be taken for failing criterion||9|
|Need 4.3a||Mission Control Procedures||Include post-launch testing to be performed and actions to be taken for passing criterion||9|
|Need 4.3b||Mission Control Procedures||Include post-launch testing to be performed and actions to be taken for failing criterion||9|
|Need 5.1a||Mission Control Procedures||Take into account all local regulations||3|
|Need 5.1b||Mission Control Procedures||Take into account all state regulations||3|
|Need 5.1c||Mission Control Procedures||Take into account all federal regulations||3|
|Need 5.1d||Mission Control Procedures||Take into account all international regulations||3|
|Need 5.2a||Mission Control Procedures||Take into account all RIT Policies||3|
|Need 5.2b||Mission Control Procedures||Take into account all KGCOE Policies||3|
|Need 5.3||Mission Control Procedures||Take into accound all industry standards||3|
|Need 6.1||Mission Control Procedures||Include a training program for student controllers that simulates nominal scenarios||3|
|Need 6.2||Mission Control Procedures||Include a training program for student controllers that simulates contingency scenarios||3|
Useful Web Resources
You may find it helpful to review these web resources to better understand the METEOR Project and gain some insight on space flight.
Take a look at the METEOR Homepage for general information about the project along with the history of the design.
It may be helpful to browse the FAA Homepage for find some additional information on Federal Regulations related to space flight.
Research, design, and create an all encompassing launch electronic procedures manual. A training program that allows the students to practice pre-launch activities will also be delievered. See the "Detailed Course Deliverables" section for more specifics.
Customer and Sponsor Involvement
The team will be expected to carry out the vast majority of their interactions with the Team Guide (Dr. Patru), and the team consultant (Dr. Kozak). Dr. Patru (The customer) will be available for a series of meetings during the course of the project. Dr. Patru and will meet with a group of teams during the beginning of SD1 to lay out common goals, objectives, and philosophies for the sequence of projects being sponsored by RIT. It is anticipated that Dr. Patru and Dr. Kozak will meet with the team (or multiple related teams) for 2 hour meetings approximately 4 times during Senior Design I, and twice during Senior Design II. Dr. Patru and Dr. Kozak will participate with team communications electronically and through the web site as well.
- The design shall comply with all applicable federal, state, and local laws and regulations. The team's design project report should include references to, and compliance with all applicable federal, state, and local laws and regulations, most notably, Liscensing and Safety Requirements for Launch: Final Rule, 14 CFR Parts 401, 406, 413, et al. Please visit the FAA Homepage for more information on this regulation.
- The design shall comply with all applicable RIT Policies and Procedures. The team's design project report should include references to, and compliance with all applicable RIT Policies and Procedures.
- Wherever practical, the design should follow industry standard codes and standards (e.g. Restriction of Hazardous Substances (RoHS), FCC regulations, IEEE standards, and relevant safety standards as prescribed by IEC). The team's design project report should include references to, and compliance with industry codes or standards. ASME has a Communication Standard for Document Control Systems that will be used.
Project Budget and Special Procurement Processes
The EE Department through RIT funding has allocated $50,000 to this project track for AY06-07. While there is no pre-defined limit for each project within the track, each team in the track must demonstrate that their expenditures are in-line to satisfy both the requirements of the individual project, as well as to set the stage towards completion of the overall objectives of the track.
Each team will be required to keep track of all expenses incurred with their project, and to communicate with members of other teams in the track, to ensure that the overall track budget as well as the individual project budgets are being followed.
Being that the Mission Control Procedures Project is not very capital intensive, a budget of around $1,000 has be allocated for the project. The only equipment required is a computer in the EE Senior Design lab that is devoted to the METEOR Project.
Intellectual Property Considerations
All work to be completed by students in this track is expected to be released to the public domain. Students, Faculty, Staff, and other participants in the project will be expected to release rights to their designs, documents, drawings, etc., to the public domain, so that others may freely build upon the results and findings without constraint.
Students, Faculty, and Staff associated with the project are encouraged to publish findings, data, and results openly.
List of Metrics
The table below presents the metrics that will be used by the team to design against.
|Metric No.||Need Nos.||Metric||Importance||Units|
|1.0||ALL||Accuracy of procedures||9||N/A|
||ALL||A user submits a change to the procedures||9||N/A|
||ALL||Determine what team and faculty members have review privelages||9||N/A|
|2.0||ALL||Demonstrate fully functional document control system||9||N/A|
||ALL||Control access to writing privelages||9||N/A|
||ALL||Document what change was made||9||N/A|
||ALL||Document justification of change||9||N/A|
||ALL||Contains a review stage in which all changes are pending until accepted by a reviewer||9||N/A|
||ALL||Capable of recovering old revisions of the procedures||9||N/A|
||ALL||Demonstrates a lockout feature that prevents changes from being made without consent of Mission Controller||9||N/A|
||ALL||Attaches expiration dates to all printed hard copies of the procedures||9||N/A|
|3.0||ALL||Demonstrate ease of altering the presentation of the electronic system through a technical user demonstration||9||N/A|
|4.0||ALL||Demonstate that electronic system accurately presents procedures through a technical user demonstration||9||N/A|
Needs Related to the Metrics Using a Matrix
|Needs and Metrics||Metric 1.0||Metric 1.1||Metric 1.2||Metric 2.0||Metric 2.1||Metric 2.2||Metric 2.3||Metric 2.4||Metric 2.5||Metric 2.6||Metric 2.7||Metric 3.0||Metric 4.0|
Competitive Benchmarking InformationThere are a number of number of document control systems available today. The format of this software may be a good starting point.
- Benchmark 1
- PTC: WindChill - A document control system that includes storage and a change process for CAD drawings, Bill of Materials, etc. It is unlikely team will have access to the program, however the team leader has experience with the program.
- Benchmark 2
- Quality America Inc. Q-Pulse: Document Control Software - A Windows-based application for managing Document Control, corrective action and many other quality assurance issues. Offers a free 30 day trial.
- Benchmark 3
- NASA establishes Mission Control Procedures for every launch. If available, these procedures may be referenced in the design of the electronic system.
- Human safety takes precedence over all other design objectives.
- Building and facilities safety takes precedence over METEOR platform damage.
Detailed Course Deliverables
Note that this level describes an absolute level of expectation for the design itself, and for the hardware. However, the student team must also meet all requirements related to analysis, documentation, presentations, web sites, and posters, etc. that are implicit to all projects.
See Senior Design I Course Deliverables for detail.
- The following tasks should be completed by the end of SD1:
- Develop the structure of the electronic system
- Determine a method of document control
- Determine the structure of the training program
- The following tasks should be completed by the end of SD2:
- Populate pre-test, test, post-test, and contingency procedures for the balloon and vehicle recovery systems, the instrumentation platform, the environmental and centrifuge chambers, and the steel rocket
- Populate pre-launch, launch, post-launch, and contingency procedures for the balloon and vehicle recovery systems and the instrumentation platfrom
- Populate the training program for the balloon and vehicle recovery systems and the instrumentation platform
Preliminary Work Breakdown
The following roles are not necessarily to be followed by the team. It is merely to justify the number of students from each discipline. The student team is expected to develop their own work breakdown structure, consistent with the general work outline presented in the workshop series at the beginning of SD1. However, the customer requests a level of detail NO GREATER than weekly tasks to be completed by each student team member for the benefit of the other team members. The customer DOES NOT request any level of detail finer than one-week intervals, but will assist the team members if they wish to develop a finer level of detail to support their own efforts.
- Interface with all METEOR teams and serve as mechanical lead
- Structure of Procedures
- Interface with all METEOR teams and serve as electrical lead
- Structure of Training Program
- Interface with all METEOR teams
- Determine multiple presentation styles for electronic system
- Establish document control system
Grading and Assessment Scheme
Grading of students in this project will be fully consistent with grading policies established for the SD1 and SD2 courses. The following level describes an absolute level of expectation. The student team must also meet all requirements related to analysis, documentation, presentations, web sites, and posters, etc. that are implicit to all projects. Due to the uniqueness of this project, separate grading schemes have been established for both Senior Design I and Senior Design II.
Senior Design I
- Level D:
- The student team will deliver an electronic system that has the basic structure in place to allow the team to populate the information.
- Level C:
- The student team will deliver all elements of Level D PLUS: The student team will deliver a versatile electronic system with the structure in place to easily alter the presentation styles to which the system can be formatted. Several different presentation styles of the procedures will be delivered. The electronic system shall have a basic system for document control in place allowing the students to record the who, what, and when of changes that have been made to the procedures.
- Level B:
- The student team will deliver all elements of Level D and C PLUS: The student team will deliever additions to the document control system in that it will include an automatically updating database for actions taken and a secure login. The basic structure of the training program will be in place to allow the students to populate the information.
- Level A:
- The student team will deliver all elements of Level D, C, and B PLUS: A versatile electronic system that integrates the procedures with the training program. Several different presentation styles of the training program will be delivered.
Senior Design IIBelow is a chart representing the grading scheme for Senior Design II. In order to earn a D, all areas marked D must be populated. To earn a C, all areas marked D and C must be populated and so on.
|Balloon||Recovery Vehicle||Instrumentation Platform||Environmental Chamber||Centrifuge Chamber||Steel Rocket||Rocket Stages 1-4||PicoSatelite||Fully Integrated System|
Three-Week SDI Schedule
The first 3 weeks of Senior Design I is considered to be the concept development phase.
- Team Introduction - Get to know the team. Introduce yourself, your major, your strengths and how you think you will be able to benefit the team
- Project Introduction - Review the Product Readiness Package and become familiar with the Track, Family of Projects, and the Project itself.
- Team Values and Norms - Discuss what is expected from each team member in terms of attendance, communication, and individual task completion.
- Discuss prior commitments of individual group members and outline a schedule for Senior Design I.
- Assign Initial Tasks - Become familiar with the Edge website, understand customer needs and engineering specifications, and conduct research on the proposed design, including CSS, SVN, and CVS.
- Finalize the team values and norms by establishing a roles and responsibilities document that also includes team meeting times for the quarter.
- Create a 10 week schedule outlining the tasks to be completed, milestones to meet, and work breakdown among the team.
- Begin to brainstorm ideas for the structure of the electronic system, the structure of the training program, and the presentation style of the electronic system.
- Research benchmarks for presentation styles
- Develop a method to validate the design
- Evaluate the initial concepts for the structure of the electronic system, structure of the training program, and the presentation style of the electronic system
- Determine the structure of the electronic system
- Determine the structure of the training program
- Identify at least 3 presentation styles for the electronic system
|Prof. Patru||EE||Faculty Guide/Coordinator/Mentor/Customer||Yes|
|Prof. Kozak||ME||Faculty Consultant||Yes|
|Prof. Amuso||EE||Faculty Consultant||Yes|
|EE Senior Design Lab||EE 09-3xxx||Work Space/Storage||Yes|
|METEOR Computer||EE Senior Design Lab||PC devoted to METEOR Project||Yes|
The team members will be expected to procure the materials needed for the project, excluding the following:
|FAA Final Rule Liscensing and Safety Requirements||Faculty Guide||Federal Space Flight Regulations||Yes|
Home | Launch | Documents | Training | Misc | Help