TW202301143A - System and method of managing report - Google Patents

Abstract

A system for managing a report comprises a generating module, for receiving a data of a first user and for generating a first report according to the data; an associating module, coupled to the generating module, for determine a first content of a second report according an association between the first report and the second report; and a notifying module, coupled to the associating module, for notifying a managing result of the first report and the second report to the first user and a second user, wherein the second user is associated with a project corresponding to the first report.

Description

System and method for managing reports

The present invention relates to a system and method for management reporting.

When the user wants to store the report in the public storage space, the user must generate the report on his computer device and store the report in the public storage space. When the user wants to update the report to the public storage space, the user must perform the above operations repeatedly to store the updated report in the public storage space. When the user wants to obtain reports from the public storage space, if the public storage space has no sorting or sorting rules, the user must rearrange and sort the reports in the public storage space, and confirm whether there is an update in the public storage space and which report is the latest version of the report. When a user wants to access the public storage space from outside the enterprise, the user must access the public storage space through a network domain or personnel within the enterprise.

However, the above operations will consume a lot of time for the user, not only making it difficult for the user to efficiently or timely store the report in the public storage space, but also make it difficult for the user to efficiently or timely obtain the report from the public storage space. Report. In the case that the common storage space is not organized or sorted, it is difficult to effectively utilize the common storage space. Therefore, how to manage the reports so that the users can efficiently access the reports and the public storage space can be effectively used is an urgent problem to be solved.

The present invention provides a system and method for managing reports to solve the above problems.

The invention discloses a system for managing reports, which includes a generating module used to receive a data of a first user, and generate a first report according to the data; an associated module coupled to the generated a module for determining a first content of the second report according to an association between the first report and a second report; and a notification module coupled to the association module for notifying the first report A report and a management result of the second report to the first user and a second user, wherein the second user is associated with a project corresponding to the first report.

The present invention further discloses a method for managing reports, which is used for managing the above reports.

FIG. 1 is a schematic diagram of a computer network 10 according to an embodiment of the present invention. As shown in FIG. 1 , the computer network 10 includes a management reporting system 100 and at least one user 110 . In one embodiment, at least one user 110 can transmit (eg, store or upload) data to the reporting management system 100 through a computer device. According to the data received from at least one user 110 , the system 100 for managing reports can generate a report, and can notify the at least one user 110 of the management result of the report. In one embodiment, the computer device may include a device for connecting to the system 100 for managing reports, such as a desktop computer, a notebook computer, a tablet computer, or a mobile phone (such as a smart phone), but is not limited thereto.

FIG. 2 is a schematic diagram of a management report system 20 according to an embodiment of the present invention, which can be used in the management report system 100 in FIG. 1 . As shown in FIG. 2 , the report management system 20 includes a generation module 200 , an association module 210 and a notification module 220 . In detail, the generation module 200 can be used to receive the data of the first user (such as the first user among the at least one user 110 in FIG. 1 ), and according to the data, the generation module 200 can generate the first report. The association module 210 is coupled to the generation module 200 and can be used to determine (for example, generate) the first content of the second report according to the association between the first report and the second report. The notification module 220 is coupled to the association module 210, and can be used to notify the management results of the first report and the second report to the first user and the second user (such as the second user in at least one user 110 in FIG. 1 ). user). In one embodiment, the second user may be associated with (eg, belongs to) the project corresponding to the first report.

In an embodiment, the first user may include an internal person of an enterprise or a manufacturer. In an embodiment, the second user may include internal personnel of the enterprise, manufacturers or customers. In one embodiment, internal personnel of the enterprise may include institutional personnel (such as institutional engineers), designers (such as design engineers), process personnel (such as process engineers), circuit board personnel (such as circuit board engineers), testers (such as test engineer), line assembler or project/product manager (such as project manager). In one embodiment, a vendor may include a supplier.

In one embodiment, according to (eg by using) the encoding information, the generation module 200 can generate the encoding of the first report. In one embodiment, the encoded information may include at least one of the following information: time (such as date) or version. In one embodiment, the encoded information may include the report type. In one embodiment, the first report may be organized (eg, categorized, filed, or sorted) according to (eg, by using) the encoding of the first report.

In an embodiment, the data may include at least one of the following information: images (such as images or photos) or text descriptions. In one embodiment, the image may include a 2D image or a 3D image. In one embodiment, the text description may include the quantity of the parts. That is to say, by enabling the first user to send data in a specific format, the generation module 200 can generate the first report with a specific format.

In one embodiment, the association may include (eg being) the first report and the second report corresponding to (eg belonging to) the project. In one embodiment, projects can be implemented according to (eg, by using) folders. That is to say, in the system 20 for managing reports, a file folder can correspond to a project.

In an embodiment, the field corresponding to the first content may be included in the first report. That is, the first report and the second report contain the same fields. In one embodiment, according to the second content corresponding to the fields in the first report, the correlation module 210 may determine (for example, generate) the first content. That is to say, the association module 210 can automatically substitute the second content into the first content, that is, replace the first content with the second content. For example, the first report contains specific fields (such as FAI C2 and specification standards), which correspond to the second content (such as -4.100), when the correlation module determines (such as detects) and the first When the second report belonging to the same project also includes the specific field, the association module 210 can automatically substitute the second content into the first content corresponding to the specific field in the second report, that is, the first content is- 4.100. It should be noted that this example is only an embodiment of the present invention, but not limited thereto.

In one embodiment, the notification module 220 can notify the first user and the second user of the management result through the communication software or the bulletin board of the login screen of the management report system 20 . In one embodiment, the notification module 220 can notify the first user and the second user of the confirmation reply (such as a button) of the management result through the communication software or the bulletin board of the login screen of the management report system 20 . By confirming (for example, clicking or pressing) the confirmation reply, the first user and the second user can notify the management result is confirmed to the management report system 20 . In one embodiment, the communication software may include email software (such as Outlook or Gmail), but is not limited thereto.

In one embodiment, the management result includes at least one of the following information: the first update information of the first report, the second update information of the second report, the third update information of the data, the progress of the project or the pending completion of the project matter.

In one embodiment, when the generation module 200 determines that the data includes an update, the notification module 220 can notify the first user and the second user of the third update information of the data through the management result. In one embodiment, according to the change of the data, the generating module 200 determines that the data includes an update. For example, according to the change of the data sent by the first user (such as the change of the workstation, the change of the process step, the change of the tolerance analysis method or the change of the measurement specification), the generating module 200 determines that the data contains an update, through the management In the bulletin board of the login screen of the reporting system 20, the notification module 220 can notify the first user and the second user of the third update information of the data.

In one embodiment, when the generation module 200 determines that the data (such as the image of the completed part assembly and the quantity of the parts) includes an update, according to the comparison between the data and the previously transmitted data, the generation module 200 can determine (such as analysis ) information is incomplete (such as incomplete assembly of parts). When the generation module 200 determines that the data is incomplete, the generation module 200 can generate debug information, and by managing the results, the notification module 220 can notify the third update information and debug information associated with the data to the first user and second users. In an embodiment, the comparison of the data with the previously transmitted data may include a comparison of 2D images, a comparison of 3D images, or a comparison of the number of parts. In one embodiment, according to the debugging information, the first user can debug by modifying data. In one embodiment, the first user can send the modified data to the management report system 20, and the generation module 200 can repeat the above operations. In one embodiment, the first user may repeatedly send the modified data to the reporting management system 20 until the first user does not receive the debugging information.

In one embodiment, the first user is (for example) set by the administrator of the project with a login method and access authority. In one embodiment, the access authority of the first user can be set to save data or obtain reports. In one embodiment, when the second user is an internal employee of the enterprise, the access authority of the second user can be set to save data or obtain reports. In one embodiment, when the second user is a manufacturer, the access authority of the second user can be set to save data or obtain reports. In one embodiment, when the second user is a client, the access authority of the second user can be set to obtain reports.

In one embodiment, before creating a project, according to the needs of the project, the project manager can dynamically adjust (for example, add or remove) the users of the project, and can set the login method and access of the users of the project authority. In one embodiment, the project manager can add a first user or a second user of the project, and can set the login method and access authority of the first user or the second user. In one embodiment, during project creation, according to the needs of the project, the project manager can dynamically adjust (for example, add or remove) the users of the project, and can set the login method and access of the users of the project authority. In one embodiment, the project manager can remove the first user or the second user, and can reset (for example modify) the login method and access authority of the first user or the second user. In one embodiment, the project manager can add a third user of the project, and can set the login method and access authority of the third user.

