WO2000077684A1 - Dispositif et procedes de mise au point et de gestion de l'interoperabilite logicielle et de l'integration de donnees dans des systemes d'information - Google Patents

Dispositif et procedes de mise au point et de gestion de l'interoperabilite logicielle et de l'integration de donnees dans des systemes d'information Download PDF

Info

Publication number
WO2000077684A1
WO2000077684A1 PCT/US2000/014072 US0014072W WO0077684A1 WO 2000077684 A1 WO2000077684 A1 WO 2000077684A1 US 0014072 W US0014072 W US 0014072W WO 0077684 A1 WO0077684 A1 WO 0077684A1
Authority
WO
WIPO (PCT)
Prior art keywords
instance
data
instances
database
network
Prior art date
Application number
PCT/US2000/014072
Other languages
English (en)
Other versions
WO2000077684A8 (fr
Inventor
Yee Sue Chiou
Original Assignee
Virtualstep, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Virtualstep, Inc. filed Critical Virtualstep, Inc.
Priority to AU52811/00A priority Critical patent/AU5281100A/en
Publication of WO2000077684A1 publication Critical patent/WO2000077684A1/fr
Publication of WO2000077684A8 publication Critical patent/WO2000077684A8/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database

Definitions

  • This invention relates to software inter-operability.
  • this invention relates to software inter-operability and data integration among information systems.
  • CAD Computer-aided Design Systems
  • examples of CAD systems are Autodesk AutoCAD® and Autodesk Architecture Desktop®, Autodesk, San Rafael, CA, and Bentley Microstation®, Bentley System, Exton, PA
  • Scheduling and Project Management Systems that provide project scheduling, project control and resource management
  • examples of scheduling and project management systems are Primavera Project Planner®, Primavera System, Bala Cynwyd, PA, and Microsoft Project®, Microsoft, Redmond, WA
  • Cost Estimating Systems that provide cost estimation for a project; examples of cost estimating systems are Timberline Precision Collection® and Timberline Gold Collection®, Timberline, Beaverton, OR;
  • Database Management Systems that maintain the persistence of software instances; examples of database management systems are Oracle® Database Server, Oracle, Redwood Shores, CA, Microsoft SQL Server® and Microsoft Access®, Microsoft, Redmond, WA.
  • Data manageable by a software program is generally limited to the capabilities of that software program. Data exchange among different software programs is limited and usually inflexible. Thus, it is desirable to provide apparatus and methods which are capable of extracting interrelated project data residing in different software applications and incorporate such interrelated data in a centralized database for each project. Further, it is desirable to provide access to such centralized database through a network, such as the Internet.
  • a method for processing data received across a network in multiple formats includes the steps of: (a) receiving data at a server computer from a client computer; (b) identifying a selected parser program based at least in part on the received data; (c) parsing the received data using the selected parser program to create parsed data; (d) selectively establishing assigned portions of the parsed data to a target object in a database; (e) encapsulating the assigned portions within the target object to form a new target object; and (f) storing the new target object in the database.
  • the method also includes the steps of: (g) receiving a request from the client computer; (h) selectively retrieving data stored in the database in response to the request to form retrieved data; (i) converting the retrieved data into a network compatible format to form converted data; (j) generating a report based on the converted data; and (k) sending the report to the client computer.
  • the converting step includes the step of forming converted data in a HTML or XML format.
  • the identifying step includes the step of identifying a selected parser program from a set of parser programs.
  • the method includes the step of inter-relating a set of target objects in a relational table structure.
  • a method for processing data received across a network in multiple formats includes the steps of: (a) uploading a document provided by a client computer; (b) identifying a selected parser program based at least in part on the document; (c) parsing the document using the selected parser program to provide a parsed document; (d) identifying an entity from the parsed document; and (e) associating the entity to an object in a schedule.
  • the uploading step includes uploading a CAD document.
  • a system for processing data received across a network in multiple formats includes a central processing unit, a communication interface for connection between the network and the central processing unit, and a memory.
  • the memory includes a set of data parser programs and a database having a set of objects. Data received through the communication interface is processed by the central processing unit utilizing at least one of the set of data parser programs to create processed data, the processed data being selectively associated with one of the set of objects in the database and stored in the database based on the association.
  • the memory further comprises a report generator module.
  • the report generator module includes logic code to selectively produce retrieved data from the database in response to a request from a client computer across the network, logic code to convert the retrieved data into converted data in a network compatible format, and logic code to send the converted data across the network to the client computer.
  • the network is a distributed network and the client computer includes an end user or a web site.
  • FIGURE 1 illustrates an exemplary system in accordance with an embodiment of the invention.
  • FIGURE 2A illustrates an exemplary system server in accordance with an embodiment of the invention.
  • FIGURE 2B illustrates an exemplary system in accordance with an embodiment of the invention.
  • FIGURE 3 is a flow chart of an exemplary process in accordance with an embodiment of the invention.
  • FIGURE 4 A is a flow chart of an exemplary process in accordance with an embodiment of the invention.
  • FIGURE 4B is a flow chart of an exemplary process in accordance with an embodiment of the invention.
  • FIGURE 4C is a flow chart of an exemplary process in accordance with an embodiment of the invention.
  • FIGURE 5 illustrates an exemplary inter-relationship of objects in an objects database.
  • FIG. 1 illustrates a network system 100 in accordance with an embodiment of the present invention.
  • the network system 100 includes a communications network 102 connected to a system server 104, client computers 106, Web sites 108, and other networks 114.
  • the communications network 102 is the Internet.
  • Figure 2 A is an exemplary embodiment of the system server 104 in accordance with an embodiment of the present invention.
  • the system server 104 includes one or more central processing units 202, a communications interface 204 for connecting to the communications network 102, and memory 206.
  • the memory 206 includes an operating system 208, server applications 210, communications applications 212, parser programs for parsing incoming documents received through the communications network 102, a report generator 216 for generating reports, a main database 218, a format converter 234 for converting formats, and a relationship compiler 236 for compiling data and object inter-relationships.
  • the main database 218 includes an objects database 220 for storing objects, a programs database 222 for storing computer programs, and a systems application program interfaces 232.
  • the programs database 222 includes scheduling programs 224, cost estimating programs 226, graphical report programs 228, and computer aided design (CAD) programs 230.
  • CAD computer aided design
  • Figure 2B is an exemplary embodiment of the communication between the system server 104 and the client computers 106 through the communications network 102.
  • client computers 106 can upload native data through the communications network 102 for processing by the system server 104.
  • the client computers's native data includes drawings 201, schedules 203, and financial files 205.
  • the data is parsed by a parser program 214.
  • the parser program 214 is selected from a set of parser programs. After the data is parsed, inter-relationships among the parsed data and objects in the objects database 220 are developed by the relationship compiler 236.
  • the parsed data is stored in the main database 218 in accordance with the parsed data's interrelationships to objects in the objects database 220 of the main database 218. Data associated with each object is encapsulated by that object. New objects may also be developed to accommodate the parsed data.
  • Data stored in the main database 218 can be accessed by client computers 106 or Web sites 108 through the communications network 102.
  • the system server 104 receives a request from the client computers 106 or Web sites 108 through the communication network 102, data responsive to the request is retrieved from the main database 218.
  • the report generator 216 generates a report based on the retrieved data.
  • the generated report is then converted into a network compatible format by the format converter 234 and sent to the requesting client computers 106 or Web sites 108.
  • FIG. 3 illustrates an exemplary process in accordance with an embodiment of the present invention.
  • data is received from a client.
  • a parser program is selected (step 304).
  • the received data is parsed by the selected parsing program (step 306).
  • Inter-relationships among the parsed data and objects in an objects database are developed (step 308).
  • the parsed data is stored in a main database, organized by the parsed data's inter-relationships with objects in the objects database (step 309). New objects may also be developed to accommodate the parsed data.
  • responsive data is retrieved from the main database and a report is generated from retrieved data (step 310).
  • the generated report is converted into a network compatible format (step 312).
  • the converted report is sent across the network to the requesting client (step 314).
  • the client can either be a client computer accessed by a end user or a Web site.
  • FIG. 4A illustrates an exemplary process in accordance with an embodiment of the present invention.
  • a user is allowed to sign on to the server system.
  • a new project is initialized (step 404).
  • the user is prompted to define work areas (step 406).
  • the defined work areas form work area objects. Examples of work areas are various floors in a construction project.
  • the user is prompted to select building blocks for each work area (step 408).
  • the selected building blocks form building block objects. Examples of building blocks are number of columns, walls, girders, etc. Building elements and actions are developed based on the defined work areas and selected building blocks (step 410).
  • the developed building elements and actions form building element objects and action objects, respectively.
  • Building elements are developed by associating building blocks to each work area, for example, two columns on the first floor.
  • Actions are developed by defining the work necessary to achieve each building element, for example, welding the columns onto the first floor.
  • Activities are developed based on the developed building elements and actions (step 412).
  • the developed activities form activity objects. Activities are developed based on when each action should be accomplished, for example, welding columns onto the first floor on the fifteenth day of the construction project.
  • a schedule listing detail activities on a day- to-day basis is generated (step 414).
  • inter-relationships among the objects are developed and each object is stored in a main database in accordance with the developed inter-relationships.
  • the system server 104 is able to service clients using different computer software to generate documents.
  • a manager of the construction project may use cost estimating software to generate estimated cost and an architect of the same construction project may use computer-aided design software to sketch the structure of the construction.
  • the system server 104 of this invention can upload the documents created by individuals in a project using different computer software, compile the data in such uploaded documents, generate a centralized database, and provide a comprehensive report to each individual having access to the system regarding the construction project.
  • Figure 4B illustrates an exemplary process in accordance with an embodiment of the present invention.
  • the user has at least one document already created using a computer-aided design software.
  • the user is allowed to sign on to the server system.
  • a new project is initialized (step 418).
  • the user is prompted to define work areas (step 420).
  • the defined work areas form work area objects.
  • the user's CAD drawings are uploaded into the server system (step 422). Entities from the CAD drawings, or CAD entities, are identified (step 424). Building elements and actions are developed based on the identified entities (step 426).
  • the developed building elements and actions form building element objects and action objects, respectively.
  • Activities are developed based on the developed building elements and actions (step 428).
  • the developed activities form activity objects.
  • a schedule listing detail activities on a day- to-day basis is generated (step 430).
  • inter-relationships among the objects are developed and each object is stored in a main database in accordance with the developed inter-relationships.
  • Figure 4C illustrates an exemplary process in accordance with an embodiment of the present invention.
  • the user has more than one document already created using computer-aided design software and scheduling software.
  • the user is allowed to sign on to the server system. After the user is signed on, a new project is initialized (step 434). The user is prompted to define work areas (step 436).
  • the user's documents including a CAD drawing and a schedule, are uploaded into the server system (step 438). Entities from the user's documents, such as CAD entities from the CAD drawing and task entities from the schedule, are identified (step 440). Activities are developed by associating task entities from uploaded schedule to CAD entities from the CAD drawing (step 442). In an exemplary embodiment, the developed activities form activity objects. A new schedule is generated based on the developed activities (step 444). At step 445, inter- relationships among the objects are developed and each object is stored in a main database in accordance with the developed inter-relationships.
  • An exemplary system in accordance with the present invention comprises three functional layers: (1) a presentation layer; (2) an object layer; and (3) an interface and data access layer.
  • the layers are inter-dependent and each layer includes different functionality.
  • the presentation layer organizes user interface components and defines the interaction between users and the system.
  • the object layer categorizes information relating to physical and logical entities in a project.
  • the interface and data access layer defines interfacing mechanisms to third-party software and database management systems. Functionality performed by each layer is discussed in more detail below.
  • the presentation layer provides interfaces between the system and the client.
  • the client may be end users or Web sites.
  • the presentation layer includes mechanism to gather information from clients as well as mechanism to present data to clients.
  • multiple interfaces are used to achieve the functionality. For example, input user interfaces and output interfaces gather data from clients as well as display and publish data to clients.
  • third-party user interfaces allow clients to input or review project data created by third-party software and object interfaces allow communication with objects in the object layer.
  • the object layer provides simple data validation logic as well as computing and data retrieving functionality.
  • each user interface can be mapped to one or more objects defined in the object layer.
  • objects defined in the object layer.
  • a class may comprise multiple attributes that delegate entity data and methods and define the behavior of the entities.
  • An object, instantiated from its class, preserves inherited attributes and methods that regulate the relationship between this object and other project objects. The relationship among objects maintains data integrity and consistency among objects.
  • An index of exemplary objects are as described in appendix A.
  • Each exemplary object is identified by a numerical number and each attribute or method in an object is identified by an alphabetical letter.
  • Numbers in brackets as shown in appendix A for each object represent the inter-relationship between the object to another object identified by that number.
  • a letter following a number in a bracket represents a corresponding attribute of the object identified by the number.
  • Exemplary objects in appendix A can be inter-related using a relational table structure, such as hash table structure.
  • Figure 5 represents an exemplary interrelationship of the objects listed in appendix A. As shown in Fig. 5, the interrelationship among objects establishes a systematic mechanism for project data exchange among objects. Further, systematic data transaction maintains data integrity and achieves data compatibility among different software packages.
  • the inter-relationship of the objects allow the object layer to coordinate data exchange between the presentation layer and the interface and data access layer.
  • the interface and data access layer defines interface mechanisms for data exchange between third-party software and objects in the object layer.
  • an interface between work area objects [object 3] and CAD software is provided.
  • CAD drawings may be uploaded from a client computer 106 or created within the system server 104.
  • CAD entities in CAD drawings are linked to work area objects by assigning identifications ("IDs") to the CAD entities in the drawings.
  • IDs identifications
  • CAD entities represent the geometrical data of a work area object.
  • IDs identifications
  • CAD entities represent the geometrical data of a work area object.
  • corresponding CAD entities with matching IDs are accessed through the CAD's API.
  • all work area objects are checked to find the ones that match the CAD entity's ID.
  • an interface between activity objects [object 15] and Scheduling/Project Management software is provided.
  • schedules created using Scheduling/Project Management software may be uploaded from a client computer 106 or created within the system server 104.
  • task entities in uploaded schedules are linked to activities objects by assigning identifications ("IDs") to the task entities in the schedules.
  • Task entities represent scheduling data of an activity object.
  • IDs identifications
  • corresponding task entities with matching IDs are accessed through the scheduling/project management software's API.
  • all activity objects are checked to find the ones that match the task entity's ID.
  • cost estimates created using cost estimating software may be uploaded from a client computer 106 or created within the system server 104.
  • account entities in the uploaded schedules are linked to cost account objects by assigning identifications ("IDs") to the account entities in the cost estimates.
  • IDs identifications
  • Account entities represent detailed cost data of a cost account object.
  • detailed cost data of a cost account object is bi-directionally linked to account entities by the IDs.
  • an interface between simulation report object [object 21] and report creating software is provided.
  • reports created using report creating software may be uploaded from a client computer 106 or created within the system server 104.
  • cell entities in uploaded reports are linked to simulation report objects by assigning identifications ("IDs") to the cell entities in the reports.
  • IDs identifications
  • cell entities of a simulation report object is bi- directionally linked to cell entities by the IDs.
  • additional methods defined within the object such as SET_X and SET_Y methods, may be invoked to further establish direct access to cell data in a third-party report creating software [object 21 , attributes D, E].
  • an interface to database management systems is provided.
  • the persistence of objects in the object layer are maintained by the WRITE() and READ() method of each object (see appendix A). For example, when the WRITE() method of a current project object is invoked, the project object and all related/subordinate objects are invoked through recursive calling to corresponding WRITEQ methods in those related/subordinate objects. Similarly, the READ() method of the current project object can retrieve all related/subordinate objects from local file systems, database or remote nodes.
  • a new operator object [object 23] is created and added into the operator objects group [object 24].
  • the new operator object's LOGIN() method invokes a new session object [object 27].
  • the user can associate a domain object [object 25] to the new operator object.
  • the data access control table of the domain object [object 25, attribute C] regulates the user's right to access other objects.
  • the system Based on the number of above ground and underground levels of the initiated project object, the system automatically generates a work area object [object 3].
  • the work area object defines floor plans for the new project.
  • a user having appropriate access privileges can modify the generated floor plans or define new floor plans.
  • the elevation attributes of the work area object [attribute E] and any successor work area objects [attribute C] determine the sequence of work area objects. In consideration of gravity, work area objects having the lowest elevation are usually created first. However, users having appropriate access privileges can reorganize the sequence of work area objects.
  • building block objects [object 11] for the type of building structure are assigned or generated. Users having appropriate access privileges are allowed to review, add, delete or modify the default building block objects.
  • building element objects [object 17] and activity objects [object 15] are developed and linked.
  • a user provides pre-existing CAD drawings and/or schedules.
  • the user's pre-existing documents are uploaded into the system.
  • CAD entities in any CAD drawings are identified.
  • the user needs to identify related work areas, building elements, and building blocks. If such information is not discernible visually on the CAD drawings, a request for additional information may be issued to the user for clarification.
  • a new object for each identified building element is developed.
  • the developed building element objects are associated with their related building block and work area objects.
  • Each building block object is related to a set of action objects and building element objects.
  • An activity object can be generated based on the action objects and building element objects associated with a building block object.
  • Each building element object includes the IDs of activity objects for that building element object.
  • each activity object includes the IDs of the related building element object for that activity object.
  • Each action object [object 9] includes a list of resource usage objects [object 9, attribute E].
  • resource usage objects for each activity object can be gathered from associated action objects.
  • Activity objects are grouped based on the following: (1) the attribute in building element objects [object 17, attribute C] that specifies the IDs of associated work area objects; (2) the attribute in building element objects [object 17, attribute D] that specifies the IDs of associated building block objects; and (3) the attribute in activity objects [object 15, attribute F] that specifies associated action objects.
  • a summary activity object group is developed.
  • the summary activity object group includes activity objects having the same attribute category. A user can associate each instance of summary activity object group to one or more task entities in an existing schedule.
  • a user provides pre-existing CAD drawings only.
  • the system in accordance with an embodiment of the present invention generates schedules based on any existing drawings uploaded from the user.
  • the user's pre- existing CAD drawings are uploaded into the system.
  • the uploaded CAD drawings are processed in the same way as described above, whereby CAD entities in any CAD drawings are identified, building element objects are created, and created building element objects are associated with their related building block and work area objects.
  • activity objects are also developed and grouped according to attribute categories. When the activity objects are developed and grouped, a schedule can be generated.
  • the summary activity object groups can be organized as follows: (1) the sequence of a work area object [object 3, attribute C] associated with a building element object [object 17, attribute C] and child activities [object 15, attribute E]; (2) the elevation [object 3, attribute E] of building element objects [object 15, attribute C] of the work area object; (3) the sequence of CAD entities identified; and (4) the sequence of action objects associated with each identified CAD entity [object 15, attribute F].
  • the system Based on the above organizations, the system generates a new schedule using the summary activity object groups through the APIs of the scheduling/project management software. The generated schedule can be modified by users with appropriate access privileges.
  • a user creates new drawings and schedules using the system in accordance with this invention.
  • the user is prompted to identify a current work area and select a target building block object from a customized list provided through a user interface.
  • Each item on the customized list provides a link to a pre-drawn CAD entity.
  • the linked CAD entity is drawn onto a CAD document.
  • the user is allowed to select as many building blocks as desired to create a CAD drawing.
  • the system After a CAD drawing is created, the system generates objects based on the CAD entities as described in the above embodiments. When the appropriate objects are developed, the system generates a schedule as described in the above embodiment.
  • Project data are encapsulated in target objects.
  • Target objects can further be grouped into object groups.
  • a user is able to access the encapsulated data for a project across a network, such as the Internet.
  • Data encapsulated by each target object are referred to as instances.
  • changes to object instances that are encapsulated by target objects are distributed throughout the object groups.
  • the present invention avoids data inconsistency and data re-entry.
  • a user can obtain a display of activity information associated with a selected CAD entity.
  • activity information associated with a selected CAD entity.
  • CAD entities associated building element instances are highlighted by implementing a building object's HIGHLIGHT() method [object 17, attribute G].
  • activity instances (including task entities) associated with the highlighted building element instances are highlighted by the HIGHLIGHT() method [object 15, attribute I].
  • a user can obtain resource information related to a selected CAD entity.
  • CAD entities When a user selects one or more CAD entities from a drawing, associated building element instances are highlighted by implementing building object's HIGHLIGHT() method [object 17, attribute G]. Activity instances associated with the highlighted building element instances are highlighted by the HIGHLIGHTO method. Further, resource entities associated to action instances that are linked to the highlighted activity instances are displayed. Thus, direct links between CAD entities in the drawing and resource entities are created and the user can review linked resource information by selecting CAD entities from the drawing.
  • a user can highlight related building element instances in CAD drawings by selecting task entities.
  • activity instances relating to the selected task entities are retrieved.
  • the CAD entities representing the building element instances linked in the retrieved activity instances are highlighted by the HIGHLIGHT() method [object 17, attribute E].
  • a user can obtain a display of related building element instances at any given time along a time line. Based on a time period specified by a user, the task entities for the specified time period are retrieved.
  • Corresponding CAD entities of the related building element instances for the retrieved task entities are highlighted by the HIGHLIGHTO method.
  • the user can observe the building element instances that are involved at any given time period.
  • a user can obtain a display of building element instances in a critical path.
  • task entities in the critical path are retrieved.
  • CAD entities corresponding to the retrieved task entities are highlighted by the HIGHLIGHTO method.
  • the user can distinguish building element instances in a critical path.
  • a user can obtain a display of building element instances using selected resource.
  • activity instances whose related action instances use the selected resource instance are retrieved.
  • CAD entities of building element instances relating to the retrieved activity instances are highlighted.
  • the user is able to view all CAD entities implementing the selected resource instance.
  • a user can obtain a display of activities using selected resources. When an instance of a resource entity encapsulated in a resource object is selected, activity instances whose related action instances use the selected resource instance are retrieved. Task entities linked to the retrieved activity instances are highlighted. Thus, the user is able to view all task entities implementing the selected resource instance.
  • a user can exchange data between drawings and resources.
  • building element instances corresponding to the selected CAD entities are highlighted.
  • activity instances related to the highlighted building element instances are also highlighted.
  • Resource instances included in action instances of the highlighted activity instances are displayed. If dimensions of the selected CAD entities are modified, the number of linked resource usage instances can be updated by implementing the CALCULATE JVOLUME() method or the CALCULATE_LENGTH() method of the building element object [object 17, attribute K and L].
  • a user can obtain a display of resource information in a work area. When an instance of work area is selected, related building element instances are retrieved. CAD entities related to the retrieved building element instances are highlighted. Resource usage information of the action instances relating to the activity instances that define the construction of the retrieved building element instances is displayed.
  • daily event instances [object 19] are used to provide project simulations. First, the system loops through daily event instances for each day of a project from its start date to its end date. For each project date, a daily event object is developed. The date attribute of the developed daily event object [object 19, attribute B] is the looped date for its corresponding daily event instance. The daily event object also includes IDs of activity instances that should take place within the looped date [object 19, attribute C].
  • instances of daily event objects are sorted in the order of their date attribute [object 19, attribute B] and maintained by the current daily events object group [object 20]. Based on a specified simulation date, daily event instances beginning from the project start date to the specified simulation date are used to prepare various simulations.
  • construction sequence can be visualized in a simulation.
  • the daily event instances during the simulation period include associations with appropriate activity instances.
  • the associated activity instances include association with appropriate building element instances.
  • the DISPLAY() method of the involved building element instances are implemented to simulation the work that should be performed during the simulation period.
  • different colors are used in the simulation to represent different phases of the building element instances.
  • project progress can be simulated for the specified simulation period.
  • a progress line in a schedule for the project can be simulated for the specified simulation period by using the APIs of third-party scheduling/project management software.
  • projected cash flow simulation is provided for the specified simulation period.
  • An array of X-axis data in a simulation report object [object 21, attribute F] records the simulated day and an array of Y-axis data in the simulation report object [object 21, attribute G] records daily spending.
  • Daily spending can be gathered from the balance attribute of a linked cost account instances [object 13, attribute C].
  • the latest daily or cumulative cash flow projections are published by implementing the SET_X() [object 21, attribute D] and SET_Y() [object 21, attribute E] methods.
  • projected resource usage can be simulated for the specified simulation period.
  • An array of X-axis data in a simulation report object [object 21, attribute F] records the simulated day and an array of Y-axis data in the simulation report object [object 21, attribute G] records the consumed quantity of a resource instance.
  • the latest resource usage projections are published by implementing the SET_X() [21, D] and SET_Y() [21, E] methods.
  • Changes to instances encapsulated by respective target objects can be incorporated into simulations by developing a new set of daily event instances based on the changes.
  • a user can simulate project progress using various schedules and resource allocation.
  • Generic project information can be encapsulated into an instance of project class and its subordinate instances.
  • An exemplary project instance may include, but is not limited to the following attributes and methods:
  • G type of contracting method, which regulates the relationship between project participants and the data access control for each party.
  • L an instance of building elements [18], which manages a set of building element instances [17] belonging to the current instance of this project class [1].
  • M an instance of activities [16], which manages a set of activity instances [15] that denote tasks of the current project instance [1].
  • N an instance of work areas [4], which manages a set of work area instances [3] belonging to the current project instance [1].
  • O an instance of resources [6], which manages a set of resource instances [5] used by the current instance of this project class [1].
  • P an instances of cost accounts [14], which manages a set of cost account instances [13] of the current project instance [1].
  • R. an instance of simulation reports [22], which manages a set of simulation report [21] used in the current project instance [1].
  • S. audit information including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • T. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • U. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • V. CREATEO method which instantiates an object of this class.
  • W. DESTROY0 method which removes the calling object from the invented systems.
  • Projects The instance of projects class [2] groups a set of project instances [1] together.
  • An exemplary projects class includes, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of project instance [1 ]) method which return a Boolean value representing whether the project instance [1], whose ID is passed as the parameter, is a member of the ID array [2, B] or not.
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROY() method which removes the calling object from the invented systems.
  • the instances of work area class [3] divide the physical space of the project site into manageable logical zones.
  • An exemplary work area instance [3] may include but is not limited to the following attributes and methods.
  • G ID of project instance [1], which owns this work area instance [2].
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROY() method which removes the calling object from the invented systems.
  • the instance of work areas class [4] groups a set of work area instances [3] together.
  • An exemplary instance of work areas class includes, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of work area instance [3]) method which returns a Boolean value representing whether the work area instance [3], whose ID is passed as the parameter, is a member of the ID array [4, B] or not.
  • I. audit information including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • J. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • K. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • L. CREATEO method which instantiates an object of this class.
  • M. DESTROY() method which removes the calling object from the invented systems. 5.
  • An exemplary resource instance [5] may include, but is not limited to, following attributes and methods.
  • F. cost per unit which is the cost for using a unit of the current class
  • J. audit information including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • K. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • L. WRITEO method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • M. CREATEO method which instantiates an object of this class.
  • N. DESTROY() method which removes the calling object from the invented systems.
  • the instance of resources class [6] groups a set of resource instances [5] together.
  • An exemplary resources class includes, but is not limited to, the following attributes and methods.
  • ISJMEMBER(ID of resource instance [5]) method which returns a Boolean value representing whether the instance, whose ID is passed as the parameter, is a member of the ID array [6, B] or not.
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROY0 method which removes the calling object from the invented systems.
  • An exemplary resource usage instance [7] may include, but is not limited to, the following attributes and methods.
  • F. audit information including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • H. WRITEO which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • the instance of resource usages class [8] groups a set of resource usage instances [7] together.
  • An exemplary resource usages class includes, but is not limited to, the following attributes and methods.
  • E. COUNT() method which returns the number of instances in the ID array [8, B].
  • F. IS_MEMBER(ID of resource usage instance [7]) method which returns a Boolean value representing whether the resource usage instance [7], whose ID is passed as the parameter, is a member of the ID array [8, B] or not.
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROYO method which removes the calling object from the invented systems.
  • Each tasks for a building block instance [6] can be decomposed into a set of action instances, which may include, but is not limited to, the following exemplary attributes and methods.
  • F. audit information including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • H. WRITEO which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • the instance of actions class [10] groups a set of action instances [9] together.
  • An exemplary actions class includes, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of action instance [9]) method which returns a Boolean value representing whether the action instance [9], whose ID is passed as the parameter, is a member of the ID array [10, B] or not.
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROYO method which removes the calling object from the invented systems.
  • This class is the template for development of building element instances [17].
  • An exemplary building block class may include, but is not limited to, the following attributes and methods.
  • a building block instance may consist of none or multiple other building blocks.
  • G audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • H. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • I. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • J. CREATEO method which instantiates an object of this class.
  • the instance of building blocks class [10] groups a set of building block instances [9] together.
  • An exemplary building blocks class includes, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of building block instance [1 1]) method which returns a Boolean value representing whether the building block instance [11], whose ID is passed as the parameter, is a member of the ID array [12, B] or not.
  • H LINK_TO_MEMBER(Link to 3-party CAD entities), which returns a building block instance[l 1], whose link to the geometrical representation [3, D] of CAD system [I] matches the passed one.
  • I audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • J. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • K. WRITEO method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • L. CREATEO method which instantiates an object of this class.
  • M. DESTROYO method which removes the calling object from the invented systems.
  • the cost and budget information are organized by a set of cost account instances, which may include, but is not limited to, the following attributes and methods.
  • G audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • H. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • I. WRITEO method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • J. CREATEO method which instantiates an object of this class.
  • K. DESTROYO method which removes the calling object from the invented systems.
  • the instance of cost accounts class [14] groups a set of cost account instances [13] together.
  • An exemplary cost accounts class includes, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of cost account instance [13]) method which returns a Boolean value representing whether the cost account instance [13], whose ID is passed as the parameter, is a member of the ID array [14, B] or not.
  • H. LuNfK_TO_MEMBER Link to 3-party account entities
  • I. audit information including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • J. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • K. WRITEO method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • L. CREATEO method which instantiates an object of this class.
  • An exemplary activity class may include, but is not limited to, the following attributes and methods.
  • H CPM/PERT attributes, which may be derived from the linked task entities [15, G].
  • J audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • K. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • L. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • M. CREATEO method which instantiates an object of this class.
  • N. DESTROYO method which removes the calling object from the invented systems.
  • the instance of activities class [16] groups a set of activity instances [15] together.
  • An exemplary activities class includes, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of activity instance [15]) method which returns a Boolean value representing whether the activity instance [15], whose ID is passed as the parameter, is a member of the ID array [16, B] or not.
  • H LINK_TO_MEMBER(Link to 3-party task entities), which returns an activity instance[15], whose link to the corresponding task entities [15, G] of scheduling/project management system [II] matches the passed one.
  • I audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • J. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • K WRITE() method, which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • L. CREATEO method which instantiates an object of this class.
  • M. DESTROYO method which removes the calling object from the invented systems.
  • This class represents a physical project object, which occupies work area [3], performs activity [15] and consumes resource [5].
  • An exemplary building element instance may include, but is not limited to the following attributes and methods.
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CACULATE VOLUMEO method which returns the current volume of the linked
  • building elements class [18] groups building element instances [17] together.
  • An exemplary building element class may include, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of building element instance [17]) method which returns a Boolean value representing whether the building element instance [17], whose ID is passed as the parameter, is a member of the ID array [18, B] or not.
  • H LINK_TO_MEMBER(Link to 3-party CAD entities), which returns a building element instance[17], whose link to the geometrical representation [3, D] of CAD system [I] matches the passed one.
  • I audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • J. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • K. WRITEO method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • L. CREATEO method which instantiates an object of this class.
  • M. DESTROYO method which removes the calling object from the invented systems.
  • Project information for a given project day can be organized into a daily event.
  • An exemplary daily event class may include, but is not limited to, the following attributes and methods:
  • E. audit information including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • H. CREATEO method which instantiates an object of this class.
  • the instance of daily events class [20] groups a set of daily event instances [19] together.
  • An exemplary daily event class may include, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of daily event instance [19]) method which returns a Boolean value representing whether the daily event instance [19], whose ID is passed as the parameter, is a member of the ID array [20, B] or not.
  • G MEMBER( Index of the ID array [20, B] ), which returns a daily event instance [19] , whose index number in the ID array [20, B] matches the passed one.
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROYO method which removes the calling object from the invented systems.
  • This class publishes the project information in the order of construction sequence.
  • An exemplary simulation report instance may include, but is not limited to, the following attributes and methods.
  • the instances of this class may be used to report cash flow projection, resource allocation and other chronical project control information.
  • G an array of Y-axis data
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROYO method which removes the calling object from the invented systems.
  • the instance of simulation reports class [21] groups a set of simulation report instances [19] together.
  • An exemplary simulation report class may include, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of simulation report instance [21]) method which returns a Boolean value representing whether the simulation report instance [21], whose ID are passed as the parameter, is a member of the ID array [22, B] or not.
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITEO method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITEO methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROYO method which removes the calling object from the invented systems.
  • the operator class denotes a user who initiates a session instance [27] and has interaction with instances of any classes defined in the invented model.
  • An exemplary operator class may include, but is not limited to, the following attributes and methods.
  • G audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • H. READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • I. WRITEO method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • J. CREATEO method which instantiates an object of this class.
  • the instance of operators class [24] groups a set of operator instances [23] together.
  • An exemplary operators class may include, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of operator instance [23]) method which returns a Boolean value representing whether the operator instance [23], whose ID is passed as the parameter, is a member of the ID array [24, B] or not.
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITEO method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROYO method which removes the calling object from the invented systems.
  • Each operator instance [23] may be associated with different instances of the domain class, which may include, but is not limited to the following attributes and methods.
  • C the data access control table, which is used to determine whether the current users have privilege to create, retrieve, update or delete attributes of model instances.
  • D audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • READ() method which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • WRITE() method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • G CREATEO method, which instantiates an object of this class.
  • the instance of domains class [26] groups a set of domain instances [25] together.
  • An exemplary domains class may include, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of domain instance [25]) method which returns a Boolean value representing whether the domain instance [25], whose ID is passed as the parameter, is a member of the ID array [26, B] or not.
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITEO method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROYO method which removes the calling object from the invented systems.
  • Software session created by operator instances [23] may be represented by this class, which may include, but is not limited to the following attributes and methods.
  • F. audit information including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • OPEN_PROJECT() method which initializes a new project instance [1] or retrieves an existing project instance [1].
  • the instance of sessions class [26] groups a set of session instances [25] together.
  • An exemplary sessions class may include, but is not limited to, the following attributes and methods.
  • IS_MEMBER(ID of session instance [25]) method which returns a Boolean value representing whether the session instance [25], whose ID is passed as the parameter, is a member of the ID array [26, B] or not.
  • H audit information, including who creates the current instance of this class, when this instance was created, who updates this instance and when this instance was modified.
  • I READ() method, which reads information of this instance from the local file system, database or network nodes. Whenever retrieving instances of subordinate classes, it triggers their READ() methods recursively.
  • J. WRITEO method which saves information of this instance to the local file system, database or network nodes. Whenever saving instances of subordinate classes, it invokes their WRITE() methods recursively.
  • K. CREATEO method which instantiates an object of this class.
  • L. DESTROY() method which removes the calling object from the invented systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un dispositif et des procédés de mise en oeuvre de l'interopérabilité logicielle et de l'intégration de données dans des systèmes d'information (100). Des données de projet sont extraites à partir de différents logiciels et encapsulées par des objets mis au point, lesquels sont groupés en groupes d'objets. Les données encapsulées sont accessibles, à travers un réseau (102), à partir d'un d'entrepôt (104) de données centralisées. Lors de la demande de données encapsulées par un ordinateur client (106), ces données sont converties en format compatible avec le réseau et un rapport est produit à partir des données et envoyé à l'ordinateur client (106).
