File naming method and system for collaborative design jobs

Abstract

The application relates to the technical field of file naming management, and discloses a file naming method and system for collaborative design work, which comprises the following steps: S1, dividing a file name into a general unit and a special unit according to the content of each file in a construction link; S2, dividing the general unit according to a division criterion to obtain multiple general codes; S3, classifying the special unit according to a classification mode to obtain a part code and a component code; and S4, adopting different general codes, part codes or component codes according to file content, and combining to form a unique file name according to a set standard. The application uniformly names files according to the set naming standard, the file format formed is uniform, the files are convenient to search and retrieve, and the files are convenient to classify, store and arrange; the required files can be quickly called by personnel in each construction link, so that the efficiency is improved.

Description

Technical Field

[0001] This invention relates to the field of file naming management technology, and more specifically to a file naming method and system for collaborative design work. Background Technology

[0002] With the continuous development of the technology industry, modern engineering projects are also advancing, and the goals they can undertake are becoming increasingly larger. The planning of these projects is becoming more complex and comprehensive, and the architectural designs are becoming more intricate and diverse. This results in a continuous increase in the number of architectural design drawings. Therefore, it is crucial to distinguish and name all documents, including drawings, to differentiate between them.

[0003] To standardize naming practices, a strict file naming format is often adopted within an organization. However, when multiple organizations collaborate, various file name formats still exist. When multiple files need to be used interchangeably or jointly, the file names become complex and difficult to identify, requiring all received files to be renamed. There is no commonality between them. Even if the naming methods are strictly defined within each organization, they still lack universality. In the process of collaboration, the file names are not practical, causing great inconvenience to file identification and management.

[0004] In reality, modern engineering projects involve a wide range of professionals and span a long period of time, resulting in numerous process and phase documents. Traditional naming methods cannot dynamically name the generated process documents, making it impossible to have a clear way to identify intermediate files. When too many files are generated, the file names cannot be standardized, leading to file name chaos. This requires a lot of time and effort to organize and search, thus affecting work efficiency.

[0005] Therefore, in order to address the problem that diverse file names during the construction process are not conducive to searching and management and affect work efficiency, there is a need to provide a file naming method and system for collaborative design work. Summary of the Invention

[0006] The present invention aims to provide a file naming method and system for collaborative design work, and to solve the problem that design drawings are numerous and complex in construction work, making them difficult to search.

[0007] To achieve the above objectives, the present invention adopts the following technical solution:

[0008] This invention enables designers at various construction stages to simultaneously edit drawing files during building construction. By using standardized naming conventions for these files, a correlation is established between them, facilitating quick and easy searching and coordination among construction personnel of all trades, thus saving unnecessary waiting time between construction stages. Specifically, this is a file naming method for collaborative design work, comprising the following steps:

[0009] S1. Based on the content of each document in the construction process, filenames are divided into general units and special units; the general units are filename contents that are used throughout the project; the special units are filename contents that are used only in sub-projects.

[0010] S2, the general unit is divided according to the partitioning criteria to obtain multiple general codes;

[0011] S3, classify the special units according to the classification mode to obtain part codes and component codes;

[0012] S4 uses different general codes, part codes, or component codes based on the document content, and combines them according to the set standards to form a unique document name.

[0013] The principle and advantages of this scheme are as follows:

[0014] File names are categorized into general and specific units. The file name allows for a clear understanding of the file content. If a file contains only general unit content, construction personnel at each stage can access it directly without waiting for each stage to complete before editing. Similarly, files in specific units can be accessed and edited simultaneously based on specific construction needs. By adhering to a pre-defined naming standard, files maintain a consistent format, facilitating searching and retrieval, as well as easy categorization and organization. This ensures that personnel at each stage can quickly access the necessary files, thereby improving efficiency.

