JP2024033076A - Support device, support method, and support program - Google Patents

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

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

Businesses related to the environment must comply with environmental laws and regulations, but it takes time to understand all of them. Therefore, it takes a lot of effort to identify the laws and regulations that must be observed in each business and manage them manually. Therefore, there is a possibility that tasks required by each law may be omitted from being carried out or notifications may be omitted from government agencies. Failure to comply with laws and regulations may lead to serious corporate compliance violations.

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 the environmental aspects and environmental impact assessment items for each operation. to identify. As a result, an environmental management plan is formulated for each business based on information related to environmental aspects, and the performance of activities against the formulated environmental management plan is evaluated.

Furthermore, the technology disclosed in Patent Document 2 prevents omissions in notifications to government offices by notifying the submission of notifications according to the updated contents when any of equipment, notifiers, or laws and regulations are updated.

Japanese Patent Application Publication No. 2010-102589 Japanese Patent Application Publication No. 2018-205899

However, the technology described in Patent Document 1 does not take legal requirements other than environmental aspects regarding equipment into consideration. Furthermore, the technology described in Patent Document 2 does not take into consideration legal requirements other than notification to government offices. Therefore, the above-mentioned technology cannot manage all the laws and regulations that must be complied with in business.

The present invention has been made in view of the above circumstances, and provides a support device, a support method, and a support program that allow users to comprehensively manage legal requirements that they must comply with in their work. The purpose is to

One of the present inventions for solving the above-mentioned problems is to add a target tag to the legal requirement that indicates the type of object that has a processor and memory and is the object of the legal requirement stipulated by law. a tagged legal requirements storage unit that stores the data as specified by the legal requirements, an implementation history storage unit that stores the implementation history of the business related to the objects specified by the legal requirements for each object, and a search unit that searches the tagged legal requirements storage unit for legal requirements to which a target tag associated with the received and input object is attached; The support device includes a display unit that displays a history of business operations related to the object read from a history storage unit.

According to the present invention, it is possible to comprehensively manage legal requirements that users should comply with in their work.
Structures, effects, etc. other than those described above will be made clear by the description of the embodiments below.

1 is a diagram illustrating an example of the configuration of a support system in this embodiment. FIG. 3 is a diagram showing a detailed functional configuration of a legal requirements management department. FIG. 3 is a diagram showing an example of tags attached to legal requirements. FIG. 3 is a diagram for explaining content tags. It is a figure which shows an example of a tagged legal requirement table. It is a figure which shows an example of an implementation history table. It is a figure showing an example of a menu screen. It is a figure showing an example of an object registration screen. It is a figure which shows the other display example of a menu screen. It is a figure which shows an example of a legal requirements search screen. It is a figure which shows an example of a legal requirements search result screen. FIG. 3 is a diagram for explaining the priority of each tag. It is a figure which shows an example of an implementation item search screen. It is a figure which shows an example of an implementation item management screen. It is a figure showing an example of a report search screen. It is a figure which shows an example of a notification management screen. It is a figure which shows an example of a periodic implementation item search screen. It is a figure which shows an example of a periodic implementation item management screen. FIG. 3 is a processing flow diagram illustrating an overview of search processing. FIG. 3 is a processing flow diagram illustrating details of legal requirements acquisition processing.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
The following description and drawings are examples for explaining the present invention, and are omitted and simplified as appropriate for clarity of explanation. The present invention can also be implemented in various other forms. Unless specifically limited, each component may be singular or plural.

The position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.
In the following description, various information may be described using expressions such as "table,""list," and "queue," but various information may be expressed using data structures other than these. "XX table", "XX list", etc. are sometimes referred to as "XX information" to indicate that they do not depend on the data structure. When describing identification information, expressions such as "identification information", "identifier", "name", "ID", and "number" are used, but these expressions can be replaced with each other.
When there are multiple components having the same or similar functions, the same reference numerals may be given different suffixes for explanation. However, if there is no need to distinguish between these multiple components, the subscripts may be omitted in the description.

In addition, in the following explanation, processing performed by executing a program may be explained, but the program is executed by a processor (e.g., CPU, GPU) to perform a predetermined process using storage resources ( Since the processing is performed using a memory (for example, memory) and/or an interface device (for example, a communication port), the main body of the processing may be a processor. Similarly, the subject of processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The main body of processing performed by running the program is
It may be any arithmetic unit, and may include a dedicated circuit (for example, FPGA or ASIC) that performs specific processing.
A program may be installed on a device, such as a computer, from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server includes a processor and a storage resource for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Furthermore, in the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

FIG. 1 is a diagram showing a configuration example of a support system 1 in this embodiment.
The support system 1 includes a support device 100, one or more law-related databases 200, one or more business management systems 300, and one or more user terminals 400. The support device 100, the law-related database 200, the business management system 300, or the user terminal 400 are connected to, for example, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or a wired or wireless communication such as a dedicated line. Connect for communication via network.

The support device 100 is an environmental law compliance automation system for supporting compliance with environmental laws and regulations when performing environment-related work. 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 includes a processing device 110 such as a CPU (Central Processing Unit), a storage device 120 such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive), a RAM (Random Access Memory), R.O.
It includes a memory 130 such as an M (Read Only Memory), and a network interface 140 configured with an NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, or the like. Processing device 110, storage device 120, memory 130, and network interface 140 are interconnected via a bus.

The processing device 110 is a processor that implements the functions of a law/ordinance information collection section 111, a clause analysis section 112, a legal requirements generation section 113, and a legal requirements management section 114.
The law/ordinance information collection unit 111 acquires information on environmental laws, ordinances, ordinances, etc. from the law-related database 200 and writes the acquired law, ordinance, or ordinance information into the storage device 120.
The article analysis unit 112 analyzes articles of each law, statute, ordinance, etc. stored in the storage device 120. For example, the article analysis unit 112 extracts legal requirements from the article by morphological analysis using article part information 122 stored in the storage device 120. Legal requirements are matters that are required to be observed by laws, ordinances, ordinances, etc. Legal requirements include, for example, the type, content (object), and timing of work that a business operator must perform.

