Most of us would like to see Business Process Management Suites (BPMS) as the organization’s business hub, the heart of the organization, the mainframe that integrates with all of the other systems. To achieve this goal BPMS should be deployed as a full business process solution – not just as a one-off process implemented in isolation.
Providing organizations with built-in process templates enables the users to start using the BPM platform immediately.
The business-critical process (the main reason for purchasing the BPMS), will take some months to design, create, test and deploy.
During this time, the users will have started using the simple day-to-day workflows like “vacation request”, “expense approval”..
Templates provide a good baseline and enable quicker development cycles as they don’t need to be built from scratch.
They will need a bit of tweaking later on to fit the different specs of each company, but they usually provide enough out-of-the-box functionality to be used as-is (or at least until the main process development is completed).
This means that at the end of a few months, dozens of processes will be in use across the whole organization, instead of just one “killer app” used in one department. The BPM platform has now become a critical corporate environment, the business hub of the organization.
From the vendor’s point-of-view – more deployed workflows means more PS revenue (more workflows to change) and more license revenue (more users using the system)
These are the common process templates:
- Employee Onboarding
- Employee Offboarding
- Employee Review
- Leave of Absence Request
- Vacation Request
- Purchase Request
- Expense Approval
- Billing and Invoicing
- Request for Proposal
- Request for Information
- Request for Information
- New Lead
- New Customer
- New Supplier
- Audit Review
- Change Request
- Generic Approval Cycle
- Helpdesk
- Customer complaints
- Maintenance Problem
Adam Deane 
Leave a Reply