EPD-Concept To Product-1
EPD-Concept To Product-1
EPD-Concept To Product-1
Design
(EPD)
Unni A M,SOE,CUSAT
Why a course on EPD ?
To make the “Graduating” electronics engineers aware and
familiar with “reallife” Electronics Product Design process,
constrains, challenges etc., and thereby make them more
competent and comfortable in their carrier (in electronics
engineering).
Unni A M,SOE,CUSAT
Why a course on EPD ?
“In the past, most electrical engineers could content to work on their
circuits or with a team on circuit related problems and
technologies. If you are still working that way, you have got to
change now.
Today’s designers can’t be content to design circuits and remain
disconnected from the overall problems and opportunities of
product design. The days of circuit designers are over.
Today you have got to be a product designer. Yes designing
circuits, writing software, and developing test strategies will
continue to be important. However these activities have to be
undertaken in the broad sense of product design.”
Unni A M,SOE,CUSAT
Why a course on EPD ?
……………Engineers have to start thinking of themselves as
product designers and they have to develop the skills that
get them involved with almost all facets of product design.
…... The future belongs to the engineers who can take a
look at the “big picture” of proper product design”.
Unni A M,SOE,CUSAT
What should be covered in EPD ?
• Electronics Circuit
• Packaging and interconnection (Enclosure/ PCB)
• Structural
• Aesthetics
• Ergonomics
• Thermal
• Signal Integrity & EMI/EMC
• Product development Process and Project management
Unni A M,SOE,CUSAT
Module 1
From Requirement to Product
• Definitions of Science, Engineering, and Technology
• Engineering design as real life problem solving
• Requirement analysis of Electronic products
• Formulation of product requirement specifications and target
specifications.
• The design process
• Computer Aided Design
• Product conceptualization; Product architecture; Product synthesis
Design analysis
• Portable Electronic Design Factors.
• Product Life Cycle, Representation of development tasks using
standard tools showing timing and dependencies
Unni A M,SOE,CUSAT
Module 2
Electronic Product Design
• Various dimensions of Electronic Product Design
• Industrial design
• Aesthetics and Ergonomics Inputs, control and display
interface
• DFx methodologies in product design (DFM/ DFA/ DFT)
• Quality by design
• Sketches and Engineering drawing of Electronic products.
Unni A M,SOE,CUSAT
Module 3
Thermal Design of Electronic Equipment
• Heat generation and modes of heat transfer in Electronic products
• Selection of Power Semiconductor Devices based on thermal
considerations
• Selection/Design of Heat Sinks Factors affecting the design of
heat sinks and its cooling effectiveness
• Assembly of components on heat sinks
• Electrical analogue of thermal circuits
• Enclosure design of Electronic Equipments and thermal
considerations
• Design guidelines for Ventilations Forced cooling Heat pipes for
electronic cooling applications
• Cooling of power intensive IC chips
• Thermal Considerations in PCB design.
Unni A M,SOE,CUSAT
Module 4
EMI & Design for EMC
• Electric Field Interference, Magnetic Field Interference, Conducted
noise etc. in Electronic Equipment
• Sources of EMI, inter and intra system EMI
• EMI standards and Regulations
• Noise performance of passive components Cabling,
• Shielding and Grounding
• Cables, Connectors, components and equipments for interference
suppression/minimization Intrinsic noise sources and their
management
• PCB design guidelines for EM compatibility.
Unni A M,SOE,CUSAT
Module 5
Electronics Design Automation (EDA) Tools
• PCB design process Design rules for analog, digital, high
frequency, powerelectronic and MW PCBs.
• Introduction to PC based Electronic Design Automation Tools:
Schematic Capture, Circuit Simulation, Layout Design etc.
• Features of such packages with reference to popular EDA tools
such as Orcad
• Designing PCBs for manufacturability Design considerations for
power efficiency.
Unni A M,SOE,CUSAT
Module 1
From Requirement to Product
• Definitions of Science, Engineering, and Technology
• Engineering design as real life problem solving
• Requirement analysis of Electronic products
• Formulation of product requirement specifications and target
specifications.
• The design process
• Computer Aided Design
• Product conceptualization; Product architecture; Product synthesis
Design analysis
• Portable Electronic Design Factors.
• Product Life Cycle, Representation of development tasks using
standard tools showing timing and dependencies
Unni A M,SOE,CUSAT
Module 1
Engineering Design & Quality
• Engineering:
Is the profession in which Knowledge, Gained by Study,
Experience, and Practice is applied with Judgment to
develop ways to utilize economically the material, and
forces of nature for the benefit of mankind.
Is the Analysis, Design, Construction, Verification and
Management of Technical entities
Is the Process of Investigation of how to Solve Problems
Unni A M,SOE,CUSAT
• Economic
• Efficient
• Ergonomic
• Esthetics
• Environmental
Unni A M,SOE,CUSAT
Module 1
Engineering – Design & Quality
• Design
Is the Process of Making things people want or useful to
the People
• Quality
Consists of those product features which meets the needs
of the customer and thereby provide product
satisfaction
Is Fitness for Purpose
Unni A M,SOE,CUSAT
Real Life Problem Solving ?
Swamy and His Friends – By R.K Narayan
If 15 mangoes cost 5 rupees, what is the cost of 3 mangoes?
? Are all the 30 mangoes of equal size
? Are they of same quality?, and ripped
? Which three are the mangoes for which cost is to be
calculated etc…
Unni A M,SOE,CUSAT
“Reallife” problem and “Ideal problem”
• Real problems will have domain dependant constraints;
whereas ideal problem is domain independent.
• Ideal problem will have a unique (right) solution, whereas
reallife problems will always have multiple right solutions.
• The criteria for checking value of a solution for reallife
problem is its “appropriateness” in the specified context/
domain.
Unni A M,SOE,CUSAT
Engineers should THINK like “Swamy” !
Unni A M,SOE,CUSAT
From
Requirement
to
Product
Unni A M,SOE,CUSAT
Product Development – Life Cycle
• Frontend process
• Requirement analysis .
• Requirement driven & Technology driven
∀ Basic features : (implicit requirements)
∀ Specified features: (explicit requirements)
∀ Excitement features:
• High bandwidth bidirectional communication”
between groups/ professionals
Unni A M,SOE,CUSAT
Product Development – Life Cycle
• Requirement analysis .
∀ Identifying customer needs:
ο Gather raw data
ο Interpret raw data in terms of customer needs
ο Organize needs into hierarchy of primary, secondary and
tertiary needs as applicable.
ο Establish relative importance of needs
ο Review the result
∀ Establish target specification
∀ (precise description of what product has to do)
Unni A M,SOE,CUSAT
Product Development – Life Cycle
• Concept Development .
∀ Concept Generation Goal is to thoroughly explore the
product concepts that may address the customer needs
∀ Concept selection (analysis of multiple concepts and identifying
the most promising concept)
∀ Setting final specification (Technical model, Cost model etc.)
Unni A M,SOE,CUSAT
Product Development – Life Cycle
• System level design .
∀ Definition of product architecture and decomposition of
product into subsystems and components (with its interface
specifications)
• Detailed design
∀ Complete specification of the geometry, material, tolerance,
interfaces, Considering DFM/ DFA, other standards
specifications etc. (Schematic, PCB, BOM, FAB/ASSY Files etc.)
Unni A M,SOE,CUSAT
Product Development – Life Cycle
• Product engineering (Prototype) & refinement
• Production ramp up
Unni A M,SOE,CUSAT
Unni A M,SOE,CUSAT
Unni A M,SOE,CUSAT
Unni A M,SOE,CUSAT
Unni A M,SOE,CUSAT
Unni A M,SOE,CUSAT
Unni A M,SOE,CUSAT
Unni A M,SOE,CUSAT
Project Development Issues
Understanding Customer requirements in full depth and
breadth.
Requirements without details
Lack of understanding/ misunderstandings (assumptions)
Change in requirements
Estimation of Time and efforts
How complex are the requirements
What is our expertise/ capability/ availability
Develop the system to meet the actual requirements
All Requirements in complete (~ Incomplete )
Unni A M,SOE,CUSAT
Models and Modeling
“A Picture Speaks A Thousand Words”
“A Model is a Simplification of Reality”
Unni A M,SOE,CUSAT
Models and Modeling
• Models are usually described in Visual language (information
expressed by Graphical Symbols and Connections)
• Modeling Helps us to
• Visualize a system as it is (or as we want it to be
• Specify the structure/ behavior of a system
• Provides a Template that guides us in constructing a
system
• Document the decision we have made
• A Usable Model Should be
• Accurate & Consistent
• Easy to Communicate, Change, and Understand
Unni A M,SOE,CUSAT
Thanks
Unni A M,SOE,CUSAT