A system, method and carrier medium for modeling a Financial service organization (fso) business in a computer software program and for storing the model of the fso business in a database. An object-oriented business model representing the fso may be created and stored in a business model database. The one or more business objects included in the business model may be configured to describe various products, methods, functions and properties associated with an fso. A process map business object may describe a process workflow. The process workflow may identify a sequence of tasks to be performed by an fso production system to process an fso transaction. The sequence of tasks associated with an fso transaction may be consistent with pre-defined business logic for the transaction. Selecting a task object from a plurality of task objects and transferring the task object to a process map display representing the process map business object may create the process workflow. Additional task objects may be transferred and connected to the transferred task objects in a manner consistent with the business logic. An fso production system, which may be configured to process fso transactions, may access the database to request data associated with a particular fso transaction. On receiving the requested data from the business model database, the fso production system may complete the processing of the fso transaction.
|
1. A method for defining a process map for processing a financial service organization business product transaction, the method comprising:
displaying a plurality of task objects on a computer display screen;
displaying a process map design palette on the computer display screen;
selecting a first task object from the displayed plurality of task objects;
adding the first task object to the process map design palette; and
storing the process map in a business model database;
wherein the process map stored in the business model database is configured for translation into a financial service organization production system database,
wherein the financial service organization production system database is configured for use in the financial service organization production system, and
wherein the financial service organization production system is configured to process business product transactions between a financial service organization and a financial service organization customer.
23. A carrier memory medium comprising program instructions, wherein the program instructions are executable having stored thereon, computer-executable instructions configured for execution by a computer system to implement the method of, to cause the computer system to perform acts comprising:
displaying a plurality of task objects on a computer display screen;
displaying a process map design palette on the computer display screen;
selecting a first task object from the displayed plurality of task objects;
adding the first task object to the process map design palette; and
storing the process map in a business model database;
wherein the process map stored in the business model database is configured for translation into a financial service organization production system database,
wherein the financial service organization production system database is configured for use in the financial service organization production system, and
wherein the financial service organization production system is configured to process business product transactions between a financial service organization and a financial service organization customer.
10. A system for processing fso transactions, the system comprising:
a computer program;
a computer system;
wherein the computer program is executable on the computer system to execute the method of:
displaying a plurality of task objects on a computer display screen;
displaying a process map design palette on the computer display screen;
selecting a first task object from the displayed plurality of task objects;
adding the first task object to the process map design palette; and
storing the process map in a business model database;
wherein the process map stored in the business model database is configured for translation into a financial service organization production system database,
wherein the financial service organization production system database is configured for use in the financial service organization production system, and
wherein the financial service organization production system is configured to process business product transactions between a financial service organization and a financial service organization customer.
2. The method of
3. The method of
4. The method of
selecting a second task object from the displayed plurality of task objects; and
adding the second task object to the process map design palette.
5. The method of
defining a processing path between the first task object and the second task object,
wherein the processing path describes a path for business product transactions to be passed from the first processing task to the second processing task in the financial service organization production system.
6. The method of
one or more output links, and
wherein defining the processing path between the first task object and the second task object comprises connecting a first output link of the first task object to the second task object.
7. The method of
selecting a third task object from the displayed plurality of task objects;
adding the third task object to the process map design palette; and
defining a processing path between the first task object and the third task object;
wherein defining the processing path between the first task object and the third task object comprises disconnecting the first output link of the first task object from the second task object and connecting the first output link of the first task object to the third task object.
8. The method of
selecting a third task object from the displayed plurality of task objects;
adding the third task object to the process map design palette; and
defining a processing path between the first task object and the third task object;
wherein the first task object is a decision task object configured to pass a business product transaction to one of the first and second tasks objects as a function of data relating to the financial service organization customer associated with the business product transaction.
9. The method of
11. The system of
12. The system of
13. The system of
selecting a second task object from the displayed plurality of task objects; and
adding the second task object to the process map design palette.
14. The system of
defining a processing path between the first task object and the second task object,
wherein the processing path describes a path for business product transactions to be passed from the first processing task to the second processing task in the financial service organization production system.
15. The system of
one or more output links, and
wherein defining the processing path between the first task object and the second task object comprises connecting a first output link of the first task object to the second task object.
16. The system of
selecting a third task object from the displayed plurality of task objects;
adding the third task object to the process map design palette; and
defining a processing path between the first task object and the third task object;
wherein defining the processing path between the first task object and the third task object comprises disconnecting the first output link of the first task object from the second task object and connecting the first output link of the first task object to the third task object.
17. The system of
selecting a third task object from the displayed plurality of task objects;
adding the third task object to the process map design palette; and
defining a processing path between the first task object and the third task object;
wherein the first task object is a decision task object configured to pass a business product transaction to one of the first and second tasks objects as a function of data relating to the financial service organization customer associated with the business product transaction.
18. The system of
19. The system of
21. The system of
24. The carrier memory medium of
25. The carrier memory medium of
26. The carrier memory medium of
selecting a second task object from the displayed plurality of task objects; and
adding the second task object to the process map design palette.
27. The carrier memory medium of
defining a processing path between the first task object and the second task object,
wherein the processing path describes a path for business product transactions to be passed from the first processing task to the second processing task in the financial service organization production system.
28. The carrier memory medium of
29. The carrier memory medium of
selecting a third task object from the displayed plurality of task objects;
adding the third task object to the process map design palette; and
defining a processing path between the first task object and the third task object;
wherein defining the processing path between the first task object and the third task object comprises disconnecting the first output link of the first task object from the second task object and connecting the first output link of the first task object to the third task object.
30. The carrier memory medium of
selecting a third task object from the displayed plurality of task objects;
adding the third task object to the process map design palette; and
defining a processing path between the first task object and the third task object;
wherein the first task object is a decision task object configured to pass a business product transaction to one of the first and second tasks objects as a function of data relating to the financial service organization customer associated with the business product transaction.
31. The carrier memory medium of
0. 32. The carrier medium of
|
This application claims the benefit of U.S. Provisional Application No. 60/151,031 entitled “Flow Designer For Establishing And Maintaining Assignment And Strategy Process Maps,” filed Aug. 27, 1999.
1. Field of the Invention
The present invention generally relates to computer software programs to be used in Financial Service Organizations. More particularly, the present invention relates to a system for modeling a Financial Service Organization (FSO) production system for processing FSO transactions.
2. Description of the Related Art
FSOs such as banks, credit unions, insurance companies, mutual fund companies, credit card companies, brokerage houses, etc., market many types of financial products to their customers, such as savings accounts, brokerage accounts, commercial loans, mortgage loans, auto loans, personal loans, and credit cards. To acquire a credit product, for example, a customer of a FSO is typically required to submit an application for the credit product. The FSO then follows an application processing procedure for the credit product to determine whether the application is approved or rejected.
The application procedure includes such steps as gathering financial related information of the customer applying for the credit product, requesting credit reports on the customer, and examining and scoring the credit product application to see if the customer's credit be opened for the assignment map object created in step 830.
In steps 834-846, task objects are added to the assignment map, resolved, and connected in an assignment flow. These steps may be iterative, with one or more task objects added, their properties resolved, connections made, more task objects added, and so on. Steps 834-846 may also be performed in other orders than shown in
In one embodiment of a flow designer, some tasks may be available only for account acquisition assignment and strategy maps, some tasks may be available only for account collections assignment and strategy maps, and some tasks may be available for both account acquisition and account collections assignment and strategy maps.
In step 834, one or more processing task objects may be added. Processing tasks may be configured to perform operations on one or more data elements. Examples of processing tasks include, but are not limited to: calculation tasks, which are configured to perform mathematical operations on one or more data elements or data constants, and; score tasks, which grade or rank one or more data elements. In step 836, decision task objects may be added. Decision task objects provide branching within an assignment or strategy map by comparing data elements or results of previous tasks or operations within the decision task object. Decision task objects manage the flow of business product transactions in an assignment or strategy map by representing possible outcomes of conditions, and the desired result(s) that correspond to the conditions.
In step 838, invoke external interface task objects may be added. Invoke external interface task objects launch an external interface, which may have been previously defined in business modeler. External interfaces send and receive information from outside sources such as credit bureaus and FSO mainframe systems. In step 840, send to organizational unit task objects may be added. Send to organizational unit task objects may be configured to assign a business product transaction to another organizational unit for processing. A send to organizational unit task object may be invoked when a decision task object has determined that the organizational unit that is the parent of this assignment task object is not the preferred organizational unit for processing a business product transaction. In step 842, send to strategy task objects may be added. A send to strategy task object may be resolved to send a business product transaction to a strategy map as illustrated in
Other types of task objects may be added to an assignment map. Examples of other types of task objects that may be added to an assignment map include, but are not limited to, the following. Champion challenger task objects may be configured to assign business product transactions with similar characteristics to different strategies based upon a random sampling scheme, and may be used to measure and compare the results of alternative strategies.
In step 844, task objects that have been added to the assignment map may be resolved. In one embodiment of a flow designer program, resolution of tasks objects may involve selecting the added task object and opening the property sheet for the task object. In one embodiment of a flow designer program, a task object resolution property sheet may be opened automatically when a task object is added. Data elements included as properties of the task object may be resolved during the resolution of the task. During resolution of a task object, the source(s) from which the task object is to receive data during processing is specified. The sources may be from data elements included in other business objects and document templates previously defined in business modeler, from external sources through external interfaces, from a list of predefined values in a menu, or from other sources.
In step 846, the business product transaction processing flow for the assignment map may be defined by connecting outputs of task objects to inputs of other task objects. In one embodiment of a flow designer program, task objects may have one or more arrows projecting from the bottom, representing output links. Decision task objects may have two or more output links. Some task objects, such as send to organizational unit objects, may not have output links. In one embodiment of a flow designer program, to connect a first task object to a second task object, an arrow, or output link, on the first object may be dragged on the computer screen to contact the second object. In one embodiment of a flow designer program, all output links must be connected to task objects for the assignment map to be complete. In one embodiment of a flow designer program, circular links may not be allowed; that is, task objects may not be linked in a pattern in which a business product transaction may end up in a circular processing path.
Task objects may be added to the assignment map, resolved, and connected in a processing flow until the desired assignment map for assigning business product transactions is completed. At this point, the process goes to step 848. Here, the assignment map may be saved and closed. Saving the assignment map may include writing the assignment map object, and all the task objects added to the assignment map, to a business model database, as described in step 124 of
FIG. 3a—One Embodiment of a Business Modeler Display Screen with Business Model Objects
The business model objects defined for a business model may be displayed in object view 492. The objects may be displayed in a top-to-bottom sequence corresponding to the inheritance relationship or the hierarchical business relationship of the objects. In one embodiment, the business model objects may be displayed as icons representing the type of object, with the name of the object displayed to the right of the icon. Shown as an example are object 1 icon 472 with object 1 name 474, object 2 icon 476 with object 2 name 478, object 3 icon 480 with object 3 name 482, object 4 icon 484 with object 4 name 486, and object 5 icon 488 with object 5 name 490. An object expansion icon 492 may be displayed to the left of each object icon. Object expansion icons 492 may be used to expand an object icon, that is, to show the children of the object icon. In one embodiment, an expanded object's expansion icon 492 may be displayed as a minus sign (−), and an unexpanded, or collapsed, object's expansion icon 492 may be displayed as a plus sign (+). In this example, object 1 is expanded, showing object 2, object 3, and object 5 as children of the object. Object 2 is not expanded. In some embodiments, children objects' icons may be inset below and to the right of the parent object's icon. In some embodiments, lines 494 may be drawn between object expansion icons 492 and between object expansion icons 492 and object icons.
FIG. 3b—One Embodiment of a Business Modeler Display Screen with an Object Menu
FIG. 4—One Embodiment of a Business Model Object Property Sheet
Property names and values may be modified on the business model object property sheet 500. For example, property 1 value 514 may be selected and a new value entered in the field. Changing property 1 value 514 may result in a change in the inheritance indicator 524 for property 1. In some embodiments, property values may be selectable from a list of predefined values. In this example, a property value selection icon 526 is disposed to the right of property 3 value 522. Selecting property value selection icon 526 may result in a list of possible values for property 3 to be displayed for selection. In some embodiments, business model object property sheet 500 may include one or more buttons for controlling property sheet 500. The example in
FIG. 5a—Business Model Objects at the Highest Level of the Inheritance View
User objects 148 are shown as children of the root object. User objects may be defined at this level because user objects may be used to give employees of the business organization security access to functions of the business modeler and the production system. Properties of user objects may include user name, user title, password, and security information defining what facilities in the business modeler and the production system a particular user may access. FSO systems 150 may be the parent object of the account acquisition and account collections systems, which are in turn the parent objects of the organizational unit objects included in the business model.
FIG. 5b—Business Model Objects Representing One Embodiment of Organizational Units in the Inheritance View
As organizational units 154, 156, and 158 are of the same type, organizational units lower on the tree may inherit property values from their ancestor organizational units. Thus, organizational unit 158 may inherit property values from organizational units 154 and 156. An organizational unit may not inherit property values from its descendents. Thus, organizational unit 154 may not inherit property values from organizational units 156 or 158. A business model object may not inherit property values from siblings or siblings' descendents. Thus, organizational unit 160 may inherit property values from its ancestor organizational unit 154, but may not inherit property values from its sibling organizational unit 156 or organizational unit 156's child organizational unit 158. An object may be able to reference siblings or a sibling's descendents. Thus, organizational unit 160 may be able to reference property values of organizational units 156 and 158. Security features of business model objects may also be used to regulate referencing among business model objects. For example, security properties for a business model object may be set to deny referencing of one or more properties to siblings. Thus, security properties for organizational unit 160 may be set to prohibit organizational unit 156 from referencing organizational unit 160's properties.
FIG. 5c—One Embodiment of an Account Acquisition Organizational Unit in the Inheritance View
FIG. 5d—One Embodiment of an Account Collections Organizational Unit in the Inheritance View
FIG. 6a—One Embodiment of Business Model Objects at the Highest Level of the Business View
FIG. 6b—One Embodiment of an Account Acquisition Organizational Unit in the Business View
FIG. 6c—One Embodiment of an Account Collections Organizational Unit in the Business View
FIG. 7—One Embodiment of a Document Template Design Process
Examples of document templates that may be designed with a document template design process as illustrated in
FIG. 8a—High-Level Business Product Transaction Processing in an Embodiment of a Production System
FIG. 8b—Modeling High-Level Business Product Transaction Processing in an Embodiment of a Business Modeler System
In the assignment designer subsystem shown in
FIG. 9—A High-Level Assignment and Strategy Process in an Embodiment of a Production System
FIG. 10—An Example Master Assignment Model in an Embodiment of a Business Modeler System
In master assignment 340, the first task added may be start assignment task 342. Task 342 may be configured to gather data from internal (production system) and external (other system) sources. Decision task A 344 may be added to master assignment 340 and configured to evaluate one or more data elements in a business product transaction to determine the routing of the business product transaction. A send to organizational unit task 346 may be added to master assignment 340 and the property sheet of task 346 may be opened to specify what organizational unit to send a business product transaction to. In this example, the properties of task 346 are resolved to route a business product transaction to organizational unit B. An output node on task 344 is connected to an input node on task 346. On master assignment 340, the link between nodes may be signified by a line drawn between the output and input node.
Processing task A 348 and decision task B 352 may then be added to master assignment 340. Outputs from task 344 may be connected to inputs on task 348 and task 352. Send to strategy A task 350 may then be added to master assignment 340. The property sheet of task 350 may be resolved to route a business product transaction to a previously defined strategy A. Send to strategy task 354 and processing task B 356 may then be added to master assignment 340. Outputs from decision task 352 may then be connected to inputs on tasks 354 and 356. Send to strategy task 358 may be added to master assignment 340. An output from task 356 may be connected to an input on task 358. Finally, the property sheets of task 354 and 358 may be resolved to route a business product transaction to strategies B and C, respectively.
Note that the process described for
FIG. 11—An Example Strategy Model in an Embodiment of a Business Modeler System
In strategy 360, the first task added may be start strategy task 362. Task 362 may be configured to perform some initial processing on the data elements in a business product transaction. Decision task C 364 may be added to strategy 360 and configured to evaluate one or more data elements in a business product transaction to determine the routing of the business product transaction. A send to queue task 366 may be added to strategy 360 and the property sheet of task 366 may be opened to specify what queue to send a business product transaction to. In this example, the properties of task 366 are resolved to route a business product transaction to queue A. An output node on task 364 is connected to an input node on task 366.
Processing task C 368 and decision task D 372 may then be added to strategy 360. Outputs from task 364 may be connected to inputs on task 368 and task 372. End strategy 370 may then be added to strategy 360. An output from task 368 may be routed to an input on task 370. Send to queue task 374 and end strategy 376 may then be added to strategy 360. Outputs from task 372 may then be connected to inputs on tasks 374 and 376. The properties of task 374 may then be resolved to route a business product transaction to queue B.
FIG. 12—The Relationship Among Organizational Units in Customer Processing in an Embodiment of a Production System
FIG. 13—An Embodiment of a Database Store Process for Business Modeler Objects
Object store process 400 is aware of the business model objects included in the business model currently loaded in business modeler program 30's memory. Object store process 400 may iterate through the objects, decompose each object into its component properties, and store the objects' properties as records in business model database 40. The object property records in business model database 40 may include enough information to reconstruct the business model and all of the business model objects included in the business model in a subsequent execution of business modeler program 30.
FIG. 14—An Embodiment of a Process for Converting a Business Model Defined in an Embodiment of a Business Modeler System into a Production System Database
Production build 422 may include information describing the format of business model database 40 and production system database 420. In one embodiment, production build 422 may compare the business transaction processing business model described in business model database 40 with a previously implemented business transaction processing database stored in production system database 420. Production build 422 may search for differences between the new model and the previously implemented model. In one embodiment, production build 422 may create production build scripts 424 including instructions for updating production system database 420 to match the updated business model described in business model database 40. Script 424 may then be prepared for application to production system database 420 by a database administrator. Scripts 424 may then be executed to apply the updates to production system database 420. The execution of scripts 424 may be performed when the production system is offline and not accessing the database or scripts 424 may be executed when the production system is online. In another embodiment, production build 422 may directly update production system database 420, bypassing the creation of scripts 424. In yet another embodiment, a business model database 40 created in a business modeler system may be used directly as a production system database 420 without going through a production build process.
Production build 422 may also output display and printing templates 428 in response to the comparison between business model database 40 and production system database 420. Display and printing templates 428 may be used in a production system to display customer information including documents included in a business product transaction on client systems and to print documents on printers available to the production and client systems. Display and printing templates 428 may have a one-to-one correspondence to document template objects defined in the business modeler system.
FIG. 15—A Flowchart Describing an Example of a Business Product Transaction Processing Flow in an Embodiment of a Production System that was Modeled in an Embodiment of a Business Modeler System
Task 604 is configured as a starting task for assignment process 600. Assignment process 600 may be configured to process applications for a particular FSO product. Task 604 may be configured to accept an application for a product. In this example, task 604 is configured to accept a request for a loan application. Task 606 may be configured to send a loan application to a client system. Task 608 may be configured to accept a loan application with basic customer information filled in. Task 610 may be configured to invoke an external interface to the FSO's customer database to retrieve information on a customer and to map the retrieved customer information onto a loan application. Task 612 may be configured to send a partially completed loan application to a client system. Task 614 may be configured to accept a completed application from a client system. Task 616 is a decision task that may be configured to choose an appropriate strategy for a loan application based upon information on the loan application and any other customer information that is available. Task 618 may be one of several branches off task 616. Task 618 may be configured to send a loan application and all available information to a strategy, in this example strategy A 602.
Strategy process A 602 may start at task 620, which may be configured for receiving a loan application and associated customer information from an assignment process. Task 622 is a decision task, and may be configured to gather more information about a customer, perform calculations on data elements in a loan application, and score the loan application. Task 622 may then compare a score for a loan application against a loan accept/decline score constant to determine if the loan is approved. Task 624 may be one of several branches off task 622. Other branches may include a task to be invoked if a loan application is not approved. Task 624 may be configured to notify a client system that a loan application is approved. Task 626 may be configured to accept a loan acceptance confirmation message from a client system. Task 628 may be configured to invoke one or more external interfaces to FSO systems to inform the systems to implement and record a newly approved loan. Task 630 may be configured to clean up a production system by deleting any temporary files created in the production system during loan application processing.
FIG. 17—A Block Diagram of an Embodiment of a Production System Illustrating the Usage of a Production System Database
Referring to
Business product transaction processing program 714 may include one or more implementations of processing tasks. Processing tasks perform operations on work packets. A work packet may be defined as a collection of documents associated with a particular customer's business product transaction. Examples of operations that may be performed on work packets include, but are not limited to, adding documents to a work packet, modifying data elements in the documents, performing calculations with data elements, making decisions based upon data elements, invoking external interfaces, sending work packets to queues, and sending work packets to other organizational units.
Production system 700 may be described as a data-driven system. The processing tasks included in business product transaction processing program 714 are preprogrammed into the system. However, the actual paths through the processing tasks that transactions may take while being processed by business product transaction processing program 714 are not preprogrammed. Instead, the paths through the processing tasks are dynamically defined by the contents of the production system database 704 at runtime. The formats and contents of documents, display screens, and printed output may also be defined in production system database 704 or in display and printer templates 706 and may be dynamically accessed by business product transaction processing program 714 at runtime.
Referring to
Transaction router 712 may begin the processing of a business product transaction by sending the business product transaction to a first processing task in business product transaction processing program 714. When the first processing task completes, it may notify transaction router 712 that it has finished. The first processing task may also notify transaction router 712 of the next processing task for the business product transaction. Transaction router 712 may then send the business product transaction to the next processing task. Processing tasks may send feedback on the processing of the business product transaction to a client workstation that was the business product transaction source 710. An FSO employee may enter additional information in response to the feedback. Processing tasks may request and receive data from one or more of the FSO's databases external to the production system through external interfaces 722. Processing tasks may also request and receive data from one or more sources external to the FSO through external interfaces 722. Examples of external data sources include, but are not limited to, credit bureaus and other FSOs. Processing tasks may also send correspondence documents to one or more external entities 726 through external interfaces 722. An example may be sending a letter to the customer associated with the business product transaction. Some processing tasks may be configured to delay the processing of the business product transaction for a length of time. An example may be delaying 30 days after sending a notice of delinquency before starting a next funds collections task.
The processing of the business product transaction continues until the transaction comes to a final resolution. If a business product transaction is successfully resolved automatically by the distributed transaction processing system 702, the results of the resolution may be reported back to the client workstation that was the business product transaction source 710. Documents associated with the business product transaction may be sent to FSO databases 724 through external interfaces 722. If a business product transaction cannot be successfully resolved automatically by the distributed transaction processing system 702, the transaction may be sent to a manual transaction processing queue 716 for manual processing by an FSO employee 720 working at manual transaction processing client workstation 718. Customer documents may be sent to an external entity if the business product transaction was not successfully resolved automatically. An example may be reporting a customer to an external collections agency for funds collection if the FSO's internal collections strategy did not succeed with the customer. After resolution of a transaction, FSO databases 724 may be updated with documents associated with the business product transaction through external interfaces 722.
FIGS. 18a and 18b—One Embodiment of a Data-Driven Business Product Transaction Processing Program
Turning to
In this example, task A 752 may be the first task. Processing task A 752 may access database 704 during execution of processing steps to read data values, data formats, or other data as required. When processing task A 752 completes its processing steps, it may access database 704 to determine the next processing task for this transaction type. In this example, decision task D 758 may be the next processing task. When decision task D completes, it may access database 704 to determine a next processing task, and may use transaction data along with the transaction type to choose among multiple possible next processing tasks for this transaction type. For example, a decision task may compare a customer's age to a customer age limit stored in database 704, send the transaction to task B 754 if the customer is under 30, or send the transaction to task C 756 if the customer is 30 or above.
FIG. 19—An Illustration of One Embodiment of a Flow Designer Window
Palette 900 may be used to display and edit assignment and strategy maps. Task object icons may be selected from task toolbar 902 and added to palette 900. A task object icon may be resolved by selecting the task object icon and opening the property sheet for the task object. Added task object icons may include one or more arrows or output links 916 for connecting one task object icon to another task object icon. The connection of task object icons in this manner defines the processing flow in assignment and strategy maps. In this illustration, one copy of each task object type 908, 910, 912, and 914 have been added and linked. Task object icon 908 illustrates a task object type with one output link, such as a calculation task object. Task object 910 illustrates a task object type with more than one output link, such as decision task objects. Task object 922 illustrates another task object type with one output link, but where the output link is not yet connected to another task object. Task objects 924 and 926 illustrate task object types with no output links, such as completion task objects. Task objects 924 and 926 are also used to illustrate that more than one object of a particular type may be added to a map.
In one embodiment, circular links among objects may not be allowed. For example, in
Edit toolbar 904 may include one or more edit tool icons 906. Different edit tools may be selected to perform editing tasks on the map currently displayed in template 900. Examples of edit tools include, but are not limited to: a delete tool for deleting one or more selected task objects on a map, a clear links tool to remove the links from one or more selected task objects on a map, grid and alignment tools for aligning task objects on a map, and a validate tool for validating the map. Validating a map may include verifying that all output links are attached to a task object, that all task objects are linked to at least one other task object, and that the properties of all task objects have been resolved.
Various embodiments further include receiving or storing instructions and/or data implemented in accordance with the foregoing description upon a carrier medium. Suitable carrier media include memory media or storage media such as magnetic or optical media, e.g., disk or CD-ROM, as well as signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as networks and/or a wireless link.
Although the system and method of the present invention have been described in connection with several embodiments, the invention is not intended to be limited to the specific forms set forth herein, but on the contrary, it is intended to cover such alternatives, modifications, and equivalents as can be reasonably included within the spirit and scope of the invention as defined by the appended claims.
Patent | Priority | Assignee | Title |
8473317, | Mar 31 2008 | SAP SE | Managing consistent interfaces for service part business objects across heterogeneous systems |
8554637, | Sep 30 2009 | SAP SE | Managing consistent interfaces for merchandising business objects across heterogeneous systems |
8601490, | Jul 28 2011 | SAP SE | Managing consistent interfaces for business rule business object across heterogeneous systems |
8615451, | Jun 28 2012 | SAP SE | Consistent interface for goods and activity confirmation |
8671041, | Dec 12 2008 | SAP SE | Managing consistent interfaces for credit portfolio business objects across heterogeneous systems |
8694397, | Jun 04 2004 | SAP SE | Consistent set of interfaces derived from a business object model |
8725654, | Jul 28 2011 | SAP SE | Managing consistent interfaces for employee data replication business objects across heterogeneous systems |
8732083, | Jun 15 2010 | SAP SE | Managing consistent interfaces for number range, number range profile, payment card payment authorisation, and product template template business objects across heterogeneous systems |
8756135, | Jun 28 2012 | SAP SE | Consistent interface for product valuation data and product valuation level |
8756274, | Feb 16 2012 | SAP SE | Consistent interface for sales territory message type set 1 |
8762453, | Feb 16 2012 | SAP SE | Consistent interface for feed collaboration group and feed event subscription |
8762454, | Feb 16 2012 | SAP SE | Consistent interface for flag and tag |
8775280, | Jul 28 2011 | SAP SE | Managing consistent interfaces for financial business objects across heterogeneous systems |
8799115, | Feb 28 2008 | SAP SE | Managing consistent interfaces for business objects across heterogeneous systems |
8924269, | May 13 2006 | SAP SE | Consistent set of interfaces derived from a business object model |
8949855, | Jun 28 2012 | SAP SE | Consistent interface for address snapshot and approval process definition |
8984050, | Feb 16 2012 | SAP SE | Consistent interface for sales territory message type set 2 |
9043236, | Aug 22 2012 | SAP SE | Consistent interface for financial instrument impairment attribute values analytical result |
9047578, | Jun 26 2008 | SAP SE | Consistent set of interfaces for business objects across heterogeneous systems |
9063753, | Jun 22 2010 | SAP SE | Scripting framework for business objects |
9076112, | Aug 22 2012 | SAP SE | Consistent interface for financial instrument impairment expected cash flow analytical result |
9135585, | Jun 15 2010 | SAP SE | Managing consistent interfaces for property library, property list template, quantity conversion virtual object, and supplier property specification business objects across heterogeneous systems |
9191343, | Mar 15 2013 | SAP SE | Consistent interface for appointment activity business object |
9191357, | Mar 15 2013 | SAP SE | Consistent interface for email activity business object |
9232368, | Feb 16 2012 | SAP SE | Consistent interface for user feed administrator, user feed event link and user feed settings |
9237425, | Feb 16 2012 | SAP SE | Consistent interface for feed event, feed event document and feed event type |
9246869, | Jun 28 2012 | SAP SE | Consistent interface for opportunity |
9261950, | Jun 28 2012 | SAP SE | Consistent interface for document output request |
9367826, | Jun 28 2012 | SAP SE | Consistent interface for entitlement product |
9400998, | Jun 28 2012 | SAP SE | Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule |
9436437, | Dec 17 2010 | Microsoft Technology Licensing, LLC | Creation, editing and navigation of diagrams |
9547833, | Aug 22 2012 | SAP SE | Consistent interface for financial instrument impairment calculation |
Patent | Priority | Assignee | Title |
4878167, | Jun 30 1986 | International Business Machines Corporation | Method for managing reuse of hard log space by mapping log data during state changes and discarding the log data |
5099422, | Apr 10 1986 | RPX Corporation | Compiling system and method of producing individually customized recording media |
5191522, | Jan 18 1990 | HARTFORD LIFE INSURANCE COMPANY | Integrated group insurance information processing and reporting system based upon an enterprise-wide data structure |
5201044, | Apr 16 1990 | International Business Machines Corporation | Data processing method for file status recovery includes providing a log file of atomic transactions that may span both volatile and non volatile memory |
5233513, | Dec 28 1989 | SOLUTION STRATEGIES, LLC | Business modeling, software engineering and prototyping method and apparatus |
5386566, | Mar 20 1991 | Hitachi, Ltd.; Hitachi VLSI Engineering Corporation | Inter-processor communication method for transmitting data and processor dependent information predetermined for a receiving process of another processor |
5394555, | Dec 23 1992 | BULL HN INFORMATION SYSTEMS INC | Multi-node cluster computer system incorporating an external coherency unit at each node to insure integrity of information stored in a shared, distributed memory |
5434994, | May 23 1994 | International Business Machines Corporation | System and method for maintaining replicated data coherency in a data processing system |
5455947, | May 28 1992 | Fujitsu Limited | Log file control system in a complex system |
5483632, | Sep 03 1988 | Hitachi, Ltd. | Method and system of help-information control |
5499330, | Sep 17 1993 | SAMSUNG ELECTRONICS CO , LTD | Document display system for organizing and displaying documents as screen objects organized along strand paths |
5504674, | Feb 19 1991 | CCC INFORMATION SERVICES, INC | Insurance claims estimate, text, and graphics network and method |
5523942, | Mar 31 1994 | Metropolitan Life Insurance Company; NEW ENGLAND LIFE INSURANCE COMPANY | Design grid for inputting insurance and investment product information in a computer system |
5530861, | Aug 26 1991 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Process enaction and tool integration via a task oriented paradigm |
5550976, | Dec 08 1992 | NMETRIC, LLC | Decentralized distributed asynchronous object oriented system and method for electronic data management, storage, and communication |
5586310, | Dec 04 1992 | International Business Machines Corporation | System for distributed database replicated read with exclusive central server transfer of primary copies |
5630069, | Jan 15 1993 | ACTION TECHNOLOGIES, INC | Method and apparatus for creating workflow maps of business processes |
5638508, | Jul 17 1987 | Hitachi, Ltd.; Hitachi Micro Computer Engineering, Ltd. | Method and a system for processing a log record |
5689706, | Jun 18 1993 | Alcatel Lucent | Distributed systems with replicated files |
5699527, | May 01 1995 | AUCTNYC 1 LLC | Method and system for processing loan |
5734837, | Jan 14 1994 | ACTION TECHNOLOGIES, INC | Method and apparatus for building business process applications in terms of its workflows |
5745901, | Nov 08 1994 | GLOBAL 360, INC | Workflow initiated by graphical symbols |
5764989, | Feb 29 1996 | Open Invention Network, LLC | Interactive software development system |
5768505, | Dec 19 1995 | International Business Machines Corporation | Object oriented mail server framework mechanism |
5768506, | Sep 30 1994 | PTC INC | Method and apparatus for distributed workflow building blocks of process definition, initialization and execution |
5774661, | Apr 18 1995 | HTA TECHNOLOGY INVESTMENTS LLC | Rule engine interface for a visual workflow builder |
5797134, | Jan 29 1996 | Progressive Casualty Insurance Company | Motor vehicle monitoring system for determining a cost of insurance |
5832481, | Aug 20 1991 | Powersoft Corporation | Reuseable and modifiable interface object |
5870711, | Dec 11 1995 | SABRE GLBL INC | Method and system for management of cargo claims |
5873066, | Feb 10 1997 | Insurance Company of North America | System for electronically managing and documenting the underwriting of an excess casualty insurance policy |
5878403, | Sep 12 1995 | DEALERTRACK, INC | Computer implemented automated credit application analysis and decision routing system |
5900870, | Jun 30 1989 | Massachusetts Institute of Technology | Object-oriented computer user interface |
5907848, | Mar 14 1997 | VISION SOLUTIONS, INC | Method and system for defining transactions from a database log |
5918207, | May 01 1996 | ENT SERVICES DEVELOPMENT CORPORATION LP | Process and system for predictive resource planning |
5928082, | May 06 1992 | LUCKY TAB HOLDINGS, LLC | Voucher and game ticket combination and apparatus and method used therewith |
5930759, | Apr 30 1996 | Symbol Technologies, LLC | Method and system for processing health care electronic data transactions |
5930776, | Nov 01 1993 | CU DIRECT CORPORATION | Lender direct credit evaluation and loan processing system |
5933816, | Oct 31 1996 | CITICORP CREDIT SERVICES, INC USA | System and method for delivering financial services |
5937189, | Nov 12 1996 | International Business Machines Corporation | Object oriented framework mechanism for determining configuration relations |
5950169, | May 19 1993 | CCC INFORMATION SERVICES INC | System and method for managing insurance claim processing |
5987434, | Jun 10 1996 | RPX Corporation | Apparatus and method for transacting marketing and sales of financial products |
5991733, | Mar 22 1996 | HARTFORD FIRE INSURANCE COMPANY | Method and computerized system for managing insurance receivable accounts |
6023572, | May 12 1998 | GOOGLE LLC | Computer based system and method for modeling activities of people in an organization |
6023578, | May 09 1997 | International Business Machines Corporation | Systems, methods and computer program products for generating an object oriented application for an object oriented environment |
6035300, | Dec 15 1995 | IBM Corporation | Method and apparatus for generating a user interface from the entity/attribute/relationship model of a database |
6038393, | Sep 22 1997 | Unisys Corporation | Software development tool to accept object modeling data from a wide variety of other vendors and filter the format into a format that is able to be stored in OMG compliant UML representation |
6049665, | Oct 15 1996 | GOOGLE LLC | Object oriented framework mechanism for order processing including pre-defined extensible classes for defining an order processing environment |
6061057, | Mar 10 1997 | VENTURE INVESTMENT MANAGEMENT COMPANY LLC | Network commercial system using visual link objects |
6064983, | Mar 22 1996 | Koehler Consulting, Inc.; KOEHLER CONSULTING, INC | System for performing tax computations |
6081832, | Dec 19 1995 | International Business Machines Corporation | Object oriented mail server framework mechanism |
6092049, | Jun 30 1995 | Microsoft Technology Licensing, LLC | Method and apparatus for efficiently recommending items using automated collaborative filtering and feature-guided automated collaborative filtering |
6101481, | Jan 25 1996 | TASKEY PTY LTD | Task management system |
6105007, | Aug 27 1993 | DECISIONING COM, INC | Automatic financial account processing system |
6115690, | Dec 22 1997 | BIG BABOON, INC | Integrated business-to-business Web commerce and business automation system |
6119103, | May 27 1997 | Visa International Services Association | Financial risk prediction systems and methods therefor |
6122627, | May 09 1997 | International Business Machines Corporation | System, method, and program for object building in queries over object views |
6134582, | May 26 1998 | Microsoft Technology Licensing, LLC | System and method for managing electronic mail messages using a client-based database |
6134706, | Aug 14 1997 | International Business Machines Corporation | Software business objects in a multi-level organizational structure |
6163770, | Aug 25 1998 | FINANIAL GROWTH RESOURCES, INC ; MEGA GROUP INTERNATIONAL, LTD ; FINANCIAL GROWTH RESOURCES, INC ; MEGA GROUP INTERNTIONA, LTD | Computer apparatus and method for generating documentation using a computed value for a claims cost affected by at least one concurrent, different insurance policy for the same insured |
6167564, | Sep 17 1998 | Unisys Corp.; Unisys Corporation | Software system development framework |
6185540, | Dec 28 1994 | GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT | Insurance estimating system |
6226623, | May 23 1996 | CITIBANK, N A | Global financial services integration system and process |
6236975, | Sep 29 1998 | Ignite Sales, Inc.; IGNITE SALES, INC | System and method for profiling customers for targeted marketing |
6336096, | Oct 09 1998 | System and method for evaluating liability | |
6347307, | Jun 14 1999 | Integral Development Corp.; Integral Development Corporation | System and method for conducting web-based financial transactions in capital markets |
6381640, | Sep 11 1998 | Genesys Telecommunications Laboratories, Inc | Method and apparatus for automated personalization and presentation of workload assignments to agents within a multimedia communication center |
6434590, | Jul 14 1995 | Microsoft Technology Licensing, LLC | Methods and apparatus for scheduling parallel processors |
6505176, | Jun 12 1998 | CREDIT MANAGEMENT SOLUTIONS, INC | Workflow management system for an automated credit application system |
6591300, | Jun 30 1999 | Alcatel Lucent | Integrated management application |
6601034, | Mar 05 1998 | CGI TECHNOLOGIES AND SOLUTIONS INC | Decision management system which is cross-function, cross-industry and cross-platform |
6604114, | Dec 04 1998 | Technology Enabling Company, LLC | Systems and methods for organizing data |
6970844, | Aug 27 1999 | FINTEGRAPH, LLC | Flow designer for establishing and maintaining assignment and strategy process maps |
20010011247, | |||
EP280773, | |||
EP465018, | |||
EP926608, | |||
JP9237181, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Mar 28 2002 | BIERENBAUM, STEVEN E | Computer Sciences Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 020395 | /0969 | |
Jul 03 2007 | Computer Sciences Corporation | Comp Sci Holdings, Limited Liability Company | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 020396 | /0008 | |
Nov 29 2007 | Comp Sci Holdings, Limited Liability Company | (assignment on the face of the patent) | / | |||
Aug 12 2015 | Comp Sci Holdings, Limited Liability Company | S AQUA SEMICONDUCTOR, LLC | MERGER SEE DOCUMENT FOR DETAILS | 036871 | /0454 | |
Dec 22 2022 | S AQUA SEMICONDUCTOR, LLC | INTELLECTUAL VENTURES ASSETS 191 LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 062666 | /0716 | |
Feb 14 2023 | MIND FUSION, LLC | INTELLECTUAL VENTURES ASSETS 191 LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 063295 | /0001 | |
Feb 14 2023 | MIND FUSION, LLC | INTELLECTUAL VENTURES ASSETS 186 LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 063295 | /0001 | |
Feb 14 2023 | INTELLECTUAL VENTURES ASSETS 191 LLC | MIND FUSION, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 064270 | /0685 | |
Mar 26 2024 | MIND FUSION, LLC | FINTEGRAPH, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 066912 | /0311 |
Date | Maintenance Fee Events |
Mar 18 2013 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Apr 26 2017 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
Jan 01 2016 | 4 years fee payment window open |
Jul 01 2016 | 6 months grace period start (w surcharge) |
Jan 01 2017 | patent expiry (for year 4) |
Jan 01 2019 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jan 01 2020 | 8 years fee payment window open |
Jul 01 2020 | 6 months grace period start (w surcharge) |
Jan 01 2021 | patent expiry (for year 8) |
Jan 01 2023 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jan 01 2024 | 12 years fee payment window open |
Jul 01 2024 | 6 months grace period start (w surcharge) |
Jan 01 2025 | patent expiry (for year 12) |
Jan 01 2027 | 2 years to revive unintentionally abandoned end. (for year 12) |