Anil Nigam

Business artifacts: An approach to operational specification

Any business, no matter what physical goods or services it produces, relies on business records. It needs to record details of what it produces in terms of concrete information. Business artifacts are a mechanism to record this information in units that are concrete, identifiable, self-describing, and indivisible. We developed the concept of artifacts, or semantic objects, in the context of a technique for constructing formal yet intuitive operational descriptions of a business. This technique, called OpS (Operational Specification), was developed over the course of many business-transformation and business-process-integration engagements for use in IBMs internal processes as well as for use with customers. Business artifacts (or business records) are the basis for the factorization of knowledge that enables the OpS technique. In this paper we present a comprehensive discussion of business artifacts--what they are, how they are represented, and the role they play in operational business modeling. Unlike the more familiar and popular concept of business objects, business artifacts are pure instances rather than instances of a taxonomy of types. Consequently, the key operation on business artifacts is recognition rather than classification.

Business artifacts with guard-stage-milestone lifecycles: managing artifact interactions with conditions and events

A promising approach to managing business operations is based on business artifacts, a.k.a. business entities (with lifecycles). 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. An artifact type includes both an information model that captures all of the business-relevant data about entities of that type, and a lifecycle model, that specifies the possible ways an entity of that type might progress through the business. Two recent papers have introduced and studied the Guard-Stage-Milestone (GSM) meta-model for artifact lifecycles. GSM lifecycles are substantially more declarative than the finite state machine variants studied in most previous work, and support hierarchy and parallelism within a single artifact instance. This paper presents the formal operational semantics of GSM, with an emphasis on how interaction between artifact instances is supported. Such interactions are supported both through testing of conditions against the artifact instances, and through events stemming from changes in artifact instances. Building on a previous result for the single artifact instance case, a key result here shows the equivalence of three different formulations of the GSM semantics for artifact instance interaction. One formulation is based on incremental application of ECA-like rules, one is based on two mathematical properties, and one is based on the use of first-order logic formulas.

Introducing the guard-stage-milestone approach for specifying business entity lifecycles

A promising approach to managing business operations is based on business entities with lifecycles (BELs) (a.k.a. business artifacts), i.e., key conceptual entities that are central to guiding the operations of a business, and whose content changes as they move through those operations. A BEL type includes both an information model that captures, in either materialized or virtual form, all of the business-relevant data about entities of that type, and a lifecycle model, that specifies the possible ways an entity of that type might progress through the business by responding to events and invoking services, including human activities. Most previous work on BELs has focused on the use of lifecycle models based on variants of finite state machines. This paper introduces the Guard-Stage-Milestone (GSM) meta-model for lifecycles, which is an evolution of the previous work on BELs. GSM lifecycles are substantially more declarative than the finite state machine variants, and support hierarchy and parallelism within a single entity instance. The GSM operational semantics are based on a form of Event-Condition-Action (ECA) rules, and provide a basis for formal verification and reasoning. This paper provides an informal, preliminary introduction to the GSM approach, and briefly overviews selected research directions.

Qualitative physics using dimensional analysis

Abstract In this paper we use dimensional analysis as a method for solving problems in qualitative physics. We pose and solve some of the qualitative reasoning problems discussed in the literature, in the context of devices such as the pressure regulator and the heat exchanger. Using dimensional analysis, such devices or systems can be reasoned about without explicit knowledge of the physical laws that govern the operation of such devices. Instead, the method requires knowledge of the relevant physical variables and their dimensional representation. Our main thesis can be stated as follows: the dimensional representations of physical variables encode a significant amount of physical knowledge; dimensionless numbers provide a representation of the physical processes, and they can be obtained without direct, explicit knowledge of the underlying laws of physics. Then, a variety of partial derivatives can be computed and used to characterize the behavior of the system. These partials, along with some simple heuristics, can be used to reason qualitatively about the behavior of devices and systems. Here we present the techniques for dimensional analysis and develop the representation and reasoning machinery.

Artifact-Based Transformation of IBM Global Financing

