Workflow Sample

Workflow Sample
Workflow Sample

Contact

Process Archives

Official Process Archives

Process archives are business process models designed in Questetra BPM Suite and saved in file format. They can be imported into any Questetra BPM Suite that is installed and operated in another server.
* Please note that process archives created in newer versions of Questetra BPM Suite may not be properly imported into older versions of Questetra BPM Suite.
 
There is no limitation to the possible variations of business processes. The Official Process Archives available in this page are processes that Questetra assessed can be used in many organizations and can contribute to the improvement of business quality.
 
Please use the Official Process Archives as samples and hints for designing other business processes.
* Many of the Process Models available in this page were originally designed for the October2009 version, but they can all be used in newer versions as well.
 
 

Organization Info

The Official Process Archives are created with group settings defined as below.
  • Org
  •  - HR & General Affairs
  •  - Accounting
  •  - Marketing
  •  - Sales
  •  - R&D

Office Info

The Official Process Archives are created under the assumption of the below workplaces.
  • Tokyo Main Office
  • Osaka Branch

Archives List

To learn how to use the Process Archives, see our Usage of QAR Files page.
Feel free to try the online Quick Trial version, in which some of the below process archives are already imported and ready to use.
Please also check other types of process archives (some of them overlap with below archives), available from Case Study page in Questetra BPM Suite website.


Basic Process Models

Process Model samples with basic functions.

Category

Title

Summary & Flow

Process Diagram
(Click to enlarge)

Download

Date

Sales, Marketing Customer Inquiry Management
Point of contact receives and checks the content of inquiry. If necessary, advice is sought from other departments before reply is created. Then Supervisor approves.
This is the simplified version of a Process Model that one of our customers actually uses.

 Dec 21, 2009
Blog Posting (Bilingual)
Initiated by manager.
Composer -> Translator -> Peer review -> Post by Composer -> Final check.
If translation is not necessary, the step can be skipped.

 Dec 21, 2009
Complaint Management (Technical)
Point of contact -> Person in charge of response -> Leader -> Point of contact reports to customer.
If the complaint is considered to have high priority, information of complaint is reported to executives.

 Dec 21, 2009
Proposal Draft Leader starts by appointing a member.
Member -> Leader check.
If the draft is rejected by Leader, the process returns to Applicant.

 Nov 24, 2009
Estimate Submission Two methods available: 1) Leader starts process by appointing a member, 2) member starts process.
Flow is the same as "Proposal Draft." 

 Nov 24, 2009
Order Acceptance Report Sales member -> Head of Sales Dept. ->Accounting.
If the report is rejected by Head of Sales Dept., the process returns to Sales Member, and if rejected by Accounting, the process returns to Head of Sales Dept.

 Nov 24, 2009
Contract Check by Legal Department Applicant -> Supervisor -> Legal Department.
If the application is rejected by Supervisor or Legal Dept., the process returns to Applicant.

 Nov 24, 2009
Application: Open/Change of Transaction Account Applicant -> Supervisor -> Accounting.
If the application is rejected by Supervisor or Accounting, the process returns to Applicant.

 Nov 24, 2009
All departments
Daily Report Staff -> Leader.
If the report is rejected by Leader, it returns to Staff. The process normally starts by timer. Start the process manually after forcible termination and when reporting works on a holiday.

 Oct 26, 2009
HR & General Affairs (Attendance and absence) Attendance Record Submission Method of submission: attach Attendance Record File.
Staff -> Supervisor -> HR & General Affairs.
If Attendance Record File is rejected by Supervisor or HR & General Affairs, process returns to Staff.

 Oct 5, 2009
Application: Absence from Work Applicant -> Supervisor -> HR & General Affairs.
If the application is rejected by Supervisor or HR & General Affairs, the process ends without returning to Applicant.

 Oct 5, 2009
Application: Late Night Overtime Flow is same as "Application: Absence from Work."

 Oct 26, 2009
Application:Holiday Compensation Flow is same as "Application: Absence from Work."

 Oct 5, 2009
Application: Maternity Leave Applicant -> HR & General Affairs -> Supervisor.
If the application is rejected by HR & General Affairs, the process returns to Applicant.


 Nov 24, 2009
