Business process automation
|
Investigation of potential copyright issue</font-size> | |
| If you have just labeled this page as a potential copyright issue, please follow the instructions for filing at the bottom of the box. | |
 The previous content of this page or section has been identified as posing a potential copyright issue, as a copy or modification of the text from the source(s) below, and is now listed on Wikipedia:Copyright problems (listing): Unless the copyright status of the text on this page is clarified, the problematic text or the entire page may be deleted one week after the time of its listing. | |
| Can you help resolve this issue?
If you hold the copyright to this text, you can license it in a manner that allows its use on Wikipedia. Click "Show" to see how.
To demonstrate that this text is in the public domain, or is already under a license suitable for Wikipedia, click "Show".
Explain this on this article's discussion page, with reference to evidence. Wikipedia:Public domain and Wikipedia:Compatibly licensed may assist in determining the status. Otherwise, you may write a new article without copyright-infringing material. Click "Show" to read where and how.
Your rewrite should be placed on this page, where it will be available for an administrator or clerk to review it at the end of the listing period. Follow this link to create the temporary subpage.
| |
About importing text to Wikipedia
|
Instructions for filing
If you have tagged the article for investigation, please complete the following steps:
|
Extension of existing IT systems
As most IT systems are inherently automation engines in themselves, a valid option is to extend their functionality to enable the desired automation, creating customized linkages between the disparate application systems where needed. This approach means that the automation can be tailored specifically to the exact environment of the organization; on the down-side, it can be time-consuming to find the necessary skills either internally or in the marketplace.
The boundaries of the concept end with the boundaries of the vision. If vision does not have boundaries the concept does not have boundaries.
Purchase of a specialist BPA tool
Specialist companies are now bringing toolsets to market which are purpose-built for the function of BPA. These companies tend to focus on different industry sectors but their underlying approach tends to be similar in that they will attempt to provide the shortest route to automation by exploiting the user interface layer rather than going deeply into the application code or databases sitting behind them. They also simplify their own interface to the extent that these tools can be used directly by non-technically qualified staff. The main advantage of these toolsets is therefore their speed of deployment, the drawback is that it brings yet another IT supplier to the organization.
Purchase of a Business Process Management solution with BPA extensions
The next section explains that a Business Process Management system is quite different from BPA. However, it is possible to build automation on the back of a BPM implementation. The actual tools to achieve this vary, from writing custom application code to using specialist BPA tools, as described above. The advantages and disadvantages of this approach are inextricably linked – the BPM implementation provides an architecture for all processes in the business to be mapped, but this in itself delays the automation of individual processes and so benefits may be lost in the meantime.
Business Process Automation (BPA) v. Business Process Engineering (BPE) v. Business Process Management (BPM)
An area of discussion exists as to whether BPA is a distinct field of activity in its own right or merely a subset of a wider activity. Given the similarity in terminology it is not surprising most casual observers would believe them to be closely related if not identical. However, to experts in these areas they carry very distinct meanings, even if they are ultimately complementary concepts. To explain this further it is necessary to define the scope of each activity:
The BPE rationale is that before any process can be automated, it is necessary to define (often at a very strategic level or enterprise-wide) all of the business processes running inside an organisation. From this the processes can be re-defined and where necessary optimised, including automation.
BPM practice asserts that before any process can be automated, it is necessary to define all of the business processes running inside the domain of endeavour. From this the processes can be re-defined and where necessary optimised, including automation.
The BPA approach states that until a process is automated, there is no real value in analysing and defining it, and that the cycle of business change is so rapid there simply isn’t time to define every process before choosing which ones to address with automation, and that delivering immediate benefits creates more value.
BPE is an approach which has ceased to be of value due to the utopian nature of the practice. Process improvement methodologies such as Lean manufacturing and Six Sigma appear to align well with the BPM and BPA view of the world, as they constantly look for incremental opportunities to make processes more efficient and reduce defects, however these methodologies can also be used downstream of a BPM deployment.
See also
- Business-driven development (BDD)
- Business process management (BPM)
- Business Process Modeling Notation
- Business process reengineering
- Comparison of business integration software
- Job Scheduling
- Real Time Enterprise (RTE)
- Run Book Automation (RBA)
- Workflow