The User-Trained Agent has an EYE on Goals

This is Papyrus Platform specific information related to ‘Adaptive Process and Goal Orientation‘.

Rather than the approach chosen by Social-BPM or other collaborative process design tools, Papyrus pushes for ‘Design by Doing’ where the users are empowered to create processes interactively without analysis and then can execute or change as required. Therefore the Papyrus ACM (Adaptive Case Management) implementation is especially suited for the knowledge workers who produce the high-value, innovation workload of a business – without which it will not survive or at least fall behind against the competition.

ISIS Papyrus Platform and Adaptive Case Management utilizes adaptive technology to provide business user access to data and content in structured and unstructured processes. Authorizes user can at any point in time add data entities, content, rules, or participants and assign work tasks to them. The tasks can be standalone or linked by dependencies or rules to other tasks. Because of the object-oriented models stored in the object-relational database, all elements of an executed process are available and can be archived. The process can even be ‘restarted’ and resimulated while watching it play out as it was executed along a timeline scale. A Gantt chart is used to display the process as a PLAN with activities and GOALS. But at any point in time it is possible to turn to the BPMN chart display, that will show all tasks, even the ones that were added by the UTA on the fly. This is how flexible the direct model execution is to man and machine.

Papyrus ACM – BPMN View in user Inbox

Papyrus uses the patented User-Trained Agent that will recommend next steps to the business users based on choices made by previous user roles. These choices are however not made in terms of which steps were followed in which sequence, but which data patterns were the repeated pattern for a follow-on action. The process is termed Transductive Training. Even without the User-Trained Agent, the process engine will expose to the user all the possible next steps in terms of fulfilled prerequisites and — if so defined — will select the fastest or lowest-cost step leading to the same goal outcome. Actor roles can be assigned to act based on shortest work queue or round-robin.

All aspects and information of the execution runtime is exposed within the system and therefore it is very easy to define charts displays to show process execution monitoring, activity monitoring or performance indicators from the real business data in real-time. Users can enter business rules at runtime to create additional goals and monitor their effectiveness immediately. Using sample data, processes can be simulated in a safe TEST sandbox environment.

User presentation of the processes, goals and outcomes is through the Papyrus EYE Widgets user interface that presents all data entities in a user-definable manner. The presentation is either through the Papyrus EYE Desktop or the Payprus EYE GUI in Flash. Other graphics engines are also being developed as is presentation to Mobile platforms such as the WebArchive support for the iPhone. Because all data entities are modeled in the repository it is simple to create GUIs, rules, content and validate them for correctness.

ACM Dashboard in Papyrus Platform

A key difference to all other BPM and Case Management products (adaptive, agile or dynamic) is the state-of-the art embedded content management capability of the Papyrus Platform. The inbound and outbound content software functions can be instantiated on any node and mostly any number of times. A complex network of automated and intelligent agents can be set up to execute in any kind of complexity required. Peer-to-peer node communication powers the Papyrus enterprise service bus with its long list of messaging (i.e. SOA) adapters and database type-managers. All changes to the process, including its content is fully change and version managed with automatic deployment and roll-back to any number of users. Depending on the setup, processes that are already being executed can be selectively updated with new functionality. All process execution elements are archived and remain fully auditable. Any process can at any time be reinstantiated and continued should the process concept allow for that.

The technology of the Papyrus Platform is unique with its object-relational database and distributed execution engine in a peer-to-peer kernel developed in platform portable C++. It was designed in 1997 and became first available in 2001 in major installations with up to 5000 users. As a unique niche player, ISIS focuses on complex and exceptional projects and needs rather than a let’s-do-it-all mass market.

The Papyrus Platform is unique in the sense that it is an application modeling and model execution infrastructure that supports the creation of standalone business applications, integrated GUI front-ends for desktop and portal, as well as a powerful goal oriented business process environment.  It is most likely that a mix of all three types of user interaction will be the norm in the future.

Papyrus Supports New OASIS Open Standard CMIS 1.0

The OASIS international consortium today announced the approval of Content Management Interoperability Services (CMIS) version 1.0, a new open standard that enables information to be shared across Enterprise Content Management (ECM) repositories from different vendors. Advanced via a collaboration of major ECM solution providers worldwide, CMIS is now an official OASIS Standard, a status that signifies the highest level of ratification.

The OASIS CMIS 1.0 ratification is an important first step to enable businesses to freely make important solution choices for ECM, BPM and CRM applications without being limited to the functionality of the underlying archive system vendor. We hope that subsequent releases will reach beyond access to content and metadata, and we are positive that this emerging standard – which Papyrus Platform already supports – will be widely adopted and increase motivation for continuous expansion to full content interoperability in process-oriented environments.