Support device, support method, and support program

Abstract

To provide a support device, a support method, and a support program capable of comprehensively managing legal requirements that a user has to observe in a work.SOLUTION: In a support device comprising processors and a memory, a processor which realizes a legal requirement management unit comprises: a tagged legal requirement storage unit which assigns a target tag indicative of a type of an object which is a target of a legally prescribed requirement to the legal requirement and stores the legal requirement; an execution history storage unit which stores a work execution history on an object prescribed by the legal requirement per object; a retrieval unit which accepts an input of an object on a work from a user and retrieves the legal requirement given the target tag associated with the input object from the tagged legal requirement storage unit; and a display unit which displays the retrieved legal requirement together with the work execution history on the object read from the execution history storage unit.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a support device, a support method, and a support program.

Background Art

[0002] In operations related to the environment, there are environmental laws and regulations that must be complied with, but it takes time to understand all of them. Therefore, it requires a lot of labor to identify the laws and regulations to be complied with in each operation and manage them manually. As a result, there is a possibility of omission in the implementation of tasks obligated by each law or omission in the submission of reports to government agencies, etc. And failure to comply with the laws may lead to serious non-compliance of the company.

[0003] Regarding such problems, the technology disclosed in Patent Document 1 creates environmental impact assessment items corresponding to environmental aspects for each facility, and identifies significant environmental aspects based on information related to environmental aspects and environmental impact assessment items for each operation. Thereby, an environmental management plan is formulated for each operation based on information related to environmental aspects, and the activity achievements, etc. for the formulated environmental management plan are evaluated.

[0004] Also, the technology disclosed in Patent Document 2 prevents omission in the submission of reports to government agencies by notifying the submission of reports in accordance with the updated content when any of the facility, the reporter, or the law is updated.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, the technology described in Patent Document 1 does not consider legal requirements other than environmental aspects related to the equipment. Similarly, the technology described in Patent Document 2 does not consider legal requirements other than notifications to government agencies. Therefore, the above technologies cannot manage all laws and regulations that must be complied with in the course of business.

[0007] This invention has been made in view of these circumstances, and aims to provide a support device, a support method, and a support program that enable users to comprehensively manage legal requirements that must be complied with in their work. [Means for solving the problem]

[0008] One of the present inventions for solving the above problems is a support device comprising: a processor and memory, a tagged legal requirements storage unit that stores a target tag indicating the type of object subject to legal requirements stipulated by law, attached to the legal requirements; an implementation history storage unit that stores the implementation history of business related to the object defined by the legal requirements for each object; a search unit that receives input of an object related to business from a user and searches the tagged legal requirements storage unit for legal requirements to which a target tag associated with the input object has been attached; and a display unit that displays the searched legal requirements together with the implementation history of business related to the object read from the implementation history storage unit. [Effects of the Invention]

[0009] According to the present invention, it is possible to comprehensively manage the legal requirements that users must comply with in their work. Cut. Other configurations and effects will be clarified by the following description of the embodiments. [Brief explanation of the drawing]

[0010] [Figure 1] This figure shows an example of the configuration of the support system in this embodiment. [Figure 2] This diagram shows the detailed functional configuration of the Legal Requirements Management Department. [Figure 3] It is a diagram showing an example of a tag given to the requirements of the law. [Figure 4] It is a diagram for explaining the content tag. [Figure 5] It is a diagram showing an example of a table of legal requirements with tags. [Figure 6] It is a diagram showing an example of an implementation history table. [Figure 7] It is a diagram showing an example of a menu screen. [Figure 8] It is a diagram showing an example of a target registration screen. [Figure 9] It is a diagram showing another display example of the menu screen. [Figure 10] It is a diagram showing an example of a legal requirements search screen. [Figure 11] It is a diagram showing an example of a legal requirements search result screen. [Figure 12] It is a diagram for explaining the priority of each tag. [Figure 13] It is a diagram showing an example of an implementation item search screen. [Figure 14] It is a diagram showing an example of an implementation item management screen. [Figure 15] [[ID=*38]]It is a diagram showing an example of a filing search screen. [Figure 16] It is a diagram showing an example of a filing management screen. [Figure 17] [ It is a diagram showing an example of a regularly implemented item search screen. [Figure 18] It is a diagram showing an example of a regularly implemented item management screen. [Figure 19] It is a processing flowchart for explaining the outline of the search process. [Figure 20] It is a processing flowchart for explaining the details of the legal requirements acquisition process.

Mode for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Note: There seems to be a small error in the original text where "届出検索画面" is translated as "filing search screen" which might not be a very common or accurate term in this context. A more common term could be "notification search screen" but I translated it as per the provided text.The following description and drawings are illustrative for illustrating the present invention, and have been omitted and simplified as appropriate for clarity of explanation. The present invention can also be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0012] The positions, sizes, shapes, and ranges of the components shown in the drawings may not represent their actual positions, sizes, shapes, and ranges in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the positions, sizes, shapes, and ranges disclosed in the drawings. In the following explanation, various types of information may be described using terms such as "table," "list," and "queue," but these types of information may also be represented using other data structures. To indicate independence from data structure, "XX table," "XX list," etc., may be referred to as "XX information." When describing identification information, terms such as "identification information," "identifier," "name," "ID," and "number" will be used, but these terms are interchangeable. When there are multiple components with the same or similar function, they may be described using the same symbol but with different subscripts. However, if it is not necessary to distinguish between these multiple components, the subscripts may be omitted in the description.

[0013] Furthermore, while the following explanation may describe processes performed by executing a program, the processor (e.g., CPU, GPU) executes the defined processes, using memory resources (e.g., memory) and / or interface devices (e.g., communication ports) as appropriate; therefore, the processor may be the primary entity performing the processes. Similarly, the primary entity performing the processes by executing a program may be a controller, device, system, computer, or node having a processor. The primary entity performing the processes by executing a program is: It only needs to be an arithmetic unit, and may include dedicated circuits (such as FPGAs or ASICs) that perform specific processing. A program may be installed from its program source into a device such as a computer. The program source may be, for example, a program distribution server or a computer-readable storage medium. If the program source is a program distribution server, the program distribution server includes a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to other computers. Furthermore, in the following description, two or more programs may be implemented as a single program, or one program may be implemented as two or more programs.

[0014] Figure 1 shows an example of the configuration of the support system 1 in this embodiment. Support system 1 comprises a support device 100, one or more legal and regulatory databases 200, one or more business management systems 300, and one or more user terminals 400. The support device 100, the legal and regulatory databases 200, the business management systems 300, and the user terminals 400 are connected via a wired or wireless communication network such as the Internet, LAN (Local Area Network), WAN (Wide Area Network), or dedicated lines. Connect to the network.

[0015] The support device 100 is an automated environmental compliance system designed to assist in compliance with environmental laws and regulations when performing environmentally related tasks. The support device 100 is an information processing device composed of one or more server devices. As shown in the figure, the support device 100 consists of a processing device 110 such as a CPU (Central Processing Unit), a storage device 120 such as an HDD (Hard Disk Drive) or SSD (Solid State Drive), and RAM (Random Access Memory), RO The system includes a memory 130 such as M (Read Only Memory), and a network interface 140 consisting of a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, or a serial communication module. The processing unit 110, storage device 120, memory 130, and network interface 140 are interconnected via a bus.

[0016] The processing unit 110 is a processor that implements the functions of the law and ordinance information collection unit 111, the article analysis unit 112, the legal requirements generation unit 113, and the legal requirements management unit 114. The Laws and Regulations Information Collection Unit 111 retrieves information on environmental laws, regulations, or ordinances from the Laws and Regulations Database 200 and writes the retrieved information on laws, regulations, or ordinances to the Storage Device 120. The Article Analysis Unit 112 analyzes the articles of each law, regulation, or ordinance stored in the storage device 120. For example, the Article Analysis Unit 112 extracts legal requirements from the articles by morphological analysis using the article component information 122 stored in the storage device 120. Legal requirements are matters that must be complied with by laws, regulations, or ordinances. Examples of legal requirements include the type, content (target), and timing of the work that businesses must perform.

[0017] The legal requirements generation unit 113 assigns tags, described later, to the extracted legal requirements and writes them to the storage device 120. The Legal Requirements Management Unit 114 performs processes to support compliance with legal requirements related to business operations. For example, the Legal Requirements Management Unit 114 displays a screen on the user terminal 400 for managing legal requirements that must be complied with in business operations. Details of each function of the Legal Requirements Management Unit 114 will be described later.

[0018] The storage device 120 stores article information 121, article component information 122, a list of laws / ordinance names 123, legal requirements information 124, and applicability information 125. Article information 121 refers to text data of articles of laws, regulations, or ordinances, etc., as described below. This information is obtained from the 200 legal and regulatory databases. The article component information 122 is information about components (for example, the grammar of the target language or the part of speech of a word) that the article analysis unit 112 uses to analyze the article. List of Laws / Ordinances 123 is a list of laws, ordinances, or ordinances whose articles should be memorized. Legal requirements information 124 is information that indicates what the subject of the legal requirements must do to comply with the law, and is, for example, text data extracted from the legal text. The applicability information 125 is information indicating whether or not equipment or parts used in the business, or persons related to the business, fall under the category of subjects subject to legal requirements.

[0019] The Legal Information Database 200 is a database system that stores information on environmental laws, regulations, or ordinances. Examples of Legal Information Database 200 include database systems that store collections of regulations, websites of government ministries or local governments, or systems that provide online versions of official gazettes. The business management system 300 is an external system for managing business operations. For example, the business management system 300 stores information such as equipment or supplies used in business operations or persons related to business operations, as stipulated in legal requirements. User terminals 400 are terminal devices used by each person in charge of the business (hereinafter referred to as "users") U1 to U3, such as personal computers, tablet terminals, or smartphones. In this diagram, a configuration in which multiple users U1 to U3 can each operate user terminals 400 is illustrated, but the number of users or the number of user terminals 400 are not limited.

[0020] Figure 2 shows the detailed functional configuration of the legal requirements management unit 114 in this embodiment. As shown in the figure, the legal requirements management unit 114 includes a search unit 115, a display unit 116, a registration unit 117, a tagged legal requirements storage unit 118, and an implementation history storage unit 119. The tagged legal requirements storage unit 118 stores legal requirements with tags attached to them. The tagged legal requirements storage unit 118 takes the tagged legal requirements 151 (hereinafter referred to as "tagged legal requirements") as input and stores a tagged legal requirements table 500 that shows the input tagged legal requirements.

[0021] Figure 3 shows an example of tags to be assigned to legal requirements in this embodiment. As illustrated, in this embodiment, there are three types of tags attached to each legal requirement: timing tags, content tags, and target tags. Timing tags indicate the timing at which a user should perform the tasks specified in the legal requirements. In the illustrated example, the timing tags include the "Action" tag, which indicates that the tasks specified in the legal requirements must be performed at the time of the action; the "Periodic" tag, which indicates that the tasks specified in the legal requirements must be performed periodically; and the "Continuous" tag, which indicates that the tasks specified in the legal requirements must be performed at all times. An action is a predetermined business activity performed at any time, such as the installation of equipment, the modification of equipment, the disposal of equipment, the disposal of industrial waste, or outdoor work. Target tags indicate the type of object to which the legal requirements apply. The object can be equipment, a person, etc. As illustrated, target tags include, for example, the name of a facility such as a smoke-generating facility or a general waste treatment facility, or the title of a specific business operator or energy manager. Furthermore, content tags indicate the type of work required by the legal requirements. In the illustrated example, content tags classify the legal requirements into five categories: "Implementation," "Notification," "Standards," "Restrictions," and "Obligations."

[0022] Figure 4 is a diagram illustrating the content tag according to this embodiment. The content tags primarily indicate whether or not it is necessary to register the implementation history of tasks related to the subject matter defined by legal requirements (specifically, whether or not the user needs to register the implementation history in the implementation history table 600, described later, with respect to the subject matter of legal requirements). The implementation history is a record of the history of performing tasks related to the subject matter defined by legal requirements. As shown in the diagram, the content tag "Implementation" indicates the tasks to be performed (specifically what needs to be done) and indicates that the tasks performed by the user need to be registered as part of the implementation history (indicating the necessity of registering the implementation history). The content tag "Notification" indicates notifications that need to be performed, such as permits, licenses, and notifications to the mayor or government office, and indicates that the notification procedures need to be registered as part of the implementation history. The content tag "Standard" indicates conditional implementation or restriction, indicating that if it is implementation, the tasks performed by the user need to be registered as part of the implementation history, and if it is restriction, it indicates that registration of the implementation history is not necessary (does not indicate the necessity of registering the implementation history). The content tag "Restriction" indicates specific prohibited actions and indicates that registration of the implementation history is not necessary. Furthermore, the content tag "Obligation" indicates an obligation to make an effort or an idea, and that registration of the implementation history is not required.

