MSD END-STATE EXPECTATIONS Todays Agenda 7:30-7:59 Continental Breakfast & Reconnecting 8:00 Review of Agenda Workshop with students EH 8:02-8:30 MSD 2 Summary of Expectations- EH 8:30-9:00 Problem Solving Process & Tracking- WN Nowak 9:00-9:15 Break 9:15-10:45 WORKSHOP: Students will take action on some/all of the key deliverables for Phase 1 MSD2 exit. Guides to facilitate, examine state of deliverables, and provide feedback. Two major reasons for the MSD2 kickoff workshop are the 5 week layoff only 2 weeks in phase 1 for MSD2. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations The Journey MSD I & II 30 weeks (6 credits) MSD I: Project definition and design MSD II: Prototype development and delivery Design & delivery process defined by faculty Five 3-week phases each semester Review and grading after each phase Students take ownership utilize process methods & tools to define, develop and deliver expected outcomes, implement peer reviews All engineers utilize appropriate analysis tools to support engineering decision making MSD End State Expectations MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD I WksPhaseDeliverables 1-3 Problem Definition Customer Requirements, Engineering Requirements (& Relationship Diagram), Project Plan 4-6 System Design Functional Decomposition, Concepts Developed, Engineering Analysis to support critical technology, Architecture, Test Plan, Risk Assessment, Update Project Plan 7-9 Subsystem Design (High Technical Risk) Requirements Flowdown, Engineering Analysis to demonstrate feasibility of critical subsystems, Update Test Plan, Update Risk Assessment, Update Project Plan Detailed Design (High & Med Technical Risk) Design Output (drawings, schematics, layouts, algorithms, BOM), Engineering Analysis to support Detailed Design, Update Test Plan, etc Complete Design (Low Technical Risk) Complete Design Output (), Design Package Completion, Ready to order long lead time parts 16MSD I WrapupGate Review Readiness for MSD II MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD II WksPhaseDeliverables 1-2 Subsystem Level Prep/Build & Action Items (if failed Gate Review) Test Bench setup, simulation, analysis, Create Problem List, Update Test Plan & Project Plan 3-5 Build/Test/Integrate Subsystem Level Testing, simulation, analysis, Subsystem Function Demo, Update Problem Status, Test Plan, Project Plan 6-8 Build/Test/Integrate Subsystem & System Level Execute overall Test Plan to evaluate performance, Preliminary Integrated System Demo, Update Problem Status, Conference Paper Outline 9-11 Build/Test/Integrate System Level Continue full system testing for reliability, Full Integrated System Demo with Customer, Project Documentation Complete Verification & Validation Project Complete Complete full system testing for reliability Project Complete handoff obligations to Customer Complete Paper & Poster, ImagineRIT 15Final Presentation & ReviewCompletion of MSD II MSD 2 KICKOFF 28 JAN 2014 MSD 2 GRADING Emphasis MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations Project Completion 70% Process Followed and Tool Usage 20% Personal Contribution to Team 10% MSD 2 GRADING RUBRIC MSD 2 KICKOFF 28 JAN 2014 Grade Definitions *Letter Grade ScoreBrief DescriptionLonger Description A+100 Outstanding (Work is high quality) - Deliverables completed and high quality; - Executed process and used process tools very effectively; - Took ownership of the project by consistently demonstrating initiative, persistence, and process discipline. A95 A-92 B+88 Good to Very Good (Work is satisfactory) - Deliverables completed and acceptable; - Executed process and used process tools satisfactorily; - Took some ownership of the project by demonstrating periodic initiative, persistence, and process discipline. B85 B-82 C+78 Minimally Acceptable (Most work is satisfactory) - Deliverables minimally acceptable but incomplete in some areas; - Process haphazardly followed, not intelligently or efficiently applied; - Lacked ownership of the project by seldom demonstrating initiative, persistence, or process discipline. C75 C-72 D+68 Unacceptable (Less than half of the work is satisfactory) D65 D-62 F55 Disaster (Little to none of the work is satisfactory) Guide reserves the right to assign a score lower than 55 if less than 55% of the work has been done. Grade Expectations B is a good to very Good outcome A is an outstanding Outcome. (It is not the Default) MSD End State Expectations MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations Project Completion: 70% Deliver a working Prototype achieves all requirements & satisfies customer Complete project documentation: Specific Documentation per Customer. eg Organized & Concise Project Documentation on EDGE Technical Paper per MSD / Design Contest Standards Poster for ImagineRIT14; possible update Enter a Student Design competition Mycourses info ARM, TI, ASME. Prof. Slack, Debartolo, Becker- Gomez Participation in Imagine RIT 2014 Final Public presentation & Gate Review MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations Project Completion: 70% Team must Deliver a Working Prototype that achieves all requirements & satisfies the customer. This is by far the most challenging part of MSD. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations Deliver a Working Prototype: You may have to make some of your parts MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations Deliver a Working Prototype: You must TEST at the Subsystem Level. You must resolve your problems as they reveal themselves. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations Deliver a Working Prototype: You must TEST at the SYSTEM Level. You must resolve your problems as they reveal themselves. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations Deliver a Working Prototype: You will demonstrate ImagineRIT MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations Process Followed & Tool Usage: 20% Grade Project Plan was actively followed and updated: Project Progress Reviews were conducted in w2, w5, w8, w12, and w15 Project progress is communicated via demonstrations, test data, and traceability/achievement of requirements. Problem Identification, Tracking & Resolution Process demonstrated: Team created & utilized a problem tracking system Initial problem entries came from technical risk list, assessment of requirement achievement, and action item list. New problems were entered, processed, and resolved as the Truth revealed itself. Team demonstrated good decision making habits on critical problems Continue to use your ENGINEERING Logbooks; document your technical project journey. Team aggressively drove build, and test activities to reveal any shortfalls as early as possible. No procrastination!!!! MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations Personal Contribution to Team: 10% Grade Own your project: Success and completion are important to you Be a problem solver Take a moment and THINK! Identify the actionable root cause, follow the process and solve the problem in a thoughtful manner. Respond to challenges and disappointments Expect constructive criticism Be a good team mate Respect others; align your words with your actions. Expectation is that all members contribute equally. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations Personal Contribution to Team: 10% Grade Own your project: Success and completion are important to you Be a problem solver Take a moment and THINK! Identify the actionable root cause, follow the process and solve the problem in a thoughtful manner. Respond to challenges and disappointments Expect constructive criticism Be a good team mate Respect others; align your words with your actions. Expectation is that all members contribute equally. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 1 Post Mortem Updated MSD 2 Plan BOM Review: Problem ID, resolution & tracking process Test Plan & Test Bench MSD 2 Phase 1 Deliverables MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Phase 1 Deliverables MSD 1 Post Mortem: Current state Design Proposal is complete and approved with a few problems. Critical parts ordered. Team worked well together with some exceptions. Why worry about MSD 1? Kaizen- continuous improvement What could we have done better? Muda- waste Where were we wasteful with time, resources, etc? Identify 2-3 opportunities for improvement of your teams performance. Develop your action plan for implementation. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Phase 1 Deliverables Why worry about MSD 1 team performance shortfalls? MSD 2 Deliverables are challenging. Working prototype that meets all engineering requirements. Course has a hard end date. Team has to develop and deliver the design you planned. Team has to resolve all of the critical problems that will be revealed and enjoyed on the 15 week journey. Most Teams have opportunities for improvement. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Phase 1 Deliverables Team Self-Critique: Score: 1- 5** 1= was not a problem for our team 3= was a concern 5 = was a very serious problem for our team Major Issues Encountered* Self CritiquePlan to Address (or how it was/will be addressed) Norms & values: - Team dynamics: conflict, leadership/control, communication 4 Teammate personal conflict; team intervention. Set and inforce expectations for acceptable behavior. - Individual behavior/performance/participation 4 As above. Logistics: scheduling meetings, scheduling work 3 Had scheduled meetings without agenda or a plan. Lots of yelling and frustration. 1. All mtgs Agenda; 2. Will follow updated MSD 2 plan Skills gap? 2 concern but we have faculty help if needed. Customer requirements: access to customer, clarity of rqmts, behavior (support, commitment, attitude) 1 No Problem; we have a great customer. Engineering requirements: quality, completeness, flowdown to subsystems, traceability 1 No Problem; we think we a good list. Risk assessment and mitigation plans: missed important risks, focus on minor issues, ineffecitve mitigation plans, etc. 2 Don't really know. Project planning & tracking: unrealistic schedule, poor tracking, not proactive, no accountability 4 Our MSD 1plan is a joke; it did really reflect what we were& should be doing. WE know this is a problem for MSD2. Will review and update MSD2 plan. Systems design: benchmarking inadequate, limited concepts, functional decomposition gaps, mapping between functional and physical architecture, interface complexity, etc 1 System design went well, we ensured CRs, Functions, and Ers mapped to each other by combining them on the same spreadsheet Engineering analysis & feasbility: analysis gaps or prioritization, appropriateness of analysis, timing, etc. 2 Well done but there was a lot of frustration as we really did not have a plan. Detailed design: scope, complexity, resources, time, etc. 2 Well done but there was a lot of frustration as we really did not have a plan. Test planning: ambiguity, implementation difficulty, resources, ownership 2 Timing of tests ambiguous, but there are tests planned for each ER Design reviews: participation, value-add 2 All group members contributed to design reviews. Individual presentation styles varied in effectiveness. All were well prepared This team has two engineers who are having trouble playing nice in the technical sandbox. This team has met the challenges of MSD 1 by a lot of extra work. They will be in trouble delivering a working prototype. Behavior PLAN MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Phase 1 Deliverables Why update your Teams MSD 2 Plan? You only have 15 weeks. Your team should have a working Imagine RIT. 3 May 2014 Test Activities will reveal new problems Plan individual contribution. Fabrication may present some challenges. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Phase 1 Deliverables Updated MSD 2 Plan Proposal Add known mileposts for the (5) phase exit reviews, ImagineRIT14 etc. These phase exit reviews are project progress reviews Develop a Team Shared vision of ImagineRIT Develop a detailed Shared Vision for W5 review What will be accomplished and demonstrated at the week 5 project progress review Each engineer should have a three week plan that supports the shared vision of the team. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Shared Vision: ImagineRIT Shared Vision Team: P13026 Portable Emergency Ventilator End of MSD 1 On May 4, 2013 our team will be presenting our Senior Design Project at Imagine RIT. We are still waiting to see if our proposal to be placed in the Field House will be accepted, but regardless of where we are placed this is what we would like to do for our exhibit: Have both our product and the original Mediresp III be seen by the public Have a CPR Torso on the table so that we can demonstrate how our Ventilator works. We can show off the CPR Mode by doing compressions to make our CPR Mode function. We can obstruct the airway to demonstrate our pressure feedback system as one of our systems safety measures. We can also run the system in CVM to show how it will breath for a person. Use either poster boards or a monitor to show off the future produce concepts Create a poster board to describe our project We will keep a minimum of 2 members of the team at the table at all times We will develop our schedule closer to the date of Imagine RIT (No Later than 3 days before the event, May 1, 2013) We will work on developing an elevator speech to give Depending on the flow of traffic at our table, we will also allow the public to interact with our system. We can develop scenarios for them to work through in terms of changing the settings on the Ventilator MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Shared Vision Week 5 Shared Vision Week 5 Demo Proposal Team: P13026 Portable Emergency Ventilator Demo Date:March 24, 2013 At the end of week 5 of MSD 2 we plan to demo the following systems of our Portable Emergency Ventilator: Product Housing with placement of: Knobs, switches, screen Mount Points for all interior components K-70 interfacing with: Mass Flow Sensor, Pressure Sensor, Pulse Oximeter,Power Regulator,Pump,Battery This system demonstration will not be 100% put together, meaning it is possible that the integration of the components may not be placed within the housing. At a minimum though the system components (i.e. battery, pump, sensor, etc.) will be connected correctly and function at some level. And we will have the mounting points laid out on the interior of the housing. The user interface features will be mounted on the exterior of the product housing in the positions that match the positions of our expected final product. These knobs and switches will not be functional, meaning varying them will not affect the system functionality. Continuing with our goal set for the Week 3 demonstration, we plan to have the K-70 operating so that it will be able to control the pump and read in values from our sensors. The integration with the LCD screen will not be developed yet, so an external computer screen will be used to show this functionality as well as an oscilloscope so that the input values can be observed as well. MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Phase 1 Deliverables MSD 2 Plan Started in MSD 1 Activities for the weeks 1- 3 Other 4 phases for MSD 2 MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Phase 1 Deliverables Project Element W1W2W3W4W5W6W7W8W9W10W11W12W13W14W15 Course Mileposts: PHASE EXIT REVIEWS Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 ImagineRIT 14 3-May Weekly Guide Meetings Final Public Project Presentations Phase 1: MSD 1 Post Mortem Phase 1 MSD 2 Plan Updated Phase 1 BOM Review & Update Phase 1 Problem Tracking Process Phase 1 Test Plans & Test Bench Phase 1 Ordering & Receiving Parts Phase 1 Fabrication of key parts Phase 1 Other Project Progress Phase 2: Critcal Susbystem Testing Phase 2 Progress on Prototype Fabrication Phase 2 Update Problem ID, Tracking, Solve Phase 2 Enter ImaginerRIT, Competition Phase 2 Other Project Progress Phase 2 Phase 3: System Level Test Results Phase 3 Other Project Progress Phase 3 Phase 4: System Level Test Results Phase 4 Other Project Progress Phase 4 Phase 5:Deliverables Completion Working Prototype: TEST RESULTs 33% 75% 90% 100%? 100% Technical Paper 75% 100% Poster 100% Professional Documentation 100% Final Public Project Presentations 100% Details for Week 5 Growth Projection Working Prototype MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Phase 1 Deliverables BOM Review: BILL of Materials Is your Design complete? BOM is the tool to track required materials. Is everything required on the BOM? What are you approved to order? Follow requisition process on Mycourses What are you not quite ready to order Still specifying / selecting Critical & All Part Availability? Lead time from order to receipt; check with supplier When do you need it? Within Budget? Update BOM with cost data frequently Manage shipping and handling MSD 2 KICKOFF 28 JAN 2014 MSD End State Expectations MSD 2 Phase 1 Deliverables MSD 1 Post Mortem Updated MSD 2 Plan BOM Review: Problem ID, resolution & tracking process W.Novak next Test Plan & Test Bench Thursday 30 Jan M. Zona