BPM for All

Although popular and widely discussed recently, RPA by definition is very limited technology , not a panacea on IT problems existing in a company. In this capacity, RPA is senseless and dangerous when applied alone. Technically, RPA is a fragile collection of scripts , which are difficult to impossible to adapt on even slightest change in business environment. An intent to rely widely on RPA is equal to an attempt to conserve indefinitely a status-quo with legacy IT systems. Evidently, it is only a matter of time when such a crippled construct will collapse and bury business. However, it does not diminish an important role of RPA as a facilitator and accelerator of digital transformation through robust instant automation of routine legacy procedures. It should serve as a proof of concept in discovery of business transformation potential in an organization. To reap all benefits of this automated discovery, it is essential to explore RPA only in the context of a business model where RPA

Data is an indispensable part of any business process. It is simply impossible to imagine a process, which operates without certain input as a starting condition and without an output representing its results. In one or another form, these inputs and outputs are always associated with certain business data. A process is a flow (in business terms, a workflow) transforming the data. On another hand, data is amorphous and shapeless without a process behind. Data is always a result of certain process and always have a reservation of consumption by one or another process sooner or later. Rarely somebody stores the data, especially, business data, entirely without an intent for subsequent usage. Business process is a fundamental foundation, which shapes the data and gives it a business sense. Data with an undefined or lost business context become a silos. Synthesis of the data and its associated processes in a business model is the cornerstone for consistent storage of the data and its effe