KR100791475B1 - Architectural design management system for cooperating with active partners - Google Patents

Abstract

A system for managing architectural designs electronically for multi-user collaboration is provided to output an optimal result by inducing smooth collaboration among subjects joined in the architectural design, and manage whole project efficiently by tracing information, and collaborating, examining, and checking design business processes. A database stores information needed for the architectural design. A database managing module extracts/transmits the information stored in the database by responding to a search request and condition received from other modules. A result generating module receives the needed information from the database managing module and generates an architectural design result based on the received information. A server operating module controls and manages the module to receive a user request from a user terminal and generate the result. A class ID code is assigned to the result generated from the result generating module according to concrete contents of the result. The class ID code includes a business subject class code, a unit process class code, a business packet class code, and a result property class code.

Description

Architectural design management system for cooperating with active partners

1 is a view showing the overall configuration of a building design management system for multilateral collaboration in accordance with the present invention.

2 is a diagram illustrating a flowchart of a building design management system for multilateral collaboration according to the present invention.

FIG. 3 is a diagram showing the arrangement of unit tasks and work packages for each business entity in an architectural design management system for multilateral collaboration according to the present invention.

4A to 4F are diagrams showing work package achievements when the architectural design department participates as a work subject, and a checklist for necessity of collaboration and review by unit work.

5A to 5F are diagrams showing work package achievements when the mechanical design department participates as a work entity, and a checklist for necessity of collaboration and review by unit work.

6A to 6D are diagrams showing work package achievements in the case where the electrical design department participates as a work entity, and a checklist for necessity of collaboration and review by unit work.

7A to 7D are diagrams showing work package achievements when the civil engineering department participates as a work subject and a checklist for necessity of collaboration and review by unit work.

8A through 8D are diagrams showing work package achievements when the structural design unit participates as a work entity, and shows a checklist for necessity of collaboration and review by unit work.

9 is a view showing the architectural design management output generated by the present invention.

The present invention relates to an architectural design computerized management system for multilateral collaboration as a computerized design task management tool. More specifically, it is possible to derive an optimized outcome by inducing a smooth collaboration among the business entities participating in the architectural design. Of course, it is related to the architecture design computerized management system that can track information by structuring around the information flow and enable collaboration and review according to the design work process.

With the advent of large-scale construction projects, the design process is being subdivided into stages, the number of participants in the design phase is increasing, and the types of participants are diversifying. As the number of participants increases, the importance of collaboration for various opinions and decision-making is emphasized in order to best meet the requirements of the client. Collaboration is defined as the cooperative work of the project owner, the architect design department, and the engineering department for the purpose of improving work efficiency and smoothly progressing the process.

In the past, the importance of managing elements of the design process overlooked the impact of design-level work on the project as a whole. Because design work is an intellectual creative activity, the concept that the design process itself is the object of management has not been established. Recently, however, it has been established that managing the design process can reduce time, cost and manpower, and further improve the satisfaction of the majority of project participants, including owners.

On the other hand, architectural design management is now defined as the process of producing the highest quality work within a limited project budget and time frame. Within this concept, it was difficult to collaborate with the architectural design department because information and decision-making information generated before and after the design task were not easily communicated to the subjects involved in the design process, such as engineering.

In addition, the design deliverables are created and managed mainly for the final deliverables for the purpose of delivery book in each design stage, and it is difficult to keep track of when the person in charge is replaced or the result generated does not meet the requirements. In addition, it is pointed out that it is difficult for the client to check whether the client's requirements are properly reflected in the design process before receiving the final product.

Accordingly, the present inventors have developed a building design computerized management system that can improve the design management efficiency while optimizing collaboration between the building design sector and the engineering sector.

The present invention has been made to improve the above-described conventional problems, and in consideration of the characteristics of the architectural design made by the cooperation of the engineering sector, with the architectural design sector as the main axis, it is optimized by inducing a smooth collaboration between the business entities participating in the architectural design. As the result can be derived and structured around the information flow, not only the information can be traced, but also the collaboration and review can be confirmed according to the design work process. The purpose is to provide an architecture design management system for collaboration.

In order to achieve the above object, the present invention is a system consisting of a web server for providing architectural design management information and a user terminal connected to the web server via the Internet at the request of the user, the web server is required for the architectural design A database storing request information; A database management module for extracting and transmitting information stored in the database in response to a search request and a search condition received from another module; A result generation module for receiving necessary information from the database management module and generating a result based on the transmitted information; And a server operation module for controlling and managing the module so as to receive a user request input from the user terminal and generate a result.

