System and method for providing an aggregation tool

Information

  • Patent Grant
  • 10078868
  • Patent Number
    10,078,868
  • Date Filed
    Monday, March 20, 2017
    7 years ago
  • Date Issued
    Tuesday, September 18, 2018
    6 years ago
Abstract
Embodiments of the present invention assist in the development, management, and deployment of aggregated data attributes for multiple data sources. One embodiment provides a development interface that allows for elements of attributes, including filters, to be moved into a coding area in which an attribute or an attribute element is being edited. In another embodiment, the user interface presents data fields to assist in the development of filters for multiple data sources with divergent formats. The application further provides a validation interface through which users can validate attributes and trace the results returned by various elements referenced by the attributes under validation. Another embodiment provides a system for managing attributes and deploying them to various systems by creating a deployment file that is used by an attribute calculation system. In one embodiment, the attribute calculation system is a scalable system that dynamically calculates attributes for multiple data sources.
Description
BACKGROUND OF THE INVENTION
Field of the Invention

The disclosure relates generally to the field of scoring and prediction and to tools to improve the flexibility and efficiency in generating and evaluating aggregated attributes.


Description of the Related Art

There exists significant interest in information indicative of the relative financial risk or profitability of potential business transactions with individuals or other entities. For example, a lending institution is interested in the relative likelihood of a loan recipient timely and reliably making mutually agreed loan payments. An insurance company is interested in the relative likelihood of claims arising from an existing or potential client. Such predictive information is a factor in deciding whether to engage in a particular business transaction and/or the terms under which a transaction takes place.


A large variety of public records and privately developed databases can be utilized to inform such risk/benefit determinations. For example, credit reporting agencies (CRAs) collect and maintain information on a person's individual credit history. This information can include a total credit line on one or more accounts, current credit balance, credit ratios, satisfactorily paid accounts, any late payments or delinquencies, depth of credit history, total outstanding credit balance, and/or records of recent and/or historical inquiries into the person's credit. Governmental motor vehicle agencies generally maintain records of any vehicle code violations by a person as well as histories of reported accidents. Courts will generally maintain records of pending or disposed cases associated with a person, such as small claims filings, bankruptcy filings, and/or any criminal charges. Similar information also exists for large and small businesses, such as length of the business's existence, reported income, profits, outstanding accounts receivable, payment history, market share, and so forth.


The extensive amount of data available for any given person or entity makes the task of evaluating a business decision regarding the person or entity very difficult. Accordingly, such raw data is frequently processed to facilitate more convenient and rapid financial decisions. For example, a person's raw financial data can be processed to produce a “score” indicative of their relative credit worthiness. Such a score can be utilized in decisions to extend the person or entity further credit and/or as a factor in determining an interest rate to be charged. The evaluation of the relative risk/benefit of a given decision is even more complex when considering multiple persons simultaneously, such as spouses, partnerships, sole proprietorships, joint ventures, LLCs or other entities. When considering multiple persons, raw data from multiple sources about each of the individuals may need to be evaluated.


Attributes can be used to calculate various types of scores and in many instances may be used on their own to guide business decisions as well. Attributes can be aggregated to target various aspects of credit histories, bankruptcy data, and other types of non-credit-based data. For example, a simple attribute could be “consumers who have opened a new credit line in the last 12 months.” The results of the attribute would be a set of consumers who meets both the criteria of having opened a new credit line and having done so in the last 12 months. Therefore, attributes are important in facilitating the use of raw data for a variety of decisions that financial institutions and other entities may need to make.


SUMMARY OF THE DISCLOSURE

Embodiments of the present invention provide systems and methods for creating, managing, and calculating attributes and filters for multiple data sources. One embodiment is an attribute toolbox (ATB) architecture that comprises an ATB user interface (ATB UI) and an ATB engine system.


One embodiment of the present invention is a system for creating and using credit data attributes, comprising an attribute repository for storing a plurality of credit data attributes, a first application server executing a platform-independent user interface application, a credit data repository, and a second application server executing an attribute calculation engine system, wherein the attribute calculation engine system is configured to retrieve credit data from the credit data repository and performs calculations on the credit data in accordance to the attributes in a deployment package generated by the user interface application. In one embodiment, the user interface application further comprises a development interface for editing credit data attributes, wherein the development interface is configured to retrieve the credit data attributes from the attribute repository for editing and return edited credit data attributes or newly created credit data attributes for saving in the attribute repository, a validation interface for testing credit data attributes, wherein the user interface application is configured to execute a validation engine to calculate credit data attributes on test credit data and display the results on the validation interface, and a management interface for managing the deployment of the credit data attributes, wherein the credit data attributes are saved into a deployment package.


Another embodiment is a system for creating of data attributes, comprising an attribute repository and a user interface application configured to receive a plurality of requests from users. The attribute repository stores a plurality of data attribute elements, including attributes, filters, functions, operators, and data definitions. The user interface application further comprises a development interface for editing attribute elements, wherein the development interface is configured to retrieve attribute elements from the attribute repository for editing and return edited attribute elements or newly created attribute elements for saving in the attribute repository, and a validation interface for testing data attributes, wherein the user interface application is configured to execute a validation processing engine to calculate data attributes on test credit data and display the calculation results of the individual attribute elements on the validation interface.


One embodiment is a system for calculating credit data attributes, comprising at least one credit data repository, a first plurality of application servers executing a plurality of attribute calculation engines, a second plurality of application servers executing a plurality of data access engines, wherein the data access engines are configured to access data from the at least one credit data repository, and a third plurality of application servers executing a plurality of façade applications, wherein the façade applications are configured to receive a plurality of attribute calculation requests from a plurality of calling applications, send corresponding requests to the attribute calculation engines and data access engines, and return calculation results from the attribute calculation engines to the calling applications.


One embodiment is a method for building attributes for data from multiple data sources, comprising the steps of defining a plurality of filters, wherein each filter takes into account the format of a data source among a plurality of data sources, defining a plurality of data source-independent attributes, wherein the attributes operate on data selected by the plurality of filters, and creating a deployment package based on the plurality of attributes.


One embodiment is a method for calculating data scores based on data from multiple data sources, comprising the steps of selecting a plurality of data sets from a plurality of data sources, wherein each of the plurality of data sources stores its data in a different format, defining a plurality sets of filters, wherein each set of filters takes into account the format of each of the plurality of data sources, defining a plurality of data source-independent attributes, extracting a subset of data from each of the selected data sets in accordance to the filters, calculating the attributes based on the subset of data, and aggregating the results obtained from the step of calculating to create data scores.


One embodiment of the present invention is a system for creating and using data attributes, comprising an attribute repository for storing a plurality of data attributes, a first application server executing a platform-independent user interface application, a data repository, and a second application server executing an attribute calculation engine system, wherein the attribute calculation engine system is configured to retrieve data from the data repository and performs calculations on the data in accordance to the attributes in a deployment package generated by the user interface application. In one embodiment, the user interface application further comprises a development interface for editing data attributes, wherein the development interface is configured to retrieve the data attributes from the attribute repository for editing and return edited data attributes or newly created data attributes for saving in the attribute repository, a validation interface for testing data attributes, wherein the user interface application is configured to execute a validation engine to calculate data attributes on test data and display the results on the validation interface, and a management interface for managing the deployment of the data attributes, wherein the data attributes are saved into a deployment package.





BRIEF DESCRIPTION OF THE DRAWINGS

Specific embodiments of the invention will now be described with reference to the following drawings, which are intended to illustrate embodiments of the invention, but not limit the invention:



FIG. 1 illustrates the architecture of the ATB architecture according to an embodiment;



FIG. 2 illustrates the hierarchy and the dependencies of systems, clients, attributes, filters, functions and raw data as used in one embodiment;



FIG. 3A illustrates an example deployment configuration of the ATB UI according to an embodiment;



FIG. 3B illustrates an example deployment configuration of the ATB engine system according to an embodiment;



FIG. 4A is a schematic diagram showing the implementation of the ATB UI according to one embodiment;



FIG. 4B is a schematic diagram showing the implementation of the ATB engine system according to one embodiment;



FIG. 5A is an example computer screen showing how attributes are located and managed in the ATB UI according to one embodiment;



FIG. 5B is an example computer screen showing the attribute development interface according to one embodiment;



FIG. 5C is an example computer screen showing how functions and operators can be added to attributes according to one embodiment;



FIG. 6A is an example computer screen showing the filter development interface according to one embodiment;



FIG. 6B is an example computer screen showing how details of a selected data source are displayed in the filter development interface according to one embodiment;



FIG. 6C is a computer screen showing a search and browse interface displaying how filters are used according to one embodiment;



FIG. 7 is an example computer screen of the validation interface showing the results of the validation engine according to one embodiment;



FIG. 8A is an example computer screen showing how a client system can be created in the ATB UI according to one embodiment;



FIG. 8B is an example computer screen showing how attributes can be associated with a client system for deployment according to one embodiment;



FIG. 8C is an example computer screen showing how multiple clients and systems are managed in the ATB UI according to one embodiment;



FIG. 9A is an example computer screen showing how multiple data sources are managed in the ATB UI according to one embodiment; and



FIG. 9B is an example computer screen showing show attributes and filters can be exported according to one embodiment.





DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments of the ATB UI system architecture solve many problems associated with developing, managing, and deploying attributes. First, many common aggregated attributes are often complex, referencing other attributes as well as filters that are data format dependent. The filters themselves have to be coded to access specific fields within a data source. For example, since each of the main CRAs in the United States maintains data in a different format, a separate filter is often used for each CRA. Therefore, the development of filters and attributes is often a tedious process and syntax errors frequently occur. Those skilled in the art will recognize that attributes can be developed for non-credit data sources, and the challenge of accounting for the individual formats of non-credit data sources exist as well. In one embodiment, the ATB UI includes a development interface that allows for filters and attributes to be moved via the UI, for example, into a coding area in which an attribute or a filter is being edited. In another embodiment, the ATB UI provides a filter development interface that presents data fields to the user. The interface simplifies the task of developing filters for multiple data sources that have different formats by presenting the data fields of the data sources in a graphical user interface. The fields can be moved into coding area as well, ensuring that proper data field references are included.


Second, the development of efficient and accurate attributes relies on extensive testing on raw data and constant revisions are made based on test results. Attributes often reference other attribute elements in a long chain of dependencies, including other attributes that may in turn reference numerous filters. For example, in developing an attribute that uses five other attributes, a developer may have to run numerous tests in order to arrive at the proper weight that should be accorded to each of the five attributes. In one embodiment, the ATB UI includes a validation interface that advantageously allows the user to see results returned by each attribute element that is referenced by the attribute that is currently being tested. One embodiment displays the results of each filter and each attribute that is referenced by the attribute that is being validated. This enables the user to quickly determining any errors or performance problems hidden in the chain of dependencies. The user can, for example, quickly determine that a filter is selecting a wrong field or that an attribute calculation is returning erroneous or undesirable results. The interface is particularly helpful in the development of aggregation attributes, which often reference a large number attributes and filters. The ability to trace the results of the individual elements is invaluable to the development of such attributes.


Third, institutions often require the use hundreds of attributes in multiple combinations to handle complex analysis and modeling on credit-based and non-credit based data. As a result, both the creation and maintenance of filters and attributes can require significant time and effort. Finally, the ability to effectively calculate attributes and scores on data from multiple data sources also presents significant challenges as well.


Embodiments of the ATB UI and ATB engine system architectures facilitate the management of the attributes and remove some of the difficulties that come with having to manually configure the deployment of attributes in system files. In one embodiment, the ATB UI allows users to associate groups of attributes into a system through a graphical user interface. The ATB UI also provides a comprehensive view of how attributes are deployed in various systems. Users can quickly and easily view the dependencies between attributes and the associated systems and determine how editing an attribute will affect the systems in their deployment scheme. In one embodiment, upon user request the ATB UI will automatically output a single deployment package including all of the user's systems, along with the proper associations of attributes, filters, and other configuration information. The deployment package can then be used in the ATB engine system, a system that performs attribute calculations.


In one embodiment, the ATB engine system is configured to dynamically access multiple data sources and automatically performs attribute calculations based on the attributes included in the deployment package. In another embodiment, the ATB engine system can calculate the attributes on credit data for a related set of individuals or entities. In one embodiment, both the ATB UI and the ATB engine system are implemented in a component-based architecture with a high degree of flexibility, maintainability, and scalability. In one embodiment, multiple components can be hosted in a single environment. In another embodiment, the components can be distributed across a network with a load balancing server to manage and distribute requests among the components.



FIG. 1 depicts the architecture of an embodiment of the present invention. Attribute Toolbox (ATB) architecture 100 includes two main components: an ATB User Interface (ATB UI) module 102 and an ATB engine system 104. The ATB UI 102 presents a comprehensive user interface through which users can view, edit, validate, and simulate filters and attributes. The ATB engine system 104 takes the attributes created by the ATB UI 102, fetches data from the appropriate data sources, and performs calculations on the fetched data based on those attributes.


ATB UI


As shown in FIG. 1, the ATB UI 102 includes a presentation component 110, a business logic abstraction 112, an attribute/filter management business logic 114, and a data access layer 116.


Attribute Development


The presentation component 110 presents various user interfaces to assist in the development of filters and attributes and the management of their deployment to various systems. In one embodiment, the presentation component 110 further comprises filter and attribute development interfaces 150, a search/browse interface 152, a management interface 154, and a validation interface 156. The filter and attribute development interfaces 150 enable users to drag and drop existing data definitions, filters, functions, and attributes into a coding area and thereby substantially reducing the time and effort required to locate the proper elements that need to be added into new filters and attributes. The search interface 152 enables user to search for and browse filters, attributes, and clients/systems. The management interface 154 allows user to configure clients and systems and provides an interface through which attributes can be associated to systems for deployment. These user interfaces will be further described in conjunction with FIGS. 5A-9B. In one embodiment, the ATB UI 102 accepts requests from client computers 122 and responds by presenting the appropriate user interfaces to the client computers 122.


These user interfaces access objects and methods within the business logic abstraction 112 layer, which is an abstraction layer of the attribute/filter management business logic 114. Hence, any future changes in the implementation in the attribute/filter management business logic 114 will not necessarily necessitate recoding or reconfiguring the presentation component 110. The ATB UI 102 retrieves attributes and filters from the attribute/filter repository 118 through the data access layer 116. Likewise, new or edited filters and attributes are saved back to the repository 118. The attributes can be standardized attributes such as standard aggregation (STAGG) attributes created by Experian, custom-made attributes, or both.


In one embodiment, the repository 118 implements a version control feature so that users of the ATB UI 102 can retrieve previous versions of attributes and filters. Furthermore, the ATB UI 102 provides a locking mechanism by which users can lock the attributes and filters that they are currently editing to prevent other users from changing them. The locking mechanism and the version control feature enable multiple users to collaborate on the development of attributes and filters.


In addition, one embodiment of the ATB UI 102 has user access control. For example, some users may be given rights to execute but not view attributes. Other users may have full rights to view and edit the attributes. In one embodiment, the user access rights are controlled by special serial numbers or passcodes, though it is recognized that a variety of security procedures and methods may be used. A user presents the proper serial number or passcode in order to view and edit attributes. The modularity of various interfaces, in addition to the user control feature of ATB UI 102, allows users with various roles to collaborate on a project. For example, developers of attributes and filters may be granted full rights to view and modify attributes and filters, while business analysts may be granted limited rights to deploy the attributes to various systems. In another example, a company that specializes in developing attributes and filters may have full access rights while its customers who purchase the attributes and filters may be given limited rights to use but not view the attributes and filters.


Testing, Validation and Simulation


One main difficulty with attribute and filter development is the significant effort required for validation. Often attribute and filter developers have to test the attributes and filters on sample data and modify them repeatedly to improve performance and accuracy. In addition to this iterative process, developers have to account for the large number of dependencies that can potentially be in any attributes and filters. FIG. 2 illustrates the potential dependencies as used in one embodiment. Hierarchy 170 shows that clients are dependent on systems, which in turn are dependent on attributes. An example client may be a credit card company, and the company may have a number of systems for its credit card products. For example, one system may be used to screen commercial card applicants and another may be used to screen consumer card applicants. As such, the two systems have different attributes because the screening criteria for these two groups of applicants are different.


Retuning to the hierarchy, attributes are further dependent on filters, which in turn are dependent on the raw data definitions. This is because attributes are data-independent and filters are data dependent. In one embodiment, a filter must be defined for each data source. As shown in the hierarchy 170, each filter can also reference other filters, functions and data definitions. Each attribute, in turn, can reference a number of filters, functions and other attributes. Thus, an error in a data definition in a single filter can adversely affect all filters that that reference that single filter, and in turn all attributes that reference those affected filters will be affected as well, and so on.


One embodiment of the ATB UI 102 addresses this difficulty by providing a validation engine 160 that allows for dependency tracing. In one example, an attribute A includes three other attributes B, C, D, and attributes B, C and D each additionally has three filters B1, B2, B3 and so on. When the user decides to test attribute A on a test data set in the validation engine 160, the validation interface 156 shows the user the results of applying filters B1, B2, B3, C1, C2, C3, D1, D2, and D3 to the sample data, as well as the results of calculating attributes B, C, and D. In addition, the validation interface 156 displays the raw data used in testing. Because each result in the chain of dependency for attribute A is displayed, the user can quickly locate any problem within the chain of dependency. For example, the user can see that attribute B is returning undesirable results, determine that filter B1 is incorrect, and adjust filter B1 to correct the problem. Because the dependencies can often be far more numerous and complex than this simple example, the validation interface 156 provides a powerful tracing tool for developers of attributes and filters for multiple data sources.


In addition to the validation engine 160, embodiments also provide a simulation configuration wherein the user can utilize the ATB UI 102 to simulate the performance of their filters and attributes to see how they affect attribute and score calculations. In one embodiment, the ATB UI 102 provides an interface by which a user may connect a custom application so the user may simulate the attributes and filters created in the ATB UI 102 in the custom application.


ATB Viewer


Embodiments of the invention also include an ATB Viewer component. The ATB Viewer is a user interface that allows users to “view” parsed raw data, calculated filter or attribute results. Attributes and filters can be created and generated and the results can be stored. The results can further be returned to a custom/calling application selected by the user. If the user wishes to view the results immediately, he/she can access the ATB Viewer to have a general formatted overview of the results for a specific test case.


Management and Deployment


The ATB UI 102 allows users to manage the collections of filters and attributes that are slated for deployment in the ATB engine system 104. Users can quickly create attributes and associate a group of attributes for deployment. For example, a bank user may create twenty attributes for its credit card operations and another fifty attributes for its home loan operations. The bank may then associate the twenty attributes to a “Credit Cards” system and the fifty attributes to a “Home Loans” systems by using the ATB UI 102. The ATB UI 102 then outputs a deployment package 120 to be used by the ATB UI engine system 104, which performs calculations based on these associated attributes included with the deployment package 120. In one embodiment, the deployment package 120 is generated with the proper dependencies among the attributes and filters. Furthermore, the deployment package 120 can accommodate multiple systems, each with its own associated attributes. This one-step deployment function of this embodiment substantially eliminates the cost of having to code the dependencies of the attributes manually and enables rapid deployment of multiple systems with a single request sent to the ATB UI 102.


ATB Engine System


The ATB engine system 104 retrieves and parses raw data, calculates attributes, and returns results. In the illustrated embodiment, the ATB engine system 104 comprises an ATB engine 106 and a data access engine 108. In other embodiments, they can be combined into one engine. The ATB engine 106 calculates attributes or scores using data received from the data access engine 108. In one embodiment, the ATB engine 106 comprises a parser 162, which reads and parses data. In other embodiments, during calculation, the ATB engine 106 reads instructions in a manually created file or a deployment file produced by the ATB UI 102. The ATB engine 106 then instructs a business rules component 164, which performs the actual calculations.


In one embodiment, the data access engine 108 accesses the external data source(s) 140 or reads the data from one or several files (for example, an automatic response format (ARF) file), parses the data, and sends it to the ATB engine 106 for calculation. The data access engine 108 comprises a mapper 166 and a communication module 168. The mapper 166 handles the mapping of data fields in data sources 140 to objects within ATB engine system 104. The communication module 168 handles the tasks of communicating with various data sources 140. Because data access engine 108 accepts a wide variety of data input, it can be configured to access data from credit data sources 402 as well as data from non-credit data sources 404, such as a local data source 406. In one embodiment, the local data source 406 is a batch XML input. For example, a bank running an instance of the ATB engine 104 may configure the ATB engine 104 to perform attribute calculations on data from a credit bureau, a third-party data source, and/or its own internal customer data. In one embodiment, the results of the calculations are sent to a repository 148 so the calling application 124 may access them.


Because the ATB engine system 104 can handle multiple data sources, it can dynamically calculate the attributes across data sources as needed. Embodiments of the ATB engine system 104 can be configured to automatically calculate attributes across multiple data sources, whether in response to requests from a plurality of calling applications or a large volume of batch requests from batch files. The ability to handle calculations across multiple data sources in accordance to the incoming requests greatly assist in the evaluation of the relative risk/benefit of a given financial decision that involve multiple persons at the same time, such as spouses, partnerships, sole proprietorships, joint ventures, LLCs or other entities. Thus, unlike prior systems, users of the ATB engine system 104 will not have to access the data sources individually and perform attribute calculation for each source and then combine the results of their calculations. Similarly, the ATB engine system 104 will not have to perform an analysis on individuals separately and then combine the results.


Profile


Embodiments of the ATB engine system 104 additionally includes a profile component. In one embodiment the profile component is part of the façade 130. A profile provides the ability to handle simple work flows. For example, one work flow may be a decision of call one data source versus another that depends on the results coming from a previous service request. For example, one profile can include instructions to the ATB engine system 104 to access an alternative data source in case a first request does not return the desired data. The profile workflow logic can include a variety of instructions and requests that can be executed based on the occurrence or non-occurrence of various conditions. Embodiments of ATB engine system include profiles that can handle roll-over logic, ZIP code tables and any other type of logic driven by one or several attribute calculations.


ATB UI Architecture



FIG. 3A depicts an embodiment of the ATB UI web server architecture. The illustrated ATB UI architecture 200 includes an ATB UI web server 202 configured to receive requests from a plurality of workstations or other remote computing devices 204. In one embodiment, workstations or remote computing devices 204 send requests and receive responses via the HTTP or HTTPS protocols, and use web browsers to solicit inputs and display the information to the end users. For example, an end user may be a bank that regularly extends credit to its customers. The bank may be able to use its computers to remotely interact with the ATB UI web server 202 in order to view, edit, validate, and test its own attributes and filters stored in relational databases 206. In one embodiment, the ATB UI web server 202 is a self-contained Ruby on Rails application that acts as a web server. It communicates via the HTTP or HTTPS protocol in one embodiment. Syntax checking of attribute codes is accomplished through java-script on the client computers. It is recognized that other applications, protocols, and languages may be used.


ATB Engine Architecture



FIG. 3B illustrates an embodiment of the ATB engine system architecture. The illustrated ATB engine system architecture 220 includes a calling application 222, a load balancer 224, one or more façade web services 226, data access engines 228, ATB engines 230, and a data storage 232. In one embodiment, the calling application 222 is an application that sends calculation requests to the load balancer 224. In other embodiments, the calling application 222 directly sends requests to the façade web service 226. These requests include requests to calculate attributes and scores. For example, a bank may have a calling application that sends a request to calculate the number of customers who have the attribute of recently opening a credit line within the last twelve months. In one embodiment, the calling application is a custom-coded application. For example, a mortgage company may have a custom-coded application to process its loan applicants. In another embodiment, the calling application is a commercially available application such as Transact by Experian Decision Analytics. It is recognized that other applications may be used.


In one embodiment, the load balancer 224 receives requests from a plurality of calling applications 222 and distributes those requests to a plurality of the façade web services 226 in order to improve the efficiency of the overall architecture. Each façade web service 226 publishes objects and methods available for attribute calculation. Upon receipt of an incoming request from the calling application 224, the façade web service 226 initiates the appropriate remote procedural calls (RPC) over the TCP/IP protocol to either the data access engine 228 or the ATB engine 230. For example, the façade web service 226 may initiate a first RPC to the data access engine 228 to retrieve the requested data from the data storage 232 and then initiate a second RPC to the ATB engine 230 for calculation. The ATB engine 230 then calculates the results by applying attributes within the deployment package 120 to the retrieved data sets. In one embodiment, a user can use the ATB UI 102 to create the deployment package 120. The final results are sent back to the calling application 222. In the recently opened credit line example mentioned above, the results would be a list of customers who have opened a recent credit line.


The configuration depicted in FIGS. 3A and 3B is for illustrative purposes only and those skilled in the art will recognize that any number of components of the architecture can be used. In one embodiment, the architecture is designed to be scalable. For example, although not depicted, a plurality of calling applications and a plurality of credit bureau data sources can be used in the architecture. Moreover, the components can reside in a single computer environment or distributed across multiple computer environments.



FIG. 4A provides a more detailed depiction of the architecture of the ATB UI 102 according to one embodiment. As previously shown in FIG. 1, client computers 122 access the ATB UI 102 over one or more communication networks. The presentation component 110 presents a user interface by which users can interact with the ATB UI 102. Except for the web browsers located on client computers 122, no installed code base of ATB UI needs to reside on client computers 122. Communications from the browser interface to the presentation component 110 occur through URL navigation or HTTP requests.


The business logic abstraction layer 112 is an abstraction layer of the attribute/filter management business logic 114. The abstraction layer 110 further comprises a filter manager 132, an attribute manager 134, and a client manager 136. These managers present objects, systems and methods for viewing, editing, and managing filters, attributes, and systems to which the filters and attributes will employ. The managers have their corresponding counterparts within the business logic 114, namely, a filter business component 142, an attribute business component 144, and a client business component 146. The three business components work with a repository object 120 within the data access layer 116 for transactions involving the repository 118. In this example embodiment, the repository 118 comprises a SQLite database server, but those skilled in the art will recognized that other database servers such as Oracle, mySQL, Microsoft SQL Server, and IBM DB2 can be used as well.


The abstraction layer 112 serves as a liaison between the presentation component 110 and the business logic 114. The abstraction layer 112 also provides security enforcement functions in one embodiment. For example, it ensures that attributes are only displayed for the users who have the proper access rights to view them. In one embodiment, the abstraction layer 112, the business logic 114 and the data access layer 116 are implemented in a Ruby on Rails environment, which has the advantages of providing ease of maintenance and a modular programming construct, though other environments may be used.


As shown in FIG. 4A, the ATB UI 102 further includes a core services component 254 and a support service component 256. In one embodiment, the core services component 254 is a Rails framework comprising a security component 260, an exception component 262, an export/import component 264, and a logger component 266. The security component 260 provides the logic for security enforcement, which limits access to the attributes and filters to those users who have the proper levels of access rights. The exception component 262 handles exceptions generated by any component within the ATB UI 102. The export/import component 264 is a data interchange service that supports and provides the capability to export and import ATB entities (for example, attributes) from and into the ATB UI 102. The logger component 266 is served by the Ruby log 4r library in one embodiment. It provides the functionality to publish messages to external log stores and to control the type and volume of data logged. The support service component 256 comprises a reporting component 268, which provides a set of pre-defined reports that can be run. In one embodiment, the generated reports are templates for specification documents and include attributes and related results.



FIG. 4B is a schematic diagram showing the implementation of the ATB engine system 104 according to one embodiment. The façade 130 includes two methods of accepting requests. It has a web service component 270 and a batch component 272. In one embodiment, the web service component 270 is supported by a SOAP4R component 294 within technical services 288. SOAP4R is a Simple Object Access Protocol (SOAP) implementation in the Ruby programming language. The web service component 270 thus accepts SOAP requests from calling applications. Alternatively, the batch component 272 reads batched requests in a repository 298. In one embodiment, the repository 298 is a hard drive.


In either case, once an incoming request has been received, the façade 130 begins the process of managing the request and performs the necessary work in order to return a response to the request. First, the façade 130 has a message publisher 276 that will publish a message to either the ATB engine 106 or the data access engine 108. In one embodiment, the message is a RPC sent via the TCP/IP protocol. The façade 130 includes managing logic that will handle the sequence in which RPCs are sent. The façade 130 additionally includes a profile component that handles a variety of work-flow logic as described earlier.


Both the ATB engine 106 and the data access engine 108 have a message subscriber component that subscribes to the message publisher 276. In the ATB engine 106, once the message subscriber 278 receives a message from the message publisher 276, it will instruct business component 280 to perform calculations. In one embodiment, business component 280 further comprises the parser 162 and the business rules component 164. The business rules component 164 performs calculations based on the attributes and filters within deployment package 120, using data parsed by the parser 162. In one embodiment, the business component 280 is implemented in the Lua scripting language, which provides fast execution times and increased performance. This is particularly important in some embodiments because the ATB engine system may be configured to receive a high volume of requests from the batch component 272 and to accept a large number of requests from calling applications through the web service 270. The façade 130 and the access engine 108 are implemented in the Ruby programming language in one embodiment.


Access engine 108 also includes the aforementioned message subscriber 282 and a data source access framework 284. After the message subscriber 282 receives a message from the message publisher 276, it will instruct the data source access framework 284 to access the requested data. The data source access framework reads a data source definition file 286 in order to determine the data formats of the various data sources that are being accessed. Finally, technical services 288 include a log 4r component that provides logging capability for debugging purposes.


Attribute Interfaces



FIG. 5A is an example computer screen showing the attribute search/browse interface 152 in the ATB UI 102 according to one embodiment. As shown, a search panel 302 is provided so users can search for attributes by various parameters such as name/keyword, system, and format. In response, the ATB UI 102 displays a sortable list 304 of attributes stored in the repository 118 that match the search parameters. For each attribute, the ATB UI 102 shows the system in which the attribute is being deployed, as well as whether the attribute is locked by another user who is viewing or editing it.


The ATB UI 102 facilitates the management of the attributes and removes some of the difficulties of having to manually configure the deployment of attributes. Because the UI provides a comprehensive view of how attributes are deployed in various systems, users can quickly and easily view the dependencies between attributes and the associated systems and determine how editing an attribute will affect the systems in their deployment scheme. In addition, because the name of each attribute listed is a link to the attribute development interface with that selected attribute shown in a coding area, the users can quickly launch into the development environment from the list 304.



FIG. 5B is an example computer screen showing how attributes can be edited in the attribute development interface 150 according to one embodiment. As shown, an example attribute is being edited or created in a coding area 314. Because attributes often reference numerous other attributes, filters, functions, and operators, the development interface 150 provides a panel 312 that lists other attributes, filters, functions, and operators that can be inserted into the coding area 314. This ensures that the newly created attribute or the edited attribute will have the proper dependencies. In one embodiment, the list is populated by the attributes and filters retrieved from the repository 118. Any attribute or filter listed can be moved (for example, dragged and dropped) into the coding area 314, and a proper reference to that attribute or filter automatically appears within the coding area 314.


In addition, the panel 312 has a tab area 316, which has two other tabs “filters” and “functions & operators” as shown. A user can select one of the other tabs and brings up either the filters or the functions and operators that are available. Likewise, these elements can be dragged and dropped into the coding area 314 and the proper references are automatically created. FIG. 5C shows an example of the panel 312 after a user selects the “functions &operators” tab within the tab area 316. Any of the functions and operators shown can be moved (for example, dragged and dropped) into the coding area 314. Therefore, the development interface 150 enables users to rapidly code new attributes or modify existing attributes with accurate references to other attributes, filters, functions, and operators.


Filter Interfaces



FIG. 6A is one embodiment of an example computer screen of the filter development interface 150. Similar to the attribute development interface shown in FIG. 5B, the filter development interface presents other filters, functions, and operators in a panel 322 that can be dragged and dropped into a coding area 324.


Coding Filters for Various Data Sources


Because of the complexities of database definitions, the task of developing filters on raw data is often left to programmers. To overcome this problem, the filter development interface 150 simplifies the task of developing filters for various data sources by showing the data fields within segments of the data sources. Therefore, in addition to filters, functions, and operators, the filter development interface has a “raw data” tab in the tab area 326. As shown in FIG. 6A, the available data segments in the data source “Experian” are listed in the panel 322. The fields within the segments are available to be dragged and dropped into the coding area 324. As shown, the coding area 324 shows the codes the filter that is being developed.



FIG. 6B is an example computer screen showing how filters can be developed for different data sources in the ATB UI. As shown in FIG. 6B, data fields for a selected segment within a selected data source are listed in the panel 322. Drop down boxes 320 include a data source drop-down box, a segment drop-down box, and an argument drop-down box. The data source is selected at the data source drop-down box, and the data segment is selected at the segment drop-down box and so on. In this example, the “Experian” data source has been selected and a segment has also been selected. In one embodiment, all available valid segments associated with the selected data source are listed in the segment drop-down box.


In one embodiment, once a segment is selected, all the available data fields are shown within the panel 322. The user can drag and drop a field into the coding area 324. Through the filter development interface 150, a user can easily scan through the available fields within the segments in a data source and quickly and accurately add the necessary fields to a filter that is currently being edited in the coding area 324. This interface minimizes errors and speeds up the development of filters for multiple data sources with different data formats.



FIG. 6C is a computer screen showing the filter search/browse interface 152. Much like the interface shown FIG. 5A for attributes, users can search for filters and the search results will be displayed in a listing 340. Each filter is listed with status information, whether it has been locked by another user for editing, and whether it has been encoded for a particular data source (as indicated by the check marks). Clicking on the name of the filter will launch a development interface similar to the one shown in FIG. 6A, where the user can edit the selected filter.


Syntax Checking and Validation


In one embodiment, ATB UI provides a syntax checking engine that checks the syntax of a filter or an attribute within a current coding area if requested by the user. As shown in FIG. 6A, once the user selects a “Check Syntax” button 330, the ATB UI will run a syntax check on either the filter or attribute that is currently being edited. For example, FIG. 6A shows the syntax check window 328 displaying a message indicating that the syntax check engine has discovered a syntax error on line 13 of the example filter. The syntax check engine can likewise check for syntax errors within an attribute. Thus users of the ATB UI can avoid saving invalid filters or attributes. In other embodiments, a syntax check is automatically performed when a user attempts to save a filter or an attribute to the repository 118, or save changes to an existing filter or attribute.


Besides a syntax checking engine, embodiments of ATB UI also provide the validation interface 156 and the validation engine 160 (shown in FIG. 1) through which users can validate attributes against test data. FIG. 7 shows an example computer screen of the validation interface 156. The validation interface 156 includes an information/selection area 350, which further includes a data file selector 352 and a data source selector 354. Using the data file selector 354, the user can select a sample test file including test data for the data source that the user selects in the data source selector 354. In the example shown, the user has selected a file including sample data from the data source “Experian” to be sent to the validation engine 160. In one embodiment, the validation engine 160 accepts test files for in the ARF format.


In the example shown in FIG. 7, the validation engine 160, through the validation interface 156, provides a result 358 for the selected attribute “ALL002.” The validation engine 160 has calculated the attribute “ALL002” against the test data and has determined that the result is 52.0. More importantly, the validation interface 156 further includes a validation table 356 in which a user can examine the raw data and the dependencies within the attribute that is undergoing validation. The column headings of the validation table 356 show all the depending filters and attributes referenced in the code of attribute “ALL002.” The rows of the validation table 356 show raw data from the test file.


The validation interface 156 advantageously allows the user to see exact results returned by each filter or attribute referenced by the attribute that is being validated. This enables the user to quickly determining any errors or performance problems hidden in the chain of dependencies. The user can, for example, quickly determine that a filter is selecting a wrong field or that an attribute calculation is returning erroneous or undesirable results. The validation interface 156 is particularly helpful in the development of aggregation attributes, which often reference a large number attributes and filters.


System Management



FIG. 8A is one embodiment of an example computer screen showing how a client can be created in the ATB UI. An input interface 360 solicits configuration information that is needed to create a new client. The input interface 360 includes a listing of data sources that the new client will access, as well as a listing of systems that will be associated with this new client. When the user attempts to save the client configuration information, the ATB UI will check for errors and display an error message 362 (as shown) if needed.



