Learn More
A promising approach to managing business operations is based on business arti-facts, a.k.a. business entities (with lifecycles) [8, 6]. These are key conceptual entities that are central to guiding the operations of a business, and whose content changes as they move through those operations. A business artifact type is modeled using (a) an information(More)
The business artifact (a.k.a. business entity) approach to modeling and implementing business operations and processes is based on a holistic marriage of data and process and enables a factoring of business operations based on key business-relevant conceptual entities. The recently introduced Guard-Stage-Milestone (GSM) artifact meta-model provides a(More)
An important omission in current development practice for business process (or workflow) management systems is modeling of data & access for a business process, including relationship of the process data and the persistent data in the underlying enterprise database(s). This paper develops and studies a new approach to modeling data for business(More)
In most business process management (BPM) systems, the interleav-ing nature of data management and business process (BP) execution makes it hard for providing " Business-Process-as-a-Service " (BPaaS) due to the enormous effort required on maintaining both the engines as well as the data for the clients. In this paper we formulate a concept of a self-guided(More)
This paper describes the development of a patrol robot for the detection of equipments fault inside an electric power substation. The robot, carrying an infrared thermograph, automatically moves around the substation and positions for collecting images of possible critical points. It is fully featured with autonomous navigation, autonomous battery charging(More)
In most BPM systems (a.k.a. workflow systems), the data for process execution is scattered across databases for enterprise, auxiliary local data stores within the BPM systems, and even file systems (e.g., specification of process models). The interleaving nature of data management and BP execution and the lack of a coherent conceptual data model for(More)
Business processes (BPs) can be designed using a variety of model-ing languages and executed in different systems. In most BPM applications, the semantics of BPs needed for runtime management is often scattered across BP models, execution engines, and auxiliary stores of workflow systems. The inability to capture such semantics in BP models is the root(More)
The business artifact approach to modeling business processes and web service orchestration is gaining wide attention because it enables a holistic marriage of data and process, that in turn supports an intuitive, top-down view of processes, rich flexibility, and verification in the presence of data. The Guard-Stage-Milestone (GSM) variant of artifacts(More)