BPM plays especially important role in all situations related to regulations and compliance. This is not accidental. Any regulation is a set of requirements and complementary procedures necessary to fulfill these requirements. Therefore, conformance to requirements can and should be expressed in a form of a business model. GDPR is just another standard to prove this common rule together with ISO, HIPPA and many others.
Especially, in case of GDPR one may even say that its implementation literally boils down to BPM and process adjustments. How else one can plan, implement and prove GDPR compliance, if not through process driven system design? It is fairly unlikely that GDPR will cause total replacement of existing digital business platforms. Instead, platforms will be adapted to follow GDPR procedures, in other words, processes.
We may think of GDPR as one of the world's biggest BPM initiates bringing process driven practices into daily routine of every business.
There always exists a discrepancy between a model of business process, however well designed and accurate, and real execution of this process in a business environment. The reason for this gap is an unforeseen depth and hidden details inherent to any real process. Real business model of organization is ultimately unlimited in its depth. Going from highest management levels, it descends to individual departments, client relations, production units, technical code of equipment and controllers etc. In vast majority of cases, it is impossible and senseless to build a complete model covering all and every fine detail of the business. Omitted lower layers of the model create (pseudo) random fluctuations during execution of the model. Real execution paths of a process never follow its model exactly. However, in case of the correct model, we can expect to see that an ensemble of execution paths statistically converges to the model as to its average path over a significant set of observation...
Comments
Post a Comment