The legal requirements generation unit 113 attaches a tag, which will be described later, to the extracted legal requirements and writes the tags into the storage device 120.
The legal requirements management unit 114 executes processing to support compliance with legal requirements regarding business. For example, the legal requirements management unit 114 causes the user terminal 400 to display a display screen for managing legal requirements to be complied with in business operations. Details of each function possessed by the legal requirements management section 114 will be described later.

The storage device 120 stores article information 121, article component information 122, a list of laws/ordinance names 123, legal requirement information 124, and applicability information 125.
The article information 121 is text data of articles such as laws, ordinances, or ordinances, and is information obtained from the law-related database 200 described later.
The article component information 122 is information regarding components (for example, the grammar of the target language, the part of speech of a word, etc.) used by the article analysis unit 112 to analyze the article.
The law/ordinance name list 123 is a list of laws, law names, or ordinance names of articles to be stored.
The legal requirement information 124 is information indicating what an object of legal requirements should do in order to comply with the law, and is, for example, text data extracted from an article.
Applicability information 125 is information indicating whether or not equipment or parts used in business, or persons related to business, fall under the object of legal requirements.

The law-related database 200 is a database system that stores information on environmental laws, ordinances, ordinances, and the like. The law-related database 200 is, for example, a database system that stores a collection of regulations, a home page of a government agency or local government, or a system that provides an Internet version of official gazettes.
The business management system 300 is an external system for managing business. For example, the business management system 300 stores information such as equipment or supplies used in the business, people related to the business, etc., as stipulated by legal requirements.
The user terminal 400 is a terminal device, such as a personal computer, a tablet terminal, or a smartphone, used by each of the business personnel (hereinafter referred to as "users") U1 to U3. Note that although this diagram exemplifies a configuration in which each of a plurality of users U1 to U3 can operate the user terminal 400, the number of users or the configuration of the number of user terminals 400 is not limited.

FIG. 2 is a diagram showing a detailed functional configuration of the legal requirements management section 114 in this embodiment.
As illustrated, the legal requirements management section 114 includes a search section 115, a display section 116, a registration section 117, a tagged legal requirements storage section 118, and an implementation history storage section 119.
The tagged legal requirements storage unit 118 attaches tags to legal requirements and stores them. The tagged legal requirements storage unit 118 inputs the tagged legal requirements 151 (hereinafter referred to as "tagged legal requirements") and indicates the input tagged legal requirements. Store the tagged legal requirements table 500.

FIG. 3 is a diagram showing an example of tags added to legal requirements in this embodiment.
As shown in the figure, in this embodiment, there are three types of tags attached to each legal requirement: a timing tag, a content tag, and a target tag. A timing tag is a tag that indicates the timing at which a user should perform a task specified by legal requirements. In the illustrated example, the timing tags include an "action" tag that indicates that the work stipulated by the legal requirements must be performed at the time of the action, and an "action" tag that indicates that the work stipulated by the legal requirements must be performed at the time of the action. A ``regular'' tag indicates that the work must be performed regularly, and a ``constantly'' tag indicates that the work stipulated by legal requirements must be performed at all times. An action is a predetermined business activity that is performed at any timing, such as installing equipment, changing equipment, disposing of equipment, disposing of industrial waste, or working outdoors. Further, the target tag is a tag indicating the type of object that is the target of legal requirements. The object is equipment, a person, or the like. As shown in the figure, the target tag includes, 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 an energy manager. Further, the content tag is a tag indicating the type of work required by legal requirements. In the illustrated example, legal requirements are classified into five categories, ``implementation'', ``notification'', ``standards'', ``restrictions'', and ``duties'', based on content tags.

FIG. 4 is a diagram for explaining the content tag according to this embodiment.
The content tag mainly indicates the necessity of registering the implementation history of the work related to the object specified by the legal requirements (specifically, the user registers the implementation history of the object of the legal requirement in the implementation history table 600 described later). whether registration is necessary or not). The implementation history is a record of the history of operations specified by legal requirements regarding an object. As shown in the figure, the content tag "Implementation" indicates what should be done (specifically what to do) and indicates that the work performed by the user needs to be registered as an implementation history (Registration of implementation history is required). (indicating gender). Further, the content tag "notification" indicates a notification to be performed, such as a permit, a notification to the mayor or a government office, and indicates that the notification procedure needs to be registered as an implementation history. In addition, the content tag "criteria" indicates conditional implementation or restriction, and in the case of implementation, it indicates that the work performed by the user must be registered as the implementation history, and in the case of restriction, registration of the implementation history is not required. (does not indicate the necessity of registering implementation history). Further, the content tag "restriction" indicates a specific prohibition and indicates that registration of implementation history is unnecessary. Further, the content tag "obligation" indicates an obligation to make an effort or an idea, and indicates that registration of an implementation history is unnecessary.

(Tagged Legal Requirements Table)
FIG. 5 is a diagram showing 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 may be set in advance by the user, for example.
The tagged legal requirements table 500 is a database that stores legal requirements with tags (timing tags, content tags, or target tags). The tagged legal requirements table 500 includes an ID 501 that is identification information for identifying a legal requirement, a requirement 502 that is the specific content of the legal requirement, and the content of a timing tag attached to the legal requirement. A timing tag 503 to be set, a content tag 504 to which the content of the content tag attached to the legal requirement is set, a target tag 505 to which the content of the target tag attached to the legal requirement is set, and a legal Each data item has a deadline 506 for implementing the specific requirements. Information is set in the deadline 506 when a deadline is required by legal requirements.

In the illustrated example, the legal requirement with ID "1" is assigned the timing tag "regular", the content tag "implementation", and the target tag "products using fluorocarbons", and the deadline is "once/3 months". ”. Therefore, the legal requirements for ID "1" must be "regularly" implemented once every three months for "products that use fluorocarbons." Further, the legal requirements for ID "2" are given a timing tag "regular", a content tag "implementation", and a target tag "smoke", and the deadline is "once/5 years". Therefore, the legal requirement for ID "2" is that "soot and smoke" must be "regularly" carried out once every five years. In addition, the legal requirements with ID "3" are assigned the timing tag "action", the content tag "notification", and the target tag "owner of large-scale commercial buildings", and the deadline is "~14 days". It is. Therefore, the legal requirement for ID "3" is that "owners of large-scale commercial buildings" must "report" within "14 days" from "the time of action (the date of appointment)." Furthermore, the legal requirement with ID "4" has a timing tag "action", a content tag "implementation", a target tag "smoke", and a deadline of "- (not set)". Therefore, the legal requirements of ID "4" must be "implemented" regarding "soot and smoke" "at the time of action (when an accident occurs)".

