Product Design & Development

Transcription

1 Product Design & Deveopment Product Architecture 1 2 1

2 What is Product Architecture? Product architecture is the assignment of the product's functions to physica buiding bocks or "chunks". Product modue modue modue modue modue modue 3 modue modue Moduar or integra architecture? 4 2

3 Moduar product architecture Each chunk fuy embodies one or more product functions. Interactions between chunks are: we defined (typicay) fundamenta to product's primary functions. Moduar architecture has advantages in simpicity and reusabiity for a product famiy or patform. 5 Patform Architecture of the Sony Wakman 6 3

4 Integra product architecture Typica functions invove more than one chunk Typica chunks impement more than one function Interactions between chunks are i-defined and may be incidenta to product's primary functions. Integra architecture generay increases performance and reduces costs for any specific product mode. 7 Traier Exampe: Moduar Architecture box hitch fairing bed springs whees protect cargo from weather connect to vehice minimize air drag support cargo oads suspend traier structure transfer oads to road 8 4

5 Traier Exampe: Integra Architecture upper haf ower haf nose piece cargo hanging straps spring sot covers whees protect cargo from weather connect to vehice minimize air drag support cargo oads suspend traier structure transfer oads to road 9 Moduarity Moduarity is a reative property Products are rarey stricty moduar or integra. 10 5

6 Types of moduarity Sot-moduar architecture Each chunk-to-chunk interface is different from the others. Chunks cannot be swapped around. 11 Sot-moduar architecture 12 6

7 Bus-moduar architecture Uses a common bus, or simiar concept. Uses standard chunk-to-bus interfaces. 13 Sectiona-moduar architecture No common bus or other singe eement interfacing with a other chunks. Uses standard chunk-to-chunk interfaces. 14 7

8 Moduar or integra? Roerbade In-Line Skates Appe ibook 15 Motoroa v60 Ceuar Phone Ford Exporer Choosing the Product Architecture Architecture decisions reate to product panning and concept deveopment decisions: Product Change (copier toner, camera enses) Product Variety (computers, automobies) Standardization (motors, bearings, fasteners) Performance (racing bikes, fighter panes) Manufacturing Cost (disk drives, razors) Project Management (team capacity, skis) System Engineering (decomposition, integration) 16 8

9 When is the product architecture defined? Product architecture begins to emerge during concept deveopment. Panning Panning Concept Concept Deveopment Deveopment System-Leve System-Leve Design Design Detai Detai Design Design Testing Testing and and Refinement Refinement Production Production Ramp-Up Ramp-Up Patform decision Concept decision Decomposition decision 17 Product architecture affects: Product changes Upgrades Ex.: Changing the processor board of a computer Add-ons Ex.: Third-party mass storage devices Adaptation to oca conditions Ex.: 110 or 220 Vot power suppy 18 9

10 High-wear components Ex.: tires on vehices Consumabes Ex.: fim cartridges Fexibiity in use Ex.: Lens or fash options for a camera 19 Product variety Variety refers to the range of product modes the firm can produce within a particuar timeframe in response to market demand. Swatch produces hundreds of watch modes

11 Component standardization Use the same components or chunks in various products. Ex.: Watch movement, watch battery, etc. 21 Product performance How wi product impement intended functions? Ex.: Function sharing of BMW transmission chunk 22 11

12 Manufacturabiity Benefits from: Design-for-manufacturing (DFM) Minimization of parts count through component integration. These strategies are best appied at the chunk eve. 23 Managing the PD process Detaied design responsibiity for each chunk is usuay assigned to a sma in-house team or outsourced to a suppier

13 Concepts of integra and moduar appy at severa eves System Sub-system Component 25 Product Architecture = Decomposition + Interactions Interactions within chunks Interactions across chunks 26 13

14 Estabishing the architecture Create schematic (iustrating product architecture) Custer eements Create rough geometric ayout Identify fundamenta and incidenta interactions 27 DeskJet Printer Schematic Encose Printer Print Cartridge Provide Structura Support Position Cartridge In X-Axis Accept User Inputs Dispay Status Store Output Store Bank Paper Position Paper In Y-Axis Pick Paper Contro Printer Suppy DC Power 28 Functiona or Physica Eements Fow of forces or energy Fow of materia Fow of signas or data Communicate with Host Connect to Host Command Printer 14

15 Custering eements Key considerations when custering eements (of schematic) into chunks incude: Geometric integration and precision Ex.: H-P custering for ink-jet printer cas for cartridge positioning on x-axis and paper positioning on y-axis 29 Custering eements (cont) Function sharing Ex.: Status dispay and user contros for H-P printer Ex.: Transmission for BMW motorcyce Vendor (= Suppier) capabiities Ex.: H-P printer Ex.: Spring and shock absorber for rear suspension of BMW motorcyce 30 15

16 Custering eements (cont) Simiarity of design or production technoogy Location of change Accommodating variety Enabing standardization Portabiity of interfaces 31 Custer Eements into Chunks 32 Functiona or Physica Eements Encosure Encose Printer Provide Structura Support Chassis Chunks Store Output Store Bank Paper Paper Tray Print Cartridge Position Cartridge In X-Axis Position Paper In Y-Axis Pick Paper Print Mechanism User Interface Board Accept User Inputs Contro Printer Communicate with Host Connect to Host Dispay Status Power Cord and Brick Suppy DC Power Command Printer Host Driver Software Logic Board 16

17 Geometric ayout 33 Key considerations when creating a rough geometric ayout incude: Identification of fundamenta and incidenta interactions Fundamenta interactions Ex.: H-P printer Sheets of paper fow from the paper tray to print mechanism. Incidenta interactions Ex.: Vibration induced by the actuators in paper tray may interfere with precision positioning of print cartridge (x-axis) Create a rough geometric ayout ogic board user interface board 34 height encosure ogic board chassis print cartridge roer chassis print mechanism paper print cartridge paper tray paper tray 17

18 Incidenta interactions Encosure User Interface Board Stying Paper Tray Vibration Print Mechanism Therma Distortion Logic Board Host Driver Software Therma Distortion Chassis Power Cord and Brick 35 Probem Product chunks tend to be deveoped separatey as independent tasks (decomposition) The sequencing of tasks is important and reated to product architecture Some tasks may depend on others to get going Some are independent of the others Some may interact back and forth (couped) 36 18

19 Probem If one decomposes to deveop, in the end one has to integrate back the chunks System integration needs are determined by the chosen decomposition and its resuting architecture 37 Types of sequencing 38 19

20 PERT and CPM charts 39 The Design Structure Matrix (DSM) Interpretation Task D requires information fom tasks E, F and L Task B transfers information to tasks C, F, G, J and K (Inputs are easier to capture than outputs) 40 20

21 DSM sequencing Couped tasks can be identified uniquey. The dispay of the matrix can be manipuated to emphasize certain features of the process fow. DSM anaysis software impements partitioning agorithms. 41 DSM where to appy? DSM canbeappiedto: Tasks (chunks) -> Product architecture Organizations -> Organization Structure 42 21

22 Appication of DSM - Exampe New engine deveopment 22 product deveopment teams invoved simutaneousy 43 Decomposition of the Engine Deveopment Project 44 22

23 PDT interactions 45 Proposed system teams 46 F G E D I A C B1K1 J P N Q R B2K2 O L M H S T U V Crankshaft F F Fywhee G G Team 1 Connecting Rods E E Pistons D D Lubrication I I Team 2 Engine Bock A A Camshaft/Vave Train C C Cyinder Heads B1 B1 Intake Manifod K1 K1 Team 3 Water Pump/Cooing J J Fue System P P Air Ceaner N N Throtte Body Q Q EVAP R R Team 4 Cyinder Heads B2 B2 Intake Manifod K2 Integration K2 A.I.R. O Team O Exhaust L L E.G.R. M M Accessory Drive H H Ignition S S E.C.M. T T Eectrica System U U Engine Assemby V V Frequency of PDT Interactions November 8, 2007 Daiy Weeky Monthy Product Design and Deveopment - Chapter 9 23

24 Another way to view it 47 Fundamenta Decisions Integra vs. moduar architecture? What type of moduarity? How to assign functions to chunks? How to assign chunks to teams? Which chunks to outsource? 48 24

25 Practica Concerns Panning is essentia to achieve the desired variety and product change capabiity. Coordination is difficut, particuary across teams, companies, or great distances. Specia attention must be paid to hande compex interactions between chunks (system engineering methods). 49 Product Architecture: Concusions Architecture choices define the sub-systems and modues of the product patform or famiy. Architecture determines: ease of production variety feasibiity of customer modification system-eve production costs Key Concepts: moduar vs. integra architecture custering into chunks panning product famiies 50 25