Abstract: Systems, methods, and other embodiments associated with software identifier based correlation are described. One example system includes an identifier data store to store a first identifier that uniquely identifies a discovered instance of a software title installed in an enterprise. The first identifier is discoverable from the discovered instance and may be provided by a discovery logic. The second identifier identifies a known instance of a software title associated with the enterprise and is provided from an enterprise resource planning (ERP) data store by an ERP logic. The example system may also include a correlation logic to identify a correlation between the discovered instance and the known instance based on a relationship between the identifiers. The example system may also include an update logic to selectively update a value in the ERP data store based on the correlation.

Abstract: This disclosure describes, generally, methods and systems for providing consolidated self service IT asset management. The method includes displaying, on a display device of an IT asset management system, an IT asset management user interface (UI), logging in, by an IT assets custodian, to the IT assets management UI, and displaying, at the IT assets management UI, an aggregated view of all IT assets assigned to the IT asset custodian. The aggregated view of the IT assets is generated from a plurality of IT asset assignment sources. The method further includes providing, the IT asset custodian with the ability to management the assigned IT assets and accurately account for the asset according to its actual use.

Abstract: A web service for automatically determining accounting entries that are affected by the deletion of a journal, formulating reverse accounting entries, and sending the reverse entries back to the source system is described. The service can use transaction identification keys to map and track which accounting entries are affected by the deletion of the journal. The web service can use extensible markup language (XML) among other formats.

Abstract: A method of estimating development resources in a feature development cycle may include receiving a selection of a feature and receiving a feature category value. The feature may be associated with a feature category. The method may also include determining one or more tasks associated with the feature category and assigning rating levels to each of the one or more tasks. The method may additionally include computing a task resource estimate for each of the one or more tasks using the corresponding rating levels. The method may further include computing a feature resource estimate for the feature using each task resource estimate and the feature category value.

Abstract: A method of estimating development resources in a feature development cycle may include receiving a selection of a feature and receiving a feature category value. The feature may be associated with a feature category. The method may also include determining one or more tasks associated with the feature category and assigning rating levels to each of the one or more tasks. The method may additionally include computing a task resource estimate for each of the one or more tasks using the corresponding rating levels. The method may further include computing a feature resource estimate for the feature using each task resource estimate and the feature category value.

Abstract: Discrepancies in two sets of asset data for an organization are identified and automatically reconciled. One set of asset data may be compiled using automatic physical discovery software while the other set is from a financial system of the organization. Automatic reconciliation is performed according to user-configurable rules and corresponding user-configurable actions.

Abstract: A web-service for validating or invalidating accounts from a general ledger (GL) chart of accounts is described. Upon a request from an application for whether an account value corresponding to a department and a product is valid, the service indicates whether the combination of account value/department/product is valid for the chart of accounts. The system can be extensible markup language (XML)-based and can indicate validity down to the line level of a request.

Abstract: Software device groups allow owners and administrators to be defined for various intelligent devices, instead of tracking by primary user. A software license compliance management system obtains discovery information for these devices to determine software installed or active on these devices. The management system also obtains the number of licenses for each software package and determines whether the software is in compliance, or if the number of instances exceeds the number of licenses. This determination is flexible and can handle various license types, such as per user, per device, and per processor. For any exception, the group owner is informed and then can re-allocate licenses, purchase additional licenses, or request the uninstalling of a software instance(s). Device groups also can include sub-groups with sub-group owners responsible for handling any exception in that sub-group.

Abstract: Asset data is loaded or entered into an asset management system using a Web service or a manual load, or both. The asset data may be discovered using a third-party asset discovery application. As a first loading option, an inbound asynchronous Web service is used to process the discovered data. As a second loading option, exposed tables are used for loading discovered data and processing through a run control. These entry points provide for additional data validation and error handling of invalid data. They provide ways for data to enter the asset management system and can also streamline the data integration, the reconciliation processes, and additionally automatically address or fix specific exceptions.

Abstract: Discrepancies in two sets of asset data for an organization are identified and automatically reconciled. One set of asset data may be compiled using automatic physical discovery software while the other set is from a financial system of the organization. Automatic reconciliation is performed according to user-configurable rules and corresponding user-configurable actions.

Abstract: Discrepancies in two sets of asset data for an organization are identified and automatically reconciled. One set of asset data may be compiled using automatic physical discovery software while the other set is from a financial system of the organization. Automatic reconciliation is performed according to user-configurable rules and corresponding user-configurable actions.

