Designing a process
Proces w firmie da się zmienić bez projektu informatycznego. Jak dobrze opisać potrzebę, żeby nowy albo poprawiony obieg powstał szybko i trafił w to, o co chodzi.
A process as configuration
The flow of a matter, the approvals, the order of stages, all of this in Opero is a setting, not a program to be written. That is why a new process or a correction of an existing one arises in days, not months, and does not require a system update.
One thing matters: describing well how a matter is to flow. The more specific, the fewer rounds of correction.
Describing the need
The administrator will build a process faster with this information.
- Stages. The states a matter passes through, in order. For example: submitted, to approve, approved, completed.
- Decisions. Where someone approves or rejects something and what happens then. A rejection usually turns a matter back; it is worth saying where to.
- Who does what. At each stage: who is to perform the task and who may push the matter on.
- Conditions. Whether there are things without which one may not move on, for example a missing amount or a missing attachment.
- Endings. How a matter may end. Often there is more than one ending, for example completed and rejected.
Example. Instead of "I want an invoice flow", write: an invoice comes in as To check (accountant), after checking it goes To approve (manager), the manager approves or rejects with a comment, and after approval the invoice is Approved. That is enough to build a process without further questions.
Effects of a change
- A change comes in wholesale and at once, after the administrator publishes it. Until then the old version is in force.
- Matters already started will finish under the old rules. The new flow works for matters started after the change. This is intended, so as not to overturn matters in progress.
- Data does not disappear. Changing the flow does not touch the records' contents or the history.
Incorrect process behavior
Report a specific matter and the course that did not match expectations: the record number, what you did, what you expected, what happened. The administrator will reconstruct that matter's course, and it usually turns out to be one of two things: either a case the flow does not cover came up, or the matter went exactly as arranged, only the arrangement needs a correction.
Course history
Każda sprawa prowadzona procesem zapisuje swój bieg: kto, kiedy i jakim przejściem ją przesunął. Dzięki temu da się odtworzyć decyzje bez pytania kogokolwiek.
Rules - introduction
Reguła to automat, który sam robi rutynową czynność: wysyła powiadomienie, przelicza wartość, tworzy dokument. Dzięki temu nie trzeba pamiętać o powtarzalnych krokach.