[0015] It's worth noting that in the past, construction processes had a sequential order, leading to different trades having their own order of entry. Some even required the next stage's design to be based on the completion of the previous stage's work and its results. Since each stage required adherence to specific design drawings, a technical bias arose: the design drawings needed to be edited sequentially according to the construction process to ensure accuracy and allow for adjustments and improvements based on completed work. This resulted in different naming conventions for the drawings from different designers at each stage. Over time, this led to a chaotic and disorganized workflow during collaborative work, making quick searching and identification difficult. The limitations in file naming further reduced efficiency and increased the likelihood of missing, incorrect, or identical files. This application precisely categorizes file names into general and specialized units, allowing users to directly determine the file content from the name. This enables designers at each stage to simultaneously edit files according to their content and synchronize information, overcoming the technical bias of having to wait for the previous stage to complete before proceeding to the next. Through file name categorization, personnel at each construction stage can simultaneously design and edit files and quickly search for required content by file name, thereby saving construction waiting time and improving construction efficiency.

[0016] Furthermore, by standardizing file names, a unique and universal naming convention is ensured. This guarantees the uniqueness of each file, preventing errors and omissions. It also better reflects the actual content of the generated files, making the content more intuitive. Standardized file names also allow for timely and dynamic adjustments during collaboration, reducing errors and file duplication, making the process more convenient and facilitating collaborative operations, thereby improving productivity.

[0017] Preferably, as an improvement, the classification criteria include professional classification criteria, building attribute classification criteria, floor classification criteria, and unit type classification criteria. File names are classified according to multiple distinguishing features to ensure accurate and reasonable file categorization, facilitating quick searching and retrieval. Furthermore, file names are classified according to various commonly used application scenarios in building construction, making the names clear, concise, and easy to understand.

[0018] Preferably, as an improvement, the general code obtained by classifying general units according to the aforementioned professional classification criteria is defined as the professional code; the professional classification criteria include classification according to job type (i.e., professional category) and classification according to design category. Drawing files are mainly used by designers to edit the parameters required by their profession on the corresponding underlying drawings, and also facilitate construction personnel to view the construction. To facilitate the classification and storage of drawing files, and to make them easier to find, professional codes are classified according to professional categories, which makes it easier for designers to retrieve the required file information. At the same time, classifying files according to design categories allows designers to intuitively understand the design content that each file corresponds to, facilitating quick searching and retrieval, and making file storage more standardized.

[0019] Preferably, as an improvement, the general code obtained by dividing the general unit according to the building attribute classification criteria is defined as the building type code; the building attribute classification criteria are based on the building type. In building construction, the building type is fundamental information about the building. After defining the building type code, construction personnel can quickly retrieve relevant file information for the corresponding building type as needed. When it is necessary to find similar files, they can be quickly retrieved and accessed.

[0020] Preferably, as an improvement, the general code obtained by dividing the general unit according to the floor division criteria is defined as the floor code; the floor division criteria are based on the relative spatial position of the floors. Due to the diverse designs of modern buildings, the structure of each floor or every few floors often differs during construction. When similar buildings exist, the corresponding floors have the same structure. Therefore, naming files according to floor codes allows for quick retrieval and access to relevant files for the same floor when encountering the same building, thus avoiding large amounts of duplicate files, complex and redundant file data, excessive file storage, and reduced file reading efficiency. Furthermore, floor codes enable faster and more convenient retrieval, saving design and construction time, simplifying workflows, and reducing labor costs.

[0021] Preferably, as an improvement, the general code obtained by dividing the general unit according to the unit type classification criteria is defined as the unit type code; the unit type classification criteria are based on the number of main rooms or the size of the unit area. In each floor, especially in residential buildings, there may be units with the same or similar structural designs. Therefore, classifying the units by type and naming them with unit type codes allows for quick retrieval of files with the same unit type structure using the unit type code. Furthermore, when archiving and classifying files, the unit type code can be used for quick indexing and saving, thus saving access time.

[0022] Preferably, as an improvement, the classification mode is based on the general attributes of specialized units. File content that is universally applicable in sub-projects is defined as part codes and named using part coding rules; file content that is not universally applicable in sub-projects or has weak universality is defined as component codes and named using component coding rules. Simultaneously, an association relationship is established between the formed component codes, creating a mutual mapping relationship. When the content of a component code file changes, the mapping relationship allows for timely detection of the file modification status and timely alerts to relevant professionals for review and adjustment, ensuring the accuracy and timeliness of information at each stage of construction. This avoids the information gap where changes are only known after the previous stage is completed. Furthermore, adjustments to files are limited to completed engineering designs, increasing the difficulty of modification. If modifications involve multiple engineering stages, it will increase construction costs and affect the project schedule.