Returning to FIG. 2, the description of the functional configuration of the legal requirements management section 114 will be continued.
The implementation history storage unit 119 receives from the user the input of the implementation history 154 of the work related to the object defined by the legal requirements, and stores the input implementation history in the implementation history table 600.

(Implementation history table)
FIG. 6 is a diagram showing an example of an implementation history table 600 in this embodiment. The implementation history table 600 is updated at any time, for example, when a user performs a business activity required by legal requirements.
The implementation history table 600 is a database that stores the implementation history of legal requirements implemented for each object related to business. The implementation history table 600 includes data items such as object name 601, target tag 602, legal requirements 603, implementation history 604, implementation notes 605, and action implementation history 606. The legal requirement 603 indicates the ID of the legal requirement. The implementation history 604 is the date when the corresponding legal requirement was most recently implemented. Implementation notes 605 are notes regarding implementation of legal requirements. The action implementation history 606 is the date when the corresponding legal requirement was first implemented.

In the illustrated example, the target "boiler A" with the target tag "smoke" has the legal requirement "ID1" implemented on "2020/10/1", and the implementation notes are "measurement result: 5cm/sec" It is. In addition, for the subject "Boiler A," the legal requirement "ID2" was most recently implemented on "February 15, 2021," and was first implemented on "February 1, 2021." Further, for the target "boiler B" with the target tag "smoke", the legal requirement "ID1" was implemented on "2020/11/1", and the implementation notes are "measurement result: 3 cm/sec". In addition, the target "Mr. Suzuki" with the target tag "person in charge" implemented the legal requirement "ID3" on "2020/9/1".

Returning to FIG. 2, the description of the functional configuration of the legal requirements management section 114 will be continued.
The search unit 115 (environmental law search unit) receives from the user an input of a search query 153 that is a condition of a legal requirement to be searched. Then, the search unit 115 searches for legal requirements matching the search query based on the tagged legal requirements 152 read from the tagged legal requirements table 500. A search query is a combination of arbitrary keywords and tags. For example, the search unit 115 receives an input of an object related to business from a user, and searches the tagged legal requirements table 500 for legal requirements to which a target tag associated with the input object is attached. . The search unit 115 also searches for legal requirements that require the work indicated by the content tag. The search unit 115 also searches for legal requirements that stipulate the execution of business related to the object at the timing indicated by the timing tag.

The display unit 116 (search result display unit) displays the searched legal requirements (search results 156) together with the implementation history 155 regarding the object read from the implementation history table 600. At this time, the display unit 116 calculates and displays the implementation deadline of the searched legal requirement based on the implementation history 155 stored in the implementation history table 600 and the information on the deadline defined by the searched legal requirement. The display unit 116 also displays, as reference information, legal requirements to which a timing tag indicating that the user always complies with the legal requirements is attached. In addition, the display unit 116 notifies unimplemented tasks identified based on the implementation history stored in the implementation history table 600 among the tasks indicated by the legal requirements to which content tags that require registration of implementation history are attached. . “Not implemented” indicates that it has not been implemented.

The registration unit 117 accepts input of the implementation status regarding the object of the displayed legal requirements, and writes the input implementation status into the implementation history table 600 as the implementation history 154.

Next, the operation of the support device 100 will be explained.
The display screen described below is displayed on the user terminal 400 by the display unit 116 of the support device 100. Further, each operation on the display screen described below is accepted by the registration unit 117 of the support device 100.

(Menu screen)
FIG. 7 is a diagram showing an example of a menu screen 700 according to this embodiment.
The menu screen 700 includes object registration 701 for registering objects related to business, legal requirements search 702 for searching for legal requirements required for business, and implementation for managing implementation of legal requirements. Various menus of matter management 703, notification management 704 for managing notifications regarding legal requirements, and periodic implementation matter management 705 for managing legal requirements that should be periodically implemented, and those that are not implemented. and an unimplemented matter notification column 710 for notifying legal requirements. Details of the unimplemented matter notification column 710 will be described later.

(Target registration screen)
FIG. 8 is a diagram showing an example of a target registration screen 800 according to this embodiment.
The display unit 116 displays the target registration screen 800 when receiving an operation to select the target registration 701 on the menu screen 700. The target registration screen 800 includes a keyword input field 801 that accepts the input of the name of the object related to the business (for example, equipment name, administrator name), a target tag selection field 802 that accepts the selection of target tags, and a keyword input field 801 that accepts the input of the name of the object related to the business (e.g., equipment name, administrator name). It includes a registration button 803 for adding and registering the target tag selected in the target tag selection field 802 to the name, and a target list table 810 for displaying a list of registered targets. The object list 810 displays a list of registered object names in association with assigned object tags.

For example, as shown in the figure, when the user inputs the name of the object "heating furnace" in the keyword input field 801, selects "smoke" in the target tag selection field 802, and presses the registration button 803, The display unit 116 displays the name "heating furnace" at the bottom of the target list 810 in association with the target tag "smoke" (for example, by arranging both tags). Further, the registration unit 117 tags and stores the object name “heating furnace” registered on the object registration screen 800 with the object tag “smoke”. Note that, in this example, a case has been described in which one target tag is assigned to one object, but the present invention is not limited to this, and a plurality of target tags may be assigned to one object.

(Menu screen)
FIG. 9 is a diagram showing another display example of the menu screen 700 according to the present embodiment.
This figure shows a display example when the object “heating furnace” is newly registered on the object registration screen 800. The display unit 116 displays the legal requirements to which the target tag associated with each registered object has been attached, and among the legal requirements to which the content tag that requires implementation history registration has been attached, the legal requirements have been implemented. The unimplemented items identified based on the implementation history stored in the history table 600 are displayed in the notification column 711 of the unimplemented item notification column 710, and the name of the object is displayed in the target column 712 of the unimplemented item notification column 710. In the illustrated example, the display unit 116 displays notifications of unfulfilled legal requirements to be implemented regarding a newly registered "heating furnace", "Please submit installation notification!", and "Pollution prevention manager Please appoint someone!” and “Please measure soot and smoke! (XX days left until deadline)” are listed in the unimplemented item notification column 710. Here, the display unit 116 displays the target tag assigned to each registered object and the legal requirements assigned with the content tag "implementation" or "notification" as legal requirements to be implemented for each object. It is extracted from the tagged legal requirements table 500 as a matter.

In this way, by displaying unfulfilled legal requirements for each registered object on the menu screen, users can become aware of legal requirements that must be implemented in their work. Therefore, omissions in implementation can be prevented.

(Legal requirements search screen)
FIG. 10 is a diagram showing an example of a legal requirements search screen 900 according to this embodiment.
Display unit 116 displays legal requirements search screen 900 when receiving an operation to select legal requirements search 702 on menu screen 700 . The legal requirements search screen 900 includes a keyword input field 901 that accepts the input of any keyword, a timing tag selection field 902 that accepts the selection of timing tags, a content tag selection field 903 that accepts the selection of content tags, and a content tag selection field 903 that accepts the selection of objects. It includes a target selection field 904 and a search button 905 for starting a search. In the object selection field 904, the name of the object registered on the object registration screen 800 can be selected.

(Legal requirements search results screen)
FIG. 11 is a diagram showing an example of a legal requirements search result screen 1000 according to the present embodiment.
The display unit 116 displays the legal requirements search result screen 1000 when receiving an operation to press the search button 905 on the legal requirements search screen 900. The search unit 115 searches for keywords entered in the keyword input field 901 of the legal requirements search screen 900, timing tags selected in the timing tag selection field 902, content tags selected in the content tag selection field 903, and target selection. Legal requirements matching the first search query indicating the target tag associated with the object selected in column 904 are searched and read from the tagged legal requirements table 500. The display unit 116 executes the implementation history regarding the object selected in the target selection field 904 (all objects if no object is selected in the target selection field 904) with respect to the legal requirements read by the search unit 115. Read from the history table 600. Then, the display unit 116 displays a list of the legal requirements read by the search unit 115 along with the implementation history regarding the object on the legal requirements search result screen 1000.

This figure shows a display example when "heating furnace" is selected in the target selection column 904 on the legal requirements search screen 900. In this example, the display unit 116 displays a list of legal requirements to which the target tag "smoke" of "heating furnace" is attached on the legal requirements search result screen 1000. The legal requirements search result screen 1000 includes a legal requirements column 1001 indicating read legal requirements, a timing tag column 1002 indicating timing tags attached to the corresponding legal requirements, and a corresponding legal requirement column 1002. A content tag column 1003 showing content tags added to the corresponding legal requirements, a target tag column 1004 for tags added to the corresponding legal requirements, and a previous implementation column 1005 displaying the user's implementation history read from the implementation history table 600. A search result table 1010 having each item is provided. The display unit 116 displays the name of the object targeted for the previous implementation, the date and time of the previous implementation, and notes on the previous implementation in the previous implementation column based on the name 601, implementation history 604, and implementation notes 605 read from the implementation history table 600. 1005.

For example, the legal requirement shown in the first line in this example is implemented for "heating furnace" on the implementation date and time "2021/12/1" with the note "Mr. Suzuki selected". In addition, the legal requirement shown in the second line in this example is a remark "not implemented" for "heating furnace".

In this way, by specifying the conditions of the legal requirements that the user wishes to search on the legal requirements search screen 900, legal requirements matching the conditions are listed on the legal requirements search results screen 1000. can be displayed. For example, by selecting an object in the object selection field 904, the user can display a list of legal requirements to be complied with regarding the object. This allows the user to easily understand the legal requirements to be complied with with respect to each object related to business. In other words, it is possible to comprehensively and collectively manage the legal requirements that users must comply with in their work.

In addition, the legal requirements search result screen 1000 displays timing tags, content tags, and target tags attached to each legal requirement. It is possible to easily grasp the timing of implementing the specified work, the type of work, and the type of object to which it is performed.

Furthermore, the legal requirements search result screen 1000 displays the object for which the work specified in each legal requirement was last performed, the date and time of the work, and its notes. It is possible to easily understand whether or not the object has been implemented.

In addition, on each screen displaying a list of searched legal requirements, the display unit 116 displays legal requirements to which a tag with a high priority is attached according to the preset priority of each tag. Display priority over legal requirements with lower tags. For example, the registration unit 117 receives an input for setting the priority of each tag, and stores the input priority in association with each tag. The display unit 116 identifies the priority of each tag by reading out the stored priority of each tag. "Priority display" means to display legal requirements in the order of priority tags, or to highlight and display legal requirements with tags of high priority. Including. "Displaying with emphasis" includes changing the display color, changing the font size, changing the background color, or adding a mark or the like. In this embodiment, the display unit 116 displays legal requirements in order of priority.

FIG. 12 is a diagram for explaining the priority of each tag in this embodiment.
As shown, content tags have higher priority than timing tags. Furthermore, the timing tags have a higher priority in the order of "action", "regular", and "always". Furthermore, the priority of the content tags is in the order of "implementation,""notification,""standard,""restriction," and "obligation." That is, content tags that require implementation history registration have a higher priority, and content tags that do not require implementation history registration have a lower priority.

Therefore, as shown in the figure, the display unit 116 displays legal requirements that match the search query with the highest priority content tag "implementation" and timing tag "action" according to the priority of each tag. The legal requirements are displayed on the legal requirements search result screen 1000 in order of legal requirements. In this way, legal requirements with content tags that require registration of implementation history are displayed with priority over legal requirements with content tags that do not require registration of implementation history. This allows users to easily identify legal requirements that require registration of implementation history.

(Implementation item search screen)
FIG. 13 is a diagram showing an example of an implementation item search screen 1100 according to this embodiment.
The display unit 116 displays the implementation item search screen 1100 when receiving 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 that accepts the input of an arbitrary keyword, an object selection field 1102 that accepts the selection of an object, and a search button 1103 for starting a search. In the object selection field 1102, the name of the object registered on the object registration screen 800 can be selected.

(Implementation item management screen)
FIG. 14 is a diagram showing 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 receiving an operation of pressing the search button 1103 on the implementation item search screen 1100. The search unit 115 searches for the keyword input in the keyword input field 1101 of the action 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". A legal requirement matching the second query indicating ``is searched from the tagged legal requirement table 500 and read out. The display unit 116 executes the implementation history for the object selected in the target selection field 1102 (all objects if no object is selected in the target selection field 1102) with respect to the legal requirements read by the search unit 115. Read from the history table 600. Then, the display unit 116 displays the list of legal requirements read by the search unit 115 on the implementation item management screen 1200 together with the implementation history regarding the object.

This figure shows a display example when "heating furnace" is selected in the target selection field 1102 on the implementation item search screen 1100. In this example, the display unit 116 displays a list of legal requirements to which the target tag "smoke", the content tag "implementation", and the timing tag "action" of "heating furnace" are attached on the implementation item management screen 1200. There is. The implementation item management screen 1200 includes an implementation item table 1210 having the following items: a legal requirements column 1201, a timing tag column 1202, a content tag column 1203, a target tag column 1204, a previous implementation column 1205, and an implementation column 1206. . The implementation field 1206 includes a date input field 1207 for accepting the input of the date of implementation, a notes input field 1208 for accepting the input of notes on implementation, and a registration button 1209 for registering the input contents. Accept input on implementation status.

When the registration unit 117 receives an input to press the registration button 1209 provided in the implementation field 1206, the registration unit 117 inputs the date input in the date input field 1207 and the notes input in the notes input field 1208 to the implementation history table 600. Write in the history 604 and implementation notes 605. The other items in the implementation matters table 1210 are the same as the search result table 1010 of the legal requirements search result screen 1000, so the description thereof will be omitted.

In this way, by specifying the conditions of the legal requirements that the user wants to search on the implementation item search screen 1100, the user can search for legal requirements that match the conditions and that should be implemented at the time of action. , can be displayed as a list on the implementation item management screen 1200 along with their implementation history. For example, by selecting an object in the object selection field 1102, the user can display legal requirements to be implemented at the time of action regarding the object, along with the contents of past implementation history. This allows the user to thoroughly check whether the work specified by the legal requirements to be complied with is being carried out with respect to the object.

In addition, since the implementation item management screen 1200 accepts input of the implementation history of the legal requirements that the user should perform at the time of action, the user can easily register the implementation history of the work specified by the legal requirements. .

In addition, the implementation item management screen 1200 shown in this example includes legal requirements to which the target tag "smoke" of "heating furnace" is attached, and legal requirements to which the timing tag "periodically" or "constantly" is assigned. A reference table 1220 is provided that displays a list of requirements as reference information. The search unit 115 searches for the legal requirements to which the target tag "smoke" has been added to the "heating furnace" selected in the target selection field 1102, and the legal requirements to which the timing tag "periodically" or "constantly" has been added. Requirements are searched and read from the tagged legal requirements table 500. The display unit 116 displays the list of legal requirements read by the search unit 115 in a reference table 1220. Each item included in the reference table 1220 is the same as that in the implementation items table 1210, so the description thereof will be omitted. Furthermore, among the legal requirements displayed in the reference table 1220, legal requirements with the content tag "implementation" or "notification" that require registration of implementation are provided with a date entry field and notes in the implementation column. A field and a registration button are provided to accept input of implementation history.

By displaying the reference table 1220 in this way, the user can easily understand the legal requirements that should be implemented periodically or constantly, and can also register the implementation history. In this example, the display unit 116 displays legal requirements to which the timing tag "regular" or "always" is attached as reference information, but the timing tag "action" and the content tag "implementation" are displayed as reference information. The legal requirements to be displayed as reference information are not limited to these, as long as they are other than the legal requirements that have been given. For example, the display unit 116 may display, as reference information, legal requirements to which a timing tag of "action" is attached and a content tag other than content tag of "implementation". Good too.

(Notification search screen)
FIG. 15 is a diagram showing an example of a notification search screen 1300 according to this embodiment.
Display unit 116 displays notification search screen 1300 when receiving an operation to select notification management 704 on menu screen 700. The report search screen 1300 includes a keyword input field 1301 for accepting the input of an arbitrary keyword, a target selection field 1302 for accepting the selection of an object, and a search button 1303 for starting a search. In the object selection field 1302, the name of the object registered on the object registration screen 800 can be selected.

(Notification management screen)
FIG. 16 is a diagram showing an example of a notification management screen 1400 according to this embodiment.
The display unit 116 displays the notification management screen 1400 when receiving an operation to press the search button 1303 on the notification search screen 1300. The search unit 115 searches for the keyword entered in the keyword input field 1301 of the notification search screen 1300, the target tag associated with the object selected in the target selection field 1302, and a third search query indicating the content tag "notification." A list of matching legal requirements is searched and read from the tagged legal requirements table 500. The display unit 116 executes the implementation history regarding the object selected in the target selection field 1302 (or all objects if no object is selected in the target selection field 1302) with respect to the legal requirements read by the search unit 115. Read from the history table 600. Then, the display unit 116 displays the list of legal requirements read by the search unit 115 on the notification management screen 1400 together with the implementation history regarding the object.

This figure shows a display example 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 to which the target tag "smoke" of "heating furnace" and the content tag "notification" are attached on the notification management screen 1400. The notification management screen 1400 includes a legal requirements column 1401, a timing tag column 1402, a content tag column 1403, a target tag column 1404, a previous implementation column 1405, and a notification indicating the deadline for the user to carry out the notification specified by the legal requirements. A notification matter table 1410 having each item of an implementation deadline column 1406, an action implementation column 1407, and a notification implementation column 1408 is provided.

The display unit 116 calculates the notification implementation deadline for each legal requirement based on the deadline 506 of the tagged legal requirements table 500 and the implementation history 604 of the implementation history table 600, and displays the calculated notification implementation deadline. It is displayed in the notification implementation deadline column 1406. Further, the action execution column 1407 accepts input of the date on which an action requiring notification was performed. The registration unit 117 writes the date input in the action execution column 1407 into the action execution history 606 of the implementation history table 600. The notification implementation field 1408 includes a date input field 1409 for accepting the input of the date on which the notification was implemented, a notes input field 1411 for accepting the input of notes regarding implementation of the notification, and a registration button 1412 for registering the input contents. Accepts input of implementation history. When the registration unit 117 receives an input to press the registration button 1412 provided in the notification implementation field 1408, the registration unit 117 stores the date input in the date input field 1409 and the notes input in the notes input field 1411 in the implementation history table 600. Write in the implementation history 604 and implementation notes 605. The other items included in the notification matter table 1410 are the same as those in the implementation matter table 1210 included in the implementation matter management screen 1200, and therefore the description thereof will be omitted.

