JP7555105B2 - Management systems and programs - Google Patents

Description

The present invention relates to a management system and program, and in particular to a management system that manages at least one of cases, deadlines, documents, and invoices and has a form issuing function, and a program that causes a computer to execute the steps of the management system.

There are known management systems that manage cases, deadlines, documents, and invoices related to intellectual property rights such as patents, utility models, designs, and trademarks. One of the functions of a management system is to issue documents (including letters, notices, patent office documents, invoices, internal documents, correspondence, and other documents) to applicants and the patent office. For example, after completing a patent application, a patent office issues and sends a letter to its client, the applicant, reporting the completion of the application. For example, Patent Document 1 discloses a technology that identifies cases using specified information and issues correspondence.

JP 2002-109028 A

In the technology of Patent Document 1, when you want to issue reports for multiple cases, it is time-consuming and cumbersome to change the specified conditions and identify the cases one by one. In addition, if you relax the conditions too broadly, reports may be issued for unnecessary cases.

A management system according to one embodiment of the present invention is a management system that manages at least one of cases, deadlines, documents, or invoices, and has a form issuing function, and includes a control unit that displays a list of cases, deadlines, documents, or invoices, displays a selection screen for a form to be issued for the list, and adds an issue button for the form to the list based on the selected form.

In addition, a program according to one embodiment of the present invention causes a computer to manage at least one of cases, deadlines, documents, or invoices, and is a program with a form issuing function, and executes the steps of displaying a list of cases, deadlines, documents, or invoices, displaying a selection screen for a form to be issued for the list, and adding an issue button for the form to the list based on the selected form.

In addition, a storage medium according to one embodiment of the present invention is a computer-readable recording medium on which a program according to one embodiment of the present invention is recorded.

The management system, program, and recording medium disclosed herein enable a system that manages at least one of cases, deadlines, documents, or invoices to identify the target for which a report is to be issued from a list and issue the report.

FIG. 1 is a diagram illustrating a system for executing a program according to an embodiment of the present invention. 13 is an example of a flowchart of information processing performed by a management program. FIG. 13 is a diagram illustrating an example of a case list page. FIG. 13 is a diagram showing an example of an issuance form selection screen. FIG. 13 is a diagram showing an example of adding a report issuance button for applicant. FIG. 13 is a diagram showing an example of an applicant's form. FIG. 13 is a diagram showing another example of adding a report issuance button for applicant. FIG. 13 is a diagram showing another example of adding a report issuance button for applicant. FIG. 13 is a diagram showing an example of adding a document issuance button addressed to the Patent Office. FIG. 13 is a diagram showing an example of adding a form issue button to a term list page. FIG. 13 is a diagram showing an example of an applicant's form regarding deadlines. FIG. 13 is a diagram showing an example of adding a form issue button to a shipping documents list page. FIG. 13 is a diagram showing an example of an applicant's address form regarding shipping documents. FIG. 13 is a diagram showing an example of adding a form issue button to an invoice list page. FIG. 13 is a diagram showing an example of a billing destination form related to an invoice.

The management system according to one embodiment of the present invention is a management system capable of managing at least one of cases, deadlines, documents, or invoices, and issuing reports.

In addition, a program according to one embodiment of the present invention is a program (hereinafter referred to as a "management program") that causes a computer to manage at least one of cases, deadlines, documents, or invoices and can issue reports.

A case is, for example, case data related to an intellectual property case, and includes bibliographic information such as the application date, application number, and applicant. A deadline is, for example, a deadline related to the procedure of an intellectual property case, and includes the deadline for claiming priority and the deadline for requesting examination. A document is, for example, a patent office document related to intellectual property rights, and includes a notice of reasons for refusal, a decision to register, a decision to reject, and the like. An invoice is, for example, an invoice issued by a patent office to an applicant (applicant company), and includes documents that are essentially similar in format to an invoice, such as an estimate and a delivery note.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram showing a management system 1 according to one embodiment of the present invention. The management system 1 comprises a control unit 10, a display unit 20, and a storage unit 30. The control unit 10 is a processor that controls the management system 1. The control unit 10 reads software related to a management program, and realizes information processing related to the management program in cooperation with the display unit 20 and the storage unit 30. The display unit 20 is any display device such as a liquid crystal display or an EL display. The storage unit 30 is any storage device such as a memory, hard disk, or database that stores information.

