US20080133307A1 - Administering a contract over a data network - Google Patents

Administering a contract over a data network Download PDF

Info

Publication number
US20080133307A1
US20080133307A1 US11/927,961 US92796107A US2008133307A1 US 20080133307 A1 US20080133307 A1 US 20080133307A1 US 92796107 A US92796107 A US 92796107A US 2008133307 A1 US2008133307 A1 US 2008133307A1
Authority
US
United States
Prior art keywords
general contractor
change order
order request
subcontractor
line item
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/927,961
Inventor
Sherwood Creedle
Michael W. Petersen
Tom Obermeyer
Eric Kukanic
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
HART BUSINESS SOLUTIONS LLC
Original Assignee
HART BUSINESS SOLUTIONS LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by HART BUSINESS SOLUTIONS LLC filed Critical HART BUSINESS SOLUTIONS LLC
Priority to US11/927,961 priority Critical patent/US20080133307A1/en
Publication of US20080133307A1 publication Critical patent/US20080133307A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • G06Q10/0631Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311Scheduling, planning or task assignment for a person or group
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • G06Q10/0631Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311Scheduling, planning or task assignment for a person or group
    • G06Q10/063118Staff planning in a project environment
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • G06Q10/0631Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06315Needs-based resource requirements planning or analysis

Definitions

  • the present invention relates to the field of contract administration. More particularly, the present invention relates to efficiently administering a construction contract using the Internet or other commonly accessible data network.
  • the traditional roles involved in procurement and construction of building and other structures include the owner, the architect, the general contractor and the subcontractor.
  • the architect creates the design of the building or structure through a separate contract with the owner.
  • the design and specification of the project are necessarily quite detailed to enable competing entities to accurately prepare estimates for performing the work and to assure the integrity of the finished structure with respect to the conceptualization.
  • the architect will also normally act as a liaison between the owner and the general contractor, assuring that the project is proceeding and payments are made according to the contract.
  • the architect is also responsible for approving any change orders that are submitted for review by the general contractor over the course of the project.
  • the general contractor is typically selected by the owner and/or architect through a competitive bidding process based on the detailed design of the project.
  • Each prospective general contractor elicits bids or proposals from subcontractors specializing in areas of contract performance, such as site preparation, plumbing, electrical, masonry, roofing and the like.
  • the general contractor prepares its bid or proposal generally using the subcontractors' estimates, together with its administrative overhead and a percentage markup.
  • the proposal includes an itemized list or schedule of tasks to be accomplished in furtherance of the project, known as line items.
  • the subcontractors likewise prepare their estimates, based on the design documents provided by the architect, by determining materials and labor needed to accomplish the tasks specific to their respective specialties.
  • the subcontractors also factor in their administrative overhead and percentage markup, and provide their proposed schedule in the form of line items.
  • the subcontractor line items do not generally match the general contractor line items, although each of the subcontractor line items must fit within a line item proposed by the general contractor. Possibly, all of a particular subcontractor's proposed labor, materials, overhead and markup may fall within a single line item of the general contractor.
  • the owner and/or architect awards the contract to the most desirable general contractor, based on any number of factors. For example, the award may be based solely on the lowest bid of a qualified general contractor. Alternatively, the award decision may include consideration of a weighted combination of factors, including price, experience, references, time availability, or any other factor deemed significant by the owner and/or architect.
  • the selected general contractor then enters a contract with the owner and/or architect, essentially committing the general contractor to the proposed price and schedule. The general contractor in turn contracts with each of its subcontractors to commit them to their respective prices and schedules.
  • the present invention overcomes the problems associated with the prior art, as described below.
  • the present invention relates to a computer-based method for administering a construction contract in which all parties to the contract (and any associated subcontracts) access a common server over a data network, such as the Internet, and provide contract schedules and requests for payment based on performance of work in accordance of the schedules.
  • An aspect of the present invention provides a method for administering performance of a contract using a server accessible by performing parties through a data network, which may include a public Internet.
  • the method includes receiving performance data at the server from at least one of the performing parties through the data network, the performance data indicating an amount of work performed under the contract by the at least one performing party.
  • a payment amount is determined based on the performance data.
  • the performance data may further include an amount of materials stored.
  • the method may further include initially storing a schedule of values associated with performance of the contract, so that determining the payment amount is further based on comparing the performance data with the schedule of values. Also, the method may further include calculating a contract markup amount based on the performance data and determining the payment further based on the contract markup amount.
  • the payment amount may be sent from the server to another one of the performing parties through the data network. Also, an electronic message may be sent to another one of the performing parties indicating that the payment amount has been determined. A request may be received from the messaged party to receive the payment amount through the data network.
  • Another aspect of the present invention provides a method for administering performance of a contract, including receiving at a server, through a data network, schedules corresponding to subcontractors performing work under the contract. Each schedule identifies at least one task to be performed by the corresponding subcontractor and a cost associated with each task.
  • the method further includes receiving at the server, through the data network, an application for payment corresponding to one of the schedules.
  • the application for payment identifies a portion of the at least one task completed by the corresponding subcontractor. At least one of an amount of work completed and an amount of payment to the subcontractor is determined based on comparing the application for payment and the corresponding schedule.
  • the data network is a public Internet.
  • the method for administering performance of the contract may also include receiving at the server a change order request associated with the at least one task and a change order approval approving the change order request. Determining at least one of the amount of work completed and the amount of payment to the subcontractor is then further based on the approved change order. Also, determining the amount of payment may be further based on subtracting a retainage amount, which is a predetermined percentage applied to the application for payment.
  • Another aspect of the present invention provides a method for administering performance of a project using a web server accessible through a packet switched data network, which may be the Internet.
  • the method includes creating a general contract schedule of values relating to the project, the general contract schedule of values including general contract line items. At least one subcontract schedule of values is received through the packet switched data network.
  • the subcontract schedule of values includes subcontract line items. Associations between the subcontract line items of each subcontract schedule of values and the general contract line items of the general contract schedule of values are received.
  • At least one subcontract application for payment is then received through the packet switched data network, the subcontract application for payment including the subcontract line items.
  • the general contract line items are updated based on information in the associated subcontract line items received in the subcontract application for payment.
  • a general contract application for payment is created based on the updated contract line items.
  • the general contract application for payment automatically determines a total performed work amount and a payment amount due based on the total completed work amount.
  • the method for administering performance of the project may further include submitting the general contract application for payment through the packet switched data network. An approval of the general contract application for payment is received through the packet switched data network.
  • the method may further include initially creating a project profile and assigning roles to participants, including the at least one subcontractor and at least one of an owner or an architect. Assigning roles includes selecting at least one of the participants from a database accessible by the web sewer. Also, assigning roles may include identifying a proxy to represent the at least one of the participants, so that the subcontract schedule of values and the subcontract application for payment are received from the proxy.
  • the method may further include basing the subcontract schedule of values on a predetermined template accessible through the packet switched data network.
  • Creating the general contract application for payment may be further based on a change order corresponding to at least one of the general contract schedule of values and the at least one subcontract schedule of values.
  • creating the general contract application for payment may include entering at least one of a work completed amount and a material presently stored amount. Entering at least one of the work completed amount and the material presently stored amount may be performed automatically based on the subcontract application for payment. Or, entering at least one of the work completed amount and the material presently stored amount may include receiving a dictated amount, different than the at least one of the work completed amount and the material presently stored amount, through the packet switched data network.
  • the received subcontractor application for payment may be modified before updating the general contract line items, based on permission to modify the received subcontractor application received through the packet switched data network.
  • the computer readable medium includes a schedule source code segment, a payment application source code segment and a determining source code segment.
  • the schedule source code segment receives schedules corresponding to subcontractors performing work under the contract, each schedule identifying at least one task to be performed by the corresponding subcontractor and a cost associated with each task.
  • the payment application source code segment receives an application for payment corresponding to one of the schedules, the application for payment identifying a portion of the at least one task completed by the corresponding subcontractor.
  • the determining source code segment determines at least one of an amount of work completed and an amount of payment to the subcontractor based on comparing the application for payment and the corresponding schedule.
  • the data network may be an Internet.
  • the computer readable medium may further include a change order source code segment that receives a change order request associated with the at least one task and that modifies the corresponding schedule in accordance with the change order request, when the change order request is approved. Determining at least one of the amount of work performed and the amount of payment to the subcontractor is then further based on the approved change order.
  • FIG. 1 is a block diagram showing an exemplary network of web clients accessing a common web server, according to an aspect of the present invention
  • FIG. 2 is a flowchart depicting an exemplary process by which the general contractor initiates a project and establishes the schedules of value, according to an aspect of the present invention
  • FIG. 3 is a flowchart depicting an exemplary process by which the general contractor creates a project, according to an aspect of the present invention
  • FIG. 4 is a flowchart depicting an exemplary process by which the general contractor creates a schedule of values, according to an aspect of the present invention
  • FIG. 5 is an exemplary web page for creating a schedule of values, according to an aspect of the present invention.
  • FIG. 6 is an exemplary web page showing a schedule of values, according to an aspect of the present invention.
  • FIG. 7 is an exemplary web page for associating subcontractor schedules of values with a general contractor schedule of values, according to an aspect of the present invention
  • FIG. 8 is a flowchart depicting an exemplary process by which a subcontractor creates an application for payment, according to an aspect of the present invention
  • FIG. 9 is an exemplary web page for submitting a subcontractor application for payment, according to an aspect of the present invention.
  • FIG. 10 is a flowchart depicting an exemplary process by which a contractor creates an application for payment, according to an aspect of the present invention
  • FIG. 11 is an exemplary web page for submitting a subcontractor application for payment, according to an aspect of the present invention.
  • FIG. 12A-12C are exemplary spread sheets indicating corresponding application for payment submissions by a subcontractor and a general contractor, according to an aspect of the present invention.
  • the present invention is directed to efficiently administering a construction contract using a server accessible by the parties to the contract and/or the project participants over a data network, such as the Internet.
  • the contract schedules, as well as the requests for payment based on performance of work in accordance with the schedules, are provided over the Internet, from any client capable of interfacing with the Internet.
  • FIG. 1 depicts an exemplary network of users according to an embodiment of the present invention.
  • the parties to the contract and the project participants are depicted as web clients for the owner/architect 102 , the general contractor 103 , and the subcontractors 104 and 105 .
  • Each of the web clients 102 - 105 communicates with a web server 52 over a packet switched data network, such as a public Internet 50 .
  • the web server 52 has an associated database 53 , which may be internal to the web server 52 or a separate database. It is understood that the invention may be implemented over any common data network accessible by the project participants without departing from the spirit and scope of the present invention.
  • the software is GCPay®, available from Hart Business Solutions.
  • the software may be based on any known programming languages and techniques, including object oriented programming, that enables the web server 52 to reliably interface with the web clients 102 - 105 and to execute the steps of the contract administration program that is the subject of the present invention.
  • the web server 52 may operate running any known operating system and associated software, including, for example, the Linux or Microsoft Windows operating system and the Apache web server software, available from the Apache Software Foundation, or the Jigsaw web server software, available from World Wide Web Consortium (W3C).
  • Each of the depicted web clients 102 - 105 includes a graphical user interface that incorporates a web browser, such as Microsoft Internet Explorer, available from Microsoft Corporation, or Netscape Navigator, available from Netscape Communications Corporation.
  • the web clients 102 - 104 may be any device capable of communicating over the Internet, such as a personal computer (PC), a personal digital assistant (PDA), an Internet compatible wireless telephone, or the like.
  • the web clients 102 - 105 are implemented with IBM Pentium based PCs, running the Linux operating system, available from, for example, Free Software Foundation, Inc., or the Microsoft Windows operating system, and running web browser software, such as Microsoft Internet Explorer, Netscape Navigator or HotJava, available from Sun Microsystems, Inc.
  • the web clients 102 - 105 do not require special software to interact with the web server 52 , other than the conventional web browsers.
  • the general contractor takes the lead in administering a contract.
  • the general contractor must fulfill numerous obligations with respect to the contract, including developing the initial proposal for performing the project, executing a general contract with the owner, retaining and managing subcontractors, overseeing contract performance, managing change order requests, periodically submitting requests for payment and interfacing with the owner and/or architect throughout performance of the contract. Accordingly, it is anticipated that the general contractor would be the entity responsible for initiating and implementing the contract administration program of the present invention. Therefore, the flowcharts discussed below are directed to the process as implemented by the general contractor, although any other party may initiate and implement the process without departing from the spirit and scope of the present invention.
  • FIG. 2 is of flowchart depicting an exemplary process by which the general contractor initiates a project and establishes the schedule of values governing contract performance.
  • the process is implemented pursuant to a computer program executed at the web server 52 .
  • the general contractor registers with the contract administration program at the web server 52 .
  • the general contractor simply accesses the Internet 50 from the general contractor web client 103 and enters the domain name for a web site operated at the web server 52 , such as www.gcpay.com.
  • the general contractor web client 103 and the web server 52 interact through the Internet 50 in a known manner.
  • logic is executed by the web server 52 , which is accessed over the Internet 50 .
  • the information received by the web server 52 is responsive to prompting by the web server 52 , which is programmed in a form reasonably calculated to elicit the desired information.
  • the web server 52 may display a table or form having blank fields that the general contractor fills in based on the identity of each field.
  • the web server 52 may be programmed to request information through discrete fields consecutively displayed in a succession of web pages.
  • the registration process initially involves registering the general contractor company, which includes receiving basic information about the general contractor, including, for example, the company name, telephone number, mailing address, federal tax ID number, and the like. Also, the identity of a company administrator is entered.
  • the company administrator has the capability and necessary permission to perform numerous proprietary functions in the contract administration program. For example, in an embodiment of the invention, only the company administrator is able to register the general contractor with the contract administration program, create and delete projects and assign other company permissions, discussed below. Therefore, in an embodiment of the invention, the company administrator is identified through a user ID number and a password, in addition to the company administrator's name, for example.
  • the security measures provide protection from unauthorized access to proprietary contract performance data, although other user permissions are able to access certain sets of data relating to the contract.
  • the general contractor receives a Welcome web page or home page whenever it accesses the web server 52 .
  • Users in addition to the company administrator may be added or deleted, together with various levels of permission.
  • the user permissions may include a project manager, a company primary contact, a company auditor and a project creator.
  • the project manager is able to add and remove project users and to edit project information and settings.
  • the company primary contact which may coincide with the company administrator, has the ability to receive email notifications when project events occur, including submitting and reviewing schedules of values, applications for payment and change order.
  • the project auditor can view audit trails for the project.
  • the project creator has the ability to build and edit new projects.
  • the various user permissions may all be granted to the same person, each to a different person, or any combination of people, according to the company administrator's discretion.
  • a user from the general contractor creates a new project by initially accessing the web server 52 from the general contractor web client 103 over the Internet 50 . It is assumed that the general contractor has already been awarded the contract based on a previously submitted bid or proposal, based in part on various bids and proposals submitted by the subcontractors. Therefore, certain contractual terms are set, for example, the overall contract price, the general contractor's percentage mark-up, retainage (if any), procedures for change orders, and other typical contract terms and conditions.
  • the user creates a new project by selecting a “create new project” button, for example, on an introductory web page of the contract administration program.
  • the web server 52 accordingly transmits a new project web page to the web client 103 to direct the user through the project creation process.
  • the general contractor In order to create a new project, the general contractor first creates a project profile, as indicated in step s 310 of FIG. 3 . Creating a project profile is necessary so that the relationships among the project participants are delineated to enable the exchange of information through the web server 52 . Creating a project profile entails entering basic information regarding the project. For example, the project profile may include a project name, a project number, a contract start date and the name of the general contractor. The general contractor may have multiple projects which it tracks over the Internet 50 using the contract administration program of the present invention, so the project profile enables the general contractor to distinguish among the various projects.
  • the general contractor user assigns roles to the participants of the project.
  • the project participants are referred to as “companies” for purposes of simplifying the explanation, although it is understood that the project participants may be any legal entity capable of contracting to perform work on the project, including sole proprietors and partnerships.
  • at least one company must be assigned to each role of the project, i.e., an owner, an architect and a subcontractor, in addition to the general contractor.
  • the owner and the architect are the same company because of the overlap in duties between the two. For example, the architect typically reviews and approves schedules of values, applications for payment and change orders, while the owner typically approves release of funds, although these responsibilities may be handled differently.
  • Each of the companies assigned a role must exist in the database 53 of the web server 52 .
  • a general contractor may perform multiple projects for the same owner/architect or using the same subcontractors. If a company is not in the database 53 , e.g., the company is not registered with the GCPay® service, it must be added or a proxy is created to substitute for the missing company.
  • the company administrator of the general contractor or an administrator of the contract administration program may create the proxy.
  • the general contractor company administrator In order to create a proxy, the general contractor company administrator, for example, registers the proxy company in the same manner in which a company would register itself with the contract administration program, but marks the company as a proxy.
  • the database 53 stores the name and other information of the company for which a proxy is created.
  • a web page listing, for example, of the project participants indicates each company that is a proxy.
  • the system automatically adds the general contractor's company administrator as the initial project manager of the proxy project company, which is created in the same manner as any normal registered company being assigned to the project by the project manager or other qualified user of the general contractor.
  • the general contractor company administrator may access a listing of proxy companies at the web server 52 from the web client 103 , for example.
  • the general contractor company administrator is automatically the company administrator for each of the proxy companies, as well.
  • the company administrator may therefore assign permissions and the like with respect to the other proxy users (e.g., also from the general contractor) for the proxy companies.
  • the assigned users perform all of the functions of the subcontractors corresponding to the proxy companies, based on information supplied by the represented company, typically a subcontractor.
  • a proxy company needs to become a real company, e.g., the proxy subcontractor eventually subscribes to the GCPay® program, there is handover to the real company, coordinated by the administrator of the contract administration program.
  • a proxy from the general contractor point of view is that the general contractor must enter the contract performance data on behalf of the proxied company.
  • a subcontractor that subscribes to and participates in the GCPay service enters performance data directly to the web server 52 from the subcontractor web client 104 or 105 .
  • the performance data includes, for example, a schedule of values, applications for payment, change orders and the like, as discussed below.
  • a subcontractor that is not registered with the GCPay service provides contract performance data through conventional means, and the general contractor then enters the data into the contract administration program at the web server 52 on behalf of the subcontractor. It is self-evident that the present invention is most efficient whenever all of the project participants are likewise registered with the GCPay service.
  • the general contractor then assigns user permissions at step s 314 .
  • the user permissions include the following: a company administrator, who is able to edit company information and is the first point of contract for automatic email notifications, discussed below; a company primary contact, who is able to receive email notifications; company auditor, who is able to view an audit trail of changes or edits to company information and user information; a company user manager, who is able to edit other users information within their same company and lock/unlock users from accessing the contract administration program; and a project creator, who is able to create projects.
  • the project user permissions include the following: a project manager, who is able to edit project information, including users, and is the first point of contact for automatic email notifications; a primary contract, who is able to receive email notifications of project events; a project auditor, who is able to view an audit trail of changes or edits to project related information; a schedule of values editor, who is able to create and edit the project schedule of values and change orders, e.g., for the general contractor; an application for payment editor, who is able to create and edit the project applications for payment; a schedule of values reviewer, who is able to review and approve or reject the subcontractors' schedules of values, as well as the general contractor change orders, and an application for payment reviewer, who is able to review and approve or reject the subcontractors' applications for payment.
  • permissions are assigned using a drop-down window of employees of the general contractor.
  • the general contractor selects an employee and then clicks on the project permission categories assigned to the selected employee. The process is repeated for each employee associated with the project. Permission may likewise be removed from employees, for example, by clicking a remove icon next to the user's information.
  • the registered subcontractors or other party to the project is responsible for assigning their respective user permissions.
  • the general contractor finishes creating the project by entering the project settings.
  • the project settings include any administrative items applicable to performance of the contract.
  • the general contractor identifies the company that will review and approve the general contractor's schedule of value, applications for payment and change orders, e.g., the owner and/or the architect.
  • the project settings may be displayed at the general contractor web client 103 as a web page sent from the web server 52 .
  • the project settings enable the general contractor to determine whether to allow the contract administration program to automatically number line items created by the general contractor in an incrementally ascending order, beginning with the number one. When the general contractor prefers using its own line item numbers, it does not select automatic line item numbering.
  • variable retainage enables the general contractor to adjust the amount of retainage the owner is able to withhold over the course of the project, typically reducing the retainage nearer completion of the project.
  • the web server 52 sends a web page to the general contractor web client 103 showing everything input to create the project for verification.
  • the general contractor is allowed to correct any wrong entries by clicking on a “fix” button, for example. Otherwise, the user clicks on a “create project” button, for example, to accept and program into the contract administration program all of the entered data for the new project.
  • the settings are accordingly stored by the database 53 in association with the project.
  • the general contractor is able to access a project web page listing all of the created projects by name or other unique identifier.
  • the general contractor is therefore able to access data on any of its projects by simply clicking on the appropriate icon, retrieving a project detail web page corresponding to the selected project.
  • the general contractor adds subcontractors to an existing project.
  • the general contractor selects a company role management icon, which causes the web server 52 to display the company role management web page at the general contractor web client 103 .
  • the company role management web page displays the existing companies and associated roles, e.g., architect, owner and subcontractor, previously entered by the general contractor at step s 312 of FIG. 3 .
  • the general contractor may select a button for adding a subcontractor, or other company, and is queried to enter the name and other information relating to the new subcontractor.
  • the general contract may simply identify the subcontractor by name or other identification information.
  • the company role management web page includes a drop-down window of all companies and associated roles in the database 53 , including subcontractors from all projects, so that the general contractor is able to add a subcontractor to the present project by selecting the desired subcontractor from the subcontractor drop-down window. For example, the general contractor clicks a box next to the desired subcontractor and then associates the selected subcontractor with the present project.
  • the general contractor saves the information in association with the project.
  • new subcontractors, as well as other companies associated with the project may be added to the project using any variations of the web screens and/or associated commands retrieved from the web server 52 without departing from the spirit and scope of the present invention.
  • the general contractor is able to deactivate project participants.
  • the general contractor web client 103 retrieves the project detail web page from the web server 52 .
  • the general contractor is then able to select the company role management icon, which displays all of the contract participants, including the subcontractors associated with the project.
  • each subcontractor is listed with corresponding “view” and “deactivate” buttons, for example. Clicking on the view button causes the web server 52 to display a web page containing all of the company information relating to the corresponding subcontractor. Clicking on the deactivate button causes the corresponding subcontractor to be removed from the project, although any previous schedule of values, applications for payment and/or change order information is retained in the project history of the database 53 .
  • a subcontractor's schedule of values has been approved, it can no longer be simply removed from the project, and must be deactivated, as described above.
  • the general contract creates the original schedule of values for the project.
  • the general contractor retrieves the project detail web page from the web server 52 at the general contractor web client 103 .
  • the general contractor selects an indication of creating a schedule of values for the project, such as a button labeled “create SOV.”
  • a web page is displayed requesting general information regarding the contact, including percentages of retainage for stored materials and completed work, the maximum retainage limit and the number of lines needed for the general contractor's original schedule of values.
  • the retainage amounts are negotiated and agreed upon by the owner and the general contractor pursuant to the general contract.
  • the percentage of retainage for stored materials and completed work, as well as the maximum retainage limit are entered by the general contractor at step s 412 of FIG. 4 , which is a flow diagram of creating the general contractor's schedule of values.
  • FIG. 5 provides an example of the general contractor's schedule of values web page 500 , according to an embodiment of the present invention.
  • the web page 500 includes basic contract information, such as the name of the project 501 , the start date 502 , the general contactor's name and address 503 and the owner's name and address 504 .
  • the web page also displays the retainage information 505 entered by the general contractor at step s 412 .
  • the stored material retainage is five percent
  • the completion of work retainage is five percent
  • the maximum retainage limit is $20,000.
  • the owner respectively retains five percent of each value submitted for stored materials and completed work, up to a total of $20,000 over the life of the contract. The retainage is released upon completion of the project and acceptance of the work by the architect and/or owner.
  • each line item includes four columns of information: item number 508 , description of work 509 , scheduled value 510 and index 511 .
  • the general contractor enters the item number 508 , which is a free form field that accepts any combination of alpha or numeric characters corresponding to the particular line item.
  • the general contactor may select automatic numbering, in which case each item number 508 is filled automatically with incremental, ascending numbers.
  • the contractor enters the description of work 509 at step s 416 , which is a free form field that accepts any combination of alpha or numeric characters descriptive of the line item. Examples of entries for description of work 509 include “carpeting—labor,” “carpeting—materials,” “drywall—labor,” “drywall—materials,” HVAC—labor,” “HVAC—materials,” “plumbing—labor,” plumbing—materials,” and the like.
  • the general contractor enters the scheduled value 510 corresponding to the description of work.
  • the scheduled value 510 is a numeric field that accepts a dollar amount scheduled for the particular line item.
  • the format is entered, for example, as xxxxxxx.xx, which is interpreted by the program as $x,xxx,xxx.xx.
  • the index number 511 entered at step s 420 , is simply an incremental, numerical index of each line item, provided automatically in an embodiment of the invention.
  • the index number 511 enables quick and efficient indexing of the various line items, without reference to the item numbers 508 .
  • the item numbers 508 are typically coded by specialty, such as 300+ for finishing work, 400+ for HVAC work, 600+ for electrical work and 700+ for plumbing work.
  • the incremental index numbers 511 identify each line item incrementally as it appears in the list of line items with no consideration of the specialty.
  • the general contractor determines whether to edit the schedule of values.
  • the web page 500 depicts a fifth column, remove 512 , which enables the general contractor to remove the corresponding line item by marking the box and clicking the “remove items” button 520 at step s 424 .
  • New line items may also be added to the end of the list by entering the number of line items to be added in box 521 and clicking the “add items” button 522 .
  • the general contractor enters the number of line items to be inserted in box 523 , identifies the index number of the line item after which the new line items are to be inserted via box 524 and clicks the “insert items” button 525 , for example.
  • the general contractor clicks on the cancel button 531 all of the entries are deleted.
  • the contract administration program at the web server 52 calculates the contract sum at step s 430 by adding each entry in the scheduled value 510 column of FIG. 5 and displays the result as the contract sum 610 in web page 600 .
  • the general contractor submits the original schedule of values to the owner over the Internet 50 , for example, by selecting the submit button 612 on the web page 600 .
  • the schedule of values is stored in the database 53 and subsequently accessed by the web server 52 for display at the owner/architect web client 102 .
  • a box for comments 614 may also be provided on the web page 600 , enabling the general contractor to elaborate on any line items requiring further explanation.
  • the web server 52 generates an email, including the comments, and sends the email over the Internet 50 to the owner/architect web client 102 to notify the owner and/or architect that the schedule of values has been submitted and to seek approval of the comments.
  • the email received by the owner and/or architect includes the URL of the web server 52 in a link, so that they may access the web server 52 , and the contract administration program, by simply opening the link in the email. The owner and/or architect may then review the general contractor's schedule of values.
  • the general contractor cannot make changes pending approval. This includes not being able to add or remove subcontractors. Once the schedule of values is approved the general contractor may add or remove subcontractors as discussed above, or seek to change the schedule of values itself by submission of change orders, discussed below.
  • the general contractor may elect to store the completed schedule of values as a template at step s 434 .
  • the schedule of values is similar to that of other projects or anticipated projects, saving the schedule of values as a template saves time and effort in the other projects.
  • the general contractor may enter a template name in a field provided on the redisplayed web page.
  • the template name describes the type of project for which the template is useful, for example, school construction, hospital construction, or the like.
  • the initial general contactor schedule of work web page 500 may include a button labeled “choose template” (not pictured), which enables the general contractor to select a previously stored template, e.g., from a drop-down window, and customize the selected template as necessary for the schedule of values on the new project.
  • the general contractor (as well as the subcontractors) may create a template prior to creating a schedule of values for a particular project.
  • the line items for the template are created and edited in essentially the same manner as described above with respect to creating a schedule of values. Accordingly, the general contractor can build subsequent schedules of values relating to various projects based on the stored template.
  • the process returns to FIG. 2 , with respect to approval of the schedule of values.
  • the owner and/or architect review the schedule of values, submitted via the Internet 50 .
  • the owner and/or architect accesses the web server 52 from the owner/architect web client 102 over the Internet 50 upon receiving notice by email that the schedule of values has been submitted.
  • the owner and/or architect approves the schedule of values
  • the owner and/or architect clicks on an approve button, for example, displayed along with the submitted schedule of values on a web page at the web client 102 .
  • the general contactor receives notice of the approval at step s 216 .
  • the general contractor receives notice of approval by email, generated by the contract administration program, via the Internet 50 .
  • the owner and/or architect reject the schedule of values, a notice to that effect is sent to the general contractor. No applications for payment or change orders may be submitted until an approval for the schedule of values is received.
  • the general contractor receives the schedules of values from the various subcontractors assigned to the project.
  • the general contractor accesses the web server 52 and retrieves the project detail web page.
  • the general contractor clicks on a box labeled “view submitted schedule of values,” for example.
  • the web client 103 displays an overview web page of the submitted schedules of values received from the web server 52 .
  • the web page lists all of the subcontractors that have submitted a schedule of values, along with the status of each schedule of values, e.g., submitted, viewed, approved or rejected.
  • the overview may also include a subcontract sum, which is the total amount of the submitted subcontract based on the schedule of values.
  • “submitted” indicates that the subcontractor has submitted its schedule of values over the Internet 50 to the web server 52 , so it is available for the general contractor's review, but the general contractor has not yet looked at the submission.
  • “Viewed” indicates that the general contractor has accessed the web server 52 , retrieved the submitted schedule of values for viewing at least once, but has not yet decided to approve or reject the submission.
  • “Approved” indicates that the general contractor has reviewed and approved the corresponding subcontractor's submission. In an embodiment, once the general contractor approves a schedule of values, the state cannot be changed, so any corrections would need to be made by a change order.
  • the overview web page of the submitted schedules of values may also identify the subcontracted representative who submitted and the general contractor representative who reviewed each of the schedules of values.
  • the overview web page indicates the representative of the general contractor who entered and submitted the schedule of values for the proxy company on behalf of the subcontractor. Accordingly, a schedule of values may be submitted and approved by the same person.
  • the general contractor's representative is previously assigned a role within the general contractor having authority to approve subcontractor schedules of values, e.g., the SOV reviewer.
  • the web server 52 sends the selected schedule of values, previously submitted by the associated subcontractor (and stored in the database 53 ) to the web client 103 .
  • the subcontractor's schedule of values is prepared and submitted in the same general manner as the general contractor's schedule of values, discussed above with respect to FIGS. 4 and 5 .
  • the subcontractors limit their respective schedules of values to their subcontract specialties.
  • the subcontractors provide significantly more detail for the performance of the work under the subcontracts, requiring the general contractor to associate line items from each subcontractor's schedule of values with the appropriate line items from the general contractor's schedule of values, as discussed below with respect to step s 222 .
  • the general contractor may accept or reject the submitted schedule of values, e.g., by clicking on respective indications, or simply exit the subcontractor schedule of values web page.
  • the subcontractor is notified by email of whatever action the general contractor takes through the Internet 50 .
  • the subcontractor may receive an email at the subcontractor web client 104 stating that “your schedule of values has been approved,” “your schedule of values has been rejected,” or “your schedule of values has been viewed.”
  • the subcontractor is able to access the program to check the status of the approval, which information is available from the web server 52 over the Internet 50 at any time.
  • the general contractor is also able to include comments regarding the subcontractor's schedule of values, which likewise may be included in the status email sent to the web client 104 .
  • the general contractor associates the line items of the subcontractor's schedule of values with the line items of the general contractor's schedule of values. Association with the general contractor's line items is necessary so that the contract administration program is able to automatically determine payment amounts in applications for payment, for example, based on a contract administration algorithm, discussed below. From the general contractor's schedule of values web page, the general contractor views the line items and associated values of the schedule of values submitted to the owner/architect. In an embodiment of the invention, the general contractor then opens an unassociated items window, within the schedule of values web page, which displays all line items from all subcontractor schedules of values that have been submitted for the project that have not yet been associated with general contractor line items.
  • an unassociated items window 710 can be opened, resized and dragged anywhere on the general contractor schedule of values web page 700 , enabling the general contractor to directly compare the various subcontractor line items with the general contractor line items without have to open and close the associated web pages.
  • a subcontractor line item is associated with a general contractor line item by clicking on the subcontractor line item, holding down on the left mouse button and dragging the item to a folder icon 720 , for example, associated with the desired general contractor line item. The association is completed by releasing the mouse button.
  • Alternative embodiments incorporate any method of efficiently associating the two sets of line items without departing from the spirit and scope of the present invention.
  • the associated subcontractor and general contractor line items are stored in the database 53 at step s 224 , for example, by clicking on a “save” button 730 on the web page 700 .
  • a + icon 721 or other positive indicator appears in order to indicate successful association of the subcontractor line item with the general contractor line item.
  • Clicking on the + icon opens an associated line items window 722 corresponding to the general contractor line item.
  • Each of the associated line items in the open associated line items window 722 has a corresponding folder 724 .
  • the general contractor clicks on the folder 724 holds down the left mouse button and drags the folder (and/or line item) back to the window of unassociated line items 710 . Releasing the mouse button completes the removal. The process is repeated until all of the line items of the subcontractor schedules of values, which the general contractor wishes to incorporate into its schedule of values, are associated with the general contractor's line items.
  • Change order requests seek alterations to the respective submitted and approved schedules of values to reflect a change in performance of work on a contract.
  • change order requests seek compensation for additional work performed, materials procured or other unanticipated expenses.
  • change orders may also request a reduction in compensation based on work or materials that is determined to be unnecessary in the course of the project.
  • a subcontractor builds a change order by first retrieving a list of current change orders from the web server 52 , to be displayed at the subcontractor web client 104 or 105 , for example.
  • the new change order may be included in an existing change order that has not yet been approved, or provided as a separate change order. Also, unapproved change orders may be edited or deleted at any time.
  • the subcontractor To create a change order, the subcontractor enters data identifying the item number of the subcontractor's schedule of values, with which the change order is associated. However, the change order may also identify a new item number to the extent it involves work that is not readily associated with the existing subcontractor line items. The subcontractor also enters a description of the additional work, e.g., “additional building pad work,” and the scheduled value of the change order, e.g., $3,000.00. The change orders are numbered incrementally. As in the case of the schedules of values, the contract administration program enables the subcontractor to enter comments about the change order to be submitted along with the change order.
  • the subcontractor clicks on a “submit to owner” button, for example, to send the change order to the web server 52 , which stores the change order in the database 53 and generates an email to the general contractor at the web client 103 informing of the submitted change order.
  • the general contractor incorporates the subcontractor change order into a general contractor change order and submits the general contractor change order to the owner/architect in the same manner described above.
  • the general contractor may incorporate more than one subcontractor change order into a general contractor change order, in which case the general contractor change order includes a list of the associated subcontractor change orders.
  • the general contractor reviews and approves or rejects the subcontractors' change orders in much the same manner it reviews and approves or rejects the subcontractors' schedules of values. For example, the general contractor associates the line items of a subcontractor's change order with the line items of the general contractor's schedule of values.
  • the general contractor submits the change order, sending it to the web server 52 .
  • the web server 52 stores the change order in the database 53 and generates an email to the owner/architect at the web client 102 informing of the submitted change order.
  • the owner/architect reviews the change order and determines whether to accept or reject it. Data indicating the decision is stored in the database 53 and sent by email to the general contractor at the web client 103 . When the general contractor receives notice of approval, the general contractor approves the corresponding subcontractor's change order. Likewise, data indicating the approval is stored in the database 53 and sent by email to the appropriate subcontractor at the web client 104 or 105 .
  • the general contractor and subcontractors are able to begin submitting applications for payment over the Internet 50 to the web server 52 .
  • the original schedule of values is updated throughout the course of project performance based on approved change orders, described above.
  • the general contractor does not submit an application for payment until it has received a number of applications for payment from the subcontractors. Accordingly, the subcontractors' applications for payment are addressed first.
  • a subcontractor cannot submit an application for payment until it has received approval of its schedule of values from the general contractor at step s 810 .
  • the subcontractor automatically receives notice that its schedule of values has been approved by email over the Internet 50 .
  • the subcontractor may access the contract administration program at the web server 52 from the web client 104 or 105 at any time to check the status of the approval.
  • the subcontractor periodically creates applications for payment.
  • the timing of the applications for payment are generally governed by the subcontract and may include, for example, submitting an application weekly, monthly or upon completion of predetermined project milestones.
  • the subcontractor accesses the web server 52 from the web client 104 or 105 and retrieves a web page at step s 812 designed to elicit information regarding the status of the work performed on the project, an example of which is web page 900 of FIG. 9 .
  • the initial application for payment is based on the approved schedule of values. Therefore, before entering any amount to be billed under the subcontract, the application for payment must be edited to include any change orders sought by the subcontractor.
  • the subcontractor determines whether any change orders have been submitted to the general contractor since work began. When change orders have been submitted, and approved, the subcontractor decides which, if any, change orders to include in the present application for payment at step s 816 . Any change orders not included may be submitted in subsequent applications for payment.
  • the line items corresponding to the change orders are automatically updated to reflect the subject matter of the change orders at step s 818 .
  • the subcontractor After the line items are updated, or when no approved change orders exist, the subcontractor begins building the application for payment. Referring to the web page 900 , the subcontractor enters basic information at step s 819 to track the application, including, for example, the application number 901 , the application date 902 and the time period 903 covered by the application. In an embodiment of the invention, these fields are completed automatically by the contract administration program, along with the identification of the subcontractor submitting the application, the name of the project, the contracting parties and the like.
  • the subcontractor enters the work completed and the material stored.
  • the subcontractor uses the fields provided on the web page 900 to accurately track the progress of the subcontract performance.
  • columns A, B and C are the item number 910 , the description of work 911 and the scheduled value 912 , which respectively match the line item numbers, descriptions of work and scheduled values assigned by the subcontractor in its schedule of values (and modified by any approved change orders selected by the subcontractor in step s 816 ).
  • Columns D and E show the work completed 913 by the subcontractor during the period covered by the application for payment.
  • the work completed 913 is divided into work completed-from previous application 915 and from this period 916 . Because the exemplary application for payment is the initial application for payment, the work completed from previous application 915 is all zeros.
  • the work completed-this period 916 shows the amount of work performed in dollars. For example, for line item 1001 (CMU foundations ⁇ materials), $800 has been expended of the $8,000 allocated for that line item, and for line item 1002 (CMU foundations ⁇ labor), $1,000 has been expended of the $10,000 allocated.
  • Column F of the web page 900 shows the materials presently stored 917 .
  • This column contains the dollar amount of materials purchased by the subcontractor and stored, e.g., on site, but not yet incorporated into the project. In the present example, none of the line items include an amount for materials stored.
  • the subcontractor indicates when it finishes entering the work completed and the materials stored, for example, by clicking a “re-calculate fields” button on the web page 900 (not pictured).
  • the contract administration program calculates the remaining entries of the web page 900 .
  • column G shows the total dollar amount associated with each line item, including the total work completed 913 (i.e., the sum of the work completed-from previous application 915 and the work completed-this period 916 ) and the materials presently stored 917 for each line item.
  • Column G also includes the percentage 919 , showing the percentage of completion based on a comparison of the total completed and stored to data 918 with the scheduled value 912 . For line items 1001 and 1002 , percent of the scheduled value is included in this application for payment.
  • Column H, balance to finish 920 shows the remaining amount of the scheduled value to be performed by the subcontractor for each line item.
  • the totals for each line item are automatically determined for each of the columns.
  • One exception is the column for percentage 919 , which does not show the total percentages. Rather, the percentage 919 for the grand total 930 shows the percentage of the total work completed 918 to the total scheduled value 912 .
  • the subcontractor indicates whether the general contractor is allowed to make modifications to the application for payment by clicking on the YES/NO radio buttons 931 .
  • the subcontractor may expedite approval of the application for payment, as well as the subsequent general contractor application for payment, in which the subcontractor's application is included.
  • the subcontractor can also enter explanations of charges, give status reports or the like in the comments window 932 .
  • the subcontractor submits the application for payment to the general contractor at step s 826 , for example, by clicking on the “submit to owner” button 933 .
  • the application for payment is stored at the database 53 by the web server 52 for the general contractor to review.
  • the web server 52 also generates and sends an email to the general contractor at the web client 103 to inform the general contractor that a new application for payment has been submitted.
  • the subcontractor's application for payment cannot be approved unless all of the previous applications for payment have been approved. Also, as stated above with respect to schedules of value, once an application for payment has been approved or rejected, its state cannot be changed, so the general contractor should not approve the subcontractor applications for payment until after it receives approval for the general contractor application for payment in which the subcontractor applications are incorporated. Once an application for payment has been rejected, all subsequent applications for payment from the same subcontractor are also rejected. Similar to the subcontractor schedules of values, the applications for payment submitted to the general contractor have one of four statuses: submitted, viewed, approved and rejected. In an embodiment of the invention, the subcontractor receives an email from the web server 52 whenever the general contractor views, approves and/or rejects each submission.
  • the general contractor's application for payment to the owner/architect is similar to that of the subcontractor's application for payment to the general contractor. Initially, the general contractor receives an approval of its schedule of values from the owner/architect at step s 1010 of FIG. 10 . Typically, the general contractor receives the notice at the web client 103 from the web server 52 as an email.
  • the general contractor determines to submit an application for payment, based on project completion milestones, agreed monthly or weekly submissions, target dates or the like, as indicated in the general contract.
  • the general contractor logs onto the contract administration program at the web server 52 and selects application for payment for the desired project from a project detail web page.
  • the web client 103 retrieves the application for payment form web page from the web server 52 over the Internet 50 .
  • An exemplary application for payment web page is depicted as web page 1100 in FIG. 11 .
  • the general contractor determines whether any subcontractor applications for payment have been newly submitted or have not yet been included in a previous general contractor application for payment. If so, the general contractor retrieves a list of subcontractor applications at step s 1016 and selects the applications that are to be included in the general contractor's application for payment at step s 1018 .
  • the general contractor also has self-performed tasks, included in the schedule of values and an application for payment, that do not involve performance of work by a subcontractor.
  • the general contractor determines whether any change orders have been newly submitted or have not yet been included in a previous application for payment. When there are change orders, the general contractor assures that it has received approval of the change orders from the owner/architect at step s 1022 , discussed above. The general contractor then selects the change orders, if any, to include in the application for payment at step s 1024 . Any change orders not included may be submitted in subsequent applications for payment. Also, in an embodiment of the invention, a subcontractor change order cannot be disassociated from a general contractor change order once the subcontractor application for payment that includes the subcontractor change order has been included and submitted in a general contractor application for payment. The line items corresponding to the change orders are automatically updated to reflect the subject matter of the change orders.
  • the general contractor After the line items are updated, or when no approved change orders exist, the general contractor begins building the application for payment.
  • the subcontractor enters basic information at step s 1028 to track the application, including, for example, the application number 1101 , the application date 1102 and the time period 1103 covered by the application.
  • these fields are completed automatically by the contract administration program, along with the identification of the name of the general contactor, the name of the project, the contracting parties and the like.
  • the general contractor enters the work completed and the material stored.
  • the general contractor uses the fields provided in the web page 1100 to accurately track the progress of contract performance.
  • columns A, B and C are the item number 1110 , the description of work 1111 and the scheduled value 1112 , which respectively match the line item numbers, descriptions of work and scheduled values assigned by the general contractor in its schedule of values (and modified by any approved change orders selected by the general contractor in step s 1024 ).
  • the work completed and the materials stored for each line item, as well as the general contractor's markup, are entered at step s 1030 of FIG. 10 .
  • the amount previously billed is entered, for example, in column D, from previous application 1115 .
  • the general application for payment includes the general contactor's markup.
  • the $11,000 allocated for line item 103 a includes an exemplary ten percent markup on the subcontractor's work.
  • the subcontractor had scheduled $10,000 for this work and the general contractor added a $1,000 markup (ten percent) in its corresponding scheduled value.
  • the work completed 1113 for this period 1116 is based on a $5,000 submission from the subcontractor and a $500 markup by the general contractor.
  • the work completed this period 1116 and the materials presently stored 1117 fields are automatically populated by the contract administration program at steps s 1030 and s 1034 when the general contractor clicks on a button labeled “auto-populate” (not pictured), for example.
  • the program then populates these fields based on information stored in the database 53 , such as the general contractor schedule of values, the subcontractor applications for payment, the associated line items, the approved change orders and the like.
  • the amounts automatically entered are guide values for the general contractor, who may replace any of the automatically populated fields with any figure it desires within the scheduled value amount.
  • the general contractor may want to front-load payments under the contract by billing the owner/architect more than amounts billed by the subcontractor. Whether the general contractor has the right to front-load is typically covered by the terms and conditions of the general contract.
  • the fields are recalculated for each GC line item according to the following algorithm:
  • WC (LI) the general contractor line item (from the schedule of values) for which the work completed payment amount is being determined;
  • E (SC) the work completed in the current period for all subcontractor line items associated with the general contractor line item
  • C (SC) the original scheduled value for all subcontractor line items associated with the general contractor line item
  • the work completed calculation divides the work completed for the present period for all associated subcontractor line items by the work remaining for the same subcontractor line items to determine a ratio, E (SC) /(C (SC) ⁇ D (SC) ).
  • the ratio is multiplied by the remaining work of the general contractor, C (GC) ⁇ D (GC) , to determine the amount that the general contractor should use for work completed this period 1113 .
  • Using the remaining work instead of just the original work accommodates the situation in which the general contractor “front loads” its applications for payment, i.e., initially billing the owner at a higher rate than it is actually paying the subcontractor.
  • the subcontractor figures are based on the general contractor figures, less the general contractor's 10 percent markup.
  • the application for payment of FIG. 11 is an initial application for payment, the work completed as of the previous application for both the subcontractor and the general contractor is “0.” Accordingly, the application for payment amount is determined as follows:
  • the contact administration program can also determine the amount of materials stored 1117 included by the general contractor in its application for payment to the owner/architect for each line item.
  • the field is calculated for each GC line item according to the following algorithm:
  • MPS (LI) the general contractor line item for which the materials presently stored payment amount is being determined
  • C (SC) the original scheduled value for all subcontractor line items associated with the general contractor line item
  • the stored materials calculation divides the materials presently stored for the present period for all associated subcontractors line items by the original scheduled values for the same line items. This ratio is then multiplied by the corresponding original scheduled value of the general contractor to determine the amount that the general contractor should claim for the materials presently stored. There is no “remaining” stored materials, as in the work completed, so factoring a remaining amount is not applicable to determining the materials presently stored.
  • the general contractor may accept the automatically determined amount, or enter a higher or lower amount.
  • the general contractor may wish to “front load” its applications for payment, initially billing the owner at a higher rate than it is actually paying the subcontractor.
  • the contract administration program will apply the algorithms expressed in equations (1) and (2), above, with respect to subsequent applications for payment, resulting in guide values that fully amortize the payment applications to the owner/architect when the subcontractor(s) has been fully paid, even when the general contractor ignores the previous guide values, e.g., when it front-load certain line items.
  • FIGS. 12A-12C shown portions of exemplary spread sheets in which the general contractor elects to front load its applications for payment, requesting a higher payment in the initial application for payment than has been submitted for the corresponding line item by the subcontractor.
  • FIG. 12A shows three line items from a sample first subcontractor application for payment 1210 , indicating in columns E and F, respectively, that the total work completed on the subcontract is $7,500 and the total materials presently stored is $2,500.
  • the sample first general contractor application 1230 shows the guide values in columns E and F calculated by the contract administration program in accordance with equations (1) and (2), respectively. Assuming a 10 percent markup, the guide values are determined to be $8,250 and $2,750 for the work completed this period and the materials presently stored.
  • FIG. 12B shows the same three line items from a sample second subcontractor application for payment 1240 , indicating in columns E and F, respectively, that the additional work completed on the subcontract is $11,000 and the total materials presently stored is still $2,500.
  • the sample second general contractor application 1260 again shows the guide value in columns E calculated by the contract administration program in accordance with equation (1). Note that the materials presently stored in column F is unchanged.)
  • the general contractor front loaded its previous application by submitting $12,000, as opposed to the guide value of $8,250, as the work completed from the previous application. Therefore, the guide value determined according to equation (1) in column E is $10,266.67.
  • the total completed and stored to date entry is $25,016.67, while if the guide value had been followed in the first general contractor application 1230 , the total completed and stored to date entry would have been $23,100.
  • FIG. 12C shows the same three line items from a sample third subcontractor application for payment 1270 , indicating in columns E and F, respectively, that the additional work completed on the subcontract is $11,500, with no materials presently stored, resulting in 100 percent completion of the work scheduled for those three line items, indicated by the percentage in column G.
  • the sample third general contractor application 1290 again shows the guide values in column E calculated by the contract administration program in accordance with equation (1). As indicated in column D, the general contractor followed the guide value from the previous application and submitted the total work from previous applications as $22,266.67. Therefore, the guide value determined according to equation (1) in column E is $10,733.33, which coincides with the remaining amount of work to be performed for the general contractor's line item.
  • FIGS. 12A-12C demonstrate that the contract administration program accurately tracks, and recommends appropriate application for payment values, even in the case where the general contractor front loads its billing.
  • the contract administration program calculates the remaining entries of the web page 1100 based on the entered values.
  • column G shows the dollar total amount associated with each line item.
  • Column G includes the total completed and stored to data 118 , which includes the sum of the work completed-from previous application 1115 , the work completed-this period 1116 , and the materials presently stored 1117 for each line item.
  • Column G also includes the percentage 1119 , showing the percentage of completion based on a comparison of the total completed and stored to data 1118 with the scheduled value 1112 .
  • For line item 103 a and 103 b 50 percent and 100 percent of the scheduled values are respectively included in this application for payment.
  • Column H balance to finish 1120 , shows the remaining amount of the scheduled value to be performed on each project line item.
  • the totals for each of the general contractor's line items are automatically determined for each of the columns.
  • One exception is the column for percentage 1119 , which does not show the total percentages. Rather, the percentage 1119 for the grand total 1130 shows the percentage of the total work completed 1118 to the total scheduled value 1112 .
  • the GC can also enter explanations of charges, give status reports or the like in the Comments window 1132 .
  • the general contractor submits the application for payment to the general contractor at step s 1040 , for example, by clicking on the “submit to owner” button 1133 .
  • the application for payment is stored at the database 53 by the web server 52 for the owner and/or architect to review.
  • the web server 52 also generates and sends an email to the owner/architect at the web client 102 to inform them that a new application for payment has been submitted.
  • the general contractor's application for payment cannot be approved unless all of the previous applications for payment have been approved. Also as stated above, once an application for payment has been approved or rejected, its state cannot be changed. Once an application for payment has been rejected, all subsequent applications for payment from the same subcontractor are also rejected. Similar to the subcontractor applications for payment, the general contractor's applications for payment have one of four statuses: submitted, viewed, approved and rejected.
  • the owner/architect reviews the general contractor's application for payment, as described above with respect to approval of subcontractor applications for payment. For example, the owner/architect is notified of the pending application for payment by email and logs onto the contract administration program at the web sewer 52 to retrieve the application.
  • the owner/architect can approve or reject the application for payment, an indication of which is stored in the database 53 for retrieval by the general contractor, as well as emailed to the general contractor at the web client 103 .
  • the owner/architect may include comments in the approval or rejection email, such as “check will be mailed on Friday.”
  • the owner/architect is able to initiate an electronic finds transfer at the web server 52 , based on bank account data for the owner/architect and the general contractor stored in the database 53 .
  • the general contractor may have the ability to pay subcontractors over the Internet 50 using electronic funds transfer.
  • the present invention provides administration of a contract, and associated subcontracts, from a centralized web server accessible by all contracting (and subcontracting) parties over a packet switched data network, such as the Internet.
  • Schedules of values, applications for payment and change orders corresponding to the general contractor and the subcontractors are built and submitted to the owner/architect and the general contractor, respectively, by way of the web server. Responsive approvals and rejections are likewise communicated through the web servers.
  • emails are generated automatically to notify the contracting and subcontracting parties of the status of various submissions, as well as other contract and project related communications.
  • the methods described herein are intended for operation as software programs running on a computer processor.
  • Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices can likewise be constructed to implement the methods described herein.
  • alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.
  • a tangible storage medium such as: a magnetic medium such as a disk or tape; a magneto-optical or optical medium such as a disk; or a solid state medium such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories.
  • a digital file attachment to email or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. Accordingly, the invention is considered to include a tangible storage medium or distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.

Abstract

A method implements change orders over a data communications network for a construction contract. The method includes entering a new change order request at a user interface connected to the data communications network, the new change order request includes a description of at least one of additional work or additional materials and a corresponding scheduled value. The method further includes determining whether the at least one of addition work or additional materials is associated with an existing line item of a schedule of values previously stored in a database accessible over the communications network via a web server. The existing line item is included in the change order request when the work to be performed is determined to be associated with the existing line item. The new change order request is sent to the web server over the communications network for approval.

Description

  • This application is a division of U.S. patent application Ser. No. 10/673,142, filed Sep. 30, 2003, which application claims priority of U.S. Provisional Patent Application No. 60/415,762, filed on Oct. 4, 2002, the disclosures of which are expressly incorporated by reference herein in their entireties.
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • The present invention relates to the field of contract administration. More particularly, the present invention relates to efficiently administering a construction contract using the Internet or other commonly accessible data network.
  • 2. Background Information
  • Administration of a construction contract is a difficult and time consuming task. Typically, the efficiency with which a contract is administered means the difference between a profitable and unprofitable contract performance, especially from the point of view of the general contractor.
  • The traditional roles involved in procurement and construction of building and other structures include the owner, the architect, the general contractor and the subcontractor. The architect creates the design of the building or structure through a separate contract with the owner. The design and specification of the project are necessarily quite detailed to enable competing entities to accurately prepare estimates for performing the work and to assure the integrity of the finished structure with respect to the conceptualization. The architect will also normally act as a liaison between the owner and the general contractor, assuring that the project is proceeding and payments are made according to the contract. The architect is also responsible for approving any change orders that are submitted for review by the general contractor over the course of the project.
  • The general contractor is typically selected by the owner and/or architect through a competitive bidding process based on the detailed design of the project. Each prospective general contractor elicits bids or proposals from subcontractors specializing in areas of contract performance, such as site preparation, plumbing, electrical, masonry, roofing and the like. The general contractor prepares its bid or proposal generally using the subcontractors' estimates, together with its administrative overhead and a percentage markup. Typically, the proposal includes an itemized list or schedule of tasks to be accomplished in furtherance of the project, known as line items. The subcontractors likewise prepare their estimates, based on the design documents provided by the architect, by determining materials and labor needed to accomplish the tasks specific to their respective specialties. The subcontractors also factor in their administrative overhead and percentage markup, and provide their proposed schedule in the form of line items. The subcontractor line items do not generally match the general contractor line items, although each of the subcontractor line items must fit within a line item proposed by the general contractor. Possibly, all of a particular subcontractor's proposed labor, materials, overhead and markup may fall within a single line item of the general contractor.
  • The owner and/or architect awards the contract to the most desirable general contractor, based on any number of factors. For example, the award may be based solely on the lowest bid of a qualified general contractor. Alternatively, the award decision may include consideration of a weighted combination of factors, including price, experience, references, time availability, or any other factor deemed significant by the owner and/or architect. The selected general contractor then enters a contract with the owner and/or architect, essentially committing the general contractor to the proposed price and schedule. The general contractor in turn contracts with each of its subcontractors to commit them to their respective prices and schedules.
  • As work on the project under the contract proceeds, periodic payments are made to the general contractor and the subcontractors. The progress of the project and the corresponding payments are closely tracked to assure that the owner is not paying for work that has not yet been performed (unless the owner has agreed to allow the general contractor to “frontload” progress payments, as discussed below) and that the general contractor and the subcontractors are being paid for work that has been performed. Tracking the progress is complicated by the fact that dozens of subcontractors, whose activities are coordinated by the general contractor, are performing integrated tasks at various stages of completion. Each request for payment, each change order request, each payment, and their effects on the status of the overall project presents a significant accounting challenge. Further, contracts often provide for retainage, which is a predetermined percentage of payments held back or retained by the owner until the project has been completed to its satisfaction. Therefore, the amount of payments likewise needs to be accurately tracked to protect the agreed upon retainage amount.
  • Computer programs have been developed to assist owners, architects and/or general contractors track progress and status of construction projects. However, these programs rely on conventional submission of payment requests and require manual data entry in order to function properly. There currently is no efficient way in which the various contracting parties can efficiently communicate and exchange data relating to the status of contract performance, submission and approval of payment requests, submission and approval of change orders, and the like.
  • The present invention overcomes the problems associated with the prior art, as described below.
  • SUMMARY OF THE INVENTION
  • The present invention relates to a computer-based method for administering a construction contract in which all parties to the contract (and any associated subcontracts) access a common server over a data network, such as the Internet, and provide contract schedules and requests for payment based on performance of work in accordance of the schedules.
  • In view of the above, the present invention through one or more of its various aspects and/or embodiments is presented to accomplish one or more objectives and advantages, such as those noted below.
  • An aspect of the present invention provides a method for administering performance of a contract using a server accessible by performing parties through a data network, which may include a public Internet. The method includes receiving performance data at the server from at least one of the performing parties through the data network, the performance data indicating an amount of work performed under the contract by the at least one performing party. A payment amount is determined based on the performance data. The performance data may further include an amount of materials stored.
  • The method may further include initially storing a schedule of values associated with performance of the contract, so that determining the payment amount is further based on comparing the performance data with the schedule of values. Also, the method may further include calculating a contract markup amount based on the performance data and determining the payment further based on the contract markup amount. The payment amount may be sent from the server to another one of the performing parties through the data network. Also, an electronic message may be sent to another one of the performing parties indicating that the payment amount has been determined. A request may be received from the messaged party to receive the payment amount through the data network.
  • Another aspect of the present invention provides a method for administering performance of a contract, including receiving at a server, through a data network, schedules corresponding to subcontractors performing work under the contract. Each schedule identifies at least one task to be performed by the corresponding subcontractor and a cost associated with each task. The method further includes receiving at the server, through the data network, an application for payment corresponding to one of the schedules. The application for payment identifies a portion of the at least one task completed by the corresponding subcontractor. At least one of an amount of work completed and an amount of payment to the subcontractor is determined based on comparing the application for payment and the corresponding schedule. In an embodiment, the data network is a public Internet.
  • The method for administering performance of the contract may also include receiving at the server a change order request associated with the at least one task and a change order approval approving the change order request. Determining at least one of the amount of work completed and the amount of payment to the subcontractor is then further based on the approved change order. Also, determining the amount of payment may be further based on subtracting a retainage amount, which is a predetermined percentage applied to the application for payment.
  • Another aspect of the present invention provides a method for administering performance of a project using a web server accessible through a packet switched data network, which may be the Internet. The method includes creating a general contract schedule of values relating to the project, the general contract schedule of values including general contract line items. At least one subcontract schedule of values is received through the packet switched data network. The subcontract schedule of values includes subcontract line items. Associations between the subcontract line items of each subcontract schedule of values and the general contract line items of the general contract schedule of values are received. At least one subcontract application for payment is then received through the packet switched data network, the subcontract application for payment including the subcontract line items. The general contract line items are updated based on information in the associated subcontract line items received in the subcontract application for payment. A general contract application for payment is created based on the updated contract line items. The general contract application for payment automatically determines a total performed work amount and a payment amount due based on the total completed work amount.
  • The method for administering performance of the project may further include submitting the general contract application for payment through the packet switched data network. An approval of the general contract application for payment is received through the packet switched data network. The method may further include initially creating a project profile and assigning roles to participants, including the at least one subcontractor and at least one of an owner or an architect. Assigning roles includes selecting at least one of the participants from a database accessible by the web sewer. Also, assigning roles may include identifying a proxy to represent the at least one of the participants, so that the subcontract schedule of values and the subcontract application for payment are received from the proxy.
  • The method may further include basing the subcontract schedule of values on a predetermined template accessible through the packet switched data network. Creating the general contract application for payment may be further based on a change order corresponding to at least one of the general contract schedule of values and the at least one subcontract schedule of values. Also, creating the general contract application for payment may include entering at least one of a work completed amount and a material presently stored amount. Entering at least one of the work completed amount and the material presently stored amount may be performed automatically based on the subcontract application for payment. Or, entering at least one of the work completed amount and the material presently stored amount may include receiving a dictated amount, different than the at least one of the work completed amount and the material presently stored amount, through the packet switched data network. The received subcontractor application for payment may be modified before updating the general contract line items, based on permission to modify the received subcontractor application received through the packet switched data network.
  • Yet another aspect of the present invention provides a computer readable medium storing a computer program for administering performance of a contract, the computer program being executed by a server accessible through a data network. The computer readable medium includes a schedule source code segment, a payment application source code segment and a determining source code segment. The schedule source code segment receives schedules corresponding to subcontractors performing work under the contract, each schedule identifying at least one task to be performed by the corresponding subcontractor and a cost associated with each task. The payment application source code segment receives an application for payment corresponding to one of the schedules, the application for payment identifying a portion of the at least one task completed by the corresponding subcontractor. The determining source code segment determines at least one of an amount of work completed and an amount of payment to the subcontractor based on comparing the application for payment and the corresponding schedule. The data network may be an Internet.
  • The computer readable medium may further include a change order source code segment that receives a change order request associated with the at least one task and that modifies the corresponding schedule in accordance with the change order request, when the change order request is approved. Determining at least one of the amount of work performed and the amount of payment to the subcontractor is then further based on the approved change order.
  • The various aspects and embodiments of the present invention are described in detail below.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The present invention is further described in the detailed description that follows, by reference to the noted drawings by way of non-limiting examples of embodiments of the present invention, in which like reference numerals represent similar parts throughout several views of the drawings, and in which:
  • FIG. 1 is a block diagram showing an exemplary network of web clients accessing a common web server, according to an aspect of the present invention;
  • FIG. 2 is a flowchart depicting an exemplary process by which the general contractor initiates a project and establishes the schedules of value, according to an aspect of the present invention;
  • FIG. 3 is a flowchart depicting an exemplary process by which the general contractor creates a project, according to an aspect of the present invention;
  • FIG. 4 is a flowchart depicting an exemplary process by which the general contractor creates a schedule of values, according to an aspect of the present invention;
  • FIG. 5 is an exemplary web page for creating a schedule of values, according to an aspect of the present invention;
  • FIG. 6 is an exemplary web page showing a schedule of values, according to an aspect of the present invention;
  • FIG. 7 is an exemplary web page for associating subcontractor schedules of values with a general contractor schedule of values, according to an aspect of the present invention;
  • FIG. 8 is a flowchart depicting an exemplary process by which a subcontractor creates an application for payment, according to an aspect of the present invention;
  • FIG. 9 is an exemplary web page for submitting a subcontractor application for payment, according to an aspect of the present invention;
  • FIG. 10 is a flowchart depicting an exemplary process by which a contractor creates an application for payment, according to an aspect of the present invention;
  • FIG. 11 is an exemplary web page for submitting a subcontractor application for payment, according to an aspect of the present invention; and
  • FIG. 12A-12C are exemplary spread sheets indicating corresponding application for payment submissions by a subcontractor and a general contractor, according to an aspect of the present invention.
  • DETAILED DESCRIPTION OF EMBODIMENTS
  • As stated above, the present invention is directed to efficiently administering a construction contract using a server accessible by the parties to the contract and/or the project participants over a data network, such as the Internet. The contract schedules, as well as the requests for payment based on performance of work in accordance with the schedules, are provided over the Internet, from any client capable of interfacing with the Internet.
  • FIG. 1 depicts an exemplary network of users according to an embodiment of the present invention. The parties to the contract and the project participants are depicted as web clients for the owner/architect 102, the general contractor 103, and the subcontractors 104 and 105. Each of the web clients 102-105 communicates with a web server 52 over a packet switched data network, such as a public Internet 50. The web server 52 has an associated database 53, which may be internal to the web server 52 or a separate database. It is understood that the invention may be implemented over any common data network accessible by the project participants without departing from the spirit and scope of the present invention.
  • Software implementing the contract administration program resides on the web server 52. In an embodiment of the invention, the software is GCPay®, available from Hart Business Solutions. The software may be based on any known programming languages and techniques, including object oriented programming, that enables the web server 52 to reliably interface with the web clients 102-105 and to execute the steps of the contract administration program that is the subject of the present invention. The web server 52 may operate running any known operating system and associated software, including, for example, the Linux or Microsoft Windows operating system and the Apache web server software, available from the Apache Software Foundation, or the Jigsaw web server software, available from World Wide Web Consortium (W3C).
  • Each of the depicted web clients 102-105 includes a graphical user interface that incorporates a web browser, such as Microsoft Internet Explorer, available from Microsoft Corporation, or Netscape Navigator, available from Netscape Communications Corporation. The web clients 102-104 may be any device capable of communicating over the Internet, such as a personal computer (PC), a personal digital assistant (PDA), an Internet compatible wireless telephone, or the like. In an exemplary embodiment, the web clients 102-105 are implemented with IBM Pentium based PCs, running the Linux operating system, available from, for example, Free Software Foundation, Inc., or the Microsoft Windows operating system, and running web browser software, such as Microsoft Internet Explorer, Netscape Navigator or HotJava, available from Sun Microsystems, Inc. The web clients 102-105 do not require special software to interact with the web server 52, other than the conventional web browsers.
  • Typically, the general contractor takes the lead in administering a contract. The general contractor must fulfill numerous obligations with respect to the contract, including developing the initial proposal for performing the project, executing a general contract with the owner, retaining and managing subcontractors, overseeing contract performance, managing change order requests, periodically submitting requests for payment and interfacing with the owner and/or architect throughout performance of the contract. Accordingly, it is anticipated that the general contractor would be the entity responsible for initiating and implementing the contract administration program of the present invention. Therefore, the flowcharts discussed below are directed to the process as implemented by the general contractor, although any other party may initiate and implement the process without departing from the spirit and scope of the present invention.
  • FIG. 2 is of flowchart depicting an exemplary process by which the general contractor initiates a project and establishes the schedule of values governing contract performance. As stated above, the process is implemented pursuant to a computer program executed at the web server 52. At step s208, the general contractor registers with the contract administration program at the web server 52. The general contractor simply accesses the Internet 50 from the general contractor web client 103 and enters the domain name for a web site operated at the web server 52, such as www.gcpay.com. The general contractor web client 103 and the web server 52 interact through the Internet 50 in a known manner. For example, in an embodiment of the invention, logic is executed by the web server 52, which is accessed over the Internet 50.
  • The information received by the web server 52 is responsive to prompting by the web server 52, which is programmed in a form reasonably calculated to elicit the desired information. For example, the web server 52 may display a table or form having blank fields that the general contractor fills in based on the identity of each field. Alternatively, the web server 52 may be programmed to request information through discrete fields consecutively displayed in a succession of web pages.
  • The registration process initially involves registering the general contractor company, which includes receiving basic information about the general contractor, including, for example, the company name, telephone number, mailing address, federal tax ID number, and the like. Also, the identity of a company administrator is entered. The company administrator has the capability and necessary permission to perform numerous proprietary functions in the contract administration program. For example, in an embodiment of the invention, only the company administrator is able to register the general contractor with the contract administration program, create and delete projects and assign other company permissions, discussed below. Therefore, in an embodiment of the invention, the company administrator is identified through a user ID number and a password, in addition to the company administrator's name, for example. The security measures provide protection from unauthorized access to proprietary contract performance data, although other user permissions are able to access certain sets of data relating to the contract.
  • After the initial company registration, the general contractor receives a Welcome web page or home page whenever it accesses the web server 52. Users in addition to the company administrator may be added or deleted, together with various levels of permission. For example, the user permissions may include a project manager, a company primary contact, a company auditor and a project creator. The project manager is able to add and remove project users and to edit project information and settings. The company primary contact, which may coincide with the company administrator, has the ability to receive email notifications when project events occur, including submitting and reviewing schedules of values, applications for payment and change order. The project auditor can view audit trails for the project. The project creator has the ability to build and edit new projects. The various user permissions may all be granted to the same person, each to a different person, or any combination of people, according to the company administrator's discretion.
  • At step s210 of FIG. 2, a user from the general contractor (e.g., the project creator or company administrator, identified above) creates a new project by initially accessing the web server 52 from the general contractor web client 103 over the Internet 50. It is assumed that the general contractor has already been awarded the contract based on a previously submitted bid or proposal, based in part on various bids and proposals submitted by the subcontractors. Therefore, certain contractual terms are set, for example, the overall contract price, the general contractor's percentage mark-up, retainage (if any), procedures for change orders, and other typical contract terms and conditions.
  • The user creates a new project by selecting a “create new project” button, for example, on an introductory web page of the contract administration program. The web server 52 accordingly transmits a new project web page to the web client 103 to direct the user through the project creation process.
  • In order to create a new project, the general contractor first creates a project profile, as indicated in step s310 of FIG. 3. Creating a project profile is necessary so that the relationships among the project participants are delineated to enable the exchange of information through the web server 52. Creating a project profile entails entering basic information regarding the project. For example, the project profile may include a project name, a project number, a contract start date and the name of the general contractor. The general contractor may have multiple projects which it tracks over the Internet 50 using the contract administration program of the present invention, so the project profile enables the general contractor to distinguish among the various projects.
  • At step s312, the general contractor user assigns roles to the participants of the project. The project participants are referred to as “companies” for purposes of simplifying the explanation, although it is understood that the project participants may be any legal entity capable of contracting to perform work on the project, including sole proprietors and partnerships. In an embodiment of the invention, at least one company must be assigned to each role of the project, i.e., an owner, an architect and a subcontractor, in addition to the general contractor. In an embodiment of the invention, the owner and the architect are the same company because of the overlap in duties between the two. For example, the architect typically reviews and approves schedules of values, applications for payment and change orders, while the owner typically approves release of funds, although these responsibilities may be handled differently.
  • Each of the companies assigned a role must exist in the database 53 of the web server 52. In fact, a general contractor may perform multiple projects for the same owner/architect or using the same subcontractors. If a company is not in the database 53, e.g., the company is not registered with the GCPay® service, it must be added or a proxy is created to substitute for the missing company. In alternative embodiments, the company administrator of the general contractor or an administrator of the contract administration program may create the proxy.
  • In order to create a proxy, the general contractor company administrator, for example, registers the proxy company in the same manner in which a company would register itself with the contract administration program, but marks the company as a proxy. The database 53 stores the name and other information of the company for which a proxy is created. A web page listing, for example, of the project participants indicates each company that is a proxy.
  • When the general contractor project manager adds the proxy company to the project, the system automatically adds the general contractor's company administrator as the initial project manager of the proxy project company, which is created in the same manner as any normal registered company being assigned to the project by the project manager or other qualified user of the general contractor. The general contractor company administrator may access a listing of proxy companies at the web server 52 from the web client 103, for example. The general contractor company administrator is automatically the company administrator for each of the proxy companies, as well. The company administrator may therefore assign permissions and the like with respect to the other proxy users (e.g., also from the general contractor) for the proxy companies. The assigned users perform all of the functions of the subcontractors corresponding to the proxy companies, based on information supplied by the represented company, typically a subcontractor. When a proxy company needs to become a real company, e.g., the proxy subcontractor eventually subscribes to the GCPay® program, there is handover to the real company, coordinated by the administrator of the contract administration program.
  • The significance of a proxy from the general contractor point of view is that the general contractor must enter the contract performance data on behalf of the proxied company. For example, a subcontractor that subscribes to and participates in the GCPay service enters performance data directly to the web server 52 from the subcontractor web client 104 or 105. The performance data includes, for example, a schedule of values, applications for payment, change orders and the like, as discussed below. However, a subcontractor that is not registered with the GCPay service provides contract performance data through conventional means, and the general contractor then enters the data into the contract administration program at the web server 52 on behalf of the subcontractor. It is self-evident that the present invention is most efficient whenever all of the project participants are likewise registered with the GCPay service.
  • The general contractor then assigns user permissions at step s314. Included among the user permissions are company user permissions within each participating company and project user permissions with respect to the overall project. In an embodiment of the invention, the company user permissions include the following: a company administrator, who is able to edit company information and is the first point of contract for automatic email notifications, discussed below; a company primary contact, who is able to receive email notifications; company auditor, who is able to view an audit trail of changes or edits to company information and user information; a company user manager, who is able to edit other users information within their same company and lock/unlock users from accessing the contract administration program; and a project creator, who is able to create projects.
  • Only one party to the contract, typically the general contractor, should have a project creator in order to avoid duplicative efforts for one project. Also in an embodiment of the invention, the project user permissions include the following: a project manager, who is able to edit project information, including users, and is the first point of contact for automatic email notifications; a primary contract, who is able to receive email notifications of project events; a project auditor, who is able to view an audit trail of changes or edits to project related information; a schedule of values editor, who is able to create and edit the project schedule of values and change orders, e.g., for the general contractor; an application for payment editor, who is able to create and edit the project applications for payment; a schedule of values reviewer, who is able to review and approve or reject the subcontractors' schedules of values, as well as the general contractor change orders, and an application for payment reviewer, who is able to review and approve or reject the subcontractors' applications for payment.
  • In an embodiment of the invention, permissions are assigned using a drop-down window of employees of the general contractor. The general contractor selects an employee and then clicks on the project permission categories assigned to the selected employee. The process is repeated for each employee associated with the project. Permission may likewise be removed from employees, for example, by clicking a remove icon next to the user's information. The registered subcontractors or other party to the project is responsible for assigning their respective user permissions.
  • At step s316, the general contractor finishes creating the project by entering the project settings. The project settings include any administrative items applicable to performance of the contract. For example, under the project settings, the general contractor identifies the company that will review and approve the general contractor's schedule of value, applications for payment and change orders, e.g., the owner and/or the architect. The project settings may be displayed at the general contractor web client 103 as a web page sent from the web server 52. In an embodiment of the invention, the project settings enable the general contractor to determine whether to allow the contract administration program to automatically number line items created by the general contractor in an incrementally ascending order, beginning with the number one. When the general contractor prefers using its own line item numbers, it does not select automatic line item numbering. Another exemplary setting is specifying whether the project includes a variable retainage or a fixed retainage. Variable retainage enables the general contractor to adjust the amount of retainage the owner is able to withhold over the course of the project, typically reducing the retainage nearer completion of the project.
  • After the settings are entered, the web server 52 sends a web page to the general contractor web client 103 showing everything input to create the project for verification. In an embodiment of the invention, the general contractor is allowed to correct any wrong entries by clicking on a “fix” button, for example. Otherwise, the user clicks on a “create project” button, for example, to accept and program into the contract administration program all of the entered data for the new project. The settings are accordingly stored by the database 53 in association with the project.
  • Once the project is created, the general contractor is able to access a project web page listing all of the created projects by name or other unique identifier. The general contractor is therefore able to access data on any of its projects by simply clicking on the appropriate icon, retrieving a project detail web page corresponding to the selected project.
  • At step s212 of FIG. 2, the general contractor adds subcontractors to an existing project. For example, at the project detail web page, the general contractor selects a company role management icon, which causes the web server 52 to display the company role management web page at the general contractor web client 103. The company role management web page displays the existing companies and associated roles, e.g., architect, owner and subcontractor, previously entered by the general contractor at step s312 of FIG. 3. When needed, the general contractor may select a button for adding a subcontractor, or other company, and is queried to enter the name and other information relating to the new subcontractor.
  • When a new subcontractor is already in the database 53, e.g., the subcontractor has been used on another project and was previously entered into the database 53 when assigning company roles, the general contract may simply identify the subcontractor by name or other identification information. In an embodiment of the invention, the company role management web page includes a drop-down window of all companies and associated roles in the database 53, including subcontractors from all projects, so that the general contractor is able to add a subcontractor to the present project by selecting the desired subcontractor from the subcontractor drop-down window. For example, the general contractor clicks a box next to the desired subcontractor and then associates the selected subcontractor with the present project. Once the new subcontractor is selected, and the subcontractor's company information added to the database 53, if necessary, the general contractor saves the information in association with the project. Of course, new subcontractors, as well as other companies associated with the project, may be added to the project using any variations of the web screens and/or associated commands retrieved from the web server 52 without departing from the spirit and scope of the present invention.
  • Similarly, the general contractor is able to deactivate project participants. For example, the general contractor web client 103 retrieves the project detail web page from the web server 52. The general contractor is then able to select the company role management icon, which displays all of the contract participants, including the subcontractors associated with the project. In an embodiment of the invention, each subcontractor is listed with corresponding “view” and “deactivate” buttons, for example. Clicking on the view button causes the web server 52 to display a web page containing all of the company information relating to the corresponding subcontractor. Clicking on the deactivate button causes the corresponding subcontractor to be removed from the project, although any previous schedule of values, applications for payment and/or change order information is retained in the project history of the database 53. In an embodiment of the invention, once a subcontractor's schedule of values has been approved, it can no longer be simply removed from the project, and must be deactivated, as described above.
  • At step s214, the general contract creates the original schedule of values for the project. In an exemplary embodiment, the general contractor retrieves the project detail web page from the web server 52 at the general contractor web client 103. The general contractor then selects an indication of creating a schedule of values for the project, such as a button labeled “create SOV.” Initially, a web page is displayed requesting general information regarding the contact, including percentages of retainage for stored materials and completed work, the maximum retainage limit and the number of lines needed for the general contractor's original schedule of values. The retainage amounts are negotiated and agreed upon by the owner and the general contractor pursuant to the general contract. The percentage of retainage for stored materials and completed work, as well as the maximum retainage limit are entered by the general contractor at step s412 of FIG. 4, which is a flow diagram of creating the general contractor's schedule of values.
  • The general contractor clicks a “create” button, for example, in response to which the web client 103 displays a general contactor schedule of work web page received from the web sever 52. FIG. 5 provides an example of the general contractor's schedule of values web page 500, according to an embodiment of the present invention. The web page 500 includes basic contract information, such as the name of the project 501, the start date 502, the general contactor's name and address 503 and the owner's name and address 504. The web page also displays the retainage information 505 entered by the general contractor at step s412. In the exemplary embodiment, the stored material retainage is five percent, the completion of work retainage is five percent and the maximum retainage limit is $20,000. In other words, for each application for payment submitted by the general contractor during performance of the project, the owner respectively retains five percent of each value submitted for stored materials and completed work, up to a total of $20,000 over the life of the contract. The retainage is released upon completion of the project and acceptance of the work by the architect and/or owner.
  • Below the contract information are rows of blank fields corresponding to line items, the number of which was previously identified by the general contractor, as described above. In the exemplary embodiment shown in FIG. 5, each line item includes four columns of information: item number 508, description of work 509, scheduled value 510 and index 511. At step s414 of FIG. 4, the general contractor enters the item number 508, which is a free form field that accepts any combination of alpha or numeric characters corresponding to the particular line item. Alternatively, the general contactor may select automatic numbering, in which case each item number 508 is filled automatically with incremental, ascending numbers.
  • The contractor enters the description of work 509 at step s416, which is a free form field that accepts any combination of alpha or numeric characters descriptive of the line item. Examples of entries for description of work 509 include “carpeting—labor,” “carpeting—materials,” “drywall—labor,” “drywall—materials,” HVAC—labor,” “HVAC—materials,” “plumbing—labor,” plumbing—materials,” and the like. At step s418, the general contractor enters the scheduled value 510 corresponding to the description of work. The scheduled value 510 is a numeric field that accepts a dollar amount scheduled for the particular line item. The format is entered, for example, as xxxxxxx.xx, which is interpreted by the program as $x,xxx,xxx.xx.
  • The index number 511, entered at step s420, is simply an incremental, numerical index of each line item, provided automatically in an embodiment of the invention. The index number 511 enables quick and efficient indexing of the various line items, without reference to the item numbers 508. For example, the item numbers 508 are typically coded by specialty, such as 300+ for finishing work, 400+ for HVAC work, 600+ for electrical work and 700+ for plumbing work. The incremental index numbers 511, however, identify each line item incrementally as it appears in the list of line items with no consideration of the specialty.
  • At step s422, the general contractor determines whether to edit the schedule of values. For example, the web page 500 depicts a fifth column, remove 512, which enables the general contractor to remove the corresponding line item by marking the box and clicking the “remove items” button 520 at step s424. New line items may also be added to the end of the list by entering the number of line items to be added in box 521 and clicking the “add items” button 522. To insert line items between existing line items, the general contractor enters the number of line items to be inserted in box 523, identifies the index number of the line item after which the new line items are to be inserted via box 524 and clicks the “insert items” button 525, for example. When the general contractor clicks on the cancel button 531, all of the entries are deleted.
  • After all of the line items for the general contractor's original schedule of values have been entered, the general contactor clicks on the create button 530. The result is a completed schedule of values, an example of which is shown in web page 600 of FIG. 6. The contract administration program at the web server 52 calculates the contract sum at step s430 by adding each entry in the scheduled value 510 column of FIG. 5 and displays the result as the contract sum 610 in web page 600.
  • At step s432, the general contractor submits the original schedule of values to the owner over the Internet 50, for example, by selecting the submit button 612 on the web page 600. For example, the schedule of values is stored in the database 53 and subsequently accessed by the web server 52 for display at the owner/architect web client 102. A box for comments 614 may also be provided on the web page 600, enabling the general contractor to elaborate on any line items requiring further explanation.
  • In an embodiment of the invention, the web server 52 generates an email, including the comments, and sends the email over the Internet 50 to the owner/architect web client 102 to notify the owner and/or architect that the schedule of values has been submitted and to seek approval of the comments. In an embodiment of the invention, the email received by the owner and/or architect includes the URL of the web server 52 in a link, so that they may access the web server 52, and the contract administration program, by simply opening the link in the email. The owner and/or architect may then review the general contractor's schedule of values.
  • Once the schedule of values has been submitted for approval, the general contractor cannot make changes pending approval. This includes not being able to add or remove subcontractors. Once the schedule of values is approved the general contractor may add or remove subcontractors as discussed above, or seek to change the schedule of values itself by submission of change orders, discussed below.
  • In the depicted embodiment of the invention, the general contractor may elect to store the completed schedule of values as a template at step s434. For example, when the schedule of values is similar to that of other projects or anticipated projects, saving the schedule of values as a template saves time and effort in the other projects. At step s436, after submitting the schedule of values to the owner and/or architect, the general contractor may enter a template name in a field provided on the redisplayed web page. The template name describes the type of project for which the template is useful, for example, school construction, hospital construction, or the like. The general contractor then saves the template at step s436 to instruct the web server 52 to save the schedule of values, e.g., in the database 53, as a template for future reference. In this embodiment of the invention, the initial general contactor schedule of work web page 500 may include a button labeled “choose template” (not pictured), which enables the general contractor to select a previously stored template, e.g., from a drop-down window, and customize the selected template as necessary for the schedule of values on the new project.
  • In an embodiment of the invention, the general contractor (as well as the subcontractors) may create a template prior to creating a schedule of values for a particular project. The line items for the template are created and edited in essentially the same manner as described above with respect to creating a schedule of values. Accordingly, the general contractor can build subsequent schedules of values relating to various projects based on the stored template.
  • Regardless of whether the schedule of values is saved as a template, the process returns to FIG. 2, with respect to approval of the schedule of values. The owner and/or architect review the schedule of values, submitted via the Internet 50. In an embodiment of the invention, the owner and/or architect accesses the web server 52 from the owner/architect web client 102 over the Internet 50 upon receiving notice by email that the schedule of values has been submitted. When the owner and/or architect approves the schedule of values, the owner and/or architect clicks on an approve button, for example, displayed along with the submitted schedule of values on a web page at the web client 102. The general contactor receives notice of the approval at step s216. In an embodiment of the invention, the general contractor receives notice of approval by email, generated by the contract administration program, via the Internet 50. When the owner and/or architect reject the schedule of values, a notice to that effect is sent to the general contractor. No applications for payment or change orders may be submitted until an approval for the schedule of values is received.
  • At step s218, the general contractor receives the schedules of values from the various subcontractors assigned to the project. Using the web client 103, the general contractor accesses the web server 52 and retrieves the project detail web page. The general contractor clicks on a box labeled “view submitted schedule of values,” for example. The web client 103 displays an overview web page of the submitted schedules of values received from the web server 52. The web page lists all of the subcontractors that have submitted a schedule of values, along with the status of each schedule of values, e.g., submitted, viewed, approved or rejected. The overview may also include a subcontract sum, which is the total amount of the submitted subcontract based on the schedule of values.
  • With respect to the status, “submitted” indicates that the subcontractor has submitted its schedule of values over the Internet 50 to the web server 52, so it is available for the general contractor's review, but the general contractor has not yet looked at the submission. “Viewed” indicates that the general contractor has accessed the web server 52, retrieved the submitted schedule of values for viewing at least once, but has not yet decided to approve or reject the submission. “Approved” indicates that the general contractor has reviewed and approved the corresponding subcontractor's submission. In an embodiment, once the general contractor approves a schedule of values, the state cannot be changed, so any corrections would need to be made by a change order. Therefore, it is to the general contractor's benefit to associate the line items from the subcontractor's schedule of values with the line items from the general contractor's schedule of values, discussed below with respect to step s222, prior to approving the schedule of values to assure that any inconsistencies are addressed prior to final approval. “Rejected” indicates that the subcontractor's submission is unacceptable. If the general contractor had previously associated any line items from the subcontractor's ultimately rejected schedule of values with the line items from the general contractor's schedule of values, these lines are automatically disassociated upon rejection.
  • The overview web page of the submitted schedules of values may also identify the subcontracted representative who submitted and the general contractor representative who reviewed each of the schedules of values. In an embodiment, when the subcontractor is represented by a proxy company, the overview web page indicates the representative of the general contractor who entered and submitted the schedule of values for the proxy company on behalf of the subcontractor. Accordingly, a schedule of values may be submitted and approved by the same person. As discussed above with respect to step s312 of FIG. 3, the general contractor's representative is previously assigned a role within the general contractor having authority to approve subcontractor schedules of values, e.g., the SOV reviewer.
  • In response to the general contractors request to review a selected schedule of values, the web server 52 sends the selected schedule of values, previously submitted by the associated subcontractor (and stored in the database 53) to the web client 103. In an embodiment of the invention, the subcontractor's schedule of values is prepared and submitted in the same general manner as the general contractor's schedule of values, discussed above with respect to FIGS. 4 and 5. Of course, there are differences in the line items because the subcontractors limit their respective schedules of values to their subcontract specialties. Also, the subcontractors provide significantly more detail for the performance of the work under the subcontracts, requiring the general contractor to associate line items from each subcontractor's schedule of values with the appropriate line items from the general contractor's schedule of values, as discussed below with respect to step s222.
  • Upon review, the general contractor may accept or reject the submitted schedule of values, e.g., by clicking on respective indications, or simply exit the subcontractor schedule of values web page. In an embodiment of the invention, the subcontractor is notified by email of whatever action the general contractor takes through the Internet 50. For example, the subcontractor may receive an email at the subcontractor web client 104 stating that “your schedule of values has been approved,” “your schedule of values has been rejected,” or “your schedule of values has been viewed.” Further, the subcontractor is able to access the program to check the status of the approval, which information is available from the web server 52 over the Internet 50 at any time. The general contractor is also able to include comments regarding the subcontractor's schedule of values, which likewise may be included in the status email sent to the web client 104.
  • At step s222 of FIG. 2, the general contractor associates the line items of the subcontractor's schedule of values with the line items of the general contractor's schedule of values. Association with the general contractor's line items is necessary so that the contract administration program is able to automatically determine payment amounts in applications for payment, for example, based on a contract administration algorithm, discussed below. From the general contractor's schedule of values web page, the general contractor views the line items and associated values of the schedule of values submitted to the owner/architect. In an embodiment of the invention, the general contractor then opens an unassociated items window, within the schedule of values web page, which displays all line items from all subcontractor schedules of values that have been submitted for the project that have not yet been associated with general contractor line items.
  • As shown in FIG. 7, an unassociated items window 710 can be opened, resized and dragged anywhere on the general contractor schedule of values web page 700, enabling the general contractor to directly compare the various subcontractor line items with the general contractor line items without have to open and close the associated web pages. In an embodiment of the invention, a subcontractor line item is associated with a general contractor line item by clicking on the subcontractor line item, holding down on the left mouse button and dragging the item to a folder icon 720, for example, associated with the desired general contractor line item. The association is completed by releasing the mouse button. Alternative embodiments incorporate any method of efficiently associating the two sets of line items without departing from the spirit and scope of the present invention. The associated subcontractor and general contractor line items are stored in the database 53 at step s224, for example, by clicking on a “save” button 730 on the web page 700.
  • In the depicted exemplary embodiment, a + icon 721 or other positive indicator appears in order to indicate successful association of the subcontractor line item with the general contractor line item. Clicking on the + icon opens an associated line items window 722 corresponding to the general contractor line item. Each of the associated line items in the open associated line items window 722 has a corresponding folder 724. To remove an association, the general contractor clicks on the folder 724, holds down the left mouse button and drags the folder (and/or line item) back to the window of unassociated line items 710. Releasing the mouse button completes the removal. The process is repeated until all of the line items of the subcontractor schedules of values, which the general contractor wishes to incorporate into its schedule of values, are associated with the general contractor's line items.
  • Once the schedules of values are created, associated and approved, the subcontractors may submit change order requests to the general contractor, and the general contractor may submit change order requests to the owner/architect, over the Internet 50 to the web server 52. Change order requests seek alterations to the respective submitted and approved schedules of values to reflect a change in performance of work on a contract. Typically, change order requests seek compensation for additional work performed, materials procured or other unanticipated expenses. However, change orders may also request a reduction in compensation based on work or materials that is determined to be unnecessary in the course of the project.
  • A subcontractor builds a change order by first retrieving a list of current change orders from the web server 52, to be displayed at the subcontractor web client 104 or 105, for example. The new change order may be included in an existing change order that has not yet been approved, or provided as a separate change order. Also, unapproved change orders may be edited or deleted at any time.
  • To create a change order, the subcontractor enters data identifying the item number of the subcontractor's schedule of values, with which the change order is associated. However, the change order may also identify a new item number to the extent it involves work that is not readily associated with the existing subcontractor line items. The subcontractor also enters a description of the additional work, e.g., “additional building pad work,” and the scheduled value of the change order, e.g., $3,000.00. The change orders are numbered incrementally. As in the case of the schedules of values, the contract administration program enables the subcontractor to enter comments about the change order to be submitted along with the change order. The subcontractor clicks on a “submit to owner” button, for example, to send the change order to the web server 52, which stores the change order in the database 53 and generates an email to the general contractor at the web client 103 informing of the submitted change order.
  • The general contractor, in turn, incorporates the subcontractor change order into a general contractor change order and submits the general contractor change order to the owner/architect in the same manner described above. In an embodiment, the general contractor may incorporate more than one subcontractor change order into a general contractor change order, in which case the general contractor change order includes a list of the associated subcontractor change orders.
  • The general contractor reviews and approves or rejects the subcontractors' change orders in much the same manner it reviews and approves or rejects the subcontractors' schedules of values. For example, the general contractor associates the line items of a subcontractor's change order with the line items of the general contractor's schedule of values. The general contractor submits the change order, sending it to the web server 52. The web server 52 stores the change order in the database 53 and generates an email to the owner/architect at the web client 102 informing of the submitted change order.
  • The owner/architect reviews the change order and determines whether to accept or reject it. Data indicating the decision is stored in the database 53 and sent by email to the general contractor at the web client 103. When the general contractor receives notice of approval, the general contractor approves the corresponding subcontractor's change order. Likewise, data indicating the approval is stored in the database 53 and sent by email to the appropriate subcontractor at the web client 104 or 105.
  • Once the original schedules of values are created, associated and approved, the general contractor and subcontractors are able to begin submitting applications for payment over the Internet 50 to the web server 52. Of course, the original schedule of values is updated throughout the course of project performance based on approved change orders, described above. Typically, the general contractor does not submit an application for payment until it has received a number of applications for payment from the subcontractors. Accordingly, the subcontractors' applications for payment are addressed first.
  • Referring to FIG. 8, a subcontractor cannot submit an application for payment until it has received approval of its schedule of values from the general contractor at step s810. As stated above, the subcontractor automatically receives notice that its schedule of values has been approved by email over the Internet 50. Also, the subcontractor may access the contract administration program at the web server 52 from the web client 104 or 105 at any time to check the status of the approval.
  • Once approval is received and work on the project commences, the subcontractor periodically creates applications for payment. The timing of the applications for payment are generally governed by the subcontract and may include, for example, submitting an application weekly, monthly or upon completion of predetermined project milestones. The subcontractor accesses the web server 52 from the web client 104 or 105 and retrieves a web page at step s812 designed to elicit information regarding the status of the work performed on the project, an example of which is web page 900 of FIG. 9.
  • The initial application for payment is based on the approved schedule of values. Therefore, before entering any amount to be billed under the subcontract, the application for payment must be edited to include any change orders sought by the subcontractor. At step s814, the subcontractor determines whether any change orders have been submitted to the general contractor since work began. When change orders have been submitted, and approved, the subcontractor decides which, if any, change orders to include in the present application for payment at step s816. Any change orders not included may be submitted in subsequent applications for payment. The line items corresponding to the change orders are automatically updated to reflect the subject matter of the change orders at step s818.
  • After the line items are updated, or when no approved change orders exist, the subcontractor begins building the application for payment. Referring to the web page 900, the subcontractor enters basic information at step s819 to track the application, including, for example, the application number 901, the application date 902 and the time period 903 covered by the application. In an embodiment of the invention, these fields are completed automatically by the contract administration program, along with the identification of the subcontractor submitting the application, the name of the project, the contracting parties and the like.
  • At step s820, the subcontractor enters the work completed and the material stored. The subcontractor uses the fields provided on the web page 900 to accurately track the progress of the subcontract performance. For example, columns A, B and C are the item number 910, the description of work 911 and the scheduled value 912, which respectively match the line item numbers, descriptions of work and scheduled values assigned by the subcontractor in its schedule of values (and modified by any approved change orders selected by the subcontractor in step s816).
  • Columns D and E show the work completed 913 by the subcontractor during the period covered by the application for payment. The work completed 913 is divided into work completed-from previous application 915 and from this period 916. Because the exemplary application for payment is the initial application for payment, the work completed from previous application 915 is all zeros. The work completed-this period 916 shows the amount of work performed in dollars. For example, for line item 1001 (CMU foundations−materials), $800 has been expended of the $8,000 allocated for that line item, and for line item 1002 (CMU foundations−labor), $1,000 has been expended of the $10,000 allocated.
  • Column F of the web page 900 shows the materials presently stored 917. This column contains the dollar amount of materials purchased by the subcontractor and stored, e.g., on site, but not yet incorporated into the project. In the present example, none of the line items include an amount for materials stored. The subcontractor indicates when it finishes entering the work completed and the materials stored, for example, by clicking a “re-calculate fields” button on the web page 900 (not pictured).
  • At step s824, the contract administration program calculates the remaining entries of the web page 900. For example, column G shows the total dollar amount associated with each line item, including the total work completed 913 (i.e., the sum of the work completed-from previous application 915 and the work completed-this period 916) and the materials presently stored 917 for each line item. Column G also includes the percentage 919, showing the percentage of completion based on a comparison of the total completed and stored to data 918 with the scheduled value 912. For line items 1001 and 1002, percent of the scheduled value is included in this application for payment. Column H, balance to finish 920, shows the remaining amount of the scheduled value to be performed by the subcontractor for each line item.
  • In the row showing grand totals 930, the totals for each line item are automatically determined for each of the columns. One exception is the column for percentage 919, which does not show the total percentages. Rather, the percentage 919 for the grand total 930 shows the percentage of the total work completed 918 to the total scheduled value 912.
  • In an embodiment of the invention, the subcontractor indicates whether the general contractor is allowed to make modifications to the application for payment by clicking on the YES/NO radio buttons 931. By agreeing to allow the general contractor to make modifications, the subcontractor may expedite approval of the application for payment, as well as the subsequent general contractor application for payment, in which the subcontractor's application is included. The subcontractor can also enter explanations of charges, give status reports or the like in the comments window 932.
  • The subcontractor submits the application for payment to the general contractor at step s826, for example, by clicking on the “submit to owner” button 933. The application for payment is stored at the database 53 by the web server 52 for the general contractor to review. As with the schedules of values, the web server 52 also generates and sends an email to the general contractor at the web client 103 to inform the general contractor that a new application for payment has been submitted.
  • In an embodiment of the invention, the subcontractor's application for payment cannot be approved unless all of the previous applications for payment have been approved. Also, as stated above with respect to schedules of value, once an application for payment has been approved or rejected, its state cannot be changed, so the general contractor should not approve the subcontractor applications for payment until after it receives approval for the general contractor application for payment in which the subcontractor applications are incorporated. Once an application for payment has been rejected, all subsequent applications for payment from the same subcontractor are also rejected. Similar to the subcontractor schedules of values, the applications for payment submitted to the general contractor have one of four statuses: submitted, viewed, approved and rejected. In an embodiment of the invention, the subcontractor receives an email from the web server 52 whenever the general contractor views, approves and/or rejects each submission.
  • The general contractor's application for payment to the owner/architect is similar to that of the subcontractor's application for payment to the general contractor. Initially, the general contractor receives an approval of its schedule of values from the owner/architect at step s1010 of FIG. 10. Typically, the general contractor receives the notice at the web client 103 from the web server 52 as an email.
  • The general contractor determines to submit an application for payment, based on project completion milestones, agreed monthly or weekly submissions, target dates or the like, as indicated in the general contract. The general contractor logs onto the contract administration program at the web server 52 and selects application for payment for the desired project from a project detail web page. At step s1012, the web client 103 retrieves the application for payment form web page from the web server 52 over the Internet 50. An exemplary application for payment web page is depicted as web page 1100 in FIG. 11.
  • At step s1014, the general contractor determines whether any subcontractor applications for payment have been newly submitted or have not yet been included in a previous general contractor application for payment. If so, the general contractor retrieves a list of subcontractor applications at step s1016 and selects the applications that are to be included in the general contractor's application for payment at step s1018. The general contractor also has self-performed tasks, included in the schedule of values and an application for payment, that do not involve performance of work by a subcontractor.
  • At step s1020, the general contractor determines whether any change orders have been newly submitted or have not yet been included in a previous application for payment. When there are change orders, the general contractor assures that it has received approval of the change orders from the owner/architect at step s1022, discussed above. The general contractor then selects the change orders, if any, to include in the application for payment at step s1024. Any change orders not included may be submitted in subsequent applications for payment. Also, in an embodiment of the invention, a subcontractor change order cannot be disassociated from a general contractor change order once the subcontractor application for payment that includes the subcontractor change order has been included and submitted in a general contractor application for payment. The line items corresponding to the change orders are automatically updated to reflect the subject matter of the change orders.
  • After the line items are updated, or when no approved change orders exist, the general contractor begins building the application for payment. Referring to the web page 1100, the subcontractor enters basic information at step s1028 to track the application, including, for example, the application number 1101, the application date 1102 and the time period 1103 covered by the application. In an embodiment of the invention, these fields are completed automatically by the contract administration program, along with the identification of the name of the general contactor, the name of the project, the contracting parties and the like.
  • At step s1030, the general contractor enters the work completed and the material stored. The general contractor uses the fields provided in the web page 1100 to accurately track the progress of contract performance. For example, columns A, B and C are the item number 1110, the description of work 1111 and the scheduled value 1112, which respectively match the line item numbers, descriptions of work and scheduled values assigned by the general contractor in its schedule of values (and modified by any approved change orders selected by the general contractor in step s1024).
  • Columns D and E shown the work completed 1113 on the project during the period covered by the application for payment. The work completed 1113 is divided into work completed-from previous application 1115 and from this period 1116. Assuming the exemplary application for payment is the initial application for payment, the work completed from previous application 1115 is all zeros. The work completed-this period 1116 shows the amount of work performed in dollars. For example, for line item 103 a (clear building pad), $5,500 has been expended of the $11,000 allocated for that line item, and for line item 103 b (clear remaining site), $6,000 has been expended of the $6,000 allocated. Column F of the web page 1100 shows the materials presently stored 1117. This column contains the dollar amount of materials purchased by the subcontractor and stored, but not yet incorporated into the project. In the present example, none of the line items include an amount for materials stored.
  • The work completed and the materials stored for each line item, as well as the general contractor's markup, are entered at step s1030 of FIG. 10. Also, at step s1034, the amount previously billed is entered, for example, in column D, from previous application 1115. Unlike the subcontractor applications of payment, the general application for payment includes the general contactor's markup. For example, the $11,000 allocated for line item 103 a includes an exemplary ten percent markup on the subcontractor's work. In other words, the subcontractor had scheduled $10,000 for this work and the general contractor added a $1,000 markup (ten percent) in its corresponding scheduled value. Likewise, the work completed 1113 for this period 1116 is based on a $5,000 submission from the subcontractor and a $500 markup by the general contractor.
  • In an embodiment of the invention, the work completed this period 1116 and the materials presently stored 1117 fields are automatically populated by the contract administration program at steps s1030 and s1034 when the general contractor clicks on a button labeled “auto-populate” (not pictured), for example. The program then populates these fields based on information stored in the database 53, such as the general contractor schedule of values, the subcontractor applications for payment, the associated line items, the approved change orders and the like.
  • The amounts automatically entered, however, are guide values for the general contractor, who may replace any of the automatically populated fields with any figure it desires within the scheduled value amount. For example, the general contractor may want to front-load payments under the contract by billing the owner/architect more than amounts billed by the subcontractor. Whether the general contractor has the right to front-load is typically covered by the terms and conditions of the general contract.
  • In an embodiment of the invention, the fields are recalculated for each GC line item according to the following algorithm:
  • WC ( LI ) = E ( SC ) C ( SC ) - D ( SC ) × C ( GC ) - D ( GC ) ( 1 )
  • Where:
  • WC(LI)=the general contractor line item (from the schedule of values) for which the work completed payment amount is being determined;
  • E(SC)=the work completed in the current period for all subcontractor line items associated with the general contractor line item;
  • C(SC)=the original scheduled value for all subcontractor line items associated with the general contractor line item;
  • D(SC)=the work completed as of the previous application for all subcontractor line items associated with the general contractor line item;
  • C(GC)=the original scheduled value of the general contractor's line item; and
  • D(GC)=the work completed as of the previous application for the general contractor's line item.
  • The work completed calculation divides the work completed for the present period for all associated subcontractor line items by the work remaining for the same subcontractor line items to determine a ratio, E(SC)/(C(SC)−D(SC)). The ratio is multiplied by the remaining work of the general contractor, C(GC)−D(GC), to determine the amount that the general contractor should use for work completed this period 1113. Using the remaining work instead of just the original work accommodates the situation in which the general contractor “front loads” its applications for payment, i.e., initially billing the owner at a higher rate than it is actually paying the subcontractor.
  • Referring to the example depicted in web page 1100 of FIG. 11, the contract administration program determines the amount of work completed this period 1113 for Item number 101, based on the subcontractor application for payment as follows: E(SC)=$10,000; C(SC)=$20,000; D(SC)=0; C(GC)=$22,000; and D(GC)=0. Note that the subcontractor figures are based on the general contractor figures, less the general contractor's 10 percent markup. Also, since the application for payment of FIG. 11 is an initial application for payment, the work completed as of the previous application for both the subcontractor and the general contractor is “0.” Accordingly, the application for payment amount is determined as follows:

  • AFP(101)=10,000/20,000×22,000=$11,000
  • The contact administration program can also determine the amount of materials stored 1117 included by the general contractor in its application for payment to the owner/architect for each line item. In an embodiment of the invention, the field is calculated for each GC line item according to the following algorithm:
  • MPS ( LI ) = F ( SC ) C ( SC ) × C ( GC ) ( 2 )
  • Where:
  • MPS(LI)=the general contractor line item for which the materials presently stored payment amount is being determined;
  • F(SC)=the stored materials for the current period for all subcontractor line items associated with the general contractor line item;
  • C(SC)=the original scheduled value for all subcontractor line items associated with the general contractor line item; and
  • C(GC)=the original scheduled value of the general contractor's line item.
  • The stored materials calculation divides the materials presently stored for the present period for all associated subcontractors line items by the original scheduled values for the same line items. This ratio is then multiplied by the corresponding original scheduled value of the general contractor to determine the amount that the general contractor should claim for the materials presently stored. There is no “remaining” stored materials, as in the work completed, so factoring a remaining amount is not applicable to determining the materials presently stored.
  • As stated above, following the guide value for each line item in the general contractor application for payment is discretionary. The general contractor may accept the automatically determined amount, or enter a higher or lower amount. For example, the general contractor may wish to “front load” its applications for payment, initially billing the owner at a higher rate than it is actually paying the subcontractor. Regardless, the contract administration program will apply the algorithms expressed in equations (1) and (2), above, with respect to subsequent applications for payment, resulting in guide values that fully amortize the payment applications to the owner/architect when the subcontractor(s) has been fully paid, even when the general contractor ignores the previous guide values, e.g., when it front-load certain line items.
  • FIGS. 12A-12C shown portions of exemplary spread sheets in which the general contractor elects to front load its applications for payment, requesting a higher payment in the initial application for payment than has been submitted for the corresponding line item by the subcontractor. FIG. 12A shows three line items from a sample first subcontractor application for payment 1210, indicating in columns E and F, respectively, that the total work completed on the subcontract is $7,500 and the total materials presently stored is $2,500. The sample first general contractor application 1230 shows the guide values in columns E and F calculated by the contract administration program in accordance with equations (1) and (2), respectively. Assuming a 10 percent markup, the guide values are determined to be $8,250 and $2,750 for the work completed this period and the materials presently stored.
  • FIG. 12B shows the same three line items from a sample second subcontractor application for payment 1240, indicating in columns E and F, respectively, that the additional work completed on the subcontract is $11,000 and the total materials presently stored is still $2,500. The sample second general contractor application 1260 again shows the guide value in columns E calculated by the contract administration program in accordance with equation (1). Note that the materials presently stored in column F is unchanged.) However, as indicated in column D of the second general contractor application 1260, the general contractor front loaded its previous application by submitting $12,000, as opposed to the guide value of $8,250, as the work completed from the previous application. Therefore, the guide value determined according to equation (1) in column E is $10,266.67. As a result, the total completed and stored to date entry is $25,016.67, while if the guide value had been followed in the first general contractor application 1230, the total completed and stored to date entry would have been $23,100.
  • FIG. 12C shows the same three line items from a sample third subcontractor application for payment 1270, indicating in columns E and F, respectively, that the additional work completed on the subcontract is $11,500, with no materials presently stored, resulting in 100 percent completion of the work scheduled for those three line items, indicated by the percentage in column G. The sample third general contractor application 1290 again shows the guide values in column E calculated by the contract administration program in accordance with equation (1). As indicated in column D, the general contractor followed the guide value from the previous application and submitted the total work from previous applications as $22,266.67. Therefore, the guide value determined according to equation (1) in column E is $10,733.33, which coincides with the remaining amount of work to be performed for the general contractor's line item. Note that the materials presently stored in column F is zero, indicating that the stored material has been used. Accordingly, FIGS. 12A-12C demonstrate that the contract administration program accurately tracks, and recommends appropriate application for payment values, even in the case where the general contractor front loads its billing.
  • Referring back to FIG. 10, the general contractor indicates that it has finished entering the work completed and the materials stored values by clicking a “re-calculate fields” button (not pictured), for example. At step s1036, the contract administration program calculates the remaining entries of the web page 1100 based on the entered values. For example, column G shows the dollar total amount associated with each line item. Column G includes the total completed and stored to data 118, which includes the sum of the work completed-from previous application 1115, the work completed-this period 1116, and the materials presently stored 1117 for each line item. Column G also includes the percentage 1119, showing the percentage of completion based on a comparison of the total completed and stored to data 1118 with the scheduled value 1112. For line item 103 a and 103 b, 50 percent and 100 percent of the scheduled values are respectively included in this application for payment. Column H, balance to finish 1120, shows the remaining amount of the scheduled value to be performed on each project line item.
  • In the row showing grand totals 1130, the totals for each of the general contractor's line items are automatically determined for each of the columns. One exception is the column for percentage 1119, which does not show the total percentages. Rather, the percentage 1119 for the grand total 1130 shows the percentage of the total work completed 1118 to the total scheduled value 1112. The GC can also enter explanations of charges, give status reports or the like in the Comments window 1132.
  • The general contractor submits the application for payment to the general contractor at step s1040, for example, by clicking on the “submit to owner” button 1133. The application for payment is stored at the database 53 by the web server 52 for the owner and/or architect to review. As with the schedules of values, the web server 52 also generates and sends an email to the owner/architect at the web client 102 to inform them that a new application for payment has been submitted.
  • As described above with respect to subcontractor applications for payment, in an embodiment of the invention, the general contractor's application for payment cannot be approved unless all of the previous applications for payment have been approved. Also as stated above, once an application for payment has been approved or rejected, its state cannot be changed. Once an application for payment has been rejected, all subsequent applications for payment from the same subcontractor are also rejected. Similar to the subcontractor applications for payment, the general contractor's applications for payment have one of four statuses: submitted, viewed, approved and rejected.
  • The owner/architect reviews the general contractor's application for payment, as described above with respect to approval of subcontractor applications for payment. For example, the owner/architect is notified of the pending application for payment by email and logs onto the contract administration program at the web sewer 52 to retrieve the application. The owner/architect can approve or reject the application for payment, an indication of which is stored in the database 53 for retrieval by the general contractor, as well as emailed to the general contractor at the web client 103. The owner/architect may include comments in the approval or rejection email, such as “check will be mailed on Friday.”
  • In an embodiment, the owner/architect is able to initiate an electronic finds transfer at the web server 52, based on bank account data for the owner/architect and the general contractor stored in the database 53. Likewise, the general contractor may have the ability to pay subcontractors over the Internet 50 using electronic funds transfer.
  • The process of receiving and accepting applications for payment from subcontractors, and sending applications for payment to the owner/architect, is repeated until work on the contract is complete. Other standard contract provisions, such as time-tables, receipt of permits, project inspections, acceptance of the work, release of retainage amounts and the like, are administered in a conventional manner. However, notices of inspection times and dates, release of retainage amounts, as well as other contract governed events, may be noticed over the Internet 50, e.g., by email, and posted at the associated project web site, since the project participants routinely interact with the centralized web server 52.
  • Accordingly, the present invention provides administration of a contract, and associated subcontracts, from a centralized web server accessible by all contracting (and subcontracting) parties over a packet switched data network, such as the Internet. Schedules of values, applications for payment and change orders corresponding to the general contractor and the subcontractors are built and submitted to the owner/architect and the general contractor, respectively, by way of the web server. Responsive approvals and rejections are likewise communicated through the web servers. Furthermore, emails are generated automatically to notify the contracting and subcontracting parties of the status of various submissions, as well as other contract and project related communications.
  • Although the invention has been described with reference to several exemplary embodiments, it is understood that the words that have been used are words of description and illustration, rather than words of limitation. Changes may be made within the purview of the appended claims, as presently stated and as amended, without departing from the scope and spirit of the invention in its aspects. Although the invention has been described with reference to particular means, materials and embodiments, the invention is not intended to be limited to the particulars disclosed; rather, the invention extends to all functionally equivalent structures, methods and uses such as are within the scope of the appended claims.
  • In accordance with various embodiments of the present invention, the methods described herein are intended for operation as software programs running on a computer processor. Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices can likewise be constructed to implement the methods described herein. Furthermore, alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.
  • It should also be noted that the software implementations of the present invention as described herein are optionally stored on a tangible storage medium, such as: a magnetic medium such as a disk or tape; a magneto-optical or optical medium such as a disk; or a solid state medium such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories. A digital file attachment to email or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. Accordingly, the invention is considered to include a tangible storage medium or distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.

Claims (20)

1. A method of implementing change orders over a data communications network for a construction contract, the method comprising:
entering a new change order request at a user interface connected to the data communications network, the new change order request comprising a description of at least one of additional work or additional materials and a corresponding scheduled value;
determining whether the at least one of addition work or additional materials is associated with an existing line item of a schedule of values previously stored in a database accessible over the communications network via a web server;
including the existing line item in the change order request when the work to be performed is determined to be associated with the existing line item; and
sending the new change order request to the web server over the communications network for approval.
2. The method of claim 1, further comprising:
when the at least one of addition work or additional materials is not associated with an existing line item, creating a new line item corresponding to the new change order request and including the new line item in the change order request.
3. The method of claim 1, further comprising:
retrieving a previous change order from the database;
determining whether the previous change order has been approved or rejected;
when the previous change order has not yet been approved or rejected, revising the previous change order to include the new change order; and
submitting the revised new change order request to the web server over the communications network for approval.
4. The method of claim 1, further comprising:
automatically generating and sending an email notifying an approving party of the submission of the new change order request, wherein the approving party accesses the web server to obtain the change order request.
5. The method of claim 1, further comprising:
accessing the database over the communications network to determine whether the new change order request has been approved or rejected.
6. The method of claim 5, further comprising:
revising the new change order request to change at least one of the description of the work to be performed and the corresponding scheduled value when it is determined that the new change order request has not yet been approved or rejected.
7. The method of claim 5, further comprising:
when the new change order request is approved, updating the existing line item of the previously stored schedule of values to include the scheduled value of the new change order request.
8. The method of claim 1, further comprising:
receiving an email from the approving party over the communications network indicating when the new change order request has been approved or rejected.
9. The method of claim 1, wherein the new change order request is included in a request for payment submitted to the web server for approval.
10. A method of implementing change orders over a data communications network for a construction contract, the method comprising:
retrieving a new change order request of a subcontractor from a web server accessible through the data communications network, the new change order request comprising a scheduled change order value, a subcontractor line item and a description of at least one of additional work and additional materials;
associating the subcontractor line item with a general contractor line item;
generating a general contractor change order request comprising the general contractor line item, a general contractor scheduled value based on the scheduled change order value and a mark-up percentage, and the description of the at least one of the additional work and the additional materials;
sending the general contractor change order request to the web server over the communications network for approval; and
automatically generating a notification to an approving party of the submission of the general contractor change order request, wherein the approving party accesses the web server to obtain the change order request.
11. The method of claim 10, wherein associating the subcontractor line item with the general contractor line item comprises:
determining whether the additional work or the additional materials is associated with an existing general contractor line item of a general contractor schedule of values previously stored in a database accessible through the data communications network;
including the existing general contractor line item in the general contractor change order request when the additional work or the additional materials is determined to be associated with the existing general contractor line item; and
creating a new general contractor line item corresponding to the general contractor change order request when the work to be performed is not associated with an existing line item, and including the new general contractor line item in the general contractor change order request.
12. The method of claim 10, wherein the general contractor change order request comprises a plurality of subcontractor change order requests, including the new subcontractor change order request.
13. The method of claim 10, further comprising:
accessing a database over the communications network to determine whether the general contractor change order request has been approved or rejected.
14. The method of claim 13, further comprising:
when the general contractor change order request is approved, approving the new subcontractor change order request and updating the general contractor line item of the previously stored schedule of values to include the scheduled value of the general contractor change order request.
15. The method of claim 14, further comprising:
automatically generating and sending a notification to the subcontractor to inform the subcontractor that the new subcontractor change order request has been approved.
16. A computer readable medium, storing a program executable by a computer connected to a data communications network, for implementing change orders over the data communications network for a construction contract, the computer readable medium comprising:
a retrieving code segment for retrieving a new subcontractor change order request from a web server accessible through the data communications network, the new change order request comprising a scheduled change order value, a subcontractor line item and a description of at least one of additional work and additional materials, the subcontractor line item being associated with a general contractor line item of a previously stored schedule of values;
a generating code segment for generating a general contractor change order request comprising the general contractor line item, a general contractor scheduled value based on the scheduled change order value and a mark-up percentage, and the description of the at least one of additional work and additional materials;
a submitting code segment for causing the general contractor change order request to be sent to a web server over the communications network requesting approval; and
a notification code segment for automatically generating and sending an electronic notification to an approving party of the submission of the general contractor change order request, wherein the approving party accesses the web server to obtain the general contractor change order request.
17. The computer readable medium of claim 16, wherein when the additional work or the additional materials is determined to be associated with the existing general contractor line item, the existing general contractor line item is included in the general contractor change order request; and
wherein when the additional work or additional materials is not associated with an existing line number, a new general contractor line item corresponding to the general contractor change order request is created and included the new general contractor line item in the change order request.
18. The method of claim 16, wherein the general contractor change order request is included in a subsequent request for payment sent to the web server for approval.
19. The method of claim 16, further comprising:
an updating code segment for updating the general contractor line item of the previously stored schedule of values to include the scheduled value of the general contractor change order request when the general contractor change order request is approved,
wherein the new subcontractor change order request is approved after the general contractor line item has been updated.
20. The method of claim 19, wherein the email code segment automatically generates and sends an email to the subcontractor notifying the subcontractor that the new subcontractor change order request has been approved.
US11/927,961 2002-10-04 2007-10-30 Administering a contract over a data network Abandoned US20080133307A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/927,961 US20080133307A1 (en) 2002-10-04 2007-10-30 Administering a contract over a data network

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US41576202P 2002-10-04 2002-10-04
US10/673,142 US8510181B2 (en) 2002-10-04 2003-09-30 Administering a contract over a data network
US11/927,961 US20080133307A1 (en) 2002-10-04 2007-10-30 Administering a contract over a data network

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/673,142 Division US8510181B2 (en) 2002-10-04 2003-09-30 Administering a contract over a data network