[0023] Preferably, as an improvement, this also includes classifying and storing files according to their content and naming file packages according to set rules. Classifying and storing files according to their content and naming file packages ensures that files are stored in a reasonable and orderly manner, avoiding clutter, making file storage simpler and more convenient, easier to retrieve and find, and easier to manage files.

[0024] Accordingly, the present invention also provides a file naming system for collaborative design work, applied to the above-mentioned file naming method for collaborative design work, specifically including an identification module, an association module, a query module, an organization module, a prompting module, and a definition module connected by electrical connections.

[0025] Implementing this invention has the following beneficial effects:

[0026] This application categorizes file names, making file management more convenient and efficient, allowing for quick retrieval and querying of files based on key information. Simultaneously, an association module links files together, establishing mapping relationships. When a file is modified or requires adjustments to multiple elements, the association module quickly alerts relevant files, and a notification module promptly notifies relevant personnel. This ensures that construction workers can work simultaneously without waiting for each process to complete, improving collaborative work efficiency. Furthermore, using a unified naming format ensures file consistency and order, facilitating management and organization.

[0027] Preferably, as an improvement, the identification module is used to identify the name encoding segment in the file name and extract key information to transmit to the association module; the association module is used to associate files according to the received key information to form a mapping relationship; the query module is used to search and retrieve files according to the input key information; the sorting module is used to classify or bind files into sets and archive them according to the set sorting method, and classify and sort the files in the set folder; the prompting module is used to promptly issue a prompt message when the content of the associated file is updated; and the definition module is used to edit and update the established naming rules. Attached Figure Description

[0028] Figure 1 This is a logic diagram of a first embodiment of the file naming method for collaborative design work according to the present invention. Detailed Implementation

[0029] The following detailed description illustrates the specific implementation method:

[0030] Example 1

[0031] The basics are as follows: Figure 1 The document illustrates a file naming method for collaborative design work. In building construction, this method allows designers at different stages of construction to simultaneously edit drawing files. By using standardized naming conventions, files are linked together, facilitating quick searching and coordination among construction personnel of all trades, and saving unnecessary waiting time between construction stages. The specific steps include:

[0032] Step one: Based on the content of each document in the construction process, classify file names into general units and specific units. General units are file names used universally throughout the project; specific units are file names used only in sub-projects. Distinguishing between general and specific file names allows construction personnel at each stage to directly access files containing only general unit content, while files in specific units can be accessed and edited simultaneously according to actual construction needs, without waiting for the completion of the previous construction stage before editing new files, thus improving efficiency.

[0033] Step two involves dividing the general unit according to a set classification criterion, resulting in multiple general codes under different classification criteria. These classification criteria include professional classification criteria, building attribute classification criteria, floor classification criteria, and unit type classification criteria.

[0034] Specifically, the general code obtained according to the aforementioned professional classification criteria is the professional code. The professional classification criteria include two methods: classification based on job type and classification based on design category. For example, classification based on job type can be divided into site planning, architecture, structure, water supply and drainage, HVAC, and power supply and distribution; classification based on design category can be divided into energy conservation, landscape, and interior decoration. A unified identifier is used to name the classified professional codes. In this embodiment, the first letter of the corresponding professional's English name is used as the unique identifier. If the first letters are the same, the first two letters are used as the displacement identifier for that professional. For example, site planning is defined as G, architecture as A, structure as S, energy conservation as GR, and so on.

[0035] Specifically, the general code obtained according to the building attribute classification criteria is the building type code. The building attribute classification criteria are based on the building type, such as classifying buildings as residential, commercial, or landscaped, and then identifying and naming them according to the building type codes provided by the developer. This way, when relevant files are needed, they can be directly retrieved through key information filtering, improving file application efficiency.

[0036] Specifically, the general code obtained according to the aforementioned floor division criteria is the floor code. The floor division criteria classify floors into multiple types based on their relative spatial location, and each type is uniquely identified using a letter + code format. In this embodiment, floors are divided into four types: a basement level, a floor above ground, a floor on the roof, and a mezzanine level. The corresponding code format for each type is: basement level (B + two-digit serial number), floor above ground (F + two-digit serial number), floor on the roof (R + two-digit serial number), and mezzanine level (M + two-digit serial number). For example, a third basement level would be coded as B03; a first floor above ground as F01; a first floor on the roof as R01 (i.e., the main roof); and a mezzanine level between the basement and the ground floor as B01M01.

[0037] Specifically, the general code obtained according to the aforementioned apartment type classification criteria is the apartment type code. The apartment type classification criteria include the following sub-steps:

[0038] Sub-step 1: Determine whether it is a unit type and obtain the unit type identification number based on the determination result;

[0039] Sub-step 2: Classify the apartment types according to the number of main rooms or the size of the apartment area to obtain the apartment type code;

[0040] Sub-step 3: Sort the apartment types to obtain their numerical serial numbers;

[0041] Sub-step 4: Arrange and combine the apartment type identification number, apartment type code, and apartment type serial number in sequence to obtain the apartment type number.

[0042] In this embodiment, if the building is determined to be a residential type, it can be classified as a unit type, and the unit type identifier is defined as a UNIT. This unit type identifier is applicable to various unit types, including courtyard houses, townhouses, and high-rise villas. Then, for villa and courtyard houses, the unit types are divided into one-bedroom, two-bedroom, three-bedroom, and four-bedroom units according to the number of rooms, and are identified using the corresponding A, B, C, and D symbols. For townhouses and high-rise buildings, the unit types are divided into 0-50㎡, 51-100㎡, 101-150㎡, and >150㎡ units according to their area, and are identified using the corresponding A, B, C, and D symbols. This results in a unique letter code for each unit type under the unit type identifier. The unit types are then numbered sequentially to obtain a unit type numerical sequence number. Finally, the obtained unit type identification number, unit type code, and unit type numerical sequence number are arranged and combined sequentially to form the unit type number. For example, the unit type number for villa three-bedroom unit 03 is represented as UNIT_C03; the unit type number for apartment 120㎡ unit 05 is UNIT_C05. Furthermore, the area range of the unit type can be directly determined from the number, such as whether it is a three-bedroom unit or falls within the area of ​​101-150㎡, making identification and classification easier. In this embodiment, a lowercase letter suffix can also be added after the unit type numerical sequence number to distinguish information about individual rooms within the same unit type. For example, two units are both two-bedroom, one-living room units, both with an area of ​​80㎡, but one room is located at the end and the other in the middle. Therefore, there will be differences in window openings or specific areas on the drawings, but the remaining structure has 90% similarity. To group them under the same management category, they are distinguished by _a / _b at the end of the naming.

[0043] Step three: Classify the specialized units according to a prescribed classification pattern to obtain part codes and component codes. The classification pattern is based on common attributes within sub-projects. Filenames that are common within sub-projects are defined as part codes; filenames that are not common within sub-projects or have low commonality are defined as component codes. Part codes and component codes are named according to their respective rules.

[0044] Specifically, the part coding rules and component coding rules are defined by distinguishing part codes and component codes using corresponding identifiers and supplementary information. In this embodiment, components that are common to all sub-projects, such as location base maps, accompanying legends, stairs, tables, and door / window elevations, are defined as parts. The corresponding part codes are defined using the format "part identifier X_supplementary information"; for example, the corresponding part codes are table_type, stair_serial number, door / window_number, etc. By using components that are used by various professions as parts and encoding them, the file names are made universal across different professions, which is more conducive to querying and using them by different professions. When searching for files, the file content can be intuitively obtained, while reducing the computational load of file storage management and improving the accuracy of file retrieval.

[0045] All content that is not universally applicable or has limited universality in sub-projects—specifically, excluding universally applicable part codes—is defined as component codes and defined using the format "component identifier X_supplementary information," where supplementary information is optional. In this embodiment, components include grid lines, annotations, columns, and walls, and their corresponding component codes are grid lines_scale, annotations, columns, and walls, etc. By using combinatorial parts with a certain degree of universality within each discipline as components, the ease of use of components across disciplines is improved. Specifically, components are set according to parts in each discipline or sub-project that can be partially combined for universality. This facilitates quick and real-time work for operators using components and reduces the possibility of overly complex design structures and excessive storage due to too many parts. This approach facilitates collaborative operation while reducing system space usage.

[0046] In this embodiment, parts with 70%-100% versatility are defined as parts and named using part codes, thereby improving the versatility of part codes. Parts with 20%-40% versatility are classified as components, and those with less than 40% versatility are classified as components. This reasonable distinction between parts and components makes the system more streamlined, facilitates collaborative work, and makes file naming more concise, enabling better collaboration.

[0047] Here, both part identification and component identification are defined using X_supplementary information. X represents incomplete drawings, indicating only partial component drawings, thus distinguishing them from complete drawings. In actual use, the specific names of partial components rarely overlap or are similar to each other. To make naming more concise and convenient, a simplified naming method is uniformly adopted, which is more flexible and simple to use, easier to identify, and reduces storage space.

[0048] Specifically, a correlation is established between the resulting component codes, forming a mutual mapping relationship. Key information within the codes is used to establish this correlation. This correlation is based on the construction content that requires coordination and mutual influence between different stages of the construction process. For example, in architectural design, if the graphic element content is a grid, the component code is defined as "Grid_Scale". If the project implementation scenario involves the shared grid of the standard floor for buildings 1 and 5, the file would be named AX-01_05-FBZ01-Grid_100. In architectural design, if the graphic element content is a basic floor plan element, its component code is defined as "Main Body". If the project implementation scenario involves the large roof plan of building 1, the file would be named AX-01-R01-Main Body. In architectural design, if the graphic element content is basic text annotations, its component code is "Annotation". If the project implementation scenario involves basic annotation information for the first floor of buildings 1 to 5, the file would be named AX-01~05_F01-Annotation. When the grid of Building 1 changes during the design process, the annotation information and main content of Building 1 and Building 5 must also be adjusted according to the grid. At this time, based on the established relationships, the related documents will be promptly adjusted.

[0049] Compared to the current system, where file naming is either standardized and fixed, making it inconvenient to use dynamically, leading to omissions, duplicate names, or even arbitrary naming to ensure unique filenames, this proposed solution dynamically adapts to each collaborative stage. It not only avoids omitting process and temporary files but also ensures that interim and final deliverables can be searched and saved more clearly and concisely.

[0050] Step four: Based on the content of the drawing file, use different general codes, part codes, or component codes, and arrange them in descending order according to the set standard to form a unique design drawing file name. For example, set the standard to name the drawing file according to professional code-part identifier-building type code-floor code-part code-supplementary information; or according to professional code-component identifier-sub-item code-floor code-component code.

[0051] Step 5: Categorize and store the drawing files according to their specific content, and name the file packages according to the set rules. The set rules are based on the formula: Professional Chinese abbreviation + Stage Chinese abbreviation - Sub-item code - Drawing remarks. For example, in this embodiment, based on the drawing content, it can be named General (General Drawing) - Scheme (Plan) - (Sub-item code) 01 - Structure.

[0052] Furthermore, this invention also provides a file naming system for collaborative design tasks, applied to the aforementioned file naming method for collaborative design tasks. Specifically, it includes an identification module, an association module, a query module, an organization module, a prompting module, and a definition module that are electrically connected to each other.

[0053] Specifically, the identification module is used to identify the name encoding segments of drawings and documents, and extract key information from the identified encoding segments and transmit it to the association module. The association module is used to associate the received key information to form a mapping relationship. The query module is used to query and retrieve drawings or documents based on the input key information; at the same time, the query module is also used to query the document encoding rules.

[0054] The organization module is used to classify or bind files into sets according to a set organization method, and then sort the files within the resulting folders. In this embodiment, the organization method is as follows: First, the definition module defines a set of drawings as drawing files organized by sub-items, and a bound set of drawings as a set of drawings organized by project. Then, according to the requirements for a set of drawings, the relevant working drawings are merged into a single DWG file to form a complete set of files, which is the set of drawings folder. Then, the set of drawings is bound according to the requirements for bound drawings, and named with the archiving date + archiving reason, thus forming a bound drawings folder. Within the formed folder, the drawing files are further classified and sorted by comparing the alphabetical order of the file names and arranging them in alphabetical order; if the file name is in Chinese, it is arranged in Chinese pinyin order.