The management system 1 can be implemented as a single computer including the control unit 10, the display unit 20, and the memory unit 30. Note that the computer includes a server, a personal computer, a tablet terminal, a smartphone terminal, etc. The management system 1 can also be implemented as an independent computer in which the control unit 10, the display unit 20, and the memory unit 30 can be mutually accessible via a network. In this case, for example, the management system 1 can be configured by an application server including the control unit 10, a user computer including the display unit 20, and a database server including the memory unit 30.

Figure 2 is an example of a flowchart of information processing performed by the management system 1 (management program). The control unit 10 displays a list of cases, deadlines, documents, or invoices on the display unit 20 (step S1). Figure 3 is a diagram showing an example of a case list page. The case list page displays a list switching button 41 for switching the display of a list of cases, deadlines, documents, or invoices. In addition, the case list page displays an issued form selection button 42 and a list 43. The control unit 10 can narrow down the display of the list 43 using search conditions input by the user. When the user presses the issued form selection button 42, the control unit 10 displays an issued form selection screen 51 as shown in Figure 4. The control unit 10 can display the issued form selection screen 51 as part of the case list page, as a pop-up display, or in a separate tab or window. The issued form selection screen 51 displays a list of forms by destination type, such as a list of forms addressed to applicants 52, a list of forms addressed to the Patent Office 53, and a list of forms addressed to the office 54. The list of forms is stored in the storage unit 30. Note that the destinations of the forms are not limited to the above, and may include, for example, domestic/foreign agents, pension management companies, inventors, parties in dispute, billing recipients other than the applicant, and other parties (co-owners, licensees, intervenors, and other stakeholders).

When the user selects the issuance form (Y in step S2), the control unit 10 adds a form issue button 45 to the list 43 (step S3). FIG. 5 is a diagram showing an example of adding a form issue button addressed to the applicant. The control unit 10 displays the identification information of the form selected by the user in the selected form display unit 44. The control unit 10 also adds a form issue button 45 to the list 43. The form issue button 45 is an object that accepts any input operation from the user, such as clicking, tapping, or touching, and has the function of issuing the target form in response to the input operation. As shown in the figure, in the case of a form addressed to the applicant, the control unit 10 adds a form issue button 45 that can identify the applicant. In this way, it is preferable to display a form issue button 45 that can identify the destination for an item that has a 1:N (multiple) relationship with one case, such as an applicant. Note that the form issue button 45 shown in the figure is just one example, and instead of displaying the applicant's name itself, a short character string such as "issue" or an image such as a print icon may be displayed on the screen, and the applicant's name may be displayed when the mouse cursor is placed over it.

When the user presses the report issue button 45 (Y in step S4), the control unit 10 issues the selected report (step S5). For example, when the "To Test Co., Ltd." report issue button 45 corresponding to the serial number P001 is pressed, the control unit 10 issues an "Application Completion Report" report "To Test Co., Ltd." for the case with serial number P001. FIG. 6 is a diagram showing an example of an applicant-addressed report. The control unit 10 can insert data stored in the memory unit 30 into the report. For example, the control unit 10 can use a notation surrounded by specific symbols or signs such as ${}, such as ${applicant}, as an insertion item. The control unit 10 issues a report in which the applicant, application date, and application number of the case are inserted for each of the insertion items ${applicant}, ${application date}, and ${application number}.

According to the above embodiment, the report issue button 45 added to the list 43 allows the user to specify the target and issue the report. Therefore, when issuing multiple reports, the user can check the screen and issue only the necessary reports, which allows the user to work efficiently. Also, when there are multiple applicants, the user can identify the applicants and issue the report.

Furthermore, according to the above embodiment, the report issue button 45 can be additionally displayed in the case list/case search page that is provided in a general management system. In other words, the user can additionally display the report issue button 45 only when necessary while performing a normal case list display or case search. This provides the user with high operability, and since it can be developed based on a general case list/case search page, development costs can be reduced.

