Abstract: A system described herein may identify a chaincode record recorded to a blockchain, and may output chaincode discovery information to a chaincode discovery system. A client device may receive the chaincode discovery information from the chaincode discovery system, and may output a request to invoke the chaincode. The system may obtain verification, from the chaincode discovery system, that the client device is authorized to invoke the chaincode, and may instruct a node that maintains the blockchain to execute the chaincode. The system may receive output values resulting from executing the chaincode and may output, to the client device, the output values resulting from executing the chaincode.

Abstract: A system described herein may receive a cross-ledger recordation request that includes an information payload, an indication of a target distributed ledger to which the information payload should be recorded, and an indication of a second distributed ledger to which a reference that refers to the first distributed ledger should be recorded. The system may provide the information payload to a second system that implements the first distributed ledger. The system may determine that at least a portion of the information payload has been recorded to the first distributed ledger based on providing the information payload to the second system that implements the first distributed ledger. Based on determining that at least the portion of the information payload has been recorded to the second distributed ledger, the system may record the reference, that refers to the first distributed ledger, to the second distributed ledger.

Abstract: A system may receive a request to migrate a first distributed ledger, maintained by a first distributed ledger management system, to a second distributed ledger management system, and may generate first verification information based on information recorded to the first distributed ledger. The system may instruct the second distributed ledger management system to establish a second distributed ledger, such that the second distributed ledger management system maintains the second distributed ledger. The system may also instruct the second distributed ledger management system to record the information, recorded to the first distributed ledger, to the second distributed ledger. The system may generate second verification information based on the information recorded to the second distributed ledger, and verify that the first distributed ledger has been migrated to the second distributed ledger management system by comparing the first verification information to the second verification information.

Abstract: A system described herein may receive a distributed ledger creation request that specifies a quantity of nodes. The system may provision a plurality of sets of hardware resources to implement a set of nodes which includes the requested quantity of nodes. Provisioning the plurality of sets of hardware resources may include generating communication information associated with each node of the set of nodes. The system may instruct at least one node, of the set of nodes, to establish a distributed ledger. The at least one node may communicate with one or more other nodes of the set of nodes to establish the distributed ledger. The system may output, in response to the distributed ledger creation request, communication information associated with one or more nodes of the plurality of nodes. The communication information may be used to interact with the established distributed ledger.

Abstract: A system described herein may generate a group of distributed ledgers that are each associated with a respective set of ledger parameters, receive a data item that is associated with a set of attributes, identify a distributed ledger that is associated with ledger parameters that meet the set of attributes, and record the data item to the distributed ledger that is associated with ledger parameters that meet the particular set of attributes. The system may determine that a set of archival parameters, associated with a particular distributed ledger, have been met; and may remove the particular distributed ledger from the group of distributed ledgers based on determining that the set of archival parameters, associated with the particular distributed ledger, have been met. Nodes that maintain the group of distributed ledgers may remove ledger data, associated with the removed distributed ledger, from one or more storage resources associated with the nodes.

Abstract: A system described herein may generate a group of distributed ledgers that are each associated with a respective set of ledger parameters, receive a data item that is associated with a set of attributes, identify a distributed ledger that is associated with ledger parameters that meet the set of attributes, and record the data item to the distributed ledger that is associated with ledger parameters that meet the particular set of attributes. The system may determine that a set of archival parameters, associated with a particular distributed ledger, have been met; and may remove the particular distributed ledger from the group of distributed ledgers based on determining that the set of archival parameters, associated with the particular distributed ledger, have been met. Nodes that maintain the group of distributed ledgers may remove ledger data, associated with the removed distributed ledger, from one or more storage resources associated with the nodes.

Abstract: Providing an open data marketplace may include identifying one or more data attributes from a plurality of applications registered with a shared data management system; mapping said one or more data attributes to a data model to create a first set of mapped data; augmenting said first set of mapped data with additional data imported into the shared data management system from other data locations to create an augmented set of mapped data; receiving one or more of second set of mapped data from one or more shared data management system associated respectively with one or more shared data management networks; enabling of composing a data set by combining and cleansing one or more of said first set of mapped data, said second set of mapped data, and said augmented set of mapped data; and offering said composed data set in a digital marketplace with associated pricing characteristics.

