Design Document

Team: <>, Project: <>

Design Document
Team: WCGI Project: Rivets Retrieval System Date: Spring 2012

Design Document

Team: <>, Project: <>

1 Table of Contents
1 2 3 4 Table of Contents ....................................................................................................................... 2 Revision History ........................................................................................................................ 3 Design Status Summary ........................................................................................................... 4 Project Charter ........................................................................................................................... 5
4.1 4.2 4.3 4.4 4.5 Description of the Community Partner ...........................................................................................5 Stakeholders .........................................................................................................................................5 Project Objectives ...............................................................................................................................5 Outcomes/Deliverables .......................................................................................................................5 Overall Project Timeline ....................................................................................................................5 Phase Six ...............................................................................................................................................6 Phase Five .............................................................................................................................................7 Phase Four ............................................................................................................................................8 Phase Three ..........................................................................................................................................9 Phase Two .......................................................................................................................................... 10 Phase One .......................................................................................................................................... 12

Overall Project Design ............................................................................................................. 6

5.1 5.2 5.3 5.4 5.5 5.6

Semester Documentation (current semester) ................................................................ 14

6.1 Team Member ................................................................................................................................... 14 6.2 Current Status and Location on Overall Project Timeline ....................................................... 14 6.3 Goals for the Semester ..................................................................................................................... 14 6.4 Semester Timeline ............................................................................................................................ 14 6.5 Semester Budget ............................................................................................................................... 14 6.6 Transition Report ............................................................................................................................. 15 6.6.1 Summary of Semester Progress / Comparison of Actual Semester Timeline to Proposed Semester Timeline ................................................................................................................................................................. 15 6.6.2 Draft Timeline for (next semester) and Relationship to Overall Project Timeline ..................... 15

Past Semester Archive ........................................................................................................... 16

7.1 Past Semester 1 .............................................................................................................................. 16 7.1.1 Past Team Members ........................................................................................................................................... 16 7.1.2 Past Timeline.......................................................................................................................................................... 16 7.2 Past Semester 2 .............................................................................................................................. 16 7.2.1 Past team Members ............................................................................................................................................ 16 7.2.2 Past Timeline.......................................................................................................................................................... 16

Last revised 8/20/2011

Design Document

Team: <>, Project: <>

2 Revision History
Date 01/27/2012 02/01/2012 Author Jin, Kimi Aaron Revisions Made (5.6)Phase One, (6.1)Team members,(6.4) Timeline (4.1-4.5)Created Project Charter, (6.4)Updated/Revised Timeline, (6.2,6.3,6.5)Other Sections of Documentation Created/Updated (4.5) added goals for milestones. (5.6)Added narrative sentences to the evidences. (6.4) Revised the table to fit into one page. (6.5) updated the semester budget. Included what is done to date in Phase Two (5.5), and included its current narrative as well as the narrative for Phase One (5.6)

02/03/2012

Jin, Kimi

02/15/2012

Aaron

Last revised 8/20/2011

Design Document

Team: <>, Project: <>

3 Design Status Summary

Phase 6: Service / Maintenance Status: Gate 6: Project Partner and Advisor approve continued fielding of project. If not, retire or redesign. Date of Advisor approval:

Phase 5: Delivery

Status:

Gate 5: Continue if Project Partner, Advisor and EPICS Admin agree that project is ready for delivery! Date of Advisor approval:

Phase 4: Detailed Design

Status:

Gate 4: Continue if can demonstrate feasibility of solution (is there a working prototype?). Project Partner and advisor approval required. Date of Advisor approval:

Phase 3: Conceptual Design

Status:

Gate 3: Continue if project partner and advisor agree that solution space has been appropriately explored and the best solution has been chosen. Date of Advisor approval:

Phase 2: Specification Development

Status:

Gate 2: Continue if project partner and advisor agree that you have identified the right need, specification document is completed and no existing commercial products meet design specifications. Date of Advisor approval:

Phase 1: Project Identification

Status:

Gate 1: Continue if have identified appropriate EPICS project that meets a compelling need for the project partner. Date of Advisor approval:

Last revised 8/20/2011

Design Document

Team: <>, Project: <>

4 Project Charter
4.1
y y y y y

Description of the Community Partner

Wabash Center Greenbush industries is the project partner WCGI employs mentally and physically handicapped individuals for factory/assembly work Fills contracts from third parties, such as Caterpillar. Ideal goal is to have workers and management benefit from final product Final product will be delivered to WCGI for intended use by workers

4.2
y y

Stakeholders
Project will ideally help WCGI run more smoothly, helping companies receive orders more quickly Workers, managers, and indirectly third parties with contracts have vital interest. They are benefiting from higher efficiency and safety.

4.3
y y

Project Objectives
Motivation for the product is the need for it by WCGI as well as the benefit of the workers who might be better off if they are able to work more efficiently, and thus make better wages. Our product will help WCGIs mission of helping their employees be productive and make a living by enabling them to do their job in a more safe and efficient manner.

4.4
y y

Outcomes/Deliverables
The result of the project should be a product which addresses the issue of rivets being strewn on the factory floor more efficiently than the current model. Ideally the project will be fully deliverable, however future teams may be tasked with improving the design after seeing how it is implemented.

4.5
y y

Overall Project Timeline

Project needs to be delivered by week 9 Milestones o Design Review 1-week 8 o Design Review 2- week 14 o End of Semester Documentation Project intended to be completed by design review 2 to focus on design review and final documentation.

Last revised 8/20/2011

Design Document

Team: <>, Project: <>

5 Overall Project Design

5.1 Phase Six
Status: Evidence can be found: Phase 6: Service / Maintenance y Evaluate performance of fielded project y Determine what resources are necessary to support and maintain the project Gate 6: Project Partner and Advisor approve continued fielding of project. If not, retire or redesign. Advisor approval:

Decision:

Rationale summary:

Yes / No

Date:

Narrative of Service/Maintenance phase of design.

Last revised 8/20/2011

Design Document

Team: <>, Project: <>

5.2

Phase Five
Status: Evidence can be found:

Phase 5: Delivery

Goal is to refine detailed design so as to produce a product that is ready to be delivered! In addition, the goal is to develop user manuals and training materials. y Complete deliverable version of project including Bill of Materials y Complete usability and reliability testing y Complete user manuals/training material y Complete delivery review y Project Partner, Advisor, and EPICS Admin Approval Gate 5: Continue if Project Partner, Advisor and EPICS Admin agree that project is ready for delivery! Advisor approval:

Decision:

Rationale summary:

Yes / No

Date:

Narrative of Delivery phase of design.

Last revised 8/20/2011

Design Document

Team: <>, Project: <>

5.3

Phase Four
Status: Evidence can be found:

Phase 4: Detailed Design

Goal is to design working prototype which meets functional specifications. y Bottom-Up Development of component designs y Develop Design Specification for components y Design/analysis/evaluation of project, sub-modules and/or components (freeze interfaces) y Design for Failure Mode Analysis (DFMEA) y Prototyping of project, sub-modules and/or components y Field test prototype/usability testing Gate 4: Continue if can demonstrate feasibility of solution (is there a working prototype?). Project Partner and advisor approval required. Advisor approval: Decision: Rationale summary:

Yes / No

Date:

Narrative of Detailed Design phase of design.

Last revised 8/20/2011

Design Document

Team: <>, Project: <>

5.4

Phase Three
Status: Evidence can be found:

Phase 3: Conceptual Design

Goal is to expand the design space to include as many solutions as possible. Evaluate different approaches and selecting best one to move forward. Exploring how. y Complete functional decomposition y Brainstorm several possible solutions y Prior Artifacts Research y Create prototypes of multiple concepts, get feedback from users, refine specifications y Evaluate feasibility of potential solutions (proof-of-concept prototypes) y Choose "best" solution Gate 3: Continue if project partner and advisor agree that solution space has been appropriately explored and the best solution has been chosen. Advisor approval: Decision: Rationale summary:

Yes / No

Date:

Narrative of Conceptual Design phase of design.

Last revised 8/20/2011

Design Document

Team: <>, Project: <>

5.5

Phase Two
Status: Evidence can be found:

Phase 2: Specification Development

Goal is to understand what is needed by understanding the context, stakeholders, requirements of the project, and why current solutions dont meet need, and to develop measurable criteria in which design concepts can be evaluated. Current system uses broom to sweep rivets from floor of factory. WCGI Factory employing disabled workers to do contracted work 1 draft each of Vacuum, Scooper, and Magnet systems TBD Aaron - TBD

y Understand and describe context (current situation and environment) y Create stakeholder profiles

Aaron - TBD

y Create mock-ups and simple prototypes: quick, low-cost, multiple cycles incorporating feedback

All members, TBD

y Develop a task analysis and define how users will interact with project (user scenarios) y Identify other solutions to similar needs and identify benchmark products (prior art) y Define customer requirements in more detail; get project partner approval y Develop specifications document

Vacuums, brooms, more TBD TBD Currently in process, TBD TBD Decision:

y Establish evaluation criteria Gate 2: Continue if project partner and advisor agree that you have identified the right need, specification document is completed and no existing commercial products meet design specifications. [This includes their agreeing that you have captured and documented the critical requirements and specifications for this project]

Rationale summary:

Last revised 8/20/2011

10

Design Document Advisor approval: Yes / No

Team: <>, Project: <> Date:

Narrative of Specification Development phase of design.

