realizes concretizes process plan specification planned process 'Plan' includes a future direction sense. That can be problematic if plans are changed during their execution. There are however implicit contingencies for protocols that an agent has in his mind that can be considered part of the plan, even if the agent didn't have them in mind before. Therefore, a planned process can diverge from what the agent would have said the plan was before executing it, by adjusting to problems encountered during execution (e.g. choosing another reagent with equivalent properties, if the originally planned one has run out.) 6/11/9: Edited at workshop. Used to include: is initiated by an agent Bjoern Peters Injecting mice with a vaccine in order to test its efficacy We are only considering successfully completed planned processes. A plan may be modified, and details added during execution. For a given planned process, the associated realized plan specification is the one encompassing all changes made during execution. This means that all processes in which an agent acts towards achieving some objectives is a planned process. branch derived planned process A processual entity that realizes a plan which is the concretization of a plan specification. This class merges the previously separated objective driven process and planned process, as they the separation proved hard to maintain. (1/22/09, branch call) planned process