Application: Childcare Leave Flow is same as "Application: Maternity Leave."

 Nov 24, 2009
Application: Family Care Leave Flow is same as "Application: Maternity Leave."

 Nov 24, 2009
Application: Long-term Leave Flow is same as "Application: Absence from Work."

 Nov 24, 2009
Report of Injury or Illness To be used when taking temporary leave due to injury or illness. (A more fragmented version of "Application: Long-term Leave")
Staff -> Supervisor -> HR & General Affairs.
If the report is rejected by Supervisor or HR & General Affairs, it returns to Staff.


 Jan 18, 2010
Report of Disaster To be used when taking temporary leave due to disaster such as fire or earthquake. (A more fragmented version of "Application: Long-term Leave")
Flow is same as "Report of Injury or Illness."


 Jan 18, 2010
HR & General Affairs (Other) Change of Address & Commutation Staff -> HR & General Affairs.
If the report is rejected by HR & General Affairs, it returns to Applicant.

 Oct 5, 2009
Application: Salary Deposit Account Registration/Change Applicant -> HR & General Affairs.
If the application is rejected by HR & General Affairs, the process returns to Applicant.

 Oct 26, 2009
Application: Certification Issuance Applicant -> HR & General Affairs.
If the application is rejected by HR & General Affairs, the process returns to Applicant.

 Oct 26, 2009
Change of Personal Information
Applicant -> HR & General Affairs -> Supervisor.
If the application is rejected by HR & General Affairs, the process returns to Applicant.

 Oct 26, 2009
Change of Family Information
Flow is same as "Change of Personal Information."

 Nov 24, 2009
Application: Congratulatory & Condolence Payment Applicant -> HR & General Affairs -> Supervisor (if approved).
If the application is rejected by HR & General Affairs, the process ends without returning to Applicant.


 Jan 18, 2010
Application: Medical Physical Examination Applicant -> Supervisor -> HR & General Affairs.
If the application is rejected by Supervisor or HR & General Affairs, the process ends without returning to Applicant.


 Jan 18, 2010
Application: Business Cards Applicant -> Supervisor -> HR & General Affairs.
If the application is rejected by Supervisor, the process ends without returning to Applicant. If approved, data is adjusted at HR & General Affairs, and then flows to receipt.

 Oct 5, 2009
Application: IP Address & Computer name Organization in which HR & General Affairs manages the PC info, and applicant performs setting.
Applicant -> Supervisor -> HR & General Affairs.
If the application is rejected by Supervisor, the process ends without returning to Applicant.

 Oct 5, 2009
Application: Use of Computer Organization in which HR & General Affairs manages and sets the PC, and hands it over to Applicant.
Applicant -> Supervisor -> HR & General Affairs.
If the application is rejected by Supervisor or HR & General Affairs, the process ends without returning to Applicant.

 Nov 24, 2009
Application: Business Trip
Applicant -> Supervisor.
If the application is rejected by Supervisor, the process ends without returning to Applicant.

 Dec 21, 2009
Application: Registration for Qualification Exam Applicant registers for qualification exam after receiving approval.
Applicant -> Supervisor -> HR & General Affairs.
If the application is rejected by Supervisor or HR & General Affairs, the process ends without returning to Applicant.

 Nov 24, 2009
Application: Registration for Seminar Attendance Flow is same as "Application: Registration for Qualification Exam."

 Nov 24, 2009
Qualification Acquisition Report Applicant -> Supervisor -> HR & General Affairs.
If the report is rejected by Supervisor or HR & General Affairs, the process returns to Applicant.

 Nov 24, 2009
Seminar Attendance Report To be used together with "Application: Registration for Seminar Attendance."
Flow is same as "Qualification Acquisition Report."

 Nov 24, 2009
Application: Company Seal Request Applicant -> Supervisor -> HR & General Affairs.
If the application is rejected by Supervisor, the process ends without returning to Applicant.

 Nov 24, 2009
Application: Goods Transfer Applicant -> Supervisor -> HR & General Affairs.
If the application is rejected by Supervisor or HR & General Affairs, the process ends without returning to Applicant. 

 Oct 26, 2009
Application: Equipment Repair Flow is same as "Application: Goods Transfer."


 Jan 18, 2010