Figure 7 is a diagram showing another example of adding a report issue button addressed to the applicant. In the addition step of step S3, if a column corresponding to the destination of the selected report exists in the list 43, the control unit 10 can display the report issue button 45 in association with the column. For example, if a letter addressed to the applicant is selected and the list 43 has a column for the applicant, the control unit 10 can display the report issue button 45 in the applicant column of the list 43. This makes it possible to display the report issue button 45 while suppressing changes to the screen without adding a new column. In addition, since the report issue button 45 is displayed in the same column as the list 43 being displayed, it is possible to provide the user with intuitive operability. In addition, it is possible to reduce the collapse of the layout of the list 43, which occurs when the screen size of the display unit 20 is relatively small. Note that "display associated with a column" refers to a case where all the notations in the column are replaced, or the notations in the column are maintained and the report issue button 45 is displayed in the vicinity of the column (such as in the same column or adjacent columns before and after) (including a simplified notation such as only the word "issue"). In addition, "display associated with a column" does not only refer to text, but also includes color changes such as changing the text color/background color of existing text, formatting changes such as underlining/bold/italics/boxing, and adding icons such as a print button.

Figure 8 is a diagram showing another example of adding a report issue button for applicant. The control unit 10 can display a selection box 46 on each report issue button 45. The control unit 10 can also display a collective operation panel 47 that operates in association with the selection boxes 46. When "Select All" on the collective operation panel 47 is pressed, the control unit 10 places all of the selection boxes 46 in a selected state. When "Deselect All" on the collective operation panel 47 is pressed, the control unit 10 places all of the selection boxes 46 in a deselected state. When "Bulk Issue" on the collective operation panel 47 is pressed, the control unit 10 issues reports corresponding to the selected selection boxes 46. This allows the user to select the target reports and issue them all at once, improving convenience.

Figure 9 is a diagram showing an example of adding a button for issuing a form addressed to the Patent Office. The control unit 10 displays the form selected by the user in the selected form display unit 44. The control unit 10 also adds a form issue button 45 to the list 43. As shown in the figure, in the case of a form addressed to the Patent Office, the control unit 10 displays the form issue button 45 addressed to the Patent Office. In this way, for a 1:1 (single) relationship with a single case, such as the Patent Office, it is preferable to display a form issue button 45 that indicates the destination type. The control unit 10 can also display a simple form issue button 45, such as the word "issue" or a print icon.

Figure 10 is a diagram showing an example of adding a report issue button to a deadline list page. The table 43 of the deadline list page displays deadline information such as the deadline date and deadline content. On the deadline list page, for example, deadlines within a specified period can be searched for and a reminder report can be issued to a client. The flowchart of the information processing performed by the management program on the deadline list page is the same as that shown in Figure 2, and a duplicated explanation will be omitted. When the user selects an issue report (Y in step S2), the control unit 10 adds a report issue button 45 to the list 43 (step S3). When the user presses the report issue button 45 (Y in step S4), the control unit 10 issues the selected report (step S5). For example, when the "To Test Co., Ltd." report issue button 45 corresponding to the reference number P001 is pressed, the control unit 10 issues a "Deadline reminder" report "To Test Co., Ltd." for the case with the reference number P001. Figure 11 is a diagram showing an example of an applicant-addressed report regarding a deadline. The control unit 10 can insert data held by the management system into the report. The control unit 10 issues a report into which the applicant, deadline details, and deadline date of the case corresponding to the deadline are inserted for each of the insertion items ${applicant}, ${deadline content}, and ${deadline date}.

Figure 12 is a diagram showing an example of adding a report issue button to the shipping documents list page. The list 43 of the shipping documents list page displays shipping document information such as the shipping date and shipping documents. On the shipping documents list page, for example, shipping documents sent during a specified period can be searched for and a receipt report report can be issued to a client. The flowchart of the information processing performed by the management program on the shipping documents list page is the same as that shown in Figure 2, and redundant explanations will be omitted. When the user selects an issue report (Y in step S2), the control unit 10 adds a report issue button 45 to the list 43 (step S3). When the user presses the report issue button 45 (Y in step S4), the control unit 10 issues the selected report (step S5). For example, when the "To Test Co., Ltd." report issue button 45 corresponding to the reference number P001 is pressed, the control unit 10 issues a "Shipping documents receipt report" report to "To Test Co., Ltd." for the case with the reference number P001. Figure 13 is a diagram showing an example of an applicant-addressed report regarding shipping documents. The control unit 10 can insert data held by the management system into the form. For each of the insertion items ${applicant}, ${shipping document}, and ${shipping date}, the control unit 10 issues a form into which the applicant, shipping document, and shipping date of the corresponding case are inserted.

Figure 14 is a diagram showing an example of adding a form issue button to an invoice list page. Invoice information such as invoice number and invoice amount is displayed in the list 43 of the invoice list page. In the invoice list page, for example, invoices issued during a specified period can be searched for and invoice forms for invoice recipients can be issued. The flow chart of information processing performed by the management program on the invoice list page is the same as that shown in Figure 2, and duplicated explanations will be omitted. When the user selects an issue form (Y in step S2), the control unit 10 adds a form issue button 45 to the list 43 (step S3). When the user presses the form issue button 45 (Y in step S4), the control unit 10 issues the selected form (step S5). For example, when the form issue button 45 "To Test Co., Ltd." corresponding to invoice number 2020-001 is pressed, the control unit 10 issues an "invoice" form "To Test Co., Ltd." for the invoice with invoice number 2020-001. As shown in the case with reference number P003, in a case with multiple applicants, an invoice can be issued to each applicant as the invoice recipient. FIG. 15 is a diagram showing an example of a billing destination form related to an invoice. The control unit 10 can insert data held by the management system into the form. The control unit 10 issues a form into which the corresponding billing destination, invoice number, billing amount, cost item, unit price, quantity, and subtotal are inserted for each of the insertion items ${billing destination}, ${invoice number}, ${billing amount}, ${expense item}, ${unit price}, ${quantity}, and ${subtotal}.

In this way, the management system according to one embodiment of the present invention includes a control unit that displays a list of cases, deadlines, documents, or invoices, displays a selection screen for a form to be issued for the list, and adds a button for issuing the form to the list based on the selected form. This allows the user to specify the target and issue the form. Therefore, when issuing multiple forms, the user can check the screen and issue only the necessary forms, making it possible to work efficiently. In addition, a form issue button can be additionally displayed in the list/search page that is provided in a general management system. In other words, the user can add a form issue button only when necessary during normal list display and search. This provides high operability to the user, and since it can be developed based on a general case list/case search page, development costs can be reduced.

Furthermore, in the case where a column corresponding to the destination of the selected form exists in the list, the management system according to one embodiment of the present invention can display the form issue button in association with that column. This makes it possible to display the form issue button with minimal changes to the screen without adding a new column. Furthermore, since the form issue button is displayed in the same column as the list being displayed, it is possible to provide the user with intuitive operability. It is also possible to reduce the collapse of the list layout that occurs when the screen size of the display unit is relatively small.

Although the present invention has been described based on embodiments, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents described in the claims.

For example, while the above embodiment has been described using an example of an intellectual property rights management system, the present invention is not limited to this. The present invention is compatible with systems that manage at least one of cases, deadlines, documents, or invoices, and is applicable to various systems such as accounting systems, contract management systems, business management systems, and litigation management systems.

The program according to the present invention can also be stored in a computer-readable recording medium such as a magnetic disk (floppy disk (registered trademark), hard disk, etc.), optical disk (CD-ROM, DVD, MO, Blu-ray Disc (registered trademark), etc.), or semiconductor memory (ROM, RAM, flash memory, etc.). The recording medium is not limited to portable recording media, but also includes storage media such as magnetic disks and semiconductor memories installed inside a computer or in a device connected via a network.

According to the present invention, in a system that manages at least one of cases, deadlines, documents, or invoices, it becomes possible to identify the target for which a report is to be issued from a list and issue the report.

REFERENCE SIGNS LIST 1 Management system 10 Control unit 20 Display unit 30 Memory unit 41 List selection menu 42 Issue form selection button 43 List 44 Selected form display unit 45 Form issuance button 46 Selection box 47 Collective operation panel 51 Issue form selection screen 52 Form addressed to applicant 53 Form addressed to Patent Office 54 Form addressed to office 71 Case-related form 72 Deadline-related form 73 Document-related form 74 Invoice-related form

Claims (2)

A management system that manages at least one of cases, deadlines, documents, and invoices and has a form issuing function,
Display a list of cases, deadlines, documents or invoices;
Display a selection screen for a form to be issued for the list,
A management system comprising a control unit that adds an issue button for a form to the list based on a form selected on a displayed selection screen . A program that causes a computer to manage at least one of cases, deadlines, documents, and invoices, and has a form issuing function,
displaying a list of cases, deadlines, documents or invoices;
displaying a selection screen for a form to be issued for the list;
and an additional step of adding an issue button for the form to the list based on the form selected on the displayed selection screen .