Workflow Sample: System integration

Showing posts with label System integration. Show all posts

There's no chance to spy what coworker has claimed for his advance pay if he applied in paper document.
However, those applications had done Online and optimized in company, you often see other person's claim unexpectedly.
And it gradually brings morality and "Commonsense" inside company.

To collect monthly applications in one document per person, [1. Application Advances Paid] task timed to launch on the first day of the month with initialized title like "Mr.Smith March period". A mechanism to make an employee habit of overwrite and save many times over through the month by looping [1. Application Advances Paid] task.

Expanding

<Tasks>
1. Application Advances Paid, 2. Approval by Supervisor, 3. Response to Notion, 4. Approval by Accounting, 5. Settlement
1b. Input Estimate, 2b. approval by Accounting Manager

[Application Advances Paid-Settlement Confirmation <Auto Launch> :

"1. Application Advances Paid" screen]

In the article"Bravery To Optimize Money Flow Inside Company", we didn't mention about "bills".

There must be processes of checking bills form outside before the first Task [1b. Input Estimate].
We would like to build a system that over takes previous process by adding "Message Start Event".

<Tasks>
1. Application Advances Paid, 2. Approval by Supervisor, 3. Response to Notion, 4. Approval by Accounting, 5. Settlement
1b. Input Estimate, 2b. approval by Accounting Manager

[Paid-Settlement Confirmation-Data Connection "5. Settlement" ]

You feel office meetings are inefficient.
It might because bad preparation. Deadline date is not given for Tasks of preparation.
(Always carelessness of secretariat)

Expand How to Optimize Meetings and improve them.

Workflow process below is added Deadline date into task of listing (2.Curriculum ideas) to notice all participant should do.

<Tasks>
1. Notify Date, 2. Curriculum Ideas, 3. Create Curriculum and Notify, 4. Pre-opinions/Minutes, 5. Create Meeting Minutes]

[Meeting Management <Curriculum Ideas Deadline>: "3. Create Curriculum and Notify" screen]

Important meetings are more often than not participated by members with high salaries. That means it's crucial to keep these meetings efficient. Facilitating meetings is not always the easiest thing to do, so it is extremely meaningful to optimize and standardize preparations.

Today's workflow sample allows users to link meeting data to the next scheduled meeting, after task 5 (Create Meeting Minutes). This eliminates having to prepare meeting minutes items.

(By the way, using workflow systems for meetings themselves increases visualization! But you have to be careful of authorization settings.)

<Tasks>
1. Notify Date, 2. Curriculum Ideas, 3. Create Curriculum and Notify, 4. pre-opinions/minutes, 5. Create Meeting Minutes

[Meeting Management <Data Integration>: "1. Notify Date" screen]

Our fourth installment in the BPMN lecture series.
After spending two or three months in business process management activities, you will probably start to want to connect processes in a "primary—secondary" relationship.
In other words, process a1 (model A) can:

Start process b1 (model B) [e.g. order acceptance -> production]
Start processes b1 and b2 (model B) [e.g. order -> shipping]
Start process a2 (model A) [e.g. this month's invoice -> next month's invoice]

The settings depend on what BPMS system you are using; naturally, we'll explain with the functions of Questetra BPM Suite.

Previous BPMN Lecture articles:

<Tasks>
1. Name your child

[BPMN Sample <Generate Child> : "Birth" setting screen]

The billing process is operated every month. The accounting team is responsible for sending out and processing every invoice without fail, and the sales team is responsible for being aware of the status of each customer. Yes, this process needs transparency.

We've already introduced several examples involving billing processes, but today let's look at an example of a company that issues multiple invoices in response to one order.

<Related>

<Tasks>
1. Input Invoice Data, 2. Confirm Invoice Data, 3-1. Check This Month's Content, 4-1. Send Invoice, 5-1. Confirm Payment

[Invoice Issuance <Issue By Order>: "3-1. Check This Month's Content" screen]

We introduced a workflow for Taking Data Outside the Office in the Era of Cloud Computing, but you don't want to grant and cancel temporary authorization manually. Naturally, the authorization settings for accessing data files depends on the system that manages those files. For example, if your company uses Google Apps as an internal platform, it will be necessary to use Google Documents APIs. (We must borrow the power of SE.)

* Google Documents List Data API v3.0 (Labs) - Modifying Document and Folder Sharing Permissions
* Google Documents List Data API v2.0 - Modifying Document Sharing Permissions

Tasks: Apply for Authorization to Access, 2. Give Temporary Authorization, 3. Handle Rejection, 4. Report Action, 5. Cancel Authorization, 6. Confirm Cancellation

[Data Access <Change External Authorization>: "4. Report Action" screen]

"A Workflow for Daily Reporting Work Time"
"Using Daily Reports Only for Cost Price Calculation Is a Waste"
"Go Ahead and Include All Necessary Info in the Daily Report"

Approved workflow data is usually used to calculate salaries and cost prices, etc. This could be done by an accounting software or an enterprise system, depending on the company. In any case, what we DON'T want to do is have someone transfer the information manually. In BPMN, a Message Throwing Intermediate Event is used for sending information to external systems.