Publications (1)

Publication Number Publication Date
US20080133307A1 true US20080133307A1 (en) 2008-06-05

Family

ID=38823042

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/673,142 Active - Reinstated 2033-06-27 US8510181B2 (en) 2002-10-04 2003-09-30 Administering a contract over a data network
US11/927,961 Abandoned US20080133307A1 (en) 2002-10-04 2007-10-30 Administering a contract over a data network

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/673,142 Active - Reinstated 2033-06-27 US8510181B2 (en) 2002-10-04 2003-09-30 Administering a contract over a data network

Country Status (1)

Country Link
US (2) US8510181B2 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050187808A1 (en) * 2004-02-19 2005-08-25 Adamson James L. Integrated destination sales system with ASP-hosted member interface
US20090018889A1 (en) * 2007-06-13 2009-01-15 Hart Business Solutions, Llc. Administering contracts over data network
US9726750B2 (en) 2013-08-26 2017-08-08 Specialty Electrical, Llc Method and apparatus for multi-mode tracking and display of personnel locations in a graphical model

Families Citing this family (50)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU763571B2 (en) 1998-12-23 2003-07-24 Chase Manhattan Bank, The System and method for integrating trading operations including the generation, processing and tracking of and trade documents
US7822656B2 (en) 2000-02-15 2010-10-26 Jpmorgan Chase Bank, N.A. International banking system and method
US8285641B2 (en) 2000-11-06 2012-10-09 Jpmorgan Chase Bank, N.A. System and method for selectable funding of electronic transactions
US8805739B2 (en) 2001-01-30 2014-08-12 Jpmorgan Chase Bank, National Association System and method for electronic bill pay and presentment
US7191141B2 (en) * 2001-06-13 2007-03-13 Ricoh Company, Ltd. Automated management of development project files over a network
US10311412B1 (en) 2003-03-28 2019-06-04 Jpmorgan Chase Bank, N.A. Method and system for providing bundled electronic payment and remittance advice
US7814003B2 (en) 2003-12-15 2010-10-12 Jp Morgan Chase Billing workflow system for crediting charges to entities creating derivatives exposure
US20050222923A1 (en) * 2004-03-02 2005-10-06 Abstar Disbursing Company Disbursement system
US8554673B2 (en) 2004-06-17 2013-10-08 Jpmorgan Chase Bank, N.A. Methods and systems for discounts management
US8121944B2 (en) 2004-06-24 2012-02-21 Jpmorgan Chase Bank, N.A. Method and system for facilitating network transaction processing
US20080288379A1 (en) 2004-06-29 2008-11-20 Allin Patrick J Construction payment management system and method with automated electronic document generation features
US7925584B2 (en) 2004-06-29 2011-04-12 Textura Corporation Construction payment management system and method with document tracking features
US7877321B2 (en) * 2004-06-29 2011-01-25 Textura Corporation Method of and system for evaluating financial risk associated with a construction project
CA2570897C (en) * 2004-06-29 2017-05-09 Textura, Llc Construction payment management system and method
US9460441B2 (en) 2004-06-29 2016-10-04 Textura Corporation Construction payment management system and method with document exchange features
US20060111945A1 (en) * 2004-11-19 2006-05-25 Realtytracker Llc Method and system for tracking real estate transactions
US7822682B2 (en) 2005-06-08 2010-10-26 Jpmorgan Chase Bank, N.A. System and method for enhancing supply chain transactions
US20150186844A1 (en) * 2006-05-05 2015-07-02 Eznetpay, Llc Pay Request System
US8799043B2 (en) 2006-06-07 2014-08-05 Ricoh Company, Ltd. Consolidation of member schedules with a project schedule in a network-based management system
US8050953B2 (en) * 2006-06-07 2011-11-01 Ricoh Company, Ltd. Use of a database in a network-based project schedule management system
US7734545B1 (en) * 2006-06-14 2010-06-08 Jpmorgan Chase Bank, N.A. Method and system for processing recurring payments
US7668800B2 (en) * 2007-03-15 2010-02-23 Ricoh Company, Ltd. Database query generation for project task management system for managing project schedules over a network
US8826282B2 (en) 2007-03-15 2014-09-02 Ricoh Company, Ltd. Project task management system for managing project schedules over a network
US9152433B2 (en) 2007-03-15 2015-10-06 Ricoh Company Ltd. Class object wrappers for document object model (DOM) elements for project task management system for managing project schedules over a network
US8306883B2 (en) 2007-04-30 2012-11-06 Textura Corporation Construction payment management systems and methods with specified billing features
US20080281738A1 (en) * 2007-05-07 2008-11-13 Ian Christopher Automated Compliance Management of Endowments Throughout Their Life Cycle
US20080281739A1 (en) * 2007-05-09 2008-11-13 Kevin Byrne Automated administration of endowments throughout their life cycle
US8622308B1 (en) 2007-12-31 2014-01-07 Jpmorgan Chase Bank, N.A. System and method for processing transactions using a multi-account transactions device
US7766244B1 (en) 2007-12-31 2010-08-03 Jpmorgan Chase Bank, N.A. System and method for processing transactions using a multi-account transactions device
US20090217241A1 (en) * 2008-02-22 2009-08-27 Tetsuro Motoyama Graceful termination of a web enabled client
US20090217240A1 (en) * 2008-02-22 2009-08-27 Tetsuro Motoyama Script generation for graceful termination of a web enabled client by a web server
US8706768B2 (en) 2008-05-16 2014-04-22 Ricoh Company, Ltd. Managing to-do lists in task schedules in a project management system
US8321257B2 (en) 2008-05-16 2012-11-27 Ricoh Company, Ltd. Managing project schedule data using separate current and historical task schedule data
US7941445B2 (en) * 2008-05-16 2011-05-10 Ricoh Company, Ltd. Managing project schedule data using separate current and historical task schedule data and revision numbers
US8352498B2 (en) 2008-05-16 2013-01-08 Ricoh Company, Ltd. Managing to-do lists in a schedule editor in a project management system
US8862489B2 (en) * 2008-09-16 2014-10-14 Ricoh Company, Ltd. Project management system with inspection functionality
US20100070328A1 (en) * 2008-09-16 2010-03-18 Tetsuro Motoyama Managing Project Schedule Data Using Project Task State Data
US20110161304A1 (en) * 2009-12-30 2011-06-30 Verizon North Inc. (SJ) Deployment and compliance manager
US8447641B1 (en) 2010-03-29 2013-05-21 Jpmorgan Chase Bank, N.A. System and method for automatically enrolling buyers into a network
US8589288B1 (en) 2010-10-01 2013-11-19 Jpmorgan Chase Bank, N.A. System and method for electronic remittance of funds
US20120232945A1 (en) * 2011-03-10 2012-09-13 Hong Kong R&D Centre for Logistics and Supply Chain Management Enabling Technologies Lightweight privacy protection protocol, methods, and systems for rfid and sensor based logistics track and trace data sharing over business subcontracting relationships
US8543503B1 (en) 2011-03-30 2013-09-24 Jpmorgan Chase Bank, N.A. Systems and methods for automated invoice entry
US8543504B1 (en) 2011-03-30 2013-09-24 Jpmorgan Chase Bank, N.A. Systems and methods for automated invoice entry
US9354769B1 (en) 2011-03-31 2016-05-31 Emc Corporation Electronically controlling commitment of a change to stored information
EP3901792A1 (en) * 2011-12-29 2021-10-27 Koninklijke KPN N.V. Method and system for content distribution
US20140297468A1 (en) * 2013-03-27 2014-10-02 Fraser Patterson Consumer Contractor Connector Apparatuses, Methods and Systems
US9058626B1 (en) 2013-11-13 2015-06-16 Jpmorgan Chase Bank, N.A. System and method for financial services device usage
US11055725B2 (en) * 2017-03-20 2021-07-06 HomeAdvisor, Inc. System and method for temporal feasibility analyses
US10872370B2 (en) 2017-11-14 2020-12-22 Tommy Run LLC Systems and methods for on-demand delivery of construction materials and other items
US11481702B1 (en) * 2020-06-18 2022-10-25 MiView Integrated Solutions, LLC Worksite information management system

Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
US5689705A (en) * 1995-02-13 1997-11-18 Pulte Home Corporation System for facilitating home construction and sales
US5761674A (en) * 1991-05-17 1998-06-02 Shimizu Construction Co., Ltd. Integrated construction project information management system
US5799286A (en) * 1995-06-07 1998-08-25 Electronic Data Systems Corporation Automated activity-based management system
US5893082A (en) * 1996-12-23 1999-04-06 Mccormick; John M. System for processing and presenting cost estimates in the construction industry
US5926816A (en) * 1996-10-09 1999-07-20 Oracle Corporation Database Synchronizer
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
US6038547A (en) * 1998-01-07 2000-03-14 Casto; Robin L. Construction tracking and payment method and system
US6076080A (en) * 1997-11-04 2000-06-13 The Standard Register Company Forms order entry system
US6078907A (en) * 1998-02-18 2000-06-20 Lamm; David Method and system for electronically presenting and paying bills
US20020016725A1 (en) * 2000-06-13 2002-02-07 Insustria Solutions, Incorporated Systems and methods for the collaborative design, construction, and maintenance of fluid processing plants
US6393410B1 (en) * 2000-05-12 2002-05-21 Frederick Thompson Process and a system for listing information relating to a construction project over a computer network
US20020073114A1 (en) * 2000-10-30 2002-06-13 Nicastro Cherisse M. Business asset management system
US6446053B1 (en) * 1999-08-06 2002-09-03 Michael Elliott Computer-implemented method and system for producing a proposal for a construction project
US20050289051A1 (en) * 2004-06-29 2005-12-29 Allin Patrick J Construction payment management system and method
US20070078771A1 (en) * 2004-06-29 2007-04-05 Allin Patrick J Construction payment management system and method with document tracking features
US7330822B1 (en) * 2001-05-29 2008-02-12 Oracle International Corporation Methods and systems for managing hierarchically organized and interdependent tasks and issues

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8660931B2 (en) * 2001-09-28 2014-02-25 Siebel Systems, Inc. Method and system for automatically generating invoices for contracts