Application: Telegram Request Applicant -> Supervisor -> HR & General Affairs.
If Supervisor or HR & General Affairs decides the telegram is unnecessary, the process ends. If Supervisor decides the telegram must be revised, the process returns to Applicant.

 Oct 5, 2009
Written Apology/Incident Report Applicant -> Supervisor -> HR & General Affairs.
If the report is rejected by Supervisor or HR & General Affairs, the process returns to Applicant.

 Nov 24, 2009
Report of Lost Property Staff -> Supervisor -> HR & General Affairs.
If the report is rejected by HR & General Affairs, the process ends without returning to Staff.

 Dec 21, 2009
Application: Use of Company Car Applicant -> Supervisor -> HR & General Affairs.
If the application is rejected by Supervisor, the process ends without returning to Applicant.


 Jan 18, 2010
Report of Accident Applicant -> Supervisor -> HR & General Affairs.
If the report is rejected by Supervisor or HR & General Affairs, the process returns to Applicant.


 Jan 18, 2010
Application: Company Housing (Move Into)
Applicant -> Supervisor -> HR & General Affairs.
If the report is rejected by Supervisor or HR & General Affairs, the process returns to Applicant.


 Jan 18, 2010
Application: Company Housing (Move Out Of) Applicant -> Supervisor -> HR & General Affairs.
If the report is rejected by Supervisor or HR & General Affairs, the process returns to Applicant.


 Jan 18, 2010
Accounting Application: Executive Approval Applicant -> Supervisor -> Accounting -> Head of Applicant's Department -> President.
If the application is rejected by Supervisor or Accounting, the process returns to Applicant. If it is rejected by Department Head or President, it returns to Accounting.

 Oct 5, 2009
Application: Reimbursement One application for each refund.
Applicant -> Supervisor -> Accounting.
If the application is rejected by Supervisor, the process returns to Applicant. If the application is rejected by Accounting, the process ends.

 Oct 5, 2009
Travel Expense Report One application for each day. However, up to 10 trips can be inputted in each report.
Applicant -> Supervisor -> Accounting.
If the application is rejected by Supervisor or Accounting, the process returns to Applicant.

 Oct 5, 2009
Application: Item Purchase Applicant -> Supervisor -> HR & General Affairs -> Accounting.
If the application is rejected by Supervisor or HR & General Affairs, the process returns to Applicant.

 Oct 26, 2009
Application: Temporary Payment
Final adjustment payments can be made within the process.
Applicant -> Supervisor -> Accounting.
If the application is rejected by Supervisor, the process returns to Applicant.


 Nov 24, 2009
Application: Client Congratulatory & Condolence Payment Applicant -> Supervisor -> Accounting.
If the application is rejected by Supervisor, the process returns to Applicant. 


 Jan 18, 2010

Process Models with Advanced Items

Process Model samples that use items in the "advanced" palette in the Process Modeler.

Category

Title

Summary & Flow

Process Diagram
(Click to enlarge)

Download

Date

"advanced" items
Timer Start Event
(Daily Report)
Process is started at fixed intervals (fixed time and day).
A normal Start Event is also prepared so that users can start manually when necessary.
* Also listed in above Official Process Archives list.

 Oct 26, 2009
Message Start Event
(Client Inquiry Management)
Process is started by HTTP communication, from online forms or external systems.
* Also listed in above Official Process Archives.
* For more info see Message Start Event Manual.
* A custom adapter for starting process by email is also available. Please contact us.

 Dec 21, 2009
Message Throwing Intermediate Event--Email
(Blog Posting)
Emails are sent according to specified settings. Process Data can also be embedded into emails.
*  Also listed in above Official Process Archives.
into email. 

 Dec 21, 2009
Message Throwing Intermediate Event--HTTP
Message Catching Intermediate Event
(Application for Absence from Work & System Linkage)
This Event enables the sending/receiving of messages with external systems via HTTP.
In this Process, an imagined external attendance management system is utilized.
* For more info see Message Throwing Intermediate Event (HTTP) Manual and Message Catching Intermediate Event Manual.

 Mar 11, 2010
Terminate End Event
(Request with deadline)
When the Terminate End Event is reached the entire Process is terminated.
In this Process the flow is separated into two, and when either flows ends, the entire Process is terminated.

 Mar 15, 2010
Team Swimlane
(Document Drafting)
This Swimlane enables multiple Users to execute one Task.

 Mar 11, 2010
Inclusive Gateway (OR)
Exclusive Gateway (XOR)
(System Complaint)
Inclusive Gateways (OR) divide the Process to the flow(s) that meet the conditions. Exclusive Gateways (XOR) move to only one flow.
* Also listed in above Official Process Archives list.

 Dec 21, 2009
Parallel Gateway (AND)
Join Gateway
(Request for Software & Manual Modification)
Parallel Gateways (AND) divide the Process to all flows. Join Gateways merge separate flows into one flow.
This Process connects gateways for more detailed control. 

 Mar 15, 2010

Process Models Using HTML Template Function (For version 6 and after)

Process Model sample using the HTML Template function, which enables complex customization of the Task Execution screen.

Category

Title

Summary/Flow

Process Diagram
(Click to enlarge)

Download

Date

HTML Template Application: Absence from Work With this sample, the Task Execution screen is configured to this excel form.
Click here to see the Task Execution screen.
*The Process Model itself (summary and flow) is identical to the "Application: Absence from Work" sample listed above, under Basic Process Models.

Aug 05, 2010

Process Model Interoperability (For version 6.1 and after, not available for Download Edition)

Process Model samples that inter-operate between Process Models, using Message Throwing Intermediate Events and Message Start Events. (One Process Model initiates another Process Model.)

Category

Title

Summary/Flow

Process Diagram
(Click to enlarge)

Download

Date

Process Model Interoperability Blog Posting (Bilingual) Initiation (Initiates max 5 Processes) This Process Model is for initiating the below Blog Posting (Bilingual) Initiated Process. The Model uses Message Throwing Intermediate Events (HTTP) and can initiate up to 5 Processes. The number of entered "Process titles" correspond to the number of Processes initiated.
In the Blog Posting (Bilingual) Initiated Process, the three Process Data Items (Process title, Date of Posting, Composer) are necessary, so all of these Process Data must be entered.
In order to use with the Blog Posting (Bilingual) Initiated Process, follow the below procedures:
  1. Import both Process Model archives. (Blog Posting (Bilingual) Initiation (Initiates max 5 Processes) and Blog Posting (Bilingual) Initiated) *It is convenient to open both Process Models in separate windows or tabs.
  2. Activate the Blog Posting (Bilingual) Initiated Process.
  3. Open the version details of the activated version.
  4. (In the separate window or tab) click [Edit] and open the Modeler of the Blog Posting (Bilingual) Initiation (Initiates max 5 Processes) Process. Click [Variables Setting].
  5. From the version details of the Blog Posting (Bilingual) Initiated Process, copy the URL found under "URL and Parameters for Message Start Event and Message Throwing Intermediate Event." Set this as the "ConnectURL" in the other Process's variables setting.
  6. Save the Process and activate.

Aug 05, 2010
Blog Posting (Bilingual) Initiated
This Process Model can be initiated via the above Blog Posting (Bilingual) Initiation (Initiates max 5 Processes) Process.
The Process Model itself (summary and flow) is similar to the "Blog Posting (Bilingual)" Process listed above, under Basic Process Models.

Aug 05, 2010

Process Model with New Function (For Ver. 6.1 and after)


Category

Title

Summary/Flow

Process Diagram
(Click to enlarge)

Download

Date

Development
Bug Management This Process Model was introduced in our blog on August 27 and 30, 2010. (SaaS BPM Blog)

Each Task, from the reporting of the bug to the final check, is allocated to the user that is specified in the previous Task. This is possible by selecting [All subsequent Tasks are allocated or offered by the same rule as the first task] (not available in earlier versions).Tasks and selections are numbered, to make sorting easier later. This sample is a simpler version of the Process Model that is actually used in our company.

Sep 17, 2010

How to use

  1. Click of the Process Archive you would like to use.
  2. Once the Process Archive (.qar file) is downloaded, use the "MD-03: New Model from Archive" function of QBPMS to import the archive.

Sign in  |  Recent Site Activity  |  Terms  |  Report Abuse  |  Print page  |  Powered by Google Sites