kflow in their packages as well. The key point to realize is that in order to configure these packages to individual requirements, it is nearly always necessary to use the embedded workflow manager. This immediately precludes the use of an external workflow manager to manage tasks within an application. To put it another way - intra-application workflow management is often mandated to be done by the embedded workflow manager. Frequently, these embedded workflow managers will be enabled with some form of interface, SO that when necessary, tasks can be sent or received from other applications, and status updates sent or received in return. A good example would be an order manager sending an LSR to an ILEC through a trading partner gateway product. The next level to consider is inter-application workflow. That is the flow of tasks and work from one application to another. The classic example here is ordering. An order might originate in an SFA application, flow-through the order manager and ultimately end up in the billing system. What is managing this process? In an OSS, integrated via point-to-point techniques, the answer is often the logic embedded in the bridging technology. This logic provides a form of implicit control. For example, the job scheduler that transfers files from one system to another is a form of workflow control. In an EAI-based OSS, the roll is typically filled by the tool-integrated workflow manager. This integrated workflow manager can in essence be the manager of managers, as illustrated in Figure 26. Chapter 6 - Integrating the OSS Platform OE/OM Activate Tasks Tasks Tasks rigure 20. WORKILOW manager or Managers Closer examination of some of these EAI workflow engines may lead to some discussion as to whether they constitute what might be called an "event- flow" manager, as opposed to a full-blown workflow capability. An event- flow manager is a term coined to describe a process controller that is focused solely on managing inter-application events. As such, these controllers are highly opt