1 / 16

Pushing the border of IT support for processes

Pushing the border of IT support for processes. Move to the Matrix. Current IT processes have a problem … and a solution. There is a need to revisit how systems manage processes – description of the problem and the "mind trap"

tovah
Download Presentation

Pushing the border of IT support for processes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Pushing the border of IT support for processes Move to the Matrix

  2. Current IT processes have a problem … and a solution • There is a need to revisit how systems manage processes – description of the problem and the "mind trap" • Apply the right tool for the process – a 2 by 2 model for catgorizing process tasks • There exists no single Workflow Standard • Buyers of BPM Systems get a ”strait jacket” – and unsatisfied users, longer process times than before IT • Designers spend ages and never complete their process designs • If I say ”workflow” everyone falls in the ”Flow Chart Mind Trap”

  3. The simple flow patterns are supported by all …

  4. … but the more advanced patterns are not covered by current standards UML BPMN BPEL

  5. One problem is that "Flow Charts" get messy in the complex process domain ”A messy workflow” Source: Ultimus

  6. Apply a process model, which suits the problem and its solution Solution complexity (Number of steps) Pro-ject Treat-ment 24 Appro-val Diag-nosis Problem complexity (Nature and number of variants) 7

  7. Allready at appr. 25 process steps and 8 decision points a flow chart is unsuited as process model: Messy, unclear, and inflexible to design

  8. The right data models for the processes Project Treatment Many steps & actors Solution complexity Diagnosis Approval Few steps & actors Simple rules, few variants Complex rules, many variants Problem complexity

  9. The Process Matrix – an extension to Gantt – scales well with the number of steps, and it can be certified by an auditor

  10. Symptom: when specifying advanced processes (e.g. clinical process) people opt to use a matrix

  11. A Flow Chart can always be imported into a Process Matrix – and is thus a subset Flow Chart Process Matrix Dept 1 Dept 2 Pre-deces Dept 1 Dept 2 A B Start <Always> 1 Step 1 X - Step 1 1 A 2 Step 2 - X 2 3 Step 3 - X A and B No Yes A? • Benefits:Dynamic freedom • Only the necessary constraints enforced • Users may work simultaneously in parallel • A and B may be decided any time • Easy overview for users – Gantt like • Orderly design – auditable for conformance Step 2 End No Yes B? Step 3 End End

  12. The design process from Flow Chart via Process Matrix to operational IT system 1 2 Import from BPMN it is adisble to take advantage over better description options (post edit) 1 Modify in workflow designer – a faster editing than drawing a flow chart 2 3 Fast prototyping – users can see the advantages of the new process and approve it 3

  13. Show time [demo time] • Seeing is believing • A skeptic who wanted to experience blind love

  14. Demo: Workflow Designer allowing fast prototyping of Process Matrix designs

  15. Add a dimension –Move to the Matrix

More Related