the washington post, some weekday between october and december, 1999

20
The Washington Post, some weekday between October and December, 1999.

Upload: velika

Post on 14-Jan-2016

29 views

Category:

Documents


0 download

DESCRIPTION

The Washington Post, some weekday between October and December, 1999. Categorizing Intelligent Lessons Learned Systems. Rosina Weber, David W. Aha, Irma Becerra-Fernandez. Computer Science, U. of Wyoming, Navy Center for Applied Research in AI, Naval Research Laboratory. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: The Washington Post, some weekday between October and December, 1999

The Washington Post, some weekday between October and December, 1999.

Page 2: The Washington Post, some weekday between October and December, 1999

July 31 2000 Rosina Weber/ILLS AAAI’00

Categorizing Intelligent Lessons Learned Systems

Rosina Weber, David W. Aha,

Irma Becerra-FernandezComputer Science, U. of Wyoming, Navy Center for Applied Research in

AI, Naval Research Laboratory

Page 3: The Washington Post, some weekday between October and December, 1999

Goals & Perspectives

AI research perspectiveLLS are organizational systems

Organizational goals and restrictions

Problems in promoting knowledge sharing

How can AI help?

DOD, DOE, Space agencies

Survey, categorization

Design, develop, & deploy issues

Page 4: The Washington Post, some weekday between October and December, 1999

Defining Lessons learned

• Generate impact

• Working experiences work practice

• Applicable to a task/decision (process)

• Successes

• Failures

• Valid

•Consistency

•Redundancy

•Correctness

Work practice

Successes/Failures

Valid

Applicable

Generate an impact

Page 5: The Washington Post, some weekday between October and December, 1999

Two step categorization

1. LL process:CollectVerifyStoreDisseminateReuse

2. LL systems

Page 6: The Washington Post, some weekday between October and December, 1999

Lessons Learned Process

Page 7: The Washington Post, some weekday between October and December, 1999

Collect

reactive collect COIN,

NASDA

active (military)

collect

CALL, JCLL, NLLS

active (scan)

collect

ESA LL, Lockheed Martin LL,

Project Hanford LL,

ESH LL Program

after action collect

Alenia, Canadian Army LL

Centre, ESA, JCLL, Marine Corps, NLLS

proactive collect

CALVIN

passive collect

others

interactive collect

ongoing

Page 8: The Washington Post, some weekday between October and December, 1999

Disseminate

passive disseminate

AFCKS, CALL, ESA LL, JCLL, RECALL, AMEDD, NLLS,

NAWCAD, ALLCARS,

Alenia, Eureka,

SELLS members

broadcasting disseminate

Canadian Army LL Centre, DOE

Corporate, Federal Transit

Administration LL Program, Marine Corps LL System,

NLLS

active casting

disseminate

CALL, DOE Corporate

proactive disseminat

e

ACPA

active disseminate

ALDS

CALVIN

reactive disseminat

e

ACPA

Page 9: The Washington Post, some weekday between October and December, 1999

Reuse

browsable recommendati

on

ACPA

Standalone

. . .

executable recommendati

on

ALDS

Page 10: The Washington Post, some weekday between October and December, 1999

Two step categorization

1. LL process2. LL systems

ContentRolePurpose and scopeOrganization type, durationAttributes and formatArchitecture

Page 11: The Washington Post, some weekday between October and December, 1999

Content

Pure Eureka (XEROX), AirForceCKS, JCLL, RECALL

Microsoft PowerPoint

Presentation

Hybrid CALL, DOE corporate, NLLS, NAWCAD, ESA LL

Page 12: The Washington Post, some weekday between October and December, 1999

Role Planning

JCLL, Marine Corps, NAWCAD, AMEDD, Canadian Army

Technical Eureka, DOE Corporate, Alenia

(Italian) Both

RECALL, CNES

Microsoft PowerPoint

Presentation

Page 13: The Washington Post, some weekday between October and December, 1999

Purpose & scope

Start design with scopeOrganization subsystemPurpose of the subsystemSubsystem processesWhich lessons to include

Page 14: The Washington Post, some weekday between October and December, 1999

Organization Type rigid flexible

Duration• permanent• temporary

Page 15: The Washington Post, some weekday between October and December, 1999

Attributes & Format

Typical:Observation, discussion, lessons learned: textual

Desired:•Applicable task (process)•Conditions necessary for

reuse•The lesson (work practice)

Page 16: The Washington Post, some weekday between October and December, 1999

Architecture

Standalone: all implemented LL systems

Embedded to the process:

CALVIN, ACPA, ALDS

Page 17: The Washington Post, some weekday between October and December, 1999

Conclusions (DDD)

Identify the TYPE of your organization ;Define the DURATION for the system;Define the SCOPE & PURPOSE;Identify the CONTENT;Identify the ROLE;Define ATTRIBUTES & FORMAT;Design an embedded ARCHITECTURE;DDD methods for COLLECT;DDD methods for VERIFY & STORE;DDD methods for DISSEMINATE & REUSE.

Page 18: The Washington Post, some weekday between October and December, 1999

Research Directions

different processes and embedded architectures

elicitation tool planning audiencetechnical audience

extraction tool (from text)

Page 19: The Washington Post, some weekday between October and December, 1999

Watch out for Harry’s

lessons!!NBC’s sitcom has a lessons learned session in every episode when characters sit on the roof.

Lessons learned session

Page 20: The Washington Post, some weekday between October and December, 1999

Lessons learned and other knowledge artifacts