News Column

"Systems and Methods for Data-Warehousing to Facilitate Advanced Business Analytic Assessment" in Patent Application Approval Process

July 22, 2014



By a News Reporter-Staff News Editor at Information Technology Newsweekly -- A patent application by the inventor Guerra, Joseph (Cheshire, CT), filed on March 15, 2013, was made available online on July 10, 2014, according to news reporting originating from Washington, D.C., by VerticalNews correspondents.

This patent application has not been assigned to a company or institution.

The following quote was obtained by the news editors from the background information supplied by the inventors: "Data warehouses provide systems for storing and organizing data that organizations use to plan and conduct business operations, for example. Data is organized using extraction, transform and load (ETL) operations to enable use of computer systems to access data for specific organizational needs. However, as the amount and complexity of data increases, existing tools are inadequate to provide access to the types of data that businesses need to conduct operations at the pace that is now required. Unfortunately, existing data warehouses are not a panacea for all business needs. Particularly, many warehouses are inefficient in their implementation and perform conventional operations in a manner which may render the system impractical for dealing with large datasets in a timely manner. There exists a need for novel systems and methods to improve data warehousing operations and to better coordinate data organization for analysis, input, and retrieval."

In addition to the background information obtained for this patent application, VerticalNews journalists also obtained the inventor's summary information for this patent application: "Data warehouses typically maintain a copy of information from source transaction systems. This architecture provides the opportunity to perform a variety of functions. For example, the warehouse may be used to maintain data history, even if the source transaction systems do not maintain a history. The warehouse may also integrate data from multiple source systems, enabling a central view across the enterprise. This is particularly valuable when the organization has grown by one or more mergers, for example. A warehouse can also restructure the data to deliver excellent query performance, even for complex analytic queries, without impacting the transactional database systems. A warehouse may also present the organization's information in a consistent manner and restructure the data so that it makes sense to the business users. A warehouse may provide a single common data model for all data of interest regardless of the data's source.

"In this manner the warehouse adds value to operational business applications. The warehouse may be built around a carefully designed data model that transforms production data from a high speed data entry design to one that supports high speed retrieval. This improves data quality, by providing consistent codes and descriptions, and possibly flagging bad data. A preferred embodiment of the invention uses a derived surrogate key in which an identifier is formed from field entrees in the source table in which transaction data has been positioned. Different combinations of fields can be employed to generate derived surrogate keys depending on the nature of the data and the fields in use for a given data warehouse. It is generally preferred to use a specific combination of fields, or a specific formula, to form the derived surrogate keys for a particular data warehouse. This provides for data consistency and accuracy, and avoids the look-up operations commonly used in generating surrogate keys in existing data warehouses. Preferred embodiments of the invention utilize the derived surrogate key methodology to provide faster access to more complex data systems, such as the merger of disparate source data into a single warehouse.

"A preferred embodiment of the invention uses the advantages provided by the derived surrogate key methodology in a hierarchical structure that uses a hierarchy table with a plurality of customer dimensions associated with a plurality of levels of an interim table. As hierarchy reporting requirements change it is no longer necessary to alter the dimension of the hierarchy table, as the interim table can be altered to provide for changed reporting requirements. Thus, a preferred method of the invention includes altering the interim table to provide for a change in reporting without the need for changing of each dimension. A preferred embodiment includes altering a rolling format which can include, for example, resetting the offset distance to identify which level in an interim table is used to retrieve the appropriate data. Thus preferred methods involve setting the parameters such as the number of levels to be traversed in order to populate the interim table with an ETL tool. The interim table is then connected to the fact table and the dimension table to enable the generation of reports.

BRIEF DESCRIPTION OF THE DRAWINGS

"FIG. 1 is a high level representation of a data warehouse design used in certain embodiments, including a source system feeding the data warehouse and being utilized by a business intelligence (BI) toolset.

"FIG. 2 is an exemplary computing device which may be programmed and/or configured to implement certain processes described in relation to various embodiments of the present disclosure.

"FIG. 3 illustrates a database topology for pulling multiple Enterprise Resource Planning (ERP) data sources using an Extract, Transform, and Load (ETL) software tool. The ETL tool may obtain data from each appropriate source, including whatever ERP systems are in use.

"FIG. 4 illustrates a database topology for creating a separate Central Repository (CR) for each of the separate sources that uses a separately maintained ETL process.

"FIG. 5 illustrates a sample of the separate business subjects (data marts) that can be included in the data warehouse of certain embodiments.

"FIG. 6 illustrates how the Accounts Receivable (AR) business subject (data mart) may be included in the data warehouse of certain embodiments.

"FIG. 7 illustrates how certain embodiments move data from the separate source ERP transactional detail data stores into the AR Data Mart Fact table and the subordinate ERP specific extension tables.

"FIG. 8 illustrates how certain embodiments move data from the separate source ERP transactional data stores into the Data Mart Fact Header table associated with each ERP.

"FIG. 9 illustrates a method of creation and usage of system generated surrogate keys.

"FIG. 10 is a flow diagram depicting certain steps in a derived surrogate key creation process.

"FIG. 11 illustrates a method of creation and usage of simple derived surrogate keys based on application data in certain embodiments.

"FIG. 12 illustrates a method of creation and usage of complex derived surrogate keys based on application data in certain embodiments.

"FIG. 13 illustrates the method of certain embodiments for creating and using derived complex numeric surrogate keys based on application data.

"FIG. 14 illustrates the method of certain embodiments for creating and using derived complex character surrogate keys based on application data.

"FIG. 15 illustrates the method of certain embodiments for creating and using a source control.

"FIG. 16 is a flow diagram depicting a method for providing multisource control in certain embodiments.

"FIG. 17 illustrates the method of certain embodiments for using audit controls.

"FIG. 18A-D illustrate various prior art methods of utilizing hierarchies.

"FIG. 19A illustrates the method of utilizing hierarchies in certain of the embodiments, overcoming certain of the deficiencies of the structures of FIGS. 18A-D.

"FIG. 19B is a flowchart of an exemplary method of generating an interim table.

"FIG. 19C is a flowchart of an exemplary method of using an interim table.

"FIG. 20 illustrates a method used in certain embodiments to build a dates dimension.

"FIG. 21 is a flow diagram depicting a method used in certain embodiments to create a dates dimension.

"FIGS. 22A-B show an example of the dates dimension in certain embodiments.

"FIG. 23 is a flow diagram depicting steps in a process for traversing a hierarchical structure such as the Table of FIG. 19A.

"FIGS. 24-31 are process flow diagrams illustrating methods of forming derived surrogate keys from selected parameters."

URL and more information on this patent application, see: Guerra, Joseph. Systems and Methods for Data-Warehousing to Facilitate Advanced Business Analytic Assessment. Filed March 15, 2013 and posted July 10, 2014. Patent URL: http://appft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&u=%2Fnetahtml%2FPTO%2Fsearch-adv.html&r=1138&p=23&f=G&l=50&d=PG01&S1=20140703.PD.&OS=PD/20140703&RS=PD/20140703

Keywords for this news article include: Patents, Information Technology, Information and Data Aggregation.

Our reports deliver fact-based news of research and discoveries from around the world. Copyright 2014, NewsRx LLC


For more stories covering the world of technology, please see HispanicBusiness' Tech Channel



Source: Information Technology Newsweekly


Story Tools






HispanicBusiness.com Facebook Linkedin Twitter RSS Feed Email Alerts & Newsletters