[0055] The notification module is used to promptly issue a notification message when the content of the associated files is updated. The notification message is a pop-up window that includes information such as the changed file content, the file's location, and the update time. The definition module is used to edit and update the naming rules.

[0056] In this embodiment, drawing names are divided into general and special units, and then coded according to a set unified standard. This makes the drawing names more concise, easier to identify and find. At the same time, this naming method accurately reflects information such as profession, project, sub-item, and document content, making drawing files more uniform and unique, meeting sorting and retrieval needs, facilitating quick searching, and improving workflow coordination. Furthermore, this naming method allows for faster guidance by name, provides a convenient indexing method, keeps files neat and organized, and makes storage and organization easier.

[0057] Meanwhile, this naming convention allows for direct identification of dedicated drawing files based on their names, and determines the relevance of drawing content to actual construction work based on the specific construction stage. This enables simultaneous editing of multiple drawings in conjunction with the actual progress. When related drawings undergo changes, update prompts are displayed based on the drawing name, facilitating designers' review and adjustments, thus preventing errors, ensuring drawing accuracy and consistency, avoiding rework, and improving construction efficiency. Furthermore, this application overcomes the technical bias of requiring each construction stage to be performed sequentially, allowing all drawing designs to be completed simultaneously while maintaining overall consistency, thereby saving time spent waiting during construction and further improving efficiency.

[0058] Meanwhile, construction workers can coordinate with the work progress by modifying and adjusting the drawings and documents in real time, thereby planning the construction schedule in advance and avoiding adjustments after construction is completed, which would increase workload and construction costs and affect the overall project schedule, thus effectively improving work efficiency.

[0059] Furthermore, in an engineering project, a basic set of design drawings is first created based on fundamental construction information for construction personnel to use. However, because the project involves numerous construction specialties, and each specialty requires different design drawings, and some related specialties need to build upon the previous stage's design, they all select and modify the necessary parts from the existing basic drawings. This facilitates the coordination of subsequent construction work and allows designers in later specialties to design based on prior information. Therefore, it is impossible to prepare a separate set of design drawings for each specialty, as this would lead to more disorganized drawings, inconsistent and untimely information, and ultimately, an inability to clearly define the final version of the construction drawings.

[0060] Furthermore, because each specialty operates relatively independently during construction, when retrieving and adjusting the necessary design drawings, they habitually use the design methods they are most familiar with in their own field and employ their preferred file naming conventions. This results in a diverse range of drawing files generated at different construction stages within a project, with only the respective discipline capable of understanding their corresponding parts. This is highly detrimental to document retrieval and coordination among construction personnel in subsequent stages. Moreover, with increasingly demanding construction requirements and more complex building structures, the number of design drawings is only increasing, leading to even larger and more disorganized construction drawings. If adjustments are needed at one stage of construction, requiring modifications to subsequent parts of the project, dealing with such a massive amount of design drawings will consume a significant amount of effort in searching and verifying them, and is also prone to errors, causing construction delays and increasing costs.

[0061] Example 2

[0062] Unlike Embodiment 1, this embodiment also includes settings for the total character length and the total number of segments in the file name. Specifically, the settings stipulate that the total character length of the name should not exceed 30 characters (including symbols); and the total number of segments should not exceed 6. Each segment is separated by a hyphen (-). This setting makes the file name more concise and the content of the file name clear and complete, which can not only cover the main information of the file content, but also facilitate differentiation and management. At the same time, it is easier to remember and describe during communication. If the name is too long and complicated, it will increase the difficulty of identification and consume more computing power when organizing and managing, thus increasing management costs.

[0063] In this embodiment, the overall length and number of name segments of the file name are standardized to ensure the uniformity and standardization of the file name, which is more conducive to the management and classification of files. At the same time, the naming process is simplified through a concise naming method, thereby improving the efficiency of file management and making it easier to retrieve and query. In addition, the unified naming method standardizes the behavior of operators, making file management in the industry more intuitive and concise, thereby improving the overall efficiency of file management and reducing the management workload of operators.

[0064] Example 3

