Project working hour statistical analysis system for architectural design application behavior monitoring and algorithm analysis

Abstract

The invention relates to the technical field of architectural design, in particular to an architectural design application behavior monitoring and algorithm analysis project man-hour statistical analysis system, which comprises a page behavior recording module, a task trajectory generation module, a project identifier collection module, a personnel time consumption verification module and an error offset tracking module. According to the method, a clear task execution structure is formed by extracting a task window and an operation path sequence in design software, reconstructing a task behavior chain and removing irrelevant operation content, continuous operation time periods are aggregated in combination with task affiliation information, and an accurate mapping relation between behavior data and project content is established; and matching the effective man-hour with the person in charge, collecting and comparing the effective man-hour with the person in charge, identifying a time offset section between a behavior record and declaration data, quantifying an offset rate, and judging the reasonability of man-hour declaration, thereby realizing dynamic verification and precision improvement of the corresponding relationship between man-hour distribution and tasks.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of architectural design, in particular to a project work hour statistical analysis system for architectural design application behavior monitoring and algorithm analysis. BACKGROUND

[0002] The technical field of architectural design mainly involves the systematic planning and implementation management of the whole process of architectural projects from conception, design, modeling to drawing, etc. This field covers multiple professional directions such as architectural scheme design, structural design, water supply and drainage design, electrical design, and heating and ventilation design. Its core matters include the decomposition and distribution of design tasks, the formation and optimization of design schemes, the organization and coordination of collaborative work processes, the preparation and proofreading of design drawings, and the synchronous control of project progress and quality. With the widespread application of digital design tools, architectural design activities increasingly rely on computer-aided design platforms, which not only improve design efficiency and accuracy but also put forward higher requirements for data management, behavior monitoring, and resource scheduling in the design process. Among them, the project work hour statistical analysis system for traditional architectural design application behavior monitoring and algorithm analysis refers to the information recording of the operation behavior, task execution, and file interaction of designers in the process of using professional software in architectural design activities to estimate the time distribution of designers in different design tasks. The traditional way usually uses the log function of the design software to record the opening and closing time of the file, command execution record, or relies on manual filling of the work hour table to statistically analyze the work time of each stage. These methods rely on fixed rules to record specific operation data or subjective judgment of work content and duration to form a basic understanding and preliminary summary of project work hours.

[0003] The prior art uses operation logs or manual recording of work hours to statistically analyze project task time, which can only obtain the start and end information of the task and cannot restore the task operation structure. In the case of frequent window switching or task cross-processing in the project, operation fragments are easily mixed with non-task content and cannot be removed, which causes data deviation due to the miscounting of corresponding time into the target project. Especially when the multi-stage task does not form a clear boundary, the log cannot distinguish the operation range corresponding to each task, and manual recording relies on subjective judgment and lacks a verifiable path, which easily leads to distortion of work hour attribution. The granularity of work hour data in the project management process is insufficient, which makes it difficult to meet the requirements of data accuracy and matching precision in the high-frequency task decomposition or concurrent execution scenario. SUMMARY

[0004] To solve the technical problems existing in the prior art, the present application provides a project work hour statistical analysis system for architectural design application behavior monitoring and algorithm analysis. The technical solution is as follows: On the one hand, a project work hour statistical analysis system for architectural design application behavior monitoring and algorithm analysis is provided, which includes: The page behavior recording module obtains the user's foreground operation behavior when using design software such as AutoCAD, Revit, and SketchUp, records the software startup action, extracts the software name and task window identifier, identifies window switching events and corresponds them to the operation sequence, segments the task operation and serializes the timeline, and extracts continuous design operation segments; The task trajectory generation module receives monitoring plug-in data based on the continuous design operation segments, identifies the drawing path and task call content, splices repeated call path files, removes behavior segments that are not related to the task, and generates design task trajectory segments; The project identification collection module calls the design server interface through the design task trajectory fragment, extracts the project number in the drawing path, connects the project information source, compares the project type and design stage, completes the classification based on the behavior time and the drawing annotation content, and obtains the professional task attribution content; The personnel time consumption verification module writes the responsible person's behavior into the database according to the professional task attribution content, extracts the continuous time value of each task and combines them for calculation, compares them with the user's working time records, identifies the verifiable time segments, and obtains the distribution of project working time.

[0005] As a further solution of the present invention, the continuous design operation segment includes the design software name, task window identifier, and window switching timing; the design task trajectory segment includes the drawing file path, task call sequence, and irrelevant behavior stripping results; the professional task attribution content includes the project number field, project type identifier, design stage classification, and drawing annotation information; the project work time distribution includes the attribution task time, merged task period, and working time comparison data.

[0006] As a further solution of the present invention, the task-independent behavior fragment refers to a non-design operation record that does not involve project drawing editing, viewing, and task calling path; The verifiable time period refers to a continuous working period in which the behavior records are consistent with the user's working hours declaration and can be cross-verified through operation data.

[0007] As a further solution of the present invention, the page behavior recording module includes: The software identification submodule obtains the user's operation record of starting the design software, extracts the process startup event, filters the software names of AutoCAD, Revit, and SketchUp, and splices them with the task window logo to generate a software task identification tag; The task switching submodule, based on the software task identification tag, calls the timestamp and the foreground window switching record, matches the window handle and the software identifier, extracts the switching time and compares it with the software usage sequence to generate the window task switching segment information; The operation sequence construction submodule combines the task segments in time sequence according to the window task switching section information, calculates the time difference between adjacent segments, judges whether the time difference is lower than a minimum interval threshold value, merges into continuous operation segments, and generates continuous design operation paragraphs.

[0008] As a further scheme of the present application, the task trajectory generation module comprises: The path recognition submodule calls data sent by a user monitoring plug-in based on the continuous design operation paragraphs, extracts drawing path and task call information, identifies repeated paths and numbers the repeated paths, records a number sequence in call order, and generates a repeated path identification sequence; The behavior splicing submodule splices operation behaviors into a structure chain in path number order according to the repeated path identification sequence, filters connection points between differentiated task numbers, extracts corresponding behavior segments, and obtains a structured behavior sequence; The trajectory extraction submodule calls the structured behavior sequence, excludes behavior segments not belonging to a task path according to a path field and a task number, and obtains a design task trajectory segment.

[0009] As a further scheme of the present application, the project identification collection module comprises: The task feedback receiving submodule calls a design server interface to receive task feedback information in a source path based on the design task trajectory segment, extracts a path field and associated task content in feedback data, judges and filters out a non-response field, and obtains a task path feedback set; The project number identification submodule calls the task path feedback set, extracts a project number field embedded in a drawing path, connects project information source data, positions a project number position according to a field structure and completes field comparison, and obtains a project number list; The attribution content determination submodule compares a project type value and a design stage value corresponding to a number according to the project number list, and classifies and judges according to a time stamp range in a field in combination with a behavior triggering time in a drawing annotation content, and obtains professional task attribution content.

[0010] As a further scheme of the present application, the personnel time consumption approval module comprises: The behavior writing submodule writes a responsible person behavior record corresponding to each task into a behavior database based on the professional task attribution content, extracts a start time field and an end time field of each attribution behavior, generates a time period record, and obtains a task behavior time period set; The time calculation submodule calls the task behavior time period set, performs set union on time periods in which a same responsible person exists in differentiated attribution behaviors, and retains start and end times of a union segment, and generates a behavior time cumulative value; The time length authorized sub-module obtains the project work time length distribution quantity by comparing the time start and end intervals of the two data sets according to the behavior time cumulative value, the time period field in the user work time record data, and whether there is an overlapping relationship.

[0011] As a further scheme of the present application, the system further comprises: The error offset tracking module extracts the start and end time difference values and classifies them by comparing the time period of the report and the manually reported time period, cross-analyzing the blank time and the interruption record, identifying the offset record segment, and calculating and obtaining the task execution time offset rate.

[0012] As a further scheme of the present application, the task execution time offset rate comprises the start and end time difference values, the blank time segment, and the operation interruption record.

[0013] As a further scheme of the present application, the error offset tracking module comprises: The time difference value extraction sub-module extracts the task time period of the BI report record and the user manually reported time period based on the project work time length distribution quantity, compares the start and end values of the two time fields according to the task number, calculates the difference value field, classifies the difference value field according to the task sequence number, and obtains the task time difference value sequence. The blank screening sub-module calls the task time difference value sequence, compares the operation time period of the corresponding task in the behavior database, detects the blank time segment and the operation interruption record in the time period, screens the behavior points without binding the reported record in the time period, and obtains the non-reported behavior segment set. The offset rate identification sub-module calculates the ratio of the time length of each segment to the corresponding item in the task time difference value sequence according to the non-reported behavior segment set, marks the records with an offset degree exceeding the report segment length threshold as offset paragraphs, and obtains the task execution time offset rate.

[0014] The technical scheme provided by the embodiment of the present application has at least the following beneficial effects: By extracting the task window and operation path sequence in the design software, the task behavior chain is reconstructed and irrelevant operation content is removed to form a clear task execution structure, the continuous operation time period is aggregated by combining the task attribution information, the accurate mapping relationship between the behavior data and the project content is established, the effective working hours and the responsible personnel are matched and compared, the time offset segment between the behavior record and the reported data is identified, the offset rate is quantified and the working hour reporting rationality is determined, and the dynamic verification and precision improvement of the working hour distribution and the task corresponding relationship are realized. BRIEF DESCRIPTION OF DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the embodiments description. Obviously, the drawings in the following description only are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0016] Figure 1 The flowchart of the present application; Figure 2 The system framework diagram of the present application; Figure 3 The flowchart of the page behavior recording module in the present application; Figure 4 The flowchart of the task trajectory generation module in the present application; Figure 5 The flowchart of the project identification collection module in the present application; Figure 6 The flowchart of the personnel time consumption verification module in the present application; Figure 7 The flowchart of the error offset tracking module in the present application. DETAILED DESCRIPTION

[0017] The technical solutions in the present application will be described below in combination with the drawings.

[0018] In the embodiments of the present application, the words such as "example", "for example" are used to represent as an example, illustration or description. Any embodiment or design scheme described as "example" in the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. In fact, the word "example" is intended to present the concept in a specific way. In addition, in the embodiments of the present application, the meaning expressed by "and / or" can be both, or can be one of the two.

[0019] In the embodiments of the present application, "image" and "picture" can be used interchangeably at times. It should be pointed out that when the distinction is not emphasized, the meanings expressed are consistent. "Of", "corresponding" and "relevant" can be used interchangeably at times. It should be pointed out that when the distinction is not emphasized, the meanings expressed are consistent.

[0020] In the embodiments of the present application, sometimes the subscript such as W1 can be written in the form of non-subscript such as W1. When the distinction is not emphasized, the meanings expressed are consistent.

[0021] In order to make the technical problems, technical solutions and advantages of the present application more clear, the following will be described in detail in combination with the drawings and specific embodiments.

[0022] The embodiment of the application provides a project working hour statistical analysis system for building design application behavior monitoring and algorithm analysis, as shown in the drawing. Figures 1-2 The project working hour statistical analysis system for building design application behavior monitoring and algorithm analysis comprises the following modules. The page behavior recording module acquires the foreground page behavior record of a user when the user operates design software including AutoCAD, Revit and SketchUp, records the action of the user opening the design software, extracts the design software name and task window identifier for combination, reads the task window switching event and corresponds to the design software use time sequence, segments the operation between tasks and performs timeline serialization processing, constructs a continuous task segment operation flow, and acquires a continuous design operation paragraph. The task trajectory generation module receives the data content sent by the user monitoring plug-in according to the continuous design operation paragraph, identifies the drawing file path and task calling content, combines and splices the path file repeatedly called in the design task, organizes the behavior segment into a continuous structure according to the calling order, strips off irrelevant segments not belonging to the project task range in the behavior, and acquires a design task trajectory segment. The project identifier collection module calls the design server interface to receive the task feedback information in the source path based on the design task trajectory segment, extracts the project number embedded in the drawing path field, connects the project information source data, compares the project type and design stage value, completes the classification operation according to the behavior triggering time and drawing annotation content, and acquires professional task attribution content. The personnel time consumption checking module writes the task responsibility person behavior record into the behavior database according to the professional task attribution content, extracts the task continuous time value of each attribution behavior, performs combined calculation on the task segment time in the behavior database, compares with the user working hour record data, identifies and binds the verifiable time section, and acquires the project working hour distribution quantity. The error offset tracking module extracts and compares the task time section presented by the BI report and the user manual declaration time section in combination with the project working hour distribution quantity, extracts the start and end time difference field and performs parallel division, cross screens the blank time piece in the behavior record and the operation interruption record, identifies the record paragraph with significant offset from the declaration content, and acquires the task execution time offset rate.

[0023] The continuous design operation paragraph includes design software name, task window identification, window switching timing, design task trajectory segment includes drawing file path, task call sequence, irrelevant behavior stripping result, professional task attribution content includes project number field, project type identification, design stage classification, drawing annotation information, project work time length distribution quantity includes attribution task time, combined task period, work hour comparison data, task execution time offset rate includes start and end time difference, blank time segment, operation interruption record.

[0024] Specifically, as shown in Figure 2 , 3 The page behavior record module includes: The software identification sub-module obtains the operation record of the user starting the design software, extracts the process start event, filters the AutoCAD, Revit and SketchUp software names, splices the task window identification, and generates a software task identification label; The system will first extract all process start events from the system-level event log of the user terminal, each event record containing the start time point, process ID, process name, start path, and process state, etc. The system will iterate through these event records one by one and compare the process name field with the preset software identification list. The identification list has fixedly set the process names of the three design software "AutoCAD", "Revit", and "SketchUp". The system uses exact matching logic and does not accept fuzzy matching. For example, "AutoCAD2023" and "AutoCAD" will be considered inconsistent, and only when the process name is exactly "AutoCAD" will it be confirmed. After successful matching, the system immediately retrieves the active window handle generated by the process during running according to the corresponding process ID and calls the window management interface to extract the window title information. The window title often contains the brief name of the current project, such as "City Square Modeling-AutoCAD". The system will segment the title text with spaces or dashes as delimiters and take the first segment "City Square Modeling" as the project identification field. This field is used to further combine with the process name to generate the task label. The label formation is "software name_project identification", and the combination result is "AutoCAD_City Square Modeling". The system writes this result as the task unique identifier into the identification record table. This process is suitable for parallel identification operation of multiple software. If the user starts multiple design tools at the same time, the system will identify each process according to the start order and generate a label for each task window. In the example, if the user starts Revit and SketchUp within 20 seconds, the window titles are "Cultural Center Design-Revit" and "Shop Appearance Sketch-SketchUp", respectively. The system will identify and generate two independent labels "Revit_Cultural Center Design" and "SketchUp_Shop Appearance Sketch" respectively to ensure accurate classification of different software tasks in the future.

[0025] The task switching submodule generates window task switching section information based on the software task identification label, calls the timestamp and foreground window switching record, matches the window handle and software identification, extracts the switching time and compares it with the software usage time sequence. Firstly, the system calls the window focus switching log record in the system, each record in the log contains switching time, window handle before switching and window handle after switching, the system reads each record in turn, queries the process name and title text corresponding to the window according to the window handle after switching, after obtaining the complete window information, the system judges the current window task according to the task identification label generated previously, the judgment method is to parse the window title into "software name_project name" format, then accurately match with the identification label, for example, if the window title after switching is "residential building modeling-Revit", the corresponding label should be "Revit_residential building modeling", if the matching is successful, record the time point as the start time of the task active, and continue to find the time when the window is switched out of focus as the end time of the task, if the task window is switched to focus again in a short time, for example, 10 seconds later, the system records the second active start time, and stores the start and end time of each section in the section record table, the whole process needs to maintain the mapping table of window handle and task label, to ensure that each window switching can be accurately corresponded to a specific task, if there are multiple different task labels alternating switching, the system will accurately distinguish according to the actual window title change, for example, the user switches between "SketchUp_business street scheme" and "AutoCAD_ underground pipe network layout" multiple times, the system will establish multiple task active sections for the two respectively, to ensure that the task section division has the characteristics of clear boundary and no intersection, each task section will contain four kinds of basic data: start time, end time, task label and corresponding window handle.

