Instructor: Dr. Joseph A. Morgan, P.E. Office: F111B Telephone: 979-575-0128 Email: email@example.com
ENTC 420. Engineering Technology Projects. (2-4). Credit 3. I, II
Team approach to analysis and design of basic industrial-level projects; use of standard components and proven design techniques. Prerequisites: ENTC 419; must be taken semester of graduation or by approval of instructor; admitted to major degree sequence(upper-level) in engineering technology.
The ESET 420 Course Syllabus (available at howdy.tamu.edu) should be downloaded and reviewed. Students will have the opportunity to ask any clarification questions during the second class period. In addition, students should complete the Lab Safety requirements.
ESET 420 is the second in a two-course Capstone Design sequence. Design teams complete final hardware/software designs, implementation, fabrication, testing, demonstration, presentation, and documentation of a fully functional prototype. The teams will conduct weekly project management review meetings, and schedule and conduct periodic technical meetings with project stakeholders. Two formal presentations are required: 1) Critical Design Review, and 2) Final Project Presentation. A demonstration of the working prototype is required that demonstrates that all functional requirements and performance specifications have been achieved. A formal Final Project Report must be submitted that documents all design and testing results.
The goal of ESET 420 is to provide students with the opportunity to integrate their educational experiences into a project-oriented design and development effort while facilitating the practice of applied engineering. To obtain experience with solving project related problems in a team environment under resource constrains. Projects will use standard components and proven design techniques, and require hardware/software design, system integration, testing and verification, and technical documentation/presentations. To successfully complete the ESET 420 requirements, each team must reduce their design to a fully functional pre-production prototype that is ready for operational test and evaluation. The prototype must be demonstrated and documented in a professional manner. Technology development accomplished by Capstone teams will be archived in a Knowledge Base that will be accessible by subsequent teams to improve design processes and reduce development time.
In addition to all of the project deliverables outlined and described in the Formal Technical Proposal, a number of course deliverables are also required. These are:
1. System Design Process Document
2. Project Notebook
3. Weekly Progress Reports and TAT Meetings
4. Critical Design Review (CDR) presentation
5. Final pre-production working prototype ready for operational testing
6. Final Project Demonstration
7. Final Project Presentation
8. Final Project Technical Report
In addition, each team member must maintain an individual engineering journal/notebook.
Before submitting your form, each team must become familiar with the 3D Printer operation by veiwning the following video:
Capstone teams will report on the progress of their project periodical throughout the implementation phase. Information is provided to facilitate these presentations and demonstrations.
TECHNICAL ASSISTANCE TEAM (TAT) MEETINGS
Each week, Capstone Design teams will provide project management/technical updates on their projects. Teams must use the TAT Meeting Slide format Example of TAT Meeting Slides as a minimum, but can augment these slides, if appropriate. All team members are required to attend TAT meetings and to participate in them. A different team member will lead the TAT Meeting each week so that all team members have equal opportunity to present project materials. Although a majority of the presentation will be made by one team member, each member will report on his/her own accomplishments.
Presentations must start on time and be clear, concise and crisp. The Capstone teams are responsible for ensuring that all support equipment (camera, LCD projector, conference phone, etc)is functioning properly. If a team is not prepared to begin at its scheduled time, the TAT meeting will be cancelled which will negatively impact the team project grade.
The Capstone Project Notebook must be created and maintained by each Capstone team. The Notebook must be easily accessible by all stakeholders. Although historical files may be included, the organization of the notebook should intuitively communicate the most current documents.
Periodically, TAT meetings will be video taped. Team members should dress in business casual/team shirts for TAT meetings.
Every three weeks Capstone Design teams will demonstrate the current level of implementation that has been achieved. The demonstrations are meant to give the stakeholders an overall view of current status of the hardware and software development as well as a good understanding of testing, validation and documentation. Teams should strive to demonstrate the full capability of their design efforts.
Each team should begin the demonstration with an overview of what is going to be demonstrated, the overall sequence of events that will be followed including what the stakeholder should observe. The team should conclude the demonstration with a summary of what the demonstration has indicated in terms of completing a fully functional, pre-prodcution prototype.
CRITICAL DESIGN REVIEW
Week 7 will be used for Critical Design Reviews. This is the first of two formal technical presentations during Capstone II. Each team will be given up to 45 minutes to cover all aspects of their final design for project stakeholders review and approval. All team members must be present for all CDR presentations. Each CDR presentation should be subdivided equally among all team members. The ENTC 420 CDR Presentation Memorandum provides format/content of the CDR presentation.
Capstone teams will grade all other team presentations. This responsibility should be taken seriously and completed in a professional manner. Team managers will consolidate grading from each of his/her team members and submit grading results to the course director in soft copy format. The ESET 420 CDR Presentation Requirements should be used by all ESET 420 students to grade presentations given by other teams.
FINAL PROJECT REQUIREMENTS
Each Capstone project must produce a fully functional, pre-production prototype that is properly packaged to meet all functional requirements and performance specifications. The prototype should be ready for operational testing. Documentation of the project design and implementation efforts includes:
Prototype Demonstration: The Capstone Team must conduct a prototype demonstration that clearly shows that all functional/performance requirements have been met. The team will normally make a short presentation prior to the actual demonstration to outline the steps that will be taken and the expected results that will be achieved. Generally, a demonstration check list is provided to project stakeholders at the demonstration presentation.
The capstone team should ensure that all aspects of the demonstration will work correctly by doing several dry runs prior to the actual stakeholder demonstration. All aspects of the demonstration should be ready to go so that the demonstration can be conducted in a timely and efficient manner. If any type of failure or other problem is encountered during the demonstration, the demonstration will be restarted. Problems/failures are justification to terminate the demonstration. Generally plan for a minimum of an hour to successfully complete the Demonstration.
Project Presentation: Once a successful demonstration has been conducted by the Capstone team, a detailed technical project presentation can be scheduled and conducted. The Capstone team should plan on 2.5 to 3 hours for this formal presentation. Questions will be asked throughout the presentation and guest can be invited by the team or any of the stakeholders involved in the project. Generally, discussions will create additional information or inclusion of information for the final documentation. The team needs to record all of these action items and ensure they are addressed in the final documentation. Final Project Presentation Guidelines should be used to ensure all required elements are included
Project Documentation: Following the demonstration/presentation and the successful completion of any actions generated from these two activities, the Capstone team must submit a formal Final Project Report. Final Report Guidelines outlines the report that should also cover all aspects of the design and testing of the prototype.
Project Wrap-up: The Capstone team will wrap up the project with a meeting with the Capstone Course Director. The following items are included in the wrap-up meeting: