Method and system for vendor management

Abstract
A method and system for managing business transactions, such as mortgages or other financial transactions. A business transaction between an end user and a financial institution includes sub-transactions between the end user and a vendor. A software system performs functions to complete the business transaction. Automated ordering allows an end user to quickly and easily order a sub-transaction without input from the financial institution or the vendor, and also automatically orders sub-transactions upon satisfaction of a trigger event. Vendor management functionality allows a financial institution to manage the transactions of a vendor. Qualitative performance analysis functionality allows an end user to monitor and evaluate a vendor's price, turn-around time, quality score, and overall score. Vendor distribution functionality distributes sub-transactions among vendors. Vendor management company functionality allows a vendor management company—a vendor that outsources some or all of its sub-transactions to independent service providers—to effectively use the system.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


The present invention relates to a method and system for managing business transactions that require goods or services from multiple vendors, and in particular to a method and system for providing a banking transaction to an individual while managing sub-transactions with one or more vendors.


2. Background of the Technology


There exist in the art paper-based methods and systems for completing financial transactions, such as providing mortgages, but these systems are typically slow and costly. Computer-implemented systems to manage financial transactions are also known, but these systems typically do not contain functionality to manage each step in the lifespan of a financial transaction. In particular, they do not provide functionality to initiate or track sub-transactions that are necessary for the completion of a financial transaction.


There is an unmet need in the art for methods and systems for the management of financial transactions, that include functionality to manage sub-transactions. A sub-transaction, also interchangeably referred to herein as an order or a product, relates to goods or services being provided during the life of the transaction, and sub-transactions help to define parameters of the transaction or otherwise bring the transaction to completion. For example, a financial institution or other company (also interchangeably referred to herein as a customer), such as a mortgage company, wishes to make a transaction with an end user. For example, the transaction may be providing a mortgage, and the end user may be an individual or business. The transaction may require the completion of one or more sub-transactions. One example of such a sub-transaction is a home inspection. Sub-transactions include transactions between the end user and a vendor, such as an inspection company, which has a service agreement with the financial institution. Sub-transactions also include, for example, transactions between the end user and the financial institution, between the financial institution and a vendor, or between a vendor and another party, such as an independent service provider.


There is an unmet need in the art for automated vendor distribution functionality that enables a financial institution or another requesting party to automate the distribution of sub-transactions to select vendors. There is a further need to provide order tracking and order management functionality. There is also a need to create a system that is tailored to the needs of a vendor management company. A vendor management company, also interchangeably referred to herein as a network vendor, is a vendor which itself outsources some or all sub-transactions to local independent contractors or service providers.


SUMMARY OF THE INVENTION

The present invention provides a structure and platform that embodies an effective method and system for managing business transactions between an end user and a financial institution, where the business transactions include one or more sub-transactions between a vendor and the end user or financial institution. For example, when an end user obtains a loan from a financial institution or enters into another financial transaction, goods and services are ordered in conjunction with the loan or other financial transaction. These goods and services, or sub-transactions, include, for example, a flood order, an inspection, a business process outsourcing (BPO), an appraisal, an automated valuation model (AVM), a mortgage insurance (MI) policy, or other sub-transactions associated with the loan or other financial transaction. In one embodiment, the present invention includes systems and methods for ordering these sub-transactions from vendors. The sub-transactions may be ordered by the end user, by the financial institution, by a member of an outsourced labor force, by a real estate agent or other agent for the end user, or by another party. In one embodiment, the present invention includes systems and methods for selecting a vendor for a sub-transaction.


In addition, in one embodiment, the present invention is branded and customized to a particular financial institution or other company. Furthermore, the present invention allows outsourcing of non-automated transaction management operations, such that, for example, the human labor force required for transaction management is outsourced to a third party or other entity that is, for example, unrelated to the financial institution.


The present invention streamlines business processes, such as providing mortgages or performing other financial transactions, by, among other things, automating many traditionally manual steps. This eliminates manual errors and reduces cost, and also does not require a company to hire additional employees. The present invention is capable of being integrated into existing business infrastructure, and is capable of interfacing with other software applications.


The present invention enables mortgage lenders and others to reengineer their mortgage origination and servicing processes. This reduces operating costs and allows for a process that is fully electronic.


One embodiment of the present invention provides automated ordering functionality. In one embodiment, automated ordering apprises an end user that a particular sub-transaction is required or optional, and allows an end user to quickly and easily order a sub-transaction, without input from the financial institution or the vendor. In one embodiment, automated ordering functionality also automatically orders sub-transactions upon the ordering of a transaction or is otherwise automatically triggered. Automated ordering may thereby reduce cost and may reduce erroneous ordering.


One embodiment of the invention includes vendor management processing and set-up functionality. This functionality allows a financial institution to manage the transactions of a vendor, including real-time calculation of vendor capacity, threshold, and late-order ratios.


One embodiment of the invention includes qualitative performance analysis functionality. This functionality allows an end user or other requesting party to monitor and evaluate a vendor's price for a given sub-transaction, as specified in the service contract between the vendor and the financial institution. This functionality also allows an end user or other requesting party to monitor and evaluate such measures as a vendor's turn-around time and quality score. The qualitative performance analysis functionality further calculates an overall score for the vendor, such as by combining and weighting the turn-around and quality scores and providing a score via a scoring mechanism for evaluating a vendor's turn-around time performance.


One embodiment of the invention includes vendor distribution functionality. This functionality distributes sub-transactions among vendors, taking into account criteria such as a vendor's price, turn-around time, quality score, capacity, threshold, late order ratios, outstanding late order volume, outstanding new order volume, and the like. Vendor distribution functionality also includes functionality to withhold order distribution to a specified vendor for a specified period of time.


One embodiment of the invention includes vendor management company functionality. This functionality allows a vendor management company—e.g., a vendor that outsources some or all of its sub-transactions to independent service providers or the like—to effectively use the system. This functionality provides a vendor management company with many of the same tools available to the financial institution, such as automated distribution of orders to independent service providers and qualitative analysis of the independent service providers.


One embodiment of the invention provides a customizable system that can be tailored for a particular financial institution or other company. Customizing the system includes branding the system, or altering the look, feel, and user interaction with the system. Customizing the system further includes tailoring the capabilities of the system in accordance with vendor rules and policies concerning the requirements for transactions and sub-transactions. In one embodiment, customizing the system also includes adding automated support for the day-to-day operations of a particular financial institution or other company.


One embodiment of the invention provides a method and system that allow outsourcing of the human labor force that performs non-automated transaction management tasks. Outsourcing allows the system to be implemented in such a way that the financial institution or the vendors have little or no interaction with the system.


In one implementation, each type of transaction has a unique profile. The profile specifies, for example, the relationship between an end user and the financial institution. For example, the profile may specify the terms of a home loan. To select a transaction for a particular end user, in one embodiment, parameters matching the end user's requirements are input, and a transaction with a profile matching the input parameters is selected. Furthermore, the profile for a given transaction specifies, for example, which sub-transactions are required or are optional for the transaction. This assists in triggering automatic ordering of sub-transactions.


Additional advantages and novel features of the invention will be set forth in part in the description that follows, and in part will become more apparent to those skilled in the art upon examination of the following or upon learning by practice of the invention.




BRIEF DESCRIPTION OF THE FIGURES

In the drawings:



FIG. 1 shows various features of an example computer system for use in conjunction with an embodiment of the present invention;



FIG. 2 presents an example flow diagram of functions performed in accordance with an embodiment of the present invention;



FIG. 3 presents an exemplary system diagram of various hardware components and other features, in accordance with an embodiment of the present invention;



FIG. 4 is a block diagram of various system components, in accordance with an embodiment of the present invention;



FIG. 5 presents an example flow diagram of functions performed in accordance with an embodiment of the present invention;



FIG. 6 presents an example flow diagram of functions performed in accordance with an embodiment of the present invention;



FIGS. 7-57 show sample Graphical User Interface (GUI) screens presented to a user in conjunction with an embodiment of the present invention;



FIG. 58 is a block diagram illustrating a sample corporate hierarchy in conjunction with an embodiment of the present invention;



FIG. 59 is a block diagram illustrating various functionalities of a system in conjunction with an embodiment of the present invention; and



FIGS. 60-61 illustrate a branded customer portal in conjunction with an embodiment of the present invention.




DETAILED DESCRIPTION

Among other advantages, the present invention maximizes process efficiencies and reduces customer costs by automating additional processes in the transaction management lifecycle. For example, when an end user obtains a loan from a financial institution or enters into another financial transaction, goods and services are ordered in conjunction with the loan or other financial transaction. These goods and services, or sub-transactions, include, for example, a flood order, an inspection, a business process outsourcing (BPO), an appraisal, an automated valuation model (AVM), a mortgage insurance (MI) policy, or other sub-transactions associated with the loan or other financial transaction. In one embodiment, the present invention includes systems and methods for ordering these sub-transactions from vendors. The sub-transactions may be ordered by the end user, by the financial institution, by a member of an outsourced labor force, by a real estate agent or other agent for the end user, or by another party. In one embodiment, the present invention includes systems and methods for selecting a vendor for a sub-transaction.


Advantages of the present invention include the following: 1) providing customers with superior vendor management tools to automate the vendor management process; 2) creating a competitive advantage in the vendor management and transaction management market space; and 3) providing sufficient tools and features to eliminate the need to maintain another order tracking system.


The present invention works in conjunction with features designed to provide foundational vendor management functionality, as well as automated vendor distribution tools. Automated vendor distribution functionality provides requesting parties with the ability to automate the distribution of orders to select service providers based upon various loan file criteria, as well as such factors as geographic location, vendor capacity, and threshold limits. The present invention provides additional vendor management functionality to a suite of management tools.


The present invention also provides features to satisfy the order tracking and management needs of the system manager. These additional features reduce operational costs as well as expand the functionality to encompass the needs of the vendor management company, also herein interchangeably referred to as a Network Service Provider (service provider who outsources a majority of the products and services to local independent service providers).


The present invention contains features that address the following areas, among others: 1) automated ordering; 2) vendor management processing/set-up; 3) enhanced qualitative analysis; 4) vendor distribution enhancements; 5) vendor management company accommodations; and 6) financial institution operational needs.


Automated Ordering


The Automated Ordering functionality offers full end-to-end order placement automation, optionally without the need for user intervention. This feature reduces customer costs due to the reduction in manual processes, and also reduces erroneous product ordering (e.g., ordering the wrong set of products for a specified loan).


The Automated Ordering feature allows users to utilize File and Order data to determine which products to order and when to order them. For example, a customer is able to automatically order a BPO for loans with a loan type of “refinance,” and to order a full appraisal for loans with a loan type of “purchase.” The functionality is designed to also combine comparison logic to automate the order placement process. For instance, a customer may want loans with a loan-to-value ratio (LTV) greater than 95%, and with a loan product of “home equity line of credit” (HELOC), handled differently than loans with a loan-to-value ratio (LTV) less than 95% and loan product of “conforming.” Essentially, the Automated Ordering features handle the typical decision making scenarios that customers face on a daily basis.


To maximize the effectiveness of Automated Ordering functionality, one embodiment of the present invention offers automated product selection and order placement capabilities for various scenarios, such as file creation and order fulfillment.


The file creation scenario enables customers to trigger the automated product selection and order placement at the time a file is created. Under this scenario, file level data is utilized to determine the appropriate products to order for the specified file. The file level data includes typical order placement data, such as Premium Type, Rate Type and Renewal Type for the Mortgage Insurance product.


The order fulfillment scenario enables automatic product selection and order placement based upon order fulfillment data. Under this scenario, order fulfillment data is utilized to determine the appropriate products to order for the specified file. An example would be when a customer orders an AVM product and would like a BPO ordered if the AVM fulfillment Property Value is 10% less or greater than the Estimated Property Value.


In one embodiment, automated product selection enables requesters to create custom decision rules to automatically place orders for required products. The decision rules are based, for example, on “If, Then” logic and can include any data element from the following: loan data (pre-fulfillment data), indicating the type of loan or other transaction; fulfillment data, indicating which orders have been completed; and file/order status data, indicating the status of outstanding orders.


Loan data (pre-fulfillment data) indicates the type of loan or other transaction. In one embodiment, loan data also includes data indicating which products to order for the transaction. Loan data triggers, for example, the automatic ordering of necessary products based on file data or other transaction data. Automated ordering based on loan data eliminates the product ordering decision process and provides tool to ensure that Vendor Order Allocation requirements are satisfied.


Fulfillment data indicates which orders have been completed. Fulfillment data triggers, for example, the ordering of subsequent products based on the result of fulfillment data. For example, when an AVM value is delivered and it is greater than 20% of the original appraised value, a BPO is automatically ordered. Automated ordering based on fulfillment data eliminates the manual processing that occurs when products are fulfilled. For example, if the product is rejected, the order is automatically placed with a different vendor. As another example, if the fulfillment data does not meet the acceptance rules, an alternative product is automatically ordered.


File/order status data indicates the status of outstanding orders. File/order status data triggers, for example, automatic ordering of alternative or supplemental products based on the result of specified status changes. For example, when a mortgage loan is funded, an MI policy can automatically be activated and a flood zone determination can be automatically upgraded from a one-time to a life-of-loan. Automated ordering based on file/order status data eliminates the manual processing that occurs when the status of a file or order changes.


Vendor Management Processing


The Vendor Management Processing features enable real-time calculation of vendor capacity, threshold and late order ratios; enhanced acknowledgement file capabilities; and enhancements to vendor management distribution processing trigger, including pre-order placement.


The present invention also provides functionality to aid vendors and Vendor Management Companies (VMCs). One embodiment of the present invention includes functionality to automate the selection of an independent service provider for an order. Vendor Management Processing features also provide functionality to score independent service providers.


One embodiment of the present invention uses a parent-child infrastructure to describe corporations, such as vendors. Thus, a corporation may be described a hierarchy. For example, a corporation is described as a parent, subsidiaries are described as children of the corporation, and offices are described as children of subsidiaries. Users are described as children of offices. The present invention may include additional parent-child infrastructure describing some users as children of others. Additionally, work groups may be defined, which include users from one or more offices. This is simply one example of a parent-child hierarchy for a corporation. Many others are possible.


The parent-child infrastructure (PCI) enables support of companies with multiple levels in their corporate hierarchy. PCI provides the ability to track orders and generate reports at any level in the hierarchy.


PCI features enable vendors or others to: customize corporate level labels, add offices at each level, add users to each office, view the corporate hierarchy, add users to multiple workgroups, assign orders to workgroups, search files by corporate level and office, generate reports by corporate level and office, view the administrative history log, provide certain privileges (e.g., menu options, products to order, order assignment) for normal users, access enhanced setup for products to order, bulk assign orders to workgroups, assign files to users or workgroups, bulk assign files to a project, or display file assignment in the order manager.


Qualitative Analysis


The Qualitative Analysis segment provides qualitative performance analysis tools for customers. Features enable the requesting party to monitor and evaluate a service provider's Service Level Agreement price, turn-around time, and quality score. Qualitative analysis functionality also generates a unique score for each customer's service provider by supporting the ability to combine and weight the qualitative and timeline performance scores. Embodiments of the invention also include a scoring mechanism for evaluating a service provider's turn-around-time performance. These Qualitative Analysis functionalities allow for greater support of multiple vendor selection methodologies.


In one embodiment, a cumulative vendor score is based on a customized ratio. The cumulative vendor score is calculated, for example, by summing a weighted vendor quality score and a weighted vendor service score. The vendor quality score may incorporate factors such as customer satisfaction and price, and the vendor service score may take into account such factors as late orders and turnaround time.


Vendor Distribution


The present invention provides functionality to automatically distribute work to vendors based on a set of criteria. These criteria include the features of the Qualitative Analysis segment, as well as additional distribution criteria and logic. The present invention provides the ability to manage the distribution levels based upon a service provider's outstanding late order volume and new order volume, as well as withholding order distribution to a specified vendor for a specified period of time.


Vendor Management Company Accommodations


The present invention provides additional functionality for Vendor Management Companies (VMCs). VMCs maintain and manage large groups of independent service providers. An example would be a company that receives nationwide orders for appraisal services and in turn distributes those orders to smaller independent service providers across the nation. The independent service provider then submits the product fulfillments back to the VMC. The VMC then reviews the work product for quality and transfers the fulfillment to the original ordering party. The present invention provides the VMC with the same vendor management tools available to the Requestor. The present invention allows a VMC to automate the distribution of orders to their down-line service providers, or perform qualitative analysis of the down-line service provider's performance.


Financial Institution Operational Needs


The present invention provides a set of operational tools to support the day-to-day operational and management needs of the financial institution. The tools are fully integrated with applications and may even reside with the present invention. By providing operational tools for the customer, the customer can eliminate the need to maintain and manage a separate order tracking system.


In one embodiment of the present invention, an outsourced labor force assists in non-automated transaction management operations. In one embodiment, the labor force-assisted operations include, for example: mortgage origination transactions, such as processing, decisioning, and closing; accounting services, such as cashiering, accounts payable, corporate accounting functions, and investor reporting; call center services, such as early stage collection, inbound customer service calls, skip tracing, and late stage unsecured collections; title insurance services, such as assignments and lien releases; mortage servicing, such as customer research/services, escrow, payoffs and loan satisfactions, and loan setup/imaging; default services, such as loan resolution/bankruptcy and foreclosure/REO/claims; real estate analytics, such as reality advisors, commercial servicing, and mortgage analytics/capital markets; and data entry services.


Example embodiments will now be described in conjunction with the following figures.



FIG. 1 shows various features of an example computer system 600 for use in conjunction with an embodiment of the present invention. As shown in FIG. 1, the computer system is used by a requestor 602 or a representative of the requestor 602 to order goods or services from a vendor 604. The system includes a REALPayments and Softrax module 606 that includes functionality for billing, billing presentment, charges, pricing, and vendor setup. The system also includes a REALPayments module 608 that includes functionality for approval, dispute resolution, invoice, payments, and constructive receipts. The system 600 also includes functionality for invoice creation. The system 600 also includes or otherwise has access to one or more databases, such as, for example, a REALServicing database 610, a REALTrans database 612, an accounts receivable (AR) database 614, an accounts payable (AP) database 616, and a general ledger (GL) database 618. Features of the REALPayments and Softrax module 606, the REALPayments module 608, and the REALServicing, REALTrans, AR, AP, and GL databases 610, 612, 614, 616, and 618 are described in copending U.S. patent application Ser. No. 09/512,845 titled “Method for Workflow Processing Through Computer Network,” filed Feb. 25, 2000; copending U.S. patent application Ser. No. ______ titled “Management and Reporting System and Process for Use with Multiple Disparate Data Base,” filed Mar. 19, 2002; copending U.S. patent application Ser. No. ______ titled “Method and Apparatus for Providing Selective Access to Information,” filed Apr. 4, 2003; copending U.S. Provisional Application Ser. No. 60/495,103 titled “Electronic Ordering, Invoice Presentment, and Payment System and Method,” filed Aug. 15, 2003; copending U.S. patent application Ser. No. 10/729,019 titled “Expense Tracking, Electronic Ordering, Invoice Presentment, and Payment System and Method,” filed Dec. 8, 2003. The entirety of each of those patent applications is incorporated herein by reference.



FIG. 2 presents an example flow diagram showing the pages a user might encounter, in accordance with an embodiment of the present invention. A user first places an order 500. If Vendor Management (VM) is not enabled, an Xpress ordering Graphical User Interface (GUI) screen is displayed 502. The user then, for example, selects one or more sub-transactions (also referred to as orders or products) 504, and submits the order 506.


If VM is enabled, a VM Xpress ordering GUI page is displayed 508. If Automated Product Selection (APS) is used, the APS profile is processed 510 and the sub-transaction or product(s) is selected 512. If APS is not used, the user then selects products 504. The order is then submitted 506.


If AVS is used, the AVS engine processes order and vendor parameters 514 and selects a vendor(s) 516.


If only one sub-transaction, product, or order has been triggered, a vendor criteria GUI screen is displayed 518 and vendor criteria are selected. The vendor criteria are then submitted 520. The file data for the transaction are retrieved 522. Some fields in the order or sub-transaction are populated with data from the transaction 524, and a product order form GUI screen is displayed. A user edits the product order form, and the order form is then submitted 526. Information about the order or sub-transaction is displayed 528, for example, automatically or at a request from a user.


If more than one product, order, or sub-transaction have been triggered, a vendor selection GUI screen is displayed 530, and the user edits a pre-selected vendor list. The edited vendor list is then submitted 532. The file data for the transaction are retrieved 534 and fields in the sub-transactions are populated with data from the transaction. A consolidated order form GUI screen is displayed 536. The order form is submitted 538 and the information about the orders or sub-transactions is displayed 540.


In one embodiment, the invention includes machine-executable instructions stored in a computer-readable medium. These machine-executable instructions include software functions that perform specific actions. A list of the software functions of this embodiment is shown in Table 1.


The present invention may be implemented using hardware, software or a combination thereof and may be implemented in one or more computer systems or other processing systems. In one embodiment, the invention is directed toward one or more computer systems capable of carrying out the functionality described herein. An example of such a computer system 200 is shown in FIG. 3.


Computer system 200 includes one or more processors, such as processor 204. The processor 204 is connected to a communication infrastructure 206 (e.g., a communications bus, cross-over bar, or network). Various software embodiments are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the relevant art(s) how to implement the invention using other computer systems and/or architectures.


Computer system 200 can include a display interface 202 that forwards graphics, text, and other data from the communication infrastructure 206 (or from a frame buffer not shown) for display on the display unit 230. Computer system 200 also includes a main memory 208, preferably random access memory (RAM), and may also include a secondary memory 210. The secondary memory 210 may include, for example, a hard disk drive 212 and/or a removable storage drive 214, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive 214 reads from and/or writes to a removable storage unit 218 in a well-known manner. Removable storage unit 218, represents a floppy disk, magnetic tape, optical disk, etc., which is read by and written to removable storage drive 214. As will be appreciated, the removable storage unit 218 includes a computer usable storage medium having stored therein computer software and/or data.


In alternative embodiments, secondary memory 210 may include other similar devices for allowing computer programs or other instructions to be loaded into computer system 200. Such devices may include, for example, a removable storage unit 222 and an interface 220. Examples of such may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an erasable programmable read only memory (EPROM), or programmable read only memory (PROM)) and associated socket, and other removable storage units 222 and interfaces 220, which allow software and data to be transferred from the removable storage unit 222 to computer system 200.


Computer system 200 may also include a communications interface 224. Communications interface 224 allows software and data to be transferred between computer system 200 and external devices. Examples of communications interface 224 may include a modem, a network interface (such as an Ethernet card), a communications port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, etc. Software and data transferred via communications interface 224 are in the form of signals 228, which may be electronic, electromagnetic, optical or other signals capable of being received by communications interface 224. These signals 228 are provided to communications interface 224 via a communications path (e.g., channel) 226. This path 226 carries signals 228 and may be implemented using wire or cable, fiber optics, a telephone line, a cellular link, a radio frequency (RF) link and/or other communications channels. In this document, the terms “computer program medium” and “computer usable medium” are used to refer generally to media such as a removable storage drive 214, a hard disk installed in hard disk drive 212, and signals 228. These computer program products provide software to the computer system 200. The invention is directed to such computer program products.


Computer programs (also referred to as computer control logic) are stored in main memory 208 and/or secondary memory 210. Computer programs may also be received via communications interface 224. Such computer programs, when executed, enable the computer system 200 to perform the features of the present invention, as discussed herein. In particular, the computer programs, when executed, enable the processor 204 to perform the features of the present invention. Accordingly, such computer programs represent controllers of the computer system 200.


In an embodiment where the invention is implemented using software, the software may be stored in a computer program product and loaded into computer system 200 using removable storage drive 214, hard drive 212, or communications interface 224. The control logic (software), when executed by the processor 204, causes the processor 204 to perform the functions of the invention as described herein. In another embodiment, the invention is implemented primarily in hardware using, for example, hardware components, such as application specific integrated circuits (ASICs). Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s).


In yet another embodiment, the invention is implemented using a combination of both hardware and software.



FIG. 4 presents an exemplary system diagram of various hardware components and other features in accordance with an embodiment of the present invention. As shown in FIG. 4, in an embodiment of the present invention, data and other information and services for use in the system is, for example, input by an end user 30 via a terminal 31. The terminal 31 is coupled to a server 33 via a network 34, such as the Internet, via couplings 35, 36. In one embodiment, a vendor 39 also inputs information/data via a terminal 37 coupled 38 to the network 34. Furthermore in one embodiment, a member of an outsourced workforce 40 inputs information/data via a terminal 41 coupled 42 to the network 34, and in another embodiment, a member of a financial institution workforce 43 inputs information/data via a terminal 44 coupled 45 to the network 34.


Each of the terminals 31, 37, 41, 44 is, for example, a personal computer (PC), minicomputer, mainframe computer, microcomputer, telephone device, personal digital assistant (PDA), or other device having a processor and input capability. The terminal 31 is coupled to a server 33, such as a PC, minicomputer, mainframe computer, microcomputer, or other device having a processor and a repository for data or connection to a repository for maintained data,


In operation, in an embodiment of the present invention, via the network 34, vendor data, transactional data, sub-transactional data, order data and/or other information is communicated with the server 33. The server 33 receives and resolves the transaction including triggering and resolving sub-transactions, stores data regarding the transaction, vendor, and sub-transaction, and documents the transaction (e.g., electronically).


In one embodiment, the present invention uses active server page (ASP) technology to deliver information and services to a user. This may include one or more ASPs stored on the server 33. This reduces the maintenance expense and hardware expense, results in limited implementation/integration costs, limited support expense, and low total cost of ownership.


In one embodiment of the present invention, information relating to a transaction, such as a loan, is stored electronically. This information is referred to interchangeably as a virtual loan file. Among other things, the virtual loan file enables data mining, reduces post closing quality reviews, facilitates secondary market due diligence, streamlines loan servicing functions, reduces data archive costs, reduces processing costs, automates routine and decision based processes, and reduces data entry errors.


In one embodiment, the present invention includes a branded customer portal, which enables a customer, such as a mortgage company, to tailor the look and feel of a software system, as well as the information and services provided by the software system, to the company's particular needs.



FIG. 5 shows an example flow diagram of a process for providing automatic ordering for a sub-transaction associated with a particular transaction, in accordance with an embodiment of the present invention. This flow diagram demonstrates automatic ordering of a sub-transaction, triggered by the input of a transaction. As shown in FIG. 5, specific parameters for a particular transaction, such as a loan, are input into the system 300. In one implementation, this action is performed, for example, by a member of an outsourced labor force. Alternatively, the parameters are input by an end user, such as an individual wishing to obtain a mortgage. The parameters input into the system are then processed 302. A transaction matching the input parameters is then selected 304. For example, a particular type of home loan may be selected that matches the parameters. If there is no transaction with a profile matching the parameters, the file or transaction is moved to an exception bin 306.


In one embodiment, if a transaction matching the input parameters is selected, one or more sub-transactions or orders, such as providing products or services, are automatically selected 308. The sub-transactions automatically selected 308 are, for example, sub-transactions that are required for the selected transaction. If the auto-vendor selection function is not present or is not selected, the sub-transactions, also referred to as orders, move to the vendor selection page 310, and vendor(s) for the sub-transaction(s) are manually selected 311. The vendor(s) are manually selected 311, for example, by an end user, by an employee of the financial institution, or by a member of a third-party outsourced labor force.


If the auto-vendor selection function is present and is enabled, a vendor is automatically selected 312. If no additional information for the sub-transaction or order is required, the order is placed 314. If additional information for the sub-transaction or order is required, an order form corresponding to the order is edited 316, for example, by an end user, by an employee of the financial institution, or by a member of a third-party outsourced labor force. In one embodiment, additional information is input 318, by such users as, for example, the end user, the employee of the financial institution, or the member of a third-party outsourced labor force. The order is then placed 320.



FIG. 6 shows an example flow diagram of a process for providing automatic ordering for a sub-transaction associated with a particular transaction, in accordance with an embodiment of the present invention. This flow diagram demonstrates automatic ordering of a second sub-transaction, triggered by the completion of a first sub-transaction. This type of triggering may be useful, for example, in situations in which two or more sub-transactions must occur in a particular sequence. The sequence of the sub-transactions is be specified, for example, in the profile for a particular transaction.


The automatic ordering process begins, for example, when a vendor sends a product fulfillment indication 400, signifying that the vendor has completed a first sub-transaction. The sub-transaction is associated with a particular instance of a particular transaction, such as a particular type of home loan for a particular end user. The product fulfillment is then received 402. In one embodiment, a particular identification code is examined or processed 404 to identify the instance of the transaction. The parameters of the instance of the transaction are processed or updated 406.


Fulfillment profile selection 408 is then performed. This includes, for example, examining the profile for the transaction to determine if the fulfillment of the first sub-transaction triggers a second sub-transaction. If the profile does not indicate that a second sub-transaction should be triggered, no action is taken 410. If the profile indicates that one or more second sub-transactions should be triggered, the subsequent sub-transaction(s) are selected 412 (e.g., automatically). The following actions are then optionally performed for each of the subsequent sub-transaction(s). Automatic Vendor Selection (AVS) rules are examined and run 414, and an AVS profile is selected 416. If there is a problem with one of the AVS processing functions, the file or loan is moved to an exception bin 418. Otherwise, a vendor is selected 420 (e.g., automatically) for the subsequent sub-transaction and an order is placed 422 for the subsequent sub-transaction.



FIGS. 7-56 illustrate example GUI screens presented to a user ordering goods and services, in accordance with an embodiment of the present invention. After logging in or otherwise entering the system, a user is presented with the GUI screen of FIG. 7. The user selects “Vendor Admin” and is presented with the GUI screen of FIG. 8. The user selects “Score Cards” and is presented with the GUI screen of FIG. 9. The user selects “Cumulative Score” and is presented with the GUI screen of FIG. 10. The GUI screen presents the user with all the cumulative score cards the user has previously created, and presents the user with an option to create a new cumulative score card.


The user selects “Create new score card” and is presented with the GUI screen of FIG. 11. The user enters information pertaining to the items and vendors to be scored in FIGS. 11-12, and selects “Save” to create a new score card.


If the user selects “Service Score” from the GUI screen of FIG. 9, the GUI screen of FIG. 13 is presented. This screen displays all the service score cards, each card including a timeliness score or service score. The user has the option to create a new service score card by entering information into the GUI screens of FIGS. 14-15.


If the user selects “Automated Scoring” from the GUI screen of FIG. 9, the GUI screen of FIG. 16 is presented. This screen displays all the automated score cards. The user has the option to create a new automated score card by entering information into the GUI screens of FIGS. 17-18.


If the user selects “Quality score” from the GUI screen of FIG. 9, the GUI screen of FIG. 19 is presented. This screen displays all the quality score cards, which score the quality of work. The user has the option to create a new quality score card by entering information into the GUI screen of FIG. 20.



FIG. 21 is a GUI screen that allows a user to select a vendor for a particular order and to transmit the order to the vendor. FIGS. 22-23 are GUI screens that allow a user to place a bulk order for an order package consisting of two or more goods or services. Bulk ordering provides, for example, a cost benefit to the user. The user may select a vendor for each product or may enable autoselect, in which case the vendors will be automatically selected.



