Download
1 / 27
270 likes | 431 Views
ELM 4702 Electromechanical Projects II Spring 2012. Course Outcomes To develop the skills to function effectively as a contributing member of a technical design team
E N D
ELM 4702 Electromechanical Projects II Spring 2012 Course Outcomes • To develop the skills to function effectively as a contributing member of a technical design team • To develop an aptitude for researching, organizing and evaluating concepts and ideas in order to develop a solution to a technical problem • To understand how to integrate mechanical, electrical, and software components in a functional system design and to communicate the system concept. • To be capable of planning and managing a technical project through group meetings, work plans and cost budgeting. • To effectively communicate the technical functionality and development plan of an engineering design through oral presentations and written documentation.
Assignments and Grading • Design Review Presentations (team) (10% x 2) • Project Tasks (WBS, System Diagram, etc.) (team) (10%) • Final Design Presentation (team) (10% ) • Prototype Demonstration and Subsystem Tests (team and indiv.) (15%) • Web Site and Electronic Documentation (team) (10%) • Engineering Notebook and Design Records (individual) (15%) • Engineering Design Report (individual) (10%) • Teamwork, Leadership, Individual Scope and Challenge* (individual) (10%) • *May be considered as a general weighting factor
Elements of a Project Plan • Problem Statement • A clear written statement that defines the problem to be solved • Solution • Written statement • System overview • Defined functionality - system diagram, state diagram, process flow chart • Concept diagrams for different subsystems • Specific components identified • Operating specifications, limitations, performance expectations • Schedule • Work breakdown structure • Timeline schedule (for example, Gantt Chart) • Major milestones to accomplished (with target dates) • Responsibilities • Assignments for engineering tasks • Assignments for management tasks • Regular meeting schedule • Cost • Bill of materials for subsystems • $ costs for major components, materials • Man hours requirements for work to be done (designing, mechanical drawings, manufacturing, software coding, electrical circuit assembly, testing • Over-all budget
Work Breakdown Structure (WBS) A list or graphical representation of the different areas and associated tasks and milestones that will need to be completed to successfully design, build, and test a new product or system.
Lannie Mindy Adam Dave Turret Turret X-Y Pen Move Base/ Frame Pen Ext/ Retract Stepper Motor Solenoid ACME Threaded Rod 3 Jaw Clamp Base Spring Micro Stepper Motor Power Supply Power Req. Letters Micro Mount Boards
System Mechanical Software Electrical PC Driver UART Supply Turntable R Control Z Control MCU Front End User Interface Rack & Pinion Stepping & Timing MCU Rubber Mat Acme Rod Driver Bearings Acme Nut Servo UART COM Back End User Interface Drive Shaft Carriage Belt Stepper Stepper
Technical Design Notebooks • A design notebook's usefulness is aided by occasional "time outs" from the scribbling of notes and calculations. • Assessment of the state of the project in the form of a thoughtful paragraph or annotated diagram can significantly improve the documentation of the design process. The following examples are from: www.me.utexas.edu/sdp/students/notebook.php
Technical Notebook The technical notebook is critical to the documentation process and should be used to keep track of basic communication as well as a proper record of the design process. For this course each student must keep a bound engineering lab bookthat includes notes from: group meetings, calculations, supplier contacts, notes of conversations with contacts, doodles, calculations, designs, test results, etc. Each student should also keep three-ring binder for course handouts, printed information, any other information developed on paper and gathered during research and design and the other stages of prototype development.
When running experiments, describe the planning undertaken ….
If the data requires some explanation, write a post-test interpretation guide….
When designing a part or a system, explain the reasoning behind your decisions…. Example 1
Technical Design Notebooks • Technical notebooks will be checked weekly • Action items will be identified and noted • Each week progress on defined action items and over-all project work, as evidenced through notebook and other records, will be evaluated.
Upcoming Tasks • Friday 16 January 2012 • System Diagram • WBS • Website • (These need to identify the subsystems and the mechanical, electrical, software elements for each) • Friday 20 January 2012 • Budget and Schedule (team) • Monday 23 January 2012 • Subsystem Concept Diagrams (from each team member) • * Post all assignments for review on website
