robin/Robin_PHD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

.

Browse Source
This commit is contained in:
Robin Clark 2010-10-12 17:44:01 +01:00
parent 7e6f1477d6
commit 4ad9c0dfa2
12 changed files with 11990 additions and 5987 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

311
fmmd_concept/fmmd_concept.tex
View File

@ -68,7 +68,18 @@ are held in a computer program, we can determine if the model is complete
%OK need to describe the need for it
\section{The need for a new failure mode modelling methodology}
In summary.
\paragraph{Ideal Static failure mode methodology}
An ideal Static failure mode methodology would build a failure mode model
from which the the other four could be derived.
It would address the short-comings in the other methodologies, and
would have a user friendly interface, with a visual (rather than mathematical/formal) syntax with icons
to represent the results of analysis phases.
There are four static analysis failure mode methodologies in common use.
Each has its advantages and drawbacks, and each is suited for
a different phase in the product life cycle.
These four methodologies are discussed briefly below.
\subsection { FTA }
@ -90,19 +101,53 @@ system level outcomes.
\subsection { FMEA }
This places a burden of taking individual component failure modes
and trying to determine what affects this will have at SYSTEM level.
Justifications for this methodology are often statistical and Bayes Theorem \cite{probstat}
is often cited.
This lacks precision, or in other words, determinability prediction accuracy,
as often the component failure mode cannt be proven to cause a SYSTEM level failure, only to make it more likely.
Also, it can miss combinations of failure modes that will cause SYSTEM level errors.
This is an early static analysis methodology, and concentrates
on SYSTEM level errors which have been investigated.
The investigation will typically point to a particular failure
of a component.
The methodology is now applied to find the significance of the failure.
Its is based on a simple equation where $S$ ranks the severity (or cost \cite{fmea}) of the identified SYSTEM failure,
$O$ its occurrance, and $D$ giving the failures detectability. Mulipliying these
together,
gives a risk probability number, i.e. $RPN = S \times O \times D$.
This gives in effect
a prioritised todo list, with higher the $RPN$ values being the most urgent.
\subsection{FMECA}
Failure mode, effects, and criticality analysis (FMECDA) extends FMEA.
This is a bottom up methodology, which takes component failure modes
and traces them to the SYSTEM level failures. The components
have reliability data and this can be used to predict the
failure statistics in the design stage \cite{mil1992}.
It can do this using probability \footnote{for a given component failure mode there will be a $\Beta$ value, the
probability that the component failure mode will cause a given SYSTEM failure}.
%
This lacks precision, or in other words, determinability prediction accuracy \cite{fafmea},
as often the component failure mode can't be proven to cause a SYSTEM level failure, but
assigned a probability $\Beta$ fator by the design engineer.
%Also, it can miss combinations of failure modes that will cause SYSTEM level errors.
%
The results, as with FMEA are an $RPN$ number determing the significance of the SYSTEM fault.
%%-WIKI- Failure mode, effects, and criticality analysis (FMECA) is an extension of failure mode and effects analysis (FMEA).
%%-WIKI- FMEA is a a bottom-up, inductive analytical method which may be performed at either the functional or
%%-WIKI- piece-part level. FMECA extends FMEA by including a criticality analysis, which is used to chart the
%%-WIKI- probability of failure modes against the severity of their consequences. The result highlights failure modes with relatively high probability
%%-WIKI- and severity of consequences, allowing remedial effort to be directed where it will produce the greatest value.
%%-WIKI- FMECA tends to be preferred over FMEA in space and North Atlantic Treaty Organization (NATO) military applications,
%%-WIKI- while various forms of FMEA predominate in other industries.
\subsection { FMEDA or Statistical Analyis }
This is a process that takes all the components in a system,
and from the failure modes of those components
tnote{for a given component failure mode there will be a $\Beta$ value, the
probability that the component failure mode will cause a given SYSTEM failure}.
calculates a risk factor for each.
The risk factors of all the component failure modes are summed and
give a value for the `safety level' for the equipment in a given environment.
@ -140,11 +185,13 @@ This suffers from the same problems of
lack of determinability prediction accuracy, as FMEA above.
We have to decide how particular components failing will impact ot the SYSTEM or top level.
This involves a `leap of faith'. For instance a resistor failing in a sensor cirrcuit
may be part of a critical montioring function. But the analyst is put in a position
may be part of a critical montioring function.
The analyst is now put in a position
where he must assign a critical failure possibility to it. There is no analysis
of how that resistor would/could affect that circuit, but because of the circuitry
it is part of critical section it is linked to a critical system level fault.
There is no cause and effect analysis for the failure modes. Unintended side
effects that lead to failure can be missed.
By this we may have the MTTF of some critical component failure
modes, but we can only guess, in most cases what the safety case outcome
@ -168,122 +215,144 @@ of the Safety Integrity Levels (SIL) of EN61508 \cite{en61508}.
\item It should have a formal basis, that is to say, it should be able to produce mathematical proofs
for its results.
\item It should be capable of producing reliability and danger evaluation statistics.
\item It should be easy to use.
\item It should be easy to use, Ideally useing a graphical syntax (as oppossed to a formal mathematical one).
\item From the top down the failure mode model should follow a logical de-composition of the functionality
to smaller and smaller functional modules \cite{maikowski}.
\end{itemize}
\section{building blocks of a safety critical systen}
\section{Proposed Methodology}
This section looks at common features in a safety critical system and
then looks at the building blocks of these systems
and their characteristics.
The proposed methodology will be bottom-up. to fulfill the logical de-composition requirement
it must build {\fg}s from the bottom-up. These are minimal collections of components
that work together to perform a simple function.
We can perform a failure mode effects analysis on each of the component failure
modes within the {\fg}. We can thus ensure that all component failure modes
are covered. We can then treat the {\fg} as a `black box' or component in its own right.
We can now look at how the {\fg} can fail. Many of the component failure modes will
cause the same failure symptoms in the {fg} fialure behaviour.
We can collect these failures as common symptoms.
When we have out set of symptoms, we can now create
a {\dc}. The {\dc} will have as its set of failures
modes, the collected symptoms of the {\fg}.
\subsection{what is a safety critical system?}
DEFINITIONS GET REFS
TYPICALLY HAS MECHANICAL, ELECTRONIC and SOFTWARE
actuators control intelligence
\subsection{An example : industrial burner}
An industrial burner is a nice example of a safety critical system.
It has some lethal risks and some environmental.
It could, by igniting an explosive mixture, cause an explosion.
By burning incorrect proportions of fuel and air, it could be ineffecient and waste
resources, or worse could cause poisonous burning (typically carbon monoxide, but also
where flame temperature is very high, can produce NOX emmissions).
To prevent igniting an explosive mixture, air is pumped though the furnace
chamber on start-up, and this is verified with an air pressure switch.
NEED A DIAGRAM HERE
NEED A STATE CHART TOO
It is interesting here to compare how the different methodologies
would deal with a particular sub-system in the burner controller
and compare how they analyse it.
The Flame scanner is a good example for this.
We shall consider a simple infra red (IR) flame scanner.
This is in the form of an IR sensitive resistor.
The flame type we will be looking for will have a characteristic
flicker frequency of around 13Hz.
The circuit is then simply a resitor voltage divider connected to
a micro-controller reading the voltage.
The flame scanner is thus a two resistor voltage divider.
\subsection{The Flame Scanner}
\subsubsection{Macro FTA perspective}
SHOW ALL TOP LEVEL FAULTS. EXPLOSION, POISONOUS BURNING CO, POISONOUS BURNING NOX, FAILS TO LIGHT etc
Follow the explosion tree down to flame scanner fails ON, and OFF
etc
\subsubsection{Macro FMEA/Statistical perspective}
Each of the resistors is considered critical, in the statistical case, and so the MTTF
is added inot the DANGEROUS section.
For FMEA the resistor failures add up to the SYSTEM level, show this is inappropriate
and makes several jumps in applied knowledge, thus Bayes theorem etc
\subsubsection{Micro FMMD perspective}
Here show how the flame scanner becomes a black box, or component in itself.
How it is now available to be integrated into higher level designs.
%and then an ignition position is checked.
%Initially a pilot flame is started and when this is stable, the main
%flame is fired.
%To check the stability of the flame, a flame scanner is required.
%To mix the fuel and air, motors to position valves are generally used.
%To prevent fuel leakage into the furnace, safety shut-off valves are used \footnote{These generally open slowly under power, and when power is removed `slam shut'. Thus
%in the event of a general power failure, the default to safe behaviour.}
Because we can now have a {\dc} we can use these to form
new {\fg}s and we can build a hierarchical model of the system failure modes.
Motors controlling air and fuel flow
safety chain to power for shutdown valves
safety shutdown valves on fuel
flame sensor
air pressure sensor
\section{Base Level Components}
A common factor with all safety critical systems, is
base level -or- bought in components. Be these
electrical, mechanical or firmware, they should all
have known failure modes.
\subsection { Failure modes defining the component}
We can consider each bought-in component as a base level component,
and it should have an associated set of failure modes.
\subsection { Complication of multiple failure modes }
A very complicated component, like an integrated circuit or perhaps a servo motor, has
a set of failure modes, where several things could go worng with it within the $\tau$ period.
This is a simultaneous failure, or more than one failure mode being active during the same time period.
\section{FMMD Proposed Methology Outline}
fire away, essentially the elevator pitch
\subsection{Treating a functional group as a component}
\subsection{Using a derived component in designs}
\section{Building a failure Mode model Hierarchy}
AND the hierarchy...
Probab about 3 pages
%%- \section{building blocks of a safety critical systen}
%%-
%%- This section looks at common features in a safety critical system and
%%- then looks at the building blocks of these systems
%%- and their characteristics.
%%-
%%- \subsection{what is a safety critical system?}
%%-
%%- DEFINITIONS GET REFS
%%-
%%-
%%- TYPICALLY HAS MECHANICAL, ELECTRONIC and SOFTWARE
%%- actuators control intelligence
%%-
%%- \subsection{An example : industrial burner}
%%-
%%- An industrial burner is a nice example of a safety critical system.
%%- It has some lethal risks and some environmental.
%%- It could, by igniting an explosive mixture, cause an explosion.
%%- By burning incorrect proportions of fuel and air, it could be ineffecient and waste
%%- resources, or worse could cause poisonous burning (typically carbon monoxide, but also
%%- where flame temperature is very high, can produce NOX emmissions).
%%-
%%- To prevent igniting an explosive mixture, air is pumped though the furnace
%%- chamber on start-up, and this is verified with an air pressure switch.
%%-
%%-
%%- NEED A DIAGRAM HERE
%%-
%%-
%%- NEED A STATE CHART TOO
%%-
%%- It is interesting here to compare how the different methodologies
%%- would deal with a particular sub-system in the burner controller
%%- and compare how they analyse it.
%%- The Flame scanner is a good example for this.
%%- We shall consider a simple infra red (IR) flame scanner.
%%- This is in the form of an IR sensitive resistor.
%%- The flame type we will be looking for will have a characteristic
%%- flicker frequency of around 13Hz.
%%- The circuit is then simply a resitor voltage divider connected to
%%- a micro-controller reading the voltage.
%%- The flame scanner is thus a two resistor voltage divider.
%%-
%%- \subsection{The Flame Scanner}
%%- \subsubsection{Macro FTA perspective}
%%-
%%- SHOW ALL TOP LEVEL FAULTS. EXPLOSION, POISONOUS BURNING CO, POISONOUS BURNING NOX, FAILS TO LIGHT etc
%%-
%%- Follow the explosion tree down to flame scanner fails ON, and OFF
%%-
%%- etc
%%- \subsubsection{Macro FMEA/Statistical perspective}
%%-
%%- Each of the resistors is considered critical, in the statistical case, and so the MTTF
%%- is added inot the DANGEROUS section.
%%-
%%- For FMEA the resistor failures add up to the SYSTEM level, show this is inappropriate
%%- and makes several jumps in applied knowledge, thus Bayes theorem etc
%%-
%%- \subsubsection{Micro FMMD perspective}
%%-
%%-
%%- Here show how the flame scanner becomes a black box, or component in itself.
%%- How it is now available to be integrated into higher level designs.
%%-
%%- %and then an ignition position is checked.
%%- %Initially a pilot flame is started and when this is stable, the main
%%- %flame is fired.
%%- %To check the stability of the flame, a flame scanner is required.
%%- %To mix the fuel and air, motors to position valves are generally used.
%%- %To prevent fuel leakage into the furnace, safety shut-off valves are used \footnote{These generally open slowly under power, and when power is removed `slam shut'. Thus
%%- %in the event of a general power failure, the default to safe behaviour.}
%%-
%%-
%%-
%%-
%%- Motors controlling air and fuel flow
%%- safety chain to power for shutdown valves
%%- safety shutdown valves on fuel
%%- flame sensor
%%- air pressure sensor
%%-
%%-
%%- \section{Base Level Components}
%%-
%%- A common factor with all safety critical systems, is
%%- base level -or- bought in components. Be these
%%- electrical, mechanical or firmware, they should all
%%- have known failure modes.
%%-
%%- \subsection { Failure modes defining the component}
%%- We can consider each bought-in component as a base level component,
%%- and it should have an associated set of failure modes.
%%-
%%-
%%-
%%- \subsection { Complication of multiple failure modes }
%%- A very complicated component, like an integrated circuit or perhaps a servo motor, has
%%- a set of failure modes, where several things could go worng with it within the $\tau$ period.
%%- This is a simultaneous failure, or more than one failure mode being active during the same time period.
%%-
%%-
%%- \section{FMMD Proposed Methology Outline}
%%-
%%- fire away, essentially the elevator pitch
%%-
%%- \subsection{Treating a functional group as a component}
%%- \subsection{Using a derived component in designs}
%%- \section{Building a failure Mode model Hierarchy}
%%-
%%- AND the hierarchy...
%%-
%%-
%%- Probab about 3 pages

17500
introduction/introduction.log
View File

File diff suppressed because it is too large Load Diff

24
introduction/introduction.tex
View File

@ -320,17 +320,25 @@ common sense of a human pilot; and if fed the incorrect sensory information
can make horrendous mistakes. This means that simply reading sensors and applying control
corrections cannot be enough.
Checking for error conditions must also be incorporated.
It could also develop an internal fault, and must be able to recognise and cope with this.
Equipment can also develop an internal faults, and strategies
must be in-pcae to recognise and cope with them.
\begin{figure}[h]
\centering
\includegraphics[width=300pt,bb=0 0 678 690,keepaspectratio=true]{introduction/mv_opamp_circuit.png}
% mv_opamp_circuit.png: 678x690 pixel, 72dpi, 23.92x24.34 cm, bb=0 0 678 690
\caption{Milli-volt amplifier with added safety Resistor}
\includegraphics[width=300pt,keepaspectratio=true]{introduction/mv_opamp_circuit.png}
% mv_opamp_circuit.png: 577x479 pixel, 72dpi, 20.35x16.90 cm, bb=0 0 577 479
\caption{Milli-Volt Amplifier with added Safety Resistor (R18)}
\label{fig:millivolt}
\end{figure}
% \begin{figure}[h]
% \centering
% \includegraphics[width=300pt,bb=0 0 678 690,keepaspectratio=true]{introduction/mv_opamp_circuit.png}
% % mv_opamp_circuit.png: 678x690 pixel, 72dpi, 23.92x24.34 cm, bb=0 0 678 690
% \caption{Milli-volt amplifier with added safety Resistor}
% \label{fig:millivolt}
% \end{figure}
%
% %5
% \begin{figure}
@ -343,10 +351,10 @@ It could also develop an internal fault, and must be able to recognise and cope
\paragraph{Component added to detect errors}
The op-amp in the circuit in figure \ref{fig:millivolt}, supplies a gain of $\approx 180$ \footnote{
applying formula for non-inverting op-amp gain\cite{aoe} $\frac{150 \times 10^3}{820}+ 1 = 183$ }.
The op-amp in the circuit in figure \ref{fig:millivolt}, supplies a gain of $\approx 184$ \footnote{
applying formula for non-inverting op-amp gain\cite{aoe} $\frac{150 \times 10^3}{820}+ 1 \approx 184$ }.
The safety case here is that
any amplified signal between 0.5 and 4 volts on the ADC will be considered in range.
any amplified signal between a range say, of 0.5 and 4 volts on the ADC will be considered in range.
This means that between 3mV and 21mV on the input correctly amplified
can be measured.\footnote{this would be a typical thermocouple amplifier circuit where milli-volt signals
are produced by the Seebeck effect\cite{aoe}}

BIN
introduction/mv_opamp_circuit.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 13 KiB

After

Width:  |  Height:  |  Size: 9.6 KiB

7
mybib.bib
View File

@ -5,6 +5,12 @@
% $Id: mybib.bib,v 1.3 2009/11/28 20:05:52 robin Exp $
@ARTICLE{fafmea,
AUTHOR = "Zigmund Bluvband, Pavel Grabov",
TITLE = "Failure Analysis of FMEA",
JOURNAL = "IEEE 1-4244-2509-9/09/",
YEAR = "2009"
}
@ARTICLE{fmeda,
AUTHOR = "John C. Grebe Dr. William M. Goble",
TITLE = "FMEDA – Accurate Product Failure Metrics",
@ -357,6 +363,7 @@ OPTissn = {},
OPTabstracts = {},
}
@TechReport{eurothermtables,
author = {Alan Brown},
title = {Thermocouple Emf TABLES and PLATINUM 100 RESISTANCE THERMOMETER TABLES},

28
standards/paper.aux
View File

@ -1,19 +1,21 @@
\relax
\bibstyle{plain}
\bibdata{vmgbibliography,mybib}
\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{1}}
\@writefile{toc}{\contentsline {subsection}{\numberline {1.1}Product Life Cycle}{1}}
\@writefile{toc}{\contentsline {section}{\numberline {2}European or `EN' Standards}{1}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Scope}{1}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Approval Process}{1}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}Legal Framework}{1}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}References}{1}}
\@writefile{toc}{\contentsline {section}{\numberline {3}North American Standards}{1}}
\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Scope}{1}}
\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Approval Process}{1}}
\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Legal Framework}{1}}
\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}References}{1}}
\@writefile{toc}{\contentsline {section}{\numberline {4}Cross Referencing}{1}}
\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Product Life Cycle with Competent Body Approval and Surveillance}}{1}}
\newlabel{fig:prod_life}{{1}{1}}
\bibstyle{plain}
\bibdata{vmgbibliography,mybib}
\@writefile{toc}{\contentsline {section}{\numberline {2}European or `EN' Standards}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Scope}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Approval Process}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}Legal Framework}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}References}{2}}
\@writefile{toc}{\contentsline {section}{\numberline {3}North American Standards}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Scope}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Approval Process}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Legal Framework}{2}}
\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}References}{2}}
\@writefile{toc}{\contentsline {section}{\numberline {4}Cross Referencing}{2}}
\@writefile{toc}{\contentsline {section}{\numberline {5}Standard in detail: EN298}{2}}
\@writefile{toc}{\contentsline {section}{\numberline {6}Standard in detail: UL1998}{2}}
\@writefile{toc}{\contentsline {section}{\numberline {7}Standard in detail: EN230}{2}}

75
standards/paper.log
View File

@ -1,15 +1,16 @@
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=pdflatex 2010.5.22) 11 JUN 2010 23:04
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2010.10.4) 12 OCT 2010 16:40
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**paper.tex
(./paper.tex
LaTeX2e <2005/12/01>
Babel <v3.8h> and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, loaded.
LaTeX2e <2009/09/24>
Babel <v3.8l> and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, sanskrit, loaded.
(/usr/share/texmf-texlive/tex/latex/base/article.cls
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo
File: size10.clo 2005/09/16 v1.4f Standard LaTeX file (size option)
File: size10.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
@ -31,18 +32,18 @@ Package: keyval 1999/03/16 v1.13 key=value parser (DPC)
\KV@toks@=\toks14
)
(/usr/share/texmf-texlive/tex/latex/graphics/graphics.sty
Package: graphics 2006/02/20 v1.0o Standard LaTeX Graphics (DPC,SPQR)
Package: graphics 2009/02/05 v1.0o Standard LaTeX Graphics (DPC,SPQR)
(/usr/share/texmf-texlive/tex/latex/graphics/trig.sty
Package: trig 1999/03/16 v1.09 sin cos tan (DPC)
)
(/etc/texmf/tex/latex/config/graphics.cfg
File: graphics.cfg 2007/01/18 v1.5 graphics configuration of teTeX/TeXLive
File: graphics.cfg 2009/08/28 v1.8 graphics configuration of TeX Live
)
Package graphics Info: Driver file: pdftex.def on input line 90.
Package graphics Info: Driver file: pdftex.def on input line 91.
(/usr/share/texmf-texlive/tex/latex/pdftex-def/pdftex.def
File: pdftex.def 2007/01/08 v0.04d Graphics/color for pdfTeX
File: pdftex.def 2009/08/25 v0.04m Graphics/color for pdfTeX
\Gread@gobject=\count87
))
\Gin@req@height=\dimen103
@ -278,12 +279,12 @@ File: pgfmodulematrix.code.tex 2008/01/15 (rcs-revision 1.1)
hs.code.tex
File: tikzlibrarytopaths.code.tex 2008/01/09 v2.00 (rcs-revision 1.1)
))) (/usr/share/texmf-texlive/tex/latex/amsfonts/amsfonts.sty
Package: amsfonts 2001/10/25 v2.2f
Package: amsfonts 2009/06/22 v3.00 Basic AMSFonts support
\@emptytoks=\toks20
\symAMSa=\mathgroup4
\symAMSb=\mathgroup5
LaTeX Font Info: Overwriting math alphabet `\mathfrak' in version `bold'
(Font) U/euf/m/n --> U/euf/b/n on input line 132.
(Font) U/euf/m/n --> U/euf/b/n on input line 96.
)
(/usr/share/texmf-texlive/tex/latex/amsmath/amsmath.sty
Package: amsmath 2000/07/18 v2.13 AMS math features
@ -381,7 +382,7 @@ LaTeX Font Info: ... okay on input line 15.
LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 15.
LaTeX Font Info: ... okay on input line 15.
(/usr/share/texmf/tex/context/base/supp-pdf.tex
(/usr/share/texmf/tex/context/base/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
\scratchcounter=\count122
\scratchdimen=\dimen157
@ -396,35 +397,39 @@ LaTeX Font Info: ... okay on input line 15.
)
LaTeX Font Info: Try loading font information for U+msa on input line 24.
(/usr/share/texmf-texlive/tex/latex/amsfonts/umsa.fd
File: umsa.fd 2002/01/19 v2.2g AMS font definitions
File: umsa.fd 2009/06/22 v3.00 AMS symbols A
)
LaTeX Font Info: Try loading font information for U+msb on input line 24.
(/usr/share/texmf-texlive/tex/latex/amsfonts/umsb.fd
File: umsb.fd 2002/01/19 v2.2g AMS font definitions
) (./standards_paper.tex)
No file paper.bbl.
File: umsb.fd 2009/06/22 v3.00 AMS symbols B
) (./standards_paper.tex
<./prod_life.jpg, id=4, 635.37375pt x 422.57875pt>
File: ./prod_life.jpg Graphic file (type jpg)
<use ./prod_life.jpg>
[1
{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2] (./paper.aux) )
{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map} <./prod_life.jpg>])
No file paper.bbl.
[2] (./paper.aux) )
Here is how much of TeX's memory you used:
8148 strings out of 95086
137558 string characters out of 1183255
184667 words of memory out of 1500000
11149 multiletter control sequences out of 10000+50000
10465 words of font info for 39 fonts, out of 1200000 for 2000
8189 strings out of 495052
137972 string characters out of 1182271
187902 words of memory out of 3000000
11197 multiletter control sequences out of 15000+50000
10456 words of font info for 39 fonts, out of 3000000 for 9000
28 hyphenation exceptions out of 8191
47i,11n,49p,350b,242s stack positions out of 5000i,500n,6000p,200000b,5000s
</usr/s
hare/texmf-texlive/fonts/type1/bluesky/cm/cmbx12.pfb></usr/share/texmf-texlive/
fonts/type1/bluesky/cm/cmbx9.pfb></usr/share/texmf-texlive/fonts/type1/bluesky/
cm/cmr10.pfb></usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmr12.pfb></usr/s
hare/texmf-texlive/fonts/type1/bluesky/cm/cmr17.pfb></usr/share/texmf-texlive/f
onts/type1/bluesky/cm/cmr9.pfb></usr/share/texmf-texlive/fonts/type1/bluesky/cm
/cmsl10.pfb>
Output written on paper.pdf (2 pages, 52324 bytes).
47i,11n,49p,350b,242s stack positions out of 5000i,500n,10000p,200000b,50000s
</usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmb
x12.pfb></usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmbx9.pfb></us
r/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmr10.pfb></usr/share/texm
f-texlive/fonts/type1/public/amsfonts/cm/cmr12.pfb></usr/share/texmf-texlive/fo
nts/type1/public/amsfonts/cm/cmr17.pfb></usr/share/texmf-texlive/fonts/type1/pu
blic/amsfonts/cm/cmr9.pfb></usr/share/texmf-texlive/fonts/type1/public/amsfonts
/cm/cmsl10.pfb>
Output written on paper.pdf (2 pages, 127654 bytes).
PDF statistics:
40 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 131072)
13 words of extra memory for PDF output out of 10000 (max. 10000000)
41 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
18 words of extra memory for PDF output out of 10000 (max. 10000000)