FIGS. 24-35 are sample GUI screens that may be presented to a user, such as a user wishing to enroll a vendor in a system. FIG. 24 is a GUI screen that allows the user to input general company information for the vendor. FIG. 25 is a GUI screen that is presented to a user enrolling a VMC. This screen allows the user to input criteria related to sub-distribution among independent service providers, such as the available independent service providers, and the criteria to use in distributing work orders among independent service providers. The GUI screen of FIG. 26 allows the user to enter the workload capacity for the vendor.


The GUI screen of FIG. 27 allows the user to view the work queue for the vendor. The GUI screens of FIGS. 28-35 allow the user to add an item to the work queue or change fields of an item in the work queue.


The GUI screen of FIG. 36 allows a user to view information on a property. The GUI screens of FIGS. 37-38 allow the user to add and approve delegates to perform work orders. The GUI screen of FIG. 39 allows a user to view a portfolio, or list of services ordered, for a particular property.


The GUI screen of FIG. 40 displays the options available to a user selecting “Admin” from the menu bar. The GUI screen of FIG. 41 displays the options available to a user selecting “Workstation” from the menu bar. The GUI screen of FIG. 42 displays the viewing options available to a user selecting from a drop-down box. The GUI screen of FIG. 43 displays the options for viewing work queues available to a user selecting from a drop-down box. The GUI screen of FIG. 44 displays work queues to a user.


The GUI screen of FIG. 45 allows a user to enter data for a new work order or product in a workflow. The GUI screen of FIG. 46 allows a user to attach a file to a work order or other communication. The GUI screen of FIG. 47 displays attached files to a recipient of the files. The GUI screens of FIGS. 48-49 allow a user to input information for automatic product selection.


The GUI screen of FIG. 50 allows a user to enter data for process management setup. The GUI screens of FIGS. 51-53 present a user with information regarding an automatic process management setup and allow the user to enter data for automatic process management setup.


The GUI screen of FIG. 54 allows a user to send an email to a recipient. If the email is regarding a particular product or order, the user specifies the product or order by inputting information into the GUI screen of FIG. 55. The user may input information into the GUI screen of FIG. 56 to cancel the product or order.



FIG. 57 is a GUI screen listing properties and information related to each property, such as property data, loan information, and work order information.



FIG. 58 displays a sample corporate hierarchy. The corporate hierarchy exhibits, for example, parent-child infrastructure (PCI) and is displayed as a tree diagram. FIG. 59 is a block diagram illustrating various functionalities of a system in accordance with an embodiment of the present invention. FIGS. 60-61 illustrate a branded customer portal in accordance with an embodiment of the present invention.


Example embodiments of the present invention have now been described in accordance with the above advantages. It will be appreciated that these examples are merely illustrative of the invention. Many variations and modifications will be apparent to those skilled in the art.

TABLE 1UNIQUEREQREQUIREMENTIDFUNCTIONNAMEREQUIREMENT/FUNCTION DESCRIPTIONFigure 2VENDORVENDORMANAGEMENTMANAGEMENTPROCESSING/SETUPPROCESSING/SETUP 2.0AReal-time calculationReal-time updates of vendors' orders.updates: 2.1ACapacityReal-time updates of vendors' open orders. 2.2AThresholdReal-time updates of total number of vendors'orders for a specified time period. 2.3AOutstanding Late OrderReal-time updates of the specified outstandingRatiolate order ratio (ratio of late orders to openorders). 2.0CModification ofWith the addition of Workflow and AVS, theAcknowledgement FileAcknowledgement file would need to be(file-based orders)modified to handle notification of theautomated selection. 2.1CWorkflow SpecificThe Acknowledgement file wouldInformationcontain the following APS Info:Product SelectedWorkflow Name Used 2.2CAVS SpecificThe Acknowledgement file contains theInformationfollowing AVS Info:Vendor SelectedAVS Profile SelectedAVS Distribution Rule SelectedCurrent % of ordersCurrent capacityCurrent thresholdCurrent late order ratio 2.0DAVS Profile ViewerThis will provide a Vendor Manager to viewAppendix AAVS Rulescurrent AVS distribution rules that are inProduction. 2.1DAVS Profile ViewerProvide a section to view the AVS Rules thatAppendix ASectionare currently in Production.(See appendix for layout) 2.2DAVS Profile EffectiveDisplay the date the AVS Rules migrated toAppendix ADateProduction(See appendix for layout) 2.3DAVS Profile ViewerProvide a table that contains all Profiles thatAppendix ATableare currently in Production. 2.4DAVS Profile ViewerThis table layout and functionality willAppendix AActionsduplicate the current Profile table, except theAction column will contain a View link. 2.5DAVS Profile ViewerThe Action link will duplicate the edit link,Appendix AView Profilesexcept it will be view-only. 2.6DAVS Profile ViewerThe AVS Profile Viewer will contain a ViewAppendix AVendor Distribution Listlink on each distribution set to view the vendorlist (This View link will replace the Edit link). 3.1Cumulative Score 3.1.ACreate a Link forCreate a link for Scorecards under ProductsAppendix BScorecard MenuOrdered Menu. Link will go to the Scorecardmenu. 3.1.BCreate ScorecardCreate a Scorecard Menu. This will be set upAppendix CMenuthe same as the Automated Product SelectionMenu. 3.1.B.1Add links to ScorecardAdd links to the Scorecard Menu for QualityAppendix CMenuScore, Service Score, Cumulative Score andAuto Scoring. 3.1.B.2Create a link forCreate a link for Cumulative Score underAppendix CCumulative ScoreScorecard Menu. Link will go to theScreenCumulative Score Screen. 3.1.CCreate CumulativeCreate Cumulative Score Screen to allowAppendix DScore Screenusers to view all saved cumulative scorecards 3.1.C.1Create CumulativeCreate a table to display Scorecard Name,Appendix DScorecard tableDescription of Scorecard, Products, QualityRatio, and Service Ratio. 3.1.C.2Add Edit ButtonsAdd edit buttons to edit any saved scorecard.Appendix DThe edit button will be a link to CumulativeScore Setup Screen #2. 3.1.C.3Add Delete ButtonsAdd Delete buttons to delete any savedAppendix Dscorecards. Display message box “Are yousure you want to delete the saved scorecard”when the Delete button is clicked Removescorecard from table if yes is clicked. RefreshCumulative Score Screen. 3.1.C.4Add Create NewAdd Create New Scorecard Button to createAppendix DScorecard Buttonnew Cumulative Scorecard. Create NewScorecard button will be a link to CumulativeScore Setup Screen #1. 3.1.DCreate CumulativeCreate Cumulative Score Setup Screen toAppendix EScore Setup Screen #1allow users to create a new cumulativescorecard. 3.1.D.1Add Radio ButtonsAdd Radio Buttons to start with an existingAppendix Escorecard. Radio button will default to No. Ifyes button is selected, provide combo box forall saved scorecards. 3.1.D.2Add Scorecard NameAdd Scorecard Name text box. This is aAppendix EText Boxrequired field. Text box should be largeenough to display 30 characters. 3.1.D.3Add ScorecardAdd Scorecard Description text box. This is aAppendix EDescription Text Boxrequired field. Text box should have a scrollbar to allow user to scroll through entiredescription. 3.1.D.4Add Next ButtonAdd Next button to link to Cumulative ScoreAppendix ESetup Screen #2. If No Radio button isselected and Scorecard Name or ScorecardDescription are null, display message“Scorecard Name and Description areRequired”. 3.1.D.5Add Cancel ButtonAdd Cancel Button to link to Cumulative ScoreAppendix EScreen. 3.1.ECreate CumulativeCreate Cumulative Score Setup Screen toAppendix FScore Setup Screen #2allow users to add products and quality andservice ratios for the Cumulative Scorecards. 3.1.E.1Display ScorecardDisplay Scorecard name text box that wasAppendix FNameentered on Cumulative Score Setup Screen#1. 3.1.E.2Display ScorecardDisplay Scorecard Description text box thatAppendix FDescriptionwas entered on Cumulative Score SetupScreen #1. 3.1.E.3Add Product CategoryProvide a combo box for the user to select theAppendix FCombo Boxproduct category that the scorecard will applyto. 3.1.E.4Add Product ComboProvide a combo box for the user to select theAppendix FBoxproduct that the scorecard will apply to. Thelist will only contain products that are in thechosen Product Category. 3.1.E.5Create Product TableCreate table to display products for the currentAppendix Fscorecard. 3.1.E.6Add Product buttonAdd “Add Product” button to allow user to addAppendix Fthe selected product to the current scorecard.When Add Product button is clicked, check tomake sure that product does not exist in anysaved scorecards. If product is not in anysaved scorecards, add product selected to theProduct Table. Refresh screen after button isclicked. 3.1.E.7Add Delete ButtonsAdd Delete buttons to delete any products inAppendix Fthe Product Table. Display message box “Areyou sure you want to delete the product fromthe current scorecard” when the Delete buttonis clicked. Remove product from table if yes isclicked. Refresh screen after button is clicked. 3.1.E.8Add Quality Ratio TextProvide a text box to enter the ratio for theAppendix FBoxQuality Score. Values entered must bebetween 0 and 100. 3.1.E.9Add Service Ratio TextProvide a text box to enter the ratio for theAppendix FBoxService Score. Values entered must bebetween 0 and 100. 3.1.E.10Display CumulativeProvide a field to display the total of theAppendix FRatioQuality and Service ratios. Cumulative Ratiois the sum of the Quality Ratio and ServiceRatio. 3.1.E.11Add Submit ButtonAdd Submit button to save current scorecard.Appendix FCumulative Ratio must be equal to 100.Display message box “Cumulative Ratio mustequal 100% before proceeding” if CumulativeRatio does not equal 100. Message box “Areyou sure you want to save this scorecard”should appear when submit button is clicked,if Cumulative Ratio is equal to 100. If theusers clicks OK, add current scorecard toCumulative Scorecard table and the users isreturned to the Cumulative Score Screen. Ifthe user clciks “Cancel”, the action iscancelled. 3.2Turnaround TimeScore Matrix 3.2.ACreate a Link forCreate a link for the Service Score underAppendix CService Score ScreenScorecard Menu. Link will go to the ServiceScore Screen. 3.2.BCreate Service ScoreCreate Service Score Screen to allow users toAppendix GScreenview all saved service scorecards. 3.2.B.1Create ServiceCreate a table to display Products andAppendix GScorecard TableDescription of scorecard. 3.2.B..2Add Edit ButtonsAdd edit button to edit any saved scorecard.Appendix GThe edit button will be a link to Service ScoreSetup Screen #2. 3.2.B..3Add Delete ButtonsAdd Delete buttons to delete any savedAppendix Gscorecards. Display message box “Are yousure you want to delete the saved scorecard”when the Delete button is clicked. Removescorecard from table if yes is clicked. RefreshService Score Screen. 3.2.B..4Add Create ScorecardAdd Create Scorecard Button to create newAppendix GButtonService Scorecard. Create Scorecard buttonwill be a link to Service Score Setup Screen#1. 3.2.CCreate Service ScoreCreate Service Score Setup Screen to allowAppendix HSetup Screen #1users to create a new service scorecard. 3.2.C.1Add Radio ButtonsAdd Radio Buttons to start with an existingAppendix Hscorecard. Radio button will default to No. Ifyes button is selected, provide combo box forall saved scorecards. 3.2.C.2Add Scorecard NameAdd Scorecard Name text box. This is aAppendix HText Boxrequired field. Text box should be largeenough to display 30 characters. 3.2.C.3Add ScorecardAdd Scorecard Description text box. This is aAppendix HDescription Text Boxrequired field. Text box should have a scrollbar to allow user to scroll through entiredescription. 3.2.C.5Add Next ButtonAdd Next button to link to Service Score SetupAppendix HScreen #2. If No Radio button is selected andScorecard Name is null, display message“Scorecard is Required”. 3.2.C.6Add Cancel ButtonAdd Cancel Button to link to Service ScoreAppendix HScreen. 3.2.DCreate Service ScoreCreate Service Score Setup Screen to allowAppendix ISetup Screen #2users to add products and set up Turn TimeMatrix. 3.2.D.1Display ScorecardDisplay Scorecard name t that was entered onAppendix INameService Score Setup Screen #1. 3.2.D.2Display ScorecardDisplay Scorecard Description that wasAppendix IDescriptionentered on Service Score Setup Screen #1. 3.2.D.3Add Product CategoryProvide a combo box for the user to select theAppendix ICombo Boxproduct category that the scorecard will applyto. (The category will only be those categoriesthe Requestor has setup in Products to Order) 3.2.D.4Add Product ComboProvide a combo box for the user to select theAppendix IBoxproduct that the scorecard will apply to. Thelist will only contain products that are in thechosen Product Category. (The products willonly be those products the Requestor hassetup in Products to Order) 3.1.D.5Create Product TableCreate table to display products for the currentAppendix Iscorecard. 3.1.D.6Add Product buttonAdd “Add Product” button to allow user to addAppendix Ithe selected product to the current scorecard.When Add Product button is clicked, check tomake sure that product does not exist in anysaved scorecards. If product is not in anysaved scorecards, add product selected to theProduct Table. Refresh screen after button isclicked. 3.1.D.7Add Delete ButtonsAdd Delete buttons to delete any products inAppendix Ithe Product Table. Display message box “Areyou sure you want to delete the product fromthe current scorecard” when the Delete buttonis clicked. Remove product from table if yes isclicked. Refresh screen after button is clicked. 3.2.D.8Create Turn TimeCreate Turn Time Matrix to allow user toAppendix IMatrixassign a percentage score to range of days. 3.2.D.9Add a text box for (<=)This box will contain the number of days, fromthe ordered date, it takes a vendor tocomplete an order. If the vendor completesthe order within the set period (<=), the vendorwill receive the score specified. 3.2.D.10Add Nine Range TextProvide nine range text boxes to allow theAppendix IBoxesuser to enter the number of days from the duedate for each score. 3.2.D.11Range - Rule 1When a value is entered in the first text box,the min value on the following text box willcontain the previous value + 1. (i.e 2 isentered for the first text box, 3 will bedisplayed for the min for the following range) 3.2.D.12Range - Rule 2When a value is entered for the max value,the following min value will contain theprevious max value + 1. (i.e 3 to 5 is enteredfor the range, 6 will be displayed for the minfor the following range) 3.2.D.13Range - Rule 3All min values will be grayed-out and disabled. 3.2.D.14Range - Rule 4An infinity sign will be displayed in the maxvalue for a range following a completed range. 3.2.D.15Range - Rule 5The infinity sign will be removed when themax value field is accessed. 3.2.D.16Range - Rule 6If no value is entered in the ending range'smax value field, and the user tabs out of thebox, the infinity sign is repopulated. 3.2.D.17Range - Rule 7The max value of an ending range mustcontain an infinity symbol. 3.2.D.18Range - Rule 8If a max value is lower than the min value andthe user tabs out of the max value field,display the following message “A max valuecan't be lower than the min value”. 3.2.D.19Add Service ScoreProvide a text box for the user to enter theAppendix I% Text Boxscore that is attributed to each day range.There should be ten text boxes. 3.2.D.20Service Score % - Rule 1When a value is entered in a Service Score %text field, a % is added to the value. (i.e 95 isentered, value displayed is 95%) 3.2.D.21Service Score % - Rule 2The value entered in a Service Score % textfield must be numeric. 3.2.D.22Service Score % - Rule 3Special characters can't be entered in theService Score % text field. 3.2.D.23Service Score % - Rule 4The Service Score % can't be higher than100%. 3.2.D.24Add Submit ButtonWhen the Submit button is depressed, addAppendix Icurrent service score to Service Score tableand display the Service Score Screen. 3.2.D.25Add Cancel ButtonWhen the Cancel button is depressed, themessage “All information will be lost, are yousure you wish to continue?” will appear. Thetwo options will be “Yes” or “No”. 3.3.0Automated VendorRules for the setup process for the AutomatedScoringVendor Scoring Setup 3.3.1BAutomated VendorWhen Automated Scoring link is activatedAppendix CScoring Setupfrom the Score Card page, populate theworkstation frame with the Automated Scoringpage 3.3.2BAutomated VendorProvide a table that will contain all of theAppendix JScoring Setup -Profiles created.Profile Table 3.3.3BProfile Table - ColumnsThe Profile Table's columns will be as follows:Appendix JAPS Profile NameDescriptionOptions 3.3.4BProfile Table - OptionsThe following hyperlinks will appear under theAppendix JOptions column:EditDelete 3.3.5BOptions - EditWhen the Edit link is activated, the workstationAppendix Ksection will display the Profile for editing. 3.3.6BOptions - DeleteWhen the Delete link is activated, theAppendix Jmessage “Are you sure you wish to delete thisitem?” will appear. The two options will be“Yes” or “No”. 3.3.7BProfile Table - CreateWhen the “Create New Auto-Scoring Profile”Appendix JNew Auto-Scoringbutton is depressed, the New Profile page willProfileappear in the workstation. 3.3.8BNew Auto-ScoringThe New APS Profile page will contain theAppendix KProfilefollowing sections:DescriptionProducts Fulfilled(See Appendix Q for layout) 3.3.9BAuto-Scoring Profile -Description will contain a scrolling text box.Appendix KDescription(See Appendix Q for layout) 3.3.10BAuto-Scoring Profile -Products to Order will contain the standardAppendix KProducts Fulfilledproduct selection process: Select Category,Select Product. The products available will bethose that the Requestor has setup. 3.3.11BAuto-Scoring Profile -The list of products will not contain productsProduct Sub-List 1that are contained within other Profiles withinStaging. (This prevents overlaps) 3.3.12BAuto-Scoring Profile -The list of products will only contain thoseProduct Sub-List 2products that are setup for a Quality ScoreCard. (All products must have a Quality ScoreCard association to be a product defined inAuto-Scoring). 3.3.13BAuto-Scoring Profile -When the ‘Next’ button is depressed, theAppendix KNext Buttonsecond screen of New APS Profile will appearin the workstation frame. 3.3.14BAuto-Scoring Profile -When the Cancel button is depressed, theAppendix KCancel Buttonmessage “All information will be lost, are yousure you wish to continue?” will appear. Thetwo options will be “Yes” or “No”. 3.3.15BAuto-Scoring Profile -The 2nd screen will contain the followingAppendix L2nd Screensections:Product FulfilledOptionsScore 3.3.16BAPS Profile - ProductThe Products Fulfilled section will contain theAppendix LFulfilledproduct identified in the first screen.(See Appendix R for layout) 3.3.17BAPS Profile - AddWhen the Add Product Rule button isAppendix LProduct Ruledepressed, add a row for a new Product APSrule. 3.3.18BAPS Profile - ProductThe Product section will contain the followingAppendix Lcolumns:Data ElementOperatorData ElementOperatorValueOptions 3.3.19BAPS Profile - DataWhen Data Element has ‘Product ‘selected,Appendix LElement (1) [Product]provide all “product fulfillment” fields for thespecified product in the combo-box for DataElement. (i.e. for Flood Zone DeterminationLOL, the complete dataset for Element 79) 3.3.20BAPS Profile - DataWhen Data Element has ‘Product ‘selected,Appendix LElement (1) [File]provide all “file data” fields in RT in the combo-box for Data Element. This includes theProperty BO and Loan BO data elements. 3.3.21BFile Data Element (1) -When the data type = enumerated value, theAppendix Lw/Enumerated Valuesfollowing requirements will apply: 3.3.22BOperator (1) -When the data type of Data Element (1) = ‘enumeratedAppendix LEnumerated Valuesvalue’, then provide the followingvalue in the combo-box:=<=> 3.3.23BData Element (2) -This field should be disabled and grayed-out.Appendix LEnumerated Values 3.3.24BOperator (2) -This field should be disabled and grayed-out.Appendix LEnumerated Values 3.3.25BValue - EnumeratedProvide the data element (1) enumeratedAppendix LValuesvalue list in a combo-box 3.3.26BFile Data Element (1) -When the data type = numeric, the followingAppendix Lw//Numeric Valuesrequirements will apply: 3.3.27BOperator (1) - non-When the data type of Data Element (1) = ‘numeric’,Appendix Lenumerated valuesthen provide the following values inthe combo-box:+/*=<<=>>=<=> 3.3.28BFile Data Element (2) -Provide all “file data” fields in RT that does notAppendix LNon-Enumeratedhave a data type = ‘Enumerated Value’ in aValues Icombo-box. 3.3.29BFile Data Element (2) -Remove the value that was selected in DataAppendix LNon-EnumeratedElement (1) from the list in Data Element (2).Values II 3.3.30BOperator (2) -When the data type of Data Element (1) = ‘numeric’,Appendix LEnumerated Valuesthen provide the following values inthe combo-box:N/A+/*=<<=>>=<=>In RangeOutside Range 3.3.31BValue - Non-Provide an open text box.Appendix LEnumerated Values 3.3.32BValue - Data TypeThe data entered must be numericAppendix L 3.3.33BValue - Character limit10 character limitAppendix L 3.3.34BValue - DecimalAllow up to two decimal placesAppendix L 3.3.35BData Element (2)Rules for Data Element (2)Appendix L 3.3.36BData Element (2) -Defaults value = N/AAppendix LDefault 3.3.37BOperator (2) - N/AWhen Data Element (2) value is = N/A, thenAppendix LOperator (2) is disabled and grayed-out. 3.3.38BOperator (2)Rules for Operator (2)Appendix L 3.3.39BOperator (2) -Provide the following values in the combo-box:Appendix LEnumerated ValuesN/A+/*=<<=>>=<=>In RangeOutside Range 3.3.40BOperator (2) - RangeIf Operator (2) value = Range, then provideAppendix Ltwo text boxes.(See Appendix R for layout) 3.3.41BDelete LinkRules for Delete linkAppendix L 3.3.42BDelete linkWhen the Delete link is activated, theAppendix Lmessage “Are you sure you wish to delete thisitem?” will appear. The two options will be“Yes” or “No”. 3.3.43BAdd Rule ButtonRules for Add Rule buttonAppendix L 3.3.44BAdd Rule ButtonWhen the add Rule button is depressed, add aAppendix Lrow for a new APS rule. 3.3.45BSave ButtonRules for Save ButtonAppendix L 3.3.46BSave ButtonWhen the Save Button is depressed, itAppendix Lsubmits Profile and brings you to the Auto-Scoring Profile page 3.3.47BCancel ButtonRules for Cancel ButtonAppendix L 3.3.48BCancel ButtonWhen the Cancel Button is depressed, displayAppendix L“Are you sure you want to cancel this action?”The two options will be “Yes” or “No”. 3.3.49BCancel Button - YesIf Yes is selected, action cancelled, takes youAppendix Lto Auto-Scoring Profile page. 3.3.50BProduct FulfillmentRules for Product Fulfillment APS - OptionsAppendix LAPS - Options 3.3.51BProduct FulfillmentThere will be two option boxes for ProductAppendix LAPS - OptionsFulfillment APS:Both of the rules fit the criteriaEither of the rules fit the criteria 3.3.52BOptions - Both RulesIf the option box ‘Both of the rules fit theAppendix Lcriteria’ is selected then both of the rules musttake place for the APS to take place. 3.3.53BOptions - Either of theIf the option box ‘Either of the rules fit theAppendix LRulescriteria’ is selected then if either of the rulescan happen for the APS to take place. 3.3.54BScoreThis is the score the vendor will receive if theAppendix Lrules are met. 3.3.55BAuto-Scoring - ScoreA combo-box with the list of the possibleAppendix Lscores for that product's Score Card will becontained within the combo-box. 3.3.54BAPS Profile - SubmitWhen the ‘Submit’ button is depressed, theAppendix LButtonProduct Fulfillment APS page will appear inthe workstation frame. 3.3.55BAPS Profile - CancelWhen the Cancel button is depressed, theAppendix LButtonmessage “All information will be lost, are yousure you wish to continue?” will appear. Thetwo options will be “Yes” or “No”. 3.4Quality ScoringAbility to applyscorecard to multipleproducts 3.4.AUpdate QualityAdd new column to quality scorecard table toAppendix CScorecard Tabledisplay products that saved scorecards applyto. 3.4.BUpdate Quality ScoreProvide the ability to assign products to aAppendix MSetup Screen #2quality scorecard. 3.4.B.1Add Product categoryProvide a combo box for the user to select theAppendix NCombo Boxproduct category that the scorecard will applyto. 3.4.B.2Add Product ComboProvide a combo box for the user to select theAppendix NBoxproduct that the scorecard will apply to. Thelist will only contain products that are in thechosen Product Category. 3.4.B.3Create Product TableCreate table to display products for the currentAppendix Nscorecard. 3.4.B.4Add Product buttonAdd “Add Product” button to allow user to addAppendix Nthe selected product to the current scorecard.When Add Product button is clicked, check tomake sure that product does not exist in anysaved scorecards. If product is not in anysaved scorecards, add product selected to theProduct Table. Refresh screen after button isclicked. 3.4.B.5Add Delete ButtonsAdd Delete buttons to delete any products inAppendix Nthe Product Table. Display message box “Areyou sure you want to delete the product fromthe current scorecard” when the Delete buttonis clicked. Remove product from table if yes isclicked. Refresh screen after button is clicked.Delete CurrentDelete the current Scorecard/Product SetupScorecard/Productfeatures located within the Product Page.Setup 4.0AEnhanced QualitativeEnhanced QualitativeThis function will provide the users of AVS theDistributionDistributioncapability of distributing orders to vendorsbased on the history of their turn-timeperformance. The cumulative score functionwill allow a requestor to uniquely weight avendor's quality score w/the vendor's servicescore on a per product basis. 4.1ATurn-time scoreThis function will provide the users of AVS thecriteria.capability of distributing orders to vendorsbased on the history of their turn-timeperformance. 4.2ACumulative scoreTHE CUMULATIVE SCORE FUNCTION WILLcriteria.ALLOW A REQUESTOR TO UNIQUELY WEIGHTA VENDOR'S QUALITY SCORE W/THEVENDOR'S SERVICE SCORE ON A PERPRODUCT BASIS.Automated VendorSelection 4.0CAdd’l Distribution LimitsAdd’l Distribution LimitsThis function will provide the users of AVS thecapability of preventing distribution of ordersto vendors that do not fall into the automateddistribution model. 4.2COutstanding Late OrderThis function will provide the users of AVS theAppendix YRatiocapability of preventing distribution of ordersto vendors that do not have more than “x”percent of late orders/“x” percent orders 4.3CDaily CapacityThis will provide the users of AVS theAppendix Ycapability of limiting the number of ordersgiven to a vendor on a given day. 4.3C1Daily CapacityDaily capacity is the maximum number of newDefinition/Calculationorders a vendor can receive in a given day. 4.3C2Add Daily Capacity toAdd Daily Capacity to Products OrderedProducts OrderedVendor Selection Screen.Vendor SelectionScreen 4.3C3Daily Capacity Rule 1The auto vendor selection feature shouldeliminate vendors who have reached theirdaily capacity.automateddistribution model. 4.1DAuto-ReprocessThis function will provide the users of AVS theDeclined Orderscapability of reprocessing a declined order.This reprocessing will create a new order,deselect the original vendor from the availabledistribution list, run the AVS engine, select thevendor, and place the order. 4.2DDistribution OptionAdd a distribution option section to theSectionDistribution Option Page. 4.3DAuto-ReprocessAdd a Yes/No option box for Auto-ReprocessDeclined OrdersDeclined Orders.Option Box 4.4DAuto-ReprocessWhen an order is declined, and the product isDeclined Ordersselected for AVS, and Yes is selected forAuto-Reprocess Declined Orders, the orderautomatically gets reprocessed.Data needed for reprocessing:Declined StatusOrder IDRESP ID 4.5DReprocessThe original declined order's order form will beFunctionality 1used to create a duplicate order. 4.6DReprocessThe duplicate order will be processed via theFunctionality 2AVS engine, with the original vendor (thatdeclined the order) de-selected from theeligible vendor list. 4.7DReprocessIf successfully placed via the AVS engine, theFunctionality 3order will be placed to the selected vendor. 4.8DReprocessIf there is a problem with the AVS processing,Functionality 4the file will be sent to the exception bin withthe reason for the exception. 4.9DReprocess - SubstatusThe Placed status should contain a substatusof Reprocessed. 4.10DReprocess - Event LogThe reprocessing events should be loggedwithin the Event Log. 4.0EAVS - Pre Order FormAVS - Pre Order FormThis function will use the AVS functionalitySubmissionSubmissionprior to order form submission. 4.1EExpanding File LevelThis modification will expand the file levelDatainformation to capture key data that will beused for AVS. 4.2EPre-Selection of BestThis functionality will pre-select “the best”Vendorvendor that the RT engine has selected. 4.3EDisplaying AvailableThis functionality will display vendors that areVendors for Distributionavailable for distribution. 4.4EAVS Selection OverrideThis functionality will allow for the user tooverride the AVS decision. 4.5EAVS Selection - OrderThe vendor's order count will be incrementedCountingwhen the order is placed (Not when the AVSrules engine selects the vendor) 5.1AOrder Forwarding -Order Forwarding -Provide the ability for auto vendor selection toAVSAVSwork with Order Forwarding 5.2AOrder Forwarding -When the forward link is activated, if theAppendix OAVSrequestor is VM enabled the AVS engine willrun the rules, and highlight the AVS selectedvendor. 5.3AOrder Forwarding PageExpand the Order Fowarding page to includeAppendix Othe additions made to the new ordering pagedetailed in Xpress Ordering. 5.4AOrder ForwardingDetailed below are the Order ForwardingAppendix OChanges:changes 5.5AFilter OptionsThe filter options detailed in Appendix CAppendix Oshould duplicate the current vendor filters inREALTrans.(The screen layout is detailed in Appendix L.) 5.6AVendor List TableThe available vendor list should be displayedAppendix Lin a table depicted in Appendix C. The tableshould contain the following sections/columns.AVS Profile NameAVS Distribution Rule IDCompany NameBranch NameCityStateVendor TypeNational Coverage FlagSLA Price% Current profile ordersCurrent Vendor GradeCurrent capacityAuto-Select FlagExceeded Capacity FlagCurrent late order ratio(See Appendix C for details on layout of thetable.) 5.7AAVS Profile NameDisplay the AVS Profile NameAppendix O 5.8AAVS Distribution RuleDisplay the AVS Distribution Rule IDAppendix OID 5.9ACompany NameDisplay the vendor's Company NameAppendix O 5.10ABranch NameDisplay the vendor's Branch NameAppendix O 5.11ACityDisplay the vendor's CityAppendix O 5.12AStateDisplay the vendor's StateAppendix O 5.13AVendor TypeDisplay the vendor's Vendor TypeAppendix O 5.14ANational Coverage FlagDisplay a check mark if the vendor hasAppendix Onationwide coverage 5.15ASLA PriceDisplay the vendor's SLA priceAppendix O 5.16A% Current profileIf the Distribution Rule is set for % distribution,Appendix Oordersthen display the vendor's percentage ofcurrent profile orders 5.17ACurrent Vendor GradeDisplay the vendor's current vendor gradeAppendix O 5.18ACurrent capacityDisplay the vendor's current capacityAppendix O 5.19AAuto-Select FlagDisplay a check mark if the vendor is markedAppendix Ofor AVS 5.20AExceeded CapacityDisplay a check mark if the vendor hasAppendix OFlagExceeded Capacity 5.21ACurrent late order ratioDisplay the vendor's current late order ratioAppendix O(Late Open Orders/Total Open orders) 5.22ASelected VendorThe entire row for the Vendor selected by theAppendix OAVS engine should be highlighted.(See Appendix C in Xpress Ordering Req fordetails on layout of the table.) 5.23AScreen LayoutThe screen layout is detailed in Appendix C inAppendix OXpress Ordering Req. 5.24ACommand Button -When the Next command is depressed, theAppendix ONextuser should be brought to the selected(Single Productproduct's order form (Appendix D in XpressSelected)Ordering Req). 5.25ACommand Button -When the Next command is depressed, theAppendix ONextuser should be brought to the consolidated(Multiple Productsorder form (Appendix E in Xpress OrderingSelected)Req). 5.26ACommand Button -When the Cancel command is depressed, theAppendix OCancelorder placement should be halted and theuser should be brought to the Ordering Page(Appendix A in Xpress Ordering Req). 5.0BBulk Order ForwardingProvide the ability for a vendor to bulk forwardAppendix Sorders by either Prortfolio or by Requestor.The Bulk Order Forwarding will be used inconjunction with AVS. 5.1BBulk Order ForwardingIf the client's account is VM enabled, provide aAppendix SBulk Order Forwarding section in the BulkManagement Screen. 5.2BBulk Order Forwarding -The orders will be able to be filtered by:Appendix SFiltersPortfolio NumberIn the vendor's entire system 5.3BBulk Order Forwarding -This filter will display the specified product forAppendix SSpecified Categoryeach file that has a status of New (10) orTypeConfirmed (20) in their system. (This can alsobe sub-filtered by Portfolio.) 5.4BBulk Order Forwarding -If only the product type is specified, this willAppendix SSystemdisplay the specified product for each file inthe vendor's system. 5.5BBulk Order Forwarding -This sub-filter will display the specified productAppendix SPortfolio Number(Req # 5.3B) for each file that has a status ofNew (10) or Confirmed (20), in the specifiedPortfolio. 5.7BBulk Order Forwarding -When the ‘Go’ button is depressed, theAppendix S‘Go’ Buttonspecified filters will be ran, and the 2nd pagewill appear (AppendixT). 5.8BOrder ForwardingThe order forwarding options detailed inAppendix TOptionsAppendix C should duplicate the current orderforwarding options in REALTrans.(The screen layout is detailed in Appendix T.) 5.9BBulk Order Forwarding -This page will display the orders that haveAppendix TOrder Pagebeen specified by the filters on the previouspage. 5.10BBulk Order Forwarding -The table of orders will consist of the followingAppendix TOrder Page Tablecolumns:SelectProductFile #Vendor Order #PropertyBorrowerRequestorOrdered DateDue DateStatusOrder Form 5.11BBulk Order Forwarding -This column will contain a check box thatAppendix TSelectselects (if checked) or deselects (ifunchecked) the order to be forwarded 5.12BBulk Order Forwarding -This column will contain the Product NameAppendix TProduct 5.13BBulk Order Forwarding -This column will contain the File NumberAppendix TFile # 5.14BBulk Order Forwarding -This column will contain the Vendor OrderAppendix TVendor Order #Number 5.15BBulk Order Forwarding -This column will contain the Property AddressAppendix TProperty 5.16BBulk Order Forwarding -This column will contain the Borrower's FirstAppendix TBorrowerand Last Name 5.17BBulk Order Forwarding -This column will contain the Requestor's nameAppendix TRequestorthat is ordering the product 5.18BBulk Order Forwarding -This column will contain the date the productAppendix TOrdered Datewas ordered 5.19BBulk Order Forwarding -This column will contain the date the productAppendix TDue Dateis due 5.20BBulk Order Forwarding -This column will contain the Stauts of theAppendix TStatusorder (New or Confirmed) 5.21BBulk Order Forwarding -This column will contain an icon that links toAppendix TOrder Placement Formthe Order Placement Form. 5.22BActivation of the OrderWhen the Order Placement Form icon isAppendix TPlacement Form Iconactivated, the Order Placement Form willappear in a separate window. 5.23BEditing of the OrderWhen the Order Placement Form is edited,Appendix TPlacement Formthe Bulk Order Forwarding page will updatethe changes. 5.24BBulk Order Forwarding -The standard page scrolling function will beAppendix TPage scrollinglocated on the bottom of the page. (SeeAppendix T) 5.25BBulk Order Forwarding -When the ‘Auto Select Vendors’ button isAppendix TAuto Select Vendorsdepressed, each order will run the AVS rules,and then place the selected orders to thevendors specified in the AVS engine. 5.26BBulk Order Forwarding -If the AVS engine can't place an order forAppendix TException Binwhatever reason (i.e no vendor coverage,error, etc . . . ), the files will be sent to theException Bin. 7.0Work QueuesProvide the capability of creating flexible workqueues that will contain orders that meet thespecified criteria. The criteria for each workqueue must be rules driven and set up ormodified by the account administrator. 7.0ACreate Work QueueCreate a screen to allow the user to view allDisplay ScreenWork Queues that have been created. 7.1AAdd Work QueuesAdd a menu option for Work Queues underMenu Optionthe ‘Admin’ button. 7.2ACreate Work QueueCreate a screen to display all active andAdministration screeninactive work queues. 7.3ACreate Work QueueCreate work queue table to store all workAppendix BBtablequeues and information related to the workqueues. 7.4AWork Queue tableThe Work Queue table's columns will be:columnsWork Queue DescriptionWork Queue TypeWork Queue StatusWork Queue Created DateWork Queue Inactive DateOptions 7.4A1Work Queue table -The Work Queue Description will display theWork Queuedescription of the work queue.Description 7.4A2Work Queue table -The Work Queue Type will display the type ofWork Queue Typework queue. The type of work queue will beWorkFlow or Work Queue. 7.4A3Work Queue StatusThe Work Queue Status will display thecurrent status of the work queue. 7.4A4Work Queue CreatedThe Work Queue Created Date will display theDatedate that the work queue was created. 7.4A5Work Queue InactiveThe Work Queue Created Date will display theDatedate that the work queue was inactivated. 7.5AWork Queue table -The following buttons will appear under theOptionsOptions column:EditDelete 7.6AOptions - Edit ButtonWhen the ‘Edit’ button is clicked, the WorkActionQueue setup screen will appear for thecorresponding Work Queue. 7.7AOptions - DeleteWhen the ‘Delete’ button is clicked, theButtonmessage “Are you sure you want to delete thisitem?” 7.8A.1Delete Message BoxThe Delete Message Box will contain twobuttons - “OK” and “Cancel” 7.8A.2Delete Message Box -When the ‘OK’ button is clicked, the workOK Buttonqueue will be deleted and the Work QueueDisplay screen will refresh. 7.8A.3Delete Message Box -When the ‘Cancel’ button is clicked, theCancel ButtonMessage box will close and no changes willbe made. 7.8AAdd Create New ButtonWhen the ‘Create New’ button is clicked theWork Queue setup screen will appear. 7.0BCreate Workflow/Create a screen to allow the user to setupAppendix CCQueue Setup Screenwork queues and workflows. 7.1BAdd Description TextAdd a text box to the Work Queue Setupbox to Work Queuescreen to allow the user to enter a descriptionSetup screenof the Work Queue. The text box should allowup to 250 characters. 7.2BAdd Work Queue TypeAdd a combo box to the Work Queue SetupCombo box to Workscreen to allow the user to specify the type ofQueue Setup screenwork queue being created. 7.2B1Work Queue Type -The Work Queue Type combo box shouldValuescontain the following values:Work QueueWork Flow 7.3BAdd Active RadioAdd a radio button to the Work Queue SetupButton to Work Queuescreen to allow the user to mark the currentSetup screenwork queue as active. 7.4B1Add Active Date field toAdd a field to the Work Queue Setup screenWork Queue Setupto display the date that the work queue wasscreenmarked as active. 7.4B2Active Date field - RuleThe Active Date field should automaticallypopulate based on the date that the ActiveRadio Button is clicked. 7.5BAdd Inactive RadioAdd a radio button to the Work Queue SetupButton to Work Queuescreen to allow the user to mark the currentSetup screenwork queue as inactive. 7.6B1Add Inactive Date fieldAdd a field to the Work Queue Setup screento Work Queue Setupto display the date that the work queue wasscreenmarked as inactive. 7.6B2Inactive Date field -The Active Date field should automaticallyRulepopulate based on the date that the InactiveRadio Button is clicked. 7.7B1Setup Screen - NextAdd a ‘Next’ button to the Work Queue setupbuttonscreen. 7.7B2Next Button - Rule 1When the ‘Next’ button is clicked, if value inthe Work Queue Type Combo Box equals“Work Queue” the Work Queue setup2 screenwill appear. 7.7B3Next Button - Rule 2When the ‘Next’ button is clicked, if value inthe Work Queue Type Combo Box equals“Work Flow” the WorkFlow setup2 screen willappear. 7.8BSetup Screen - CancelAdd a ‘Cancel’ button to the Work Queuebuttonsetup screen. When the ‘Cancel’ button isclicked, the Work Queue Display screen willappear. 7.9B1Setup2 screen -Provide a warning message that appears if theCancel Warning‘Cancel’ button is clicked. The warning shouldMessageread “Are you sure you want to Cancel thesetup?” 7.9B2Warning MessageProvide an ‘OK’ button on the warningbutton - OKmessage. If the ‘OK’ button is clicked allchanges will be lost and the Work QueueDisplay screen will appear. 7.9B3Warning MessageProvide a ‘Cancel’ button on the warningbutton - Cancelmessage. If the ‘Cancel’ button is clicked thewarning message will close and the Setupscreen will appear. 7.0CCreate Work QueueCreate a screen to allow the user to setupSetup 2 Screenwork queues and select the fields that will beused in the work queue. 7.1CSetup Screen 2 -Add a table to display all available fields forAppendix DDFields Availablethe Work Queue. 7.2CSetup Screen 2 - FieldsAdd a table to display all fields selected for theSelectedWork Queue. 7.3C.1Setup Screen 2 - SelectProvide a button for the user to select theField buttonhighlighted field in the ‘Fields Available’ table. 7.3C.2Select Field Button -When the button is clicked, the highlightedActionfield is moved to the ‘Fields Selected’ tableand removed from the ‘Fields Available’ table. 7.4CSetup Screen 2 -Provide a warning message that appears if theSelect Warning‘Select Field’ button is clicked withoutMessagehighlighting a field in the ‘Fields Available’ listbox. The warning should read “Please selecta field from the list of Fields Available”. 7.5CSetup Screen 2 -Provide a button for the user to deselect theDeselect Field buttonhighlighted field. When the button is clickedthe highlighted field should be moved to the‘Fields Available’ table and removed from the‘Fields Selected’ table. 7.6CSetup Screen 2 -Provide a warning message that appears if theDeselect Warning‘Deselect Field’ button is clicked withoutMessagehighlighting a field in the ‘Fields Selected’ listbox. The warning should read “Please selecta field from the list of Fields Selected”. 7.7CSetup Screen 2 -Provide a button for the user to deselect all ofDeselect All Fieldsthe fields from the ‘Fields Selected’ list. Whenbuttonthe button is clicked, all fields in the ‘FieldsSelected’ table should be moved to the ‘FieldsAvailable’ table and removed from the ‘FieldsSelected’ table. 7.8CSetup Screen 2 - NextAdd a ‘Next’ button to the Work Queue Setupbutton2 screen. When the ‘Next’ button is clicked,the Work Queue setup2 screen will appear. 7.9CSetup Screen 2 -Add a ‘Cancel’ button to the Work QueueCancel buttonSetup 2 screen. When the ‘Cancel’ button isclicked, the Work Queue Display screen willappear. 7.10CSetup screen 2 -Provide a warning message that appears if theCancel Warning‘Cancel’ button is clicked. The warning shouldMessageread “Are you sure you want to Cancel thesetup?” 7.11CWarning MessageProvide an ‘OK’ button on the warningbutton - OKmessage. If the ‘OK’ button is clicked allchanges will be lost and the Work QueueDisplay screen will appear. 7.12CWarning MessageProvide a ‘Cancel’ button on the warningbutton - Cancelmessage. If the ‘Cancel’ button is clicked thewarning message will close and the Setupscreen will appear. 7.13CVendor Fields AvailableThe Vendor fields that should be available are:Contact NameCompany NameCompany AddressCompany CityCompany StateCompany ZipBusiness PhoneEmail AddressCell Phone 7.14CAdd Calculated FieldAdd a button to allow the user to create aButtoncalculated field. 7.15CCalculated Field Button -When the Calculated Field Button is clicked,Actionthe Calculated Field screen will open. 7.0DCreate Work QueueCreate a screen to allow the user to sort theAppendix EESetup Screen 3fields that will be displayed in the WorkQueue. 7.1D1Add Selected FieldsAdd a table to contain all selected fields to thetable to Setup Screen 3Work Queue Setup Screen 3. 7.1D2Selected Fields Table -The Selected Fields table should contain allValuesfields in the selected Fields table from theWork Queue Setup Screen 2. 7.2D1Add Move to TopAdd Move to Top button to the Work Queuebutton to the SetupSetup Screen 3.Screen 3 7.2D2Move to Top button -When the Move to Top button is clicked, theActionhighlighted field should be moved to the top ofthe list. 7.2D3Move to Top button -When the Move to Top button is clicked, if theRule 1field is already located at the top of the list, theMove Up Warning message box shouldappear. 7.3D1Add Move to BottomAdd Move to Bottom button to the Workbutton to the SetupQueue Setup Screen 3.Screen 3 7.3D2Move to Bottom button -When the Move to Bottom button is clicked,Actionthe highlighted field should be moved to thebottom of the list. 7.3D3Move to Bottom button -When the Move to Bottom button is clicked, ifRule 1the field is already located at the bottom of thelist, the Move Down Warning message boxshould appear. 7.4D1Add Move Up button toAdd Move Up button to the Work Queuethe Setup Screen 3Setup Screen 3. 7.4D2Move Up button -When the Move Up button is clicked, theActionhighlighted field should be moved up oneposition in the list. 7.4D3Move Up button - Rule 1When the Move Up button is clicked, if thefield is already located at the top of the list, theMove Up Warning message box shouldappear. 7.5D1Add Move Down buttonAdd Move Down button to the Work Queueto the Setup Screen 3Setup Screen 3. 7.5D2Move Down button -When the Move Down button is clicked, theActionhighlighted field should be moved down oneposition in the list. 7.5D3Move Down button -When the Move to Bottom button is clicked, ifRule 1the field is already located at the bottom of thelist, the Move Down Warning message boxshould appear. 7.6DMove Up WarningThe Move Up Warning message should readMessage - Details“The selected field is at the top of the list. 7.7DMove Down WarningThe Move Down Warning message shouldMessage - Detailsread “The selected field is at the bottom of thelist. 7.8D1Add Remove Button toAdd Remove button to the Work Queue Setupthe Setup Screen 3Screen 3. 7.8D2Remove Button -When the Remove button is clicked, theActionhighlighted field should be removed from thelist. 7.0ECreate Work QueueCreate a screen to determine how each of theAppendix FFCriteria screenfields selected in Work Queue Setup 3 screenwill be used. 7.1ECriteria screen -Display all fields in the “Fields Selected” tableDisplay Fieldson the Work Queue Criteria screen. The fieldsshould be displayed in one column verticallydown the left side of the screen. 7.2ECriteria screen - ShowAdd a check box to the right of each field thatCheck Boxis in the ‘Fields Selected’ table. If the box ischecked the field will be displayed in the WorkQueue. If the box is not checked the field willnot be displayed, but it can be used as criteria. 7.3ECriteria screen -Add a combo box to the right of each checkOperator combo boxbox containing the following values:=>> =<< =< > 7.4ECriteria screen - FilterAdd a text box to the right of each operatorText Boxcombo box. This text box will contain thecriteria for the Work Queue. 7.5ECriteria screen - BackAdd a ‘Back’ button to the Work QueuebuttonCriteria screen. When the ‘Back’ button isclicked, the Work Queue setup screen willappear. All of the fields that were in the‘Fields Selected’ table should remain in the‘Fields Selected’ table. All changes to theWork Queue Criteria screen should save. 7.6ECriteria screen - NextAdd a ‘Next’ button to the Work Queue Criteriabuttonscreen. When the ‘Next’ button is clicked, theWork Queue setup3 screen will appear. All ofthe changes to the Work Queue Criteriascreen should save. 7.7ECriteria screen -Add a ‘Cancel’ button to the Work QueueCancel buttonCriteria screen. 7.8ECriteria screen -Provide a warning message that appears if theCancel Warning‘Cancel’ button is clicked. The warning shouldMessageread “Are you sure you want to Cancel thesetup?” 7.9EWarning MessageProvide an ‘OK’ button on the warningbutton - OKmessage. If the ‘OK’ button is clicked allchanges will be lost and the Work QueueDisplay screen will appear. 7.10EWarning MessageProvide a ‘Cancel’ button on the warningbutton - Cancelmessage. If the ‘Cancel’ button is clicked thewarning message will close and the Criteriascreen will appear. 7.0FCreate Work QueueAppendix GGAdmin Screen 7.1F.1Add User Combo boxAdd a combo box to allow the user to selectthe user or users that will be associated to thework queue. 7.1F.2User Combo box -The combo box should contain all users set upDetailsfor the account. 7.1F.3User Combo box -The user should be able to select multipleMultiple Selectionsusers by holding down the control button. 7.2F.1Add Group Combo boxAdd a combo box to allow the admin to selectthe group or groups that will be associated tothe work queue. 7.2F.2Group Combo box -The combo box should list all users set up forDetailsthe account. 7.2F.3Group Combo box -The user should be able to select multipleMultiple Selectionsgroups by holding down the control button. 7.3F1Add Work ScreenAdd a combo box to allow the admin to selectCombo boxthe screen that should appear when the WorkQueue user selects an order in the queue. 7.3F2Work Screen ComboThe Work Screen combo box should list allbox - Detailsscreens available to the user. Examples ofscreens that should be available are:Order ManagerValuation Product Review elementView Only Fulfillment Form for all productsVendor Maintenance ScreenMessage Center 7.3F3Work Screen ComboThe user should be able to select multiplebox - Multiplegroups by holding down the control button.Selections 7.4F1Add Work QueueAdd a combo box to allow the admin to selectSelection combo boxthe selection type for the current Work Queue. 7.4F2Selection Combo box -Add the following values to the Work QueueValuesSelection Combo box:Round RobinAuto FeedManual Select 7.4F3Round Robin SelectionWhen Round Robin is selected, the items inDescriptionthe work queue will be distributed to each userequally until all items in the work queue havebeen distributed or all users assigned to thequeue have reached their maximum capacity. 7.4F4Auto Feed SelectionWhen Auto Feed is selected, the items in theDescriptionwork queue will be distributed to each userequally automatically as each workflow item isclosed. The user will not see the WorkQueue, only the Work Queue Work Screenwill appear. 7.5F5Manual SelectWhen Manual Select is selected, the items inthe work queue will be available to all usersuntil a user selects the item to work on. Oncea user has selected an item in the workqueue, that item is unavailable for all otherusers and is removed from the work queue. 7.5F1Add Inactive Date FieldAdd a text box to enter the date that the WorkQueue will become inactive. 7.5F2Inactive Date Field -The format of the Inactive Date field should beFormata date (mm/dd/yyyy). 7.5F3Inactive Date Field -The Inactive Date field is not a required field.Rule 1 7.5F4Inactive Date Field -When the Inactive Date is less than today'sRule 2date the Work Queue status should changefrom active to inactive. 7.6F1Add Work Queue TypeAdd a combo box to allow the admin to selectcombo boxthe Work Queue Type. 7.6F2Work Queue TypeAdd the following values to the Work QueueCombo box - ValuesType Combo box:FileOrder 7.7FWork QueueThe Work Queue Distribution must refreshDistributioneach day. All items in a user's Work Queuewill be removed and redistributed at thebeginning of the day. 7.0GCreate Work FlowCreate a screen to allow the user to setupAppendix HHSetup2work flows and select the business processthat will occur when the work flow criteria ismet. 7.1G1Add Business ProcessAdd a combo box to the Work Flow Setup 2Combo Boxscreen to allow the user to select the businessprocess that will kick off when all of theworkflow criteria are met. 7.1G2Business ProcessThe Business Process Combo box will containCombo Box - Valuesall business process that have been created. 7.2G1Add Work Flow TriggerAdd a combo box to the Work Flow Setup 2Combo boxscreen to allow the user to select the triggertype for the current workflow. 7.2G2Work Flow TriggerThe Work Flow Trigger Combo box shouldCombo box - Valuescontain the following values:PassiveActive 7.3GAdd Next button toAdd a ‘Next’ button to the Work Flow Setup 2Work Flow Setup 2screen. When the ‘Next’ button is clicked, thescreenWorkFlow setup3 screen will appear. All ofthe changes to the Work Flow Setup 2 screenshould save. 7.4GAdd Cancel button toAdd a ‘Cancel’ button to the Work Flow SetupWork Flow Setup 22 screen.screen 7.5G1Cancel WarningProvide a warning message that appears if theMessage‘Cancel’ button is clicked. The warning shouldread “Are you sure you want to Cancel thesetup?” 7.5G2Warning MessageProvide an ‘OK’ button on the warningbutton - OKmessage. If the ‘OK’ button is clicked allchanges will be lost and the Work QueueDisplay screen will appear. 7.5G3Warning MessageProvide a ‘Cancel’ button on the warningbutton - Cancelmessage. If the ‘Cancel’ button is clicked thewarning message will close and the Criteriascreen will appear. 7.0HCreate Work FlowCreate a screen to allow the user to setupAppendix IISetup 3 Screenwork queues and select the fields that will beused in the work queue. 7.1H1Setup Screen 3 -Add a table to display all available fields forFields Availablethe WorkFlow. 7.2HSetup Screen 3- FieldsAdd a table to display all fields selected for theSelectedWorkFlow. 7.3H.1Setup Screen 3- SelectProvide a button for the user to select theField buttonhighlighted field in the ‘Fields Available’ table. 7.3H.2Select Field Button -When the button is clicked, the highlightedActionfield is moved to the ‘Fields Selected’ tableand removed from the ‘Fields Available’ table. 7.4HSetup Screen 3 -Provide a warning message that appears if theSelect Warning‘Select Field’ button is clicked withoutMessagehighlighting a field in the ‘Fields Available’ listbox. The warning should read “Please selecta field from the list of Fields Available”. 7.5HSetup Screen 3 -Provide a button for the user to deselect theDeselect Field buttonhighlighted field. When the button is clickedthe highlighted field should be moved to the‘Fields Available’ table and removed from the‘Fields Selected’ table. 7.6HSetup Screen 3 -Provide a warning message that appears if theDeselect Warning‘Deselect Field’ button is clicked withoutMessagehighlighting a field in the ‘Fields Selected’ listbox. The warning should read “Please selecta field from the list of Fields Selected”. 7.7HSetup Screen 3 -Provide a button for the user to deselect all ofDeselect All Fieldsthe fields from the ‘Fields Selected’ list. Whenbuttonthe button is clicked, all fields in the ‘FieldsSelected’ table should be moved to the ‘FieldsAvailable’ table and removed from the ‘FieldsSelected’ table. 7.8HSetup Screen 3 - NextAdd a ‘Next’ button to the Work Queue Setupbutton2 screen. When the ‘Next’ button is clicked,the Work Queue setup2 screen will appear. 7.9HSetup Screen 3 -Add a ‘Cancel’ button to the Work Flow SetupCancel button2 screen. When the ‘Cancel’ button is clicked,the Work Queue Display screen will appear. 7.10HSetup screen 3 -Provide a warning message that appears if theCancel Warning‘Cancel’ button is clicked. The warning shouldMessageread “Are you sure you want to Cancel thesetup?” 7.11HWarning MessageProvide an ‘OK’ button on the warningbutton - OKmessage. If the ‘OK’ button is clicked allchanges will be lost and the Work QueueDisplay screen will appear. 7.12HWarning MessageProvide a ‘Cancel’ button on the warningbutton - Cancelmessage. If the ‘Cancel’ button is clicked thewarning message will close and the Setupscreen will appear. 7.13HVendor Fields AvailableThe Vendor fields that should be available are:Contact NameCompany NameCompany AddressCompany CityCompany StateCompany ZipBusiness PhoneEmail AddressCell Phone 7.14H1Add Calculated FieldAdd a button to allow the user to create aButtoncalculated field. 7.14H2Calculated Field Button -When the Calculated Field Button is clicked,Actionthe Calculated Field screen will open. 7.0ICreate Work FlowCreate a screen to determine how each of theAppendix JJCriteria screenfields selected in Work Flow Setup 3 screenwill be used. 7.1ICriteria screen -Display all fields in the “Fields Selected” tableDisplay Fieldson the WorkFlow Criteria screen. The fieldsshould be displayed in one column verticallydown the left side of the screen. 7.2ICriteria screen -Add a combo box to the right of each checkOperator combo boxbox containing the following values:=>>=<<=<> 7.3ICriteria screen - FilterAdd a text box to the right of each operatorText Boxcombo box. This text box will contain thecriteria for the WorkFlow. 7.4ICriteria screen - BackAdd a ‘Back’ button to the WorkFlow Criteriabuttonscreen. When the ‘Back’ button is clicked, theWorkFlow setup screen 3 will appear. All ofthe fields that were in the ‘Fields Selected’table should remain in the ‘Fields Selected’table. All changes to the WorkFlow Criteriascreen should save. 7.5ICriteria screen - NextAdd a ‘Next’ button to the WorkFlow Criteriabuttonscreen. When the ‘Next’ button is clicked, theWorkFlow setup3 screen will appear. All ofthe changes to the WorkFlow Criteria screenshould save. 7.6ICriteria screen -Add a ‘Cancel’ button to the WorkFlow CriteriaCancel buttonscreen. 7.7ICriteria screen -Provide a warning message that appears if theCancel Warning‘Cancel’ button is clicked. The warning shouldMessageread “Are you sure you want to Cancel thesetup?” 7.8IWarning MessageProvide an ‘OK’ button on the warningbutton - OKmessage. If the ‘OK’ button is clicked allchanges will be lost and the WorkFlow Displayscreen will appear. 7.9IWarning MessageProvide a ‘Cancel’ button on the warningbutton - Cancelmessage. If the ‘Cancel’ button is clicked thewarning message will close and the Criteriascreen will appear. 7.0JAdd Work Queue LinkAdd a link to the Work Queue display screenAppendix OOto Menu Barto the menu bar. 7.1JAdd Link to WorkAdd a link to the Menu Bar to direct users toQueue to Menu Barthe Work Queue Display screen. 7.0KAdd Work Queue toAdd Work Queue to the View SelectionAppendix QQthe View SelectionCombo box.Combo Box 7.1KAdd Work Queue toAdd a link to the View Selection Combo box toView Selection Combodirect the user to the Assigned Work Queueboxscreen. 7.0LCreate Assigned WorkCreate a screen to allow users to select fromAppendix RRQueue Screenall Work Queues that they have beenassigned to. 7.1LAdd Assigned WorkAdd a combo box to display all work queuesQueues combo box tothat the current user is assigned to.Assigned Work QueueScreen 7.2L1Add ‘Go’ button to theAdd ‘Go’ button to the Assigned Work QueueAssigned Work Queuescreen.Screen 7.2L2Go Button - ActionWhen the ‘Go’ button is clicked, the WorkQueue screen for the selected work queue willappear. 7.0MCreate Work QueueCreate Work Queue screen to display all itemsAppendix SSscreenthat have not been completed in a workqueue. 7.1M1Create Work QueueCreate a table to display details about theDetail Tableitems in the current work queue. 7.1M2Add Work Queue ItemAdd the link to the Work Queue item to thelink to Work Queuework queue table.Detail Table 7.1M3Work Queue Item Link -When the Work Queue Item Link is clicked, aActionseparate window will open with the workscreen selected for the current work queue.The screen will open inside of the WorkQueue Frame. 7.1M4Add Work Queue ItemAdd the date that the item appeared in theDate to Work Queuework queue to the work queue table.Detail Table 7.1M5Add Work Queue ItemAdd the status of the item to the work queuelink to Work Queuetable.Detail Table 7.1M6Work Queue ItemThe Statuses that will be displayed in theStatusesWork Queue table will be:ViewedNewCompleted 7.1M7Work Queue ItemThe Work Queue Item Status for an order thatStatus - Newappears in a work queue and has not beenviewed by any user and has not beencompleted will have a status of ‘New’. 7.1M9Work Queue ItemThe Work Queue Item Status for an order thatStatus - Viewedappears in a work queue and has beenviewed by a user and has not been completedwill have a status of ‘Viewed’. The item is notremoved from the work queue, but it is movedto the bottom of the work queue. 7.1M10Work Queue ItemThe Work Queue Item Status for an order thatStatus - Completedappears in a work queue and has beenviewed by a user and has been completed willhave a status of ‘Completed’. 7.1M11Add Work Queue ItemAdd the user name that the Work Queue ItemViewed By to Workwas last viewed by.Queue Detail Table 7.1M12Work Queue ItemWill only be available for items with a status ofViewed By - Rule‘Viewed’. 7.1M13Add Work Queue ItemAdd the date that the Work Queue Item wasViewed On to Worklast viewed on.Queue Detail Table 7.1M14Work Queue ItemWill only be available for items with a status ofViewed On - Rule‘Viewed’. 7.2M1Create Work QueueCreate a Frame that will open when the WorkAppendix TTFrameQueue Item Link is clicked. 7.2M2Add Work Queue ItemAdd the Item Status to the Work QueueStatus to Work QueueFrame.Frame 7.2M3Add Work Queue ItemAdd the user name of the last person thatViewed By to Workviewed the work queue item.Queue Frame 7.2M4Add Work Queue ItemAdd the last date that the work queue itemViewed On to Workwas viewed.Queue Frame 7.2M5Add ‘Complete’ buttonAdd the ‘Complete’ button to the Work Queueto the Work QueueFrame.Frame 7.2M6Complete Button -When the Complete button is clicked, the workAction 1queue item status will change to complete. 7.2M7Complete Button -When the Complete button is clicked, theAction 2Work Queue screen will appear if the WorkQueue Selection type is not ‘Auto Feed’. 7.2M8Complete Button -When the Complete button is clicked, if theAction 3Work Queue Selection type is ‘Auto Feed’, thecurrent item will close and the next workqueue item will appear in the Work QueueFrame. 7.0NCreate CalculatedCreate a screen to allow the user to create aAppendix YYField Screencalculated field. 7.1NAdd Field Name toAdd a text box to allow the user to name theCalculated Fieldfield that is being created.Screen 7.2NAdd Input Button toAdd a button to the Calculated Field screenCalculated Fieldthat will change the Field Variable to a textScreenbox. This will allow the user to enter free formvalues. 7.3NAdd Select Button toAdd a button to the Calculated Field screenCalculated Fieldthat will change the Field Variable to a ComboScreenbox. This will allow the user to select a field. 7.4N1Add Field SelectAdd a combo box to the Calculated FieldCombo Box toscreen that will allow the user to choose a fieldCalculated Fieldto perform a calculation.Screen 7.4N2Select Combo box -The Select Combo box will contain the sameValuesvalues that are available in the CriteriaSelection screen. 7.5NAdd Field Text Box toAdd a text box to allow the user to enter aCalculated Fieldvalue to perform a calculation.Screen 7.6NField Variable - DefaultField Variable should default to the Combobox. 7.7N1Add ‘Add’ button to theAdd a button to the Calculated Field screen toCalculated Fieldallow a user to add another text box or selectScreencombo box. 7.7N2‘Add’ Button - Action 1When the ‘Add’ button is clicked, the operatorAppendix ZZcombo box will appear. 7.7N3‘Add’ Button - Action 2When the ‘Add’ button is clicked, the ‘Input’Button will appear. 7.7N4‘Add’ Button - Action 3When the ‘Add’ button is clicked, the ‘Select’Button will appear. 7.7N5‘Add’ Button - Action 3When the ‘Add’ button is clicked, the FieldVariable will appear. 7.7N6‘Add’ Button - Action 4When the ‘Add’ button is clicked, the ‘Add’button will appear. 7.7N7Add Button - RuleEach time the ‘Add’ button is clicked a newrow should be added and all of the aboveitems should be provided. 7.8N1Add Operator ComboAdd a combo box to include all operators thatBox to Calculated Fieldwill be needed to create a calculated field.Screen 7.8N2Operator Combo Box -The Operator Combo box should contain theValuesfollowing values:+/* 7.0Add Unavailable DateProvide the ablility for a vendor to removeAppendix UUto Vendor Informationitself from a list of available vendors for aScreenspecified period of time. This will benecessary if a vendor is going on vacation orunavailable for a period of time. 7.1AAAdd Unavailable FlagAdd a check box to the vendor informationAppendix UUto Vendor Informationscreen.screen 7.1BBUnavailable Flag -When the Unavailable Flag is checked, theAppendix UUActionvendor will not appear as an available vendorfor all requestors. 7.2AAAdd Unavailable StartAdd a field to the vendor information screen toAppendix UUDate to Vendorallow a vendor to enter the date at which theInformation Screenvendor will become unavailable. 7.2BBAdd Unavailable EndAdd a field to the vendor information screen toAppendix UUDate to Vendorallow a vendor to enter the date at which theInformation Screenvendor will become available. 7.2CCUnavailable Date End -The Unavailable End Date must be after theAppendix UURuleUnavailable Start Date. 8.0Update QualitativeUpdate the Qualitative Distribution SetupAppendix VVDistribution SetupScreen to allow users to use different criteriaScreenfor vendor selection than in the currentproduction environment. 8.1Add Lowest PriceAdd an option for the Lowest Price as aAppendix VVparameter todistribution parameter.Qualitative Distributionscreen 8.2Add Highest ServiceAdd an option for the Highest Service ScoreAppendix VVScore parameter toas a distribution parameter.Qualitative Distributionscreen 8.3Add Highest QualityAdd an option for the Highest Quality Score asAppendix VVScore parameter toa distribution parameter.Qualitative Distributionscreen 8.4Add HighestAdd an option for the Highest CumulativeAppendix VVCumulative ScoreScore as a distribution parameter.parameter toQualitative Distributionscreen 8.0Add Valuation ProductReview element to allORA valuationproducts. 8.0AAdd Valuation ProductAdd option to select a Valuation ProductReview element toReview to Ocwen BPO productOcwen BPO product 8.0BAdd Valuation ProductAdd option to select a Valuation ProductReview element toReview to Ocwen Comparative MarketOcwen ComparativeAnalysis productMarket Analysis 8.0CAdd Valuation ProductAdd option to select a Valuation ProductReview element toReview to ORA 2055 productORA 2055 8.0DAdd Valuation ProductAdd option to select a Valuation ProductReview element toReview to ORA 1004 product. (This productORA 1004does not exist yet. An RDD is forthcoming). 8.1Create ValuationProduct ReviewElement Fulfillment 8.1ACreate ValuationCreate the Data Entry Valuation ProductProduct ReviewReview element fulfillment form to enter theelement fulfillmentdata needed for a Valuation Product Review. 8.1BValuation ProductValuation Product Review will not beReview - Rule 1forwarded to vendor it will only be available torequestor/forwarder. 8.1CValuation ProductCompleted order is not available toReview - Rule 2requestor/forwarder until Valuation ProductReview status changes to ConfirmedComplete. 8.1DAdd Market Value LowAdd the Market Value Low field to thefield to ValuationValuation Product Review Element Fulfillment.Product ReviewThis field should be formatted as currency.Element Fulfillment 8.1EAdd Market Value HighAdd the Market Value High field to thefield to ValuationValuation Product Review Element Fulfillment.Product ReviewThis field should be formatted as currency.Element Fulfillment 8.FIAdd Market Value MidAdd the Market Value Mid field to thefield to ValuationValuation Product Review Element Fulfillment.Product ReviewThis field should be formatted as currency.Element Fulfillment 8.1F1Review ElementThe Market Value Mid should not populate ifFulfillment - Marketthe Market Value High is nullValue Mid field Rule 1 8.1F2Review ElementThe Market Value Mid should not populate ifFulfillment - Marketthe Market Value Low is nullValue Mid field Rule 2 8.1F3Review ElementThe Market Value Mid calculation method isFulfillment - Market(Market Value High + Market Value Low)/2Value Mid fieldcalculation 8.1GAdd Repaired MarketAdd the Repaired Market Value Low field toValue Low field tothe Valuation Product Review ElementValuation ProductFulfillment. This field should be formatted asReview Elementcurrency.Fulfillment 8.1HAdd Repaired MarketAdd the Repaired Market Value High field toValue High field tothe Valuation Product Review ElementValuation ProductFulfillment. This field should be formatted asReview Elementcurrency.Fulfillment 8.1IAdd Repaired MarketAdd the Repaired Market Value Mid field toValue Mid field tothe Valuation Product Review ElementValuation ProductFulfillment. This field should be formatted asReview Elementcurrency.Fulfillment 8.1I1Review ElementThe Market Value Mid should not populate ifFulfillment - Repairedthe Repaired Market Value High is nullMarket Value Mid fieldRule 1 8.1I2Review ElementThe Repaired Market Value Mid should notFulfillment - Repairedpopulate if the Repaired Market Value Low isMarket Value Mid fieldnullRule 2 8.1I3Review ElementThe Repaired Market Value Mid calculationFulfillment - Repairedmethod is (Repaired Market Value High + RepairedMarket Value Mid fieldMarket Value Low)/2calculation 8.1JAdd DeferredAdd the Total Repair Amount Field to theMaintenance field toValuation Product Review Element Fulfillment.Valuation ProductThis field should be formatted as currency.Review ElementFulfillment 8.1KAdd Marketing TimeAdd the Marketing Time Field to the Valuationfield to ValuationProduct Review Element Fulfillment. This fieldProduct Reviewshould be formatted as Number (Double).Element Fulfillment 8.1LAdd Review CommentAdd the Review Comment Field to thefield to ValuationValuation Product Review Element Fulfillment.Product ReviewThis field should be formatted as Memo.Element Fulfillment 8.1MAdd Reason Code fieldAdd the Reason Code Field to the Valuationto Valuation ProductProduct Review Element Fulfillment. This fieldReview Elementshould be formatted as Text (50).Fulfillment 8.1KM1Add Reason CodeAdd a combo box to specify the Reason Codecombo box field toField on the Valuation Product ReviewValuation ProductElement Fulfillment. The combo box shouldReview Elementcontain the following values:FulfillmentDrivebyBad previous valueCondemnedDriveby on wrong propertyDeferred MaintenanceEarthquakeFireFloodFunctional ObsolescenceIncorrect Prop Rights ValuedMarket DeclineMarket IncreaseMudslideNo Change In ValueNo Original (Previous) ValueGo RepairedSight Area IncorrectStructural ProblemsTornadoVandalizedDoes Not Comply With Zoning 8.1NAdd Condition Codefield to ValuationProduct ReviewElement Fulfillment 8.1OAdd Condition CodeAdd the Condition Code Field to the Valuationfield to ValuationProduct Review Element Fulfillment. This fieldProduct Reviewshould be formatted as Text (10).Element Fulfillment 8.1O1Add Condition CodeAdd a combo box to specify the Conditioncombo box field toCode Field on the Valuation Product ReviewValuation ProductElement Fulfillment. The combo box shouldReview Elementcontain the following values:FulfillmentPoorFairAverageGood 8.1PCreate Valuation OrderTable 8.1P1Valuation Order Table -Links will be created for all other valuationAdd Link to Valuationproducts associated to the file number of theProductorder the review is selected for. 8.1P2Valuation Order Table -Activating link will open a new windowLink Actiondisplaying the valuation product referenced bythe link. 8.1P2Valuation Order Table -This will show the Valuation Product Type ofAdd Valuation Typethe valuation product referenced by the link. 8.2P4Valuation Order Table -This will show the confirmed completed dateAdd Completed Dateof the valuation product referenced by the link. 9.0Create InvoiceCreate output file from REAL Trans databaseCreation Processfor upload into Infinium for Invoice creation. 9.1Create Infinium exportCreate file with all needed data for invoicefile creationcreation in Infinium. 9.2Create Infinium importCreate Infinium mapping process from filefile mappingcreated in Section (9.1) 9.0ACreate BusinessCreate basic business processes that performProcesses fora simple function. This will allow admin usersWorkflow Automationto select a business process that can occur forall files/orders that meet workflow criteria. 9.1ACreate Send MessageCreate a business process to send a messageAppendix WWBusiness Processusing the Message Center function. 9.1BSend MessageWhen the user selects the ‘Send MessageAppendix WWBusiness Process -Business Process’ from the Work Flow Setup2Actionscreen, a Process Parameter window shouldappear. 9.1CProcess ParameterThe Process Parameter window shouldAppendix WWWindowappear requiring the user to complete all fieldsfor the business process. 9.1DProcess ParameterThe number of parameters that are necessaryAppendix WWWindow - Parameterswill be determined by the process that is beingcreated. 9.1EParameter 1 - ‘To’The ‘To’ combo box should be the firstAppendix WWCombo Boxparameter required by the user that appearson the Process Parameter window. 9.1FParameter 1 - ValuesThe ‘To’ combo box should include theAppendix WWfollowing values:Vendor CompanyVendor ContactVendor Company and Vendor Contact 9.1GParameter 2 - ‘Subject’The ‘Subject’ field should be the secondAppendix WWfieldparameter required by the user that appearson the Process Parameter window. 9.1HParameter 2 - DetailsThe ‘Subject’ field should allow the user toAppendix WWenter a subject for all of the emails that will besent for the current workflow. 9.1IParameter 3 -The ‘Message’ field should be the thirdAppendix WW‘Message’ fieldparameter required by the user that appearson the Process Parameter window. 9.1JParameter 3 - Details 1The ‘Message’ field should allow the user toAppendix WWenter a message for all of the emails that willbe sent for the current workflow. 9.1KParameter 3 - Details 2The ‘Message’ field should also include theAppendix WWfollowing data points for all messages that aresent via a workflow:File NumberLoan NumberOrder NumberProperty Street AddressProperty CityProperty StateProperty Zip CodeProperty APNProperty Legal DescriptionBorrower NameOrder Due Date 9.2ACreate Cancel OrderCreate a business process to change theAppendix XXBusiness Processstatus to Cancelled for all orders for thecurrent workflow. 9.2BCancel Order BusinessWhen the user selects the ‘Cancel Order’ fromAppendix XXProcess - Actionthe WorkFlow Setup2 screen, a ProcessParameter window should appear. 9.2CProcess ParameterThe Process Parameter window shouldAppendix XXWindowappear requiring the user to complete all fieldsfor the business process. 9.2DParameter 1 - ‘Reason’The ‘Reason’ field should be the onlyAppendix XXfieldparameter required by the user that appearson the Process Parameter window. 9.2EParameter 1 - ValuesThe data entered in the ‘Reason’ field shouldAppendix XXpopulate the Cancellation Form. 9.2FCancel Order - Action 1When the order is cancelled via the workflow,Appendix XXthe cancellation form should appear undersubmitted items. 9.2GCancel Order - Action 2When the order is cancelled via the workflow,Appendix XXthe status should change to cancelled. 9.3ACreate Place OrderCreate a business process to place an orderAppendix YYBusiness Processusing AVS. 9.3BParameter 1 - ‘ProductThe ‘Product Category’ combo box should beAppendix YYCategory’ Combo Boxthe first parameter required by the user. 9.3CParameter 1 - ValuesThe ‘Product Category’ combo box shouldAppendix YYinclude only product categories that therequestor has selected as products to beordered. 9.3DParameter 2 - ‘ProductThe ‘Product to Order’ combo box should beAppendix YYto Order’ Combo Boxthe second parameter required by the user. 9.3EParameter 2 - ValuesThe ‘Product to Order’ combo box shouldAppendix YYinclude only products that the requestor hasselected as products to be ordered. 9.3FPlace Order - ActionWhen the order is placed via workflow, theAppendix YYorder should be placed with the best vendorthat is selected using AVS rules. 9.4ACreate Cancel andCreate a business process to cancel an orderAppendix ZZReorder Businessand re-assign the order with a new vendorProcessusing AVS. 9.4BParameter 1 - ‘Reason’The ‘Reason’ field should be the firstAppendix ZZfieldparameter required by the user that appearson the Process Parameter window. 9.4CParameter 1 - ValuesThe data entered in the ‘Reason’ field shouldAppendix ZZpopulate the Cancellation Form. 9.4DParameter 2 - ‘DueThe ‘Due Date’ combo box should be theAppendix ZZDate’ Combo Boxsecond parameter required by the user thatappears on the Process Parameter window. 9.4EParameter 2 - ValuesThe ‘Due Date’ combo box should include theAppendix ZZfollowing values:Same as previous orderCalculate new due date 9.4FDue Date - Rule 1If ‘Same as previous order’ is selected fromAppendix ZZthe ‘Due Date’ combo box and the due datefor the previous order is not in the past, thenew order that is created should contain thesame due date as the previous order. 9.4GDue Date - Rule 2If ‘Same as previous order’ is selected fromAppendix ZZthe ‘Due Date’ combo box and the due datefor the previous order is in the past, the neworder that is created should contain the duedate based on a standard order time for theproduct. 9.4GDue Date - Rule 3If ‘Calculate new due date’ is selected fromAppendix ZZthe ‘Due Date’ combo box, the new order thatis created should contain the due date basedon a standard order time for the product. 9.4HCancel Order - Action 1When the order is cancelled via the workflow,Appendix ZZthe cancellation form should appear undersubmitted items. 9.4ICancel Order - Action 2When the order is cancelled via the workflow,Appendix ZZthe status should change to cancelled. 9.4JPlace Order - ActionWhen the order is placed via workflow, theAppendix ZZorder should be placed with the best vendorthat is selected using AVS rules.11.0Create VendorPayment Process11.1Create Infinium exportCreate file with all needed data for vendorfile creationpayment in Infinium.11.2Create Infinium importCreate Infinium mapping process from filefile mappingcreated in Section (11.1)12.0Create DelegateThis process will allow other members orProcessREAL Trans to place orders for the truerequestor through their account. This will beused solely with the portfolio managementupload process.12.1Add Delegate menuAdd Delegate menu item under theAppendix PPitem under theAdmin/More menu item. This will open theAdmin/more menu itemDelegate Creation Screen12.2Create ApprovedThis will allow members to approve otherDelegate Screenmembers as delegates.12.2ACreate ApprovedCreate Delegate Creation Screen.Appendix LLDelegates Table12.2A1Add Company toThis should show all members who have beenApproved Delegateapproved as delegates.Screen12.2A2Add Active Date toThis should show the date the delegate wasApproved Delegatesapproved.Screen12.2BAdd “Add” Button toThis button will open Approve DelegateApproved DelegatesScreen.Screen12.2CAdd “Delete” Button toAdd a button to delete the selected DelegateApproved Delegatesfrom the Approved Delegate list.Screen12.2C1Approved DelegatesIf a delegate has not been highlighted whenScreen - Delete Buttonthe Delete button is clicked, the SelectionRule 1Warning Pop up Box should appear (This iscreated in 12.2D3-12.2D5)12.2C2Approved DelegatesIf a delegate has been highlighted the DeleteScreen - Delete ButtonWarning Pop up Box should appear (This isRule 2created in 12.2D6-12.2D8)12.2C3Approved DelegatesProvide a warning message that appears if theScreen - Missing‘Delete’ button is clicked but there is noSelection WarningDelegate highlighted. The warning shouldMessageread “Please highlight the Delegate that youwould like to delete from the list above?”12.2C4Approved DelegatesProvide an ‘OK’ button on the warningScreen - Missingmessage. If the ‘OK’ button is clicked theSelection WarningApproved Delegates screen will appear.Message button - OK12.2C5Approved DelegatesProvide a warning message that appears if theScreen - Delete‘Delete’ button is clicked and there is aWarning MessageDelegate highlighted. The warning shouldread “Are you sure you want to Delete theDelegate?”12.2C6Approved DelegatesProvide an ‘OK’ button on the warningScreen - Deletemessage. If the ‘OK’ button is clicked allWarning Messagechanges will be lost and the Approvedbutton - OKDelegates screen will appear.12.2C7Approved DelegatesProvide a ‘Cancel’ button on the warningScreen - Deletemessage. If the ‘Cancel’ button is clicked theWarning Messagewarning message will close and the Approvedbutton - CancelDelegates screen will appear.12.2C8Approved DelegatesWhen the Delete button is clicked theScreen - Delete Button -highlighted Delegate should be removed fromActionthe list of Delegates.12.3Create ApproveThis will allow members to add members asAppendix MMDelegate Screendelegates.12.3ACreate ApproveCreate Approve Delegates Screen.Delegates Screen12.3BAdd Delegate ComboThis should be a list box showing all membersBox to Approvewho have been approved as delegates.Delegates Screen12.3B1Delegate Combo Box -The Delegate Combo box should contain allValuesapproved vendors.12.3CAdd “Add” button to theThis button will Add the Delegate selected inApprove Delegatesthe Approve Delegates Screen.Screen12.3DAdd “Add” Button toThis button will open Approve DelegatesDelegate CreationScreen.Screen12.3D1Approve DelegatesProvide a warning message that appears if theScreen - Missing'Add button is clicked but there is not aSelection WarningDelegate selected from the Delegate ComboMessageBox. The warning should read “Please selecta Delegate that you would like to add from thelist?”12.3D2Approve DelegatesProvide an ‘OK’ button on the warningScreen - Missingmessage. If the ‘OK’ button is clicked theSelection WarningApprove Delegates screen will appear.Message button - OK12.3D3Approve DelegatesWhen the Add button is clicked the selectedScreen - Add button -vendor should be added as a delegate.Action 12.3D4Approve DelegatesWhen the Add button is clicked the DelegateScreen - Add button -Creation Screen should appear.Action 212.4Enhance PortfolioEnhance the current Portfolio ManagementAppendix NNManagement Screenscreen to allow a vendor to select the owner ofa portfolio who has approved them as adelegate.12.4AAdd Owner Combo BoxAdd the Owner Combo Box to the Portfolioto PortfolioManagement screen.Management Screen12.4BOwner Combo Box -The Owner Combo Box should contain allValuesrequestors that have selected them as anapproved Delegate.13.0ACreate Today FunctionCreate a function to allow the user to enter akeyword “Today” to retrieve the system date.13.1ACreate Today FunctionWhen the keyword Today is entered, thesystem should use the current date forcalculating time lapses.Example: Current System Date - Jun. 5, 2003Today Function Results Today - 3 = Jun. 2, 200314.0ACreate View OnlyCreate View Only fulfillment form that displaysAppendix UUFulfillment Form withthe completed order fulfillment with thumbnailsThumbnailsfor all of the attached documents in a separateframe.14.1ACreate frame forThe View Only Fulfillment form should open infulfillment forma separate frame.14.2ACreate Thumbnails forCreate thumbnails for all documents that haveall attached documentsbeen attached.14.3AAdd Thumbnails toDisplay thumbnails for all attached documentsFrame for Fulfillmentin frame with View Only Fulfillment form.Form14.4AFrame for FulfillmentThe Frame and thumbnails should be createdFormfor all of the products listed below:Ocwen CMAOcwen BPO15.0AModify AttachModify the Attach document screen to requireAppendix VVDocument Screenthe vendor to select the document type from acombo box instead of using free form textfields.15.1A1Add Document TypeAdd a combo box to allow the vendor to selectCombo Boxthe type of document being attached from astandardized list of documents.15.1A2Document TypeThe Document Type Combo box shouldCombo Box - Valuescontain the following values:Subject PhotoSales Comp 1 PhotoSales Comp 2 PhotoSales Comp 3 PhotoListing Comp 1 PhotoListing Comp 2 PhotoListing Comp 3 PhotoOther15.1A3Document TypeThe user must select a value from theCombo Box - Rule 1Document Type Combo box before attachingany document.15.0BModify SubmittedModify the Submitted Documents screen toAppendix XXDocuments Screendisplay the Document type.15.0B1Add Document Type toAdd the Document Type to the SubmittedSubmitted DocumentsDocuments screen.Screen

