Presentation is loading. Please wait.

Presentation is loading. Please wait.

1/9/09 System Level Design Review January 16, 2009 Aaron Heyman – Lead Adam Cook Jose Rodriguez Abraham Taleb.

Similar presentations


Presentation on theme: "1/9/09 System Level Design Review January 16, 2009 Aaron Heyman – Lead Adam Cook Jose Rodriguez Abraham Taleb."— Presentation transcript:

1 1/9/09 System Level Design Review January 16, 2009 Aaron Heyman – Lead Adam Cook Jose Rodriguez Abraham Taleb

2 Team Expectations for Design Review Learn if Costumer Needs are being met Catch any mistakes in design Receive input on user interface Confirm coherence between all involved parties to create the best end product 1/9/09

3 Agenda Review Goals of Project Project Status Customer Needs Assumptions, Constraints and Risk Assessment Discussion of User Interface

4 1/9/09 Goals of Project Be able to answer the following question: o How many labor hours does CooperVision need per pick area given demand in terms of lines for a particular time segment (daily, weekly, monthly, yearly)? Process Improvements will be identified and investigated beginning in March

5 1/9/09 Project Status Aaron's Screen Shot

6 Customer Need # ImportanceDescriptionComments/Status CN15The time required to train users is minimal.Not Met CN25The computer tool is user friendly.Not Met CN33 The computer tool is able to be upgraded and/or modified in the future. Not Met CN45The computer tool represents the real world.Not Met CN53The computer tool identifies invalid data inputs.Not Met CN61The computer tool executes commands quickly.Not Met CN73 The computer tool alerts the user when a given demand input is not realizable given actual capacity.Not Met CN83 The computer tool allows the user to visualize all the information on a single screen. Not Met CN93 The computer tool provides the option to print a report of the output. Not Met Customer Needs Importance Scale: 5= Must Have 3= Nice To Have 1= Preferential

7 Engineering SpecificationsMetrics 1The training time is less than 30 minutes.Training Time 2The computer tool is user friendly.Ease of use 3The computer tool is able to be upgraded and/or modified in the future.Flexibility 4The system represents the real world.Validity Test 5The system identifies invalid data inputs.Ease of use 6The system executes a command in no more than 0.25 minutes.Execution Time 7The system alerts the user when a given demand input is not realizable given actual capacity.Validity Test 8The computer tool allows the user to visualize all the information on a single screen.Validity Test 9The computer tool provides the option to print a report of the output.Validity Test Table 1.1 Relationship of customer needs to metrics Target Specifications Metrics and Specifications Metrics Need Nos.Importance Units Ideal ValueMarginal value 1Training Time15Minutes<30<60 2Ease of use2,55Subjective53 3Flexibility33BinaryYes 4Validity Test4,7,8,91BinaryPass 5Execution Time61Minutes0.050.25 Table 1.2 Target Specifications Importance Scale: 5= Must Have 3= Nice To Have 1= Preferential Binary: Pass or Fail.

8 1/9/09 Assumptions & Constraints Pick per area distribution is constant Capacity analysis only applies to pick areas not packing/shipping SKUs are always in stock Unable to pull data with out IT assistance No budget to make improvements unless approved Picking system and design constraints

9 1/9/09 Risk Assessment Risk ItemLevelOwnerStatus and/or Contingency Plans Optimizing part of the system and not the whole. MediumCooperVisionThe team will optimize the pick area to the best of their ability. The entire distribution process is beyond the project scope. Validating the computer tool. HighTeamThe team plans on using historical data to validate the model. Creating an easily modifiable computer tool. MediumTeamThe team will use excel for the computer tool due to its popularity with the customer. Missing data that is needed for calculations. LowTeamThe team has requested all data and has been receiving it in a timely manner from the customer.

10 1/9/09 User Interface Discussion

11 Demand Timeframe for which demand is evaluated. Inputs Outputs Output labor hours for each picking area. Output aggregated labor hours required to meet specified demand.

12 General Information Max. # of employees per area per shift ADM1 Pick to Voice30 Pick to Light24 Carousel4 Note: all data is accurate as of 1/1/09. SeptemberOctober November PickAreaLinesUnitsLinesUnitsLinesUnits ADMPCK12%8%12%7%13%9% CAGEPCK1% 2% 1% CARPCK7%4%7%4%7%5% LISTPCK12%43%12%48%7%39% MEZVRF8%5%8%4%10%5% PTLPCK52%34%51%30%52%34% VRFPCK8%5%9%5%10%6% Hits By Picking Method

13 1/9/09 Questions & Discussion ?

14 1/9/09 General Formulations


Download ppt "1/9/09 System Level Design Review January 16, 2009 Aaron Heyman – Lead Adam Cook Jose Rodriguez Abraham Taleb."

Similar presentations


Ads by Google