P07107: Mission Control Procedures Aerospace Systems and Technology Dr. Dorin Patru Faculty Guide Alberto Lopez Samper ISE Jeff Sullivan EE Jon Klenovic ME

MSD II Project Review Outline Project Description Customer Needs Site Design Process Finalized Site Design Procedure Design Process Finalized Procedure Design Strengths/Weaknesses of Design Future Improvements

Project Description Justification Lack of structure Inefficient use of time Unforeseen issues Facilitate setup process and streamline launch Reduce errors

Project Description Pre-launch, Launch, Post-Launch Procedures Tools and Equipment Nominal and Contingency Procedures Launch Training

Detailed Customer Needs Nominal procedures for pre-launch, launch and post-launch activities Contingency procedures for pre-launch, launch, and post-launch activities Documentation of all tools and equipment needed for pre-launch, launch, and post-launch activities Pre-launch, launch, and post-Launch testing to be performed and actions to be taken for a passing criterion Pre-launch, launch and post-launch testing to be performed and actions to be taken for a failing criterion Take into account all local, state, federal, and international regulations Take into account all RIT and KGCOE Policies Take into account all industry standards Training program for student controllers that simulates nominal and contingency scenarios

Design Process Presentation of Information: Software Options: Paper, Electronic, or Electronic with hard copy Software Options: Data basing and meta data, Web based system, Versioning software, or Integrated systems

System Selection Why EDGE? Software support Infrastructure in place Student and faculty knowledgeable of system Available for use at no cost Built-in features met most of customer needs Table of contents, user types, review & lock-out process Ease of use

Benchmarking Tab format Sidebar outline Series of hyperlinks Tab across the side Table of contents style Icons

Organizational Hierarchy Finalized Site Design Main Tabs Organizational Hierarchy

Finalized Site Design: Features Main Tabs and Subsections Location Bar Table of Contents: Showing Breakdown of Procedures

Finalized Site Design: Features Check Boxes Pictures Back to Top Quick Link

Procedure Development Process Meeting with Individual Teams Attending Testing Examining Previous Documentation

Finalized Procedure Design Land based, Sea based, and Testing Multiple procedure types Tools & Equipment, Pre-launch, Launch, Post Launch Director & Individual Procedures

Finalized Procedure Design

Finalized Procedures Design Director Procedures Comprehensive procedures for team leader and faculty guide Individual Procedures Student and task specific procedures

Finalized Procedures Design Check Boxes: to ensure no procedures have been missed Student Call-outs: assigns students to specific tasks Error Log: documentation of contingencies

Finalized Procedures Design Individual Procedures contain the necessary tools, equipment, and tasks to complete their assigned responsibilities

Strengths of Design Procedures are easy to use Clear organization Streamlines testing by accounting for all equipment Eliminates errors Increases efficiency of launch participants Robust Room for expansion in procedures and software Withstands the test of time

Weaknesses of Design Updates to the Edge Site planned for Summer 2007 Could affect Mission Control Procedures site format or coding Did not meet following engineering specifications: The ability to recursively print The ability to work off-line Procedures lack detail Formatting dependent on web browser Internet Explorer vs. Mozilla Firefox

Future Considerations Ability to develop procedures Accessibility of other teams Course deliverable – Mission Procedures Organization of equipment Store procedures in a stand alone system Software improvements Search capabilities Recursive printing Printing break points

Questions