Workflow Sample

Happy New Year!

In the previous article, space had run out in the middle of "Gundam Sortie Workflow".
So we'd like to continue to describe the rest. If you haven't read the previous article, please read it first.

The important operation comes after is [3. Command to Sortie].
It is also up to Captain Bright Noah's decision in his mind. But actual 'Order' will be transmitted by Communication Officer, Sayla Mass. In the cases like this, an operation is separated into 'Direction' and 'Operation', a Workflow system is also useful.

That is, the director monitors progress of the process after making important decision on process came through the Workflow. It helps him to concentrate on "the next decision" or "emergency command". It is more better if the operating screen for the director is simpler.

And then pilot Amuro Ray sortie. (Finally!)
As business process definition, receiving [3. Command to Sortie] from Sayla Mass, a Communication Officer, only react [4. Accept Sortie]. For the flow here, he cannot [Return] the Task. There's no time to fuss saying "Not even my own father hit me before!".
Of course, there are no way to refuse the sortie for a fifteen year old boy, when beautiful seventeen year old girl speaks to him " Listen Amuro, you are a real talent..."

[Gundam Sortie Workflow 2]

Let’s make the process (workflow) so that sortie Gundam. This process will help rookie soldiers successfully work for the fight. It is quite helpful. (I wonder really it is helpful…)

“Gundam Sortie Workflow” defined in this article is composed of roughly four tasks: “1. Detecting Enemies”, “2. Order Action Station”, “3. Sortie Command” and “4. Sortie”. However, there is a case that no sortie is actually done. So we must take care of where the bifurcated points are defined and when the process is finished on the way. Let’s learn more detail!

First, this process starts from “1. Detecting Enemies”. There are two cases such as radar detects enemies automatically and humans find enemies visually. Anyhow, a flight controller must report to the Captain. From the point of view of designing workflow, you should not list detailed development in this case. We want to focus on abstract process such as “report to the Captain”.

By the way, if you report to the captain orally, the business record cannot remain (rather the workflow system has no role in this case). I sincerely recommend to report with ”Questetra BPM Suite SaaS Edition” .

…Yes! Using this workflow, Captain Bright Noah could check the situation by email even if he has been working at his own desk or has been exercising in the gym (!!?).
…Yes! “Alert in the ship” will be automated if the alert system works together with RESTful. This is convenient.
…Rather, what were reported and when they were reported are automatically saved as “business record” . This is so convenient.

By the way there are two flight controllers in the White Base. As you know, Oscar Dublin and Marker Clan are the only two. Therefore, the process of this workflow will stagnate if those two persons are absent. This fact is to be specified as “risky item” in the Risk Control Matrix (RCM) documents.

[Gundam Sortie Workflow]

It is the idea that counts when it comes to small gifts and souvenir for Sales promotion. Novelty that 'seen somewhere' is not very impressive.

In such a case, you would better ask Professional. Much better than a bunch of 'amateurs' in House...When you think so, External companies begin to join the Workflow.

The Novelty Production Workflow, here we introduce to you, begins with a setting by personnel in Marketing, the request of quantity, theme and etc..(Task [1. Request Setting]) 'The external Pro' (novelties sales company) will create a proposal(in GoogleDocs,etc.), and enter the URL into Task

[Novelty Production flow]

People ask works. This is a familiar story.

However, you don't know what have been asked in-house. If you can visualize them and analyse, you will see the "chain" of works. Yes, the chain is that true Workflow.
Here, we are going to consider a simple flow to visualize and to manage.

[Asking Flow]

'Wish to accept "Campaign Registration" with Google docs's Web Form!'
It's really frequent story, in this Cloud Computing era. In many cases, using the "Google Apps" Web form. Some people may combine with Google Sites. It's really easy to create a Public Form. Amazing Customizability. Even the totalization is in real-time. And the best point is, it is for free!

But yet, merely accepting them is not satisfying. Yes, want 'Quick Response'. For example, 1. Sending completion email, 2. Shipping out relating materials, 3. Passing over registered information to Area sales staff,,, want to achieve such a Workflow. However, Google Apps provides no Workflow function.

Now, here comes a Workflow, dynamically cooperating with Google Apps, 'Questetra BPM Suite'! It is also for free. It will help more people more efficiently, yet will be able to respond quickly!!

[Registration flow Area select]

"BPO" stands for Business Process Outsourcing.

To outsource non-core business, such as Affairs, Accounting, Personnel, Welfare Program, or Contact Center. Among them, companies that are outsourcing "Information system" are frequently seen. (Especially, it is called "IT outsourcing".)

e.g.: Claim Management, Data Entry, Data Analysis, Agency Management, Sales Training, Product Testing, etc.

For the trustee side, advances of System Integrators, Printing companies, Consulting companies,etc. are remarkable, as well as "BPO Vendor which specialize in BPO" and "Offshore BPO companies which take advantage of low wages of outside country". The market will still continue to expand. (Incidentally, the Japanese BPO market is already one trillion yen, even though the growth is slower compared to the global market.)

In BPO, "visualization of business process" and "development of operation manual" is very important for both entrust and trustee. However, those are difficult. Now, we assume a scenario that a trustee (outsourcer) will propose business process (interim process) on the step of sales negotiation.

The following is a business process for "business of designing and proposing business process". (complicated...)

[Workflow to design Workflow]

"Proposal" is important. A lot of proposals are written with keywords like "New Business", "New Products", "Business Improvement". The more the better for a company. In reality, only a few of those proposal is adopted.

In the following "Proposal Review Workflow", proposals are sieved in each stage. The president will read finally survived proposal only.

But, it is not interesting only to adopt "Survival" of the proposals into business process. Rather you would better make those sieved out proposals into assets of the company. That is, to build an environment that "Reusable Proposal" can be excavated.

[Proposal Review flow]