[0026] The operation sequence construction submodule combines the task sections in time sequence according to the window task switching section information, calculates the time difference between adjacent sections, judges whether it is lower than the minimum interval threshold, merges into continuous operation section, and generates continuous design operation paragraph; First, all segments are sorted in ascending order by start time to construct a complete task time sequence, then the system will process each pair of adjacent task segments in turn, calculate the time difference between the start time of the current segment and the end time of the last segment, and compare the difference with the preset minimum interval threshold, which is set based on the analysis of a large amount of user behavior data. The task switching interval data of 50 designers shows that more than 70% of the task intervals are concentrated between 2 minutes and 3 minutes. In order to ensure the accuracy of operation continuity recognition, the system sets the minimum interval threshold to 150 seconds. This value can be dynamically adjusted to 120 seconds, 180 seconds, etc. according to the user behavior model. The actual deployment takes 150 seconds as the regular recommended value. The system uses this as the basis for judgment. When the interval time between two adjacent segments is less than 150 seconds, they are merged into a continuous operation segment. If the interval is greater than or equal to 150 seconds, it is considered as two independent task segments. For example, the user completes a SketchUp task segment and ends at 12:20:10, and the next Revit task starts at 12:22:00. The interval between them is only 110 seconds, which is less than the threshold, so they are merged into a continuous segment of "SketchUp + Revit". The start and end times recorded after merging are 12:15:40 to 12:29:10. When another task starts at 12:34:40, the interval between it and the end time of the last segment is 330 seconds, which is considered as a new operation segment and recorded separately. After traversing the entire task segment list, the final continuous operation segment is output in chronological order, each segment containing start time, end time, total operation time, and task label list to support subsequent design behavior analysis.

[0027] Specifically, as shown in Figure 2 、 4 the task trajectory generation module includes: The path recognition submodule calls the data sent by the user monitoring plug-in based on the continuous design operation paragraph, extracts the drawing path and task call information, identifies and numbers the repeated paths, records the number sequence in the call order, and generates a repeated path identification sequence. First, activate the local user monitoring plug-in data channel and read the task behavior data reported by the plug-in one by one, which includes fields such as drawing file access path, user click behavior, design tool internal function call record, task scheduling status, etc. The system extracts the drawing path field from the data packet and establishes a temporary path list. Each record in the list is the complete path of the drawing file opened or operated by the user at a certain point in time. The system reads the path data in the list in sequence and performs a complete comparison in the form of a string to determine whether there is a duplicate path. A two-layer traversal method is used in the judgment process. The outer layer traverses the current path item, and the inner layer compares the characters one by one with the registered path items. If the characters are exactly the same and the length is the same, it is considered a repeated call of the same drawing path. The system then assigns a unique number to each path item that appears for the first time, and the number increases automatically starting from 1. The numbering method is as follows: if the current path does not exist in the number registration table, the integer of the current maximum number plus 1 is assigned as the number of the path. For example, the path "D1 Plan" is numbered 1 when it appears for the first time, and reuses number 1 when it appears again. If a new path "D2 Section" appears subsequently, it is numbered 2, and so on. Finally, the number sequence is output according to the path call order. For example, if the continuous access order is "D1 Plan", "D2 Section", "D1 Plan", and "D3 Structure", the number sequence is 1, 2, 1, 3. The number sequence is recorded by the system as a repeated path identification sequence, providing a behavioral chain reference for the path dimension in subsequent behavioral organization and judgment. The entire numbering process remains unique within the same task and will not be reset. Even if the path is switched multiple times in the task segment, the number will not be updated to ensure that the number sequence has accurate tracking capabilities in subsequent analysis.

[0028] The behavior splicing submodule splices the operation behaviors into a structure chain according to the repeated path identification sequence in the order of path numbers, screens the connection points between the differentiated task numbers, extracts the corresponding behavior fragments, and obtains the structured behavior sequence; According to the numbering sequence, read the operation behavior segments corresponding to each number in turn, the behavior segment is composed of the operation set completed by the user under a certain path file, including primitive drawing, command calling, interface operation and other basic actions, the system arranges the operation behaviors in order with path number as index, and adds logical connection relationship between behavior data, constructs path number driven structure chain, for example, the numbering sequence is 1, 2, 1, 3, the composition order of the structure chain is "path 1→path 2→path 1→path 3", the system connects the operation segments corresponding to the numbers one by one, and records the connection position, then the system filters the connection points in the structure chain, judges whether the path numbers before and after the connection are inconsistent, if the connection point is a cross-path connection case between path 1 and path 2, path 2 and path 1, path 1 and path 3, etc., it is marked as a differentiated task connection point, the filtering logic uses inequality judgment method, if the current number and the previous number are not the same, it is determined as an effective connection point, then the system takes these connection points as range defining points to extract the complete behavior segment covered by the connection point from the source data, judges whether the behavior segment meets the continuity condition, that is, the time interval between the operations before and after should not exceed the preset threshold, the system sets the interval threshold to 300 seconds, which is derived from the average interruption time statistics in the design behavior process, collects the first operation time of 120 designers after path switching in the real working environment, calculates the average value as 273 seconds, the system adjusts the threshold to 300 seconds as the standard, if the operation segment on both sides of the connection point is within 300 seconds, it is considered as continuous behavior and is extracted completely, if it exceeds 300 seconds, the connection point behavior segment is excluded and the structure chain is not constructed, finally the system outputs the structure chain spliced according to the path numbering order, each chain contains path number, start and end time, operation set, connection position, whether it is a difference connection and other fields, which constitutes the structured behavior sequence basic data set.

[0029] The trajectory extraction submodule calls the structured behavior sequence, excludes the behavior segments not belonging to the task path according to the path field and task number, and obtains the design task trajectory segment; After reading each behavior segment data, the path number to which the current operation belongs is first obtained from the path field thereof, and the task number field thereof is read, and then the system performs matching judgment according to the path number list called by the task recorded in the task record, which is generated by the path identification module in the task identification process and records all the actual called path numbers in the current task, for example, the path number set of a task is {2, 3, 4}, and when the trajectory is extracted, the path number of the behavior segment is compared with the set, if the number is in the set, it is retained, otherwise it is excluded, the judgment logic adopts the inclusion judgment mode of whether the path number exists in the set, if the path number is 1 and there is no number 1 in the task path set, it is judged that the behavior does not belong to the current task, and the exclusion operation is performed, in addition, the system also judges the task number field, if the task number of the behavior segment is inconsistent with the current processing task number, even if the path number matches, it is excluded, for example, the task number of the behavior segment is A, and the current task number is B, the behavior segment is excluded, to ensure the task consistency of the trajectory extraction, under the above double screening, the system finally retains all the behavior segments that meet the consistency of the path number and the task number, arranges them in the time sequence, forms the task behavior trajectory segment, and records the path number, operation content, operation start and end time, user identifier and the like in the segment, in the actual example, if a user visits path numbers 2, 3 and 4 under task number T1, the behavior segment records the drawing operation of path 3, the parameter adjustment operation of path 2 and the layer management operation of path 4 in turn, the system assembles the three operations into the design task trajectory segment of task T1, as the basic data for subsequent design behavior visualization and behavior chain analysis.

