"Free Trial Account" Issuance Automated And Unmanned

Issuing "Free Trial Account" in practice, manpower required on some occasion by all means. But what men do is only inputting same fixed commands into computer. "Free Trial Account" is sure to be issued by Automated And Unmanned when receiving Applicant information.

In the Workflow model below, It issues "Free Trial Account" without manpower by receiving info from BPM. Only whenever error occurs, human needed. Making inter-working between human and computer is the real pleasure of BPMS.

• Similar:"Automate From Acceptance To Issue On Trial Account"

<Tasks>
1. Application Info, 2. Manual Issue Account

[Trial Account Issue-Automatic Issue: [2. Manual Issue Account]　screen]

Automate From Acceptance To Issue On Trial Account

In any business, "Free Trial" is important. Sending out samples, issuing trial accounts... But don't want to spend much cost on them. We want make [Accepting Free Trial Flow] automated.
Today's Workflow model below is a example of process in issuance of Free Trial account.

<Tasks>
1. Application Info, 2. Issue Account

[Trial Account Issue: [2. Issue Account]　screen]

Ad Hok Flow Without Procedure

"Ad hoc", a Latinic phrase. There is no specific word or phrase for us Japanese, so we use that as it is.
Then what does it mean? For example, we use them like "ad hoc Network" or "ad hoc working area" and it stands for "not permanent" and/or "temporary measure."

In the category of Workflow (Business Process), there're expressions like "ad hoc Task" or "ad hoc workflow." To say in plain words, they are series of tasks that not fixed who or how to proceed. "Circulation of document" and "Multiple approval" cases are introduced as example. How they should be treated, with [Workflow system]? or with [Group ware]? are discussed.

Theme of eighth installment in the BPMN lecture series is "Designing ad hoc Tasks"

-BPMN lecture series Before-

• Split Conditions are a Basic Concept in BPMN
• BPMN Splits for flexible flow conditions
• Automatically Sending Template Emails in the Middle of a Workflow
• How to Design Primary Workflows With Many Baby Workflows
• Eternal Looping
• Never Use Your Own Rules When Designing Workflow Diagrams (interrupting flows that include concurrent processing)
• Same Results, Different Starts (Multiple Triggers)

<Tasks>
1. Task, 2. Task

[BPMN Sample-Ad Hoc <Loop>: "2. Task" screen]

Make Complaint Treatment Efficient With Sharring "Best Practice"

The key to smooth complaints treating is to share the know-how. In other words, how we manage "Best Practice".

It's alright to select the Best out of whole thing weekly or monthly. But we often apt to leave to chance putting it later for what you have right in front of you. You'd better put "Best Practice Point" sequentially through treating complaint.

Similar:

• "Shift Your Tension By "Type Of Complaint""
• "Distinction On Complaints by Priority With Automated Filter"

<Tasks>
1. Register Complaint, 2. Primary Respondent, 3. Correspondence, 4. Report, 5. Best Practice Point
2b. [Urgent] Primary Respondent, 3b. [Urgent] Correspondence

[Complaint Treatment-Best Practice: "5. Best Practice Point" screen]

Distinction On Complaints by Priority With Autmated Filter

The way how to treat complaints are different between companies for their scales or what the sell.
Even distributes on a distributes worth stationary, Listed company must treat it carefully. In other hand, for a company which distributes Free-software to the world wide, they must ignore some complaints. But in any case, accumulation of complaint and analysis on them are very important activity for maintaining their competitiveness.

In the Workflow model below, each complaint is filtered automatically and with higher priority can be acknowledged easier in sight.

Similar: "Shift Your Tension By "Type Of Complaint""


<Tasks>
1. Register Complaint, 2. Primary Respondent, 3. Correspondence, 4. Report
2b. [Urgent] Primary Respondent, 3b. [Urgent] Correspondence

[Complaint Treatment-Sort by Priority: "2b. [Urgent] Primary Respondent" screen]

Shift Your Tension By "Type OF Complaint"

"Complaints" should be treated in different ways up to such a case as the quality of merchandise or service was not good than company would provide, or as even the quality was good but the customer wasn't satisfied.

• A. Deficient (merchandise or service was less than expected quality.)
• B. Disappointment (Quality was enough but the customer expected more.)
• C. Other (Complaint on others except merchandise or service)
• D. Harassment

And about "a person who complains", we can classify into, for example,

• 1. Low risk of losing Regular
• 2. High risk of losing Regular
• 3. High chance of getting Regular
• 4. Low chance of getting Regular

Well now...A-1, B-3, C-2, which Complaint should be treated right away...?

<Tasks>
1.Register Complaint, 2. Primary Respondent, 3.Correspondence, 4. Report

[Complaint Treatment-Individual : "2. Primary Respondent" screen]

Automatic Analysis On Sensor Information And Change The Flow

"Auto-sensing Data comes in!" Should we start Inspection right away? (maintenance on Server, vending machine, internal computers...)
It's not a simple story. Maintenance costs rise up if all the detection of sensors had inspected right at the time. It may affect Corporate cost structure. But you cant leave it.
So make "Conditions" if response immediately or not. In this kind of workflow, the most improving point may be to brush up imposing conditions.
similar article;

• "Maintenance Duty Certainly Is A Flow"
• "Periodic Or Emergency, Maintenance Duty Goes On Almost the Same Flow"

<Tasks>
1. Inspection Point, 2. Inspection Date, 3. Operation of Inspection Report, 4. Repair Date, 5. Operation of Repair Report, 6.Confirmation

[Maintenance Duty-Receive Inspection Data:[2. Inspection Date] screen]