Claims
  • 1. A method for electronically facilitating a transaction between a financial institution and an end user, the method comprising: receiving input specifying the transaction; identifying at least one sub-transaction associated with the transaction; and identifying a vendor for the at least one sub-transaction.
  • 2. The method of claim 1, wherein identifying the at least one sub-transaction occurs automatically.
  • 3. The method of claim 1, wherein identifying the at least one sub-transaction further comprises: a trigger event triggering identifying the at least one sub-transaction.
  • 4. The method of claim 3, wherein the trigger event comprises a received input specifying the transaction.
  • 5. The method of claim 3, wherein the trigger event comprises a completed second sub-transaction.
  • 6. The method of claim 3, wherein the trigger event comprises a third sub-transaction having a predetermined status.
  • 7. The method of claim 3, wherein the trigger event comprises a satisfied decision rule.
  • 8. The method of claim 7, wherein the decision rule is evaluated based on at least one selected from a group consisting of input specifying the transaction, a completed second sub-transaction, and a predetermined status of a third sub-transaction.
  • 9. The method of claim 1, wherein the at least one sub-transaction is identified as required or optional.
  • 10. The method of claim 9, further comprising: if the at least one sub-transaction is marked as optional, receiving input from the end user prior to identifying the vendor.
  • 11. The method of claim 1, wherein identifying a vendor further comprises: a trigger event triggering identifying a vendor.
  • 12. The method of claim 11, wherein the trigger event comprises a received input specifying the transaction.
  • 13. The method of claim 12, wherein the trigger event comprises a received input from the end user.
  • 14. The method of claim 11, wherein the trigger event comprises a second completed sub-transaction.
  • 15. The method of claim 11, wherein the trigger event comprises a third sub-transaction having a predetermined status.
  • 16. The method of claim 11, wherein the trigger event comprises a satisfied decision rule.
  • 17. The method of claim 16, wherein the decision rule is evaluated based on at least one selected from a group consisting of input specifying the transaction, a completed second sub-transaction, and a predetermined status of a third sub-transaction.
  • 18. The method of claim 1, further comprising: placing an order with the vendor to complete the sub-transaction.
  • 19. The method of claim 18, wherein placing the order comprises: a trigger event triggering placing the order.
  • 20. The method of claim 19, wherein the trigger event comprises a received input specifying the transaction.
  • 21. The method of claim 19, wherein the trigger event comprises a completed second sub-transaction.
  • 22. The method of claim 19, wherein the trigger event comprises a third sub-transaction having a predetermined status.
  • 23. The method of claim 19, wherein the trigger event comprises a satisfied decision rule.
  • 24. The method of claim 23, wherein the decision rule is evaluated based on at least one selected from a group consisting of input specifying the transaction, a completed second sub-transaction, and a predetermined status of a third sub-transaction.
  • 25. The method of claim 1, wherein the input specifying the transaction is received from the end user.
  • 26. The method of claim 1, wherein the vendor is automatically selected.
  • 27. The method of claim 1, wherein the vendor is manually selected.
  • 28. The method of claim 27, wherein the vendor is manually selected by the end user.
  • 29. The method of claim 1, further comprising: obtaining at least one vendor metric.
  • 30. The method of claim 29, wherein the at least one vendor metric includes one selected from a group consisting of vendor capacity, vendor threshold, and vendor late-order ratio.
  • 31. The method of claim 29, wherein obtaining the at least one vendor metric comprises: calculating the at least one vendor metric.
  • 32. The method of claim 29, wherein obtaining the at least one vendor metric comprises: receiving the at least one vendor metric from an outside source.
  • 33. The method of claim 29, wherein obtaining the at least one vendor metric comprises: receiving vendor data from an outside source.
  • 34. The method of claim 29, further comprising: displaying the at least one vendor metric.
  • 35. The method of claim 29, wherein the identified vendor is selected based on the at least one vendor metric.
  • 36. The method of claim 1, further comprising obtaining at least one vendor performance score.
  • 37. The method of claim 36, wherein the at least one vendor performance scorn includes one selected from a group consisting of vendor price, vendor turn-around time, vendor quality score, vendor overall score.
  • 38. The method of claim 36, wherein obtaining the at least one vendor performance score comprises: calculating the at least one vendor performance score.
  • 39. The method of claim 36, wherein obtaining the at least one vendor performance score comprises: receiving the at least one vendor performance score from an outside source.
  • 40. The method of claim 36, wherein obtaining the at least one vendor performance score comprises: receiving vendor data from an outside source.
  • 41. The method of claim 36, further comprising: displaying the at least one vendor performance score.
  • 42. The method of claim 36, wherein the identified vendor is selected based on the at least one vendor performance score.
  • 43. A system for electronically facilitating a transaction between a financial institution and an end user, comprising: means for receiving input specifying the transaction; means for identifying at least one sub-transaction associated with the transaction; and means for identifying a vendor for the at least one sub-transaction.
  • 44. A system for electronically facilitating a transaction between a financial institution and an end user, comprising: a processor; and a repository accessible by the processor; wherein input specifying the transaction is received and stored in the repository; wherein at least one sub-transaction associated with the transaction is identified via the processor; and wherein a vendor for the at least one sub-transaction is identified via the processor.
  • 45. The system of claim 44, wherein the processor is housed on a terminal.
  • 46. The system of claim 45, wherein the terminal is selected from a group consisting of a personal computer, a minicomputer, a main frame computer, a microcomputer, a hand held device, and a telephonic device.
  • 47. The system of claim 44, wherein the processor is housed on a server.
  • 48. The system of claim 47, wherein the server is selected from a group consisting of a personal computer, a minicomputer, a microcomputer, and a main frame computer.
  • 49. The system of claim 47, wherein the server is coupled to a network.
  • 50. The system of claim 49, wherein the input is received via the network.
  • 51. The system of claim 49, wherein the network is the Internet.
  • 52. The system of claim 49, wherein the server is coupled to the network via a coupling.
  • 53. The system of claim 52, wherein the coupling is selected from a group consisting of a wired connection, a wireless connection, and a fiberoptic connection.
  • 54. The system of claim 44, wherein the repository is housed on a server.
  • 55. The system of claim 54, wherein the server is coupled to a network.
  • 56. A computer program product comprising a computer usable medium having control logic stored therein for causing a computer to provide interactive assistance with performing a transaction between a financial institution and an end user, the control logic comprising: first computer readable program code means for receiving input specifying the transaction; second computer readable program code means for identifying at least one sub-transaction associated with the transaction; and third computer readable program code means for identifying a vendor for the at least one sub-transaction.
  • 57. A method for electronically facilitating a transaction between a financial institution and an end user, the method comprising: receiving an order from a user; receiving a sub-transaction from a user, the vendor sub-selecting identifying at least one sub-transaction associated with the order; receiving vendor criteria from a user; and selecting at least one vendor for the at least one sub-transaction;
  • 58. The method of claim 57, wherein the vendor criteria comprise: an indication that the at least one vendor is selected electronically.
  • 59. The method of claim 57, wherein the vendor criteria comprise: vendor criteria used to electronically select the at least one vendor.
  • 60. The method of claim 57, wherein the vendor criteria comprise: an indication that the at least one vendor is selected by the user.
  • 61. The method of claim 57, wherein the vendor criteria comprise: a request for vendor information to be presented to the user.
  • 62. A method for electronically facilitating ordering for a sub-transaction associated with a particular transaction, comprising: receiving parameters for a transaction from a user; selecting a transaction matching the input parameters; selecting at least one sub-transaction associated with the selected transaction; selecting at least one vendor for the at least one sub-transaction; and placing an order with the at least one vendor for the at least one sub-transaction.
  • 63. A method for electronically facilitating ordering for a sub-transaction associated with a particular transaction, comprising: receiving a product fulfillment indication from a vendor; selecting at least one sub-transaction; selecting at least one vendor for the at least one sub-transaction; and placing an order with the at least one vendor for the at least one sub-transaction.
  • 64. A method for providing online services between a vendor and a service recipient, the method comprising: receiving a transaction request; identifying a service concern associated with the transaction request; identifying a vendor capable of addressing the service concern; providing a request for the service concern to a vendor; and if the vendor agrees to address the service concern, receiving a transaction response, receiving a transaction response including: receiving at least one item of information relating to addressing the service concern.
  • 65. The method of claim 64, wherein the transaction request is a request for a loan for a real estate purchase.
  • 66. The method of claim 64, wherein the service concern is selected from a group consisting of determination of flood classification status, an inspection, a business process outsourcing, an appraisal, an automated valuation model, and a mortgage insurance policy.
  • 67. The method of claim 66, wherein the vendor is an entity providing a service selected from a group consisting of determining of flood classification status, providing an inspection, providing a business process outsourcing, providing an appraisal, providing an automated valuation model, and providing a mortgage insurance policy.
  • 68. The method of claim 64, further comprising: if the vendor agrees to address the service concern, receiving a confirmation of services provided.
  • 69. The method of claim 68, wherein the confirmation of services provided comprises: a result of services provided.
  • 70. The method of claim 69, wherein the result of services provided comprises one selected from the group consisting of flood classification status information, inspection status information, business process outsourcing information, appraisal information, automated valuation model information, and mortgage insurance policy information.
  • 71. The method of claim 68, further comprising: upon receiving the confirmation of services provided, generating a second service concern. The method of claim 1, wherein the vendor is automatically selected.
  • 72. The method of claim 64, wherein identifying the vendor comprises: receiving an input from a user, the input specifying the vendor.
  • 73. The method of claim 64, wherein identifying the vendor comprises: electronically selecting a vendor.
Parent Case Info

This application claims priority to applicants' copending U.S. Provisional Application Ser. No. 60/502,273 titled “METHOD AND SYSTEM FOR VENDOR MANAGEMENT” filed Sep. 12, 2003. The entirety of this patent application is incorporated herein by reference.

Provisional Applications (1)
Number Date Country
60502273 Sep 2003 US