Patent Citations (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
US5761674A (en) * 1991-05-17 1998-06-02 Shimizu Construction Co., Ltd. Integrated construction project information management system
US5689705A (en) * 1995-02-13 1997-11-18 Pulte Home Corporation System for facilitating home construction and sales
US5991769A (en) * 1995-02-13 1999-11-23 Pulte Home Corporation System for facilitating home construction and sales
US5799286A (en) * 1995-06-07 1998-08-25 Electronic Data Systems Corporation Automated activity-based management system
US5926816A (en) * 1996-10-09 1999-07-20 Oracle Corporation Database Synchronizer
US5893082A (en) * 1996-12-23 1999-04-06 Mccormick; John M. System for processing and presenting cost estimates in the construction industry
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
US6076080A (en) * 1997-11-04 2000-06-13 The Standard Register Company Forms order entry system
US6038547A (en) * 1998-01-07 2000-03-14 Casto; Robin L. Construction tracking and payment method and system
US6078907A (en) * 1998-02-18 2000-06-20 Lamm; David Method and system for electronically presenting and paying bills
US6446053B1 (en) * 1999-08-06 2002-09-03 Michael Elliott Computer-implemented method and system for producing a proposal for a construction project
US6393410B1 (en) * 2000-05-12 2002-05-21 Frederick Thompson Process and a system for listing information relating to a construction project over a computer network
US20020016725A1 (en) * 2000-06-13 2002-02-07 Insustria Solutions, Incorporated Systems and methods for the collaborative design, construction, and maintenance of fluid processing plants
US20020073114A1 (en) * 2000-10-30 2002-06-13 Nicastro Cherisse M. Business asset management system
US20040015367A1 (en) * 2000-10-30 2004-01-22 Nicastro Cherisse M. Business asset management system using virtual areas
US7330822B1 (en) * 2001-05-29 2008-02-12 Oracle International Corporation Methods and systems for managing hierarchically organized and interdependent tasks and issues
US20050289051A1 (en) * 2004-06-29 2005-12-29 Allin Patrick J Construction payment management system and method
US20070078771A1 (en) * 2004-06-29 2007-04-05 Allin Patrick J Construction payment management system and method with document tracking features

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050187808A1 (en) * 2004-02-19 2005-08-25 Adamson James L. Integrated destination sales system with ASP-hosted member interface
US8560355B2 (en) * 2004-02-19 2013-10-15 Idss (Internet Destination Sales System) Internet destination sales system with ASP-hosted member interface
US20140236646A1 (en) * 2004-02-19 2014-08-21 Idss (Internet Destination Sales System) Internet Destination Sales System with ASP-Hosted Member Interface
US20090018889A1 (en) * 2007-06-13 2009-01-15 Hart Business Solutions, Llc. Administering contracts over data network
US8015113B2 (en) 2007-06-13 2011-09-06 Hart Business Solutions, Llc. Administering contracts over data network
US8326755B2 (en) 2007-06-13 2012-12-04 Hart Business Solutions, LLC Administering contracts over data network
US9726750B2 (en) 2013-08-26 2017-08-08 Specialty Electrical, Llc Method and apparatus for multi-mode tracking and display of personnel locations in a graphical model

Also Published As

Publication number Publication date
US8510181B2 (en) 2013-08-13
US20070288334A1 (en) 2007-12-13

Similar Documents

Publication Publication Date Title
US8510181B2 (en) Administering a contract over a data network
US8326755B2 (en) Administering contracts over data network
US8712819B2 (en) System and method for internet based procurement of goods and services
US7062514B2 (en) Construction project submittal management
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
US8341078B2 (en) Construction payment management system and method with document tracking features
JP4898638B2 (en) System and method for placing reinsurance
US20060190391A1 (en) Project work change in plan/scope administrative and business information synergy system and method
US20030225683A1 (en) Electronic bid/proposal system for the construction industry
US20020087705A1 (en) System and method for managing contracts
US20140343987A1 (en) Construction project submittal management
US20100287092A1 (en) Method and system for real estate loan administration
US20090210307A1 (en) Method and system for promoting service providers
US20150193886A1 (en) Pay Request System
US20070005440A1 (en) Construction project submittal management
AU2016200117B2 (en) Construction Payment Management System and Method with Document Tracking Features
AU2014200162B2 (en) Construction payment management system and method with document tracking features
AU2012207008B2 (en) Construction payment management system and method with document tracking features

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

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