The achievements generated by the achievement generation module are assigned an identification classification code according to a specific content, wherein the identification classification code includes: a work subject classification code defined according to a work subject participating in a building design; A unit business classification code defined for distinguishing each unit of work which is a management standard for each service entity according to the order of progress; A plurality of unit tasks, the task package classification code being defined by distinguishing according to the progress of the work package that is a collaboration standard for each work subject; And, a result object component code defined by distinguishing whether an attribute of the result is a unit task or a work package.

The achievements generated by the achievement generation module are collected by each work package and output as a single outcome package, and the work subjects participating as the subjects of the work package and the work subjects participating as the collaborators are displayed separately. It provides a building design computerized management system for multi-party collaboration, characterized in that the review results and collaboration progress results can be displayed.

Hereinafter, the present invention will be described according to the accompanying drawings and preferred embodiments.

1 is a view showing the overall configuration of a building design management system for multilateral collaboration in accordance with the present invention. As shown, the present invention includes a web server and at least one user terminal connected to the web server via the Internet.

The user terminal is a means for accessing the web server by the subjects who are directly involved in the architectural design management, where the user is the architectural design department and the engineering department (mechanical design, electrical equipment design, civil engineering) in the architectural design management. Design, structural design, etc.), and there is a client (architecturist) who is the decision maker in architectural design management.

The web server is a system for providing architectural design computational management information in response to a user's request from a user terminal. Specifically, the web server includes a database, a database management module for managing the database, and information received from the database management module. It comprises a product generation module for generating the architectural design management results on the basis, and a server operation module for controlling the respective modules so that the entire web server can perform the desired function smoothly.

In the web server, the database is the part that stores the required information for the architectural design. The database basically holds or inputs the user inputs as well as various achievements generated by operating the computerized management system of the present invention. It is stored as the request information.

In the web server, the database management module is a module for manipulating and managing data stored in the database. When a request for providing information is received from the user terminal, the database management module receives corresponding data from the database in response to a search request received from the server operation module. Search and extract and deliver it to the product creation module for product creation.

The product generation module in the web server is a module that receives data from the database management module and generates a product based on the received data. The generated product performs various drawings, documents, etc. related to architectural design management. It means each of the outputs and the identification classification code is given according to the specific contents. The identification classification code may include a work subject classification code defined according to a work subject participating in the architectural design; A unit business classification code defined for distinguishing each unit of work which is a management standard for each service entity according to the order of progress; A plurality of unit tasks, the task package classification code being defined by distinguishing according to the progress of the work package that is a collaboration standard for each work subject; And a performance object component class code that is defined by distinguishing whether an attribute of the achievement is a unit task or a work package. In particular, the achievements generated in the achievement generation module are collected for each work package and output as a single work product package, and the work subjects participating as the subjects of the work package and the work subjects participating as the collaborators are displayed separately, and the achievements in the work package. The results of the review and collaboration results should be displayed. Therefore, the present invention provides a more accurate understanding of the current status of collaboration and review status between tasks by user task subjects, and as a result, it can be used as a useful management tool in architectural design management for the entire project.

The server operating module in the web server is a module for controlling and managing the respective modules so that the architectural design computerized management system implemented by the present invention can smoothly perform the desired function, which is a service transmitted from the user terminal. The data processing process is controlled to receive the request signal and process the corresponding command to output the desired result. To this end, the server operation module retrieves and extracts predetermined data from a database through a database management module, and then refers to this data to provide a predetermined control program and data for controlling the modules so that the result generation module can generate a result. It is built.

2 is a diagram illustrating a flowchart of a building design management system for multilateral collaboration according to the present invention.

The present invention has been developed with a close grasp of information generation and transmission in the course of design work, in order to improve the situation in which the current design work is focused only on the management of contractual submission drawings rather than the actual design work. . Therefore, redefine and package the design tasks described in the existing design guidelines to the task of creating actual design information, and define and package the information generated for each task as the information generated and input from the actual design task and package them. It allows the management of work and outcomes by participating participants. Furthermore, the information flow centered computerized design management model is established by establishing an information flow system from the redefined design tasks and achievements, re-establishing the design process, and setting contact / participation forms and control points for review and collaboration. Building. The outcomes derived from these systems will enable the management of collaboration and review points among participants, such as each architectural design / engineering sector.

