US20080027861A1 - System and method for automatic financial project management - Google Patents
System and method for automatic financial project management Download PDFInfo
- Publication number
- US20080027861A1 US20080027861A1 US11/844,903 US84490307A US2008027861A1 US 20080027861 A1 US20080027861 A1 US 20080027861A1 US 84490307 A US84490307 A US 84490307A US 2008027861 A1 US2008027861 A1 US 2008027861A1
- Authority
- US
- United States
- Prior art keywords
- project
- documents
- construction
- participant
- construction project
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
- G06Q10/063114—Status monitoring or status determination for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
- G06Q10/063118—Staff planning in a project environment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06312—Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06313—Resource planning in a project environment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
Definitions
- Project management is traditionally a process which is driven by paper forms and documents.
- paper documents include for example, purchase orders, work orders, contracts, Requests for Assistance (RFA), Requests for Proposals (RFPs), commitments, bids, invoices, messages (generic correspondence), meeting announcements and minutes, project close outs, complete punch lists, project evaluations, and departmental statistics.
- the present invention was originally designed to automate the project management process for the Corporate Real Estate and Facilities Department of the assignee of the present invention. Although originally designed for this type of real estate and facilities department, it is readily seen that the project management method and system of the present invention has wide applicability to most types of project management.
- the system is a collection of process and business objects that provide project management tools to support construction, renovations, maintenance and other projects.
- One primary function of the system is to automate the creation, processing and approval cycles of the numerous documents involved with each project.
- the system and method of the present invention provides automation to support the following business processes.
- Strategic Space Planning This function is responsible for determining how much space is required, demographic and market analysis of locations, and owned versus leased funding strategies.
- Client Management allows project initiation and funding approval by clients throughout the corporation via a desktop browser coupled to the system via a corporate intranet. This concept facilitates self-service delivery.
- the request component allows clients to specific requirements for construction, renovation, relocation or office furniture.
- Project Support The system assists the real estate department staff in creating budgets and controlling how budgets are dispensed though purchase orders, work orders and contracts. This includes the table maintenance involved in vendor authorization, workload, reassignment of tasks, security access and security registration, and changes to processes. Project support is provided for the administrative processes such as administering roles and responsibilities, which includes signing authority.
- Project Management The business objects of the system of the present invention assist a project manager in creating a project budget and controlling how that budget is dispensed through purchase orders, work orders and contracts. Invoices are processed against the commitments and are paid through an electronic accounts payable interface.
- the underlying system structure provides standardized work processes through processing templates. The system provides automated control and management of the process. This methodology is expandable because it is template based, thereby providing an environment for financial based project management.
- Project Management includes phases of project initiation, predesign, schematic design, design development, construction documents, procurement, preconstruction, construction, and post construction.
- the system includes project management functionality to assist in: Tracking Project Milestones; Corporate Cost Center Allocations for identifing how project expenses should be charged; Messages which are generic correspondence; Meeting Announcements and Minutes; Creation and approval of commitments; Approval of invoices; Project Close Outs; Complete Punch Lists; Project Evaluations; and Departmental Statistics.
- Vendor Management allows direct access via the Internet to provide extensive functionality for managing approved vendors in relationship to specific projects. This functionality allows an approved vendor to author Bids, Requests for Quotes (RFQs), Invoices, Punch Lists, Lien Waivers and Messages. Other documents can be received and processed with more limited functionality. These documents include Request for Proposals, Contracts, Work/Purchase Orders, Change Orders, Payment Confirmations and Meeting notices. In addition, an in-box allows for timely communications of messages and documents.
- RFQs Requests for Quotes
- Invoices Invoices
- Punch Lists Lien Waivers
- Lien Waivers Lien Waivers
- Other documents can be received and processed with more limited functionality. These documents include Request for Proposals, Contracts, Work/Purchase Orders, Change Orders, Payment Confirmations and Meeting notices.
- an in-box allows for timely communications of messages and documents.
- the present invention automates the creation, processing and approval cycles of numerous documents involved in project management. It allows project initiation and funding approval by clients throughout the corporation via a desktop browser coupled to a corporate Intranet.
- a software application embodying the present invention and its underlying technology are appropriate for a paper intensive area. It reduces the approval cycle of projects. It automates the creation, processing and approval cycle of documents by routing documents electronically for on-line approval.
- FIG. 1 is an illustration of the structure of the system of the present invention
- FIG. 2 depicts the process flow of the present invention
- FIG. 3 illustrates the tree structure organization of project management data
- FIG. 4 depicts a user interface input screen for inputting a Request for Assistance
- FIG. 5 shows an approval hierarchy structure according to the present invention
- FIG. 6 illustrates a budget template and an example budget
- FIG. 7 depicts an On-call commitment to a vendor
- FIG. 8 shows a Purchase Order commitment
- FIG. 9 illustrates the creation of a bid package
- FIG. 10 illustrates the bid opening processing
- FIG. 11 depicts the processing of bid responses from vendors
- FIG. 12 shows the processing of a vendor invoice
- FIG. 13 illustrates a funding document generated by the system of the present invention
- FIG. 14 depicts the close out information available to a project manager
- FIG. 15 illustrates a close out ledger
- FIG. 16 depicts a partial closeout.
- FIG. 1 illustrates the system 100 of the present invention.
- the various parties to the project managed by the system 100 communicate via a corporate Local Area Network (LAN) 105 .
- LAN Local Area Network
- Server 115 contains the applications that enable the clients to initiate and approve project requests and approve funding for such projects.
- Work flow server 110 contains the applications which enable the project staff to create and route project documents and manage information.
- the workplace server 110 is accessed through an icon on the staffs' work stations 120 which operates in a windows environment.
- the applications can be developed using C, PowerbuilderTM, SQL, Cold FusionsTM, or other similar software development languages and tools.
- Database server 120 provides access to database 122 that contains the various databases housing the details of all of the projects under management.
- the databases on server 110 are relational database such as is available from the OracleTM corporation. Illustrated in FIG. 1 is a work station 125 , such as a personal computer (PC), laptop computer or other such workstations for use by project managers.
- Clients employees of the corporation initiating projects
- access system 100 through a corporate intranet 130 and client work stations 135 .
- Vendors access system 100 using a vendor In workstation 140 connect to the corporate LAN 105 preferably through the Internet 145 using a browser.
- the vendor workstation 140 uses a “thin” client technology meaning that the majority of the software for the vendor access resides on LAN 105 (servers 110 , 115 ).
- the firewall 150 provides all of the requisite security such as password protection, authentication and encryption (if necessary).
- System 100 provides security functions based on roles, signing authority and access rights. Security access is defined through a Role-Business Object-Function relationship.
- the ability to perform a function on an object depends on the state of the object. For example, as further described below, if a document has been approved, that document can no longer be modified so as to protect the integrity of the approval.
- Database 122 contains various tables that support the security function and allow definitions such as: Roles to Person table that identifies all the roles a person can perform; a Functions to Business Object table that identify all the functions and menu items available to a Business Object; a Tree-views to Role table that identifies all the tree views (described below) available for a role; a Functions to Role table used to classify the functions and menu items as enabled or disabled for each business object within a role; a Function Exceptions table that overrides the classification for functions and menu items for each business object within a role identified at the person level (in other words, include or exclude a specific function in this business object for a person playing this role).
- a further table contains the state of all of the objects being managed by the system.
- An object in the present invention can have multiple documents associated therewith. For example, if the object is a bid, some of the documents associated with the bid could be a list of vendors (requiring approval) and a commitment (requiring its own separate approval).
- FIG. 2 illustrates a overview of the project process managed by the present invention.
- the process begins with a client 160 determining that there is a need for the creation of a project.
- the project is a construction project.
- the client 160 initiate the project by generating a Request for Assistance (RFA).
- the Request For Assistance is typically generated by the client 160 with the assistance of a project manager 170 .
- the process of generating an RFA with the aid of a project manager 170 is an iterative one that involves preparation, negotiation, performance and acceptance.
- the RFA contains the nature and scope of the project, the funding available for and required by the project, and the schedule by which the project must be complete.
- the RFA can be communicated by telephone call or e-mail
- the RFA is generated by the client 160 using system 100 .
- the client uses its workstation 135 to connect to LAN 105 through the corporate intranet 130 ( FIG. 1 ).
- the applications on web server 115 prompt the client 160 for all of the necessary information required to complete the RFA 165 .
- the data contained in the RFA 165 is stored in database 122 in separate files associated with the project.
- the client 160 and the and project manager 170 After the client 160 and the and project manager 170 have finalized the RFA, it goes through an approval process (described below) within the client management chain 162 .
- the RFA has been approved by client management 162 is it automatically forwarded to facilities management 172 for approval and assignment of a project manager 170 .
- the project manager 170 uses the RFA as a blueprint.
- the project manager 170 can typically delegate portions of the project to other groups (e.g., design work and its management can be delegated to a design group within the organization).
- the project manager 170 creates bid packages, purchase orders and or contracts 175 which are used to solicit the work from vendors 180 .
- project managers 170 work with the various vendors 180 in refining the nature and scope of the project.
- the project managers 170 receive proposals from the vendors 180 who are bidding on the whole or pieces of the project under consideration.
- the communication between the project managers 170 and the vendors can occur using the telephone or e-mail, but preferably the vendors 180 communicate with the project managers using their workstations 140 through the Internet 145 and firewall 150 .
- contract 175 defines, in detail, the tasks to be preformed by the vendors 180 in completing the projects.
- the specific tasks to be accomplished can be defined via a Purchase Order, a facilities agreement or a service agreement.
- contract 175 is a master contract which defines the general nature of the project as well as the general nature of the relationship between the corporation and the vendors 180 .
- the project manager 170 Pursuant to the contract 175 , the project manager 170 will generate specific commitments to vendors 180 to pay for specific tasks performed by the vendors 180 .
- the contract 175 further provides for the ability of the project managers 170 to issue change orders to the vendors 180 as the scope of the project changes during the evolution of the project.
- the vendors 180 Upon completion of a task, the vendors 180 issue an invoice 185 to the corporation.
- the invoice 185 can be transmitted to the corporation via tradition paper method, but preferably is transmitted in an electronic form compatible with system 100 . If received in paper form, an invoice 185 is scanned so that it is rendered in electronic form which can be incorporated into system 100 in database 122 .
- the invoice 185 is reviewed by a project analyst 190 for comparison with the contract and the commitment to the vendor 180 .
- the invoice 185 then goes through an approval process by the project manager 195 according to the business rules for the project as further described below.
- the payment on the invoice goes through an accounting process 200 in which the payment is validated and charged against the appropriate portions of the contract.
- the payment is then remitted 205 to the vendor either through a credit to the vendor's Demand Deposit Account (DDA), via check or via Electronic Data Interchange (EDI) remittance.
- DDA Demand Deposit Account
- EDI Electronic Data Interchange
- FIG. 2 has depicted the general process of how a project is initiated and managed.
- the remainder of the Figures will illustrate how system 100 facilitates the initiation management and closure of the project process.
- the workstations for managing the project process ( 120 , 125 in FIG. 1 ) operate in a windows environment although any other suitable network operating system (e.g., Unix) can be employed.
- System 100 includes security procedures, such as sign-on procedures, as known by those skilled in the art.
- FIG. 3 illustrates a typical user interface screen 250 which will help explain the structure and functions of system 100 .
- Information concerning projects managed by system 100 are preferably organized in folders 255 by projects.
- the folders 255 are organized in a tree structure 260 .
- User interface 250 illustrates one tree structure 260 of a particular project 270 .
- System 100 contains various predefined tree views of folders 255 which are selected using list box 265 . Specifically illustrated in FIG. 3 is a tree view entitled “My Projects” in list box 265 .
- the tree view of “My Projects” illustrated in FIG. 3 is the standard default view of system 100 .
- the “My Projects” tree view is most frequently used by project managers and other support staff. Other tree views access information in a variety of ways.
- Other tree views include: a close out master view that lists all of the closed projects; a major expenditure plan view that lists all of the major projects; “my” major expenditure plan view which lists the major projects which a particular project manager is managing; a personal view that is an information folder for use by the user to store data for activities not related to specific projects; a projects by business sector view that lists all of the projects, sorted by major business division; a project by facilities division view that lists all projects sorted by a specific facilities department within the corporation; a view of projects by location that lists all of the projects sorted by location; a view of projects by project manager that lists all of the projects sorted by the project manager managing the project; a projects being supervised view that lists all of the projects being managed by the staff of a manager within the corporation; a view of recently approved documents that lists all of the documents that a user has approved within a predetermined period of time (e.g., two weeks); a view of system tables that lists various categories of system data such as roles, user profiles, and signing authorities; and a
- Each of the user interface screens of the system 100 include toolbars 275 , 280 containing icons that provide short cuts to the functionality of system 100 .
- the icons on toolbar 275 are consistent across the user interface screens of system 100 .
- These icons provide basic functionality to all screens such as a button for returning the user to default tree view, a print button which prints the screens, a close button which closes a screen in which the user is currently operating, a tile up button that returns the screen to the standard screen format with the tree view 260 on the left hand portion of the screen and the selected item on the right hand portion of the screen, and an exit button that is used to exit the system.
- the icons on toolbar 280 change from screen to screen, depending on the function being performed by the user.
- Some of the toolbar 280 icons illustrated in FIG. 3 include a new document icon 281 that produces a new document menu; a view notes button that produces a list of all notes created using the notebook feature of the present invention as further described below; a refresh button that renews and updates the tree view after completing an activity; a toggle tree button that toggles between the tree view and a full screen view of the selected item on the right hand portion of the screen; and a create note button that activates the notebook feature of the present invention.
- the icons on toolbars 275 , 280 and other functions of the present invention are accessed using a standard input device of the user's workstation such as a mouse. The mouse is used to click on a button to activate a specific function, to select an item and to drag and drop items of information.
- FIG. 3 illustrates the folders 255 associated with the project 270 .
- the user illustrated in FIG. 3 only has a single project 270 , otherwise the other projects associated with the user would be illustrated in the tree view area.
- Eleven folders 255 are shown as being associated with the project 270 .
- the project directory folder 282 contains a listing of all of the project team members as well as the project vendors. The list is populated from database 122 ( FIG. 1 ) as individuals or vendors are identified on the project.
- the Request For Assistance folder 284 contains the approved RFA form as described above.
- the budget and funding folder 286 contains all budget worksheets and funding documents. These documents include a preliminary funding document, a supplemental funding document and surrogate funding documents.
- Project task folder 288 contains the project tasks that are set up to assign portions of the approved budget to specific trades (e.g., plumbing) in preparation for creating commitments to vendors.
- Commitments by trade folder 290 lists all of the commitments that have been prepared for a project (including draft, unapproved and approved commitments).
- the approved commitments folder 292 contains all of the approved commitments.
- the payments folder 294 contains all approved invoices from vendors for which payment has been made.
- the bid documents folder 296 contains all information related to bids and bid waivers. Each bid listed in this folder is assigned a unique number for accounting tracking purposes.
- Reports folder 298 contains a tracking report with respect to the project which lists all commitments and payments. This folder can also be used to store copies of other reports.
- Projects attachment folder 300 contains sub-folders for storing scan documents or electronic files of plans, specifications, correspondence, schedules and furniture/finishes information for example.
- the close out folder 302 contains partial and final close out information with respect to the project. Again, the above list of folders 282 - 302 is not exhaustive and any folders can be created which suit the needs of the particular project being undertaken or the corporate system in which the system of the present invention operates.
- the right hand portion of screen 250 depicts the information associated with the folder selected on the left hand portion of the screen.
- the project 270 has been selected and accordingly, a profile 304 of the project is displayed on the right hand portion of screen 250 .
- the project profile 304 contains information related to the category of the project, the project number, the project name, the location of the project, the division for which the project is being conducted and the cost center associated with that division as well as the current phase of the project.
- the project profile further includes a brief project description 306 as well as an area 308 for the project status.
- every document within system 100 has its own notebook in which is recorded comments, issues or status information associated with the project.
- the notebook feature can be activated at any time, such as while preparing a document, during the approval process, or even after final approval.
- Notes can be saved generally in three different categories.
- a first category is a comment which includes general notes for the facility staff.
- a second category of notes is the status of the project which contains on going project status information. This status information from the notebook is displayed in the status area 308 in the project profile area.
- the final general category of notes contains specific notes to be published to other members of the team such as the clients. The published notes are available to the clients as previously described through the corporate intranet 130 .
- FIG. 4 illustrates an initial user interface screen 350 for creating an RFA.
- the RFA is prepared either directly by a requestor or by a coordinator within the business unit requiring the project.
- the input screen 350 allows the user to input all of the required information into an electronic RFA form.
- the electronic form is used for projects over a predetermined dollar amount (e.g., $10,000). If the project total is less than the predetermined amount, the user can e-mail the project and requestor information to the facility staff. The facility staff can then prepare an internal RFA on behalf of the requester so that the request can be inputted and managed within the system 100 of the present invention.
- FIG. 5 This screen represents one of the unique features of the present invention.
- the user is able to identify the proper personnel required to approve the RFA.
- the first approval is a business unit manager 362
- the second approval by a business unit controller 364 and the final approval by a business executive 366 .
- Different rules are capable of being set in the database 122 of system 100 such that depending on the scope of the project (typically the total dollar amount) the number of approvals will change.
- a business unit executive 366 will be required to approve the RFA.
- area 368 the user is able to select the actual person who is fulfilling the role required for approval.
- the database of system 100 contains all of the relevant information with respect to each person in each business unit that can fulfill each role (e.g., name, e-mail address, title, etc.). The user can select the appropriate person from a drop down menu by selecting the down arrow on each box in area 368 .
- This action automatically forwards the electronic RFA to the person fulfilling the role of the first level of approval required for the RFA.
- a notice of the pending RFA requiring approval is added to the workflow list of pending tasks of the approver.
- This workflow list is accessed by the approver using button 375 . When activated, this button provides a list of all of the documents requiring the persons' approval. The approver is then able to click on the notice which will bring up the actual electronic RFA document for review by the approver. After the review is complete, the reviewer is able to type any notes into a comment area of the RFA document and select one of several actions.
- the electronic RFA is sent to the next individual in the approval hierarchy.
- System 100 enables electronic signatures as is well known to those skilled in the art.
- the approver can also return the RFA for clarifications to the previous approver or to the requester. Such an action should be accompanied by the approver including notes in the comment area which further define the clarifications required.
- the approver can also disapprove the RFA which sends the form directly back to the requestor or client coordinator. Again, if the RFA is disapproved, the approver should include notes in the comment area including reasons for the disapproval. Finally, the approver can discontinue the review of the RFA and come back to complete the review at a later time.
- the notice of the pending RFA will remain in the approver's work list. If the RFA is approved by the final approver in the client hierarchy, the form is automatically routed to a dispatcher in the project management staff. At this point, the approved RFA is assigned a project number and a project manager.
- the automatic approval process of the present invention has several distinct advantages.
- First, the process is instantaneous. Once a document has been submitted for approval, notice of the receipt of the document for approval is immediately sent to the approver and the document is immediately available for review. This is in sharp contrast to the prior art method of approval in which documents typically were rerouted using interoffice mail. Apart from the delay associated with such a mail system, documents were often lost or misplaced. Tracking the status of approvals using the present invention is as simple as clicking on a button on the user's screen. The prior art required someone to conduct a series of phone calls, e-mails and personal visits to the approvers.
- Another advantage of the approval hierarchy of the present invention is that it recognized the corporate reality that people often change jobs, responsibilities, and locations.
- the database 122 of system 100 is easily modified to reflect the change. For example, if someone having the role of an approver is promoted and another person takes over the role, the database can be easily modified to replace the promoted person with the successor. Any subsequent approvals will then be automatically forwarded to the successor. Similarly, if someone having a role is on a temporary leave or absence, any task assigned to that person (e.g., approvals) can be easily and temporarily reassigned to a substitute person.
- Additional functionality provided to the clients of system 100 is the ability to view a list of RFAs for its business unit by clicking button 378 .
- This button will bring up a window containing all of the RFAs of the business unit.
- the list will include the project name, the date prepared, the status of the RFA and the status of the funding of the project.
- a client is able to view a list of all of the finding documents by clicking on button 380 .
- the finding list will display all of the funding documents for projects on which the user is involved. Once a list is displayed in the system 100 of the present invention, the user is able to view the actual documents associated with the item by selecting the particular item.
- FIG. 6 illustrates a user input screen 400 for creating budgets and funding documents.
- budgets are created using predefined templates.
- Area 402 allows the user to view a list of all of the budget templates available within system 100 . These templates can either be global (general formats available to all personnel) or private (i.e., templates that the user has personally created for his or her own use). Once a template is selected, the template is displayed in area 403 on the left hand portion of screen 400 .
- the templates contain three levels of project information, including individual trades (e.g., lighting fixtures), trade categories (e.g., electrical) and summary categories (e.g., construction, 404 in FIG. 6 ).
- the templates in area 403 can be viewed in the standard view as illustrated in FIG. 6 , or a tree view as previously described, that shows summary categories in expandable folders.
- the user is able to create the unique budget for the project in area 406 by dragging and dropping the items from the template area 403 into the budget area 406 .
- the user is required to input the unit 408 , quantity 410 and price 412 .
- system 100 automatically calculates the cost of the item 414 .
- system 100 allocates the cost as a capital item 416 or an expense item 418 .
- System 100 additionally calculates an allowed contingency amount 420 which can be set in the system as a percentage of the cost (e.g., 10% of the capital cost). The user is able to increase or decrease this contingency amount in area 422 .
- the system of the present invention generates a funding document for approval.
- An example of a funding document is depicted in FIG. 13 .
- the funding document of FIG. 13 was generated by a template accessing data from the database containing the budget. It is appreciated that any template can be used to generate any type or form of funding document desired.
- the funding document summarizes the capital items for the project 700 as well as the expense items 705 .
- These summaries 700 , 705 provide the approvers with an overview of the total spending for the project without the complexity of the details of the entire budget.
- Further shown in FIG. 13 are the names of the approvers of the funding document as well as the dates of the approval.
- the funding document indicates approval by both the facilities department 710 as well as the management of the business unit 715 .
- the project staff member submits the funding document for approval which is automatically forwarded to the facilities hierarchy for approval.
- the first person in the facilities hierarchy receives a notice in his or her work list regarding the funding document to be approved.
- the same automatic forwarding of approved documents is follows as described above with respect to an RFA.
- the reviewer denies approval or requests further clarification, the funding document is automatically returned to the previous approver with notes in the comments section providing reasons for the disapproval or the required clarification.
- the client business unit has a similar level hierarchy for approvals, depending on the scope and size of the project.
- the same approval process is repeated within the client business unit including automatic forwarding of approved funding documents.
- the funding document Once the funding document has received final approval from the client hierarchy, it is automatically forwarded to the assigned project manager who acknowledges the approved funding document. The funds are now available for commitments and the process of managing the project begins.
- the project manager With the approved RFA and budget in place, the project manager is able to begin the actual project management. This process starts with the project manager generating commitments to vendors for various aspects of the projects.
- the commitments include: architectural/engineering on calls; Purchase Orders; bids; bid waivers; contracts; change orders; and work orders.
- Architectural/engineering on-calls are commitments for on-call consultant services which typically result in the generation of a purchase order.
- a Purchase Order is a commitment for goods, materials, equipment or services, typically up to a predetermined dollar amount (e.g., $25,000). In the preferred embodiment, commitments over the predetermined amount (e.g., $25,000), require competitive bids.
- bids result in purchase orders for goods, materials and equipment or contracts for the provision of services.
- biding can be waived pursuant to a special bid waiver approval process.
- Work orders are commitments made against a master contract with a vendor for certain services of any dollar amount and for other trade services up to a predetermined amount (e.g., $10,000).
- Change orders are amendments to previously approved purchase orders or contracts, either increasing or decreasing the dollar amount. The change order results in a revised purchase order or a revised contract.
- the commitments are created against the previously approved funding and begin with the creation of a project task that assigns a portion of the approved budget to a specific trade.
- the project manager selects the new document icon ( 281 in FIG. 3 ) to create the task.
- Activation of this icon 281 displays a document selection menu which includes the various documents which the project manager is able to create. A selection exists for each of the above-identified types of commitments (e.g., an on-call commitment).
- the project manager is required to complete a description of the project task including the trade, the protocol for the commitment (e.g., source, bid, waived bid, negotiated, national contract), the type of commitment (e.g., purchase order, contract, work order) the tax status of the commitment (e.g., taxable, nontaxable) and a detailed description of the scope of work to perform pursuant to the commitment.
- the protocol for the commitment e.g., source, bid, waived bid, negotiated, national contract
- type of commitment e.g., purchase order, contract, work order
- the tax status of the commitment e.g., taxable, nontaxable
- a detailed description of the scope of work to perform pursuant to the commitment e.g., taxable, nontaxable
- the project manager is further required to complete a trade code details section. All of the trade codes that are contained within the approved budget are displayed (e.g., electrical). The project manager is able to drag and drop the applicable trades from the project budget to the trade code portion of the project task. The project manager then types in the dollar amount for each applicable trade for the commitment. Once the project manager has completed the above, the project manager saves the project task and is then able to generate the actual commitment.
- All of the trade codes that are contained within the approved budget are displayed (e.g., electrical).
- the project manager is able to drag and drop the applicable trades from the project budget to the trade code portion of the project task. The project manager then types in the dollar amount for each applicable trade for the commitment. Once the project manager has completed the above, the project manager saves the project task and is then able to generate the actual commitment.
- FIG. 7 illustrates a complete commitment request 450 for an architectural/engineering on-call.
- the project manager was prompted to enter information related to the project 455 , information related to the consultant (vendor) 460 , the scope of the job and the square footage affected and the fees associated therewith 465 , as well as a summary of the funding and financial commitments 470 , both with respect to this particular commitments and the project in total.
- Many of the items found on this on-call commitment were obtained from pull down menus (not shown) such as the consultant.
- Other items such as the cost center to be changed for work performed are provided by system 100 as a default once the project number is inputted by the project manager.
- the project manager submits the commitment for approval to the project staff.
- the approval process is automatic, with each level of approval being able to approve the document, disapprove the document or return the document for clarification.
- system 100 provides the project manager with the capability of scanning in additional documents that are associated with the commitment or creating any attachment such as spreadsheets, JPEG files, drawings.
- attachments are created using Object Linking and Embedding (OLE) compliant software.
- Additional documents attached to a commitment may include proposals from the consultant or vendor. These attachments are available for review by the approvers at their work stations by selecting a view menu and selecting the attachments choice on the view menu (not shown).
- system 100 automatically generates a purchase order number and notifies the project manager (electronically) of the purchase order number.
- a hard copy of the purchase order is issued by the project staff to the vendor.
- the vendor is also able to obtain an electronic copy of the purchase order through the Internet interface previously described with respect to FIG. 1 .
- the purchase order contains all of the basic information contained in the on-call commitment request as illustrated in FIG. 7 .
- the vendor opens the electronic purchase order (or other document such as a contract or a change order)
- the vendor is presented with a set of appropriate functions. For example, for contracts, a command button will be provided to Agree to the terms or Not Agree with an opportunity to comment or create addendum.
- the Agree function invokes an electronic signature process.
- records relating to a vendor remain available in system 100 for a period of at least one year following the job's completion.
- Documents the vendor can author include Bids, RFQs, Invoices, Punch Lists, Lien Waivers and Messages.
- Documents the vendor can receive and process with limited functionality are Request for Proposals, Contracts, Work/Purchase Orders, Change Orders, Payment Confirmations and Meeting notices.
- the vendor is only allowed to view documents they authored or documents intended for them. The ability to delete documents are limited from a vendor's perspective and may only be allowed depending on the state of a document. This will provide for a document draft feature prior to posting to the workflow.
- FIG. 8 illustrates a request for a purchase order commitment 475 generated by system 100 of the present invention.
- the project profile information 455 is the same as described above with respect to the on-call commitment.
- the commitment information 480 includes the trade involved, the type of commitment (a purchase order in this example) and the protocol for the commitment.
- the vendor information 485 describes the vendor to which the Purchase Order is to be issued. Again, this information can be input by the project manager using drag and drop methods previously described from a master list of vendors for the selected trade. The selection of vendors can either by from all of the vendors contained in the system or from vendors with which the corporation has a master contract.
- the cost associated with the purchase order is entered in area 490 and the summary of the financial commitments is again listed in area 470 .
- the project manager is able to scan non-electronic documents into the system for attachment to the purchase order.
- the purchase order request Once the purchase order request has been saved, it can be submitted for approval and proceeds through the approval hierarchy as previously described.
- the purchase order is issued to the vendor with notification being made to the project manager electronically.
- a project task for a bid is again created as described above.
- the project manager is then able to create a bid package 500 as illustrated in FIG. 9 .
- System 100 automatically assigns a bid number 502 to the bid package as well as assigning the bid status 504 of “initialization”.
- a bid is an object that can have many documents associated therewith. Each document can have a separate approval process as described above. There is not necessarily a one to one relationship between documents and the object with which they are associated.
- the trade 506 is obtained by the system from the information provided by the project manager in the creation of the project task. The project manager then inputs the invitation and bid due dates 508 and 510 as required by the project.
- the contract type 512 is selected by the project manager from a pull down menu (not shown).
- the project manager further inputs any special instruction in area 514 .
- the bid package total 518 is automatically calculated by the system as the sum of the tasks 520 .
- the tasks 520 are initially populated by system 100 from the entries input the project manager when creating the project task.
- the project manager can add additional tasks in area 520 that he or she desires to be bid upon.
- the task can relate to the same project number or be associated with different projects,
- the price options 522 defaults to a base price, but the project manager can select alternative pricing options from a pull down menu (not shown).
- the documents supporting the bid are listed in area 524 and include such documents as architectural or engineering drawings as well as equipment specifications.
- the project manger is provided with a bid package vendor selection screen that allows the project manger to choose the vendors from which bids will be requested. Again, the project manager is able to select the vendors from a list complied from the database 122 in system 100 . Once the project manager has finished selecting the vendors from which bids will be requested, the list is saved and submitted for automatic approval as described above. Once the list of proposed bidders has been approved, the bid package is sent to each of the bidders in hard copy form and preferably in electronic form.
- FIG. 10 illustrates an input screen 550 used for conducting the bid opening. As illustrated in this Figure, three witnesses 552 are provided. System 100 requires these witnesses 552 to input their IDs and passwords when conducting the bid opening. As each bid is open, the information from each vendor is input into area 554 . The vendor name and the price options are defaulted by the system 100 from the approved proposed bidder list previously described. The amount 556 is obtained from the vendors bid and is input into the system by the project staff. Additionally, the actual bid documents are scanned into system 100 and linked as attachment to the project. Once all of the bids from the selected bidders have been entered, the bid responses on screen 550 is saved and the bid opening is officially closed. The project manager is now able to perform an evaluation of the bids.
- the project manager selects the bid documents folder ( 296 in FIG. 3 ) to view the various bids.
- the bid documents folder contains all of the bids associated with the selected project.
- Selecting a modify button activates a bid evaluation screen 560 as illustrated in FIG. 1l .
- each of the bidding vendors is displayed.
- the project manager is able to enter a qualified price 562 which is either the bid amount submitted by the vendor during the bidding process or an adjusted amount due to clarifications with the vendor after the bid has been opened.
- the project manager is additionally able to enter any comments on the pricing in area 564 with respect to each of the vendors.
- the project manger is then required to rank the vendors in area 566 and provide a reason for selecting a particular vendor in area 568 . If addition documents have been submitted by the vendors, they can be scanned in and attached to the data for project as well as other attachment such as drawings. Once the project manager has completed his or her ranking 556 , the bid evaluation is saved and submitted for approval. The automatic approval process proceeds as described above with respect to the approval hierarchy.
- the vendors submitted invoices for the services and materials provided pursuant to the commitments.
- the invoices are electronically transmitted from a vendor workstation 140 ( FIG. 1 ) through the Internet 145 and the firewall 150 for receipt by system 100 .
- paper invoices may be submitted, scanned and the data entered into the system either manually or through drag and drop methods.
- the project manager reviews the invoice data contained in system 100 against the scanned copy and makes any necessary adjustments in the payment amount, retainage, freight/delivery or tax, based on the actual goods or services provided.
- FIG. 12 illustrates an example of an invoice data entry screen 600 .
- the purchase order number 602 , the invoice number 604 and the invoice date 606 are entered.
- System 100 using the purchase order number 602 , automatically fills in the commitment information 608 as well as the vendor information 610 .
- the amount of the invoice including the material amount, the freight amount and the taxable amount are entered in area 612 .
- the data is saved and submitted for approval.
- the invoice approval process follows the approval hierarchy described above with respect to the other documents generated by the system. In a preferred embodiment, if the invoice amount does not exceed the commitment amount, the project manager alone can approve the invoice.
- the project manager can prepare a change order.
- the change order requires approval through the hierarchy and the issuance of a revised purchase order reflecting the adjusted commitment amount.
- the payment can be made to the vendor either through the issuance as by check, crediting of the vendors demand deposit account, or through other EDI means.
- One further advantage of the present invention is the automatic nature of the tracking of the accounting information.
- a general rule is that any required accounting information (e.g., the business unit to which items will be charged) is captured by the system as soon as possible and thereafter carried through throughout the project. For example, once the client identifies the business unit to be charged, this identification is automatically carried into the templates for the project, commitments and invoices. All documents created from these templates will therefore automatically carry the identification of the business unit to be charged.
- one of the features of the present invention is the ability to automate the close out process.
- the process of closing out a project has historically been an arduous and manually intensive process.
- the preferred embodiment of the present invention relates to construction projects, and the close out process will be described in terms of this embodiment.
- the closeout procedures of the present invention automate the financial transactions associated with the following two processes: handling of a project's CIP (construction-in-progress) account balance; and the final closing of a project.
- CIP construction-in-progress
- the CIP account is a holding account that captures a construction project's capital expenditures.
- the balance in the CIP account is passed to a fixed asset (F/A) account for depreciation.
- F/A fixed asset
- the balance is passed to a fixed account it starts depreciating thus creating depreciation expenses for portion of the corporation that is benefitting from the project.
- the construction project There is no hard requirement for the construction project to be 100% complete in order to commence depreciation. Depreciation can start with the payment of the first invoice with respect to the project.
- 80% threshold for commencing depreciation (i.e., 80% of the project must be complete before depreciation is started).
- the specifics of a project might require for the depreciation to be started both before or after an 80% threshold is reached.
- a partial closeout is a type of closeout that is done when there is a need to move a portion of CIP balance to a F/A account. On larger projects, either in terms of funds and or the period of time for completing the entire project, having multiple partial closeouts is a very useful function practical.
- a full closeout is a type of closeout that is performed by the project manager only once. After successful completion of full closeout the project is closed to any further activity (including commitments and payments).
- a Cancel closeout is a type of closeout that is performed by the project manager in a case where a project was initiated in the system of the present invention but, before any commitments were issued to the vendors or any invoices were paid, the decision was made to stop it.
- An abort closeout is a type of closeout that is performed by a project manager when the client requested to stop the project after the funding was approved, commitments were issued and/or invoices were paid.
- a trigger built in the system initiates the first partial closeout for a project when the payment of a particular invoice meets the 80% threshold.
- the 80% threshold is with respect to the entire project.
- This trigger for a partial close out can be set to occur with respect to any event that is kept track of in the system. For example if there are several phases of a project, the trigger can cause a partial closeout at the completion of a particular phase.
- the trigger initiates a workflow process gets started that opens a closeout session.
- the system automatically links all of the paid invoices for the project to the closeout session created by the trigger.
- the system also generates a substantial number (sometimes hundreds) of financial transactions that will be sent to the General Ledger (G/L).
- G/L General Ledger
- the work flow process sends the generated transactions to an analyst in the financial area. After reviewing the transactions, the analyst approves the session. This single automated procedure alone replaces a substantial manual effort (document collection, data entry, data validation, etc.,) which would take weeks or even months to complete.
- the financial analyst can request that the system start a partial closeout if needed. In the preferred embodiment, there is no system-imposed limit on the number of partial closeouts that can be processed by the system.
- FIG. 14 illustrates the close out information that the system makes available to the project manager.
- the tree structure of folders in the project manager's directory includes a close out folder 800 . Opening the close out folder brings up the screen 802 seen in the left hand portion of FIG. 14 . Close out screen 802 contains six tabs 805 - 830 for viewing further information with respect to the status of the various close outs with respect to a project.
- the Financial Summary tab 805 displays a summary of the overall financial status of the project.
- Information in area 835 provides identification of the project, while the information in area 840 summarized the actual financials.
- the financial information in area 840 includes the budget for the project, the amount of the budget that has been committed, the amount of the commitments that have been paid, the percentage of the budget that has been paid, the retainage held and the retainage paid.
- the project manager is quickly able to obtain a summary of the progress, from the financial point of view, of the project.
- Each of the other tabs, commitments 810 , unapproved budget 815 , unapproved commitments 820 , change orders 825 and invoices 830 respectively bring up screen that detail the status of the subject matter related to the items associated with the tab.
- the commitments tab 820 brings up a screen (not shown) that shows in detail all of the commitments that were created in the system.
- the screen shows the vendor to which the commitment has made, the category (e.g., construction, move) the amount of the commitment, the amount paid to date and the remaining balance of the commitment.
- the remainder of the tabs 810 - 830 bring up similar screens that list all of the items associated with the tab.
- the folders Closeout Ledger 850 and Partial 860 in the project manager's tree directory contain further information related to the closeout status.
- the closeout ledger folder 850 bring up a screen 900 as illustrated in FIG. 15 .
- This ledger screen 900 includes a summary are 905 and a detailed area 910 . Within the detailed area 910 , there is an entry for each of the closeouts associated with the project. In the particular example depicted in this Figure, only a single partial closeout has been executed with respect to the project.
- FIG. 16 illustrates the details associated with a partial closeout.
- Area 950 lists the project information and the project details are listed in area 955 .
- Area 960 contains the details as to the G/L accounts to which the items in the partial closeout were assigned.
- Area 970 details the different G/L accounts to which items were posted as well as the depreciation schedule that is assigned to the items.
- the project manager initiates a final closeout.
- the full level of automation associated with the partial closeout as described above is applied to the full close out.
- additional tests are performed to make sure that no unfinished business associated with the project is left unattended. For example, one test is performed to expose any unpaid invoices. Another test is performed to identify any commitment that is not fully paid. A further test is performed to identify any credit from a third party (e.g. a real estate) due to the project that is not collected. And so on.
- a full diagnostic of the state of the project is presented to the project manager in a manner of seconds and a list of actions required is fully identified. In the prior art manual process, this undertaking would have required days if not weeks to complete.
Abstract
A system and method for providing project management tools to support construction, renovations, maintenance and other projects. The system automates the creation, processing and approval cycles of the numerous documents involved with each project. The system provides standardized work processes through processing templates. The system provides automated control and management of the process. The system allows project initiation and funding approval by clients throughout the corporation via a desktop browser coupled to a corporate Intranet. A software application embodying the present invention and its underlying technology are appropriate for a paper intensive area. It reduces the approval cycle of projects. It automates the creation, processing and approval cycle of documents by routing documents electronically for on-line approval.
Description
- The present invention is related to and claims priority to U.S. Provisional Patent Application No. 60/163,506 entitled AUTOMATED FINANCIAL PROJECT MANAGEMENT SYSTEM, filed Nov. 4, 1999, the contents of which are incorporated herein by reference.
- Project management, especially in the area of corporate real estate project management, is traditionally a process which is driven by paper forms and documents. These paper documents include for example, purchase orders, work orders, contracts, Requests for Assistance (RFA), Requests for Proposals (RFPs), commitments, bids, invoices, messages (generic correspondence), meeting announcements and minutes, project close outs, complete punch lists, project evaluations, and departmental statistics.
- The processing of all of these various documents is very labor intensive, error prone and subjects the proposed projects to needless delays. For example, if the manager in charge of approving commitments is on a business trip for two weeks, a commitment requiring his or her signature might be delayed for an additional six weeks, which in turn delays another vendor's initiation of work and so on.
- Furthermore, an increase in the number of requests for new construction or engineering projects increases the volume of documents that are processed by the project administration group and the accounting operations group. This in turn requires an increase in processing capacity through an increase in staff levels or overtime. Conversely, a decrease in volume of requests lowers the productivity of the groups, as the staff levels are maintained to support the processing at the peak operations volume.
- The present invention was originally designed to automate the project management process for the Corporate Real Estate and Facilities Department of the assignee of the present invention. Although originally designed for this type of real estate and facilities department, it is readily seen that the project management method and system of the present invention has wide applicability to most types of project management.
- The system is a collection of process and business objects that provide project management tools to support construction, renovations, maintenance and other projects. One primary function of the system is to automate the creation, processing and approval cycles of the numerous documents involved with each project. The system and method of the present invention provides automation to support the following business processes.
- Strategic Space Planning. This function is responsible for determining how much space is required, demographic and market analysis of locations, and owned versus leased funding strategies.
- Client Management. The system allows project initiation and funding approval by clients throughout the corporation via a desktop browser coupled to the system via a corporate intranet. This concept facilitates self-service delivery. The request component allows clients to specific requirements for construction, renovation, relocation or office furniture.
- Project Support. The system assists the real estate department staff in creating budgets and controlling how budgets are dispensed though purchase orders, work orders and contracts. This includes the table maintenance involved in vendor authorization, workload, reassignment of tasks, security access and security registration, and changes to processes. Project support is provided for the administrative processes such as administering roles and responsibilities, which includes signing authority.
- Project Management. The business objects of the system of the present invention assist a project manager in creating a project budget and controlling how that budget is dispensed through purchase orders, work orders and contracts. Invoices are processed against the commitments and are paid through an electronic accounts payable interface. The underlying system structure provides standardized work processes through processing templates. The system provides automated control and management of the process. This methodology is expandable because it is template based, thereby providing an environment for financial based project management. Additionally, Project Management includes phases of project initiation, predesign, schematic design, design development, construction documents, procurement, preconstruction, construction, and post construction. The system includes project management functionality to assist in: Tracking Project Milestones; Corporate Cost Center Allocations for identifing how project expenses should be charged; Messages which are generic correspondence; Meeting Announcements and Minutes; Creation and approval of commitments; Approval of invoices; Project Close Outs; Complete Punch Lists; Project Evaluations; and Departmental Statistics.
- Vendor Management. The system allows direct access via the Internet to provide extensive functionality for managing approved vendors in relationship to specific projects. This functionality allows an approved vendor to author Bids, Requests for Quotes (RFQs), Invoices, Punch Lists, Lien Waivers and Messages. Other documents can be received and processed with more limited functionality. These documents include Request for Proposals, Contracts, Work/Purchase Orders, Change Orders, Payment Confirmations and Meeting notices. In addition, an in-box allows for timely communications of messages and documents.
- The present invention automates the creation, processing and approval cycles of numerous documents involved in project management. It allows project initiation and funding approval by clients throughout the corporation via a desktop browser coupled to a corporate Intranet. A software application embodying the present invention and its underlying technology are appropriate for a paper intensive area. It reduces the approval cycle of projects. It automates the creation, processing and approval cycle of documents by routing documents electronically for on-line approval.
- Other objects, features, and advantages of the present invention will be apparent to one skilled in the art from the following description of the invention with reference to the accompanying drawing.
- For the purposes of illustrating the present invention, there is shown in the drawings a form which is presently preferred, it being understood however, that the invention is not limited to the precise form shown by the drawing in which:
-
FIG. 1 is an illustration of the structure of the system of the present invention; -
FIG. 2 depicts the process flow of the present invention; -
FIG. 3 illustrates the tree structure organization of project management data; -
FIG. 4 depicts a user interface input screen for inputting a Request for Assistance; -
FIG. 5 shows an approval hierarchy structure according to the present invention; -
FIG. 6 illustrates a budget template and an example budget; -
FIG. 7 depicts an On-call commitment to a vendor; -
FIG. 8 shows a Purchase Order commitment; -
FIG. 9 illustrates the creation of a bid package; -
FIG. 10 illustrates the bid opening processing; -
FIG. 11 depicts the processing of bid responses from vendors; -
FIG. 12 shows the processing of a vendor invoice; -
FIG. 13 illustrates a funding document generated by the system of the present invention; -
FIG. 14 depicts the close out information available to a project manager; -
FIG. 15 illustrates a close out ledger; and -
FIG. 16 depicts a partial closeout. -
FIG. 1 illustrates thesystem 100 of the present invention. The various parties to the project managed by thesystem 100 communicate via a corporate Local Area Network (LAN) 105. Connected to theLAN 105 are various servers 110-120 on which reside the applications and databases supporting thesystem 100.Server 115 contains the applications that enable the clients to initiate and approve project requests and approve funding for such projects.Work flow server 110 contains the applications which enable the project staff to create and route project documents and manage information. In a preferred embodiment, theworkplace server 110 is accessed through an icon on the staffs'work stations 120 which operates in a windows environment. The applications can be developed using C, Powerbuilder™, SQL, Cold Fusions™, or other similar software development languages and tools. -
Database server 120 provides access todatabase 122 that contains the various databases housing the details of all of the projects under management. In a preferred embodiment, the databases onserver 110 are relational database such as is available from the Oracle™ corporation. Illustrated inFIG. 1 is awork station 125, such as a personal computer (PC), laptop computer or other such workstations for use by project managers. Clients (employees of the corporation initiating projects)access system 100 through acorporate intranet 130 andclient work stations 135.Vendors access system 100 using a vendor Inworkstation 140 connect to thecorporate LAN 105 preferably through theInternet 145 using a browser. Thevendor workstation 140 uses a “thin” client technology meaning that the majority of the software for the vendor access resides on LAN 105 (servers 110, 115). The firewall 150 provides all of the requisite security such as password protection, authentication and encryption (if necessary). -
System 100 provides security functions based on roles, signing authority and access rights. Security access is defined through a Role-Business Object-Function relationship. In addition, the ability to perform a function on an object (e.g., a document to be approved) depends on the state of the object. For example, as further described below, if a document has been approved, that document can no longer be modified so as to protect the integrity of the approval. -
Database 122 contains various tables that support the security function and allow definitions such as: Roles to Person table that identifies all the roles a person can perform; a Functions to Business Object table that identify all the functions and menu items available to a Business Object; a Tree-views to Role table that identifies all the tree views (described below) available for a role; a Functions to Role table used to classify the functions and menu items as enabled or disabled for each business object within a role; a Function Exceptions table that overrides the classification for functions and menu items for each business object within a role identified at the person level (in other words, include or exclude a specific function in this business object for a person playing this role). A further table contains the state of all of the objects being managed by the system. A history of the revisions to an object (e.g., the changes in state during the approval process of a document) is maintained for auditing purposes. An object in the present invention can have multiple documents associated therewith. For example, if the object is a bid, some of the documents associated with the bid could be a list of vendors (requiring approval) and a commitment (requiring its own separate approval). -
FIG. 2 illustrates a overview of the project process managed by the present invention. The process begins with aclient 160 determining that there is a need for the creation of a project. In the preferred embodiment the project is a construction project. Theclient 160 initiate the project by generating a Request for Assistance (RFA). The Request For Assistance is typically generated by theclient 160 with the assistance of aproject manager 170. The process of generating an RFA with the aid of aproject manager 170 is an iterative one that involves preparation, negotiation, performance and acceptance. The RFA contains the nature and scope of the project, the funding available for and required by the project, and the schedule by which the project must be complete. Although the RFA can be communicated by telephone call or e-mail, in a preferred embodiment of the present invention, the RFA is generated by theclient 160 usingsystem 100. Specifically, the client uses itsworkstation 135 to connect toLAN 105 through the corporate intranet 130 (FIG. 1 ). The applications onweb server 115 prompt theclient 160 for all of the necessary information required to complete the RFA 165. The data contained in the RFA 165 is stored indatabase 122 in separate files associated with the project. - After the
client 160 and the andproject manager 170 have finalized the RFA, it goes through an approval process (described below) within theclient management chain 162. Once the RFA has been approved byclient management 162 is it automatically forwarded tofacilities management 172 for approval and assignment of aproject manager 170. Once theproject manager 170 has been assigned and receives the approved RFA, theproject manager 170 uses the RFA as a blueprint. As shown in loop 173, theproject manager 170 can typically delegate portions of the project to other groups (e.g., design work and its management can be delegated to a design group within the organization). As will be further described below, theproject manager 170 creates bid packages, purchase orders and orcontracts 175 which are used to solicit the work fromvendors 180. Typicallyproject managers 170 work with thevarious vendors 180 in refining the nature and scope of the project. Theproject managers 170 receive proposals from thevendors 180 who are bidding on the whole or pieces of the project under consideration. The communication between theproject managers 170 and the vendors can occur using the telephone or e-mail, but preferably thevendors 180 communicate with the project managers using theirworkstations 140 through theInternet 145 and firewall 150. - For larger projects, the result of the bidding and proposal process is a
contract 175 which defines, in detail, the tasks to be preformed by thevendors 180 in completing the projects. The specific tasks to be accomplished can be defined via a Purchase Order, a facilities agreement or a service agreement. Typically,contract 175 is a master contract which defines the general nature of the project as well as the general nature of the relationship between the corporation and thevendors 180. Pursuant to thecontract 175, theproject manager 170 will generate specific commitments tovendors 180 to pay for specific tasks performed by thevendors 180. Thecontract 175 further provides for the ability of theproject managers 170 to issue change orders to thevendors 180 as the scope of the project changes during the evolution of the project. - Upon completion of a task, the
vendors 180 issue aninvoice 185 to the corporation. Theinvoice 185 can be transmitted to the corporation via tradition paper method, but preferably is transmitted in an electronic form compatible withsystem 100. If received in paper form, aninvoice 185 is scanned so that it is rendered in electronic form which can be incorporated intosystem 100 indatabase 122. Theinvoice 185 is reviewed by aproject analyst 190 for comparison with the contract and the commitment to thevendor 180. Theinvoice 185 then goes through an approval process by theproject manager 195 according to the business rules for the project as further described below. Once approved, the payment on the invoice goes through anaccounting process 200 in which the payment is validated and charged against the appropriate portions of the contract. The payment is then remitted 205 to the vendor either through a credit to the vendor's Demand Deposit Account (DDA), via check or via Electronic Data Interchange (EDI) remittance. -
FIG. 2 has depicted the general process of how a project is initiated and managed. The remainder of the Figures will illustrate howsystem 100 facilitates the initiation management and closure of the project process. As previously described, the workstations for managing the project process (120, 125 inFIG. 1 ) operate in a windows environment although any other suitable network operating system (e.g., Unix) can be employed.System 100 includes security procedures, such as sign-on procedures, as known by those skilled in the art.FIG. 3 illustrates a typicaluser interface screen 250 which will help explain the structure and functions ofsystem 100. - Information concerning projects managed by
system 100 are preferably organized infolders 255 by projects. In a preferred embodiment, thefolders 255 are organized in atree structure 260.User interface 250 illustrates onetree structure 260 of a particular project 270.System 100 contains various predefined tree views offolders 255 which are selected usinglist box 265. Specifically illustrated inFIG. 3 is a tree view entitled “My Projects” inlist box 265. The tree view of “My Projects” illustrated inFIG. 3 is the standard default view ofsystem 100. The “My Projects” tree view is most frequently used by project managers and other support staff. Other tree views access information in a variety of ways. Other tree views include: a close out master view that lists all of the closed projects; a major expenditure plan view that lists all of the major projects; “my” major expenditure plan view which lists the major projects which a particular project manager is managing; a personal view that is an information folder for use by the user to store data for activities not related to specific projects; a projects by business sector view that lists all of the projects, sorted by major business division; a project by facilities division view that lists all projects sorted by a specific facilities department within the corporation; a view of projects by location that lists all of the projects sorted by location; a view of projects by project manager that lists all of the projects sorted by the project manager managing the project; a projects being supervised view that lists all of the projects being managed by the staff of a manager within the corporation; a view of recently approved documents that lists all of the documents that a user has approved within a predetermined period of time (e.g., two weeks); a view of system tables that lists various categories of system data such as roles, user profiles, and signing authorities; and a vendor view that lists all of the vendors sorted by several categories. Although the above is not an exhausted list of all of the views capable of creation in thesystem 100 of the present invention, it is a preferred list of the views. - Each of the user interface screens of the
system 100 includetoolbars system 100. In a preferred embodiment, the icons ontoolbar 275 are consistent across the user interface screens ofsystem 100. These icons provide basic functionality to all screens such as a button for returning the user to default tree view, a print button which prints the screens, a close button which closes a screen in which the user is currently operating, a tile up button that returns the screen to the standard screen format with thetree view 260 on the left hand portion of the screen and the selected item on the right hand portion of the screen, and an exit button that is used to exit the system. - The icons on
toolbar 280 change from screen to screen, depending on the function being performed by the user. Some of thetoolbar 280 icons illustrated inFIG. 3 include anew document icon 281 that produces a new document menu; a view notes button that produces a list of all notes created using the notebook feature of the present invention as further described below; a refresh button that renews and updates the tree view after completing an activity; a toggle tree button that toggles between the tree view and a full screen view of the selected item on the right hand portion of the screen; and a create note button that activates the notebook feature of the present invention. The icons ontoolbars - As previously described, information is preferably presented to the user in a
tree view 260. The specific tree view illustrated inFIG. 3 illustrates thefolders 255 associated with the project 270. The user illustrated inFIG. 3 only has a single project 270, otherwise the other projects associated with the user would be illustrated in the tree view area. - Eleven
folders 255 are shown as being associated with the project 270. The project directory folder 282 contains a listing of all of the project team members as well as the project vendors. The list is populated from database 122 (FIG. 1 ) as individuals or vendors are identified on the project. The Request For Assistance folder 284 contains the approved RFA form as described above. The budget and funding folder 286 contains all budget worksheets and funding documents. These documents include a preliminary funding document, a supplemental funding document and surrogate funding documents. Project task folder 288 contains the project tasks that are set up to assign portions of the approved budget to specific trades (e.g., plumbing) in preparation for creating commitments to vendors. Commitments bytrade folder 290 lists all of the commitments that have been prepared for a project (including draft, unapproved and approved commitments). The approved commitments folder 292 contains all of the approved commitments. The payments folder 294 contains all approved invoices from vendors for which payment has been made. The bid documents folder 296 contains all information related to bids and bid waivers. Each bid listed in this folder is assigned a unique number for accounting tracking purposes. Reports folder 298 contains a tracking report with respect to the project which lists all commitments and payments. This folder can also be used to store copies of other reports.Projects attachment folder 300 contains sub-folders for storing scan documents or electronic files of plans, specifications, correspondence, schedules and furniture/finishes information for example. The close outfolder 302 contains partial and final close out information with respect to the project. Again, the above list of folders 282-302 is not exhaustive and any folders can be created which suit the needs of the particular project being undertaken or the corporate system in which the system of the present invention operates. - The right hand portion of
screen 250 depicts the information associated with the folder selected on the left hand portion of the screen. In this particular example, the project 270 has been selected and accordingly, aprofile 304 of the project is displayed on the right hand portion ofscreen 250. Theproject profile 304 contains information related to the category of the project, the project number, the project name, the location of the project, the division for which the project is being conducted and the cost center associated with that division as well as the current phase of the project. The project profile further includes abrief project description 306 as well as anarea 308 for the project status. - Although not specifically illustrated in
FIG. 3 , every document withinsystem 100 has its own notebook in which is recorded comments, issues or status information associated with the project. The notebook feature can be activated at any time, such as while preparing a document, during the approval process, or even after final approval. Notes can be saved generally in three different categories. A first category is a comment which includes general notes for the facility staff. A second category of notes is the status of the project which contains on going project status information. This status information from the notebook is displayed in thestatus area 308 in the project profile area. The final general category of notes contains specific notes to be published to other members of the team such as the clients. The published notes are available to the clients as previously described through thecorporate intranet 130. - As previously described, the project management process initiated by a Request for Assistance (RFA).
FIG. 4 illustrates an initial user interface screen 350 for creating an RFA. The RFA is prepared either directly by a requestor or by a coordinator within the business unit requiring the project. There are generally two types of information required on an RFA, requestor information 352 and information related to the project requested 354. The input screen 350 allows the user to input all of the required information into an electronic RFA form. In a preferred embodiment, the electronic form is used for projects over a predetermined dollar amount (e.g., $10,000). If the project total is less than the predetermined amount, the user can e-mail the project and requestor information to the facility staff. The facility staff can then prepare an internal RFA on behalf of the requester so that the request can be inputted and managed within thesystem 100 of the present invention. - Once the RFA has been completed, the user saves the document and clicks on a button (not shown) to send the RFA for approval. This action brings up a
client hierarchy screen 360 illustrated inFIG. 5 . This screen represents one of the unique features of the present invention. Onscreen 360, the user is able to identify the proper personnel required to approve the RFA. In the specific example depicted inFIG. 5 , three separate approvals are required for the RFA. The first approval is abusiness unit manager 362, the second approval by a business unit controller 364 and the final approval by a business executive 366. Different rules are capable of being set in thedatabase 122 ofsystem 100 such that depending on the scope of the project (typically the total dollar amount) the number of approvals will change. For example, for larger projects (e.g., above $100,000) a business unit executive 366 will be required to approve the RFA. Inarea 368, the user is able to select the actual person who is fulfilling the role required for approval. The database ofsystem 100 contains all of the relevant information with respect to each person in each business unit that can fulfill each role (e.g., name, e-mail address, title, etc.). The user can select the appropriate person from a drop down menu by selecting the down arrow on each box inarea 368. - Once the appropriate people have been selected for the approval roles with respect to the RFA, the user clicks on the submit
button 370. This action automatically forwards the electronic RFA to the person fulfilling the role of the first level of approval required for the RFA. A notice of the pending RFA requiring approval is added to the workflow list of pending tasks of the approver. This workflow list is accessed by theapprover using button 375. When activated, this button provides a list of all of the documents requiring the persons' approval. The approver is then able to click on the notice which will bring up the actual electronic RFA document for review by the approver. After the review is complete, the reviewer is able to type any notes into a comment area of the RFA document and select one of several actions. If the approver approves the RFA, the electronic RFA is sent to the next individual in the approval hierarchy.System 100 enables electronic signatures as is well known to those skilled in the art. The approver can also return the RFA for clarifications to the previous approver or to the requester. Such an action should be accompanied by the approver including notes in the comment area which further define the clarifications required. The approver can also disapprove the RFA which sends the form directly back to the requestor or client coordinator. Again, if the RFA is disapproved, the approver should include notes in the comment area including reasons for the disapproval. Finally, the approver can discontinue the review of the RFA and come back to complete the review at a later time. In this action, the notice of the pending RFA will remain in the approver's work list. If the RFA is approved by the final approver in the client hierarchy, the form is automatically routed to a dispatcher in the project management staff. At this point, the approved RFA is assigned a project number and a project manager. - The automatic approval process of the present invention has several distinct advantages. First, the process is instantaneous. Once a document has been submitted for approval, notice of the receipt of the document for approval is immediately sent to the approver and the document is immediately available for review. This is in sharp contrast to the prior art method of approval in which documents typically were rerouted using interoffice mail. Apart from the delay associated with such a mail system, documents were often lost or misplaced. Tracking the status of approvals using the present invention is as simple as clicking on a button on the user's screen. The prior art required someone to conduct a series of phone calls, e-mails and personal visits to the approvers. Another advantage of the approval hierarchy of the present invention is that it recognized the corporate reality that people often change jobs, responsibilities, and locations. If such a change occurs, the
database 122 ofsystem 100 is easily modified to reflect the change. For example, if someone having the role of an approver is promoted and another person takes over the role, the database can be easily modified to replace the promoted person with the successor. Any subsequent approvals will then be automatically forwarded to the successor. Similarly, if someone having a role is on a temporary leave or absence, any task assigned to that person (e.g., approvals) can be easily and temporarily reassigned to a substitute person. - Additional functionality provided to the clients of
system 100 is the ability to view a list of RFAs for its business unit by clickingbutton 378. This button will bring up a window containing all of the RFAs of the business unit. The list will include the project name, the date prepared, the status of the RFA and the status of the funding of the project. In a similar manner, a client is able to view a list of all of the finding documents by clicking onbutton 380. The finding list will display all of the funding documents for projects on which the user is involved. Once a list is displayed in thesystem 100 of the present invention, the user is able to view the actual documents associated with the item by selecting the particular item. - After the approved RFA has been received by the project staff, one of the first tasks for the project staff is to create a budget and funding documents for the project.
FIG. 6 illustrates auser input screen 400 for creating budgets and funding documents. In a preferred embodiment, budgets are created using predefined templates.Area 402 allows the user to view a list of all of the budget templates available withinsystem 100. These templates can either be global (general formats available to all personnel) or private (i.e., templates that the user has personally created for his or her own use). Once a template is selected, the template is displayed inarea 403 on the left hand portion ofscreen 400. In the preferred construction embodiment of the present invention, the templates contain three levels of project information, including individual trades (e.g., lighting fixtures), trade categories (e.g., electrical) and summary categories (e.g., construction, 404 inFIG. 6 ). The templates inarea 403 can be viewed in the standard view as illustrated inFIG. 6 , or a tree view as previously described, that shows summary categories in expandable folders. - Once the template is displayed, the user is able to create the unique budget for the project in area 406 by dragging and dropping the items from the
template area 403 into the budget area 406. For each item in the budget, the user is required to input theunit 408,quantity 410 andprice 412. Once these items 408-412 have been input by the user,system 100 automatically calculates the cost of theitem 414. Additionally,system 100 allocates the cost as acapital item 416 or anexpense item 418.System 100 additionally calculates an allowed contingency amount 420 which can be set in the system as a percentage of the cost (e.g., 10% of the capital cost). The user is able to increase or decrease this contingency amount inarea 422. - If the creation of the budget document lasts longer than the user session, the user can save the budget as a worksheet and come back at a later time and complete the budget. Once the budget has been finalized, it is saved in a final form. The budget is then used to create a funding document that requires approval. The budget is a very complex and detailed document(s) that potentially includes hundreds of trades, capital items, expense items, etc. Rather than have the client and facilities management approve the very detailed budget, the system of the present invention generates a funding document for approval. An example of a funding document is depicted in
FIG. 13 . The funding document ofFIG. 13 was generated by a template accessing data from the database containing the budget. It is appreciated that any template can be used to generate any type or form of funding document desired. As seen in this Figure, the funding document summarizes the capital items for theproject 700 as well as theexpense items 705. Thesesummaries FIG. 13 are the names of the approvers of the funding document as well as the dates of the approval. The funding document indicates approval by both the facilities department 710 as well as the management of thebusiness unit 715. - As previously described with the approval process for an RFA, the project staff member submits the funding document for approval which is automatically forwarded to the facilities hierarchy for approval. Again, the first person in the facilities hierarchy receives a notice in his or her work list regarding the funding document to be approved. The same automatic forwarding of approved documents is follows as described above with respect to an RFA. Again, if at any level of the approval process the reviewer denies approval or requests further clarification, the funding document is automatically returned to the previous approver with notes in the comments section providing reasons for the disapproval or the required clarification. Once the funding document has been approved by all levels of the facilities hierarchy, it is automatically forwarded to the client hierarchy for its approval. In a preferred embodiment, the client business unit has a similar level hierarchy for approvals, depending on the scope and size of the project. The same approval process is repeated within the client business unit including automatic forwarding of approved funding documents. Once the funding document has received final approval from the client hierarchy, it is automatically forwarded to the assigned project manager who acknowledges the approved funding document. The funds are now available for commitments and the process of managing the project begins.
- With the approved RFA and budget in place, the project manager is able to begin the actual project management. This process starts with the project manager generating commitments to vendors for various aspects of the projects. In the preferred construction embodiment of the present invention, the commitments include: architectural/engineering on calls; Purchase Orders; bids; bid waivers; contracts; change orders; and work orders. Architectural/engineering on-calls are commitments for on-call consultant services which typically result in the generation of a purchase order. A Purchase Order is a commitment for goods, materials, equipment or services, typically up to a predetermined dollar amount (e.g., $25,000). In the preferred embodiment, commitments over the predetermined amount (e.g., $25,000), require competitive bids. Again, these bids result in purchase orders for goods, materials and equipment or contracts for the provision of services. Alternatively, for commitments over the predetermined dollar amount, biding can be waived pursuant to a special bid waiver approval process. Work orders are commitments made against a master contract with a vendor for certain services of any dollar amount and for other trade services up to a predetermined amount (e.g., $10,000). Change orders are amendments to previously approved purchase orders or contracts, either increasing or decreasing the dollar amount. The change order results in a revised purchase order or a revised contract.
- The commitments are created against the previously approved funding and begin with the creation of a project task that assigns a portion of the approved budget to a specific trade. In order to create a project task for a commitment, the project manager selects the new document icon (281 in
FIG. 3 ) to create the task. Activation of thisicon 281 displays a document selection menu which includes the various documents which the project manager is able to create. A selection exists for each of the above-identified types of commitments (e.g., an on-call commitment). By selecting one of the items, the project manager is required to complete a description of the project task including the trade, the protocol for the commitment (e.g., source, bid, waived bid, negotiated, national contract), the type of commitment (e.g., purchase order, contract, work order) the tax status of the commitment (e.g., taxable, nontaxable) and a detailed description of the scope of work to perform pursuant to the commitment. - The project manager is further required to complete a trade code details section. All of the trade codes that are contained within the approved budget are displayed (e.g., electrical). The project manager is able to drag and drop the applicable trades from the project budget to the trade code portion of the project task. The project manager then types in the dollar amount for each applicable trade for the commitment. Once the project manager has completed the above, the project manager saves the project task and is then able to generate the actual commitment.
-
FIG. 7 illustrates acomplete commitment request 450 for an architectural/engineering on-call. In creating thiscommitment 450, the project manager was prompted to enter information related to theproject 455, information related to the consultant (vendor) 460, the scope of the job and the square footage affected and the fees associated therewith 465, as well as a summary of the funding andfinancial commitments 470, both with respect to this particular commitments and the project in total. Many of the items found on this on-call commitment were obtained from pull down menus (not shown) such as the consultant. Other items such as the cost center to be changed for work performed are provided bysystem 100 as a default once the project number is inputted by the project manager. Once the on-call commitment has been completed by the project manager, the project manager submits the commitment for approval to the project staff. As previously described, the approval process is automatic, with each level of approval being able to approve the document, disapprove the document or return the document for clarification. - In addition to the electronic commitment,
system 100 provides the project manager with the capability of scanning in additional documents that are associated with the commitment or creating any attachment such as spreadsheets, JPEG files, drawings. In the preferred embodiment, such attachments are created using Object Linking and Embedding (OLE) compliant software. Additional documents attached to a commitment may include proposals from the consultant or vendor. These attachments are available for review by the approvers at their work stations by selecting a view menu and selecting the attachments choice on the view menu (not shown). - Once an on-call commitment request has received final approval,
system 100 automatically generates a purchase order number and notifies the project manager (electronically) of the purchase order number. A hard copy of the purchase order is issued by the project staff to the vendor. Preferably, the vendor is also able to obtain an electronic copy of the purchase order through the Internet interface previously described with respect toFIG. 1 . The purchase order contains all of the basic information contained in the on-call commitment request as illustrated inFIG. 7 . In the preferred embodiment, when the vendor opens the electronic purchase order (or other document such as a contract or a change order), the vendor is presented with a set of appropriate functions. For example, for contracts, a command button will be provided to Agree to the terms or Not Agree with an opportunity to comment or create addendum. The Agree function invokes an electronic signature process. Some functionality may not be available based on the stage of a particular process. For example, invoices cannot be created until a work document has been accepted. - In the preferred embodiment, records relating to a vendor remain available in
system 100 for a period of at least one year following the job's completion. Documents the vendor can author include Bids, RFQs, Invoices, Punch Lists, Lien Waivers and Messages. Documents the vendor can receive and process with limited functionality are Request for Proposals, Contracts, Work/Purchase Orders, Change Orders, Payment Confirmations and Meeting notices. In this preferred embodiment, the vendor is only allowed to view documents they authored or documents intended for them. The ability to delete documents are limited from a vendor's perspective and may only be allowed depending on the state of a document. This will provide for a document draft feature prior to posting to the workflow. - The generation of a project task for purchase orders is the same as described above with respect to on-call commitments.
FIG. 8 illustrates a request for apurchase order commitment 475 generated bysystem 100 of the present invention. Theproject profile information 455 is the same as described above with respect to the on-call commitment. Thecommitment information 480 includes the trade involved, the type of commitment (a purchase order in this example) and the protocol for the commitment. The vendor information 485 describes the vendor to which the Purchase Order is to be issued. Again, this information can be input by the project manager using drag and drop methods previously described from a master list of vendors for the selected trade. The selection of vendors can either by from all of the vendors contained in the system or from vendors with which the corporation has a master contract. The cost associated with the purchase order is entered in area 490 and the summary of the financial commitments is again listed inarea 470. As with the on-call commitment described above, the project manager is able to scan non-electronic documents into the system for attachment to the purchase order. Once the purchase order request has been saved, it can be submitted for approval and proceeds through the approval hierarchy as previously described. Upon final approval, the purchase order is issued to the vendor with notification being made to the project manager electronically. - A project task for a bid is again created as described above. Once the project task has been created, the project manager is then able to create a bid package 500 as illustrated in
FIG. 9 .System 100 automatically assigns abid number 502 to the bid package as well as assigning thebid status 504 of “initialization”. As previously described, a bid is an object that can have many documents associated therewith. Each document can have a separate approval process as described above. There is not necessarily a one to one relationship between documents and the object with which they are associated. Thetrade 506 is obtained by the system from the information provided by the project manager in the creation of the project task. The project manager then inputs the invitation and bid due dates 508 and 510 as required by the project. The contract type 512 is selected by the project manager from a pull down menu (not shown). The project manager further inputs any special instruction inarea 514. Thebid package total 518 is automatically calculated by the system as the sum of the tasks 520. The tasks 520 are initially populated bysystem 100 from the entries input the project manager when creating the project task. The project manager can add additional tasks in area 520 that he or she desires to be bid upon. The task can relate to the same project number or be associated with different projects, Theprice options 522 defaults to a base price, but the project manager can select alternative pricing options from a pull down menu (not shown). The documents supporting the bid are listed inarea 524 and include such documents as architectural or engineering drawings as well as equipment specifications. - Once the bid package has been saved. The project manger is provided with a bid package vendor selection screen that allows the project manger to choose the vendors from which bids will be requested. Again, the project manager is able to select the vendors from a list complied from the
database 122 insystem 100. Once the project manager has finished selecting the vendors from which bids will be requested, the list is saved and submitted for automatic approval as described above. Once the list of proposed bidders has been approved, the bid package is sent to each of the bidders in hard copy form and preferably in electronic form. - Prior to the bid due date, the bidders submit their bid proposals in response to the bid package. Due to legal concerns, it its preferable that the bids be opened and witnessed by two and preferably three witnesses.
FIG. 10 illustrates an input screen 550 used for conducting the bid opening. As illustrated in this Figure, threewitnesses 552 are provided.System 100 requires thesewitnesses 552 to input their IDs and passwords when conducting the bid opening. As each bid is open, the information from each vendor is input intoarea 554. The vendor name and the price options are defaulted by thesystem 100 from the approved proposed bidder list previously described. Theamount 556 is obtained from the vendors bid and is input into the system by the project staff. Additionally, the actual bid documents are scanned intosystem 100 and linked as attachment to the project. Once all of the bids from the selected bidders have been entered, the bid responses on screen 550 is saved and the bid opening is officially closed. The project manager is now able to perform an evaluation of the bids. - In performing the bid evaluation, the project manager selects the bid documents folder (296 in
FIG. 3 ) to view the various bids. The bid documents folder contains all of the bids associated with the selected project. Selecting a modify button (not shown) activates abid evaluation screen 560 as illustrated inFIG. 1l . As seen inscreen 560, each of the bidding vendors is displayed. The project manager is able to enter aqualified price 562 which is either the bid amount submitted by the vendor during the bidding process or an adjusted amount due to clarifications with the vendor after the bid has been opened. The project manager is additionally able to enter any comments on the pricing inarea 564 with respect to each of the vendors. The project manger is then required to rank the vendors inarea 566 and provide a reason for selecting a particular vendor inarea 568. If addition documents have been submitted by the vendors, they can be scanned in and attached to the data for project as well as other attachment such as drawings. Once the project manager has completed his or herranking 556, the bid evaluation is saved and submitted for approval. The automatic approval process proceeds as described above with respect to the approval hierarchy. - The above has described a process for creating and approving three types of commitments, namely architecture/engineering on calls, purchase orders and bids. Similar processes are performed for the creation and approval of bid waivers, work orders and change orders. These processes shall not be specifically described herein, those skilled in the art appreciated how such processes are accomplished.
- After the commitments have been made to the various vendors and the work has been completed, the vendors submitted invoices for the services and materials provided pursuant to the commitments. In a preferred embodiment of the present invention, the invoices are electronically transmitted from a vendor workstation 140 (
FIG. 1 ) through theInternet 145 and the firewall 150 for receipt bysystem 100. Alternatively, paper invoices may be submitted, scanned and the data entered into the system either manually or through drag and drop methods. The project manager reviews the invoice data contained insystem 100 against the scanned copy and makes any necessary adjustments in the payment amount, retainage, freight/delivery or tax, based on the actual goods or services provided. -
FIG. 12 illustrates an example of an invoicedata entry screen 600. After an invoice has been received, thepurchase order number 602, theinvoice number 604 and theinvoice date 606 are entered.System 100, using thepurchase order number 602, automatically fills in the commitment information 608 as well as thevendor information 610. The amount of the invoice including the material amount, the freight amount and the taxable amount are entered in area 612. Once the data has been entered on invoicedata entry screen 600, the data is saved and submitted for approval. The invoice approval process follows the approval hierarchy described above with respect to the other documents generated by the system. In a preferred embodiment, if the invoice amount does not exceed the commitment amount, the project manager alone can approve the invoice. If the invoice amount does exceed the commitment amount, the project manager can prepare a change order. The change order requires approval through the hierarchy and the issuance of a revised purchase order reflecting the adjusted commitment amount. Once the invoice has been approved, the payment can be made to the vendor either through the issuance as by check, crediting of the vendors demand deposit account, or through other EDI means. - One further advantage of the present invention is the automatic nature of the tracking of the accounting information. A general rule is that any required accounting information (e.g., the business unit to which items will be charged) is captured by the system as soon as possible and thereafter carried through throughout the project. For example, once the client identifies the business unit to be charged, this identification is automatically carried into the templates for the project, commitments and invoices. All documents created from these templates will therefore automatically carry the identification of the business unit to be charged.
- As briefly described above, one of the features of the present invention is the ability to automate the close out process. The process of closing out a project has historically been an arduous and manually intensive process. As previously described, the preferred embodiment of the present invention relates to construction projects, and the close out process will be described in terms of this embodiment. The closeout procedures of the present invention automate the financial transactions associated with the following two processes: handling of a project's CIP (construction-in-progress) account balance; and the final closing of a project.
- The CIP account is a holding account that captures a construction project's capital expenditures. At the end of the project, the balance in the CIP account is passed to a fixed asset (F/A) account for depreciation. Until the asset has been thus transferred, it cannot be depreciated. After the balance is passed to a fixed account it starts depreciating thus creating depreciation expenses for portion of the corporation that is benefitting from the project. There is no hard requirement for the construction project to be 100% complete in order to commence depreciation. Depreciation can start with the payment of the first invoice with respect to the project. Typically, financial accounting rules governing construction projects employ an 80% threshold for commencing depreciation (i.e., 80% of the project must be complete before depreciation is started). The specifics of a project might require for the depreciation to be started both before or after an 80% threshold is reached.
- As previously described, many of the processes of the method and system of the present invention are driven by the documents related to the project. The final closing of a project in the system of the present invention is a system controlled procedure that starts with automatic examination of various states of the project documents. As a result of this thorough examination, the system produces an on-line diagnostics which highlights all inconsistencies detected by the process. The problems are categorized and displayed for the project manager.
- The system performs several types functions related to close outs, including a partial close out, a full close out, abort a close out and cancel a close out. A partial closeout is a type of closeout that is done when there is a need to move a portion of CIP balance to a F/A account. On larger projects, either in terms of funds and or the period of time for completing the entire project, having multiple partial closeouts is a very useful function practical. A full closeout is a type of closeout that is performed by the project manager only once. After successful completion of full closeout the project is closed to any further activity (including commitments and payments). A Cancel closeout is a type of closeout that is performed by the project manager in a case where a project was initiated in the system of the present invention but, before any commitments were issued to the vendors or any invoices were paid, the decision was made to stop it. An abort closeout is a type of closeout that is performed by a project manager when the client requested to stop the project after the funding was approved, commitments were issued and/or invoices were paid.
- A trigger built in the system initiates the first partial closeout for a project when the payment of a particular invoice meets the 80% threshold. The 80% threshold is with respect to the entire project. This trigger for a partial close out can be set to occur with respect to any event that is kept track of in the system. For example if there are several phases of a project, the trigger can cause a partial closeout at the completion of a particular phase. The trigger initiates a workflow process gets started that opens a closeout session. The system automatically links all of the paid invoices for the project to the closeout session created by the trigger. The system also generates a substantial number (sometimes hundreds) of financial transactions that will be sent to the General Ledger (G/L).
- The work flow process sends the generated transactions to an analyst in the financial area. After reviewing the transactions, the analyst approves the session. This single automated procedure alone replaces a substantial manual effort (document collection, data entry, data validation, etc.,) which would take weeks or even months to complete. The financial analyst can request that the system start a partial closeout if needed. In the preferred embodiment, there is no system-imposed limit on the number of partial closeouts that can be processed by the system.
-
FIG. 14 illustrates the close out information that the system makes available to the project manager. As previously described with respect toFIG. 3 , the tree structure of folders in the project manager's directory includes a close outfolder 800. Opening the close out folder brings up thescreen 802 seen in the left hand portion ofFIG. 14 . Close outscreen 802 contains six tabs 805-830 for viewing further information with respect to the status of the various close outs with respect to a project. - As illustrated in
screen 802 inFIG. 14 , theFinancial Summary tab 805 displays a summary of the overall financial status of the project. Information in area 835 provides identification of the project, while the information in area 840 summarized the actual financials. The financial information in area 840 includes the budget for the project, the amount of the budget that has been committed, the amount of the commitments that have been paid, the percentage of the budget that has been paid, the retainage held and the retainage paid. On thissingle summary screen 802, the project manager is quickly able to obtain a summary of the progress, from the financial point of view, of the project. - Each of the other tabs,
commitments 810,unapproved budget 815,unapproved commitments 820,change orders 825 andinvoices 830 respectively bring up screen that detail the status of the subject matter related to the items associated with the tab. For example, thecommitments tab 820 brings up a screen (not shown) that shows in detail all of the commitments that were created in the system. For each commitment, the screen shows the vendor to which the commitment has made, the category (e.g., construction, move) the amount of the commitment, the amount paid to date and the remaining balance of the commitment. The remainder of the tabs 810-830 bring up similar screens that list all of the items associated with the tab. - The
folders Closeout Ledger 850 and Partial 860 in the project manager's tree directory contain further information related to the closeout status. Thecloseout ledger folder 850 bring up ascreen 900 as illustrated inFIG. 15 . Thisledger screen 900 includes a summary are 905 and adetailed area 910. Within thedetailed area 910, there is an entry for each of the closeouts associated with the project. In the particular example depicted in this Figure, only a single partial closeout has been executed with respect to the project.FIG. 16 illustrates the details associated with a partial closeout. Area 950 lists the project information and the project details are listed in area 955.Area 960 contains the details as to the G/L accounts to which the items in the partial closeout were assigned.Area 970 details the different G/L accounts to which items were posted as well as the depreciation schedule that is assigned to the items. - When a project has been completed, the project manager initiates a final closeout. Again, the full level of automation associated with the partial closeout as described above is applied to the full close out. In contrast to a partial closeout though, additional tests are performed to make sure that no unfinished business associated with the project is left unattended. For example, one test is performed to expose any unpaid invoices. Another test is performed to identify any commitment that is not fully paid. A further test is performed to identify any credit from a third party (e.g. a real estate) due to the project that is not collected. And so on. A full diagnostic of the state of the project is presented to the project manager in a manner of seconds and a list of actions required is fully identified. In the prior art manual process, this undertaking would have required days if not weeks to complete.
- To close projects that were canceled before they were started and those that were stopped after they were started, two other types of closeout processing are performed as previously described, Cancel closeouts and Abort closeouts. Various tests are performed by the system to help the project manager to handle these exceptional conditions correctly.
- Although the present invention has been described in relation to particular embodiments thereof, many other variations and other uses will be apparent to those skilled in the art. It is preferred, therefore, that the present invention be limited not by the specific disclosure herein, but only by the appended claims.
Claims (23)
1-67. (canceled)
68. A construction payment management system comprising:
a server that stores an application, the application receiving information from a participant in a construction project; and
a database server connected to the server, the database server storing the information of the participant, the application accessing the information of the participant in order to transfer to the participant a payment associated with the construction project.
69. The construction payment management system of claim 68 , further comprising a notification module.
70. The construction payment management system claim 69 , wherein the notification module is an inbox for timely communications of messages and documents to the participant.
71. The construction payment management system of claim 68 , wherein the participant is a vendor.
72. The construction payment management system of claim 71 , wherein the vendor is a construction entity.
73. The construction payment management system of claim 68 , wherein the information is an invoice relating to the construction project.
74. The construction payment management system of claim 68 , further comprising a web server, wherein the participant accesses the construction project through the web server.
75. The construction payment management system of claim 68 , wherein the construction project is associated with a document collection and the document collection is maintained in the database server.
76. The construction payment management system of claim 75 , wherein the document collection has a plurality of documents, each of the plurality of documents in the document collection being associated with a respective electronic notebook, the documents in the document collection being electronic documents, each electronic notebook including associated categories, for each electronic notebook the categories provided including:
a comment category that includes general notes;
a status category that includes a status of the construction project ; and
a published notes category, the method including publishing notes in the published notes category to a team working on the construction project.
77. The construction payment management system of claim 68 , wherein the received information is encrypted during transmission.
78. The construction payment management system of claim 68 , wherein the construction project being a contract and the document collection including contract documents.
79. The construction payment management system of claim 68 , wherein the construction project is engineering related.
80. The construction payment management system of claim 68 , wherein the construction project is architectural related.
81. A method of managing a construction payment process implemented by a computer, the method comprising:
receiving by an application an invoice and a lien waiver from a participant in a construction project;
approving the invoice; and
transferring monetary funds to the participant.
82. The method of claim 81 , further wherein transferring monetary funds to the participant is achieved by one of the following: giving a credit to the participant's Demand Deposit Account (DDA), issuing a check, or using Electronic Data Interchange (EDI) remittance.
83. The method of claim 81 , wherein the construction project is associated with a document collection and the document collection is maintained in the database server.
84. The method of claim 83 , wherein the document collection has a plurality of documents, each of the plurality of documents in the document collection being associated with a respective electronic notebook, the documents in the document collection being electronic documents, each electronic notebook including associated categories, for each electronic notebook the categories provided including:
a comment category that includes general notes;
a status category that includes a status of the construction project ; and
a published notes category, the method including publishing notes in the published notes category to a team working on the construction project.
85. The method of claim 84 , wherein approving the invoice further comprising:
identifying approvers that comprises an approval hierarchy, the approval hierarchy being a series of approvers;
automatically forwarding a notice requesting approval of at least one electronic document, in the document collection, from a previous approver to a successive one of the approvers upon approval of the at least one electronic document by the previous approver in the approval hierarchy.
86. The method of claim 81 , wherein the construction project being a contract and the document collection including contract documents.
87. The method of claim 81 , wherein the construction project is engineering related.
88. The method of claim 81 , wherein the construction project is architectural related.
89. A construction payment management system comprising:
a server that stores an application, the application receiving information from a participant in a construction project, wherein the information is encrypted during transmission;
an inbox allowing timely communication of messages and documents to the participant;
a web server, wherein the participant accesses the construction project through the web server; and
a database server connected to the server, the database server storing the information of the participant, the application accessing the information of the participant in order to transfer to the participant a payment associated with the construction project, wherein the construction project is associated with a document collection and the document collection is maintained in the database server, wherein the document collection has a plurality of documents, each of the plurality of documents in the document collection being associated with a respective electronic notebook, the documents in the document collection being electronic documents, each electronic notebook including associated categories, for each electronic notebook the categories provided including:
a comment category that includes general notes;
a status category that includes a status of the construction project ; and
a published notes category, the method including publishing notes in the published notes category to a team working on the construction project.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/844,903 US20080027861A1 (en) | 1999-11-04 | 2007-08-24 | System and method for automatic financial project management |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16350699P | 1999-11-04 | 1999-11-04 | |
US09/705,486 US7321864B1 (en) | 1999-11-04 | 2000-11-03 | System and method for providing funding approval associated with a project based on a document collection |
US11/844,903 US20080027861A1 (en) | 1999-11-04 | 2007-08-24 | System and method for automatic financial project management |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/705,486 Continuation US7321864B1 (en) | 1999-11-04 | 2000-11-03 | System and method for providing funding approval associated with a project based on a document collection |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080027861A1 true US20080027861A1 (en) | 2008-01-31 |
Family
ID=38950951
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/705,486 Expired - Lifetime US7321864B1 (en) | 1999-11-04 | 2000-11-03 | System and method for providing funding approval associated with a project based on a document collection |
US11/844,903 Abandoned US20080027861A1 (en) | 1999-11-04 | 2007-08-24 | System and method for automatic financial project management |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/705,486 Expired - Lifetime US7321864B1 (en) | 1999-11-04 | 2000-11-03 | System and method for providing funding approval associated with a project based on a document collection |
Country Status (1)
Country | Link |
---|---|
US (2) | US7321864B1 (en) |
Cited By (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050289051A1 (en) * | 2004-06-29 | 2005-12-29 | Allin Patrick J | Construction payment management system and method |
US20080147468A1 (en) * | 2004-06-29 | 2008-06-19 | Textura, Llc. | Construction payment management system and method with automated electronic document generation features |
US20080208602A1 (en) * | 2007-01-09 | 2008-08-28 | Westernoff W Gary | Method and apparatus for an on-line building registry and organizer |
US20090030794A1 (en) * | 2007-07-23 | 2009-01-29 | One On One Ads, Inc. | Online marketing tool using videos to promote printable coupons |
US20090171724A1 (en) * | 2007-04-05 | 2009-07-02 | Allin Patrick J | Construction payment management system and method with sub-tier document exchange and approval features |
US20090222820A1 (en) * | 2008-02-29 | 2009-09-03 | Canon Kabushiki Kaisha | Information processing apparatus, information processing method, and information processing program |
US20090319429A1 (en) * | 2008-06-23 | 2009-12-24 | Bank Of America Corp. | Systems and methods for cash positioning and reporting |
US20100063910A1 (en) * | 2008-09-05 | 2010-03-11 | Oracle International Corporation | Providing a unified view of contract revenue and invoice details |
US20100070881A1 (en) * | 2008-09-12 | 2010-03-18 | At&T Intellectual Property I, L.P. | Project facilitation and collaboration application |
US20100198652A1 (en) * | 2009-01-30 | 2010-08-05 | Exact Logix Inc | System for the Management of Construction Projects |
WO2011079306A2 (en) * | 2009-12-24 | 2011-06-30 | Clearspire Service Company, Llc | A system and method for total resource management |
US20120116932A1 (en) * | 2010-11-08 | 2012-05-10 | Bank Of America Corporation | Evaluating requests using historical benchmarking |
US20120116936A1 (en) * | 2010-11-08 | 2012-05-10 | Bank Of America Corporation | Integrated facility managment system |
WO2013049803A1 (en) * | 2011-09-30 | 2013-04-04 | Ecates, Inc. | Worksite safety, planning and environmental documentation and mapping system and method |
US20130198102A1 (en) * | 2012-01-30 | 2013-08-01 | Bank Of America | Method and apparatus for approving a transaction |
US20140081862A1 (en) * | 2008-07-29 | 2014-03-20 | Barbara Elizabeth Patterson | Transaction processing using a global unique identifier |
US20140236783A1 (en) * | 2011-03-10 | 2014-08-21 | Ebay Inc. | Managing delivery of application server content |
US9189816B1 (en) | 2011-06-14 | 2015-11-17 | Amazon Technologies, Inc. | Budget planner for softlines |
CN107944665A (en) * | 2017-11-01 | 2018-04-20 | 北京新机场建设指挥部 | A kind of Engineering Project Information Management System and method |
US10013715B2 (en) | 2014-07-21 | 2018-07-03 | Bank Of America Corporation | Temporary waiver tool |
US10531069B2 (en) | 2012-11-08 | 2020-01-07 | Ultrahaptics IP Two Limited | Three-dimensional image sensors |
WO2021142434A1 (en) * | 2020-01-10 | 2021-07-15 | Procore Technologies, Inc. | Computer system and method for tracking the impact of a change event |
US11086963B2 (en) | 2018-12-05 | 2021-08-10 | Ebay Inc. | Adaptive data platforms |
Families Citing this family (147)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1159799B1 (en) * | 1999-02-26 | 2006-07-26 | Bitwise Designs, Inc. | Digital file management and imaging system and method including secure file marking |
US7058817B1 (en) | 1999-07-02 | 2006-06-06 | The Chase Manhattan Bank | System and method for single sign on process for websites with multiple applications and services |
US7321864B1 (en) * | 1999-11-04 | 2008-01-22 | Jpmorgan Chase Bank, N.A. | System and method for providing funding approval associated with a project based on a document collection |
WO2001033477A2 (en) * | 1999-11-04 | 2001-05-10 | Jpmorgan Chase Bank | System and method for automated financial project management |
US8571975B1 (en) | 1999-11-24 | 2013-10-29 | Jpmorgan Chase Bank, N.A. | System and method for sending money via E-mail over the internet |
US8706618B2 (en) | 2005-09-29 | 2014-04-22 | Ebay Inc. | Release of funds based on criteria |
US7499875B1 (en) | 2000-03-17 | 2009-03-03 | Ebay Inc. | Method and apparatus for facilitating online payment transactions in a network-based transaction facility using multiple payment instruments |
AU2001245754A1 (en) * | 2000-03-17 | 2001-10-03 | Ebay, Inc. | Method and apparatus for facilitating online payment transactions in a network-based transaction facility using multiple payment instruments |
US10185936B2 (en) * | 2000-06-22 | 2019-01-22 | Jpmorgan Chase Bank, N.A. | Method and system for processing internet payments |
US7103556B2 (en) * | 2000-11-02 | 2006-09-05 | Jpmorgan Chase Bank, N.A. | System and method for aggregate portfolio client support |
US20070294617A1 (en) * | 2000-12-23 | 2007-12-20 | Kroeger Dann E | System, method, and article of manufacture for scheduling and document management integration |
US20020133470A1 (en) * | 2001-01-10 | 2002-09-19 | Gruber Robert M. | Material ordering and reporting expediter (MORE) |
US8849716B1 (en) | 2001-04-20 | 2014-09-30 | Jpmorgan Chase Bank, N.A. | System and method for preventing identity theft or misuse by restricting access |
WO2002099598A2 (en) | 2001-06-07 | 2002-12-12 | First Usa Bank, N.A. | System and method for rapid updating of credit information |
US7191141B2 (en) * | 2001-06-13 | 2007-03-13 | Ricoh Company, Ltd. | Automated management of development project files over a network |
US7266839B2 (en) | 2001-07-12 | 2007-09-04 | J P Morgan Chase Bank | System and method for providing discriminated content to network users |
EP1425680A4 (en) * | 2001-08-31 | 2006-05-03 | Trac Medical Solutions Inc | System for interactive processing of form documents |
CA2466071C (en) * | 2001-11-01 | 2016-04-12 | Bank One, Delaware, N.A. | System and method for establishing or modifying an account with user selectable terms |
US7987501B2 (en) | 2001-12-04 | 2011-07-26 | Jpmorgan Chase Bank, N.A. | System and method for single session sign-on |
US20180165441A1 (en) | 2002-03-25 | 2018-06-14 | Glenn Cobourn Everhart | Systems and methods for multifactor authentication |
US7424702B1 (en) | 2002-08-19 | 2008-09-09 | Sprint Communications Company L.P. | Data integration techniques for use in enterprise architecture modeling |
US7058660B2 (en) | 2002-10-02 | 2006-06-06 | Bank One Corporation | System and method for network-based project management |
US8301493B2 (en) | 2002-11-05 | 2012-10-30 | Jpmorgan Chase Bank, N.A. | System and method for providing incentives to consumers to share information |
CA2451164C (en) * | 2003-09-11 | 2016-08-30 | Teamplate Inc. | Customizable components |
CA2443454A1 (en) * | 2003-09-11 | 2005-03-11 | Teamplate Inc. | Data binding method in workflow system |
US8805731B2 (en) * | 2003-10-24 | 2014-08-12 | Elbert Harris | Construction project submittal management |
PL1687725T3 (en) * | 2003-11-26 | 2021-02-08 | Veroguard Systems Pty Limited | Secure payment system |
US7983968B1 (en) | 2004-04-01 | 2011-07-19 | Hometelos, L.P. | Facilitating submission and processing of requests to perform services on real property |
US7813978B2 (en) * | 2004-05-03 | 2010-10-12 | Ge Corporate Financial Services, Inc. | Methods and systems for managing and approving legal expenses |
US7849438B1 (en) | 2004-05-27 | 2010-12-07 | Sprint Communications Company L.P. | Enterprise software development process for outsourced developers |
US8655756B2 (en) | 2004-06-04 | 2014-02-18 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8606723B2 (en) * | 2004-06-04 | 2013-12-10 | Sap Ag | Consistent set of interfaces derived from a business object model |
WO2006038924A2 (en) * | 2004-06-18 | 2006-04-13 | Sap Ag | Consistent set of interfaces derived from a business object model |
US9460441B2 (en) * | 2004-06-29 | 2016-10-04 | Textura Corporation | Construction payment management system and method with document exchange features |
US20060047811A1 (en) * | 2004-09-01 | 2006-03-02 | Microsoft Corporation | Method and system of providing access to various data associated with a project |
US20060101031A1 (en) * | 2004-10-21 | 2006-05-11 | Faul Jacob J | Automated dynamic routing of documents based on database storage of user relationships |
US8744937B2 (en) * | 2005-02-25 | 2014-06-03 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8041650B2 (en) * | 2005-03-11 | 2011-10-18 | Howard Marcus | Method and system for directed documentation of construction projects |
US7801809B1 (en) * | 2005-06-24 | 2010-09-21 | Fannie Mae | System and method for management of delegated real estate project reviews |
US8645175B1 (en) * | 2005-07-12 | 2014-02-04 | Open Text S.A. | Workflow system and method for single call batch processing of collections of database records |
US8484065B1 (en) | 2005-07-14 | 2013-07-09 | Sprint Communications Company L.P. | Small enhancement process workflow manager |
US8583926B1 (en) | 2005-09-19 | 2013-11-12 | Jpmorgan Chase Bank, N.A. | System and method for anti-phishing authentication |
IL172208A0 (en) * | 2005-11-28 | 2009-02-11 | Bniya & Internet Ltd | Method for monitoring and controlling the construction of an engineering project |
US8166061B2 (en) * | 2006-01-10 | 2012-04-24 | Aol Inc. | Searching recent content publication activity |
US20070214491A1 (en) * | 2006-03-07 | 2007-09-13 | Shield Security Systems, L.L.C. | Interactive security control system and method with automated order submission and approval process |
US20070219840A1 (en) * | 2006-03-09 | 2007-09-20 | Tierra Right Of Way Services, Ltd. | System and method for web based project management |
US8374931B2 (en) * | 2006-03-31 | 2013-02-12 | Sap Ag | Consistent set of interfaces derived from a business object model |
WO2007134265A2 (en) * | 2006-05-12 | 2007-11-22 | Captaris, Inc. | Workflow data binding |
EP2076874A4 (en) * | 2006-05-13 | 2011-03-09 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8392364B2 (en) * | 2006-07-10 | 2013-03-05 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8566193B2 (en) * | 2006-08-11 | 2013-10-22 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8468544B1 (en) | 2006-09-28 | 2013-06-18 | Sap Ag | Managing consistent interfaces for demand planning business objects across heterogeneous systems |
US8010397B1 (en) * | 2007-01-23 | 2011-08-30 | Sprint Communications Company L.P. | Enterprise infrastructure development systems and methods |
US10402757B1 (en) * | 2007-03-16 | 2019-09-03 | Devfactory Fz-Llc | System and method for outsourcing projects |
US8473735B1 (en) | 2007-05-17 | 2013-06-25 | Jpmorgan Chase | Systems and methods for managing digital certificates |
US20080309665A1 (en) * | 2007-06-13 | 2008-12-18 | 3D Systems, Inc., A California Corporation | Distributed rapid prototyping |
US20090063240A1 (en) * | 2007-08-30 | 2009-03-05 | Oracle International Corporation | Routing transactions in a multiple job environment using an approval framework |
US8321919B2 (en) * | 2007-09-05 | 2012-11-27 | Oracle International Corp. | Framework for delegating roles in human resources ERP systems |
US8321682B1 (en) | 2008-01-24 | 2012-11-27 | Jpmorgan Chase Bank, N.A. | System and method for generating and managing administrator passwords |
US8417593B2 (en) * | 2008-02-28 | 2013-04-09 | Sap Ag | System and computer-readable medium for managing consistent interfaces for business objects across heterogeneous systems |
US8423418B2 (en) * | 2008-03-31 | 2013-04-16 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US20090249358A1 (en) * | 2008-03-31 | 2009-10-01 | Sap Ag | Managing Consistent Interfaces for Kanban Business Objects Across Heterogeneous Systems |
US8364715B2 (en) * | 2008-03-31 | 2013-01-29 | Sap Ag | Managing consistent interfaces for automatic identification label business objects across heterogeneous systems |
US8930248B2 (en) * | 2008-03-31 | 2015-01-06 | Sap Se | Managing consistent interfaces for supply network business objects across heterogeneous systems |
US8413165B2 (en) | 2008-03-31 | 2013-04-02 | Sap Ag | Managing consistent interfaces for maintenance order business objects across heterogeneous systems |
US8433585B2 (en) * | 2008-03-31 | 2013-04-30 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8589263B2 (en) * | 2008-03-31 | 2013-11-19 | Sap Ag | Managing consistent interfaces for retail business objects across heterogeneous systems |
US8577991B2 (en) * | 2008-03-31 | 2013-11-05 | Sap Ag | Managing consistent interfaces for internal service request business objects across heterogeneous systems |
US8473317B2 (en) * | 2008-03-31 | 2013-06-25 | Sap Ag | Managing consistent interfaces for service part business objects across heterogeneous systems |
US20090248463A1 (en) * | 2008-03-31 | 2009-10-01 | Emmanuel Piochon | Managing Consistent Interfaces For Trading Business Objects Across Heterogeneous Systems |
US8370233B2 (en) * | 2008-03-31 | 2013-02-05 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8165934B2 (en) * | 2008-06-20 | 2012-04-24 | Micro Graphic Information Services Corp. | Automated invoice processing software and services |
US20090326988A1 (en) * | 2008-06-26 | 2009-12-31 | Robert Barth | Managing consistent interfaces for business objects across heterogeneous systems |
US8566185B2 (en) * | 2008-06-26 | 2013-10-22 | Sap Ag | Managing consistent interfaces for financial instrument business objects across heterogeneous systems |
US8671064B2 (en) * | 2008-06-26 | 2014-03-11 | Sap Ag | Managing consistent interfaces for supply chain management business objects across heterogeneous systems |
US8645228B2 (en) * | 2008-06-26 | 2014-02-04 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8286171B2 (en) | 2008-07-21 | 2012-10-09 | Workshare Technology, Inc. | Methods and systems to fingerprint textual information using word runs |
US8412556B2 (en) * | 2008-07-31 | 2013-04-02 | Siemens Aktiengesellschaft | Systems and methods for facilitating an analysis of a business project |
US8630888B2 (en) * | 2008-07-31 | 2014-01-14 | Siemens Aktiengesellschaft | Systems and methods for analyzing a potential business partner |
US9092636B2 (en) | 2008-11-18 | 2015-07-28 | Workshare Technology, Inc. | Methods and systems for exact data match filtering |
US8463666B2 (en) * | 2008-11-25 | 2013-06-11 | Sap Ag | Managing consistent interfaces for merchandise and assortment planning business objects across heterogeneous systems |
US8577760B2 (en) | 2008-11-25 | 2013-11-05 | Sap Ag | Managing consistent interfaces for tax authority business objects across heterogeneous systems |
US20100153297A1 (en) * | 2008-12-12 | 2010-06-17 | Sap Ag | Managing Consistent Interfaces for Credit Portfolio Business Objects Across Heterogeneous Systems |
US20100211610A1 (en) * | 2009-02-17 | 2010-08-19 | American Express Travel Related Services Company, Inc. | Method and system for managing financial transaction data |
US9608826B2 (en) | 2009-06-29 | 2017-03-28 | Jpmorgan Chase Bank, N.A. | System and method for partner key management |
US20110029351A1 (en) * | 2009-07-31 | 2011-02-03 | Siemens Ag | Systems and Methods for Providing Compliance Functions in a Business Entity |
US8396751B2 (en) * | 2009-09-30 | 2013-03-12 | Sap Ag | Managing consistent interfaces for merchandising business objects across heterogeneous systems |
US20110167007A1 (en) * | 2010-01-07 | 2011-07-07 | Chris Saitta | System and method for task management |
US9135585B2 (en) | 2010-06-15 | 2015-09-15 | Sap Se | Managing consistent interfaces for property library, property list template, quantity conversion virtual object, and supplier property specification business objects across heterogeneous systems |
US8732083B2 (en) | 2010-06-15 | 2014-05-20 | Sap Ag | Managing consistent interfaces for number range, number range profile, payment card payment authorisation, and product template template business objects across heterogeneous systems |
US8515794B2 (en) | 2010-06-15 | 2013-08-20 | Sap Ag | Managing consistent interfaces for employee time event and human capital management view of payroll process business objects across heterogeneous systems |
US8412603B2 (en) | 2010-06-15 | 2013-04-02 | Sap Ag | Managing consistent interfaces for currency conversion and date and time business objects across heterogeneous systems |
US8417588B2 (en) | 2010-06-15 | 2013-04-09 | Sap Ag | Managing consistent interfaces for goods tag, production bill of material hierarchy, and release order template business objects across heterogeneous systems |
US8370272B2 (en) | 2010-06-15 | 2013-02-05 | Sap Ag | Managing consistent interfaces for business document message monitoring view, customs arrangement, and freight list business objects across heterogeneous systems |
US8364608B2 (en) | 2010-06-15 | 2013-01-29 | Sap Ag | Managing consistent interfaces for export declaration and export declaration request business objects across heterogeneous systems |
US20120133989A1 (en) | 2010-11-29 | 2012-05-31 | Workshare Technology, Inc. | System and method for providing a common framework for reviewing comparisons of electronic documents |
US10783326B2 (en) | 2013-03-14 | 2020-09-22 | Workshare, Ltd. | System for tracking changes in a collaborative document editing environment |
US11030163B2 (en) | 2011-11-29 | 2021-06-08 | Workshare, Ltd. | System for tracking and displaying changes in a set of related electronic documents |
US10574729B2 (en) | 2011-06-08 | 2020-02-25 | Workshare Ltd. | System and method for cross platform document sharing |
US9613340B2 (en) * | 2011-06-14 | 2017-04-04 | Workshare Ltd. | Method and system for shared document approval |
US9170990B2 (en) | 2013-03-14 | 2015-10-27 | Workshare Limited | Method and system for document retrieval with selective document comparison |
US10963584B2 (en) | 2011-06-08 | 2021-03-30 | Workshare Ltd. | Method and system for collaborative editing of a remotely stored document |
US9948676B2 (en) | 2013-07-25 | 2018-04-17 | Workshare, Ltd. | System and method for securing documents prior to transmission |
US10880359B2 (en) | 2011-12-21 | 2020-12-29 | Workshare, Ltd. | System and method for cross platform document sharing |
US8666845B2 (en) | 2011-07-28 | 2014-03-04 | Sap Ag | Managing consistent interfaces for a customer requirement business object across heterogeneous systems |
US8775280B2 (en) | 2011-07-28 | 2014-07-08 | Sap Ag | Managing consistent interfaces for financial business objects across heterogeneous systems |
US8560392B2 (en) | 2011-07-28 | 2013-10-15 | Sap Ag | Managing consistent interfaces for a point of sale transaction business object across heterogeneous systems |
US8725654B2 (en) | 2011-07-28 | 2014-05-13 | Sap Ag | Managing consistent interfaces for employee data replication business objects across heterogeneous systems |
US8601490B2 (en) | 2011-07-28 | 2013-12-03 | Sap Ag | Managing consistent interfaces for business rule business object across heterogeneous systems |
US8521838B2 (en) | 2011-07-28 | 2013-08-27 | Sap Ag | Managing consistent interfaces for communication system and object identifier mapping business objects across heterogeneous systems |
US9237425B2 (en) | 2012-02-16 | 2016-01-12 | Sap Se | Consistent interface for feed event, feed event document and feed event type |
US8756274B2 (en) | 2012-02-16 | 2014-06-17 | Sap Ag | Consistent interface for sales territory message type set 1 |
US8762453B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for feed collaboration group and feed event subscription |
US8984050B2 (en) | 2012-02-16 | 2015-03-17 | Sap Se | Consistent interface for sales territory message type set 2 |
US8762454B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for flag and tag |
US9232368B2 (en) | 2012-02-16 | 2016-01-05 | Sap Se | Consistent interface for user feed administrator, user feed event link and user feed settings |
US8949855B2 (en) | 2012-06-28 | 2015-02-03 | Sap Se | Consistent interface for address snapshot and approval process definition |
US8615451B1 (en) | 2012-06-28 | 2013-12-24 | Sap Ag | Consistent interface for goods and activity confirmation |
US9367826B2 (en) | 2012-06-28 | 2016-06-14 | Sap Se | Consistent interface for entitlement product |
WO2014000200A1 (en) | 2012-06-28 | 2014-01-03 | Sap Ag | Consistent interface for document output request |
US8521621B1 (en) | 2012-06-28 | 2013-08-27 | Sap Ag | Consistent interface for inbound delivery request |
US9246869B2 (en) | 2012-06-28 | 2016-01-26 | Sap Se | Consistent interface for opportunity |
US8756135B2 (en) | 2012-06-28 | 2014-06-17 | Sap Ag | Consistent interface for product valuation data and product valuation level |
US9400998B2 (en) | 2012-06-28 | 2016-07-26 | Sap Se | Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule |
US20140012740A1 (en) * | 2012-07-06 | 2014-01-09 | Great Bridge Corporation | Collecting and analyzing transaction datacollecting and analyzing transaction and demographic data to fulfill queries and target surveys |
US9547833B2 (en) | 2012-08-22 | 2017-01-17 | Sap Se | Consistent interface for financial instrument impairment calculation |
US9043236B2 (en) | 2012-08-22 | 2015-05-26 | Sap Se | Consistent interface for financial instrument impairment attribute values analytical result |
US9076112B2 (en) | 2012-08-22 | 2015-07-07 | Sap Se | Consistent interface for financial instrument impairment expected cash flow analytical result |
US20140164238A1 (en) * | 2012-12-12 | 2014-06-12 | Sap Ag | Concurrent Servicing of Multiple Processing Requests |
US8856234B2 (en) | 2013-02-28 | 2014-10-07 | Workiva Llc | System and method for performing distributed asynchronous calculations in a networked environment |
US11567907B2 (en) | 2013-03-14 | 2023-01-31 | Workshare, Ltd. | Method and system for comparing document versions encoded in a hierarchical representation |
US9191357B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for email activity business object |
US9191343B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for appointment activity business object |
US9419957B1 (en) | 2013-03-15 | 2016-08-16 | Jpmorgan Chase Bank, N.A. | Confidence-based authentication |
US10911492B2 (en) | 2013-07-25 | 2021-02-02 | Workshare Ltd. | System and method for securing documents prior to transmission |
US10148726B1 (en) | 2014-01-24 | 2018-12-04 | Jpmorgan Chase Bank, N.A. | Initiating operating system commands based on browser cookies |
US20150262126A1 (en) * | 2014-03-14 | 2015-09-17 | Poplicus Inc. | Method and system for aggregating records for a project from disparate databases |
GB201417262D0 (en) * | 2014-09-30 | 2014-11-12 | Bizagi Group | Contextual workflow management |
US11182551B2 (en) | 2014-12-29 | 2021-11-23 | Workshare Ltd. | System and method for determining document version geneology |
US10133723B2 (en) | 2014-12-29 | 2018-11-20 | Workshare Ltd. | System and method for determining document version geneology |
US10410178B2 (en) | 2015-03-16 | 2019-09-10 | Moca Systems, Inc. | Method for graphical pull planning with active work schedules |
US11763013B2 (en) | 2015-08-07 | 2023-09-19 | Workshare, Ltd. | Transaction document management system and method |
US20170308836A1 (en) * | 2016-04-22 | 2017-10-26 | Accenture Global Solutions Limited | Hierarchical visualization for decision review systems |
US11556991B1 (en) * | 2017-12-29 | 2023-01-17 | Wells Fargo Bank, N.A. | Network-based joint investment platform |
US11074530B1 (en) | 2018-12-21 | 2021-07-27 | Wells Fargo Bank, N.A. | Systems and methods for improved project management |
CN112801629B (en) * | 2021-02-04 | 2022-05-27 | 江西清能高科技术有限公司 | Scientific and technological innovation platform project declaration method and system based on multi-level encryption |
US11494799B1 (en) * | 2021-05-14 | 2022-11-08 | William C. Rehm | Supporting action tracking and deeds between multiple parties |
Citations (195)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3860870A (en) * | 1973-01-12 | 1975-01-14 | Nippon Electric Co | Microwave relay system having auxiliary signal transmission arrangement |
US3896266A (en) * | 1971-08-09 | 1975-07-22 | Nelson J Waterbury | Credit and other security cards and card utilization systems therefore |
US3938091A (en) * | 1972-03-17 | 1976-02-10 | Atalla Technovations Company | Personal verification system |
US4567359A (en) * | 1984-05-24 | 1986-01-28 | Lockwood Lawrence B | Automatic information, goods and services dispensing system |
US4725719A (en) * | 1986-07-21 | 1988-02-16 | First City National Bank Of Austin | Restricted purpose, commercial, monetary regulation method |
US4799156A (en) * | 1986-10-01 | 1989-01-17 | Strategic Processing Corporation | Interactive market management system |
US4801787A (en) * | 1985-07-05 | 1989-01-31 | Casio Computer Co., Ltd. | IC card identification system having first and second data identification functions |
US4941090A (en) * | 1989-01-27 | 1990-07-10 | Mccarthy Patrick D | Centralized consumer cash value accumulation system for multiple merchants |
US4992940A (en) * | 1989-03-13 | 1991-02-12 | H-Renee, Incorporated | System and method for automated selection of equipment for purchase through input of user desired specifications |
US5084816A (en) * | 1987-11-25 | 1992-01-28 | Bell Communications Research, Inc. | Real time fault tolerant transaction processing system |
US5117355A (en) * | 1989-01-27 | 1992-05-26 | Mccarthy Patrick D | Centralized consumer cash valve accumulation system for multiple merchants |
US5189606A (en) * | 1989-08-30 | 1993-02-23 | The United States Of America As Represented By The Secretary Of The Air Force | Totally integrated construction cost estimating, analysis, and reporting system |
US5220501A (en) * | 1989-12-08 | 1993-06-15 | Online Resources, Ltd. | Method and system for remote delivery of retail banking services |
US5287268A (en) * | 1989-01-27 | 1994-02-15 | Mccarthy Patrick D | Centralized consumer cash value accumulation system for multiple merchants |
US5315504A (en) * | 1989-03-14 | 1994-05-24 | International Business Machines Corporation | Electronic document approval system |
US5317683A (en) * | 1990-09-10 | 1994-05-31 | International Business Machines Corporation | Method and apparatus for automated meeting agenda generation in a data processing system |
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 |
US5381332A (en) * | 1991-12-09 | 1995-01-10 | Motorola, Inc. | Project management system with automated schedule and cost integration |
US5412708A (en) * | 1993-03-12 | 1995-05-02 | Katz; Ronald A. | Videophone system for scrutiny monitoring with computer control |
US5420405A (en) * | 1993-02-26 | 1995-05-30 | Chasek; Norman E. | Secure, automated transaction system that supports an electronic currency operating in mixed debit & credit modes |
US5485370A (en) * | 1988-05-05 | 1996-01-16 | Transaction Technology, Inc. | Home services delivery system with intelligent terminal emulator |
US5532920A (en) * | 1992-04-29 | 1996-07-02 | International Business Machines Corporation | Data processing system and method to enforce payment of royalties when copying softcopy books |
US5534855A (en) * | 1992-07-20 | 1996-07-09 | Digital Equipment Corporation | Method and system for certificate based alias detection |
US5537473A (en) * | 1991-07-08 | 1996-07-16 | Amstrad Public Limited Company | Video recorder system |
US5537314A (en) * | 1994-04-18 | 1996-07-16 | First Marketrust Intl. | Referral recognition system for an incentive award program |
US5548506A (en) * | 1994-03-17 | 1996-08-20 | Srinivasan; Seshan R. | Automated, electronic network based, project management server system, for managing multiple work-groups |
US5592553A (en) * | 1993-07-30 | 1997-01-07 | International Business Machines Corporation | Authentication system using one-time passwords |
US5592378A (en) * | 1994-08-19 | 1997-01-07 | Andersen Consulting Llp | Computerized order entry system and method |
US5592560A (en) * | 1989-05-01 | 1997-01-07 | Credit Verification Corporation | Method and system for building a database and performing marketing based upon prior shopping history |
US5594837A (en) * | 1993-01-29 | 1997-01-14 | Noyes; Dallas B. | Method for representation of knowledge in a computer as a network database system |
US5598557A (en) * | 1992-09-22 | 1997-01-28 | Caere Corporation | Apparatus and method for retrieving and grouping images representing text files based on the relevance of key words extracted from a selected file to the text files |
US5603025A (en) * | 1994-07-29 | 1997-02-11 | Borland International, Inc. | Methods for hypertext reporting in a relational database management system |
US5602936A (en) * | 1993-01-21 | 1997-02-11 | Greenway Corporation | Method of and apparatus for document data recapture |
US5604490A (en) * | 1994-09-09 | 1997-02-18 | International Business Machines Corporation | Method and system for providing a user access to multiple secured subsystems |
US5606496A (en) * | 1990-08-14 | 1997-02-25 | Aegis Technologies, Inc. | Personal assistant computer method |
US5634101A (en) * | 1991-05-31 | 1997-05-27 | R. Alan Blau & Associates, Co. | Method and apparatus for obtaining consumer information |
US5638457A (en) * | 1989-05-01 | 1997-06-10 | Credit Verification Corporation | Method and system for building a database for use with selective incentive marketing in response to customer shopping histories |
US5640577A (en) * | 1991-12-30 | 1997-06-17 | Davox Corporation | Data processing system with automated at least partial forms completion |
US5642419A (en) * | 1994-04-28 | 1997-06-24 | Citibank N.A. | Method for acquiring and revalidating an electronic credential |
US5644493A (en) * | 1991-08-30 | 1997-07-01 | Nsk Ltd. | Production information processing system |
US5706452A (en) * | 1995-12-06 | 1998-01-06 | Ivanov; Vladimir I. | Method and apparatus for structuring and managing the participatory evaluation of documents by a plurality of reviewers |
US5710886A (en) * | 1995-06-16 | 1998-01-20 | Sellectsoft, L.C. | Electric couponing method and apparatus |
US5710887A (en) * | 1995-08-29 | 1998-01-20 | Broadvision | Computer system and method for electronic commerce |
US5710889A (en) * | 1995-02-22 | 1998-01-20 | Citibank, N.A. | Interface device for electronically integrating global financial services |
US5715402A (en) * | 1995-11-09 | 1998-02-03 | Spot Metals Online | Method and system for matching sellers and buyers of spot metals |
US5715298A (en) * | 1996-05-16 | 1998-02-03 | Telepay | Automated interactive bill payment system using debit cards |
US5715399A (en) * | 1995-03-30 | 1998-02-03 | Amazon.Com, Inc. | Secure method and system for communicating a list of credit card numbers over a non-secure network |
US5715314A (en) * | 1994-10-24 | 1998-02-03 | Open Market, Inc. | Network sales system |
US5715450A (en) * | 1995-09-27 | 1998-02-03 | Siebel Systems, Inc. | Method of selecting and presenting data from a database using a query language to a user of a computer system |
US5754840A (en) * | 1996-01-23 | 1998-05-19 | Smartpatents, Inc. | System, method, and computer program product for developing and maintaining documents which includes analyzing a patent application with regards to the specification and claims |
US5758328A (en) * | 1996-02-22 | 1998-05-26 | Giovannoli; Joseph | Computerized quotation system and method |
US5758126A (en) * | 1996-03-19 | 1998-05-26 | Sterling Commerce, Inc. | Customizable bidirectional EDI translation system |
US5761288A (en) * | 1995-06-05 | 1998-06-02 | Mitel Corporation | Service context sensitive features and applications |
US5761661A (en) * | 1994-07-14 | 1998-06-02 | The Sabre Group, Inc. | Data management system and method |
US5761647A (en) * | 1996-05-24 | 1998-06-02 | Harrah's Operating Company, Inc. | National customer recognition system and method |
US5765140A (en) * | 1995-11-17 | 1998-06-09 | Mci Corporation | Dynamic project management system |
US5765141A (en) * | 1995-10-06 | 1998-06-09 | Spector; Donald | Computerized merchandising system |
US5764789A (en) * | 1994-11-28 | 1998-06-09 | Smarttouch, Llc | Tokenless biometric ATM access system |
US5765143A (en) * | 1995-02-28 | 1998-06-09 | Triad Systems Corporation | Method and system for inventory management |
US5768382A (en) * | 1995-11-22 | 1998-06-16 | Walker Asset Management Limited Partnership | Remote-auditing of computer generated outcomes and authenticated biling and access control system using cryptographic and other protocols |
US5774122A (en) * | 1989-09-29 | 1998-06-30 | Hitachi, Ltd. | Method for visual programming with aid of animation |
US5857079A (en) * | 1994-12-23 | 1999-01-05 | Lucent Technologies Inc. | Smart card for automatic financial records |
US5862323A (en) * | 1995-11-13 | 1999-01-19 | International Business Machines Corporation | Retrieving plain-text passwords from a main registry by a plurality of foreign registries |
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 |
US5864830A (en) * | 1997-02-13 | 1999-01-26 | Armetta; David | Data processing method of configuring and monitoring a satellite spending card linked to a host credit card |
US5866889A (en) * | 1995-06-07 | 1999-02-02 | Citibank, N.A. | Integrated full service consumer banking system and system and method for opening an account |
US5870718A (en) * | 1996-02-26 | 1999-02-09 | Spector; Donald | Computer-printer terminal for producing composite greeting and gift certificate card |
US5870725A (en) * | 1995-08-11 | 1999-02-09 | Wachovia Corporation | High volume financial image media creation and display system and method |
US5870724A (en) * | 1989-12-08 | 1999-02-09 | Online Resources & Communications Corporation | Targeting advertising in a home retail banking delivery service |
US5870721A (en) * | 1993-08-27 | 1999-02-09 | Affinity Technology Group, Inc. | System and method for real time loan approval |
US5871398A (en) * | 1995-06-30 | 1999-02-16 | Walker Asset Management Limited Partnership | Off-line remote system for lotteries and games of skill |
US5873096A (en) * | 1997-10-08 | 1999-02-16 | Siebel Systems, Inc. | Method of maintaining a network of partially replicated database system |
US5873072A (en) * | 1991-07-25 | 1999-02-16 | Checkfree Corporation | System and method for electronically providing customer services including payment of bills, financial analysis and loans |
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 |
US5909486A (en) * | 1997-03-19 | 1999-06-01 | Walker Asset Management Limited Partnership | Method and apparatus for awarding and redeeming prepaid telephone time |
US5910988A (en) * | 1997-08-27 | 1999-06-08 | Csp Holdings, Inc. | Remote image capture with centralized processing and storage |
US5913202A (en) * | 1996-12-03 | 1999-06-15 | Fujitsu Limited | Financial information intermediary system |
US5915244A (en) * | 1996-12-31 | 1999-06-22 | Bi Performance Services | Computerized incentive program with plateau pricing and remote award redemption |
US5914472A (en) * | 1997-09-23 | 1999-06-22 | At&T Corp | Credit card spending authorization control system |
US5918239A (en) * | 1997-01-21 | 1999-06-29 | International Business Machines Corporation | Deferred display of web pages corresponding to links selected by user |
US5918214A (en) * | 1996-10-25 | 1999-06-29 | Ipf, Inc. | System and method for finding product and service related information on the internet |
US5918217A (en) * | 1997-12-10 | 1999-06-29 | Financial Engines, Inc. | User interface for a financial advisory system |
US6012088A (en) * | 1996-12-10 | 2000-01-04 | International Business Machines Corporation | Automatic configuration for internet access device |
US6010404A (en) * | 1997-04-03 | 2000-01-04 | Walker Asset Management Limited Partnership | Method and apparatus for using a player input code to affect a gambling outcome |
US6014635A (en) * | 1997-12-08 | 2000-01-11 | Shc Direct, Inc. | System and method for providing a discount credit transaction network |
US6012983A (en) * | 1996-12-30 | 2000-01-11 | Walker Asset Management Limited Partnership | Automated play gaming device |
US6014641A (en) * | 1996-12-11 | 2000-01-11 | Walker Asset Management Limited Partnership | Method and apparatus for providing open-ended subscriptions to commodity items normally available only through term-based subscriptions |
US6014645A (en) * | 1996-04-19 | 2000-01-11 | Block Financial Corporation | Real-time financial card application system |
US6014439A (en) * | 1997-04-08 | 2000-01-11 | Walker Asset Management Limited Partnership | Method and apparatus for entertaining callers in a queue |
US6014639A (en) * | 1997-11-05 | 2000-01-11 | International Business Machines Corporation | Electronic catalog system for exploring a multitude of hierarchies, using attribute relevance and forwarding-checking |
US6014636A (en) * | 1997-05-06 | 2000-01-11 | Lucent Technologies Inc. | Point of sale method and system |
US6016476A (en) * | 1997-08-11 | 2000-01-18 | International Business Machines Corporation | Portable information and transaction processing system and method utilizing biometric authorization and digital certificate security |
US6018718A (en) * | 1997-08-28 | 2000-01-25 | Walker Asset Management Limited Partnership | Method and system for processing customized reward offers |
US6016810A (en) * | 1995-01-31 | 2000-01-25 | Boston Scientific Corporation | Endovasular aortic graft |
US6018714A (en) * | 1997-11-08 | 2000-01-25 | Ip Value, Llc | Method of protecting against a change in value of intellectual property, and product providing such protection |
US6026429A (en) * | 1995-06-07 | 2000-02-15 | America Online, Inc. | Seamless integration of internet resources |
US6026398A (en) * | 1997-10-16 | 2000-02-15 | Imarket, Incorporated | System and methods for searching and matching databases |
US6032147A (en) * | 1996-04-24 | 2000-02-29 | Linguateq, Inc. | Method and apparatus for rationalizing different data formats in a data management system |
US6032134A (en) * | 1998-11-18 | 2000-02-29 | Weissman; Steven I. | Credit card billing system for identifying expenditures on a credit card account |
US6061665A (en) * | 1997-06-06 | 2000-05-09 | Verifone, Inc. | System, method and article of manufacture for dynamic negotiation of a network payment framework |
US6064987A (en) * | 1997-03-21 | 2000-05-16 | Walker Digital, Llc | Method and apparatus for providing and processing installment plans at a terminal |
US6065120A (en) * | 1997-12-09 | 2000-05-16 | Phone.Com, Inc. | Method and system for self-provisioning a rendezvous to ensure secure access to information in a database from multiple devices |
US6067531A (en) * | 1998-07-21 | 2000-05-23 | Mci Communications Corporation | Automated contract negotiator/generation system and method |
US6065675A (en) * | 1997-06-30 | 2000-05-23 | Cardis Enterprise International N.V. | Processing system and method for a heterogeneous electronic cash environment |
US6070244A (en) * | 1997-11-10 | 2000-05-30 | The Chase Manhattan Bank | Computer network security management system |
US6070147A (en) * | 1996-07-02 | 2000-05-30 | Tecmark Services, Inc. | Customer identification and marketing analysis systems |
US6070153A (en) * | 1997-11-21 | 2000-05-30 | Simpson; Mark S. | System and method for automatically investing a portion of a credit card interest charged amount in an investment account |
US6073113A (en) * | 1998-06-29 | 2000-06-06 | Sun Microsystems, Inc. | Compatibility checking between instruments, operations and protocols in electronic commerce |
US6073105A (en) * | 1997-06-13 | 2000-06-06 | Tele-Publishing, Inc. | Interactive personals online network method and apparatus |
US6075519A (en) * | 1993-08-06 | 2000-06-13 | Minolta Co., Ltd. | Operational mode setting apparatus for display screen |
US6076072A (en) * | 1996-06-10 | 2000-06-13 | Libman; Richard Marc | Method and apparatus for preparing client communications involving financial products and services |
US6081810A (en) * | 1998-02-03 | 2000-06-27 | Electronic Data Systems Corporation | Report database system |
US6081900A (en) * | 1999-03-16 | 2000-06-27 | Novell, Inc. | Secure intranet access |
US6081790A (en) * | 1998-03-20 | 2000-06-27 | Citibank, N.A. | System and method for secure presentment and payment over open networks |
US6170011B1 (en) * | 1998-09-11 | 2001-01-02 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for determining and initiating interaction directionality within a multimedia communication center |
US6178511B1 (en) * | 1998-04-30 | 2001-01-23 | International Business Machines Corporation | Coordinating user target logons in a single sign-on (SSO) environment |
US6182225B1 (en) * | 1997-02-03 | 2001-01-30 | Canon Kabushiki Kaisha | Network data base control device and method thereof |
US6182052B1 (en) * | 1994-06-06 | 2001-01-30 | Huntington Bancshares Incorporated | Communications network interface for user friendly interactive access to online services |
US6182220B1 (en) * | 1998-03-30 | 2001-01-30 | International Business Machines Corporation | System and method for building and exchanging encrypted passwords between a client and server |
US6182142B1 (en) * | 1998-07-10 | 2001-01-30 | Encommerce, Inc. | Distributed access management of information resources |
US6185242B1 (en) * | 2000-05-24 | 2001-02-06 | South Carolina Systems, Inc. | Integral side wall and tap hole cover for an eccentric bottom tap (EBT) electric furnace |
US6189029B1 (en) * | 1996-09-20 | 2001-02-13 | Silicon Graphics, Inc. | Web survey tool builder and result compiler |
US6195644B1 (en) * | 1987-07-08 | 2001-02-27 | Stuart S. Bowie | Computer program and system for credit card companies for recording and processing bonus credits issued to card users |
US6226679B1 (en) * | 1997-06-30 | 2001-05-01 | Sun Microsystems, Inc. | Common management information protocol (CMIP) agent registration methods systems and computer program products |
US6226623B1 (en) * | 1996-05-23 | 2001-05-01 | Citibank, N.A. | Global financial services integration system and process |
US6226752B1 (en) * | 1999-05-11 | 2001-05-01 | Sun Microsystems, Inc. | Method and apparatus for authenticating users |
US6230148B1 (en) * | 1994-11-28 | 2001-05-08 | Veristar Corporation | Tokenless biometric electric check transaction |
US6227447B1 (en) * | 1999-05-10 | 2001-05-08 | First Usa Bank, Na | Cardless payment system |
US6243816B1 (en) * | 1998-04-30 | 2001-06-05 | International Business Machines Corporation | Single sign-on (SSO) mechanism personal key manager |
US6243688B1 (en) * | 1997-04-14 | 2001-06-05 | Dyan T. Kalina | Internet-based credit interchange system of converting purchase credit awards through credit exchange system for purchase of investment vehicle |
US6253327B1 (en) * | 1998-12-02 | 2001-06-26 | Cisco Technology, Inc. | Single step network logon based on point to point protocol |
US6253328B1 (en) * | 1998-02-12 | 2001-06-26 | A. James Smith, Jr. | Method and apparatus for securing passwords and personal identification numbers |
US20020002479A1 (en) * | 1999-12-20 | 2002-01-03 | Gal Almog | Career management system |
US20020007460A1 (en) * | 2000-07-14 | 2002-01-17 | Nec Corporation | Single sign-on system and single sign-on method for a web site and recording medium |
US20020007313A1 (en) * | 2000-07-12 | 2002-01-17 | Khanh Mai | Credit system |
US20020010599A1 (en) * | 2000-01-12 | 2002-01-24 | Levison Michael D. | Method for targeting insurance policy incentive rewards |
US20020010668A1 (en) * | 2000-01-27 | 2002-01-24 | Travis Roger M. | Online merchandising and marketing system |
US6343279B1 (en) * | 1998-08-26 | 2002-01-29 | American Management Systems, Inc. | System integrating credit card transactions into a financial management system |
US6345261B1 (en) * | 1999-09-21 | 2002-02-05 | Stockback Holdings, Inc. | Customer loyalty investment program |
US20020019938A1 (en) * | 2000-08-04 | 2002-02-14 | Aarons Michael Thomas | Method and apparatus for secure identification for networked environments |
US20020018585A1 (en) * | 2000-07-19 | 2002-02-14 | Kim Young Wan | System and method for cardless secure credit transaction processing |
US6349336B1 (en) * | 1999-04-26 | 2002-02-19 | Hewlett-Packard Company | Agent/proxy connection control across a firewall |
US6349242B2 (en) * | 1999-02-05 | 2002-02-19 | First Data Corporation | Method for selectively printing messages and adding inserts to merchant statements |
US20020023108A1 (en) * | 1999-09-09 | 2002-02-21 | Neil Daswani | Automatic web form interaction proxy |
US6385591B1 (en) * | 1999-05-11 | 2002-05-07 | Jeffrey W. Mankoff | Method and system for electronic organization of coupons |
US6385652B1 (en) * | 1998-04-16 | 2002-05-07 | Citibank, N.A. | Customer access solutions architecture |
US6385594B1 (en) * | 1998-05-08 | 2002-05-07 | Lendingtree, Inc. | Method and computer network for co-ordinating a loan over the internet |
US20020059141A1 (en) * | 2000-06-07 | 2002-05-16 | The Chase Manhattan Bank | System and method for executing deposit transactions over the internet |
US6401211B1 (en) * | 1999-10-19 | 2002-06-04 | Microsoft Corporation | System and method of user logon in combination with user authentication for network access |
US6401125B1 (en) * | 1999-08-05 | 2002-06-04 | Nextpage, Inc. | System and method for maintaining state information between a web proxy server and its clients |
US6408389B2 (en) * | 1997-05-28 | 2002-06-18 | Symantec Corporation | System for supporting secured log-in of multiple users into a plurality of computers using combined presentation of memorized password and transportable passport record |
US20020077978A1 (en) * | 2000-06-22 | 2002-06-20 | The Chase Manhattan Bank | Method and system for processing internet payments |
US20020077964A1 (en) * | 1999-12-15 | 2002-06-20 | Brody Robert M. | Systems and methods for providing consumers anonymous pre-approved offers from a consumer-selected group of merchants |
US6411933B1 (en) * | 1999-11-22 | 2002-06-25 | International Business Machines Corporation | Methods and apparatus for correlating biometric attributes and biometric attribute production features |
US20030001888A1 (en) * | 2000-03-01 | 2003-01-02 | Power Mark P J | Data transfer method and apparatus |
US6505176B2 (en) * | 1998-06-12 | 2003-01-07 | First American Credit Management Solutions, Inc. | Workflow management system for an automated credit application system |
US6507912B1 (en) * | 1999-01-27 | 2003-01-14 | International Business Machines Corporation | Protection of biometric data via key-dependent sampling |
US6510523B1 (en) * | 1999-02-22 | 2003-01-21 | Sun Microsystems Inc. | Method and system for providing limited access privileges with an untrusted terminal |
US20030018915A1 (en) * | 2001-07-19 | 2003-01-23 | Louis Stoll | Method and system for user authentication and authorization of services |
US20030023880A1 (en) * | 2001-07-27 | 2003-01-30 | Edwards Nigel John | Multi-domain authorization and authentication |
US20030034388A1 (en) * | 2000-05-15 | 2003-02-20 | Larry Routhenstein | Method for generating customer secure card numbers subject to use restrictions by an electronic card |
US20030084345A1 (en) * | 2001-09-14 | 2003-05-01 | Anders Bjornestad | Managed access to information over data networks |
US20030088552A1 (en) * | 2001-11-08 | 2003-05-08 | First Data Corporation | Systems and methods of providing inserts into envelopes |
US20030084647A1 (en) * | 2001-11-08 | 2003-05-08 | First Data Corporation | Real-time intelligent packet-collation systems and methods |
US6574348B1 (en) * | 1999-09-07 | 2003-06-03 | Microsoft Corporation | Technique for watermarking an image and a resulting watermarked image |
US20030105981A1 (en) * | 2001-12-04 | 2003-06-05 | Miller Lawrence R. | System and method for single session sign-on |
US20030110399A1 (en) * | 2001-12-10 | 2003-06-12 | Electronic Data Systems Corporation | Network user authentication system and method |
US6580814B1 (en) * | 1998-07-31 | 2003-06-17 | International Business Machines Corporation | System and method for compressing biometric models |
US6581040B1 (en) * | 2000-02-18 | 2003-06-17 | Daniel B. Wright | Project specific communications system and method |
US20030115160A1 (en) * | 2001-12-19 | 2003-06-19 | First Data Corporation | Weight measuring systems and methods for weighing items |
US6584508B1 (en) * | 1999-07-13 | 2003-06-24 | Networks Associates Technology, Inc. | Advanced data guard having independently wrapped components |
US6584505B1 (en) * | 1999-07-08 | 2003-06-24 | Microsoft Corporation | Authenticating access to a network server without communicating login information through the network server |
US20030119642A1 (en) * | 2001-12-21 | 2003-06-26 | First Data Corporation | Sheet folding systems and methods |
US6675261B2 (en) * | 2000-12-22 | 2004-01-06 | Oblix, Inc. | Request based caching of data store data |
US6684384B1 (en) * | 1997-03-28 | 2004-01-27 | International Business Machines Corporation | Extensible object oriented framework for general ledger |
US6735695B1 (en) * | 1999-12-20 | 2004-05-11 | International Business Machines Corporation | Methods and apparatus for restricting access of a user using random partial biometrics |
US6738779B1 (en) * | 2001-02-21 | 2004-05-18 | Telecom Italia S.P.A. | Apparatus for and method of multiple parallel string searching |
US6751654B2 (en) * | 1999-03-31 | 2004-06-15 | International Business Machines Corporation | Simulating web cookies for non-cookie capable browsers |
US20040117409A1 (en) * | 2001-03-03 | 2004-06-17 | Scahill Francis J | Application synchronisation |
US6755341B1 (en) * | 2000-05-15 | 2004-06-29 | Jacob Y. Wong | Method for storing data in payment card transaction |
US6847957B1 (en) * | 2001-08-01 | 2005-01-25 | Oracle International Corporation | Dynamically extensible rule-based expert-system shell for database-computing environments |
US6847991B1 (en) * | 2000-09-06 | 2005-01-25 | Cisco Technology, Inc. | Data communication among processes of a network component |
US6892231B2 (en) * | 2000-11-02 | 2005-05-10 | Microsoft Corporation | Method and apparatus for verifying the contents of a global configuration file |
US20050120180A1 (en) * | 2000-03-30 | 2005-06-02 | Stephan Schornbach | Cache time determination |
US6907566B1 (en) * | 1999-04-02 | 2005-06-14 | Overture Services, Inc. | Method and system for optimum placement of advertisements on a webpage |
US6983421B1 (en) * | 2001-06-22 | 2006-01-03 | I2 Technologies Us, Inc. | Using connectors to automatically update graphical user interface elements at a client system according to an updated state of a configuration |
US6992786B1 (en) * | 2000-06-27 | 2006-01-31 | Printon Ab | Method and system for online creation and ordering of customized material for printing |
US7051199B1 (en) * | 2000-06-19 | 2006-05-23 | Xerox Corporation | System, method and article of manufacture for providing cryptographic services utilizing a network |
US7051330B1 (en) * | 2000-11-21 | 2006-05-23 | Microsoft Corporation | Generic application server and method of operation therefor |
US7058817B1 (en) * | 1999-07-02 | 2006-06-06 | The Chase Manhattan Bank | System and method for single sign on process for websites with multiple applications and services |
US7213064B2 (en) * | 2000-11-18 | 2007-05-01 | In2M Corporation | Methods and systems for job-based accounting |
US7319986B2 (en) * | 1999-09-28 | 2008-01-15 | Bank Of America Corporation | Dynamic payment cards and related management systems and associated methods |
US7321864B1 (en) * | 1999-11-04 | 2008-01-22 | Jpmorgan Chase Bank, N.A. | System and method for providing funding approval associated with a project based on a document collection |
US7647275B2 (en) * | 2001-07-05 | 2010-01-12 | Cummins-Allison Corp. | Automated payment system and method |
Family Cites Families (73)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE387462C (en) * | 1923-12-28 | Walter Meinck | Crushing, vibrating or similar machine | |
US4321672A (en) | 1979-11-26 | 1982-03-23 | Braun Edward L | Financial data processing system |
US4965825A (en) | 1981-11-03 | 1990-10-23 | The Personalized Mass Media Corporation | Signal processing apparatus and methods |
US5309355A (en) | 1984-05-24 | 1994-05-03 | Lockwood Lawrence B | Automated sales system |
US4882675A (en) | 1984-11-26 | 1989-11-21 | Steven Nichtberger | Paperless system for distributing, redeeming and clearing merchandise coupons |
US4633397A (en) | 1984-12-24 | 1986-12-30 | Richard Macco | Union member accounts management system |
US4713761A (en) | 1985-07-18 | 1987-12-15 | Pitney Bowes, Inc. | System for centralized processing of accounting and payment functions |
US4695880A (en) | 1985-07-30 | 1987-09-22 | Postron Corp. | Electronic information dissemination system |
US4926255A (en) | 1986-03-10 | 1990-05-15 | Kohorn H Von | System for evaluation of response to broadcast transmissions |
US4745468B1 (en) | 1986-03-10 | 1991-06-11 | System for evaluation and recording of responses to broadcast transmissions | |
US4823264A (en) | 1986-05-27 | 1989-04-18 | Deming Gilbert R | Electronic funds transfer system |
US4696491A (en) | 1986-06-19 | 1987-09-29 | Stenger Barbara J | Information reference book and indexing system |
EP0306781B1 (en) * | 1987-09-08 | 1994-04-20 | Wang Laboratories Inc. | Electronic mail circulation method and apparatus |
JPH01195568A (en) | 1988-01-29 | 1989-08-07 | Hitachi Ltd | Electronic document editing control system |
US4964043A (en) | 1988-06-13 | 1990-10-16 | Galvin Thomas M | System for visualizing, identifying and ordering gearing configurations |
US5016270A (en) | 1989-04-03 | 1991-05-14 | First Data Resources Inc. | Expanded telephone data organization system |
US5560008A (en) | 1989-05-15 | 1996-09-24 | International Business Machines Corporation | Remote authentication and authorization in a distributed data processing system |
US5235509A (en) | 1989-06-28 | 1993-08-10 | Management Information Support, Inc. | Customer self-ordering system using information displayed on a screen |
US5050207A (en) | 1989-11-03 | 1991-09-17 | National Transaction Network, Inc. | Portable automated teller machine |
US5157717A (en) | 1989-11-03 | 1992-10-20 | National Transaction Network, Inc. | Portable automated teller machine |
JPH03180968A (en) | 1989-12-08 | 1991-08-06 | Hitachi Ltd | Data base retrieving method and formated document outputting method using the retrieving method |
US5351186A (en) | 1991-01-16 | 1994-09-27 | Bullock Communications, Inc. | System and method for obtaining information concerning a product or a service |
US5473143A (en) | 1991-09-23 | 1995-12-05 | Atm Communications International, Inc. | ATM/POS based electronic mail system |
US5265033A (en) | 1991-09-23 | 1993-11-23 | Atm Communications International, Inc. | ATM/POS based electronic mail system |
US5467269A (en) | 1991-12-20 | 1995-11-14 | J. B. Laughrey, Inc. | Method and means for telephonically crediting customers with rebates and refunds |
US5297026A (en) | 1992-01-03 | 1994-03-22 | Frank Hoffman | System for promoting account activity |
US5241594A (en) | 1992-06-02 | 1993-08-31 | Hughes Aircraft Company | One-time logon means and methods for distributed computing systems |
GB9226475D0 (en) | 1992-12-18 | 1993-02-10 | Cambridge Display Tech Ltd | Chromophoric polymeric compositions |
US5450134A (en) | 1993-01-12 | 1995-09-12 | Visual Automation Systems, Inc. | Video facility management system for encoding and decoding video signals to facilitate identification of the video signals |
US5557334A (en) | 1993-01-12 | 1996-09-17 | Visual Automation Systems, Inc. | Apparatus for tracking the flow of video signals by incorporating patterns of machine readable signals which will appear at predetermined locations of a television picture |
AU677393B2 (en) | 1993-07-08 | 1997-04-24 | E-Talk Corporation | Method and system for transferring calls and call-related data between a plurality of call centres |
US5570465A (en) | 1993-07-22 | 1996-10-29 | Tsakanikas; Peter J. | Apparatus, method and system for printing of legal currency and negotiable instruments |
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 |
US5666493A (en) | 1993-08-24 | 1997-09-09 | Lykes Bros., Inc. | System for managing customer orders and method of implementation |
US5621789A (en) | 1993-09-01 | 1997-04-15 | Teknekron Infoswitch Corporation | Method and system for integrating a plurality of call center agent performance enhancement modules |
US5590199A (en) | 1993-10-12 | 1996-12-31 | The Mitre Corporation | Electronic information network user authentication and authorization system |
US5465206B1 (en) | 1993-11-01 | 1998-04-21 | Visa Int Service Ass | Electronic bill pay system |
US5611052A (en) * | 1993-11-01 | 1997-03-11 | The Golden 1 Credit Union | Lender direct credit evaluation and loan processing system |
US5473732A (en) | 1993-11-02 | 1995-12-05 | Chang; Hou-Mei H. | Relational artificial intelligence system |
US5446740A (en) | 1993-12-17 | 1995-08-29 | Empire Blue Cross/Blue Shield | Method of and apparatus for processing data at a remote workstation |
US5570295A (en) | 1994-03-18 | 1996-10-29 | Lucent Technologies Inc. | System and method of capturing encoded data transmitted over a communications network in a video system |
US5500513A (en) | 1994-05-11 | 1996-03-19 | Visa International | Automated purchasing control system |
US5513102A (en) | 1994-06-28 | 1996-04-30 | Auriemma Consulting Group, Inc. | Data processing methods of implementing an award to an authorized user of a credit card |
RU2144269C1 (en) * | 1994-07-19 | 2000-01-10 | Сертко, Ллс | Method of secret use of digital signatures in commercial cryptographic system |
US5583778A (en) | 1994-09-21 | 1996-12-10 | Instasearch Corp. | Computer method for collecting on judgments |
US5511117A (en) | 1994-09-26 | 1996-04-23 | Zazzera; Andre C. | Integrated voice and business transaction reporting for telephone call centers |
US5544086A (en) | 1994-09-30 | 1996-08-06 | Electronic Payment Services, Inc. | Information consolidation within a transaction network |
US6181837B1 (en) | 1994-11-18 | 2001-01-30 | The Chase Manhattan Bank, N.A. | Electronic check image storage and retrieval system |
US5546452A (en) | 1995-03-02 | 1996-08-13 | Geotel Communications Corp. | Communications system using a central controller to control at least one network and agent system |
US5625767A (en) | 1995-03-13 | 1997-04-29 | Bartell; Brian | Method and system for two-dimensional visualization of an information taxonomy and of text documents based on topical content of the documents |
US5689100A (en) | 1995-03-21 | 1997-11-18 | Martiz, Inc. | Debit card system and method for implementing incentive award program |
US5590197A (en) | 1995-04-04 | 1996-12-31 | V-One Corporation | Electronic payment system and method |
US5677955A (en) | 1995-04-07 | 1997-10-14 | Financial Services Technology Consortium | Electronic funds transfer instruments |
US5675637A (en) | 1995-05-16 | 1997-10-07 | Inventions, Inc. | Method for automatically obtaining and presenting data from multiple data sources |
JP2737695B2 (en) * | 1995-05-24 | 1998-04-08 | 日本電気株式会社 | Scan test circuit and semiconductor integrated circuit device including the same |
US5682524A (en) | 1995-05-26 | 1997-10-28 | Starfish Software, Inc. | Databank system with methods for efficiently storing non-uniform data records |
US5657383A (en) | 1995-06-06 | 1997-08-12 | Lucent Technologies Inc. | Flexible customer controlled telecommunications handling |
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 |
US5692132A (en) | 1995-06-07 | 1997-11-25 | Mastercard International, Inc. | System and method for conducting cashless transactions on a computer network |
US5703344A (en) | 1995-06-30 | 1997-12-30 | Visa International Service Association | Electronic funds confirmation at point of transaction |
US5659165A (en) | 1995-07-24 | 1997-08-19 | Citibank. N.A. | Customer-directed, automated process for transferring funds between accounts via a communications network |
US5699528A (en) | 1995-10-31 | 1997-12-16 | Mastercard International, Inc. | System and method for bill delivery and payment over a communications network |
US5671285A (en) | 1995-12-13 | 1997-09-23 | Newman; Bruce D. | Secure communication system |
US6161113A (en) * | 1997-01-21 | 2000-12-12 | Texas Instruments Incorporated | Computer-aided project notebook |
US6167378A (en) * | 1997-01-21 | 2000-12-26 | Webber, Jr.; Donald Gary | Automated back office transaction method and system |
US5950206A (en) * | 1997-04-23 | 1999-09-07 | Krause; Gary Matthew | Method and apparatus for searching and tracking construction projects in a document information database |
US6832202B1 (en) * | 1997-08-29 | 2004-12-14 | Electronic Data Systems Corporation | Method and system of routing requests for authorized approval |
US6038547A (en) * | 1998-01-07 | 2000-03-14 | Casto; Robin L. | Construction tracking and payment method and system |
US6092050A (en) * | 1998-03-09 | 2000-07-18 | Hard Dollar Corporation | Graphical computer system and method for financial estimating and project management |
US6032132A (en) * | 1998-06-12 | 2000-02-29 | Csg Systems, Inc. | Telecommunications access cost management system |
US6442567B1 (en) * | 1999-05-14 | 2002-08-27 | Appintec Corporation | Method and apparatus for improved contact and activity management and planning |
US7089203B1 (en) * | 1999-06-04 | 2006-08-08 | Crookshanks Rex J | Building construction bid and contract management system, internet-based method and computer program therefor |
US6882986B1 (en) * | 2000-08-07 | 2005-04-19 | Tymetrix | Method for automatic processing of invoices |
-
2000
- 2000-11-03 US US09/705,486 patent/US7321864B1/en not_active Expired - Lifetime
-
2007
- 2007-08-24 US US11/844,903 patent/US20080027861A1/en not_active Abandoned
Patent Citations (199)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3896266A (en) * | 1971-08-09 | 1975-07-22 | Nelson J Waterbury | Credit and other security cards and card utilization systems therefore |
US3938091A (en) * | 1972-03-17 | 1976-02-10 | Atalla Technovations Company | Personal verification system |
US3860870A (en) * | 1973-01-12 | 1975-01-14 | Nippon Electric Co | Microwave relay system having auxiliary signal transmission arrangement |
US4567359A (en) * | 1984-05-24 | 1986-01-28 | Lockwood Lawrence B | Automatic information, goods and services dispensing system |
US4801787A (en) * | 1985-07-05 | 1989-01-31 | Casio Computer Co., Ltd. | IC card identification system having first and second data identification functions |
US4725719A (en) * | 1986-07-21 | 1988-02-16 | First City National Bank Of Austin | Restricted purpose, commercial, monetary regulation method |
US4799156A (en) * | 1986-10-01 | 1989-01-17 | Strategic Processing Corporation | Interactive market management system |
US6195644B1 (en) * | 1987-07-08 | 2001-02-27 | Stuart S. Bowie | Computer program and system for credit card companies for recording and processing bonus credits issued to card users |
US5084816A (en) * | 1987-11-25 | 1992-01-28 | Bell Communications Research, Inc. | Real time fault tolerant transaction processing system |
US5485370A (en) * | 1988-05-05 | 1996-01-16 | Transaction Technology, Inc. | Home services delivery system with intelligent terminal emulator |
USRE36116E (en) * | 1989-01-27 | 1999-02-23 | Mccarthy; Patrick D. | Centralized consumer cash value accumulation system for multiple merchants |
US5117355A (en) * | 1989-01-27 | 1992-05-26 | Mccarthy Patrick D | Centralized consumer cash valve accumulation system for multiple merchants |
US4941090A (en) * | 1989-01-27 | 1990-07-10 | Mccarthy Patrick D | Centralized consumer cash value accumulation system for multiple merchants |
US5287268A (en) * | 1989-01-27 | 1994-02-15 | Mccarthy Patrick D | Centralized consumer cash value accumulation system for multiple merchants |
US4992940A (en) * | 1989-03-13 | 1991-02-12 | H-Renee, Incorporated | System and method for automated selection of equipment for purchase through input of user desired specifications |
US5315504A (en) * | 1989-03-14 | 1994-05-24 | International Business Machines Corporation | Electronic document approval system |
US5592560A (en) * | 1989-05-01 | 1997-01-07 | Credit Verification Corporation | Method and system for building a database and performing marketing based upon prior shopping history |
US5638457A (en) * | 1989-05-01 | 1997-06-10 | Credit Verification Corporation | Method and system for building a database for use with selective incentive marketing in response to customer shopping histories |
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 |
US5189606A (en) * | 1989-08-30 | 1993-02-23 | The United States Of America As Represented By The Secretary Of The Air Force | Totally integrated construction cost estimating, analysis, and reporting system |
US5774122A (en) * | 1989-09-29 | 1998-06-30 | Hitachi, Ltd. | Method for visual programming with aid of animation |
US5870724A (en) * | 1989-12-08 | 1999-02-09 | Online Resources & Communications Corporation | Targeting advertising in a home retail banking delivery service |
US5220501A (en) * | 1989-12-08 | 1993-06-15 | Online Resources, Ltd. | Method and system for remote delivery of retail banking services |
US5606496A (en) * | 1990-08-14 | 1997-02-25 | Aegis Technologies, Inc. | Personal assistant computer method |
US5317683A (en) * | 1990-09-10 | 1994-05-31 | International Business Machines Corporation | Method and apparatus for automated meeting agenda generation in a data processing system |
US5634101A (en) * | 1991-05-31 | 1997-05-27 | R. Alan Blau & Associates, Co. | Method and apparatus for obtaining consumer information |
US5537473A (en) * | 1991-07-08 | 1996-07-16 | Amstrad Public Limited Company | Video recorder system |
US5873072A (en) * | 1991-07-25 | 1999-02-16 | Checkfree Corporation | System and method for electronically providing customer services including payment of bills, financial analysis and loans |
US5644493A (en) * | 1991-08-30 | 1997-07-01 | Nsk Ltd. | Production information processing system |
US5381332A (en) * | 1991-12-09 | 1995-01-10 | Motorola, Inc. | Project management system with automated schedule and cost integration |
US5640577A (en) * | 1991-12-30 | 1997-06-17 | Davox Corporation | Data processing system with automated at least partial forms completion |
US5532920A (en) * | 1992-04-29 | 1996-07-02 | International Business Machines Corporation | Data processing system and method to enforce payment of royalties when copying softcopy books |
US5534855A (en) * | 1992-07-20 | 1996-07-09 | Digital Equipment Corporation | Method and system for certificate based alias detection |
US5598557A (en) * | 1992-09-22 | 1997-01-28 | Caere Corporation | Apparatus and method for retrieving and grouping images representing text files based on the relevance of key words extracted from a selected file to the text files |
US5602936A (en) * | 1993-01-21 | 1997-02-11 | Greenway Corporation | Method of and apparatus for document data recapture |
US5594837A (en) * | 1993-01-29 | 1997-01-14 | Noyes; Dallas B. | Method for representation of knowledge in a computer as a network database system |
US5420405A (en) * | 1993-02-26 | 1995-05-30 | Chasek; Norman E. | Secure, automated transaction system that supports an electronic currency operating in mixed debit & credit modes |
US5412708A (en) * | 1993-03-12 | 1995-05-02 | Katz; Ronald A. | Videophone system for scrutiny monitoring with computer control |
US5592553A (en) * | 1993-07-30 | 1997-01-07 | International Business Machines Corporation | Authentication system using one-time passwords |
US6075519A (en) * | 1993-08-06 | 2000-06-13 | Minolta Co., Ltd. | Operational mode setting apparatus for display screen |
US5870721A (en) * | 1993-08-27 | 1999-02-09 | Affinity Technology Group, Inc. | System and method for real time loan approval |
US5548506A (en) * | 1994-03-17 | 1996-08-20 | Srinivasan; Seshan R. | Automated, electronic network based, project management server system, for managing multiple work-groups |
US5537314A (en) * | 1994-04-18 | 1996-07-16 | First Marketrust Intl. | Referral recognition system for an incentive award program |
US5642419A (en) * | 1994-04-28 | 1997-06-24 | Citibank N.A. | Method for acquiring and revalidating an electronic credential |
US6182052B1 (en) * | 1994-06-06 | 2001-01-30 | Huntington Bancshares Incorporated | Communications network interface for user friendly interactive access to online services |
US5761661A (en) * | 1994-07-14 | 1998-06-02 | The Sabre Group, Inc. | Data management system and method |
US5603025A (en) * | 1994-07-29 | 1997-02-11 | Borland International, Inc. | Methods for hypertext reporting in a relational database management system |
US5592378A (en) * | 1994-08-19 | 1997-01-07 | Andersen Consulting Llp | Computerized order entry system and method |
US5604490A (en) * | 1994-09-09 | 1997-02-18 | International Business Machines Corporation | Method and system for providing a user access to multiple secured subsystems |
US5715314A (en) * | 1994-10-24 | 1998-02-03 | Open Market, Inc. | Network sales system |
US6230148B1 (en) * | 1994-11-28 | 2001-05-08 | Veristar Corporation | Tokenless biometric electric check transaction |
US5764789A (en) * | 1994-11-28 | 1998-06-09 | Smarttouch, Llc | Tokenless biometric ATM access system |
US5857079A (en) * | 1994-12-23 | 1999-01-05 | Lucent Technologies Inc. | Smart card for automatic financial records |
US6016810A (en) * | 1995-01-31 | 2000-01-25 | Boston Scientific Corporation | Endovasular aortic graft |
US5710889A (en) * | 1995-02-22 | 1998-01-20 | Citibank, N.A. | Interface device for electronically integrating global financial services |
US5765143A (en) * | 1995-02-28 | 1998-06-09 | Triad Systems Corporation | Method and system for inventory management |
US5899982A (en) * | 1995-03-08 | 1999-05-04 | Huntington Bancshares Incorporated | Bank-centric service platform, network and system |
US5715399A (en) * | 1995-03-30 | 1998-02-03 | Amazon.Com, Inc. | Secure method and system for communicating a list of credit card numbers over a non-secure network |
US5761288A (en) * | 1995-06-05 | 1998-06-02 | Mitel Corporation | Service context sensitive features and applications |
US6026429A (en) * | 1995-06-07 | 2000-02-15 | America Online, Inc. | Seamless integration of internet resources |
US5866889A (en) * | 1995-06-07 | 1999-02-02 | Citibank, N.A. | Integrated full service consumer banking system and system and method for opening an account |
US5710886A (en) * | 1995-06-16 | 1998-01-20 | Sellectsoft, L.C. | Electric couponing method and apparatus |
US5871398A (en) * | 1995-06-30 | 1999-02-16 | Walker Asset Management Limited Partnership | Off-line remote system for lotteries and games of skill |
US6024640A (en) * | 1995-06-30 | 2000-02-15 | Walker Asset Management Limited Partnership | Off-line remote lottery system |
US5870725A (en) * | 1995-08-11 | 1999-02-09 | Wachovia Corporation | High volume financial image media creation and display system and method |
US5710887A (en) * | 1995-08-29 | 1998-01-20 | Broadvision | Computer system and method for electronic commerce |
US5715450A (en) * | 1995-09-27 | 1998-02-03 | Siebel Systems, Inc. | Method of selecting and presenting data from a database using a query language to a user of a computer system |
US5765141A (en) * | 1995-10-06 | 1998-06-09 | Spector; Donald | Computerized merchandising system |
US5715402A (en) * | 1995-11-09 | 1998-02-03 | Spot Metals Online | Method and system for matching sellers and buyers of spot metals |
US5862323A (en) * | 1995-11-13 | 1999-01-19 | International Business Machines Corporation | Retrieving plain-text passwords from a main registry by a plurality of foreign registries |
US5765140A (en) * | 1995-11-17 | 1998-06-09 | Mci Corporation | Dynamic project management system |
US5768382A (en) * | 1995-11-22 | 1998-06-16 | Walker Asset Management Limited Partnership | Remote-auditing of computer generated outcomes and authenticated biling and access control system using cryptographic and other protocols |
US5706452A (en) * | 1995-12-06 | 1998-01-06 | Ivanov; Vladimir I. | Method and apparatus for structuring and managing the participatory evaluation of documents by a plurality of reviewers |
US5754840A (en) * | 1996-01-23 | 1998-05-19 | Smartpatents, Inc. | System, method, and computer program product for developing and maintaining documents which includes analyzing a patent application with regards to the specification and claims |
US5758328A (en) * | 1996-02-22 | 1998-05-26 | Giovannoli; Joseph | Computerized quotation system and method |
US5870718A (en) * | 1996-02-26 | 1999-02-09 | Spector; Donald | Computer-printer terminal for producing composite greeting and gift certificate card |
US5758126A (en) * | 1996-03-19 | 1998-05-26 | Sterling Commerce, Inc. | Customizable bidirectional EDI translation system |
US6014645A (en) * | 1996-04-19 | 2000-01-11 | Block Financial Corporation | Real-time financial card application system |
US6032147A (en) * | 1996-04-24 | 2000-02-29 | Linguateq, Inc. | Method and apparatus for rationalizing different data formats in a data management system |
US5715298A (en) * | 1996-05-16 | 1998-02-03 | Telepay | Automated interactive bill payment system using debit cards |
US6226623B1 (en) * | 1996-05-23 | 2001-05-01 | Citibank, N.A. | Global financial services integration system and process |
US5761647A (en) * | 1996-05-24 | 1998-06-02 | Harrah's Operating Company, Inc. | National customer recognition system and method |
US6076072A (en) * | 1996-06-10 | 2000-06-13 | Libman; Richard Marc | Method and apparatus for preparing client communications involving financial products and services |
US6070147A (en) * | 1996-07-02 | 2000-05-30 | Tecmark Services, Inc. | Customer identification and marketing analysis systems |
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 |
US6189029B1 (en) * | 1996-09-20 | 2001-02-13 | Silicon Graphics, Inc. | Web survey tool builder and result compiler |
US5918214A (en) * | 1996-10-25 | 1999-06-29 | Ipf, Inc. | System and method for finding product and service related information on the internet |
US5913202A (en) * | 1996-12-03 | 1999-06-15 | Fujitsu Limited | Financial information intermediary system |
US6012088A (en) * | 1996-12-10 | 2000-01-04 | International Business Machines Corporation | Automatic configuration for internet access device |
US6014641A (en) * | 1996-12-11 | 2000-01-11 | Walker Asset Management Limited Partnership | Method and apparatus for providing open-ended subscriptions to commodity items normally available only through term-based subscriptions |
US6012983A (en) * | 1996-12-30 | 2000-01-11 | Walker Asset Management Limited Partnership | Automated play gaming device |
US5915244A (en) * | 1996-12-31 | 1999-06-22 | Bi Performance Services | Computerized incentive program with plateau pricing and remote award redemption |
US5918239A (en) * | 1997-01-21 | 1999-06-29 | International Business Machines Corporation | Deferred display of web pages corresponding to links selected by user |
US6182225B1 (en) * | 1997-02-03 | 2001-01-30 | Canon Kabushiki Kaisha | Network data base control device and method thereof |
US5864830A (en) * | 1997-02-13 | 1999-01-26 | Armetta; David | Data processing method of configuring and monitoring a satellite spending card linked to a host credit card |
US5909486A (en) * | 1997-03-19 | 1999-06-01 | Walker Asset Management Limited Partnership | Method and apparatus for awarding and redeeming prepaid telephone time |
US6064987A (en) * | 1997-03-21 | 2000-05-16 | Walker Digital, Llc | Method and apparatus for providing and processing installment plans at a terminal |
US6336104B1 (en) * | 1997-03-21 | 2002-01-01 | Walker Digital, Llc | Method and apparatus for providing and processing installment plans at a terminal |
US6684384B1 (en) * | 1997-03-28 | 2004-01-27 | International Business Machines Corporation | Extensible object oriented framework for general ledger |
US6010404A (en) * | 1997-04-03 | 2000-01-04 | Walker Asset Management Limited Partnership | Method and apparatus for using a player input code to affect a gambling outcome |
US6014439A (en) * | 1997-04-08 | 2000-01-11 | Walker Asset Management Limited Partnership | Method and apparatus for entertaining callers in a queue |
US6243688B1 (en) * | 1997-04-14 | 2001-06-05 | Dyan T. Kalina | Internet-based credit interchange system of converting purchase credit awards through credit exchange system for purchase of investment vehicle |
US6014636A (en) * | 1997-05-06 | 2000-01-11 | Lucent Technologies Inc. | Point of sale method and system |
US6408389B2 (en) * | 1997-05-28 | 2002-06-18 | Symantec Corporation | System for supporting secured log-in of multiple users into a plurality of computers using combined presentation of memorized password and transportable passport record |
US5903881A (en) * | 1997-06-05 | 1999-05-11 | Intuit, Inc. | Personal online banking with integrated online statement and checkbook user interface |
US6061665A (en) * | 1997-06-06 | 2000-05-09 | Verifone, Inc. | System, method and article of manufacture for dynamic negotiation of a network payment framework |
US6073105A (en) * | 1997-06-13 | 2000-06-06 | Tele-Publishing, Inc. | Interactive personals online network method and apparatus |
US6226679B1 (en) * | 1997-06-30 | 2001-05-01 | Sun Microsystems, Inc. | Common management information protocol (CMIP) agent registration methods systems and computer program products |
US6065675A (en) * | 1997-06-30 | 2000-05-23 | Cardis Enterprise International N.V. | Processing system and method for a heterogeneous electronic cash environment |
US6016476A (en) * | 1997-08-11 | 2000-01-18 | International Business Machines Corporation | Portable information and transaction processing system and method utilizing biometric authorization and digital certificate security |
US5910988A (en) * | 1997-08-27 | 1999-06-08 | Csp Holdings, Inc. | Remote image capture with centralized processing and storage |
US6018718A (en) * | 1997-08-28 | 2000-01-25 | Walker Asset Management Limited Partnership | Method and system for processing customized reward offers |
US5914472A (en) * | 1997-09-23 | 1999-06-22 | At&T Corp | Credit card spending authorization control system |
US5873096A (en) * | 1997-10-08 | 1999-02-16 | Siebel Systems, Inc. | Method of maintaining a network of partially replicated database system |
US6026398A (en) * | 1997-10-16 | 2000-02-15 | Imarket, Incorporated | System and methods for searching and matching databases |
US6014639A (en) * | 1997-11-05 | 2000-01-11 | International Business Machines Corporation | Electronic catalog system for exploring a multitude of hierarchies, using attribute relevance and forwarding-checking |
US6018714A (en) * | 1997-11-08 | 2000-01-25 | Ip Value, Llc | Method of protecting against a change in value of intellectual property, and product providing such protection |
US6070244A (en) * | 1997-11-10 | 2000-05-30 | The Chase Manhattan Bank | Computer network security management system |
US6070153A (en) * | 1997-11-21 | 2000-05-30 | Simpson; Mark S. | System and method for automatically investing a portion of a credit card interest charged amount in an investment account |
US6014635A (en) * | 1997-12-08 | 2000-01-11 | Shc Direct, Inc. | System and method for providing a discount credit transaction network |
US6754833B1 (en) * | 1997-12-09 | 2004-06-22 | Openwave Systems Inc. | Method for generating and distributing telecom and internet revenue |
US6065120A (en) * | 1997-12-09 | 2000-05-16 | Phone.Com, Inc. | Method and system for self-provisioning a rendezvous to ensure secure access to information in a database from multiple devices |
US5918217A (en) * | 1997-12-10 | 1999-06-29 | Financial Engines, Inc. | User interface for a financial advisory system |
US6081810A (en) * | 1998-02-03 | 2000-06-27 | Electronic Data Systems Corporation | Report database system |
US6253328B1 (en) * | 1998-02-12 | 2001-06-26 | A. James Smith, Jr. | Method and apparatus for securing passwords and personal identification numbers |
US6081790A (en) * | 1998-03-20 | 2000-06-27 | Citibank, N.A. | System and method for secure presentment and payment over open networks |
US6182220B1 (en) * | 1998-03-30 | 2001-01-30 | International Business Machines Corporation | System and method for building and exchanging encrypted passwords between a client and server |
US6385652B1 (en) * | 1998-04-16 | 2002-05-07 | Citibank, N.A. | Customer access solutions architecture |
US6178511B1 (en) * | 1998-04-30 | 2001-01-23 | International Business Machines Corporation | Coordinating user target logons in a single sign-on (SSO) environment |
US6243816B1 (en) * | 1998-04-30 | 2001-06-05 | International Business Machines Corporation | Single sign-on (SSO) mechanism personal key manager |
US6385594B1 (en) * | 1998-05-08 | 2002-05-07 | Lendingtree, Inc. | Method and computer network for co-ordinating a loan over the internet |
US6505176B2 (en) * | 1998-06-12 | 2003-01-07 | First American Credit Management Solutions, Inc. | Workflow management system for an automated credit application system |
US6073113A (en) * | 1998-06-29 | 2000-06-06 | Sun Microsystems, Inc. | Compatibility checking between instruments, operations and protocols in electronic commerce |
US6182142B1 (en) * | 1998-07-10 | 2001-01-30 | Encommerce, Inc. | Distributed access management of information resources |
US6067531A (en) * | 1998-07-21 | 2000-05-23 | Mci Communications Corporation | Automated contract negotiator/generation system and method |
US6580814B1 (en) * | 1998-07-31 | 2003-06-17 | International Business Machines Corporation | System and method for compressing biometric models |
US6343279B1 (en) * | 1998-08-26 | 2002-01-29 | American Management Systems, Inc. | System integrating credit card transactions into a financial management system |
US6170011B1 (en) * | 1998-09-11 | 2001-01-02 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for determining and initiating interaction directionality within a multimedia communication center |
US6032134A (en) * | 1998-11-18 | 2000-02-29 | Weissman; Steven I. | Credit card billing system for identifying expenditures on a credit card account |
US6253327B1 (en) * | 1998-12-02 | 2001-06-26 | Cisco Technology, Inc. | Single step network logon based on point to point protocol |
US6507912B1 (en) * | 1999-01-27 | 2003-01-14 | International Business Machines Corporation | Protection of biometric data via key-dependent sampling |
US6349242B2 (en) * | 1999-02-05 | 2002-02-19 | First Data Corporation | Method for selectively printing messages and adding inserts to merchant statements |
US6510523B1 (en) * | 1999-02-22 | 2003-01-21 | Sun Microsystems Inc. | Method and system for providing limited access privileges with an untrusted terminal |
US6081900A (en) * | 1999-03-16 | 2000-06-27 | Novell, Inc. | Secure intranet access |
US6751654B2 (en) * | 1999-03-31 | 2004-06-15 | International Business Machines Corporation | Simulating web cookies for non-cookie capable browsers |
US6907566B1 (en) * | 1999-04-02 | 2005-06-14 | Overture Services, Inc. | Method and system for optimum placement of advertisements on a webpage |
US6349336B1 (en) * | 1999-04-26 | 2002-02-19 | Hewlett-Packard Company | Agent/proxy connection control across a firewall |
US6227447B1 (en) * | 1999-05-10 | 2001-05-08 | First Usa Bank, Na | Cardless payment system |
US6385591B1 (en) * | 1999-05-11 | 2002-05-07 | Jeffrey W. Mankoff | Method and system for electronic organization of coupons |
US6226752B1 (en) * | 1999-05-11 | 2001-05-01 | Sun Microsystems, Inc. | Method and apparatus for authenticating users |
US7058817B1 (en) * | 1999-07-02 | 2006-06-06 | The Chase Manhattan Bank | System and method for single sign on process for websites with multiple applications and services |
US6584505B1 (en) * | 1999-07-08 | 2003-06-24 | Microsoft Corporation | Authenticating access to a network server without communicating login information through the network server |
US6584508B1 (en) * | 1999-07-13 | 2003-06-24 | Networks Associates Technology, Inc. | Advanced data guard having independently wrapped components |
US6401125B1 (en) * | 1999-08-05 | 2002-06-04 | Nextpage, Inc. | System and method for maintaining state information between a web proxy server and its clients |
US6574348B1 (en) * | 1999-09-07 | 2003-06-03 | Microsoft Corporation | Technique for watermarking an image and a resulting watermarked image |
US20020023108A1 (en) * | 1999-09-09 | 2002-02-21 | Neil Daswani | Automatic web form interaction proxy |
US6345261B1 (en) * | 1999-09-21 | 2002-02-05 | Stockback Holdings, Inc. | Customer loyalty investment program |
US7319986B2 (en) * | 1999-09-28 | 2008-01-15 | Bank Of America Corporation | Dynamic payment cards and related management systems and associated methods |
US6401211B1 (en) * | 1999-10-19 | 2002-06-04 | Microsoft Corporation | System and method of user logon in combination with user authentication for network access |
US7321864B1 (en) * | 1999-11-04 | 2008-01-22 | Jpmorgan Chase Bank, N.A. | System and method for providing funding approval associated with a project based on a document collection |
US6411933B1 (en) * | 1999-11-22 | 2002-06-25 | International Business Machines Corporation | Methods and apparatus for correlating biometric attributes and biometric attribute production features |
US20020077964A1 (en) * | 1999-12-15 | 2002-06-20 | Brody Robert M. | Systems and methods for providing consumers anonymous pre-approved offers from a consumer-selected group of merchants |
US20020002479A1 (en) * | 1999-12-20 | 2002-01-03 | Gal Almog | Career management system |
US6735695B1 (en) * | 1999-12-20 | 2004-05-11 | International Business Machines Corporation | Methods and apparatus for restricting access of a user using random partial biometrics |
US20020010599A1 (en) * | 2000-01-12 | 2002-01-24 | Levison Michael D. | Method for targeting insurance policy incentive rewards |
US20020010668A1 (en) * | 2000-01-27 | 2002-01-24 | Travis Roger M. | Online merchandising and marketing system |
US6581040B1 (en) * | 2000-02-18 | 2003-06-17 | Daniel B. Wright | Project specific communications system and method |
US20030001888A1 (en) * | 2000-03-01 | 2003-01-02 | Power Mark P J | Data transfer method and apparatus |
US20050120180A1 (en) * | 2000-03-30 | 2005-06-02 | Stephan Schornbach | Cache time determination |
US20030034388A1 (en) * | 2000-05-15 | 2003-02-20 | Larry Routhenstein | Method for generating customer secure card numbers subject to use restrictions by an electronic card |
US6755341B1 (en) * | 2000-05-15 | 2004-06-29 | Jacob Y. Wong | Method for storing data in payment card transaction |
US6185242B1 (en) * | 2000-05-24 | 2001-02-06 | South Carolina Systems, Inc. | Integral side wall and tap hole cover for an eccentric bottom tap (EBT) electric furnace |
US20020059141A1 (en) * | 2000-06-07 | 2002-05-16 | The Chase Manhattan Bank | System and method for executing deposit transactions over the internet |
US7051199B1 (en) * | 2000-06-19 | 2006-05-23 | Xerox Corporation | System, method and article of manufacture for providing cryptographic services utilizing a network |
US20020077978A1 (en) * | 2000-06-22 | 2002-06-20 | The Chase Manhattan Bank | Method and system for processing internet payments |
US6992786B1 (en) * | 2000-06-27 | 2006-01-31 | Printon Ab | Method and system for online creation and ordering of customized material for printing |
US20020007313A1 (en) * | 2000-07-12 | 2002-01-17 | Khanh Mai | Credit system |
US20020007460A1 (en) * | 2000-07-14 | 2002-01-17 | Nec Corporation | Single sign-on system and single sign-on method for a web site and recording medium |
US20020018585A1 (en) * | 2000-07-19 | 2002-02-14 | Kim Young Wan | System and method for cardless secure credit transaction processing |
US20020019938A1 (en) * | 2000-08-04 | 2002-02-14 | Aarons Michael Thomas | Method and apparatus for secure identification for networked environments |
US6847991B1 (en) * | 2000-09-06 | 2005-01-25 | Cisco Technology, Inc. | Data communication among processes of a network component |
US6892231B2 (en) * | 2000-11-02 | 2005-05-10 | Microsoft Corporation | Method and apparatus for verifying the contents of a global configuration file |
US7213064B2 (en) * | 2000-11-18 | 2007-05-01 | In2M Corporation | Methods and systems for job-based accounting |
US7051330B1 (en) * | 2000-11-21 | 2006-05-23 | Microsoft Corporation | Generic application server and method of operation therefor |
US6675261B2 (en) * | 2000-12-22 | 2004-01-06 | Oblix, Inc. | Request based caching of data store data |
US6738779B1 (en) * | 2001-02-21 | 2004-05-18 | Telecom Italia S.P.A. | Apparatus for and method of multiple parallel string searching |
US20040117409A1 (en) * | 2001-03-03 | 2004-06-17 | Scahill Francis J | Application synchronisation |
US6983421B1 (en) * | 2001-06-22 | 2006-01-03 | I2 Technologies Us, Inc. | Using connectors to automatically update graphical user interface elements at a client system according to an updated state of a configuration |
US7647275B2 (en) * | 2001-07-05 | 2010-01-12 | Cummins-Allison Corp. | Automated payment system and method |
US20030018915A1 (en) * | 2001-07-19 | 2003-01-23 | Louis Stoll | Method and system for user authentication and authorization of services |
US20030023880A1 (en) * | 2001-07-27 | 2003-01-30 | Edwards Nigel John | Multi-domain authorization and authentication |
US6847957B1 (en) * | 2001-08-01 | 2005-01-25 | Oracle International Corporation | Dynamically extensible rule-based expert-system shell for database-computing environments |
US20030084345A1 (en) * | 2001-09-14 | 2003-05-01 | Anders Bjornestad | Managed access to information over data networks |
US20030084647A1 (en) * | 2001-11-08 | 2003-05-08 | First Data Corporation | Real-time intelligent packet-collation systems and methods |
US20030088552A1 (en) * | 2001-11-08 | 2003-05-08 | First Data Corporation | Systems and methods of providing inserts into envelopes |
US20030105981A1 (en) * | 2001-12-04 | 2003-06-05 | Miller Lawrence R. | System and method for single session sign-on |
US20030110399A1 (en) * | 2001-12-10 | 2003-06-12 | Electronic Data Systems Corporation | Network user authentication system and method |
US20030115160A1 (en) * | 2001-12-19 | 2003-06-19 | First Data Corporation | Weight measuring systems and methods for weighing items |
US20030119642A1 (en) * | 2001-12-21 | 2003-06-26 | First Data Corporation | Sheet folding systems and methods |
Non-Patent Citations (1)
Title |
---|
Brown, Keith T., The Builder's RevolutionBuildsoft.com, January 1998 * |
Cited By (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9336542B2 (en) | 2004-06-29 | 2016-05-10 | Textura Corporation | Construction payment management system and method with automatic notification workflow features |
US8244606B2 (en) | 2004-06-29 | 2012-08-14 | Textura Corporation | Construction payment management system and method with lien waiver exchange features |
US20110125636A1 (en) * | 2004-06-29 | 2011-05-26 | Allin Patrick J | Construction payment management system and method with lien waiver exchange features |
US10621566B2 (en) | 2004-06-29 | 2020-04-14 | Textura Corporation | Construction payment management system and method with automatic notification workflow features |
US7877302B2 (en) * | 2004-06-29 | 2011-01-25 | Textura Corporation | Construction payment management system and method with automated electronic document generation features |
US20120284178A1 (en) * | 2004-06-29 | 2012-11-08 | Allin Patrick J | Construction payment management system and method with lien waiver exchange features |
US20080046359A1 (en) * | 2004-06-29 | 2008-02-21 | Textura, Llc. | Construction payment management system and method with one-time registration features |
US9727871B2 (en) * | 2004-06-29 | 2017-08-08 | Textura Corporation | Construction payment management system and method with lien waiver exchange features |
US20080147468A1 (en) * | 2004-06-29 | 2008-06-19 | Textura, Llc. | Construction payment management system and method with automated electronic document generation features |
US20050289051A1 (en) * | 2004-06-29 | 2005-12-29 | Allin Patrick J | Construction payment management system and method |
US7725384B2 (en) | 2004-06-29 | 2010-05-25 | Textura Corporation | Construction payment management system and method with one-time registration features |
US20080208602A1 (en) * | 2007-01-09 | 2008-08-28 | Westernoff W Gary | Method and apparatus for an on-line building registry and organizer |
US8296199B2 (en) * | 2007-04-05 | 2012-10-23 | Textura Corporation | Construction payment management system and method with sub-tier document exchange and approval features |
US9721280B2 (en) | 2007-04-05 | 2017-08-01 | Textura Corporation | Construction payment management system and method with sub-tier document exchange and approval features |
US20090171724A1 (en) * | 2007-04-05 | 2009-07-02 | Allin Patrick J | Construction payment management system and method with sub-tier document exchange and approval features |
US20090030794A1 (en) * | 2007-07-23 | 2009-01-29 | One On One Ads, Inc. | Online marketing tool using videos to promote printable coupons |
US20090222820A1 (en) * | 2008-02-29 | 2009-09-03 | Canon Kabushiki Kaisha | Information processing apparatus, information processing method, and information processing program |
US20090319429A1 (en) * | 2008-06-23 | 2009-12-24 | Bank Of America Corp. | Systems and methods for cash positioning and reporting |
US9208522B2 (en) | 2008-06-23 | 2015-12-08 | Bank Of America Corporation | Systems and methods for cash positioning and reporting |
US20160027012A1 (en) * | 2008-07-29 | 2016-01-28 | Barbara Elizabeth Patterson | Transaction processing using a global unique identifier |
US9530131B2 (en) * | 2008-07-29 | 2016-12-27 | Visa U.S.A. Inc. | Transaction processing using a global unique identifier |
US20140081862A1 (en) * | 2008-07-29 | 2014-03-20 | Barbara Elizabeth Patterson | Transaction processing using a global unique identifier |
US9183555B2 (en) * | 2008-07-29 | 2015-11-10 | Visa U.S.A. Inc. | Transaction processing using a global unique identifier |
US20100063910A1 (en) * | 2008-09-05 | 2010-03-11 | Oracle International Corporation | Providing a unified view of contract revenue and invoice details |
US8666854B2 (en) * | 2008-09-05 | 2014-03-04 | Oracle International Corporation | Providing a unified view of contract revenue and invoice details |
US20100070881A1 (en) * | 2008-09-12 | 2010-03-18 | At&T Intellectual Property I, L.P. | Project facilitation and collaboration application |
US20100198652A1 (en) * | 2009-01-30 | 2010-08-05 | Exact Logix Inc | System for the Management of Construction Projects |
WO2011079306A3 (en) * | 2009-12-24 | 2011-10-20 | Clearspire Service Company, Llc | A system and method for total resource management |
WO2011079306A2 (en) * | 2009-12-24 | 2011-06-30 | Clearspire Service Company, Llc | A system and method for total resource management |
US20110166904A1 (en) * | 2009-12-24 | 2011-07-07 | Arrowood Bryce | System and method for total resource management |
US20120116936A1 (en) * | 2010-11-08 | 2012-05-10 | Bank Of America Corporation | Integrated facility managment system |
US20120116932A1 (en) * | 2010-11-08 | 2012-05-10 | Bank Of America Corporation | Evaluating requests using historical benchmarking |
US9471941B2 (en) * | 2011-03-10 | 2016-10-18 | Ebay Inc. | Managing delivery of application server content |
US20140236783A1 (en) * | 2011-03-10 | 2014-08-21 | Ebay Inc. | Managing delivery of application server content |
US10089587B1 (en) | 2011-06-14 | 2018-10-02 | Amazon Technologies, Inc. | Budget planner for softlines |
US9189816B1 (en) | 2011-06-14 | 2015-11-17 | Amazon Technologies, Inc. | Budget planner for softlines |
WO2013049803A1 (en) * | 2011-09-30 | 2013-04-04 | Ecates, Inc. | Worksite safety, planning and environmental documentation and mapping system and method |
US20130198102A1 (en) * | 2012-01-30 | 2013-08-01 | Bank Of America | Method and apparatus for approving a transaction |
US10531069B2 (en) | 2012-11-08 | 2020-01-07 | Ultrahaptics IP Two Limited | Three-dimensional image sensors |
US10013715B2 (en) | 2014-07-21 | 2018-07-03 | Bank Of America Corporation | Temporary waiver tool |
CN107944665A (en) * | 2017-11-01 | 2018-04-20 | 北京新机场建设指挥部 | A kind of Engineering Project Information Management System and method |
US11086963B2 (en) | 2018-12-05 | 2021-08-10 | Ebay Inc. | Adaptive data platforms |
US11921811B2 (en) | 2018-12-05 | 2024-03-05 | Ebay Inc. | Adaptive data platforms |
WO2021142434A1 (en) * | 2020-01-10 | 2021-07-15 | Procore Technologies, Inc. | Computer system and method for tracking the impact of a change event |
US11416793B2 (en) | 2020-01-10 | 2022-08-16 | Procore Technologies, Inc. | Computer system and method for tracking the impact of a change event |
Also Published As
Publication number | Publication date |
---|---|
US7321864B1 (en) | 2008-01-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7685013B2 (en) | System and method for automatic financial project management | |
US7321864B1 (en) | System and method for providing funding approval associated with a project based on a document collection | |
US10621566B2 (en) | Construction payment management system and method with automatic notification workflow features | |
US7747457B2 (en) | Computer system and method for facilitating and managing the project bid and requisition process | |
US7925568B2 (en) | Computer system and method for producing analytical data related to the project bid and requisition process | |
US9721280B2 (en) | Construction payment management system and method with sub-tier document exchange and approval features | |
US20060190391A1 (en) | Project work change in plan/scope administrative and business information synergy system and method | |
US20130054485A1 (en) | Construction payment management system and method with document tracking features | |
US20010011222A1 (en) | Integrated procurement management system using public computer network | |
AU2016200117B2 (en) | Construction Payment Management System and Method with Document Tracking Features | |
AU2013201445A1 (en) | Computer system and method for facilitating and managing the project bid and requisition process | |
AU2014200162B2 (en) | Construction payment management system and method with document tracking features | |
AU2012202421A1 (en) | Project Work Change in Plan/Scope Administrative and Business Information Synergy System and Method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GENDLER, JOSEPH;REEL/FRAME:026076/0657 Effective date: 20001102 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |