REGISTER  |  SIGN IN
United States Patent Application20040015367
Kind CodeA1
Nicastro, Cherisse M. ; et al.January 22, 2004
Business asset management system using virtual areas
Abstract
A system for defining and managing an asset which includes a data store for virtual area data provided on a host computer coupled to a network. The system includes a data input and supplement toolset including and including at least one of an item procurement system, a cost management system, a project management system, and an information collection system. Each system includes a database interface allowing the system to retrieve, use and modify data subject to permissions granted by project managers.
Inventors:Nicastro; Cherisse M. (Las Vegas, NV), Wucherer; Thomas A.  (Las Vegas, NV), Nisbet; W. Todd  (Las Vegas, NV), Marnell; Anthony A. II  (Las Vegas, NV), Marnell; Anthony A. III  (Las Vegas, NV), Spencer; Herman JR.  (Las Vegas, NV)
Correspondence Name and Address:685 MARKET STREET, SUITE 540
VIERRA MAGEN MARCUS HARMON & DENIRO LLP
SAN FRANCISCO
CA
94105
US
Series Code:016615
Filed:October 30, 2001
U.S. Current Class:705/1
U.S. Class at Publication:705/1
Intern'l Class:G06F 017/60
Claims

What is claimed is:
1. A system for defining and managing an asset, comprising: a data store for virtual area data provided on a computer coupled to a network; and a data input and supplement toolset linking virtual area data to business objects.

2. The system of claim 1 wherein the virtual area data comprises data arranged in a hierarchical data structure representing three-dimensional physical space.

3. The system of claim 2 wherein the virtual area data is linked to item specification data values comprising an item specification provided in a plurality of data fields describing the item.

4. The system of claim 3 wherein said item specification data includes: at least one attribute value; at least one component value; and at least one allocation value.

5. The system of claim 2 wherein the data input and supplement toolset comprises a computer aided design software plug-in.

6. The system of claim 2 wherein the data input and supplement toolset comprises a item specification creation and editing tool.

7. The system of claim 1 wherein the data input and supplement toolset includes an item procurement toolset.

8. The system of claim 7 wherein the item procurement toolset includes a bid tool.

9. The system of claim 7 wherein the item procurement toolset includes a request for quotation tool.

10. The system of claim 1 wherein the data modification toolset includes a cost management toolset.

11. The system of claim 10 wherein the data input and supplement toolset includes an estimate tool.

12. The system of claim 10 wherein the data input and supplement toolset includes an invoice tool.

13. The system of claim 10 wherein the data input and supplement toolset includes a budget tool.

14. The system of claim 10 wherein the data input and supplement toolset includes a payment tool.

15. The system of claim 10 wherein the data input and supplement toolset includes an contract tool.

16. The system of claim 1 wherein the data input and supplement toolset includes a teamwork toolset.

17. The system of claim 16 wherein the project teamwork toolset includes a collaboration tool.

18. The system of claim 16 wherein the project teamwork toolset includes a message center.

19. The system of claim 16 wherein the project teamwork toolset includes a request for information tool.

20. The system of claim 1 wherein the project includes a design phase, a modification phase and a procurement phase, and data is entered and modified throughout each such phase.

21. The system of claim 1 wherein the data store contains links to other data in the system such that a change to one item or component is propagated to all linked data.

22. The system of claim 1 wherein the data input system includes a CAD software plug-in.

23. The system of claim 1 wherein the data store is updated in real time.

24. The system of claim 1 further including an order fulfillment tool.

25. A system for defining and managing a physical asset requiring a plurality of items and components, comprising: a data store for virtual area data, including item attributes, for objects incorporated into or consumed during the creation of the asset; at least one data creation toolset for virtual area data into the data store; and at least one item procurement system, the procurement system including a data store interface allowing supplementation of virtual area data.

26. The system of claim 25 further including a cost management system including a data store interface allowing modification of virtual area data.

27. The system of claim 25 further including a project management system including a data store interface allowing reference to virtual area data.

28. The system of claim 25 further including an information collection system including a data store interface.

29. The system of claim 25 wherein the procurement system includes a bidding tool.

30. The system of claim 29 wherein data in the data store organized in the virtual area is linked to bidding tool.

31. The system of claim 30 wherein data in the data store includes attributes and components exploitable by users in formulating and responding to bids.

32. The system of claim 30 wherein the bidding tool modifies data and updates virtual areas used by other tools.

33. The system of claim 25 wherein the procurement system includes a purchasing tool.

34. The system of claim 33 wherein data in the data store organized in virtual area is linked to purchase tool.

35. The system of claim 34 wherein data in the data store includes attributes and components exploitable by users in formulating and responding to purchases.

36. The system of claim 34 wherein the purchase tool modifies data and updates data linked to virtual areas used by other tools.

37. The system of claim 34 where in the purchase tool includes a purchase rule set, including a default rule set and a user-defined business rule set.

38. The system of claim 34 wherein said system further includes a virtual area definition application, and said purchase tool interfaces with said virtual areas during a bid process.

39. A system for defining and managing a physical asset requiring a plurality of items and components, comprising: a data store for virtual area data, including item attributes, for objects incorporated into or consumed during the creation of the asset; at least one data creation system for virtual area data into the data store; and a cost management system including a data store interface allowing supplementing of virtual area data.

40. The system of claim 39 wherein the cost management system includes an estimate tool.

41. The system of claim 40 wherein said system further includes a virtual area definition application, and said estimate tool incorporates virtual area classifications and virtual area data.

42. The system of claim 40 wherein said estimate tool allows assignment of project codes to estimate items which can be rolled into a budget.

43. The system of claim 40 wherein said estimate tool includes an estimate roll-up tool.

44. The system of claim 39 wherein the cost management system includes a budgeting tool.

45. The system of claim 44 wherein said budget tool incorporates links to transactions with virtual areas.

46. The system of claim 44 wherein said budget tool incorporates links to transactions with item purchase orders.

47. The system of claim 44 wherein said budget tool incorporates transaction documents and defines documents based on default and user-defined business rules.

48. The system of claim 44 wherein said system further includes a virtual area definition application, and said budget tool interfaces with said virtual areas to allow categorization of budget items by virtual area.

49. The system of claim 39 wherein the cost management system includes a contract tool.

50. The system of claim 49 wherein said contract tool is linked to a bidding tool.

51. The system of claim 49 wherein said system further includes a virtual area definition application, and said contract tool is linked to said virtual areas.

52. The system of claim 49 wherein modifications made by the contract tool update virtual areas used by other toolsets.

53. The system of claim 52 wherein the contract tool includes a set of default and user-defined business rules.

54. The system of claim 39 wherein the cost management system includes an application for payment tool.

55. The system of claim 39 wherein the cost management system includes an invoice tool.

56. A system for defining and managing a physical asset requiring a plurality of items and components, comprising: a data store for virtual area data, including item attributes, for objects incorporated into or consumed during the creation of the asset; at least one data creation system for virtual area data into the data store; and a teamwork system including a data store interface.

57. The system of claim 56 further including at least one item procurement system, the procurement system including a data store interface allowing modification of virtual area data.

58. The system of claim 56 further including a cost management system including a data store interface allowing modification of virtual area data.

59. The system of claim 56 further including a project management system including a data store interface allowing reference to virtual area data.

60. A system for defining and managing a physical asset requiring a plurality of items and components, comprising: a data store for virtual area data, including item attributes, for objects incorporated into or consumed during the creation of the asset; at least one data creation system for virtual area data into the data store; and a project management system including a data store interface allowing supplement to virtual area data.

61. The system of claim 60 further including at least one item procurement system, the procurement system including a data store interface allowing modification of virtual area data.

62. The system of claim 60 further including a cost management system including a data store interface allowing modification of virtual area data.

63. The system of claim 60 further including an information collection system including a data store interface.

64. The system of claim 33 wherein the project management system includes multiple projects.

65. The system of claim 60 wherein the data store stores object data by project.

66. A method for constructing data concerning item specifications of an asset, comprising: providing a user data entry interface; receiving a plurality of data values, each into a data field of the interface, wherein the plurality of data fields comprise a specification for the item and each data field of the specification describes an attribute of the item, and associating the specification with a virtual area.

67. The method of claim 66 wherein said step of providing occurs on a first computer and said step of receiving occurs on a second computer.

68. The method of claim 67 wherein said first and second computers are coupled by a network.

69. The method of claim 68 wherein said network is the Internet.

70. A system for project management, comprising: a component virtual area data store including component object data; a project management application server including a virtual area input system, having a virtual area definition tool

71. The system of claim 70 wherein the virtual area definition tool defines a virtual area as a collection of components and items.

72. The system of claim 70 wherein the virtual area comprises a spatial representation of an asset that can be used throughout the lifecycle of the asset.

73. The system of claim 70 wherein the system further includes: a data input tool; an virtual area system; a procurement system; a cost management system; a project management system.

74. The system of claim 73 wherein said virtual area definition can be shared by said virtual area system, procurement system, cost management system, and project management system.

75. The system of claim 73 wherein said virtual area definition can be shared amongst users in a project.

76. The system of claim 73 wherein said virtual area definition can be shared by multiple organizations.

77. The system of claim 73 wherein said virtual area provides a plurality of work breakdown structures.

78. The system of claim 77 wherein said work breakdown structure is a spatial representation of data.

79. The system of claim 77 wherein said work breakdown structure is a project viewpoint.
Description


CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application relates to application Ser. No. 09/557,641
(attorney docket TRIRG-08330US0) filed on Apr. 25, 2000, entitled "Agent Based Purchasing System" and naming Thomas A. Wucherer as inventor, the application being incorporated herein by reference in its entirety.

