Abstract: According to some embodiments, a business user interface page associated with a business service provider may be established. The user interface page may have, for example, at least one in-port to receive data from components and at least one out-port to provide data to components. A mashup component may be embedded within the business user interface page, and may also have at least one out-port to provide data to components. A display of the user interface page to a client may then be facilitated, including the embedded mashup component, wherein the mashup component combines and displays data received from a plurality of external data sources.

Abstract: According to some embodiments, input may be received from a designer via a runtime authoring tool associated with a business service provider user interface page. The designer input defining at least one in-port to receive data from components and at least one out-port to provide data to components. A mashup component may then be embedded within the business user interface page in accordance with the input received from the designer. Moreover, a display of the user interface page to a client may be facilitated, including the embedded mashup component. Further, according to some embodiments the mashup component consumes business context data and combines and displays data received from a plurality of external data sources.

Abstract: A system includes a portal connected to user interface (UI) components, application logic linking the UI components to a repository layer and connectivity layer through an object access layer, and source systems linked to the repository layer and the connectivity layer.

Abstract: In a computer system (100) that launches application services for predetermined roles, a service-to-role assignment is customized in a target table. The user inserts a CD-ROM with master and reference tables, and the system automatically provides the target table. The master table (119) stores a first assignment (112) of application services (S, 151-156) to roles (RO), and stores a second assignment (113) of service attributes (SA), such as language or industry branch, of the application services (S). The reference table (129) stores reference attributes (REA) for each application service (S) in the master table. The service representations for each role (RO) are forwarded from the master table (119) into the target table (149) if service and reference attributes match.

Abstract: A role-based computer system has a first processor with a computer program (100) and has further processors with application systems (Sy1, Sy2, Sy3) and application services (Se). The program generates a start instruction for the further processors to execute the services by consecutively receiving a log-in identification from the user and looking up in a first assignment table (101) for a role (Ro), looking up in a second assignment table (102) to determine logical services (LSe) assigned to the role; and looking up in a second assignment table to determine a pointer (P(Sy/Se)) to the services (Se) that are assigned to the logical service. The pointer has first and second portions to identify the application system (Sy) and the application service (Se), respectively, and becomes part of the start instruction (350).

Abstract: The present invention discloses a method, computer program product and system for adjusting roles in a computer system (100) that launch application services (301-307) by a first user who is assigned to at least one role. A first role (110) calls a second role (150) by reference (111). Both roles comprise representations of applications services (101, 102, 103) and (104, 105). When representations in the second role are modified, for example, application services are added (106, 107), a delta list (112) for the first reference is automatically created to conditionally prevent the first role (110) from referencing to at least some of the modified representations of the second role (150). This is achieved by using a rule database (118) containing rules about application services that are mutually exclusive and checking for conflicts between the representations of the first role and modified, second role. A second user, e.g.

Abstract: A method includes storing a plurality of role data entries on a storage device coupled to a computer system, each role data entry corresponding to an assigned role of at least one of a plurality of individuals, each role corresponding to an enterprise with which the individual is associated and corresponding to a set of resources accessible through the computer system, receiving at the computer a resource request from one of the individuals, determining whether the requested resource is included in the set of accessible resources corresponding to the assigned role of the requesting individual, and selectively permitting access to the requested resource if the resource is determined to be in the set of resources corresponding to the assigned role of the requesting individual.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A method includes providing a single logical physically distributed information system across one or more information systems of at least two enterprises, wherein the enterprises are being combined, and providing a user interface to access the single logical physically distributed information system to execute one or more merger activities of the enterprises, the merger activities comprising a sales-related integration and a management of sales support activities, the sales support activities comprising addressing one or more customer issues for customer retention.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A method for planning a merger of at least two organizations includes human-resource tools, the human-resource tools including a compensation cost assessment tool, a compensation comparison and level mapping tool, and a self-servicing tool for employees and managers, the human-resource tools including one or more user interfaces.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A system for planning a merger of at least two organizations includes at least one of an organizational strategy tool, a strategy management tool, a strategy risk management tool, a strategy portfolio management tool, a strategy planning tool, and one or more software tools presenting a user with at least one of a personalized object, a preferred object, a recently accessed object, and a merger-related object.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A system for planning a restructuring of at least two organizations includes an intranet interface adapted for at least one employee of one of the organizations, an extranet interface adapted for an external restructuring member of at least one of the organizations, and an information repository related to at least one of the organizations, the information repository being accessible by the intranet interface.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A method for managing a corporate restructuring of at least two organizations includes presenting a user interface including information relating to consolidating customer accounts for at least one of the restructuring organizations, and presenting a template in the user interface, the template including a rollout template menu, a pull down window, a list of action items, and a status relating to each action item in the list.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A method includes providing a single logical physically distributed information system across one or more information systems of at least two enterprises, wherein the enterprises are being combined, and providing a user interface to access the single logical physically distributed information system to execute one or more pre-merger activities, merger activities, and post-merger activities, wherein the merger activities comprise procurement realignment.

Abstract: A method for planning a restructuring of at least two organizations includes a first interface adapted to allow a user to plan a project with a resource management capability and a time management capability, a second interface adapted to provide collaborative capabilities to restructuring members to plan the project, and one or more tools adapted to allow a user to exchange restructuring information with a person associated with one of the organizations.

Abstract: A method includes providing a single logical physically distributed information system across one or more information systems of at least two enterprises, wherein the enterprises can be being combined, and providing a user interface to access the single logical information system, wherein the single logical physically distributed information system executes one or more merger activities, pre-merger activities, and post-merger activities, wherein the merger activities comprise organizational restructuring and personnel redeployment.

Abstract: The present invention discloses a method, computer program product and system for adjusting roles in a computer system (100) that launch application services (301-307) by a first user who is assigned to at least one role. A first role (110) calls a second role (150) by reference (111). Both roles comprise representations of applications services (101, 102, 103) and (104, 105). When representations in the second role are modified, for example, application services are added (106, 107), a delta list (112) for the first reference is automatically created to conditionally prevent the first role (110) from referencing to at least some of the modified representations of the second role (150). This is achieved by using a rule database (118) containing rules about application services that are mutually exclusive and checking for conflicts between the representations of the first role and modified, second role. A second user, e.g.

Abstract: A role-based computer system has a first processor with a computer program (100) and has further processors with application systems (Sy1, Sy2, Sy3) and application services (Se). The program generates a start instruction for the further processors to execute the services by consecutively receiving a log-in identification from the user and looking up in a first assignment table (101) for a role (Ro), looking up in a second assignment table (102) to determine logical services (LSe) assigned to the role; and looking up in a second assignment table to determine a pointer (P(Sy/Se)) to the services (Se) that are assigned to the logical service. The pointer has first and second portions to identify the application system (Sy) and the application service (Se), respectively, and becomes part of the start instruction (350).

Abstract: Systems and techniques relating to software for enterprise change, in particular to restructuring processes and tools for one or more organizations. In one general implementation, the technique includes the generation of a single logical information system across one or more information systems of at least two enterprises, wherein the enterprises are combined, and the single logical information system is used to execute restructuring activities. The logical information system facilitates restructuring-related issue management.

Abstract: A system includes a portal connected to user interface (UI) components, application logic linking the UI components to a repository layer and connectivity layer through an object access layer, and source systems linked to the repository layer and the connectivity layer.