Abstract
An object-centric behavioral constraint (OCBC) model provides an integrated view on entities handled in a process-oriented information system. It defines behavioral constraints between activities operating on data objects and cardinality constraints for relations over activities and objects. Existing techniques for OCBC conformance checking evaluate conditions from the model on an event log. As such, conformance cannot be evaluated directly over the relational databases that typically store the event data. Instead, log construction is required, which induces computational overhead and decouples data management and process analysis. In this paper, we show how to incorporate OCBC conformance checking directly within relational database systems. To this end, we introduce conformance queries for two representations of process data that differ in how they capture the relationships between events and objects, i.e., explicitly by dedicated tables or implicitly through foreign keys. Moreover, we present strategies for continuous conformance monitoring under database updates. We demonstrate the feasibility of our approach using event data generated based on the TPC-H benchmark.