BIN
standards/paper.pdf
View File

Binary file not shown.

BIN
standards/prod_life.dia Normal file
View File

Binary file not shown.

BIN
standards/prod_life.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 29 KiB

7
standards/standards.tex
View File

@ -20,6 +20,13 @@ are reviewed.
\section{Introduction}
\subsection{Product Life Cycle}
\begin{figure}[h]
\centering
\includegraphics[width=300pt,keepaspectratio=true]{./standards/prod_life.jpg}
% prod_life.jpg: 620x421 pixel, 72dpi, 21.87x14.85 cm, bb=0 0 620 421
\caption{Product Life Cycle with Competent Body Approval and Surveillance}
\label{fig:prod_life}
\end{figure}
difffernent areas
EN61508 REQ to SPEC to DESIGN

25
standards/standards_paper.tex
View File

@ -4,29 +4,44 @@
\ifthenelse {\boolean{paper}}
{
\begin{abstract}
This chapter describes the legal frameworks and standards organisations
This paper describes the legal frameworks and standards organisations
that exist in Europe and North America.
Some specific standards (that the author has experience with directly)
are reviewed.
\end{abstract}
}
{}
{
This chapter describes the legal frameworks and standards organisations
that exist in Europe and North America.
Some specific standards (that the author has experience with directly)
are reviewed.
}
\section{Introduction}
\subsection{Product Life Cycle}
i
\begin{figure}[h]
\centering
\includegraphics[width=300pt,keepaspectratio=true]{./prod_life.jpg}
% prod_life.jpg: 620x421 pixel, 72dpi, 21.87x14.85 cm, bb=0 0 620 421
\caption{Product Life Cycle with Competent Body Approval and Surveillance}
\label{fig:prod_life}
\end{figure}
difffernent areas
EN61508 REQ to SPEC to DESIGN
EN298
DESIGN TO PRODUCT
DESIGN TO
TESTING (EMC PRODUCT
FM
PRODUCT VERIFICATION MONITORING
NEW A PRODUCT LIFE CYCLE IMAGE WITH AN EULER DIAGRMA FOR THE DIFFERENT STANDARDS
Different agencies - approval is testing of new product
and verification to standard - manufacturing overwatch / supervision
word on tip of tounge -