ISIS Papyrus Software

Avoiding Constraints Of Conventional BPM

In benefits on November 10, 2009 at 3:05 am

When analysts come to the conclusion that end-user organizations want to be able to change their processes considerably faster than they actually can and add “They want to move to environments in which there’s a lot more self sufficiency on the part of the end user to configure the process,” this clearly reflects the constraints of currently used rigid process models.

To avoid such limitations ISIS Papyrus focuses on the business needs to respond quickly to dynamically changing customer requirements. The built-in process engine of the Papyrus Platform does not use simplistic procedural flowchart graphs to define the process but instead the Papyrus BPM is state and event driven to avoid problems associated with parallel activities, human interaction management and the rigid sequence of a procedure. This state and event driven process does not require complex decision blocks or listen-for-event-loops. All changes of the process are defined in the Desktop and stored in the central WebRepository.

Papyrus process management is flexible, understands the needs of users and supports knowledge-intensive business processes in combination with business communication. Users define the user interaction with the Activity Recorder and Natural Language Rule Editor and train the process sequence with the User-trained Agent. Collaboration, check-in/check-out, versioning, project management are generic platform functions. Other major benefits include:

  • Less process tuning and correction because an unforeseeable event sequence does not invalidate the process
  • Changing the state engine and event definition of one item updates automatically all processes using this item
  • Changes of the process do not require Java coding
  • No programming of dialogs required
%d bloggers like this: