scholarly journals Efficient Semantics-Based Compliance Checking Using LTL Formulae and Unfolding

2013 ◽  
Vol 2013 ◽  
pp. 1-24
Author(s):  
Liang Song ◽  
Jianmin Wang ◽  
Lijie Wen ◽  
Hui Kong
Keyword(s):  
State Space ◽  
Business Process ◽  
Process Model ◽  
Query Language ◽  
Process Models ◽  
State Space Explosion ◽  
Business Process Compliance ◽  
Compliance Checking ◽  
Process Compliance ◽  
Retrieval Language

Business process models are required to be in line with frequently changing regulations, policies, and environments. In the field of intelligent modeling, organisations concern automated business process compliance checking as the manual verification is a time-consuming and inefficient work. There exist two key issues for business process compliance checking. One is the definition of a business process retrieval language that can be employed to capture the compliance rules, the other concerns efficient evaluation of these rules. Traditional syntax-based retrieval approaches cannot deal with various important requirements of compliance checking in practice. Although a retrieval language that is based on semantics can overcome the drawback of syntax-based ones, it suffers from the well-known state space explosion. In this paper, we define a semantics-based process model query language through simplifying a property specification pattern system without affecting its expressiveness. We use this language to capture semantics-based compliance rules and constraints. We also propose a feasible approach in such a way that the compliance checking will not suffer from the state space explosion as much as possible. A tool is implemented to evaluate the efficiency. An experiment conducted on three model collections illustrates that our technology is very efficient.

scholarly journals The Journey to Business Process Compliance

2011 ◽  
pp. 426-454 ◽  
Author(s):  
Guido Governatori ◽  
Shazia Sadiq
Keyword(s):  
Business Process ◽  
Business Processes ◽  
Specific Problem ◽  
Business Partners ◽  
Business Process Compliance ◽  
Industry Standards ◽  
Compliance Checking ◽  
Process Compliance ◽  
Contractual Obligations ◽  
Typical Scenario

It is a typical scenario that many organisations have their business processes specified independently of their business obligations (which includes contractual obligations to business partners, as well as obligations a business has to fulfil against regulations and industry standards). This is because of the lack of guidelines and tools that facilitate derivation of processes from contracts but also because of the traditional mindset of treating contracts separately from business processes. This chapter will provide a solution to one specific problem that arises from this situation, namely the lack of mechanisms to check whether business processes are compliant with business contracts. The chapter begins by defining the space for business process compliance and the eco-system for ensuring that process are compliant. The key point is that compliance is a relationship between two sets of specifications: the specifications for executing a business process and the specifications regulating a business. The central part of the chapter focuses on a logic based formalism for describing both the semantics of normative specifications and the semantics of compliance checking procedures.

scholarly journals Multi-party business process compliance monitoring through IoT-enabled artifacts

2018 ◽  
Vol 73 ◽  
pp. 61-78 ◽  
Author(s):  
Giovanni Meroni ◽  
Luciano Baresi ◽  
Marco Montali ◽  
Pierluigi Plebani
Keyword(s):  
Business Process ◽  
Compliance Monitoring ◽  
Business Process Compliance ◽  
Process Compliance

scholarly journals Business processes exceptions in relation to operational performance

2019 ◽  
Vol 25 (5) ◽  
pp. 908-922 ◽  
Author(s):  
Remco Dijkman ◽  
Oktay Turetken ◽  
Geoffrey Robert van IJzendoorn ◽  
Meint de Vries
Keyword(s):  
Business Process ◽  
Process Model ◽  
Business Processes ◽  
Process Models ◽  
Operational Performance ◽  
Normal Flow ◽  
Throughput Time ◽  
Content Type ◽  
Business Process Models ◽  
Practical Implications

Purpose Business process models describe the way of working in an organization. Typically, business process models distinguish between the normal flow of work and exceptions to that normal flow. However, they often present an idealized view. This means that unexpected exceptions – exceptions that are not modeled in the business process model – can also occur in practice. This has an effect on the efficiency of the organization, because information systems are not developed to handle unexpected exceptions. The purpose of this paper is to study the relation between the occurrence of exceptions and operational performance. Design/methodology/approach The paper does this by analyzing the execution logs of business processes from five organizations, classifying execution paths as normal or exceptional. Subsequently, it analyzes the differences between normal and exceptional paths. Findings The results show that exceptions are related to worse operational performance in terms of a longer throughput time and that unexpected exceptions relate to a stronger increase in throughput time than expected exceptions. Practical implications These findings lead to practical implications on policies that can be followed with respect to exceptions. Most importantly, unexpected exceptions should be avoided by incorporating them into the process – and thus transforming them into expected exceptions – as much as possible. Also, as not all exceptions lead to longer throughput times, continuous improvement should be employed to continuously monitor the occurrence of exceptions and make decisions on their desirability in the process. Originality/value While work exists on analyzing the occurrence of exceptions in business processes, especially in the context of process conformance analysis, to the best of the authors’ knowledge this is the first work that analyzes the possible consequences of such exceptions.

Sign in / Sign up

Export Citation Format

Share Document