US20100199279A1 - User connectivity process management system - Google Patents

User connectivity process management system Download PDF

Info

Publication number
US20100199279A1
US20100199279A1 US12/717,326 US71732610A US2010199279A1 US 20100199279 A1 US20100199279 A1 US 20100199279A1 US 71732610 A US71732610 A US 71732610A US 2010199279 A1 US2010199279 A1 US 2010199279A1
Authority
US
United States
Prior art keywords
task
client
computer
manual task
tasks
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/717,326
Inventor
John Connolly
Premila Vekaria
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US12/717,326 priority Critical patent/US20100199279A1/en
Publication of US20100199279A1 publication Critical patent/US20100199279A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806Task transfer initiation or dispatching
    • G06F9/4843Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/085Payment architectures involving remote charge determination or related payment systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Definitions

  • This invention relates to a user connectivity process management system.
  • this invention relates to a system for managing the process of providing users with direct market access for the trading of financial instruments.
  • Today's technology is capable of providing direct access to markets, allowing users to trade financial instruments on their own from almost any location. Access to this technology is highly demanded, and, therefore, it is important to quickly and efficiently provide such access to users.
  • providing users with access to systems that provide direct market access is very complicated, requiring numerable steps. Conventionally, these steps have been manually managed and performed, taking up to six or more months to complete the task of providing direct market access to users. With the high state of demand for direct market access, such delays of six or more months are unacceptable.
  • the secured service is a computer system that allows the client to trade financial instruments.
  • the process management system according to the present invention includes managing execution of tasks that can be automatically executed; delegating tasks that require manual execution; communicating with entities outside of the process management system; and handling “demands,” or unexpected problems that arise in the middle of the client connectivity process.
  • the client connectivity process includes a series of tasks, both automatic and manual.
  • the automatic tasks are executed by either the process management system or other computers automatically.
  • the manual tasks are executed by individuals who interface with the process management system via a user-interface disclosed herein.
  • the process management system advances through the client connectivity process by instructing the pertinent computers to automatically execute the automatic tasks and sending messages to the individuals responsible for executing the manual tasks.
  • the individuals responsible for executing the manual tasks access the user-interface via a computer and view such messages in their “activity” list.
  • the process management system is notified that the manual task is complete also via the interface.
  • the process management system advances to the next task in the client connectivity process.
  • the system also interfaces with these external entities. For instance, the system sends messages to the client regarding connection information required to connect to the secured service, and sends requests to third party networks to initiate client connectivity through such networks, if necessary.
  • the process management system handles “demands,” or unexpected problems that arise in the middle of the client connectivity process.
  • a problem occurs during the process, an individual enters such problem, or demand, into the system via the user-interface.
  • the process management system takes this demand and inserts additional required tasks into the client connectivity process flow. These additional tasks are then delegated to the computers and or individuals for execution as necessary.
  • FIG. 1 illustrates an exemplary computer hardware arrangement according to an aspect of the present invention
  • FIGS. 2 and 3 illustrate icons used to describe tasks in the process flows according to the exemplary embodiment of the invention
  • FIG. 4 illustrates a high level view of the client connect process flow according to the exemplary embodiment
  • FIG. 5 illustrates the initiation process flow shown in FIG. 4 ;
  • FIGS. 6 and 7 illustrate the environment set-up process flow shown in FIG. 4 ;
  • FIG. 8 illustrates the user acceptance testing process flow shown in FIG. 4 ;
  • FIG. 9 illustrates the production environment set-up process flow shown in FIG. 4 ;
  • FIG. 10 illustrates the go-live process flow shown in FIG. 4 ;
  • FIG. 11 illustrates a “Regions” or “Home” page of a user-interface according to the exemplary embodiment of the present invention
  • FIG. 12 illustrates a portion of a client page of the user-interface relating to a “General” tab
  • FIG. 13 illustrates a portion of a client page of the user-interface relating to a “UAT” tab
  • FIG. 14 illustrates a portion of a client page of the user-interface relating to a “Production” tab
  • FIG. 15 illustrates a portion of a client page of the user-interface relating to a “Connection” tab
  • FIG. 16 illustrates a portion of a client page of the user-interface relating to a “FIX Message” tab
  • FIG. 17 illustrates a portion of a client page of the user-interface relating to a “Markets” tab
  • FIG. 18 illustrates a portion of a client page of the user-interface relating to a “Normalizer” tab
  • FIG. 19 illustrates a portion of a client page of the user-interface relating to a “Demands” tab
  • FIG. 20 illustrates a portion of a client page of the user-interface relating to a “Progress” tab
  • FIG. 21 illustrates a portion of a client page of the user-interface relating to a “Activity” tab
  • FIG. 22 illustrates a “Client Tests” page of the user-interface, which is accessed from the page of FIG. 12 ;
  • FIG. 23 illustrates a “Test Details” page of the user-interface, which is accessed from the page of FIG. 22 ;
  • FIG. 24 illustrates a “Demands” page of the user-interface, which is accessed from the page of FIG. 11 ;
  • FIG. 25 illustrates a “Creating a Demand” page of the user-interface, which is accessed from the page of FIG. 24 ;
  • FIG. 26 illustrates a “Demand Raised” business process map that relates to creating a demand as described with reference to FIG. 25 ;
  • FIG. 27 illustrates a “Normalizer” page of the user-interface, which is accessed from the page of FIG. 11 ;
  • FIG. 28 illustrates a “Creating a Normalizer” page of the user-interface, which is accessed from the page of FIG. 27 ;
  • FIG. 29 illustrates a “Work Queue” page of the user-interface, which is accessed from the page of FIG. 11 ;
  • FIG. 30 illustrates a “Client Monitor” page of the user-interface, which is accessed from the page of FIG. 11 .
  • the process management system 100 includes the “client connectivity” system 101 , the “active workflow” system 102 , and the database 103 .
  • the client connectivity system 101 includes one or more computers that gather information pertaining to the client connectivity process, such as client information, demands, manual task work queues, connection information, etc. . . . , and store such information in the database 103 .
  • the active workflow system 102 includes one or more computers that manage advancement through the client connectivity process. Accordingly, the active workflow system 102 communicates with the client connectivity system 101 to exchange demand information and manual task queues.
  • the client connectivity system 101 passes them on to the active workflow system 102 , and the workflow system 102 adjusts the task flow in the client connectivity process accordingly. It should be noted that although the active workflow system 102 and the client connectivity system 101 are shown separate, they may reside on a single computer.
  • the active workflow 102 also manages communication with entities external to the process management system. Such entities include one or more computers 104 belonging to what is referred to herein as the “on-boarding team.”
  • the “on-boarding team” represents one or more individuals responsible for executing manual tasks in the client connectivity process.
  • the computers 104 of the on-boarding team operate the user-interface disclosed herein.
  • the active workflow system 102 notifies a computer belonging to one or more individuals on the on-boarding team 104 responsible for executing such tasks.
  • the notified individuals view the task via the user-interface, execute the task, and then notify the active workflow system 102 of its completion via the user-interface. Once complete, the workflow system 102 proceeds to the next task in the process.
  • Other external entities include clients 105 that desire to obtain access to the secured service (not shown).
  • the workflow 102 communicates with the client 105 , notifying the client of demands, status updates, and connection information.
  • External entities also include individuals 106 , referred to herein as the “Firewall Change Request team,” or “FCR team,” responsible for updating the secured service's firewall to accommodate the client 105 .
  • the active workflow system 102 will send a message to the FCR team when the manual task of updating the firewall is ready for execution.
  • External entities include individuals 107 , referred to herein as the “Logical Virtual Connection team,” or “LVC team,” responsible for establishing a Logical Virtual Connection required by some third party networks, if necessary.
  • the workflow system 102 will send a message to the LVC team if and when establishment of an LVC is required.
  • external entities include Autex 108 , which is an exemplary third party network provider that some clients 105 may use.
  • the worfkflow system 102 will send requests to Autex 108 , or other third party network providers, if any, when establishment of a connection between the client 105 , the third party network, and the secured service is required.
  • FIGS. 2 and 3 illustrate the symbols used to describe particular tasks in the CC process. These symbols appear next to the tasks described in FIGS. 4-10 and 26 .
  • “Ordinary Activity” icon 201 denotes a default task type that is executed manually. Tasks of this default type are normally carried out by specified useable resources.
  • “Script Activity” 202 denotes a task that executes a series of instructions in a given language consecutively. Specified usable resources execute these script tasks either automatically or manually.
  • “COM Activity” icon 203 denotes a task that calls a COM object, known in the art, and can be executed automatically or manually by specified resources.
  • Transport Activity denotes a task that calls a combination of one or more COM objects and is always executed automatically.
  • .NET Activity icon 205 denotes a task that calls a .NET object. Tasks of this type can be executed automatically or manually by specified resources.
  • Web Service Activity denotes a web service task that calls a specific URL and can be executed either automatically or manually by specified usable resources.
  • Create New Job Type Activity 207 denotes a task that allows the creation of and insertion of a new task into the CC process. This task type incorporates flexibility into the CC process by allowing unanticipated issues, such as demands, to be addressed on the fly. Create New Job tasks 207 can be executed automatically or manually by specified resources.
  • Sttate Activity Icon 208 denotes an “Ordinary” type activity 201 that has no specified resources.
  • “Static Useable Resource Only” icon 301 denotes a task that is executed manually by a static resource.
  • a static resource is defined at design time and cannot be changed at run-time.
  • “Dynamic Useable Resource Only” icon 302 denotes a task that is executed manually by dynamically defined resources that can be changed at run-time.
  • “Dynamic and Static Useable Resource” icon 303 denotes a task that is executed manually by static and dynamic resources.
  • “Same as Previous Resource” icon 304 denotes a task that is executed manually by resources that have carried out a selected previous task. Icons 301 - 304 can appear in conjunction with any task type, with the exception of “Transactional” activities 204 .
  • “Automatic” icon 305 denotes a task that is executed automatically by the system. This icon may appear in conjunction with “Script” 202 , “COM” 203 , and “Create New Job” 207 type tasks, and always appears in conjunction with a “Transactional” activity 204 .
  • “Library Activity” icon 306 denotes a shared task. Library activities can be used across different subprocesses of the CC process. This icon can appear in conjunction with any activity type.
  • the workflow system 102 instructs automatic execution of the automatic tasks described by the icons in FIGS. 2 and 3 .
  • the workflow system 102 When manual tasks arise in the CC process, the workflow system 102 notifies the appropriate individual(s) 104 , 106 , and/or 107 via the user interface to execute such tasks.
  • the workflow system 102 is notified of completion of the manual tasks via the user interface and then advances the CC process to the next task.
  • FIG. 4 represents a high level view of the entire CC process according to the exemplary embodiment of the present invention.
  • the process flow of FIG. 4 is referred to as the “main process.”
  • the main process includes five subprocesses: Initiation 401 , described with FIG. 5 ; Environment Set-Up 402 , described with FIGS. 6 and 7 ; User Acceptance Testing (“UAT”) Testing 403 , described with FIG. 8 ; Production Environment Set-Up 404 , described with FIG. 9 ; and Go Live 405 , described with FIG. 10 .
  • email addresses associated with individuals involved with the CC process may be obtained at 406 .
  • the first subprocess of FIG. 4 is initiation 401 , which will now be described in detail with reference to FIG. 5 .
  • the initiation process 401 includes tasks focusing on obtaining information necessary to begin the CC process, such as general client information 501 , protocol information, such as information required to comply with the FIX protocol 502 and 504 , and connection information about the client 503 .
  • the FIX protocol is the Financial Information eXchange (FIX) protocol, which is a messaging standard developed specifically for the real-time electronic exchange of securities transactions as is known in the art.
  • FIX Financial Information eXchange
  • the tasks 501 - 504 are manually performed by individuals on the on-boarding team 104 using the user-interface described below.
  • the active workflow system 102 delegates manual tasks, such as these, by sending notifications to the responsible individuals on the on-boarding team 104 , via the user-interface.
  • the workflow system 102 waits for an indication that the manual tasks are complete before proceeding to the next task.
  • the information input at 501 , 502 , 503 , and 504 is described with reference to FIGS. 12 , 13 , 15 , and 16 , respectively.
  • each of the subprocesses of FIG. 4 include a subprocess of resolving outstanding demands.
  • this subprocess occurs at 505 .
  • an individual on the on-boarding team 104 raises a demand via the user interface described below with reference to FIGS. 24-26 .
  • tasks required to resolve the demand are delegated to the appropriate individuals on the on-boarding team 104 for execution. Once the tasks are complete and the demand resolved, the CC process exits the demand subprocess at 505 .
  • the initiation process 401 also includes status update tasks and some other preliminary tasks.
  • the initiation process 401 includes updating a status of the CC process to indicate that the initiation process 401 is being executed at 506 .
  • an overall percentage complete of the CC process is updated periodically when certain tasks are completed, as shown at 509 , for example.
  • the client is added to a mapping table at 507 stored in the database 103 that includes a list of all clients involved in the CC process.
  • the initiation process 401 includes adding a set of tests at 508 to the database 103 that must be performed to ensure proper connectivity for the client. Client tests are described in more detail with respect to FIGS. 22 and 23 .
  • the environment set-up process 402 begins, which is shown with FIGS. 6 and 7 .
  • the environment set-up process 402 prepares the appropriate connection parameters, accounts, and third party networks for connection between the secured service and the client.
  • the preparations made in the environment set-up process 402 are a prelude for testing the connection to the client, which is described below with reference to User Acceptance Testing and FIG. 8 .
  • the tasks involved in the environment set-up process 402 include setting up the client for access to the Global Trading Workstation (“GTW”), which is a platform by which the client will trade financial instruments, and setting up FIX gateway routing and associated account information at 601 .
  • GTW Global Trading Workstation
  • the tasks at 602 represent recording additional parameters required for the client to seamlessly communicate via the FIX protocol, such as normalizers discussed below with reference to FIGS. 27 and 28 .
  • the tasks at 603 pertain to updating the secured service's firewall to accommodate the client. Such tasks include sending a notification to the FCR team 106 requesting that the firewall be adjusted, receiving a notification from the FCR team 106 that this manual task has been completed, and recording the updated port information associated with the firewall change.
  • the tasks at 701 and 702 pertain to acquiring a test date at which the client will be able to perform its User Acceptance Testing to test its connection to the secured service.
  • a test date is acquired, such information is sent to the client 105 via a message from the active workflow system 102 , as shown at 701 .
  • members of the on-boarding team 104 are notified of the test date and associated information via a message from the active workflow system 102 , as shown at 702 .
  • these members of the on-boarding team 104 are referred to as the “CC Infrastructure” team.
  • the tasks at 703 determine whether the client uses TNS, which is an exemplary third party network that requires use of a “Logical Virtual Connection.” If the client 105 uses TNS, a message is sent to the LVC team 107 by the active workflow system 102 notifying them of their responsibility to complete the manual task of setting up an LVC.
  • TNS is an exemplary third party network that requires use of a “Logical Virtual Connection.”
  • the tasks at 704 determine whether the client uses Autex, another exemplary third party network. If so, a message is prepared and sent to the third party network provider, in this example, Autex 108 , by the workflow system 102 . The message requests the third party network provider to adjust their system to allow connectivity between the client 105 and the secured service.
  • the tasks at 705 pertain to preparation of a test plan, which is a manual task, for use in the user acceptance testing (“UAT”) process.
  • the client 105 is sent a message at 604 containing the connection information required for the client to connect to secured service for UAT.
  • outstanding demands are resolved prior to proceeding to such testing.
  • the UAT testing process 403 includes preparation of logging functionality 801 to log errors in the testing process and performing internal testing 802 of client tests identified at 508 in FIG. 5 and according to the test plan of 705 in FIG. 7 .
  • UAT also includes establishing a connection with the client 105 at 803 so that the client can perform its user acceptance testing to ensure that the connection works properly.
  • the LVC is established to such network at 804 .
  • the third party provider of the INS network is notified of such connection at 805 .
  • outstanding demands are resolved and the status of the process is updated at 806 .
  • the CC process advances to production environment set-up 404 , shown in detail in FIG. 9 .
  • the environment set-up process involves compiling final port information 901 and protocol interface information 902 , and preparing the applications necessary to allow the client 105 access to the secured service 903 .
  • such applications include the global trading workstation which uses the FIX protocol and allows the client 105 direct market access to trading financial instruments.
  • the environment set-up process 404 also includes tasks that notify appropriate individuals at 904 on the on-boarding team 104 of the client's impending live connection to the secured service.
  • the individuals that are notified are referred to as the “production client connectivity” team, or “PROD CC,” and the “client connectivity infrastructure” team, or “CC Infrastructure.”
  • PROD CC production client connectivity team
  • CC Infrastructure client connectivity infrastructure
  • the “Go-Live” process 405 is executed, as shown in detail with FIG. 10 .
  • This process includes tasks pertaining to testing the live connection to the client, such as executing a dummy live trade 1001 , and receiving approval from the appropriate individuals to allow the client 105 access to the secured service. Such approval is shown at 1002 , and includes approval from legal personnel, front office personnel, and operators. Once approval is received, a message is sent to all involved parties, including the client 105 , indicating that the client now has access to the secured service at 1003 , thereby completing the CC process.
  • the exemplary user interface for interacting with the process management system 100 will now be described.
  • the exemplary user interface is operated by computers associated with individuals on the on-boarding team 104 , the FCR team 106 , and the LVC team 107 .
  • this user interface may also be operated by the client 105 , Autex 108 , and any other individual or entity interested in the CC process.
  • Access to the process management system 100 via the interface is controlled using user names, passwords, and a series of user types having varying levels of access rights to the process management system 100 .
  • a particular user may be associated with an “admin” user type and have complete read and write access to the process management system 100 .
  • the client 105 may be associated with a user type that has read-only access.
  • Members of the on-boarding team 104 may be associated with an intermediate user type having limited write access and full read access.
  • a home page shown at FIG. 11 is displayed.
  • the home page includes a navigation bar 1101 having links that, when selected, take the user to another page and/or perform an action.
  • the “Admin” link 1102 displays a “User Configuration” page where an admin can add users to or remove users from the user-interface, or modify the user types associated with users.
  • the “Log In” link 1103 displays a “Login” page where the user, or another user, may log in.
  • the “Home” link 1206 brings the user to the home page, which is currently being described with reference to FIG. 11 .
  • the “Client” link 1105 displays the “Client” page illustrated at FIGS. 12-23 .
  • the “Demands” link 1106 brings the user to a “Demands” page illustrated at FIGS. 24-25 .
  • the “Normalizer” link 1107 displays a “Normalizer” page illustrated at FIGS. 27-28 .
  • the “Vendor” link 1108 displays a “Vendor” page where the user can add, remove, or modify vendor information.
  • the “Work queue” link 1109 brings the user to a “Work queue” page illustrated at FIG. 29
  • the “Reports” link 1110 displays a “Reports” page where the user can run reports displaying information pertaining to the CC process.
  • the “Client Search” link 1111 displays a “Client Search” page where the user can search for particular clients.
  • the “Monitor” link 1112 displays a “Client Monitor” page illustrated at FIG. 30 .
  • the “Log Off” link 1113 logs the user off of the user-interface.
  • the “Client” page accessed by link 1105 , will now be described with reference to FIGS. 12-23 .
  • the “Client” page is used to set up clients or display information relating to clients.
  • the Client page includes several subpages which can be accessed by clicking on tabs 1200 at the top of the Client page ( FIG. 12 ).
  • the user inputs the information required on each of these subpages and then click on a “Submit” button ( 1201 , for example).
  • the client information is sent to the project management system 100 via the client connectivity system 101 . If all of the necessary information has been entered, the new client is created and a new client connect process is initiated for that client ( FIG. 4 ).
  • the “General” tab 1202 displays a form containing general client information, such as company identifiers for the client 1203 , client contact information 1204 , other contact information 1205 , client status information 1206 , and key event dates pertaining to the CC process 1207 .
  • the task of inputting this information is shown at 501 in FIG. 5 .
  • the UAT tab 1301 provides information relating to the FIX details associated with the client at issue for use in the User Acceptance Testing environment. These details describe parameters of the client's system to facilitate communication using the FIX protocol. The task of inputting this information is shown at 502 in FIG. 5 .
  • the “Production” tab 1401 will now be described with reference to FIG. 14 .
  • This tab provides the same information as the UAT Tab 1301 , except that the information in the “Production” tab 1501 relates to the production environment.
  • FIG. 15 illustrates the “Connection” tab 1501 .
  • the connection tab 1501 provides information relating to the client's communication connection, such as IP addresses 1502 , network connection types 1503 , ports 1504 , and encryption types 1505 . This information is input at 503 in FIG. 5 .
  • FIG. 16 illustrates the “FIX Message” tab 1601 that provides information relating to the particular parameters associated with the client's FIX message usage when conducting trades, such as session layer information 1602 , session and application exceptions 1603 , order status 1604 , order types 1605 , and currency 1606 .
  • FIG. 17 illustrates the “Markets” tab 1701 , which allows the user to select, among other things, trading regions 1702 where the client will be trading financial instruments via the secured service.
  • Exemplary regions include EMEA (i.e., Europe, the Middle East, and Asia), the United States, Latin America, Japan, Hong Kong, and Australia.
  • the notes tab 1703 allows the user to enter any miscellaneous information regarding the CC process. Also from the notes tab 1703 , the user can set up reminders that prompt the workflow system 102 to send messages to particular users of the user interface at particular times.
  • FIG. 18 illustrates the “Normalizer” tab 1801 , that when selected, displays a form pertaining to message translations. Because the client's system may not communicate in the same manner that the secured service communicates, messages from the client system to the secured service, and vice versa, may need to have translation functions applied to them.
  • the translation functions, or normalizers act as an interface between the client system 105 and the secured service allowing them to communicate with each other in a format understandable by both sides.
  • the form shown in FIG. 18 allows the user to view existing normalizers, which are listed in the window 1802 . Entry of new normalizers is discussed below with reference to FIGS. 27 and 28 .
  • FIG. 19 illustrates the “Demands” tab 1901 that, when selected, displays a form allowing the user to view a list of outstanding demands. Existing demands are displayed in row format in the window 1902 . The user can view more details of a particular demand by selecting an existing demand in the window and then selecting the “View Demand” button 1903 . Entry of new demands is discussed in more detail with reference to FIGS. 24-26 .
  • the two additional tabs are the “Progress” tab 2001 and the “Activity” tab 2101 .
  • the “Progress” tab 2001 when selected, displays the CC process flow ( FIGS. 4-10 ) and indicates the current status of the process by highlighting tasks that have been completed.
  • the “Activity” tab 2101 in FIG. 21 when selected, provides information about any manual tasks that have been assigned to the user by the workflow system 102 . For example, if the current user has been assigned the task “setup client in production GTW,” shown at 906 in FIG. 9 , such task is shown at 2102 in FIG. 22 informing the user that he or she is responsible for completing the task. Once the task is complete, the user selects the “Complete Activity” button 2103 . Selecting this button notifies the active workflow system 102 that the task is complete, so that processing can advance to the next task in the CC process, which in this example is “update percent complete” 907 in FIG. 9 .
  • the user interface pertaining to client tests will now be described. Referring back to FIG. 12 , when the “Client Tests” button 1208 is selected, the “Client Tests” dialog box illustrated in FIG. 22 is displayed.
  • the dialog box of FIG. 22 lists all of the existing Client Tests to be executed at 802 in FIG. 8 .
  • the tests are listed row-by-row in window 2201 .
  • Information displayed for each test includes a test identifier, a status of the test, such as “run” or “not run,” a run date and time, and the number of attempts that have been made to complete the test.
  • Test Details When the user selects one of the tests in the window 2201 , a “Test Details” form is displayed, as illustrated in FIG. 23 .
  • the user may view and/or edit test details including a description of the test 2301 , the tasks involved in completing the tests and their order of execution 2302 , result details 2303 , number of attempts made 2304 , and whether the test passed or failed 2305 .
  • the demands page is accessed by selecting the “demands” link 1106 ( FIG. 11 ) from the navigation bar 1101 .
  • the demands page is illustrated with FIG. 24 , from which the user can view, create, edit, and delete demands. Existing demands are listed row-by-row in the window 2401 .
  • a demand may be deleted by selecting a demand and then selecting the “Delete Demand” button 2402 .
  • a demand may be edited by selecting a demand and then selecting the “Edit Demand” button 2403 .
  • a demand may be created by selecting the “Create Demand” button 2404 .
  • the “Client Demand” page illustrated with FIG. 25 is displayed. If the “Edit Demand” button 2403 is selected, the “Client Demand” page is shown filled with the information pertaining to the selected demand. If the “Create Demand” button 2404 is selected, a new “Client Demand” page is displayed.
  • the “Client Demand” page is a form that allows the user to view and/or enter information about a demand, including a description of the demand 2501 , impacts of the demand 2502 , the demand priority 2503 , a status of the demand 2504 , manual workarounds 2505 , and clients affected by the demand 2506 .
  • the user may also attach documents 2507 to the demand.
  • the user selects the “Add/Save” button 2508 to complete the creation of the new demand or accept the changes made to an existing demand.
  • This subprocess notifies responsible individuals on the on-boarding team 104 , as shown at 2601 , obtains approval of the demand from particular individuals on the on-boarding team 104 , as shown at 2602 , and releases the demand at 2603 , when approved.
  • Release of the demand means that the workflow system 102 modifies the CC process to include the tasks associated with resolving the demand.
  • the manual tasks required to resolve the demand are delegated to the appropriate individuals on the on-boarding team 104 , FCR team 106 , or LVC team 107 as previously discussed.
  • the workflow system 102 ensures that these tasks have been completed when the demands outstanding subprocess occurs, such as at 505 in FIG. 5 .
  • the “Normalizer” page is accessible via the “Normalizer” link 1107 shown in FIG. 11 . Once this link is selected, the “Normalizer” page is displayed, which is illustrated with FIG. 27 .
  • the “Normalizer” page allows the user to view, edit, create, and delete normalizers.
  • a normalizer may be deleted by selecting a normalizer and then selecting the “Delete Normalizer” button 2702 .
  • a normalizer may be edited by selecting a normalizer and then selecting the “Edit Normalizer” button 2703 .
  • a normalizer may be created by selecting the “Create Normalizer” button 2704 .
  • the “Client Normalizer” page is displayed, which is illustrated with FIG. 28 .
  • the user may view and/or enter data pertaining to the normalizer including the name of the field that requires data translation 2801 , a FIX tag name of the affected field 2802 , the status of the normalizer 2803 , such as “build,” the actions involved in executing the normalizer 2804 , and the clients affected by the normalizer 2805 .
  • the user may select the “Add/Save” button 2806 to complete the changes. Any changes to the normalizers are recorded during the CC process, as shown for example, at 602 in FIG. 6 .
  • the “Work queue” page will be described, which is accessed via the “Work queue” link 1109 .
  • the “Work queue” page is illustrated with FIG. 29 . This page displays a list of activities that need to be completed for a particular client 105 . Contrary to the “Activity” tab described with reference to FIG. 21 , the “Work queue” page displays all outstanding manual tasks for a particular client, instead of just the tasks assigned to a particular user.
  • the user can take on an assigned activity by selecting button “Take Activity” 2901 , and/or can mark an activity as complete by selecting button “Complete Activity” 2902 .
  • work loads can be managed on the fly in a simple manner.
  • a user takes on someone else's task such task shows up on his or her “Activity” form ( FIG. 21 ).
  • the “Client Monitor” page displays all clients for the selected region and their status.
  • the information that is displayed for each client includes a color-coded status 3001 , a client name 3002 , a text based status 3003 , a percentage complete 3004 , and an expected CC process completion date 3005 .
  • the color-coded status 3001 can use any number of colors to represent any sort of status, the exemplary embodiment uses three colors to indicate three different statuses.
  • a first color 3006 indicates that the client connect process is in production without outstanding issues or demands.
  • a second color 3007 indicates that the process is in a subprocess other than production without issues or demands.
  • a third color 3008 indicates that there are outstanding issues or demands in the client connect process.
  • the first color is green
  • the second color is yellow
  • the third color is red.
  • the status field 3003 displays the client status that was discussed with respect to the process maps in FIGS. 4-10 ( 506 in FIG. 5 , for example.)
  • the percent complete field 3004 displays the percent complete that was also discussed with respect to FIGS. 4-10 ( 509 in FIG. 5 , for example.)

Abstract

A system is disclosed according to the present invention that manages the process of providing a client access to a secured service. In the exemplary embodiment, the secured service is a computer system that allows the client to trade financial instruments. Management of this process includes managing execution of tasks that can be automatically executed and delegating tasks that require manual execution; communicating with entities outside of the process management system; and handling “demands,” or unexpected problems that arise in the middle of the client connectivity process.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application claims benefit of expired U.S. Provisional Application No. 60/551,436 filed Mar. 9, 2004, and is a continuation application of U.S. patent application Ser. No. 10/888,923, filed Jul. 9, 2004. The entire disclosures of U.S. Provisional Patent Application No. 60/551,436 and U.S. patent application Ser. No. 10/888,923 are incorporated herein by reference.
  • FIELD OF THE INVENTION
  • This invention relates to a user connectivity process management system. In particular, this invention relates to a system for managing the process of providing users with direct market access for the trading of financial instruments.
  • BACKGROUND OF THE INVENTION
  • Today's technology is capable of providing direct access to markets, allowing users to trade financial instruments on their own from almost any location. Access to this technology is highly demanded, and, therefore, it is important to quickly and efficiently provide such access to users. However, providing users with access to systems that provide direct market access is very complicated, requiring numerable steps. Conventionally, these steps have been manually managed and performed, taking up to six or more months to complete the task of providing direct market access to users. With the high state of demand for direct market access, such delays of six or more months are unacceptable.
  • SUMMARY OF THE INVENTION
  • These problems are solved and a technical advance is achieved in the art by a system according to the present invention that manages the process of providing a client access to a secured service, referred to herein as the “client connectivity” process or the “CC” process. In the exemplary embodiment, the secured service is a computer system that allows the client to trade financial instruments. The process management system according to the present invention includes managing execution of tasks that can be automatically executed; delegating tasks that require manual execution; communicating with entities outside of the process management system; and handling “demands,” or unexpected problems that arise in the middle of the client connectivity process.
  • To elaborate, the client connectivity process includes a series of tasks, both automatic and manual. The automatic tasks are executed by either the process management system or other computers automatically. The manual tasks are executed by individuals who interface with the process management system via a user-interface disclosed herein. The process management system advances through the client connectivity process by instructing the pertinent computers to automatically execute the automatic tasks and sending messages to the individuals responsible for executing the manual tasks. The individuals responsible for executing the manual tasks access the user-interface via a computer and view such messages in their “activity” list. When the individual completes a manual task, the process management system is notified that the manual task is complete also via the interface. Once a manual task is complete, the process management system advances to the next task in the client connectivity process.
  • As the client connectivity process depends upon entities external to the process management system, such as the client and third party network providers, the system also interfaces with these external entities. For instance, the system sends messages to the client regarding connection information required to connect to the secured service, and sends requests to third party networks to initiate client connectivity through such networks, if necessary.
  • Further, the process management system according to the present invention handles “demands,” or unexpected problems that arise in the middle of the client connectivity process. In particular, if a problem occurs during the process, an individual enters such problem, or demand, into the system via the user-interface. The process management system takes this demand and inserts additional required tasks into the client connectivity process flow. These additional tasks are then delegated to the computers and or individuals for execution as necessary.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • A more complete understanding of this invention may be obtained from a consideration of this specification taken in conjunction with the drawings, in which:
  • FIG. 1 illustrates an exemplary computer hardware arrangement according to an aspect of the present invention;
  • FIGS. 2 and 3 illustrate icons used to describe tasks in the process flows according to the exemplary embodiment of the invention;
  • FIG. 4 illustrates a high level view of the client connect process flow according to the exemplary embodiment;
  • FIG. 5 illustrates the initiation process flow shown in FIG. 4;
  • FIGS. 6 and 7 illustrate the environment set-up process flow shown in FIG. 4;
  • FIG. 8 illustrates the user acceptance testing process flow shown in FIG. 4;
  • FIG. 9 illustrates the production environment set-up process flow shown in FIG. 4;
  • FIG. 10 illustrates the go-live process flow shown in FIG. 4;
  • FIG. 11 illustrates a “Regions” or “Home” page of a user-interface according to the exemplary embodiment of the present invention;
  • FIG. 12 illustrates a portion of a client page of the user-interface relating to a “General” tab;
  • FIG. 13 illustrates a portion of a client page of the user-interface relating to a “UAT” tab;
  • FIG. 14 illustrates a portion of a client page of the user-interface relating to a “Production” tab;
  • FIG. 15 illustrates a portion of a client page of the user-interface relating to a “Connection” tab;
  • FIG. 16 illustrates a portion of a client page of the user-interface relating to a “FIX Message” tab;
  • FIG. 17 illustrates a portion of a client page of the user-interface relating to a “Markets” tab;
  • FIG. 18 illustrates a portion of a client page of the user-interface relating to a “Normalizer” tab;
  • FIG. 19 illustrates a portion of a client page of the user-interface relating to a “Demands” tab;
  • FIG. 20 illustrates a portion of a client page of the user-interface relating to a “Progress” tab;
  • FIG. 21 illustrates a portion of a client page of the user-interface relating to a “Activity” tab;
  • FIG. 22 illustrates a “Client Tests” page of the user-interface, which is accessed from the page of FIG. 12;
  • FIG. 23 illustrates a “Test Details” page of the user-interface, which is accessed from the page of FIG. 22;
  • FIG. 24 illustrates a “Demands” page of the user-interface, which is accessed from the page of FIG. 11;
  • FIG. 25 illustrates a “Creating a Demand” page of the user-interface, which is accessed from the page of FIG. 24;
  • FIG. 26 illustrates a “Demand Raised” business process map that relates to creating a demand as described with reference to FIG. 25;
  • FIG. 27 illustrates a “Normalizer” page of the user-interface, which is accessed from the page of FIG. 11;
  • FIG. 28 illustrates a “Creating a Normalizer” page of the user-interface, which is accessed from the page of FIG. 27;
  • FIG. 29 illustrates a “Work Queue” page of the user-interface, which is accessed from the page of FIG. 11; and
  • FIG. 30 illustrates a “Client Monitor” page of the user-interface, which is accessed from the page of FIG. 11.
  • DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENT OF THE INVENTION I. Exemplary Hardware Arrangement
  • The exemplary embodiment of the process management system 100 according to the present invention will now be described in greater detail with reference to FIG. 1. In this figure, an exemplary hardware arrangement of the process management system is shown. The process management system 100 includes the “client connectivity” system 101, the “active workflow” system 102, and the database 103. The client connectivity system 101 includes one or more computers that gather information pertaining to the client connectivity process, such as client information, demands, manual task work queues, connection information, etc. . . . , and store such information in the database 103. The active workflow system 102 includes one or more computers that manage advancement through the client connectivity process. Accordingly, the active workflow system 102 communicates with the client connectivity system 101 to exchange demand information and manual task queues. As demands arise, the client connectivity system 101 passes them on to the active workflow system 102, and the workflow system 102 adjusts the task flow in the client connectivity process accordingly. It should be noted that although the active workflow system 102 and the client connectivity system 101 are shown separate, they may reside on a single computer.
  • The active workflow 102 also manages communication with entities external to the process management system. Such entities include one or more computers 104 belonging to what is referred to herein as the “on-boarding team.” The “on-boarding team” represents one or more individuals responsible for executing manual tasks in the client connectivity process. The computers 104 of the on-boarding team operate the user-interface disclosed herein. As manual tasks arise in the client connectivity process flow, the active workflow system 102 notifies a computer belonging to one or more individuals on the on-boarding team 104 responsible for executing such tasks. The notified individuals view the task via the user-interface, execute the task, and then notify the active workflow system 102 of its completion via the user-interface. Once complete, the workflow system 102 proceeds to the next task in the process.
  • Other external entities include clients 105 that desire to obtain access to the secured service (not shown). The workflow 102 communicates with the client 105, notifying the client of demands, status updates, and connection information. External entities also include individuals 106, referred to herein as the “Firewall Change Request team,” or “FCR team,” responsible for updating the secured service's firewall to accommodate the client 105. The active workflow system 102 will send a message to the FCR team when the manual task of updating the firewall is ready for execution.
  • Other external entities include individuals 107, referred to herein as the “Logical Virtual Connection team,” or “LVC team,” responsible for establishing a Logical Virtual Connection required by some third party networks, if necessary. As with the FCR team, the workflow system 102 will send a message to the LVC team if and when establishment of an LVC is required. Additionally, external entities include Autex 108, which is an exemplary third party network provider that some clients 105 may use. The worfkflow system 102 will send requests to Autex 108, or other third party network providers, if any, when establishment of a connection between the client 105, the third party network, and the secured service is required.
  • I.I. Exemplary Client Connectivity Process Flow
  • Now, the client connectivity process flow (“CC process”) managed by the active workflow system 102 will be described in more detail with reference to FIGS. 2-10. FIGS. 2 and 3 illustrate the symbols used to describe particular tasks in the CC process. These symbols appear next to the tasks described in FIGS. 4-10 and 26. Referring to FIG. 2, “Ordinary Activity” icon 201 denotes a default task type that is executed manually. Tasks of this default type are normally carried out by specified useable resources. “Script Activity” 202 denotes a task that executes a series of instructions in a given language consecutively. Specified usable resources execute these script tasks either automatically or manually. “COM Activity” icon 203 denotes a task that calls a COM object, known in the art, and can be executed automatically or manually by specified resources.
  • “Transactional Activity” 204 denotes a task that calls a combination of one or more COM objects and is always executed automatically. “.NET Activity” icon 205 denotes a task that calls a .NET object. Tasks of this type can be executed automatically or manually by specified resources. “Web Service Activity” 206 denotes a web service task that calls a specific URL and can be executed either automatically or manually by specified usable resources. “Create New Job Type Activity” 207 denotes a task that allows the creation of and insertion of a new task into the CC process. This task type incorporates flexibility into the CC process by allowing unanticipated issues, such as demands, to be addressed on the fly. Create New Job tasks 207 can be executed automatically or manually by specified resources. “State Activity Icon” 208 denotes an “Ordinary” type activity 201 that has no specified resources.
  • Referring to FIG. 3, “Static Useable Resource Only” icon 301 denotes a task that is executed manually by a static resource. A static resource is defined at design time and cannot be changed at run-time. “Dynamic Useable Resource Only” icon 302 denotes a task that is executed manually by dynamically defined resources that can be changed at run-time. “Dynamic and Static Useable Resource” icon 303 denotes a task that is executed manually by static and dynamic resources. “Same as Previous Resource” icon 304 denotes a task that is executed manually by resources that have carried out a selected previous task. Icons 301-304 can appear in conjunction with any task type, with the exception of “Transactional” activities 204.
  • “Automatic” icon 305 denotes a task that is executed automatically by the system. This icon may appear in conjunction with “Script” 202, “COM” 203, and “Create New Job” 207 type tasks, and always appears in conjunction with a “Transactional” activity 204. Finally, “Library Activity” icon 306 denotes a shared task. Library activities can be used across different subprocesses of the CC process. This icon can appear in conjunction with any activity type.
  • The workflow system 102 instructs automatic execution of the automatic tasks described by the icons in FIGS. 2 and 3. When manual tasks arise in the CC process, the workflow system 102 notifies the appropriate individual(s) 104, 106, and/or 107 via the user interface to execute such tasks. The workflow system 102 is notified of completion of the manual tasks via the user interface and then advances the CC process to the next task.
  • Having introduced the meaning of the icons shown in the figures, the underlying subprocesses of the CC process will now be described with reference to the process flows shown in FIGS. 4-10. FIG. 4 represents a high level view of the entire CC process according to the exemplary embodiment of the present invention. The process flow of FIG. 4 is referred to as the “main process.” The main process includes five subprocesses: Initiation 401, described with FIG. 5; Environment Set-Up 402, described with FIGS. 6 and 7; User Acceptance Testing (“UAT”) Testing 403, described with FIG. 8; Production Environment Set-Up 404, described with FIG. 9; and Go Live 405, described with FIG. 10. Prior to beginning the subprocesses, email addresses associated with individuals involved with the CC process may be obtained at 406.
  • The first subprocess of FIG. 4 is initiation 401, which will now be described in detail with reference to FIG. 5. The initiation process 401 includes tasks focusing on obtaining information necessary to begin the CC process, such as general client information 501, protocol information, such as information required to comply with the FIX protocol 502 and 504, and connection information about the client 503. The FIX protocol is the Financial Information eXchange (FIX) protocol, which is a messaging standard developed specifically for the real-time electronic exchange of securities transactions as is known in the art.
  • In the exemplary embodiment, the tasks 501-504 are manually performed by individuals on the on-boarding team 104 using the user-interface described below. The active workflow system 102 delegates manual tasks, such as these, by sending notifications to the responsible individuals on the on-boarding team 104, via the user-interface. The workflow system 102 waits for an indication that the manual tasks are complete before proceeding to the next task. The information input at 501, 502, 503, and 504 is described with reference to FIGS. 12, 13, 15, and 16, respectively.
  • As will be shown, each of the subprocesses of FIG. 4 include a subprocess of resolving outstanding demands. In the initiation process 401, this subprocess occurs at 505. When a problem arises during the CC process, an individual on the on-boarding team 104 raises a demand via the user interface described below with reference to FIGS. 24-26. In the subprocess at 505, tasks required to resolve the demand are delegated to the appropriate individuals on the on-boarding team 104 for execution. Once the tasks are complete and the demand resolved, the CC process exits the demand subprocess at 505.
  • The initiation process 401 also includes status update tasks and some other preliminary tasks. In particular, the initiation process 401 includes updating a status of the CC process to indicate that the initiation process 401 is being executed at 506. Also, an overall percentage complete of the CC process is updated periodically when certain tasks are completed, as shown at 509, for example. Further, the client is added to a mapping table at 507 stored in the database 103 that includes a list of all clients involved in the CC process. Additionally, the initiation process 401 includes adding a set of tests at 508 to the database 103 that must be performed to ensure proper connectivity for the client. Client tests are described in more detail with respect to FIGS. 22 and 23.
  • After completing the initiation process 401, the environment set-up process 402 begins, which is shown with FIGS. 6 and 7. The environment set-up process 402 prepares the appropriate connection parameters, accounts, and third party networks for connection between the secured service and the client. The preparations made in the environment set-up process 402 are a prelude for testing the connection to the client, which is described below with reference to User Acceptance Testing and FIG. 8.
  • The tasks involved in the environment set-up process 402 include setting up the client for access to the Global Trading Workstation (“GTW”), which is a platform by which the client will trade financial instruments, and setting up FIX gateway routing and associated account information at 601. The tasks at 602 represent recording additional parameters required for the client to seamlessly communicate via the FIX protocol, such as normalizers discussed below with reference to FIGS. 27 and 28. The tasks at 603 pertain to updating the secured service's firewall to accommodate the client. Such tasks include sending a notification to the FCR team 106 requesting that the firewall be adjusted, receiving a notification from the FCR team 106 that this manual task has been completed, and recording the updated port information associated with the firewall change.
  • Turning now to FIG. 7, which shows the second half of FIG. 6, the tasks at 701 and 702 pertain to acquiring a test date at which the client will be able to perform its User Acceptance Testing to test its connection to the secured service. Once a test date is acquired, such information is sent to the client 105 via a message from the active workflow system 102, as shown at 701. Also, members of the on-boarding team 104 are notified of the test date and associated information via a message from the active workflow system 102, as shown at 702. In the exemplary embodiment, these members of the on-boarding team 104 are referred to as the “CC Infrastructure” team.
  • The tasks at 703 determine whether the client uses TNS, which is an exemplary third party network that requires use of a “Logical Virtual Connection.” If the client 105 uses TNS, a message is sent to the LVC team 107 by the active workflow system 102 notifying them of their responsibility to complete the manual task of setting up an LVC.
  • The tasks at 704 determine whether the client uses Autex, another exemplary third party network. If so, a message is prepared and sent to the third party network provider, in this example, Autex 108, by the workflow system 102. The message requests the third party network provider to adjust their system to allow connectivity between the client 105 and the secured service. The tasks at 705 pertain to preparation of a test plan, which is a manual task, for use in the user acceptance testing (“UAT”) process.
  • Returning to FIG. 6, after the above-mentioned tasks have completed, the client 105 is sent a message at 604 containing the connection information required for the client to connect to secured service for UAT. At 605, outstanding demands are resolved prior to proceeding to such testing.
  • Testing occurs during execution of the UAT testing process 403 shown in detail in FIG. 8. The UAT testing process 403 includes preparation of logging functionality 801 to log errors in the testing process and performing internal testing 802 of client tests identified at 508 in FIG. 5 and according to the test plan of 705 in FIG. 7. UAT also includes establishing a connection with the client 105 at 803 so that the client can perform its user acceptance testing to ensure that the connection works properly. Once testing is complete, if the client 105 uses TNS, the LVC is established to such network at 804. The third party provider of the INS network is notified of such connection at 805. To complete the UAT process, outstanding demands are resolved and the status of the process is updated at 806.
  • With UAT testing 403 complete, the CC process advances to production environment set-up 404, shown in detail in FIG. 9. The environment set-up process involves compiling final port information 901 and protocol interface information 902, and preparing the applications necessary to allow the client 105 access to the secured service 903. In the exemplary embodiment, such applications include the global trading workstation which uses the FIX protocol and allows the client 105 direct market access to trading financial instruments. The environment set-up process 404 also includes tasks that notify appropriate individuals at 904 on the on-boarding team 104 of the client's impending live connection to the secured service. In the exemplary embodiment, the individuals that are notified are referred to as the “production client connectivity” team, or “PROD CC,” and the “client connectivity infrastructure” team, or “CC Infrastructure.” To complete the production environment set-up process 403, process statuses are updated and outstanding demands resolved at 905.
  • With the production environment ready, the “Go-Live” process 405 is executed, as shown in detail with FIG. 10. This process includes tasks pertaining to testing the live connection to the client, such as executing a dummy live trade 1001, and receiving approval from the appropriate individuals to allow the client 105 access to the secured service. Such approval is shown at 1002, and includes approval from legal personnel, front office personnel, and operators. Once approval is received, a message is sent to all involved parties, including the client 105, indicating that the client now has access to the secured service at 1003, thereby completing the CC process.
  • III. Exemplary User Interface
  • The exemplary user interface for interacting with the process management system 100 will now be described. The exemplary user interface is operated by computers associated with individuals on the on-boarding team 104, the FCR team 106, and the LVC team 107. However, this user interface may also be operated by the client 105, Autex 108, and any other individual or entity interested in the CC process.
  • Access to the process management system 100 via the interface is controlled using user names, passwords, and a series of user types having varying levels of access rights to the process management system 100. For instance, a particular user may be associated with an “admin” user type and have complete read and write access to the process management system 100. The client 105, on the other hand, may be associated with a user type that has read-only access. Members of the on-boarding team 104 may be associated with an intermediate user type having limited write access and full read access.
  • Once a user enters a valid user name and password, a home page shown at FIG. 11 is displayed. The home page includes a navigation bar 1101 having links that, when selected, take the user to another page and/or perform an action. The “Admin” link 1102 displays a “User Configuration” page where an admin can add users to or remove users from the user-interface, or modify the user types associated with users. The “Log In” link 1103 displays a “Login” page where the user, or another user, may log in. The “Home” link 1206 brings the user to the home page, which is currently being described with reference to FIG. 11. The “Client” link 1105 displays the “Client” page illustrated at FIGS. 12-23. The “Demands” link 1106 brings the user to a “Demands” page illustrated at FIGS. 24-25. The “Normalizer” link 1107 displays a “Normalizer” page illustrated at FIGS. 27-28. The “Vendor” link 1108 displays a “Vendor” page where the user can add, remove, or modify vendor information. The “Work queue” link 1109 brings the user to a “Work queue” page illustrated at FIG. 29, and the “Reports” link 1110 displays a “Reports” page where the user can run reports displaying information pertaining to the CC process. The “Client Search” link 1111 displays a “Client Search” page where the user can search for particular clients. The “Monitor” link 1112 displays a “Client Monitor” page illustrated at FIG. 30. And, the “Log Off” link 1113 logs the user off of the user-interface.
  • The “Client” page, accessed by link 1105, will now be described with reference to FIGS. 12-23. The “Client” page is used to set up clients or display information relating to clients. The Client page includes several subpages which can be accessed by clicking on tabs 1200 at the top of the Client page (FIG. 12). To create a new client, the user inputs the information required on each of these subpages and then click on a “Submit” button (1201, for example). After selecting the submit button 1201, the client information is sent to the project management system 100 via the client connectivity system 101. If all of the necessary information has been entered, the new client is created and a new client connect process is initiated for that client (FIG. 4).
  • Each of the tabs 1200 of the Client page will now be described by first referring to FIG. 12. In FIG. 12, the “General” tab 1202 is currently selected. The “General” tab 1202 displays a form containing general client information, such as company identifiers for the client 1203, client contact information 1204, other contact information 1205, client status information 1206, and key event dates pertaining to the CC process 1207. The task of inputting this information is shown at 501 in FIG. 5.
  • Turning now to FIG. 13, the UAT Tab 1301 on the client page will be described. The UAT tab 1301 provides information relating to the FIX details associated with the client at issue for use in the User Acceptance Testing environment. These details describe parameters of the client's system to facilitate communication using the FIX protocol. The task of inputting this information is shown at 502 in FIG. 5.
  • The “Production” tab 1401 will now be described with reference to FIG. 14. This tab provides the same information as the UAT Tab 1301, except that the information in the “Production” tab 1501 relates to the production environment.
  • FIG. 15 illustrates the “Connection” tab 1501. The connection tab 1501 provides information relating to the client's communication connection, such as IP addresses 1502, network connection types 1503, ports 1504, and encryption types 1505. This information is input at 503 in FIG. 5.
  • FIG. 16 illustrates the “FIX Message” tab 1601 that provides information relating to the particular parameters associated with the client's FIX message usage when conducting trades, such as session layer information 1602, session and application exceptions 1603, order status 1604, order types 1605, and currency 1606.
  • FIG. 17 illustrates the “Markets” tab 1701, which allows the user to select, among other things, trading regions 1702 where the client will be trading financial instruments via the secured service. Exemplary regions include EMEA (i.e., Europe, the Middle East, and Asia), the United States, Latin America, Japan, Hong Kong, and Australia. The notes tab 1703 allows the user to enter any miscellaneous information regarding the CC process. Also from the notes tab 1703, the user can set up reminders that prompt the workflow system 102 to send messages to particular users of the user interface at particular times.
  • FIG. 18 illustrates the “Normalizer” tab 1801, that when selected, displays a form pertaining to message translations. Because the client's system may not communicate in the same manner that the secured service communicates, messages from the client system to the secured service, and vice versa, may need to have translation functions applied to them. The translation functions, or normalizers, act as an interface between the client system 105 and the secured service allowing them to communicate with each other in a format understandable by both sides. The form shown in FIG. 18 allows the user to view existing normalizers, which are listed in the window 1802. Entry of new normalizers is discussed below with reference to FIGS. 27 and 28.
  • FIG. 19 illustrates the “Demands” tab 1901 that, when selected, displays a form allowing the user to view a list of outstanding demands. Existing demands are displayed in row format in the window 1902. The user can view more details of a particular demand by selecting an existing demand in the window and then selecting the “View Demand” button 1903. Entry of new demands is discussed in more detail with reference to FIGS. 24-26.
  • If the current user has assigned tasks to complete for this client, two additional tabs are displayed on the Client page. With reference to FIGS. 20 and 21, the two additional tabs are the “Progress” tab 2001 and the “Activity” tab 2101. The “Progress” tab 2001, when selected, displays the CC process flow (FIGS. 4-10) and indicates the current status of the process by highlighting tasks that have been completed.
  • The “Activity” tab 2101 in FIG. 21, when selected, provides information about any manual tasks that have been assigned to the user by the workflow system 102. For example, if the current user has been assigned the task “setup client in production GTW,” shown at 906 in FIG. 9, such task is shown at 2102 in FIG. 22 informing the user that he or she is responsible for completing the task. Once the task is complete, the user selects the “Complete Activity” button 2103. Selecting this button notifies the active workflow system 102 that the task is complete, so that processing can advance to the next task in the CC process, which in this example is “update percent complete” 907 in FIG. 9.
  • The user interface pertaining to client tests will now be described. Referring back to FIG. 12, when the “Client Tests” button 1208 is selected, the “Client Tests” dialog box illustrated in FIG. 22 is displayed. The dialog box of FIG. 22 lists all of the existing Client Tests to be executed at 802 in FIG. 8. The tests are listed row-by-row in window 2201. Information displayed for each test includes a test identifier, a status of the test, such as “run” or “not run,” a run date and time, and the number of attempts that have been made to complete the test.
  • When the user selects one of the tests in the window 2201, a “Test Details” form is displayed, as illustrated in FIG. 23. The user may view and/or edit test details including a description of the test 2301, the tasks involved in completing the tests and their order of execution 2302, result details 2303, number of attempts made 2304, and whether the test passed or failed 2305.
  • Having completed the description of the “Client” page, which is accessed by selecting the “Client” link 1105 (FIG. 11), the “demands” page will now be described. The demands page is accessed by selecting the “demands” link 1106 (FIG. 11) from the navigation bar 1101. The demands page is illustrated with FIG. 24, from which the user can view, create, edit, and delete demands. Existing demands are listed row-by-row in the window 2401.
  • A demand may be deleted by selecting a demand and then selecting the “Delete Demand” button 2402. A demand may be edited by selecting a demand and then selecting the “Edit Demand” button 2403. And, a demand may be created by selecting the “Create Demand” button 2404.
  • When selecting either the “Edit Demand” button 2403 or the “Create Demand” button 2404, the “Client Demand” page illustrated with FIG. 25 is displayed. If the “Edit Demand” button 2403 is selected, the “Client Demand” page is shown filled with the information pertaining to the selected demand. If the “Create Demand” button 2404 is selected, a new “Client Demand” page is displayed.
  • The “Client Demand” page is a form that allows the user to view and/or enter information about a demand, including a description of the demand 2501, impacts of the demand 2502, the demand priority 2503, a status of the demand 2504, manual workarounds 2505, and clients affected by the demand 2506. The user may also attach documents 2507 to the demand. After the user enters the information in the “Client Demand” page, the user selects the “Add/Save” button 2508 to complete the creation of the new demand or accept the changes made to an existing demand.
  • Once a demand has been created an instance of a Demand Raised subprocess is created, as illustrated in FIG. 26. This subprocess notifies responsible individuals on the on-boarding team 104, as shown at 2601, obtains approval of the demand from particular individuals on the on-boarding team 104, as shown at 2602, and releases the demand at 2603, when approved. Release of the demand means that the workflow system 102 modifies the CC process to include the tasks associated with resolving the demand. The manual tasks required to resolve the demand are delegated to the appropriate individuals on the on-boarding team 104, FCR team 106, or LVC team 107 as previously discussed. The workflow system 102 ensures that these tasks have been completed when the demands outstanding subprocess occurs, such as at 505 in FIG. 5.
  • Having concluded the description of the “Demands” page, which is accessible via the “Demands” link 1106 in FIG. 11, the “Normalize” page will now be described. The “Normalizer” page is accessible via the “Normalizer” link 1107 shown in FIG. 11. Once this link is selected, the “Normalizer” page is displayed, which is illustrated with FIG. 27. The “Normalizer” page allows the user to view, edit, create, and delete normalizers.
  • Existing normalizers are displayed in the window 2701 in row format. A normalizer may be deleted by selecting a normalizer and then selecting the “Delete Normalizer” button 2702. A normalizer may be edited by selecting a normalizer and then selecting the “Edit Normalizer” button 2703. A normalizer may be created by selecting the “Create Normalizer” button 2704.
  • By selecting either the “Edit Normalizer” button 2703 or the “Create Normalizer” button 2704, the “Client Normalizer” page is displayed, which is illustrated with FIG. 28. On this page, the user may view and/or enter data pertaining to the normalizer including the name of the field that requires data translation 2801, a FIX tag name of the affected field 2802, the status of the normalizer 2803, such as “build,” the actions involved in executing the normalizer 2804, and the clients affected by the normalizer 2805. Once the information has been entered, the user may select the “Add/Save” button 2806 to complete the changes. Any changes to the normalizers are recorded during the CC process, as shown for example, at 602 in FIG. 6.
  • Having completed the description of the “Normalizer” page, which is accessed from the “Normalizer” link 1107 shown in FIG. 11, the “Work queue” page will be described, which is accessed via the “Work queue” link 1109. The “Work queue” page is illustrated with FIG. 29. This page displays a list of activities that need to be completed for a particular client 105. Contrary to the “Activity” tab described with reference to FIG. 21, the “Work queue” page displays all outstanding manual tasks for a particular client, instead of just the tasks assigned to a particular user. From the “Work Queue” page, the user can take on an assigned activity by selecting button “Take Activity” 2901, and/or can mark an activity as complete by selecting button “Complete Activity” 2902. By allowing the user to take on someone else's task, work loads can be managed on the fly in a simple manner. When a user takes on someone else's task, such task shows up on his or her “Activity” form (FIG. 21).
  • Having completed the description of the “Work queue” page, the “Client Monitor” page will be described, which is accessed via the “Monitor” link 1112 illustrated with FIG. 11. The “Client Monitor” page, illustrated with FIG. 30, displays all clients for the selected region and their status. The information that is displayed for each client includes a color-coded status 3001, a client name 3002, a text based status 3003, a percentage complete 3004, and an expected CC process completion date 3005. Although the color-coded status 3001 can use any number of colors to represent any sort of status, the exemplary embodiment uses three colors to indicate three different statuses. A first color 3006 indicates that the client connect process is in production without outstanding issues or demands. A second color 3007 indicates that the process is in a subprocess other than production without issues or demands. And, a third color 3008 indicates that there are outstanding issues or demands in the client connect process. In the exemplary embodiment, the first color is green, the second color is yellow, and the third color is red.
  • The status field 3003 displays the client status that was discussed with respect to the process maps in FIGS. 4-10 (506 in FIG. 5, for example.) The percent complete field 3004 displays the percent complete that was also discussed with respect to FIGS. 4-10 (509 in FIG. 5, for example.)
  • It is to be understood that the above-described embodiment is merely illustrative of the present invention and that many variations of the above-described embodiment can be devised by one skilled in the art without departing from the scope of the invention. It is therefore intended that such variations be included within the scope of the following claims and their equivalents.

Claims (10)

1. A system for providing access to a secured service, the system comprising:
a computer-readable memory storing a process flow comprising a plurality of tasks associated with providing access to the secured service, the plurality of tasks comprising automatic tasks and at least one manual task;
a manual task computer associated with an individual responsible for executing the manual task;
a process management system communicatively connected to the computer-readable memory and the manual task computer, the process management system advancing through the plurality of tasks in the process flow by performing actions comprising:
(i) instructing automatic execution of a first automatic task when due for execution,
(ii) transmitting, after the execution of the first automatic task, a message to the manual task computer indicating that the manual task is due for execution, and
(iii) receiving, prior to advancing to a second automatic task, an indication from the manual task computer that the manual task is complete; and
a demand creation computer that transmits a demand to the process management system while the process management system is advancing through the plurality of tasks in the process flow, the demand indicating a problem encountered while creating a connection with the secured service that must be rectified to provide access to the secured service, wherein the process management system performs actions further comprising:
(i) receiving the demand from the demand creation computer, and
(ii) inserting a new task into the process flow, the new task associated with rectifying the problem.
2. The system of claim 1 wherein the secured service is provided by a computer system that allows trading of financial instruments.
3. The system of claim 1, wherein the new task is a new manual task, and the system further comprises:
a second manual task computer associated with an individual responsible for executing the new manual task, the second manual task computer communicatively connected to the process management system, wherein the process management system is programmed to perform actions further comprising:
transmitting, when the new manual task is due for execution, a message to the second manual task computer indicating that the new manual task is due for execution; and
receiving, prior to advancing the process flow, an indication from the second manual task computer that the new manual task is complete.
4. A computer-implemented method for providing access to a secured service, comprising:
retrieving, from a computer-readable memory, a process flow comprising a plurality of tasks associated with providing access to the secured service, the plurality of tasks comprising automatic tasks and at least one manual task;
advancing, by a computer, through the plurality of tasks in the process flow by performing actions comprising:
instructing automatic execution of a first automatic task when due for execution,
transmitting, after the execution of the first automatic task, a message to a manual task computer associated with an individual responsible for executing the manual task indicating that the manual task is due for execution,
receiving prior to advancing to a second automatic task, an indication from the manual task computer that the manual task is complete,
receiving a demand indicating a problem encountered while creating a connection with the secured service that must be rectified to provide access to the secured service, and
inserting into the process flow, a new task associated with rectifying the problem.
5. The computer-implemented method of claim 4 wherein the secured service is provided by a computer system that allows trading of financial instruments.
6. The computer-implemented method of claim 4, wherein the new task is a new manual task, further comprising:
transmitting, when the new manual task is due for execution, a message to a second manual task computer indicating that the new manual task is due for execution; and
receiving, prior to advancing the process flow, an indication from the second manual task computer that the new manual task is complete.
7. A method for providing a client access to a secured service, the method comprising:
transmitting a first message from a computer system to instruct the secured service to configure a firewall associated with the secured service, wherein the firewall allows a connection to be established between the secured service and the client;
receiving, with the computer system, notification that the firewall has been configured;
requesting a connection be established between the secured service and the client by transmitting a second message from the computer system to the client, wherein the second message contains client connection information;
receiving, with the computer system, an indication that the connection has been established between the secured service and the client;
requesting that the connection be tested by transmitting a third message to the client from the computer system;
receiving, with the computer system, an indication that the connection has been manually tested by the client; and
transmitting a notification indicating that client access to the secured service has been established.
8. The method of claim 7 wherein the secured service is provided by a computer system that allows the client to trade financial instruments.
9. The method of claim 8 further comprising:
requesting protocol information by transmitting a fourth message from the computer system; and
receiving, with the computer system, the protocol information.
10. The method of claim 9 wherein the protocol information pertains to the FIX protocol.
US12/717,326 2004-03-09 2010-03-04 User connectivity process management system Abandoned US20100199279A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/717,326 US20100199279A1 (en) 2004-03-09 2010-03-04 User connectivity process management system

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US55143604P 2004-03-09 2004-03-09
US10/888,923 US7702767B2 (en) 2004-03-09 2004-07-09 User connectivity process management system
US12/717,326 US20100199279A1 (en) 2004-03-09 2010-03-04 User connectivity process management system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/888,923 Continuation US7702767B2 (en) 2004-03-09 2004-07-09 User connectivity process management system

Publications (1)

Publication Number Publication Date
US20100199279A1 true US20100199279A1 (en) 2010-08-05

Family

ID=34922733

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/888,923 Active 2027-08-13 US7702767B2 (en) 2004-03-09 2004-07-09 User connectivity process management system
US12/717,326 Abandoned US20100199279A1 (en) 2004-03-09 2010-03-04 User connectivity process management system

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/888,923 Active 2027-08-13 US7702767B2 (en) 2004-03-09 2004-07-09 User connectivity process management system

Country Status (1)

Country Link
US (2) US7702767B2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105283888A (en) * 2013-06-12 2016-01-27 惠普发展公司,有限责任合伙企业 Distributed worker-sourced process engineering

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006004008A (en) * 2004-06-15 2006-01-05 Sony Computer Entertainment Inc Processing control unit, computer system, distributed processing method, and computer program
US20060136832A1 (en) * 2004-12-17 2006-06-22 Siebel Systems, Inc. Flexible and extensible combination user interfaces
US7747959B2 (en) * 2004-12-17 2010-06-29 Siebel Systems, Inc. Flexible and extensible combination user interfaces
US9411794B2 (en) * 2007-09-14 2016-08-09 International Business Machines Corporation Facilitating selection of objects on display screens
JP5047870B2 (en) * 2008-04-17 2012-10-10 株式会社日立製作所 Master management system, master management method, and master management program
US20100036832A1 (en) * 2008-08-08 2010-02-11 Yahoo!, Inc. Searching by object category for online collaboration platform
US8195419B2 (en) 2009-03-13 2012-06-05 Teradyne, Inc. General purpose protocol engine
US20110138333A1 (en) * 2009-12-03 2011-06-09 Ravishankar Gundlapalli Room User Interface
US9116785B2 (en) 2013-01-22 2015-08-25 Teradyne, Inc. Embedded tester
US11194441B2 (en) * 2020-04-14 2021-12-07 Sap Se Process map navigation tool

Citations (97)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3316395A (en) * 1963-05-23 1967-04-25 Credit Corp Comp Credit risk computer
US3634669A (en) * 1969-07-16 1972-01-11 Aero Flow Dynamics Inc Analog computation of insurance and investment quantities
US4594663A (en) * 1982-07-09 1986-06-10 Omron Tateisi Electronics Co. Credit transaction processing system
US4598367A (en) * 1983-11-09 1986-07-01 Financial Design Systems, Inc. Financial quotation system using synthesized speech
US4642768A (en) * 1984-03-08 1987-02-10 Roberts Peter A Methods and apparatus for funding future liability of uncertain cost
US4736294A (en) * 1985-01-11 1988-04-05 The Royal Bank Of Canada Data processing methods and apparatus for managing vehicle financing
US4739478A (en) * 1984-11-21 1988-04-19 Lazard Freres & Co. Methods and apparatus for restructuring debt obligations
US4760604A (en) * 1985-02-15 1988-07-26 Nestor, Inc. Parallel, multi-unit, adaptive, nonlinear pattern class separator and identifier
US4812628A (en) * 1985-05-02 1989-03-14 Visa International Service Association Transaction system with off-line risk assessment
US4831526A (en) * 1986-04-22 1989-05-16 The Chubb Corporation Computerized insurance premium quote request and policy issuance system
US4866634A (en) * 1987-08-10 1989-09-12 Syntelligence Data-driven, functional expert system shell
US4897811A (en) * 1988-01-19 1990-01-30 Nestor, Inc. N-dimensional coulomb neural network which provides for cumulative learning of internal representations
US4914587A (en) * 1985-07-01 1990-04-03 Chrysler First Information Technologies, Inc. Financial data processing system with distributed data input devices and method of use
US4964043A (en) * 1988-06-13 1990-10-16 Galvin Thomas M System for visualizing, identifying and ordering gearing configurations
US5054096A (en) * 1988-10-24 1991-10-01 Empire Blue Cross/Blue Shield Method and apparatus for converting documents into electronic data for transaction processing
US5206803A (en) * 1991-03-15 1993-04-27 Vitagliano Francis M System for enhanced management of pension-backed credit
US5220500A (en) * 1989-09-19 1993-06-15 Batterymarch Investment System Financial management system
US5227874A (en) * 1986-03-10 1993-07-13 Kohorn H Von Method for measuring the effectiveness of stimuli on decisions of shoppers
US5231571A (en) * 1990-08-14 1993-07-27 Personal Financial Assistant, Inc. Personal financial assistant computer method
US5233547A (en) * 1991-11-12 1993-08-03 Ncr Corporation Electronic checking account apparatus and method having a digitizer to receive information as a check is being written
US5239462A (en) * 1992-02-25 1993-08-24 Creative Solutions Groups, Inc. Method and apparatus for automatically determining the approval status of a potential borrower
US5262941A (en) * 1990-03-30 1993-11-16 Itt Corporation Expert credit recommendation method and system
US5274547A (en) * 1991-01-03 1993-12-28 Credco Of Washington, Inc. System for generating and transmitting credit reports
US5278751A (en) * 1991-08-30 1994-01-11 International Business Machines Corporation Dynamic manufacturing process control
US5321841A (en) * 1989-06-29 1994-06-14 Digital Equipment Corporation System for determining the rights of object access for a server process by combining them with the rights of the client process
US5424938A (en) * 1992-10-13 1995-06-13 First Chicago Corporation Method and apparatus for providing access to a plurality of payment networks
US5444844A (en) * 1991-06-04 1995-08-22 Nsk Ltd. Figure drawing apparatus and inventory purchasing system using the same
US5481647A (en) * 1991-03-22 1996-01-02 Raff Enterprises, Inc. User adaptable expert system
US5523942A (en) * 1994-03-31 1996-06-04 New England Mutual Life Insurance Company Design grid for inputting insurance and investment product information in a computer system
US5537315A (en) * 1994-03-23 1996-07-16 Mitcham; Martin K. Method and apparatus for issuing insurance from kiosk
US5551021A (en) * 1993-07-30 1996-08-27 Olympus Optical Co., Ltd. Image storing managing apparatus and method for retreiving and displaying merchandise and customer specific sales information
US5550734A (en) * 1993-12-23 1996-08-27 The Pharmacy Fund, Inc. Computerized healthcare accounts receivable purchasing collections securitization and management system
US5611052A (en) * 1993-11-01 1997-03-11 The Golden 1 Credit Union Lender direct credit evaluation and loan processing system
US5644493A (en) * 1991-08-30 1997-07-01 Nsk Ltd. Production information processing system
US5649116A (en) * 1995-03-30 1997-07-15 Servantis Systems, Inc. Integrated decision management system
US5655085A (en) * 1992-08-17 1997-08-05 The Ryan Evalulife Systems, Inc. Computer system for automated comparing of universal life insurance policies based on selectable criteria
US5664115A (en) * 1995-06-07 1997-09-02 Fraser; Richard Interactive computer system to match buyers and sellers of real estate, businesses and other property using the internet
US5689649A (en) * 1991-03-01 1997-11-18 Altman; Robert System for operation of a combination mortgage, equity load and savings plan
US5696907A (en) * 1995-02-27 1997-12-09 General Electric Company System and method for performing risk and credit analysis of financial service applications
US5699527A (en) * 1995-05-01 1997-12-16 Davidson; David Edward Method and system for processing loan
US5701400A (en) * 1995-03-08 1997-12-23 Amado; Carlos Armando Method and apparatus for applying if-then-else rules to data sets in a relational data base and generating from the results of application of said rules a database of diagnostics linked to said data sets to aid executive analysis of financial data
US5715402A (en) * 1995-11-09 1998-02-03 Spot Metals Online Method and system for matching sellers and buyers of spot metals
US5717865A (en) * 1995-09-25 1998-02-10 Stratmann; William C. Method for assisting individuals in decision making processes
US5732397A (en) * 1992-03-16 1998-03-24 Lincoln National Risk Management, Inc. Automated decision-making arrangement
US5742775A (en) * 1995-01-18 1998-04-21 King; Douglas L. Method and apparatus of creating financial instrument and administering an adjustable rate loan system
US5758328A (en) * 1996-02-22 1998-05-26 Giovannoli; Joseph Computerized quotation system and method
US5765144A (en) * 1996-06-24 1998-06-09 Merrill Lynch & Co., Inc. System for selecting liability products and preparing applications therefor
US5774882A (en) * 1992-03-12 1998-06-30 Keen; Regina D. Credit approval system
US5774883A (en) * 1995-05-25 1998-06-30 Andersen; Lloyd R. Method for selecting a seller's most profitable financing program
US5794207A (en) * 1996-09-04 1998-08-11 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers
US5797133A (en) * 1994-08-31 1998-08-18 Strategic Solutions Group, Inc Method for automatically determining the approval status of a potential borrower
US5802251A (en) * 1993-12-30 1998-09-01 International Business Machines Corporation Method and system for reducing perplexity in speech recognition via caller identification
US5802502A (en) * 1993-05-24 1998-09-01 British Telecommunications Public Limited Company System for selective communication connection based on transaction pricing signals
US5809478A (en) * 1995-12-08 1998-09-15 Allstate Insurance Company Method for accessing and evaluating information for processing an application for insurance
US5815683A (en) * 1996-11-05 1998-09-29 Mentor Graphics Corporation Accessing a remote cad tool server
US5832447A (en) * 1994-05-24 1998-11-03 Envoy Corporation Automated system and method for providing real-time verification of health insurance eligibility
US5838906A (en) * 1994-10-17 1998-11-17 The Regents Of The University Of California Distributed hypermedia method for automatically invoking external application providing interaction and display of embedded objects within a hypermedia document
US5844553A (en) * 1993-08-30 1998-12-01 Hewlett-Packard Company Mechanism to control and use window events among applications in concurrent computing
US5845256A (en) * 1993-08-19 1998-12-01 John B. Pescitelli Interactive self-service vending system
US5848427A (en) * 1995-09-14 1998-12-08 Fujitsu Limited Information changing system and method of sending information over a network to automatically change information output on a user terminal
US5862223A (en) * 1996-07-24 1999-01-19 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically-assisted commercial network system designed to facilitate and support expert-based commerce
US5870723A (en) * 1994-11-28 1999-02-09 Pare, Jr.; David Ferrin Tokenless biometric transaction authorization method and system
US5870721A (en) * 1993-08-27 1999-02-09 Affinity Technology Group, Inc. System and method for real time loan approval
US5873096A (en) * 1997-10-08 1999-02-16 Siebel Systems, Inc. Method of maintaining a network of partially replicated database system
US5875437A (en) * 1987-04-15 1999-02-23 Proprietary Financial Products, Inc. System for the operation and management of one or more financial accounts through the use of a digital communication and computation system for exchange, investment and borrowing
US5878403A (en) * 1995-09-12 1999-03-02 Cmsi Computer implemented automated credit application analysis and decision routing system
US5897621A (en) * 1996-06-14 1999-04-27 Cybercash, Inc. System and method for multi-currency transactions
US5899982A (en) * 1995-03-08 1999-05-04 Huntington Bancshares Incorporated Bank-centric service platform, network and system
US5903881A (en) * 1997-06-05 1999-05-11 Intuit, Inc. Personal online banking with integrated online statement and checkbook user interface
US5910988A (en) * 1997-08-27 1999-06-08 Csp Holdings, Inc. Remote image capture with centralized processing and storage
US5911135A (en) * 1987-04-15 1999-06-08 Proprietary Financial Products, Inc. System for managing financial accounts by a priority allocation of funds among accounts
US5913202A (en) * 1996-12-03 1999-06-15 Fujitsu Limited Financial information intermediary system
US5918217A (en) * 1997-12-10 1999-06-29 Financial Engines, Inc. User interface for a financial advisory system
US5920848A (en) * 1997-02-12 1999-07-06 Citibank, N.A. Method and system for using intelligent agents for financial transactions, services, accounting, and advice
US5926800A (en) * 1995-04-24 1999-07-20 Minerva, L.P. System and method for providing a line of credit secured by an assignment of a life insurance policy
US5930764A (en) * 1995-10-17 1999-07-27 Citibank, N.A. Sales and marketing support system using a customer information database
US5930775A (en) * 1997-01-14 1999-07-27 Freddie Mac Method and apparatus for determining an optimal investment plan for distressed residential real estate loans
US5930776A (en) * 1993-11-01 1999-07-27 The Golden 1 Credit Union Lender direct credit evaluation and loan processing system
US5940812A (en) * 1997-08-19 1999-08-17 Loanmarket Resources, L.L.C. Apparatus and method for automatically matching a best available loan to a potential borrower via global telecommunications network
US5940811A (en) * 1993-08-27 1999-08-17 Affinity Technology Group, Inc. Closed loop financial transaction method and apparatus
US5963953A (en) * 1998-03-30 1999-10-05 Siebel Systems, Inc. Method, and system for product configuration
US5966699A (en) * 1996-10-11 1999-10-12 Zandi; Richard System and method for conducting loan auction over computer network
US5970482A (en) * 1996-02-12 1999-10-19 Datamind Corporation System for data mining using neuroagents
US5970483A (en) * 1997-07-25 1999-10-19 Claritech Corporation Apparatus and methodology for submitting search queries
US5983206A (en) * 1989-05-25 1999-11-09 Oppenheimer; Robert H. Computer system and computer-implemented process for implementing a mortgage partnership
US5987436A (en) * 1999-01-26 1999-11-16 Halbrook; W. Bracey Obligated investment system
US5987434A (en) * 1996-06-10 1999-11-16 Libman; Richard Marc Apparatus and method for transacting marketing and sales of financial products
US5991750A (en) * 1997-10-24 1999-11-23 Ge Capital System and method for pre-authorization of individual account transactions
US5995947A (en) * 1997-09-12 1999-11-30 Imx Mortgage Exchange Interactive mortgage and loan information and real-time trading system
US20020029194A1 (en) * 2000-09-07 2002-03-07 Richard Lewis System and method of managing financial transactions over an electronic network
US20020073018A1 (en) * 2000-09-28 2002-06-13 Charles Mulinder Real-time trading system
US20020083213A1 (en) * 2000-09-18 2002-06-27 Oberstein Brien M. Method and system for simulating and certifying complex business applications
US20030217166A1 (en) * 2002-05-17 2003-11-20 Mario Dal Canto System and method for provisioning universal stateless digital and computing services
US20030216990A1 (en) * 1998-11-09 2003-11-20 Onecore Financial Network, Inc. Systems and methods for performing integrated financial transactions
US20030233583A1 (en) * 2002-06-13 2003-12-18 Carley Jeffrey Alan Secure remote management appliance
US7237257B1 (en) * 2001-04-11 2007-06-26 Aol Llc Leveraging a persistent connection to access a secured service
US7310659B1 (en) * 2003-06-27 2007-12-18 Sprint Communications Company L.P. Interface and method for extending a target application over an instant message link of a communication network

Family Cites Families (138)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0789337B2 (en) * 1985-10-30 1995-09-27 株式会社日立製作所 Distributed file recovery method
US4751702A (en) * 1986-02-10 1988-06-14 International Business Machines Corporation Improving availability of a restartable staged storage data base system that uses logging facilities
FR2615641B1 (en) 1987-05-20 1989-08-18 Airbus Ind METHOD FOR DEVELOPING A STATISTICAL MODEL FOR DETERMINING THE WORKLOAD OF AN AIRCRAFT PILOT, RESULTING MODEL, DEVICE FOR CARRYING OUT SAID METHOD AND APPLICATIONS OF THE MODEL
US5027269A (en) * 1989-04-27 1991-06-25 International Business Machines Corporation Method and apparatus for providing continuous availability of applications in a computer network
US5179702A (en) * 1989-12-29 1993-01-12 Supercomputer Systems Limited Partnership System and method for controlling a highly parallel multiprocessor using an anarchy based scheduler for parallel execution thread scheduling
US5396635A (en) * 1990-06-01 1995-03-07 Vadem Corporation Power conservation apparatus having multiple power reduction levels dependent upon the activity of the computer system
CA2019327C (en) 1990-06-19 2000-02-29 Peter K.L. Shum User inquiry facility for data processing systems
US5313616A (en) * 1990-09-18 1994-05-17 88Open Consortium, Ltd. Method for analyzing calls of application program by inserting monitoring routines into the executable version and redirecting calls to the monitoring routines
US5563998A (en) 1990-10-19 1996-10-08 Moore Business Forms, Inc. Forms automation system implementation
JPH0772870B2 (en) * 1990-12-21 1995-08-02 インターナショナル・ビジネス・マシーンズ・コーポレイション Method for automated production of structural inspection panels
US5301320A (en) * 1991-06-28 1994-04-05 Digital Equipment Corporation Workflow management and control system
WO1993012488A1 (en) * 1991-12-13 1993-06-24 White Leonard R Measurement analysis software system and method
US5592675A (en) 1992-01-08 1997-01-07 Hitachi, Ltd. Computer controlled method and system capable of preserving information representing plural work states and recovering the work states
JP3343949B2 (en) * 1992-08-31 2002-11-11 株式会社日立製作所 Distributed information processing system
US5630069A (en) * 1993-01-15 1997-05-13 Action Technologies, Inc. Method and apparatus for creating workflow maps of business processes
US5752034A (en) * 1993-01-15 1998-05-12 Texas Instruments Incorporated Apparatus and method for providing an event detection notification service via an in-line wrapper sentry for a programming language
US5386551A (en) * 1993-04-16 1995-01-31 Storage Technology Corporation Deferred resource recovery
DE4497149T1 (en) 1993-09-24 1996-10-17 Oracle Corp Method and device for replicating data
US6920467B1 (en) * 1993-11-26 2005-07-19 Canon Kabushiki Kaisha Avoiding unwanted side-effects in the updating of transient data
US5828883A (en) 1994-03-31 1998-10-27 Lucent Technologies, Inc. Call path refinement profiles
EP0754321B1 (en) 1994-04-05 2000-09-06 Intel Corporation Method and appartus for monitoring and controlling programs in a network
US5721913A (en) * 1994-05-05 1998-02-24 Lucent Technologies Inc. Integrated activity management system
US5704366A (en) * 1994-05-23 1998-01-06 Enact Health Management Systems System for monitoring and reporting medical measurements
US5566297A (en) 1994-06-16 1996-10-15 International Business Machines Corporation Non-disruptive recovery from file server failure in a highly available file system for clustered computing environments
US5768506A (en) * 1994-09-30 1998-06-16 Hewlett-Packard Co. Method and apparatus for distributed workflow building blocks of process definition, initialization and execution
US5594863A (en) * 1995-06-26 1997-01-14 Novell, Inc. Method and apparatus for network file recovery
US5701471A (en) 1995-07-05 1997-12-23 Sun Microsystems, Inc. System and method for testing multiple database management systems
US5655074A (en) * 1995-07-06 1997-08-05 Bell Communications Research, Inc. Method and system for conducting statistical quality analysis of a complex system
GB2303979B (en) * 1995-08-02 2000-03-29 Mitsubishi Electric Corp A control system and control method for uninterruptible power supply
US6067412A (en) * 1995-08-17 2000-05-23 Microsoft Corporation Automatic bottleneck detection by means of workload reconstruction from performance measurements
US5748878A (en) * 1995-09-11 1998-05-05 Applied Microsystems, Inc. Method and apparatus for analyzing software executed in embedded systems
US5630047A (en) * 1995-09-12 1997-05-13 Lucent Technologies Inc. Method for software error recovery using consistent global checkpoints
US5721914A (en) * 1995-09-14 1998-02-24 Mci Corporation System and method for hierarchical data distribution
US5784562A (en) * 1995-10-10 1998-07-21 U S West Advanced Technologies, Inc. System for using a dialog session context to process electronic forms data on the world wide web
US6477471B1 (en) 1995-10-30 2002-11-05 Texas Instruments Incorporated Product defect predictive engine
US6029002A (en) * 1995-10-31 2000-02-22 Peritus Software Services, Inc. Method and apparatus for analyzing computer code using weakest precondition
US5920719A (en) * 1995-11-06 1999-07-06 Apple Computer, Inc. Extensible performance statistics and tracing registration architecture
US6167534A (en) 1995-11-24 2000-12-26 Rational Software Corporation Load test system and method
US5712971A (en) * 1995-12-11 1998-01-27 Ab Initio Software Corporation Methods and systems for reconstructing the state of a computation
US5799297A (en) * 1995-12-15 1998-08-25 Ncr Corporation Task workflow management system and method including an external program execution feature
US5758061A (en) * 1995-12-15 1998-05-26 Plum; Thomas S. Computer software testing method and apparatus
US6584447B1 (en) * 1996-01-18 2003-06-24 Planalytics, Inc. Method and computer program product for weather adapted, consumer event planning
US6058393A (en) * 1996-02-23 2000-05-02 International Business Machines Corporation Dynamic connection to a remote tool in a distributed processing system environment used for debugging
US6279039B1 (en) * 1996-04-03 2001-08-21 Ncr Corporation Resource management method and apparatus for maximizing multimedia performance of open systems
US5842196A (en) 1996-04-03 1998-11-24 Sybase, Inc. Database system with improved methods for updating records
US5960445A (en) 1996-04-24 1999-09-28 Sony Corporation Information processor, method of updating a program and information processing system
US6028938A (en) * 1996-04-30 2000-02-22 Shana Corporation Secure electronic forms permitting layout revision
US5940074A (en) * 1996-06-03 1999-08-17 Webtv Networks, Inc. Remote upgrade of software over a network
US5812857A (en) * 1996-08-28 1998-09-22 Extended Systems, Inc. Field configurable embedded computer system
US5884037A (en) * 1996-10-21 1999-03-16 International Business Machines Corporation System for allocation of network resources using an autoregressive integrated moving average method
US6513154B1 (en) * 1996-10-21 2003-01-28 John R. Porterfield System and method for testing of computer programs in programming effort
US6061503A (en) * 1996-11-06 2000-05-09 Zenith Electronics Corporation Method for resolving conflicts among time-based data
US5995965A (en) 1996-11-18 1999-11-30 Humetrix, Inc. System and method for remotely accessing user data records
US6632248B1 (en) * 1996-12-06 2003-10-14 Microsoft Corporation Customization of network documents by accessing customization information on a server computer using uniquie user identifiers
US5905974A (en) * 1996-12-13 1999-05-18 Cantor Fitzgerald Securities Automated auction protocol processor
US6009274A (en) 1996-12-13 1999-12-28 3Com Corporation Method and apparatus for automatically updating software components on end systems over a network
US5845292A (en) 1996-12-16 1998-12-01 Lucent Technologies Inc. System and method for restoring a distributed checkpointed database
US5903897A (en) * 1996-12-18 1999-05-11 Alcatel Usa Sourcing, L.P. Software documentation release control system
US5960196A (en) 1996-12-18 1999-09-28 Alcatel Usa Sourcing, L.P. Software release metric reporting system and method
US6108673A (en) * 1997-02-25 2000-08-22 International Business Machines Corporation System for creating a form from a template that includes replication block
US5903721A (en) * 1997-03-13 1999-05-11 cha|Technologies Services, Inc. Method and system for secure online transaction processing
US6446125B1 (en) 1997-03-28 2002-09-03 Honeywell International Inc. Ripple scheduling for end-to-end global resource management
US5872976A (en) * 1997-04-01 1999-02-16 Landmark Systems Corporation Client-based system for monitoring the performance of application programs
US6145121A (en) 1997-04-17 2000-11-07 University Of Washington Trace based method for the analysis, benchmarking and tuning of object oriented databases and applications
US6105089A (en) * 1997-05-13 2000-08-15 Micron Electronics, Inc. Data management system for adding or exchanging components on a running computer
US6061686A (en) * 1997-06-26 2000-05-09 Digital Equipment Corporation Updating a copy of a remote document stored in a local computer system
US6003075A (en) 1997-07-07 1999-12-14 International Business Machines Corporation Enqueuing a configuration change in a network cluster and restore a prior configuration in a back up storage in reverse sequence ordered
US6073107A (en) * 1997-08-26 2000-06-06 Minkiewicz; Arlene F. Parametric software forecasting system and method
US6574661B1 (en) * 1997-09-26 2003-06-03 Mci Communications Corporation Integrated proxy interface for web based telecommunication toll-free network management using a network manager for downloading a call routing tree to client
US6026237A (en) * 1997-11-03 2000-02-15 International Business Machines Corporation System and method for dynamic modification of class files
US6237035B1 (en) * 1997-12-18 2001-05-22 International Business Machines Corporation System and method for preventing duplicate transactions in an internet browser/internet server environment
US6128708A (en) 1997-12-24 2000-10-03 Fitzpatrick; Gordon James Method for testing and mitigating shared memory contention in multi-processor systems
US6243862B1 (en) * 1998-01-23 2001-06-05 Unisys Corporation Methods and apparatus for testing components of a distributed transaction processing system
US6311327B1 (en) 1998-03-02 2001-10-30 Applied Microsystems Corp. Method and apparatus for analyzing software in a language-independent manner
US6519763B1 (en) * 1998-03-30 2003-02-11 Compuware Corporation Time management and task completion and prediction software
US6626953B2 (en) 1998-04-10 2003-09-30 Cisco Technology, Inc. System and method for retrieving software release information
JPH11306244A (en) * 1998-04-16 1999-11-05 Hitachi Ltd Work management system
US6101601A (en) * 1998-04-20 2000-08-08 International Business Machines Corporation Method and apparatus for hibernation within a distributed data processing system
US6175833B1 (en) * 1998-04-22 2001-01-16 Microsoft Corporation System and method for interactive live online voting with tallies for updating voting results
US6247029B1 (en) * 1998-05-01 2001-06-12 International Business Machines Corporation Web browser form enhancements
US6138112A (en) 1998-05-14 2000-10-24 Microsoft Corporation Test generator for database management systems
US6505176B2 (en) * 1998-06-12 2003-01-07 First American Credit Management Solutions, Inc. Workflow management system for an automated credit application system
US6182142B1 (en) * 1998-07-10 2001-01-30 Encommerce, Inc. Distributed access management of information resources
US6237143B1 (en) * 1998-09-17 2001-05-22 Unisys Corp. Method and system for monitoring and capturing all file usage of a software tool
US6363499B1 (en) * 1998-09-21 2002-03-26 Microsoft Corporation Method and system for restoring a computer to its original state after an unsuccessful installation attempt
US6985953B1 (en) 1998-11-30 2006-01-10 George Mason University System and apparatus for storage and transfer of secure data on web
US6269479B1 (en) * 1998-11-30 2001-07-31 Unisys Corporation Method and computer program product for evaluating the performance of an object-oriented application program
US7085997B1 (en) * 1998-12-08 2006-08-01 Yodlee.Com Network-based bookmark management and web-summary system
US6405250B1 (en) * 1999-01-25 2002-06-11 Lucent Technologies Inc. Network management system based on passive monitoring and proactive management for formulation behavior state transition models
US6601018B1 (en) * 1999-02-04 2003-07-29 International Business Machines Corporation Automatic test framework system and method in software component testing
US6470464B2 (en) 1999-02-23 2002-10-22 International Business Machines Corporation System and method for predicting computer system performance and for making recommendations for improving its performance
US6438749B1 (en) * 1999-03-03 2002-08-20 Microsoft Corporation Method and system for restoring a computer to its original state after an unsuccessful patch installation attempt
US6430687B1 (en) * 1999-04-15 2002-08-06 International Business Machines Corporation Boot sequence for a network computer including prioritized scheduling of boot code retrieval
US6526443B1 (en) * 1999-05-12 2003-02-25 Sandia Corporation Method and apparatus for managing transactions with connected computers
US6467052B1 (en) 1999-06-03 2002-10-15 Microsoft Corporation Method and apparatus for analyzing performance of data processing system
US6463454B1 (en) 1999-06-17 2002-10-08 International Business Machines Corporation System and method for integrated load distribution and resource management on internet environment
US6466980B1 (en) 1999-06-17 2002-10-15 International Business Machines Corporation System and method for capacity shaping in an internet environment
US6601233B1 (en) * 1999-07-30 2003-07-29 Accenture Llp Business components framework
US6088700A (en) * 1999-08-06 2000-07-11 Larsen; Kenneth N. Automated forms completion for global information network applications
US6934934B1 (en) * 1999-08-30 2005-08-23 Empirix Inc. Method and system for software object testing
US6405364B1 (en) * 1999-08-31 2002-06-11 Accenture Llp Building techniques in a development architecture framework
US6546506B1 (en) * 1999-09-10 2003-04-08 International Business Machines Corporation Technique for automatically generating a software test plan
US6363524B1 (en) * 1999-09-10 2002-03-26 Hewlett-Packard Company System and method for assessing the need for installing software patches in a computer system
US6301701B1 (en) 1999-11-10 2001-10-09 Tenfold Corporation Method for computer-assisted testing of software application components
US6629266B1 (en) 1999-11-17 2003-09-30 International Business Machines Corporation Method and system for transparent symptom-based selective software rejuvenation
US20020133593A1 (en) 2000-03-03 2002-09-19 Johnson Scott C. Systems and methods for the deterministic management of information
US6820088B1 (en) 2000-04-10 2004-11-16 Research In Motion Limited System and method for synchronizing data records between multiple databases
US6411910B1 (en) * 2000-04-26 2002-06-25 American Power Conversion System and method for estimating power availability
US6578004B1 (en) * 2000-04-27 2003-06-10 Prosight, Ltd. Method and apparatus for facilitating management of information technology investment
US20020016818A1 (en) * 2000-05-11 2002-02-07 Shekhar Kirani System and methodology for optimizing delivery of email attachments for disparate devices
EP1410281A2 (en) 2000-07-10 2004-04-21 BMC Software, Inc. System and method of enterprise systems and business impact management
US7317732B2 (en) * 2000-09-28 2008-01-08 Teridian Semiconductor, Corp. Method and apparatus for handling link suspend pulse and silent line state transitions of a network device
US6601017B1 (en) * 2000-11-09 2003-07-29 Ge Financial Assurance Holdings, Inc. Process and system for quality assurance for software
US6687817B1 (en) * 2000-11-14 2004-02-03 Sun Microsystems, Inc. Configuration of a network device via the network
US20020143929A1 (en) 2000-12-07 2002-10-03 Maltz David A. Method and system for collection and storage of traffic data from heterogeneous network elements in a computer network
US20030041000A1 (en) * 2000-12-18 2003-02-27 Paul Zajac System and method for providing a graphical user interface for a multi-interface financial transaction system
US7185364B2 (en) * 2001-03-21 2007-02-27 Oracle International Corporation Access system interface
TW540205B (en) 2001-02-27 2003-07-01 Ind Tech Res Inst Real-time scheduling mechanism capable of controlling quality of service
GB2373069B (en) 2001-03-05 2005-03-23 Ibm Method, apparatus and computer program product for integrating heterogeneous systems
US7761288B2 (en) 2001-04-30 2010-07-20 Siebel Systems, Inc. Polylingual simultaneous shipping of software
US20020194370A1 (en) 2001-05-04 2002-12-19 Voge Brendan Alexander Reliable links for high performance network protocols
US7610228B2 (en) * 2001-06-29 2009-10-27 International Business Machines Corporation Automated service level management in financial terms
US20030018952A1 (en) * 2001-07-13 2003-01-23 Roetzheim William H. System and method to estimate resource usage for a software development project
US20030033586A1 (en) * 2001-08-09 2003-02-13 James Lawler Automated system and method for software application quantification
US7337124B2 (en) 2001-08-29 2008-02-26 International Business Machines Corporation Method and system for a quality software management process
CA2357937A1 (en) * 2001-09-28 2003-03-28 Ibm Canada Limited-Ibm Canada Limitee Database diagnostic system and method
US7632101B2 (en) * 2001-10-05 2009-12-15 Vision Works Ip Corporation Method and apparatus for periodically questioning a user using a computer system or other device to facilitate memorization and learning of information
WO2003032125A2 (en) * 2001-10-11 2003-04-17 Visualsciences, Llc System, method, and computer program product for processing and visualization of information
JP2003196096A (en) * 2001-12-07 2003-07-11 Internatl Business Mach Corp <Ibm> Computer system, its starting control method and program
US20030120539A1 (en) * 2001-12-24 2003-06-26 Nicolas Kourim System for monitoring and analyzing the performance of information systems and their impact on business processes
US20030167223A1 (en) * 2002-03-01 2003-09-04 Financial Fusion, Inc., A Wholly-Owned Subsidiary Of Sybase, Inc. System with methodology for improved transmission of financial information
US20030225663A1 (en) 2002-04-01 2003-12-04 Horan James P. Open platform system and method
US20030225662A1 (en) 2002-04-01 2003-12-04 Horan James P. Managed asset platform system and method
CA2381596A1 (en) 2002-04-12 2003-10-12 Ibm Canada Limited-Ibm Canada Limitee Generating and managing test plans for testing computer software
US20030212518A1 (en) 2002-05-09 2003-11-13 Johnson & Johnson System and method for quality performance evaluation and reporting
US7228461B2 (en) * 2003-01-09 2007-06-05 Siemens Energy & Automation, Inc. System, method, and user interface for acceptance testing
US20050055555A1 (en) * 2003-09-05 2005-03-10 Rao Srinivasan N. Single sign-on authentication system
US20050071807A1 (en) * 2003-09-29 2005-03-31 Aura Yanavi Methods and systems for predicting software defects in an upcoming software release

Patent Citations (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3316395A (en) * 1963-05-23 1967-04-25 Credit Corp Comp Credit risk computer
US3634669A (en) * 1969-07-16 1972-01-11 Aero Flow Dynamics Inc Analog computation of insurance and investment quantities
US4594663A (en) * 1982-07-09 1986-06-10 Omron Tateisi Electronics Co. Credit transaction processing system
US4598367A (en) * 1983-11-09 1986-07-01 Financial Design Systems, Inc. Financial quotation system using synthesized speech
US4642768A (en) * 1984-03-08 1987-02-10 Roberts Peter A Methods and apparatus for funding future liability of uncertain cost
US4739478A (en) * 1984-11-21 1988-04-19 Lazard Freres & Co. Methods and apparatus for restructuring debt obligations
US4736294A (en) * 1985-01-11 1988-04-05 The Royal Bank Of Canada Data processing methods and apparatus for managing vehicle financing
US4760604A (en) * 1985-02-15 1988-07-26 Nestor, Inc. Parallel, multi-unit, adaptive, nonlinear pattern class separator and identifier
US4812628A (en) * 1985-05-02 1989-03-14 Visa International Service Association Transaction system with off-line risk assessment
US4914587A (en) * 1985-07-01 1990-04-03 Chrysler First Information Technologies, Inc. Financial data processing system with distributed data input devices and method of use
US5227874A (en) * 1986-03-10 1993-07-13 Kohorn H Von Method for measuring the effectiveness of stimuli on decisions of shoppers
US4831526A (en) * 1986-04-22 1989-05-16 The Chubb Corporation Computerized insurance premium quote request and policy issuance system
US5911135A (en) * 1987-04-15 1999-06-08 Proprietary Financial Products, Inc. System for managing financial accounts by a priority allocation of funds among accounts
US5875437A (en) * 1987-04-15 1999-02-23 Proprietary Financial Products, Inc. System for the operation and management of one or more financial accounts through the use of a digital communication and computation system for exchange, investment and borrowing
US4866634A (en) * 1987-08-10 1989-09-12 Syntelligence Data-driven, functional expert system shell
US4897811A (en) * 1988-01-19 1990-01-30 Nestor, Inc. N-dimensional coulomb neural network which provides for cumulative learning of internal representations
US4964043A (en) * 1988-06-13 1990-10-16 Galvin Thomas M System for visualizing, identifying and ordering gearing configurations
US5054096A (en) * 1988-10-24 1991-10-01 Empire Blue Cross/Blue Shield Method and apparatus for converting documents into electronic data for transaction processing
US5983206A (en) * 1989-05-25 1999-11-09 Oppenheimer; Robert H. Computer system and computer-implemented process for implementing a mortgage partnership
US5321841A (en) * 1989-06-29 1994-06-14 Digital Equipment Corporation System for determining the rights of object access for a server process by combining them with the rights of the client process
US5220500A (en) * 1989-09-19 1993-06-15 Batterymarch Investment System Financial management system
US5262941A (en) * 1990-03-30 1993-11-16 Itt Corporation Expert credit recommendation method and system
US5231571A (en) * 1990-08-14 1993-07-27 Personal Financial Assistant, Inc. Personal financial assistant computer method
US5606496A (en) * 1990-08-14 1997-02-25 Aegis Technologies, Inc. Personal assistant computer method
US5274547A (en) * 1991-01-03 1993-12-28 Credco Of Washington, Inc. System for generating and transmitting credit reports
US5689649A (en) * 1991-03-01 1997-11-18 Altman; Robert System for operation of a combination mortgage, equity load and savings plan
US5206803A (en) * 1991-03-15 1993-04-27 Vitagliano Francis M System for enhanced management of pension-backed credit
US5481647A (en) * 1991-03-22 1996-01-02 Raff Enterprises, Inc. User adaptable expert system
US5444844A (en) * 1991-06-04 1995-08-22 Nsk Ltd. Figure drawing apparatus and inventory purchasing system using the same
US5278751A (en) * 1991-08-30 1994-01-11 International Business Machines Corporation Dynamic manufacturing process control
US5644493A (en) * 1991-08-30 1997-07-01 Nsk Ltd. Production information processing system
US5233547A (en) * 1991-11-12 1993-08-03 Ncr Corporation Electronic checking account apparatus and method having a digitizer to receive information as a check is being written
US5239462A (en) * 1992-02-25 1993-08-24 Creative Solutions Groups, Inc. Method and apparatus for automatically determining the approval status of a potential borrower
US5774882A (en) * 1992-03-12 1998-06-30 Keen; Regina D. Credit approval system
US5732397A (en) * 1992-03-16 1998-03-24 Lincoln National Risk Management, Inc. Automated decision-making arrangement
US5655085A (en) * 1992-08-17 1997-08-05 The Ryan Evalulife Systems, Inc. Computer system for automated comparing of universal life insurance policies based on selectable criteria
US5424938A (en) * 1992-10-13 1995-06-13 First Chicago Corporation Method and apparatus for providing access to a plurality of payment networks
US5802502A (en) * 1993-05-24 1998-09-01 British Telecommunications Public Limited Company System for selective communication connection based on transaction pricing signals
US5551021A (en) * 1993-07-30 1996-08-27 Olympus Optical Co., Ltd. Image storing managing apparatus and method for retreiving and displaying merchandise and customer specific sales information
US5845256A (en) * 1993-08-19 1998-12-01 John B. Pescitelli Interactive self-service vending system
US5870721A (en) * 1993-08-27 1999-02-09 Affinity Technology Group, Inc. System and method for real time loan approval
US5940811A (en) * 1993-08-27 1999-08-17 Affinity Technology Group, Inc. Closed loop financial transaction method and apparatus
US5844553A (en) * 1993-08-30 1998-12-01 Hewlett-Packard Company Mechanism to control and use window events among applications in concurrent computing
US5611052A (en) * 1993-11-01 1997-03-11 The Golden 1 Credit Union Lender direct credit evaluation and loan processing system
US5930776A (en) * 1993-11-01 1999-07-27 The Golden 1 Credit Union Lender direct credit evaluation and loan processing system
US5550734A (en) * 1993-12-23 1996-08-27 The Pharmacy Fund, Inc. Computerized healthcare accounts receivable purchasing collections securitization and management system
US5802251A (en) * 1993-12-30 1998-09-01 International Business Machines Corporation Method and system for reducing perplexity in speech recognition via caller identification
US5537315A (en) * 1994-03-23 1996-07-16 Mitcham; Martin K. Method and apparatus for issuing insurance from kiosk
US5523942A (en) * 1994-03-31 1996-06-04 New England Mutual Life Insurance Company Design grid for inputting insurance and investment product information in a computer system
US5832447A (en) * 1994-05-24 1998-11-03 Envoy Corporation Automated system and method for providing real-time verification of health insurance eligibility
US5797133A (en) * 1994-08-31 1998-08-18 Strategic Solutions Group, Inc Method for automatically determining the approval status of a potential borrower
US5838906A (en) * 1994-10-17 1998-11-17 The Regents Of The University Of California Distributed hypermedia method for automatically invoking external application providing interaction and display of embedded objects within a hypermedia document
US5870723A (en) * 1994-11-28 1999-02-09 Pare, Jr.; David Ferrin Tokenless biometric transaction authorization method and system
US5742775A (en) * 1995-01-18 1998-04-21 King; Douglas L. Method and apparatus of creating financial instrument and administering an adjustable rate loan system
US5696907A (en) * 1995-02-27 1997-12-09 General Electric Company System and method for performing risk and credit analysis of financial service applications
US5701400A (en) * 1995-03-08 1997-12-23 Amado; Carlos Armando Method and apparatus for applying if-then-else rules to data sets in a relational data base and generating from the results of application of said rules a database of diagnostics linked to said data sets to aid executive analysis of financial data
US5899982A (en) * 1995-03-08 1999-05-04 Huntington Bancshares Incorporated Bank-centric service platform, network and system
US5649116A (en) * 1995-03-30 1997-07-15 Servantis Systems, Inc. Integrated decision management system
US5926800A (en) * 1995-04-24 1999-07-20 Minerva, L.P. System and method for providing a line of credit secured by an assignment of a life insurance policy
US5699527A (en) * 1995-05-01 1997-12-16 Davidson; David Edward Method and system for processing loan
US5774883A (en) * 1995-05-25 1998-06-30 Andersen; Lloyd R. Method for selecting a seller's most profitable financing program
US5664115A (en) * 1995-06-07 1997-09-02 Fraser; Richard Interactive computer system to match buyers and sellers of real estate, businesses and other property using the internet
US5878403A (en) * 1995-09-12 1999-03-02 Cmsi Computer implemented automated credit application analysis and decision routing system
US5848427A (en) * 1995-09-14 1998-12-08 Fujitsu Limited Information changing system and method of sending information over a network to automatically change information output on a user terminal
US5717865A (en) * 1995-09-25 1998-02-10 Stratmann; William C. Method for assisting individuals in decision making processes
US5930764A (en) * 1995-10-17 1999-07-27 Citibank, N.A. Sales and marketing support system using a customer information database
US5715402A (en) * 1995-11-09 1998-02-03 Spot Metals Online Method and system for matching sellers and buyers of spot metals
US5809478A (en) * 1995-12-08 1998-09-15 Allstate Insurance Company Method for accessing and evaluating information for processing an application for insurance
US5970482A (en) * 1996-02-12 1999-10-19 Datamind Corporation System for data mining using neuroagents
US5758328A (en) * 1996-02-22 1998-05-26 Giovannoli; Joseph Computerized quotation system and method
US5842178A (en) * 1996-02-22 1998-11-24 Giovannoli; Joseph Computerized quotation system and method
US5987434A (en) * 1996-06-10 1999-11-16 Libman; Richard Marc Apparatus and method for transacting marketing and sales of financial products
US5897621A (en) * 1996-06-14 1999-04-27 Cybercash, Inc. System and method for multi-currency transactions
US5765144A (en) * 1996-06-24 1998-06-09 Merrill Lynch & Co., Inc. System for selecting liability products and preparing applications therefor
US5862223A (en) * 1996-07-24 1999-01-19 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically-assisted commercial network system designed to facilitate and support expert-based commerce
US5794207A (en) * 1996-09-04 1998-08-11 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers
US5966699A (en) * 1996-10-11 1999-10-12 Zandi; Richard System and method for conducting loan auction over computer network
US5815683A (en) * 1996-11-05 1998-09-29 Mentor Graphics Corporation Accessing a remote cad tool server
US5913202A (en) * 1996-12-03 1999-06-15 Fujitsu Limited Financial information intermediary system
US5930775A (en) * 1997-01-14 1999-07-27 Freddie Mac Method and apparatus for determining an optimal investment plan for distressed residential real estate loans
US5920848A (en) * 1997-02-12 1999-07-06 Citibank, N.A. Method and system for using intelligent agents for financial transactions, services, accounting, and advice
US5903881A (en) * 1997-06-05 1999-05-11 Intuit, Inc. Personal online banking with integrated online statement and checkbook user interface
US5970483A (en) * 1997-07-25 1999-10-19 Claritech Corporation Apparatus and methodology for submitting search queries
US5940812A (en) * 1997-08-19 1999-08-17 Loanmarket Resources, L.L.C. Apparatus and method for automatically matching a best available loan to a potential borrower via global telecommunications network
US5910988A (en) * 1997-08-27 1999-06-08 Csp Holdings, Inc. Remote image capture with centralized processing and storage
US5995947A (en) * 1997-09-12 1999-11-30 Imx Mortgage Exchange Interactive mortgage and loan information and real-time trading system
US5873096A (en) * 1997-10-08 1999-02-16 Siebel Systems, Inc. Method of maintaining a network of partially replicated database system
US5991750A (en) * 1997-10-24 1999-11-23 Ge Capital System and method for pre-authorization of individual account transactions
US5918217A (en) * 1997-12-10 1999-06-29 Financial Engines, Inc. User interface for a financial advisory system
US5963953A (en) * 1998-03-30 1999-10-05 Siebel Systems, Inc. Method, and system for product configuration
US20030216990A1 (en) * 1998-11-09 2003-11-20 Onecore Financial Network, Inc. Systems and methods for performing integrated financial transactions
US5987436A (en) * 1999-01-26 1999-11-16 Halbrook; W. Bracey Obligated investment system
US20020029194A1 (en) * 2000-09-07 2002-03-07 Richard Lewis System and method of managing financial transactions over an electronic network
US20020083213A1 (en) * 2000-09-18 2002-06-27 Oberstein Brien M. Method and system for simulating and certifying complex business applications
US20020073018A1 (en) * 2000-09-28 2002-06-13 Charles Mulinder Real-time trading system
US7237257B1 (en) * 2001-04-11 2007-06-26 Aol Llc Leveraging a persistent connection to access a secured service
US20030217166A1 (en) * 2002-05-17 2003-11-20 Mario Dal Canto System and method for provisioning universal stateless digital and computing services
US20030233583A1 (en) * 2002-06-13 2003-12-18 Carley Jeffrey Alan Secure remote management appliance
US7310659B1 (en) * 2003-06-27 2007-12-18 Sprint Communications Company L.P. Interface and method for extending a target application over an instant message link of a communication network

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105283888A (en) * 2013-06-12 2016-01-27 惠普发展公司,有限责任合伙企业 Distributed worker-sourced process engineering

Also Published As

Publication number Publication date
US20050204029A1 (en) 2005-09-15
US7702767B2 (en) 2010-04-20

Similar Documents

Publication Publication Date Title
US20100199279A1 (en) User connectivity process management system
RU2400814C2 (en) Hierarchical projects in system and method of project control supported by computer
US8645178B2 (en) Task management for a plurality of team members
US8554794B2 (en) System and method for enforcing privacy in social networks
US20140236649A1 (en) Method and Apparatus for Performing Remote Operations in an Issue Tracking Environment
US7469217B2 (en) Product toolkit system and method
US20040148214A1 (en) Workflow services architecture
US20020138582A1 (en) Methods and apparatus providing electronic messages that are linked and aggregated
US11784962B2 (en) Systems and methods for collaborative chat with non-native chat platforms
TW200841241A (en) Method for implementing management software, hardware with pre-configured software and implementing method thereof
US20040148213A1 (en) Automated workflow constraints
TW200525402A (en) Methods and apparatus for information hyperchain management for on-demand business collaboration
JP2005539324A (en) Presentation of process flow and choreography controller as a web service
US20040088300A1 (en) Management system for a contact centre
US20170357943A1 (en) Method and apparatus for integrating automated workforce management systems and work intermediation platforms
JP2012118674A (en) Method for making it possible to share local environment of application executed on client, and server and computer program thereof
Lewis Introductions.”
JP2008501158A (en) System and method for workflow-enabled link activation
Thakar et al. On composition of SOAP based and RESTful services
US9477941B2 (en) Genealogy system for interfacing with social networks
CN101894312B (en) Information exchange/share system, method thereof
EP3073769A1 (en) System and method for intermediating between subscriber devices and communication service providers
US8626557B2 (en) System and method of providing snapshot to support approval of workflow changes
US8117334B2 (en) System and methods for workflow management
KR20100053227A (en) Information exchange support system for collaborative design work

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION