Beruflich Dokumente
Kultur Dokumente
Case Study :
Case Study 1: Reliability Engineering in Mechanical Domain 20 Mins
Case Study 2: Reliability Engineering in Hardware Domain 20 Mins
Case Study 3: Reliability in Wind Energy 20 Mins
Q&A 15 Mins
$7.6 BILLION
32 COUNTRIES
119,000 P E O P L E
Access to one of
Best Reliability
Team in the
Industry
Strong experience
from different
domain brings in
knowledge base of
Do and Don’ts
Methodologies,
processes and best
practices leverage
Experience on
reliability tools /
Engineering TEAM software
3 Copyright © 2018 HCL Technologies Limited | www.hcltech.com
What is Reliability?
Failure Rate
Reliability % PPM
Warranty Maintainability
Availability
5 Copyright © 2018 HCL Technologies Limited | www.hcltech.com
Why we should do Reliability?
• To determine the that to what extent the system/component can endure before
failing.
• To uncover all potential failures which could be available in the field and to
reduce the surprise of failures in the field.
• To determine the Failure rate , Maintenance Period and other parameters related
to the system/component.
6 | Copyright © 2019 HCL Technologies Limited | www.hcltech.com
Cost of Unreliability
COST OF FAILURE Before we go deeper, lets refresh again to know WHY should I learn Reliability?
• Unreliable System fails very often.
• The costs of this unreliability is very high
• Major affect on the company’s reputation and brand name.
• Reliability Engineering analysis helps to minimize not just cost of failure, but entire life cycle cost.
•Warranty Costs
• Field Repair Costs
Baseline
Study
PRAT
ʎ
Process
FTA Systematic
Capability IEC 61511
FMEDA SPFM
EN 50129 Off-Road
Reliability SAFETY Vehicles
LPFM Railway
Prediction LIFECYCLE
SUPPORT
BI / Visualization
SAS
Tableau
QlikView
Power BI
MS Excel
Data Processing
SAS
SAP
Minitab
Data Storage
MS Access
MySQL
Challenges Faced:
• Customer was denied new business
by an major truck manufacturer in
North America owing to their poor
warranty, poor reliability and the
Defining operating Identified Failure modes
complication in the new NPD conditions and functional from warranty analysis and
requirements FMEA
• The OEM demanded higher
reliability demonstration from the
customer to award the business
• The system is more complicated
than the existing HVAC unit Calculate Sample size and test
duration
Accelerated Test Profile
15 Copyright © 2018 HCL Technologies Limited | www.hcltech.com
Recent Researches-Replication of Field Scenario in Testing
Conventional Vibration testing Measure and Record
• Based on any international standard • Measure actual vibration
• Use a PSD vs HZ, with break point from the field or test track
table • Record the vibration data
• Most of the time have higher
excitation energy level Analyze, edit and combine
• Remove dead space,
Disadvantage: unwanted recordings
• Do not represent actual field condition • Combine multiple waveforms
• Total fatigue damage in the test is not
equivalent to field condition
• Low shock levels
Dead Space
• Do not uncover field failures
Design import & Life Profile modelling 3D distribution of Time to Failure plots
PCB modelling & Meshing stress
• Electrical Overstress
− Based on Voltage / Current / Power rating – Rated Vs. Actual
• Thermal Overstress
− Calculation of Junction Temperature based on Power Dissipated and actual Ambient Temperatures
− IR Imaging to assess the Hot Spots
Thermal De-rating
• Due to advancement in computing power of PCs, it is now possible to extend this to Electronic CCAs.
Start
• Plated through hole (PTH) lifetime
Collect Inputs
• Inputs
− ODB++ file of CCA
− Operational Profile
▫ Thermal – Cycles
▫ Mechanical Shock Profile
▫ Harmonic Levels
− Part Details
− PCB – Stackup & Layer info
• To uncover latent defects in product design, component selection and / or manufacturing process that would not
otherwise be found through conventional qualification methods.
Can we reduce the cost spent by the company for the products which is already existing in the field ?
Your Views ?
Add-on:
We can provide Predictive Modelling (Machine Learning) for Maintenance
Create a tool based to perform the analysis repetitive for all sub-systems
Provide the inputs of failures to design team for re-design of the system
Gather the data from SQL Via R- Programming. Perform Filtering, Scrubbing of unwanted data from the data table and have a much better quality output.
You can also use Python as an alternative / any other language to do it.
You can perform the same in SQL as well, the reason to do this is to visualize the raw data and understand how the population is working in the field.
With the output data of time to failure from R-Studio, we can plot the Weibull graph to get the eta and beta values.
This shows how the failures are distributed in the field for the deployed products
You can perform the analysis either using Minitab software or dedicated software's like Weibull++.
With the output data of reliability parameters, reliability block diagram is performed and given as input
This diagram represents the system level simulation of reliability and all the input from each components from previous step are given as input into each block.
You can perform the analysis using BlockSim which are block based design based on either the components are connected in series and parallel.
From the above analysis Maintenance Strategy and Cost Optimization is done for the system and sub-system.
The time to replace the components are identified from this analysis, which gives maximum availability of the system and on the meantime also increases the
reliability.