ISSUE 70 : May/Jun - 1988 - Australian Defence Force Journal
ISSUE 70 : May/Jun - 1988 - Australian Defence Force Journal
ISSUE 70 : May/Jun - 1988 - Australian Defence Force Journal
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Harnessing Military Expertise in <strong>Defence</strong> Decision<br />
Analyses — A Realisable Goal<br />
By Dr Malcolm S. Bilton and Mr Keith Lawson<br />
TO those involved in the analysis of <strong>Defence</strong><br />
problems it comes as no surprise to find<br />
that often management decisions require comparison<br />
of 'apples and oranges'. What often<br />
does cause surprise is the way in which the<br />
comparison is made. We become used to commonplace<br />
justifications which make appeals to<br />
the 'average outcome' or which are founded on<br />
the shaky ground of expedience. It is easy to<br />
gain the impression that some of the public<br />
justifications for decisions tend to gloss over<br />
the degree of vagueness incorporated in the<br />
arguments.<br />
<strong>Defence</strong> Management decisions usually involve<br />
many different factors and criteria, some<br />
of which might actually be in conflict. For<br />
example, what is the effect of overall force<br />
readiness when Air <strong>Force</strong> flying hours are traded<br />
off for Navy Steaming time? These situations<br />
are not solvable using classical concepts of optimisation.<br />
Rather, the decision maker must<br />
choose from a set of feasible alternative decisions<br />
which, in the light of the information<br />
available, are not readily distinguishable. The<br />
decision maker is in the position of choosing<br />
from two or more 'good' decisions rather than<br />
having a single 'correct" alternative.<br />
And now, with Freedom of Information legislation,<br />
and a general drive within the community<br />
for everyone to lift their game, the<br />
decision makers are expected to make ever more<br />
complex decisions under conditions of increasing<br />
uncertainty. There is ever-increasing scope<br />
to provide techniques which the decision maker<br />
can use to structure problems in a flexible manner,<br />
and provide a repeatable and explainable<br />
decision synthesis. Such techniques have appeared<br />
in the private sector, some built into<br />
integrated hardware/software machines (these<br />
are usually called 'analysis workstations' because<br />
they were originally designed for stockmarket<br />
portfolio analysts' needs).<br />
We take the view that it is possible to build<br />
a 'generalised decision model' which the decision<br />
makers can use to map out their (often<br />
intuitive) ideas about a problem, often in the<br />
quiet of their own office, so the techniques need<br />
to be implemented on a small computer. Our<br />
most important premise is that the decision<br />
makers' intuitions about a problem (in our business<br />
these are often renamed 'military judgements')<br />
can be harnessed and refined.<br />
In this article we discuss a set of techniques<br />
which are being developed as part of ongoing<br />
investigations into the construction of a generalised<br />
decision model. The work is in its Phase<br />
II development under the project name Management<br />
Decision Support System (MDSS). Unlike<br />
more traditional methods of operational<br />
research, the MDSS does not try to find 'correct'<br />
or 'optimum' solutions to problems. What<br />
it does attempt to do is:<br />
a. provide a reasonable method of assessment<br />
and synthesis of information, and<br />
then<br />
b. provide an explicit statement of the degree<br />
to which decision alternatives are of equal<br />
worth.<br />
The overall aim of our article is to introduce<br />
the ideas behind the MDSS approach to decision<br />
making.<br />
Extensive research of the decision analysis<br />
literature leads us to the conclusion that there<br />
are several processes that go on when making<br />
a decision to do something and which are independent<br />
of the decision type.<br />
Using fairly common terms, the processes<br />
are:<br />
a. identify the problem as a problem for the<br />
decision maker to deal with. What is the<br />
probem and does it belong to me?<br />
b. analyse the problem, determine what the<br />
basic questions are — what do I want to<br />
do?<br />
c. define (implicitly or explicitly) what your<br />
objectives are, the major goals that should<br />
be met when the decision is implemented<br />
— what do I really want to change and<br />
achieve?<br />
d. generate alternative ways of achieving the<br />
major goals — how can I do these things<br />
and are they really possible?