1. Workflow: News, a program proposal, and a demonstration The Workflow Steering Committee November 1 st, 2006 Steve Lutter, Assistant Director IS

2. November 1, 2006Cornell's Workflow Program2 Agenda Recap of progress to date (5 minutes) The big picture: a proposal for the Workflow Program (30-40 minutes) Demonstration of an emerging workflow pilot application or two (10 minutes)

3. November 1, 2006Cornell's Workflow Program3 Activities since June 2006 Discovery project completed with an Infrastructure proposal Infrastructure project started and completed – development, test and production environments are setup! Proposed Program and Roadmap defined 3 sample EDocLite pilots pursued Conversations with CASS

4. November 1, 2006Cornell's Workflow Program4 Proposed Program Outline Set a clear strategic mission Set goals to meet the mission Add, deliver, repeat –Reduce risk –Learn by delivering small pilots of increasing complexity –Pick small, doable projects and partners to learn from –Nurture a knowledge base prior to larger, broader efforts Measure results by… –Working software –Use by developers on campus – not only CIT/IS

5. November 1, 2006Cornell's Workflow Program5 Proposed Mission Statement Enable the Cornell Community to go to one place to respond to requests and enable the delivery of such solutions throughout the Cornell technical community.

6. November 1, 2006Cornell's Workflow Program6 Proposed Goals in 8 months 1.Set the Foundation 2.Learn while quickly delivering solutions to problems of increasing complexity 3.Lead and Collaborate 4.Plan to meet the large cross unit process needs

7. November 1, 2006Cornell's Workflow Program7 Approach: Add, deliver, repeat 1.Non integrated workflow form (paper / pdf / fax forms as EDocLites) 2.Automatic lookups for common fields such as name, phone 3.Routing that uses institutional data such as employee supervisor data 4.Workflow apps that use database lookups for some fields (such as departments) 5.An application that uses workflow and updates a transaction system upon approvals and uses other services

8. November 1, 2006Cornell's Workflow Program8 The frayed rope

9. November 1, 2006Cornell's Workflow Program9 EDocLite & KEW app candidates 1.Account Distribution and Adjustment 2.Agency account request / approval forms 3.Approval for temporary employment 4.APPS authorization 5.Capital asset new, transfer, and scrap forms 6.Certificate of Insurance 7.CIT HR Action forms 8.Collections placement 9.Confidentiality agreement forms 10.Conflict of Interest form 11.Consolidated bursar billing 12.Direct deposit non payroll 13.Employer provided vehicle certification 14.Establish & charge a petty cash fund forms 15.Facilities Inventory coding form 16.Facilities Inventory research space form 17.Facilities Inventory room transfer 18.Finance charge waiver 19.Foreign visitors honoraria attestation 20.Grad School thesis submitter 21.HR Online forms 22.HR Performance Dialogue forms 23.Independent contractor agreement and questionnaire 24.Independent service provider agreement 25.Meal for business purposes 26.New Account request 27.OSP request to engage a consultant 28.Payroll and time collection authorization 29.Payroll deduction 30.Pre travel approval forms 31.PS Authorization 32.Purchasing auth request 33.Refund SS Taxes directly 34.Request for solicitation form 35.Research Admin Form 10 36.Stop / delete account request 37.Student refund deposit form 38.Subcode request form 39.Time away request forms 40.Transfer petty cash fund accountability 41.Vendor information request 42.W-9 substitute / Vendor request Intent: To give ideas. Some of those listed may not be worthy. Source: Policy site, DFA forms, identified projects, common existing forms. Not included: all college and unit ideas for forms, KFS documents…

10. November 1, 2006Cornell's Workflow Program10

11. November 1, 2006Cornell's Workflow Program11 Targeted milestones

12. November 1, 2006Cornell's Workflow Program12 Single Biggest Issue No central repositories to repeatedly draw on for routing data Users in each service center? Nope Employee supervisor data? Not yet PIs to department chairs? Nyet Users as members of a workgroup? Possibly, but it’s in various forms in various places.

13. November 1, 2006Cornell's Workflow Program13 One of several new services Concept: composite apps built using central services –Workflow services –Document management services –Identify management services –Vertical services for institutional data (such as HR position lookup) –Complementing local, unit databases (by unit techs) at times –Launched from Portal’s administrative tab in many cases

14. November 1, 2006Cornell's Workflow Program14 CU Data Local Data Add, deliver, repeat Utility services Business services KEW App 5 App 3 and 4 Apps 1 and 2: EDLs as routable forms

15. November 1, 2006Cornell's Workflow Program15 Teamwork OIT/IWS CIT/ATSUS CIT/IS CIT/ ATA Unit technical colleagues Unit leaders and users

16. November 1, 2006Cornell's Workflow Program16 Pilot #1 Demo intent Why these? – Pilots selected because they were doable, can add value, and are easy to understand. In sum, they are good stepping stones. Goals: –Reduce risk for later efforts –Learn by doing –Get something in production and observe use

17. November 1, 2006Cornell's Workflow Program17 Pilot #1 Demo expectations Will show: –User 1: Fill in and route a System Authorization request document –User 2: Find, view and approve the document –User 1: Search on and find the status of the document Not shown at this time: –Email notification with a link –Delegation to another user –Searching and retrieval restrictions based on who you are –Portal action list channel showing how many pending items are waiting

18. November 1, 2006Cornell's Workflow Program18 Pilot #1 credits Users: Sarah Christen, Mel Radcliff Project Manager & Analyst: Butch Labrecque Developers : Bryan Hutchinson, Chad Dumont, Aaron Hamid (ATA) Infrastructure support: Jeff Hanavan Service Manager: Jon Atherton

19. November 1, 2006Cornell's Workflow Program19 Demo: previously recorded