[0002] This application relates to application Ser. No. 09/519,935
(attorney docket TRIRG-08331US0) filed on Mar. 7, 2000, entitled "Integrated Business System for the Design, Execution and Management of Projects" and naming Cherisse M. Nicastro, Thomas A. Wucherer, Todd Nisbet and Anthony A. Marnell II as inventors, the application being incorporated herein by reference in its entirety.

[0003] This application relates to U.S. Pat No. ______ (attorney docket TRIRG-08851US00) filed on Oct. 30, 2001, entitled "Intelligent Object Builder" and naming Thomas A. Wucherer, Cherisse M. Nicastro, Anthony A. Marnell II and Anthony A. Marnell III as inventors, the application being incorporated herein by reference in its entirety.

[0004] This application relates to application Ser. No. ______ (attorney docket TRIRG-01000US0) filed on Oct. 30, 2001, entitled "Business Asset Management System" and naming Cherisse M. Nicastro, Thomas A. Wucherer, Todd Nisbet, Anthony A. Marnell II, Anthony A. Marnell III, and Herman Spencer Jr. as inventors, the application being incorporated herein by reference in its entirety.

[0005] This application relates to application Ser. No. ______ (attorney docket TRIRG-01001US0) filed on Oct. 30, 2001, entitled "Item Specification Object Management System" and naming Cherisse M. Nicastro, Thomas A. Wucherer, Todd Nisbet, Anthony A. Marnell II, and Anthony A. Marnell III as inventors, the application being incorporated herein by reference in its entirety.

CLAIM OF PRIORITY

[0006] This application claims the benefit of U.S. Provisional Application Serial No. 60/244,492, entitled "Intelligent CAD Objects Technology", filed Oct. 30, 2000.

[0007] This application also claims the benefit of U.S. Provisional Application Serial No. 60/246,275, entitled "Intelligent CAD Objects", filed Nov. 6, 2000.

[0008] This application claims the benefit of U.S. Provisional Application Serial No. 60/244,457, entitled "Item Data Integration System And Method", filed Oct. 30, 2000.

[0009] This application also claims the benefit of U.S. Provisional Application Serial No. 60/246,276, entitled "Item Data Integration System And Method", filed Nov. 6, 2000.

[0010] This application claims the benefit of U.S. Provisional Application Serial No. 60/244,493, entitled "Tracking Modules For Specified Objects", filed Oct. 30, 2000.

[0011] This application claims the benefit of U.S. Provisional Application Serial No. 60/244,485, entitled "Module For Publishing Reports On Intelligent Object", filed Oct. 30, 2000.

LIMITED COPYRIGHT WAIVER

[0012] A portion of the disclosure of this patent document contains material to which the claim of copyright protection is made. The copyright owner has no objection to the facsimile reproduction by any person of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office file or records, but reserves all other rights whatsoever.

BACKGROUND OF THE INVENTION

[0013] 1. Field of the Invention

[0014] The present invention relates to a system for designing, constructing and managing the a physical asset such as a building, property, aircraft, or the like.

[0015] 2. Description of the Related Art

[0016] Many industries employ a team of players to design and execute a project. For example, the construction industry employs a team of players to design and construct a building, such as an office building, a hotel/casino, or a manufacturing facility. Typically, the project team includes architects who prepare architectural drawings and specifications of the project according to a developer's direction. The team also includes engineers who are responsible for building systems such as structural, power, heating, cooling, plumbing systems, etc., and interior designers who are responsible for specifications relevant to interior design such as the selection and placement of furniture, paint selection, wall coverings, fixtures, office equipment, etc. The team's contractor implements the designs of the architects, engineers, and interior designers, and is generally responsible for the purchase of materials, electrical systems, mechanical systems, life safety systems, furniture, fixtures, etc., and for the management of any or all subcontractors who implement the design drawings and specifications. Other project participants may include a purchasing agent or purchasing department that is responsible for purchasing items (e.g., furniture, fixtures and equipment, etc.) for integration into the project. Contractors and subcontractors who actually build the project according to the architectural drawings. A project superintendent may manage the participants, such as by approving some or all changes to the project requested by the participants. Additionally, the project owner may participate to ensure that the project meets his or her requirements from initial conception through completion. Finally, project accountants are responsible for payment of goods and services.

[0017] In the past, the design and construction of an asset involved the transfer of a substantial amount of paper between the various team members. For example, the architect may prepare conceptual paper specifications and drawings for a building project. These paper specifications and drawings, in turn, may be provided to one or more additional architectural engineers for modification or approval. The chief architect must provide his paper design specifications and drawings, typically via overnight delivery, to one or more of the collaborating firms. These additional team members typically add components or make modifications to the initial architectural drawings and specifications. Once revisions are completed, the collaborating firms return the revised architectural specification and drawings to the architect so that he may compile a master set of building specifications and drawings. Several different, further revisions may occur between the architect and the other project team engineers before the final set of master architectural specifications and drawings is created.

[0018] The architectural specifications and drawings, once completed, are also provided to interior designers for input with respect to interior design features such as furniture, wall coverings, paint selection, office equipment, etc. In that each item added to a construction project, including furniture, fixtures, and equipment, typically generates more paper specifications, the interior designers additionally generate a substantial amount of paper that must be properly cataloged and distributed to other project team members. At any point during the project, revisions to the original architectural design specifications and drawings may occur which, in turn, may require other revision of the specifications of the interior designers and/or collaborating engineers.

[0019] Ultimately, the interior design specifications along with the architectural and engineering design specifications and/or drawings are provided to a contractor who, in accordance with the specifications and drawings, coordinates subcontractors, purchasing agents, etc., to purchase the raw materials, electrical systems, mechanical systems, life safety systems, building equipment, labor fixtures, etc. and facilitates construction management of the project. Construction management or finance team members are responsible for maintaining the budget of the construction project, and must have current, accurate information relating to costs of materials, fixtures, labor, etc. Additionally, accountants pay project invoices and track the project's accounting commitments. At any point, an owner, architect, engineer, interior designer, or contractor may propose modifications to the project that necessitate further, hurried paper transfer amongst the team members to insure that all are working with the same information.

[0020] Computer implemented systems have streamlined many project processes. In the architecture, engineering, and construction industry, software systems have been developed which aid each team member (specific to each team member's position) in the development of a construction project. For example, computer aided design tools have been developed which enable an architect or interior designer to model an asset and store that model in a database. These computer aided design tools allow more efficient modifications to an existing design than the prior art method of employing drawings in which changes were made by hand. Accounting systems are also available which enable the paperless financial management of a construction project. Additionally, software systems are available to contractors to facilitate the necessary purchases, scheduling and management of a construction project.

[0021] While these existing architecture, engineering and construction software systems aid individual project team members, communication between the various team members remains as inefficient as in the past. In other words, an architect can make revisions to the architectural specifications of a asset by accessing and modifying an existing database model of that asset. The architect has no need to generate a hard-copy of the architectural drawings and manually revise each drawing. However, the architect must still communicate with the interior designer, contractor, finance team members, etc., via the old method of printing out and hastily distributing (usually numerous) architectural drawings. This is especially true when project team members wish to modify item specifications.

[0022] A project typically involves many phases including design and build. These phases often overlap and each is highly dynamic. The design phase usually starts with one or more designers creating conceptual drawings of the project according to a developer's direction. The drawings generally include perimeter lines representing specific areas (e.g., restaurants, rooms, lobbies, offices, etc.) within the project. The drawings may also include graphical representations of items within the specified areas. For example, an architect may create a drawing of a restaurant area of a hotel/casino project. The restaurant drawing may include graphical representations of furniture, fixtures, and equipment (FF&E) such as tables, windows, ovens, refrigerators, a backup power generator, etc.

[0023] The initial drawings, once completed, are provided to several other project participants involved in the design and build process. For example, the restaurant drawing example above may be provided to one or more structural engineers, mechanical engineers, electrical engineers and interior designers for their review, modification, and/or supplementation. These project participants may add further graphical representations of items to the initial set of drawings. An interior designer of the project may wish to add graphical representations of additional items such as chairs or art work to a dining room sub-area of the example restaurant drawing above. A structural engineer may also seek to add graphical representations of items to the restaurant drawing such as a platform on which the backup power generator (graphically represented in the drawing) rests. When project participants (e.g., engineers, interior designers, etc.) receive initial drawings of the project, the drawings give very little information about the items graphically represented. Typically, the drawings simply identify the items by title or type (e.g., "a table," "a window," "a backup power generator"). The engineers, interior designers, and other project participants further define or specify the characteristics or attributes of items originally contained in the drawings or items added to the drawings.

[0024] The engineers or designers sometimes annotate specification information on the drawings, but usually the engineer or designer creates a separate specification sheet for each item graphically represented on the drawing. For example, an interior designer may create a separate specification sheet for each type of chair graphically represented in the restaurant drawing. Each specification sheet contains descriptive information (size, as size, material and finish, etc.) regarding a type of chair, and may reference other specifications such as fabric. Likewise, an electrical engineer may, for example, create a separate specification sheet for the graphically represented backup power generator describing, for example, the generator's size, power generation capacity, weight, and other attributes.

[0025] In addition to providing specifications for items contained on drawings, there are times when drawings are not created or items are not contained on a drawing which is created, but there are still specifications for items required. For instance, in the above restaurant example is remodeled, specifications for new furnishings may be created without a drawing. Alternately the designer may provide an item schedule which list many like items and their distinguishing characteristics or referenced items.

[0026] FIG. 1 includes an example of an item specification to be included as part of a construction project. An interior designer developed this specification sheet for an entertainment center to be included in the living room of a suite of a hotel project. Portion 110 of the specification sheet includes general information about the specification, such as a specification number, and the area and project into which the item will be incorporated. Portion 120 includes manufacturer information, distributor information, a description of the item, the dimensions of the item, manufacturer catalog information and the manufacturer catalog description. Portion 130 describes the quantity of the item to be ordered, price information, and budget information for the item. Portion 140 indicates information about receiving a sample of the item, and portion 150 includes information about the finish for the item. Portion 150 also includes notes about the finish, notes about the interior dimensions, and a note that the specification was issued to the purchasing department on May 26, 1998. Portion 160 includes an image of the entertainment center. Portion 170 shows information about other specifications providing information about the entertainment center. Not all portions 110 through 160 are included as part of every specification, and specifications may have portions describing other information not shown.

[0027] Other item specifications may contain different data or sections of information. For instance, portion 120 may list the color, weave, repeat, and pattern for a fabric. The details required are identified by the type of item (e.g., hard furniture, upholstered furniture, fabric, oven, sink, faucet, chiller, etc.). Each of these types will have different characteristics or attributes to be described to differentiate like items. The type of item also may require references to other specifications required for an assembly. For example, furniture may reference fabric and paint while chillers may reference piping and pumps. Attributes and required references must be defined in templates for each type of item specification.

[0028] Engineers and designers normally employ software applications for generating specification sheets for project items for which they have responsibility. These software applications generate electronic versions of specification sheets into which engineers or interior designers enter descriptive information. Engineers or designers usually enter a reference to a graphical representation in a drawing into the appropriate specification sheet so that the specification sheet can be associated with an item represented on the drawing. The electronic specification sheets may be organized as flat files, spreadsheets, or word-processing documents.

[0029] Once the engineers or designers finish writing an item specification, the specification is ready to be provided or "published" to other project participants for review, modification, supplementation, and/or approval. The engineer or designer can send the specification as e-mail attachments if the recipient has a computer system with appropriate software applications for accessing the attachments. Alternatively, copies of the specification may be printed and distributed. The author saves one copy as the original specification sheet in electronic version form, hard copy form, or both, for archiving purposes. Except for the graphical reference in the specification sheet, specification sheets are forwarded to other project participants disassociated from their corresponding drawings.

[0030] One or more revisions to each item specification may occur throughout the process. Indeed, revisions to an item specification can occur even after the corresponding item is purchased. In this latter case, the purchased item would normally be located and returned to its manufacturer, and the purchase price may be refunded, in whole or in part.

[0031] Specification revisions may occur for a variety of reasons by a variety of project participants. For example, the project owner, upon receipt of a specification for one of the restaurant chairs, may desire the chair color to be different than originally specified or determine that the chair as originally specified is too expensive. Another interior designer for the project, upon receipt of the same specification for the restaurant chair, may notice that the originally specified fabric did not include fire treatment in accordance with local fire codes. The structural engineer, upon receipt of the specification for the backup power generator, may notice that his platform may not support the weight of the backup generator specified by the electrical engineer. Each reason for revision is communicated to the original author who, in response, revises the specification accordingly. Once revised, the specification is re-distributed to other project participants for further review, modification, supplementation, and/or approval. The author of the original specification sheet has the responsibility for maintaining a history of all revisions to the specification sheet. The author also has the responsibility to ensure that all necessary project participants have the most recent version of the specification sheet.

[0032] Once a specification sheet for an item has been approved by all the necessary project participants, it may be submitted to the project's purchasing agent. The purchasing agent, in turn, may create a purchase order for the item using information from the specification sheet. An example of a purchase order for several items, including the entertainment center of FIG. 1, is shown in FIG. 2. Page 1 of the purchase order shows the entertainment center of FIG. 1 as item 1, page 2
shows orders for other items 2-5, and page 3 shows general notes for the purchase order.

[0033] The purchasing agent, like the project engineers and interior designers, may employ a computer system executing specialized software for generating a purchase order. Typically, the purchasing agent manually transfers specification sheet information into the purchase order, as shown in FIG. 2. The purchasing agent subsequently sends the purchase order to manufacturers via hard copy or e-mail attachment. The purchasing agent also sends a copy of the purchase order to the project's accountant.

[0034] Coordinating communication of information regarding items in a construction project becomes more complex as the scale of the project increases. Collaboration and the exchange of information, including drawings and item specifications, between design and build participants also increase the complexity of each project. Effective and efficient collaboration is often the single most important key to bringing a project to fruition in a quality, timely and cost effective manner. However, as more fully exemplified above, collaboration and information exchange between participants, is typically a paper-based and chaotic process. Furthermore, it is difficult to determine the history of an item based upon the papers residing at different project participants.

[0035] Managing change throughout the life cycle is also difficult in a paper-based or disparate application-based process. Decisions are not always based on all information available, for instance, an owner may choose not change the color of a fabric if the owner had known that the fabric had already been purchased and that a restocking fee would apply.

[0036] What is needed is an item data integration system that will integrate data from different applications about an item throughout the item's lifecycle. Data from the separate applications should be presented as an integrated whole to users of the item data integration system. An item data integration system that is capable of providing budgeting, design specification, CAD drawings, purchasing, bid processing, receiving, invoicing, location, and maintenance data, or other processes in the item's lifecycle, about an item is desirable.

[0037] Integrated data allows change management throughout the process. For example, designers may wish to be notified if they are deleting an item from a drawing that has already been purchased; Specifiers may wish to be notified if they are exceeding the approved budget for an item; Purchasing Agents may wait to purchase items if they know there is a revision in progress; Maintenance personnel may want to know when preventative maintenance is required or a warrantee for an item is expired; etc. The rules for managing these changes and notifications should be configured by project participants.

SUMMARY OF THE INVENTION

[0038] The present invention, roughly described, pertains to a system and method allowing comprehensive management of an asset from design through building and management. Multiple implementations of the method and system are disclosed herein.

[0039] In one aspect the invention is a system for defining and managing an asset which includes a data store for virtual area data provided on a host computer coupled to a network, and a data input and supplement toolset linking virtual area data to business objects. In a further embodiment, the system manages physical assets requiring a plurality of items and components. In this embodiment, the system a data store for virtual area data, including item attributes, for objects incorporated into or consumed during the creation of the asset. The system also includes at least one data creation system for virtual area data in the data store, and at least one of: a teamwork system, a project management system, a cost management system, or an item procurement system, each including a data store interface allowing supplementation of virtual area data.

[0040] In another aspect, the invention may provide a change management notification to team members notifying them when specific actions occur as defined by user set business rules. Furthermore, The invention may also route system business objects for approval and publishing to project team members and track the history of changes to system business objects.

[0041] In yet anther embodiment, the invention comprises a method for constructing data concerning item specifications of an asset. The method may include the steps of providing a user data entry interface; receiving a plurality of data values, each into a data field of the interface, wherein the plurality of data fields comprise a specification for the item and each data field of the specification describes an attribute of the item, and associating the specification with a virtual area.

[0042] The present invention can be accomplished using hardware, software, or a combination of both hardware and software. The software used for the present invention is stored on one or more processor readable storage media including hard disk drives, CD-ROMs, DVDs, optical disks, floppy disks, tape drives, RAM, ROM or other suitable storage devices.

[0043] These and other objects and advantages of the present invention will appear more clearly from the following description in which the preferred embodiment of the invention has been set forth in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The invention will be described with respect to the particular embodiments thereof. Other objects, features, and advantages of the invention will become apparent with reference to the specification and drawings in which:

[0045] FIG. 1 depicts a prior art item specification document used in a project.

[0046] FIG. 2 depicts a prior art purchase order for the items in the specification document shown in FIG. 1.

[0047] FIG. 3A is a block diagram showing an overview of one embodiment of the system of the present invention.

[0048] FIG. 3B is a representation of a user Home Page in accordance with the present invention.

[0049] FIG. 3C is a representation of a Project Home Page in accordance with the present invention.

[0050] FIG. 4 is a block diagram showing the data flow for an item throughout several stages of an item's lifestyle.

[0051] FIG. 5 shows an example of a specification as a configurable data object.

[0052] FIG. 6 shows an example of a configuration window allowing a user to define a configurable data object such as a specification.

[0053] FIG. 7A is a flowchart of programmably linked browser display pages which illustrates the collaboration system used in the system of the present invention.

[0054] FIG. 7B is a depiction of an exemplary Message Center screen used in conjunction with the collaboration process.

[0055] FIG. 8 is a flowchart of programmably linked browser pages illustrating a project set up used in the system of the present invention.

[0056] FIG. 9A is a flowchart of programmably linked browser pages illustrating the creation of a virtual area in accordance with the system of the present invention.

[0057] FIG. 9B is a graphical depiction of a virtual area.

[0058] FIG. 9C illustrates a specification list.

[0059] FIG. 10 is a flowchart illustrating the interaction of various system tools and how such tools modify data in the database to manage an asset in accordance with the present invention.

[0060] FIG. 11 is a flowchart illustrating the lifecycle of an Item Specification in the system of the present invention.

[0061] FIG. 12 is a flowchart illustrating the process of specifying an item in accordance with the Item Specification Wizard tool used in the system of the present invention.

[0062] FIGS. 13A-13M are screen shots of page types used in the process shown in FIG. 12.

[0063] FIG. 14 is a flowchart illustrating an request for quotation process flow in accordance with the system of the present invention.

[0064] FIG. 15 is a flowchart illustrating a RFQ response process flow in accordance with the system of the present invention.

[0065] FIG. 16 is a flowchart illustrating an RFQ review process flow in accordance with the system of the present invention.

[0066] FIG. 17 is a flowchart illustrating a Bid Request Wizard process flow in accordance with the system of the present invention.

[0067] FIG. 18 is a flowchart illustrating a Bid Response Wizard process flow in accordance with the system of the present invention.

[0068] FIG. 19 is a flowchart illustrating a Bid Review Wizard process flow in accordance with the system of the present invention.

[0069] FIG. 20 is a flowchart illustrating a Purchase Order process flow in accordance with the system of the present invention.

[0070] FIG. 21 is a screenshot illustrating a purchase order process page in accordance with the system of the present invention.

[0071] FIG. 22 is a flowchart illustrating a shipping process flow in accordance with the system of the present invention.

DETAILED DESCRIPTION

[0072] The system described herein presents a complete design--build--management solution to the tasks involved in overseeing and managing construction, manufacturing, and maintaining assets such as buildings, ships, airplanes and the like. In one aspect, the system an enterprise system, Application Service Providers (ASP) platform, and open architecture system which provides application toolsets that allow multiple participants in projects, automation of bidding and estimating processes, accuracy and efficiency in purchasing, integration with existing applications, and simple but secure access over the Internet or a private network. The system captures and manages information throughout the design, build, and manage phases of the resulting asset.

[0073] In a further unique feature of the invention, all data is available in real-time providing consistent information throughout a project's lifecycle. Even after an asset has been built, an owner or property manager can access the system to derive specific information within a few seconds. This system can be applied to any number of design and build industries, including: Hospitality, Civil and Electrical Infrastructure; Telecom; Commercial, Residential, and Government Buildings; Manufacturing; Aerospace and Nautical applications; and Automobile, Railways, and Public Transportation projects.

[0074] The system provides a single, logical solution to gathering and manipulating information concerning assets. In performing this function, the system provides an efficiency of cost not heretofore known in prior art systems. Design data is stored and manipulated by the system throughout construction/manufacturing and, later, the management process for any type of asset. While the system will be described herein with respect to construction of a building, it will be readily recognized that the system is applicable to any type of asset. The system allows management of the designing and construction from beginning to end, and information is gathered and updated from multiple sources throughout the project. The system is also flexible enough to accommodate many different types of businesses and projects.

[0075] The system provides this solution to users in real time, so that all information modified by users is instantly available to other users in the system, creating even greater efficiency.

[0076] The following terms will be used throughout the specification and are defined as follows:

[0077] Attribute: A quality of characteristic inherent in or ascribed to an item specification.

[0078] Business Object: An article used in the conducting of business, such as a schedule of items, a letter, an email, a purchase order, a request for quotation, and the like.

[0079] CAD: Acronym for "Computer-aided design." Computer-aided design software is used by architects, engineers, drafters, artists and others to create precision drawings or technical illustrations. CAD software can be used to create two-dimensional (2-D) drawings or three-dimensional (3-D) models.

[0080] Classification: The system of the present invention recognizes classifications as a category or class of item types. The classification tree displays the classes in a hierarchal fashion.

[0081] Company: An organization or group that performs services or provides products within the system. A business enterprise; a firm. Individual company defaults and standards revolve around a company.

[0082] Company Administrator: The first user for any company. This user is responsible for setting up licensing, company information, company defaults, users, vendors, and so forth.

[0083] Component: The system supports components as a part of an Item Specification. A component is an existing Item Specification associated to another item specification; together, they make up a whole item or an assembly. An Item Specification can have multiple components.

[0084] Document Set: A special type of folder in the Collaboration tool. A document set allows a user to group together any number of files into a common set. The actual files are stored in separate folders organized in whatever manner suits the user. The contents of the document set folder are merely shortcuts, or pointers, to the actual files. Only one copy of any given file needs to be maintained.

[0085] Item Specification: The detail information about objects involved in building the parts and components of something. An example of an item would be a desk; an example of the item specification would be the description of the desk (height, width, depth, color, material, and so forth), its manufacturer(s), costs, delivery options, catalog numbers, and so forth.

[0086] Item Type: A template for creating item specifications for broad categories of items. For example: a user might have an item type of "office furniture," this item type forms a template a user would use to create the many item specifications for various desks required.

[0087] Project : A plan or proposal; a scheme or undertaking requiring concerted effort. The system of the present invention allows any plan with more than one task to be considered as a project.

[0088] Project Partners: Project Partners can include suppliers, vendors, contractors, designers, and consultants who have different levels of access to specifications and receive information about, and respond to information on, the Property or Project.

[0089] Property: The base organizational point for the activities of a Company within the present system. The property is the larges hierarchal space in one or more virtual areas. The "Property" label may be customized using the Nomenclature options in Company Defaults.

[0090] Qualification: The Qualification process is the act of ensuring that a company is suitable to perform work or provide materials for a specific project. The system provides the ability to qualify vendors and/or services before bidding and purchasing. Qualification is an information gathering process that can be used for screening purposes.

[0091] Schedule: A schedule is a list of specified items, a reference number, a version number and the item status information. The system provides the ability to generate schedules, either by type or instance, for the entire project or specific virtual areas.

[0092] The foregoing terminology is used herein for convenience in understanding the present invention. It should be understood that the aforementioned definitions are not intended as limiting the scope of the present invention to the particular terms which are defined. Other nomenclature may be used to represent the concepts and substance of the foregoing definitions.

SYSTEM OVERVIEW

[0093] FIG. 3A is an overview of the system 1000 of the present invention. As shown therein, the system includes an application server providing application toolsets to one or more client computers. The server and computers are coupled by a network, which may be a public network, a private network, or a combination of public and private networks such as the Internet. The toolsets are designed to facilitate the project creation and management by manipulating data describing basic elements of the project stored in at least one database on the application server or a separate database server. FIG. 3A shows the six general types of application toolsets accessible by a client device. Each of the applications support project data entry and modification, while two are support system management and utilities. The specific functions of each of these groups of applications are set forth below.

[0094] Each client device may comprise a personal computer, a thin client or any other type of processing device capable of supporting applications described herein, and the system may be accessed by different types of client devices--such devices need not be personal computers but do need to support the applications provided in the applications toolsets. Applications server 1020 also includes at last one database for property item data managed by the system of the present invention. In FIG. 3A, the databases are organized by property, but such organization is exemplary and not meant as limiting on the system of the present invention. Organization of the databases into one or more other data structures or classifications is contemplated as being within the scope of the present invention.

[0095] The application toolsets provided in the system include: a Design Toolset 1100, a Procurement Toolset, a Cost Management Toolset, and a Project Teamwork Toolset. In the following description, although the aforementioned tool sets comprise one embodiment of the present invention, it should be understood that additional tool sets may be provided without departing from the scope of the invention.

[0096] The Design Toolset allows users of the system to input into the system 1000. The Procurement Toolset 1200 includes a Bid/RFQ tool and a Purchase tool. The Cost Management Toolset 1400 provides an Cost Estimate tool, Budgeting tool, a Contract tool, a Payment tool, and an Invoicing tool. Finally, a Project Teamwork Toolset 1600 includes a Collaboration Tool, a Request for Information tool and Meeting Minutes tool. Two other sets of applications are provided--an administration tool set 1300 and a utilities tool set 1400.

[0097] The system will be described herein in the context of its implementation in an Application Service Provider (ASP) model. As used herein, the ASP model includes providing applications from an application server including databases organized by project or property to a client computer. In this context, an ASP is used to refer to an application server providing applications to a client device, as opposed to those applications which are installed in non-volatile memory on the client device. In one embodiment, the application toolsets may be implemented as a set of applications configured to run in another interpretive application, such as in Internet Browser.

[0098] The application server 1020 is a server program in a computer in a distributed network that provides the business logic for an application program run on the client computer 1050. The application server 1020 may comprise a portion of the system which may further include a graphical user interface (GUI) server, an application (business logic) server, and a database and transaction server. In one embodiment, the application server combines or works with a Web (Hypertext Transfer Protocol) server and is called a Web application server. The Web server provides several different ways to forward a request to an application server and to forward back a modified or new Web page to the user. These approaches include the Common Gateway Interface (CGI), FastCGI, Microsoft's Active Server Page, and the Java Server Page. In some cases, the Web application servers also support request "brokering" interfaces such as CORBA Internet Inter-ORB Protocol (IIOP), and Enterprise Java Beans.

[0099] In general, a request, such as an HTTP request, from the client device is made to the application server via the network. If the request is for a particular application, the application will be transmitted to the client, loaded and run by the client by presenting a graphical input/output page to a user.

[0100] The system is configured to have a "Home Page" and "Project Page" for each user. Representations of exemplary pages are shown in FIGS. 3B and 3C. The project page may be customized to provide any number of the tools, or a subset of the available tools, to the user depending on the permissions granted to the user by the Company Administrator. The project page will contain links to the applications which are accessible to the user, and the data supplying those applications and the applications themselves are provided by the applications server. In addition, security level access to the data is controlled by the application server.

[0101] In general, design data is created in the database by the design toolset applications, but such data can be further supplemented and/or modified by nearly all other components of the system. An object linking application links design drawings (created in a CAD system or specification builder) to specification data that describes the "real world" object. The result is an "intelligent object." When actions (budgeting, purchasing, delivering, maintenance scheduling) occur to that object, by any system user, the "intelligence" of the object is updated with this information.

[0102] An example of the data which may be used in the system of the present invention is set forth in co-pending U.S. patent application Ser. No. ______ filed ______ entitled INTELLIGENT OBJECT BUILDER (TRIG8851) by Thomas A. Wucherer, M. Cherisse Nicastro, Anthony A. Marnell II and Anthony A. Marnell III (hereby fully incorporated by reference herein).

[0103] The data may be stored in a database in any of a number of object, relational or distributed database structures. In one embodiment, the data is organized in a series of name value pairs and relationship tables accessible via XML or SQL. In another embodiment, the data is provided in a relational database with each object represented by a single row of generic columns of attribute data, along with an attribute definition row. In yet another embodiment, the data is organized into object classes and subclasses in an object database.

[0104] In accordance with the invention, the Application server may be supplied by a System Administrator. The Administrator may host the applications databases, and provide assistance to users of the system at all levels in using the application. In this embodiment, the system administrator enables the application server for internet access such that the client computers may be positioned at remote sites, such as the physical location of each of the members of the design team, purchasers, contractors and the like, allowing all users to communicate data to the application server via a secure protocol. The administrator may offer access to the application server, store data and customer service as a service for which the System Administrator collects a fee. Types of fees charged by the System Administrator are described herein.

[0105] In understanding the comprehensiveness of the system of the present invention, it is helpful to understand how conventional data flows in a project. FIG. 4 shows an example data flow for an item through several stages of an item's lifecycle in a construction project of a building. A project participant 312 originally provides a budget 330 for the project. From the budget 330, different project participants produce specifications such as specification 332 for items to be purchased. The purchasing department 316 optionally may produce a bid package 334 from the specification to obtain bids for an item to be purchased. Subcontractors and vendors, among others, such as subcontractor 314, submit bid responses such as bid response 336 to the purchasing department 316. Purchasing department 316 decides to which subcontractor or vendor a contract 337 or purchase order to provide the item should be awarded. Contract 337 is communicated to project accountant 310 and project manager 320. Each of project account 310 and project manager 320
may use respective computer system(s) (not shown) for managing different types of data associated with an item.

[0106] Upon awarding contract 337 or directly upon receiving specification 332, purchasing department 316 may produce a purchase order 338 or contract for ordering the item from a seller 318. The vendor 318 sends the item 340 to the receiving department 322 and an invoice 342 to project accountant 310. Receiving department 322 sends a receiving list 344 to project accountant 310 and project manager 320. Receiving department 322 also places item 340 in storage. Storage manager 324
optionally sends item 340 to a warehouse and provides location data 348
to the project manager 320. From the warehouse, warehouse manager 326
distributes item 340 to the construction site and provides location data 348 to the project manager 320. Location data 348 regarding the current location of item 324 is provided by warehouse manager 326 to project manager 320. Alternatively, storage manager 324 may send item 340
directly to the construction site and provide current location data 348
to project manager 320. Project superintendent 328 then places the item in the appropriate location within the project.

[0107] The stages of the lifecycle depicted in FIG. 4 include only those stages through the delivery of the item to the site and payment for the item. An item has a life beyond the stages depicted; for example, after being delivered to the site, the item is placed into a location within the project and often used for many years. The scope of the invention includes managing these maintenance stages of the lifecycle of the item. The stages shown in FIG. 4 are one example and used for illustration purposes only.

[0108] As shown in FIG. 4, many types of data flow to many project participants during the lifecycle of an item used in a project. The term "item data" is used herein to describe collectively these many types of data associated with the lifecycle of the item. Each of the project participants may use one or more application programs to track the different types of item data that he or she receives and/or generates. Often project participants use application programs that are not used by other project participants, so that data is sent via paper from one project participant to another. In such a paper-based system, each project participant manually enters the data into one or more respective application programs.

[0109] Item data are described herein as objects of an object-oriented framework, although the scope of the invention includes other organizations of item data. For those unfamiliar with object-oriented frameworks, a brief summary is presented here. The building block of an object-oriented framework is an object. An object is defined through its state and behavior. The state of an object is set forth via attributes of the object, which are included as data fields in the object. The behavior of the object is set forth by methods of the object. Each object is an instance of a class, which provides a template for the object. A class defines zero or more data fields to store attributes of an object and zero or more methods.

[0110] Each data field contains attribute information defining a portion of the state of an object. Objects that are instances of the same class have the same data fields, but the particular attribute values contained within the data fields may vary from object to object. Each data field can contain information that is direct, such as an integer value, or indirect, such as a reference or pointer to another object.

[0111] Design System Toolset

[0112] The Design system tools include a CAD intelligence plug-in, specification tool and a schedule tool. Each of these tools provide project designers with the ability to enter data into the system in a manner which the designer would be normally accustomed to.

[0113] CAD Intelligence Plug-in

[0114] The CAD Intelligence plug-in adds functionality to AutoCAD or MicroStation/J or other computer aided design software. It can connect to the application server database, select item specifications, assign those specifications to drawn items in the CAD drawing, assign the drawing to a virtual area in the project and upload the "intelligent objects" in the drawing to the database. The CAD Intelligence plug-in is available for download to a local PC from a designated home Page. Once installed, the plug-in automatically updates itself as necessary when the System Administrator updates the functionality or design of the plug-in.

[0115] The CAD Intelligence plug-in adds a menu and/or toolbar to an existing CAD application. Its main function is to connect drawing objects with detailed specifications associated to the project. The architect or engineer can also create new specifications while drawing. From within CAD Intelligence, a user can: login to the system database, add data fields to the cells/elements in a drawing (making them "intelligent"), associate drawing elements to an area, associate drawing elements to an item specification in the database, edit and view the attributes of intelligent elements, associate a mark in the drawing to an item specification, generate marks for the entire drawing and upload intelligent elements from a CAD drawing to the database. The CAD intelligence plug-in such as that described in co-pending U.S. patent application Ser. No. ______ filed ______ entitled INTELLIGENT OBJECT BUILDER by Nicastro, Wucherer, Nisbet, Marnell II, Marnell III (hereby fully incorporated by reference herein) is suitable for use in the present system.

[0116] Item Specification Tool

[0117] The Item Specification Tool is an independent application for creating intelligent objects without using a CAD system. The Specification Tool is fully described in co-pending application Ser. No. ______. Item Types are templates for creating item specifications for broad categories of items. The use of Item Types enables a user to display all the item types for a selected classification. The system recognizes classifications as a category or class of disciplines and trades. The classification tree displays disciplines and trades in a hierarchal fashion. Classifications are used to organize item types and control access to them. This function allows a user to open and display all details of a selected item type. The manager also allows a user to copy the attributes of a selected item type to create a new item type with the ability to edit the existing attributes. This process also provides the ability to delete an existing item type that has not yet been used to define an item specification. A user may create a new item type for a selected classification by accessing the Item Type Wizard.

[0118] FIG. 5 shows an example of the item specification as a configurable data object. Three items are shown, including a chair 510, a drapery 520
and a fabric 530. Specifications 512, 522 and 532 are associated with the three items. Fabric 530 is a sub-item of chair 510 and has its own specification 532. The drapery is made from the same fabric as the chair and fabric 530 is also a sub-item of drapery 520. All of these items are specified as part of the guest room furnishings group for the Palazzo Suites area of the project.

[0119] While each of the specifications 512, 522 and 532 provides a specification for an item, each has different attributes. For example, the specification object 512 for chair 510 has a finish attribute, which in the example shown has a value of "dark cherry." In contrast, specification object 522 for drapery 520 has a style attribute with a value of "Roman blinds" and specification object 532 for fabric 530 has a color attribute with a value of "red." The ability of different specifications to have different attributes provides great flexibility to a user of the item data integration system 400. Standard specifications can be defined when information is to be tracked for many items of a particular type, but a new specification can be defined whenever additional information is needed for an item. Item data integration system 400 performs operations on all specifications in the same way even though specifications for different types of items are defined differently.

[0120] FIG. 6 is an example of a configuration window that allows a user to define a configurable data object such as a specification. Data field Group field 610 allows the user to choose a group into which the configurable data object will be placed. Select Object button 612 allows the user to select an item object with which the configurable data object is associated. For example, the user may link a specification to a graphical object in the architectural drawing or to another item object. Space field 620 allows the user to indicate the space, or location, to which the configurable data object pertains and Select Space button 622
allows the user to select a location in the construction project where the item will be placed. Mark field 630 allows the user to specify a mark and Place Mark button 632 allows the user to place the mark on a graphical drawing.

[0121] Spec field 640 allows the user to select an existing specification for the item and New Spec button 642 allows the user to create a new specification. Apply button 644 allows the user to link a configurable data object with an item object, Reset button 647 allows the user to reset fields of the configurable data object to default values, and Details button 648 allows the user to view the details of the configurable data object as shown in windows 650, 660 and 690. When apply button 644 is used to link a configurable data object with an item object, a relationship between the configurable data object and the item object is created. In one embodiment of the invention, an integrated data object containing pointers to the configurable data object and the item object is created.

[0122] New Spec button 642 will bring up windows such as windows 650, 660, and 690 and buttons such as buttons 662 through 669. For a new configurable data object, the attributes list shown in Attributes tab 670
is empty and the user can define attributes using Add Attributes button 692. Numeric attributes would have Unit of Measure buttons such as buttons 673, 675 and 677.

[0123] Status area field 650 shows a status of the configurable data object. Window 660 shows a hierarchy in which the configurable data object resides. The user would highlight the level of the hierarchy into which the new configurable data object should be placed.

[0124] In the example of FIG. 6, the user has selected a specification configurable data object and may use one of the buttons 662 through 669
to modify the specification. Add SubSpec button 662 allows the user to add a sub-specification to the specification and Add Instance button 664
allows the user to add a new instance of the specification (an item associated with the specification). Remove button 666 allows the user to delete a specification, Edit Instance button 668 allows the user to edit an instance of the specification (an item), and Edit Spec button 669
allows the user to edit the existing specification.

[0125] The user has selected an existing specification so that fields are shown in the Attributes tab 670 of the specification. Height data field 672, width data field 674, depth data field 676 have associated unit of measure buttons 673, 675, and 677, respectively. Finish data field 677, fire rating data field 678 and other data field 679 are non-numeric fields for character data. The user may add a new attribute to the specification using Add Attribute button 692 and remove an attribute using Remove Attribute button 694. The user may specify status information using Status tab 680, quantity information using Quantities tab 682, and cost information using Cost tab 684. Each of these tabs has its own corresponding data fields that the user may define and/or from which the user may select.

[0126] An Item Type Wizard may be provided to define the general properties of the item type, including the type of attributes and components that will need to be specified in the item specification. Attributes are characteristics of the item type that are necessary to define the item specification. Components link item(s) required for the assembly or completion of a particular item specification. The system supports components as a part of an item specification. A component is an existing item specification associated to a new item specification that makeup a whole item.

[0127] For example, a door may require hardware, such as hinges, for completion. The hinge item type is a component of the door item type. Existing item types can be located through a search feature and added as components. This tool allows the user to create rules for the item type that define how a waste factor is calculated for the item, which CAD mark is associated with the item type, whether component cost should be calculated as an associated cost or rolled up into the cost of the original item, and so forth. The preferences defined apply to all item specifications that are created with this item type.

[0128] Additional functions which may be added to the item type include but are not limited to the following: definition of reporting preferences including the selection of layout per attribute and specification data type; definition of a purchasing plug-in's ability to modify the requirements of a specification; etc.

[0129] Item Specification Manager

[0130] Item Specifications contain detail information about objects within a physical space. An example of an item would be a desk; the item specification for the desk would include descriptions of its height, width, depth, color, material, manufacturer(s), costs, delivery options, catalog numbers, and so forth. Item Specifications are a central feature of system 1000. They are used in several Tools such as Purchasing, Bids, RFQs, Publishing, and Schedules.

[0131] The Item Specification Manager enables a user to display all the item specifications for a selected classification and item type. A general outline of the functions of the Item Specification Manager are shown in FIG. 4. This function allows a user to open and display all details of a selected item specification. The manager also allows a user to copy the attributes of a selected item specification to create a new item and provides the ability to edit the existing attributes. This process also provides the ability to delete an existing item specification that has not yet been published. A user may create a new item specification for a selected classification by accessing the Item Specification Wizard. The Item Specification Wizard is explained with respect to FIG. 12 and in co-pending U.S. application Ser. No. entitled Item Data Management System (TRIRG-01001US0).

[0132] Item Specification Wizard

[0133] The Item Specification Wizard enables a user to assign general properties to the item specification, such as: item specification number, name, physical classification, and item type. After a user has created the item specification, the user can define other general properties such as the base cost and budget code. A user may also define which users for this property can view the item.

[0134] Additional functions which may be added to the item costs page include but are not limited to the following: definition billing data from the specifier to their customer; designed quantities for areas to be used in conjunction with the multiplier to assist in defining a specified quantity and cost for an area; etc.

[0135] The Item Specification Wizard allows a user to define specific attributes and associate available components relating to the item specification. Components link item(s) required for the assembly or completion of a particular item specification. This tool also enables a user to provide a vendor with written notes about the item specification, such as delivery requirements, special instructions, vendor terms or any other information that needs to be communicated to the vendor. This feature also enables a user to preview the item specification information and prepare a report for printing. This Item Specification Wizard also provides the ability to calculate the total estimated cost, including component items, automatically. Costs are used for budgeting, bidding, and purchasing items. A history of the item specification is tracked by system 1000 to allow users the capability to view the historical status and specification changes for the item specification and its components over time, or view previous versions of the item specification. It should be further recognized that item specifications need not only be linked to other item specifications, but may also be linked to business objects which do not include item specifications. For example, a Request for Information may simply comprise an email asking a question without reference to an item specification. This object may be linked to other item specifications.

[0136] Additional functions which may be added to the item specification include but are not limited to the following: definition of critical time frames for completing tasks relating to the item specifications; documentation of warranty and maintenance requirements of an item; link of an item to a real-time building automation system's status of that item; etc.

[0137] Schedule Tool

[0138] A Schedule is a list of specified items, a reference number, a version number and the item status information. System 1000 provides the ability to schedule item specifications either by type or instance for the entire project or specific virtual areas. A user can create custom schedules for specific items, such as doors, fixtures or finishes. The schedule can then be used as are porting tool and report item specifications based on their classification and associated virtual area.

[0139] Item Spec Schedule Builder

[0140] A schedule builder tool is provided to allow users to create two different types of item specification schedules (a list in tabular form). The Schedule Builder tool enables a user to schedule each instance in which the item specification occurs throughout the entire project and allows a user to define an instance schedule report. The Schedule Builder tool also enables a user to create reports based on item specifications and virtual area. It reports the quantities of item specifications in this project and allows a user to define an item schedule report.

[0141] Additional functions which may be added to the item schedule tool include but are not limited to the following: item schedule editor which allows project participant to edit specification in a the schedule grid; links to publishing tool including selection of a publications purpose which may defines whether or not the items are ready for purchase; exporting of schedule to other interfaces such as a CAD tool; etc.

[0142] Item Spec Schedule Report Tool

[0143] A Schedule Report tool is provided to allow a user to run existing instance or item schedules for a specific virtual area or the entire property. These reports display on screen, an output of computer 1050, such as a display, and allow a user to print each schedule or save the schedule locally in a common format, such as Microsoft Corporation's Excel.RTM. spreadsheet program.

[0144] Publish Tool

[0145] A publishing tool allows the item specification to be published and allows the system to track any and all changes by renumbering each published version of an item specification. Publishing an official version of the items specification provides one form of version control. In one embodiment, the system prevents users from altering any information for that item specification without creating a new revision. Revisions are particular form or variation of an earlier or original item. System 1000 maintains a numerical format of versions for tracking history. Publishing also allows a user to create an Item Specification Book. A unique feature of the online Item Specification Book is the ability for it to be shared as different media. The Item Specification Book may be viewed online, printed, or saved to the user's personal computer or laptop for later use.

[0146] Additional functions which may be added to the publish tool include but are not limited to the following: selection of a publications purpose which may define whether or not the items are ready for purchase; routing of the publication for approval; selection of specific project participants to publish the items to; etc.

[0147] Cost Management Tool Set

[0148] The Cost Management Tools offer a comprehensive electronic process to monitor, manage and control cost from a central location, track and forecast all estimates, costs, commitments, revenue, transactional events, and associated project information from the design to the construction and management of the resulting asset.

[0149] Estimate Tool

[0150] The Estimate Tool enables a user to create a detailed budget estimate for a project. A user can import a classification list, virtual area structure, or specification book as the basis of the estimate. This tool imports transaction information and data structure into the Budget Tool to create a budget for the project. An estimate can be imported into the budget as the baseline, or preliminary budget. The individual items imported become rows in the estimate table. Each estimate has a unique name and description, and is assigned a unique ID number by the system. This advantage allows a user to quickly track and identify each estimate and transfer the values into the budget in a logical format. All calculations and data manipulations occur locally and are not shared until a user chooses to save the data to the database 1025. An Estimate Wizard is provided in a manner which resembles spreadsheets such as Microsoft.RTM. Excel or Lotus 123.RTM.. Default columns calculate the values automatically and maintain a running total for the entire estimate. The Estimate Wizard allows a user to customize an estimate in order to suit the methods in which a company conducts business. A user can enter estimate values and add any additional columns to suit particular business needs. A user can group rows and subtotal within a user-defined hierarchy. The estimate can be sorted by any of the columns. User-defined formulas can be entered into fields and columns. Columns can be hidden from view at any time.

[0151] Additional functions which may be added to the estimate include but are not limited to the following: consolidation of sub-bid responses for submittal of an overall bid response; enterprise cost planning across multiple projects; etc.

[0152] Budget Tool

[0153] The Budget Tool provides the ability to track and display all cost related transactions within the system 1000 on a project-by-project basis. The budget transactions are managed and stored as a consecutive set of events, with associated values and sources. All cost related items within the system allow the allocation of a budget code and the application of the cost related information to be accumulated as transactions. The Budget Tool uses budget codes that can be defined at either the Company or Project level. The requirements or structure of a budget code number can be defined by the user. Budget codes can be tied to item specifications in the Item Specification Tool. This tool generates budget entries automatically from a number of system 1000
processes, such as purchase orders. These system-generated budget entries are created when the appropriate user in the purchase order approval chain approves a given purchase order. Manual entry is allowed for the following transaction types: original budget entry, revised budget entry, pending budget entry, commitment entry, revised commitment entry, pending commitment entry, actual cost entry, committed revenue entry, pending revenue entry, and revenue entry. A user can also create an "estimate to complete" entry and transfer funds from one budget code to another.

[0154] The Budget Tool allows a user to customize the budget by hiding or viewing columns as needed, as well as sorting by any column heading. The display follows a familiar rows and columns format, similar to that of a spreadsheet. One advantage of this tool is the ability to generate totals and subtotals for budget entries automatically, based upon a user-defined budget structure. The tool allows the appropriate users to access any value and display the detailed history for that transaction. The Budget report may be printed to a local or network printer and allows a user to export to common file formats. This tool allows a user to lock the budget to prevent further changes to the original. After locking the budget, transactions apply to the corresponding revised columns only.

[0155] Additional functions which may be added to the budget include but are not limited to the following: enterprise-wide budget control and spending constraints across multiple projects; etc.

[0156] Contract Tool

[0157] A contract is a legal agreement between the buyer and the vendor defining a scope of work. A contract may contain billing, terms, items, cost, shipping, terms and conditions, notes, and payment information. The contract tool can generate a contract as a standalone process or can be initiated automatically from the Bid processes; the Bid process feeds into Contracts. The Contract tool may automate a collection of the boilerplate legal text and other variables, such as name of the buyer, the name of the vendor, the items to be built or delivered, the terms of the contract, the costs of the items, the conditions of payment, and so forth, into a single electronic document.

[0158] Change Orders to contracts are also legal agreements between the buyer and the vendor detailing the change to a scope of work. Change events leading to change orders such as revisions to item specifications, requests for information, etc. may be consolidated to create a change order to a contract.

[0159] Application for Payment Tool

[0160] The Application For Payment Tool generates payment request documentation. The contract's schedule of values provides the line item details of the application for payment, ensuring consistent data entry. The user can link and include change orders for timely billing and payment processing. It links application requests to the Budget Tool for accurate cost and revenue management and reporting.

[0161] Invoice Tool

[0162] The Invoice Tool generates and submits an online invoice to initiate the payment process and notify users of current requests. The tool set provides tracking and management capabilities. The purchase order provides the line item detail for the invoice, ensuring consistent data entry. The user can link and include change orders for timely billing and payment processing. This tool also links invoices to the Budget Tool for accurate cost and revenue management and reporting.

[0163] Procurement Toolset

[0164] The system Procurement Solution offers a complete and centralized electronic process to organize, send, receive and analyze procurement documents and processes. Users in the supply chain can define procurement needs, review and award bids, issue and track contracts and purchase orders, and track the procured goods and services utilizing real-time project information all through one system 1000. The Procurement Tools automate bidding, purchasing, shipping and receiving, while facilitating process efficiencies.

[0165] Bidding Tool

[0166] A bid is a formal request sent to vendors requesting that they review the project requirements and submit responses indicating how much they would charge to work on the project or supply materials. The Bidding Tool is composed of the following functions: Qualifications (including the Qualification Request Wizard, the Qualification Response Wizard, and the Qualification Review Wizard), Bids (including the Bid Package Wizard, the Bid Response Wizard, and the Bid Review Wizard), and Request for Quote (including the RFQS Request Wizard, the RFQ Response Wizard, and the RFQ Review Wizard).

[0167] A detailed description of the Bidding and RFQ tools is provided below. As will be understood from these descriptions, the Qualification toolset--Request, Response and Review--operates in a similar manner.

[0168] Additional functions which may be added to the bidding and RFQ tools include but are not limited to the following: consolidation of sub-bid responses linked via an estimate for submittal of an overall bid response; enterprise-wide bidding consolidating procurement across multiple projects; etc.

[0169] Qualification

[0170] The Qualification process is the act of ensuring that a company is suitable to perform work or provide materials for your project. The system of the present invention provides the ability to qualify vendors and/or services before bidding and purchasing. Qualification is an information gathering process that can be used for screening purposes. Before sending out bids, a user can qualify vendors to ensure they have the credentials required to perform the work in the bidding process, saving both time and money y. Credentials are evidence or testimonials concerning right to credit, confidence, or authority. When a user sends out the bid, one of the options is to send the bid only to pre-qualified vendors.

[0171] Qualification Request Wizard

[0172] A Qualification Request is a request that is sent to prospective bidders to determine their qualifications prior to entering the bid process. The Qualification Request Wizard allows a user to create and issue qualification requests to prospective vendors. This wizard allows a user to indicate the type of credentials a user wants the vendors to provide for this qualification as well as create a user's own questions for vendors to answer, including attached reference documents, if desired. A unique advantage to this process allows a user to select which vendors will receive the qualification request from either the customized company vendor list or the entire database of available vendors. Optionally, the list of vendors can be published, so that each vendor sees who else was included in this qualification, or this information may remain private. Once the Qualification Request is complete it may be published with the attachments, questions, and comments. Vendors have the option of accepting the qualification request and providing the requested information, or declining the request within the designated time frame.

[0173] Qualification Response Wizard

[0174] A Qualification Response Wizard allows vendors to provide a response to the credentials, requirements and questions contained in the qualification. The Qualification Response Wizard displays a summary of the credentials and requirements the vendor must supply and any questions the vendor has to answer. This process then allows the vendor to send the completed qualification response back to the original requestor electronically.

[0175] Qualification Review Wizard

[0176] A Qualification Review Wizard allows the originator of the request to review and compare the qualification responses, and select the qualified vendors. This step in the process displays the qualification request description, vendor list, requirements the vendors are required to match and questions the vendors are required to answer. One advantage to this process is the unique ability to allow the originator of the request to view the credentials and the answers to questions for all bidders as a side-by-side comparison. This process allows the originator to then identify selected vendors as being qualified, based on the comparison.

[0177] Bid Package Wizard

[0178] The Bid Package Wizard is a step by step process that assists in the creation of a bid request. Often bidders source materials or request bids from sub-contractors to create their response to a particular bid request. The Bid Package Wizard has a feature to import items from another bid request, which one can then edit and incorporate into their bid requests. This is a shortcut way of entering the sub-bid items without having to re-enter them manually.

[0179] Each bid can have attached drawings, specification documents, item specifications (from the Item Specification Tool), and file attachments. Some advantages to using the Bid Package Wizard include the ability to provide bidders with special instructions, schedule meetings for bidders to attend, and import a list of existing item specifications or manually create a bill of materials forth bid package. A benefit to using this wizard is the ability to create one or more alternative options for the bid; each alternate has its own set of drawings, specifications, item lists and attachments.

[0180] An advantage that saves time and effort is the ability to select bidders manually, or automatically include previously qualified vendors from a Qualification Request. A company can choose to publish its vendor list to allow bidders to know who else has received the bid package.

[0181] When the bid is issued to prospective bidders, it contains the issue date, due date, and anticipated award date. This process even allows changes to be made to an issued bid by creating an addendum in the Bid Review Wizard. An addendum is document describing an addition, change, correction, or modification to contract documents. An addendum is issued by a the author of the bid package during the bidding period or prior to the award of contract, and is the primary method of informing bidders of modifications to the work during the bidding process. Addenda become part of the contract documents.

[0182] The bidders can either decline to participate or they can accept. If they accept, they review the materials attached to the bid and prepare a response.

[0183] Bid Response Wizard

[0184] A bid is a complete and duly signed proposal to perform work (or a designated portion thereof) for a stipulated sum. A bid is submitted in accordance with the bidding documents. The Bid Response Wizard is the mechanism through which bidders respond to the bid package. This wizard parallels the Bid Package Wizard. Any information specified in the Bid Package Wizard can be viewed by the bidder in the Response Wizard.

[0185] The bidder can view drawings, specification documents, attachments, and item specifications, as well as any alternates. The list of bidders is not available unless the company has chosen to publish the vendor list.

[0186] The Bid Response Wizard allows the bidders to enter a response for each breakdown on the bid package and review the addenda for each bid. The review includes descriptions, drawings, specifications, items list, attachments, alternates and cost from any previous addenda and the original bid.

[0187] This wizard allows the bidders to generate requests for information (RFI) messages. These are messages to various users that request some type of information a vendor feels is necessary in order to respond to the bid. This feature also displays any RFIs that need to be answered.

[0188] Bid Review Wizard

[0189] The Bid Review Wizard allows a user to review bid responses, including the description, drawings, specifications, item list and attachments from the Bid Response Wizard.

[0190] This review process allows a user to issue an addendum to make changes to the original bid package. An addendum can specify the same attributes as the original bid: for example, drawings, specifications, item lists, attachments, cost forms and so forth.

[0191] Just as the bidders may issue an RFI, the same ability is provided to the reviewer in order to respond to the bidder or gather more information.

[0192] The advantage to using this wizard is the ability to view the bidders' responses side-by-side to facilitate comparisons and award the bid from the comparison screen. This review can be used to compare the Quantity, Unit Cost, Units, Labor Rate, Hours, or Lump sum breakdowns between vendors for any specific bid/RFQ item.

[0193] Request for Quotation

[0194] Request for Quotation (RFQ) is a simplified Bid Package. A similar process of issuing the request, communicating with bidders, and reviewing responses is followed. For RFQs, a user has the option of simply awarding the RFQ, or awarding and automatically generating a purchase order.

[0195] Purchasing Tools

[0196] The Purchasing Tools provide a complete means for requesting, responding to, and reviewing purchase orders which integrates with the Procurement Tools. A user can track and management purchases electronically with project partners and vendors who are part of the system, as well as those who are not a part of the system.

[0197] Additional functions which may be added to the purchasing tools include but are not limited to the following: consolidation of requisitions into purchase orders to the appropriate vendor(s); enterprise-wide procurement across multiple projects; etc.

[0198] Purchase Order Request

[0199] The Purchasing Tool electronically creates, issues, receives and tracks the history of purchase orders (POs). Some system processes, such as Requests for Quote, can automatically generate purchase orders upon issue. The Purchasing Tool directly relates to the Shipping and Receiving functions of the Order Fulfillment Tool.

[0200] Detailed item specifications and other project related information found within system 1000 can be attached to the purchase order, according to the individual line item or as a file attachment. The unit cost, tax, and total cost are automatically calculated to allow for accurate budgeting. All of the information is sent to the vendor as an itemized list for fulfillment.

[0201] The Purchase Order Tool allows a user to select a vendor from the company's vendors list or locate a vendor in the system and indicate the Bill To and Ship To addresses for the company. A user can also identify a contact person at the vendor company to approve the order.

[0202] This process also allows a user to select stored "prefabricated" notes or comments. This saves time by not insisting that a user type a new note for every purchase order. A user can select the access level for each note; a private note can only be viewed by its creator, a company note can be viewed by anyone in the company with access to the purchase order process, and public notes are available to anyone with access to the purchase order.

[0203] The history of the purchase order displays any change orders created and the notification log, which tracks and identifies anyone who has created, changed, or modified this purchase order.

[0204] This tool provides the ability to generate Requests For Information (RFI). The request, as well as "carbon copies", can be sent to one or more users.

[0205] One of the greatest advantages is the ability to include user definable standard legal terms and conditions that are available to the vendor when they review the purchase order.

[0206] This process then allows a user to issue the purchase order to the vendor electronically if the vendor is a licensed member of the system 1000 as defined by the company administrator or a user may print the purchase order and manually contact the vendor.

[0207] Purchase Order Response

[0208] Once the licensed vendor receives the purchase order request notification, they have the opportunity to review the request in detail before committing to approving or declining the request.

[0209] The purchase order displays in a preview format providing the opportunity to print the purchase order or save the file in common format.

[0210] The history of the purchase order is available to the vendor to ensure they are reviewing the most recent version, in the event that a change order may have been issued.

[0211] The vendor also has the option of issuing an Request for Information (RFI) to the buyer, ensuring open and accurate communication between both parties.

[0212] Once the vendor has determined to accept or decline the purchase order request, the system provides the ability to attach comments regarding the decision about the purchase order.

[0213] This information is sent to the buyer with an e-mail that confirms the acceptance or decline of the purchase order request.

[0214] Purchase Order Review

[0215] Upon vendor approval, the Purchase Order Tool automatically updates the budget with the committed costs. The vendor sends notification informing the buyer of the acceptance of the purchase order request.

[0216] The review process allows a user to preview the response from the buyer, which includes the printable version, any requests for information and an updated history of events for that purchase order. In addition to all of these capabilities, a user may also change any information on this purchase order and re-issue the order. This change creates a new tracked and numbered version of the purchase order and notifies the vendor automatically.

[0217] Order Fulfillment Tool

[0218] The Order Fulfillment tool allows users to track shipping and receiving of items electronically via an Internet based interface, or via email, or via the Teamwork Toolset.

[0219] Additional functions which may be added to the order fulfillment tool include but are not limited to the following: staging and routing of items required for the project; expediting of items required for the project; inventory control and work orders; etc.

[0220] Shipping

[0221] A user can use this function to notify the buyer, via e-mail to the company contact's message center, of the items which is being shipped.

[0222] This process requires an approved purchase order that contains the items which are being prepared to ship. The Shipping Tool provides the flexibility of shipping all of the items at once or sending a partial shipment with comments to the buyer.

[0223] This process also tracks the status of purchase order items. The history log is a tracking mechanism for the shipments completed for this purchase order. The item number (item specification number), the quantity that has been shipped, and the date that shipment was recorded, appear in the history log.

[0224] Receiving

[0225] The receiving tool enables a user to electronically flag the date of the received items. This tool also allows a user to notify the vendor that the items were received at the job location. A user may use this process to access the tracking history of the items once they have been received as well as authorizing payment.

[0226] Additional functions relating to asset management which may be incorporated into the system include but are not limited to the following: bar coding of items; tracking of maintenance, replacement, and/or retirement of items including planned and actual occurrences of such events; tracking of aging and/or depreciation schedules of items; tracking of inventory and allocation of items; tracking work orders and/or requisitions for repair, replacement, and/or acquisition of items; forecasting of replacement or repair costs; forecasting of contract renewal requirements and costs; assignment of cost for use of items; and the like.

[0227] Additional functions relating to business partner management which may be incorporated into the system include but are not limited to the following: tracking of distributors, suppliers, and/or manufacturers (i.e., supply chain) of items; tracking of item assembly and components through the supply chain; links to inventory availability from supply chain; links to customer items and purchasing including revenue and/or inventory requirement forecasting; and the like.

[0228] Project Teamwork Tools

[0229] The Project Teamwork Tools offer users a complete electronic process to manage and control asset and lifecycle cost from a central point. Intelligent documentation begins in design as noted above and is compiled throughout the asset creation process. This provides a complete, integrated, referenced and searchable project record.

[0230] All specifications, drawings, documents, and costs are generated and maintained within the database ensuring that all project history and legacy data is readily available. This unique combination of tools provides an online management solution and a new dimension in continuity and efficiency for designers, builders and owners.

[0231] Collaboration Tool

[0232] The Collaboration Tool allows the members of a project team to coordinate their activities and share information. This module allows file sharing, messaging, comments, and discussions for each project.

[0233] A flowchart of the general processes available in the collaboration tool is shown in FIG. 7A. In FIG. 7A each box represents a programmably linked page or function selection from a menu item on, for example, a web page displayed in a browser.

[0234] The collaboration tool is generally access from a toolbar link 702
on a main page provided by the application server to the client computer 1050. This presents a collaboration page 704 to the user from which the user can select any number of pop-up menu commands to perform collaboration functions. The collaboration page 704 includes a collaboration tree showing uploaded files 710 that a user wishes to share with others on the project and allows a user to view 718, upload 708, download 730, discuss 760, and comment 726 on each of the files. The Collaboration Tree is composed of folders and files, similar to standard software file systems. New folders can be created as needed. The user can create new folders 712 in the tree and manipulate files within folders.

[0235] Files that are uploaded into the Collaboration Tool are accessible from several other parts of the system. The files uploaded here can be used as attachments on bids and RFQs, as pictures for item specifications and so forth. One file or multiple files can be uploaded at one time.

[0236] One unique feature of the Collaboration Tool is the ability to create document sets 714. A document set is does not contain files, but rather contains "shortcuts" or "pointers" to files another folders. Document sets can be used to collect files that relate to a given task without maintaining duplicate copies of the files. One copy of each file is stored in a folder somewhere in the Collaboration Tree, then a shortcut in a document set points to that file. Multiple shortcuts can point to any single document. This ensures that everyone can access the most updated information while only one user is maintaining the file.

[0237] Another unique feature is the available history and status 738. A user can view the current status of any file in the Collaboration Tree, including the revisions, the name of the person(s)accessing the file, and the date and time it was accessed. A file log review function is also provided 740.

[0238] The greatest advantage to this tool is the ability to share information with only specific users. The Collaboration Tree allows a user to assign access and permissions to a "Share Group" 750.

[0239] A Share Group 750 is a named set of users who can access the portions of the Collaboration Tree with a specific set of permissions. The Project Administrator defines sharing options for collaboration groups. Any user assigned to the project can be assigned to a collaboration group. A user might create a number of collaboration groups for different management purposes.

[0240] Users can perform share group searches 752 and review group lists 754, as well as create new groups 758.

[0241] The collaboration page 704 includes links to a file viewer 728 as well as a library function allowing the user to checkout 734 and check in 736 files.

[0242] An online discussion forum 760 is also provided. Users can generate on-line messages, view messages from others and reply to others' messages in a familiar on-line chat format.

[0243] Additional functions which may be added to the collaboration fulfillment tools include but are not limited to the following: document logs tracking revisions and publication of documents; document type tracking and attribute assignment; document links to virtual areas; etc.

[0244] Request for Information (RFI) Tool

[0245] A standalone, Request for Information tool is a more extensive version of the functionality available within the Bid, RFQ, and Purchase Order Tools. This is a focused tool that allows a user to create a message requesting information. The added functionality allows a user to title the RFI, request a date for a response, indicate the cost or time impact of the requestor the project and attach any files to the request. This tool also allows a user to search for and track the history of all RFIs. A graphic depiction of the collaboration process is shown in FIG. 7.

[0246] Additional functions which may be added to the RFI tool include but are not limited to the following: routing and approval of RFIs and their responses; linking of RFIs to change events; etc.

[0247] Meeting Minutes Tool

[0248] The Meeting Minutes Tool allows a user to manage, schedule, record and share meeting information. A Meeting Minutes Manager allows a user to create meetings, organize them by type, create and edit meeting minutes and schedule future meetings.

[0249] A Meeting Minutes Wizard is provided to allow a user to determine how the meeting information will be carried forward to future meetings or what previous meeting information will be included in the current meeting minutes. Once the type of the meeting is selected and the user has determined which information will carry forward into the meeting minutes, the user may set up the meeting(date, time and location), create an agenda and invite attendees to the meeting.

[0250] The meeting agenda is interactive and allows users to flag agenda items as they are addressed. The system automatically transfers any agenda items that are not addressed to the next scheduled meeting. This process serves as a reminder to cover items that may not have been covered in previous meetings and assists in organizing and completing tasks. This tool also allows a user to import information from one meeting to another in the case of recurring items or topic continuation from meeting to meeting. This feature prevents the user from re-defining any repeating information between meetings.

[0251] This tool can also be used to take meeting minutes, share the information and address action items. Action items function similar to the agenda items, but allow a user to assign individuals and completion dates to tasks. A user may create a distribution list for meeting information. Any changes to upcoming meetings, meeting minutes, attachments, or action items maybe distributed to the members involved in the meeting.

[0252] Additional functions may be added to the project management tools of which, include, but are not limited to the following: submittals for items; tasks and calendar items linked to business objects in the system; as-builts for items; and the like.

[0253] Administrative Toolset

[0254] The following functions are used in the system 1000 to manage projects.

[0255] User Licenses allows a user to use the functionality suites of the system 1000. Several licensing packages are available: Core, Design Suite, Procurement Suite, Supplier Suite and the Management Suite. Each licensing package allows a user to use specific sets of functionality for the system 1000. A user may purchase one package, a combination, or all of the packages depending on the company's needs.

[0256] The Company Administrator agrees to the system terms of service and specifies licenses for their company employees.

[0257] The Company Administrator is the first user for any company and is responsible for setting up licensing, company information, company defaults, subsequent users, vendors, and so forth. The Company Administrator does not have access toady projects or "work"; this is solely an administrative role. The licenses specified in User Licenses correspond to the Design, Cost Management, Procurement, and Manage Solutions.

[0258] A User Profile is a collection of information specifically relating to a user. This information is mainly used for contact purposes. The user profile contains information such as: Company Name, Full Name, Nickname, Employee Number, Department, Primary Function (Role), Manager's Name, Assistant's Name, Primary E-Mail, Primary Address, Business, Fax, Cell Phone Numbers and so forth. When a user accesses the system for the first time, they need to create a user profiles well as change their user name and password. Over time, any changes to name, telephone, address, position, company, and so forth, will need to be maintained using this process.

[0259] This profile information is used in the company contact processes as well as the user search process. This process assists other users in locating contact information.

[0260] Company Wizard

[0261] A Company (Setup) Wizard is provided to allow a user to create a profile for an entire company. This function also allows a user to setup specific information regarding business processes. A company is an organization, group, business enterprise or firm that performs services or provides products within the system.

[0262] This company information is stored in the database and if Company Administrator so chooses, general information will be available to other companies within system 1000.

[0263] The benefit to having a company visible to other companies in the system is the ability to generate new business for the displaying company.

[0264] Any profile information for a company will remain private and can only be u