IBM Global Financing (IGF) is transforming its business using the Business Artifact Method, an innovative business process modeling technique that identifies key business artifacts and traces their life cycles as they are processed by the business. IGF is a complex, global business operation with many business design challenges. The Business Artifact Method is a fundamental shift in how to conceptualize, design and implement business operations. The Business Artifact Method was extended to solve the problem of designing a global standard for a complex, end-to-end process while supporting local geographic variations. Prior to employing the Business Artifact method, process decomposition, Lean and Six Sigma methods were each employed on different parts of the financing operation. Although they provided critical input to the final operational model, they proved insufficient for designing a complete, integrated, standard operation. The artifact method resulted in a business operations model that was at the right level of granularity for the problem at hand. A fully functional rapid prototype was created early in the engagement, which facilitated an improved understanding of the redesigned operations model. The resulting business operations model is being used as the basis for all aspects of business transformation in IBM Global Financing.

Declarative business artifact centric modeling of decision and knowledge intensive business processes

In this paper we address the problem of modeling collaborative decision and knowledge intensive business processes (sometimes referred to as Decision Intensive Processes, or DIP processes). DIP processes assist users in performing decision intensive tasks, and provide users with a guidance relevant to process execution context. DIP processes are by nature collaborative, data-driven, need to support various kinds of flexibility at design and run time, and need to integrate with external services and information sources. Such a combination presents significant challenges for contemporary business processes technologies. We present a solution based on a business artifacts paradigm (a.k.a. business entities with lifecycles) using a Guard-Stage-Milestone (GSM) model for declarative lifecycles specification. We introduce a CoreControl -- MicroProcess process design pattern, which allows a natural blending of a business functional process structure (usual for most business processes), with a decision & knowledge driven structure providing domain specific decision guidance to users. The proposed design pattern along with the declarative GSM BA approach provide suitable design primitives for DIP process, as demonstrated on a real problem from the supply chain solutions enablement domain.

Core business architecture for a service-oriented enterprise

The business architecture of a service-oriented enterprise can be adequately represented through five main architectural domains: business value, structure, behavior, policy, and performance. In this paper we focus on the core business architecture, the set of essential elements in each of the five domains, and the interrelationships among these elements. The business architecture described in this paper identifies the key elements required for business reasoning and for its application to business transformation through service-oriented solutions. A business scenario involving a fictional company in the apparel business illustrates the concepts presented here.

Using a model-driven transformational approach and service-oriented architecture for service delivery management

IT (information technology) service providers often assume that efficient and effective service delivery can be achieved by migrating to a standard set of tools. This assumption is true only if the service provider has monolithic control over the scope and architecture of the customer environment. The trend, however, is toward selective outsourcing, customer control over the architecture of IT solutions, and retention of legacy tools. Target environments are extremely heterogeneous, and the ability of the service provider to control them is diminishing. Consequently, there is a need for a new approach to IT service workflow automation and a new generation of service-delivery management systems that support heterogeneity and collaboration. This paper introduces a new approach to automating complex and variable workflows, applies this approach to IT service delivery management (SDM), presents an SDM architecture based on this approach, and discusses an SDM implementation driven by this architecture. Our implementation architecture leverages service-oriented architecture (SOA) principles by defining loosely coupled service components and a service fulfillment pattern that dynamically integrates them. We discuss the modeling of performance metrics for service delivery and describe how the monitoring and management of key performance indicators (KPIs) are supported as an integral part of our SDM platform.

Realizing business components, business operations and business services

Business components are founded on the notion that complex business organizations can be decomposed into discrete into self-functioning logical units. Decomposing an enterprise into business components facilitates a logical understanding of business design and can be leveraged to provide finer levels of detailed analysis on how it operates. This involves a range of improvements, from evaluating and validating business organization structures, extending to ways of expressing dynamic relationships among business components, and finally, influencing the IT application base and infrastructure that realize the business intent

NON-VON's performance on certain database benchmarks

In a paper by P.B. Hawthorn and D.J. DeWitt (1982) the projected performance of several proposed database machines was examined for three relational database queries. The present authors investigate the performance of a massively parallel machine called NON-VON for the same queries under comparable assumptions. In the case of simple queries, a NON-VON machine of comparable size to those considered by Hawthorn and DeWitt is found to be somewhat faster than the fastest machines examined in their study; for a more complex database operation, NON-VON is shown to be five to ten times faster than the fastest of these machines.