PCT/US2000/014072 1999-06-14 2000-05-22 Dispositif et procedes de mise au point et de gestion de l'interoperabilite logicielle et de l'integration de donnees dans des systemes d'information WO2000077684A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU52811/00A AU5281100A (en) 1999-06-14 2000-05-22 Apparatus and methods for developing and managing software inter-operability anddata integration across information systems

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13901299P 1999-06-14 1999-06-14
US60/139,012 1999-06-14

Publications (2)

Publication Number Publication Date
WO2000077684A1 true WO2000077684A1 (fr) 2000-12-21
WO2000077684A8 WO2000077684A8 (fr) 2002-02-28

Family

ID=22484727

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/014072 WO2000077684A1 (fr) 1999-06-14 2000-05-22 Dispositif et procedes de mise au point et de gestion de l'interoperabilite logicielle et de l'integration de donnees dans des systemes d'information

Country Status (2)

Country Link
AU (1) AU5281100A (fr)
WO (1) WO2000077684A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004038614A2 (fr) * 2002-10-21 2004-05-06 The Boeing Company Systeme et procede de distribution de donnees en lots
US7260772B2 (en) 2002-10-21 2007-08-21 The Boeing Company System and method for creating a pert chart
US7720703B1 (en) * 2001-02-05 2010-05-18 Trimble Navigation Limited System and method for tracking and managing construction projects

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5793966A (en) * 1995-12-01 1998-08-11 Vermeer Technologies, Inc. Computer system and computer-implemented process for creation and maintenance of online services
US5890171A (en) * 1996-08-06 1999-03-30 Microsoft Corporation Computer system and computer-implemented method for interpreting hypertext links in a document when including the document within another document

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5793966A (en) * 1995-12-01 1998-08-11 Vermeer Technologies, Inc. Computer system and computer-implemented process for creation and maintenance of online services
US5890171A (en) * 1996-08-06 1999-03-30 Microsoft Corporation Computer system and computer-implemented method for interpreting hypertext links in a document when including the document within another document

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7720703B1 (en) * 2001-02-05 2010-05-18 Trimble Navigation Limited System and method for tracking and managing construction projects
WO2004038614A2 (fr) * 2002-10-21 2004-05-06 The Boeing Company Systeme et procede de distribution de donnees en lots
WO2004038614A3 (fr) * 2002-10-21 2004-05-27 Boeing Co Systeme et procede de distribution de donnees en lots
US7260772B2 (en) 2002-10-21 2007-08-21 The Boeing Company System and method for creating a pert chart

