Page History

This is the home page for the ITANA group's discussion of enterprise workflow. Please feel free to add to the wiki!

Contents

So far the group has gathered the following information:

• Workflow definitions
  What do we mean by workflow, enterprise workflow, workflow solutions, etc.?
• Workflow benefits
  Why do we want workflow? What kinds of problems are we trying to solve?
• Workflow solution components
  What does a workflow solution look like?
• Workflow progression
  How do organizations progress through different kinds of workflow solutions?
• Workflow success factors
  What kinds of things determine the success of a workflow implementation?
• Workflow resources
  Links to related web sites and documents.

Tasks

Next steps for the group could include

Sites of interest:

• https://wiki.cac.washington.edu/display/workflow/Enterprise+Workflow+Investigation^{Image Removed}
• http://www.wfmc.org^{Image Removed}

Tasks:

• Provide overviews of workflow systems included with products like the Sun access management system.
• Develop applicable definitions (what do we mean by workflow?)
• Define use cases to illustrate the range of problems that we're trying to solve.
• Develop case studies
• Compile a survey of tools
• Adapt information from well-known workflow sites to higher education the workflow management coalition site is www.wfmc.org

Workflow is based on Work Items in a Business Process that are acted on by People in Roles

Enterprise Workflow vs. Internal Workflow

• Internal Workflow is within a given application. Enterprise Workflow spans across multiple applications. Many business processes cross the boundaries of applications (e.g. Hiring may touch on Telephone, Network, HR, Parking, etc.)
• Various aspects or styles of Enterprise Workflow:
  • Document-centric workflow (routing for approval or signature) vs. messaging centric workflow (like in SOA-based workflow)
  • Automatically Trigging Events and changes in the systems vs. notifying a person to make changes in the system
  • Collector of Information that automatically gets updated in the systems vs. gathering data for a person to key into a system
  • Physical Workflows (moving things like goods and people) vs. digital workflows

Benefits:

• Gather example workflows
• Develop a single workflow (Hiring) and see how it has been implemented on various campuses
• Have a Screen2Screen session to show the tools that various groups are using, for example:
  • Discussion of the UK Local e-Gov Workflow work - Paul Hobson
  • IBM Websphere Workflow Stack - Paul Hobson
  • Oracle Workflow - Keith Hazelton
• Transparency into the state of the workflow
• Ability to gather metrics of the process
• Audit-ability and Traceability
• Workflow as a way of knowing what your capabilities are.
  • If you don't know you business processes, you don't know what you are capable of delivering as a service.
  • There is a tight coupling of Business Processes, their triggers, and the services you offer.
• Allows you to parallelize process which might be serial processes now because of the paper workflow.