FIG. 8B is one embodiment of an example computer screen showing how attributes can be associated with a client system for deployment. As an example, a client who is a bank may wish to deploy various systems associated with its needs. The bank may thus have one system that screens potential home loan applicants and another system for finding prospective commercial credit card applicants. Because each system requires different data and calculations, the bank client may wish to configure each one differently. The ATB UI provides an interface 366 to allow a client user to associate various attributes to a system for deployment. The interface 366 includes an available attribute listing 368 and a deployment attribute listing 370. The user can search for and browse attributes that are available deployment in the listing 368 and then add the attributes to the deployment listing 370 by using an arrow selector 372. The attributes will then be slated for deployment for the particular system.



FIG. 8C is one embodiment of an example computer screen showing how multiple client system deployments are managed in the ATB UI. A system listing 380 lists systems that are available for deployment. Each system is listed with a name, a historical data entry including the date of last deployment, status, and the number of associated attributes. Under the status column, the ATB UI may indicate whether a system is ready or not ready for deployment. Some systems may not be ready to be deployed because they may have attributes with syntax errors or no attributes at all. The system listing 380 provides a way for the user to browse through the available systems and quickly determine which are ready for deployment. Furthermore, the ATB UI provides a link to the attributes so the user can quickly view or edit the attributes associated with the systems. The user is also given the option to select multiple systems from the listing 380 and deploy all of them at the same time. The deployment package 120 is then automatically created and can be used in ATB engine system 104.


Managing Data Sources and Attribute Exports



FIG. 9A is one embodiment of an example computer screen showing how multiple data sources are managed in the ATB UI 102. The ATB UI 102 provides a data source listing 386 that lists the available data sources. Each entry lists the short and long names of the data source as well as the time when the data source was last modified. The ATB UI 102 also provides a data source area 388 that displays the detail information of a data source that has been selected. The user can then view or edit the details of a particular data source, including the location of the file from which data can be obtained.



FIG. 9B is one embodiment of an example computer screen shot showing how attributes can be exported to a file. A system listing 390 provides a listing of systems that can be exported. Once exported, the file will include all attributes associated with the selected system. The export function allows multiple users from various sites to collaborate on a project. In one embodiment, users at remote sites without access to the centralized repository can run their own copies of the ATB UI 102. For example, a first user may be developing attributes and filters on a laptop while traveling. The export function enables the first user to export the attributes and filters and send the export file to a second user who runs a different instance of the ATB UI 102 that has a connection to a centralized repository. The second user will then be able to import the attributes created by the first user and save the attributes to the centralized repository. In one embodiment, the ATB UI 102 checks the import file against the repository, so that duplicate attributes are shown to the user. The second user will then have the option of overwriting the attributes that are in the repository with the imported version. In this manner, numerous users from various remote locations, even those without connection to a centralized attribute repository, can independently develop attributes and filters and merge their work later.


Various Embodiments of System and Method Implementations


In one embodiment, the systems and methods for generating and calculating attributes may be embodied in part or in whole in software that is running on one or more computing devices. The functionality provided for in the components and modules of the computing device(s) may comprise one or more components and/or modules. For example, the computing device(s) may comprise multiple central processing units (CPUs) and one or more mass storage device(s), such as may be implemented in an array of servers.


In general, the word “module,” “application”, or “engine,” as used herein, refers to logic embodied in hardware and/or firmware, and/or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Ruby, Ruby on Rails, Lua, C and/or C++. These may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that modules, applications, and engines may be callable from others and/or from themselves, and/or may be invoked in response to detected events or interrupts. Instructions may be embedded in firmware, such as an EPROM.


It will be further appreciated that hardware may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules, applications, and engines described herein are in certain applications preferably implemented as software modules, but may be represented in hardware or firmware in other implementations. Generally, the modules, applications, and engines described herein refer to logical modules that may be combined with other modules and/or divided into sub-modules despite their physical organization or storage.


In some embodiments, the computing device(s) communicates with one or more databases that store information, including credit data and/or non-credit data. This database or databases may be implemented using a relational database, such as SQLite, Sybase, Oracle, CodeBase, mySQL, and Microsoft® SQL Server as well as other types of databases such as, for example, a flat file database, an entity-relationship database, and object-oriented database, and/or a record-based database.


In one embodiment, the computing device is IBM, Macintosh, and/or Linux/Unix compatible. In another embodiment, the computing device comprises a server, a laptop computer, a cell phone, a Blackberry, a personal digital assistant, a kiosk, or an audio player, for example. In one embodiment, the computing device includes one or more CPUs, which may each include microprocessors. The computing device may further include one or more memory devices, such as random access memory (RAM) for temporary storage of information and read only memory (ROM) for permanent storage of information, and one or more mass storage devices, such as hard drives, diskettes, or optical media storage devices. In one embodiment, the modules of the computing are in communication via a standards based bus system, such as bus systems using Peripheral Component Interconnect (PCI), Microchannel, SCSI, Industrial Standard Architecture (ISA) and Extended ISA (EISA) architectures, for example. In certain embodiments, components of the computing device communicate via a network, such as a local area network that may be secured.


The computing is generally controlled and coordinated by operating system software, such as the Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, Windows Vista, Linux, SunOS, Solaris, PalmOS, Blackberry OS, or other compatible operating systems. In Macintosh systems, the operating system may be any available operating system, such as MAC OS X. In other embodiments, the computing device may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, and I/O services, and provide a user interface, such as a graphical user interface (GUI), among other things.


The computing device may include one or more commonly available input/output (I/O) devices and interfaces, such as a keyboard, mouse, touchpad, microphone, and printer. Thus, in one embodiment the computing device may be controlled using the keyboard and mouse input devices, while in another embodiment the user may provide voice commands to the computing device via a microphone. In one embodiment, the I/O devices and interfaces include one or more display device, such as a monitor, that allows the visual presentation of data to a user. More particularly, a display device provides for the presentation of GUIs, application software data, and multimedia presentations, for example. The computing device may also include one or more multimedia devices, such as speakers, video cards, graphics accelerators, and microphones, for example.


In one embodiment, the I/O devices and interfaces provide a communication interface to various external devices. For example, the computing device may be configured to communicate with one or more networks, such as any combination of one or more LANs, WANs, or the Internet, for example, via a wired, wireless, or combination of wired and wireless, communication links. The network communicates with various computing devices and/or other electronic devices via wired or wireless communication links.


Although the foregoing invention has been described in terms of certain embodiments, other embodiments will be apparent to those of ordinary skill in the art from the disclosure herein. Moreover, the described embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms without departing from the spirit thereof. Accordingly, other combinations, omissions, substitutions and modifications will be apparent to the skilled artisan in view of the disclosure herein. For purposes of discussing the invention, certain aspects, advantages and novel features of the invention have been described herein. Of course, it is to be understood that not necessarily all such aspects, advantages or features will be embodied in any particular embodiment of the invention.

Claims
  • 1. A computer-implemented method for generating attributes, the computer-implemented method comprising: identifying a credit data attribute formula expression, wherein identifying the credit data attribute formula expression comprises: receiving, via a validation user interface that includes options that enable a user to define and deploy filters and attributes associated with different data sources having different data formats, a user selection of at least one attribute, wherein the at least one attribute relates to a type of credit data;receiving, via the validation user interface, a user selection of at least one function or at least one operator; andidentifying the credit data attribute formula expression based on the retrieved user selection of the at least one attribute, and the at least one function or the at least one operator;retrieving data associated with the at least one attribute, wherein retrieving the data comprises: identifying a first data source and a second data source that each store data associated with the type of credit data, wherein a first format of data stored in the first data source is different from a second format of data stored in the second data source;identifying a first filter and a second filter, wherein the first filter is configured to extract data from the first data source stored in the first format by mapping one or more data fields in the first data source to the type of credit data, wherein the second filter is configured to extract data from the second data source stored in the second format by mapping one or more data fields in the second data source to the type of credit data;extracting a first subset of data from the first data source in accordance with the first filter;extracting a second subset of data from the second data source in accordance with the second filter, wherein the data associated with the at least one attribute includes the first and second subsets of data; anddisplaying, via the validation user interface, (a) the first subset of data extracted in accordance with the first filter and (b) the second subset of data extracted in accordance with the second filter; andgenerating at least one attribute score for the at least one attribute, wherein generating the at least one attribute score includes: generating a deployment package by compiling the credit data attribute formula expression into computer executable code, wherein the deployment package includes computer instructions;deploying the deployment package to a computing system; andexecuting the computer executable code to generate the at least one attribute score based on one or more computer instructions included within the deployment package, wherein executing the computer executable code causes the computing system to apply the data associated with the at least one attribute to the computer executable code of the credit data attribute formula expression.
  • 2. The computer-implemented method of claim 1 further comprising: accessing a dependency tracing indicative of a dependency between the at least one attribute, and the at least one function or the at least one operator; anddisplaying a result of applying the data associated with the at least one attribute to at least a portion of the computer executable code of the credit data attribute formula expression.
  • 3. The computer-implemented method of claim 1, further comprising: receiving, from the validation user interface, user information associated with a user;generating a user profile;adding the received user information to data fields of the user profile; andstoring the identified credit data attribute formula expression in the user profile.
  • 4. The computer-implemented method of claim 3, further comprising: receiving, from the validation user interface, client information associated with a client of the user;adding the received client information to data fields of the user profile; andassociating the identified credit data attribute formula expression with the received client information in the user profile.
  • 5. The computer-implemented method of claim 1, further comprising retrieving, from the validation user interface, a user selection of a version command to store the credit data attribute formula expression as one version of a plurality of versions of the credit data attribute formula expression.
  • 6. The computer-implemented method of claim 1, further comprising retrieving, from the validation user interface, a user selection of other user access authorization, wherein the user selection includes at least authorization to use the credit data attribute formula expression without authorization to edit the credit data attribute formula expression.
  • 7. The computer-implemented method of claim 1, further comprising determining at least one weighting to be applied to the at least one attribute.
  • 8. The computer-implemented method of claim 1, further comprising causing display of dependencies between the at least one attribute, and the at least one function or the at least one operator.
  • 9. A system for generating attributes, the system comprising: one or more processors; andnon-transitory computer storage comprising code executable by the one or more processors, the executable code causing the one or more processors to: receive, via a validation user interface that includes options that enable a user to define and deploy filters and attributes associated with different data sources having different data formats, a user selection of at least one attribute, wherein the at least one attribute relates to a type of credit data;identify a credit data attribute formula expression based on the retrieved user selection of the at least one attribute, and at least one function or at least one operator;retrieve data associated with the at least one attribute, wherein to retrieve the data comprises to: identify a first data source and a second data source that each store data associated with the type of credit data, wherein a first format of data stored in the first data source is different from a second format of data stored in the second data source;identify a first filter and a second filter, wherein the first filter is configured to extract data from the first data source stored in the first format by mapping one or more data fields in the first data source to the type of credit data, wherein the second filter is configured to extract data from the second data source stored in the second format by mapping one or more data fields in the second data source to the type of credit data;extract a first subset of data from the first data source in accordance with the first filter;extract a second subset of data from the second data source in accordance with the second filter, wherein the data associated with the at least one attribute includes the first and second subsets of data;display, via the validation user interface, (a) the first subset of data extracted in accordance with the first filter and (b) the second subset of data extracted in accordance with the second filter; andgenerate at least one attribute score for the at least one attribute by generating a deployment package that applies the data associated with the at least one attribute to the credit data attribute formula expression, wherein the deployment package is deployed to a computer system, and wherein the computer system is configured to generate the at least one attribute score based on one or more computer instructions included within the deployment package.
  • 10. The system of claim 9 wherein the executable code further causes the one or more processors to: access a dependency tracing indicative of a dependency between the at least one attribute, and the at least one function or operator; anddisplay a result of applying the data associated with the at least one attribute to at least a portion of the credit data attribute formula expression.
  • 11. The system of claim 9 wherein the executable code further causes the one or more processors to: receive, from the validation user interface, user information associated with a user;generate a user profile;add the received user information to data fields of the user profile; andstore the identified credit data attribute formula expression in the user profile.
  • 12. The system of claim 11, wherein the executable code further causes the one or more processors to: receive, from the validation user interface, client information associated with a client of the user;add the received client information to data fields of the user profile; andassociate the identified credit data attribute formula expression to the received client information in the user profile.
  • 13. The system of claim 9, wherein the executable code further causes the one or more processors to retrieve, from the validation user interface, a user selection of a version command to store the credit data attribute formula expression as one version of the formula expression.
  • 14. The system of claim 9, wherein the executable code further causes the one or more processors to retrieve, from the validation user interface, a user selection of a lock command to lock the identified credit data attribute formula expression.
  • 15. A non-transitory computer storage medium which stores a client application comprising executable code, the executable code causing a computing device to perform operations that comprise at least: receiving, via a validation user interface that includes options that enable a user to define and deploy filters and attributes associated with different data sources having different data formats, a user selection of at least one attribute, wherein the at least one attribute relates to a type of credit data;receiving, via the validation user interface, a user selection of at least one function or at least one operator;retrieving data associated with the at least one attribute, wherein retrieving the data comprises: identifying a first data source and a second data source that each store data associated with the type of credit data, wherein a first format of data stored in the first data source is different from a second format of data stored in the second data source;identifying a first filter and a second filter, wherein the first filter is configured to extract data from the first data source stored in the first format by mapping one or more data fields in the first data source to the type of credit data, wherein the second filter is configured to extract data from the second data source stored in the second format by mapping one or more data fields in the second data source to the type of credit data;extracting a first subset of data from the first data source in accordance with the first filter;extracting a second subset of data from the second data source in accordance with the second filter, wherein the data associated with the at least one attribute includes the first and second subsets of data;displaying, via the validation user interface, (a) the first subset of data extracted in accordance with the first filter and (b) the second subset of data extracted in accordance with the second filter; andgenerating at least one attribute score for the at least one attribute by generating a deployment package that applies the data associated with the at least one attribute to the at least one function or the at least one operator, wherein the deployment package is deployed to a computing system, and wherein the computing system is configured to generate the at least one attribute score based on one or more computer instructions included within the deployment package.
  • 16. The non-transitory computer storage medium of claim 15, wherein the operations further comprise: accessing a dependency tracing indicative of a dependency between the at least one attribute, and the at least one function or operator; anddisplaying a result of applying the data associated with the at least one attribute to the at least one function or operator.
  • 17. The non-transitory computer storage medium of claim 15, wherein the operations further comprise: receiving, from the validation user interface, user information associated with a user;generating a user profile;adding the received user information to data fields of the user profile;storing the at least one attribute, and the at least one function or operator in the user profile;receiving, from the validation user interface, client information associated with a client of the user;adding the received client information to data fields of the user profile; andassociating the at least one attribute, and the at least one function or operator with the received client information in the user profile.
  • 18. The non-transitory computer storage medium of claim 15, wherein generating the at least one attribute score for the at least one attribute includes generating the at least one attribute score using a simulation file, and wherein the first data source and the second data source are each a simulated data source.
  • 19. The non-transitory computer storage medium of claim 15, wherein the executable code is configured to be executed in response to a calling function.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 14/091,174 filed on Nov. 26, 2013, entitled “SYSTEM AND METHOD FOR PROVIDING AN AGGREGATION TOOL”, which is a continuation of U.S. patent application Ser. No. 12/022,954 filed on Jan. 30, 2008, and which issued as U.S. Pat. No. 8,606,666, entitled “SYSTEM AND METHOD FOR PROVIDING AN AGGREGATION TOOL,” which claims the benefit of priority under 35 U.S.C. § 119(e) of U.S. Provisional Patent Application No. 60/887,523 filed on Jan. 31, 2007, the entire contents of which are each hereby incorporated by reference in their entirety herein and should be considered a part of this application. All publications and patent applications mentioned in this specification are herein incorporated by reference in their entirety and made a part of this specification to the same extent as if each individual publication or patent application was specifically and individually indicated to be wholly incorporated by reference.

