Workflow: Update and program proposal The Workflow Steering Committee November 1 st, 2006 Steve Lutter, Assistant Director CIT/IS

November 1, 2006Cornell's Workflow Program2 Agenda What we heard from you last time Recap of progress to date The big picture: a proposal for the Workflow Program

November 1, 2006Cornell's Workflow Program3 What we heard last time ‘Workflow’ is something that is fully integrated with cross functional business processes or it isn’t worth much. For example: Show departments from the data of record Route documents/ transactions automatically Update a financial record in the financial system In other words… Show us something that integrates with the finance system or integrates with PeopleSoft HR, or Research Administration / EZRA, etc.

November 1, 2006Cornell's Workflow Program4 KEW Product KEW CU Investment KEW environments KEW prototypes The Program is about filling the Gap Design, Implement WEICFA* * WEICFA = Workflow Enabled, Integrated Cross Functional Apps What you want. What you heard about last time.

November 1, 2006Cornell's Workflow Program5 Since June 2006… Discovery project: completed KEW, the product, will work with a supportive program Infrastructure proposal Infrastructure project: started and just about completed – the required technical environments are setup! Program design: Built up a program roadmap

November 1, 2006Cornell's Workflow Program6 …since June... KEW-CORE-L: Built up a core technical knowledgebase Source Forge: Created process to track and assign issues and share documentation Partnership: Identified issues and worked with IU on additional features & bugs. CASS: Gauged interest in distributed development using KEW with CASS – it’s very strong

November 1, 2006Cornell's Workflow Program7 …since June. Core team: Started expanding core team to IWS and ATSUS for their specialties Candidate apps: Researched candidates for 1 st and 2 nd generation apps, the ‘stray frays’, from the Policy web site and other places. Prototypes: Bursar student refund, un-integrated form 10 Pilot #1: HR System Authorization form

November 1, 2006Cornell's Workflow Program8 Pilot #1 for 1st generation Workflow – in progress.

November 1, 2006Cornell's Workflow Program9 Pilot #1 for 1st generation workflow in its current form.

November 1, 2006Cornell's Workflow Program10 Many small steps Authen.DirectoryHRDocMgmtWorkflowAuthor.Notif. workflow solutions of increasing complexity using central services Some CU DB

November 1, 2006Cornell's Workflow Program11 Next… Filling the gap Making a mission and a program to meet it Differentiating the product, the program and workflow enabled applications The biggest issues Targeted milestones, including the Era of KEW The team

November 1, 2006Cornell's Workflow Program12 Proposed Program Outline A strategic mission and goals The process: Add, deliver, repeat –Reduce risk –Learn how to manage 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 –Working software that achieves functional results –Use by developers on campus – not only CIT/IS –Support for projects that will deliver web enabled integrated cross functional apps

November 1, 2006Cornell's Workflow Program13 Proposed Mission Statement Enable the entire Cornell Community to go to one place to complete their business oriented tasks.

November 1, 2006Cornell's Workflow Program14 Proposed Goals in 8 months 1.Continue the KEW partnership investment 2.Set the Foundation 3.Quickly deliver solutions to problems of increasing complexity 4.Lead and Collaborate 5.Resolve the big issue around routing data 6.Plan to meet the large cross unit process needs

November 1, 2006Cornell's Workflow Program15 Support, partner w/units Unit tech solutions KEW Product KEW CU Investment KEW environments KEW prototypes Workflow CU Program The building blocks KEW Pilots; nonintegrated at first Experienced core dev and support team Central, reusable routing patterns and data KEW pilots; more integrated Planning & analysis for WEICFA Design, Implement WEICFA WEICFA = Workflow Enabled, Integrated Cross Functional Apps

November 1, 2006Cornell's Workflow Program16 Single Biggest Issue No central repositories to repeatedly draw on for routing data Without which we have two options: –Add hoc routing, and / or –Routing defined for point solutions with rules that are more expensive to set up, more difficult to maintain and impractical to share

November 1, 2006Cornell's Workflow Program17 Supervisor Data; scenario for enabling org hierarchy routing universally

November 1, 2006Cornell's Workflow Program18 Service Center Data; scenario for enabling routing to service centers 1 2

November 1, 2006Cornell's Workflow Program19 Service Center Data; scenario for enabling routing to service centers

November 1, 2006Cornell's Workflow Program20 Era of KEW at CU Time Milestones illustrate the KEW related sequence of events. Relative timing is not to scale.

November 1, 2006Cornell's Workflow Program21 Target milestones

November 1, 2006Cornell's Workflow Program22 Teamwork Unit Techs; local development Unit Business Experts; requirements, rules, policies, testing ATA; KEW core investments IS; Leadership, Collaboration Infrastructure, Analysis, Development and Support, Project Management IWS; QAATSUS; tutorials, tech docs

November 1, 2006Cornell's Workflow Program23 Covered so far… The gap and how to fill it How KEW is an enabling Product that needs a Program to support workflow enabled applications The biggest issue The timeline The team

November 1, 2006Cornell's Workflow Program24 Resources Technical: 2.5 FTE –not including complementary KEW partnership investment from ATA Awaiting ACAC deliberations Minor available staff

November 1, 2006Cornell's Workflow Program25 Role of WFSC Monitor status Work on routing data