Abstract: Meta-Rules are a special set of business rules whose purpose is to enable business rules selection and subsequent rule invocation by a business rules manager. Contained within a Meta-Rule are business policy and other information that enables the selection of a business rule used by a business application. Meta-rules allow the system to dynamically select and identify specific business rules to be executed within a given business application. By enabling a higher level of abstraction, and relying on rules to resolve specific business rule selection and invocations, Meta-rules further separate the binding of business knowledge and practice from application programming logic. The application programmer is freed from having specific knowledge of the business rule; all that is required is an assertion that a rule is to be used.

Abstract: Generating a transition plan for a computer resource portfolio, representing each resource as a state machine, by generating a transition plan, the transition plan having a set of acts for transitioning states of the resources, to move the computer resource portfolio from a present state, the present state based on an inventory of present computer capabilities, to a future state. The future state is identified based on a difference between a present state and an identified state meeting given performance requirements. The transition plan is optimized to maximize the sum value of the computer resource portfolio values added over the state sequence of the transition.

Abstract: A method of modeling a service-oriented business including identifying a business service to provide, creating its business specification which specifies business requirements for the provided service, the business specification of a service, and service management terms, storing the business specification for the provided service in a service catalog, creating and reviewing its business process model, the business process model providing a sequence of business tasks in the business process, analyzing each of the business tasks to determine which of the business tasks should be accomplished via required service, process modeling each of the business tasks that are not service tasks, storing a process model for each of the business tasks that are not service tasks in a operation model repository, creating a business specification for each required service and storing the business specification for each of the required services in a repository of business specifications of required services.

Abstract: Meta-Rules are a special set of business rules whose purpose is to enable business rules selection and subsequent rule invocation by a business rules manager. Contained within a Meta-Rule are business policy and other information that enables the selection of a business rule used by a business application. Meta-rules allow the system to dynamically select and identify specific business rules to be executed within a given business application. By enabling a higher level of abstraction, and relying on rules to resolve specific business rule selection and invocations, Meta-rules further separate the binding of business knowledge and practice from application programming logic. The application programmer is freed from having specific knowledge of the business rule; all that is required is an assertion that a rule is to be used.

Abstract: Improvements in the creation, maintenance and management of web based information are provided. A development environment conducive to separation of tasks and data, works in combination with the means to present views of changed information for approval to users. Data from file systems and database systems can be combined to create a rich source of material for users, while changes to such material can be effectively controlled and released for production.

Abstract: A method and system are described for using business artifacts to identify elements of a component business model. Artifacts operated upon by the business are first identified, and then used to analyze the business into business operations. This is done by identifying every business activity that acts on an artifact, creating directed graphs for the business activities, and decomposing the directed graphs into sub-graphs, each sub-graph representing a business operation and being annotated by a verb expression, the annotated sub-graph representing a business service. The business services are then clustered into non-overlapping components, using common affinities reflected in the verb expressions, and organized by partitioning into internal and external operations, exposing a business service for each external operation. The components are then clustered into non-overlapping business competencies, and arranged by accountability level.

Abstract: A method and system for enterprise monitoring maps monitor events to elements of a component business model of the enterprise and displays the mapped events using the component business model. Rules are used to determine whether events captured from a monitor source are monitor events. An enterprise monitor metamodel linking monitor artifacts and elements of a component business model is used to annotate monitor events with data from the component business model of the enterprise.

Abstract: A method and system are described for using the structure and relationships between components in a component business model of an enterprise to assign components providing monitoring data to a management component. In response to the monitoring data, the management component executes a business rule invoking a service that alters a behavior of the enterprise. The management component contains data rules limiting the information provided by the assigned components, analysis rules defining the interaction between components, and report rules for consolidating recommendations for altering behavior of the enterprise, including decisions to invest in certain aspects of the business, to reengineer certain processes of the business, and to alter operation of certain aspects of the business.

Abstract: A system and method is described for using a component business model to partition a business into non-overlapping components, and then allocating different components to appropriate organizing strategies, based on attribute values assigned to each component. In the best mode of implementation there are two attributes: whether or not the component differentiates the business within the market place; and whether the component is industry standard or is tailored by the organization. These attributes and their values map the components of the business to a matrix. Based on the combination of attribute values in each cell of the matrix, available organizing strategies are also mapped to the matrix, thereby identifying for each component an appropriate organizing strategy.

Abstract: A method and system is described for an enterprise architecture being viewed through a component business model of an organization, where the artifacts of the enterprise architecture are mapped to corresponding elements of the component business model. A metamodel is used to integrate a model of the enterprise architecture with the component business model. Views of the enterprise architecture are coupled to the layers of a component business model stack.

Abstract: This invention introduces a method, system and computer readable media that enables a computer system or computer networked system to perform enterprise portfolio transition optimization. The invention considers several key factors that are traditionally treated informally. The invention provides a sequential decision model for enterprise portfolio transition management of computer and software resources. Using a finite state Markov Decision process, a mathematical formulation is developed to ensure an optimal enterprise portfolio transition plan, with the objective of balancing expected value and risk, that is solved numerically via an approximate dynamic programming algorithm. The output of the model is a set of recommendations in the form of a transition plan for each of the computer and software resources selected within the enterprise portfolio during each phase of a planning horizon.

Abstract: A method for managing a business. At least one relationship is determined between N business components (B1, B2, . . . , BN) and respective N costs (C1, C2, . . . , CN) and respective N values (V1, V2, . . . , VN) pertaining to the N business components. The N business components are a subset of M business components (B1, B2, . . . , BM) of a Component Based Model (CBM) of the M business components subject to M?2 and N?M. Determining the at least one relationship includes relating business components of the CBM with an Information Technology (IT) model of an IT system. The IT model includes abstract IT structures, virtual IT structures, real IT structures, or combinations thereof.

Abstract: Meta-Rules are a special set of business rules whose purpose is to enable business rules selection and subsequent rule invocation by a business rules manager. Contained within a Meta-Rule are business policy and other information that enables the selection of a business rule used by a business application. Meta-rules allow the system to dynamically select and identify specific business rules to be executed within a given business application. By enabling a higher level of abstraction, and relying on rules to resolve specific business rule selection and invocations, Meta-rules further separate the binding of business knowledge and practice from application programming logic. The application programmer is freed from having specific knowledge of the business rule; all that is required is an assertion that a rule is to be used.

Abstract: A system and method for supporting Product Lifecycle Management over a distributed service network topology that connects a hierarchy of functional domains, each domain having a service ontology and one or more service composition schemas defined by the service ontology. Each service composition schema models a business process in its domain. Descriptions of services provided to each domain are published to a service repository by providers of the services, in conformity with one of the service composition schemas. There is a business process proxy provided by the service provider for each service description, which encapsulates for public access the internal processes of the service provider. The invention makes use of an event messaging protocol that enables service collaboration and ad-hoc workflow composition. Each business process is implemented by an ad-hoc workflow comprised of one or more tasks connected by one or more business rules.