Things you can do with iPB

iPB is a tool for building executable process maps. Independently whether you have a process map, or need to build one,  iPB is a tool for you:

  • If you do not have a map, and need to build one, you use iPB to draw your map and share it with others.
  • If you have a process map, you need iPB to make it work so that everybody can get help in following it up in each particular case and moment.

Technically speaking, you can do two things:

  1. Create a process map (more exactly, process definition) and share it via WEB with all concerned. The main module for this task is Map designer that facilitates creating process steps and arranging them in a flow.
  2. Given a process map create a system/service that supports/implements the process and give WEB access to it to everybody who needs/desires such a service. The main module for this task is Form designer that facilitates creating electronic forms attached to the steps of the map.

How much of the first, and how much of the second you do, depends on the nature of the project for which iPB is used. For example:

  • If the goal is to map and document business processes in an organization, you do much of the first and none (or little) of the second
  • If a process map already exists on a piece of paper, in your head, or in your computer, and you want to make it work, you do much of the second, and little of the first (adjusting your map to the iPB standard)
  • If your goal is creating requirements for a system that satisfies some business needs, you do much of the first, and some of the second by creating a prototype of the future system
  • If your goal is to create a system/service starting from analysis of the needs and ending with an operational system/service, you do much of the first and much of the second.