US Referenced Citations (1073)
Number Name Date Kind
3316395 Lavin et al. Apr 1967 A
4305059 Benton Dec 1981 A
4371739 Lewis et al. Feb 1983 A
4398055 Ijaz et al. Aug 1983 A
4578530 Zeidler Mar 1986 A
4617195 Mental Oct 1986 A
4672149 Yoshikawa et al. Jun 1987 A
4736294 Gill Apr 1988 A
4754544 Hanak Jul 1988 A
4774664 Campbell et al. Sep 1988 A
4812628 Boston et al. Mar 1989 A
4827508 Shear May 1989 A
4868570 Davis Sep 1989 A
4876592 Von Kohorn Oct 1989 A
4895518 Arnold Jan 1990 A
4935870 Burk, Jr. et al. Jun 1990 A
4947028 Gorog Aug 1990 A
5025138 Cuervo Jun 1991 A
5025373 Keyser, Jr. et al. Jun 1991 A
5034807 Von Kohorn Jul 1991 A
5060153 Nakagawa Oct 1991 A
5148365 Dembo Sep 1992 A
5201010 Deaton et al. Apr 1993 A
5216612 Cornett et al. Jun 1993 A
5220501 Lawlor et al. Jun 1993 A
5247575 Sprague et al. Sep 1993 A
5259766 Sack Nov 1993 A
5262941 Saladin Nov 1993 A
5274547 Zoffel et al. Dec 1993 A
5297031 Guterman et al. Mar 1994 A
5325509 Lautzenheiser Jun 1994 A
5336870 Hughes et al. Aug 1994 A
5341429 Stringer et al. Aug 1994 A
5454030 de Oliveira et al. Sep 1995 A
5468988 Glatfelter et al. Nov 1995 A
5504675 Cragun et al. Apr 1996 A
5528701 Aref Jun 1996 A
5555409 Leenstra, Sr. et al. Sep 1996 A
5563783 Stolfo et al. Oct 1996 A
5583763 Atcheson et al. Dec 1996 A
5590038 Pitroda Dec 1996 A
5592560 Deaton et al. Jan 1997 A
5611052 Dykstra et al. Mar 1997 A
5615408 Johnson Mar 1997 A
5621201 Langhans et al. Apr 1997 A
5629982 Micali May 1997 A
5630070 Dietrich et al. May 1997 A
5630127 Moore et al. May 1997 A
5640551 Chu et al. Jun 1997 A
5640577 Scharmer Jun 1997 A
5655129 Ito Aug 1997 A
5659731 Gustafson Aug 1997 A
5666528 Thai Sep 1997 A
5679176 Tsuzuki et al. Oct 1997 A
5689651 Lozman Nov 1997 A
5692107 Simoudis et al. Nov 1997 A
5696907 Tom Dec 1997 A
5704029 Wright, Jr. Dec 1997 A
5732400 Mandler Mar 1998 A
5737732 Gibson et al. Apr 1998 A
5745654 Titan Apr 1998 A
5748098 Grace May 1998 A
5765143 Sheldon et al. Jun 1998 A
5768423 Aref et al. Jun 1998 A
5771562 Harvey et al. Jun 1998 A
5774692 Boyer et al. Jun 1998 A
5774868 Cragun et al. Jun 1998 A
5774883 Andersen Jun 1998 A
5778405 Ogawa Jul 1998 A
5793972 Shane Aug 1998 A
5797136 Boyer et al. Aug 1998 A
5802142 Browne Sep 1998 A
5812840 Shwartz Sep 1998 A
5819226 Gopinathan et al. Oct 1998 A
5822750 Jou et al. Oct 1998 A
5822751 Gray et al. Oct 1998 A
5825884 Zdepski et al. Oct 1998 A
5828833 Belville et al. Oct 1998 A
5832068 Smith Nov 1998 A
5835915 Carr Nov 1998 A
5844218 Kawan et al. Dec 1998 A
5864830 Armetta et al. Feb 1999 A
5870721 Norris Feb 1999 A
5875108 Hoffberg et al. Feb 1999 A
5875236 Jankowitz Feb 1999 A
5878403 DeFrancesco Mar 1999 A
5881131 Farris et al. Mar 1999 A
5884287 Edesess Mar 1999 A
5884289 Anderson et al. Mar 1999 A
5893090 Friedman et al. Apr 1999 A
5905985 Malloy et al. May 1999 A
5912839 Ovshinsky et al. Jun 1999 A
5924082 Silverman et al. Jul 1999 A
5930764 Melchione et al. Jul 1999 A
5930774 Chennault Jul 1999 A
5930776 Dykstra et al. Jul 1999 A
5940812 Tengel et al. Aug 1999 A
5950172 Klingman Sep 1999 A
5956693 Geerlings Sep 1999 A
5963932 Jakobsson et al. Oct 1999 A
5966695 Melchione et al. Oct 1999 A
5974396 Anderson Oct 1999 A
5995947 Fraser et al. Nov 1999 A
6014688 Venkatraman et al. Jan 2000 A
6021362 Maggard et al. Feb 2000 A
6026368 Brown et al. Feb 2000 A
6029139 Cunningham et al. Feb 2000 A
6029149 Dykstra et al. Feb 2000 A
6029154 Pettitt Feb 2000 A
6038551 Barlow et al. Mar 2000 A
6044357 Garg Mar 2000 A
6058375 Park May 2000 A
6061658 Chou et al. May 2000 A
6061691 Fox May 2000 A
6064973 Smith et al. May 2000 A
6064987 Walker May 2000 A
6070141 Houvener May 2000 A
6070142 McDonough et al. May 2000 A
6070147 Harms et al. May 2000 A
6073140 Morgan et al. Jun 2000 A
6088686 Walker et al. Jul 2000 A
6094643 Anderson et al. Jul 2000 A
6105007 Norris Aug 2000 A
6115690 Wong Sep 2000 A
6115693 McDonough et al. Sep 2000 A
6119103 Basch et al. Sep 2000 A
6121901 Welch et al. Sep 2000 A
6128599 Walker Oct 2000 A
6128602 Northington et al. Oct 2000 A
6128603 Dent Oct 2000 A
6128624 Papierniak et al. Oct 2000 A
6134548 Gottsman et al. Oct 2000 A
6144957 Cohen et al. Nov 2000 A
6151601 Papierniak et al. Nov 2000 A
6157927 Schaefer et al. Dec 2000 A
6178442 Yamazaki Jan 2001 B1
6185543 Galperin et al. Feb 2001 B1
6198217 Suzuki et al. Mar 2001 B1
6202053 Christiansen et al. Mar 2001 B1
6208979 Sinclair Mar 2001 B1
6223171 Chaudhuri Apr 2001 B1
6233566 Levine et al. May 2001 B1
6236977 Verba et al. May 2001 B1
6239352 Luch May 2001 B1
6249770 Erwin et al. Jun 2001 B1
6254000 Degen et al. Jul 2001 B1
6256630 Gilai et al. Jul 2001 B1
6263334 Fayyad et al. Jul 2001 B1
6263337 Fayyad et al. Jul 2001 B1
6278055 Forrest et al. Aug 2001 B1
6285983 Jenkins Sep 2001 B1
6304869 Moore et al. Oct 2001 B1
6307958 Deaton et al. Oct 2001 B1
6311169 Duhon Oct 2001 B2
6324524 Lent et al. Nov 2001 B1
6330546 Gopinathan et al. Dec 2001 B1
6330575 Moore et al. Dec 2001 B1
6334110 Walter et al. Dec 2001 B1
6339769 Cochrane et al. Jan 2002 B1
6345300 Bakshi et al. Feb 2002 B1
6366903 Agrawal et al. Apr 2002 B1
6385594 Lebda et al. May 2002 B1
6393406 Eder May 2002 B1
6405173 Honarvar Jun 2002 B1
6405181 Lent et al. Jun 2002 B2
6412012 Bieganski et al. Jun 2002 B1
6418436 Degen et al. Jul 2002 B1
6424956 Werbos Jul 2002 B1
6430539 Lazarus et al. Aug 2002 B1
6442577 Britton et al. Aug 2002 B1
6446200 Ball et al. Sep 2002 B1
6456979 Flagg Sep 2002 B1
6457012 Jatkowski Sep 2002 B1
6496819 Bello et al. Dec 2002 B1
6505168 Rothman et al. Jan 2003 B1
6513018 Culhane Jan 2003 B1
6523022 Hobbs Feb 2003 B1
6523041 Morgan et al. Feb 2003 B1
6567791 Lent et al. May 2003 B2
6574623 Laung et al. Jun 2003 B1
6597775 Lawyer et al. Jul 2003 B2
6601234 Bowman-Amuah Jul 2003 B1
6611816 Lebda et al. Aug 2003 B2
6615193 Kingdon et al. Sep 2003 B1
6615247 Murphy Sep 2003 B1
6622266 Goddard et al. Sep 2003 B1
6623529 Lakritz Sep 2003 B1
6640215 Galperin et al. Oct 2003 B1
6651220 Penteroudakis et al. Nov 2003 B1
6654727 Tilton Nov 2003 B2
6658393 Basch et al. Dec 2003 B1
6665715 Houri Dec 2003 B1
6687713 Mattson et al. Feb 2004 B2
6708166 Dysart et al. Mar 2004 B1
6714918 Hillmer et al. Mar 2004 B2
6714944 Shapiro et al. Mar 2004 B1
6735572 Landesmann May 2004 B2
6738748 Wetzer May 2004 B2
6748426 Shaffer et al. Jun 2004 B1
6757740 Parekh et al. Jun 2004 B1
6766327 Morgan, Jr. et al. Jul 2004 B2
6804346 Mewhinney Oct 2004 B1
6804701 Muret et al. Oct 2004 B2
6823319 Lynch et al. Nov 2004 B1
6836764 Hucal Dec 2004 B1
6839682 Blume et al. Jan 2005 B1
6839690 Foth et al. Jan 2005 B1
6850606 Lawyer et al. Feb 2005 B2
6850895 Brodersen et al. Feb 2005 B2
6859785 Case Feb 2005 B2
6865566 Serrano-Morales et al. Mar 2005 B2
6873979 Fishman et al. Mar 2005 B2
6901406 Nabe et al. May 2005 B2
6910624 Natsuno Jun 2005 B1
6934714 Meinig Aug 2005 B2
6954757 Zargham et al. Oct 2005 B2
6959281 Freeling et al. Oct 2005 B1
6965889 Serrano-Morales et al. Nov 2005 B2
6983379 Spalink et al. Jan 2006 B1
6983478 Grauch et al. Jan 2006 B1
6985887 Sunstein et al. Jan 2006 B1
6991159 Zenou Jan 2006 B2
6993493 Galperin et al. Jan 2006 B1
7003504 Angus Feb 2006 B1
7028001 Muthuswamy et al. Apr 2006 B1
7028052 Chapman et al. Apr 2006 B2
7031945 Donner Apr 2006 B1
7035855 Kilger et al. Apr 2006 B1
7039176 Borodow et al. May 2006 B2
7047251 Reed et al. May 2006 B2
7050986 Vance et al. May 2006 B1
7050989 Hurt et al. May 2006 B1
7054828 Heching et al. May 2006 B2
7072963 Anderson et al. Jul 2006 B2
7076462 Nelson et al. Jul 2006 B1
7076475 Honarvar et al. Jul 2006 B2
7082435 Guzman et al. Jul 2006 B1
7117172 Black Oct 2006 B1
7133935 Hedy Nov 2006 B2
7143063 Lent Nov 2006 B2
7152053 Serrano-Morales et al. Dec 2006 B2
7165036 Kruk et al. Jan 2007 B2
7165037 Lazarus et al. Jan 2007 B2
7167907 Shaffer et al. Jan 2007 B2
7184974 Shishido Feb 2007 B2
7185016 Rasmussen Feb 2007 B1
7188169 Buus et al. Mar 2007 B2
7200602 Jonas Apr 2007 B2
7212995 Schulkins May 2007 B2
7234156 French et al. Jun 2007 B2
7240059 Bayliss et al. Jul 2007 B2
7249048 O'Flaherty Jul 2007 B1
7249114 Burchetta et al. Jul 2007 B2
7263506 Lee et al. Aug 2007 B2
7272591 Ghazal et al. Sep 2007 B1
7275083 Seibel et al. Sep 2007 B1
7277875 Serrano-Morales et al. Oct 2007 B2
7277900 Ganesh et al. Oct 2007 B1
7283974 Katz et al. Oct 2007 B2
7296734 Pliha Nov 2007 B2
7313618 Braemer et al. Dec 2007 B2
7314166 Anderson et al. Jan 2008 B2
7314167 Kiliccote Jan 2008 B1
7324962 Valliani et al. Jan 2008 B1
7328169 Temares et al. Feb 2008 B2
7337133 Bezos et al. Feb 2008 B1
7343149 Benco Mar 2008 B2
7346573 Cobrinik et al. Mar 2008 B1
7366694 Lazerson Apr 2008 B2
7367011 Ramsey et al. Apr 2008 B2
7370044 Mulhern et al. May 2008 B2
7373324 Engin et al. May 2008 B1
7376603 Mayr et al. May 2008 B1
7376618 Anderson et al. May 2008 B1
7376714 Gerken May 2008 B1
7379880 Pathria et al. May 2008 B1
7383215 Navarro et al. Jun 2008 B1
7386786 Davis et al. Jun 2008 B2
7392203 Edison et al. Jun 2008 B2
7392216 Palmgren et al. Jun 2008 B1
7403942 Bayliss Jul 2008 B1
7409362 Calabria Aug 2008 B2
7421322 Silversmith et al. Sep 2008 B1
7421442 Gelb et al. Sep 2008 B2
7424439 Fayyad et al. Sep 2008 B1
7428509 Klebanoff Sep 2008 B2
7428526 Miller et al. Sep 2008 B2
7433855 Gavan et al. Oct 2008 B2
7433864 Malik Oct 2008 B2
7444302 Hu et al. Oct 2008 B2
7451113 Kasower Nov 2008 B1
7458508 Shao et al. Dec 2008 B1
7467127 Baccash et al. Dec 2008 B1
7467401 Cicchitto Dec 2008 B2
7472088 Taylor et al. Dec 2008 B2
7475118 Leiba et al. Jan 2009 B2
7483842 Fung et al. Jan 2009 B1
7499868 Galperin et al. Mar 2009 B2
7505938 Lang et al. Mar 2009 B2
7509117 Yum Mar 2009 B2
7512221 Toms Mar 2009 B2
7516149 Motwani et al. Apr 2009 B2
7529698 Joao May 2009 B2
7533179 Tarquini et al. May 2009 B2
7536346 Aliffi et al. May 2009 B2
7542993 Satterfield et al. Jun 2009 B2
7546266 Beirne et al. Jun 2009 B2
7548886 Kirkland et al. Jun 2009 B2
7552089 Bruer et al. Jun 2009 B2
7556192 Wokaty, Jr. Jul 2009 B2
7562093 Gelb et al. Jul 2009 B2
7562184 Henmi et al. Jul 2009 B2
7571139 Giordano et al. Aug 2009 B1
7575157 Barnhardt et al. Aug 2009 B2
7580856 Pliha Aug 2009 B1
7581112 Brown et al. Aug 2009 B2
7584126 White Sep 2009 B1
7584146 Duhon Sep 2009 B1
7590589 Hoffberg Sep 2009 B2
7593893 Ladd et al. Sep 2009 B1
7596512 Raines et al. Sep 2009 B1
7596716 Frost et al. Sep 2009 B2
7610216 May et al. Oct 2009 B1
7610243 Haggerty et al. Oct 2009 B2
7610257 Abrahams Oct 2009 B1
7613671 Serrano-Morales et al. Nov 2009 B2
7620592 O'Mara et al. Nov 2009 B2
7620596 Knudson et al. Nov 2009 B2
7623844 Herrmann et al. Nov 2009 B2
7624068 Heasley et al. Nov 2009 B1
7653592 Flaxman et al. Jan 2010 B1
7657471 Sankaran et al. Feb 2010 B1
7668769 Baker et al. Feb 2010 B2
7668840 Bayliss et al. Feb 2010 B2
7672833 Blume et al. Mar 2010 B2
7672865 Kumar et al. Mar 2010 B2
7672924 Scheurich et al. Mar 2010 B1
7672926 Ghazal et al. Mar 2010 B2
7676418 Chung Mar 2010 B1
7676751 Allen et al. Mar 2010 B2
7686214 Shao et al. Mar 2010 B1
7689494 Torre et al. Mar 2010 B2
7689504 Warren et al. Mar 2010 B2
7689505 Kasower Mar 2010 B2
7690032 Peirce Mar 2010 B1
7698163 Reed et al. Apr 2010 B2
7702550 Perg et al. Apr 2010 B2
7707059 Reed et al. Apr 2010 B2
7707102 Rothstein Apr 2010 B2
7708190 Brandt et al. May 2010 B2
7711635 Steele et al. May 2010 B2
7725300 Pinto et al. May 2010 B2
7734523 Cui et al. Jun 2010 B1
7734539 Ghosh et al. Jun 2010 B2
7742982 Chaudhuri et al. Jun 2010 B2
7747480 Agresta et al. Jun 2010 B1
7747559 Leitner et al. Jun 2010 B2
7752236 Williams et al. Jul 2010 B2
7756789 Welker et al. Jul 2010 B2
7761384 Madhogarhia Jul 2010 B2
7778885 Semprevivo et al. Aug 2010 B1
7783515 Kumar et al. Aug 2010 B1
7783562 Ellis Aug 2010 B1
7788147 Haggerty et al. Aug 2010 B2
7788152 Haggerty et al. Aug 2010 B2
7792732 Haggerty et al. Sep 2010 B2
7793835 Coggeshall et al. Sep 2010 B1
7797252 Rosskamm et al. Sep 2010 B2
7801811 Merrell et al. Sep 2010 B1
7801812 Conlin et al. Sep 2010 B2
7802104 Dickinson Sep 2010 B2
7805345 Abrahams et al. Sep 2010 B2
7805362 Merrell et al. Sep 2010 B1
7814004 Haggerty et al. Oct 2010 B2
7814005 Imrey et al. Oct 2010 B2
7818228 Coulter Oct 2010 B1
7822665 Haggerty et al. Oct 2010 B2
7827115 Weller et al. Nov 2010 B2
7835983 Lefner et al. Nov 2010 B2
7836111 Shan Nov 2010 B1
7840484 Haggerty et al. Nov 2010 B2
7844534 Haggerty et al. Nov 2010 B2
7848987 Haig Dec 2010 B2
7853518 Cagan Dec 2010 B2
7853998 Blaisdell et al. Dec 2010 B2
7856397 Whipple et al. Dec 2010 B2
7856494 Kulkarni Dec 2010 B2
7870078 Clark et al. Jan 2011 B2
7877320 Downey Jan 2011 B1
7890420 Haggerty et al. Feb 2011 B2
7908242 Achanta Mar 2011 B1
7912770 Haggerty et al. Mar 2011 B2
7912865 Akerman et al. Mar 2011 B2
7925549 Looney et al. Apr 2011 B2
7925582 Kornegay et al. Apr 2011 B1
7930242 Morris et al. Apr 2011 B2
7930285 Abraham et al. Apr 2011 B2
7941363 Tanaka et al. May 2011 B2
7958126 Schachter Jun 2011 B2
7962404 Metzger, II et al. Jun 2011 B1
7966255 Wong et al. Jun 2011 B2
7970676 Feinstein Jun 2011 B2
7983932 Kane Jul 2011 B2
7983976 Nafeh et al. Jul 2011 B2
7991666 Haggerty et al. Aug 2011 B2
7991677 Haggerty et al. Aug 2011 B2
7991689 Brunzell et al. Aug 2011 B1
7991901 Tarquini et al. Aug 2011 B2
7996521 Chamberlain et al. Aug 2011 B2
7996912 Spalink et al. Aug 2011 B2
8005759 Hirtenstein et al. Aug 2011 B2
8006261 Haberman et al. Aug 2011 B1
8015045 Galperin et al. Sep 2011 B2
8024245 Haggerty et al. Sep 2011 B2
8024264 Chaudhuri et al. Sep 2011 B2
8024778 Cash et al. Sep 2011 B2
8036979 Torrez et al. Oct 2011 B1
8060424 Kasower Nov 2011 B2
8065234 Liao et al. Nov 2011 B2
8073752 Haggerty et al. Dec 2011 B2
8073768 Haggerty et al. Dec 2011 B2
8078524 Crawford et al. Dec 2011 B2
8082202 Weiss Dec 2011 B2
8086509 Haggerty et al. Dec 2011 B2
8086524 Craig et al. Dec 2011 B1
8099341 Varghese Jan 2012 B2
8103530 Quiring et al. Jan 2012 B2
8121918 Haggerty et al. Feb 2012 B2
8126805 Sulkowski et al. Feb 2012 B2
8127982 Casey et al. Mar 2012 B1
8127986 Taylor et al. Mar 2012 B1
8131614 Haggerty et al. Mar 2012 B2
8131639 Haggerty et al. Mar 2012 B2
8145754 Chamberlain et al. Mar 2012 B2
8160960 Fei Apr 2012 B1
8161104 Tomkow Apr 2012 B2
8170938 Haggerty et al. May 2012 B2
8175945 Haggerty et al. May 2012 B2
8180654 Berkman et al. May 2012 B2
8185408 Baldwin, Jr. et al. May 2012 B2
8204774 Chwast et al. Jun 2012 B2
8209250 Bradway et al. Jun 2012 B2
8214238 Fairfield et al. Jul 2012 B1
8214262 Semprevivo et al. Jul 2012 B1
8271378 Chaudhuri et al. Sep 2012 B2
8280805 Abrahams et al. Oct 2012 B1
8285577 Galperin et al. Oct 2012 B1
8285656 Chang Oct 2012 B1
8290840 Kasower Oct 2012 B2
8296229 Yellin et al. Oct 2012 B1
8312033 McMillan Nov 2012 B1
8315942 Haggerty et al. Nov 2012 B2
8315943 Torrez et al. Nov 2012 B2
8321952 Spalink et al. Nov 2012 B2
8326671 Haggerty et al. Dec 2012 B2
8326672 Haggerty et al. Dec 2012 B2
8352343 Haggerty et al. Jan 2013 B2
8364518 Blake Jan 2013 B1
8386377 Xiong et al. Feb 2013 B1
8392334 Hirtenstein et al. Mar 2013 B2
8401889 Chwast et al. Mar 2013 B2
8458074 Showalter Jun 2013 B2
8463919 Tarquini et al. Jun 2013 B2
8468198 Tomkow Jun 2013 B2
8478673 Haggerty et al. Jul 2013 B2
8478674 Kapczynski et al. Jul 2013 B1
8510184 Imrev et al. Aug 2013 B2
8515828 Wolf et al. Aug 2013 B1
8515862 Zhang Aug 2013 B2
8533322 Chamberlain et al. Sep 2013 B2
8560434 Morris et al. Oct 2013 B2
8595101 Daukas et al. Nov 2013 B1
8600854 Mayr et al. Dec 2013 B2
8606626 DeSoto et al. Dec 2013 B1
8606666 Courbage et al. Dec 2013 B1
8626646 Torrez et al. Jan 2014 B2
8630929 Haggerty et al. Jan 2014 B2
8639616 Rolenaitis et al. Jan 2014 B1
8639920 Stack et al. Jan 2014 B2
8694390 Imrey et al. Apr 2014 B2
8706596 Cohen et al. Apr 2014 B2
8732004 Ramos et al. May 2014 B1
8738515 Chaudhuri et al. May 2014 B2
8775299 Achanta et al. Jul 2014 B2
8781953 Kasower Jul 2014 B2
8781975 Bennett et al. Jul 2014 B2
8825544 Imrey et al. Sep 2014 B2
9058340 Chamberlain et al. Jun 2015 B1
9508092 De Soto et al. Nov 2016 B1
9509711 Keanini Nov 2016 B1
9563916 Torrez et al. Feb 2017 B1
9619579 Courbage et al. Apr 2017 B1
9652802 Kasower May 2017 B1
9870589 Arnold Jan 2018 B1
9916621 Wasser Mar 2018 B1
20010011245 Duhon Aug 2001 A1
20010013011 Day et al. Aug 2001 A1
20010016833 Everling et al. Aug 2001 A1
20010027413 Bhutta Oct 2001 A1
20010037332 Miller et al. Nov 2001 A1
20010039523 Iwamoto Nov 2001 A1
20020019804 Sutton Feb 2002 A1
20020023051 Kunzle et al. Feb 2002 A1
20020023143 Stephenson et al. Feb 2002 A1
20020026507 Sears et al. Feb 2002 A1
20020035511 Haji et al. Mar 2002 A1
20020046096 Srinivasan et al. Apr 2002 A1
20020049626 Mathis et al. Apr 2002 A1
20020049701 Nabe et al. Apr 2002 A1
20020049738 Epstein Apr 2002 A1
20020052836 Galperin et al. May 2002 A1
20020055869 Hegg May 2002 A1
20020069122 Yun et al. Jun 2002 A1
20020077964 Brody Jun 2002 A1
20020082892 Raffel et al. Jun 2002 A1
20020087460 Hornung Jul 2002 A1
20020095360 Joao Jul 2002 A1
20020099628 Takaoka et al. Jul 2002 A1
20020099641 Mills et al. Jul 2002 A1
20020099649 Lee et al. Jul 2002 A1
20020099824 Bender et al. Jul 2002 A1
20020101979 Borodow et al. Aug 2002 A1
20020103809 Starzl et al. Aug 2002 A1
20020111816 Lortscher et al. Aug 2002 A1
20020111845 Chong Aug 2002 A1
20020123928 Eldering et al. Sep 2002 A1
20020128960 Lambiotte et al. Sep 2002 A1
20020128962 Kasower Sep 2002 A1
20020133444 Sankaran et al. Sep 2002 A1
20020133504 Vlahos et al. Sep 2002 A1
20020138297 Lee Sep 2002 A1
20020138331 Hosea et al. Sep 2002 A1
20020138417 Lawrence Sep 2002 A1
20020143661 Tumulty et al. Oct 2002 A1
20020147623 Rifaat Oct 2002 A1
20020147669 Taylor et al. Oct 2002 A1
20020147695 Khedkar et al. Oct 2002 A1
20020156676 Ahrens et al. Oct 2002 A1
20020161664 Shaya et al. Oct 2002 A1
20020161711 Sartor et al. Oct 2002 A1
20020165757 Lisser Nov 2002 A1
20020169747 Chapman et al. Nov 2002 A1
20020173984 Robertson et al. Nov 2002 A1
20020184255 Edd et al. Dec 2002 A1
20020188544 Wizon et al. Dec 2002 A1
20020194099 Weiss Dec 2002 A1
20020194140 Makuck Dec 2002 A1
20020198824 Cook Dec 2002 A1
20030000568 Gonsiorawski Jan 2003 A1
20030002639 Huie Jan 2003 A1
20030004787 Tripp et al. Jan 2003 A1
20030004855 Dutta et al. Jan 2003 A1
20030004865 Kinoshita Jan 2003 A1
20030009368 Kitts Jan 2003 A1
20030009393 Norris et al. Jan 2003 A1
20030009418 Green et al. Jan 2003 A1
20030009426 Ruiz-Sanchez Jan 2003 A1
20030018549 Fei et al. Jan 2003 A1
20030018578 Schultz Jan 2003 A1
20030018769 Foulger et al. Jan 2003 A1
20030023489 McGuire et al. Jan 2003 A1
20030033242 Lynch et al. Feb 2003 A1
20030033261 Knegendorf Feb 2003 A1
20030036996 Lazerson Feb 2003 A1
20030041031 Hedy Feb 2003 A1
20030046222 Bard et al. Mar 2003 A1
20030046223 Crawford et al. Mar 2003 A1
20030050882 Degen et al. Mar 2003 A1
20030061132 Yu et al. Mar 2003 A1
20030061163 Durfield Mar 2003 A1
20030065563 Elliott et al. Apr 2003 A1
20030069839 Whittington et al. Apr 2003 A1
20030078877 Beirne et al. Apr 2003 A1
20030083893 Aliffi May 2003 A1
20030093311 Knowlson May 2003 A1
20030093366 Halper et al. May 2003 A1
20030097320 Gordon May 2003 A1
20030097342 Whittingtom May 2003 A1
20030097380 Mulhern et al. May 2003 A1
20030101344 Wheeler et al. May 2003 A1
20030105696 Kalotay et al. Jun 2003 A1
20030105728 Yano et al. Jun 2003 A1
20030110111 Nalebuff et al. Jun 2003 A1
20030110293 Friedman et al. Jun 2003 A1
20030113727 Girn et al. Jun 2003 A1
20030115080 Kasravi et al. Jun 2003 A1
20030115133 Bian Jun 2003 A1
20030120591 Birkhead et al. Jun 2003 A1
20030135451 O'Brien et al. Jul 2003 A1
20030139986 Roberts Jul 2003 A1
20030144950 O'Brien et al. Jul 2003 A1
20030149610 Rowan et al. Aug 2003 A1
20030158751 Suresh et al. Aug 2003 A1
20030164497 Carcia et al. Sep 2003 A1
20030167218 Field et al. Sep 2003 A1
20030171942 Gaito Sep 2003 A1
20030182214 Taylor Sep 2003 A1
20030191731 Stewart et al. Oct 2003 A1
20030195830 Merkoulovitch et al. Oct 2003 A1
20030195859 Lawrence Oct 2003 A1
20030205845 Pichler et al. Nov 2003 A1
20030208428 Raynes et al. Nov 2003 A1
20030212618 Keyes et al. Nov 2003 A1
20030212654 Harper et al. Nov 2003 A1
20030216965 Libman Nov 2003 A1
20030225656 Aberman et al. Dec 2003 A1
20030225692 Bosch et al. Dec 2003 A1
20030229892 Sardera Dec 2003 A1
20030233323 Bilski et al. Dec 2003 A1
20030236738 Lange et al. Dec 2003 A1
20040002916 Timmerman et al. Jan 2004 A1
20040006536 Kawashima et al. Jan 2004 A1
20040010443 May et al. Jan 2004 A1
20040010458 Friedman Jan 2004 A1
20040019518 Abraham et al. Jan 2004 A1
20040023637 Johnson et al. Feb 2004 A1
20040024692 Turbeville et al. Feb 2004 A1
20040029311 Snyder et al. Feb 2004 A1
20040030649 Nelson et al. Feb 2004 A1
20040030667 Xu et al. Feb 2004 A1
20040033375 Mori Feb 2004 A1
20040034570 Davis et al. Feb 2004 A1
20040039681 Cullen et al. Feb 2004 A1
20040039688 Sulkowski et al. Feb 2004 A1
20040044615 Xue et al. Mar 2004 A1
20040044617 Lu Mar 2004 A1
20040046497 Shaepkens et al. Mar 2004 A1
20040049452 Blagg Mar 2004 A1
20040054619 Watson et al. Mar 2004 A1
20040059653 Verkuylen et al. Mar 2004 A1
20040062213 Koss Apr 2004 A1
20040078248 Altschuler Apr 2004 A1
20040088221 Katz et al. May 2004 A1
20040093278 Burchetta et al. May 2004 A1
20040098625 Lagadec et al. May 2004 A1
20040102197 Dietz May 2004 A1
20040103147 Flesher et al. May 2004 A1
20040107123 Haffner et al. Jun 2004 A1
20040107125 Guheen et al. Jun 2004 A1
20040107132 Honarvar et al. Jun 2004 A1
20040111305 Gavan et al. Jun 2004 A1
20040111358 Lange et al. Jun 2004 A1
20040111359 Hudock Jun 2004 A1
20040111363 Trench et al. Jun 2004 A1
20040117235 Shacham Jun 2004 A1
20040117358 Von Kaenel et al. Jun 2004 A1
20040122730 Tucciarone et al. Jun 2004 A1
20040128150 Lundegren Jul 2004 A1
20040128230 Oppenheimer et al. Jul 2004 A1
20040128232 Descloux Jul 2004 A1
20040128236 Brown et al. Jul 2004 A1
20040139035 Wang Jul 2004 A1
20040143526 Monasterio et al. Jul 2004 A1
20040143546 Wood et al. Jul 2004 A1
20040153330 Miller et al. Aug 2004 A1
20040153448 Cheng Aug 2004 A1
20040158520 Noh Aug 2004 A1
20040163101 Swix Aug 2004 A1
20040167793 Masuoka et al. Aug 2004 A1
20040176995 Fusz Sep 2004 A1
20040177046 Ogram Sep 2004 A1
20040193535 Barazesh Sep 2004 A1
20040199456 Flint et al. Oct 2004 A1
20040199458 Ho Oct 2004 A1
20040199462 Starrs Oct 2004 A1
20040199789 Shaw et al. Oct 2004 A1
20040212299 Ishikawa et al. Oct 2004 A1
20040220896 Finlay et al. Nov 2004 A1
20040225586 Woods et al. Nov 2004 A1
20040225594 Nolan, III et al. Nov 2004 A1
20040225596 Kemper et al. Nov 2004 A1
20040230448 Schaich Nov 2004 A1
20040230459 Dordick et al. Nov 2004 A1
20040230527 Hansen et al. Nov 2004 A1
20040230534 McGough Nov 2004 A1
20040230820 Hui Hsu et al. Nov 2004 A1
20040243450 Bernard, Jr. Dec 2004 A1
20040243518 Clifton et al. Dec 2004 A1
20040243588 Tanner et al. Dec 2004 A1
20040243641 Allen et al. Dec 2004 A1
20040261116 Mckeown et al. Dec 2004 A1
20050010513 Duckworth et al. Jan 2005 A1
20050010555 Gallivan Jan 2005 A1
20050015330 Beery et al. Jan 2005 A1
20050021397 Cui et al. Jan 2005 A1
20050021476 Candella et al. Jan 2005 A1
20050027983 Klawon Feb 2005 A1
20050033734 Chess et al. Feb 2005 A1
20050038726 Salomon et al. Feb 2005 A1
20050049991 Aggarwal Mar 2005 A1
20050050027 Yeh et al. Mar 2005 A1
20050058262 Timmins et al. Mar 2005 A1
20050086261 Mammone Apr 2005 A1
20050086579 Leitner et al. Apr 2005 A1
20050091164 Varble Apr 2005 A1
20050097039 Kulcsar et al. May 2005 A1
20050102206 Savasoglu et al. May 2005 A1
20050102226 Oppenheimer et al. May 2005 A1
20050125350 Tidwell et al. Jun 2005 A1
20050130704 McParland et al. Jun 2005 A1
20050137963 Ricketts et al. Jun 2005 A1
20050144641 Lewis Jun 2005 A1
20050149433 Rothstein Jul 2005 A1
20050154664 Guy et al. Jul 2005 A1
20050154665 Kerr Jul 2005 A1
20050159996 Lazaraus et al. Jul 2005 A1
20050177489 Neff et al. Aug 2005 A1
20050192008 Desai et al. Sep 2005 A1
20050197953 Broadbent et al. Sep 2005 A1
20050197954 Maitland et al. Sep 2005 A1
20050201272 Wang et al. Sep 2005 A1
20050209922 Hofmeister Sep 2005 A1
20050222900 Fuloria et al. Oct 2005 A1
20050228692 Hodgon Oct 2005 A1
20050251820 Stefanik et al. Nov 2005 A1
20050256809 Sadri Nov 2005 A1
20050262014 Fickes Nov 2005 A1
20050262158 Sauermann Nov 2005 A1
20050273442 Bennett et al. Dec 2005 A1
20050278246 Friedman et al. Dec 2005 A1
20050278542 Pierson et al. Dec 2005 A1
20050288998 Verma et al. Dec 2005 A1
20050289003 Thompson Dec 2005 A1
20060004731 Seibel et al. Jan 2006 A1
20060010055 Morita et al. Jan 2006 A1
20060014129 Coleman et al. Jan 2006 A1
20060020611 Gilbert et al. Jan 2006 A1
20060031158 Orman Feb 2006 A1
20060031747 Wada et al. Feb 2006 A1
20060032909 Seegar Feb 2006 A1
20060036543 Blagg et al. Feb 2006 A1
20060041443 Horvath Feb 2006 A1
20060041464 Powers et al. Feb 2006 A1
20060041840 Blair Feb 2006 A1
20060059073 Walzak Mar 2006 A1
20060059110 Madhok et al. Mar 2006 A1
20060074986 Mallalieu et al. Apr 2006 A1
20060074991 Lussier et al. Apr 2006 A1
20060080126 Greer et al. Apr 2006 A1
20060080230 Freiberg Apr 2006 A1
20060080233 Mendelovich et al. Apr 2006 A1
20060080251 Fried et al. Apr 2006 A1
20060080263 Willis et al. Apr 2006 A1
20060085454 Blegen et al. Apr 2006 A1
20060089842 Medawar Apr 2006 A1
20060095363 May May 2006 A1
20060095923 Novack et al. May 2006 A1
20060100954 Schoen May 2006 A1
20060122921 Comerford et al. Jun 2006 A1
20060129428 Wennberg Jun 2006 A1
20060129481 Bhatt et al. Jun 2006 A1
20060131390 Kim Jun 2006 A1
20060136330 DeRoy et al. Jun 2006 A1
20060149674 Cook et al. Jul 2006 A1
20060155624 Schwartz Jul 2006 A1
20060155639 Lynch et al. Jul 2006 A1
20060161435 Atef et al. Jul 2006 A1
20060173726 Hall et al. Aug 2006 A1
20060173772 Hayes et al. Aug 2006 A1
20060173776 Shalley et al. Aug 2006 A1
20060178957 LeClaire Aug 2006 A1
20060178971 Owen et al. Aug 2006 A1
20060178983 Nice et al. Aug 2006 A1
20060195390 Rusk et al. Aug 2006 A1
20060202012 Grano et al. Sep 2006 A1
20060204051 Holland, IV Sep 2006 A1
20060206416 Farias Sep 2006 A1
20060212350 Ellis et al. Sep 2006 A1
20060218069 Aberman et al. Sep 2006 A1
20060218079 Goldblatt et al. Sep 2006 A1
20060229943 Mathias et al. Oct 2006 A1
20060229961 Lyftogt et al. Oct 2006 A1
20060229996 Keithley et al. Oct 2006 A1
20060239512 Petrillo Oct 2006 A1
20060242039 Haggerty et al. Oct 2006 A1
20060242046 Haggerty et al. Oct 2006 A1
20060242047 Haggerty et al. Oct 2006 A1
20060242048 Haggerty et al. Oct 2006 A1
20060242049 Haggerty et al. Oct 2006 A1
20060242050 Haggerty et al. Oct 2006 A1
20060242051 Haggerty et al. Oct 2006 A1
20060253328 Kohli et al. Nov 2006 A1
20060253358 Delgrosso et al. Nov 2006 A1
20060259364 Strock et al. Nov 2006 A1
20060262929 Vatanen et al. Nov 2006 A1
20060265243 Racho et al. Nov 2006 A1
20060265323 Winter et al. Nov 2006 A1
20060267999 Cash Nov 2006 A1
20060271456 Romain et al. Nov 2006 A1
20060271457 Romain et al. Nov 2006 A1
20060271472 Cagan Nov 2006 A1
20060271552 McChesney et al. Nov 2006 A1
20060277092 Williams Dec 2006 A1
20060277102 Agliozzo Dec 2006 A1
20060277141 Palmer Dec 2006 A1
20060282328 Gerace et al. Dec 2006 A1
20060282359 Nobili et al. Dec 2006 A1
20060293932 Cash Dec 2006 A1
20060293979 Cash Dec 2006 A1
20060294199 Bertholf Dec 2006 A1
20070005508 Chiang Jan 2007 A1
20070011026 Higgins et al. Jan 2007 A1
20070011083 Bird et al. Jan 2007 A1
20070016500 Chatterji et al. Jan 2007 A1
20070016501 Chatterji et al. Jan 2007 A1
20070016518 Atkinson et al. Jan 2007 A1
20070016522 Wang Jan 2007 A1
20070022141 Singleton et al. Jan 2007 A1
20070027778 Schellhammer et al. Feb 2007 A1
20070027791 Young et al. Feb 2007 A1
20070030282 Cash Feb 2007 A1
20070033227 Gaito et al. Feb 2007 A1
20070038483 Wood Feb 2007 A1
20070043654 Libman Feb 2007 A1
20070055598 Arnott et al. Mar 2007 A1
20070055599 Arnott Mar 2007 A1
20070067207 Haggerty et al. Mar 2007 A1
20070067208 Haggerty et al. Mar 2007 A1
20070067209 Haggerty et al. Mar 2007 A1
20070067285 Blume Mar 2007 A1
20070067297 Kublickis Mar 2007 A1
20070067437 Sindambiwe Mar 2007 A1
20070072190 Aggarwal Mar 2007 A1
20070078741 Haggerty et al. Apr 2007 A1
20070078985 Shao et al. Apr 2007 A1
20070083460 Bachenheimer Apr 2007 A1
20070093234 Willis et al. Apr 2007 A1
20070094137 Phillips et al. Apr 2007 A1
20070106582 Baker et al. May 2007 A1
20070112667 Rucker May 2007 A1
20070118393 Rosen et al. May 2007 A1
20070156554 Nikoley et al. Jul 2007 A1
20070156718 Hossfeld Jul 2007 A1
20070168246 Haggerty et al. Jul 2007 A1
20070168267 Zimmerman et al. Jul 2007 A1
20070185797 Robinson Aug 2007 A1
20070192165 Haggerty et al. Aug 2007 A1
20070192248 West Aug 2007 A1
20070205266 Carr et al. Sep 2007 A1
20070208653 Murphy Sep 2007 A1
20070220611 Socolow et al. Sep 2007 A1
20070226093 Chan Sep 2007 A1
20070226114 Haggerty et al. Sep 2007 A1
20070226130 Haggerty et al. Sep 2007 A1
20070244732 Chatterji et al. Oct 2007 A1
20070244807 Andringa et al. Oct 2007 A1
20070271178 Davis et al. Nov 2007 A1
20070282684 Prosser et al. Dec 2007 A1
20070282730 Carpenter et al. Dec 2007 A1
20070282736 Conlin et al. Dec 2007 A1
20070288271 Klinkhammer Dec 2007 A1
20070288355 Roland et al. Dec 2007 A1
20070288559 Parsadayan Dec 2007 A1
20070294163 Harmon et al. Dec 2007 A1
20070299759 Kelly Dec 2007 A1
20070299771 Brody Dec 2007 A1
20080004957 Hildreth et al. Jan 2008 A1
20080005313 Flake et al. Jan 2008 A1
20080010687 Gonen et al. Jan 2008 A1
20080015887 Drabek et al. Jan 2008 A1
20080021804 Deckoff Jan 2008 A1
20080028067 Berkhin et al. Jan 2008 A1
20080033852 Megdal et al. Feb 2008 A1
20080059224 Schechter Mar 2008 A1
20080059317 Chandran Mar 2008 A1
20080059449 Webster et al. Mar 2008 A1
20080065774 Keeler Mar 2008 A1
20080066188 Kwak Mar 2008 A1
20080071882 Hering et al. Mar 2008 A1
20080077526 Arumugam Mar 2008 A1
20080086368 Bauman et al. Apr 2008 A1
20080091463 Shakamuri Apr 2008 A1
20080097768 Godshalk Apr 2008 A1
20080097928 Paulson Apr 2008 A1
20080103800 Domenikos et al. May 2008 A1
20080103972 Lanc May 2008 A1
20080109444 Williams et al. May 2008 A1
20080120155 Pliha May 2008 A1
20080120569 Mann et al. May 2008 A1
20080126233 Hogan May 2008 A1
20080133322 Kalia et al. Jun 2008 A1
20080133531 Baskerville Jun 2008 A1
20080134042 Jankovich Jun 2008 A1
20080140476 Anand et al. Jun 2008 A1
20080140507 Hamlisch et al. Jun 2008 A1
20080140549 Eder Jun 2008 A1
20080147454 Walker et al. Jun 2008 A1
20080167883 Khazaneh Jul 2008 A1
20080167936 Kapoor Jul 2008 A1
20080175360 Schwarz et al. Jul 2008 A1
20080177836 Bennett Jul 2008 A1
20080183504 Highley Jul 2008 A1
20080183564 Tien et al. Jul 2008 A1
20080195425 Haggerty et al. Aug 2008 A1
20080195600 Deakter Aug 2008 A1
20080208548 Metzger et al. Aug 2008 A1
20080208631 Morita et al. Aug 2008 A1
20080208788 Merugu et al. Aug 2008 A1
20080215470 Sengupta et al. Sep 2008 A1
20080221934 Megdal et al. Sep 2008 A1
20080221947 Megdal et al. Sep 2008 A1
20080221970 Megdal et al. Sep 2008 A1
20080221971 Megdal et al. Sep 2008 A1
20080221972 Megdal et al. Sep 2008 A1
20080221973 Megdal et al. Sep 2008 A1
20080221990 Megdal et al. Sep 2008 A1
20080222016 Megdal et al. Sep 2008 A1
20080222027 Megdal et al. Sep 2008 A1
20080228538 Megdal et al. Sep 2008 A1
20080228539 Megdal et al. Sep 2008 A1
20080228540 Megdal et al. Sep 2008 A1
20080228541 Megdal et al. Sep 2008 A1
20080228556 Megdal et al. Sep 2008 A1
20080228606 Megdal et al. Sep 2008 A1
20080228635 Megdal et al. Sep 2008 A1
20080243680 Megdal et al. Oct 2008 A1
20080244008 Wilkinson et al. Oct 2008 A1
20080255897 Megdal et al. Oct 2008 A1
20080255992 Lin Oct 2008 A1
20080281737 Fajardo Nov 2008 A1
20080288382 Smith et al. Nov 2008 A1
20080294540 Celka Nov 2008 A1
20080294546 Flannery Nov 2008 A1
20080301016 Durvasula et al. Dec 2008 A1
20080320575 Gelb et al. Dec 2008 A1
20090006185 Stinson Jan 2009 A1
20090006475 Udezue et al. Jan 2009 A1
20090012889 Finch Jan 2009 A1
20090018996 Hunt et al. Jan 2009 A1
20090024428 Hudock, Jr. Jan 2009 A1
20090024505 Patel et al. Jan 2009 A1
20090037247 Quinn Feb 2009 A1
20090037323 Feinstein et al. Feb 2009 A1
20090043637 Eder Feb 2009 A1
20090044279 Crawford et al. Feb 2009 A1
20090060343 Rosca Mar 2009 A1
20090089190 Girulat Apr 2009 A1
20090089205 Bayne Apr 2009 A1
20090106150 Pelegero et al. Apr 2009 A1
20090112650 Iwane Apr 2009 A1
20090119169 Chandratillake et al. May 2009 A1
20090119199 Salahi May 2009 A1
20090125369 Kloostra et al. May 2009 A1
20090132347 Anderson et al. May 2009 A1
20090132559 Chamberlain et al. May 2009 A1
20090144102 Lopez Jun 2009 A1
20090144160 Haggerty et al. Jun 2009 A1
20090182653 Zimiles Jul 2009 A1
20090199264 Lang Aug 2009 A1
20090210886 Bhojwani et al. Aug 2009 A1
20090222308 Zoldi et al. Sep 2009 A1
20090222373 Choudhuri et al. Sep 2009 A1
20090222374 Choudhuri et al. Sep 2009 A1
20090222375 Choudhuri et al. Sep 2009 A1
20090222376 Choudhuri et al. Sep 2009 A1
20090222377 Choudhuri et al. Sep 2009 A1
20090222378 Choudhuri et al. Sep 2009 A1
20090222379 Choudhuri et al. Sep 2009 A1
20090222380 Choudhuri et al. Sep 2009 A1
20090228918 Rolff et al. Sep 2009 A1
20090234665 Conkel Sep 2009 A1
20090234775 Whitney et al. Sep 2009 A1
20090240609 Cho et al. Sep 2009 A1
20090248567 Haggerty et al. Oct 2009 A1
20090248568 Haggerty et al. Oct 2009 A1
20090248569 Haggerty et al. Oct 2009 A1
20090248570 Haggerty et al. Oct 2009 A1
20090248571 Haggerty et al. Oct 2009 A1
20090248572 Haggerty et al. Oct 2009 A1
20090248573 Haggerty et al. Oct 2009 A1
20090254476 Sharma et al. Oct 2009 A1
20090254971 Herz et al. Oct 2009 A1
20090313163 Wang et al. Dec 2009 A1
20090319648 Dutta et al. Dec 2009 A1
20090327120 Eze et al. Dec 2009 A1
20100009320 Wilkelis Jan 2010 A1
20100010935 Shelton Jan 2010 A1
20100030649 Ubelhor Feb 2010 A1
20100043055 Baumgart Feb 2010 A1
20100094758 Chamberlain Apr 2010 A1
20100094768 Miltonberger Apr 2010 A1
20100100945 Ozzie et al. Apr 2010 A1
20100107225 Spencer et al. Apr 2010 A1
20100114744 Gonen May 2010 A1
20100121767 Coulter et al. May 2010 A1
20100130172 Vendrow et al. May 2010 A1
20100145836 Baker et al. Jun 2010 A1
20100145840 Kasower Jun 2010 A1
20100169159 Rose et al. Jul 2010 A1
20100169264 O'Sullivan et al. Jul 2010 A1
20100205662 Ibrahim et al. Aug 2010 A1
20100211445 Bodington Aug 2010 A1
20100217837 Ansari et al. Aug 2010 A1
20100223168 Haggerty et al. Sep 2010 A1
20100228657 Kagarlis Sep 2010 A1
20100229245 Singhal Sep 2010 A1
20100248681 Phills Sep 2010 A1
20100250364 Song et al. Sep 2010 A1
20100250411 Ogrodski Sep 2010 A1
20100250434 Megdal et al. Sep 2010 A1
20100250469 Megdal et al. Sep 2010 A1
20100250497 Redlich et al. Sep 2010 A1
20100274739 Haggerty et al. Oct 2010 A1
20100293114 Khan et al. Nov 2010 A1
20100312717 Haggerty et al. Dec 2010 A1
20110004498 Readshaw Jan 2011 A1
20110016042 Cho et al. Jan 2011 A1
20110023115 Wright Jan 2011 A1
20110035333 Haggerty et al. Feb 2011 A1
20110047071 Choudhuri et al. Feb 2011 A1
20110060905 Stack et al. Mar 2011 A1
20110066495 Ayloo et al. Mar 2011 A1
20110078073 Annappindi et al. Mar 2011 A1
20110093383 Haggerty et al. Apr 2011 A1
20110112958 Haggerty et al. May 2011 A1
20110126275 Anderson et al. May 2011 A1
20110137760 Rudie et al. Jun 2011 A1
20110137789 Kortina et al. Jun 2011 A1
20110164746 Nice et al. Jul 2011 A1
20110173116 Yan et al. Jul 2011 A1
20110184838 Winters et al. Jul 2011 A1
20110184851 Megdal et al. Jul 2011 A1
20110211445 Chen Sep 2011 A1
20110213641 Metzger, II et al. Sep 2011 A1
20110218826 Birtel et al. Sep 2011 A1
20110219421 Ullman et al. Sep 2011 A1
20110238566 Santos Sep 2011 A1
20110258050 Chan et al. Oct 2011 A1
20110258142 Haggerty et al. Oct 2011 A1
20110264581 Clyne Oct 2011 A1
20110270779 Showalter Nov 2011 A1
20110282779 Megdal et al. Nov 2011 A1
20120005070 McFall et al. Jan 2012 A1
20120011056 Ward et al. Jan 2012 A1
20120029956 Ghosh et al. Feb 2012 A1
20120035980 Haggerty et al. Feb 2012 A1
20120054592 Jaffe et al. Mar 2012 A1
20120066065 Switzer Mar 2012 A1
20120066106 Papadimitriou Mar 2012 A1
20120072464 Cohen Mar 2012 A1
20120084230 Megdal et al. Apr 2012 A1
20120101938 Kasower Apr 2012 A1
20120101939 Kasower Apr 2012 A1
20120106801 Jackson May 2012 A1
20120116807 Hane et al. May 2012 A1
20120123968 Megdal et al. May 2012 A1
20120124498 Santoro et al. May 2012 A1
20120136763 Megdal et al. May 2012 A1
20120143637 Paradis et al. Jun 2012 A1
20120173339 Flynt et al. Jul 2012 A1
20120179536 Kalb et al. Jul 2012 A1
20120191479 Gupta et al. Jul 2012 A1
20120265607 Belwadi Oct 2012 A1
20120265661 Megdal et al. Oct 2012 A1
20120290660 Rao et al. Nov 2012 A1
20130085902 Chew Apr 2013 A1
20130103571 Chung et al. Apr 2013 A1
20130124392 Achanta May 2013 A1
20130132151 Stibel et al. May 2013 A1
20130173359 Megdal et al. Jul 2013 A1
20130173481 Hirtenstein et al. Jul 2013 A1
20130268324 Megdal et al. Oct 2013 A1
20130275331 Megdal et al. Oct 2013 A1
20130293363 Plymouth Nov 2013 A1
20140012633 Megdal et al. Jan 2014 A1
20140019331 Megdal et al. Jan 2014 A1
20140032265 Paprocki et al. Jan 2014 A1
20140032384 Megdal et al. Jan 2014 A1
20140096249 Dupont et al. Apr 2014 A1
20140156501 Howe Jun 2014 A1
20140164112 Kala Jun 2014 A1
20140244353 Winters Aug 2014 A1
20170278182 Kasower Sep 2017 A1
Foreign Referenced Citations (76)
Number Date Country
91 08 341 Oct 1991 DE
0 350 907 Jan 1990 EP
0 419 889 Apr 1991 EP
0 458 698 Nov 1991 EP
0 468 440 Jan 1992 EP
0 554 083 Aug 1993 EP
0 566 736 Aug 1993 EP
0 559 358 Sep 1993 EP
0 869 652 Oct 1998 EP
0 913 789 May 1999 EP
0 977 128 Feb 2000 EP
1 028 401 Aug 2000 EP
1 122 664 Aug 2001 EP
0 772 836 Dec 2001 EP
2 392 748 Mar 2004 GB
10-222559 Aug 1998 JP
10-261009 Sep 1998 JP
10-293732 Nov 1998 JP
2000-331068 Nov 2000 JP
2001-282957 Oct 2001 JP
2001-297141 Oct 2001 JP
2001-344463 Dec 2001 JP
2001-357256 Dec 2001 JP
2002-149778 May 2002 JP
2002-163449 Jun 2002 JP
2002-163498 Jun 2002 JP
2002-259753 Sep 2002 JP
2003-271851 Sep 2003 JP
2003-316881 Nov 2003 JP
2003-316950 Nov 2003 JP
10-2000-0036594 Jul 2000 KR
10-2000-0063995 Nov 2000 KR
10-2001-0016349 Mar 2001 KR
10-2001-0035145 May 2001 KR
10-2002-0007132 Jan 2002 KR
10-2004-0078798 Sep 2004 KR
WO 94006103 Mar 1994 WO
WO 950034155 Dec 1995 WO
WO 96000945 Jan 1996 WO
WO 98041931 Sep 1998 WO
WO 98041932 Sep 1998 WO
WO 98041933 Sep 1998 WO
WO 98049643 Nov 1998 WO
WO 99004350 Jan 1999 WO
WO 99017225 Apr 1999 WO
WO 99017226 Apr 1999 WO
WO 99038094 Jul 1999 WO
WO 99046710 Sep 1999 WO
WO 00004465 Jan 2000 WO
WO 00028441 May 2000 WO
WO 00055789 Sep 2000 WO
WO 00055790 Sep 2000 WO
WO 01010090 Feb 2001 WO
WO 01011522 Feb 2001 WO
WO 01016896 Mar 2001 WO
WO 01039090 May 2001 WO
WO 01039589 Jun 2001 WO
WO 01041083 Jun 2001 WO
WO 01057720 Aug 2001 WO
WO 01075754 Oct 2001 WO
WO 01080053 Oct 2001 WO
WO 01084281 Nov 2001 WO
WO 02027610 Apr 2002 WO
WO 03071388 Aug 2003 WO
WO 03101123 Dec 2003 WO
WO 2004046882 Jun 2004 WO
WO 2004114160 Dec 2004 WO
WO 2007149941 Dec 2007 WO
WO 2008022289 Feb 2008 WO
WO 2008054403 May 2008 WO
WO 2008127288 Oct 2008 WO
WO 2009117518 Sep 2009 WO
WO 2009132114 Oct 2009 WO
WO 2010132492 Nov 2010 WO
WO 2013009920 Jan 2013 WO
WO 2014018900 Jan 2014 WO
Non-Patent Literature Citations (209)
Entry
U.S. Appl. No. 12/022,954, U.S. Pat. No. 8,606,666, System and Method for Providing an Aggregation Tool, filed Jan. 30, 2008.
U.S. Appl. No. 14/091,174, U.S. Pat. No. 9,619,579, System and Method for Providing an Aggregation Tool, filed Nov. 26, 2013.
U.S. Appl. No. 12/705,489, filed Feb. 12, 2010, Bargoli et al.
U.S. Appl. No. 12/705,511, filed Feb. 12, 2010, Bargoli et al.
U.S. Appl. No. 60/146,074, filed Jul. 28, 1999, Tomkow.
U.S. Appl. No. 60/172,479, filed Dec. 17, 1999, Tomkow.
Announcing TrueProfiler, http://web.archive.org/web/20021201123646/http://www.truecredit.com/index.asp, dated Dec. 1, 2002, 2 pages.
Applied Geographic Solutions, “What is MOSAIC™”, as captured Feb. 15, 2004 from http://web.archive.org/web/20040215224329/http://www.appliedgeographic.com/mosaic.html in 2 pages.
“AT&T Expected to Turn Up Heat in Card Wars”, American Banker, May 27, 1993, vol. 158, No. 101, pp. 3.
“Bank of America Direct Web-Based Network Adds Core Functionality to Meet Day-to-Day Treasury Needs”, Business Wire, Oct. 25, 1999. pp. 2.
Bitran et al., “Mailing Decisions in Catalog Sales Industry”, Management Science (JSTOR), vol. 42, No. 9, pp. 1364-1381, Sep. 1996.
Brown et al., “ALCOD IDSS:Assisting the Australian Stock Market Surveillance Team's Review Process,” Applied Artificial Intelligence Journal, Dec. 1, 1996, pp. 625-641.
Bult et al., “Optimal Selection for Direct Mail,” Marketing Science, 1995, vol. 14, No. 4, pp. 378-394.
Buxfer, http://www.buxfer.com/ printed Feb. 5, 2014 in 1 page.
Cantor, R. and Packer, F., “The Credit Rating Industry,” FRBNY Quarterly Review, Summer-Fall, 1994, pp. 1-24.
ChannelWave.com, PRM Central—About PRM, http://web.archive.org/web/20000510214859/http://www.channelwave.com as printed on Jun. 21, 2006, May 2000 Archive.
“Chase Gets Positive,” Bank Technology News, May 6, 2000, vol. 14, No. 5, p. 33.
Chatterjee et al., “Expenditure Patterns and Aggregate Consumer Behavior, Some Experiments with Australian and New Zealand Data”, The Economic Record, vol. 70, No. 210, Sep. 1994, pp. 278-291.
Check, http://check.me/ printed Feb. 5, 2014 in 3 pages.
Chen, et al., “Modeling Credit Card ‘Share of Wallet’: Solving the Incomplete Information Problem”, New York University: Kauffman Management Center, http://www.rhsmith.umd.edu/marketing/pdfs_docs/seminarsspr05/abstract%20-%20chen.pdf , Spring 2005, 48 pages.
CreditAnalyst, Digital Matrix Systems, as printed out Mar. 4, 2008, pp. 2.
CreditToolkit, Digital Matrix Systems, as printed out Mar. 4, 2008, pp. 2.
CreditXpert, http://www.creditxpert.com/Products/individuals.asp printed Oct. 12, 2012 in 1 page.
Cohen et al., “Optimizer: IBM's Multi Echelon Inventory System for Managing Service Logistics”, Interfaces, vol. 20, pp. 65-82, Jan.-Feb. 1990.
ComScore Networks Launches Business Unit to Help Credit Card Marketers Master Online and Multi-Channel Strategies—Solutions Provide Unprecedented Insight Into Customer Acquisition and Usage Opportunities, Reston, VA, Oct. 11, 2001, 2 pages.
Credit Risk Management Report, Potomac, Mar. 9, 1998, vol. 8, No. 4.
CreditXpert Inc., CreditXpert 3—Bureau Comparison™, 2002, pp. 5, http://web.archive.org/web/20030608171018/http://creditxpert.com/CreditXpert%203-Bureau%20Comparison(TM)%20sample.pdf.
CreditXpert Inc., CreditXpert Credit Score & Analysis™, Jan. 11, 2000, pp. 6, http://web.archive.org/web/20030611070058/http://www.creditxpert.com/CreditXpert%20Score%20&%20Analysis%20and%20Credit%20Wizard%20sample.pdf.
CreditXpert Inc., CreditXpert Essentials™, Advisor View—Experian on Jul. 7, 2003, http://www.creditxpert.com/cx_ess_app.pdf.
CreditXpert Inc., CreditXpert Essentials™, Advisor View—TransUnion on Oct. 10, 1999, pp. 6, http://web.archive.org/web/20041211052543/http://creditxpert.com/cx_ess_app.pdf.
CreditXpert Inc., CreditXpert Essentials™, Applicant View—TransUnion on Oct. 10, 1999, pp. 6, http://www.creditxpert.com/cx_ess_app.pdf.
CreditXpert Inc., CreditXpert What-If Simulator™, 2002, pp. 8, http://web.archive.org/web/20030630132914/http://creditxpert.com/CreditXpert%20What-If%20Simulator(TM)%20sample.pdf.
Dataman Group, “Summarized Credit Statistics,” Aug. 22, 2001, http://web.archive.org/web/20010822113446/http://www.datamangroup.com/summarized_credit.asp.
“Debt Settlement: Watch Video on how to Pay Your Debt Faster”, http://www.debtconsolidationcare.com/debt-settlement.html printed Jan. 9, 2013 in 6 pages.
EFunds Introduces QualiFileSM, Deluxe Corporation, eFunds Press Release and Product Launch, Sep. 23, 1999, Milwaukee, WI.
Egol, Len; “What's New in Database Marketing Software,” Direct, Aug. 1994, vol. 6, No. 8, pp. 39.
Elmasri et al., “Fundamentals of Database Systems, Third Edition (Excerpts)”, Jun. 2000, pp. 253, 261, 268-70, 278-80, 585, 595.
Equifax; “True In-Market Propensity Scores™”, http://www.equifax.com/assets/USCIS/efx-00174-11-13_efx_tips.pdf, Nov. 2013 in 1 page.
Ettorre, “Paul Kahn on Exceptional Marketing,” Managemtent Review, vol. 83, No. 11, Nov. 1994, pp. 48-51.
“Equifax and FICO Serve Consumers”, Mortgage Servicing News, Mar. 2001, vol. 5, No. 3, p. 19.
Experian Announces PLUS Score; Experian Press Release dated Oct. 16, 2003; Experian Global Press Office.
Experian and AGS Select SRC to Deliver Complete Marketing Solutions; Partnership First to Marketplace with Census2000 Data. PR Newswire. New York: Mar. 21, 2001. p. 1.
“Experian Launches Portfolio Monitor—Owner NoticesSM”, News Release, Feb. 2003, Costa Mesa, CA.
Experian-Scorex Announces New Credit Simulation Tool, PR Newswire, Costa Mesa, CA, Jun. 13, 2005.
Experian, Custom Strategist and Qualifile from Funds, 2000, in 2 pages.
Experian; “In the Market Models℠”, http://www.experian.com/assets/consumer-information/product-sheets/in-the-market-models.pdf, Sep. 2013 in 2 pages.
Experian Information Solutions, Inc., Credit Trends: Access Credit Trending Information Instantly, http://kewaneecreditbureau.com/Credit.Trends.pdf, Aug. 2000, pp. 4.
Fair Isaac Announces Integrated, End-to-End Collection and Recovery Solution, Business Wire, New York, Sep. 2, 2004, p. 1.
“Fair Isaac Offers New Fraud Tool”, National Mortgage News & Source Media, Inc., Jun. 13, 2005, pp. 2.
Fickenscher, Lisa, “Merchant American Express Seeks to Mine its Data on Cardholder Spending Patterns,” American Banker, vol. 162, Issue 56, Mar. 24, 1997, pp. 1-2.
“FinExtra, Basepoint Analytics Introduces Predictive Technology for Mortgage Fraud”, Oct. 5, 2005, pp. 3.
Fisher, Joseph, “Access to Fair Credit Reports: Current Practices and Proposed Legislation,” American Business Law Journal, Fall 1981, vol. 19, No. 3, p. 319.
Gilje, Shelby, “Keeping Tabs on Businesses That Keep Tabs on Us”, NewsRoom, The Seattle Times, Section: SCENE, Apr. 19, 1995, pp. 4.
Gonul, et al., “Optimal Mailing of Catalogs: A New Methodology Using Estimable Structural Dynamic Programming Models”, 14 pages, Management Science, vol. 44, No. 9, Sep. 1998.
Haffar, Imad, “‘SPAM’: A Computer Model for Management of Spare-Parts Inventories in Agricultural Machinery Dealerships”, Computers and Electronics in Agriculture, vol. 12, Issue 4, Jun. 1995, pp. 323-332.
Handfield, Robert B. et al., “Managing Component Life Cycles in Dynamic Technological Environments”, International Journal of Purchasing and Materials Management, Tempe, vol. 30, No. 2, pp. 20-28, Spring 1994, ProQuest ID 590096.
Haughton et al., “Direct Marketing Modeling with CART and CHAID”, Journal of Direct Marketing, Fall 1997, vol. 11, No. 4, pp. 42-52.
IDEON, Credit-Card Registry that Bellyflopped this Year, is Drawing some Bottom-Fishers, The Wall Street Journal, Aug. 21, 1995, pp. C2.
“Impac Funding Introduces Enhanced Website for Static Pool Tracking of MBS Transactions,” Waltham, MA; Webpage printed out from http://www.lewtan.com/press/1208044_Impac-Lewtan.htm on Mar. 20, 2008.
Inderfurth et al., “Decision Support for Spare Parts Acquisition in Post Product Life Cycle”, Central European Journal of Operations Research, vol. 16, pp. 17-42, 2008 [Initially published online Dec. 21, 2007].
Instant Access to Credit Reports Now Available Online with DMS' CreditBrowser-based system also Simplifies Credit Decisioning and Offers a Central Point of Control, Business Wire, Dallas, May 23, 2000, p. 0264.
“Japan's JAAI system appraises used cars over internet”, Asia Pulse, Mar. 3, 2000.
“JPMorgan Worldwide Securities Services to Acquire Paloma's Middle and Back Office Operations,” Webpage printed from http://www.jpmorgan.com on Apr. 1, 2009.
Käki, Anssi, “Forecasting in End-of-Life Spare Parts Procurement”, Master's Thesis—Helsinki University of Technology System Analysis Laboratory, Jul. 27, 2007.
Kim, Bowon et al., Optimal Pricing, EOL (End of Life) Warranty, and Spare Parts Manufacturing Strategy Amid Product Transition, European Journal of Operation Research, vol. 188, pp. 723-745, 2008 [Initially published online May 1, 2007].
Klein, et al., “A Constant-Utility Index of the Cost of Living”, The Review of Economic Studies, pp. 84-87, vol. XV-XVI, Kraus Reprint Corporation, New York, 1960.
Klein, et al., “An Econometric Model of the United States: 1929-1952”, North-Holland Publishing Company, Amsterdam, 1955, pp. 4-41.
Klein, Lawrence R., “The Keynesian Revolution”, New York, The MacMillan Company, 1947, pp. 56-189.
Krupp, James A.G.; “Forecasting for the Automotive Aftermarket”; The Journal of Business Forecasting Methods & Systems; Winter 1993-1994; 12, 4; ABI/Inform Global; pp. 8-12.
Lanubile, et al., “Evaluating Empirical Models for the Detection of High-Risk Components: Some Lessons Learned”, 20th Annual Software Engineering Workshop, Nov. 29-30, 1995, Greenbelt, Maryland, pp. 1-6.
Lapide, Larry, “New Developments in Business Forecasting”, The Journal of Business Forecasting, pp. 12-14, Spring 2002.
Loshin, Intelligent Enterprise: Better Insight for Business Decisions, “Value-Added Data: Merge Ahead”, Feb. 9, 2000, vol. 3, No. 3, 5 pages.
Manilla, http://www.manilla.com/how-it-works/ printed Feb. 5, 2014 in 1 page.
MergePower, Inc., “Attribute Pro”, http://web.archive.org/web/20060520135324/http://www.mergepower.com/attribute_pro.html, dated May 20, 2006 in 1 page.
Miller, Joe, “NADA used-car prices go online”, Automotive News, Jun. 14, 1999, p. 36.
Mint.com, http://www.mint.com/how-it-works/ printed Feb. 5, 2013 in 2 pages.
Moore, John R., Jr. “Forecasting and Scheduling for Past-Model Replacement Parts” Management Science, Application Series, vol. 18, No. 4, Part 1, Dec. 1971, pp. B200-B213.
Mvelopes, http://www.mvelopes.com/ printed Feb. 5, 2014 in 2 pages.
Otter, et al., “Direct Mail Selection by Joint Modeling of the Probability and Quantity of Response”, Jun. 1997, pp. 14.
Packer, A. H., “Simulation and Adaptive Forecasting an Applied to Inventory Control”, Operations Research, vol. 15, No. 4, pp. 660-679, Jul. 1965.
Pagano, et al., “Information Sharing in Credit Markets,” Dec. 1993, The Journal of Finance, vol. 48, No. 5, pp. 1693-1718.
“Parse”, Definition from PC Magazine Encyclopedia, http://www/pcmag.com/encyclopedia_term_0,2542,t=parse&i=48862,00.asp as downloaded Mar. 5, 2012.
PersonalCapital.com, http://www.personalcapital.com/how-it-works printed Feb. 5, 2014 in 5 pages.
Peters, Peter-Paul, “A Spare Parts Configurator for the European Service Business” (Graduation Report); Honeywell, Industrial Service Logistic Center; Amsterdam, The Netherlands; 80 Pgs.; Mar. 2000.
Ponniah, Paulraj, “Data Warehousing Fundamentals: A Comprehensive Guide for IT Professionals”, Wiley-Interscience Publication, pp. 257-289, 377-397, Aug. 3, 2001.
Porter, G. Zell, “An Economic Method for Evaluating Electronic Component Obsolescence Solutions”, Retrieved from the web at www.gidep.org/data/dmsms/library/zell.pdf, May 1998, pp. 1-9.
“PostX to Present at Internet Showcase”, PR Newswire, Apr. 28, 1997, pp. 2.
PostX, “PostX® Envelope and ActiveView”, http://web.archive.org/web/19970714203719/http://www.postx.com/priducts_fm.html, Jul. 14, 1997 (retrieved Nov. 7, 2013) in 2 pages.
Powerforms: Declarative Client-Side for Field Validation, ISSN 1386-145x, Dec. 2000.
“PremierGuide Announces Release 3.0 of Local Search Platform”, Business Wire, Mar. 4, 2004, Palo Alto, CA, p. 5574.
“Qualifying for Debt Settlement”, http://www.certifieddebt.com/debt/settlement-qualifications.shtml printed Jan. 9, 2013 in 2 pages.
Rahm, et al. “Data Cleaning: Problems and Current Approaches”, Bulletin of the IEEE Computer Society Technical Committee on Data Engineering, Dec. 2000, vol. 23, No. 4, pp. 11.
Raman, et al., “Potter's Wheel: An Interactive Data Cleaning System”, Proceedings of the 27th VLDB Conference, Roma, Italy, 2001, pp. 10.
“Resolve Debt for Less: With Help from Freedom Financial” http://www.debtsettlementusa.com/ printed Jan. 9, 2013 in 6 pages.
Roos, Gina, “Web-Based Service Helps OEMs Cure Parts Obsolescence Blues”, Electronic Engineering Times, p. 86, Oct. 8, 2001, Dialog 09056737 78968668.
Santarini, Michael, “Forecasts the Probable Obsolescence of Components—Module Predicts Parts Life”, Electronic Engineering Times, Jan. 11, 1999, p. 48(1), Dialog 0607160353548246.
Saunders, A., “Data Goldmine,” Management Today, London: Mar. 1, 2004, 6 pages.
Sawyers, Arlena, “NADA to Offer Residual Guide”, Automotive News, May 22, 2000, p. 3.
Sax, Michael M., Data Collection and Privacy Protection: An International Perspective, Presentation: Managing Online Risk and Liability Conference, Aug. 31, 1999, pp. 58.
“Settling Your Debts—Part 1 in Our Debt Settlement Series”, http://www.creditinfocenter.com/debt/settle_debts.shtml printed Jan. 9, 2013 in 6 pages.
Smith, Wendell R., “Product Differentiation and Market Segmentation as Alternative Marketing Strategies”, The Journal of Marketing, The American Marketing Association, Brattleboro, Vermont, Jul. 1956, vol. XXI, pp. 3-8.
Stanton, T.H., “Credit Scoring and Loan Scoring as Tools for Improved Management of Federal Credit Programs”, Financier, Philadelphia, Summer 1999, vol. 6, 36 pages.
Stone, “Linear Expenditure Systems and Demand Analysis: An Application to the Pattern of British Demand”, The Economic Journal: The Journal of the Royal Economic Society, Sep. 1954, pp. 511-527, vol. LXIV, Macmillan & Co., London.
Sullivan, Laurie, “Obsolete-Parts Program Thriving”, EBN, Manhasset, Issue 1296, p. 26, Jan. 2002, ProQuest 10 101195090.
Sweat, Jeff; “Know Your Customers,” Information Week, Nov. 30, 1998, pp. 20.
Tao, Lixin, “Shifting Paradigms with the Application Service Provider Model”; Concordia University, IEEE, Oct. 2001, Canada.
Tennant, Don, “How a Health Insurance Provider Uses Big Data to Predict Patient Needs,” http://www.itbusinessedge.com/blogs/from-under-the-rug/how-a-health-insurance-provider-uses-big-data-to-predict-patient-needs.html, printed Mar. 6, 2014 in 2 pages.
Van Collie, Shimon, “The Road to Better Credit-Card Marketing,” Bank Technology News, Sep. 1995, pp. 4.
Various Posts from the http://www.2p.wrox.com Forums: http://web.archive.org/web/2005045221950/http://p2p.wrox.com/topic.asp?TOPIC_ID=6513 , dated Nov. 15, 2003-Oct. 7, 2004.
Verstraeten, Geert, Ph.D.; Issues in predictive modeling of individual customer behavior: Applications in targeted marketing and consumer credit scoring; Unversiteit Gent (Belgium) 2005.
“WashingtonPost.com and Cars.com launch comprehensive automotive web site for the Washington area”, PR Newswire, Oct. 22, 1998.
Watts, Craig, “Fair, Isaac and Equifax Give Consumers New Score Power Tools Offering Greater Insights for Managing Their Credit Health,” May 21, 2002, pp. 3, http://www.myfico.com/PressRoom/PressReleases/2002_05_21.aspx.
Web Page posted at: http://web.archive.org/web20040805124909/http://www.oracle.com/technology/sample_codete/tech/pl_sql/htdocs/x/Case/start.htm, pp. 1 and 4 of the webpages posted on Jan. 7, 2003.
Webpage printed from http://www.magnum.net/pdfs/RapUpBrochure.pdf as printed Mar. 3, 2008.
Webpage printed out from http://www.jpmorgan.com/cm/ContentServer?c=TS_Content&pagename=jpmorgan%20Fts%2FTS_Content%2FGeneral&cid=1139403950394 on Mar. 20, 2008, Feb. 13, 2006, New York, NY.
Webpage printed out from http://www.fairisaac.com/NR/rdonlyres/AC4C2F79-4160-4E44-B0CB-5C899004879A/0/ScoreNetnetworkBR.pdf on Mar. 4, 2008.
Webster, Lee R., “Failure Rates & Life Cycle Costs”, Consulting-Specifying Engineer; 23, 4; ABI/INFORM Global, Apr. 1998, p. 42.
Working, Holbrook, “Statistical Laws of Family Expenditure”, Journal of the American Statistical Association, pp. 43-56, vol. 38, American Statistical Association, Washington, D.C., Mar. 1943.
Wyatt, Craig, “Usage Models just for Merchants,” Credit Card Management, Sep. 1995, vol. 8, No. 6, pp. 4.
YODLEE | Money Center, https://yodleemoneycenter.com/ printed Feb. 5, 2014 in 2 pages.
You Need a Budget, http://www.youneedabudget.com/features printed Feb. 5, 2014 in 3 pages.
Yücesan et al., “Distributed Web-Based Simulation Experiments for Optimization”, Simulation Practice and Theory 9, 2001, pp. 73-90.
Zimmerman et al., “A Web-Based Platform for Experimental Investigation of Electric Power Auctions,” Decision Support Systems, 1999, vol. 24, pp. 193-205.
Zoot—Decision Engine, www.zootweb.com/decision_engine.html, as printed on Mar. 3, 2008.
Zoot—Instant Rules GUI, www.zootweb.com/instant_rules_GUI.html as printed Mar. 3, 2008.
Zoot—Pre-Built Standard Attributes, www.zootweb.com/credit_attributes.html as printed Mar. 3, 2008.
Zoot—Rules Management GUI, www.zootweb.com/business_rules_GUI.html as printed Mar. 3, 2008.
Zoot—Zoot's Hosted Environment, http://www.zootweb.com/zootasp.html as printed Mar. 3, 2008.
International Search Report and Written Opinion for Application No. PCT/US2012/046316, dated Sep. 28, 2012.
International Preliminary Report on Patentability and Written Opinion for Application No. PCT/US2012/046316, dated Jan. 14, 2014.
International Search Report and Written Opinion for Application No. PCT/US09/60393, dated Dec. 23, 2009.
International Search Report and Written Opinion for Application No. PCT/US09/37565, dated May 12, 2009.
International Search Report and Written Opinion for Application No. PCT/US2010/034434, dated Jun. 23, 2010.
International Preliminary Report on Patentability for Application No. PCT/US2010/034434, dated Feb. 4, 2014.
MERit Credit Engine™, Diagram, http://creditengine.net/diagram.htm, copyright 1997, pp. 1.
MergePower, Inc., “MergePower, Inc”, http://web.archive.org/web/20060513003556/http:/www.mergepower.com/, dated May 13, 2006 in 1 page.
MergePower, Inc., “MergePower, Inc”, http://web.archive.org/web/20070208114622/http:/www.mergepower.com/, dated Feb. 8, 2007 in 1 page.
MergePower, Inc., “MergePower, Inc”, http://web.archive.org/web/20070914144019/http:/www.mergepower.com/, dated Sep. 14, 2007 in 1 page.
“STAGG Variables Sum Up Credit Attributes for Automated Decisions”, PRWeb, May 11, 2011, pp. 2. http://www.prweb.com/releases/2011/5/prweb8404324.htm.
“A Google Health update,” Google Official Blog, Sep. 15, 2010 in 4 pages, http://googleblog.blogspot.com/2010/09/google-health-update.html.
Akl, Selim G., “Digital Signatures: A Tutorial Survey,” Computer, Feb. 1983, pp. 15-24.
AISG's National Underwriting Database, A-PLUS, is Now the Largest in the Industry, Business Wire, Aug. 7, 1997.
“Balance Transfers Offer Opportunities”, Risk Credit Risk Management Report, Jan. 29, 1996, vol. 6, No. 2, pp. 2.
Burr Ph.D., et al., “Utility Payments as Alternative Credit Data: A Reality Check”, Asset Builders of America, Inc., Oct. 5, 2006, pp. 1-18, Washington, D.C.
“Cole Taylor Bank Chooses Integrated E-Banking/E-Payments/Reconciliation Solution From Fundtech”, Business Wire, Oct. 21, 1999, pp. 2.
Corepoint Health, “The Continuity of Care Document—Changing the Landscape of Healthcare Information Exchange,” Jan. 2009, pp. 9.
Cowie, Norman, “Warning Bells & ‘The Bust-Out’”, Business Credit, Jul. 1, 2000, pp. 5.
Credit Card Management, “Neural Nets Shoot for Jackpot,” Dec. 1995, pp. 1-6.
David, Alexander, “Controlling Information Premia by Repackaging Asset-Backed Securities,” The Journal of Risk and Insurance, Dec. 1997, 26 pages.
Davies, Donald W., “Applying the RSA Digital Signature to Electronic Mail,” Computer, Feb. 1983, pp. 55-62.
Dé, Andy, “Will mHealth Apps and Devices Empower ePatients for Wellness and Disease Management? A Case Study,” Jan. 10, 2011 in 6 pages, http://www.healthsciencestrategy.com/2011/04/will-mhealth-apps-and-devices-empower-epatients-for-wellness-and-disease-management-a-case-study-2/.
deGruchy, et al., “Geodemographic Profiling Benefits Stop-Smoking Service;” The British Journal of Healthcare Computing & Information Management; Feb. 2007; 24, 7; pp. 29-31.
Dillon et al., “Good Science”, Marketing Research: A Magazine of Management & Applications TM, Winter 1997, vol. 9, No. 4; pp. 11.
eFunds Corporation, “Data & Decisioning: Debit Report” printed Apr. 1, 2007, http://www.efunds.com/web/industry-solutions/financial-services/frm-debit-report/htm in 1 page.
Equifax; “White Paper: Driving Safe Growth in a Fluid Economy”, http://www.equifax.com/assets/USCIS/efx_safeGrowth_wp.pdf, Oct. 2012 in 14 pages.
“Experian Helps Verify the Identity of Patients and Provide Secure Enrollment to Healthcare Portals by Integrating with Major Electronic Medical Records Platform,” http://press.experian.com/United-States/Press-Release/experian-helps-verify-the-identity-of-patients-and-provide-secure-enrollment-to-healthcare.aspx?&p=1, Dec. 19, 2013, pp. 2.
Experian; “Case study: SC Telco Federal Credit Union”, http://annualcreditreport.experian.com/assets/consumer-information/case-studies/sc-telco-case-study.pdf, Jun. 2011 in 2 pages.
“Fair Isaac Introduces Falcon One System to Combat Fraud at Every Customer Interaction”, Business Wire, May 5, 2005, pp. 3.
“FTC Testifies: Identity Theft on the Rise”, FTC News Release, Mar. 7, 2000, pp. 3.
GAO-03-661, Best Practices: Improved Knowledge of DOD Service Contracts Could Reveal Significant Savings, GAO, Jun. 2003.
Glenn, Brandon, “Multi-provider patient portals get big boost with ONC ruling”, Feb. 25, 2013, http://medicaleconomics.modernmedicine.com/medical-economics/news/user-defined-tags/meaningful-use/multi-provider-patient-portals-get-big-boost in 2 pages.
Healow.com, Various screenshots from page titled “Health and Online Wellness,” https://healow.com/apps/jsp/webview/index.jsp printed Aug. 19, 2013 in 4 pages.
Healthspek.com, “How Good are We?” http://healthspek.com/how-good-are-we/ printed Jan. 21, 2014 in 2 pages.
“Healthspek Users Can Now Import Their Doctors' Records into Their Personal Health Record,” PRWeb, Nashville, TN, Jan. 14, 2014, pp. 1 http://www.prweb.com/releases/2014/01/prweb11485346.htm.
HealthVault, “Share Health Information,” https://account.healthvault.com/sharerecord.aspx, printed Feb. 20, 2013 in 2 pages.
HealthVault, “What Can you do with HealthVault?” https://www.healthvault.com/us/en/overview,http://www.eweek.com/mobile/diversinet-launches-mobihealth-wallet-for-patient-data-sharing/, printed Feb. 20, 2013 in 2 pages.
Hill, Kerry, “Identity Theft Your Social Security Number Provides Avenue for Thieves”, NewsRoom, Wisconsin State Journal, Sep. 13, 1998, pp. 4.
Horowitz, Brian T., “Diversinet Launches MobiHealth Wallet for Patient Data Sharing,” eWeek, Dec. 4, 2012, http://www.eweek.com/mobile/diversinet-launches-mobihealth-wallet-for-patient-data-sharing/.
“ID Thieves These Days Want Your Number, Not Your Name”, The Columbus Dispatch, Columbus, Ohio, http://www.dispatch.com/content/stories/business/2014/08/03/id-thieves-these-days-want-your-number-not-your-name.html, Aug. 3, 2014 in 2 pages.
igiHealth.com, “Orbit® PHR: Personal Health Record (PHR),” http://www.igihealth.com/consumers/orbit_phr.html, printed Jan. 21, 2014 in 2 pages.
“Industry News, New Technology Identifies Mortgage Fraud: Basepoint Analytics Launches FraudMark”, Inman News, American Land Title Association, Oct. 5, 2005, pp. 1.
InsightsOne.com, “Healthcare,” http://insightsone.com/healthcare-predictive-analytics/ printed Mar. 6, 2014 in 5 pages.
Internal Revenue Service Data Book 2000, Issued Aug. 2001, Revised May 2003.
Jacob et al., A Case Study of Checking Account Inquiries and Closures in Chicago, The Center for Financial Services Innovation, Nov. 2006.
Jost, Allen; Neural Networks, Credit World, Mar./Apr. 1993, vol. 81, No. 4, pp. 26-33.
Lamons, Bob, “Be Smart: Offer Inquiry Qualification Services,” Marketing News, ABI/Inform Global, Nov. 6, 1995, vol. 29, No. 23, pp. 13.
Lee, W.A.; “Experian, on Deal Hunt, Nets Identity Theft Insurer”, American Banker: The Financial Services Daily, Jun. 4, 2003, New York, NY, 1 page.
LifeLock, http://web.archive.org/web/20110724011010/http://www.lifelock.com/? as archived Jul. 24, 2011 in 1 page.
LifeLock, “How LifeLock Works,” http://www.lifelock.com/lifelock-for-people printed Mar. 14, 2008 in 1 page.
LifeLock, “LifeLock Launches First ID Theft Prevention Program for the Protection of Children,” Press Release, Oct. 14, 2005, http://www.lifelock.com/about-us/press-room/2005-press-releases/lifelock-protection-for-children.
LifeLock, Various Pages, www.lifelock.com/, 2007.
Longo, Tracey, “Managing Money: Your Family Finances”, Kiplinger's Personal Finance Magazine, Jun. 1, 1995, vol. 49, No. 6, pp. 4.
McManus et al.; “Street Wiser,” American Demographics; ABI/Inform Global; Jul./Aug. 2003; 25, 6; pp. 32-35.
McNamara, Paul, “Start-up's pitch: The Envelope, please,” Network World, Apr. 28, 1997, vol. 14, No. 17, p. 33.
Merugu, et al.; “A New Multi-View Regression Method with an Application to Customer Wallet Estimation,” The 12th International Conference on Knowledge Discovery and Data Mining, Aug. 20-23, 2006, Philadelphia, PA.
Muus, et al., “A Decision Theoretic Framework for Profit Maximization in Direct Marketing”, Sep. 1996, pp. 20.
“New Privista Product Provides Early Warning System to Combat Identity Theft”, PR Newswire, Oct. 24, 2000, PR Newswire Association, Inc., New York.
Occasional CF Newsletter; http://www.halhelms.com/index.cfm?fuseaction=newsletters.oct1999; Oct. 1999.
Office of Integrated Analysis and Forecasting, DOE/EIA-M065(2004), Model Documentation Report: Macroeconomic Activity Module (MAM) of the National Energy Modeling System, EIA, Washington DC, Feb. 2004.
Partnoy, Frank, Rethinking Regulation of Credit Rating Agencies: An Institutional Investor Perspective, Council of Institutional Investors, Apr. 2009, pp. 21.
Perlich et al., “High Quantile Modeling for Customer Wallet Estimation with Other Applications,” The 13th International Conference on Knowledge Discovery and Data Mining, Aug. 12-15, 2007, San Jose, CA.
Polatoglu et al., “Theory and Methodology, Probability Distributions of Cost, Revenue and Profit over a Warranty Cycle”, European Journal of Operational Research, Jul. 1998, vol. 108, Issue 1, pp. 170-183.
PrivacyGuard, http://web.archive.org/web/20110728114049/http://www.privacyguard.com/ as archived Jul. 28, 2011 in 1 page.
Rosset et al., “Wallet Estimation Models”, IBM TJ Watson Research Center, 2005, Yorktown Heights, NY, pp. 12.
Schmittlein et al., “Customer Base Analysis: An Industrial Purchase Process Application”, Marketing Science, vol. 13, No. 1, Winter 1994, pp. 41-67.
Singletary, Michelle, “Score One for Open Credit Ratings”, The Washington Post, Washington DC, Jun. 18, 2000, 3 pages.
Smith, Richard M., “The Web Bug FAQ”, Nov. 11, 1999, Version 1.0, pp. 4.
Stein, Benchmarking Default Prediction Models: Pitfalls and Remedies in Model Validation, Moody's KMV, Revised Jun. 13, 2002, Technical Report #020305; New York.
Sumner, Anthony, “Tackling the Issue of Bust-Out Fraud”, Retail Banker International, Jul. 24, 2007, pp. 4.
Truston, “Checking if your Child is an ID Theft Victim can be Stressful,” as posted by Michelle Pastor on Jan. 22, 2007 at http://www.mytruston.com/blog/credit/checking_if_your_child_is_an_id_theft_vi.html.
Watts, Craig, “Consumers Now Can Know What Loan Rate Offers to Expect Based on Their FICO Credit Score at MyFICO.com,” Mar. 6, 2002, pp. 2, http://www.myfico.com/PressRoom/PressReleases/2002_03_06.aspx.
Webber, Richard, “The Relative Power of Geodemographics vis a vis Person and Household Level Demographic Variables as Discriminators of Consumer Behavior,” CASA:Working Paper Series, http://www.casa.ucl.ac.uk/working_papers/paper84.pdf, Oct. 2004, pp. 17.
Declaration of Paul Clark, DSc. for Inter Partes Review of U.S. Pat. No. 8,504,628 (Symantec Corporation, Petitioner), dated Jan. 15, 2014 in 76 pages.
Exhibit D to Joint Claim Construction Statement, filed in Epsilon Data Management, LLC, No. 2:12-cv-00511-JRG (E.D. Tex.) (combined for pretrial purposes with RPost Holdings. Inc., et al. v. Experian Marketing Solutions. Inc., No. 2:12-cv-00513-JRG (E.D. Tex.)) Filed Jan. 14, 2014 in 9 pages.
First Amended Complaint in Civil Action No. 2:12-cv-511-JRG (Rpost Holdings, Inc. and Rpost Communications Limited V. Constant Contact, Inc.; et al.) filed Feb. 11, 2013 in 14 pages.
First Amended Complaint in Civil Action No. 2:12-cv-511-JRG (Rpost Holdings, Inc. and Rpost Communications Limited V. Epsilon Data Management, LLC.) filed Sep. 13, 2013 in 9 pages.
First Amended Complaint in Civil Action No. 2:12-cv-513-JRG (Rpost Holdings, Inc. and Rpost Communications Limited V. Experian Marketing Solutions, Inc.) filed Aug. 30, 2013 in 9 ages.
Petition for Covered Business Method Patent Review in U.S. Pat. No. 8,161,104 (Experian Marketing Solutions, Inc., Epsilon Data Management, LLC, and Constant Contact, Inc., v. Rpost Communications Limited) dated Jan. 29, 2014 in 90 pages.
Source Code Appendix attached to U.S. Appl. No. 08/845,722 by Venkatraman et al., Exhibit A, Part 1 & 2, pp. 32.
Provisional Applications (1)
Number Date Country
60887523 Jan 2007 US
Continuations (2)
Number Date Country
Parent 14091174 Nov 2013 US
Child 15464089 US
Parent 12022954 Jan 2008 US
Child 14091174 US