Abstract: Techniques for overlaying objects of a software application with other objects allow modification and customization of the application by one or more users in different ways, without storing multiple modified copies of the application. The technique allows configuring the software application to execute using overlaid objects instead of the base objects contained in the software application. In some embodiments, the base objects for the software application and the overlaid objects are stored in a datastore, and a runtime embodiment causes execution of the overlaid objects instead of the base objects.

Abstract: Disclosed is a method, a system and a computer readable medium for additive independent object modification. The method includes determining an association between an independent object modification and a base object of a software application, modifying at least one element of the base object based on the associated independent object modification, and configuring the software application to execute in a computer system using the modified base object.

Abstract: Data is often populated into Configuration Management Databases (CMDBs) from different sources. Because the data can come from a variety of sources, it may have inconsistencies—and may even be incomplete. A Normalization Engine (NE) may be able to automatically clean up the incoming data based on certain rules and knowledge. In one embodiment, the NE takes each Configuration Item (CI) or group of CIs that are to be normalized and applies a rule or a set of rules to see if the data may be cleaned up, and, if so, updates the CI or group of CIs accordingly. In particular, one embodiment may allow for the CI's data to be normalized by doing a look up against a Product Catalog and/or an Alias Catalog. In another embodiment, the NE architecture could be fully extensible, allowing for the creation of custom, rules-based plug-ins by users and/or third parties.

Abstract: Data is often populated into Configuration Management Databases (CMDBs) from different sources. Because the data can come from a variety of sources, it may have inconsistencies—and may even be incomplete. A Normalization Engine (NE) may be able to automatically clean up the incoming data based on certain rules and knowledge. In one embodiment, the NE takes each Configuration Item (CI) or group of CIs that are to be normalized and applies a rule or a set of rules to see if the data may be cleaned up, and, if so, updates the CI or group of CIs accordingly. In particular, one embodiment may allow for the CI's data to be normalized by doing a look up against a Product Catalog and/or an Alias Catalog. In another embodiment, the NE architecture could be fully extensible, allowing for the creation of custom, rules-based plug-ins by users and/or third parties.

Abstract: Disclosed are methods and systems to provide coordinated identification of data items across a plurality of distributed data storage repositories (datastores). In one disclosed embodiment, a single configuration management database (CMDB) controls identification rights for all CIs as they are first identified in a master/slave relationship with all other CMDBs in the distributed environment. In a second embodiment, a plurality of CMDBs divide identification rights based upon coordination identification rules where certain CMDBs are assigned authoritative identification rights for CIs matching the rules of a particular CMDB in the distributed environment. In a third embodiment, one or more of the plurality of CMDBs may also have advisory identification rights for CIs which do not already have an identifiable unique identity and can coordinate with an authoritative CMDB to establish an identity for CIs.

Abstract: Disclosed are methods and systems to automatically integrate work requests from multiple Spoke systems at a centralized Hub system. In one embodiment, a Hub system receives a portion of a work request from a problem tracking system executing in the region (e.g., geographic area or network subnet) of an associated Spoke system. The request comprises enough information for the Hub system to prioritize this work request against other work requests already received from this same Spoke system, other Spoke systems in the same region, or even other Spoke systems from other regions. A Hub user can then be presented with an integrated work queue of requests to service after they have been properly prioritized. The Hub user may be supporting multiple clients in an outsourcing style Information Technology (IT) support model or a call center model. Supported clients can execute on different data center platforms, at the same time.

Abstract: Techniques for overlaying objects of a software application with other objects allow modification and customization of the application by one or more users in different ways, without storing multiple modified copies of the application. The technique allows configuring the software application to execute using overlaid objects instead of the base objects contained in the software application. In some embodiments, the base objects for the software application and the overlaid objects are stored in a datastore, and a runtime embodiment causes execution of the overlaid objects instead of the base objects.

Abstract: Described herein is a method and instrumentation for cleaning up mercury spilled from broken fluorescent light bulbs. The method provides for the safe clean-up of the mercury spilled from four or fewer four-foot bulbs (or their equivalent) without the use of a respirator or other respiratory protection, while avoiding the expense associated with contracting an environmental remediation firm to perform the clean-up.

Abstract: An automated change management method and system has a change tool that associates a first identifier with each request to change the configuration of an Information Technology infrastructure. Tasks are configured to implement the change, and the change tool associates a second identifier with each of the tasks. The change tool sends task instructions to implementation tools to perform the tasks where each of the task instructions includes the first and second identifiers. The change tool receives responses to the task instructions where each response includes the first and second identifiers and an implementation result. The change tool maps/associates each of the implementation results to the associated change request and task based on the first and second identifiers. The associated results can be made available to a user for review, interpretation, etc. and can be used to drive subsequent processing by other task in the change process.

Abstract: A method to reconcile multiple instances of a single computer resource identified by resource discovery operations includes: (1) accessing information describing one or more resources; (2) identifying, via the accessed information, at least one resource that has been detected or discovered by at least two of the discovery operations; and (3) merging attributes associated with the identified resource from each of the at least two discovery operations into a single, reconciled resource object. Illustrative “resources” include, but are not limited to, computer systems, components of computer systems, data storage systems, switches, routers, memory, software applications (e.g., accounting and database applications), operating systems and business services (e.g., order entry or change management and tracking services).