Doctrine Applications/ Lessons Learned Breakout Session Report for DAML PI Meeting 18 July 2001

1. Semantic Web for Military Users Doctrine Applications/ Lessons Learned Breakout Session Report for DAML PI Meeting 18 July 2001 John Flynn

2. Participants Fran Dougherty - DMSO John Flynn - BBN Joel Gladding - Logicon Mark Gorniak - AFRL/IFTB Pete Haglich - ISX Marti Hall - DRC Hal Hultgren - NWDC Chuck Menges - USMC Doctrine Division Rick Morris - Center for Army Lessons Learned Bruce Peoples - Raytheon Mark Werner - NWDC Bob Wilhelm - NWDC

3. Issues • Community of practice made up of all services • More than one community: (Learning) • Lessons learned • Doctrine • Training • Leader training • Knowledge management

4. Issues • Embedded, networked training may be opportunity • Higher level training and embedded training should probably be linked to some extent • Potential for linkage between field systems and schoolhouse training • Need to coordinate DAML and Advanced Distributed Learning initiative • DAML might support the concept of doctrine without borders (dynamic doctrine with auto ripple effects)

5. Issues • Linkages to experts or mentors may be a key resource • DAML may provide opportunity to link distributed lower-level expertise without the info having to go to the top and filter back down (peer-to-peer) • There is a large body of non-DAMLised information (explicit and non-explicit) that needs to be exploited

6. Way Ahead • To get started choose a mission area with common service interest and strong joint flavor – challenge problem for DAML • Close air support • Land Mine Countermeasures * • Project chosen must be unclassified

7. Way Ahead (more) • Construct ontologies for above starting with Joint Task List and Service Task Lists • Convert existing doctrine to XML/DAML • Add experimental, theater specific, tactics/procedures, obsolete doctrine • Add lessons learned information • Demonstrate capability to dynamically add new lessons learned • Be able to combine into an op plan, battle book • Experiment with usefulness for training/operations • What constitutes usefulness – for user/producer? • What are the applicable questions & metrics?

8. Way Ahead (more) • Identify some specific agents that would act as multipliers in this domain • Need capability for users to access the appropriate view based on the user’s history of use • How to take advantage of other user’s search experience (Amazon.com – when you order book – other people who ordered that book also ordered these books) • Need to couple learning/doctrine community closely with operational close air support community *

9. Follow Up Activities • Mail lists set up • daml-milusers@daml.org • daml-doc-ll@daml.org • Navy Lessons Learned Executive Steering Committee briefed • Additional organizations asked to be involved • NRL AI Lab • DoD Office of Gulf War Illnesses • Joint Center for Lessons Learned (JWFC) • Air Force Doctrine Command • DAML linked to Army Warrior Knowledge Network concept • Groove collaboration session • DAML Military Users • Decision to focus on Land Mine Countermeasures • DRC developing Universal Joint Task List (UJTL) ontology • Master Chief Mark Nelson (COMEODGRU TWO) working with DRC • Develop Land Mine Countermeasures scenario (Flynn) • Planning next meeting at NRL AI Lab