Also Published As

Publication number Publication date
AU5281100A (en) 2001-01-02
WO2000077684A8 (fr) 2002-02-28

Similar Documents

Publication Publication Date Title
Quartel et al. Methodological support for service-oriented design with ISDL
US6850939B2 (en) System and method for providing selective data access and workflow in a network environment
Vanlande et al. IFC and building lifecycle management
US6122633A (en) Subscription within workflow management systems
Goh et al. ECA rule-based support for workflows
Beeckman CIM-OSA: computer integrated manufacturing—open system architecture
US20070100961A1 (en) Grid processing in a trading network
US20040221259A1 (en) Method and apparatus for status display with intermediate database access
Dong et al. Managing design information in enterprise-wide CAD usingsmart drawings'
CN110807015A (zh) 一种大数据资产价值交付管理方法及系统
US20080086716A1 (en) Method and apparatus for information display with intermediate datasource access
Postina et al. An ea-approach to develop soa viewpoints
Singhal et al. Quartermaster-a resource utility system
Brambilla et al. Model-driven design of service-enabled web applications
WO2000077684A1 (fr) Dispositif et procedes de mise au point et de gestion de l'interoperabilite logicielle et de l'integration de donnees dans des systemes d'information
Heller et al. A management system for dynamic and interorganizational design processes in chemical engineering
Jarke The design of a database for multiperson decision support
JP2001195255A (ja) オブジェクトの生成支援方法および装置
Ganeshan et al. CITYWORK: Application of collaborative technologies for infrastructure management
KR20030009643A (ko) 프로젝트 문서관리 시스템
Selfridge et al. Knowledge management tools for business process support and reengineering
Akhmad et al. ANALYSIS AND DESIGN OF DELIVERY INFORMATION SYSTEM DATA INSURANCE PARTICIPANTS BUSINESS GROUP JAVA DESKTOP ONLINE BASED (STUDY CASE: PT. ASURANSI JIWA GENERALI INDONESIA)
WO2000026822A9 (fr) Systeme informatique de gestion des connaissances relatives a un projet
Sun et al. GALLICON: a prototype for the design of water treatment plants using an integrated project database
Kim et al. An Architecture for Organizational Decision Support Systems that Utilizes a Model Coordination Subsystem

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: C1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: C1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

CFP Corrected version of a pamphlet front page

Free format text: REVISED ABSTRACT RECEIVED BY THE INTERNATIONAL BUREAU AFTER COMPLETION OF THE TECHNICAL PREPARATIONS FOR INTERNATIONAL PUBLICATION

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP