PRODUCT
ARCHITECTURE
Product Development Process
Planning DevelopmentConcept System-LevelDesign DesignDetail Testing andRefinement ProductionRamp-Up
Product architecture is determined early in the development process.
Platform decision Concept decision Decomposition decision
Planning Concept Develop. System-Level Design Detail Design Testing And Refinement Production Ramp-Up Marketing Design Mfg Other
Arsitektur Produk
• Arsitektur produk adalah penugasan elemen-elemen fungsional dari produk terhadap kumpulan bangunan fisik
(physical building blocks) dari suatu produk.
• Tujuan arsitektur produk adalah menguraikan komponen fisik dasar dari produk, apa yang harus dilakukan komponen tersebut dan seperti apa
penghubung/pembatas (interface) yang digunakan untuk
Product Architecture: Definition
• The arrangement of functional elements into physical
chunks which become the building blocks for the product or family of products Product module module module module module module module module
Importance of Product Architecture
• Decided early and drives design
• Bagaimana arsitektur produk mempengaruhi kemampuan tim pengembang menghasilkan beberapa variasi produk?
• Impacts manufacturing cost
• Apa implikasi biaya dari arsitektur produk yang berbeda-beda? • Impacts product evolution
• Bagaimana arsitektur produk mempengaruhi kemampuan tim pengembang untuk menyelesaikan desain dalam 1 bulan? • Impacts organization structure of design teams
• Bagaimana arsitektur produk mempengaruhi kemampuan tim pengembang untuk mengendalikan proses pengembangan?
Product Architecture Example:
Elements of Product Architecture
• Functional elements: individual operations and
transformations that contribute to the overall performance of the product.
• Physical elements: the parts, components, and sub-assemblies that ultimately implement the product’s functions.
Elemen fungsional
• Terdiri atas operasi dan transformasi yang menyumbang
terhadap kinerja keseluruhan produk
• Biasanya diuraikan dalam bentuk skema sebelum
direduksi menjadi suatu teknologi yang spesifik, komponen, atau prinsip-prinsip kerja fisik
• Contoh:
• Menyimpan kertas
Elemen fisik
• Bagian produk (part), komponen, dan sub rakitan yang pada akhirnya diimplementasikan terhadap fungsi produk • Diuraikan lebih rinci ketika usaha pengembangan
berlanjut
• Beberapa elemen fisik ditentukan oleh konsep produk, dan yang lainnya ditentukan selama fase perancangan detail
• Contoh: peralatan pengirim tinta melalui prinsip
pemanasan à diterapkan pada tinta printer (printer cartridge)
Product Architecture
• Physical elements are typically organized into several major building blocks: chunks
• Each chunk: a collection of components that implement the functions of the product
• The architecture of a product: the scheme by which the functional elements of the product are arranged into
Types of Product Architecture
• modular • integral
Modular Architecture
• Each physical chunk implements one or a few functional elements in their entirety
• The interactions between chunks are well defined (i.e. the interfaces are well defined) and fundamental to the
primary functions of the product
• Modular architecture has advantages in simplicity and reusability for a product family or platform.
• Allows a design change in one chunk without requiring changes to other chunks
• Most modular: each functional element is implemented by exactly one chunk
Modular Product Architectures
Sony Walkman
Swiss Army Knife
Platform Architecture of the Sony
Walkman
Additional Advantage to Modular Design
• HP products are designed to be recycled. • Recycling design features include:
• Modular design to allow components to be removed, upgraded or replaced
• Eliminating glues and adhesives, for example, by using snap-in features
• Marking plastic parts weighing more than 25g according to ISO 11469 international standards, to speed up materials identification during recycling
• Reducing the number and types of materials used
• Using single plastic polymers
• Using molded-in colors and finishes instead of paint, coatings or plating
• Relying on modular designs for ease of disassembly of dissimilar recyclable materials
Integral Architecture
• Functional elements are implemented by multiple chunks, or a chunk may implement many functions.
• Interactions between chunks are poorly defined, may be incidental to the primary functions of the products
• Integral architecture generally increases performance and reduces costs for any specific product model.
• Used with products with highest possible performance in mind
Integral Product Architectures
Integral vs. Modular
Integral• Higher system performance
• Tightly coupled design teams
• Hard to change
• Lower system cost (in large volume)
• Expensive Tooling
Modular
• Reduced performance
• Decoupled design teams • Increased flexibility • Accommodates made-to-order products • Changeability • Requires flexible manufacturing
Trailer Example: Modular Architecture
box hitch fairing bed springs wheels protect cargo from weather connect to vehicle minimize air drag support cargo loads suspend trailer structure transfer loads to roadTrailer Example: Integral Architecture
upper half lower half nose piece cargo hanging straps spring slot covers wheels protect cargo from weather connect to vehicle minimize air drag support cargo loads suspend trailer structure transfer loads to roadModular or Integral Architecture?
Motorola StarTAC Cellular Phone Rollerblade In-Line Skates Ford Explorer Apple iBookTypes of Modularity
• Slot-Modular Architecture
• unique interfaces for attachment to a base element (e.g. pacemaker leads)
• Bus-Modular Architecture
• common interfaces for attachment to a base element (e.g. USB connectors on a computer)
• Sectional-Modular Architecture
• Common interfaces between elements without a base element (e.g. legos & piping)
Slot-Modular Architecture
• each interface between chunks different - various chunks cannot be interchanged
• example: automobile radio - implements exactly one function, but interface different from any other
Bus-Modular Architecture
• a common bus to which chunks connect via the same
type of interface
• examples: track-lighting, shelving system with rails, expansion card for PC
Sectional-Modular Architecture
• all interfaces of same type, but no single element to which all other chunks attach
• assembly built by connecting chunks to each other via identical interfaces
Implications of the Architecture
• Decisions about how to divide the product into chunks, and how much modularity, are linked to:
• product change
• product variety
• Standardization
• Performance
• manufacturability
Product Change - Motives
• upgrade: technology or user needs evolve • add-ons: add to basic unit; third-party
• adaptation: different use environments • wear: replace elements, extend useful life
• consumption: replenish consumables
• flexibility in use: configured for different uses
Product Variety
• products built around modular architectures can be more easily varied without adding tremendous complexity to the manufacturing systems
• example: Swatch watches - many different hands, faces, wristbands but small selection of movements and cases
Standardization & performance
• Standarisasi komponen adalah penggunaan komponen atau chunk yang sama pada bermacam-macam produk • Kinerja produk didefinisikan dengan seberapa baik produk
dapat mengimplementasikan fungsi-fungsi yang ditugaskan terhadap produk
Manufacturability
• Product architecture directly affects the ability of the team to design each chunk to be produced at low cost
• One DFM strategy involves minimization of the number of parts through component integration, but component
integration across several chunks is difficult • DFM must start at system-level design
Product Development Management
• Modular and integral architecture demand different project management styles
• modular - requires very careful planning during system-level design
• integral - less planning during system-level, but more integration, conflict resolution, and coordination during detail design
Fundamental Decisions
1. Integral vs. modular architecture? 2. What type of modularity?
3. How to assign functions to chunks?
4. How to assign chunks to teams?
Choosing the Product Architecture
• Architecture decisions relate to product planning and concept development decisions:
• Product Change (copier toner, camera lenses)
• Product Variety (computers, automobiles)
• Standardization (motors, bearings, fasteners)
• Performance (racing bikes, fighter planes)
• Manufacturing Cost (disk drives, razors)
• Project Management (team capacity, skills)
apply at several levels:
system
sub-system
Product Architecture = Decomposition +
Interactions
• Interactions
within chunks
•
Interactions
across chunks
Establishing the Architecture
• To establish a modular architecture, create a schematic of the product, and cluster the elements of the schematic to achieve the types of product variety desired.
Establishing the Architecture
Create a schematic of the
product
Cluster the elements of the
schematic
Create a rough geometric
layout
Identify the fundamental and
incidental interactions
Create a Schematic
• Schematic: a diagram of the team’s understanding of the elements of the product
• physical concepts, critical components, and functional elements
• if product is a complex system with hundreds of functional elements, group into fewer, higher-level functions to be decomposed later
DeskJet Printer Schematic
Flow of forces or energy Flow of material
Flow of signals or data
Store Output Store Blank Paper Enclose Printer Provide Structural Support Print Cartridge Position Cartridge In X-Axis Position Paper In Y-Axis Supply DC Power “Pick” Paper Control Printer Command Printer Connect to Host Communicate with Host Display Status Accept User Inputs Functional or Physical Elements
Cluster the Elements of the Schematic
• To determine when there are advantages to clustering, consider:
• geometric integration and precision
• function sharing
• capabilities of vendors
• similarity of design or production technology
• localization of change
• accommodating variety
Cluster Elements into Chunks
Store Output Store Blank Paper Enclose Printer Provide Structural Support Print Cartridge Position Cartridge In X-Axis Position Paper In Y-Axis Supply DC Power “Pick” Paper Control Printer Command Printer Connect to Host Communicate with Host Display Status Accept User InputsPaper Tray Print Mechanism
Logic Board Chassis
Enclosure
User Interface Board
Host Driver Software Power Cord and “Brick” Functional or Physical Elements Chunks
Create a Rough Geometric Layout
• Geometric layout in two- or three-dimensions
• drawings
• computer models
• physical models
• cardboard or foam
• evaluate clustering
Geometric Layout
mechanism
paper tray
user interface board
cartridge logic
board
Geometric Layout
chassis paper roller print cartridge paper tray enclosure logic board heightIdentify the Fundamental and Incidental
Interactions
• fundamental: those corresponding to the lines on the schematic that connect the chunks together; planned • incidental: those that arise because of the particular
physical implementation of functional elements, or because of the geometric arrangement of the chunks
• example: chunks creating motion may have vibration as an incidental interaction
Incidental Interactions
Enclosure Paper Tray Chassis Print Mechanism User Interface Board Logic Board Power Cord and “Brick” Host Driver Software Styling Vibration Thermal Distortion Thermal Distortion RF Interference RF ShieldingPertimbangan variasi dan rantai pemasok
• Dua prinsip desain yang diperlukan untuk melakukan penundaan diferensiasi:
• Diferensiasi elemen-elemen dari produk harus dikonsentrasikan pada satu atau sedikit chunk
• Produk dan proses produksi harus dirancang sedemikian rupa sehingga chunk yang didiferensiasikan dapat ditambahkan pada produk mendekati tahap akhir dari rantai pemasok
Pertimbangan variasi dan rantai pemasok
• Atas – suplai energi didistribusikan melintasi kawat, area tertutup, kerangka (chassis), dan papan logika (logic
board)
• Bawah – suplai energi dibatasi distribusinya pada kawat dan kotak penyuplai energi
Perencanaan platform
• Bentuk dasar (platform produk): kumpulan bagian,
termasuk rancangan komponen yang dapat digunakan bersama oleh bermacam-macam produk
• Perencanaan platform produk melibatkan upaya untuk
mengendalikan pertentangan antara perbedaan dan persamaan
• Alat sederhana:
• Rencana diferensiasi (differentiation plan)
Differentiation plan
Atribut Diferensiasi Segmen Keluarga Segmen Mahasiswa Segmen Kantor Kecil, Rumah Kantor
Kualitas cetakan hitam Mendekati laser dengan kualitas 300 dpi
Laser dengan kualitas 600 dpi
Laser kualitas 600 dpi Kualitas cetakan
berwarna
Mendekati kualitas foto Sama dengan DJ600 Sama dengan DJ600 Kecepatan printer 6 halaman/menit 8 halaman/menit 10 lembar/menit Luas 360mm x 400mm 340mm (tinggi) x 360mm
(lebar)
400mm (tinggi) x 450mm (lebar)
Penyimpan kertas 100 lembar 100 lembar 150 lembar Gaya Konsumen Konsumen muda Komersial Penghubung ke komputer USB dan kawat parallel USB USB Kesesuaian
(kompatibilitas) sistem operasi
Planning a Modular Product Line:
Commonality Table
Chunks
Number of Types
Family Student SOHO
(small office, home office)
Print cartridge 2 “Manet” Cartridge “Picasso” Cartridge “Picasso” Cartridge Print Mechanism 2 "Aurora" Series Narrow "Aurora" series "Aurora" series Paper tray 2 Front-in Front-out Front-in Front-out Tall Front-in Front-out Logic board 2 “Next gen” board
with parallel port “Next gen” board “Next gen” board
Enclosure 3 Home style Youth style “Soft office” style
Driver software 5 Version A-PC
Version A-Mac Version B-Mac Version B-PC Version C
Differentiation versus Commonality
dengan persamaan
• Keputusan rencana platform harus diinformasikan melalui perkiraan terhadap implikasi biaya dan pendapatan yang kuantitatif
• Melakukan pengulangan (iterasi) dalam mengambil
keputusan akan lebih baik
• Arsitektur produk menentukan sifat pertentangan antara perbedaan (differentiation) dengan persamaan
Related System-Level Design Issues
• The four-step method for establishing architecture guides the early design activities, but more detailed activities
remain:
• defining secondary systems
• establishing architecture chunks
Defining Secondary Systems
• many functional and physical elements not shown on schematic (for simplicity)
• others may be conceived as system-level design evolves • examples: safety systems, power systems, structural
supports
• management issue: who takes on responsibility for their design?
Establishing Architecture Chunks
• some chunks of a complex system may be complex
systems themselves
• each of these may have its own architecture
Creating Detailed Interface Specifications
• as system-level design progresses, fundamental interactions need more refinement
• as a result, specification of the interfaces need to be clarified • interfaces represent “contracts” between chunks