WO2001055937A2 - Method and system for the display of business data from multiple sources - Google Patents
Method and system for the display of business data from multiple sources Download PDFInfo
- Publication number
- WO2001055937A2 WO2001055937A2 PCT/US2001/002587 US0102587W WO0155937A2 WO 2001055937 A2 WO2001055937 A2 WO 2001055937A2 US 0102587 W US0102587 W US 0102587W WO 0155937 A2 WO0155937 A2 WO 0155937A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- business
- display
- category
- indicator
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Definitions
- This invention relates to data systems, and more particularly, to a system of requesting, retrieving, and displaying business data from at least one enterprise.
- Business data is typically widely distributed in various databases across an enterprise where the databases have disparate database structures, thus complicating the retrieval and combination of the information in a display format desired by an end user.
- a client user 5 may desire business data from one or more databases 3 within the enterprise where the databases are distributed across a network 1 and even across secondary networks 2 .
- the data must be collected, processed, and sent to the client user 5.
- Traditional data systems that provide client users with information from such disparate data systems usually "get” data from multiple data systems, "process” the data, and “present” the resulting information to end users, as shown in Fig. 2.
- Data and data control is generally made within a single enterprise, with no communication between, for example, customers 2802, companies 2804, suppliers 2806, or partners 2808.
- Processing of data 2818 is typicallv designed for analytical purposes, and presentation of the data 2820 is usually geared to the management layers 2822 of an organization.
- the traditional method to "get" information 2816 from multiple data systems is to load the data onto a secondary system, called a datawarehouse 2810. These systems are designed to manage information within a single enterprise.
- Traditional uses for datawarehouses 2810 are for historical analysis and to build and maintain a single repository for such things as a customer masterfile or financial accounting processes. Loading a datawarehouse 2810 causes significant delays between the entry of information into a data system and its availability to a client user who needs the information in order to make a decision.
- a datawarehouse 2810 takes ownership of all data that passes through it. Enterprises wishing to share data with other enterprises will thus be hesitant to use such a system, as they lose long-term ownership to their own data. Furthermore, both the datawarehouse 2810 and the datamart 2812 must be maintained, adding additional expense.
- Process systems 2818 offer technologies that process data and deliver results into reports directed at financial accounting processes. These technologies either work with a single source database or they work with datawarehouses 2810. In order to process data, these systems move subsets of data into an analytical staging environment. Thus, the data is transferred from its original location and becomes stale and does not reflect real-time changes. These analytical staging environments are suitable for analysis of historic trends to yield decisions affecting the finances of the enterprise. Additionally, these analytical staging environments do not support large numbers of diverse end users, since the end reports are targeted to a specific need and the data cannot be tailored to the individual requirements of a large number of users.
- Current “present” technologies 2820 include providing information in reports. Vendors in the reporting and business intelligence segment "present” information in the form of printed or electronic reports. They focus on information that happened in a previous period and are presented as a single report. Such "present” technology 2820 is limited for the following reasons. Reports are typically forwarded to end users after a financial period closes. By this time, the ability to take action has already passed. Since changes to data represented in reports are not updated in real time, a manager or other user of the reported data may make important decisions based on data that is no longer valid.
- a system for presenting data derived from one or more databases has a model having at least one indicator and at least one category to which the indicator may be pertinent. For each indicator and category pair there may exist a parameter that is derivable from sources in the one or more data bases, the parameter not necessarily pre-existing therein.
- a projection engine receives a user querv that defines one or more indicator-category pairs with respect to each of which a corresponding parameter value is desired.
- the user query is mapped to the model by a model engine, which provides a link between the model and the sources.
- One or more desired commands to the one or more databases for retrieving data from the sources is generated by a query engine.
- the model engine derives from the retrieved data each corresponding parameter value for each indicator-category pair.
- a method for presenting data, derived from one or more databases is presented.
- the one or more databases need not be part of a single data structure or have a specific format.
- a model is provided, having at least one indicator and at least one category to which the indicator may be pertinent. For each indicator and category pair there may exist a parameter, derivable from sources in the one or more data bases, the parameter not necessarily pre-existing therein.
- a link is provided by a model engine to the sources for determining the parameter for each indicator-category pair.
- a query is received that defines one or more indicator-category pairs with respect to each of which a corresponding parameter value is desired.
- the model engine is used to access the sources by a query engine and to derive from the sources each corresponding parameter value, whereupon each corresponding parameter value is reported.
- a method for presenting business data using a computer system is presented.
- a business model is provided, the bt siness model having at least one indicator pertinent to performance of a business and at least one category identifying an aspect of the business to which the indicator may be pertinent.
- the parameter does not necessarily pre-exist in such data, nor does the business data need to be part of a single data structure in any format.
- Paths are provided, in connection with the business model, to the sources in the data for determining the parameter for each indicator-category pair.
- a query is received that defines one or more indicator-category pairs with respect to each of which a corresponding parameter value is desired, whereupon the business model is used to derive the corresponding parameter value.
- a method for presenting business data using a computer system is presented.
- a method for presenting business data using a computer system is presented.
- the business context engine in a computer process distinct from any financial accounting processes of the at least one enterprise, and pursuant to a query that defines a result subset ⁇ . . . , P rS ⁇ ⁇ , reA, seB, of the parameter set S, uses the business data to derive parameter values P rs for all values of r and s.
- a method for creating a business model using an architect module is presented. The model is based on business data of at least one enterprise.
- the two dimensional grid has the at least one indicator 7, located on a first axis of the grid and the at least one category C ⁇ located on a second axis of the grid, so that each node on the two dimensional grid represents a pair ⁇ 7 radiation C ; ⁇ .
- a method for presenting business data using a computer system is presented.
- Business data which need not be part of a single data structure in any format, of at least one enterprise is associated with a business model.
- the business model has at least one indicator pertinent to performance of a business and at least one category identifying an aspect of the business to which the indicator may be pertinent. For each indicator and category pair there may exist a parameter, derivable from the business data and not necessarily pre-existing in such business data.
- the business data is used to derive values of one or more parameters corresponding to the one or more indicator-category pairs in the query.
- the methods expressed above may operate in a network environment wherein the method steps are performed on a server, the query having been received from a client.
- the network may be the Internet.
- information derived from parameter values are outputted to a network device, the output permitting the display of the information at the network device.
- the output may permit the display of the information in a format that allows selectable display, which may be according to hierarchical level of data from which the information is derived.
- the output may also permit the display of the information in a format that allows, for a parameter, selecting an instance of a category, whereby data of a category related to the instance of the category is displayed.
- the output may permit the display of a graphical indication of a current trend of a parameter.
- the graphical indication may be used for graphical control.
- Graphical control may be actuated by graphically selecting the graphical indication, and may be dependent on the trend displayed by the graphical indication.
- the graphical indication may control the display of related data.
- a template may be associated with the business model, for displaying the one or more parameters, the template including an arrangement for displaying data in a format that permits selectable display of related data from which the one or more parameters are derived.
- the template with the parameters may be transmitted to a client via a network for display of the template in a browser.
- Fig. 1 is a diagram of a data system spread over various networks and databases
- Fig. 2 is a diagram of a traditional data system (prior art);
- Fig. 3 is a diagram of a data system for retrieving business data from at least one enterprise according to one embodiment of the invention;
- Fig. 4 is a screen image of a typical page view;
- Fig. 5 is a screen image of a typical monitor;
- Fig. 6 is a block diagram of a system showing a business context engine, an architect module, and a gateway.
- Fig. 7 is a diagram showing the business model serving as a link between the data sources and the analytical software
- Fig. 8 is an example of a business model
- Fig. 9 is a diagram showing how elements are used to form a business model
- Fig. 10 is a flowchart of the steps used in creating a business model
- Fig. 10A is a flowchart showing a use of the business model
- Fig. 11 is a graphical display that can be used in creating the business model
- Fig. 12 are four panels in the graphical display of Fig. 11, which include the grid that represents the business model;
- Fig. 13 is a graphical display for adding or editing indicators
- Fig. 14 is a graphical display for importing tables from a database
- Fig. 15 is a graphical display for linking a category to the database
- Fig. 16 is a graphical display for linking a connection to the database
- Fig. 17 is a block diagram of a system for retrieving business data from at least one enterprise utilizing the business model, including a model engine and query engine, which are components of the business context engine, and a projection engine, which is a component of the gateway.
- Fig. 18 is a block diagram of the model manager showing how the business model is implemented and utilized by the model manager in accordance with one embodiment of the invention.
- Fig. 19 is a flowchart of the steps used by the model manager to automatically retrieve business data requested by the client user;
- Fig. 20 is an example of a business model
- Fig. 21 is a table, entitled “month costs & turnover,” in the database associated with the business model of Fig. 20;
- Fig 22 is a table in the database associated with the business model of Fig. 20, entitled “client costs & turnover”;
- Fig. 23 is a table in the database associated with the business model of Fig. 20, entitled "month table”;
- Fig. 24 is a table in the database associated with the business model of Fig. 20, entitled "office table”
- Fig. 25 is a table in the database associated with the business model of
- Fig. 26 is a table associated with the business model of Fig. 20, formed in implementing relationships created by the model manager, entitled “indicator table”
- Fig. 27 is a table associated with the business model of Fig. 20, formed in implementing relationships created by the model manager, entitled “indicator property table”;
- Fig. 28 is a table associated with the business model of Fig. 20, formed in implementing relationships created by the model manager, entitled "aggregation table";
- Fig. 29 is a table associated with the business model of Fig. 20, formed in implementing relationships created by the model manager, entitled "aggregation differential level table";
- Fig. 30 is a table associated with the business model of Fig. 20, formed in implementing relationships created by the model manager, entitled "differential level table";
- Fig. 31 is a table associated with the business model of Fig. 20, formed in implementing relationships created by the model manager, entitled “category table”;
- Fig. 32 is a table associated with the business model of Fig. 20, formed in implementing relationships created by the model manager, entitled "allocation table";
- Fig. 33 is a block diagram of a system which allows client users to access and retrieve business data through the business context engine;
- Fig. 34 is a flowchart of steps used in rendering data at a client, based on an template defined by a server using JavaScript;
- Fig. 35 is a sample template containing the keyword #SESSIONDATA
- Fig. 36 is a file showing the result of merging the sample template in FIG. 35 with session data for a simple table
- Fig. 37 is the table created using the file of Fig. 36;
- Fig. 38 is an enlarged view of the report explorer panel in page view;
- Fig. 39 is an enlarged view of the results panel in page view
- Fig. 40 is a graphic display of a standard page in page view
- Fig. 41 is a graphic display of a dimensions page in page view
- Fig. 42 is a graphic display of a totals page in page view
- Fig. 43 is an enlarged view of the report panel in page view
- Fig. 44 is a graphic display allowing a user to log in and simultaneously request a personalized monitor
- Fig. 45 is an example of a business model
- Fig. 46 is a monitor based on the business model of Fig. 45. Detailed Description of Specific Embodiments
- browser means a software application program that is designed to facilitate browsing of data or programs on a network, such as the World Wide Web, by finding desired data and displaying it in understandable form.
- a web browser is a client program that uses HTTP or another similar language to request services from another computer somewhere in the Internet.
- client/server as used herein means the relationship between two computer programs in which one program, the client, makes a service request from another program, the server, which fulfills the request.
- the Web browser is a client program that requests services from another computer somewhere on the Internet.
- display shall mean the presentation of information in a format such as numerical, graphical or auditory.
- network device shall mean any device that can be connected to and communicate over a communication network.
- financial accounting processes shall mean a system used by an enterprise to generate at least one of a balance sheet, statement of earnings or other similar reports.
- indicator as used herein means a type of data, pertinent to performance of a business, which can be viewed according to at least one category.
- category as used herein means a grouping by which a user can view data corresponding to an indicator. A category may include multiple instances, such as the category "month” containing instances of January, February,..., December.
- Real world data defined by category(s) and indicator(s) combinations do not necessarily map directly to data in a database system.
- the term "parameter” as used herein means a single value or a matrix of values which is/are derived from an indicator and category combination.
- value as used herein means a numerical, textual, graphical or auditory representation of data or information.
- the term “drill-down” as used herein means an action causing presentation of data which typically provides underlying or additional detail to information currently being presented. A drill down, for example, may be performed on a parameter derived from a category(s) and indicator(s) combination by selecting a trend symbol pertinent to that parameter, causing data that pertains to the cause or effect of the trend to be presented.
- Data presented may be hierarchically related to the information currently being presented. For example, a drill down may be performed on a parameter derived from a category(s) and indicator(s) combination by selecting an instance of a category, whereby data of a category hierarchically related to the selected instance of the category is presented as it pertains to the indicator.
- Fig. 3 shows a system for retrieving business data from at least one enterprise in accordance with one embodiment of the invention.
- databases from multiple enterprises 2902, 2904, 2906, 2908 can be rapidly accessed and the data displayed in personal reports to a variety of end users 2916.
- the business model which is created by an administrator, maps the data that can be requested by a user to the data contained in the databases 2914.
- the databases 2914 may be spread across multiple enterprises or corporations 2902, 2904, 2906, and 2908.
- Data is not moved to secondary systems, such as a data warehouse. Rather, information available in the course of operation of at least one enterprise is accessed directly at the source of data, and aggregated for short term use. In this manner, business data can be accessed in substantially real-time, supporting the needs of E-commerce. Additionally, since business data is accessed at the source, the various enterprises 2902, 2904, 2906, and 2908 do not lose exclusive rights to the data, as with a datawarehouse.
- the data system utilizes the business model to map the business data requested by the user to the database.
- the proper data sources are then queried and the resulting data is retrieved and aggregated.
- the system In high-speed E-commerce, the system must respond quickly to the user, and therefore analytical processes, designed for analytical accuracy and completeness rather than speed, are not performed by the data system.
- JavaScript templates are used providing personalized, interactive information to individual end users 2916 in either page view 3002, shown in Fig. 4, or a monitor 3102, shown in Fig. 5.
- Information is presented in an easy to read fashion that requires minimal end-user training and does not require the end-user to know the underlying datastructure of the databases nor the location of each database. For example, using standard browser technologies, users are able to view a high-level monitor 3102 and drill down to find details concerning trend changes of the information they are viewing. Because the monitors are built using templates, customers are able to rapidly customize their look and feel to suit their particular requirements. In this manner, only pertinent data is shown.
- monitors 3102 are easily customized, business data can be properly presented, in real-time, to all levels of client users, allowing them to quickly take action when problems arise.
- the monitors 3102 are constructed around trend markers 3104, which provide a graphical display of a trend in business data over time. By managing these trend markers 3104, client users can quickly avert problems before they affect the financial performance of a company.
- Fig. 6 shows a system 218 for quickly and automatically accessing information from databases 210 of multiple enterprises on a network 217, based on a request for that information by a client user 206 on a client browser 207.
- Business data from multiple databases 210 on a network can be viewed, combined, and processed according to different lines of user inquiry.
- the user inquiry for business data is linked to a business model of the database(s), whereupon requests are sent to each database to retrieve the data.
- the retrieved data is then sent back to the user in the desired format.
- the network 217 may include wireless and satellite communications, and is not limited to the Internet.
- the client 219 may be a computer, mobile device, such as, a handheld personal digital assistant, a cellular phone, or a pager.
- the system 218 may be implemented, in part, as a computer program product having computer instructions for use with a computer system.
- Such computer instructions can be written in a number of programming languages for use with many computer architectures or operating systems. Such languages include, but are not limited to, C and C++.
- an end user 206 on a client browser 207 sends a query to a web server 208 over a network 217.
- a gateway 209 receives this request and forwards it to a business context engine.
- the business context engine queries, transforms, and aggregates data from the various databases, operational stores or caching systems 210.
- the business context manager 201 then delivers a response back to the user 206 via the gateway 209.
- the business context engine 201 consists of three different managers: a portal manager 202, a storage manager 203, and a model manager 204.
- the portal manager 202 serves as the interface between the gateway 209 and the storage manager 203 and model manager 204.
- XML data requests sent by the gateway 209 are forwarded by the portal manager 202 to either the storage manager 203 or the model manager 204.
- the portal manager Upon receiving the requested data back from a manager, the portal manager consolidates this information into XML messages, which are sent back to the gateway 209.
- the model manager 203 manages the business model.
- the business model can be represented as a two dimensional graphical representation, where all the enterprise's individual business data resources are displayed as an intersecting set of "categories" and "indicators", which shall be explained more thoroughly below.
- This business model maps the requested business data to the data that is stored in the various databases.
- the model manager 203 can receive XML requests for data from the portal manager 202, map the requested data to the database, and retrieve the requested business data by generating an appropriate command to the database, such as an SQL query. Retrieved data is sent back to the portal manager 202, whereupon the data is sent back thru the gateway and ultimately received by the client browser 207.
- the storage manager 204 manages and temporarily stores the data compiled by the other managers in the business context manager 201. Additionally, the storage manager 204 stores administrative data, which includes, for example, the business model 213, reports, and end user rights for accessing data or a particular business model 213.
- the client users 206 interface with the business context engine 201 via their client browser 207 using page view 214 or monitor 215 tools.
- Fig. 4 is an example of page view.
- Page view 214 allows the client user 206 on the client browser 207 to select indicators and categories contained in the business model, which are then forwarded to the business context engine 201. Based on the selected indicators and categories, the business context engine 201 derives parameters using the business data. These parameters are then forwarded to the client user 206 and displayed.
- Monitors 215 are another means by which the system displays information to the end user. An example of a monitor is shown in Fig. 5. In addition to showing business data associated with a predefined template, monitors 215 provide a set of simple, visually orientated, trend symbols 3104 (Fig.
- a trend symbol 3104 the end user 206 will be provided detailed information related to the selected trend symbol. This detailed information may also have trend symbols which allow a user to visually narrow the reasons for trend changes of the originally selected trend symbol.
- Administrators 212 control and manage the data system 218 through an architect tool 211. For example, using the architect's semantic modeling technique, the business model can be created.
- the Business Context Engine 201 communicates with the Web Server 208 via the XML Bus 216.
- the XML Bus 216 uses channels as an abstraction layer that hides the physical location of the services. Thus, all connections are made between services and processes instead of actual machines. Messages in the XML bus 216 are communicated between processes via channels, with multiple processes able to send data to the same port at the same time. In addition, more than one process may receive messages from the same port simultaneously. In other words, the bus allows "many-to-many" relationships between sending and receiving processes such that multiple client users may engage in requesting data simultaneously.
- the model manager 204, the architect 211, the gateway 208, and the end user interface, which includes page view 214 and the monitors 215, will now be examined in more detail.
- the model manager through the creation and management of a business model, accesses the information contained in the various data sources.
- the business model 301 serves as a link between the business data in the sources 303 and the analytical software 302.
- the information required for composing reports, such as monitors and page views, is extracted using the business model 301 by mapping the business data requested to the data sources 303.
- the business model 301 is represented by a two-dimensional grid that consists of indicators, categories, and relationships. Types of data pertinent to performance of a business are called indicators, and may include, but are not limited to, numerical, textual, graphical, or auditory values.
- the indicators 401 are located on the left-hand side, or Y-axis, and include "cost", "revenue", and "profit”. Many indicators are directly retrieved from the information sources in which data is stored. Indicators may also be calculated; such indicators may be referred to as derived indicators.
- Indicators can be viewed in different groupings, called categories.
- the categories 402 are located on the bottom, or Y-axis and include "day”, “month”, “year”, “employee”, “function”, "office", “region”, and "country”. Categories can be mutually related, where one category is a refinement or subset of another category. For example, the category "year” has a one to many relationship with the category "month”, in that each year consists of twelve months.
- a user looking at cost data using the "year” category can th is drill down by selecting cost data to be displayed by the category "month” for a given "year”.
- Other relationships between categories are shown, such as between “day” and “month”, “month” and “year”, “employee” and “function”, "office” and “region”, and “region” and “country”. Relationships can exist not only between categories, but also between indicators and categories, between multiple indicators, and between multiple categories.
- the indicator, "cost” may be a derived indicator, such that, it is composed of the sum of "variable costs” and “constant costs”.
- the indicator "cost” can then be displayed by various categories, which may be derived categories of the derived indicator "costs”.
- the element "variable costs” of the derived indicator "costs" for a computer business may be displayed by the categories which form the variable costs, for example, “bonuses” for employees and "price of components” to manufacture the computers.
- the category “bonuses” may be a derived category such that a bonus for a particular employee may be calculated based upon the formulas "if revenue > target + 10% then 10,000 bonus", "if revenue > target +20% then 20,000 bonus” and "else no bonus” and then all bonuses are summed for each employee to provide the indicator, "variable cost” for the derived category of "bonus".
- complex relationships may be made within the business model. It should be understood that such categories and indicators are based on a concept which defines a business and are abstract from the underlying databases and business data until connections are made between the business data and the category-indicator business model.
- connection points on the intersections of the grid affirm the relationship between the indicator and category, and indicate which indicators 401 can be viewed for which categories 402, such as "revenue” per "country".
- a connection point indicates that for a given indicator and category combination, ⁇ Ij, C j ], a parameter P -, can be derived from the business data.
- the "revenue” indicator can be viewed by the "day” category.
- Information may not be available for all possible combinations of indicators 401 and categories 402. This is represented by a lack of a connection point at the intersections between the categories and indicators on the grid. For example, cost per day can not be retrieved from the business model shown.
- the data may not be available in the data sources, or may be protected.
- Indicators categories, and the relationships between the categories and indicators define the business model.
- various business models can be construed.
- three elements are shown that form a business model 501: hours information 502, market survey 503, and time parameters 504.
- These elements may be used to build additional business models, for example, a business model for the chief executive officer, a btisiness model for the marketing department, or a business model for the sales staff.
- Business models built from the same elements are stored in a business model store 213 (see Fig. 6).
- a business model store 213 is a database or file that contains one or more business models.
- Fig. 10 The business model is created and stored by administrators using an architect module 211 (see Fig. 6).
- categories and indicators are first entered, step 601, to form a graphical representation consisting of a two dimensional grid. This may be accomplished by using displays similar to those shown in Figs. 11, 12, and 13.
- Fig. 11 is a general display 618, containing a menu bar 610, a toolbar 612 and a status bar 616. Also within the display 618, are four panels 614, which can be used to contain the grid representing the business model, as detailed in Fig. 12.
- the bottom-left panel 622 is empty.
- the upper-left panel 620 contains the indicators, while the bottom-right panel 624 contains the categories.
- the two dimensional grid that connects the entered categories and indicators is represented in the upper-right panel 626.
- a menu is provided, Fig. 13, which allows the administrator to add or edit indicators.
- the menu also allows the administrator to specify derived indicators. Categories, and the relationships between categories, can be defined in a similar manner by selecting the bottom-right panel 614.
- the connections between the categories and indicators are entered next, step 602.
- a grid appears in the upper-right panel 616 upon entering a category or indicator.
- a connection point 618 can be added to an intersection point on the grid. In various embodiments, this can be done by selecting an intersection point and entering the desired connection. Three types of connections are utilized.
- Block Query designates a blocked connection that prevents specific users from obtaining data for the indicator/category combination.
- the available databases are defined, step 603.
- One typical method used in linking with a database is to import the database definitions by retrieving the data dictionary of a database. When databases are not available during design of the business model, database definitions may also be entered manually. In this manner, a list of databases, along with available tables, fields, and keys is created.
- Fig. 14 is a graphical display for importing tables from a database.
- the administrator enters the Data Source Name (DSN), and selects Table in the Import group box.
- the Browse and Select option is selected.
- browse the administrator can then select the tables to be imported.
- the indicators, categories, and connections are then linked to tables, fields, and keys in the databases in step 604.
- Figs. 15 and 16 are examples of a graphical display for linking a category and connections to the database, respectively. Connections that are linked to more than one table may be prioritized, such that the table with the highest priority is consulted first.
- a parameter P derivable from the business data, represented by a connection on the two dimensional grid, that is susceptible to change over time.
- a computer process distinct from any financial accounting process retrieves data automatically based on a client user's data request for the presentation of one or more parameters.
- three subengines, a model engine 73, a query engine 72, and a projection engine 75 are utilized to retrieve the data based on the user request, as shown in Fig. 17.
- the model engine 73 and query engine 72 are components of the business context engine 201 (Fig. 6), while the projection engine is a component of the gateway 209 (Fig. 6).
- the projection engine scans a desired report layout 77 containing the user request and forwards to the model engine 73 the desired information type in the report.
- This may be accomplished by a look-up table which has an associated thesaurus of commonly used terms such that a user's request is translated to terminology used within the business model. In this manner, for an indicator and category pair, a result subset ⁇ . . .
- the model engine forwards a request for data specifying a specific field from a table in the database to the query engine 72.
- the query engine 72 retrieves data from the database 71 by generating SQL commands, whereupon the business data is used to derive values P r? (Step 9103) of Fig. 10A.
- the model engine can associate desired information in a query with multiple category and indicator combinations, in addition to a category and indicator pair.
- a parameter set S ⁇ . . . , P v ⁇ can then be defined for all V for which a parameter P v exists. Pursuant to the query, a result subset ⁇ . . .
- P w ⁇ of the parameter set S is defined, where W is an element of the set of all N's for which a parameter P v exists.
- the business data is then used to derive parameter values P w .
- desired information may be associated with two categories, "month” and “employee", and the indicator "cost”.
- the parameter value P w derived from the business data would then contain values for cost as it pertains to each month, with each month's cost value broken down by employee.
- Fig. 18 shows how the business model is implemented by the model manager in accordance with one embodiment of the invention.
- the business model comprises a user model and a technical database model.
- the administrator defined categories, indicators, and connections are part of the user model.
- the technical database model includes the categories, indicators, and connections that represent the underlying content and structure of the database(s).
- Each technical database category has a complete definition of all instances along with a link to the underlying database structure.
- the location of each technical database indicator and category in the database is defined.
- the user model maps to the technical database model, which further maps to the underlying database.
- Blocks 80 and 81 contain the indicators and categories as defined by the administrator, respectively.
- block 81 maps the administrator defined categories to the categories in the technical database model, and defines the relationship between categories.
- Block 82 identifies which indicators are not connected to any category in the database. Data for such indicator/category combinations are not available in the database. For example, in Fig. 7, the indicator cost is not available for category day, and therefore the lack of this combination would be indicated in block 82.
- the combination of blocks 80, 81, and 82 correlate to how the administer envisions the data, so as to allow the user to formulate a data request.
- blocks 83 to 86 represent the technical database model, and comprise of tables that are used to map the user model to the categories, indicators, and connections found in database.
- Block 83 provides the database location of each indicator defined by the administrator in block 80, including the database, the table, and the column. Some indicators may be located in more than one location in the database, and hence are listed multiple times.
- Block 86 connected to block 81, describes where each technical database category is defined in the database, so that information such as keys and category instance names can be derived.
- Block 85 then couples the categories, now defined by both the user and technical model, to the indicators. This is done by providing the location of where the categories can be found in the database in relation to the indicators.
- some categories may be located in more than one table in the database, and therefore are listed multiple times.
- a list of the database tables that contain data pertaining to indicator /category connections is found in block 84. This table is referenced by blocks 83 and 85, when providing the location of the categories and indicators.
- Fig. 19 is a flowchart whereby the model manager, using the blocks described above, automatically retrieves data requested by the user in accordance with one embodiment of the invention.
- the user requests data that relates to a connection associated with an administrator defined category and indicator using a monitor or a page view, step 902.
- the requested indicator is then mapped to the appropriate database table, step 904, correlating to block 83 in Fig. 18.
- the requested category is mapped to it's corresponding category as defined in the technical database model, so that key and instance names can be retrieved, step 906, and also mapped to a table(s) in the database that is cotipled to the indicator(s), step 908, correlating to blocks 86 and 85, respectively.
- the order of the steps 904, 906, and 908 is not important and can vary.
- Fig. 20 is a business model 101 as defined by an administrator, in accordance with one embodiment of the invention.
- the example is implemented with a single database having five tables, Figs. 21-25, although this methodology is equally applicable to multiple databases and multiple databases in multiple enterprises.
- Figs. 26-32 represent the tables formed in implementing the relationships created by the model manager. Based on a desired report layout, such as the one shown in Fig. 3, the model manager maps the requested data to the database, and forwards the database location of the requested data to the query engine.
- Fig. 26, which corresponds to block 81 of Fig. 18, identifies the indicators defined by the administrator which are available to a user. These indicators are shown on the left hand side of the business model of fig. 20, and include "number of personnel" 103, "turnover” 105, and “costs” 107.
- the categories defined by the administrator are identified in Fig. 31, which corresponds to block 80 of Fig. 18.
- the six categories 109, 111, 113, 115, 117, and 119, defined by the administrator map to only four categories in the database that have instance identifiers (database category ids 1-4).
- database category ids 1-4 For example, the administrator has defined two categories, order office 113 and client office 117.
- only one table (Fig. 24) in the database relates instances pertaining to the category office to the database.
- the administrator defined categories ordering office 113 and client office 117 are therefore equal to each other at the level of the database, each being mapped to the database category office.
- the user can drill up or down on an instance of a category by opening a category that either reports above or below it, respectively. For example, the user may view data under the category "year”. By selecting a particular instance of the category "year”, and the category “month”, the user can then view data by "month” within each "year”, which reports above to "month”.
- categories "year”, “ordering-working unit”, and “client working-unit” report above to categories "month”, "order-office", and "client office”, respectively.
- Each of these relationships can be categorized as being one to many. For example, order-working unit Gelderland has two order-offices, Apeldoorn and Arnhem.
- Fig. 30, corresponding to block 86 provides the name of a table and corresponding column name for each of the four categories in the database, wherein instance names and keys for each category are defined. For example, if the user requests information for the month of January, the category "month” is first looked up in Fig. 31, which provides a dl id of 1. Using dl id 1 in Fig. 30, the dl-table named “month-table” is identified, along with column name id "month id" and dl-colname-name "month name”. The model manager accesses the "month-table" table in the database of Fig. 23, and looks up "January” under the month-name column, and finds under the "month id” column that the number 1 represents January in the database.
- Fig. 28 lists the tables in the database which contain data associated with both an indicator and category. Only two tables are shown in this example, the month-costs & turnover table, and the client- costs & turnover table, having corresponding table identifiers of 1 and 2, respectively. These tables may be used in the following manner. Indicator "turnover" in Fig. 27, has a table identifier of both 1 and 2, and thus can be found in both tables, while the indicator "number of personnel" has a table identifier of 2 and can only be found in the client-costs & turnover table.
- Fig. 29, corresponding to block 85 lists the administrator defined categories, which are associated to a technical database category, and the location of where the categories, coupled to indicators, can be found in the database by referencing the appropriate table id. Certain user categories appear more than once in the database, and thus are listed more than once in Fig. 29. For example, both client-office and client working unit can be found in tables 1 and 2. Additionally, Fig. 29 lists the appropriate database category id, so that category instances can be cross-referenced to their identifiers in the database using Fig. 30 (see above). When data pertaining to an indicator-category combination is requested, the common table id of the given indicator and category is determined, using Figs. 27 and 29. Data can then be retrieved from the table corresponding to the common table id and processed if necessary.
- a so-called non-available can be generated for selected items within a category where no indicator data is available, such that the system does not malfunction. This can be illustrated in Fig. 21, where for months other than January and February no turnover data is available. Data for January and February is retrieved and for missing months a non-available symbol is provided. The final results are produced on the basis of the months defined in Fig. 23 rather than on the basis of available months in Fig. 21.
- derived indicators or categories are defined by an administrator and associated with a formula.
- the value of the derived indicator or category is calculated by the model manager using the associated formula.
- the derived indicator is not stored in the database(s).
- the model manager using the associated formula, retrieves the required data pertaining to indicators revenue and cost from the database(s) to derive profit. Profit is not stored in the database, but calculated based upon a user query.
- FIG. 19 An example illustrating how Figs. 19-32 are used to gather information is presented, according to one embodiment of the invention.
- a user requests, in step 902 (Fig. 19), information pertaining to indicator "number of personnel" and category "client working tmit", as defined by the administrator.
- This information is represented by connector 121 shown in the two dimensional business model of Fig. 20.
- the indicator "number of personnel” is first mapped to the database, step 904. Using Fig. 26, the indicator name “number of personnel” correlates to indicator identifier 3. This indicator identifier is utilized in Fig. 27, to determine that the indicator "number of personnel" can be found in one table in the database, represented by ag id no. 2. Using Fig. 28, ag id no. 2 correlates to the client-costs & turnover table, shown in Fig. 22.
- requested category "client- working unit” (category identifier 6) has a technical database category dl-id of 4.
- client-working unit corresponds to the category "working unit” in the technical database.
- instance names for the category "working unit” may be found in the "working unit-table", which corresponds to Fig. 25 - NH corresponds to Noord-Holland, GR corresponds to Groningen, and GE corresponds to Gelderland . Note that Fig.
- dl-id 3 corresponds technical database category "office” and refers to dl-table-name "office table", wherein the relationships between offices and working offices can be found.
- the requested category is then mapped to tables in the database that are coupled to indicators, step 908.
- the category client working unit is found in two tables of the database, with table ids of 1 and 2.
- table ids of 1 and 2.
- Fig. 28 these tables are defined as the month-costs & turnover table, Fig. 21, and the client- costs & turnover table, Fig. 22, respectively.
- the table in the database which contains the desired indicator and category information can then be identified, step 910.
- the indicator "number of personnel” is found in the client-costs & turnover table, Fig. 22, and that the category "client working unit” is located in both the month-costs & turnover table, Fig. 21, and client-costs & turnover table, Fig 22.
- the table which contains both the indicator and category is the client-costs & turnover table, as shown in Fig. 22.
- this table may also prioritize the connections between indicators and categories, as discussed above.
- the data is then retrieved from the database 912 using the client-costs & turnover table, Fig. 22.
- Fig. 33 shows a system which allows end users on a client machine 2304 to access and retrieve data through the business context engine 2302 in accordance with one embodiment of the invention.
- the client machine communicates with the business context engine via a network 2310, which may include mobile and satellite communications, and is not limited to the Internet.
- the client 219 may be a computer, mobile device, such as, a handheld personal digital assistant, a cellular phone, or a pager
- a client user at a client machine 2304 which is coupled to a network 2310 and in communication with a remote server 2308 makes a request for presentation of a business concept in the form of indicators and categories forming one or more parameters
- This communication may be initiated at the browser 2309 of the client 2304 by using either a hyperlink or form
- the request is in the form of a CGI request for execution of script at the server
- the user may need to access one of a multitude of databases
- identifiers which are representative of data which resides m the databases
- This representative data may be category and indicator combinations or direct calls to the underlying database structure
- the server 2303 accesses the CGI bin and interprets the requested script
- the script communicates with a secondary processor 2302.
- the secondary processor 2302 is the business context engine 2302, or alternatively, the same processor utilized by the server 2308
- the identifiers are used to retrieve business data which is used to derive parameters P rs .
- After deriving the parameters P r involve the secondary computer 2302 forwards the parameters P rs back to the server 2308.
- Such communication is conducted via an XML bus 2301 using XML request and response messages 2307.
- a webserver application is designed such that HTML rendering of the requested data is not performed at the web server 2308, but m the client process which is running on the client user's machine In this manner, the burden of rendering the data at the server 2308, which typically is processor intensive and subject to scalability problems, is removed and distributed to client machines
- the web sen. er 2308 application utilizes HTML templates.
- These HTML templates include an HTML body wrapper. Such body wrappers do not provide rendering information but only information so that the HTML is recognized by an HTML enabled browser.
- the JavaScript within the HTML • wrapper creates a graphical presentation of the parameters.
- a keyword is inserted into the template.
- the server 2308 replaces this keyword with JavaScript variables that are generated using parameters P -; as received from the secondary computer. Note that the server application does not generate any HTML, nor in this embodiment does it replace any other strings other than the keyword (s).
- the template is sent to the client browser.
- the JavaScript within the template is then executed at the browser at load time to create HTML code, whereupon a display is generated at the client.
- client side rendering of the parameters derived from remote data sources is realized by using JavaScript.
- Fig. 34 is a flowchart illustrating the above method for rendering data using JavaScript in accordance with one embodiment of the invention.
- An HTML template is defined 2402 at the server, which includes an HTML body wrapper and JavaScript. Included in this template is a keyword that is utilized to support the data acquisition.
- Fig. 35 is a sample template, 2501 containing the keyword #SESSIONDATA. The JavaScript in the template 2501 references the JavaScript variables to be merged into it.
- Fig. 36 is an HTML file showing the result of merging the sample template in Fig. 35 with the session data for a simple table.
- the table in this example contains two columns, both with four rows.
- JavaScript and the JavaScript variables, is then transmitted to the client, step 2406 of Fig. 34.
- the JavaScript is interpreted at load- time and rendered on the screen, step 2408.
- the HTML file in Fig. 36 will be interpreted by the client browser at load time to render the table in
- Parameters P r may be presented as, but are not limited to, textual content, graphical content, numerical content, or auditory signals. Additionally, the parameters P r$ may be directly retrieved from the various sources, or may be resultant data calculated from raw data in the various sources.
- Raw data is the most rudimentary data kept in the data sources such that no data exists on which the raw data can be calculated. For example, raw data is total dollar amount for a given month, assuming that there is no total dollar amount for a shorter time period such as day, hour, or minute. Resultant data is total dollar amount for a given year, since it is derived by summing the total amount for a month over a twelve month period.
- a client user utilizing a browser connects to a server over a network, such as the Internet.
- the user requests a business model by sending a signal to the web server. This may occur through a login procedure in which a user identification is associated with a particular business model.
- the requested business model is associated with a predefined template for displaying personalized data, or, alternatively, a list of templates associated with the business model may be presented to the user so that a particular template can be selected.
- the template is a web page which is dynamically constructed based upon a request from a client.
- the template associated with the business model is stored at the server and consists of an HTML body wrapper, containing JavaScript code and a keyword.
- the server acquires the user requested data needed to complete the template from the secondary computer.
- the secondary computer gathers the requested data, and, if necessary, performs various operations on the retrieved data , before sending it back to the server.
- the keyword is then replaced with JavaScript variables that represent the retrieved data.
- the parameters P rs displayed at the client browser may be associated with other business data contained in the multiple databases.
- these associations are organized into a hierarchy of levels, which may have a cause and effect relationship with one another.
- Raw data may be contained at the lowest level, followed by resultant data which results from the raw data at the next higher level, with subsequent levels relying on previous resultant data.
- the template rendered at the client includes an arrangement for controlling the display of parameters P rs , such that associated business data in the database can be selected and displayed.
- a user viewing a level of data can graphically select a different level of data, whereupon a new template is displayed at the client browser.
- the template allows for drilling down of hierarchical data.
- lower level data By drilling down on high level data, lower level data is displayed showing a specific instance of the high level data. For example, assume a lower level category, month, has a one to many relationship with a higher level category, year, and that cost data for the category year is displayed. The category year has instances of 1998, 1999, and 2000. By selecting and drilling down on year 1999, cost data for the next lower level category, month, is displayed. However, rather than displaying for each month the summation of costs over all three years, only costs pertaining to the year 1999 are displayed.
- the template displayed at the client browser may contain graphical trend symbols that indicate the status of a parameter(s) P r _. presented in the display.
- a trend symbol By selecting a trend symbol, drill down occurs and data associated with parameter(s) P rs is displayed to the user in a new template. A user can thus gain insight into why a parameter(s) P rs has or has not changed.
- the associated data displayed is not necessarily related in a hierarchical manner to P r; , but may simply be associated with the trend. For example, if a trend symbol indicates that, for a given P r ,., the cost of bananas is rising, the associated data may pertain to a climate change in Costa Rica for example.
- Fig. 4 shows a typical display 3002 using page view.
- a user on a client browser requests a business model.
- the user is then presented with selectable categories and indicators associated with the business model.
- data is retrieved from the multiple databases using the business model and eventually rendered at the client browser.
- the user may select the graphical representation for displaying the information content, such as numeric representation or various charts and graphs.
- the display 3002 is composed of four panels 3004, 3005, 3006, and 3007, a browser toolbar 3008, and a message bar 3009. The size of each of the panels can be modified according to user needs.
- the message bar 3009 displays the status of the current function being performed in page view. Additionally, descriptions pertaining to highlighted objects are displayed here.
- the browser toolbar 3008 allows the user to select various functions that are typically performed by a browser and which are well known in the art. These may include, but are not limited to: back and forward buttons that allow a user to move backwards or forwards through page view, thus a user may undo certain actions recently performed by using the back button; a print button; a save button; and a home button, which takes the browser out of page view.
- the report explorer panel 3007 located at the top left panel of the page view display, is utilized to control the display of information content.
- Fig. 38 shows an enlarged view of the report explorer panel 3007.
- Various objects are displayed in a hierarchical tree structure. By clicking on the expand icon next to an object, or the hyperlinked object itself, the underlying level of that object is expanded and /or opened.
- Four different types of objects may be displayed. These are libraries 3801, collections 3803, reports 3805, and pages 3807.
- Libraries 3801 and collections 3803 are only used to group reports 3805 into directory structures. As such, libraries 3801 and collections 3803 can be expanded or collapsed, but not opened. Libraries 3801 and collections 3803 are typically defined by subject and /or owner and authorization.
- collections 3803 are made up of one or more reports 3805.
- Each report 3805 is associated with a set of administrator defined categories and indicators, which a user may select from to form a page.
- a report 3805 may contain a plurality of pages 3807. When a report 3805 is selected by a user, the report's 3805 underlying pages 3807 are displayed. Additionally, the name of the report 3805, and the reports's available categories and indicators appear in the report panel 3005 (Fig. 4), which shall be discussed below in more detail.
- a page 3807 is a partial collection of the categories and indicators that belong to the report 3805.
- the data corresponding to the page's associated categories and indicators is retrieved from the database via the business context engine and displayed in the results panel 3007 (Fig. 4) as a table or graph, and may include auditory signals.
- Each page 3807 offers the option of viewing the data in the report 3805 from another perspective or category. While each category in the report 3805 can be used as a page 3807, this is not always done, as not every combination of category and indicator produces information that is useful to the end user. Additionally, if the indicator /category combination is not included in the business model, the information can not be requested.
- the sequence of pages displayed when a report is opened has significance and defines a hierarchical drill down path.
- the drilling down is an action performed on an open page associated with an indicator(s) and category(s) combination.
- the assignments report 3805 in the hour results collection 3803 in the assignments library 3801 contains the following pages: Holding Company 3808, Parent Company 3809, Division 3810, and Assignment 3811.
- the user selects on the holding company page 3808, corresponding to the result panel 3901 shown in Fig. 39.
- the user now drill downs and selects an instance of the holding company category, in this case, Daimler-Benz.
- the top right panel in Fig. 4 is the results panel 3007.
- the data from the databases, organized in pages as described above, is displayed.
- pages are displayed in three different formats - the standard page, the dimensions page, and the totals page.
- a report contains either only standard pages, or dimension pages along with an optional totals page.
- Fig. 40 shows a standard page 4001.
- the category is displayed on the left, which is the main column 4002.
- the following columns are indicators.
- a standard page displays one category, and at least one indicator.
- a dimension page 4101 shown in Fig. 41
- several category columns lie along the X-axis, in place of the indicator columns on a standard page.
- Indicators lie along an imaginary Z-axis. This structure adds an extra dimension to the two-dimensional standard page format in a report.
- several lines of inquiry can be set out next to each other in a table. By clicking on the top-most heading, a drop down list appears allowing different indicators to be selected.
- a totals page 4201 is associated with the dimension pages in a report. On a totals page 4201, the indicators appear in the main column 4203. All the categories on the dimension pages appear to the right of the main column. The category columns 4205 then give you the totals per indicator.
- the report panel 3005 is the bottom right panel in Fig. 4. When a report in report explorer is opened, the report's associated categories and indicators are listed in the report panel 3005. Parameters for a page can be selected using the report panel 3005.
- Fig. 43 is a detailed view of the report panel 4301.
- the report panel 4301 consists of four columns, the icon column 4303, name column 4305, label column 4307, and current reports settings column 4309.
- the name column 4305 the names of the available categories and indicators in the report are listed. These categories and indicators are defined by an administrator and are based on a particular business model.
- the labels column 4307 indicates whether an item is a category or an indicator.
- the icons 4303 corresponding to category or indicator appear in the first, unnamed column.
- the current reports settings column 4305 identifies which, if any, category instances for a category have been selected. Selecting a category instance is applicable to drilling down, as described more thoroughly above.
- an end user 206 may interface with the business context engine 201 using monitors 215, as shown in Fig. 5.
- a template created by an administrator 212, is assigned at the server 208.
- a request for the data required to fill in the template is forwarded to the business context engine 201.
- the business context engine 201 maps the request to the database using the business model, whereupon the multiple sources are queried 210 and the data retrieved.
- the retrieved data is then moved into the template at the server 208, and sent to the client 219 where it is rendered.
- a monitor 215 containing information is initially displayed at the client browser 207 (Fig. 6) without requiring that the user 206 request a particular category/indicator combination. Rather, the monitor 215 displays information based on categories and indicators that have been predefined and typically customized for an end user 206 by an administrator 211. Furthermore, through business logic contained in the business context engine 201, a monitor 215 displays a trend marker which displays status of information displayed, that pertains to at least one category/indicator combination.
- Fig. 5 shows a detailed view of a monitor, 3102 containing trend markers 3104.
- Trend markers 3104 may be based on a mathematical function which is associated with, but not limited to, a plurality of categories or indicators. In various embodiments, the trend marker 3104 indicates whether information displayed has exceeded a threshold, or changed over a period of time. Upon selecting a trend marker 3104, or alternatively the category instance associated with the trend marker 3104, the user is able to drill down on the category instance to acquire more detailed information. This detailed information is displayed at the client browser 207 (Fig. 6) in a new monitor.
- a request for data associated with the trend marker and corresponding category instance is sent to the server 208.
- This request for data is associated with a new template for generating another monitor 215.
- a request for the information required to fill in the new template is sent to the business context engine 201.
- the business context engine 201 retrieves the required information utilizing the business model.
- the retrieved data is sent to the server 208, moved into the template, and forwarded to the client 219 for rendering.
- the new monitor displayed may contain additional trend markers, allowing the user to drill down even further for associated data.
- Fig. 44 is a display 4401 which allows a user on a client browser to log in, by entering a user name 4403 and password 4402, to the data system and simultaneously request a personalized monitor 4404, in accordance with one embodiment of the invention.
- a monitor 3102 shown in Fig.5, is then displayed on the user's client browser.
- Fig. 45 the business model associated with the monitor 3102 is shown.
- the monitor 3102 displays the category " method of transportation" in the left column 3103, and indicators 3105 "planned pipeline revenue", “actual pipeline revenue”, and “forecasted pipeline revenue” in the adjacent columns, respectively.
- trend markers 3104 are displayed, which indicate whether the difference between actual revenue and planned revenue exceeds a predefined threshold defined by the administrator.
- the user drills down by selecting the category instance "truck” 3106, whereupon a request for data corresponding to this instance and trend marker is sent to the server and associated with a new template.
- the data needed to fill in this template is retrieved from the business context engine 201 using the business model, moved into the template, and sent from the server 208 to the client 219 where it is rendered as a new monitor 215, as shown in FIG. 6.
- the new monitor shown in Fig. 46, displays the category "region” 4603 in the left column, and the previously displayed revenue indicators 4605 in the following columns, with data shown limited to category instance "truck".
- New trend markers are shown in the far right column 4604. The new monitor allows the user to perform further drill downs.
- the disclosed method may be implemented as a computer program product for use with a computer system.
- Such implementation may include a series of computer instructions fixed either on a tangible medium, such as a computer readable media (e.g., a diskette, CD- ROM, ROM, or fixed disk) or transmittable to a computer system, via a modem or other interface device, such as a communications adapter connected to a network over a medium.
- Medium may be either a tangible medium (e.g., optical or analog communications lines) or a medium implemented with wireless techniques (e.g., infrared or other transmission techniques).
- the series of computer instructions embodies all or part of the functionality previously described herein with respect to the system.
- Such computer instructions can be written in a number of programming languages for use with many computer architectures or operating systems. Furthermore, such instructions may be stored in any memory device, such as semiconductor, magnetic, optical or other memory devices, and may be transmitted using any communications technology, such as optical, infrared, microwave, or other transmission technologies. It is expected that such a computer program product may be distributed as a removable media with accompanying printed or electronic documentation (e.g., shrink wrapped software), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over the network (e.g., the Internet or World Wide Web).
- printed or electronic documentation e.g., shrink wrapped software
- preloaded with a computer system e.g., on system ROM or fixed disk
- server or electronic bulletin board e.g., the Internet or World Wide Web
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2001233011A AU2001233011A1 (en) | 2000-01-28 | 2001-01-26 | Method and system for the display of business data from multiple sources |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17885300P | 2000-01-28 | 2000-01-28 | |
US60/178,853 | 2000-01-28 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2001055937A2 true WO2001055937A2 (en) | 2001-08-02 |
WO2001055937A8 WO2001055937A8 (en) | 2002-08-01 |
Family
ID=22654171
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2001/002587 WO2001055937A2 (en) | 2000-01-28 | 2001-01-26 | Method and system for the display of business data from multiple sources |
Country Status (2)
Country | Link |
---|---|
AU (1) | AU2001233011A1 (en) |
WO (1) | WO2001055937A2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1385101A2 (en) * | 2002-07-23 | 2004-01-28 | Cognos Incorporated | Static drill-through modelling |
EP1394696A2 (en) * | 2002-07-23 | 2004-03-03 | Cognos Incorporated | Query interface for OLAP cubes |
US8024650B2 (en) * | 2006-03-31 | 2011-09-20 | Microsoft Corporation | Drilling on elements in arbitrary ad-hoc reports |
CN112231035A (en) * | 2020-10-21 | 2021-01-15 | 中国银行股份有限公司 | Business data display method and device |
-
2001
- 2001-01-26 WO PCT/US2001/002587 patent/WO2001055937A2/en active Application Filing
- 2001-01-26 AU AU2001233011A patent/AU2001233011A1/en not_active Abandoned
Non-Patent Citations (1)
Title |
---|
No Search * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1385101A2 (en) * | 2002-07-23 | 2004-01-28 | Cognos Incorporated | Static drill-through modelling |
EP1394696A2 (en) * | 2002-07-23 | 2004-03-03 | Cognos Incorporated | Query interface for OLAP cubes |
EP1394696A3 (en) * | 2002-07-23 | 2006-04-12 | Cognos Incorporated | Query interface for OLAP cubes |
EP1385101A3 (en) * | 2002-07-23 | 2006-07-26 | Cognos Incorporated | Static drill-through modelling |
US7243106B2 (en) | 2002-07-23 | 2007-07-10 | Cognos Incorporated | Static drill-through modelling |
US9075859B2 (en) | 2002-07-23 | 2015-07-07 | International Business Machines Corporation | Parameterized database drill-through |
US8024650B2 (en) * | 2006-03-31 | 2011-09-20 | Microsoft Corporation | Drilling on elements in arbitrary ad-hoc reports |
CN112231035A (en) * | 2020-10-21 | 2021-01-15 | 中国银行股份有限公司 | Business data display method and device |
Also Published As
Publication number | Publication date |
---|---|
AU2001233011A1 (en) | 2001-08-07 |
WO2001055937A8 (en) | 2002-08-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20020059264A1 (en) | Method and system for the display of business data from multiple sources | |
US7607137B2 (en) | Integration of heterogeneous applications | |
US6279033B1 (en) | System and method for asynchronous control of report generation using a network interface | |
US7509591B1 (en) | Generation engine for a treemap display | |
US5748188A (en) | Hypertext markup language (HTML) extensions for graphical reporting over an internet | |
US7945464B2 (en) | Workflow system matrix organization search engine | |
US6647390B2 (en) | System and methods for standardizing data for design review comparisons | |
US6604113B1 (en) | Method and apparatus for providing account information | |
US5710900A (en) | System and method for generating reports from a computer database | |
US5721903A (en) | System and method for generating reports from a computer database | |
US6108686A (en) | Agent-based on-line information retrieval and viewing system | |
US7392255B1 (en) | Federated system and methods and mechanisms of implementing and using such a system | |
US8412741B2 (en) | Product network management system and method | |
US7962512B1 (en) | Federated system and methods and mechanisms of implementing and using such a system | |
US7680856B2 (en) | Storing searches in an e-mail folder | |
US6035298A (en) | Accessing plural independent databases having plural database schemas | |
US8032516B2 (en) | Methods and systems that provide unified bills of material | |
US20070038641A1 (en) | Systems and methods for automated application updating | |
US20020026441A1 (en) | System and method for integrating multiple applications | |
US20050267868A1 (en) | System and method for OLAP report generation with spreadsheet report within the network user interface | |
US20060085742A1 (en) | System and method for network user interface OLAP report formatting | |
US20080109235A1 (en) | Apparatus and method for creating business process workflows within business intelligence systems | |
US20030172082A1 (en) | Method and system for accessing action item information | |
KR20010092785A (en) | System and method of presenting channelized data | |
JP2005538429A (en) | User interface for web browser |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
AK | Designated states |
Kind code of ref document: C1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: C1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
D17 | Declaration under article 17(2)a | ||
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 69(1) EPC (EPO FORM 1205A DATED 17.12.2002) |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase in: |
Ref country code: JP |