[0023] (Tagged legal requirements table) Figure 5 shows an example of a tagged legal requirements table 500 in this embodiment. The tagged legal requirements table 500 may be automatically created by the support device 100, but it can also be pre-configured by the user, for example. The tagged legal requirements table 500 is a database that stores legal requirements that have been tagged (timing tags, content tags, or target tags). The tagged legal requirements table 500 has the following data items: ID 501, which is identification information that identifies the legal requirement; requirement 502, which is the specific content of the legal requirement; timing tag 503, which contains the content of the timing tag attached to the legal requirement; content tag 504, which contains the content of the content tag attached to the legal requirement; target tag 505, which contains the content of the target tag attached to the legal requirement; and deadline 506 for implementing the legal requirement. Information is set in deadline 506 if a deadline is required for the legal requirement.

[0024] In the illustrated example, the legal requirement for ID "1" has the timing tag "periodic," the content tag "implementation," and the target tag "fluorocarbon-containing products," with a deadline of "once every 3 months." Therefore, the legal requirement for ID "1" must be "implemented" "periodicly" once every 3 months for "fluorocarbon-containing products." Similarly, the legal requirement for ID "2" has the timing tag "periodic," the content tag "implementation," and the target tag "soot and smoke," with a deadline of "once every 5 years." Therefore, the legal requirement for ID "2" must be "implemented" "periodicly" once every 5 years for "soot and smoke." Furthermore, the legal requirement for ID "3" has the timing tag "action," the content tag "notification," and the target tag "owner of large-scale commercial buildings," with a deadline of "~14 days." Therefore, the legal requirement for ID "3" is that the "owner of a large commercial building" must "notify" within "14 days" from the "time of action (the day of appointment)". Also, the legal requirement for ID "4" has the timing tag "action", content tag "implementation", and target tag "soot and smoke", and the deadline is "- (not set)". Therefore, the legal requirement for ID "4" must be "implemented" regarding "soot and smoke" at the "time of action (when an accident occurs)".

[0025] Returning to Figure 2, we will continue our explanation of the functional configuration of the Legal Requirements Management Unit 114. The implementation history storage unit 119 receives input from the user of the implementation history 154 of the work related to the subject specified in the legal requirements, and stores the input implementation history in the implementation history table 600.

[0026] (Implementation History Table) Figure 6 shows an example of the implementation history table 600 in this embodiment. The implementation history table 600 shows, for example, when a user has performed business activities required by legal requirements. Update as needed. The Implementation History Table 600 is a database that stores the implementation history of legal requirements implemented for each object related to the business. The Implementation History Table 600 has the following data items: object name 601, target tag 602, legal requirement 603, implementation history 604, implementation notes 605, and action implementation history 606. Legal requirement 603 indicates the ID of the legal requirement. Implementation history 604 is the date the corresponding legal requirement was most recently implemented. Implementation notes 605 are notes regarding the implementation of the legal requirement. Action implementation history 606 is the date the corresponding legal requirement was first implemented.

[0027] In the illustrated example, Boiler A, whose tag is "soot," implemented legal requirement ID1 on October 1, 2020, with the implementation note being "Measurement result: 5 cm / sec." Boiler A also implemented legal requirement ID2 most recently on February 15, 2021, and initially on February 1, 2021. Boiler B, also with the tag "soot," implemented legal requirement ID1 on November 1, 2020, with the implementation note being "Measurement result: 3 cm / sec." Mr. Suzuki, whose tag is "person in charge," implemented legal requirement ID3 on September 1, 2020.

[0028] Returning to Figure 2, we will continue our explanation of the functional configuration of the Legal Requirements Management Unit 114. The search unit 115 (environmental law search unit) receives a search query 153 from the user, which is the condition for the legal requirements to be searched. The search unit 115 then searches for legal requirements that match the search query based on tagged legal requirements 152 read from the tagged legal requirements table 500. The search query is a combination of any keyword and tag. For example, the search unit 115 receives input from the user of an object related to a business and searches the tagged legal requirements table 500 for legal requirements that have been assigned a target tag associated with the input object. The search unit 115 also searches for legal requirements that require the business indicated by the content tag. Furthermore, the search unit 115 searches for legal requirements that stipulate the implementation of business related to the object at the timing indicated by the timing tag.

[0029] The display unit 116 (search result display unit) displays the searched legal requirements (search result 156) together with the implementation history 155 related to the subject read from the implementation history table 600. At this time, the display unit 116 calculates and displays the implementation deadline for the searched legal requirements based on the implementation history 155 stored in the implementation history table 600 and the deadline information specified by the searched legal requirements. The display unit 116 also displays as reference information legal requirements that have been tagged with a timing tag indicating that the user will always comply with the legal requirements. In addition, the display unit 116 notifies the user of unimplemented tasks identified based on the implementation history stored in the implementation history table 600, among the tasks indicated by legal requirements that have been tagged with a content tag requiring registration of the implementation history. "Unimplemented" indicates that the task has not been implemented.

[0030] The registration unit 117 accepts input regarding the implementation status of the displayed legal requirements for the subject, and writes the entered implementation status as implementation history 154 to the implementation history table 600.

[0031] Next, we will explain the operation of this support device 100. The display screen described below is shown on the user terminal 400 by the display unit 116 of the support device 100. In addition, each operation on the display screen described below is received by the registration unit 117 of the support device 100.

[0032] (Menu screen) Figure 7 shows an example of a menu screen 700 according to this embodiment. The menu screen 700 is for registering objects related to business operations, and the target registration 701 is for registering objects related to business operations. The system includes various menus for searching for legal requirements, implementation management for managing the implementation of legal requirements, notification management for managing notifications regarding legal requirements, and periodic implementation management for managing legal requirements that should be implemented periodically, as well as an unimplemented item notification field 710 for notifying users of legal requirements that have not been implemented. Details of the unimplemented item notification field 710 will be described later.

[0033] (Target registration screen) Figure 8 shows an example of the target registration screen 800 according to this embodiment. The display unit 116 displays the target registration screen 800 when it receives an operation to select target registration 701 on the menu screen 700. The target registration screen 800 includes a keyword input field 801 for receiving the name of an object related to the business (for example, equipment name, administrator name), a target tag selection field 802 for receiving the selection of a target tag, a registration button 803 for registering by adding the target tag selected in the target tag selection field 802 to the name entered in the keyword input field 801, and a target list table 810 for displaying a list of registered objects. The target list table 810 displays a list of registered object names, associated with the assigned target tags.

[0034] For example, as shown in the diagram, when the user enters the name of the object "heating furnace" in the keyword input field 801, selects "soot" in the target tag selection field 802, and presses the registration button 803, the display unit 116 displays the name "heating furnace" and the target tag "soot" (for example, side by side) at the bottom of the target list table 810. The registration unit 117 also tags the object name "heating furnace" registered on the target registration screen 800 with the target tag "soot" and stores it in memory. In this example, the case of assigning one target tag to one object has been explained, but it is not limited to this, and multiple target tags may be assigned to one object.

[0035] (Menu screen) Figure 9 shows another example of the menu screen 700 according to this embodiment. This figure shows an example of the display when a new object, "heating furnace," is registered on the object registration screen 800. The display unit 116 displays the names of the objects in the object in the object field 712 of the unimplemented item notification field 710. These are legal requirements that have been assigned target tags associated with each registered object, and that have been assigned content tags requiring registration of implementation history, and which have been identified as unimplemented based on the implementation history stored in the implementation history table 600. In the illustrated example, the display unit 116 displays a list of notifications in the unimplemented item notification field 710 for the newly registered "heating furnace," including notifications for unimplemented legal requirements: "Please submit an installation notification!", "Please appoint a pollution prevention manager!", and "Please measure soot and smoke! (XX days left until the deadline)." Here, the display unit 116 extracts from the tagged legal requirements table 500 the target tags assigned to each registered object and the legal requirements assigned with the content tags "implement" or "notify" as legal requirements to be implemented for each object.

[0036] In this way, by displaying the unfulfilled legal requirements for each registered entity on the menu screen, users can become aware of the legal requirements that need to be fulfilled in their work, thus preventing them from overlooking any requirements.

[0037] (Legal Requirements Search Screen) Figure 10 shows an example of the legal requirements search screen 900 according to this embodiment. The display unit 116 displays the legal requirements search screen 900 when it receives an operation to select legal requirements search 702 on the menu screen 700. The legal requirements search screen 900 includes a keyword input field 901 for accepting the input of arbitrary keywords, a timing tag selection field 902 for accepting the selection of timing tags, and a content tag selection field for accepting the selection of content tags. 903 comprises a target selection field 904 for accepting the selection of an object, and a search button 905 for starting a search. In the target selection field 904, the names of objects registered on the target registration screen 800 can be selected.

[0038] (Legal Requirements Search Results Screen) Figure 11 shows an example of the legal requirements search results screen 1000 according to this embodiment. When the display unit 116 receives an operation to press the search button 905 on the legal requirements search screen 900, it displays the legal requirements search results screen 1000. The search unit 115 searches the tagged legal requirements table 500 for legal requirements that match the first search query, which indicates the keyword entered in the keyword input field 901 of the legal requirements search screen 900, the timing tag selected in the timing tag selection field 902, the content tag selected in the content tag selection field 903, and the target tag associated with the subject selected in the target selection field 904. The display unit 116 reads the implementation history for the subject selected in the target selection field 904 (or all subjects if no subject is selected in the target selection field 904) for the legal requirements read by the search unit 115 from the implementation history table 600. The display unit 116 then displays the legal requirements read by the search unit 115, along with the implementation history for the subjects, in a list on the legal requirements search results screen 1000.

[0039] This figure shows an example of the display when "heating furnace" is selected in the target selection field 904 on the legal requirements search screen 900. In this example, the display unit 116 displays a list of legal requirements that have the target tag "soot" attached to "heating furnace" on the legal requirements search results screen 1000. The legal requirements search results screen 1000 includes a search results table 1010 which has the following items: a legal requirements field 1001 showing the retrieved legal requirements, a timing tag field 1002 showing the timing tag attached to the corresponding legal requirements, a content tag field 1003 showing the content tag attached to the corresponding legal requirements, a target tag field 1004 attached to the target tag attached to the corresponding legal requirements, and a previous execution field 1005 showing the user's execution history retrieved from the execution history table 600. The display unit 116 displays the name of the object targeted in the previous implementation, the date and time of the previous implementation, and the remarks of the previous implementation in the previous implementation column 1005, based on the name 601, implementation history 604, and implementation remarks 605 read from the implementation history table 600.

[0040] For example, the legal requirement shown in the first line of this example was implemented for the "heating furnace" on the implementation date and time "2021 / 12 / 1" with the note "Mr. Suzuki was appointed". Also, the legal requirement shown in the second line of this example was implemented for the "heating furnace" with the note "Not implemented".

[0041] In this way, users can specify the conditions for the legal requirements they want to search for on the legal requirements search screen 900, and the legal requirements that match the conditions will be displayed in a list on the legal requirements search results screen 1000. For example, by selecting an object in the object selection field 904, users can display a list of legal requirements that must be complied with for that object. This allows users to easily understand the legal requirements that must be complied with for each object related to their work. In other words, users can comprehensively manage all the legal requirements they must comply with in their work in one place.

[0042] Furthermore, the legal requirements search results screen 1000 displays timing tags, content tags, and target tags assigned to each legal requirement, allowing users to easily understand the timing of performing the tasks specified in each displayed legal requirement, the type of tasks, and the type of object to which they apply.

[0043] Furthermore, the legal requirements search results screen 1000 displays the subject, date and time of the last time the work specified in each legal requirement was performed, and any notes thereto, so the user can see the details of each legal requirement. It is possible to easily ascertain whether the tasks being performed are being carried out with respect to the object.

[0044] Furthermore, on each screen displaying a list of searched legal requirements, the display unit 116 displays legal requirements with higher priority tags in accordance with the pre-set priority of each tag, prioritizing those with lower priority tags over those with lower priority tags. For example, the registration unit 117 accepts input to set the priority of each tag and stores the entered priority in association with each tag. The display unit 116 identifies the priority of each tag by reading the priority of each tag that it has stored. "Prioritizing display" includes displaying legal requirements in order from those with higher priority tags, or highlighting legal requirements with higher priority tags. "Highlighting display" includes changing the display color, changing the font size, changing the background color, or adding marks, etc. In this embodiment, the display unit 116 displays legal requirements in order from those with higher priority tags.

[0045] Figure 12 is a diagram illustrating the priority of each tag in this embodiment. As illustrated, content tags have higher priority than timing tags. Furthermore, timing tags have higher priority in the order of "Action," "Regular," and "Always." Similarly, content tags have higher priority in the order of "Implementation," "Notification," "Standard," "Restriction," and "Obligation." In other words, content tags that require registration of implementation history have higher priority, while content tags that do not require registration of implementation history have lower priority.

[0046] Therefore, as shown in the figure, the display unit 116 displays legal requirements that match the search query on the legal requirements search results screen 1000 in order of priority of each tag, starting with legal requirements that have the highest priority content tag "Implementation" and timing tag "Action". In this way, by displaying legal requirements with content tags that require registration of implementation history as priority over legal requirements with content tags that do not require registration of implementation history, users can easily identify legal requirements that require registration of implementation history.

[0047] (Search screen for implementation items) Figure 13 shows an example of the implementation item search screen 1100 according to this embodiment. The display unit 116 displays the implementation item search screen 1100 when it receives an operation to select the implementation item management 703 on the menu screen 700. The implementation item search screen 1100 includes a keyword input field 1101 for accepting the input of arbitrary keywords, a target selection field 1102 for accepting the selection of an object, and a search button 1103 for starting a search. In the target selection field 1102, the names of objects registered on the target registration screen 800 can be selected.

[0048] (Implementation item management screen) Figure 14 shows an example of the implementation item management screen 1200 according to this embodiment. The display unit 116 displays the implementation item management screen 1200 when it receives an operation to press the search button 1103 on the implementation item search screen 1100. The search unit 115 searches the tagged legal requirements table 500 for legal requirements that match the keyword entered in the keyword input field 1101 of the implementation item search screen 1100, the target tag associated with the object selected in the target selection field 1102, the content tag "implementation", and the timing tag "action" of the second query. The display unit 116 reads the implementation history from the implementation history table 600 for the object selected in the target selection field 1102 (or all objects if no object is selected in the target selection field 1102) for the legal requirements read by the search unit 115. The display unit 116 then displays the list of legal requirements read by the search unit 115, along with the implementation history for the objects, on the implementation item management screen 1200.

[0049] This figure shows that in the implementation item search screen 1100, "heating furnace" is selected in the target selection field 1102. This shows an example of how it would look if this were done. In this example, the display unit 116 displays a list of legal requirements that have been assigned the target tag "soot", content tag "implementation", and timing tag "action" for the "heating furnace" on the implementation management screen 1200. The implementation management screen 1200 includes an implementation table 1210 which has the following items: legal requirements field 1201, timing tag field 1202, content tag field 1203, target tag field 1204, previous implementation field 1205, and implementation field 1206. The implementation field 1206 includes a date input field 1207 which accepts input of the date of implementation, a remarks input field 1208 which accepts input of remarks about the implementation, and a registration button 1209 for registering the entered content, and accepts input of the user's implementation status of the work related to the object.

[0050] When the registration unit 117 receives input by pressing the registration button 1209 on the implementation field 1206, it writes the date entered in the date input field 1207 and the remarks entered in the remarks input field 1208 to the implementation history 604 and implementation remarks 605 of the implementation history table 600, respectively. The other items in the implementation details table 1210 are the same as those in the search results table 1010 of the legal requirements search results screen 1000, so their explanation is omitted.

[0051] In this way, by specifying the conditions for the legal requirements they wish to search for on the implementation item search screen 1100, users can view a list of legal requirements that match the conditions and that should be implemented at the time of action, along with their implementation history, on the implementation item management screen 1200. For example, by selecting an object in the target selection field 1102, users can view the legal requirements that should be implemented at the time of action for that object, along with the contents of their past implementation history. This allows users to thoroughly check whether they have completed all tasks related to the legal requirements that must be complied with for the object.

[0052] Furthermore, the implementation management screen 1200 accepts the user's input of the implementation history for legal requirements that must be met at the time of action, allowing users to easily register the implementation history of tasks stipulated by legal requirements.

[0053] Furthermore, the implementation management screen 1200 shown in this example includes a reference table 1220 that displays a list of legal requirements that have the target tag "soot" for "heating furnace" and have the timing tag "periodic" or "always" as reference information. The search unit 115 searches the tagged legal requirements table 500 for legal requirements that have the target tag "soot" for "heating furnace" selected in the target selection field 1102 and have the timing tag "periodic" or "always" attached. The display unit 116 displays the list of legal requirements read by the search unit 115 in the reference table 1220. Since each item in the reference table 1220 is the same as in the implementation table 1210, its explanation is omitted. Furthermore, among the legal requirements displayed in Reference Table 1220, those with the content tags "Implementation" or "Notification" that require registration of implementation will have a date input field, a remarks field, and a registration button in their implementation column, allowing for the input of implementation history.

[0054] In this way, by displaying Reference Table 1220, users can easily understand legal requirements that should be implemented periodically or continuously, and can also register their implementation history. In this example, the display unit 116 displays legal requirements with the timing tag "periodic" or "continuous" as reference information, but the legal requirements displayed as reference information are not limited to those with the timing tag "action" and content tag "implementation". For example, the display unit 116 may display as reference information legal requirements with the timing tag "action" and content tags other than "implementation".

[0055] (Notification search screen) Figure 15 shows an example of the notification search screen 1300 according to this embodiment. The display unit 116 displays the notification search screen 1300 when it receives an operation to select notification management 704 on the menu screen 700. The notification search screen 1300 includes a keyword input field 1301 for accepting arbitrary keywords, a target selection field 1302 for accepting the selection of an object, and a search button 1303 for starting a search. In the target selection field 1302, the names of objects registered on the target registration screen 800 can be selected.

[0056] (Notification Management Screen) Figure 16 shows an example of the notification management screen 1400 according to this embodiment. When the display unit 116 receives an operation to press the search button 1303 on the notification search screen 1300, it displays the notification management screen 1400. The search unit 115 searches the tagged legal requirements table 500 for a list of legal requirements that match the keyword entered in the keyword input field 1301 of the notification search screen 1300, the target tag associated with the subject selected in the target selection field 1302, and the third search query indicating the content tag "notification". The display unit 116 reads the implementation history for the subject selected in the target selection field 1302 (or all subjects if no subject is selected in the target selection field 1302) for the legal requirements read by the search unit 115 from the implementation history table 600. The display unit 116 then displays the list of legal requirements read by the search unit 115, along with the implementation history for the subjects, on the notification management screen 1400.

[0057] This figure shows an example of the display when "heating furnace" is selected in the target selection field 1302 on the notification search screen 1300. In this example, the display unit 116 displays a list of legal requirements for "heating furnace" with the target tag "soot" and the content tag "notification" on the notification management screen 1400. The notification management screen 1400 includes a notification item table 1410 which has the following items: legal requirement field 1401, timing tag field 1402, content tag field 1403, target tag field 1404, previous implementation field 1405, notification implementation deadline field 1406 which indicates the deadline for users to implement the notification specified in the legal requirement, action implementation field 1407, and notification implementation field 1408.

[0058] The display unit 116 calculates the notification deadline for each legal requirement based on the deadline 506 in the tagged legal requirements table 500 and the implementation history 604 in the implementation history table 600, and displays the calculated notification deadline in the notification deadline column 1406. The action implementation column 1407 accepts input of the date on which the action requiring notification was performed. The registration unit 117 writes the date entered in the action implementation column 1407 to the action implementation history 606 in the implementation history table 600. The notification implementation column 1408 includes a date input field 1409 for accepting input of the date on which the notification was performed, a remarks input field 1411 for accepting input of remarks about the notification, and a registration button 1412 for registering the entered content, and accepts input of the notification implementation history. When the registration unit 117 receives input by pressing the registration button 1412 in the notification implementation field 1408, it writes the date entered in the date input field 1409 and the remarks entered in the remarks input field 1411 to the implementation history 604 and implementation remarks 605 of the implementation history table 600, respectively. The other items in the notification item table 1410 are the same as those in the implementation item table 1210 on the implementation item management screen 1200, so their explanation is omitted.

[0059] In this way, by specifying the conditions for the legal requirements they wish to search for on the notification search screen 1300, users can view a list of legal requirements that match the conditions and stipulate the implementation of notifications, along with their implementation history, on the notification management screen 1400. For example, by selecting an object in the target selection field 1302, users can view the legal requirements that stipulate notifications related to that object, along with their past implementation history. This allows users to thoroughly check whether they have implemented all notifications stipulated by the legal requirements that must be complied with for the object. Furthermore, by displaying the deadline for implementation of each legal requirement, users can see when they should implement the notifications stipulated by the relevant legal requirements. This makes it easy to grasp the situation. This helps prevent failures to comply with legally mandated notifications.

[0060] Furthermore, the notification management screen 1400 accepts user input of the notification implementation history as stipulated by legal requirements, allowing users to easily register the implementation history of notifications as stipulated by legal requirements.

[0061] Furthermore, the notification management screen 1400 shown in this example includes a reference table 1420 that displays a list of legal requirements that have the target tag "soot" for "heating furnace" and have the timing tag "periodic" or "always" as reference information. The search unit 115 searches the tagged legal requirements table 500 for legal requirements that have the target tag "soot" for "heating furnace" selected in the target selection field 1302 and have the timing tag "periodic" or "always" attached. The display unit 116 displays the list of legal requirements read by the search unit 115 in the reference table 1420. Since each item in the reference table 1420 is the same as that in the reference table 1220 of the implementation management screen 1200, its explanation is omitted.

[0062] In this way, by displaying Reference Table 1420, users can easily understand legal requirements that should be performed periodically or continuously, and can also register their implementation history. In this example, the display unit 116 displays legal requirements with the timing tag "periodic" or "continuous" as reference information, but the legal requirements displayed as reference information are not limited to those with the timing tag "action" and the content tag "notification". For example, the display unit 116 may display legal requirements with the timing tag "action" and content tags other than "notification" as reference information.

[0063] (Search screen for regularly scheduled activities) Figure 17 shows an example of the periodic implementation item search screen 1500 according to this embodiment. The display unit 116 displays the periodic implementation item search screen 1500 when it receives an operation to select periodic implementation item management 705 on the menu screen 700. The periodic implementation item search screen 1500 includes a keyword input field 1501 for accepting the input of arbitrary keywords, a target selection field 1502 for accepting the selection of an object, and a search button 1503 for starting a search. In the target selection field 1502, the names of objects registered on the target registration screen 800 can be selected.

[0064] (Regularly Implemented Tasks Management Screen) Figure 18 shows an example of the periodic implementation item management screen 1600 according to this embodiment. When the display unit 116 receives an operation to press the search button 1503 on the periodic implementation item search screen 1500, it displays the periodic implementation item management screen 1600. The search unit 115 searches the tagged legal requirements table 500 for legal requirements that match the fourth search query, which indicates the keyword entered in the keyword input field 1501 of the periodic implementation item search screen 1500, the target tag associated with the object selected in the target selection field 1502, the content tag "implementation", and the timing tag "periodic". The display unit 116 reads the implementation history for the object selected in the target selection field 1502 (or all objects if no object is selected in the target selection field 1502) for the legal requirements read by the search unit 115 from the implementation history table 600. Then, the display unit 116 displays the list of legal requirements read by the search unit 115, along with the implementation history for the objects, on the periodic implementation item management screen 1600.

[0065] This figure shows an example of the display when "heating furnace" is selected in the target selection field 1502 on the periodic implementation item search screen 1500. In this example, the display unit 116 shows the target field for "heating furnace". Legal requirements with the tag "soot," content tag "implementation," and timing tag "periodic" are listed on the periodic implementation management screen 1600. The periodic implementation search screen 1500 includes a periodic implementation table 1610 which has the following items: legal requirements field 1601, timing tag field 1602, content tag field 1603, target tag field 1604, previous implementation field 1605 which displays the user's implementation history read from the implementation history table 600, implementation deadline field 1606 which indicates the deadline for the user's future implementation of the legal requirement, and implementation field 1607 which accepts input of the user's implementation status of the work related to the subject.

[0066] The display unit 116 calculates the deadline for each legal requirement based on the deadline 506 in the tagged legal requirements table 500 and the implementation history 604 in the implementation history table 600, and displays the calculated notification implementation deadline in the implementation deadline column 1606. The other items in the periodic implementation items table 1610 are the same as those in the implementation items table 1210 provided in the implementation items management screen 1200, so their explanation is omitted.

[0067] In this way, by specifying the conditions for the legal requirements they wish to search for on the periodic implementation search screen 1500, users can view a list of legal requirements that match the conditions and should be implemented periodically, along with their implementation history, on the periodic implementation management screen 1600. For example, by selecting an object in the target selection field 1502, users can view the legal requirements that should be implemented periodically for that object, along with their past implementation history. This allows users to thoroughly check whether they are regularly implementing the tasks stipulated by the legal requirements that must be complied with for the object. Furthermore, by displaying the future implementation deadlines for each legal requirement, users can easily understand when the relevant legal requirement should be implemented next. This helps prevent omissions in the implementation of tasks that should be performed periodically as stipulated by the legal requirements.

[0068] Furthermore, the periodic task management screen 1600 accepts the user's input of the history of tasks that must be performed regularly according to legal requirements, allowing the user to easily register the history of tasks performed according to legal requirements.

[0069] Furthermore, the periodic implementation management screen 1600 shown in this example includes a reference table 1620 that displays a list of legal requirements that have the target tag "soot" for "heating furnace" and the timing tag "always" as reference information. The search unit 115 searches the tagged legal requirements table 500 for legal requirements that have the target tag "soot" for "heating furnace" and the timing tag "always" selected in the target selection field 1502. The display unit 116 displays the list of legal requirements read by the search unit 115 in the reference table 1620. Since each item in the reference table 1620 is the same as that in the reference table 1220 of the implementation management screen 1200, its explanation is omitted.

[0070] In this way, by displaying Reference Table 1620, users can easily understand the legal requirements that must always be complied with. In this example, the display unit 116 displays legal requirements with the timing tag "Always" as reference information, but the legal requirements displayed as reference information are not limited to those with the timing tag "Periodic" and the content tag "Implementation". For example, the display unit 116 may also display legal requirements with the timing tag "Action" or legal requirements with the content tag "Notification" as reference information.

[0071] <Search process> Figure 19 shows an overview of the search process performed by the support device 100 in this embodiment, which is the process for user searching for various types of information using each search screen (legal requirements search screen 900, implementation details search screen 1100, notification search screen 1300, or periodic implementation details search screen 1500). This is a processing flow diagram explaining the process. The search process shown in this diagram is executed when input is received, such as by pressing the search button on each search screen.

[0072] First, the search unit 115 reads the search query that shows the conditions entered on the search screen, and also reads the tagged legal requirements from the tagged legal requirements table 500 (step S101).

[0073] For example, the first search query, which shows the conditions entered on the legal requirements search screen 900, includes the keyword entered in the keyword input field 901, the timing tag selected in the timing tag selection field 902, the content tag selected in the content tag selection field 903, and the target tag associated with the subject selected in the target selection field 904. The second search query, which shows the conditions entered on the implementation details search screen 1100, includes the keyword entered in the keyword input field 1101, the target tag associated with the subject selected in the target selection field 1102, the content tag "implementation," and the timing tag "action." Furthermore, the third search query, which shows the conditions entered on the notification search screen 1300, includes the keyword entered in the keyword input field 1301, the target tag associated with the subject selected in the target selection field 1302, and the content tag "notification." Furthermore, the fourth search query, which indicates the conditions entered on the periodic implementation item search screen 1500, includes the keyword entered in the keyword input field 1501, the target tag associated with the object selected in the target selection field 1502, the content tag "implementation", and the timing tag "periodic".

[0074] Next, the search unit 115 retrieves legal requirements that match the search query (step S102). Details of the legal requirements retrieval process for retrieving legal requirements that match the search query will be described later.

[0075] The search unit 115 then outputs the acquired legal requirements to the display unit 116. The display unit 116 reads the implementation history for the entered legal requirements from the implementation history table 600 and displays the entered legal requirements together with the read implementation history (step S103).

[0076] For example, when the display unit 116 receives an operation to press the search button 905 on the legal requirements search screen 900, it displays the entered legal requirements along with their implementation history on the legal requirements search results screen 1000. Also, when the display unit 116 receives an operation to press the search button 1103 on the implementation items search screen 1100, it displays the entered legal requirements along with their implementation history on the implementation items management screen 1200. Also, when the display unit 116 receives an operation to press the search button 1303 on the notification search screen 1300, it displays the entered legal requirements along with their implementation history on the notification management screen 1400. Also, when the display unit 116 receives an operation to press the search button 1503 on the periodic implementation items search screen 1500, it displays the entered legal requirements along with their implementation history on the periodic implementation items management screen 1600. After that, the search process is terminated.

[0077] <Processing for obtaining legal requirements> Figure 20 is a processing flow diagram illustrating the details of the legal requirements acquisition process in this embodiment. The legal requirements acquisition process shown in this figure is performed in step S102 described above. The search unit 115 repeatedly executes the processes in steps S1021 to S1023 for all legal requirements.

[0078] First, the search unit 115 determines whether the tags attached to the legal requirements match the tags included in the search query (step S1021). Matching a tag means that the tags included in the search query and the tags attached to the legal requirements are the same. If there is no tag match (step S1021: No), the search unit 115 then searches for the next legal requirement. The processes in steps S1021 to S1023 are executed in response to the request.

[0079] On the other hand, if the search unit 115 finds a match with a tag (step S1021: Yes), it determines whether the legal requirement matches the keyword of the search query (step S1022). Matching a keyword means, for example, that the legal requirement contains the keyword or a word with the same or similar meaning as the keyword. The search unit 115 determines the semantic similarity of words using a pre-prepared vocabulary database and morphological analysis. If there is no match with the keyword (step S1022: No), the search unit 115 executes the processes in steps S1021 to S1023 for the next legal requirement.

[0080] On the other hand, if the search unit 115 finds a match with the keyword (step S1022: Yes), it outputs the relevant legal requirement as a hit legal requirement (step S1023). Then, after the search unit 115 has executed steps S1021 to S1023 for all legal requirements, it terminates the legal requirement acquisition process.

[0081] As described above, the support device 100 of this embodiment includes a processor and memory, a tagged legal requirements storage unit 118 that stores a target tag indicating the type of object subject to the legal requirements stipulated by law by attaching it to the legal requirements, an implementation history storage unit 119 that stores the implementation history of business related to the object defined by the legal requirements for each object, a search unit 115 that receives input of an object related to business from the user and searches the tagged legal requirements storage unit 118 for legal requirements to which a target tag associated with the input object has been attached, and a display unit 116 that displays the searched legal requirements together with the implementation history of business related to the object read from the implementation history storage unit 119.

[0082] With this configuration, the support device 100 can display the legal requirements to which the target tag associated with the object has been assigned, along with their past implementation history. Therefore, the user can thoroughly check whether they have performed all tasks related to the object as defined by the legal requirements that must be complied with. This allows the user to comprehensively manage all legal requirements that must be complied with in their work.

[0083] Furthermore, the support device 100 of this embodiment accepts input of the implementation status of the subject matter for the displayed legal requirements and writes the input implementation status to the implementation history storage unit 119. With this configuration, the implementation history of the work related to each subject matter specified in the legal requirements can be easily registered.

[0084] Furthermore, the support device 100 of this embodiment stores legal requirements to which content tags indicating the type of work required by the legal requirement have been assigned, and searches for legal requirements that require the work indicated by the content tag. With this configuration, legal requirements can be searched by the type of work indicated by the content tag, and thus legal requirements can be searched by category classified by the content tag.

[0085] Furthermore, the content tags in this embodiment indicate whether or not registration of the implementation history is required, and the support device 100 displays legal requirements with content tags indicating the need for registration of the implementation history as priority over legal requirements with content tags that do not indicate the need for registration of the implementation history. With this configuration, users can easily identify legal requirements that require registration of the implementation history, thereby preventing omissions in the implementation of legal requirements.

[0086] Furthermore, the support device 100 of this embodiment notifies of unperformed tasks identified based on the implementation history stored in the implementation history storage unit 119, from among the tasks indicated by legal requirements to which content tags indicating the need for registration of implementation history have been attached. With this configuration, legal requirements This can prevent users from failing to complete the tasks they are required to perform.

[0087] The support device 100 displays an implementation item management screen 1200, which includes a previous implementation field 1205 that displays the implementation history read from the implementation history storage unit 119 for legal requirements that have content tags indicating the need to register the implementation history, and an implementation field 1206 that accepts input of the implementation status of the work related to the subject. With this configuration, the user can efficiently manage the legal requirements that the user must implement in their work on the implementation item management screen 1200.

[0088] Furthermore, the support device 100 of this embodiment stores legal requirements that are tagged with timing tags indicating when the user should perform the legal requirements, and searches for legal requirements that stipulate the performance of tasks related to the subject at the timing indicated by the timing tag. With this configuration, legal requirements can be searched according to the timing at which the user should perform the tasks.

[0089] Furthermore, the support device 100 of this embodiment displays as reference information legal requirements to which timing tags indicating that the user is always complying with legal requirements have been attached. With this configuration, the user can easily understand the legal requirements that must be always complied with in their work.

[0090] Furthermore, the support device 100 of this embodiment displays a periodic implementation management screen 1600 which includes a previous implementation field 1605 that displays the user's implementation history read from the implementation history storage unit 119 for legal requirements to which a timing tag indicating that the user periodically implements the legal requirements has been assigned; an implementation deadline field 1606 that displays the future implementation deadline for the user of the legal requirement based on the implementation history stored in the implementation history storage unit 119 and the deadline information specified by the legal requirement; and an implementation field 1607 that accepts input from the user regarding the status of implementation of the tasks related to the subject. With this configuration, the user can efficiently manage the tasks that the user is required to periodically perform as specified in the legal requirements on the periodic implementation management screen 1600.

[0091] Furthermore, the support device 100 of this embodiment displays the future implementation deadlines for the searched legal requirements based on the implementation history stored in the implementation history storage unit 119 and the information on the deadlines specified by the searched legal requirements. With this configuration, the user can easily grasp the future implementation deadlines for the legal requirements.

[0092] The present invention is not limited to the embodiments described above, and can be implemented using any components without departing from its spirit. The embodiments and modifications described above are merely examples, and the present invention is not limited to these as long as the features of the invention are not impaired. Furthermore, although various embodiments and modifications have been described above, the present invention is not limited to these. Other embodiments conceivable within the scope of the technical idea of ​​the present invention are also included within the scope of the present invention.

[0093] For example, some of the hardware components of each device in this embodiment may be provided in other devices.

[0094] Furthermore, each program of the support device may be provided on other devices, a program may consist of multiple programs, or multiple programs may be integrated into a single program. [Explanation of symbols]

[0095] 100 Support device, 110 Processing device, 115 Search unit, 116 Display unit, 117 Registration unit, 118 Tagged legal requirements storage unit, 119 Implementation history storage unit

Claims

1. It has a processor and memory, A tagged legal requirements storage unit that stores a target tag indicating the type of object to which the legal requirements stipulated by law apply, by attaching it to the said legal requirements, An implementation history storage unit that stores the implementation history of the business relating to the subject specified in the aforementioned legal requirements for each of the aforementioned subjects, A search unit that receives input of business-related objects from the user and searches the tagged legal requirements storage unit for legal requirements to which target tags are assigned that correspond to the input objects, A display unit that displays the searched legal requirements together with the execution history of the business related to the subject read from the execution history storage unit. Equipped with, The tagged legal requirements storage unit stores legal requirements to which content tags indicating the type of business required by the legal requirements are attached. The search unit searches for legal requirements that demand the business indicated by the content tag, The aforementioned content tags indicate whether or not registration of the implementation history is required. The display unit prioritizes displaying legal requirements that have content tags indicating the need for registration of the implementation history over legal requirements that have content tags that do not indicate the need for registration of the implementation history. Support equipment.

2. A registration unit that accepts input of the implementation status of the aforementioned subject with respect to the displayed legal requirements and writes the entered implementation status to the implementation history storage unit. The support device according to claim 1, comprising:

3. The display unit notifies of unperformed tasks identified based on the implementation history stored in the implementation history storage unit, from among the tasks indicated by legal requirements to which content tags indicating the need for registration of the implementation history are attached. The support device according to claim 1.

4. The display unit displays a display screen comprising a previous implementation field that displays the implementation history read from the implementation history storage unit for legal requirements to which content tags indicating the need for registration of implementation history have been assigned, and an implementation field that accepts input of the implementation status of the work relating to the subject. The support device according to claim 1.

5. The tagged legal requirement storage unit stores legal requirements to which timing tags indicating the timing at which the user should implement the legal requirement, The search unit searches for legal requirements that specify the performance of the business relating to the subject at the timing indicated by the timing tag. The support device according to claim 1.

6. The display unit displays, as reference information, legal requirements to which timing tags indicating that the user is always complying with legal requirements are attached. The support device according to claim 5.

7. The display unit displays a display screen comprising: a previous implementation field that displays the user's implementation history read from the implementation history storage unit for legal requirements to which the timing tag indicating that the user periodically implements the legal requirements has been assigned; an implementation deadline field that displays the user's future implementation deadline for the legal requirements based on the implementation history stored in the implementation history storage unit and the deadline information specified by the legal requirements; and an implementation field that accepts input of the user's implementation status of the work relating to the subject. The support device according to claim 5.

8. The display unit displays the future implementation deadline for the searched legal requirement based on the implementation history stored in the implementation history storage unit and the deadline information specified by the searched legal requirement. The support device according to claim 1.

9. An information processing device that stores a target tag indicating the type of object to which a legal requirement stipulated by law applies, by attaching it to the legal requirement, A search process that receives input from a user regarding objects related to business operations, and searches for legal requirements to which target tags are assigned that correspond to the input objects, A display process that displays the searched legal requirements along with the execution history of the business related to the subject defined in the aforementioned legal requirements, which is read from the execution history storage unit that stores the execution history of the business related to the subject for each subject. A storage process that stores legal requirements to which content tags indicating the type of work required by the legal requirements have been assigned, A search process that searches for legal requirements that demand the business indicated by the content tags, A necessity determination process that indicates whether or not the aforementioned implementation history needs to be registered, The system performs a priority display process that displays legal requirements with content tags indicating the need for registration of the implementation history over legal requirements with content tags that do not indicate the need for registration of the implementation history. How to help.

10. An information processing device that stores a target tag indicating the type of object to which a legal requirement stipulated by law applies, by attaching it to the legal requirement: A search process that receives input from a user regarding objects related to business operations, and searches for legal requirements to which target tags are assigned that correspond to the input objects, A display process that displays the searched legal requirements along with the execution history of the business related to the subject defined in the aforementioned legal requirements, which is read from the execution history storage unit that stores the execution history of the business related to the subject for each subject. A storage process that stores legal requirements to which content tags indicating the type of work required by the legal requirements have been assigned, A search process that searches for legal requirements that demand the business indicated by the content tags, A necessity determination process that indicates whether or not the aforementioned implementation history needs to be registered, The process includes: executing a priority display process that displays legal requirements with content tags indicating the need for registration of the implementation history above, with higher priority than legal requirements with content tags that do not indicate the need for registration of the implementation history above. Support program.

Images