In this way, by specifying the conditions of the legal requirements that the user wishes to search on the notification search screen 1300, the user can search for legal requirements that match the conditions and specify the implementation of notifications. Each can be displayed as a list on the notification management screen 1400 along with its implementation history. For example, by selecting an object in the object selection field 1302, the user can display the legal requirements that define notification regarding the object, along with the contents of past implementation history. This allows the user to thoroughly check whether the notification specified by the legal requirements to be complied with has been carried out regarding the object. Furthermore, by displaying the deadline for filing a notification for each legal requirement, the user can easily understand by when the notification stipulated by the relevant legal requirement should be filed. This will prevent omissions in notifications stipulated by legal requirements.

Further, the notification management screen 1400 accepts input of the user's implementation history of notifications specified by legal requirements, so the user can easily register the implementation history of notifications specified by legal requirements.

In addition, the notification management screen 1400 shown in this example shows the legal requirements to which the target tag "smoke" of "heating furnace" has been added, and the legal requirements to which the timing tag "periodically" or "constantly" has been added. A reference table 1420 is provided that displays a list of requirements as reference information. The search unit 115 searches for legal requirements to which the target tag "smoke" has been assigned for the "heating furnace" selected in the target selection field 1302, and legal requirements to which the timing tag "periodically" or "constantly" has been assigned. Requirements are searched and read from the tagged legal requirements table 500. The display unit 116 displays the list of legal requirements read by the search unit 115 in a reference table 1420. Each item included in the reference table 1420 is the same as that of the reference table 1220 of the implementation item management screen 1200, so the description thereof will be omitted.

By displaying the reference table 1420 in this way, the user can easily understand the legal requirements that should be implemented periodically or constantly, and can also register the implementation history. In this example, the display unit 116 displays legal requirements to which the timing tag "periodically" or "always" is attached as reference information, but the timing tag "action" and the content tag "notification" are displayed as reference information. The legal requirements to be displayed as reference information are not limited to these, as long as they are other than the legal requirements that have been given. For example, the display unit 116 displays, as reference information, legal requirements to which a timing tag "action" is attached and a content tag other than the content tag "notification". Good too.

(Regular implementation item search screen)
FIG. 17 is a diagram showing an example of a regular implementation item search screen 1500 according to the present embodiment.
When the display unit 116 receives an operation to select the regular practice item management 705 on the menu screen 700, the display unit 116 displays the regular practice item search screen 1500. The regular implementation item search screen 1500 includes a keyword input field 1501 that accepts the input of an arbitrary keyword, an object selection field 1502 that accepts the selection of an object, and a search button 1503 for starting a search. In the object selection field 1502, the name of the object registered on the object registration screen 800 can be selected.

(Regular implementation items management screen)
FIG. 18 is a diagram showing an example of a regular implementation item management screen 1600 according to the present embodiment.
When the display unit 116 receives an operation of pressing the search button 1503 on the regular practice item search screen 1500, the display unit 116 displays the regular practice item management screen 1600. The search unit 115 searches for keywords entered in the keyword input field 1501 of the regular 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 "regular". ” is searched and read from the tagged legal requirement table 500. The display unit 116 executes the implementation history regarding the object selected in the target selection field 1502 (or all objects if no object is selected in the target selection field 1502) with respect to the legal requirements read by the search unit 115. Read from the history table 600. Then, the display unit 116 displays the list of legal requirements read by the search unit 115 on the periodic implementation item management screen 1600 together with the implementation history regarding the object.

This figure shows an example of a display when "heating furnace" is selected in the target selection field 1502 on the regular implementation item search screen 1500. In this example, the display unit 116 displays a list of legal requirements to which the target tag "smoke", the content tag "implementation", and the timing tag "regular" are attached to "heating furnace" on the periodic implementation item management screen 1600. ing. The periodic implementation item search screen 1500 includes a legal requirements column 1601, a timing tag column 1602, a content tag column 1603, a target tag column 1604, a previous implementation column 1605 that displays the user's implementation history read from the implementation history table 600, and the relevant A periodic implementation items table 1610 is provided, which includes an implementation deadline column 1606 that indicates a future deadline for the user to implement legal requirements, and an implementation column 1607 that accepts input of the user's implementation status of work related to the object.

The display unit 116 calculates the implementation deadline of each legal requirement based on the deadline 506 of the tagged legal requirements table 500 and the implementation history 604 of the implementation history table 600, and implements the calculated notification implementation deadline. It is displayed in the deadline column 1606. The other items included in the regular implementation items table 1610 are the same as those in the implementation items table 1210 included in the implementation items management screen 1200, so the description thereof will be omitted.

In this way, by specifying the conditions of the legal requirements that the user wants to search on the periodic implementation item search screen 1500, the user can search for legal requirements that match the conditions and that should be implemented periodically. Items can be displayed as a list on the regular implementation item management screen 1600 along with their implementation history. For example, by selecting an object in the object selection field 1502, the user can display legal requirements that should be periodically implemented regarding the object together with the contents of past implementation history. As a result, the user can confirm whether or not the work specified by the legal requirements to be complied with is regularly carried out regarding the object. Furthermore, by displaying the future implementation deadline of each legal requirement, the user can easily understand by when the corresponding legal requirement should be implemented next time. This makes it possible to prevent omissions in the implementation of tasks that should be performed regularly as stipulated by legal requirements.

In addition, since the periodic implementation item management screen 1600 accepts the input of the implementation history of legal requirements that should be performed periodically by the user, the user can easily register the implementation history of the work specified by the legal requirements. Can be done.

In addition, the periodic implementation item management screen 1600 shown in this example includes legal requirements to which the target tag “smoke” of “heating furnace” is attached, and legal requirements to which the timing tag “always” is attached. , a reference table 1620 is provided to display a list as reference information. The search unit 115 tags the legal requirements to which the target tag "smoke" has been added to the "heating furnace" selected in the target selection field 1502, and the legal requirements to which the timing tag "always" has been added. The information is searched and read from the legal requirements table 500. The display unit 116 displays the list of legal requirements read by the search unit 115 in a reference table 1620. Each item included in the reference table 1620 is the same as that in the reference table 1220 of the implementation item management screen 1200, so the description thereof will be omitted.