[0030] Specifically, as shown in Figure 2 , 5 the project identifier collection module includes: The task feedback receiving submodule calls the design server interface to receive the task feedback information in the source path based on the design task trajectory segment, extracts the path field and associated task content in the feedback data, judges and excludes the non-response field, and obtains the task path feedback set. First, read the path number, task number and operation start and end time in each track segment as parameters to construct the feedback request body. When the request is initiated, the system organizes the path field, task ID and timestamp range in JSON structure, accesses the task feedback database through the interface, and receives the feedback data set in the interface response. Each feedback record contains fields: path string, task number, feedback type, processing status, feedback time and specific content. The system processes the feedback data in turn, first extracts the path field and compares it with the path list in the original track segment to confirm that it belongs to the operation path within the track task, then judges whether the processing status field of the feedback record is "processed", "read" or "valid". If the field is "no response", "no feedback" or null, the system judges that the feedback is invalid response and excludes the corresponding path from the valid set. This judgment operation is performed through logical comparison, and when the record is excluded, the original path and the reason for exclusion form an error log. Then, the remaining paths are executed for path standardization operation, that is, the redundant spaces, extension differences and case differences in the path are removed to ensure that the same drawing path is not identified as multiple paths due to format problems. In the actual processing example, the system receives 12 feedback data, 8 of which are in the state of "processed" or "read", 3 are in the state of "no response", and 1 feedback content is null. Finally, the system judges that the feedback records corresponding to paths numbered 2, 5 and 7 are invalid feedback and are excluded. The remaining paths are rearranged in chronological order and summarized as a task path feedback set. The feedback set record content includes: path number, task ID, feedback time, processing status, feedback summary, feedback content label and other fields, providing a path and feedback content mapping basis for subsequent project number analysis.

[0031] The project number identification submodule calls the task path feedback set, extracts the project number field embedded in the drawing path, and connects the project information source data. According to the field structure, the project number position is located and the field comparison is completed to obtain the project number list. Each feedback path is parsed one by one, and string splitting is performed in the feedback path field. The embedded segment of the project number is identified according to the path naming convention. The system sets the starting field position of the project number extraction to be generally located in the second or third segment of the path string, and uses "-" or "_" as the field separator for decomposition. For example, if the path string is "Scheme Design-3205-Drawing One", the system identifies the second segment "3205" as the candidate number field, and then performs an accurate string comparison on the field with the system's internal project master data table. The comparison field is the project number column. If the number field extracted from the path is exactly the same as any number in the project master data table, the system records the number as a valid identification number and puts it into the project number list. If the number does not hit the data table, or there is an abnormal number of field digits (for example, less than 4 digits or more than 8 digits), the system marks the path as "number". "Parsing failed" is not included in the project number list. A number recognition threshold is also set during the path parsing process, that is, the position offset of the number field must not exceed the first 4 segments of the path structure. If the number field appears in the 5th segment or later of the path structure, it is marked as a structure out of bounds and removed. This threshold is set based on statistics of actual project path naming specifications. 90% of valid number fields are located between the 2nd and 4th segments. Based on this, the system sets the field position threshold as the first 4 segments. In an actual recognition task, a total of 10 path feedback records were processed, and the successfully recognized numbers were "2103", "4211", and "3817". Among them, the number field "0812" of the path "Drawing_D-0812" was excluded because it was located in the 5th segment. The final generated project number list is 2103, 4211, and 3817. Each item has been matched with the project master data table and confirmed to be valid.

[0032] The attribution content determination submodule compares the project type value and design stage value corresponding to the project number list, and combines the behavior trigger time in the drawing annotation content with the timestamp range in the field to make a classification judgment and obtain the attribution content of the professional task; According to the item number in the list, first read the item type field and design stage field corresponding to the number in the item master data table, for example, the number 2103 corresponds to the type field "residence" and the stage field "expansion initial", then the system calls the drawing annotation data set, extracts the trigger time field and related task number field in the annotation behavior, and performs grouping mapping processing according to the project number. The system determines whether a certain annotation behavior should belong to the corresponding project number, which needs to meet three conditions at the same time. The first is that the task number of the behavior needs to have a clear matching relationship with the project number. The second is that the annotation time needs to fall within the allowed attribution time range. The third is that the item type field and the design stage field need to meet the effective matching rule. The matching rule is that the task type value is the same, the stage value is consistent or adjacent. For example, the "expansion initial" stage and the "initial design" stage can be considered as adjacent stages and are allowed to be attributed. If it is between "construction drawing" and "scheme", it is considered as different stages and is not classified. In terms of time judgment, the system sets the threshold for timestamp comparison to ±1 day. That is, if the task record time is 08:00, the annotation trigger time needs to be between 08:00 of the previous day and 08:00 of the next day. The threshold is set based on the analysis of the peak time period in the design project feedback set. The peak mainly occurs within 24 hours before and after the task processing node, which meets the engineering collaboration rhythm. If the annotation behavior time exceeds this range, even if the type and stage match, it is excluded. In a task processing, the number 2103 corresponds to 4 annotation behaviors. Among them, 3 behaviors fall between 08:00 and 07:30 of the next day, and the stage matching is "expansion initial", and the type matching is "residence". It is determined as an effective attribution behavior. Number 4211 is excluded because one of the annotation behaviors has a time of 10:45 the next day. Number 3817 has no matching stage field behavior. Finally, the system outputs 7 effective attribution behavior entries, and constructs a professional task attribution content structure set.

[0033] Specifically, as shown in Figure 2 、 6 , the personnel time consumption approval module includes: The behavior writing submodule writes the behavior record of each task corresponding to the responsible person based on the professional task attribution content into the behavior database, extracts the start time and end time fields of each attribution behavior, and generates a time period record to obtain a task behavior time period set. Firstly, the key contents in the attribution data, such as the responsible person field, task number field, behavior type field, start time and end time field, are read. Before writing, the system will check whether the behavior time field format conforms to the "hour: minute: second" structure. If the field is missing or the format is abnormal, the record will not be entered, and will be marked as "time field abnormal" in the log table. The remaining records create new behavior entries in the behavior database. The system writes the attribution task number as the primary key index into the user behavior record table, and establishes a partition storage under the responsible person dimension to ensure that the behavior records of each designer are clearly attributed. Then the start time and end time fields are extracted from the attribution behavior, and are uniformly converted into timestamp format for subsequent operation processing. For example, "08:15:00" is converted into timestamp 29500 (counting seconds from 00:00 of the day as the starting point). The system calculates the duration of a single behavior segment according to the start and end time, stores it in seconds, and records the "behavior start point", "behavior end point" and "duration" fields in the data set as the core structure for building the time period set. In a typical processing task, 36 attribution behaviors are processed, 2 of which are excluded due to missing end time field records, and 34 behavior records are successfully written. The generated task behavior time period set is classified according to the responsible person, and the time period list corresponding to the 6 designers is finally obtained. Each time period entry clearly identifies the responsible person, task number, operation start and end time, and behavior duration information.

[0034] The time calculation submodule calls the task behavior time period set, merges the time periods that exist in the differentiated attribution behavior of the same responsible person, and retains the start and end time of the merged segment to generate the behavior time accumulation value. According to the responsibility field, the preliminary grouping is ensured that the time periods of different personnel do not interfere with each other, the system sorts the data in each group in ascending order according to the start time field, and then performs cross detection and continuous judgment processing on the sorted time period sequence. The cross detection standard is: if the start time of the current time period is less than the end time of the last time period, and the end time is later than the end time of the last time period, then the two periods are cross periods, and merging is performed. The continuous judgment standard is: if the interval between the start time of the current time period and the end time of the last period is not more than 60 seconds, it is considered as a continuous period, and merging is also performed. The 60-second time interval threshold is a standard set by the system according to the statistical operation behavior interval of the design industry. After 1800 real operation behavior data are counted, it is found that more than 98% of the task behavior intervals are less than or equal to 1 minute, so 60 seconds is used as the judgment threshold. When performing the merging operation, the system retains the earliest start time and the latest end time after merging, and calculates the behavior time length in the range, and records it in the newly generated merged behavior item. After merging, the system traverses the next time period again, and repeats the above judgment logic until all the time periods of the current responsibility person are traversed. In a sample, the responsibility person has 7 time records, among which the interval between the 2nd period 08:45:00-09:10:00 and the 3rd period 09:10:30-09:40:00 is 30 seconds, which meets the continuous condition and is merged into 08:45:00-09:40:00. The 7 original time periods of the responsibility person are finally merged into 4 continuous time periods, and the behavior time cumulative value is the sum of the time lengths of all the merged periods, which is recorded in minutes. The "merging times" field is also attached in the record for later frequency statistics.

[0035] The time length determination sub-module compares the time start and end intervals in the two data sets according to the behavior time cumulative value and the time period field in the user work time record data, and selects completely verifiable time periods to obtain the project work time length distribution. The user work hour record data is called as a reference, each entry of which contains the responsible person ID, work start time, work end time, project number and punch card identification. The system performs a table matching operation according to the responsible person field. The core of comparison is whether the two time period data sets have a complete coverage relationship. The judgment logic of the coverage relationship is as follows: if the start time of the behavior time period is greater than or equal to the start time of a work time period, and the end time of the behavior is less than or equal to the end time of the work time period, it is judged that the behavior time period is completely contained, that is, it is an effective match. If only part of it overlaps or there is a time period extending before and after, it is determined that it is not completely verified and is rejected. The requirement for time accuracy is minute level, that is, the maximum error is ± 59 seconds. If it exceeds 1 minute, it is considered as a deviation segment and is not confirmed. The tolerance is set based on the time floating range allowed by the system when comparing the attendance punch record. It is found through analysis that the manual punch card of the designer has an error of 20-40 seconds. The system finally sets the accuracy threshold to 60 seconds within which it is determined to be matched. If it exceeds, it is not counted as effective time. In one comparison, the cumulative behavior time period of the responsible person is 3, the time is 08:05-09:00, 09:10-10:15 and 10:30-11:20, and the work time record is 08:00-12:00. Therefore, all behavior segments fall within the work time period and are marked as "complete coverage". The system records the verification status as "confirmable" and the cumulative working hours as 195 minutes. If one of the behavior segments of another responsible person is 13:00-13:30, and its daily work time period is 13:10-17:00, then because the front part of the behavior segment is not covered for more than 10 minutes, this segment is marked as "partial coverage" and is rejected. Finally, the system generates a project work time distribution table, which records the effective working hours of each responsible person, the number of successful segments, the number of failed segments and the project number.

[0036] Specifically, as shown in Figure 2 , 7 The error deviation tracking module includes: The time difference extraction submodule extracts the task time period and the user manual reporting time period of the BI report record based on the project work time distribution, compares the start and end values of the two time fields according to the task number, calculates the difference field, and then classifies the difference field according to the task sequence number to obtain the task time difference sequence. Firstly, the manual reporting time period of each task recorded in the historical report is read from the BI system, and the actual system record time period of task execution is extracted from the behavior database. Both data sets are classified and organized according to the task number. The system compares the start time and end time fields of the two time period data sets for each task number item. The comparison rule is: if the start time recorded by the system is earlier than the manual reporting time, the pre-difference is the time difference between the two, if the end time recorded by the system is later than the manual reporting time, the post-difference is the corresponding end time difference, both the pre-difference and the post-difference are calculated in minutes and recorded in the difference field, if the time period is completely consistent, the difference is 0, then the difference field is bound to the task number to build a difference record item. In the actual processing process, the system finds that some tasks have time reverse filling behavior, that is, the user manually reports the time period earlier than the system behavior record time period. The system also records the difference in this case but adds the "direction abnormality" mark. In the processing example, the system record time period of task T001 is 08:00-10:00, the user manually reports 08:15-09:45, then the system calculates the pre-difference as 15 minutes, the post-difference as 15 minutes, and the total difference as 30 minutes. The difference item is recorded as "T001_30". After completing the difference field construction, the system sorts all difference record items in ascending order of task number and assigns a sequence number for classification statistics, finally forming a task time difference sequence, each record contains task number, pre-difference, post-difference, total difference, difference direction, difference sequence number and other fields.

[0037] The blank screening submodule calls the task time difference sequence, compares the operation time period of the corresponding task in the behavior database, detects the blank time segment and operation interruption record in the time period, screens the behavior points without bound reporting records in the time period, and obtains the non-reporting behavior segment set. The system reads the task number corresponding to each difference record one by one, calls the operation time period set of the task in the behavior database, constructs a time interval sequence for all operation records according to the start and end time, and performs a blank section detection operation in each difference time period interval. The method is to traverse the task operation behavior set, compare the start and end time of each operation behavior with the difference time period interval, judge whether there is a segment that is completely not covered by any operation behavior, and if it is found that there is a time interval between two continuous operation behaviors, and the interval time is greater than the system set operation interruption judgment threshold, it is considered that there is a blank segment. The judgment threshold is set to 120 seconds by default, which is derived from the average click interval time statistics of the design class task operation behavior. According to the long-period use data collected by the project operation team, if the user operation interval exceeds 2 minutes, it can be preliminarily judged as non-continuous behavior or idle period. The system sets the screening threshold to 120 seconds. In the actual screening process, the difference time period of task T001 is 08:00-08:15, and the operation behavior record is 08:02-08:06 and 08:08-08:10. Then the system marks 08:00-08:02, 08:06-08:08 and 08:10-08:15 as blank segments. Further judge whether these segments have a binding relationship with the user manual declaration data. The system matches the task number and operation person field by comparing the behavior record and the work time declaration data. If no matching item is found, it is marked as "non-declaration behavior point". Finally, the system outputs all non-declaration binding blank behavior segments as non-declaration behavior segment set, including task number, time segment start and end time, segment length, whether there is behavior data, whether it is associated with declaration record, etc.

[0038] The offset rate identification submodule calculates the time length of each segment according to the non-declaration behavior segment set and performs ratio calculation with the corresponding item in the task time difference sequence. The records with offset degree exceeding the declaration segment length threshold are marked as offset paragraphs, and the task execution time offset rate is obtained. According to each time period in the non-declaration behavior fragment set, the system sequentially counts the time length, the unit is unified as minute, and associates the corresponding total difference value field in the task time difference value sequence according to the task number, then calculates the ratio of the time length of each non-declaration behavior fragment to the total time length of the task difference value, the calculation method is to divide the current fragment length by the total difference value time length, and the single fragment offset ratio is obtained, then the sum of all fragment offset ratios is obtained to obtain the total offset proportion, then the system judges the offset ratio, if the ratio is greater than the offset judgment threshold, the behavior fragment is marked as a deviation paragraph, the offset judgment threshold is set to 0.5, and the setting basis is that the company operation management system clearly indicates that more than 50% of the task time period exists non-declaration behavior, which is regarded as deviation behavior, the value is a fixed strategy value, and is not accepted by the user to define, for example, the total time length of task T001 is 30 minutes, there are three non-declaration behavior fragments under it, the lengths are 4 minutes, 5 minutes and 9 minutes respectively, the system calculates the offset rate as 0.133, 0.167 and 0.3 respectively, and the sum of the three is 0.6, which has exceeded the threshold, the system marks task T001 as a whole as 'there is deviation', and marks fragment 3 as 'cumulative deviation segment', and the system finally outputs the task execution time offset rate list, wherein each record contains task number, offset fragment number, cumulative offset minute number, offset rate, whether the threshold is exceeded, and whether it is a serious deviation paragraph, for subsequent quality checking and attendance auditing reference.

[0039] The above is only a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, any person skilled in the art can easily think of changes or replacements within the technical range disclosed by the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. The project working hours statistics analysis system for architectural design application behavior monitoring and algorithm analysis is characterized by: The system comprises: The page behavior recording module obtains the user's foreground operation behavior when using the design software, records the software startup action, extracts the software name and task window identifier, identifies the window switching event and corresponds it to the operation sequence, segments the task operation and serializes the timeline, and extracts continuous design operation segments; The task trajectory generation module receives monitoring plug-in data based on the continuous design operation segments, identifies the drawing path and task call content, splices repeated call path files, removes behavior segments that are not related to the task, and generates design task trajectory segments; The project identification collection module calls the design server interface through the design task trajectory fragment, extracts the project number in the drawing path, connects the project information source, compares the project type and design stage, completes the classification based on the behavior time and the drawing annotation content, and obtains the professional task attribution content; The personnel time consumption verification module writes the responsible person's behavior into the database according to the professional task attribution content, extracts the continuous time value of each task and combines them for calculation, compares them with the user's working time records, identifies the verifiable time segments, and obtains the distribution of project working time.

2. The project work-hour statistics and analysis system for architectural design application behavior monitoring and algorithm analysis according to claim 1 is characterized by: The continuous design operation segment includes the design software name, task window identifier, and window switching timing; the design task trajectory segment includes the drawing file path, task call sequence, and irrelevant behavior stripping results; the professional task attribution content includes the project number field, project type identifier, design stage classification, and drawing annotation information; the project work time distribution includes the attribution task time, merged task period, and working time comparison data.

3. The project work-hour statistics and analysis system for architectural design application behavior monitoring and algorithm analysis according to claim 1 is characterized by: The task-independent behavior fragments refer to non-design operation records that do not have project drawing editing, viewing, and task calling paths; The verifiable time period refers to a continuous working period in which the behavior records are consistent with the user's working hours declaration and can be cross-verified through operation data.

4. The project work time statistics analysis system for architectural design application behavior monitoring and algorithm analysis according to claim 1 is characterized in that: The page behavior recording module includes: The software identification submodule obtains the operation record of the user starting the design software, extracts the process start event, filters the design software name, and splices it with the task window logo to generate a software task identification tag; The task switching submodule, based on the software task identification tag, calls the timestamp and the foreground window switching record, matches the window handle and the software identifier, extracts the switching time and compares it with the software usage sequence to generate the window task switching segment information; The operation sequence construction submodule combines task segments in chronological order according to the window task switching segment information, calculates the time difference between adjacent segments, determines whether it is below the minimum interval threshold, merges them into continuous operation segments, and generates continuous design operation sections.

5. The project work-hour statistics and analysis system for architectural design application behavior monitoring and algorithm analysis according to claim 1 is characterized in that: The task trajectory generation module includes: The path identification submodule calls the data sent by the user monitoring plug-in based on the continuous design operation section, extracts the drawing path and task call information, identifies and numbers the repeated paths, records the number sequence in the calling order, and generates a repeated path identification sequence; The behavior splicing submodule splices the operation behaviors into a structure chain in the order of path numbers according to the repeated path identification sequence, screens the connection points between the differentiated task numbers, extracts the corresponding behavior fragments, and obtains a structured behavior sequence; The trajectory extraction submodule calls the structured behavior sequence, excludes the behavior segments that do not belong to the task path according to the path field and the task number, and obtains the designed task trajectory segments.

6. The project work time statistics analysis system for architectural design application behavior monitoring and algorithm analysis according to claim 1 is characterized in that: The project identification collection module includes: The task feedback receiving submodule calls the design server interface to receive task feedback information in the source path based on the designed task trajectory fragment, extracts the path field and associated task content in the feedback data, judges the path and filters out the unresponsive fields to obtain the task path feedback set; The project number identification submodule calls the task path feedback set, extracts the project number field embedded in the path, connects to the project information source data, locates the project number position according to the field structure, completes field comparison, and obtains a project number list; The attribution content determination submodule compares the project type value and the design stage value corresponding to the number according to the project number list, and combines the behavior trigger time in the drawing annotation content to compare the timestamp range in the field for classification judgment to obtain the attribution content of the professional task.

7. The project work time statistics analysis system for architectural design application behavior monitoring and algorithm analysis according to claim 1 is characterized in that: The personnel time-consuming verification module includes: The behavior writing submodule writes the behavior record of the person in charge of each task into the behavior database based on the professional task attribution content, extracts the start time and end time fields of each attribution behavior, generates a time period record, and obtains the task behavior time period set; The time calculation submodule calls the task behavior time period set, merges the overlapping and continuous time periods in the differentiated attribution behaviors of the same responsible person, retains the start and end times of the merged segments, and generates a cumulative behavior time value; The duration verification submodule compares the accumulated value of the behavior time with the time period field in the user's working time record data, compares whether there is an overlapping relationship between the time start and end intervals in the two data sets, and selects completely verifiable time periods to obtain the distribution of project working time.

8. The project work-hour statistics and analysis system for architectural design application behavior monitoring and algorithm analysis according to claim 1 is characterized in that: The system further comprises: The error offset tracking module combines the distribution of project working hours, compares the report with the manually reported time period, extracts the start and end time difference and classifies it, cross-analyzes blank time and interruption records, identifies the offset record segments, and calculates and obtains the task execution time offset rate.

9. The project work-hour statistics and analysis system for architectural design application behavior monitoring and algorithm analysis according to claim 8 is characterized by: The task execution time offset rate includes the start and end time difference, blank time segments, and operation interruption records.

10. The project work-hour statistics and analysis system for architectural design application behavior monitoring and algorithm analysis according to claim 8 is characterized in that: The error offset tracking module includes: The time difference extraction submodule extracts the task time period recorded in the BI report and the user's manually declared time period based on the distribution of the project working time, compares the start and end values ​​of the two time fields by task number, calculates the difference field, and then classifies the difference field by task sequence number to obtain the task time difference sequence; The blank screening submodule calls the task time difference sequence, compares the operation time period of the corresponding task in the behavior database, detects the blank time segments and operation interruption records within the time period, screens the behavior points that are not bound to the declaration record within the time period, and obtains the non-declared behavior segment set; The offset rate identification submodule counts the time length of each segment based on the non-declared behavior segment set and calculates the ratio with the corresponding item in the task time difference sequence, marks the records whose offset degree exceeds the declared segment length threshold as deviation segments, and obtains the task execution time offset rate.

Images