Week 9 - Systems Engineering and Analysis
description
Transcript of Week 9 - Systems Engineering and Analysis
![Page 1: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/1.jpg)
1
Week 9 - Systems Engineering
System Wide Requirements – The ‘Ilities’
Reliability
How bad can a “weakest link” problem be? This is the “Silver Bridge” at Point Pleasant, WV, which collapsed into the Ohio River during rush hour on Dec 15, 1967. The cause was the failure of a single eyebar in the suspension chain, due to a defect 0.1 inch deep.
![Page 2: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/2.jpg)
Worst case reliability - Engineering disasters…
• AT&T Network Crash story (See http://users.csc.calpoly.edu/~jdalbey/SWE/Papers/att_collapse.html. )
• Kansas City Hotel story (See for example http://ethics.tamu.edu/Portals/3/Case%20Studies/HyattRegency.pdf. )
• Challenger (discussed here)
2
AT&T network map
![Page 3: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/3.jpg)
3
The Ilities
• Quality• Reliability –
– Blanchard and Fabrycky, Systems Engineering and Analysis, 4th Ed. – Ch 12
– Wasson – Ch 50
• Interoperability• Usability• Maintainability• Serviceability• Producibility and Disposability
![Page 4: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/4.jpg)
4
The Ilities-2
• All are System Wide in Scope.• All are desirable system outcomes.• Technical, engineering, mathematical
definitions behind each one.• Included as Technology and System-
Wide requirements when critical enough.
• How to measure and quantify ?
![Page 5: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/5.jpg)
5
The Second ‘Ility’ - Reliability
• Our focus –1. Reliability Definitions.2. Series and Parallel Systems.3. Reliability Improvement Methods.4. Reliability Prediction and Testing.5. Risk (Ch. 19)
![Page 6: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/6.jpg)
6
Definition of Reliability
• The reliability of an item is the probability that it will adequately perform its function for a specified period of time.
• ‘Time’ is involved – specify units – hrs, miles, etc.– specify time duration.
![Page 7: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/7.jpg)
7
Reliability vs. Quality
• Reliability : includes passage of time.• Quality : a static descriptor.
– Or, may include Reliability as one component
• High reliability implies high quality – converse not true.
• Tire example – – Ones made in 1960 and 2000.– Both ‘high quality’ wrt current standards– New ones last longer – more reliable.
• Microsoft example –– Quality means three dimensions – Reliability, Feature Set, and
Schedule!
![Page 8: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/8.jpg)
8
Reliability Example
• Space Shuttle Challenger accident on January 28, 1986.
• O-Rings sealed the joints in the solid rocket motors.
• Engineers used two O-rings – one for ‘backup’.
![Page 9: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/9.jpg)
9
![Page 10: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/10.jpg)
10
![Page 11: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/11.jpg)
11
![Page 12: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/12.jpg)
12
Launch Details
• During flight, the rocket casing ‘bulges’ which widens the gap between sections.
• Due to low temperature and bulging effect – both O-rings failed resulting in accident. (not independent systems).
• Launch ‘reliability’ calculated (after the accident) as 0.87 at 31 deg F. (but 0.98 at 60 deg F).
![Page 13: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/13.jpg)
13
![Page 14: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/14.jpg)
14
![Page 15: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/15.jpg)
15
![Page 16: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/16.jpg)
16
Three Aspects of Reliability
• Analysis – how to quantify, equations
• Testing – how to test
• Prediction – how do I know in advance
We’ll look at analysis first
![Page 17: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/17.jpg)
17
Measures of Reliability (B&F 12.2, Wasson Ch 50)
• Reliability Function, R(t) – probability that system will be successful for some time period t.
• R(t) = 1 – F(t)
• F(t) is the failure distribution or ‘unreliability’ function.
• Like, what are the odds of the system staying “up” for a year?
• At t = 0, R(t) = 1.0. At t = ∞, F(t) = 1.0.
![Page 18: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/18.jpg)
18
R(t) for Exponential distn.
• R(t) = 1 – F(t) =
• If ‘time to failure’ is (assumed to be) defined by Exponential Function (Constant Failure Rate) then –
f(t) =
t
dttf )(
)/(1
te
Integral from t to infinity is “the rest of the probability” beyond t, i.e., the probability it didn’t fail up to time t.
Like, if half fail in year 1, then half of the remaining ones will fail in year 2, etc.
![Page 19: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/19.jpg)
19
Resulting R(t) function
•R(t) =
• Mean life () is average lifetime of all items considered.
• For exponential distribution, MTBF is
et / This is the accumulated value,
what you get doing the integration.
![Page 20: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/20.jpg)
20
Failure rate and MTBF
• R(t) = =
is “instantaneous failure rate”• M or are MTBF.
MTBF
eMt /
et
![Page 21: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/21.jpg)
21
Wasson MTTF
Light bulb failures
![Page 22: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/22.jpg)
22
Wasson MTBF
• Wasson suggests
– MTBF = MTTF + MTTR
• Mean Time Between Failures• Mean Time To Failure• Mean Time To Repair
– Since MTTR is small, MTBF approx = MTTF
![Page 23: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/23.jpg)
27
The Failure Rate
• Failure Rate is:
• Number of Failures/Total Operating Hrs
• Failure rate expressed as failures per hour, failures per million hours, etc.
![Page 24: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/24.jpg)
28
Failure Rate Example• 10 Components tested for 600 hrs.
• So the other 5 lasted the full 600 hours.• Total of 4180 hours in the test, for all 10.• Failure Rate per hr, 5/4180 = 0.001196• MTBF= ?? (This is a prediction for all.)
Component Failure (hrs)1 752 1253 1304 3255 525
![Page 25: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/25.jpg)
29
Reliability Nomograph - Fig 12.3
• For exponential distribution.
• Relationship between MTBF, , R(t).
• Example : MTBF is 200 hrs (0.005) and operating time is 2 hrs – then R(t) =0.99
![Page 26: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/26.jpg)
30
et
R
MTBF
![Page 27: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/27.jpg)
31
Failure Rates vs. Life
![Page 28: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/28.jpg)
32
Wasson – Bathtub Curve
‘Burn-in’ of electronics devices
![Page 29: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/29.jpg)
33
Wasson – Electronic Equip
![Page 30: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/30.jpg)
34
Reliability of Component Relationships
• Engineers assemble systems from components and sub-systems.
• How to analyze the reliability of the ‘whole’ based on structure and component reliabilities.
• Two simple structures : series and parallel.
![Page 31: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/31.jpg)
35
Series Networks
• Series components – all must function.• R = (RA ) (RB ) (RC) (multiply R’s)
• R = (add ’s)
A B C
etnBA )...(
![Page 32: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/32.jpg)
36
Sample Problem – Series
• Series system of four components, expected to operate to 1000 hrs.
• MTBFs – – A (6000 hrs), B(4500), C(10500), D(3200)
• What is R for the series system ??– (Ans. 0.4507)
• What is MTBF for the series system ??
![Page 33: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/33.jpg)
38
Parallel Networks• Parallel components – all must fail for
system to fail.
• R = RA + RB – (RARB)
• R = 1 – (1 – RA) (1 – RB) (1 – RC)… – (n components)
A
B
C
![Page 34: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/34.jpg)
39
Reliability and Redundancy
![Page 35: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/35.jpg)
40
Series and Parallel Networks
• Figure 12.10- Reduce parallel blocks to equivalent series element.
![Page 36: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/36.jpg)
41
Sample Problems
• Figure 12.10 ‘a’ and ‘c’.
– RA = 0.99
– RB = 0.96
– RC = 0.98
– RD = 0.92
– RE = 0.8
– RF = 0.8
![Page 37: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/37.jpg)
42
Related Figures of Merit (FOM)
• Mean Time Between Maintenance – MTBM– Scheduled– Unscheduled
• Availability – A– Probability that system when used under stated
conditions in ‘ideal/actual’ operational environment will operate satisfactorily.
• Wasson – RAM– Reliability– Availability – Maintenance
![Page 38: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/38.jpg)
43
Figure 12.11• How to calculate
MTBF, MTBM ??
• MTBF – 58 failed ?• MTBM – 100 ‘failed’ ?
A Common Service Shop Finding – NTF, no trouble
found 43
![Page 39: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/39.jpg)
44
Service Life Extension
![Page 40: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/40.jpg)
45
Reliability and System Life Cycles – section 12.3
• What Reliability should the System have to accomplish mission, over life cycle, under expected environment.
• Requirements that affect reliability– System performance factors,– Mission profile,– Use conditions, duty cycle, etc.– Environment – temp, vibration, etc.
![Page 41: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/41.jpg)
46
Review of Key Concepts
• ‘Ilities’ are System Wide Requirements.• Specify ‘Reliability’ as MTBF, MTBM,
R(t),..
• Flow down/allocate top level requirements to functional blocks (Fig 12.16,17)– We have functional architecture.– We have series/parallel tools to do this.
![Page 42: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/42.jpg)
47
Reliability Flow Down
MTBFs have to get larger- See slide 33
Series : Add lambdas
Series : Add lambdas
![Page 43: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/43.jpg)
58
Reliability Prediction
1. Predict based on similar equipment – easy but inaccurate.
2. Predict from Parts Count
3. Predict from Life/Stress Analysis
![Page 44: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/44.jpg)
59
Example – Parts Count
where: n = Number of part categories Ni = Quantity of ith part λ= Failure rate of ith part π= Quality Factor of ith part(handbook)
![Page 45: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/45.jpg)
60
where: n = Number of part categories Ni = Quantity of ith part λ= Failure rate of ith part π= Quality Factor of ith part(handbook)
MTBF
![Page 46: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/46.jpg)
61
Reliability Testing - 12.6
• Part of test and qualification.• Assure that MTBF requirements are met.
• Testing :– Either accept, reject, continue test (Fig.
12.30)– Test under simulated mission profile (Fig
12.31)‘Run some tests’ – how confident are we in the results ??
![Page 47: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/47.jpg)
62
Sequential Test Plan
![Page 48: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/48.jpg)
63
Simulated Mission Profile
![Page 49: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/49.jpg)
64
Reliability Testing-2• Establish criteria for accept, reject, and
risks of false decisions.
• Equations 12.29, 12.30. Determine regions for accept, reject, continue, with defined acceptance risks.
![Page 50: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/50.jpg)
65
Example MIL-STD-781
Fig. 12.32
![Page 51: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/51.jpg)
66
Actual Test Conditions – Fig. 12-33
• MTBF=400• Max time = 4000• Failures noted and fixed.• Accept at 3200 hrs.
![Page 52: Week 9 - Systems Engineering and Analysis](https://reader036.fdocuments.in/reader036/viewer/2022062322/568145f5550346895db2fbae/html5/thumbnails/52.jpg)
67
Test Results