In one embodiment, when the fourth user who has not been set with the access authority of the project logs into the report management system 20, the report management system 20 will not display (such as a bar) information (such as a list of reports) associated with the project or report). That is to say, the fourth user who has not been set the access authority of the project cannot access (for example, browse) the information of the project. In one embodiment, the report of the project (eg, the first report or the second report) may be (eg, be) set with a copy protection mechanism by the project manager.

In one embodiment, the generation module 200 is configured to receive a request from a second user, wherein the request includes searching for the first report. Upon request, the generating module 200 may display all reports associated with the first report (eg, all versions of the first report). The second user can obtain the latest version or any version of the first report. In one embodiment, when the generation module 200 receives the information of the first user and generates an updated version of the first report, the notification module 220 can notify the second user of the first update information of the first report. By logging into the reporting management system 20, the second user can obtain an updated version of the first report.

In one embodiment, the system 20 for managing reports may be integrated (eg, linked to) a system for managing products (eg, a product data management system). Through the system 20 for managing reports, the first user, the second user or the third user can obtain (for example, retrieve) the information of the system for managing products, and can use the functions of the system for managing products (such as querying product images or for product information).

In one embodiment, the system for managing reports 20 may be integrated (eg, linked to) a system for managing parts (eg, integrating mechanism and layout database systems). Through the system 20 for managing reports, the first user, the second user, or the third user can obtain (for example, retrieve) the information of the system for managing parts, and can use the functions of the system for managing parts (for example, query part images , get parts information or apply for new parts).

In one embodiment, the reporting management system 20 may be integrated (eg, linked to) a travel management system. Through the management report system 20, the first user, the second user or the third user can obtain (for example, retrieve) the information of the attendance management system, and can use the functions of the attendance management system (for example, query employee Basic information (such as communication method, affiliation or title), making a business trip application, replying (such as approving or disapproving) a business trip application, making a leave application or responding (such as approving or disapproving) a leave application).

In one embodiment, the reporting management system 20 may be integrated (eg, linked to) a product barcode reading system. Through the system 20 for managing reports, the first user, the second user or the third user can obtain (for example, capture) the information of the product barcode reading system (such as the production process, test results or dimensions of the product), and Capabilities of systems that can use product barcode reading (for example, to read a product's barcode). In one embodiment, according to the information of the system read by the product barcode, the first user, the second user or the third user can generate (for example predict) the product assembly completion result.

FIG. 3 is a schematic diagram of a user data transmission interface 30 of a management reporting system 20 according to an embodiment of the present invention, which can be used for users to input data and receive user data. As shown in FIG. 3 , the user transmission data interface 30 may include a homepage column 300 , an institution column 301 , a circuit board column 302 , a process column 303 , a design column 304 or a supplier column 305 . The home page column 300 can be used for the user to go to the main page, the organization column 301 can be used for the user to enter data on the page of the organization personnel, the circuit board column 302 can be used for the user to input data on the page of the circuit board personnel, and the process Column 303 can be used for users to enter data on the page of the process personnel, design column 304 can be used for users to input data on the page of designers, and supplier column 305 can be used for users to input data on the page of suppliers . As shown in FIG. 3 , the supplier column 305 is drawn with dotted lines, which means that the current page is the supplier's page, that is, the user enters data on the supplier's page.

As shown in FIG. 3, the user transmission data interface 30 may include a model name field 310, a part name field 311, a test field 312, a part image field 313, a plan field 314, and an actual field 315 or field 316 next. The model name field 310 can be used for the user to input a model name, such as "Sentry", but not limited thereto. The component name field 311 can be used for the user to input a component name, such as “snty_12_disp_hinge_cover_1”, but not limited thereto. The test field 312 can be used for the user to input the test period, such as "T0", but not limited thereto. The component image field 313 can be used to display images uploaded by users, such as the image shown in FIG. 3 , but not limited thereto. The plan field 314 can be used for the user to input (eg select) the plan execution time, such as "04-10", but not limited thereto. The actual field 315 can be used for the user to input (eg select) the actual execution time, such as "04-15", but not limited thereto. Secondly, the field 316 can be used for the user to input (for example, select) the next execution time, for example, as shown in FIG. 3 , the user has not input, but it is not limited thereto.

As shown in Figure 3, the user transmission data interface 30 can include report items, and the report items can include item column 320, defective item content (including mold defective item) column 321, cause analysis column 322, countermeasure column Bit 323, image upload field 324, status field 325, description field 326 or delete field 327. The item field 320 can be used to display (eg, bar) the bad items entered by the user. The field 321 of defective item content (including mold defective item) can be used for the user to input content related to the defective item, such as "profile size NG", but not limited thereto. The reason analysis field 322 can be used for the user to input the cause analysis of the defective item, such as "aluminum extrusion aluminum extrusion die NG", but not limited thereto. The countermeasure field 323 can be used for the user to input a countermeasure for solving the defective item, such as "re-modeling", but not limited thereto. The image upload field 324 can be used for the user to choose to upload the part image (eg displayed as the part image 313 ) or delete the part image 313 . The status field 325 can be used for the user to input (eg, select) the status of the defective item, such as "OK", but not limited thereto. The description field 326 may be used for the user to input other notes associated with the defective item. The delete field 327 can be used for the user to delete the corresponding bad item, for example, the bad item corresponding to the item "1". That is to say, through the above-mentioned data input by the user or the image uploaded, the report management system 20 can receive the user's data and generate a report accordingly.

It should be noted that the above description in FIG. 3 only illustrates the content related to the present invention. As is well known to those skilled in the art, the user transmission data interface 30 may include other report-related columns, buttons, and /or tools, such as type column, all column, display column, top column, bottom column, other column, category column, sub-station column, mold manufacturer column, Model maker column, data upload column, mold scheduling column, program flow column, fixture list column, inspection tool list column, mold drawing column, but not limited to these.

FIG. 4 is a schematic diagram of a report list 40 of the report management system 20 according to an embodiment of the present invention, which can be used to display a list of generated reports. As shown in FIG. 4, the report list 40 may include an item field 400, a risk level field 401, an occurrence time field 402, a part name field 403, a category field 404, a creation time field 405, and a part image Column 406, owner column 407, issue column 408, cause analysis column 409, issue period column 410 or file upload column 411.

As shown in FIG. 4, an item field 400 may be used to display (eg, bar) the generated report. The risk level column 401 can be used to display the risk level of the report, for example, according to the text "high", "medium" or "low", or according to the color from dark to light to represent the risk level from high to low, but not limited to this . The occurrence time field 402 can be used to display the occurrence time of the report, such as "2021-2-9", but not limited thereto. The part name field 403 can be used to display the part name in the report, such as "snty_12_disp_hinge_cover_1", but not limited thereto. The category field 404 can be used to display the category field in the report, such as "IEC OPEN", but not limited thereto. The build time column 405 can be used to display the build time of the report, such as "SYSTEM BUILD", but not limited thereto. The part image column 406 can be used to display the part image in the report, such as the image shown in the part image column 313 in FIG. 3 , but not limited thereto. The owner field 407 can be used to display the owner of the report, such as "supplier", but not limited thereto. The topic column 408 can be used to display the content of defective items in the report (including mold defective items), such as "profile size NG", but not limited thereto. The cause analysis column 409 can be used to display the cause analysis in the report, such as "aluminum extrusion aluminum extrusion die NG", but not limited thereto. The issue period column 410 can be used to display the period of the content of the bad items (including mold bad items) in the report. The file upload field 411 can be used for the user to upload data or files related to the report, but not limited thereto.

It should be noted that the description in FIG. 4 above only illustrates the content related to the present invention. As is well known to those skilled in the art, the report list 40 may include other fields, buttons, and/or tools related to reports. , but not limited to this.

FIG. 5 is a schematic diagram of a report 50 generated by the report management system 20 according to an embodiment of the present invention. As shown in Figure 5, the report 50 can include a model name column 500, a part name column 501, a part image column 502, an item column 510, a defective item content (including mold defective item) column 511, and a reason Analysis column 512 , countermeasure column 513 , test column 514 , plan column 515 , actual column 516 or status column 517 .

As shown in FIG. 5 , the model name column 500 can be used to display the model name input by the user, such as "Sentry", but not limited thereto. The component name field 501 can be used to display the component name input by the user, such as “snty_12_disp_hinge_cover_1”, but not limited thereto. The component image column 502 can be used to display images uploaded by users, such as the image shown in the component image column 313 in FIG. 3 , but not limited thereto. The item field 510 can be used to display (eg, bar) the bad items entered by the user. The field 511 of defective item content (including mold defective item) can be used to display the content related to the defective item input by the user, such as "profile size NG", but not limited thereto. The cause analysis column 512 can be used to display the cause analysis of the defective item input by the user, such as "aluminum extrusion aluminum extrusion die NG", but not limited thereto. The countermeasure field 513 can be used to display countermeasures input by the user to resolve the defective items, such as "re-modeling", but not limited thereto. The test field 514 can be used to display the test period input by the user, such as "T0", but not limited thereto. The plan field 515 can be used to display the plan execution time input by the user, such as "04-10", but not limited thereto. The actual field 516 can be used to display the actual execution time input by the user, such as "04-15", but not limited thereto. The status field 517 can be used to display the status of the defective item input by the user, such as "OK", but not limited thereto.

It should be noted that the description in FIG. 5 above only illustrates the content related to the present invention. As is well known to those skilled in the art, the report 50 may include other columns, buttons or tools related to the report, but is not limited to this.

FIG. 6 is a schematic diagram of a material preparation schedule 60 in a management report system 20 according to an embodiment of the present invention, which can be a user interface for transmitting data, and can be used for users to input data and receive user data. As shown in FIG. 6 , the material preparation schedule 60 may include a program field 600 or a processing station description field 610 . The program field 600 can be used for the user to input a program, such as "die-casting" 601 corresponding to item "1" or "stamping" 602 corresponding to item "2", but not limited thereto. The processing station description column 610 can be used for the user to input the description of the processing station, such as "sheet forming" 611 corresponding to the item "1" or "cutting" 612 corresponding to the item "2", but not limited thereto.

It should be noted that the description in FIG. 6 above only illustrates the content related to the present invention. As is well known to those skilled in the art, the material preparation schedule 60 may include other fields, buttons, and/or tools such as, but not limited to, the project field, start field, end field, or estimated yield field in Figure 6.

Fig. 7 is a schematic diagram of a schedule data 70 of a management report system 20 according to an embodiment of the present invention. The schedule data 70 can be related to the material preparation schedule 60 in Fig. 6. For example, the material preparation schedule 60 and the schedule data 70 can be belong to the same project. As shown in FIG. 7 , the scheduling data 70 may include a program field 700 and a processing station description field 710 . According to the content “die-casting” 601 corresponding to the program column 600 in the material preparation schedule 60 , the association module 210 can determine (for example, generate or automatically substitute) the content corresponding to the program column 700 to be “die-casting” 701 . According to the content "sheet forming" 611 corresponding to the processing station description column 610 in the material preparation schedule 60, the associated module 210 can determine (for example, generate or automatically substitute) the content corresponding to the processing station description column 710 as "sheet forming" 711 . According to the content “stamping” 602 corresponding to the program column 600 in the material preparation schedule 60 , the association module 210 can determine (for example, generate or automatically substitute) the content corresponding to the program column 700 to be “stamping” 702 . According to the corresponding content "entry point punching" 612 in the processing station description column 610 in the material preparation schedule 60, the associated module 210 can determine (for example, generate or automatically substitute) the content corresponding to the processing station description column 710 as "entry point Die-cut "712.

It should be noted that the description in FIG. 7 above only illustrates the content related to the present invention. As is well known to those skilled in the art, the scheduling data 70 may include other scheduling-related fields, buttons, and/or Or tools, such as the project column, process photo column, before processing photo column or after processing photo column in Figure 7, but not limited thereto.

The aforementioned management method of the management report system 20 can be summarized as a process 80 in FIG. 8 . Process 80 includes the following steps:

Step 800: start.

Step 802: Receive data of the first user, and generate a first report according to the data.

Step 804: Determine the content of the second report according to the association between the first report and the second report.

Step 806 : Notify the management results of the first report and the second report to the first user and the second user, wherein the second user is associated with the project corresponding to the first report.

Step 808: end.

It should be noted that the above "first", "second", "third" and "fourth" are used to distinguish the relevant statements, not to limit the order of the relevant statements. The above "deposit" may be replaced with "upload". The above "acquisition" may be replaced with "download".

It should be noted that there are many ways to implement the report management system 20 (and the generation module 200 , the association module 210 , and the notification module 220 ). For example, the above modules may be integrated into one or more modules. In addition, the system 20 for managing reports (and the generation module 200, the association module 210, and the notification module 220) can be implemented through hardware (such as circuits or chips), software, and firmware (for hardware devices and computer instructions and Combination of data, and computer instructions and data belong to read-only software on the hardware device), electronic system, or a combination of the above-mentioned modules to achieve, but not limited to this. The steps of all the aforementioned processes can be implemented through hardware (such as circuits or chips), software (such as program codes), and firmware (which is the combination of hardware devices and computer instructions and data, and the computer instructions and data belong to the hardware device. Read-only software), electronic systems, or a combination of the above modules, but not limited thereto.

In summary, the present invention provides a system and method for managing reports. When a user wants to save a project report, the user sends the data to the management report system. According to the data, the system can automatically generate a project report and its encoding. When a user wants to obtain a project report, according to the code, the user can confirm whether there is an updated project report in the report management system and which report is the latest project report. When the user wants to access the project report from outside the enterprise, the user can access the project report by logging into the report management system. That is to say, through the report management system, users can efficiently or timely access project reports, and the storage space of project reports can also be effectively utilized. Therefore, the problems in the prior art can be solved. The above descriptions are only preferred embodiments of the present invention, and all equivalent changes and modifications made according to the scope of the patent application of the present invention shall fall within the scope of the present invention.

10: Computer network 100: A System for Managing Reports 110: at least one user 20: System for management reporting 200: generate mods 210: Associated modules 220: Notification module 80: Process 800, 802, 804, 806, 808: steps

FIG. 1 is a schematic diagram of a computer network according to an embodiment of the present invention. FIG. 2 is a schematic diagram of a management reporting system according to Embodiment 1 of the present invention. FIG. 3 is a schematic diagram of a user transmission data interface of a management report system according to an embodiment of the present invention. FIG. 4 is a schematic diagram of a report list of a report management system according to an embodiment of the present invention. FIG. 5 is a schematic diagram of a report generated by a management report system according to an embodiment of the present invention. FIG. 6 is a schematic diagram of a material preparation schedule of a management reporting system according to an embodiment of the present invention. FIG. 7 is a schematic diagram of a schedule data of a management reporting system according to an embodiment of the present invention. Fig. 8 is a flow chart of the process of Embodiment 1 of the present invention.

80: Process

800, 802, 804, 806, 808: steps

Claims (10)

A system for management reporting comprising: A generation module, used to receive a data of a first user, and generate a first report according to the data; an association module, coupled to the generation module, for determining a first content of the second report according to an association between the first report and a second report; and a notification module, coupled to the association module, for notifying a management result of the first report and the second report to the first user and a second user, wherein the second user is associated with A project corresponding to the first report. The system as claimed in claim 1, wherein the generation module generates a code of the first report according to code information, wherein the code information includes at least one of the following information: a time or a version. The system as described in Claim 1, wherein the data includes at least one of the following information: an image or a text description. The system of claim 1, wherein the association includes the first report and the second report corresponding to the project. The system according to claim 1, wherein a field corresponding to the first content is included in the first report, wherein according to a second content corresponding to the field in the first report, the association module The first content is determined. The system as claimed in claim 1, wherein the notification module notifies the management result to the first user and the second user through a communication software. The system as described in claim 1, wherein the management result includes at least one of the following information: a first update information of the first report, a second update information of the second report, a third update information of the data Update information, a progress of the project, or a to-do list of the project. The system as described in claim 7, wherein when the generation module determines that the data contains an update, through the management result, the notification module notifies the first user and the first user of the third update information associated with the update. the second user. The system as described in claim 1, wherein the first user sets a login method and an access authority for a manager of the project. A method for managing reports comprising: receiving a data of a first user, and generating a first report based on the data; determine a content of the second report based on a link between the first report and a second report; and Notifying a management result of the first report and the second report to the first user and a second user, wherein the second user is associated with a project corresponding to the first report.

Images