| | This is the home page for the Enterprise Workflow Investigation project. |
| | |
| | | So far people participating in this project include: |
| | - Darcy Van Patten |
| | - Lisa Yeager |
| | - Gary Prohaska |
| | - Oren Sreebny |
| | - Scott Stephenson |
| | | h3. General notes on approach |
| | |
| | * Evaluation effort should balance short-term immediate needs with long-term enterprise needs |
| | * Evaluation effort should take into account central and distributed needs |
| | * Solutions will be evaluated based on ability to meet representative business and technical use cases and requirements |
| | * Business use cases should span the range of needs, and be aligned with the vision of the UW Roadmap for administrative systems and information management |
| | * A broad range of potential solutions should be evaluated based ability to meet use cases |
| | |
| | h3. Key Deliverables (DRAFT) |
| | |
| | * Documented goals, approach & timeline for evaluation |
| | * Project Structure (advisory teams, analysis team, core project team) |
| | * Trends & Best Practices in workflow (including peers and vendor market place) |
| | * Business Use Cases & Requirements |
| | * Technical Requirements |
| | * Gap Analysis for current UW technologies |
| | * Gap Analysis and technical evaluation of Kuali Rice (proof of concept w/ representative workflow) |
| | * Request for Information (dependent on previous go/no go decisions) |
| | * RFI Proposal analysis |