To issue a Bill.
People who have experience of working in Accounting Department, would know how I feel great doing it.

Creating documents are cumbersome.
An exceptional handling might have been needed for some customers.
But, however, when I understand that "each one of these are the fruits of my colleagues", I will be more passionate working on those , hard and without any mistake.

[Billing Payment Confirmation Flow]

To ask somebody to work. In many cases, they tell the contents of the work request by a one-on-one communication, such as "email" or "verbal". But realistically, the one who "has been asked it" and even the one who "asked it", totally forget about the request as if it never existed in the next day. Inbox is a graveyard of 'Work Request'.

Especially, working with Workflow, workers concentrate to work on Tasks in "My tasks" list. So that such 'verbal request' will be forgotten for sure because it is not in the list.

Well... now...let's think about taking the simplest 'work request' into Workflow. As a matter of course, basic task flow is quite simple. That is, it is consist of three steps, [1. Request a Work], then [2. Complete the Work], and at last [3. Confirm Completion].

[General-purpose work request flow]

'Obtaining multiple quotations', it is quite a day-to-day work.
In particular, there is price competition between distributors such as electricity products and moving services . The ordering side, basically makes a contract to trader who gave quote less expensive.
On the other hand however, it is not so simple to compare companies such as consign System Development or Designing, by price. Because they have differences of "level of recognition on order side company situation", and also they have likes and dislikes.

Well honestly,,, I don't think this business template is ready to use, because situation of procurement is different between the companies. Yet, I sincerely would like you to establish a Workflow of "Competitive Quotations and Vendor Selection flow".
At least, it is tremendously significant to record progress from 'multiple Quotations' to 'vendor selection' and 'the final contract'. When you count to ten contracts recorded, you will see various 'problems'.

In the Workflow below, the procurement personnel who collects quotations from vendors, is different to evaluation personnel who selects a vendor by their quotations. You can call it a Workflow definition that prevent fraudulent transactions.

[Competitive Quotations and Vendor Selection flow]


A staff greets to new member of her/his family. Yes, how happy it is to welcome new life. On the other hand, various procedures to the company and government offices is also waiting for her/him. For the staff her/himself, those procedures are rather "anxious" than "troublesome" because it happens not so often in her/his life.

The company could support those anxious and troublesome procedures that come along with the 'happy occasion'. In the cases of Japan, staff must make 'child born report', because the social insurance related procedures are carried out through a company. Why don't you starting "total procedure support, including procedure in government offices", using the report as trigger?


[Childbirth Procedures flow]

Want to "move" to new system with "business data" of the past, together ?
It's the 'migration' that most of SIers hate. Customers of Questetra often ask question about it.

However...
In the first place, "the date of processed" of each Tasks is that important. It doesn't make much sense to move "business data" as final deliverable alone. No, rather you shouldn't move 'business data' at all... (Whoops, I shouldn't be curt that way. Some people want solution seriously.)

If you do want to migrate "business data" in your workflow to your new system, you've got to do is to setup a 'data spout'. For a concrete example, I will show you a process model in my latest article "Learn BPMN by 'Daily Report'". The workflow definition (Workflow Diagram) below looks like the same as the one before at a glance. But there added one strange Start point.


[Daily Report flow - Record Tasks]

Learn BPMN by 'Daily Report'

Monday, May 21, 2012
"It is easy to understand a business by looking 'BPMN', but when it comes to draw, it is hard."
(BPMN:Business Process Model and Notation)

Yes, it sure is hard. But in other words, if people do not consider "A Work flow to be", they would never be able to draw forever.
  • How many work to do will come out in daily ? And how many more at Accounting period-end ?
  • Who to be processing ? How many personnel to do ?
In any how, knowledge of how the business flow are must eventually. Knowledge of 'IT' are rather not asked.

Well then, how could you let BPMN penetrate within the company ? There is no way but start drawing simple daily work in BPMN. If you are writing daily report or let your people to write, I recommend you 'Daily Report flow'.


[Daily Report flow]

The Workflow notation nowadays are easy to understand. (BPMN)
The most fascinating point is 'anyone can understand flow of works at first sight'. And it's also good that it is 'World's standard' De facto.

But in the other hand...
Employees who work on site can participate in the discussion, and exchange hot debate about 'Workflow to be'. As the result, Process owners will be in the situation that their adjusting ability to be asked. That's right, they can't be helped because it is what they are working for, but they can get Knowledge armament by reading "The Golden Rules of Business Process Modeling". Yes, BPMN is also an 'discussion tool'.

Now...
There is a request on Decision Making Flow, that an approver himself can add other approver before the approval. There are somebody to be asked to approve, even by the regulation (Business rule) does not require to do so. Behind-the-scenes work, or NEMAWASHI in Japanese... Well now, what you do?


[Decision Making Flow]