By displaying the reference table 1620 in this way, the user can easily understand the legal requirements that must be complied with at all times. In this example, the display unit 116 displays the legal requirements to which the timing tag "always" is attached as reference information, but the legal requirements to which the timing tag "periodically" and the content tag "implementation" are attached are displayed as reference information. The legal requirements to be displayed as reference information are not limited to the legal requirements listed above. For example, the display unit 116 may display legal requirements to which the timing tag "action" is attached or legal requirements to which the content tag "notification" is attached as reference information.

<Search processing>
FIG. 19 shows various search screens (legal requirement search screen 900, implementation item search screen 1100, notification search screen 1300, or periodic implementation item search screen 1500) performed by the support device 100 in this embodiment. FIG. 2 is a process flow diagram illustrating an overview of search processing, which is a process for a user to search for information. The search process shown in this figure is executed when an input to press a search button on each search screen is received.

First, the search unit 115 reads a search query indicating the conditions input on the search screen, and reads tagged legal requirements from the tagged legal requirements table 500 (step S101).

For example, the first search query indicating 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, and the content tag selection field 903. It includes the selected content tag and the target tag associated with the object selected in the target selection field 904. The second search query indicating the conditions entered in the implementation item search screen 1100 includes the keyword entered in the keyword input field 1101, the target tag associated with the object selected in the target selection field 1102, and the content tag "implementation". ”, and the timing tag “action”. Further, the third search query indicating 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 object selected in the target selection field 1302, and the content tag " "Notification" included. In addition, the fourth search query indicating the conditions entered on the regular 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, and the content tag. Contains "implementation" and a timing tag "regular".

Subsequently, the search unit 115 obtains legal requirements that match the search query (step S102). Details of the legal requirements acquisition process for acquiring legal requirements that match the search query will be described later.

Then, the search unit 115 outputs the acquired legal requirements to the display unit 116. The display unit 116 reads the implementation history for the input legal requirements from the implementation history table 600, and displays the input legal requirements together with the read implementation history (step S103).

For example, when the display unit 116 receives an operation to press the search button 905 on the legal requirements search screen 900, the display unit 116 displays the input legal requirements together with the implementation history on the legal requirements search results screen 1000. indicate. Further, when receiving an operation of pressing the search button 1103 on the implementation item search screen 1100, the display unit 116 displays the input legal requirements along with their implementation history on the implementation item management screen 1200. Further, when receiving an operation of pressing the search button 1303 on the notification search screen 1300, the display unit 116 displays the input legal requirements on the notification management screen 1400 along with their implementation history. Further, when the display unit 116 receives an operation of pressing the search button 1503 on the periodic implementation item search screen 1500, the display unit 116 displays the input legal requirements along with its implementation history on the periodic implementation item management screen 1600. After that, the search process ends.

<Legal requirements acquisition process>
FIG. 20 is a process flow diagram illustrating details of the legal requirements acquisition process in this embodiment. The legal requirements acquisition process shown in this figure is executed in step S102 described above. The search unit 115 repeatedly executes the processes of steps S1021 to S1023 for all legal requirements.

First, the search unit 115 determines whether a tag attached to a legal requirement matches a tag included in a search query (step S1021). Matching a tag means that the tag included in the search query matches the tag attached to the legal requirement. If the tag does not match (step S1021: No), the search unit 115 executes the processes of steps S1021 to S1023 for the next legal requirement.

On the other hand, if the search unit 115 matches the tag (step S1021: Yes), the search unit 115 determines whether the legal requirement matches the keyword of the search query (step S1022). Matching a keyword means, for example, that a keyword or a word having the same or similar meaning as a keyword is described in a legal requirement. Note that the search unit 115 determines the similarity of the meanings of words using a vocabulary database prepared in advance and morphological analysis. If the keyword does not match (step S1022: No), the search unit 115 executes the processes of steps S1021 to S1023 for the next legal requirement.

On the other hand, when the search unit 115 matches the keyword (step S1022: Yes), the search unit 115 outputs the legal requirement as a hit legal requirement (step S1023). After the search unit 115 executes the processes of steps S1021 to S1023 for all legal requirements, the search unit 115 ends the legal requirements acquisition process.

As explained above, the support device 100 of this embodiment has a processor and a memory, and attaches a target tag indicating the type of object that is subject to legal requirements stipulated by law to the legal requirements. A tagged legal requirements storage unit 118 that attaches and stores tags; an implementation history storage unit 119 that stores, for each object, the implementation history of operations related to the objects specified by the legal requirements; a search unit 115 that receives an input of and searches a tagged legal requirements storage unit 118 for legal requirements to which a target tag associated with the input object is attached; and a display section 116 that displays this information along with the execution history of the work related to the object read from the execution history storage section 119.

With such a configuration, the support device 100 can display the legal requirements to which the target tags associated with the objects are attached together with the respective past implementation histories. Therefore, the user can confirm whether or not the work prescribed by the legal requirements to be complied with is being carried out with respect to the object. This makes it possible to comprehensively and collectively manage the legal requirements that users must comply with in their work.

Further, the support device 100 of the present embodiment accepts input of implementation status regarding the object for the displayed legal requirements, and writes the input implementation status into the implementation history storage unit 119. With such a configuration, it is possible to easily register the performance history of work related to each object defined by legal requirements.

The support device 100 of the present embodiment also stores legal requirements to which a content tag indicating the type of work required by the legal requirement is attached, and stores legal requirements that require the work indicated by the content tag. Search for. With such a configuration, it is possible to search for legal requirements by the type of business indicated by the content tag, so it is possible to search for legal requirements by category classified by the content tag.

Further, the content tag of this embodiment indicates whether registration of implementation history is necessary, and the support device 100 implements the legal requirements to which the content tag indicating the necessity of registration of implementation history is attached. Display with priority over legal requirements with content tags that do not indicate the need for history registration. With such a configuration, the user can easily understand the legal requirements for which the implementation history needs to be registered, so that it is possible to prevent omissions in implementing the legal requirements.

Further, the support device 100 of the present embodiment stores the implementation history stored in the implementation history storage unit 119 among the tasks indicated by the legal requirements to which the content tag indicating the necessity of registration of the implementation history is attached. notification of unperformed tasks identified based on the criteria. With such a configuration, it is possible to prevent the user from omitting to perform tasks specified by legal requirements.

The support device 100 displays a previous implementation column 1205 that displays the implementation history read from the implementation history storage unit 119 and a previous implementation column 1205 that displays the implementation history read out from the implementation history storage unit 119 for legal requirements to which a content tag indicating the necessity of registration of implementation history is attached. An implementation item management screen 1200 is displayed, which includes an implementation column 1206 that accepts input of the implementation status of the work. With such a configuration, the user can efficiently manage the legal requirements that the user should implement in his/her work on the implementation item management screen 1200.

Further, the support device 100 of the present embodiment stores legal requirements to which timing tags are attached indicating the timing at which the user should implement the legal requirements, and performs work related to the object at the timing indicated by the timing tags. Search for legal requirements governing. With this configuration, it is possible for the user to search for legal requirements according to the timing at which they should perform their work.

Further, the support device 100 according to the present embodiment displays, as reference information, legal requirements to which a timing tag indicating that the user always complies with the legal requirements is attached. With such a configuration, the user can easily understand the legal requirements that must be complied with at all times in business.

Further, the support device 100 of the present embodiment reads out from the implementation history storage unit 119 the legal requirements to which a timing tag indicating that the user regularly implements the legal requirements is carried out by the user. A previous implementation column 1605 that displays the history, and an implementation 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 information on the deadline specified by the legal requirement. A periodic implementation item management screen 1600 is displayed that includes a deadline field 1606 and an implementation field 1607 that accepts input of the user's implementation status of work related to the object. With such a configuration, the user can efficiently manage tasks that the user is required to perform periodically, which are stipulated by legal requirements, on the periodic implementation item management screen 1600.

Furthermore, the support device 100 of the present embodiment displays the future implementation deadline of the searched legal requirement based on the implementation history stored in the implementation history storage unit 119 and information on the deadline specified by the searched legal requirement. do. With such a configuration, the user can easily grasp future implementation deadlines for legal requirements.

The present invention is not limited to the embodiments described above, and can be implemented using arbitrary components without departing from the spirit thereof. The embodiments and modifications described above are merely examples, and the present invention is not limited to these contents as long as the characteristics 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 considered within the technical spirit of the present invention are also included within the scope of the present invention.

For example, some of the hardware included in each device of this embodiment may be provided in another device.

Further, each program of the support device may be provided in another device, a certain program may be composed of a plurality of programs, or a plurality of programs may be integrated into one program.

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 (12)

has a processor and memory,
a tagged legal requirements storage unit that adds and stores a target tag indicating the type of object that is a target of legal requirements stipulated by law to the legal requirements;
an implementation history storage unit that stores, for each object, the implementation history of operations related to the objects specified by the legal requirements;
a search unit that receives an 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 is attached;
a display unit that displays the searched legal requirements together with the implementation history of the work related to the object read from the implementation history storage unit. The support device according to claim 1, further comprising: a registration unit that receives input of implementation status regarding the object regarding the displayed legal requirements and writes the input implementation status into the implementation history storage unit. The tagged legal requirements storage unit stores legal requirements to which a content tag indicating the type of work required by the legal requirements is attached;
The search unit searches for legal requirements that require the work indicated by the content tag.
The support device according to claim 1. The content tag indicates whether registration of the implementation history is necessary,
The display section displays the legal requirements attached with a content tag indicating the necessity of registering the implementation history, and the legal requirements attached with a content tag not indicating the necessity of registering the implementation history. be displayed in priority over other requirements.
The support device according to claim 3. The display section displays the unfinished business identified based on the implementation history stored in the implementation history storage section, among the tasks indicated by the legal requirements to which the content tag indicating the need for registration of the implementation history is attached. informing you of the work being carried out;
The support device according to claim 4. The display unit includes a previous implementation column that displays the implementation history read from the implementation history storage unit for legal requirements to which a content tag indicating the necessity of registration of implementation history is attached, and a previous implementation column that displays the implementation history related to the object. displaying a display screen comprising an implementation column for accepting input of the implementation status of the business;
The support device according to claim 4. The tagged legal requirements storage unit stores legal requirements to which a timing tag indicating the timing at which the user should implement the legal requirements is attached;
The search unit searches for legal requirements that stipulate the execution of business related to the object at the timing indicated by the timing tag.
The support device according to claim 1. The display unit displays, as reference information, legal requirements to which a timing tag indicating that the user always complies with the legal requirements is attached.
The support device according to claim 7. The display unit displays the user's implementation history read from the implementation history storage unit for the legal requirements to which the timing tag indicating that the user regularly implements the legal requirements is attached. an implementation column, an implementation deadline column that displays a future implementation deadline for the user of the legal requirement based on the implementation history stored in the implementation history storage unit and information on the deadline specified by the legal requirement, and the object. displaying a display screen comprising an implementation field for receiving input of the user's implementation status of the related work;
The support device according to claim 7. The display unit displays a future implementation deadline of the searched legal requirement based on the implementation history stored in the implementation history storage unit and information on the deadline determined by the searched legal requirement.
The support device according to claim 1. An information processing device that attaches and stores a target tag indicating a type of object that is a target of legal requirements stipulated by law to the legal requirements,
a search process that receives an input of an object related to business from a user and searches for legal requirements attached with a target tag associated with the input object;
display processing for displaying the retrieved legal requirements along with the implementation history of the operations regarding the object that is read from an implementation history storage unit that stores the execution history of the operations regarding the object defined by the legal requirements for each object; How to help. an information processing device that assigns and stores a target tag indicating the type of object that is a target of the legal requirements stipulated by law to the legal requirements;
a search process that receives an input of an object related to business from a user and searches for legal requirements attached with a target tag associated with the input object;
display processing for displaying the retrieved legal requirements along with the implementation history of the operations regarding the object that is read from an implementation history storage unit that stores the execution history of the operations regarding the object defined by the legal requirements for each object; Support program to be implemented.

Images