Why are AIM's views on Workflow Different?
Many programs in the DARPA ISO office refer to the need for workflow
without understanding what the term actually means. When programs such
as ARPI refer to workfow they mean a simple finite state machine which
passively monitors the situation and provides the information visually
to the user. In addition programs such as ARPI view their role as
defining the modules and interfaces necessary to support
workflow. This is fine, but without knowing the functionality and
computation necessary to support workflow this will at best produce
and idealised architecture suited to no particular real world need.
The workflow research in AIM will go well beyond this and provide
truely responsive and proactive workflow.
Our research objectives:
- Revolutionary approach to Workflow Management
- Dynamic tasking of AIM agents
- Reactive and flexible control of the complete AIM Process
- Shorter AIM response cycles
- Better understanding of interactions within AIM Process
Other programs such as ACOA, ALP and JFACC refer to a need for
workflow and state that they will take idea and technologies from each
other. With this mutual reliance on each other there arises the very
great risk that nothing will be produced or at best adhoc solutions
will be provided. By undertaking the research program we have defined
other programs will be able to benefit from AIM's ideas and
technologies.
SWIM Project Page
AI Center Home Page
SRI International Home Page
Pauline M. Berry berry@ai.sri.com
Last modified: $Date: 1998/05/15 22:40:38 $