Abstract: Processing multiple kinds of event messages in a computing system includes storing the event messages as records associated with event messages. Each event message includes a timestamp and the records include a field indicating a target delivery time for an event result for the event message, the target delivery time being determined according to a kind of the event message. The event messages are processed to deliver event results based on information in the event messages and the target delivery times. Event messages are prioritized to deliver event results according to information indicating priority. A target delivery time is computed for event messages having a same priority based on fixed delays relative to their timestamps. Event results are delivered based on a comparison of their target delivery times to a clock time.

Abstract: Technologies are described herein for a representational state transfer (“REST” or “RESTful”) over Intelligent Platform Management Interface (“IPMI”) interface for firmware to baseboard management controller (“BMC”) communication and applications thereof. These applications include, but are not limited to, remote firmware configuration, firmware updates, peripheral device firmware updates, provision of management information such as system inventory data, cloning and batch migration of firmware configuration settings, and firmware integrity monitoring. This functionality can be provided in a way that enables communication between BMCs and firmware to utilize modern manageability interfaces while maintaining backward compatibility with previous IPMI implementations.

Abstract: A system, method and the like for seamlessly integrating disparate applications, such as channel applications and off-the-shelf business process management (BPM) services/applications through use of a core process framework that provides a vendor/third-party entity-agnostic approach to application integration. The core process framework provides various fundamental processes that are shared amongst applications that are in communication with the framework. The core process framework leverages a headless BPM and middleware integration patterns that serve to create an open architecture with reduced dependency on the third-party entity/vendor providing the BPM service. In this regard, the core process framework of the present invention provides a service platform that clients (i.e., channel applications) can make service requests/calls to, via an integration gateway or the like, to perform multiple different generic BPM engine-related operations.

Abstract: Methods, systems, and computer program products for suggesting application programming interfaces (APIs) based on feature and context analysis are provided herein. A computer-implemented method includes extracting at least one feature of an input function code based on application of one or more text analytics to one or more inputs pertaining to the input function code; deriving at least one item of context-related information from the input function code; generating a suggestion comprising one or more application programming interfaces, wherein said generating comprises comparing (i) the at least one feature of the input function code and (ii) the at least one item of context-related information to a database, and wherein the database comprises (a) feature data and (b) context-related information pertaining to multiple application programming interfaces; and outputting the suggestion to at least one user.

Abstract: Methods, systems and computer program products for securing access to sensor data are provided herein. A computer-implemented method includes obtaining sensor data from a user device indicative of user activity, detecting for a first time period activities of the user, generating a transformation key for the first time period, transforming sensor data obtained during the first time period utilizing the transformation key, and streaming the transformed sensor data to a plurality of applications. The method also includes determining whether respective ones of the applications have permitted activities that match the detected activities of the user and, responsive to matching the permitted activities of a given application to the detected activities of the user, providing the transformation key to the given application.

Abstract: A bipartite workflow graph, representing an understanding of an overall service, comprises two different graph elements: entities and processes and each individual microservice defines their logical constructs as either an entity or a process in accordance with a universal schema. Notifications from such microservices conform to the universal schema, thereby enabling microservices to individually change how they operate internally, without affecting an understanding of the overall system as represented by the workflow graph. Each graph element has its state maintained by a separately addressable execution unit executing a state machine, which can be individually updated based on information received from the microservices. Changes to the workflow graph are logged and an insight engine monitors such a log to insert insight markers in accordance with predefined events, thereby enabling the collection of metrics on a service wide basis and across multiple microservices.

Abstract: A data processing system includes a transaction bus, a console application in communication with the transaction bus, and a view predictor subsystem in communication with the transaction bus. A call for visual information is received at the transaction bus. Prior to returning a result to the user application in response to the call: a likelihood that the visual information will be viewable within a viewport of a user application is determined by the view predictor subsystem, the console application provides to the transaction bus a set of potential sources of the visual information, the transaction bus converts associated data from the potential sources into a common form of measurement using the likelihood, and the transaction bus selects one of the potential sources of the visual information to be the result based on the data converted into the common form of measurement. The result is returned to the user application.

Abstract: Events are raised by a worker thread that is executing a workflow, when the worker thread starts, suspends, resumes and ends execution of the workflow. A latency detection system, that is external to the worker thread, detects when these events are raised and logs a timestamp and a stack trace, corresponding to the workflow and the event that was raised.

Abstract: A method for dynamically routing of events to destinations based on mapping metadata is described. The method includes detecting, by a capture service of an application server, an event associated with values for one or more attributes that describe the event; mapping, by a metadata service of the application server, the event to a set of destinations based on the mapping metadata received by the application server at runtime, the values of the one or more attributes of the event, and permissions associated with a tenant; and storing, by a buffer of the application server, the event and the set of destinations.

Abstract: This disclosure relates to cross-platform applications that include native and non-native components on mobile devices. An exemplary method generally includes receiving a first workflow step definition including a first set of widgets to be loaded into an application shell. A mobile shell identifies a type of each widget in the first set of widgets (e.g., native or platform-agnostic) and loads each widget into the mobile shell based on the widget type. For a platform-agnostic widget, the mobile shell creates a platform-agnostic widget proxy service, which provides a runtime environment. The platform-agnostic widget may be loaded into the platform-agnostic widget proxy service and executes in the runtime provided thereby.

Abstract: A method, system, and/or computer program product modify a hardware device based on a time series of data. One or more processors standardize a time series of data received from sensors that are monitoring a hardware device. The processor(s) establish time ranges before, during and after each event. The processor(s) determine which events represented by the time series of data are significant by comparing means and trends of time sub-series corresponding to the time ranges before, during, and after each event, and then generate a modified time series of data by reducing a number of significant events described by the time series of data, which is used to modify the hardware device.

Abstract: System and methods are disclosed to facilitate the active management and allocation of the knowledge resources of an organization. In one exemplary implementation, the systems and methods include a trigger event handler module installed on a computing device, such as a computer server, configured to receive and process data that will fire trigger events in real time to modify records of the organization or perform processes and specified actions. The system collects data about the transaction and stores the data in a database for future use.

Abstract: A method and an apparatus that allocate one or more physical compute devices such as CPUs (Central Processing Unit) or GPUs (Graphics Processing Unit) attached to a host processing unit running an application for executing one or more threads of the application are described. The allocation may be based on data representing a processing capability requirement from the application for executing an executable in the one or more threads. A compute device identifier may be associated with the allocated physical compute devices to schedule and execute the executable in the one or more threads concurrently in one or more of the allocated physical compute devices concurrently.

Abstract: A distributed shared log storage system employs an adapter that translates Application Programming Interfaces (APIs) for a big data application to APIs of the distributed shared log storage system. An instance of an adapter is configured for different big data applications in accordance with a profile thereof, so that the big data applications can take on a variety of added characteristics to enhance the application and/or to improve the performance of the application. Included in the added characteristics are global or local ordering of operations, replication of operations according to different replication models, making the operations atomic and caching.

Abstract: A facility management system and method for planning and/or controlling a facility, in particular a fabrication facility, including a plurality of components. The facility management system includes at least one apparatus adapted to load component data object cubes (CDOCs) from a data cube library (DCL) stored in a database of the facility management system and to link the component data object cubes (CDOCs) to component data objects (CDOs) representing components of the facility. The loaded component data object cubes (CDOCs) linked to the component data objects (CDOs) include parameters of the respective components and are editable in a data edit model of the facility management system.

Abstract: Systems and methods provide an application programming interface to offer action suggestions to third-party applications using context data associated with the third-party. An example method includes receiving content information and context information from a source mobile application, the content information representing information to be displayed on a mobile device as part of a source mobile application administered by a third party, the context information being information specific to the third party and unavailable to a screen scraper. The method also includes predicting an action based on the content information and the context information, the action representing a deep link for a target mobile application. The method further includes providing the action to the source mobile application with a title and a thumbnail, the source mobile application using the title and thumbnail to display a selectable control that, when selected, causes the mobile device to initiate the action.

Abstract: A user interface for dynamically validating at least a portion of programming codes as an application program interface (API) modification request. A first window area statically displays data definitions for one or more configurable elements for a request to be operably connected to an API. A second window area displays programming codes structured according to the data definitions for the request. The second window area also receives a first input from a user to modify the configurable elements. In response to receiving the first input, a dynamic request display area receives an instruction from the user to submit the programming codes to the API for validation. The submitted programming codes are not complete as a complete transaction request for processing by the API. The dynamic request display area displays a response substantially immediate after the programming codes are submitted, and response indicates whether the submitted programming codes are valid.

Abstract: A computer-implemented interface apparatus and method are directed to automated calibration, sensitivity analysis, and optimization of computer models. User interfaces may be provided for automatically managing interchangeable input parameters, interchangeable output objective functions, and interchangeable optimization methods. A user may use the computer-implemented interface apparatus and method to select any number of input and output parameters and calibration or search thoroughness levels for automated calibration, sensitivity analysis, and optimization of a computer model. The functionality of selecting the input and output parameters and calibration or search thoroughness levels may allow the user to adjust or control computer run times for automated calibration, sensitivity analysis, and optimization of the computer model.

Abstract: A data center includes various sets of infrastructure modules which each provide a particular type of infrastructure support to support computing operations in the data center. Separate sets of infrastructure modules can be installed incrementally based on incrementally changing support capacity for the corresponding type of infrastructure support in the data center. Such incrementally changing support capacity can be based upon support requirements of electrical loads, including rack computer systems, which are inbound to the data center. Where support capacity for a particular type of infrastructure support drops below a threshold, a quantity of additional infrastructure modules which provide the particular type of infrastructure support can be selected and installed to increase the support capacity.

Abstract: One embodiment of the present disclosure describes a battery control system architecture design system that stores an objective function. The battery control system architecture design system determines implementation of battery systems intended be compatible with a battery control system architecture; determines target control levels to be provided by battery control systems based at least in part on the implementation of the battery systems; determines target functions to be provided by the battery control systems based at least in part on the implementation of the battery systems; determines infrastructure expected to be used to provide each of the target functions; and determines the battery control system architecture by dividing the target functions between the target control levels based at least in part on the objective function and the infrastructure, in which the battery control system architecture provides building blocks used to implement each of the battery control systems.