Abstract: A web service for automatically determining accounting entries that are affected by the deletion of a journal, formulating reverse accounting entries, and sending the reverse entries back to the source system is described. The service can use transaction identification keys to map and track which accounting entries are affected by the deletion of the journal. The web service can use extensible markup language (XML) among other formats.

Abstract: A reconciliation process identifying financial assets in a financial system that do not also exist in the real world, such as is indicated in a discovery system, generates a list of exceptions that can be examined by type of exception. The list of exceptions also includes aggregate financial impact information for the exceptions, such as aggregate cost, fair market value, and net book value. An interface allows a user to view the financial impact information and better decide how to handle the assets corresponding to the exceptions, such as by retiring at least some of the assets, routing some of the exceptions to another user better able to handle the exceptions, or storing the list so that an investigation can be done into at least some of the assets. The financial impact information becomes particularly critical near quarter-end and year-end, as any material impact to the books requires timely disclosure.

Abstract: This disclosure describes, generally, methods and systems for providing consolidated self service IT asset management. The method includes displaying, on a display device of an IT asset management system, an IT asset management user interface (UI), logging in, by an IT assets custodian, to the IT assets management UI, and displaying, at the IT assets management UI, an aggregated view of all IT assets assigned to the IT asset custodian. The aggregated view of the IT assets is generated from a plurality of IT asset assignment sources. The method further includes providing, the IT asset custodian with the ability to management the assigned IT assets and accurately account for the asset according to its actual use.

Abstract: A web-service for validating or invalidating accounts from a general ledger (GL) chart of accounts is described. Upon a request from an application for whether an account value corresponding to a department and a product is valid, the service indicates whether the combination of account value/department/product is valid for the chart of accounts. The system can be extensible markup language (XML)-based and can indicate validity down to the line level of a request.

Abstract: Systems, methods, and other embodiments associated with software identifier based correlation are described. One example system includes an identifier data store to store a first identifier that uniquely identifies a discovered instance of a software title installed in an enterprise. The first identifier is discoverable from the discovered instance and may be provided by a discovery logic. The second identifier identifies a known instance of a software title associated with the enterprise and is provided from an enterprise resource planning (ERP) data store by an ERP logic. The example system may also include a correlation logic to identify a correlation between the discovered instance and the known instance based on a relationship between the identifiers. The example system may also include an update logic to selectively update a value in the ERP data store based on the correlation.

Abstract: A reconciliation process identifying financial assets in a financial system that do not also exist in the real world, such as is indicated in a discovery system, generates a list of exceptions that can be examined by type of exception. The list of exceptions also includes aggregate financial impact information for the exceptions, such as aggregate cost, fair market value, and net book value. An interface allows a user to view the financial impact information and better decide how to handle the assets corresponding to the exceptions, such as by retiring at least some of the assets, routing some of the exceptions to another user better able to handle the exceptions, or storing the list so that an investigation can be done into at least some of the assets. The financial impact information becomes particularly critical near quarter-end and year-end, as any material impact to the books requires timely disclosure.

Abstract: Discrepancies between two sets of asset information for an organization are identified and reconciled before saving to a database. One set of asset information may be compiled using automatic physical discovery software while the other set is from a financial system of the organization. After discrepancies are identified, the user may review the differences and make changes before saving. The process may be performed in real time or in batch.

Abstract: Data that describes asset attributes is stored in an asset information repository. One of the attributes corresponds to assets' financial application defined location. A network device is detected that links the assets to a network. Device identifiers, through which the assets link with the network, are identified. The device identifiers are mapped to a physical location associated with the network device. The physical location is used to derive a financial location, which is compared to the financial location defined for the asset by a financial system. Mismatches may be identified and reconciled.

Abstract: Software device groups allow owners and administrators to be defined for various intelligent devices, instead of tracking by primary user. A software license compliance management system obtains discovery information for these devices to determine software installed or active on these devices. The management system also obtains the number of licenses for each software package and determines whether the software is in compliance, or if the number of instances exceeds the number of licenses. This determination is flexible and can handle various license types, such as per user, per device, and per processor. For any exception, the group owner is informed and then can re-allocate licenses, purchase additional licenses, or request the uninstalling of a software instance(s). Device groups also can include sub-groups with sub-group owners responsible for handling any exception in that sub-group.