Sap Ag

Sap Se

Dirk Wodtke

Vincent L Mendicino

Andrew Y Ng

Matthias Kruse

Neil Srivatsan

Peter Latocha

Michael Seubert

Werner Gnan

Jian Xu

Ramshankar Venkatasubramanian

Yingjiong He

Miro Vins

Chinmaya Sarangi

Ramprasad Rai

Timo Hoyer

Nicolai Jordt

Michael Krenkler

Iryna Vogler-Ivashchanka

Emil Voutta

Ioannis Grammatikakis

Florian Jann

Dennis Brian Moore

Annette Jann

Kai Richter

Shai Agassi

Kiran Gangadharappa

Nir Kol

Martin Steiner

Gunther Rothermel

Tzanko Stefanov

Joerg Mann

Stefan Kirchfeld

Maria Cabahug

Apurv R Jawle

Frederick E Samson

Brendan Bowles

Shridhar Nayak

Riccardo Spina

The disclosure generally describes methods, software, and systems, including a method for machine learning anomaly detection for a set of assets. Assets are analyzed using anomaly-detection analysis and a set of anomaly-detection rules. Each asset is associated with correlated records comprising characteristics of the particular asset and characteristic of non-asset-specific signals. Each anomaly-detection rule is associated with conditions determined to be indicative of a potential anomaly. At least a subset of the assets are provided for presentation in a user interface. Each asset is identified as being in a potential anomalous or non-anomalous state based on the anomaly-detection analysis. Input is received from a user identifying at least one asset as anomalous as a non-anomalous asset. Based on the received input, at least one anomaly-detection rule is modified that was applied to identify the asset as anomalous. The modified rule is stored for future analyses.

Machine learning anomaly detection

The disclosure generally describes methods, software, and systems, including a method for providing a suggested view of asset information for presentation. A set of correlated records is identified for a plurality of assets. The set of correlated records includes a correlated set of at least one characteristic of a particular asset and a characteristic of the non-asset-specific signals. The set of correlated records is analyzed to identify a set of anomaly-detection rules. In a presentation of at least a subset of the assets, an indication of assets associated with a potential anomaly identified. A suggested view is identified based on the potential anomaly and at least one characteristic/signal associated with the determination that the potential anomaly exists. The suggested view is provided for presentation in a user interface.

Suggestion of views based on correlation of data

Disclosed herein are system, method, and computer program product embodiments for managing completion of a task. An embodiment operates by receiving a selection of a collection configured to complete the task. The embodiment determines a context indicator for analyzing an application object in the selected collection. The embodiment processes the application object in based on the context indicator to generate information for completing the task. Another embodiment operates by receiving a selection of a collection configured to complete a task. The embodiment then determines that completion of the task requires solving a situation defined by a situation definition. The embodiment then identifies an anchor application object in the selected collection based on the situation definition. The embodiment then generates related information and a set of actions for solving the situation based on the anchor application object and the situation definition.

Personal digital assistant

A system includes determination of a first measure value associated with a first physical space and a first time period within the analytical data, dynamic determination of a time-dependent association between a first entity or event and the first physical, dynamic mapping of the first measure value to the first entity or event based on the time-dependent association, and presentation of the first measure value in association with the first entity or event.

Connected space

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a feed event, a feed event document, and/or a feed event type business object.

Consistent interface for feed event, feed event document and feed event type

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a user feed administrator, a user feed event link and/or a user feed settings business object.

Consistent interface for user feed administrator, user feed event link and user feed settings

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a feed collaboration group and/or a feed event subscription business object.

Consistent interface for feed collaboration group and feed event subscription

A system being monitored generates alerts directed at participants as events to be resolved occur. As a participant resolves an alerted event, the system logs the steps taken by the participant to resolve the event and stores the event resolution log associated with the event. From that event resolution log, a template for a workflow process can be automatically generated. When similar events occur again, the participant for those future events can be provided with the prior stored event resolution log and/or automatically generated templates for a workflow processes corresponding to the stored event resolution log. Iterative generation and editing of templates can be provided for, wherein subsequent event resolutions for similar events are used to modify the workflow process templates developed from previous event resolutions. Events can include conditions being met in data stored by the system or events representing the lack of occurrence of expected events. Participants can be human users, automated participants or proxies interfacing human users to the system. In one embodiment, the system is a network connecting business collaborators.

System supported optimization of event resolution

Method and system for widgetizing a web-based application are provided. An example system comprises a widgetizer trigger and a definition module. The widgetizer trigger may be configured to receive at a server computer system, from a web browser application running at a client computer system, a request to widgetize a web-based computer application to permit the computer application to be run as a desktop widget at the client computer system. The definition module may be configured to provide to the client computer application, in response to the request to widgetize, a definition file associated with the computer application, the definition file comprising a reference link to the computer application, the reference link including one or more parameters, the one or more parameters to instruct the computer application to generate output in a format suitable for use by a widget engine provided at the client computer system.

Widgetizing a web-based application

Embodiments of the present invention include techniques for creating voice applications in different design environments and translating voice applications into any runtime environment. A set of rendering engines creates a translation layer that can convert a voice application into any runtime environment. Each rendering engine receives a voice application and converts the voice application into a runtime-specific voice description. The voice description performs the same or similar functions in the selected runtime environment as the original voice application. Voice applications from different design environments may be stored as metadata and translated through one or more steps into different runtime environments.

Techniques for creating and translating voice applications

Work items are collected from one or more work item providers for presentation to a workflow participant. A work item provider is typically a workflow management system ('WFMS'), but other providers of work items might exist that generate work items and may or may not have their own local worklist. Multiple independent WFMS's of multiple types might provide work items to a universal worklist ('UWL') service that integrates the work items from all of the providers. Additional integration might be provided between the UWL and work item providers, such as for controlling work item execution with a sub-workflow through an ad-hoc workflow engine. Additional integration provides for custom attributes. Each work item has a type that is used to determine handling for that work item. A universal work list service includes storage for work items, wherein a work item represents a task generated as part of a process flow. An engine supporting the UWL service might track item types for work items and might obtain attribute values for attributes of the work item according to the work item's type.

Universal worklist service and user interface

In a structured workflow system, a configurable workflow engine provides mechanisms for executing and scheduling the work items in a defined way. End users use their discretion and define their own 'local' processes and 'local' rules for processing work items, or deviate from predefined processes. The configurable workflow engine might be installed at a server to organize workflows and business processes where end users can define processing steps for incoming work items by setting up rules and defining workflows as part of a local workflow structure. By defining these rules and workflows, the further processing steps of future incoming work items can be automated. When an administrator directs the workflow engine to move from a current phase to a next phase, the workflow engine deals with the incomplete items by allowing the administrator to carry over work items (or might do it automatically). End-user consultation might be included in the carry-over decisions. The carried over work items are added as parallel activities to the next phase. The workflow engine handles imposing and executing control flow dependencies between tasks, thus providing a smooth transition from totally unstructured work to semi-structured or completely structured work. When the workflow engine encounters semantically correlated work items/tasks, the process engine assumes that these work items/tasks belong to the same process instance.

End user oriented workflow approach including structured processing of ad hoc workflows with a collaborative process engine

Methods and apparatuses to provide extension to a groupware client to enable the groupware client to access a workflow of a business process from the context of the groupware client. An enterprise server that manages the workflow can interface with the groupware client to provide action on the workflow from within the context of the groupware client. The enterprise server passes the action to the enterprise backend to implement the action on the workflow. Thus, action on the workflow from the groupware client affects the workflow on the enterprise level. Status information about the workflow may be persisted in the groupware client to enable continued interaction with the workflow from within the groupware client.

Business process extension for productivity suite application

Embodiments of the present invention improve integration of heterogeneous software components. In one embodiment the present invention includes a computer-implemented method comprising receiving metadata that defines an interface for communicating with a custom component, mapping at least one attribute between the custom component and at least one other program component of an application, and generating wrapper code based on the metadata and the mapping, wherein the wrapper code communicates information between the custom component and the application.

Heterogeneous software integration systems and methods

In a computer system wherein messages are transferred between participants, at least some of which are human users of the computer system using the computer system in furtherance of work projects, and wherein a workflow system handles task-based operations in a structured environment, tasks embodied in messages are handled as tasks in the structure environment by transforming messages into workflow items. One embodiment provides for sending a message from a sender to a user computer system; upon review of the message at the user computer system by a user, accepting input from the user representative of a trigger for transforming the message content to a workflow object, wherein the workflow object is a structured representation of one or more tasks to be performed by one or more assignees including linkages between tasks; following a trigger for transforming, accepting user input as needed to obtain task-related information other than information present in the message; once the user input is obtained, generating one or more workflow objects for tasks representing by the message; and providing the one or more workflow objects to a workflow system for workflow handling.

Growing community of inventors

Aptos, CA, United States of America

Dirk Wodtke