FIG. 3 is a diagram illustrating the arrangement of unit tasks and work packages for each work subject in the architectural design management system for multilateral collaboration according to the present invention.

To address the shortcomings of current design management focused on final deliverables, it is necessary to identify the design unit tasks related to the design deliverables that are used and produced in the actual work phase, rather than the production phase that produces and manages the final deliverables. Therefore, in the present invention, after identifying all the tasks for producing the output as design information for each work subject, the task which is the management standard among them is defined and managed as a unit task. Of course, a number of basic tasks may exist within a unit task, and different outcomes may be derived for each task. All design work, however, is limited to the task of producing information as a result and is defined as the task in which it is produced and the task in which it is input as required information.

A work package is formed at a point where a plurality of unit tasks gather to form a collaboration point with other participants. As described above, the present invention constitutes a work package after identifying the unit work, and thus the configuration method is distinguished from a top-down step breakdown, which is a method of constructing a general classification system. Such a work package is not a formal concept, and may vary according to project type, contract type, contract, etc. for each project, and even the same project may vary depending on the participating architectural design and engineering sectors. The composition of the work package makes it possible to clarify the timing of collaboration and review between the architectural design and engineering departments, and the progress of work between participants can be adjusted by linking the work generated in the unit work.

In Fig. 3, a total of 22 tasks of five packages of architectural design work, 20 tasks of five packages of mechanical equipment, 13 tasks of three packages of electrical equipment, ten tasks of three packages of construction, and 12 tasks of three packages of civil engineering have. Since the work structure of this model is organized around information flow, it should be accompanied by consideration of the characteristics and characteristics of the project rather than generally applied to all projects, and it is necessary to reconstruct the process according to the package and scope of work. Will be.

4A to 8D are diagrams showing work package achievements when the architectural design department participates as a work subject, and a checklist for necessity of collaboration and review by unit work.

Proper classification of each task is required for smooth progress and systematic management of unit work, and a clear numbering system is required to systemize it. However, considering the characteristics of the information entity in architectural design management, it is more important to identify the subject and the flow analysis of the subjects that generate the information than to divide the hierarchy of each information and to identify the type and characteristics of the information according to each step. As this will be a big part of the work, the outcomes for architectural design management need to focus on the flow of information generation and use rather than breakdown.

In order to establish a computerized system for the efficiency of design management, the work outcomes were composed of the classification system as described above, reflecting the characteristics, and the composition thereof is shown in the following table. That is, a work subject classification code is assigned to the work outcomes, but is distinguished and defined according to the work subjects participating in the architectural design; A unit business classification code defined for distinguishing each unit of work which is a management standard for each service entity according to the order of progress; A plurality of unit tasks, the task package classification code being defined by distinguishing according to the progress of the work package that is a collaboration standard for each work subject; And a basic business classification code defined in accordance with the basic services constituting the unit service; and a performance object component code defined to distinguish whether or not the attribute of the result is a unit service or a work package. At this time, it is preferable to simplify the entire code configuration in such a manner as to arrange the work subject classification code, the work package classification code, the unit work classification code, the result object component code, and the basic work classification code.

Subject Work Package Progress Sequence Unit order in package Outcome Attributes Basic task number in unit service A: Construction C: Civil Engineering S: Structure M: Machinery E: Electricity L: Landscape G: Preliminary Information T: Other Provisional Materials Write in lowercase letters (a, b, c, ...) in order of progress Numbered according to work order in each package D: Deliverables P: Deliverables Package Numbered according to the order of achievements

According to the above classification code, for example, in the case of the first work of the first work of the first work package of the architectural design sector as the work subject, it may be represented as <Aa01D01>.

The business entity includes the architectural design and engineering sectors (engineering, structural, mechanical, electrical, and landscaping), which are actual participants in the design work, and pre-provided materials, not information generated as the project progresses, such as guidelines and checklists. It can be classified into other participant-provided data, which is included in the scope of work of other participant, and also includes a client who is a decision maker. As suggested in the table above, it is easy for the subject classification code to grasp the initial alphabet code of the subject. However, in the case of other participant-provided data, when assigning a classification number to a work information output of a specific subject, the code of the corresponding subject should be used, but when the same information output is transferred to another subject, a code as a material provided by another participant should be given. do.

