Patent Grant
10242406
Field of the Invention
Embodiments of the invention relate to a comprehensive framework for composing and executing analytics applications in business level languages. The comprehensive framework may include information and services directory, an analytics integration workbench, and an analytics integration server.
Description of the Related Art
Comprehensive risk assessment or fraud detection, and analytics applications in general, require access to operational data which may be distributed across independently created and governed data repositories in different departments of an organization. For example, an analytics solution may require data from multiple distributed repositories, external relational or structured sources, internal and external sources of unstructured and semi-structured information, real time external sources such as market data feeds, and real time internal sources such as application and information technology infrastructure events. Further, a particular analytics solution may require that data from these separately managed data sources be fused or combined to create a complete and trusted view to derive better insights.
Getting data from these diverse sources to the warehouse and data marts is often a complicated task. For example, a data architect for risk information may collaborate with a risk analyst to identify what data (often defined using industry standard models or glossaries, which provide a standardized taxonomy of risk data in business terms) and additional risk data (in terms of business level descriptions) should be provisioned in a data warehouse or OLAP cube for use by an analytics application. Once the needed information is identified, the data architect generates schemas for the data in the data warehouse and schemas for OLAP dimensional tables. The architect may then work with the database software developers to compose the data movement scripts (ETL programs) to actually move the data from their respective sources within the enterprise to the data warehouse. That is, the programs to actually obtain the data needed by the analytics solution are created. Once the ETL programs are developed and deployed, the ETL processes may be used to populate the data warehouse and OLAP cube. Only then may the risk analyst access data from the warehouse as needed for a given analytics solution. For example, data from the warehouse are populated in the OLAP cube and data marts for use in various reports and dashboards.
Given this wide distribution of data, a large percentage of the resources devoted to a typical analytics solution are spent in provisioning data for the analytics application.
One embodiment of the invention includes a method for composing an analytics solution. The method may generally include receiving a selection of one or more elements listed in a glossary to include in the analytics solution. At least one of the selected elements is associated with a mapping specifying a function invoked to move data from an underlying data source to a target data store. The method may also include receiving a selection of one or more analytics tools listed in the glossary to include in the analytics solution. At least one of the selected analytics tool is associated with a mapping specifying an instantiation of the analytical tool provided within an enterprise network infrastructure. The method may also include receiving a selection of one or more of the selected elements from the glossary to provide as inputs to one or more of the selected analytics tools and generating, by a processor, a graphical representation of each selected element from the glossary and each selected analytics solution. The graphical representation represents a data flow for the analytics solution.
Still another embodiment of the invention includes a computer-readable storage medium containing a program which, when executed by a processor, performs an operation for composing an analytics solution. The operation may generally include receiving a selection of one or more elements listed in a glossary to include in the analytics solution. At least one of the selected elements is associated with a mapping specifying a function invoked to move data from an underlying data source to a target data store. The operation may also include receiving a selection of one or more analytics tools listed in the glossary to include in the analytics solution. At least one of the selected analytics tool is associated with a mapping specifying an instantiation of the analytical tool provided within an enterprise network infrastructure. The operation may also in include receiving a selection of one or more of the selected elements from the glossary to provide as inputs to one or more of the selected analytics tools and generating a graphical representation of each selected element from the glossary and each selected analytics solution. The graphical representation represents a data flow for the analytics solution.
Still another embodiment of the invention includes a system having one or more computer processors and a memory containing a program, which when executed by the one or more computer processors is configured to perform an operation for composing an analytics solution. The operation itself may generally include receiving a selection of one or more elements listed in a glossary to include in the analytics solution. At least one of the selected elements is associated with a mapping specifying a function invoked to move data from an underlying data source to a target data store. The operation may also include receiving a selection of one or more analytics tools listed in the glossary to include in the analytics solution. At least one of the selected analytics tool is associated with a mapping specifying an instantiation of the analytical tool provided within an enterprise network infrastructure. The operation may also in include receiving a selection of one or more of the selected elements from the glossary to provide as inputs to one or more of the selected analytics tools and generating a graphical representation of each selected element from the glossary and each selected analytics solution. The graphical representation represents a data flow for the analytics solution.
So that the manner in which the above recited features, advantages and objects of the present invention are attained and can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to the embodiments thereof which are illustrated in the appended drawings.
It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.
Embodiments of the invention provide systems and methods for building and executing analytics solutions. Such a solution may provide a comprehensive analytics solution (e.g., a risk assessment, fraud detection solution, dynamic operational risk evaluations, regulatory compliance assessments, etc.). The analytics solution may perform an analytics task using operational data distributed across a variety of independently created and governed data repositories in different departments of an organization. That is, embodiments of the invention provide a framework which allows users (e.g., a risk analyst) to compose analytical tools that can access data from a variety of sources (both internal and external to an enterprise) and perform a variety of analytic functions. As described in greater detail herein, in one embodiment, the framework includes three components: an analytics Information and services directory, an analytics integration workbench, and an analytics integration server.
In the following, reference is made to embodiments of the invention. However, it should be understood that the invention is not limited to specific described embodiments. Instead, any combination of the following features and elements, whether related to different embodiments or not, is contemplated to implement and practice the invention. Furthermore, although embodiments of the invention may achieve advantages over other possible solutions and/or over the prior art, whether or not a particular advantage is achieved by a given embodiment is not limiting of the invention. Thus, the following aspects, features, embodiments and advantages are merely illustrative and are not considered elements or limitations of the appended claims except where explicitly recited in a claim(s). Likewise, reference to “the invention” shall not be construed as a generalization of any inventive subject matter disclosed herein and shall not be considered to be an element or limitation of the appended claims except where explicitly recited in a claim(s).
Further, particular embodiments of the invention will be described with respect to risk analysis. However, it should be understood that the invention more broadly relates to analytics, generally. Accordingly, references to risk analysis are merely illustrative and not limiting.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java®, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The source data 140 is representative of any available data source from the enterprise computing infrastructure 100. For example, data sources 140 may include multiple relational data repositories and operational data stores, structured and unstructured data sources (e.g., document collections), external relational or structured sources, internal and external sources of unstructured and semi-structured information, real time sources 160 such as external market data feeds or internal sources such as application and information technology infrastructure event monitoring. More generally, source data 140 represents any information stream that may be provisioned via an extract transform and load (ETL) process (represented by an arrow 170) or otherwise made available in the data warehouse 150 and OLAP cube 155.
Illustratively, the framework 105 is shown to include three computer server systems 110, 120, and 130, each including a CPU 112, 122, 132, storage 114, 124, 134, and a memory 114, 124, and 126. The computer systems 110, 120, 130 are included to be representative of a variety of computing devices, including stand alone server systems, virtualized systems, server blades or rack mounted servers, as well as virtual computing systems accessed through a cloud-based computing infrastructure, etc. In general, the computer server systems 110, 120, and 130 are each under the control of an operating system (not shown). Well known examples of operating systems include UNIX, versions of the Microsoft Windows® operating system, and distributions of the Linux® operating system. (Note: Linux is at trademark of Linus Torvalds in the United States and other countries.) Of course any operating system supporting the functions disclosed herein may be used.
The processors 112, 122, and 124 are included to be representative of a single CPU, multiple CPUs, a single CPU having multiple processing cores, and the like. The memory 116, 126, and 136 may be a random access memory. While the memory 106 is shown as a single entity, it should be understood that the memory 116, 126, and 136 may comprise a plurality of modules, and that the memory 116, 126, and 136 may exist at multiple levels, from high speed registers and caches to lower speed but larger DRAM chips. The storage 114, 124, and 134 may be a hard disk drive storage device. Although the storage 114, 124, and 134 is shown as a single unit, the storage 114, 124, and 134 may be a combination of fixed and/or removable storage devices, such as fixed disc drives, floppy disc drives, tape drives, removable memory cards, or optical storage.
Illustratively, the memory 116 of computer server 110 includes an analytics information and services directory 115, the memory 126 of computer server 120 includes an analytics integration workbench 125, and the memory 136 of computer server 130 includes an analytics integration server 135. As described in greater detail herein, these applications collectively provide the framework 105 for composing and executing analytics applications in business level languages. That is, using the terms and descriptions for information and applications customarily understood by a risk analyst or appropriate business level person, as opposed to the underlying data sources, databases, and application implementations used within a particular enterprise and understood by programmers, systems architects and data analysts Of course, one of ordinary skill in the art will recognize that the analytics information and services directory 115, the analytics integration workbench 125, and the analytics integration server 135 are shown executing on separate computer systems 110, 120, and 130 for clarity and that these applications may be configured to execute on a variety of different computing platforms. And further, the functionality described for these components may be combined (or further subdivided) in a variety of ways.
In one embodiment, the analytics information and services directory 115 maintains a set of business level definitions of data and analytics applications available to the risk analyst, e.g., a business glossary and a service vocabulary describing the available data and analytics services that may be included in a given analytics solution. The information and services directory 115 also maintains mappings from the business level definitions to the actual implementation or instantiation of the data and applications within the enterprise. For example, a mapping be stored as records in a data database matching a particular business level definition in the business glossary and an underlying data source where data corresponding to the definition may be located. Similarly, for common business analytics methods (e.g., Monte Carlo methods) may be mapped to an instantiation of the analytical tool provided within an enterprise network infrastructure. Thus, the analytics information and services directory 115 provides a formalized definition of what data streams and data analysis tools are available for a given enterprise, and such information may generally be provided in a language used by the risk analyst. The analytics information and services directory 115 also provides information to other components of the framework as needed to map from the business level definitions to the actual data and analytic tools listed in the directory 115. By abstracting out the underlying data and process infrastructure, the analytics information and services directory 115 provides a set of components that is standardized and understandable by the risk analyst, but that is also extendable and reusable. In one embodiment, the terms in the information and services directory 115 may be based on a set of logical models 205 or industry standardized frameworks for representing information within a particular enterprise. For example, in the financial services and banking industries, a portfolio credit exposure, exposure at default models or loss given default models may be used to identify a collection of terms to include in the information and services directory 115
Additionally, the analytics information and services directory 115 may specify mappings used to move data from one location to another (e.g., from an operational data store to a data warehouse or data mart) as needed for a particular analytics solution. For example, data staging and quality engines 235 may be configured to perform extract transform and load (ETL) processes to move data from an underlying operational data store into a data warehouse, data marts and/or OLAP cubes for use by a particular analytics solution. In such a case, the data staging and quality engines 235 may use the information and services directory 115 to map from a particular business term describing data needed of a data analytics application 230 to an actual source of the data, e.g., an operational data store.
Further, the analytics information and services directory 115 may certify an appropriateness of the data (as defined by the business level definitions) for use by the various analytics services in the directory. Similarly, the information and services directory 115 may certify the data transformation and movement functions needed to move the data from different operational data sources and external sources to a data warehouse, data mart, or OLAP cube are available. That is, the information and services directory 115 may certify that the provisioning required to access operational data corresponding to the business level definition is correct. The information and services directory 115 may also certify that the various data sources available in the directory 115 are appropriate for use by a given analytics service.
The analytics integration workbench 125 provides a compositional tool of the framework 105. In one embodiment, the analytics integration workbench 125 includes a canvas and palette used by a risk or data analyst to compose an analytics solution. Such a solution may reach across any aspect of the enterprise to obtain data described in the services directory 115 needed for the analytics solution. For example, a data analyst may compose a solution which presents a user interface dashboard reflecting a risk analysis performed using data pulled from multiple, disparate sources by the data staging and quality engines 235 within the enterprise and analyzed by the data analysis applications 230 using a variety of techniques (e.g., Monte Carlo or Cornish Fisher methods, etc).
The analytics integration workbench 125 may be used to compose a graphical representation of an analytics solution. In one embodiment, such an analytics solution is represented as a directed graph structure connecting the data sources and analytics services available from the analytics information and services directory 155 (and ultimately, from a variety of sources internal and external to the enterprise). Thus, a risk analyst composes analytics solutions using the standardized set of business terms from the data information and services directory 115. Further, the analytics integration workbench 125 may be configured to encode the graph structure representing a particular analytics solution as a text-based script 210 interpreted by the analytics integration server 135.
In turn, the analytics integration server 135 may parse the script 210 to perform a particular analytics task. In one embodiment, the analytics integration server 135 relies on the information and services directory 115 to resolve the business level references encoded in the script 210 into references to actual data sources in the data warehouse (provisioned using data staging and quality engines 235) and analyzed using the data analysis applications 230. For example, the analytics integration server 135 may be instructed by script 210 to obtain and move data from operational data stores to a data warehouse, obtain information from real time sources, and carry out the actual analytics processes using the data from the data warehouse (and/or real time sources) as specified for a particular solution. In one embodiment, the analytics integration server 135 may be instructed to monitor the states of various data sources within the enterprise and update the data used by a particular analytics solution as appropriate. Further, as described in greater detail below, the analytics integration server 135 may coordinate the activity of multiple disparate processes specified in the analytics solution.
Illustratively, the information and services directory 115 includes an analytics services directory 315, a data transport functions/services 320, and data source mappings 330. The analytics services directory 315 may provide a mapping from a particular analytics tool listed in the service vocabulary 305 to an actual location and description of a process used to provide the named analytics service within the enterprise. For example, the analytics services directory 315 may include a web-services description language (WDSL) document indicating where and how to invoke a particular web service to perform a particular analytics operation on a specified data stream. Of course, a variety of other techniques may be used.
The data transport functions/services 320 may describe the data provisioning or data staging needed to move data from an operational data store (or real time data source) to a data warehouse, data mart(s), or OLAP cube. For example, the data transport functions/services 320 may specify a particular ETL process used to provision data corresponding to a term in the business glossary 310 or needed by an analytics service 305. Similarly, the data source mappings 330 may specify mappings from terms in the business glossary 310 to actual data sources.
As shown, the analytics information and services directory 115 may also include a collection of interfaces used by components of the framework 105 to provide a comprehensive framework for composing and executing analytics applications in business level languages. In this example, the information and services directory 115 includes an administrative interface 335, workbench interface 340 and an integration server interface 345. In one embodiment, the interfaces may each provide a collection of API calls allowing the information and services directory 115 to interact with other components of the framework. For example the administrative interface 335 may be used to update the service vocabulary 305 or business glossary 310 with new (or updated) analytical tools or terms available to the risk analyst for composing an analytics solution for a given enterprise or to update the mappings from either the service vocabulary 305 or the business glossary 310 to any of the analytics services directory 315, the data transport functions/services 320, or the data source mappings 330.
The workbench interface 340 may include a set of routines used by the analytics integration workbench 125 to present a palette of items from the service vocabulary 305 and/or business glossary 310 to a risk analyst composing an analytics solution. Similarly, the integration server interface 345 may include a set of routines used by the analytics integration server 135 to obtain the location and invocation mechanism (e.g., a WSDL based description) for an analytics service listed in the services vocabulary 305. The integration server interface 345 may also specify the appropriate ETL processes to invoke in order to move and/or provision data for such an analytics service included in a given analytics solution.
Data sources/data feeds 420 may include any of the data sources within an enterprise as well as external data sources or feeds. For example, in addition to any internal source of structured, unstructured or semi-structured information within the enterprise, real time external sources such as market data feed may be represented by icons in the data sources/data feeds 420. For example, the data sources/data feeds 420 could include references to public and/or subscription real time data streams, e.g., stock market indexes (e.g., the Dow Jones Industrial average, NASDAQ, or Bloomberg feeds). Risk calculators 425 generally correspond to items listed in the service vocabulary 305 of the analytics information and service directory 115. Examples include historical simulations, Cornish Fisher, Monte Carlo simulations, and any other analytics process or simulation appropriate for the needs of a given case. Portfolios 430 correspond to information defined in the business glossary 310 for a particular enterprise. In particular, the portfolios 430 may describe assets of the enterprise to be evaluated using a particular analytics tool. Common examples for a financial services enterprise include a fixed income portfolio or a forward contract portfolio. Lastly, reports 435 may provide a desired standard structured presentation of the results of a risk calculations or analytics solutions. Like the other information selectable in the palette 405, the reports may be structured according to terms form the business glossary 310, which themselves may be modeled on common or standardized reports for a particular business entity. For example, for the financial services industry, common examples of a standard report could include a portfolio risk report or a trade risk report.
As shown in
In one embodiment, a status of script execution is reflected in environment tables 510. For example, as shown, the environment tables 510 include environment variables 511, logs 512, and data and services availability 513. Each of the environment variables 511, the logs 512, and the data and services availability 513 may be represented as a collection of <key:value> pairs. The environment variables 511 may represent exception events which should result in the interruption of a script as it is being executed. For example, returning to the analytical solution 412, one of the inputs to the historical simulation 450 is an interest rate value 440. In such a case, one of the environment variables 511 could include the current value for the interest rate used in the analytical solution 412. If the value for such an interest rate changes during script execution, then the script interpreter 515 could interrupt the script and re-execute any portion of the script 475 which relied on the value of this environment variable 511.
The logs 512 represent a log of statements of the script 475 that have been successfully executed. Again, using the analytics solution 412 and script 475 as an example, the first three statements of the script 475 correspond to the inputs needed for the historical simulation 450. In such a case, when the script 475 is executed, statements in the log representing the completion of the provisioning of input data sources 440, 465, and 470 may result in the script interpreter 515 selecting to execute the statements in the script 475 which invoke the historical simulation 450. Note, each of the three input statements may be executed in parallel, along with any other statements in the script that do not depend on the results of the input statements for execution. Thereafter, statements may be added to the log 512 indicating that the historical simulation 450 is complete. In response, the script interpreter 515 may select the statements in the script used to generate the report from the results of the historical simulation 450. As a given analytics solution may include a variety different paths of execution, multiple processes (e.g., risk calculators 425) may be executing concurrently with one another. Thus, the script interpreter 515 may orchestrate the execution of a variety of processes to carry out a particular analytics solution using the environment tables 510. Services availability 513 may indicate the status of a given data source or data feed. In the case a needed data source or feed is unavailable, then any statements in the script 475 that depend on that source or feed may block until the data source or feed again becomes available and an alternative to those statements may be executed instead.
As shown, the controller 505 may select one or more script statements 522 from the script 475 as they become ready to execute, based on the environment tables 510. Once selected, the controller 505 may interpret (i.e., decode) the script statement by communicating with the analytics and information serves 115, e.g., through the integration server interface 345 mentioned above. That is, the controller 505 may dereference any references to terms from the service vocabulary 305 or business glossary 310 to an actual data source, process instantiation, or service descriptions corresponding to the business level terms provided the services directory 115.
For example,
At step 610, the analytics information and services directory 115 receives mappings from analytics services to defined services vocabulary terms. At step 615, the analytics information and services directory 115 may receive data transport functions/services needed for a particular data source or analytical service mapped to a business level glossary term or service vocabulary element defined at steps 605 or 610. For example, a data analyst may evaluate an enterprise networking infrastructure to trace form terms and analytics tools in the glossary to the actual underlying data sources where data corresponding to a term may be found or where the instantiation of a given analytics tool is made available. The data transport functions/services specify the appropriate extract transform and load (ETL) processes used to move data from a given operational data store or data feed into a data warehouse, data marts and/or OLAP cubes as specified by data source mappings or used to move data as needed for a given analytic service. At step 620, the information and services directory 115 may publish the service vocabulary 305 and the business glossary 310 to the workbench 125 and the integration server 135. Thus, the service vocabulary 305 and the business glossary 310 reference the data sources and analytic tools available to include in a given analytics solution. Further, once published the workbench 125 and the integration server 135 may interact with the analytics information and services directory 115 to present a palette used to compose an analytics solution using the business level terms provided by the service vocabulary 305 and the business glossary 310 (in the case of the workbench 125) and to identify the needed ETL processes and analytic services to invoke when executing a given analytics solution. Steps 605, 610, and 615 can performed in any sequence, and repeatedly over time.
At step 715, the user may connect a selected element to an analytics solution being composed on the composition area of the workbench 125. For example, the user may select to supply data (as represented by a business level term form the business glossary) to an analytics process (as represented by a risk calculator). Similarly, the output of the analytics process may be connected to other analytic tools, to a data store (e.g., a data warehouse) or to a presentation or report supplied to the user (e.g., a dashboard display that updates as data changes over time). Once the user completes composing an analytics solution, at step 720, the integration workbench 125 may generate a graphical representation of the selected element, connected to the analytics solution being composed as specified, and present it on the composition canvas. In one embodiment, the integration workbench 125 may validate the connections in a solution being composed to prevent a user from composing a non-functioning solution (e.g., an analytics solution with repeating loops or one in which an analytic service is not provided with a required input). At step 725, if the user has not completed composing the analytical solution, then the method returns to step 705 where additional elements may be added to the analytics solution being composed. Once complete, at step 730, the integration workbench 125 may store a directed graph representing the analytical solution. At step 735, the workbench 125 may traverse the directed graph to generate a text based script encoding of the analytics solution. The palette in the workbench may include special tools to organize the information received from the information and services directory 115 and present it to the risk analyst in an intuitively navigate-able hierarchy.
At step 815, the statements selected at step 810 may be passed to a controller 505 of the script interpreter 515. And in response, at step 820, the controller 505 may dereference one or more business level references in the selected statements. For example, the script interpreter may interact with the information and services directory 115 to obtain mappings from the business level references in the statements to the underlying data and process infrastructure. Once the mappings are obtained, the script interpreter may execute the script statement, e.g., by invoking a client stub of an RPC call. Accordingly, at step 825, if the statement is a data movement statement, then at step 825, the script interpreter may invoke an ETL process to move data from one source (e.g., an operational data store or an external data feed) into a data warehouse, data mart(s), or an OLAP cube. At step 832, the results of the data movement statement may be used to update the environment tables maintained by the integration server 135.
At step 835, if the statement is an analytic service, e.g., to execute a Monte Carlo or a Cornish Fisher method, etc., then at step 840, the script interpreter may invoke the analytic service referenced in the de-referenced statement, e.g., by invoking a client stub of an RPC call. At step 845, the script interpreter may receive the results of the invoked analytic service. And at step 850, the results of the invoked analytic service may be used to update the environment tables maintained by the integration server 135. Further, at step 855, the results of the analytic service may be formatted in a report or used to update a dynamic dashboard display, e.g., a dashboard display presented to a risk analyst. Alternatively, or additionally, depending on the particular script, the results of the analytic service may be supplied as the inputs to another analytic service or to an ETL process used to store the results of the invoked analytic service in the data warehouse.
At step 860, the script interpreter may determine whether more statements remain in the script being executed. If not, then the method 800 terminates. Otherwise, the method 800 returns to step 810, where the integration server identifies statements in the script are ready for execution, based on the status of previously executed statements. Note, in one embodiment, a script representing a particular analytics solution may not have an expressed ending point. That is, a script may be configured to run continuously until terminated by a user. In such a case, the script may run continuously to execute the ETL processes to update data in the data warehouse, data mart(s), or an OLAP cube as well as perform the analytic services specified in such a script.
Advantageously, embodiments of the invention provide systems and methods for building and executing analytics solutions. Such a solution may provide a comprehensive analytics solution (e.g., a risk assessment, fraud detection solution, dynamic operational risk evaluations, regulatory compliance assessments, etc.). The analytics solution may perform an analytics task using operational data distributed across a variety of independently created and governed data repositories in different departments of an organization. That is, embodiments of the invention provide a framework which allows users (e.g., a risk analyst) to compose analytical tools that can access data from a variety of sources (both internal and external to an enterprise), analytics services form a variety of internal and external sources, and perform a variety of analytic functions. As described above, in one embodiment, the framework includes three components: an analytics Information and services directory, an analytics integration workbench, and an analytics integration server.
While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5991743 | Irving et al. | Nov 1999 | A |
| 6226649 | Bodamer | May 2001 | B1 |
| 6609123 | Cazemier et al. | Aug 2003 | B1 |
| 6668253 | Thompson | Dec 2003 | B1 |
| 6963826 | Hanaman et al. | Nov 2005 | B2 |
| 7350191 | Kompella | Mar 2008 | B1 |
| 7373633 | Kraiss et al. | May 2008 | B2 |
| 7444342 | Hall et al. | Oct 2008 | B1 |
| 7448048 | Nesamoney et al. | Nov 2008 | B1 |
| 7523106 | Russell et al. | Apr 2009 | B2 |
| 7630956 | Wyatt et al. | Dec 2009 | B2 |
| 7634397 | Suen et al. | Dec 2009 | B2 |
| 7813947 | DeAngelis et al. | Oct 2010 | B2 |
| 7945438 | Balmelli et al. | May 2011 | B2 |
| 8417715 | Bruckhaus et al. | Apr 2013 | B1 |
| 20020099563 | Adendorff | Jul 2002 | A1 |
| 20020107957 | Zargham | Aug 2002 | A1 |
| 20030061246 | Bowman et al. | Mar 2003 | A1 |
| 20030084053 | Govrin et al. | May 2003 | A1 |
| 20040093344 | Berger et al. | May 2004 | A1 |
| 20040093559 | Amaru et al. | May 2004 | A1 |
| 20040138933 | LaComb et al. | Jul 2004 | A1 |
| 20040181543 | Wu et al. | Sep 2004 | A1 |
| 20040216030 | Hellman et al. | Oct 2004 | A1 |
| 20050027683 | Dill | Feb 2005 | A1 |
| 20050096950 | Caplan | May 2005 | A1 |
| 20050209876 | Kennis et al. | Sep 2005 | A1 |
| 20050256892 | Harken | Nov 2005 | A1 |
| 20060212279 | Goldberg | Sep 2006 | A1 |
| 20060225032 | Klerk | Oct 2006 | A1 |
| 20070162444 | Haselden | Jul 2007 | A1 |
| 20070174308 | Rausch | Jul 2007 | A1 |
| 20070239769 | Fazal | Oct 2007 | A1 |
| 20080082490 | MacLaurin | Apr 2008 | A1 |
| 20080091634 | Seeman | Apr 2008 | A1 |
| 20090157419 | Bursey | Jun 2009 | A1 |
| 20090319544 | Griffin | Dec 2009 | A1 |
| 20100218134 | B'Far | Aug 2010 | A1 |
| 20100250574 | Dettinger | Sep 2010 | A1 |
| 20110066457 | Chang et al. | Mar 2011 | A1 |
| 20110066589 | Chang et al. | Mar 2011 | A1 |
| 20110066590 | Chang et al. | Mar 2011 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20110066590 A1 | Mar 2011 | US |
