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: A method for automatically determining one or more cross customer metrics from a cross customer store for cross customer analytics is provided. The method includes the steps of: (i) automatically standardizing dimensions associated with the one or more customers to create one or more cross customer metrics; (ii) automatically determining incremental data from one or more customer specific stores by tracking (a) a time stamp of a last pull time (T) for customer data stored in the one or more customer specific stores, and (b) a number of items involved (I); (iii) automatically updating the one or more cross customer metrics in the cross customer store with the incremental data; and (iv) automatically comparing the one or more cross customer metrics of a customer with one or more peer groups created at run time based on customer selected values for one or more parameters.

Abstract: Automatically determining time threshold guarantees for metrics like completion time or first response time for tasks or items. A system relies on the historical tasks data with completion or first response times. The system plots a graphical representation between completion time and a percentage of tasks completed and uses sophisticated analysis of slopes at different points of the graphical representation to determine time threshold guarantees below a specified maximum completion or first response time threshold, and above a specified minimum percentage of completion. The system also compensates for a variety of factors which may be changed from the time historical data was obtained to the present time for which time threshold guarantees are being determined. In absence of historical customer data, the system makes the recommendations based on available datasets of peer customers.

Abstract: Approaches for preserving customizations made to a data management system. Metadata that identifies a mapping between data fields of one or more data source schemas to columns of one or more data tier schemas is maintained. Each of the one or more data tier schemas stores data retrieved from the one or more data source schemas. Values from the metadata are read to dynamically generate software processes. The software processes may update one or more existing ETL processes to reflect an updated state of the one or more data tier schemas and may generate any new ETL processes required to retrieve data stored in the one or more data source schemas and load the retrieved data into the one or more data tier schemas. Customizations made to portions the data management system are preserved in an automated fashion when new versions of system components are deployed.

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: Systems and processor-implemented methods of S-expression based computation of lineage and change impact analysis. An SQL expression is converted into an S-expression tabular structure. A function table including a plurality of functions associated with S-expression tabular structure tabulated against at least one of a function name, a derived column and a derived table and an argument table including plurality of arguments associated with the S-expression tabular structure tabulated against at least one of an argument type, a function identifier linking the arguments to the function table, a computed from function, a reference to entity or a literal value, is generated based on the S-expression tabular structure. At least one of lineage or change impact analysis for an entity is determined based on the function table and the argument table, where lineage provides a provenance of the entity or attribute from a source entity or a source attribute.

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: Approaches for S-expression tabular structure based language conversion. An SQL expression is converted into an S-expression tabular structure. A function table including a plurality of functions associated with S-expression tabular structure tabulated against at least one of a function name, a derived column and a derived table and an argument table including plurality of arguments associated with the S-expression tabular structure tabulated against at least one of an argument type, a function identifier linking the arguments to the function table, a computed from function, a reference to entity or a literal value, is generated based on the S-expression tabular structure. One or more functions associated with the S-expression tabular structure is converted to a pre-determined SQL based language, based on a language map of the pre-determined language and the function table and the argument table.

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: Approaches for extracting data from data sources using a generic web service adaptor that implements a web services processing framework. Metadata stored in the database is read to identify specified named entities from a plurality of web service providers. Application protocol interface (API) semantics and configurations are retrieved from the metadata. Metadata objects for the specified named entities are fetched. Web services operation API signatures of the metadata objects are validated by comparing with predefined web services operation API signatures stored in the metadata. Web services operations for the specified named entities of the web service providers comprising the data sources are performed to obtain returned result objects. The returned result objects are serialized to XML using the same framework as used by the source web service. An adaptor may be configured to support the plurality of web service providers based on configurations.