In the present invention, in the case of general design work-related outcomes performed by the architectural design or engineering departments, a work package is packaged for the whole process of design work until the final work is derived and the classification codes are assigned according to the order. In the present invention, they are assigned in order as alphabet codes. In the case of pre-provided information (G), guidelines and checklists are provided, and in the case of information provided by other participants (T), they are classified separately according to the owner or other participants. . In addition, as a special case, since there is no previous step in the case of the request information of the first work package of each step, the classification number is not assigned, so they are represented by the lowercase letter z.

When the order of work package is determined, the result is generated by the design work contents carried out internally for each package. Therefore, to classify and classify them, number the unit tasks in each work package in order and derive them from the work. Mark your work. For packages that do not define a unit of work from which a particular deliverable is derived, such as the final deliverable package of a work package, 00 is indicated.

The results derived from the unit work in the work package are collectively defined as deliverables, but in the classification system, these are classified into two types: general deliverables and deliverables packages. In addition to the deliverables, the deliverables package was added for management efficiency and convenience assuming design management through a computerized system. If the same deliverables are introduced at the same time each time, the advantage is that they can be expressed more briefly when a package is composed by combining the deliverables instead of displaying them all at each time. In the present invention, the achievements generated as a result of the work are described as D, and in the case of the achievement package which is a collection of the achievements, P is described.

For each task in the work package, deliverables can be derived for the basic tasks that make up the unit task. In this case, the order of numbers does not mean the order of occurrence of each product, and there is no hierarchy according to the order.

4A to 4F are diagrams showing work package achievements when the architectural design department participates as a work subject, and a checklist for necessity of collaboration and review by unit work.

The work of the architectural design division is packaged. Each package is organized and reviewed at the time of consultation with the client (contractor) in the course of work, and in detail, the pre-design stage in which the preliminary data investigation and the feasibility review are conducted, and the concrete design goal establishment and contract through the grasp of the owner's intention is established. 5 stages of planning and design phases, design and design stages where various alternatives are compared / reviewed, and basic design stages, which are the development of adopted alternatives, and design and implementation stages of various books and specifications. Is packaged. Initially, each work package will reflect the consultation with the client (builder) and establish an overall plan.

The predesign phase of FIG. 4A is a phase where feasibility review is performed based on project-related data survey. A project execution plan is prepared based on the design request and the project outline. The information on the client (architectural owner) and the land is reviewed through the data survey, and the legal review is conducted. The data survey results are packaged into the data survey report and used as basic data for the feasibility review. Design cost estimates and contracts are added to the feasibility review and site analysis results, resulting in a pre-design phase deliverables package.

The planning and design phase of FIG. 4B is mainly focused on research and analysis to reflect the client's (architectural) requirements in the design. As a basis for design progress, reviews such as status surveys, site surveys on and off-site supply facilities, and environmental impact assessments are derived as outcomes and packaged into site survey analysis reports. Since it is possible to reduce the rework of the work as much as possible by grasping and specifying the intention of the client early in the design process, the reconstruction work can be minimized. The building requirements are derived. Based on this, design goals are established using feasibility review report, site survey report and cost data. The land use plan and layout alternatives are prepared and compared, the design cases and design plans are examined, the master plan is proposed, and the cost comparison for each alternative is then packaged into the planning design. Finally, the project plan (planning design), site survey analysis report, and plan design proposal are packaged into the planning design output, and the information is passed to the next step.

In the plan design step of FIG. 4C, the concept and form of the building are provided, and the comprehensive alternatives such as function, scale, shape, structure, and material are presented and compared to obtain and understand the architect's understanding and approval. Based on the planning design plan, which is the final product at the planning design stage, the design concept and space program plan are expressed as design concept, functional analysis diagram and layout plan. It is embodied by the plan design and developed into the initial plan design, and the alternative comparison is made through the detailed legal system review and the construction cost comparison by the plan alternative, and the plan is arranged. The result is packaged and packaged into the design plan, and then packaged as the design deliverable with the previous deliverables package.

The basic design step of FIG. 4D is a step in which the basic concept of the plan design is embodied together with subcontractors such as structures, facilities, civil works, and landscaping. Based on the planning plan, a basic design for cooperative work is prepared. Therefore, through design concreteization, the design program (basic design), major material deadline, and detailed regulatory review will be produced as a result and packaged into the basic design through the confirmation of space program, detailed plan, system review and confirmation, and review of detailed regulations. . Based on this, a basic design document is prepared, including an outline specification and a license document, and a rough construction cost estimate and a temporary statement are prepared through the rough construction cost estimate. The deliverables from the high-level design phase are packaged into the high-level design deliverables to move to the next step.

The implementation design phase of FIG. 4E includes a planning establishment stage, a design task and a cooperative design progress stage, and a comparative review stage for each work package. The draft design is drafted on the basis of the basic design book, and the design summary (design) and design review are prepared and packaged into the design by the supplier. Based on this, the book design and specification are arranged, and the detailed design drawings and specifications are produced and packaged into detailed design books. After that, the construction cost estimate will be made using the temporary statement, outlined construction cost calculation table, and construction cost estimation work guide.

FIG. 4F is a diagram illustrating the time of collaboration and review (review) with the engineering department focusing on the architectural design department, and displaying the time of collaboration and review for design management based on the analysis. Collaboration and review points for design management take into consideration not only decision-making elements in the architectural design sector but also the collaboration of all engineering sectors participating in the design work process.

5A to 5F are diagrams showing work package achievements when the mechanical design department participates as a work entity.

The business overview analysis step of FIG. 5A is a step of identifying the owner's demand for the design requested from the building or the client, reviewing the design guidelines, and establishing a preliminary survey on the infrastructure required for the facility design and setting the design concept through the design.

The system review step of FIG. 5B is a process of reviewing the overall system according to the intention of the owner and the infrastructure of the surrounding environment based on the contents of the project overview analysis, and calculating the rough load based on the schematic building plan. In general, since the specific shell material for load calculation is not determined at the initial stage of planning, it is a step that needs to be updated continuously with the development of decision making in the architectural design sector.

The detailed system planning step of FIG. 5C is a step of deciding an application method for each system based on system review items. The system detailed planning step accurately affects the initial investment or maintenance cost of the building according to the system selection. Decision making is a necessary step.

The basic design step of FIG. 5D is a step of selecting major devices and planning a schematic diagram according to the basic building design book, and requires organic connection with architecture and electricity, and iterative work for decision making with related fields is required.

The implementation design step of FIG. 5E is a step in which a mechanical design drawing, a quotation, a statement, specifications, etc. are generated, in particular, a step in which collaboration with architecture, electricity, or cross check of achievements is required.

FIG. 5F is a diagram illustrating the time of collaboration and review (review) with other work subjects centering on the mechanical equipment design sector and displaying the time of collaboration and review for design management based on the analysis. Mechanical equipment design is mainly carried out through collaboration with the architectural design department.However, work sharing and collaboration with the landscaping or civil engineering design departments are needed for the design of the ground drainage and securing the water space in the ground. And in the setting of the capacity of the pump, heat source equipment, etc., cooperation with the electrical design section is mainly generated. Collaboration is required for facility capacity / load estimation, device placement, and critical system design. Decision-making at these business stages forms an iterative decision-making structure between design teams, requiring systematic management of the workflow.

6A to 6D are diagrams illustrating work package achievements in the case where the electrical design department participates as a work entity.

The major decision-making contents of the electrical equipment design sector focusing on architectural design include the lighting plan according to the plan and the plan for securing the space of vertical and horizontal spaces and electrical related rooms for the strong and weak electrical wiring.

The design of the electrical equipment is closely related to the plan of the building, and space should be secured considering the piping system and structural design in the mechanical equipment as well as all the power loads required in the building. The main repetitive work in the electrical equipment design sector occurs during the electrical design (design of strong and weak electrical equipment) and detailed load calculation stages of the design package. The workflow in which iterations occur can be illustrated in blocks, as shown in Figure 4-19. The detailed load calculation, one of the final tasks of the electrical equipment detailed design phase shown in the second repetitive work block, establishes the electrical equipment implementation plan for the strong and weak electric power according to the information of the detailed construction design book, and establishes the lighting plan. In this paper, the detailed load calculation is finally calculated after the electrical load is calculated by the mechanical equipment. This work flow is not only performed in a linear form, but is performed through repetitive work according to the change of each work content.

7A to 7D are diagrams illustrating work package achievements when the civil design department participates as a work entity.

Civil design in architectural design is generally the basic work for building a building, and few tasks have a decisive influence on the decision-making of architectural design. However, in the case of a project requiring large-scale fill and cut, the planning stage of the complex design of civil engineering should be carried out through active cooperation with the planning design (layout) work in the construction sector, and FIG. 7A to 7D are configured in consideration of this. .

8A to 8D are diagrams illustrating work package achievements when the structural design unit participates as a work entity.

In architectural design, structural design is the most closely related part of architectural design, which influences the overall decision making of architectural design.

In the unit design work of the structural design division, the main collaboration with the architectural design division occurs when the structural method is decided according to the layout of the building at the planning stage. When the initial structural method is decided, structural calculation is made according to the change of architectural design. Therefore, the decision of structural method is a major work step that affects the overall structural design process. Therefore, after the initial building plan layout is made, the decision making through the most cooperation is made when establishing the structural concept for the building. Once the structural design method is decided, work proceeds by performing structural calculation and design based on the information given in the architectural design sector.

9 is a view showing the step-by-step final product produced by the present invention. Achievements are collected by work package and output as a single work product package as shown in FIG. 9, and the work subjects participating as the subjects of the work package and the work subjects participating as the collaborators are displayed separately. And the collaboration result is displayed. Of course, the client can participate as a reviewer of the work.

In particular, in Fig. 9, the construction design management outcomes are configured such that ① work participants, ② work contents, ③ achievements version, ④ design review and collaboration status are displayed. Defining the responsibility for the work by dividing the work participants into the subject, participant, and reviewer, and defining the work contents as the contents according to the information flow about the design work, and defining the results of the work for each work. Backtracking can identify the required information of each task of the information flow structure. In addition, it is possible to grasp the flow of design progress by configuring the work version to be specified, thereby reducing the confusion about books in collaboration and collaboration work. In addition, through the review of design and quality check on collaboration items, the responsibility for the results is clarified. As a result, the result is established as an information-oriented design work structure, and the collaboration and review for design management are completed in a state where the progress of design work management, the assignment of responsibility materials of design participants, and the decision-making flow can be confirmed. do.

According to the present invention as described above, the following effects are expected.

First, by clearly identifying the information required and generated in the individual design tasks of the architectural design process and producing it in the form of a result, it is easy to track and manage the generated information.

Second, the unit deliverables produced in each unit task can be reconstructed into a package of deliverables according to the packaged design workflow, thereby increasing management efficiency.

Third, by identifying design collaboration and review needs according to the information flows and the characteristics of the unit work, it is possible to clearly confirm the timing and results of collaboration and review according to the design work process flow.

Claims (5)

In a system consisting of a web server for providing architectural design management information and a user terminal connected to the web server through the Internet at the request of a user, The web server, A database storing required information necessary for architectural design; A database management module for extracting and transmitting information stored in the database in response to a search request and a search condition received from another module; A result generation module for receiving necessary information from the database management module and generating a construction design management result based on the transmitted information; And, And a server operation module for controlling and managing a corresponding module so as to receive a user request input from the user terminal and generate a result. Achievements generated by the achievement generation module is assigned an identification classification code according to the specific content, the identification classification code, Work subject classification codes defined according to the work subjects participating in the architectural design; A unit business classification code defined for distinguishing each unit of work which is a management standard for each service entity according to the order of progress; A plurality of unit tasks, the task package classification code being defined by distinguishing according to the progress of the work package that is a collaboration standard for each work subject; And, Consists of the resultant material classification code that is defined by distinguishing whether the attribute of the product is a unit work or a work package, The achievements generated by the achievement generation module are collected by each work package and output as a single outcome package, and the work subjects participating as the subjects of the work package and the work subjects participating as the collaborators are displayed separately. Architectural design computerized management system for multi-party collaboration, characterized in that the review results and collaboration progress results can be displayed. In claim 1, The identification code is, The architectural design computerized management system for multi-party collaboration, further comprising; basic business classification code that is defined according to the basic service constituting the unit business. In claim 2, The identification code is, Architectural design computerized management system for multi-party collaboration, characterized in that arranged in the order of work subject classification code, work package classification code, unit work classification code, performance object component code, basic business classification code. In claim 3, The identification code is Business subject classification code and business package classification code are made by distinguishing uppercase and lowercase letters of the alphabet code. The unit task classification code is composed of numeric codes according to the sequence of unit tasks. The resultant ingredient code consists of an alphabet code, Architectural design computing management system for multi-party collaboration, characterized in that the basic business classification code consists of a numeric code. The method according to any one of claims 1 to 4, The business entity is divided into architectural design and engineering, and the client participates as a result reviewer. Architectural design computerized management system for multi-party collaboration, characterized in that the work package of the engineering sector that requires collaboration according to each work package of the architectural design sector.

Images