Workflow Sample

The 'Shipping Record of the Contract document' is not retained as you expected.
'When it was shipped?', 'Who did that?', 'What was enclosed with?'.
Unexpectedly, there is not although they are important somehow. Although communication record of the FAX or mail exist in its own way...

The following is a Workflow for processing shipping of 'Contract document, etc.'. What seems to be excellence of this Workflow, is the step of confirmation by phone call if it is surely delivered or not, in case of especially important contract. It reduces the risk of blocking the communication for 'contract' that is seriously important for B2B. Moreover, the auto-generation of 'Cover Sheet' is also excellent. Using a windowed envelope, you will not have to type the address and the name of the recipient on the envelope. It will not only lowers the shipping labor cost, it also prevents misdelivery. Hmm, it's quite convenient.

[Signature-Shipment flow-Cover Sheet generation]

I want to collect "customer data" only...

Workflow of Web lead handling, Inquiry handling, Outing report flow (Business card exchange)... 'Prospective Customer Information' is being collected in various operations in a company. Hopefully, it should be managed centrally. (Basic data for CRM activities)

The following is a Workflow only for managing Prospective Customer Information.
It is assumed to be transmitted such as 'Zip code', 'Country', 'Organization', 'Position', 'Name', 'Email Address' as main data, and 'email delivery agreement' (flag), 'prospectivity' (rating).

You can say this is 'Usage like a Database'.
But you should be careful that there is only adding of data one after another, it is not focused on "updating" or "Deleting". That means, you will need some kind of scheme when utilizing the accumulated data, such as narrowing down by the date or by the operator.
As well as it is an idea that will be required for utilizing so-called 'Big Data', there are many cases that you should give the priority to "adding" new information, and suppress the cost for "updating" and "deleting". Speaking specifically, you should not use "business card information of more than three years ago", unless you have to.

[Customer Data Collection]

Talking about Business Record, 'in the paper' is the standard.

A variety of information will be recorded in the paper such as 'Invoices', 'Orders', 'Contracts' or 'Meeting minutes' and so on. The basic idea about this is mostly from medieval or Roman era. The point is wanting to leave a proof.

However, managing the paper is not easy.
First of all, 'information searchability' is quite low. Moreover, almost impossible 'to share information'.

'Do you remember the date I mailed that contract document?'
'Is anybody sure if somebody has sent the order form?'

21st century, information terminal has become extremely popular. We must change the idea of 'leaving proof is just enough!' to 'To record the business data in a form that is easy to utilize'. We need to promote the digitization / electromagnetic recording, even a little bit.

The following is a workflow that attempting to record the "postal shipped from the company" electromagnetically, even a little.
It is focused on to record exactly the original digital data and processed time, instead of to making a copy with the copy machine and closing it to the binder. In case the document requires a signature, you can add 'scanned data'.

[Signature/Mailing flow]

There is not a few people whose business is to write "Proposals".

A Sales person in IT industry, a planner in ad agency, a consultant for government, etc., etc.... Those proposal writers would tend to be a 'lone wolf'. That means their writings could be hardly accumulated as 'know-how' and would have less reusability.
Even if a rule to 'backup in the file server' is given, it will not lead to Centralized management just because of a reason: 'CUMBERSOME'. Most of these proposal files profoundly slumber in some folder on someone's personal computer. These files should have been shared with everybody.

The following Workflow is defined an activity of 'reading somebody else's Proposal', as a 'Task'.
In this sample, the writer registers Presentation materials which he/she think to him/herself that 'I did a good job'. Then two of the coworkers who are designated will read it. And at the same time, the file is backed up to the specified folder in Google Apps, the online storage on Cloud. (e.g. "Proposal for New customers", "Proposal for Existing customers", "Template/ Others")

[Proposal Reviewing-Sharing flow]

"Recruiting and Job hunting", the way it should be have been discussed for decades.
Especially in Japan, it seems like 'a social problem that cannot be resolved forever'.

That is, companies want better talent as possible, so they start recruiting earlier than the officially agreed date. While students spend quite a lot of time searching for their future employment after their graduation rather than studying. Both of their interest matches, even though both of them think that is not the way it should be.

Companies and colleges have tried something so far.
In Japan, there was a gentleman's agreement which was called 'Agreement for Recruitment'. It is enacted in 1952, but the rule has never been complied until it is abolished in 1996. Even in the 21th century, A variety of approaches have been made such as 'Charter of Ethics' by companies, or arrangement between colleges. However, those were not enough to achieve the self-control of both them as well. I must say, it could not limit the activities of "companies that want to ensure new graduates at an early stage" and the "college student Look for employment desperately" as if "men and women who fall in love with love".

Spring of 2013, Prime Minister Abe summoned the economic organizations and requested a "further delay" on the recruitment period, said "it cannot be overlooked that students losing the opportunity to extend their capacity". Speaking short, ' those company explanatory sessions be held later than spring break (March, which is the end of the school year in Japan) of the third grade.' A " New Charter of Ethics" will be established by the economic organization soon, and will be determined "Spring Break of 3 graders (March)" which is three months later than currently "winter break of the third grade (December)".

It is necessary for companies that no choice but to (formally) comply with the gentlemen's agreement, to change more smoothly in the "recruitment work flow".

[Recruitment workflow]

When you talk about Workflow, it is Expense Claim.

For a business person, claiming the expenses is quite cumbersome. Although, only you have to do is to steadily input every time it comes out such as travel expense, entertainment expense, so on and on...

In the following workflow, a Process will be started 1st day of each month.
That is, to be allocated a Task of 'Expense Claim of this Month' to all the employees. The deadline is the end of that month. It is as if 'handing out an Expense Claim form paper on the first day of the month' in the real world. After that, employees input expense data each on occasion and save it. The Process will not go forward. And when it comes to the end of the month, and all input is completed, click on the [Claim] button.
The rest of the process is clear at a glance over the flow diagram. It must be approved at [2. Supervisor's Approval] and [3. Accounting's Approval]. If there are correction needed, Task of [1a. Correction and reclaim] as referring back will occur.

By the way, this Business Process is defined to create PDF file automatically after the claim has been approved. The Workflow product (BPM product) must be capable of outputting PDF using business data.

* Of course, we strongly recommend you Questetra BPM Suite.

[Expense Claim Workflow]

Fax, in the first place, is " transmitted data" through telephone line. It is such a waste to print out received data. It will never be worthwhile to reconvert digitized data into analog. Why do I have to walk around the office with paper in my hand? It could be easier to pass out, even through Workflow if the data had left in digital as it was.

The following is a Business Process which receiving faxes on a Cloud-based service, circulating it through Cloud-based Workflow, and back up to Cloud-based storage in PDF format.
It will be backed up to "Google Drive", the Online storage, eventually. Automatically backed up for example, purchase orders from the customer to "Fax Order folder", quotations from suppliers to "Estimates of Purchase Fax" folder. All that Who, When, viewed which fax will be recorded.

[Circurating Online Fax flow]