Patent application number | Description | Published |
20100004968 | PATTERN-BASED POLICY APPLICATION MECHANISM FOR SCA - A pattern-based policy method for service component architecture (SCA) defines a policy pattern for SCA. The policy pattern includes a plurality of roles and one or more constraints between said plurality of roles. Each of said plurality of roles defines a plurality of intents or policy sets or combination thereof. One or more roles assigned to said one or more SCA components are identified and one or more intents or policy sets or combination thereof associated with said one or more roles are automatically applied to said one or more SCA components. Said one or more intents or policy sets or combination thereof applied to said one or more SCA components are validated based on said one or more constraints. | 01-07-2010 |
20100005451 | POLICY APPLICATION RULES FOR AUTOMATED CONFIGURATION OF SOFTWARE COMPONENTS - A method, system and article of manufacture are disclosed for configuring software application components. The method comprises the steps of developing a set of policy application rules, assembling unconfigured software components into one or more software applications, and applying said application rules to the unconfigured software components to configure said software components. In the preferred embodiment, the applying step includes the steps of passing the unconfigured software components to a policy rule engine, and using said policy rule engine to apply said application rules to the unconfigured software components to produce the configured components. In addition, the method may be done to resolve ambiguities in the software components. In particular, the application rules may be designed to resolve ambiguities in the application of these rules to the unconfigured software components. Also, each application rule preferably includes a condition, an application template, and a policy. | 01-07-2010 |
20100114627 | Processing of Provenance Data for Automatic Discovery of Enterprise Process Information - Techniques are disclosed for capturing, storing, querying and analyzing provenance data for automatic discovery of enterprise process information. For example, a computer-implemented method for managing a process associated with an enterprise comprises the following steps. Data associated with an actual end-to-end execution of an enterprise process is collected. Provenance data is generated based on at least a portion of the collected data, wherein the provenance data is indicative of a lineage of one or more data items. A provenance graph that provides a visual representation of the generated provenance data is generated, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. The generated provenance graph is stored in a repository for use in analyzing the enterprise process. | 05-06-2010 |
20100114628 | Validating Compliance in Enterprise Operations Based on Provenance Data - Techniques are disclosed for validating compliance with enterprise operations based on provenance data. For example, a computer-implemented method for validating that an enterprise process is in compliance with a rule comprises the following steps. Provenance data is generated, wherein the provenance data is based on collected data associated with an actual end-to-end execution of the enterprise process and is indicative of a lineage of one or more data items. A provenance graph is generated that provides a visual representation of the generated provenance data, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. A correlation is generated between one or more entities in the rule and one or more record types in the provenance data. One or more control points are generated in accordance with the generated correlation. A validation is performed as to whether the enterprise process is in compliance with the rule using the one or more control points. | 05-06-2010 |
20100114629 | Extracting Enterprise Information Through Analysis of Provenance Data - Techniques are disclosed for extracting information through analysis of provenance data. For example, a computer-implemented method of extracting information regarding an execution of an enterprise process comprises the following steps. Provenance data is generated, wherein the provenance data is based on collected data associated with an actual end-to-end execution of the enterprise process and is indicative of a lineage of one or more data items. A provenance graph is generated that provides a visual representation of the generated provenance data, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. At least a portion of the generated provenance data from the graph is analyzed so as to extract information about the execution of the enterprise process based on the analysis. | 05-06-2010 |
20100114630 | Influencing Behavior of Enterprise Operations During Process Enactment Using Provenance Data - Techniques are disclosed for influencing behavior of enterprise operations during process enactment using provenance data. For example, a computer-implemented method of influencing a behavior of an enterprise process comprises the following steps. Provenance data is generated, wherein the provenance data is based on collected data associated with at least a partial actual execution of the enterprise process and is indicative of a lineage of one or more data items. A provenance graph is generated that provides a visual representation of the generated provenance data, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. At least a portion of the generated provenance data from the graph is analyzed to generate an execution pattern corresponding to the at least partial actual execution of the enterprise process. The execution pattern is compared to one or more previously stored patterns. A determination is made as to whether or not to alter the enterprise process based on a result of the comparison. | 05-06-2010 |
20120179510 | PROCESSING OF PROVENANCE DATA FOR AUTOMATIC DISCOVERY OF ENTERPRISE PROCESS INFORMATION - Techniques are disclosed for capturing, storing, querying and analyzing provenance data for automatic discovery of enterprise process information. For example, a computer-implemented method for managing a process associated with an enterprise comprises the following steps. Data associated with an actual end-to-end execution of an enterprise process is collected. Provenance data is generated based on at least a portion of the collected data, wherein the provenance data is indicative of a lineage of one or more data items. A provenance graph that provides a visual representation of the generated provenance data is generated, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. The generated provenance graph is stored in a repository for use in analyzing the enterprise process. | 07-12-2012 |
Patent application number | Description | Published |
20080215641 | HIGH SPEED DATA HISTORIAN - Techniques for operating an archival database, referred to as a historian, are disclosed. The historian may be used to archive values from a real-time database. Data values to be archived in the historian are first written to a short-term, high-availability repository, such as a memory-mapped database. As data values “fill” the short-term repository, an archival processor application may be configured to “drain” them from the short-term repository and store them in a high-capacity, long-term archive, such as a disk-based database. Thus, the short-term repository may be used to provide fast access to the recent operational history of a monitored system, (e.g., a complex pipeline network), where long-term archive may be used to provide access to a comprehensive operational history of the monitored system. | 09-04-2008 |
20090006499 | SYNCHRONIZING HISTORICAL ARCHIVE DATA BETWEEN PRIMARY AND SECONDARY HISTORIAN SYSTEMS - Techniques for operating an archival database, referred to as a historian, are disclosed. Embodiments of the invention provide techniques for synchronizing historical archive files and/or archival data between a primary and a secondary historian used to archive data values from a real-time database. The real-time database may be used to monitor the current operational state of a large industrial system, such as a pipeline. In turn, the historian may be used to archive the data stored by the real-time database. In the event that either the primary or the secondary system (or both) goes down and then comes back online at a later time, embodiments of the invention may be used to synchronize data between the primary and secondary historian systems. | 01-01-2009 |
20110009984 | PRESENTING DYNAMIC SCADA DATA - Techniques are disclosed for presenting users with dynamic views of process data related to the operations of an industrial system. Data obtained by a SCADA system may be stored in a real-time status database (which reflects the current process data of the industrial system) and a historian database (which archives the process data from the industrial system as it changes over time). A design canvas allows users to compose a dynamic view of the process data obtained by the SCADA system. For example, a user may compose a dynamic view of selected temperatures, pressures, and flow rates obtained by the SCADA system while monitoring the status of a pipeline. | 01-13-2011 |