TC3 Technology Integration

1
TC3 Technology Integration

• Mark St. John Harvey Smallman
• Pacific Science Engineering Group
• Robert Fleming
• SPAWAR-San Diego

2
Collaboration content of exchange

• Shared meaning can be broken down into
• Shared perceptions (SA)
• Shared tasks (team action)
• Shared goals (empathy)
• Are all of these desirable to exchange, or only a
  subset?
• e.g. sharing all of the above could be
  detrimental - groupthink (Janis, 1972)
• Shared does not imply same
• Collaboration vs. coordination

3
Reasons for Collaboration

• Effective command
• Consequence management, Outcome-based tasking
• Effective intelligence
• Information requests (RFIs, CCIRs), COA analyses,
  answers, notifications, briefings
• Effective planning
• Resources, needs, goals, timetables, and
  priorities of multiple parties

4
Collaboration in the Military

• Military-specific issues
• Hierarchical organization
• One decision-maker at each level
• Encapsulated
• Little interaction between commands
• Need to know information protocol
• Danger of micromanagement
• Example domains
• Mission planning
• Resource allocation
• Intelligence analysis

5
Idealized Interaction Structures

• Peer interaction
• Side-to-side (always)
• Command interaction
• Top-down (always)
• Bottom-up (often)
• Side-to-side (rarely)

A
B
B
6
Planning Cycle A

• Learn goals
• Pull similar plan off shelf
• Gather SA
• Recognize and plan
• Tweek plan
• Check constraints
• Tweek plan

A
B
B
7
Planning Cycle B

• Read plan
• Find holes
• RPD, bring experience to bear
• Send feedback
• Complain
• Resolve
• Monitor plan execution
• Re-plan

A
B
B
8
Problems Collaboration Can Fix

• B misses holes in plan
• Solved by context and intent
• B finds holes but they are difficult to fix
• Solved by improved feedback to A
• Solved by negotiation with A and other Bs

9
TC3 Integration SSCs Role

• Alterman
• Fischer
• Hayne
• Keel
• Kirsch
• Nosek

Navy prototype
CLEAR R D
10
Example Truck Scheduling

• Schedule conflict
• Existing schedule does not meet needs
• Resolution
• Knowledge of resource schedule
• Knowledge of mission intent / context
• fractal order concept
• Facilitation of re-scheduling

11
Displays for Planning Collaboration

• 6 general dimensions of plans
• Goals, needs, resources, tasks, priorities, and
  schedules
• Displays
• Task Manager
• Tasks by schedule
• Resource Grid
• Attributes by resources
• CLEAR
• Resources by schedule
• Others?

12
Task Manager

• Task by time representation

13
Resource Grid

• Attributes by resource representation
• Shows current and scheduled conditions of assets

14
(No Transcript)
15
CLEAR

• Common Likeness for Earmarking of Area Resources
• Features
• Resources by time
• Plan needs represented in common format
• Computer-mediated joint activity (Alterman)
• Information participation (Fischer et al.)
• Shared information and virtual surfaces (Hayne)
• Shared Web visualization (cardwall Keel)
• Promotes conflict-catching
• Annotation (Kirsch)
• Augmenting the construction, use, and
  maintainance of shared meaning (Nosek)

16
Conclusions

• Collaboration holds great promise
• Must fit military con-ops
• Hierachical organizations, etc
• Solution Integration of basic research concepts
  into a Navy prototype to promote outcome-based
  tasking

17
Extras