Abstract: An application management service account benchmarking. An account profile is generated associated with a target account. Data associated with the target account collected and prepared for benchmarking. A benchmarking pool is formed to include a set of accounts with which to compare the target account. Operational KPIs are designed for benchmarking analysis. Measurements associated with the operational KPIs are determined for the target account and the set of accounts in the benchmarking pool. Benchmarking is conducted based on the measurements. A graph of a distance map is generated and presented on a graphical user interface. Post benchmarking analysis is performed that suggests an action to be performed for the target account.

Abstract: An application management service account benchmarking. An account profile is generated associated with a target account. Data associated with the target account collected and prepared for benchmarking. A benchmarking pool is formed to include a set of accounts with which to compare the target account. Operational KPIs are designed for benchmarking analysis. Measurements associated with the operational KPIs are determined for the target account and the set of accounts in the benchmarking pool. Benchmarking is conducted based on the measurements. A graph of a distance map is generated and presented on a graphical user interface. Post benchmarking analysis is performed that suggests an action to be performed for the target account.

Abstract: Coordinating data sharing among applications in mobile devices, in one aspect, may include a shared data manager application on a mobile device that manages data trade requirements automatically of a plurality of mobile applications, and permission grants or denials to reads and writes of data managed by the shared data manager and used by the plurality of mobile applications.

Abstract: A surrogate model to a building simulation model is built and used for finding a combination of building components that optimize energy use in a building. The surrogate model may be built iteratively using design points comprising a different combination of building product properties that maximize a predefined expected improvement function.

Abstract: Accommodating schedule variance in work, in one aspect, may comprise tracking information associated with work packets; identifying one or more work packets deviating from a planned schedule based on the tracking; identifying one or more features associated with the identified one or more work packets; computing metrics associated with the one or more features; prioritizing the identified one or more work packets based on the computed metrics using a predictive model, the predictive model calibrated at least based on historical data; and recommending one or more actions to take associated with the one or more prioritized work packets.

Abstract: Accommodating schedule variance in work, in one aspect, may comprise tracking information associated with work packets; identifying one or more work packets deviating from a planned schedule based on the tracking; identifying one or more features associated with the identified one or more work packets; computing metrics associated with the one or more features; prioritizing the identified one or more work packets based on the computed metrics using a predictive model, the predictive model calibrated at least based on historical data; and recommending one or more actions to take associated with the one or more prioritized work packets.

Abstract: Coordinating data sharing among applications in mobile devices, in one aspect, may include a shared data manager application on a mobile device that manages data trade requirements of a plurality of mobile applications, and permission grants or denials to reads and writes of data managed by the shared data manager and used by the plurality of mobile applications.

Abstract: Shared data management in software-as-a-service platform may provide a common object data schema for one or more data objects and one or more data attributes associated with said one or more data objects stored in a master database. A plurality of applications may be enabled to be deployed dynamically on a platform and interoperate by sharing said data values stored in the master database. Data trading is enabled in which applications request permissions to read from or write to, or both, the master database, and in which the requests are mediated by granting or denying permissions.

Abstract: Federating multiple-level master data management systems may include a first set of master data management nodes having one or more common characteristics. A first group master data management node may be assigned to centrally manage the first set of master data management nodes, the first group master data management node maintaining master data management functionalities at a group level and providing a single logical view of master data to the first set of master data management nodes. Each master data management node in the first set has data access link with the first group master data management node based on implementation style of said each master data management node.

Abstract: Dynamic application adaptation in software-as-a-service platform, in one aspect, may receive an access permission associated with a published shared data management data object in the software-as-a-service platform having shared data management and a plurality of applications deployed, look up one or more rules associated with one or more features of an application deployed on the software-as-a-service platform, based on the received access permission, and activate or deactivate said one or more features associated with said plurality of applications based on said one or more rules.

Abstract: Coordinating data sharing among applications in mobile devices, in one aspect, may include a shared data manager application on a mobile device that manages data trade requirements of a plurality of mobile applications, and permission grants or denials to reads and writes of data managed by the shared data manager and used by the plurality of mobile applications.

Abstract: Coordinating data sharing among applications in mobile devices, in one aspect, may include a shared data manager application on a mobile device that manages data trade requirements automatically of a plurality of mobile applications, and permission grants or denials to reads and writes of data managed by the shared data manager and used by the plurality of mobile applications.

Abstract: Managing data stewardship in multi-level MDM systems may include a steward data composer that creates data steward repository for a master data management system to define relationships between data stewards and data objects for which data stewards are responsible and steward data consolidator that creates an integrated data steward repository by combining multiple data steward repositories.