To access your work with one system You will need to log directly into PRPC. View your work list, Find out if you have work

Transcription

1 Integrated Work Manager (IWM) Presented by: David Vidoni, Senior Product Manager Pegasystems

2 Challenges As enterprises deploy multiple BPM applications into different parts of the organization, business users need to see, manage, and perform work across different systems and applications. For multiple applications on a single system, SmartBPM provides excellent visibility and control. However, in larger enterprises, it is critical to consolidate BPM work across multiple systems to avoid BPM silos which force users to log in and work in each application individually. 2 Pegasystems 2008

3 Challenges To access your work with one system You will need to log directly into PRPC View your work list, Find out if you have work Click on a task to open and perform work. 3 Pegasystems 2008

4 Challenges To access your work with two systems You will need to log directly into each PRPC View your work lists, Find out if you have work, and which have higher priorities Click on a task to open and perform work. 2x the work 4 Pegasystems 2008

5 Challenges BPM Workload Challenges How can process participants and managers simplify their workday and consolidate multiple worklists with differing priorities? How can the organization set and enforce policies for work priority, aging and reporting consistently for disparate applications? How can IT incorporate all the process-based apps into a corporate portal and still provide performance and flexibility for users? How can an organization make sure BPM projects don t turn into BPM silos? 5 Pegasystems 2008

6 One List APPLICATION A Work kit Item APPLICATION B Open Open Open APPLICATION C Open APPLICATION D 6 Pegasystems 2008

7 IWM Architecture Work List Integration IWM allows users to manage consolidated lists of work objects distributed across several PRPC source systems. IWM users can select multiple objects simultaneously from the list to process them, interacting directly with the PRPC source system in which they reside. Integrated List from sources A, B, and C IWM Server High Scalability IWM s source-based push mechanism makes the architecture highly scalable. Most of the thin processing takes place in the source systems via light-weight ti triggers. 7 Pegasystems 2008

8 IWM Portal Accessible link to multiple systems Easily create new work for any available application Sort priorities for all work items across available applications Integrated work list Search work item across multiple applications 8 Pegasystems 2008

9 IWM Demo 9 Pegasystems 2008

10 IWM Benefits Business - End Users and Managers Gives consolidated view of work across multiple applications and systems. Easier training i and less confusion; no missed hand-offs or cherry-picking. iki Consolidated view of available starting processes, search, and get next work. Manage all staff and work consistently; handle reporting and re-assignment easily Participants and managers can simultaneously see and work on multiple ongoing tasks. Technical - System Administrators IWM allows administrators to manage a distributed PRPC environment. Select application servers can be upgraded or brought down without impacting other applications. Low-impact, up-to-date environment; no programming to add and change apps. Easily integrate in corporate portals; faster and easier to deploy than alternatives. 10 Pegasystems 2008

11 Frequently Asked Questions How does this differ from having my single worklist on a PRPC Instance? This allows applications to upgrade to a newer version of PRPC on their own schedule w/o dependencies on other applications being ready. What versions of PRPC will this support? Source systems can be on PRPC 5.4SP3 and above. The IWM Server must be PRPC 5.5 and above. What benefits does IWM give me that I wouldn t otherwise have? Unified Work list view, unified search and work prioritization across the enterprise What is sent to the IWM? A minimum amount of information necessary to access the work objects on the source system. This includes Assignments, Operator Info, Access Groups, Application i Info, Starting Flows. All Rules and s stay on the source system and run on the source system. Can I use this feature on existing applications? Yes, as long as they re running on PRPC 5.4 SP3 or above What performance impact does this have my systems? IWM does not adversely impact performance because the work is still being done on the same system. IWM is simply redirecting web traffic to the source system. 11 Pegasystems 2008