Abstract: A system gathers real-time data about an enterprise over a network. A user device displays a dashboard showing a component business model map, a heat map, key performance indicators for components, key performance indicators for the enterprise, and gradients. The business is enhanced by making investments and changes to those operations having large gradients.

Abstract: A system creates and maintains an industry business architecture model (IBAM) over a network. The IBAM has a component business model, process model, service model, and information model. It also may include a reference architecture, demos and other knowledge assets, and collateral.

Abstract: A system and dashboard are provided for managing business performance. Key performance indicators developed for a component business model map are computed and displayed along with the map in real time. A user may select a corresponding key performance indicator to display a heat map of components on the dashboard.

Abstract: A system creates and maintains an industry business architecture model over a network. The system defines specific levels of maturity for the model. Associations, relationships, and linkages between content elements are also determined. From these, a specific level of aggregate maturity is defined according to an algorithm.

Abstract: Security levels are assigned to a shared component. A workflow manager receives a workflow request that corresponds to a plurality of workflow steps. For each workflow step, the workflow manager determines whether the workflow step uses a shared component or an unshared component for execution. If the workflow step uses a shared component, the workflow manager invokes the step, and stores the step and its corresponding security level in a security tracking table. When the workflow manager encounters a shared component, the workflow manager uses the security tracking table entries in order to determine a security level to assign the shared component. The workflow manager assigns the determined security level to the shared component, and invokes the shared component to execute the corresponding process step.

Abstract: A business consulting company performs an assessment of a client business enterprise. The assessment includes use of a computer implemented tool for performing business component modeling techniques for creating a heat map. The heat map is used with the tool to form a domain decomposition, form a goal-service modeling structure, and perform an existing asset analysis based to linkages to the heat map. The assessment is delivered to the client company. A service oriented architecture, SOA, solution plan based on the assessment may also be delivered. The consulting company may implement the SOA plan for the client.

Abstract: A business enterprise is assessed by a consultant using a computer implemented tool for practicing component business modeling techniques. The tool builds a map of components, filters the map to form a heat map and identifies collaborations. Key performance indicators are evaluated.

Abstract: An assessment of a business is performed using a computer implemented tool to provide a strategy model, an operating model, and an IT model. The assessment is performed by a services providing company for a client company. The assessment is used to create a SOA solution for the business. The services providing company may also implement the SOA solution for the business.

Abstract: A method, system, and computer-readable medium for utilizing the design centers, assembly line and job shops of a global delivery network across multiple software factories are presented. A work packet is examined to determine if it is authorized to be sub-contracted out to a different design center, assembly line or job shop than the design center/assembly line/job shop that have primary responsibility for the work packet. If the work packet is authorized to be sub-contracted out, then the work packet is reassigned to a different pre-qualified design center/assembly line/job shop.

Abstract: Maintaining functionality during component failures is presented. During application registration, a recovery engine generates a recovery plan for the application. The recovery plan includes recovery actions that correspond to each component that the application intends to access. When an application encounters an unavailable component, the recovery engine provides a recovery action to the application which instructs the application how to proceed, such as accessing a backup component. The recovery engine tracks unavailable components and, when a subsequent application registers that intends to use an unavailable component, the recovery engine provides the subsequent application a recovery action, instructing the subsequent application how to proceed.

Abstract: The method and system uses the component business model as a framework for locating business activities. Business value drivers are identified, related in an influence model, and structured into a prioritized driver tree. The driver tree is used to determine the relative contributions of leaf drivers to the overall value of the business. Business activities contributing to the leaf drivers are then identified, and the relative contributions of the leaf drivers are allocated to the business activities and then rolled up to the components for display as a heat map overlay on a component map.

Abstract: Security levels are assigned to a shared component. A workflow manager receives a workflow request that corresponds to a plurality of workflow steps. For each workflow step, the workflow manager determines whether the workflow step uses a shared component or an unshared component for execution. If the workflow step uses a shared component, the workflow manager invokes the step, and stores the step and its corresponding security level in a security tracking table. When the workflow manager encounters a shared component, the workflow manager uses the security tracking table entries in order to determine a security level to assign the shared component. The workflow manager assigns the determined security level to the shared component, and invokes the shared component to execute the corresponding process step.

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 are described for using a Component Business Model (CBM) to transform a business. A CBM map is used to identify components that collaborate to provide a specified capability, and a repository supporting the CBM map is filtered to provide a view of the identified components that highlights how they collaborate. The view is used to identify component features contributing to the specified capability. The specified capability is then enhanced by a transformation strategy that includes re-engineering particular components, identifying a pattern characterizing the collaboration between components and adding a component to perform the collaborative pattern, and/or adding an additional feature to the collaboration and adding component to perform the additional feature. The CBM repository provides exemplar best practices that can be adapted for use in a re-engineered component.

Abstract: Assigning security levels to a shared component is presented. A workflow manager receives a workflow request that corresponds to a plurality of workflow steps. For each workflow step, the workflow manager determines whether the workflow step uses a shared component or an unshared component for execution. If the workflow step uses a shared component, the workflow manager invokes the step, and stores the step and its corresponding security level in a security tracking table. When the workflow manager encounters a shared component, the workflow manager uses the security tracking table entries in order to determine a security level to assign the shared component. The workflow manager assigns the determined security level to the shared component, and invokes the shared component to execute the corresponding process step.

Abstract: A system and method for maintaining functionality during component failures is presented. During application registration, a recovery engine generates a recovery plan for the application. The recovery plan includes recovery actions that correspond to each component that the application intends to access. When an application encounters an unavailable component, the recovery engine provides a recovery action to the application which instructs the application how to proceed, such as accessing a backup component. The recovery engine tracks unavailable components and, when a subsequent application registers that intends to use an unavailable component, the recovery engine provides the subsequent application a recovery action, instructing the subsequent application how to proceed.

Abstract: A system and method for maintaining functionality during component failures is presented. During application registration, a recovery engine generates a recovery plan for the application. The recovery plan includes recovery actions that correspond to each component that the application intends to access. When an application encounters an unavailable component, the recovery engine provides a recovery action to the application which instructs the application how to proceed, such as accessing a backup component. The recovery engine tracks unavailable components and, when a subsequent application registers that intends to use an unavailable component, the recovery engine provides the subsequent application a recovery action, instructing the subsequent application how to proceed.

Abstract: A system and method are described for using a Component Business Model (CBM) to transform a business. A CBM map is used to identify components that collaborate to provide a specified capability, and a repository supporting the CBM map is filtered to provide a view of the identified components that highlights how they collaborate. The view is used to identify component features contributing to the specified capability. The specified capability is then enhanced by a transformation strategy that includes re-engineering particular components, identifying a pattern characterizing the collaboration between components and adding a component to perform the collaborative pattern, and/or adding an additional feature to the collaboration and adding component to perform the additional feature. The CBM repository provides exemplar best practices that can be adapted for use in a re-engineered component.

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.