‹header›

‹date/time›

Click to edit Master text styles

Second level

Third level

Fourth level

Fifth level

‹footer›

‹#›

Good morning,

I’m Mark Werner the acting director of doctrine at Navy Warfare Development Command. Today I’d like to talk about Navy Doctrine today and a vision of where we’d like to take doctrine in the future. Doctrine today is thought of as a series of books or CDs that you consult when get stuck on some of the finer points of fleet operations or training. I’d like to see doctrine evolve into a knowledge base that you consult daily as part of the normal course of your day during fleet operations. To do that, we have to make it more assessable, searchable, and dynamic. From what we’ve seen of the DARPA mark up language and the semantic web, I think you can help us overcome many of the problems we have had in Navy doctrine.

LCDR Knox, Article Naval Institute Proceedings, 1915

Doctrine. The object of military doctrine is to furnish a basis for prompt and harmonious conduct by the subordinate commanders of a large military force, in accordance with the intentions of the commander-in-chief, but without the necessity for referring each decision to superior authority before action is taken.

I’m told a good vision should take no more than 5 minutes to explain. If that is the case; I’m extrapolating that a one minute vision is better. This is doctrine department ultimate vision: A sailor with the proper access should be three clicks from:

This diagram represents the life cycle the Navy Doctrine knowledge base.

A Fleet Sailor with an idea, submits it to NWDC, NWDC evaluates it, gives it the tumbs up or down, NWDC promulgates new doctrine, the training community updates their products and teaches a new crop of operators. Then the cycle repeats at every level of experience and operations.

There is no one command or person responsible for Navy Education and training.

NWDC’s role in training is two fold:

We produce the Doctrine and TTP that training is based on

And we are the model manager for the Universal Navy Task List (UNTL)

I am by no means an expert in anything related to programming; but I’m told that the key to XML and DMAL is establishing a Taxonomy (I won’t say Ontology because it normally comes out oncology and we are not here to talk about cancer). UNTL in conjunction with the Universal Joint Task List breaks down Naval Operations down into a series of tasks that run the gamut of operations from national strategic to putting out a trash can fire. These tasks are hierarchical, mission centric, and represent an infinite number of combinations.

Navy is making the UNTL the basis for fleet training.

This and the chart in the back show the connection between the Joint National Tasks and UNTL.

I have electronic copies of both the UNTL and the UJTL.

• This slide represents the initial approach followed to develop NMETLs. The general plan is to use an operational command to develop a first draft NMETL, which will be posted on a web site for Navy-wide review and comment. • Our vision is for these NMETLs to become the notional requirement for training of deploying forces during the inter-deployment training cycle. The plan calls for NMETL module managers to be established to ensure tasks and objectives remain current.

What I’ve tried to show you is a little bit about how our current doctrinal system works and a vision of how it may function in the future. Hopefully, at the conclusion of this conference you will be able to tell me if the DARPA mark up language and the semantic web can play an important role in bringing about this vision.

Sir, I’ve given you a broad brush of what we do in the doctrine department. By necessity it was only a cursory examination of critical issues. We are fully integrated into the NWDC innovation team, and bring the word dynamic to doctrine development.