1. Simple Workflow Access Protocol (SWAP) Keith Swenson July 14, 1998

2. Overview n Workflow u Requirements n Design Details n Relationship to: u WfMC standards u Event Notification

3. Workflow Management Coalition n Started in ‘93 n Organization of over 200 vendors, users, analysts n Purpose is to u Educate the market on workflow u Develop interoperability standards n Based on a workflow architecture n http://www.wfmc.org/

4. The Nature of Workflow n A model of a business process n Every organization is different n Aggregate organizational behavior is not predictable n Effect on Design: u Customized for End User u Islands of Automation

5. Workflow == Integration n Workflow is an integrating technology u different people u different tasks u different tools u different places u together in one process

6. Service: Black Box n There is a service “out there” which takes a long time to complete n We want to configure a program “here” to call the service. n How much does the program “here” have to be given about the service “there” in order to start it, monitor it, control it, and be notified when it is completed?

7. Two Other Standards n jFlow - OMG technology u requires CORBA u requires Business Objects (BOCA) u firewall problems (domains of authority) n WfMC IF4 / MIME u unreliable email overhead u unpredictable delays u error handling is complex

8. SWAP Problem Statement A standard protocol is needed to integrate work providers, asynchronous services, across the intranet/internet and provide for their interaction. The integration and interactions consist of control and monitoring of the work. Control means creating the work, setting up the work, starting the work, stopping the work, being informed of exceptions, being informed of the completion of the work and getting the results of the work Monitoring means checking on the current status of the work and getting a history of the execution of the work. The protocol should be light weight and easy to implement, so that a variety of devices and situations can be covered.

9. Basic Interaction n Start with URI of the ProcessDefinition Invoke the createProcessInstance command, get the URI of ProcessInstance Invoke the createProcessInstance command, get the URI of ProcessInstance n Give the URI of the Observer to the ProcessInstance When done, the ProcessInstance invokes the completed command on the Observer. When done, the ProcessInstance invokes the completed command on the Observer.

10. Observer / Service Model Process Definition ObserverProcess Instance Start Pause Resume Check Status Update Data Check Results Events Completed Results

11. Both Polling & Event Oriented Using the URI of the ProcessInstance, the propFind command is invoked, to retrieve current status. Using the URI of the ProcessInstance, the propFind command is invoked, to retrieve current status. u Needed when observer has no permanent web address. n When observer has an URI, then register it to receive the completion event. u Useful to avoid traffic due to polling.

12. Work Breakdown

13. Two parts to each action

14. Workflow Process

15. Hierarchical Workflow

16. Observer / Process Model Process Definition ObserverProcess Instance Process Definition Activity Observer Process Instsance

17. Organization to Organization WW HTTP Firewall

18. Is SWAP an Event Protocol? n Observer / Process is a Relationship u each object has some knowledge of and requirements on the other n Need for other events u achievement of a particular step in a process u a particular condition on the data values u SWAP does not handle these

19. SWAP != Event Notification n SWAP originally had a SUBSCRIBE / UNSUBSCRIBE methods u Because no event notification service existed n Current feeling is to pull these out and adopt whatever event standard is adopted by IETF

20. Lightweight Events n Remember the islands of automation? u existing workflow systems u in existing departments u workflow systems themselves are reliable u need to get them interoperating n The requirement of a separate event service is problematic

21. SWAP Status n http://www.ics.uci.edu/pub/ietf/swap/ n http://people.netscape.com/kswenson/SWAP/ n Not yet a working group, u charter under review u requirements, scenarios, spec in progress n Concentration on demonstration of operating code n Planning meeting at IETF Chicago

22. Summary n Workflow u Requirements n Design Details n Relationship to: u WfMC standards u Event Notification