Method and system for managing commissioning tasks based on a hierarchical structure

The hierarchical structure-based method and system automate commissioning task management, addressing inconsistencies and errors in manual methods by updating work status and calculating progress rates, enhancing efficiency and accuracy in large-scale industrial facility projects.

KR103043058B1Active Publication Date: 2026-11-06DC E&C CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
KR1020260068253
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Filing Date
2026-04-15
Publication Date
2026-11-06
Estimated Expiration
2046-04-15

AI Technical Summary

Technical Problem

Conventional manual-based commissioning management methods for large-scale industrial facilities suffer from inconsistencies between document submission and status changes, calculation errors, update delays, data attribution errors, and errors in merging test documents, leading to inefficiencies and inaccuracies in tracking progress.

Method used

A method and system for managing commissioning tasks based on a hierarchical structure, including generating a hierarchical structure with project, construction, building, test, and equipment layers, automatically updating work status upon document upload, and calculating progress rates across these layers to ensure data consistency and reduce human error.

Benefits of technology

The system automates repetitive tasks, reduces human error, prevents calculation errors and update delays, maintains data consistency, and provides precise progress tracking through real-time hierarchical progress calculation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 112026046158668-PAT00004_ABST
    Figure 112026046158668-PAT00004_ABST
Patent Text Reader

Abstract

The present disclosure relates to a method and system for managing commissioning tasks based on a hierarchical structure. A method according to one embodiment of the present disclosure may include a method for managing commissioning tasks based on a hierarchical structure, comprising: a step of generating a hierarchical structure including a project hierarchy, a construction hierarchy, a building hierarchy, a test hierarchy, a category hierarchy, and an equipment hierarchy based on equipment data regarding a project; a step of changing the task status of at least one piece of equipment based on the uploading of a commissioning document for at least one piece of equipment; and a step of calculating a progress rate for each of a plurality of layers included in the hierarchical structure based on the task status.
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] The present disclosure relates to a method and system for managing commissioning tasks based on a hierarchical structure. Background Technology

[0002] During the construction of large-scale industrial facilities such as data centers, power plants, and semiconductor factories, testing and verification procedures are performed for various equipment. This process is generally referred to as the commissioning process, and various commissioning documents are generated for each piece of equipment, including test reports, inspection reports, material certificates, verification documents, and approval documents. The commissioning process is typically divided into multiple testing phases (e.g., factory testing, installation inspection, functional testing, integration testing, etc.), and a multi-membership structure can be formed where a single piece of equipment participates in multiple testing phases simultaneously.

[0003] In conventional commissioning management methods, personnel have manually uploaded commissioning documents to equipment folders or managed them through spreadsheet ledgers. Specifically, upon completion of equipment testing, the procedure involves generating a test report as a file, manually uploading it to the folder corresponding to the equipment, recording the completion status in a separate spreadsheet, and manually calculating and reporting the progress rate.

[0004] However, conventional manual-based management methods suffer from several structural problems. First, since document submission and task status changes are separated, the person in charge must manually update the task status separately even after equipment test documents are submitted. This can lead to inconsistencies, such as documents being submitted but status updates being omitted, or conversely, statuses being changed to "completed" without the documents being submitted. Second, because completion status for each piece of equipment must be manually tallied in a spreadsheet to track the progress of each test phase, calculation errors, update delays, and omissions occur frequently in large projects with thousands of registered devices. Third, when equipment data changes frequently during the project, the hierarchical management structure generated based on this data must be updated manually, which can lead to persistent consistency issues where the data does not match the actual status. Fourth, in environments where a large volume of test documents is generated simultaneously, attribution errors are prone to occur during the process of manually assigning each document to equipment. In particular, the likelihood of mis-attribution increases significantly when similar equipment identifiers are mixed. Fifth, the conventional workflow has a limitation in that the existing approval status is not automatically invalidated even if documents for equipment that has already been approved are replaced, resulting in the omission of re-approval for the changed documents. Finally, since the process of combining multiple test documents submitted at the equipment level into a single submission report is performed manually, errors in the merging order, omissions, and update delays occur.

[0005] The aforementioned background technology is technical information that the inventor possessed for the derivation of the present invention or acquired during the process of deriving the present invention, and it cannot be considered as prior art disclosed to the general public prior to the filing of the present invention. The problem to be solved

[0006] The present invention provides a method and system for managing commissioning tasks based on a hierarchical structure. Additionally, the invention provides a computer-readable recording medium that records a program for executing the method on a computer.

[0007] The problems that the present invention aims to solve are not limited to those mentioned above, and other problems and advantages of the present invention not mentioned can be understood from the following description and will be more clearly understood by the embodiments of the present invention. Furthermore, it will be understood that the problems and advantages that the present invention aims to solve can be realized by the means and combinations thereof set forth in the claims. means of solving the problem

[0008] As a technical means for achieving the technical problem described above, the first aspect of the present disclosure may provide a method for managing commissioning work based on a hierarchical structure, comprising: generating a hierarchical structure including a project hierarchy, a construction hierarchy, a building hierarchy, a test hierarchy, a category hierarchy, and an equipment hierarchy based on equipment data regarding a project; changing the work status of at least one piece of equipment based on the uploading of a commissioning document for at least one piece of equipment; and calculating a progress rate for each of the plurality of layers included in the hierarchical structure based on the work status.

[0009] A second aspect of the present disclosure provides a system for managing commissioning tasks based on a hierarchical structure, comprising at least one memory and at least one processor, wherein the at least one processor generates a hierarchical structure including a project layer, a construction layer, a building layer, a test layer, a category layer, and an equipment layer based on equipment data regarding a project, changes the task status of at least one piece of equipment based on the uploading of a commissioning document for at least one piece of equipment, and calculates a progress rate for each of the plurality of layers included in the hierarchical structure based on the task status.

[0010] A third aspect of the present disclosure may provide a computer-readable recording medium having a program for executing a method according to a first aspect on a computer.

[0011] In addition to this, other methods for implementing the present invention, other systems, and computer-readable recording media storing a computer program for executing said methods may be further provided.

[0012] Other aspects, features, and advantages other than those described above will become clear from the following drawings, claims, and detailed description of the invention. Effects of the invention

[0013] According to the means for solving the problem of the present disclosure described above, the present disclosure can solve the problem of inconsistency between document submission and status change.

[0014] In addition, the present disclosure can significantly reduce manpower requirements and human error by automating repetitive tasks.

[0015] In addition, the present disclosure can prevent calculation errors, update delays, and omissions that frequently occurred during manual aggregation.

[0016] In addition, the progress rate of each layer can be managed more precisely and systematically in the present disclosure.

[0017] In addition, the present disclosure allows for strict maintenance of data consistency by managing data based on a hash function.

[0018] The effects of the present invention are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art from the description below. Brief explanation of the drawing

[0019] FIG. 1 is a diagram illustrating an example of a system for managing commissioning tasks based on a hierarchical structure according to one embodiment. FIG. 2a is a configuration diagram illustrating an example of a user terminal according to one embodiment. FIG. 2b is a configuration diagram illustrating an example of a server according to one embodiment. FIG. 3 is a flowchart illustrating an example of a method for managing commissioning tasks based on a hierarchical structure according to one embodiment. FIG. 4 is a diagram illustrating an example of a processor managing and outputting project data according to one embodiment. FIG. 5 is a diagram for illustrating an example of a processor according to one embodiment managing and outputting equipment data. FIG. 6 is a diagram for illustrating another example in which a processor according to one embodiment manages and outputs equipment data. FIG. 7 is a diagram illustrating an example of a processor managing commissioning documents according to one embodiment. FIG. 8 is a diagram illustrating an example in which a processor according to one embodiment outputs the commissioning progress status. FIG. 9 is a diagram illustrating another example in which a processor according to one embodiment outputs the commissioning progress status. FIG. 10 is a diagram illustrating an example of a processor analyzing time series data according to one embodiment. FIG. 11 is a diagram illustrating an example of a processor managing permissions by user type according to one embodiment. FIGS. 12a and FIGS. 12b are drawings illustrating an example of a processor adding feedback information to a commissioning document according to one embodiment. FIG. 13 is a flowchart illustrating another example of a method for managing commissioning tasks based on a hierarchical structure according to one embodiment. FIG. 14 is a flowchart illustrating another example of a method for managing commissioning tasks based on a hierarchical structure according to one embodiment. FIG. 15 is a diagram illustrating an example of a system for managing commissioning tasks based on a hierarchical structure according to one embodiment. Specific details for implementing the invention

[0020] Hereinafter, various embodiments of the present disclosure are described in conjunction with the accompanying drawings. As various embodiments of the present disclosure may be subject to various modifications and may have various embodiments, specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the various embodiments of the present disclosure to specific forms, and it should be understood that they include all modifications and / or equivalents and substitutions that fall within the spirit and scope of the various embodiments of the present disclosure. In relation to the description of the drawings, similar reference numerals have been used for similar components.

[0021] Expressions such as “comprising” or “may comprise” that may be used in various embodiments of the present disclosure indicate the presence of the disclosed corresponding function, operation, or component, etc., and do not limit one or more additional functions, operations, or components, etc. Furthermore, in various embodiments of the present disclosure, terms such as “comprising” or “having” are intended to specify the presence of the features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0022] In various embodiments of the present disclosure, expressions such as “or” include any and all combinations of the words listed together. For example, “A or B” may include A, may include B, or may include both A and B. Additionally, in the present disclosure, expressions such as “A or B,” “at least one of A or / and B,” or “one or more of A or / and B” may include all possible combinations of the items listed together. For example, “A or B,” “at least one of A and B,” or “at least one of A or B” may refer to cases including (1) at least one A, (2) at least one B, or (3) at least one A and at least one B.

[0023] Expressions such as "first," "second," "first," or "second" used in various embodiments of the present disclosure may modify various components of the various embodiments, but do not limit such components. For example, such expressions do not limit the order and / or importance of such components. Such expressions may be used to distinguish one component from another. For example, the first user device and the second user device are both user devices and represent different user devices. For example, without departing from the scope of the various embodiments of the present disclosure, the first component may be named the second component, and similarly, the second component may be named the first component.

[0024] In the embodiments of the present disclosure, terms such as "module," "unit," "part," etc. are used to refer to a component that performs at least one function or operation, and such component may be implemented in hardware or software, or in a combination of hardware and software. Additionally, a plurality of "modules," "units," "parts," etc. may be integrated into at least one module, circuit, or chip and implemented as at least one processor, except where each needs to be implemented in individual specific hardware.

[0025] As used in this disclosure, the expression “configured to” may be replaced, depending on the context, with, for example, “suitable for,” “having the capacity to,” “designed to,” “adapted to,” “made to,” or “capable of.” The term “configured to” may not necessarily mean only “specifically designed to” in hardware.

[0026] The terms used in the various embodiments of this disclosure are used merely to describe specific embodiments and are not intended to limit the various embodiments of this disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise.

[0027] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the various embodiments of this disclosure pertain.

[0028] Terms such as those defined in commonly used dictionaries should be interpreted as having meanings consistent with their meanings in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in the various embodiments of the present disclosure.

[0029] “Commissioning work” refers to a series of processes in which testing and verification procedures are performed on various equipment during the construction of large-scale industrial facilities, such as data centers, power plants, and semiconductor factories. Specifically, the commissioning process is typically divided into multiple testing phases, including Factory Test, Installation Test, Startup Test, Function Test, Integrated System Test, and Turnover Inspection. For each testing phase, various commissioning documents—such as test reports, inspection reports, material certificates, verification documents, and approval documents—must be generated and submitted for individual equipment, and the process reaches a final completion state after approval by a manager.

[0030] Hereinafter, various embodiments of the present invention will be described in detail using the attached drawings.

[0031] FIG. 1 is a diagram illustrating an example of a system for managing commissioning tasks based on a hierarchical structure according to one embodiment.

[0032] Referring to FIG. 1, the system (1) includes a user terminal (10) and a server (20). For example, the user terminal (10) and the server (20) can be connected via wired or wireless communication to transmit and receive data to and from each other.

[0033] For convenience of explanation, FIG. 1 is illustrated as including a user terminal (10) and a server (20) in the system (1), but is not limited thereto. For example, the system (1) may include other external devices (not shown), and the operation of the user terminal (10) and server (20) described below may be implemented by a single device (e.g., user terminal (10) or server (20)) or by multiple devices.

[0034] The user terminal (10) may be a computing device comprising a display device and a device for receiving user input (e.g., a keyboard, a mouse, etc.), and including memory and a processor. For example, the display device may be implemented as a touch screen to receive user input. For example, the user terminal (10) may be a notebook PC, a desktop PC, a laptop, a tablet computer, a smartphone, etc., but is not limited thereto.

[0035] The server (20) may be a device that communicates with an external device (not shown), including a user terminal (10). As an example, the server (20) may be a device that stores various data, including equipment data, hierarchical structures, commissioning documents, etc. Alternatively, the server (20) may be a computing device that includes memory and a processor and has its own computational capabilities. As an example, the server (20) may perform at least some of the operations of the user terminal (10) described below with reference to FIGS. 1 to 15. For example, the server (20) may be a cloud server, but is not limited thereto.

[0036] The user terminal (10) can receive a structured file containing a list of equipment subject to commissioning from the user. The user terminal (10) can create a hierarchical structure including Project, Phase, Building, Test, Category, and Equipment hierarchy, and can provide the created hierarchical structure to the user (30) by visualizing it through a display device. At this time, the user terminal (10) can provide an interface for managing project design documents based on a virtual folder structure. Additionally, the user terminal (10) can systematically classify and store design documents according to the input of a user with administrator privileges.

[0037] The user terminal (10) can receive a commissioning document corresponding to at least one piece of equipment from the user (30) and perform an upload operation. In particular, the user terminal (10) can perform a function of extracting test phase information and equipment identifiers from the filename of the commissioning document and linking them to the file of the corresponding equipment. When the commissioning document is uploaded, the user terminal (10) can transition the work status of the corresponding equipment from incomplete to complete, and initialize it to a waiting state for approval and record it on the server (20). Additionally, the user terminal (10) can update the approval or rejection status of the document according to the administrator's judgment, and may support bidirectional state transitions that return the document to a waiting state regardless of the current state when the document is resubmitted.

[0038] The user terminal (10) can calculate the progress rate for each layer of the hierarchical structure in real time based on the updated work status and output the calculated progress rate so that the user (30) can check it. The progress rate calculation can be performed by aggregating from the lower layer to the upper layer in the order of the equipment unit, category, test, building, construction, and project layers. In addition, the user terminal (10) can provide a customized dashboard based on access rights set differently according to the user role. The dashboard includes a three-color progress bar that simultaneously displays approval, non-approval, and incomplete statuses in different colors to help the user immediately identify work bottlenecks. In addition, the user terminal (10) can support efficient document review in a digital environment by providing an editing function to add annotations or drawings to uploaded commissioning documents.

[0039] In addition to this, the user terminal (10) can perform various operations related to commissioning tasks, and specific details will be described later with reference to FIGS. 3 to 15.

[0040] The user terminal (10) receives equipment data regarding the project and parses the received equipment data to create a multi-level hierarchical structure for efficient management of commissioning tasks. The hierarchical structure may be composed of a project layer, a construction layer, a building layer, a test layer, a category layer, and / or an equipment layer according to the scope of management and physical or logical distinction criteria.

[0041] The Project layer forms the highest unit of management. The lower Construction layer defines detailed construction or work phases distinguished within the overall schedule. The Building layer is classified based on the physical location or zone where equipment is installed. The Testing layer defines the detailed commissioning processes (e.g., factory testing, installation inspection, functional testing, and integration testing) that equipment belonging to the Building layer must perform as separate management items. In particular, the Testing layer supports a multi-membership structure where a single piece of equipment can belong to multiple testing phases simultaneously, enabling multi-faceted tracking of the equipment's operational status. The Category layer classifies equipment groups within the same Testing layer based on their functional characteristics or uses. The Equipment layer includes individual equipment units with unique identification information as the lowest-level nodes.

[0042] The user terminal (10) can create multiple hierarchical structures by mapping dependency and inclusion relationships between attribute values ​​included in the equipment data. Through this, the user terminal (10) can establish a logical foundation in which work completion data generated at the lowest equipment layer can be aggregated and propagated in real time up to the highest project layer.

[0043] Additionally, the user terminal (10) changes the work status of at least one piece of equipment based on the upload of a commissioning document for at least one piece of equipment. The user terminal (10) detects the upload event of the commissioning document and can automatically change the work status of the equipment by using the act of attaching the document itself as the starting point for the state transition without a separate manual state update operation. Specifically, when a commissioning document, such as a test report for a specific piece of equipment, is uploaded to the system through the user terminal (10), the equipment corresponding to the document is identified, and the work status of the corresponding equipment can be immediately transitioned from an incomplete state to a waiting state for approval. Through this, the user terminal (10) can fundamentally prevent the data inconsistency problem that occurred in the conventional manual method where the act of submitting a document and the act of changing the state were separated. When a large number of documents are uploaded in bulk, the user terminal (10) can extract test stage information and / or equipment identifiers from the name of each file and apply the Longest Prefix Match method to assign documents to each piece of equipment without misassignment.

[0044] Furthermore, the user terminal (10) can update the work status to approval or rejection according to the operation of an authorized user for equipment that has been changed to a waiting for approval state after a commissioning document has been uploaded. In particular, for equipment that has already been approved or rejected, if a modified document is re-uploaded or an existing document is replaced, the user terminal (10) recognizes this as a new upload event and automatically resets the work status of the equipment to a waiting for approval state regardless of the current state. Through this bidirectional state transition mechanism, errors where the existing approval status is maintained and a review is omitted even though the document has been replaced are prevented, and the integrity between the combined report for final submission and the latest work status of the individual equipment can be strictly maintained.

[0045] Additionally, the user terminal (10) calculates a progress rate for each of the multiple layers included in the hierarchical structure based on the operational status of at least one piece of equipment. Specifically, the user terminal (10) first calculates the progress rate of individual equipment units in the equipment layer, which is the lowest node, and based on the progress rate of individual equipment units, performs sequential progress rate aggregation from the lower layer toward the upper layer in the order of the category layer, test layer, building layer, construction layer, and project layer. The progress rate of individual equipment units may be determined based on at least one of whether the commissioning document required for the equipment has been uploaded or whether the document has been approved by an administrator. For example, the user terminal (10) may derive the progress rate of the upper layer by calculating the ratio of the number of equipment with attached commissioning documents or completed approval to the total number of target equipment belonging to a specific category layer.

[0046] Furthermore, the aforementioned hierarchical progress calculation process can be performed in real-time within the system whenever the work status of the equipment is updated through document upload or approval processing. In particular, even in cases where a single piece of equipment has a multi-membership structure in which it participates in multiple test stages simultaneously, the user terminal (10) can independently track whether the equipment is participating in each of the multiple tests included in the test layer and accurately reflect this in the progress of the corresponding test layer. In this way, through an automatic calculation structure in which the completion status of the equipment unit is sequentially propagated to the upper layer and integrated into the progress of the entire project, calculation errors, update delays, and omissions that frequently occurred in the conventional manual aggregation process can be fundamentally prevented, and the user (30) can be provided with an updated and precise progress.

[0047] Meanwhile, the user terminal (10) can provide various information related to commissioning tasks to the user (30) by displaying it on the screen (40). Specifically, the user terminal (10) can display a customized dashboard on the screen (40) according to the role of the user (30), who has different access rights set for the previously created hierarchical structure. The customized dashboard may include real-time progress information for at least one of the multiple layers ranging from the project layer to the equipment layer. At this time, a progress bar may be displayed on the screen (40) in which the task status of individual equipment or a specific layer is distinguished by different visual elements (e.g., different colors, etc.), such as approval completed, approval pending, and / or incomplete. Through this, the user (30) can intuitively identify not only the progress of the overall project but also the task sections where document review is delayed or bottlenecks occur.

[0048] Additionally, the user terminal (10) can provide a drill-down interface that enters into detailed data of a lower layer dependent on the element in response to input from a user (30) who selects a specific upper layer element displayed on the screen (40). Through the drill-down interface, the user (30) can quickly search for the document status and approval status of a desired specific area or group of equipment within the vast amount of equipment data associated with large-scale industrial facilities. Furthermore, the screen (40) can support immediate feedback and sharing of review history within the system without the need for a separate external program by displaying a document review viewer that can add annotations or perform drawings on submitted or merged commissioning document files.

[0049] For example, the user terminal (10) can provide information regarding commissioning tasks through an application installed on the user terminal (10). Here, the application may be a software program installed for the purpose of commissioning activities of the user (30). For example, through the application, the user (30) can perform various commissioning activities, such as uploading commissioning documents for each piece of equipment in bulk so that the system assigns them according to the equipment identifier, performing document review tasks by adding comments or drawings to submitted or merged commissioning documents to leave feedback, processing workflow tasks by approving or rejecting the work status of individual equipment based on granted authority, and monitoring real-time progress by hierarchy through a customized dashboard.

[0050] Meanwhile, for the convenience of explanation, throughout the specification, it has been described that the user terminal (10) creates a hierarchical structure including a project layer, a construction layer, a building layer, a test layer, a category layer, and an equipment layer based on equipment data regarding a project, changes the work status of at least one piece of equipment based on the upload of a commissioning document for at least one piece of equipment, and calculates a progress rate for each of the multiple layers included in the hierarchical structure based on the work status, but is not limited thereto. For example, at least some of the operations performed by the user terminal (10) may be performed by the server (20).

[0051] In other words, at least some of the operations of the user terminal (10) described below with reference to FIGS. 1 to 15 may be performed by the server (20). For example, the server (20) may create a hierarchical structure including a project layer, a construction layer, a building layer, a test layer, a category layer, and an equipment layer based on equipment data regarding a project. Additionally, the server (20) may change the work status of at least one piece of equipment based on the uploading of a commissioning document for at least one piece of equipment. Additionally, the server (20) may calculate a progress rate for each of the multiple layers included in the hierarchical structure based on the work status.

[0052] FIG. 2a is a configuration diagram illustrating an example of a user terminal according to one embodiment.

[0053] Referring to FIG. 2a, the user terminal (100) includes a processor (110), memory (120), an input / output interface (130), and a communication module (140). For convenience of explanation, FIG. 2a only illustrates components related to the present invention. Accordingly, other general-purpose components may be included in the user terminal (100) in addition to the components illustrated in FIG. 2a. Furthermore, it is obvious to those skilled in the art that the processor (110), memory (120), input / output interface (130), and communication module (140) illustrated in FIG. 2a may be implemented as independent devices.

[0054] The processor (110) can process instructions of a computer program by performing basic arithmetic, logic, and input / output operations. Here, instructions may be provided from memory (120) or an external device (e.g., a server (20), etc.). Additionally, the processor (110) can control the overall operation of other components included in the user terminal (100).

[0055] The processor (110) generates a hierarchical structure including a project layer, a construction layer, a building layer, a test layer, a category layer, and an equipment layer based on equipment data regarding a project. Specifically, the processor (110) can parse the received equipment data to construct a multi-level logical structure for commissioning task management. The processor (110) can automatically construct a hierarchical structure by setting the project layer as the top-level unit of management and mapping it below to a construction layer that distinguishes the overall schedule, a building layer based on the physical location of the equipment, a test layer that defines detailed processes by supporting a multi-membership structure, a category layer that groups equipment groups according to functional characteristics, and an equipment layer in which individual equipment having unique identification information is the lowest node.

[0056] Subsequently, the processor (110) changes the work status of at least one piece of equipment based on the upload of a commissioning document for at least one piece of equipment. When the processor (110) detects an upload event of a commissioning document, it can transition the work status of the equipment to which the commissioning document belongs from an incomplete state to a waiting state for approval, starting from the act of attaching the commissioning document itself. In the case where a large number of commissioning documents are uploaded in bulk, the processor (110) can extract test phase information and / or equipment identifiers from each filename and apply a longest match priority matching method to assign documents to each piece of equipment. Additionally, the processor (110) can maintain data integrity by initializing the work status to a waiting state through a bidirectional state transition mechanism when a document is resubmitted or replaced.

[0057] Additionally, the processor (110) calculates the progress rate for each of the multiple layers included in the hierarchical structure based on the changed work status. The processor (110) primarily derives the progress rate of individual equipment units belonging to the lowest layer, the equipment layer, based on whether commissioning documents have been uploaded or whether approval by the manager has been completed. Subsequently, based on the derived equipment unit progress rates, the processor (110) performs sequential aggregation from the lower layer to the upper layer in the order of the category layer, test layer, building layer, construction layer, and project layer. In particular, the processor (110) calculates the precise progress of the overall project in real time by independently tracking the participation of equipment in each test and calculating the progress rate, even under a multi-membership structure where a single piece of equipment belongs to multiple test stages.

[0058] Specific examples of the operation of the processor (110) according to one embodiment are described with reference to FIGS. 3 to 15.

[0059] The processor (110) may be implemented as an array of multiple logic gates, or as a combination of a general-purpose microprocessor and memory storing a program that can be executed on the microprocessor. For example, the processor (110) may include a general-purpose processor, a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a controller, a microcontroller, a state machine, etc. In some environments, the processor (110) may include an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. For example, the processor (110) may refer to a combination of processing devices such as a combination of a digital signal processor (DSP) and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a digital signal processor (DSP) core, or any other combination of such configurations.

[0060] The memory (120) may include any non-transient computer-readable recording medium. As an example, the memory (120) may include a non-perishable permanent mass storage device such as RAM (random access memory), ROM (read only memory), disk drive, SSD (solid state drive), flash memory, etc. As another example, a non-perishable permanent mass storage device such as ROM, SSD, flash memory, disk drive, etc. may be a separate permanent storage device distinct from the memory. Additionally, the memory (120) may store an operating system (OS) and at least one program code (e.g., code for the processor (110) to perform an operation described later with reference to FIGS. 3 through 15).

[0061] These software components may be loaded from a computer-readable recording medium separate from the memory (120). This separate computer-readable recording medium may be a recording medium that can be directly connected to a user terminal (100), and may include, for example, a computer-readable recording medium such as a floppy drive, disk, tape, DVD / CD-ROM drive, or memory card. Alternatively, the software components may be loaded into the memory (120) through a communication module (140) that is not a computer-readable recording medium. For example, at least one program may be loaded into the memory (120) based on a computer program (e.g., a computer program for the processor (110) to perform the operation described later with reference to FIGS. 3 to 15) which is installed by files provided through the communication module (140) by developers or a file distribution system that distributes installation files for applications.

[0062] The input / output interface (130) may be a means for interfacing with a device for input or output (e.g., keyboard, mouse, etc.) that may be connected to or included in the user terminal (100). The input / output interface (130) may be configured separately from the processor (110), but is not limited thereto, and the input / output interface (130) may be configured to be included in the processor (110).

[0063] The communication module (140) may provide a configuration or function for the server (20) and the user terminal (100) to communicate with each other via a network. Additionally, the communication module (140) may provide a configuration or function for the user terminal (100) to communicate with other external devices. For example, control signals, commands, data, etc. provided under the control of the processor (110) may be transmitted to the server (20) and / or external devices via the communication module (140) and the network.

[0064] Meanwhile, although not illustrated in FIG. 2a, the user terminal (100) may further include a display device. For example, the display device may be implemented as a touch screen. Alternatively, the user terminal (100) may be connected to an independent display device via wired or wireless communication to transmit and receive data to and from each other. For example, information regarding commissioning activities or commissioning data (e.g., equipment data, commissioning documents, etc.) may be provided through the display device.

[0065] FIG. 2b is a configuration diagram illustrating an example of a server according to one embodiment.

[0066] Referring to FIG. 2b, the server (200) includes a processor (210), memory (220), and a communication module (230). For convenience of explanation, FIG. 2b shows only the components related to the present invention. Accordingly, other general-purpose components may be included in the server (200) in addition to the components shown in FIG. 2b. Furthermore, it is obvious to those skilled in the art that the processor (210), memory (220), and communication module (230) shown in FIG. 2b may be implemented as independent devices.

[0067] The processor (210) can generate a hierarchical structure including a project layer, a construction layer, a building layer, a test layer, a category layer, and an equipment layer based on equipment data regarding a project. Additionally, the processor (210) can change the work status of at least one piece of equipment based on the uploading of a commissioning document for at least one piece of equipment. Additionally, the processor (210) can calculate a progress rate for each of the multiple layers included in the hierarchical structure based on the work status.

[0068] In other words, at least one of the operations of the processor (110) described above with reference to FIG. 2a can be performed by the processor (210). In this case, the user terminal (100) can output information transmitted from the server (200) through a display device.

[0069] Meanwhile, since the implementation example of the processor (210) is the same as the implementation example of the processor (110) described above with reference to FIG. 2a, a detailed description is omitted.

[0070] Various data, such as data required for the operation of the processor (210) and data generated according to the operation of the processor (210), can be stored in the memory (220). Additionally, an operating system (OS) and at least one program (e.g., a program required for the operation of the processor (210)) can be stored in the memory (220).

[0071] Meanwhile, since the implementation example of the memory (220) is the same as the implementation example of the memory (120) described above with reference to FIG. 2a, a detailed description is omitted.

[0072] The communication module (230) may provide a configuration or function for the server (200) and the user terminal (100) to communicate with each other via a network. Additionally, the communication module (140) may provide a configuration or function for the server (200) to communicate with other external devices. For example, control signals, commands, data, etc. provided under the control of the processor (210) may be transmitted to the user terminal (100) and / or external devices via the communication module (230) and the network.

[0073] FIG. 3 is a flowchart illustrating an example of a method for managing commissioning tasks based on a hierarchical structure according to one embodiment.

[0074] Referring to FIG. 3, the method of managing commissioning tasks based on a hierarchical structure consists of steps processed chronologically in the user terminal (10, 100) or processor (110) shown in FIG. 1 and FIG. 2a. Therefore, even if details are omitted below, the content described above regarding the user terminal (10, 100) or processor (110) shown in FIG. 1 and FIG. 2a can also be applied to the method of managing commissioning tasks based on the hierarchical structure of FIG. 3.

[0075] Additionally, as described above with reference to FIGS. 1 and 2b, at least one of the steps of the method for managing commissioning tasks based on the hierarchical structure of FIG. 3 may be processed in a server (20, 200) or a processor (210).

[0076] In step 310, the processor (110) creates a hierarchical structure including a project layer, a construction layer, a building layer, a test layer, a category layer, and an equipment layer based on equipment data regarding the project. Specifically, the processor (110) can parse equipment data in the form of a structured file received through a user terminal, etc., to construct a multi-level logical structure for commissioning task management. The processor (110) can establish an overall classification system for task processing by mapping dependency and inclusion relationships between attribute values ​​included in the equipment data.

[0077] Equipment data refers to a set of specifications for individual equipment that must undergo commissioning procedures during the construction of industrial facilities, as well as various attribute information associated with the individual equipment. Specifically, equipment data may include an equipment identifier to uniquely identify each piece of equipment, the name of the project to which the equipment belongs, construction phase information distinguishing work schedules, building or zone information indicating the physical location where the equipment is installed, or classification information based on the functional characteristics or use of the equipment. Furthermore, equipment data may include information on participation in multiple detailed commissioning stages that individual equipment must undergo, such as factory testing, installation inspection, functional testing, and integration testing, and the processor (110) can track complex business processes based on the equipment data.

[0078] The hierarchical structure refers to a multi-level logical classification system established to efficiently manage equipment data and commissioning documents and to sequentially aggregate the progress rate of the entire project. The hierarchical structure can be configured by setting the project hierarchy, the highest unit of management, as the root node, and arranging the construction hierarchy (schedule unit), building hierarchy (space unit), test hierarchy (detailed process unit), and category hierarchy (equipment group unit) as sequential sub-nodes, while grouping individual equipment with unique identification information into the equipment hierarchy, the lowest node. In particular, the test hierarchy is designed so that a single piece of equipment can belong to multiple test stages simultaneously, allowing the submission status of commissioning documents or the status of work transfers to be independently tracked and calculated for each test stage, even for the same piece of equipment.

[0079] In step 320, the processor (110) changes the operational status of at least one piece of equipment based on the uploading of a commissioning document for at least one piece of equipment. Specifically, the processor (110) detects an event in which a commissioning document associated with a specific piece of equipment is received in the system, and can transition the status of the equipment from incomplete to waiting for approval by using the act of attaching the commissioning document itself as the starting point for the state transition. When multiple commissioning documents are uploaded in batches, the processor (110) can match each file to the corresponding equipment by utilizing identifier information extracted from the name of the commissioning document and a longest match priority matching method, and can prevent the phenomenon of document review being omitted through a bidirectional state transition that initializes the status to a waiting state regardless of the existing state when the commissioning document is replaced or resubmitted.

[0080] Commissioning documents refer to all documents used in relation to commissioning tasks. For example, commissioning documents may include various forms of test and / or verification files generated to prove that each piece of equipment has passed designated detailed processes during the construction of industrial facilities. Commissioning documents may include test reports, inspection reports, material certificates, verification documents, and approval documents; they may be generated individually and attributed to the equipment depending on the type of process involved, such as factory testing, installation inspection, functional testing, and integration testing. Commissioning documents can be updated with added annotations or drawings via an editing interface within the system and can ultimately be utilized as foundational data for a consolidated report compiled to prove the completion of the project.

[0081] The work status of equipment refers to a logical indicator representing the stage to which the submission of commissioning documents and the manager's review process have progressed for individual equipment, which is the lowest unit within the hierarchical structure. Specifically, the work status can be classified into an incomplete state (documents not yet submitted), a pending approval state (documents uploaded and awaiting review), an approved state (finally passed after manager verification), and a rejected state (rejected due to requested revisions). The work status serves as a benchmark for calculating the progress rate for each piece of equipment and can be utilized as a key basis for identifying work bottlenecks visually displayed on the dashboard and the overall project progress chart, which is derived by sequentially aggregating data from lower to upper levels.

[0082] In step 330, the processor (110) calculates a progress rate for each of the multiple layers included in the hierarchical structure based on the work status. Specifically, the processor (110) may use the work status of individual equipment belonging to the equipment layer, which is the lowest node, as the basis data for calculation. The processor (110) may derive a progress rate for a single piece of equipment based on at least one of whether a commissioning document corresponding to the individual piece of equipment has been uploaded or whether approval by an administrator has been completed. Subsequently, based on the derived progress rate for a piece of equipment, the processor (110) may perform a sequential aggregation process from the lower layers toward the upper layers in the order of the category layer, test layer, building layer, construction layer, and project layer. For example, the progress rate of a specific layer may be derived by calculating the ratio of the number of equipment to which a commissioning document has been attached or which has been approved to the total number of target equipment belonging to that layer.

[0083] In addition, the processor (110) can independently track whether the equipment is participating in individual processes included in the test layer, even under a multi-membership structure where one piece of equipment is duplicated across multiple detailed processes, and accurately reflect this in the progress calculation of each layer.

[0084] With reference to FIG. 3, the process of the processor (110) calculating the progress rate for each of the multiple layers included in the hierarchical structure through steps 310 to 330 has been described. However, the process is not limited to the above-described process, and the processor (110) can perform various operations regarding commissioning tasks.

[0085] According to one embodiment, the processor (110) can generate a unique identification value for received equipment data based on a hash function. The processor (110) can determine whether the equipment data has been changed by comparing the generated unique identification value with a previously stored unique identification value. Subsequently, the processor (110) can update the hierarchical structure based on the determined change status. Furthermore, the processor (110) can track the operational status of the equipment based on whether the equipment is participating in each of the plurality of tests included in the test layer. Additionally, the processor (110) can manage commissioning documents corresponding to at least one piece of equipment included in the equipment layer. The processor (110) can manage the upload status of the commissioning documents of at least one piece of equipment based on a hash value. Meanwhile, the processor (110) can classify the test layer based on the project design documents and equipment documents. The processor (110) can manage the project design documents based on a virtual folder structure. Additionally, when calculating the progress rate, the processor (110) can first calculate the progress rate for individual equipment units of the equipment layer. At this time, the processor (110) can calculate the progress rate for individual equipment units based on at least one of whether the commissioning document for individual equipment has been uploaded or whether the commissioning document for individual equipment has been approved. Subsequently, the processor (110) can calculate the progress rate for each layer sequentially in the order of category layer, test layer, building layer, construction layer, and project layer based on the derived progress rate for individual equipment units. Additionally, the processor (110) can display a customized dashboard for each user who has access rights set differently for the layer structure. The processor (110) can include progress information for at least one layer included in the layer structure in the customized dashboard and provide it to the user.

[0086] Below, the operation of the processor (110) regarding commissioning work is described in more detail.

[0087] The processor (110) can manage users with access rights set differently regarding the hierarchical structure by mapping them on a project basis. For example, the processor (110) can manage the client, contractor, and operator by mapping them 1:1:1 on a project basis.

[0088] The processor (110) can structure project information and store it in a database. Specifically, project information can be managed by classifying it into basic information, site information, and facility design information. Basic information includes a project name (name) indicating the name of the project, a URL identifier (slug) which is a unique identifier generated by the system for use in web address access, etc., and a company type (company_type) which is selected and mapped to one of a client, orderer, contractor, or operator. Site information can be composed of a representative image that visually guides the project and a thumbnail image that is a reduced image for displaying a list, a building location (location) specifying the physical location of the building, a construction period (construction_period) indicating the schedule from the start to the end of construction, a site area (site_area) and a gross floor area (gross_floor_area) of the building, a building number (total_floors) indicating the scale of the building, and a data hall capacity (data_hall_capacity) indicating the data center hall capacity. The facility design information includes detailed design information for the electrical system regarding electrical facilities, the mechanical system regarding mechanical facilities, and the fire system regarding firefighting facilities applicable to the project.

[0089] Project information may be information entered through a user interface by a super administrator or a user with administrator privileges (hereinafter referred to as the "System Administrator") during the project registration and editing process. Specifically, the System Administrator individually enters each item, such as images, location, area, construction period, and facility design information, on the project creation screen, and the entered project information may be stored in a structured form within the system's internal database. The stored project information may be utilized as core reference data in subsequent processes performed by the system, such as equipment classification, creation of multi-level hierarchical structures, calculation of progress rates by level, and access control based on user roles.

[0090] The processor (110) maps the client, construction company, and operator to the project one-to-one and stores them in a database, and can determine access rights for each user differentially based on the established mapping relationships. Specifically, when a specific user requests access to the system, the processor (110) can extract identification information of the company to which the specific user belongs and compare it with the company information mapped to the project to determine if the user is a valid access subject. As a result of the comparison, for users whose mapping relationship is confirmed, the scope of actions that can be performed within the system, such as uploading commissioning documents, viewing progress dashboards of individual equipment, or approving and rejecting work status, can be granted restrictively according to the authority policy assigned to the type of company to which the user belongs (e.g., client, construction company, or operator).

[0091] The processor (110) manages commissioning documents based on the Equipment ID and can apply a hierarchical structure according to the commissioning progress process ranging from commissioning stage 0 to commissioning stage 7. Equipment data, which serves as the basis for establishing the hierarchical structure and calculating the progress rate, can be registered in the system through a batch registration method of a file in a pre-configured format (e.g., Excel, etc.) or an individual registration method on a web screen.

[0092] In the case of the bulk registration method using Excel files, a user in the role of an administrator or a construction company can upload an Excel file containing a list of equipment through a user interface. The processor (110) analyzes the column titles of the uploaded Excel file and can recognize similar expressions such as "EquipmentID," "tag," and "equipment name" as corresponding items in the system through a keyword-based matching method and link them. Through this, equipment data such as tags, English names of equipment, equipment classification, construction phase, building code, and participation status for each commissioning phase can be collectively registered in the database.

[0093] In the case of the individual web screen registration method, a user in the role of an administrator or a construction company can perform registration on a per-item basis by directly entering specific attributes of individual equipment (e.g., tag, English name of equipment, facility classification, construction phase, building code, participation in commissioning phase, etc.) on the web-based equipment registration screen.

[0094] A hierarchical structure can be generated by the processor (110) based on the attribute values ​​of the registered equipment data. For example, the hierarchical structure can be configured as follows. The processor (110) places a project layer, which is the overall management unit, at the top, configures a construction layer below it that distinguishes the overall schedule, and places a building layer below the construction layer that indicates the physical location where the equipment is installed or the building code. The processor (110) configures a test layer below the building layer that indicates detailed processes classified into stages 0 through 7, and places a category layer below the test layer that indicates equipment classifications including electrical, mechanical, and fire protection. The processor (110) can complete the entire logical tree structure by connecting an equipment layer below the category layer that indicates the names of individual equipment, such as high-voltage switchboards, low-voltage switchboards, and chillers.

[0095] As a specific example, a specific building layer (e.g., Building A) may be located below a specific construction layer (e.g., Phase 1 of construction), and below it, the design and programming phase, factory testing phase, installation inspection phase, commissioning testing phase, functional testing phase, integrated system testing phase, handover inspection phase, and termination phase may be branched out as independent test layer nodes. Below the factory testing phase, electrical, mechanical, and fire protection category layers may be provided; under the electrical category, high-voltage switchboards, low-voltage switchboards, and transformers may be included as equipment layers; under the mechanical category, air conditioners, chillers, and cooling towers may be included as equipment layers; and under the fire protection category, fire pumps may be located as individual equipment layers. Other intermediate test layers, including the installation inspection phase, may also have subcategories and equipment layers that are substantially identical in form to those of the factory testing phase. Meanwhile, depending on the nature of the work, an exceptional structure may be configured, in which folders for managing commissioning plan documents and commissioning reports are placed separately under the design and program phases, and the final commissioning report is placed under the termination phase.

[0096] Meanwhile, the processor (110) can create a hierarchical structure according to the following algorithm. When equipment data is registered in the system in Excel form or when an event occurs where equipment is added or changed, the processor (110) can analyze the equipment data to determine the number of equipment by construction stage, the number of equipment by facility classification, and the status of each piece of equipment's participation in the commissioning stage. Subsequently, the processor (110) can query the list of buildings by construction stage and create folders for stages 0 through 7 for each individual building. Next, the processor (110) can perform the process of creating subfolders separated by each commissioning stage. For stage 0, the processor (110) can create a fixed folder to manage electrical, mechanical, firefighting, commissioning plans, and commissioning reports. For stages 1 through 6, the processor (110) can first query the equipment participating in the corresponding stage and then create folders by facility classification, such as electrical, mechanical, and firefighting. Subsequently, the processor (110) can create folders by equipment English name under the facility classification. Additionally, the processor (110) can sort the equipment classifications in the order of electrical, mechanical, firefighting, and others. The processor (110) can create a fixed folder to store the final commissioning report for the seventh stage of commissioning. Once the configuration of the hierarchical structure is complete, the processor (110) can store the derived hierarchical structure in a database in JSON format. The processor (110) can generate a fingerprint, which is a unique data fingerprint, by applying a hash algorithm based on the data stored in the database. The processor (110) can then store the generated fingerprint in the system.

[0097] Specifically, the processor (110) can store the derived folder tree structure in a database in the form of JSON, which is a structured data representation format. The processor (110) can organize the entire folder hierarchy stored in the JSON form into a single self-referencing tree data and store it in a single record of the database. The processor (110) can organize each folder node included in the folder tree structure into a folder name, a unique identification key, and a list of subfolders. Specifically, the processor (110) can assign the display name of the corresponding folder as the folder name. The processor (110) can assign a string that uniquely identifies the corresponding folder as the unique identification key. The processor (110) can assign an array containing folder nodes of the same structure recursively as the list of subfolders. By storing the entire hierarchy in a single record, the processor (110) can obtain tens to hundreds of folder relationships at once with only a single database query. Through this, the processor (110) can significantly improve data retrieval efficiency compared to the method of storing folders as individual rows in a relational table. Additionally, the processor (110) can represent a hierarchy with no limit on depth by utilizing a self-referencing structure in which a list of subfolders contains nodes of the same form as themselves. By utilizing this self-referencing structure, the processor (110) can fully represent the five-level hierarchy within the system, which consists of the previously constructed construction layer, building layer, test layer, category layer, and equipment layer. Furthermore, the processor (110) can perform atomic updates that store and replace the entire tree as a single record. Consequently, the processor (110) can prevent the phenomenon in which data becomes partially inconsistent when updating the tree structure.

[0098] The processor (110) may apply a hash function-based fingerprint mechanism to detect changes in equipment data. The processor (110) may use SHA256 as a cryptographic hash function that converts arbitrary data into a unique string of 64 characters. Furthermore, the processor (110) may detect changes in equipment data by utilizing the characteristic of SHA256, which generates a different value if the data is changed by even 1 byte.

[0099] When the processor (110) receives a request to look up the folder structure via an API call, it can calculate a fingerprint based on the current equipment data. Subsequently, the processor (110) can compare the calculated first fingerprint with a second fingerprint previously stored in the database. If, as a result of the comparison, the first fingerprint and the second fingerprint match, the processor (110) determines that there is no data change and can return the previously cached folder structure without a folder structure regeneration process. On the other hand, if, as a result of the comparison, the first fingerprint and the second fingerprint do not match, the processor (110) can detect that an event of adding or changing equipment data has occurred. If a data mismatch is detected, the processor (110) can update and regenerate the folder structure based on a lazy regeneration method. Afterward, the processor (110) can store the first fingerprint in the database. The processor (110) can provide the updated hierarchy structure to the system by returning the regenerated folder structure.

[0100] Specifically, the processor (110) can produce a fingerprint by combining item data including at least one of the total quantity of equipment, the last modification date of the equipment, a building list, a category list, or a list of English names of the equipment. The processor (110) can use a hash function, which is a one-way function that converts input data of arbitrary length into a fixed-length 64-character hexadecimal string. The processor (110) can determine whether the equipment data has been changed by utilizing the Avalanche Effect characteristic, in which if any one of the five combined items is changed and the input data changes by even 1 bit, the output value produced changes completely. Through this, the processor (110) can update the system's folder structure to the latest state without separate manual work when the fingerprint value changes due to the addition, modification, or deletion of equipment data. Furthermore, the processor (110) may apply a lazy regeneration method in which it regenerates the folder structure only when a change is detected by comparing the existing fingerprint with the new fingerprint at the time the user queries the folder structure, rather than regenerating the folder structure every time the equipment data changes. Through this lazy regeneration method, the processor (110) can regenerate the folder structure only once at the time of the user's query, even if the equipment data changes multiple times in a short period. Additionally, the processor (110) can complete the determination of whether data has changed with a constant time complexity (O(1)) regardless of the total number of equipment by performing a simple identity comparison of 64-character strings. As a result, the processor (110) can avoid unnecessary regeneration operations and use system resources efficiently.

[0101] The processor (110) may set an identification mark instructing 'manual editing' on an automatically generated hierarchical management structure (e.g., a folder structure) when manual operation or change by an administrator is detected. The processor (110) may control the structure with the manual editing mark set to be excluded from automatic regeneration during the process of updating the hierarchical management structure when a change in equipment data is detected. By providing such a manual editing protection function, the processor (110) can support the preservation of the administrator's intentional adjustments without damage during the automatic update process by the system. However, if the processor (110) receives an explicit request input from an administrator requesting the regeneration of the management structure, it may control the regeneration process for the structure to be forcibly performed regardless of whether the manual editing mark is enabled.

[0102] The processor (110) can link the hierarchical structure, which is a logical data classification system, with the folder structure, which is an actual document storage system within the system. Specifically, the processor (110) can convert each logical node of the project layer, construction layer, building layer, test layer, category layer, and equipment layer, derived based on the attribute values ​​of the equipment data, into an individual folder node of a self-referential tree stored as a single record in the form of JSON. Through this, the processor (110) can directly align the equipment-specific progress calculation system on the hierarchical structure, which has complex multiple membership relationships, with the submission of commissioning documents and work status under the folder structure. Additionally, if the logical connection relationship of the hierarchical structure changes due to the modification of the equipment data, the processor (110) can detect the discrepancy between the calculated first fingerprint and the previously stored second fingerprint and update the entire folder structure to conform to the new hierarchical structure based on a delayed regeneration method.

[0103] Specifically, the processor (110) may apply a lazy regeneration method to prevent unnecessary computation by withholding updates until the management structure is actually needed, even if the equipment data changes. Specifically, the processor (110) may perform a process of calculating a new fingerprint from the current equipment data and comparing it with a previously stored fingerprint whenever a query for the management structure is requested. If the fingerprint calculated as a result of the comparison matches the stored fingerprint, the existing management structure is returned and provided as is, and the processor may control the system to automatically regenerate the management structure only if the two values ​​do not match. By implementing a lazy regeneration mechanism that determines whether a change has occurred at the time of query and updates the structure, the processor (110) can effectively reduce unnecessary computational load on the system and improve overall processing efficiency even in an environment where equipment data changes frequently.

[0104] The processor (110) can determine the operational status of individual equipment units based on whether the individual equipment participates in the commissioning phase. Specifically, the processor (110) can maintain a database by mapping multiple flag items that indicate whether each piece of equipment participates in the commissioning phases 1 through 7. The processor (110) can map the first flag to the first phase corresponding to factory testing, the second flag to the second phase corresponding to installation inspection, and the third flag to the third phase corresponding to commissioning testing. Subsequently, the processor (110) can map the fourth flag to the fourth phase corresponding to functional testing and the fifth flag to the fifth phase corresponding to integrated system testing. Additionally, the processor (110) can map the sixth flag to the sixth phase corresponding to handover inspection and the seventh flag to the seventh phase corresponding to termination.

[0105] The processor (110) can track whether the commissioning document of the target equipment has been uploaded and / or the work status only for specific commissioning stages that are set to true or yes among multiple flag items assigned to each piece of equipment. By applying criteria for determining participation, the processor (110) can accurately reflect the characteristics of the site, where the inspection process required for each piece of equipment is different, into the system. Accordingly, the processor (110) can exclude unnecessary status tracking calculations for stages that are not participating and prevent distortions or errors that may occur during the progress calculation process.

[0106] The processor (110) may receive an operation in which a user uploads a file regarding commissioning documents, such as a test report, for equipment participating in a specific commissioning stage. The processor (110) may determine the work status of individual equipment units based on whether a test report file exists on the equipment. If the test report file does not exist on the equipment, the processor (110) may determine the work status of the equipment as incomplete. On the other hand, if the test report file exists on the equipment, the processor (110) may determine the work status of the equipment as completed. The processor (110) may transition the work status of the equipment from incomplete to completed without a separate manual state change operation, using the act of attaching the test report document file itself as a starting point. Subsequently, the processor (110) may perform a three-stage approval workflow based on the manager's judgment for the equipment determined to be in a completed state. In the case of an unjudged situation where approval or rejection by the manager has not been made, the processor (110) may maintain the work status of the equipment in a waiting state for approval. The processor (110) can update the equipment's work status to a final approval state when an administrator inputs an operation instructing approval. The processor (110) can update the equipment's work status to a rejection state when an administrator inputs an operation instructing rejection. Furthermore, at the time when the final approval or rejection status for the equipment is determined, the processor (110) can record the identification information of the performer who performed the corresponding processing and the time of execution in the system's database.

[0107] The processor (110) can manage multiple commissioning documents attached to individual equipment units. The processor (110) can store version control and change history for each attached commissioning document in a database. The processor (110) can differentially control upload permissions for commissioning documents based on the role of the user accessing the system. The processor (110) can allow uploading operations of commissioning documents for users in the role of a construction company or manager. For users in the role of a vendor, the processor (110) can allow uploading operations of commissioning documents limited to equipment pre-assigned to the user. On the other hand, the processor (110) can restrict uploading permissions for commissioning documents for users in the roles of a client or operator and grant only viewing and downloading permissions for files. The processor (110) can acquire documents produced during the work process, such as test reports, inspection reports, and checklists performed on-site, as commissioning documents. The processor (110) can upload the corresponding commissioning document to the system in response to the user performing manual operations such as selecting a file on the web screen or dragging and dropping it.

[0108] The processor (110) can obtain an uploaded file in response to a user uploading a file through a web screen. The processor (110) can perform a file verification procedure to check whether the obtained file has an allowed extension and whether the file size is within a preset size (e.g., 500 megabytes). If the file verification procedure is passed, the processor (110) can establish a basis for verifying data integrity by calculating a hash value for the file to generate a unique file fingerprint. Subsequently, the processor (110) can store the original file in a database (e.g., cloud storage). The processor (110) can store file metadata in the database, including Unicode Normalization processing for the filename. If the processor (110) confirms that an existing file exists in the same storage path, it can assign an incremented version to the newly uploaded file. Furthermore, the processor (110) can record the file history regarding the upload and update of the file and preserve it in the database. Afterward, the processor (110) can trigger an action to automatically convert the uploaded original document into a file of a preset format (e.g., a PDF file).

[0109] Additionally, the processor (110) can perform the process of generating a fingerprint, which is a digital fingerprint of the received file. Specifically, the processor (110) can input the entire binary data of the file into a hash function to produce a hash value, which is a fixed-length string of 64 characters, regardless of the file size. For example, the processor (110) can generate a hash value of 64 characters regardless of size. To establish a basis for integrity verification, the processor (110) can determine whether the content of the file has been corrupted due to transmission errors or storage device defects after the file is stored in storage. The processor (110) can guarantee that the file is completely identical to the original by comparing the hash value at the time of file reception with the hash value at a later time, and if the two values ​​match. Furthermore, the processor (110) can prevent unnecessary duplicate storage by identifying that the content is the same file even if the file name is different, provided the hash value is identical. Moreover, the processor (110) can prove through the hash value that the file received at a specific time has not been changed since. Through this, the processor (110) can perform an audit trail process that guarantees the authenticity of documents with legal evidentiary value, such as test reports.

[0110] The processor (110) can assign a unique version number to a file regarding a received commissioning document. If the file is received again at the same location, the processor (110) can increase the assigned version number by a preset number (e.g., 1). The processor (110) can link previous versions of files into a version chain through a parent file reference. Based on the linked version chain, the processor (110) can track the history of which revision of which file the received file is.

[0111] The processor (110) may assign and maintain a display order number for each attached file. The processor (110) may change the sorting order of the files in response to a user inputting a drag-and-drop operation, such as dragging and dropping files with a mouse on a web screen. For example, the user may change the sorting order of the files by dragging and dropping files with a mouse on a web screen. The frontend may receive the user's order change operation and send an order update request containing an array of identifiers for the changed files to the server API. Based on the received order update request, the server API may update the display order number values ​​of each attached file stored in the database. For example, the server API may change the values ​​in the database by updating the display order number of the first file in the identifier array to 0 and the display order number of the second file to 1. When the update of the display order number values ​​is completed, the server API may return an update completion response to the frontend. Based on the received update completion response, the frontend may re-render the file list in the updated order and display it on the user screen. In addition, the server API can directly reflect the updated sorting order in the page layout order when merging files (e.g., PDF files) of the commissioning document. Specifically, the server API can place the file with display order number 0 in the first position of the merged PDF, and then sequentially place the remaining files according to the ascending order of their display order numbers. Through this process of changing the file sorting order, the user can organize a submission document that meets business objectives.

[0112] The processor (110) can convert a document into a preset format (e.g., PDF format) without separate manual operation when a user uploads a document or modifies a document through an external editing system. The processor (110) can merge the converted documents on a per-device basis to create a PDF document for submission. The processor (110) can perform the document conversion and merging process starting from the user's file upload action. The processor (110) can select one of three conversion engines based on the extension of the received file. Specifically, the processor (110) can select the OnlyOffice engine if the file extension is doc, docx, ppt, pptx, xls, or xlsx. Based on the OnlyOffice engine, the processor (110) can convert the document by calling the conversion API of an external document editing server through JSON Web Token (JWT) authentication. Additionally, the processor (110) can select an image conversion engine if the file extension is jpg, png, gif, bmp, or tiff. The processor (110) can convert a file losslessly using a conversion library (e.g., an img2pdf library, etc.) included in the image conversion engine. The processor (110) can select a passthrough method if the file extension is PDF. Since the received file is already in PDF format, the processor (110) can use the original file as is without separate conversion processing.

[0113] For example, the processor (110) can determine the extension of a received file in response to detecting a file upload event. If the determined file extension is Word, Excel, or PPT (PowerPoint), the processor (110) can call the OnlyOffice conversion API including a JWT signature. If the file extension is an image, the processor (110) can perform lossless conversion using a conversion library (e.g., img2pdf). If the file extension is PDF, the processor (110) can determine that separate conversion is unnecessary and apply a passthrough method. Once the conversion or passthrough processing is complete, the processor (110) can save the derived PDF as an individual PDF cache in a database (e.g., cloud storage). At this time, the processor (110) can save the file by assigning an identification key to it. Once the PDF saving is complete, the processor (110) can update the conversion status of the file to a completed state. Next, the processor (110) can merge individual PDFs on an equipment-by-equipment basis using a merge library (e.g., pikepdf library, etc.). When performing the merging process, the processor (110) can determine the order of merging documents based on a location field. Once the merging is complete, the processor (110) can save the merged PDFs to a database (e.g., cloud storage, etc.). When saving the merged PDFs to a database (e.g., cloud storage, etc.), the processor (110) can save them by applying path and filename rules that include slug, phase number (phase N), building, merge folder (merged), equipment identifier (equipment_id), and timestamp information. After saving is complete, the processor (110) can perform cleanup operations on the previously created merged PDFs.

[0114] The processor (110) manages the PDF conversion process of each file using a Finite State Machine (FSM) structure and can track state transitions through the conversion_status item. The processor (110) can manage the initial state, where conversion has not started, as the none state. In response to the completion of the file upload, the processor (110) registers the conversion request in a queue and can transition the file's state from the none state to the queued state. Subsequently, the processor (110) can extract a task from the queue through an asynchronous task processing module and initiate the actual conversion task, thereby transitioning the state from the queued state to the processing state. The processor (110) can transition the state from the processing state to the done state in response to the conversion engine successfully completing the creation of the PDF file. If an error occurs during conversion, the processor (110) can transition the state to the failed state. In this case, even if an error occurs during conversion, the processor (110) can perform a retry process up to a preset number of times (e.g., 2 times). Additionally, the processor (110) can update the status of a file to a canceled state when the conversion is canceled by user operation or system control. When performing a document merge pipeline, the processor (110) can select only files where the value of the conversion_status item is in the done state as merge targets. By excluding files that have not been converted or have failed from the merging process, the processor (110) can prevent incomplete files from being included in the final report. Through this FSM-based selection process, the processor (110) can implement a quality assurance mechanism for the final submission report.

[0115] Furthermore, the processor (110) can perform a reverse transition mechanism to strictly maintain the consistency of the latest combined document in response to a situation where the original file is modified through an external editing system. Specifically, the processor (110) manages the conversion status of individual documents based on Finite State Machine (FSM) logic and can control the state of the document to reverse transition from a conversion completed state to a re-conversion waiting state when a modification event of the original file is detected. Through such reverse transition processing, the processor (110) can immediately invalidate the previously completed conversion results and trigger a re-conversion procedure for a new combined document, thereby ensuring that external editing content of the document is accurately reflected in the final combined report without omission.

[0116] The processor (110) can execute PDF conversion and merging tasks in the background through Celery, which is an asynchronous task queue. The processor (110) supports returning to the web screen immediately after the user uploads a file, and can perform conversion tasks separately on the server. The processor (110) can perform a retry process up to two times if the conversion task fails. Additionally, the processor (110) can set a time limit for the conversion task to 300 seconds. Furthermore, the processor (110) can perform an intermediate conversion process to a newer format, docx, to maintain layout consistency for older Word file formats, such as doc files, and then perform a final conversion to PDF. Through the intermediate conversion process, the processor (110) can output a PDF of the same quality even for older documents.

[0117] The processor (110) can utilize a PDF created by collecting and merging individual document files as the final submission report for the system. The processor (110) can provide a single PDF file by merging individual test reports and inspection reports, etc., sent by a construction company or vendor to a recipient, on an equipment-by-equipment basis. The processor (110) can produce the merged PDF file as a final result for submission to the ordering party. Subsequently, if the processor (110) modifies a document through an external document editing system, the modified file can be stored separately, distinguishing it from the original file. The processor (110) can store the modified file in a database by adding a suffix indicating an edited version to the name of the modified file. The processor (110) can check for the existence of an edited version during the process of generating the merged PDF. If an edited version exists, the processor (110) can perform the document merging process by using the edited version first. On the other hand, if an edited version does not exist, the processor (110) can perform the document merging process by using the original file. The processor (110) can reflect the latest version of the document, which has undergone review and modification steps through this process, in the final report.

[0118] The processor (110) can view a list of individual files attached to the equipment. The processor (110) can determine whether an edited version exists for the viewed individual files. If an edited version exists, the processor (110) can select the edited version having an edited version identification key as the merge target, and if no edited version exists, the original having an original identification key as the merge target. The processor (110) can derive a PDF document by merging the selected files in order based on display sequence numbers. The processor (110) can use the derived merged PDF as a final submission report. Subsequently, the processor (110) can display a preview modal screen to support an administrator in reviewing the merged PDF and processing approval or rejection. Furthermore, the processor (110) can keep the document always up to date by regenerating the merged PDF based on three conditions. First, when a file upload event occurs, the processor (110) can execute individual PDF conversion and full merging in an asynchronous manner immediately upon receipt. Secondly, when a document editing completion event occurs, the processor (110) can regenerate a merged PDF by saving the edits in OnlyOffice and reflecting the edited version. Thirdly, when a file deletion event occurs, the processor (110) can regenerate a merged PDF using the files that remain undeleted. However, if the number of remaining files becomes zero due to file deletion, the processor (110) can delete the previously created merged version.

[0119] The processor (110) can support users in previewing a merged PDF in a modal window on a web screen. When performing the preview process, the processor (110) may obtain a temporary access URL (Uniform Resource Locator) valid for 15 minutes from a database (e.g., cloud storage, etc.) and display it on the screen. The processor (110) can control differential functions based on the user's role within the modal window providing the preview. The processor (110) can provide a PDF preview function for viewing the merged final report to users in the roles of administrator, client, construction company, operator, and vendor. In this case, the processor (110) may allow preview access to users in the vendor role only for the merged PDF of the equipment assigned to the user. Additionally, the processor (110) may provide a function to directly determine approval or rejection of the document within the preview modal window, limited to users in the administrator role. The processor (110) may allow a function to add annotations or write drawings on the PDF document, limited to users in the administrator role. The processor (110) can provide an original file list verification function that displays a list of individual files and page ranges included in the document merge for users in the roles of administrator, client, contractor, operator, and vendor.

[0120] The processor (110) can calculate the progress rate for each equipment unit by analyzing the status of documents according to the criteria for each commissioning stage. The processor (110) can propagate the calculated progress rate to the upper level. In calculating the progress rate, the processor (110) may analyze the existence or attachment status of documents rather than the content of the documents. The processor (110) can calculate the progress rate in the form of a percentage by multiplying the value obtained by dividing the number of equipment with attached test report files in a specific commissioning stage by the total number of equipment participating in that specific commissioning stage by 100. Additionally, the processor (110) can determine the status of the equipment based on specific judgment criteria. If the condition is met that a file serving as a test report is attached to a specific piece of equipment, the processor (110) can determine that the commissioning stage work of the specific equipment is completed and update the status to Completed. If the processor (110) satisfies the condition that a specific piece of equipment is in a completed state and the manager has performed approval processing, it can determine that the manager's approval procedure is also completed and update the status to an Approved state. On the other hand, if the processor (110) does not satisfy the aforementioned conditions, it can determine that the specific piece of equipment is in a state where the test report is not attached and update the status to a Not Completed state.

[0121] Meanwhile, the processor (110) can perform a bottom-up aggregation process to propagate the calculated progress rate from a lower layer to an upper layer. Specifically, the processor (110) can determine whether the status is completed or not based on whether a test report for individual equipment is attached at the equipment unit level. Subsequently, the processor (110) can calculate the completion rate of a group of identical equipment English names at the equipment type unit level. Next, the processor (110) can calculate the completion rate by classification, such as electrical, mechanical, and firefighting, at the category unit level. Then, the processor (110) can calculate the total completion rate for each of the first through sixth stages at the commissioning stage unit level. Afterward, the processor (110) can calculate the progress rate by summing the commissioning stage completion rates for each of the first and second construction stages at the construction stage unit level. Finally, the processor (110) can derive the total progress rate for the entire project by summing the progress rates of all construction stages at the project unit level.

[0122] Additionally, the processor (110) can calculate the approval rate as an additional aggregation item. The processor (110) can calculate the approval rate by multiplying the value obtained by dividing the number of approved equipment by the total number of equipment by 100. Through the aggregation of approval rates, the processor (110) can separately determine the percentage of completion from the attachment of document files to the final approval process by the manager. Furthermore, the processor (110) can perform a separate aggregation process to independently calculate the progress rates of the first construction phase and the second construction phase. The processor (110) can support determining the status of individual construction phases based on the progress rates aggregated separately by construction phase.

[0123] The processor (110) can perform processing to aggregate the progress status of each test stage independently, based on a multi-test stage affiliation structure in which a single piece of equipment can be simultaneously affiliated with multiple test stages. When a test document for a specific piece of equipment is input into the system, the processor (110) can individually reflect the completion status in the computational logic of each of the multiple test stages to which the equipment belongs. Furthermore, in quantifying the progress status of each test stage, the processor (110) can track the submission progress rate, calculated based on whether the target document is simply submitted, and the approval progress rate, calculated based on whether approval has been completed after final review by a manager, by separating them from each other. By applying such a multi-affiliation-based independent aggregation and dual progress tracking mechanism, the processor (110) can provide a three-dimensional quantification of not only the superficial status of document collection but also the actual status of work approval bottlenecks, even in an environment where multiple pieces of equipment are complexly intertwined in multiple processes.

[0124] The processor (110) can acquire all equipment data in bulk through a single database query to simultaneously display multiple project progress rates on a dashboard screen. Subsequently, the processor (110) can perform aggregation operations on the server memory for each project, construction phase, and commissioning test phase based on the acquired equipment data. By preventing the number of database queries from increasing even if the number of projects under management increases through the aforementioned bulk aggregation method, the processor (110) can maintain overall system performance stably.

[0125] The processor (110) can directly or indirectly edit commissioning documents by linking with an external document editing system. Specifically, the backend server can link with a document server, which is an external web-based document editing system, to support users in directly editing commissioning documents such as Word or Excel in a browser. Users can input operations such as clicking a document editing button through the frontend. The frontend can send an editor configuration request to the backend server in response to the received operation. Upon receiving the editor configuration request, the backend server can verify the user's access rights and generate a JWT signature. The backend server can return configuration information including the generated JWT and a document server URL to the frontend. The frontend can load the editor by forwarding the received configuration information to a document server (e.g., OnlyOffice Document server, etc.). The document server can request a file download from the backend server using a proxy URL. The backend server can acquire original or edited files from cloud storage via streaming and deliver them to the document server. The user can edit the document using the editor provided through the document server. After completing the document editing, the user can close the editor or perform a forced save operation. Based on the user's operation, the document server can send a callback to the backend server containing a status value instructing the end of editing or a status value instructing a forced save. In response to receiving the callback, the backend server can download the edited document from the document server. When saving the edited document to cloud storage, the backend server may save it separately by adding a pre-configured term (e.g., the '_edited' suffix) to the filename of the edited version, based on a retention policy that never overwrites the original file.Once the edited version is saved, the backend server can perform a process to invalidate the previously created PDF cache. Subsequently, the backend server can record and maintain an activity log regarding the document editing history.

[0126] The processor (110) can save the edited document as a separate file by adding a pre-set term (e.g., a suffix '_edited') to the original file's save path. The processor (110) can control the process of saving the document so that the original file is not overwritten under any circumstances. Subsequently, the processor (110) can determine whether an edited version exists during the process of querying the file. If the processor (110) confirms that an edited version exists, it can provide the edited version first. On the other hand, if the processor (110) confirms that an edited version does not exist, it can provide the original file.

[0127] The processor (110) may provide document editing permissions differentially based on the user's role. Specifically, the processor (110) may allow full document editing, writing reviews and comments, modifying filters, and protecting sheets for users in the administrator or super administrator role. The processor (110) may allow full document editing for users in the contractor role, but may control the functions of writing reviews and comments, modifying filters, and protecting sheets to be disallowed. The processor (110) may disallow document editing functions for users in the ordering, operating, or vendor roles and provide the document in a read-only state.

[0128] Next, the processor (110) may define a number of supported document formats to provide document editing functions. The processor (110) may support files having doc, docx, odt, and rtf extensions as Word Processor formats. The processor (110) may support files having xls, xlsx, and ods extensions as Spreadsheet formats. The processor (110) may support files having ppt, pptx, and odp extensions as Presentation formats.

[0129] The processor (110) can analyze time-series data including the results of tests on equipment (e.g., performance tests, etc.) and output it as a chart to provide to the user. Specifically, the processor (110) can analyze time-series data collected from data center cooling performance tests and output it as a chart. The data analyzed by the processor (110) may be time-series data measured by sensors installed in cooling facilities at the data center site. The processor (110) can receive raw data organized by field personnel in the form of an Excel file, etc., on a project basis through a web screen. The processor (110) can grant file reception rights to all logged-in users. The processor (110) can preserve the received Excel file in its original state in a dedicated project path in S3, a cloud storage. The processor (110) can use the time-series sensor data within the received Excel file as the subject of analysis. The processor (110) can analyze the items recorded in each of the six sheets included in the Excel file. Specifically, the processor (110) can analyze the cooling capacity of cooling equipment in units of kW (Kilowatt) on the cooling capacity sheet. The processor (110) can analyze the power consumption of IT equipment in units of kW on the IT (Information Technology) load sheet. The processor (110) can analyze the cooling water flow rate in units of LPM (Liter Per Minute) on the flow rate sheet. The processor (110) can analyze the cooling water inlet temperature (inlet_temp) in units of Celsius (°C) on the inlet temperature sheet. The processor (110) can analyze the cooling water outlet temperature in units of °C on the outlet temperature sheet. The processor (110) can analyze the difference between the inlet temperature and the outlet temperature in units of °C on the temperature difference sheet.In addition to this, the processor (110) can analyze various types of input time series data and output the analysis results to the user in the form of a chart.

[0130] As a specific example, the processor (110) may receive an Excel file having an xlsx or xls extension. The processor (110) may save the received document as an original file to a designated path in cloud storage (e.g., S3, etc.). Subsequently, the processor (110) may parse six sheets within the document using an analysis library (e.g., pandas library, etc.). The processor (110) may perform the process of extracting a time column from the parsed data and converting it into a datetime format. The processor (110) may perform sampling on the data with the time format converted at intervals of 5 minutes, i.e., 300 seconds. The processor (110) may extract data by classifying it by CA (Cooling Area) from the sampled data. Based on the extracted data, the processor (110) may calculate statistical values ​​including the average, maximum, and / or minimum. Once the calculation of statistical values ​​is complete, the processor (110) may convert the calculated data into JSON format. The processor (110) stores the converted JSON data in a cache form in cloud storage and can apply specified filename rules. Afterwards, the processor (110) can provide the stored JSON data to the frontend to control visualization as a time-series chart on the screen.

[0131] The processor (110) can receive user operations to add interval annotations and text memos to a chart derived from the analysis results. The processor (110) can provide a function to customize the title of the chart based on the user operations. The processor (110) can save the added annotation data as a separate JSON file in cloud storage. The processor (110) can subsequently restore the annotations on the chart based on the stored JSON file in response to an event that retrieves the file again.

[0132] The processor (110) defines six user roles and can apply permissions differentially for file access, commissioning level (CxLevel) access, equipment management, and editing functions for each role. The processor (110) can classify user roles into a Super Admin, who holds all permissions as the overall system administrator; an Admin, who holds most permissions as the project manager; a Client, who has permissions focused on viewing and downloading; a Contractor, who has permissions focused on uploading and editing files; an Operator, who has permissions focused on viewing and downloading files; and a Vendor, who has upload permissions limited to assigned equipment. The processor (110) can control detailed permissions for each role based on a permission matrix. The processor (110) can grant common permissions for file downloading and file viewing to all user roles. The processor (110) can allow permissions for file uploading, file editing, equipment registration, cell editing, and PDF annotation addition for the Super Admin, Admin, and Contractor roles. The processor (110) may grant file deletion and equipment deletion permissions limited to the Chief Administrator and Administrator roles. The processor (110) may provide a file upload function limited to equipment pre-designated by the administrator for the Vendor role. In this case, the processor (110) may manage the list of accessible equipment for the Vendor in a format of full equipment access or a format of a list of specific equipment names and actual equipment classifications. Furthermore, the processor (110) may set different access ranges for the commissioning stage (or testing stage) depending on the user role. Specifically, the processor (110) may allow access to the range from Stage 0 (CxL0) to Stage 7 (CxL7) for the Chief Administrator and Administrator roles.The processor (110) may provide access to Level 0 (CxL0) limited to the Chief Manager and Manager roles. The processor (110) may allow access to the range from Level 1 (CxL1) to Level 7 (CxL7) for the Client and Operator roles. The processor (110) may restrict access rights to the range from Level 1 (CxL1) to Level 3 (CxL3) for the Construction Company and Vendor roles.

[0133] The processor (110) can acquire a file in response to a user inputting an operation to upload a file on a web screen. The processor (110) can perform a file verification procedure to check whether the acquired file has an allowed extension and whether the file size is within an allowed size (e.g., within 500 megabytes). If the file verification procedure is passed, the processor (110) can establish a basis for integrity verification by calculating a hash value for the file to generate a unique file fingerprint. The processor (110) can store the original file in S3, a cloud storage. The processor (110) can store file metadata in a database, including Unicode normalization processing for the filename. If the processor (110) confirms that an existing file exists in the same storage path, it can assign an incremented version to the newly uploaded file. The processor (110) can record and preserve a file history regarding file uploads and updates. Subsequently, the processor (110) can initiate an operation to convert the uploaded original document into a PDF file.

[0134] Additionally, the processor (110) can dynamically control the buttons displayed on the screen and the functions within the modal according to the user role. By not displaying buttons for functions for which the user is not authorized on the screen, the processor (110) can fundamentally block operations that do not match the role. For users in the Super Administrator and Administrator roles, the processor (110) can provide a file upload button, merged PDF preview, full PDF download, file delete button, individual file editing, approval and rejection toggles within the preview modal, PDF annotation and drawing within the preview modal, and file order change functions. For users in the Orderer and Operator roles, the processor (110) can provide only the merged PDF preview and full PDF download functions in a limited manner. For users in the Construction Company role, the processor (110) can provide a file upload button, merged PDF preview, full PDF download, individual file editing, PDF annotation and drawing within the preview modal, and file order change functions. For users in the Vendor role, the processor (110) can provide a file upload button, merged PDF preview, and file delete button functions. The processor (110) can display function buttons on the screen for users in the vendor role, limited to equipment pre-designated by the administrator. The processor (110) can control so that a file delete button is not displayed on the screen for equipment that is in an approved state. The processor (110) can display individual file edit buttons on the screen, limited to files in Word, Excel, and PowerPoint formats. The processor (110) can control the approval and rejection of documents to be performed only within the merged PDF preview modal. The processor (110) can display approval and rejection toggles, limited to users in the super administrator and administrator roles. Through the screen control process described above, the processor (110) can enforce a workflow in which the administrator directly checks the merged PDF, which is the final report, and then determines whether to approve it.

[0135] The processor (110) can individually designate the equipment accessible to users in the vendor role based on the administrator's input operations. The processor (110) may receive a selection of one of two setting modes as the equipment access scope for vendor users on the user registration or modification screen. If the processor (110) receives a selection of the all-equipment access mode, which allows access to all equipment in the project, it may maintain the storage format by designating it as an array containing "all". If the processor (110) receives a selection mode for specific equipment only, where the administrator designates the equipment English names one by one, it may configure and preserve the storage format as an array containing the designated equipment English names.

[0136] The processor (110) can check the user's accessible equipment settings in response to receiving a request to view the equipment list from a user in the vendor role. If the processor (110) confirms that the accessible equipment settings are all equipment access, it can display upload and preview buttons for all equipment on the screen. If the processor (110) confirms that the accessible equipment settings are only specific equipment selection, it can individually determine the accessibility of each row of the equipment list. The processor (110) can display upload, preview, and delete buttons for items determined to be accessible equipment. Conversely, the processor (110) can hide all operation buttons for items determined to be inaccessible equipment. If there are no accessible equipment settings, the processor (110) can restrict access by hiding all buttons.

[0137] Additionally, the processor (110) can store a list of accessible equipment in a database in a format combining the English name of the equipment and the facility classification. When displaying the list of equipment on the screen, the processor (110) can determine whether access is possible on a row-by-row basis by comparing the English name of the equipment in each row with the stored list. Furthermore, the processor (110) can perform a project isolation process that allows access only to equipment of the project to which the user in the vendor role belongs, and blocks access to equipment of other projects to which the user does not belong. The processor (110) can perform additional equipment-unit control processes within the scope to which the project isolation process is applied.

[0138] The processor (110) may apply a cache policy in units of a preset time (e.g., one hour) to optimize the processing performance of the authority lookup process. For example, when an event occurs where authority is looked up for the first time, the processor (110) may look up the authority corresponding to the user type from the database and temporarily store it in memory. Subsequently, if the processor (110) receives a request to look up authority for one hour after the initial lookup is performed, it may control the return of the result temporarily stored in memory. Through this process, the processor (110) can effectively reduce the system load caused by accessing the database every time authority is looked up.

[0139] The processor (110) can manage the design documents for the project's Phase 0 (CxL0) exclusively for administrators. The processor (110) can systematically preserve and manage the design documents through a virtual folder structure. The processor (110) can process the Phase 0 design documents by applying criteria that distinguish them from general equipment documents corresponding to Phase 1 (CxL1) through Phase 7 (CxL7). Specifically, unlike general equipment documents which must be managed by connecting them to specific equipment, the processor (110) can manage Phase 0 design documents as independent documents that exclude connection to equipment. While the processor (110) controls access to general equipment documents according to the Commissioning Level (CxLevel) range for each role, it may allow access to Phase 0 design documents only for Super Admin and Admin roles.

[0140] Additionally, the processor (110) can apply an approval workflow to general equipment documents that transitions from a pending state to an approved or rejected state. On the other hand, the processor (110) can manage documents without going through a separate approval workflow based on the fact that the zero-stage design documents correspond to an area for administrators only. The processor (110) can automatically generate a folder structure for general equipment documents based on equipment data, while classifying zero-stage design documents through a virtual folder structure based on file paths. The processor (110) can apply the original category of equipment as the default category of general equipment documents. Alternatively, the processor (110) can provide Electrical, Mechanical, Fire, Commissioning Plan (Cx Plan), and Commissioning Report (Cx Report) items as fixed default categories of zero-stage design documents.

[0141] Furthermore, the processor (110) may operate a virtual folder system to implement the folder structure of the zero-stage design document. The processor (110) may not create actual folders in cloud storage. Instead, the processor (110) may support displaying folders on the screen based on relative path information contained in each file. The processor (110) may minimize storage operation costs by processing control operations related to the creation, deletion, and renaming of folders at the database level.

[0142] The processor (110) can provide a function to display annotations and / or drawings on a merged commissioning document (e.g., a PDF document). The processor (110) can control the replacement of a paper document-based review and feedback process with a digital environment by supporting a read-only display function for the document. The processor (110) can utilize a data structure containing multiple items to systematically manage annotation data. Regarding the location item of an annotation, the processor (110) can implement a responsive system that responds to changes in screen resolution or size by storing page-based x and y coordinate information in percentage (%) units. Regarding the content item of an annotation, the processor (110) can acquire and maintain text-based comment data. Regarding the author item of an annotation, the processor (110) can automatically record and preserve user information that entered the annotation. Regarding the page number item of an annotation, the processor (110) can match and store the corresponding page index information within the merged PDF. Additionally, the processor (110) can support a drawing function that adds visual markings on the document. The processor (110) can provide pen and highlighter functions as detailed tools for drawing. The processor (110) can convert coordinate array data derived according to the user's drawing operations into JSON format and store it. The processor (110) can manage drawing data separated by page by creating and applying independent drawing layers for each page of the document.

[0143] The processor (110) can provide a function to manage announcements created by an administrator by type and target. The processor (110) can directly receive input from a user with the Super Admin or Admin role through a web screen, including items such as the content, type, target range, and whether to display a popup of the announcement. The processor (110) can classify and apply multiple announcement types according to the purpose of the announcement. Specifically, the processor (110) can designate a general announcement type to deliver general information. The processor (110) can designate an important announcement type to highlight and display important information on the screen. The processor (110) can designate an urgent announcement type to pin and display urgent information at the top of the screen. The processor (110) can designate a system maintenance type to provide information on system maintenance schedules. The processor (110) can designate an update type to provide information on system updates. Additionally, the processor (110) can control the exposure target by setting the target range to receive the announcement. The processor (110) can set an overall target range to display notices to all users within the system. The processor (110) can set a role-specific target range to display notices only to users of specific roles, such as administrators or contractors. The processor (110) can set a company-specific target range to display notices only to users belonging to a specific company involved in a specific project. The processor (110) can set a user-specific target range to display notices by directly designating individual users. Furthermore, the processor (110) can control the display of notices on the screen in a pop-up form based on input operations by an administrator. The processor (110) can receive and maintain a display period including a start date and an end date.The processor (110) can perform a process to automatically disable the exposed notice in response to the condition that the set display period has elapsed.

[0144] The processor (110) can record major activities occurring within the system without separate manual operation and utilize them for auditing and history management. The processor (110) may include the performing user, the time of execution, the target item, and the connected IP address as the information to be recorded. The processor (110) can define types of activities to be tracked based on various classifications. Specifically, the processor (110) can track file uploads, file downloads, file deletions, and ZIP format downloads for folders as activity types related to files. The processor (110) can track the creation of notices, modification of notices, and deletion of notices as activity types related to notices. The processor (110) can track equipment registration, modification of equipment, deletion of equipment, and bulk registration of equipment in Excel as activity types related to equipment. The processor (110) can track cell editing of the OnlyOffice engine as activity types related to document editing. The processor (110) can track login, logout, user creation, and user information modification as types of activities related to the user. The processor (110) can track orderer creation and orderer modification as types of activities related to the orderer. Additionally, the processor (110) can perform an aggregation optimization process for log data. The processor (110) can monitor whether the same user performs repetitive tasks, such as file uploads or file downloads. If the condition is met where the same user repeatedly performs the same type of task from the same IP address within 5 minutes, the processor (110) can aggregate by increasing the count of existing logs and adding them to a list of target filenames instead of creating a new log every time. Through this optimization method, the processor (110) can prevent the phenomenon of log data increasing excessively during large-scale operations by aggregating logs as a single count even if multiple files are uploaded consecutively.

[0145] Furthermore, the processor (110) may apply a differentiated log retention policy based on the type of activity. The processor (110) may set a short retention period of a pre-configured first period (e.g., 30 days) for frequently occurring file download and folder download activities. The processor (110) may set a retention period of 90 days for login and logout activities intended for tracking access history. The processor (110) may set a pre-configured second period (e.g., 180 days) for equipment modification, announcement creation, modification, and deletion activities intended for tracking change history. The processor (110) may set a pre-configured third period (e.g., 365 days) for file upload, file deletion, user creation and modification, equipment registration, equipment bulk registration, and orderer creation and modification activities that require long-term retention as core audit history. The processor (110) can set a default retention period of a pre-set fourth period (e.g., 180 days, etc.) for other activities including cell editing.

[0146] Next, the processor (110) can perform automatic cleanup operations on log data that has exceeded its retention period at a designated time every day. In addition, when the condition is met that the total number of log records exceeds a preset threshold (e.g., 50,000 records), the processor (110) can efficiently manage storage space by performing cleanup operations sequentially starting from the oldest.

[0147] For example, the processor (110) can manage the history of the system by applying a differentiated log retention policy based on the type of activity. The processor (110) can set a short retention period of 30 days for frequently occurring file download and folder download activities. The processor (110) can set a retention period of 90 days for login and logout activities for the purpose of tracking access history. The processor (110) can set a retention period of 180 days for equipment modification, announcement creation, modification, and deletion activities for the purpose of tracking change history. The processor (110) can set a retention period of 365 days for file upload, file deletion, user creation and modification, equipment registration, equipment bulk registration, and orderer creation and modification activities that require long-term retention as core audit history. The processor (110) can set a basic retention period of 180 days for other activities including cell editing. The processor (110) can automatically perform cleanup operations on log data that has exceeded the set retention period at dawn every day. In addition, the processor (110) can efficiently manage storage space by performing cleanup operations sequentially starting from the oldest when the condition is met that the total number of log records exceeds 50,000.

[0148] The processor (110) can receive an operation to upload equipment data in bulk based on Excel from a user in the role of an administrator or a construction company. The processor (110) can create a folder structure in response to the bulk upload of equipment data. Additionally, the processor (110) can support downloading a list of registered equipment in Excel file format.

[0149] When registering Excel files in bulk, the processor (110) can perform a smart column mapping process that automatically corresponds to system items by performing keyword-based similar matching on column names, which are column titles of the Excel files. For example, the processor (110) can recognize the same system item based on matching keywords even if the column titles of the Excel files are written in various expressions.

[0150] Specifically, the processor (110) can automatically recognize an equipment identifier (tag) item if the column title includes any one of equipmentid, tag, tag, equipment number, and equipmentno, but can exclude it from matching if it includes the exclusion keyword group. The processor (110) can automatically recognize an equipment English name (equipment_en) item if the column title includes any one of equipment, equipment name, equipment, facility, and name, but can exclude it from matching if it includes the exclusion keywords id and spec. The processor (110) can automatically recognize an facility classification (original_category) item if the column title includes any one of category, classification, category, and discipline. The processor (110) can automatically recognize a manufacturer or vendor item if the column title includes any one of vendor, vender, manufacture, supplier, manufacturer, vendor, and supplier. And, the processor (110) can automatically recognize a specification (spec) item if the column title includes any one of spec, specification, specification, and standard. The processor (110) can automatically recognize a construction phase item if the column title includes any one of phase, stage, and construction. The processor (110) can automatically recognize a building code item if the column title includes any one of building, bldg, and building. The processor (110) can automatically recognize a location or zone (zoning) item if the column title includes any one of location, zoning, zone, area, area, location, and place. The processor (110) can automatically recognize a purpose item if the column title includes any one of purpose, usage, usage, and purpose.The processor (110) can automatically recognize a column title as a remark item if it includes any one of remark, note, comment, remark, and memo. The processor (110) can automatically recognize a column title as a commissioning stage participation (lv_01 to lv_07) item if it includes any one of cxl1 to cxl7, lv01 to lv07, cx1 to cx7, and level1 to level7. Through this smart column mapping process, the processor (110) can automatically import equipment data without a separate setting process, even if Excel files of various formats are input.

[0151] Additionally, the processor (110) may apply an exclusive lock (Advisory Lock) function at the project level to ensure data consistency when multiple users simultaneously execute equipment batch registration for the same project. If the processor (110) receives a batch registration request from another user for the same project while one user is in the process of batch registration for a specific project, the processor (110) may control the other user's request to be switched to a waiting state. Through this exclusive lock processing, the processor (110) can effectively prevent data conflicts that may occur during the batch registration process.

[0152] Additionally, the processor (110) may apply a policy that does not unconditionally overwrite or delete existing data during the process of registering equipment in bulk. The processor (110) may determine whether an equipment identifier (tag) identical to the equipment subject to bulk registration already exists in the database. If the processor (110) confirms that an identical equipment identifier already exists, it may perform a process to update the information of the equipment in the existing data. On the other hand, if the processor (110) confirms that an identical equipment identifier does not exist, it may perform a process to newly register the equipment. By applying an upsert method that combines updating and new registration in this manner, the processor (110) can fundamentally prevent data loss that may occur when registering equipment data in bulk.

[0153] The processor (110) can verify whether there is a match by comparing the actual files stored in cloud storage with the file information recorded in the database, and can manage synchronization on a project or company basis. The processor (110) can maintain data consistency within the system by detecting cases where the actual file is deleted even though it is recorded in the database, or where the actual file exists but is not recorded in the database. In this regard, the processor (110) can separate and process large files received from users and metadata associated with those files. The processor (110) can store unstructured data, including text, images, videos, or document objects, in cloud storage where storage space expansion is easy. In parallel, the processor (110) can record and maintain structured information, including filenames, creation timestamps, and access rights, and identification information indicating the storage location on the cloud storage, in a relational database.

[0154] Additionally, the processor (110) can apply NFC Unicode normalization to filenames and paths. The processor (110) can control the phenomenon where the same Korean characters are internally expressed differently depending on the environment of an operating system (OS), such as Windows or macOS, or cloud storage. By unifying the method of storing characters combined into a single character and the method of storing characters separated into consonants and vowels into a single standard form through NFC normalization, the processor (110) can fundamentally prevent the phenomenon of omission that occurs during file search.

[0155] Next, the processor (110) can perform a priority lookup using a path to which NFC normalization is applied when looking up a file. If the processor (110) determines that the file cannot be found in the normalized path, it can apply a two-stage fallback process to re-lookup using the original path.

[0156] The processor (110) can minimize the time required for document search by providing an integrated search function targeting equipment and document files. In response to receiving a search term from a user, the processor (110) can perform a search that derives all results containing the entered search term based on a partial match method. When the processor (110) sets a file as the search target, it can apply the file title, file name, folder path, equipment classification, and commissioning stage as detailed search items. In parallel, when the processor (110) sets a project as the search target, it can apply the project name and project description as detailed search items. Additionally, to prevent the phenomenon where search targets are omitted due to differences in Unicode encoding of Korean file names during the search process, the processor (110) can use fields that have completed NFC normalization processing as search targets. Subsequently, the processor (110) can control the integrated return of the file list and project list derived as search results into a single response.

[0157] The processor (110) can provide a multi-stage drill-down inquiry function on the dashboard that allows for progressively viewing detailed information from the progress rate of the entire data to lower levels. Specifically, the processor (110) can display a project dashboard on the screen at Level 0 to provide summary information on the overall progress rate of all projects. Depending on user operation, the processor (110) can enter the lower level, Level 1, to provide an overview of the Commissioning Level (CxLevel). At Level 1, the processor (110) can display on the screen the total number of equipment, the number of completions, and the progress rate corresponding to each level from Level 1 (CxL1) to Level 7 (CxL7). Subsequently, the processor (110) can enter Level 2 to provide the status by equipment classification. The processor (110) can derive and display the progress rate for Electrical, Mechanical, and Fire equipment within the selected Commissioning Level. The processor (110) can enter Level 3 and provide detailed information by equipment type. The processor (110) can calculate and output the number of equipment, the number of completions, and the progress rate for each individual equipment type within a selected category. Furthermore, the processor (110) can enter Level 4 and provide a list of individual equipment. The processor (110) can provide guidance on whether a file is attached and the approval status for individual equipment belonging to the selected equipment type.

[0158] Additionally, the processor (110) can verify the authority assigned to the user's role in each of the multi-stage drill-down steps. Based on the verified authority, the processor (110) can dynamically control the scope of data exposure by automatically filtering the projects and commissioning steps accessible to the user.

[0159] The processor (110) can provide a customized dashboard on the screen optimized for each user role, including the client, contractor, and operator. The processor (110) can provide summary information and visualization information regarding the progress rate of each commissioning stage through the dashboard. Specifically, the processor (110) can provide the integrated progress rate of the entire project and detailed information on individual projects for the Super Admin and Admin roles. The processor (110) can provide the progress rate of its own projects and carousel visualization information for each commissioning stage for the Client role. The processor (110) can provide information on the file upload status from the first stage (CxL1) to the third stage (CxL3) of the project in charge for the Contractor role. The processor (110) can provide a dashboard in a format that allows the Operator role to view the overall progress rate of the project in charge.

[0160] Furthermore, the processor (110) can provide intuitive information to the user by placing visualization widgets, such as recent system activity history, a summary of announcements, and a donut chart of commissioning stages, on the dashboard.

[0161] The processor (110) may provide the ability to automatically send in-app notifications and emails in response to detecting changes in the status of work progress. The processor (110) may control the type of notification, the recipients, and whether to send emails based on preset trigger conditions. Specifically, when the condition that the upload of a specific equipment type is 100% completed is met, the processor (110) may send a notification and email regarding the completion of the equipment upload to the Admin as the recipients. When the condition that the entire upload of a specific commissioning step is 100% completed is met, the processor (110) may send a notification regarding the completion of the step upload only in an in-app format to the Admin as the recipients. Additionally, when the condition that the approval of a specific equipment type is 100% completed is met, the processor (110) may designate the Admin and the Vendor as recipients, send an in-app notification to the Admin, and send a notification regarding the completion of the equipment approval to the Vendor, including an email. When the processor (110) satisfies the condition that the waiting status of a specific equipment type becomes 0 and processing is 100% complete, it may send an email and notification regarding the completion of equipment processing, including a list of rejections, to the vendor as the recipient. When the processor (110) satisfies the condition that the total approval of a specific commissioning stage is 100% complete, it may provide a notification regarding the completion of the stage approval only in an in-app format to the administrator as the recipient. Subsequently, when the processor (110) satisfies the condition that an approval judgment for an individual file is entered, it may send a notification and email regarding file approval to the user as the recipient. When the processor (110) satisfies the condition that a rejection judgment for an individual file is entered, it may send a notification and email regarding file rejection to the user as the recipient.If the conditions for creating a notice are met, the processor (110) can provide a notification regarding the creation of a notice without sending an email to all or designated recipients.

[0162] Furthermore, the processor (110) can perform a duplicate notification prevention process at the time a notification occurs. The processor (110) can apply a database row locking technique to control that other processes do not access the same target until one process is completed. In addition, the processor (110) can perform a history comparison process for notifications that have already been sent. Through this process, the processor (110) can ensure that the same notification is not sent duplicately, even if a situation occurs where multiple users simultaneously upload or approve files.

[0163] Regarding the email sending structure, the processor (110) can send emails in a background environment by calling an external mail service using Celery, an asynchronous task queue. For example, the processor (110) can handle the email sending process by integrating with the Hiworks Representational State Transfer API (REST API). The processor (110) can control that in-app notifications within the system are provided and maintained normally even if a situation occurs where email sending fails due to communication failures, etc. Independently, the processor (110) can classify and track the email sending status into a number of pre-configured types. If email sending is unnecessary, the processor (110) can record the sending status as 'none'. If email sending is pending, the processor (110) can identify the sending status as 'pending'. If email sending is successfully completed, the processor (110) can update the sending status to 'sent'. The processor (110) can update the sending status to 'failed' if the email sending fails. The processor (110) can update the sending status to 'skipped' if the sending is omitted due to reasons such as the user's refusal to receive. Additionally, the processor (110) can individually support settings regarding whether to consent to receive emails for each user. The processor (110) immediately blocks the sending of emails on the system for users who have set themselves to refuse to receive, and can clearly manage the sending history by processing the sending status of the corresponding email as 'skipped'.

[0164] The processor (110) can provide a three-step workflow in which an administrator approves or rejects an uploaded document. The processor (110) can set the approval status of the document to a pending approval state in response to detecting an event where a file is uploaded. When the processor (110) receives an approval input from an administrator for a document in a pending approval state, it can transition the approval status of the document to a completed approval state. As the document transitions to a completed approval state, the processor (110) can record and preserve data regarding the approver and the date and time of approval. Alternatively, when the processor (110) receives a rejection input from an administrator for a document in a pending approval state, it can transition the approval status of the document to a rejected state. As the document transitions to a rejected state, the processor (110) can record and preserve data regarding the rejecter and the date and time of rejection.

[0165] Furthermore, the processor (110) can support a reset function during the transition process of the approval status. The processor (110) can determine whether the conditions for a file that already has an approval completed state or a rejection state to be re-uploaded to the system are met. If the processor (110) confirms that the file is being re-uploaded, it can automatically reset the existing approval status to an approval waiting state. By inducing a re-approval procedure by the administrator through such an automatic reset process, the processor (110) can fundamentally prevent a data inconsistency situation where the previous approval status is unfairly maintained even though the document content has been newly changed.

[0166] The processor (110) can provide a Smart Upload function that recognizes and connects specific equipment and commissioning stages based solely on filenames in an environment where multiple test report files are uploaded at once. Unlike the conventional method in which a user directly selects an equipment and uploads files one by one to the corresponding equipment during the file assignment process, the processor (110) can perform processing to automatically assign files to target equipment by automatically extracting the commissioning stage and equipment identifier from the received filenames. Furthermore, the processor (110) can eliminate the constraint that repetitive upload operations are required for each target piece of equipment during the bulk upload process. In response to a user inputting an operation to upload tens to hundreds of files to the system at once, the processor (110) can control the automatic distribution of each file to appropriate paths and equipment items based on internal logic. Moreover, during the error handling process, if the processor (110) detects an event where automatic matching fails, it can immediately display the reason to the user. The processor (110) can guide the user to take action by providing real-time guidance on specific reasons for matching failure, including failure to recognize the commissioning stage or equipment mismatch, on the screen to resolve existing problems where it is difficult to quickly detect errors when the user manually assigns files incorrectly.

[0167] The processor (110) can perform an automatic matching algorithm in response to receiving an operation from a user to upload multiple files at once. The processor (110) can extract a Commissioning Level (CxLevel) pattern indicating a first level (CxL1) or a second level (CxL2), etc., from each uploaded filename. The processor (110) can determine whether it succeeded in recognizing the commissioning level from the filename. If the processor (110) confirms that the commissioning level recognition failed, it can add the file to a Skip list and record the reason as "no commissioning level information." On the other hand, if the processor (110) confirms that the commissioning level recognition succeeded, it can query a list of equipment participating in the recognized commissioning level. Subsequently, the processor (110) can perform a process of sorting the equipment identifiers (Tags) included in the queryed list of equipment in order of longest name. The processor (110) can search for whether a matching equipment identifier exists within a filename based on a list of equipment identifiers sorted in order of long names.

[0168] The processor (110) can determine whether it has succeeded in matching the equipment identifier in the filename. If the processor (110) determines that the equipment matching failed, it can add the file to the skip list and record the reason as "equipment tag mismatch." On the other hand, if the processor (110) determines that the equipment matching was successful, it can automatically attach the file to the derived equipment. Once the file attachment is complete, the processor (110) can initialize the approval status of the file and trigger a PDF conversion operation.

[0169] Furthermore, the processor (110) may apply a long name first matching method to prevent mismatching caused by inclusion relationships between identifiers. For example, when the processor (110) processes a filename 'CxL1_ATS-001_report.pdf' in a situation where both equipment identifiers 'ATS-001' and 'ATS' exist, the processor (110) can control the phenomenon where 'ATS' is matched first and assigned to the wrong equipment. By controlling the processor (110) to attempt matching first with the identifier 'ATS-001', which has a longer number of characters, the processor (110) can ensure that the file is assigned to the correct target equipment without error.

[0170] The processor (110) may provide a comprehensive result report to the screen as feedback on the matching results in response to the completion of the bulk upload process for the file. The processor (110) may provide the user with information by calculating the number of successes, the number of failures, the number of skips, and the reasons for skipping as detailed items constituting the result report.

[0171] Specifically, the processor (110) can count the number of files that are successfully automatically matched and uploaded to the target equipment as the number of successes. The processor (110) can count the number of files that are stopped from processing due to an error occurring during the file upload process as the number of failures. The processor (110) can count the number of files that are skipped from uploading due to a failure in automatic matching as the number of skips.

[0172] Furthermore, the processor (110) can derive and display specific reasons for skipping each skipped file. The reasons for skipping provided by the processor (110) may include detailed information regarding causes such as failure to recognize the commissioning stage, equipment mismatch, and upload failure. By providing such specific result feedback, the processor (110) can support the user in intuitively understanding the upload status of all files and promptly taking follow-up actions for files that are missing or have errors.

[0173] The processor (110) can apply an automatic separation and re-summation mechanism for commissioning stages. When multiple commissioning stages are displayed together in a single equipment row within an Excel document, the processor (110) can automatically separate them by commissioning stage and store them as independent database records. In parallel with this, the processor (110) can perform a bidirectional conversion process to restore the original single-row form by inversely summing the separated records during the process of downloading the equipment list into an Excel document.

[0174] When importing equipment data, the processor (110) can perform a fan-out process that separates one row of data into multiple (N) records. Specifically, the processor (110) can create an independent record for each commissioning step indicated by a specific identifier (e.g., "O") indicating participation among the items from the first step (CxL1) to the seventh step (CxL7) included in the Excel row. At this time, the processor (110) can apply a separation criterion through a separation module to set only the items of the corresponding commissioning step within each record to True and the remaining items to False. For example, an Excel row in which the equipment identifier (tag) is 'UPS-001', the first and second steps (CxL2) are indicated as "O", and the third step (CxL3) is indicated as "X" can be input into the system. In this case, the processor (110) can individually derive and generate a first record in which only the first stage item (lv_01) is set to true and the remaining items are set to false, and a second record in which only the second stage item (lv_02) is set to true and the remaining items are set to false. Through this separation mechanism, the processor (110) can independently preserve and manage the attachment status of files, the approval status of documents, and the progress rate of work for each commissioning stage. Based on the separated records, the processor (110) can individually identify and accurately track detailed progress statuses, such as when the work of the first stage corresponding to factory testing is completed, while the work of the second stage corresponding to installation inspection is incomplete, even for the same equipment.

[0175] The processor (110) can perform a merge process to combine multiple records into one row during the process of exporting equipment data. Specifically, the processor (110) can identify database records having the same equipment identifier (tag) and perform a logical OR operation on the commissioning step values ​​of the identified records. As a result of the logical OR operation, the processor (110) can apply a summing rule to finally assign a true value to the commissioning step where any one of the multiple records has a true value.

[0176] For example, the processor (110) can merge a first database record in which the equipment identifier is 'UPS-001' and the second stage (CxL2) item (lv_02) is set to true, and a second database record in which the same equipment identifier is set to true and the third stage (CxL3) item (lv_03) is set to true. The processor (110) can restore and output the data in the form of the original Excel 1 row in which the first stage (CxL1) is marked as "X" and the second and third stages are marked as "O" as a result of passing through the summing module.

[0177] Additionally, the processor (110) may utilize a key combination to determine whether records are identical during the process of upsertting separated equipment data. The processor (110) may determine whether the data is identical based on a combination of five items including construction phase, building code, test phase, category, and equipment identifier.

[0178] If the processor (110) confirms that an existing record exists in the database that matches all five items with the received equipment data, it can perform a process to update the information of that record. On the other hand, if the processor (110) confirms that an existing record does not exist in the database that matches all five items, it can perform a process to newly register the data. By applying these five-item-based identity determination criteria, the processor (110) can fundamentally prevent the phenomenon of duplicate data registration when an Excel document is re-uploaded to the system, even under a data structure where a single piece of equipment is separated into a separate record and managed independently at different commissioning stages.

[0179] The processor (110) can apply a hierarchical folder filtering system based on authority when displaying a folder tree structure. The processor (110) can apply a differential filtering method by layer, which selects and displays only the commissioning level (CxLevel) that is allowed access according to the user's role, while completely preserving category and equipment data belonging to the lower layer of the corresponding commissioning level without performing filtering. The processor (110) can perform control that is differentiated from general filtering methods, which can cause data loss by applying the same filter to all layers and removing all lower-level data if the conditions are not met. By applying filters of different depths to each layer and completely preserving the lower-level data of the commissioning level regardless of filter conditions, the processor (110) can guarantee 100% integrity of the data existing within the scope of access authority.

[0180] For example, the processor (110) may configure a hierarchical structure leading to construction phases, buildings, commissioning phases, categories, and equipment in order to perform filtering operations. The processor (110) may perform processing that allows the construction phase and building layers to pass through without separate filtering. Subsequently, the processor (110) may perform filtering on the commissioning phase layer based on the user's authority. If the processor (110) confirms that the user is allowed access to a specific commissioning phase, it may provide the category and equipment items under that commissioning phase on the screen by fully preserving them without filtering. On the other hand, if the processor (110) determines that the user is not allowed access to a specific commissioning phase, it may block exposure by completely removing the folder of that commissioning phase from the tree structure. Furthermore, the processor (110) may differentially assign the range of accessible commissioning phases based on the user's role. The processor (110) can display the entire commissioning stages from Stage 0 (CxL0) to Stage 7 (CxL7) on the screen for the Super Admin and Admin roles, who have administrative authority over the entire system. For the Client and Operator roles, the processor (110) can display the commissioning stages from Stage 1 (CxL1) to Stage 7 on the screen, excluding Stage 0, based on the fact that the Stage 0 design document is an area exclusively for the administrator. For the Contractor and Vendor roles, who are involved only in construction and delivery procedures, the processor (110) can limit access to the commissioning stages from Stage 1 to Stage 3 (CxL3) and display only the relevant information on the screen.

[0181] The processor (110) can control the sending of notifications by applying a three-stage state transition model based on progress, moving away from a simple condition check method. By controlling the sending of notifications to be limited to the time when each state transitions, the processor (110) can fundamentally prevent the phenomenon of duplicate notifications occurring.

[0182] Specifically, the processor (110) can operate a state transition model for equipment data. The processor (110) can transition from an initial state, which is an incomplete upload state, to an upload complete state when the condition that the file upload for a specific equipment type is 100% complete is met. In response to the transition to the upload complete state, the processor (110) can send a notification to the administrator (Admin) informing them of the completion of the upload for the target equipment. Subsequently, the processor (110) can transition to a processing complete state when the condition that the number of pending approvals for the target equipment reaches zero and all files are judged as either approved or rejected is met. In response to the transition to the processing complete state, the processor (110) can send a processing complete notification to the vendor containing a list of rejected files. Furthermore, the processor (110) can transition to a final approval complete state when the condition that all target equipment is 100% approved is met. The processor (110) can send a notification to both the manager and the vendor in response to the transition to the approval complete state, informing them that the approval of the target equipment is 100% complete.

[0183] Additionally, the processor (110) can apply independent tracking logic on a building-by-building basis. The processor (110) can create and operate a separate state transition model for each building, even if they are of the same equipment type. For example, if a specific pump equipment is installed in both the first building and the second building, the processor (110) can treat the completion of the pump upload in the first building and the completion of the pump upload in the second building as mutually independent separate events and send a notification.

[0184] Furthermore, the processor (110) can perform re-notification processing after a file has been rejected. The processor (110) can determine whether the condition is met where the vendor re-uploads the file and reaches 100% progress again after the administrator has rejected a specific file. If the processor (110) confirms that the file has reached 100% progress again, it can delete the previously sent notification history and create a new notification to inform the administrator that a review is required. Through this mechanism, the processor (110) can perform intelligent control that goes beyond simple notification duplication prevention and accurately detects the situation where the progress status returns to a previous stage and then reaches the target condition again, thereby re-sending the notification.

[0185] The processor (110) can provide a three-color multi-stage progress visualization system that simultaneously displays three states in different colors within a single progress bar area. Unlike conventional methods that simply identify the progress status using a single color from 0% to 100%, the processor (110) can visualize the approved, pending approval (unapproved), and incomplete states by integrating them into a single progress bar. By simultaneously providing three pieces of information regarding the approval rate, the unapproved rate, and the incomplete rate, the processor (110) can support the user in immediately identifying not only the overall progress status of the work but also bottlenecks in the approval process.

[0186] Specifically, the processor (110) can calculate the ratio of each state by applying a predefined calculation formula and map a corresponding visual color. The processor (110) can distinguish and display the approved state as a first color (e.g., green), the unapproved state as a second color (e.g., orange), and the incomplete state as a third color (e.g., gray) on the screen. The processor (110) can calculate the approval rate (%) by performing an operation of multiplying the value obtained by dividing the number of approved devices by the total number of devices by 100. The processor (110) can calculate the unapproved rate (%) by performing an operation of multiplying the value obtained by dividing the number of devices that have completed uploading but are not yet approved by the total number of devices by 100. Subsequently, the processor (110) can derive the incomplete rate (%) by performing an operation of subtracting the calculated approval rate and unapproved rate from the total 100%.

[0187] Additionally, the processor (110) may provide a separate visual effect to intuitively indicate that the state is complete when the progress reaches the final target value. The processor (110) may perform processing to add a luminous effect and an outline to the progress bar area and output it in response to the condition that the progress reaches 100%. By applying visual changes, the processor (110) can control the user to quickly and accurately recognize the state of completion on the data on the screen.

[0188] The processor (110) can optimize inspection performance by processing the process of uploading multiple files simultaneously in a batch check method instead of individually checking for duplicate filenames. Unlike the conventional method of accessing storage for each file to repeatedly check for its existence, the processor (110) can perform comparison operations in memory after querying the entire file list of the target folder only once. Through this batch inspection method, the processor (110) can prevent database query time from increasing in proportion to the number of files and can guarantee constant query performance regardless of the number of files. Furthermore, when duplicate files are detected, the processor (110) can safely preserve the original data by applying a method of automatically adding a number to the filename instead of causing a system error or overwriting the existing file.

[0189] As a specific processing algorithm, the processor (110) may generate all possible filename candidates, including the original filename and a filename with a sequential number attached, in response to receiving an upload request for multiple files. Subsequently, the processor (110) may obtain a list of all files existing in the target folder by querying the database and / or storage once, and convert the obtained query result into a memory set structure. The processor (110) may immediately determine whether there is a duplicate by referring to the memory set configured for each file to be uploaded. If the processor (110) determines that there is no duplicate because there is no identical filename in the memory set, the file may be saved with the original filename as is. On the other hand, if the processor (110) determines that there is a duplicate because there is an identical filename, the processor may perform a process of adding a specific number to the original filename and saving it. Additionally, the processor (110) may determine whether the condition is satisfied where the number of times a number has been added exceeds a preset maximum number. The processor (110) can ensure infinite uniqueness of the filename by adding a timestamp to the filename and storing it when it is determined that the added number exceeds the maximum number.

[0190] FIG. 4 is a diagram illustrating an example of a processor managing and outputting project data according to one embodiment.

[0191] Referring to FIG. 4, the processor (110) can generate a screen (40) containing overall overview information of the project and output it to a display. The processor (110) can systematically classify and provide a number of key attribute information related to the target project through the screen (40).

[0192] Specifically, the processor (110) can display on the screen (40) identification information regarding the client, construction company, and operator involved in the project, along with location information of the target building where the project is to be performed. In providing information regarding the construction period of the project, the processor (110) can control the entire construction schedule to be divided into multiple detailed stages, including Phase 1 and Phase 2, and to specify the specific start and end dates corresponding to each stage.

[0193] Additionally, the processor (110) can provide numerical data regarding the site area of ​​the project target site and the total floor area of ​​the building. Along with this, the processor (110) can divide the target facility into multiple independent buildings, such as Building A and Building B, when providing information on the number of floors of the building. The processor (110) can visualize and display in detail the configuration status of the basement floor (B2F), ground floor (5F), and rooftop floor (RF) for each building.

[0194] Furthermore, the processor (110) can provide detailed information regarding the internal data hall capacity of the building. Based on the construction phase (Phase 1, Phase 2) and the number of detailed floors within each building (e.g., A-2F / 3F, B-2F / 3F, etc.), the processor (110) can individually derive the power capacity in megawatts (MW) of the colocation (COLO) allocated to each designated zone and output it to the screen (40). By integrating and providing such complex data structures within a single screen (40), the processor (110) can support the user in intuitively understanding the key specifications of the construction project.

[0195] FIG. 5 is a diagram for illustrating an example of a processor according to one embodiment managing and outputting equipment data.

[0196] Referring to FIG. 5, the processor (110) can generate and output a search screen (50) that allows equipment data to be searched and managed based on a hierarchical folder structure. The processor (110) can provide a user interface through the search screen (50) that allows sequential selection of construction phase, building, commissioning phase (CxLevel), equipment classification, and equipment type.

[0197] Specifically, the processor (110) can receive a selection input for Phase 1 or Phase 2 by displaying a list of construction phases of the project in the first area (51). The processor (110) can display a list of buildings of the target building (e.g., Building A, etc.) in the second area (52). The processor (110) can display a list of commissioning phases including Phase 0 (CxL0) through Phase 6 (CxL6) in the third area (53). The processor (110) can display a list of equipment categories including Electrical, Mechanical, and Fire in the fourth area (54). The processor (110) can provide a list of detailed equipment types belonging to the selected equipment category in the fifth area (55). For example, the processor (110) can output a list of equipment including an Automatic Transfer Switch (ATS), a battery, a Closed Transition Transfer Switch (CTTS), etc., under conditions where electricity is selected.

[0198] Additionally, when the processor (110) enters a specific file path according to the user's hierarchical selection operation, it may provide relative path information indicating the current search location (e.g., Phase 1 > Building A > CxL1 - Factory Test > Electrical > CTTS, etc.) at the top of the search screen (50). Furthermore, the processor (110) may place an export button (56) on one side of the search screen (50). In response to the detection of an input operation for the export button (56), the processor (110) may perform an export process to extract and download the equipment list data currently being searched into a specified file format, such as Excel.

[0199] Furthermore, the processor (110) may provide additional filter elements at the bottom of the search screen (50) to select data based on commissioning stages and floors. The processor (110) may activate a specific commissioning stage (e.g., CxL1, CxL2, etc.) or a specific floor (e.g., All, B2F, etc.) according to user operation, thereby controlling the dynamic filtering and outputting of only equipment data that meets the desired conditions on the screen.

[0200] FIG. 6 is a diagram for illustrating another example in which a processor according to one embodiment manages and outputs equipment data.

[0201] Referring to FIG. 6, the processor (110) can generate and display an equipment list screen (60) that provides detailed data and attachment file details for individual equipment in a list format. The processor (110) can place a search input area and a search button at the top right of the equipment list screen (60) where an equipment type or equipment identifier (Equipment ID) can be entered. In response to receiving a specific search term from a user, the processor (110) can quickly search for equipment data that meets the conditions and filter and provide it on the screen.

[0202] Additionally, the processor (110) may provide an Add Equip button (61) for manually registering new equipment data on the equipment list screen (60) and a Delete Equip button (62) for completely removing selected equipment data from the system. Along with this, the processor (110) may provide summary text indicating the total number of equipment displayed on the current screen (e.g., “10 total equipment items”) to help the user intuitively grasp the overall scale of the data.

[0203] The processor (110) can output multiple attribute information corresponding to each piece of equipment in row units through the data table of the equipment list screen (60). Specifically, the processor (110) can provide a checkbox for selection for each piece of equipment and display on the screen in a structured text form equipment classification (Category) such as commissioning level (CxLevel), electrical (ELEC), installation location, equipment type, equipment identifier, equipment specifications (Equip Spec) such as voltage and current, and vendor information. For example, the processor (110) can clearly provide specific specifications and supplier information for the equipment identifier 'CTTS-A-1', which belongs to the first level (CxL1) and is located in the B2F Electrical Room.

[0204] Furthermore, the processor (110) can visually display the attachment status and final processing results of the Test Report files mapped to each piece of equipment on the equipment list screen (60). The processor (110) can display the number and size information of the files attached to the target equipment (e.g., “1 attached file (7.2MB)”) and simultaneously provide a viewer icon to immediately view the attached files and a download icon to download them to a device. In addition, for equipment items where the document review process has been completed and the approval decision has been finalized, the processor (110) can clearly convey the approval status for each piece of equipment by rendering a graphic object in the form of a stamp indicating the completion of approval in the processing result column.

[0205] FIG. 7 is a diagram illustrating an example of a processor managing commissioning documents according to one embodiment.

[0206] Referring to FIG. 7, the processor (110) can output a screen to the display for managing the details of test report files mapped to each device and the final approval results. In response to a file being uploaded to the system for a test report item, the processor (110) can calculate and display the total number of attached files and the total merged capacity (e.g., “3 attached files (20.5 MB)”, “2 attached files (17.6 MB)”, etc.) in text form. Additionally, the processor (110) can intuitively guide the presence of documents by arranging multiple icons, such as a first file icon (74) and a second file icon (75), side by side to visually indicate individual attached documents.

[0207] Additionally, the processor (110) may provide a preview icon (71), a download icon (72), and a delete icon (73) placed on one side of the test report area to perform viewing and control functions for the attached files. When a mouse hover event is detected for the preview icon (71) under conditions where multiple documents are attached to a single equipment item, the processor (110) may display a tooltip containing the text 'Merged Version Preview' on the screen. When an execution operation for the preview icon (71) is received, the processor (110) can significantly improve the efficiency of the administrator's document review by rendering and providing a preview screen in the form of an integrated version where all multiple files are continuously merged into a single document (e.g., a single PDF merged document) instead of allowing multiple files to be viewed individually.

[0208] Next, the processor (110) can perform data control processing to transmit attached files to a user terminal when operation on the download icon (72) is detected, and to remove the attached files in bulk from the system when operation on the delete icon (73) is detected. In addition, the processor (110) can activate and provide a separate upload button on the screen to transmit a new file to the system server for equipment items where a test report has not yet been attached or where re-registration of the document is required.

[0209] Furthermore, the processor (110) can visualize and display the final approval status based on the administrator's document review judgment in the result area. The processor (110) can output a first graphic object in the form of a stamp indicating "REJECTED" for items rejected during the review process, and a second graphic object in the form of a stamp indicating "APPROVED" for items where the file has been finally approved. On the other hand, the processor (110) can control the user to clearly identify the approval progress and missing status of documents for each device by displaying an X-shaped icon for items in an unresolved state where the administrator's approval process has not yet been completed after file attachment or the file itself has not been uploaded.

[0210] FIG. 8 is a diagram illustrating an example in which a processor according to one embodiment outputs the commissioning progress status.

[0211] Referring to FIG. 8, the processor (110) can output a dashboard screen on the display that allows for an intuitive understanding of the overall commissioning progress of the target project. The processor (110) can provide a visual user interface by placing a bird's-eye view or a 3D modeling image of the target building (e.g., a data center) at the top of the screen. Additionally, the processor (110) can output information regarding the client, the construction company, and the operator on one side of the screen.

[0212] The processor (110) can summarize and visualize the overall goal achievement rate (e.g., 100%, etc.) for a specific construction phase (e.g., Phase 1, etc.) through a first chart (81) and a second chart (82) in the form of circular widgets. Specifically, the processor (110) can display the first chart (81) indicating the report approval completion rate and the second chart (82) indicating the report upload completion rate side by side in the form of individual donut charts. By simultaneously providing the first chart (81) and the second chart (82) indicating achievement rates of different criteria, the processor (110) can support the user in comparing the status of document uploads and the actual status of approval completion from various angles and intuitively understanding them within the entire process.

[0213] Additionally, the processor (110) can provide detailed progress rates according to the construction phase and commissioning phase in the form of a bar chart through the first area (83) and the second area (84) located at the bottom of the screen. The processor (110) can output a progress bar for the entire first process phase (Phase 1) along with individual progress bars for the lower levels from the first commissioning phase (CxL1) to the sixth commissioning phase (CxL6) in the first area (83). Similarly, the processor (110) can output the overall progress rate corresponding to the second process phase (Phase 2) and the individual progress rate for each commissioning phase in the second area (84).

[0214] Furthermore, as illustrated in the legend at the top of the drawing, the processor (110) can apply a multi-stage progress visualization method to distinguish and display the detailed status of the work within a single bar chart. To visually separate the detailed status regarding document processing, the processor (110) can simultaneously display on the screen the percentage of completed report approvals rendered as a hatching pattern and the percentage of reports that have been uploaded but not yet approved rendered as a dot pattern. Through such a patterned visualization structure, the processor (110) can support the user in immediately identifying not only the superficial progress of the entire process but also the actual approval waiting section or bottleneck point.

[0215] FIG. 9 is a diagram illustrating another example in which a processor according to one embodiment outputs the commissioning progress status.

[0216] Referring to FIG. 9, the processor (110) can output a screen (90) to the display that provides detailed progress status for a specific commissioning stage (e.g., a first stage (CxL1) Factory Test, etc.) in the form of a dashboard. The processor (110) can display a first progress bar (91) in the upper area of ​​the screen (90) indicating the number of equipment that has been processed (e.g., “445 / 662 equipment”) relative to the total number of equipment belonging to the corresponding commissioning stage.

[0217] The processor (110) can provide the overall progress status subdivided according to the equipment classification. Specifically, the processor (110) can arrange a second progress bar (92) corresponding to electrical equipment, a third progress bar (93) corresponding to mechanical equipment, and a fourth progress bar (94) corresponding to fire equipment side by side on the detailed screen (90). The processor (110) can calculate the total number of equipment assigned to each equipment classification and the number of completed items (e.g., “445 / 445”, etc.) and output them individually on the second progress bar (92), the third progress bar (93), or the fourth progress bar (94).

[0218] Additionally, the processor (110) can provide progress rate information for each individual equipment type belonging to each equipment classification sub-level in a list format. The processor (110) can display individual bar graphs for a battery, a closed transition transfer switch (CTTS), a generator, etc., at the bottom of the electrical equipment area. The processor (110) can also list and output individual bar graphs indicating the progress rate relative to the total quantity for each equipment type, such as an air handling unit (AHU), a chilled water pump, or a firefighting pump, at the bottom of the mechanical equipment area and the firefighting equipment area.

[0219] Additionally, similar to the description in FIG. 8, the processor (110) may apply a multi-stage visualization pattern according to the document processing status to a number of progress bars (91, 92, 93, 94) and individual bar graphs displayed on the screen (90). The processor (110) may render the quantity portion that has been fully approved as a hatching pattern and display the quantity portion that has been uploaded but has not yet been approved as a dot pattern. By consistently applying the patterned visualization structure to all layers of the detail screen (90), the processor (110) may support the user in intuitively understanding the progress and bottleneck status of document review, which are subdivided by facility and equipment units.

[0220] FIG. 10 is a diagram illustrating an example of a processor analyzing time series data according to one embodiment.

[0221] Referring to FIG. 10, the processor (110) can visualize the collected time-series data and output an analysis screen (100) on the display that provides artificial intelligence analysis results for the time-series data. The processor (110) can divide the analysis screen (100) into a first area (101), a second area (102), and a third area (103) to simultaneously provide multi-faceted data analysis information.

[0222] The processor (110) can generate and display a graph (e.g., a temperature difference time series graph) that analyzes time series data in the first area (101). Specifically, the processor (110) can output a left graph showing a change in flow rate in Liter Per Minute (LPM) units over time and / or a right graph showing a change in inlet temperature in Celsius (°C) units over time. The processor (110) can apply a hatching pattern or the like to highlight a test section with specific conditions applied, such as a 25% heat load test, so that it is visually distinguished from other sections. Additionally, the processor (110) can provide a dropdown menu on one side of each graph area to set calculation criteria such as averages, thereby dynamically updating the data displayed on the graph according to the user's selection operation.

[0223] Next, the processor (110) can provide an analysis result report derived based on an artificial intelligence model to the second area (102). The processor (110) can support the user's intuitive understanding of the test results by outputting a heat load test data analysis report structured in text form to the second area (102), which contains a comprehensive analysis of the heat load test data.

[0224] Furthermore, the processor (110) may provide an artificial intelligence data analysis window in the third area (103) that analyzes data while interacting with the user via text. The processor (110) may receive a user's query through the third area (103) and display the analysis results and response of the artificial intelligence model in the form of speech bubbles in a conversational interface. Additionally, the processor (110) may place shortcut buttons at the bottom of the third area (103) to immediately execute frequently used specialized analysis functions, such as outlier analysis, average temperature difference, and interval comparison. The processor (110) may control the immediate execution of the corresponding data analysis logic and rapid output of the results to the dialog box screen in response to the detection of a selection input for the corresponding button.

[0225] The processor (110) may utilize an Artificial Intelligence Model (AI Model) to analyze, classify, infer, or predict collected data. The AI ​​Model may refer to a mathematical or statistical model learned through a Machine Learning (ML) or Deep Learning (DL) algorithm based on training data that includes input data and output data corresponding to the input data. The processor (110) may perform an inference operation to derive a desired result value by providing new target data as input to the AI ​​Model that has completed training.

[0226] In one embodiment, the artificial intelligence model may be implemented in various architectures depending on the characteristics and purpose of the data to be processed. For example, the artificial intelligence model may include an Artificial Neural Network (ANN) structure that mimics the neural network of the human brain. Specifically, to extract two-dimensional or three-dimensional spatial features such as images and videos and to recognize patterns, the artificial intelligence model may be composed of a Convolutional Neural Network (CNN). Additionally, to grasp the context of sequentially occurring data such as text, voice, or time-series data and to model temporal dependencies, the artificial intelligence model may include a Recurrent Neural Network (RNN) or a Long Short-Term Memory (LSTM) network.

[0227] Furthermore, the processor (110) may utilize a Transformer-type model that identifies associations within input data based on an attention mechanism for Natural Language Processing (NLP) or large-scale time-series data analysis. For example, the artificial intelligence model may be implemented in the form of a Large Language Model (LLM) or a Generative Pre-trained Transformer (GPT) that can perform document summarization, translation, question answering, and text generation by pre-training a large-scale text corpus.

[0228] In addition, artificial intelligence models may include traditional statistical-based and ensemble learning-based models such as Support Vector Machine (SVM), Decision Tree, or Random Forest for performing linear or non-linear classification of data. Depending on the performance requirements, computational resources, and types of data of the system to be implemented, the processor (110) may use any one of the aforementioned models alone or apply them in an ensemble form combining multiple models to improve the accuracy of the analysis.

[0229] FIG. 11 is a diagram illustrating an example of a processor managing permissions by user type according to one embodiment.

[0230] Referring to FIG. 11, the processor (110) can generate and display a screen (110) that can set detailed access and control rights for multiple user types using the system. The processor (110) can provide a list of user types including Super Admin, Admin, Client, Operator, and Vendor in the upper area of ​​the screen (110). In response to receiving input from a management entity selecting a specific user type, the processor (110) can display the specific function-specific authority status to be granted to that type in a lower area.

[0231] The processor (110) can individually control permissions regarding file management through the first area (111). Specifically, the processor (110) can control to enable or disable file handling permissions for a selected user type by providing a user interface in the form of a toggle switch corresponding to file viewing, file download, file upload, file modification, and file deletion, respectively.

[0232] Next, the processor (110) can control authority regarding equipment management through the second area (112). By providing toggle switches for equipment creation and equipment deletion items, the processor (110) can grant authority to add or remove equipment records within the database differently for each user type.

[0233] Additionally, the processor (110) can control the authority regarding data editing through the third area (113). The processor (110) can provide individual authority setting items for a cell editing function that directly changes the content of cell data within the system and a comment function that adds comments to an attached commissioning document.

[0234] Furthermore, the processor (110) can set the access range for the commissioning stage through the fourth area (114). The processor (110) can provide a setting button to determine whether to allow access to the zero stage (CxL0) corresponding to basic information. The processor (110) can support numerically specifying the range of the commissioning stage that is allowed access (e.g., from 1 to 6, etc.) through a text input field. Through such an authorization management structure, the processor (110) can ensure the performance of tasks optimized for each role while strictly maintaining the security and integrity of data in a project environment where multiple participants collaborate.

[0235] FIGS. 12a and FIGS. 12b are drawings illustrating an example of a processor adding feedback information to a commissioning document according to one embodiment.

[0236] Referring to FIG. 12a, the processor (110) can output an input window (1211) on the screen (121) in the form of a pop-up, which allows the user to directly leave feedback at a designated location in a PDF document during the document review process. The processor (110) can receive specific correction instructions or comments in text form (e.g., "Please correct the equipment name") through the input window (1211), and can provide real-time guidance on the screen by limiting the maximum number of characters that can be entered (e.g., 150 characters). Additionally, the processor (110) can provide Approved and Rejected buttons (121) placed at the top of one side of the screen to confirm the final review judgment on the document.

[0237] Next, referring to FIG. 12b, the processor (110) can output an alarm information (1222) at the top of the screen indicating that a comment has been created within the commissioning document. In conjunction with the alarm information (1222), the processor (110) can provide a comment list (1223) on one side of the screen that lists and displays the comments existing in the commissioning document in a list format.

[0238] Additionally, the processor (110) may display a feedback detail window (1221) in a pop-up form, which includes the specific content of the comment, the author identifier, and the date and time of creation, in response to the detection of user interaction with a comment icon created at a specific location on the document. The processor (110) may provide an interface to modify or delete already written comments through the feedback detail window (1221). Additionally, the processor (110) may place approval and rejection buttons (122) at the top of the screen to confirm the final review decision for the document. Through this alarm and list structure, the processor (110) may support the user in checking and managing feedback information scattered at various locations within the PDF document without omission.

[0239] FIG. 13 is a flowchart illustrating another example of a method for managing commissioning tasks based on a hierarchical structure according to one embodiment.

[0240] Referring to FIG. 13, in step 1301, the processor (110) can perform a project registration procedure. Specifically, the processor (110) can receive site information from the manager and create a new project within the system.

[0241] In step 1302, the processor (110) can register equipment data in bulk. The processor (110) can upload detailed attributes and classification information for multiple pieces of equipment in bulk by importing document files in Excel format.

[0242] In step 1303, the processor (110) can automatically generate a hierarchical folder tree based on registered equipment data. The processor (110) can dynamically construct a folder tree having a multi-level hierarchical structure that follows in the order of Phase, Building, Commissioning Level (CxLevel), Category, and Equipment.

[0243] In step 1304, the processor (110) can perform the upload processing of document files on an equipment-by-equipment basis. The processor (110) can receive and attach documents, such as test reports mapped to target equipment, through a vendor or contractor account. Subsequently, the processor (110) can execute multiple subsequent processing processes in parallel or sequentially.

[0244] In one aspect, the processor (110) can perform document conversion and merging processing for the files uploaded in step 1305. The processor (110) creates a cache in PDF format as soon as the document file is uploaded and can merge multiple files belonging to one equipment unit into a single document.

[0245] Depending on the other aspect, the processor (110) can automatically determine the working status of the equipment in step 1306. The processor (110) can detect whether a test report is attached and determine the equipment with confirmed document attachment to be in a completed state.

[0246] Based on the determination that the work status of the equipment is completed, the processor (110) can automatically calculate the progress rate at the commissioning stage level in step 1307. The processor (110) can calculate the ratio of the number of equipment that has obtained a completion determination to the total number of equipment as a percentage. Subsequently, the processor (110) can propagate the progress rate data calculated in step 1308 to the upper layer. The processor (110) can transmit the progress rate calculated from the equipment type to the facility classification layer, and then sequentially propagate it to the commissioning stage, construction stage, and finally the overall project layer to update the overall progress rate of each upper node. In step 1309, the processor (110) can visualize progress information customized for each user's role based on the propagated data and provide it on a dashboard screen.

[0247] Additionally, the processor (110) can process an approval workflow in step 1310 based on the determined work status. The processor (110) can receive a review operation from the manager and determine whether the uploaded document is approved or rejected. In step 1311, the processor (110) can clearly notify the subject of the work status transition by automatically sending email and in-app notifications when specified conditions are met, such as when the upload of a specific equipment type is 100% completed or when the manager's final approval reaches 100%.

[0248] FIG. 14 is a flowchart illustrating another example of a method for managing commissioning tasks based on a hierarchical structure according to one embodiment.

[0249] Referring to FIG. 14, the entire sequence of processing commissioning data and documents through interaction between the administrator (1401), the system (or, server) (1402), and the contractor / vendor (1404) is illustrated.

[0250] In step 1406, the manager (1401) can request the creation of a new project by entering site information into the system (1402).

[0251] In step 1407, the administrator (1401) can request batch registration by transmitting equipment data written in Excel format to the system (1402).

[0252] In step 1408, the system (1402) can perform internal logic to analyze and parse the received Excel data and register it in the equipment database.

[0253] In step 1409, the system (1402) may generate and assign a unique data fingerprint, such as a fingerprint (e.g., SHA256 Fingerprint, etc.), to verify and track the integrity of the data.

[0254] In step 1410, the system (1402) can create a hierarchical folder tree based on attribute information of the registered equipment database.

[0255] In step 1411, the contractor / vendor (1404) can access the system (1402) with an established hierarchical structure and upload test report files for each piece of equipment.

[0256] In step 1412, the system (1402) can receive the uploaded original file and safely store it in cloud storage (1403).

[0257] In step 1413, the system (1402) can perform processing to convert original files of various formats into documents in PDF format in response to the completion of saving the original files.

[0258] In step 1414, the system (1402) can store the converted document in cloud storage (1403).

[0259] In step 1415, the system (1402) can perform a merging process to combine multiple documents belonging to a single equipment unit into one based on a predetermined display order.

[0260] In step 1416, the system (1402) can save the final document, after conversion and merging are complete, back to cloud storage (1403).

[0261] In step 1417, the system (1402) can determine the status of the equipment as completed as the document conversion and merging procedure is completed.

[0262] In step 1418, the system (1402) can calculate the overall progress rate by performing an operation to aggregate the completion rate of the lower layer to the upper layer based on the equipment status determination result.

[0263] In step 1419, the system (1402) can control the calculated progress to be transmitted to the dashboard (1405) so that it is visualized in real time on the user screen.

[0264] In step 1420, the administrator (1401) can review the uploaded document and input the result of the Approved or Rejected judgment for a specific piece of equipment into the system (1402).

[0265] In step 1421, the system (1402) can recalculate the approval rate of the entire project based on the judgment input of the manager (1401).

[0266] In step 1422, if a specific condition (e.g., 100% completion or approval, etc.) is detected during the recalculation process, the system (1402) may generate and deliver to the user notification information including the circumstances regarding the specific condition.

[0267] In step 1423, the system (1402) can send email notifications to the account of the contractor / vendor (1404) by linking with an external mail service.

[0268] In step 1424, the system (1402) can output a control signal to display an in-app notification on the application screen used by the administrator (1401).

[0269] FIG. 15 is a diagram illustrating an example of a system for managing commissioning tasks based on a hierarchical structure according to one embodiment.

[0270] Referring to FIG. 15, the processor (110) can process commissioning tasks integrally through a modularized system architecture divided into an input layer (1510), a processing layer (1520), and an output layer (1530). The processor (110) can receive data from the outside by supporting the batch registration of equipment list files, manual uploading of individual test document files, and automatic linked uploading based on filename rules through the input layer (1510).

[0271] The equipment list file may refer to a data file, such as an Excel file, that comprehensively contains specifications and control attribute information for multiple pieces of equipment subject to commissioning. Specifically, the equipment list file may include, for each piece of equipment, construction phase, building, commissioning phase, facility classification, equipment identifier, equipment specifications, and vendor information in the form of a structured table composed of rows and columns. By registering the equipment list file in the system in bulk, the processor (110) can generate database records for individual pieces of equipment all at once and simultaneously utilize it as basic data to automatically construct an overall hierarchical folder tree of the project based on the attribute information contained in the data.

[0272] A test document file may refer to an electronic document uploaded to a system by a user (e.g., a vendor or contractor, etc.) to prove the results of inspections and tests of specific commissioning stages performed on individual equipment. For example, a test document file may include test reports, checklists, or photo sheets derived from each stage, such as factory testing, installation testing, or functional testing. The processor (110) may automatically transition the work status of the equipment to completion in response to the upload of a test document file mapped to a specific piece of equipment, and may convert and merge the received original files into PDF format to provide them as key review materials to support the manager's approval or rejection judgment.

[0273] The processor (110) can identify data changes in a batch-registered equipment list file by driving a deformation detection module (1521) within the processing layer (1520). Subsequently, the processor (110) can automatically generate a hierarchical folder tree within the system, including construction phases, building and commissioning phases, based on the detected equipment data through a management structure creation module (1522).

[0274] Additionally, the processor (110) can perform a process of analyzing identification information included in a file name through the file automatic linkage module (1523) and linking it to the corresponding equipment record. The processor (110) can transmit manually uploaded test document file data and file data that has passed through the file automatic linkage module (1523) to the document state transition model (1524). The document state transition model (1524) can manage the dynamic determination and transition of the work status of each equipment based on whether the document is registered and / or approved.

[0275] Furthermore, the processor (110) can execute subsequent modules sequentially or in parallel based on the state determination result of the document state transition model (1524). The processor (110) can merge multiple files mapped to specific equipment into a single document through the document merging module (1526) and transmit it to the output layer (1530). The output layer (1530) can generate a combined report for each piece of equipment based on the received document. Additionally, the processor (110) can calculate and output the progress rate for each test stage by aggregating the status of lower-level equipment to the upper layer through the progress rate calculation module (1525). Furthermore, the processor (110) can send an automatic notification to the subject by triggering the notification sending module (1527) based on the calculated progress rate result.

[0276] In addition, the system operates in a cloud computing environment and can support simultaneous processing situations where multiple participating companies upload documents at the same time.

[0277] For example, if multiple participating companies (e.g., 30 companies) submit test documents to the system simultaneously, the files uploaded by each company can be distributed and stored in a cloud object storage. Subsequently, the file automatic linkage module (1523) can perform equipment matching processing for individual files asynchronously. Additionally, the document state transition module (1524) can process the business state transition for each device linked to the document independently of each other.

[0278] Furthermore, the progress calculation module (1525) can prevent unnecessary computational load by selectively performing progress recalculation limited to specific test stages where the state has changed. In addition, the notification sending module (1527) can prevent duplicate notifications for the same event from being sent even in a multi-process environment by applying a synchronization mechanism. Through this asynchronous and independent processing structure, even if multiple companies submit a large volume of documents simultaneously, the state transition and progress calculation of each equipment can be performed accurately without mutual interference or system delay.

[0279] Meanwhile, the embodiments of the present invention are not limited to the aforementioned forms and may be implemented in various modified forms by changing the operation method of each module constituting the system.

[0280] The file automatic linkage module (1523) can be modified to identify target equipment based on file metadata, such as author information or document attributes, in addition to a filename-based identification method. Additionally, the file automatic linkage module (1523) can operate by directly analyzing a portion of the file content (e.g., document header) to extract equipment identifiers. The document merging module (1526) can be modified to support conversion and merging processing functions into individual standard document formats required by specific industrial fields, in addition to general report formats.

[0281] The application of the present invention is not limited to data center commissioning tasks but can be extended to various industrial sectors. For example, it can be applied to manage test reports for thousands of devices (pumps, valves, instruments, etc.) and automatically aggregate final reports for submission to regulatory agencies during the commissioning process of power plants handling nuclear, thermal, or renewable energy. It can be utilized to manage documents for the Installation Qualification (IQ), Operational Qualification (OQ), and Performance Qualification (PQ) stages for precision equipment within cleanrooms of semiconductor fabrication facilities (FABs) in a multi-member structure. Furthermore, it can be applied to manage test documents for equipment replaced during major maintenance of petrochemical plants to track the completion of safety certification using a hierarchical progress rate, or to manage equipment test documents by zone (block) in shipbuilding and offshore plants to automatically aggregate reports for submission to classification societies. Furthermore, it can be widely applied to the systematic management of test documents in accordance with GMP (Good Manufacturing Practice) regulations during the equipment verification process of medical device manufacturing facilities.

[0282] The hierarchical structure generated by the management structure generation module (1522) may have five layers leading to tools, buildings, test phases, classifications, and equipment types, in addition to the number or order of layers that can be flexibly adjusted according to the unique characteristics of the project. The change detection module (1521) may be modified to include other attributes tailored to the project characteristics, or to exclude some of them, in addition to the equipment quantity, modification date and time, and the list of buildings, classifications, and equipment types when generating fingerprints. The storage form of the management structure constructed by the management structure generation module (1522) may use various tree representation methods, such as an adjacency list or path enumeration, in addition to a self-referential hierarchical structure method. The task completion judgment criteria of the progress rate calculation module (1525) may be strengthened to require that multiple specific document types, such as test reports and inspection reports, are all satisfied, in addition to whether a simple test report is attributed.

[0283] Each module can be configured to operate in a distributed processing environment based on cloud computing. Specifically, the received document files are stored in a cloud object repository, and the document conversion processing of the document merging module (1526) can be performed by an asynchronous task queue, such as an asynchronous task worker based on a message broker. In addition, the aggregation operation of the progress calculation module (1525) and the notification processing of the notification sending module (1527) are performed by event-based asynchronous processing, thereby ensuring real-time computation without processing delay even in a large-scale project environment where hundreds of documents are uploaded simultaneously. Furthermore, the progress calculation module (1525) can be extended to compare and sum the progress between multiple projects beyond a single project, and the change detection module (1521) can be configured to independently calculate and compare fingerprints for each project. The automatic heat recognition function of the equipment registration module is configured to support multilingual heat names, and the combined format of the document merging module (1526) can be adjusted to meet the requirements of various international standards, such as the International Electrotechnical Commission (IEC), the Institute of Electrical and Electronics Engineers (IEEE), and the American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE).

[0284] Additionally, at least one module included in the system (e.g., a document state transition module (1524) and a progress rate calculation module (1525), etc.) may operate in conjunction with a mobile terminal, such as a smartphone or tablet, carried by a field worker. When a worker uploads a photo taken directly at the site or a checklist created by the worker to the system as a test document via a mobile terminal, the document state transition module (1524) may be modified to immediately process the state transition of the equipment at the time of upload, and the progress rate calculation module (1525) may be modified to perform a real-time update of the overall progress rate in conjunction with this.

[0285] The plurality of modules described with reference to FIG. 15 are merely one embodiment for implementing the technical concept of the present invention. According to the embodiment, at least some of the modules shown in FIG. 15 may be implemented by merging them into a single integrated module, or conversely, a single module may be implemented by separating it into a plurality of sub-modules that perform detailed functions. Furthermore, the operation and function of each of the modules described in FIG. 15 may be performed by at least one processor provided within a device or server.

[0286] Meanwhile, according to the present disclosure, the following improvement effects can be confirmed. For example, in a 100-megawatt (MW) class data center construction project, a large-scale environment can be assumed in which the number of registered equipment units is 5,000, the commissioning phase consists of 5 stages (CxL1 to CxL5), and 30 participating companies are involved.

[0287] First, regarding the time required to calculate the progress rate, in the conventional method, about 4 hours of labor per week were consumed as a person in charge manually calculated the progress rate through a spreadsheet, but the processor (110) can practically automate the calculation process 100% by automatically calculating the progress rate in real time in conjunction with the time of document upload.

[0288] Second, regarding the discrepancy between the document and the work status, the conventional method resulted in a state discrepancy error of approximately 5% to 15% (approximately 250 to 750 cases) based on 5,000 units of equipment, but the processor (110) can eliminate the state discrepancy at the source through a structure that atomically links the document attachment act and the state transition.

[0289] Third, regarding the file attribution error rate, the conventional method resulted in an attribution error of about 3% to 8% as a large number of documents were placed manually, but the processor (110) can significantly reduce the probability of misattribution by applying a longest match matching algorithm based on filenames.

[0290] Fourth, regarding the update of the management structure, the conventional method relies on manual verification by the person in charge, which results in an update delay of several hours to several days, but the processor (110) can immediately resolve the delay problem through automatic detection of the time of inquiry and delay regeneration method.

[0291] Finally, regarding the number of missed approvals, the conventional method had a security limitation in that the existing approval status was maintained even when the document was replaced, resulting in missed re-approvals; however, the processor (110) can fundamentally block the possibility of missed re-approvals and guarantee the integrity of the final report through a bidirectional transition structure that automatically resets the existing approval status upon resubmission of the document. Through such a complex mechanism, the processor (110) can maximize project management efficiency, data consistency, and document reliability.

[0292] That is, the processor (110) can comprehensively control and perform a series of operations such as data collection, computation, state transition, merging, and sending notifications corresponding to each module by executing instructions in the form of software, program code, or applications stored in memory. Accordingly, a person skilled in the art can easily understand that the hierarchical structure and module configuration presented in FIG. 15 correspond to a functional and logical distinction to aid in understanding the invention, and that each module does not necessarily have to be implemented as a physically completely independent individual hardware component.

[0293] Meanwhile, the above-described method can be written as a program executable on a computer and can be implemented on a general-purpose digital computer that operates the program using a computer-readable recording medium. In addition, the structure of the data used in the above-described method can be recorded on a computer-readable recording medium through various means. The computer-readable recording medium includes storage media such as magnetic storage media (e.g., ROM, RAM, USB, floppy disk, hard disk, etc.) and optical reading media (e.g., CD-ROM, DVD, etc.).

[0294] Meanwhile, the method described above may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices. In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0295] A person skilled in the art related to the present embodiment will understand that it may be implemented in modified forms without departing from the essential characteristics of the description above. Therefore, the disclosed methods should be considered in an illustrative rather than a restrictive sense, and the scope of rights is defined in the claims rather than the description above, and should be interpreted to include all differences within the scope of equivalence.

Claims

Claim 1 A method for managing commissioning tasks based on a hierarchical structure comprising a server including at least one processor, comprising: a step of generating a hierarchical structure including a project layer, a construction layer, a building layer, a test layer, a category layer, and an equipment layer based on equipment data regarding a project; a step of changing the task status of at least one piece of equipment based on the uploading of a commissioning document for at least one piece of equipment; and a step of calculating a progress rate for each of a plurality of layers included in the hierarchical structure based on the task status; wherein the step of calculating comprises: a step of calculating a progress rate for individual equipment units of the equipment layer; and a step of calculating a progress rate for each layer sequentially in the order of the category layer, the test layer, the building layer, the construction layer, and the project layer based on the individual equipment unit progress rate; wherein the individual equipment unit progress rate is calculated based on at least one of whether the commissioning document for the individual equipment is uploaded or whether the commissioning document for the individual equipment is approved. Claim 2 A method according to claim 1, further comprising: a step of generating a unique identification value for received equipment data based on a hash function; a step of determining whether the equipment data has been changed by comparing the unique identification value with a previously stored unique identification value; and a step of updating the hierarchical structure based on whether the data has been changed. Claim 3 A method according to claim 1, further comprising the step of tracking the operational status of the equipment based on whether the equipment participates in each of the plurality of tests included in the test layer. Claim 4 A method according to claim 1, further comprising the step of managing the upload status of the commissioning document of the at least one device in correspondence with at least one device included in the device hierarchy, based on a hash value. Claim 5 A method according to claim 1, further comprising the step of classifying the test layer based on the design documents and equipment documents of the project and managing the design documents of the project based on a virtual folder structure. Claim 6 delete Claim 7 delete Claim 8 The method of claim 1 further comprises the step of displaying a customized dashboard for each user having access rights differently set for the hierarchical structure; wherein the customized dashboard includes the progress of at least one layer included in the hierarchical structure. Claim 9 A system for managing commissioning tasks based on a hierarchical structure, comprising at least one memory; and at least one processor, wherein the at least one processor generates a hierarchical structure including a project layer, a construction layer, a building layer, a test layer, a category layer, and an equipment layer based on equipment data regarding a project, changes the task status of the at least one piece of equipment based on the uploading of a commissioning document for at least one piece of equipment, calculates a progress rate for each of the plurality of layers included in the hierarchical structure based on the task status, wherein the at least one processor calculates a progress rate for individual equipment units of the equipment layer, and, based on the individual equipment unit progress rate, calculates a progress rate for each layer sequentially in the order of the category layer, the test layer, the building layer, the construction layer, and the project layer, wherein the individual equipment unit progress rate is calculated based on at least one of whether a commissioning document for the individual piece of equipment has been uploaded or whether a commissioning document for the individual piece of equipment has been approved. Claim 10 A computer-readable recording medium having a program for executing the method according to claim 1 on a computer.

Citation Information

Patent Citations

  • Project management information system

    KR1020070004162A

  • A method for automatically expressing a construction schedule according to its category and system for the same

    KR1020180097181A

  • System for providing information based on attachable code in construction site

    KR102750274B1

  • Artificial Intelligence Based System for Architectural Design and Management of Construction Project, and Method Using the Same

    KR102890450B1