With a few questions remaining unanswered from our project partner, we moved into phase two hesitantly. We developed three potential basic designs based on what we knew to be true about the criteria and constraints. We developed a vacuum, scooper, and magnetic system. The vacuum would be a modified traditional vacuum to handle metal pieces and possibly sort them from dirt. The scooper would scoop up the rivets and sort them using a ramped scooping mechanism. The magnet would be a nonferrous electromagnet designed to pick up aluminum, then drop them when electricity was disconnected (sorting is deemed unnecessary by this method). Basic specifications include compliance, accessibility, enjoyment, ease of use, space constraints, and other factors which need to be better defined. As of this writing, we have completed this much thus far, but have much to do in phase two. We need to provide proper documentation of a few things, mainly models and designs not found in our normal journals.

Last revised 8/20/2011

11

Design Document

Team: <>, Project: <>

5.6

Phase One
Status: Evidence can be found:

Phase 1: Project Identification

Goal is to identify a specific, compelling need to be addressed y Conduct needs assessment (if need not already defined) A system to pick up rivets (possibly sort rivets); be easy and fun to use. Disabled workers in a manufacturing industry (WCGI). Rivets are dropped on the floor and need to be picked up, and workers hated doing it. Stakeholders should be able to use it easily and help them pick up rivets in a more safe, efficient and fun way. 10 weeks Decision: Rationale summary: Kimis notebook P13. Jins notebook P3. Defined purposes and requirements. Site Visit to WCGI on 1/20/2011. Aarons Notebook TBD (electronic, needs to be copied) Site Visit to WCGI on 1/20/2011. Aarons Notebook TBD (electronic, needs to be copied) Employees dont like the current system for picking up the rivets. Site Visit to WCGI on 1/20/2011. Kimis notebook P13. Jins notebook P3.

y Identify stakeholders (customer, users, person maintaining project, etc.)

y Understand the Social Context

y Define basic stakeholder requirements (objectives or goals of projects and constraints)

y Determine time constraints of the project Gate 1: Continue if have identified appropriate EPICS project that meets a compelling need for the project partner [This includes a Project Charter] Advisor approval:

Yes / No

Date:

Narrative of Project Identification phase of design.

Following our first visit to WCGI we developed a project to address the issue of rivets being left on the factory floor. Workers had to use a broom to pick these up, and the workers did not enjoy the Last revised 8/20/2011 12

Design Document

Team: <>, Project: <>

task. We worked to assess all information we could about the project, but hit several speed bumps with scheduling in regards to another site visit, and fell back on simply contacting the project partner with questions. As of this writing, no response has been received. We were able to complete much of phase one without this, including scheduling, planning, and laying out knowns and unknowns, and moved into phase two with what information we had. We determined a project which had many criteria and constraints, the most important of which being that it needed to pick up rivets, possibly sort them, be as efficient or more efficient than the current system, and be fun to use.

Last revised 8/20/2011

13

Design Document

Team: <>, Project: <>

6
6.1

Semester Documentation (current semester)

Team Member

Project leader: Aaron Whiteman. Members: Jin Li, Daniel Shin, Yuanzhi Huang.

6.2

Current Status and Location on Overall Project Timeline

Project is in its first semester. All timelines have the projection of a first-semester delivery, however the actual status at the end of the semester may require adjustment if not delivered.

6.3

Goals for the Semester

Semester goals are to create a product which is more effective and fun to use than the current model at picking up rivets from a factory floor.

6.4

Semester Timeline
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Has been extended to include all 15 weeks. Goals Research &Information Gathering Brainstorm solutions Prototypes Weeks

Choose specific solution Buying Materials Build the system Delivery & Adjustment

Last revised 8/20/2011

14

Design Document

Team: <>, Project: <>

6.5

Semester Budget

$80-mechanical, $80-electrical, $20 prototyping. Total - $180

6.6

Transition Report

6.6.1 Summary of Semester Progress / Comparison of Actual Semester Timeline to Proposed Semester Timeline Compare actual semester timeline to proposed semester timeline (if different). What aspects varied the most from proposed to actual? Discuss the progress made during the current semester, including any pitfalls that you encountered that would be helpful for future teams to avoid as well as any best practices you found that helped you to advance the status of the project or work well as a team. 6.6.2 Draft Timeline for (next semester) and Relationship to Overall Project Timeline Based on the work completed this semester, the work left to be completed, and the overall project timeline, create a draft timeline for the following semester.

Last revised 8/20/2011

15

Design Document

Team: <>, Project: <>

7 Past Semester Archive

7.1 Spring 2012

7.1.1 Past Team Members List team members from the appropriate semester including their roles and their contact information. 7.1.2 Past Timeline Paste in previous semester timelines to indicate what was accomplished during this semester.

7.2

Past Semester 2

Retitle this heading to reflect the appropriate semester (e.g. Fall 2010) 7.2.1 Past team Members List team members from the appropriate semester including their roles and their contact information. 7.2.2 Past Timeline Paste in previous semester timelines to indicate what was accomplished during this semester.

Last revised 8/20/2011

16