Conference Summary

1
Conference Summary
Product Architecture Modularity ? ? ? ? ?
? ? ?
? ? ? ? One Platform, Many
Customers November 2-3, 1998

• Steven Eppinger
• Conference Chairman
• MIT Sloan School of Management

2
Architecture and Modularity

• Integral vs. modular architecture
• Types of modularity
• Define and manage interfaces

3
Mass Customization

• Link customer information to
• production system
• Types of customization
• how to evolve to each one
• Learn from relationships with customers

4
Architecture Flows From Strategy

• Customers Functionality Modules
• Modules Configuration Variety

5
Implementation Roles

• Architects define structure functions
• System Engineers handle system-level issues
  (FITs)

6
Vehicle Architectures

• Architecture Interface Definition
• Coupled to concept development
• New architecture doubles development cost!

7
Portfolio Planning

• Structured development process, coupled with
  business case analysis
• Key decisions
• of architectures
• vehicles for each
• timing of projects

8
Software Architectures

• Reusable modules
• Interfaces require contracts
• Standards enable partnerships

9
Customer-Driven Business Model

• Build-to-order, direct sales enabled by
  information flow
• Access to information changes the customer
  experience and the supply chain operation

10
Benefits and Penalties of Modularity

• Lower costs over product family
• Reduces risk
• Develops standards
• Performance penalty
• Platform overhead
• Commitment to architecture
• Aesthetics may suffer

11
Tools and Methods

• Voice of the Customer
• Features Matrix
• Define/communicate
• partitioning interfaces
• Updates and reports

12
Common Themes

• Platform/family planning is essential
• Manage interactions across modules
• Use customer information to plan and customize
  products

13
THANK YOU!!!!
Product Architecture Modularity ? ? ? ? ?
? ? ?
? ? ? ? One Platform, Many
Customers November 2-3, 1998

• www.ManagementRoundtable.com