BPM Features for Tracking Six Sigma Projects
The diagram below shows a complete Six Sigma project with all its required phases. Implementation process Six Sigma projects totally Recurring Is. Because the project must constantly repeat the definition to control framework in each phase.
What happens in each phase is based on the workflow framework, which will be described in detail below.

If we look at the example of Six Sigma process and processing. After the project is approved, the six projects management office Sigma (or the Six Sigma project manager) records it in the project tracking system and that's the start.

So the process with Register It starts and then the project based on six sigma criteria Definition will be During the definition phase, the project leader He must request the necessary documents to confirm and complete this phase in order to enter the phase Evaluation to be
In this process, Timeline It is added to the "document definition phase" and is presented in the form of a diagram and schedule. During the implementation of this process, if the project does not have any activity after a certain time frame, Warning to face Email will be announced automatically. This warning as Reminder It will be sent to the project leader to check how to proceed. In this particular plan, only one email is sent, but the process should be designed in such a way that the reminder email is sent at intervals be sent regularly. Until finally, the necessary reports of the project will be presented to review and approve moving to the next phase.
The phase of project review and approval requires Six Sigma project documents. These documents can be found in the "document definition phase" to be uploaded Also, the work flow can be adjusted in such a way that the information related to the process and the data in the database Save external data (such as: MySQL).
After the project definition phase is completed for document approval, the desktop review process by the manager or black belt board The project takes place. This work before Confirm Going to the next phase is done.
In the phase "document definition phase" and "document redefinition phase" one loop it has been shown. Because the project until by Unverified administrator, cannot continue.
this sequence Similar, from Evaluation to control It will be repeated in the next phases of the project. So part of the process is so repetitive until the project is finished.
1: User interaction in each phase: web bugs
The BPM workflow implemented by Farda Network BPMS provides a way for user action through web and task cartels.
Below is the web shape design theory used to register the project. This theory allows the entry of information related to The project gives the field defined for its management (as data related to the implementation of the standardized project).
"The web form contains the necessary fields for the project title, the names and email addresses of the stakeholders and is a means to Updates are attached files and "comment" field.
When the project leader is ready to present and submit the defined phase, then critical information about Six Sigma projects must be presented. become
For example, the timeline of each successive phase is a critical basis for project status reporting. The timeline of six projects Sigma is evaluated according to the deadlines agreed between the main project board and the stakeholders. Acquiring projects that Fully updated and completed on time, dependent on timely delivery of project documents and work. For this purpose, fields are stored for entering estimated information related to projects, in terms of amount and type.
It's simply too time-consuming when all this information about different projects is manually tracked in a spreadsheet. Backs up the program director and black belts. So automating them by process BPM A lot of help Facilitates the project management process.
2: User participation in each phase: user experience entry point
This section shows information related to the actual status of the project in the user's experimental environment. Instead of having a spreadsheet for Tracking Six Sigma projects, there is a network-based project system that follows the project workflow DMAIC follow.
Since the project leader, supporting black belts, and Six Sigma program manager can now access the data directly access and upload documents through the user experience entry point, little time to track email files Addition is spent. This time reduction is reflected in the review and approval time.
Important decisions and suggestions based on the project review can be entered in the place of comments and suggestions of the process. So that The project leader can make necessary corrections or updates in the provided project documents.
3: Other developments to complete project tracking
In addition to what is clearly stated in this process plan, a complete project tracking should include the following:

• Automatic creation of dashboard reports: via reporting Builder of tomorrow's network from data stored in external databases Uses. This report maker can automatically change and update the created dashboard reports.
• Automatic email reminder: based on the delivery date of dynamic goals in each phase, sent and presented by the project leader becomes
• Document Repository: It is the same document management system for storing all the project files through the workflow process.