[0065] In this embodiment, the correlation degree is divided into at least three categories. Different correlation degrees result in different notification methods for modifications to corresponding files that meet the correlation conditions. From left to right, if the character similarity of the file codes formed by the file names accounts for more than 80% of the total number of file codes, a modification notification is required every hour, and the notification only stops after the corresponding file is modified; if the code similarity is between 60% and 80%, three timed notifications are issued; and if the code similarity is between 50% and 60%, two timed notifications are issued. Based on the set correlation degree, timely notifications and modifications are effectively ensured when files are modified, avoiding omissions and missed important content. This improves the timeliness and accuracy of collaborative work, thereby increasing work efficiency.

[0066] The above descriptions are merely embodiments of the present invention, and common knowledge such as specific technical solutions and / or characteristics are not described in detail here. It should be noted that those skilled in the art can make various modifications and improvements without departing from the technical solutions of the present invention, and these should also be considered within the scope of protection of the present invention. These modifications and improvements will not affect the effectiveness of the implementation of the present invention or the practicality of the patent. The scope of protection claimed in this application should be determined by the content of its claims, and the specific embodiments described in the specification can be used to interpret the content of the claims.

Claims

1. A file naming method for collaborative design work, used for simultaneous editing of files across different construction stages, including the following steps: S1. Based on the content of each document in the construction process, filenames are divided into general units and special units; the general units are filename contents that are used throughout the project; the special units are filename contents that are used only in sub-projects. S2, the general unit is divided according to the partitioning criteria to obtain multiple general codes; S3, classify the special units according to the classification mode to obtain part codes and component codes; S4. Based on the content of the document, different general codes, part codes, or component codes are used to form a unique document name according to the set standard. The system determines whether a drawing file is a dedicated drawing file based on its file name, and assesses the relevance between the drawing content and the actual construction content based on the construction process. In conjunction with the actual progress, multiple drawings are edited simultaneously. When the content of a related drawing is changed, the system provides an update prompt for the related drawing based on its file name. The degree of relevance is divided into at least three categories. Different degrees of relevance result in different notification methods for modifying corresponding files that meet the corresponding relevance conditions.

2. The file naming method for collaborative design work according to claim 1, characterized in that: The classification criteria include professional classification criteria, building attribute classification criteria, floor classification criteria, and unit type classification criteria.

3. The file naming method for collaborative design work according to claim 2, characterized in that: The general code obtained by dividing the general unit according to the professional classification criteria is defined as the professional code; the professional classification criteria include classification according to job type and classification according to design type.

4. The file naming method for collaborative design work according to claim 2, characterized in that: The general code obtained by dividing the general unit according to the building attribute division criteria is defined as the building type code; The criteria for classifying building attributes are based on the building type.

5. The file naming method for collaborative design work according to claim 2, characterized in that: The general code obtained by dividing the general unit according to the floor division criteria is defined as the floor code; The floor division criteria are based on the relative position of each floor within the space.

6. The file naming method for collaborative design work according to claim 2, characterized in that: The general code obtained by dividing the general unit according to the unit type division criteria is defined as the unit type code; the unit type division criteria are based on the number of main rooms or the size of the unit area.

7. The file naming method for collaborative design work according to claim 1, characterized in that: The classification method is to classify based on the general attributes of the special units and establish an association between the obtained component codes.

8. The file naming method for collaborative design work according to claim 1, characterized in that: It also includes categorizing and storing files according to their content and naming file packages according to set rules.

9. A file naming system for collaborative design work, characterized in that, The file naming method for collaborative design work as described in any one of claims 1-8 includes naming the file through an identification module, an association module, a query module, an organization module, a prompting module, and a definition module connected by electrical connections.

10. The file naming system for collaborative design work according to claim 9, characterized in that: The identification module is used to identify the name encoding segment in the file name and extract key information to send to the association module; the association module is used to associate files according to the received key information to form a mapping relationship; the query module is used to search and retrieve files according to the input key information; the sorting module is used to classify or bind files into sets according to the set sorting method, and classify and sort the files in the formed folder; the prompting module is used to issue a prompt message in a timely manner when the content of the associated file is updated; the definition module is used to edit and update the defined naming rules.

Images