Abstract: Approaches for a model-driven tool-agnostic reporting approach are provided. In one example, a report request is received from a business intelligence reporting application, from which a graphical template and query template are created, wherein the graphical template comprises the visual presentation of data responsive to the request and the query template specifies how the data responsive to the request is to be computed. The report created by the approaches described herein is compatible with multiple business intelligence reporting applications.

Abstract: Approaches for a model-driven tool-agnostic reporting approach are provided. In one example, a report request is received from a business intelligence reporting application, from which a graphical template and query template are created, wherein the graphical template comprises the visual presentation of data responsive to the request and the query template specifies how the data responsive to the request is to be computed. The report created by the approaches described herein is compatible with multiple business intelligence reporting applications.

Abstract: Approaches for integrating an operational reporting system with a warehouse based reporting system. The operational reporting system and the warehouse based reporting system may be offered and supported by different vendors, and so may be deployed in different clouds or as separate product installations in case of on-premise software, or these systems may be offered and supported by a single vendor, and so may be deployed in the same cloud or as part of a common product installation in case of on-premise software. The integrated system uses a common or consistent dimensional model to link related measures of the operational reporting system and the warehouse based reporting system, which allows for analysis of real time content with historical and cross subject perspective provided alongside in the same interface. The integration also facilitates trend analysis and predictive analytics in real time.

Abstract: Automatically assessing the health and predicting a probability of outage of a configuration item. A system automatically assesses the health of a configuration item and determines the probability of its outage by analyzing information associated with the current conditions of the configuration item obtained from an information technology service management (ITSM) system, an application performance management (APM) system or a machine data (MD) analysis system. The system further determines a probability of outage and health degradation of a set of configuration items impacted due to a Change by matching essence key phrases of the requested Change with outage predictor list for outage probability and health degradation predictor list for health degradation probability. The system further monitors configuration items impacted by a Change by analyzing information for the associated configuration items obtained from the ITSM, APM and MD analysis systems before and after the requested Change.

Abstract: An automated input gathering system for defining, refining or validating a data warehouse star schema for a given data source. The automated data input gathering system includes a source metadata analysis module, an operational reporting environment analysis module, a usage analysis module and a data profiling module.

Abstract: An automated system for defining a star schema for a data source. The system based on automatically gathered information from the data source such as entities and columns, entity column types and lengths, entity keys, relationships between and within entities, measures, workflow and correlated attributes, specialized entities, an update frequency of entities and columns, and grouping of entity and column updates associated with the source database automatically determines facts, dimensions, dimension hierarchies, measures, workflow specific measures (if data source has workflows) and workflow correlated attribute specific measures (if data source has temporal, priority, ownership and progress tracking attributes) to come up with a star schema for the data source.

Abstract: Approaches for automatically determining of correlation for incident, problem and change items. Approaches may perform the steps of: (i) automatically extracting relevant information that includes any of (a) a time of occurrence, (b) important keywords, (c) a category, or sub-category classification, (d) related configuration items, (e) a group membership of the user who worked on, and (f) outage records associated with the incident, problem, and change items; and (ii) automatically analyzing persisted correlation maps using the essence key phrases associated with the incidents to identify essence key phrases of contributing problems, and changes; and (iii) automatically clustering the incidents, optionally with (A) the problems, and (B) the changes to identify clusters of related incident, problem and change items based on the relevant information associated with the incident, problem, and change items.

Abstract: An automated system for validating and refining a template warehouse star schema for a customized data source.

Abstract: A source computing environment administering business intelligence (BI) processing at a target computing environment. The source computing environment storing intermediate design plans for creating dimensional models, reports, and ETL jobs for deployment in a plurality of different computing environments. At the source computing environment, target specific modules translating the one or more intermediate design plans into one or more target specific plans for dimensional models, reports, and ETL job plans which are interpretable or executable by the target computing environment. The source computing environment, in consultation with a workflow engine, instructing the target computing environment to provision data repositories, create reports, and perform ETL processing based on the one or more target specific plans.

Abstract: Approaches for providing a customizable external data feed to a recipient. Metadata that identifies a plurality of configuration parameters that define characteristics of the external data feed are stored. A plurality of executable jobs using the configuration parameters defined in the metadata are programmatically generated. At least a first portion of executable jobs are executed to extract a data set identified by the configuration parameters from a persistent data store. At least a second portion of executable jobs are executed to format and transform the data set according to the configuration parameters. The external data feed, which comprises the formatted and transformed data set, is provided to the recipient.

Abstract: Approaches for a persistent data store that may be used to service data queries originating from data warehousing applications, operational reporting applications, or data archiving and data feed applications. At periodic intervals, data may be extracted from one or more disparate data sources. The extracted data may be stored in the persistent data store in a tabular format. A backward delta data set is generated. The backward delta data set identifies what additions, deletions, and modifications need to be made to the data stored in the persistent data store to return the data to a most recent version. Backward delta data sets are stored and maintained in accordance with a policy that instructs two or more backward delta data sets, associated with a continuous interval of time, be combined into a single backward delta data set after the expiration of a specified amount of time.

Abstract: An automated system for validating and refining a template warehouse star schema for a customized data source.

Abstract: An automated input gathering system for defining, refining or validating a data warehouse star schema for a given data source. The automated data input gathering system includes a source metadata analysis module, an operational reporting environment analysis module, a usage analysis module and a data profiling module.

Abstract: Approaches for a user-driven warehousing approach are provided, wherein usage patterns for business intelligence applications are gathered, for example in an automated recording fashion, allowing the automated scheduling of jobs in a manner that prioritizes jobs that populate the most-used tables and scheduling those jobs in a manner to ensure that the data is up-to-date prior to when it is generally accessed. The usage pattern analysis also allows for the automated identification of more focused data marts for particular situations. The usage pattern analysis also provides for automated data warehouse/data mart creation and customization based on usage patterns that may be used as a seed, as well as for on-the-fly latitudinal analysis across prepackaged domain-specific applications.

Abstract: A technique for exporting results from a reporting system report in a format type including a datamart, PDF file, flat file, Excel™ file, HTML file, and XML file or in another relational database management system (RDBMS) format. In one embodiment, the technique is realized through a method and a system for automatically exporting results from a business intelligence, OLAP, or other reporting system. One embodiment of the present invention involves a method of enabling a user to designate a report desired for execution as an export-report. When the report is processed, the report is exported into a datamart or other format and made available for access by the user through one or more different types of user devices. The user may then further manipulate or export the results from the datamart to a file type as desired.

Abstract: Embodiments herein receive a set of content quality threshold values, a search string, and a content data stream at a content quality metric (CQM) apparatus. Content segments associated with the content data stream are scored and/or graded according to a set of content relevance scales. The content data stream is then filtered to include only passing content segments and intermediate calculation values used to determine whether a content segment is passing. Other embodiments are described and claimed.

Abstract: Embodiments herein receive a set of content quality threshold values, a search string, and a content data stream at a content quality metric (CQM) apparatus. Content segments associated with the content data stream are scored and/or graded according to a set of content relevance scales. The content data stream is then filtered to include only passing content segments and intermediate calculation values used to determine whether a content segment is passing. Other embodiments are described and claimed.

Abstract: The present invention discloses a method for monitoring the blood flow in the cerebral vasculature of a subject. The method includes measuring the electrophysiological activity of different regions in the brain in the excited or unexcited state. The measured electrophysiological activity of each region is then compared with the baseline of the electrophysiological activity of that region for the corresponding state. External stimuli or the performance of specific tasks by the subject can be used to excite different regions of the brain. Any deviation in the measured electrophysiological activity from the baseline indicates an altered blood flow in that region of the brain. Identification of this particular region of the brain which has altered activity can be carried out based on the external stimuli that resulted in the altered activity.

Abstract: Embodiments herein receive a set of content quality threshold values, a search string, and a content data stream at a content quality metric (CQM) apparatus. Content segments associated with the content data stream are scored and/or graded according to a set of content relevance scales. The content data stream is then filtered to include only passing content segments and intermediate calculation values used to determine whether a content segment is passing. Other embodiments are described and claimed.

Abstract: Embodiments herein relate market entities, market topics, and market relationships in a market relationship module (MRM). The MRM is used to index user-applicable information content and to formulate queries for later recall and presentation of the applicable content. Other embodiments are described and claimed.