358
direct commercial value and which can be
manufactured, maintained, deployed, operated and
retrieved at an acceptable cost. The corresponding
definitionofautonomyisanautomatedsystem that
has the capability of making independent sensor
baseddecisionsbeyondordinaryclosedloopcontrol.
This paper presents some of the results of using
thenewdesignandanalysismethodintheMUNIN
projectaswellassomeofthe experiences thathave
beengainedthroughthisprocess.
Chapter 2 gives an overview of some published
workonriskbaseddesignforautonomousvehicles.
Chapter3givesabriefoverviewofthedevelopment
method
and following chapters discuss the main
partsofthemethod:Scenariodevelopments(Ch. 4),
system modularization and operational issues (Ch.
5), hazard identification and risk control (Ch. 6),
hypothesis formulation and tests (Ch. 7) as well as
design verification (Ch. 8). A few comments on the
coming cost‐benefit analysis can
be found in
chapter9. This paper concludes with chapter 10,
summarizing the conclusions and experiencesmade
sofarintheproject.
2 AUTONOMYANDRISKBASEDDESIGN
An industrial autonomous system must be a cost
effective solution for the intended tasks. “The first
question any potential customer is going
to ask is:
Can the [vehicle] do the job, and if so, at a lower
cost?” (Stokey et al. 1999). This certainly applies to
industrial autonomous systems, but even for
scientific missions this becomes more and more an
issue.Whilesciencemaybemorelaxrelativetocost‐
effectiveness than commercial
industry, they may
stillhavetopayfore.g.insuranceorreplacementof
lostvehicles(Griffithsetal.2007).However,thisis
not often a subject of scientific dissertation and
papersonrisk‐baseddesigncriteriaforautonomous
vehiclesarestillrelativelyrare.
Somepapersarepublished,mostlyinthe
domain
ofautonomousunderwatervehicles(AUV).Onewas
referenced above (Stokey et al. 1999) and it is an
interesting account of what can go wrong with an
AUV. The details are not of general interest in the
MUNIN scope as application area and operation
paradigms are quite different. However, some
general
observationscanbemade:
1 Human error is the most common source of
problems. This also includes problems with the
softwaredesigninthecontrolstations.
2 Non‐complex hardware errors, such as
connectors,batteryandcalibrationofsensorsand
algorithms,arealsoamajorcauseofproblems.
Thereis
noreasontobelievethatthispatternwill
be much different for other types of vehicles so it
confirms the idea that a risk‐based design process
maybeagoodchoice,but also emphasizes thatthe
riskanalysishastofocusasmuchonʺtrivialʺhazards
as on the more
complex and intellectually
challenging hazards related to the autonomy of the
system.
Another paper, (Griffiths et al. 2003) focuses on
risk‐based design, but still with an AUV as case. It
presents a pragmatic approach to safety, focusing
partlyonproblemsthatareknownbyexperienceto
have a high
probability and partly on simplifying
physical designs and programs to keep complexity
under control. Some of the main risks identified
were:
1 Humanerror,directlyorindirectly,accountsfora
highpercentageofproblems.
2 Relatively trivial physical problems (electronics,
GPS receiver, mechanical, power, leaks etc.) also
causealargegroup
offailures.
3 Other significant problems are environmental
disturbances (for acoustic transmissions) and
softwareerrors.
Thepaperclassifiesfaultsintoimpactclassesand
performs a more complete risk assessment, taking
consequencesofthe faults intoconsideration.While
this is of limited use to MUNIN, as the technical
domainisvery
different,itshouldbequitevaluable
to other AUV designers. One should also note that
statisticalmodelsareproposedforsomeofthefault
classes which could be used for more quantitative
assessments of expected reliability. Finally, part of
the conclusion is that “This paper has shown that by
good
design and thorough testing of the ‘significant few’
systemsthatcouldposehighrisktothevehicle,theoverall
reliability of the autonomous vehicle is not dominated by
thecomplexassembliesneededtoprovidethatautonomy”.
Thisisalsoencouragingtootherautonomoussystem
designs as this has applications not
only to AUVs,
but can be viewed as a general statement about
industrialautonomoussystems.
Another fault analysis is done by Podder et al.
(2004). This focuses on technical failures and
determination of statistical data for quantitative
assessmentofrisk.Theobservationfromthispaperis
also that most faults are
“trivial” in the sense that
they do not occur in the more complex sensing,
controlanddecisionmakingsoftwaremodulesofthe
vehicle.
In (Brito et al. 2010), an operational risk
management process model is described. This is
partly a quantitative approach where expert
judgementsarepartofthedecision
makingdataset.
It defines an acceptable risk level and tries to
determineifthe risks derived from a givenmission
exceed this level. Itis alsotargeted atoperations in
high risk environments,i.e. an AUV operating near
and under ice, and is not so relevant to MUNIN’s
operational planning.
However, the principles and
methods discussed are more quantitative in nature
thanintheMUNINprojectanditwillbeinvestigated
ifvariantsofthemethodologycanbeusedalsointhe
designphaseforindustrialautonomoussystems.
3 THEMUNINAPPROACH
The high‐level objectives of the MUNIN design
processare:
1 Ensureanacceptablesafetyandsecuritylevelfor
own and other ships and the international
shippingcommunityingeneral.
2 Minimize uncertainty in the missions’ intended
outcomeaswellasinunintendedsideeffects.