1 / 13

Requirements – Essential To Robust Product Design

Learn the essential elements of defining robust product design requirements and categorization strategies. Understand user, product, and block level validation. Efficiently specify and validate before design. Explore categorization such as standard and performance requirements, allocation, and association. Gain insights into market considerations, environmental and safety parameters, power sources, mechanical design impact, and lifecycle considerations.

Download Presentation

Requirements – Essential To Robust Product Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Requirements – Essential To Robust Product Design Definition: “Statements of desired product performances and features used to define and quantify a product design” • User Level: Special list of Requirements which state the intended application and/or purpose of the product (Labeling) • Product Level: State all features, performances, and interfaces describing the product in “Engineering Terms” • Block Level: State all features, performances and interfaces describing the block in “Engineering Terms” • User Level >>> Validation • Product & Block Level>>>Verification Efficient Engineering teams fully specify before they design !!

  2. Requirements Imply Proof of Satisfaction !Implied Product Design Integrity ! • Many Gov’t Agencies mandate that ALL product requirements should be user validated and/or engineering verified (tested or justified). A requirement which cannot be verified or validated should not be stated unless objective evidence can be compiled to prove its satisfaction • Other Requirement Categorization Used in this Course: • Standard: Common to ALL Project Teams • Performance: Unique to Project and Technology, For Differentiating Standard Reqs Enhance Consistency across Projects

  3. Blocks • Complex products require that the design be broken into logical design elements (termed blocks in this course) • During phase 1, your product design must include a brief list of user level reqs plus a robust list of product level reqs as well as a block diagram of all the logical design elements • Blocks form the basis of standardized design elements in this course. Each project must provide one or more design blocks for each team member.

  4. Allocation and Association • ALLProduct Level Requirements Must be allocated or associated to each design block within the project to complete Phase 1 • Allocated: % of total budgeted to applicable design blocks plus margin. For example: Product Cost, Power Consumption, Mass …. • Associated: Used when allocation is not applicable. For example: Country(s) of Market, Annual Volume, Safety Standards ….

  5. Standard Requirements • Standard Requirements are those requirements which are universal and can be applied to nearly all products and hence final projects • Standard Requirements may or may not be differentiating depending upon project goals but MUST be part of the minimum description of the product

  6. Standard Requirements: Market Choose & Understand your Market “before” …………. you design a product RequirementUnits to Specify • Company Name(s), Model#(s) • Total $/Region, Info Source • $/unit as sold to customers • List of Countries or Regions • Min/Max Age, Sex, Restrictions • Ind, Auto, Home, Wearable, etc • $/unit in proto production • $/unit in volume production • # of units/yr • Competitors • Market Size • Min List Price • Market Geography • Market Demography • Intended Application • Max Proto Cost • Max Product Cost • Annual Volume

  7. Standard Requirements: Env & Safety Consider Simultaneous Min or Max CasesSome will NOT be “testable” RequirementUnits to Specify • Co, Min-Max • Rh%, Min-Max • Meters or ATM, Min-Max • Co, Min-Max • Rh%, Min-Max • Meters/ATM, Min-Max • Time • List of IEC, and FCC stds • List UL, IEC or other stds • Min Oper Temp Range • Min Oper Humidity Range • Min Oper Alt or Press Range • Min Storage Temp Range • Min Storage Humidity Range • Min Storage Alt/Press Range • Max Storage Duration • Primary EMC Standards • Primary Safety Standards

  8. Standard Requirements: Power Must consider power source(s) early Undefined DC power sources NOT allowed RequirementUnits to Specify • AC,Battery,Photovoltaic,Gen… • Permanent or Temp • Volts, Min-Max For each Source • Watts Total, Per Source • Watt-Hours/Yr for AC Time for Min Battery Life • Energy Sources • Source Connection • Min Operating Voltage Range • Max Power Consumption • Max Energy Consumption

  9. Standard Requirements: Mechanical Package and Mechanical Design Impact Many Product Aspects RequirementUnits to Specify • Cm3 Total for Entire Product • Cm Max LxWxH for 1 unit • Kilograms • Type or Style • # • Cm2 Total • G force (Grms), # Reps • Max Volume • Shipping Container Size • Max Mass • Power Connector(s) • Max # of PC Bds • Max PCB Circuit Area • Max Shock

  10. Standard Requirements: Mfg & Life Cycle Product designs should consider full “life cycle” from Mfg process to Disposal RequirementUnits to Specify • # Total Parts incl elec & mech • # of Unique Parts • $ (Parts+Mfg=Product Cost) • $ (Parts+Mfg=Product Cost) • Time = MTBF(yrs) • Time (yrs) • Return, Recycle, Dispose, etc • Time (yrs) • Dispose or Repair, Factory or Field • Max Parts Count • Max Unique Parts Count • Parts/Mat $ Allocation • Asm/Test $ Allocation • Product Life, Reliability • Full Warranty Period • Product Disposition • Production Life Support • Service Strategy

  11. Project Proposal: Performance Requirements • Performance Requirements are those requirements which are specific to a product and project • Performance Requirements differentiate the product from all other similar products • Performance Requirements describe …. • Interfaces • Features, Options • Modes of Operation • Performance Parameters • User Controls • User Displays and Outputs

  12. Mandatory: Performance Requirements(Must be Considered if Applicable) All Applicable Must Be Defined RequirementDefinition • Country Usage (AC) • Battery Style, Time • Min to Max Hz • Type, Size, Visibility, Speed, Color • Volume, Pitch, Duration, Vibration, Flags, Other • Analog, Digital, Keybds, Voice, RF, etc • Nominal Input Power Sources • Battery Type, Min Life • Input Power Freq Ranges • Optical Indicators, Displays • Mechanical Indicators • User Inputs

  13. Mandatory: Performance Requirements(Must be Considered if Applicable) There may be others RequirementDefinition • Voltage, Current, Frequency, Noise, Impedance, Field Strengths, Standards, etc • Attachments, Pressure, Torque, Handles, Connector Types, Package, etc • On/Off, Idles, Resets, Standby, Xmit, Charging, etc • Accuracy, Resolution, Speeds, Distances, Errors, Noise, Distortion, etc • Electrical Interfaces • Mechanical Interfaces • Operational Modes • Effectiveness

More Related