BML Requirements

1
BML Requirements
2
Characteristics of a good BML (1)

• Cost/Benefit
• The reduction or elimination of manpower needed
  to support training of commanders and their staff
  by reducing the swivel-chair interface.
• A reduction in time needed to train controllers
  in the use of a simulation.
• The expression of orders, requests and reports in
  a universal BML could potentially allow the
  development of some powerful reasoning
  applications that could then facilitate and speed
  a whole range of currently manual procedures.

From Major Kevin Galvins Master Thesis,
Cranfield University, 2004
3
Characteristics of a good BML (2)

• Usability/Acceptability
• It should not hinder a commander and his staff
  and must therefore be acceptable to the
  professional military user.
• Maintain the ability of a commander to express
  their intent that was acceptable to commanders.
• Should be able to express a wide range of mission
  types across the full spectrum of military
  conflict.
• Should not prevent the fog of war in a training
  environment being applied as a control measure.

From Major Kevin Galvins Master Thesis,
Cranfield University, 2004
4
Characteristics of a good BML (3)

• Interoperability
• Provide support for allied and coalition
  interoperability by using existing C4I data
  representation whenever possible.
• Provide the ability to facilitate battlefield
  situational awareness during training.
• Compatible dynamic updating of weapon systems,
  C4I and logistic systems.
• Be capable of being used in a distributed Live,
  Virtual and Constructive (LVC) environment to
  facilitate training with joint and multinational
  forces.

From Major Kevin Galvins Master Thesis,
Cranfield University, 2004
5
Characteristics of a good BML (4)

• Implementation
• Be comprehensible to humans so it can be used to
  express real orders and Courses of Action (CoA).
• Be capable of being interpreted by computerised
  simulations and also exported into Commercial
  off the Shelf (COTS) product e.g. Microsoft
  Word.
• Be unambiguous to both users and developers in
  what it is defining in terms of description and
  context.

From Major Kevin Galvins Master Thesis,
Cranfield University, 2004
6
Characteristics of a good BML (5)

• Fidelity
• Should reduce or eliminate input errors by
  controllers.
• Accurately represent doctrine.

From Major Kevin Galvins Master Thesis,
Cranfield University, 2004