Document creation device, document creation method, and program
The document creation device structures maintenance records using content blocks, allowing multiple users to chronologically record and associate information, addressing the challenge of organizing and reusing maintenance records efficiently.
Patent Information
- Application Number
- JP2020198032
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-11-30
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-11-30
AI Technical Summary
Conventional maintenance record systems fail to create structured documents that can be easily organized and reused as know-how, mixing important and non-important information, requiring significant manual effort for secondary use.
A document creation device that allows multiple users to record and structure maintenance records chronologically, using blocks representing content types like abnormalities, causes, and treatments, with associations between blocks, enabling easy secondary use.
Enables multiple users to create structured maintenance records that can be easily used for secondary purposes, facilitating efficient organization and reuse of information.
Smart Images

Figure 0007589522000001 
Figure 0007589522000002 
Figure 0007589522000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a document creation device, a document creation method, and a program. [Background technology]
[0002] In maintenance projects such as inspections, investigations, and repairs of plant equipment, documents called maintenance records are generally created to record abnormalities in equipment that occur over time, their treatment, and their causes. Such maintenance records may be created and edited by multiple people over a relatively long period of time for the same project, and important and unimportant information are often mixed together. Therefore, in order to use the maintenance records as know-how, it is necessary to organize past information mainly by hand, which requires a huge amount of labor. Therefore, there is a demand for a technology for creating maintenance records that can structure various contents such as abnormalities, their treatment, and their causes, and easily organize the information when used as know-how.
[0003] As conventional techniques related to the technique of creating a structured document, for example, the techniques described in Patent Document 1 and Patent Document 2 are known. Patent Document 1 describes a technique for canceling an editing operation of any part while maintaining the communication intention of the document creator when creating a document in which information such as facts, fact interpretations, and conclusions related to a certain hypothesis, related to an image diagnosis report, is structured. Patent Document 2 describes a technique for generating a summary of text included in a selected time scale using a related word dictionary that sets the degree of association between action items and related words, related to an electronic medical record that records medical actions in chronological order. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2017-33288 A [Patent Document 2] JP 2012-174080 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, with conventional technology, it was not possible to create a structured maintenance record that would allow multiple staff members to record various details such as equipment abnormalities, the treatment they received, and their causes in chronological order, and that would allow the information to be easily organized for secondary use as know-how.
[0006] One embodiment of the present invention has been made in consideration of the above points, and aims to create a structured document that allows multiple users to record desired content in chronological order and that can be easily used in a secondary manner. [Means for solving the problem]
[0007] In order to achieve the above-mentioned objective, a document creation device according to one embodiment has a block editing unit that associates content representing recorded content with blocks representing types of recorded content in response to user operation, an association editing unit that associates the blocks with the associated content in response to user operation, and an output unit that outputs the blocks with the associated content and the associations between the blocks as a document. Effect of the Invention
[0008] A plurality of users can record desired contents in chronological order, and can create a structured document that can be easily used for secondary purposes. [Brief description of the drawings]
[0009] [Figure 1] FIG. 2 is a diagram illustrating an example of a hardware configuration of a document creation device according to the present embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a functional configuration of a document creation device according to the present embodiment. [Diagram 3] FIG. 13 illustrates an example of a record creation screen. [Figure 4A]This is a diagram (part 1) showing an example of the procedure for creating maintenance records represented in a block diagram. [Figure 4B] This is a diagram (part 2) showing an example of the procedure for creating maintenance records represented in a block diagram. [Figure 4C] This is a diagram (part 3) showing an example of the procedure for creating maintenance records represented in a block diagram. [Diagram 5] FIG. 13 is a diagram showing an example of operation history data when creating a maintenance record (part 1). [Figure 6] FIG. 1 shows an example of a maintenance record display. [Figure 7A] This is a diagram (part 4) showing an example of the procedure for creating maintenance records represented in a block diagram. [Figure 7B] This is a diagram (part 5) showing an example of the procedure for creating maintenance records represented in a block diagram. [Figure 7C] This is a diagram (part 6) showing an example of the procedure for creating maintenance records represented in a block diagram. [Figure 8] FIG. 2 shows an example of operation history data when creating a maintenance record (part 2). [Figure 9] FIG. 2 is a diagram showing an example of a maintenance record display. [Figure 10] A figure showing an example of an editing procedure for maintenance records represented in a block diagram. [Figure 11] FIG. 3 shows an example of a maintenance record display. [Figure 12] FIG. 13 is a diagram showing an example of a maintenance record display as know-how. [Figure 13] 1 is a flowchart illustrating an example of a process for creating a maintenance record represented in a block diagram. [Figure 14] 10 is a flowchart illustrating an example of a maintenance record editing process represented in a block diagram. [Figure 15] 13 is a flowchart illustrating an example of editing processing for individual blocks. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] An embodiment of the present invention will be described below. In this embodiment, a document creation device 10 will be described that can record desired contents in chronological order for multiple users and can create structured documents that can be easily used secondarily, with maintenance records of plant equipment and the like as targets. In addition, a case where maintenance records created by the document creation device 10 according to this embodiment and documents that utilize the maintenance records as know-how will be displayed. A maintenance record is, for example, a document that records abnormalities in plant equipment, the details of the measures taken, the causes, and the like in chronological order.
[0011] Note that targeting preservation records is just one example, and the document creation device 10 of this embodiment is capable of creating structured documents for various types of documents in which contents (including contents that have causal relationships with other contents) are recorded in chronological order by multiple users.
[0012] <Hardware configuration> First, the hardware configuration of the document creation device 10 according to the present embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the hardware configuration of the document creation device 10 according to the present embodiment.
[0013] 1, a document creation device 10 according to this embodiment is realized by the hardware configuration of a general computer or computer system, and has an input device 11, a display device 12, an external I / F 13, a communication I / F 14, a processor 15, and a memory device 16. Each of these hardware components is connected to each other via a bus 17 so as to be able to communicate with each other.
[0014] The input device 11 is, for example, a keyboard, a mouse, a touch panel, etc. The display device 12 is, for example, a display.
[0015] The external I / F 13 is an interface with an external device such as a recording medium 13a. The document creation device 10 can read and write data from and to the recording medium 13a via the external I / F 13. Examples of the recording medium 13a include a CD (Compact Disc), a DVD (Digital Versatile Disk), an SD memory card (Secure Digital memory card), and a USB (Universal Serial Bus) memory card.
[0016] The communication I / F 14 is an interface for connecting the document creation device 10 to a communication network. The processor 15 is, for example, various arithmetic devices such as a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit). The memory device 16 is, for example, various storage devices such as a HDD (Hard Disk Drive), an SSD (Solid State Drive), a RAM (Random Access Memory), a ROM (Read Only Memory), and a flash memory.
[0017] The document creation device 10 according to the present embodiment has the hardware configuration shown in Fig. 1 and can realize various processes described below. Note that the hardware configuration shown in Fig. 1 is an example, and the document creation device 10 may have other hardware configurations. For example, the document creation device 10 may have multiple processors 15 and multiple memory devices 16.
[0018] <Functional configuration> Next, the functional configuration of the document creation device 10 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of the functional configuration of the document creation device 10 according to this embodiment.
[0019] 2, the document creation device 10 according to this embodiment includes an account management unit 101, a record creation screen display unit 102, and a record display unit 103. Each of these units is realized, for example, by a process executed by the processor 15 of one or more programs installed in the document creation device 10.
[0020] Furthermore, the document creation device 10 according to this embodiment has a user information DB 104, an operation history DB 105, a record DB 106, and a know-how DB 107. Each of these DBs is realized, for example, by the memory device 16. Note that at least one of these DBs may be realized by a storage device or the like connected to the document creation device 10 via a communication network.
[0021] The account management unit 101 manages users who use the document creation device 10 by referring to the user information stored in the user information DB 104. The user information is information for managing users, and includes, for example, a user ID, a password, a user name, etc. In addition to the above, the user information may include various other information, such as the user's job title, operation authority, etc.
[0022] The record creation screen display unit 102 displays a screen for the user to create a maintenance record (hereinafter referred to as the "record creation screen"). The user can create a maintenance record by placing blocks representing the types of record contents on the record creation screen, associating text or images representing the contents with the blocks, and relating the blocks with lines or arrows. The lines may be either straight or curved.
[0023] In addition, the user can create records that can be used as know-how by editing the blocks that make up an already created maintenance record and the relationships between the blocks.
[0024] In this embodiment, the types of recorded contents (i.e., categories) are assumed to be four types: “abnormal”, “cause”, “treatment”, and “memo”. Therefore, the blocks are assumed to be four types: “abnormal block”, “cause block”, “treatment block”, and “memo block”.
[0025] An abnormality block is a block for recording abnormalities that have occurred or been confirmed in plant equipment, etc. An abnormality block is associated with text or an image that describes the details of the abnormality.
[0026] A cause block is a block for recording the cause of an abnormality that has occurred or been confirmed in plant equipment, etc. A cause block is associated with text or an image that expresses the content of the cause.
[0027] An action block is a block for recording actions taken in response to abnormalities that have occurred or been confirmed in plant equipment, etc. Action blocks are associated with text and images that express the content of the action.
[0028] The memo block is a block for recording supplementary information (memo) regarding an abnormality, its cause, or treatment. The memo block is associated with text and images that represent the content of the supplementary information.
[0029] A maintenance record includes at least one abnormality block, and cause blocks, action blocks, and memo blocks are optional. In addition, the cause of the abnormality and the content of the action are expressed by relating the cause block and action block to the abnormality block with a line or arrow. Similarly, supplementary information on the abnormality, cause, and content of the action are expressed by relating the memo block to the abnormality block, cause block, and action block with a line or arrow.
[0030] It is possible to associate any number of cause blocks and treatment blocks with one abnormal block by lines or arrows. Similarly, it is possible to associate any number of memo blocks with one abnormal block, one cause block, and one treatment block by lines or arrows.
[0031] Here, record creation screen display unit 102 includes a block diagram display unit 111, a block diagram editing unit 112, a text display unit 113, a text editing unit 114, an image display unit 115, an image editing unit 116, a relationship editing unit 117, and a know-how creation unit 118.
[0032] A block diagram display unit 111 displays various blocks selectable by the user on a record creation screen. A block diagram editing unit 112 performs editing such as arranging and deleting blocks in response to user operations.
[0033] A text display unit 113 displays text associated with a block on the record creation screen. A text editing unit 114 performs editing such as input, deletion, and change of text associated with a block in response to a user operation.
[0034] An image display unit 115 displays images associated with blocks on a record creation screen. An image editing unit 116 performs editing such as adding or deleting images associated with blocks in response to user operations.
[0035] A relationship editing unit 117 performs editing such as setting or deleting lines or arrows that represent relationships between blocks on the record creation screen in response to user operations.
[0036] The know-how creation unit 118 edits an already created maintenance record in response to a user's operation, and creates a maintenance record that can be utilized as know-how (hereinafter, also referred to as a "maintenance record as know-how").
[0037] A record display unit 103 displays maintenance records created on the record creation screen and maintenance records as know-how.
[0038] The operation history DB 105 stores operation history data when an operation for associating a text or an image with a block on a record creation screen is performed. The operation history data includes, for example, an operation ID for identifying the operation, the date and time when the operation was performed, and the content of the operation.
[0039] Record DB 106 stores data representing maintenance records created on a record creation screen (hereinafter referred to as "maintenance record data"). The maintenance record data is all or a part of the operation history data when the maintenance record was created. For example, the maintenance record data may be operation history data when the maintenance record was created, other than the operation history data related to the memo block.
[0040] Data representing the maintenance record as know-how (hereinafter, referred to as "maintenance record data as know-how") is stored in the know-how DB 107. The maintenance record data as know-how is operation history data when the maintenance record as know-how is created.
[0041] <Creating and displaying maintenance records> As an example embodiment, the procedure for creating a maintenance record and its display will be explained assuming that after user 1 creates a maintenance record for the same maintenance case, another user 2 subsequently creates a maintenance record.
[0042] First, an example of the record creation screen displayed by the record creation screen display unit 102 is shown in FIG. 3. The record creation screen 200 shown in FIG. 3 includes a block editing area 201, scroll bars 202-203, an abnormal block 204, a cause block 205, a procedure block 206, a memo block 207, and a delete button 208. The record creation screen 200 shown in FIG. 3 also includes a text editing area 209, a scroll bar 210, an add text button 211, and a delete text button 212. The record creation screen 200 shown in FIG. 3 further includes an image editing area 213, a scroll bar 214, an add image button 215, and a delete image button 216. In addition, the record creation screen 200 shown in FIG. 3 includes a complete button 217, an add tab button 218, and a create know-how button 219.
[0043] The block editing area 201 is an area in which various blocks are arranged. Various blocks can be arranged in the block editing area 201 by dragging and dropping the abnormal block 204, the cause block 205, the action block 206, and the memo block 207 into the block editing area 201. Note that dragging and dropping is only an example, and blocks may be arranged, for example, by pressing the abnormal block 204, the cause block 205, the action block 206, or the memo block 207, and then pressing any position in the block editing area 201.
[0044] Moreover, the display area of the block editing area 201 can be scrolled using scroll bars 202 and 203 .
[0045] When deleting a block placed in the block edit area 201, the block to be deleted is selected and then the delete button 208 is pressed.
[0046] To associate text with a block placed in the block editing area 201 (i.e., to record text in a block), select the block and then press the Add Text button 211. This adds a text input field to the text editing area 209, and by entering text in this text input field, the text can be associated with the block.
[0047] Furthermore, the display area of the text editing area 209 can be scrolled using a scroll bar 210.
[0048] To delete text associated with a block placed in the block editing area 201, the user selects the block and then presses the text delete button 212. This causes the text associated with the block to be deleted. At this time, all of the text associated with the block may be deleted, or only the text selected by the user from the text associated with the block (or a part of the character string that constitutes the text) may be deleted. The user may also select multiple pieces of text to be deleted.
[0049] When editing text associated with a block arranged in the block editing area 201, the text in the text input field displayed in the text editing area 209 can be edited by selecting the block.
[0050] To associate an image with a block arranged in the block editing area 201 (i.e., to record an image in a block), select the block, press the add image button 215, and select an image saved in the memory device 16, etc. This allows the image to be associated with the block.
[0051] Moreover, the display area of the image editing area 213 can be scrolled using a scroll bar 214.
[0052] To delete an image associated with a block placed in the block editing area 201, the user selects the block and then presses the image deletion button 216. This causes the image associated with the block to be deleted. If multiple images are associated with one block, an image selected by the user from among these multiple images may be deleted. The user can also select multiple images to be deleted.
[0053] The completion button 217 is a button for completing the creation of the maintenance record as maintenance record or know-how.
[0054] The add tab button 218 is a button for adding a new tab, and is pressed when the user creates a maintenance record. A block editing area 201, text editing area 209, and image editing area 213 exist for each tab, and when a new tab is added, a new block editing area 201, text editing area 209, and image editing area 213 are displayed. At this time, the new block editing area 201, text editing area 209, and image editing area 213 take over the display contents of the block editing area 201, text editing area 209, and image editing area 213 of the tab added immediately before. However, the taken over display contents cannot be edited.
[0055] The know-how creation button 219 is a button for adding a tab for creating a maintenance record as know-how (hereinafter referred to as a "know-how tab"). When a know-how tab is added, the block editing area 201, text editing area 209, and image editing area 213 of the know-how tab take over the display contents of the block editing area 201, text editing area 209, and image editing area 213 of the tab added immediately before. Note that, unlike normal tabs, the know-how tab allows editing of the carried over display contents.
[0056] <User 1 creates a maintenance record and displays that maintenance record> Before starting to create a security record, the user 1 must log in to the document creation device 10 using his / her own user ID and password. The account management unit 101 performs login authentication, and if the login authentication is successful, the record creation screen display unit 102 displays the record creation screen 200 shown in FIG.
[0057] When creating a maintenance record, user 1 first presses tab add button 218 to create a new tab. This causes record creation screen 200 shown in Fig. 4A to be displayed. On record creation screen 200 shown in Fig. 4A, the date and time when user 1 pressed tab add button 218 and the user name of user 1 are displayed in tab 301. Note that it is not necessary for tab 301 to display both the date and time and the user name; for example, only the date and time may be displayed.
[0058] In this embodiment, it is assumed that user 1 drags and drops abnormal block 204 into block editing area 201. As a result, block diagram editing unit 112 creates "abnormal 1" block 302, and block diagram display unit 111 displays "abnormal 1" block 302.
[0059] Also assume that User 1 selects "Anomaly 1" block 302, presses Add Text button 211 to display text input field 303, and then inputs "Text 1" into text input field 303 at time T1. As a result, "Text 1" is associated with "Anomaly 1" block 302. At this time, operation history data including the operation ID of the operation for associating "Text 1" with "Anomaly 1" block 302, the date and time indicating the time T1 when the operation was performed, and the content of the operation (i.e., associating "Text 1" with "Anomaly 1") is stored in operation history DB 105 by text editing unit 114.
[0060] However, in this embodiment, time T1 is the time when the user inputs text into the text input field, but this is only an example and various times may be used. For example, the time when the text add button 211 is pressed (i.e., the time when the text input field 303 is displayed) may be used as time T1. Also, for example, when editing is performed on the text input into the text input field 303 and the text is updated, the time may be the last update time, or the time specified or edited by the user. The same applies to times represented by the dates and times included in the operation history data related to text, such as times T3 and T4 described later.
[0061] Similarly, assume that User 1 selects "Anomaly 1" block 302, presses Add Image button 215 to display Add Image field 304, and adds "Image 1" at time T2. As a result, "Image 1" is associated with "Anomaly 1" block 302. At this time, operation history data including the operation ID of the operation for associating "Image 1" with "Anomaly 1" block 302, the date and time indicating the time T2 when the operation was performed, and the content of the operation (i.e., associating "Image 1" with "Anomaly 1") is stored in operation history DB 105 by text editing unit 114.
[0062] However, as in the above, time T2 may be various times. For example, the time when the add image button 215 is pressed (i.e., the time when the add image field 304 is displayed) may be time T2. Also, for example, if the image is deleted, changed, or updated, the last update time may be used, or the time specified or edited by the user. The same applies to the time represented by the date and time included in the operation history data related to the image, such as time T5 described later.
[0063] 4B, it is assumed that user 1 drags and drops memo block 207 into block editing area 201. As a result, block diagram editing unit 112 creates "Memo 1-1" block 305, and block diagram display unit 111 displays "Anomaly 1" block 302.
[0064] Also, assume that user 1 connects "abnormality 1" block 302 and "memo 1-1" block 305 with line 309. As a result, the relationship editing unit 117 creates line 309 connecting "abnormality 1" block 302 and "memo 1-1" block 305, and the block diagram display unit 111 displays the line 309. Note that "1-1" in the "memo 1-1" block 305 indicates that this is the first supplementary information related to "abnormality 1."
[0065] Text and images can also be associated with the "Memo 1-1" block 305, just like the "Anomaly 1" block 302. In this embodiment, it is assumed that "Text 2" is entered into the text input field 306 at time T3, and "Text 4" is entered into the text input field 307 at time T4. It is also assumed that "Image 2" is added to the image addition field 308 at time T5.
[0066] 4C, it is assumed that user 1 then drags and drops action block 206 into block editing area 201. As a result, block diagram editing unit 112 creates "action 1-1" block 310, and block diagram display unit 111 displays "action 1-1" block 310.
[0067] Also, assume that user 1 connects the "abnormality 1" block 302 and the "treatment 1-1" block 310 with an arrow 312. As a result, the relationship editing unit 117 creates the arrow 312 connecting the "abnormality 1" block 302 and the "treatment 1-1" block 310, and the arrow 312 is displayed by the block diagram display unit 111. Note that the "1-1" in the "treatment 1-1" block 310 indicates that it is the first treatment content related to "abnormality 1."
[0068] The "treatment 1-1" block 310 can also be associated with text and images, similar to the "abnormality 1" block 302. In this embodiment, it is assumed that "text 4" is entered in the text input field 311 at time T6.
[0069] After completing the above operations, it is assumed that user 1 presses completion button 217. As a result, a security record is created, and the operation history data (or a part of it) when this security record was created is stored in record DB 106 as security record data.
[0070] Here, an example of operation history data when a maintenance record is created based on the above-mentioned Figures 4A to 4C is shown in Figure 5. Operation history data 313 shown in Figure 5 includes operation ID 314, date and time 315, target 316, data type 317, and content 318. Target 316, data type 317, and content 318 indicate the content of the operation, and indicate what content of text or image is associated with which block.
[0071] The operation ID 314 is information for uniquely identifying an operation. Note that the operation ID may include information for identifying a user who performed the operation (for example, a user ID, etc.).
[0072] The date and time 315 is the date and time when the operation was performed. The object 316 is information for identifying the block to which the text or image is associated by the operation (for example, the name of the block arranged in the block editing area 201, etc.). The data type 317 is information representing either the text or the image. The content 318 is information representing the contents of the text or the image. Note that in this embodiment, the blocks are associated with text and images, but this is not limited thereto, and various contents (for example, audio, video, etc.) may be associated with the blocks. In addition, in this embodiment, operation history data regarding the deletion operation (for example, a block deletion operation, a text and image deletion operation associated with a block, etc.) is not illustrated, but the operation history data regarding the deletion operation may also be stored in the operation history DB 105.
[0073] FIG. 6 shows an example of a display of the maintenance record created by the above-mentioned FIGS. 4A to 4C, displayed by the record display unit 103. The maintenance record 319 shown in FIG. 6 includes a date and time 320, a category 321, text 322, and an image 323. The date and time 320 is the date and time when the text and image were associated with the block. In this embodiment, when multiple texts and images are associated with one block, only the oldest date and time is displayed. However, this is not limited to this, and all dates and times may be displayed, or a date and time selected by the user from the multiple dates and times may be displayed.
[0074] Section 321 is information for identifying a block (for example, the name of a block arranged in block editing area 201, etc.). Text 322 is the content of the block associated with the block. Image 323 is the content of the image associated with the block. In the example shown in FIG. 6, when a plurality of texts are associated with one block, text 322 is displayed in a divided form, and text 322 and image 323 are displayed side by side, but this is merely an example and other display methods may be used. Also, maintenance record 319 shown in FIG. 6 may be displayed simultaneously with record creation screen 200.
[0075] <User 2 creates a maintenance record and displays that maintenance record> Next, a case where a user 2 continues to create a maintenance record created by a user 1 will be described.
[0076] Before starting to create a security record, user 2 must log in to document creation device 10 using his / her own user ID and password. Login authentication is performed by account management unit 101, and if the login authentication is successful, record creation screen display unit 102 displays record creation screen 200 shown in FIG. 4C.
[0077] When creating a maintenance record, user 2 first presses tab add button 218 to create a new tab. This causes record creation screen 200 shown in Fig. 7A to be displayed. On record creation screen 200 shown in Fig. 7A, the date and time when user 2 pressed tab add button 218 and the user name of user 2 are displayed in tab 401. Note that it is not necessary for tab 401 to display both the date and time and the user name; for example, only the date and time may be displayed.
[0078] 7A, the block diagram 402 representing the maintenance record created by user 1 is grayed out. The block diagram 402 is a past maintenance record, and user 2 cannot edit the block diagram 402.
[0079] In this embodiment, it is assumed that user 2 drags and drops abnormal block 204 into block editing area 201. As a result, "abnormal 2" block 403 is created by block diagram editing unit 112, and "abnormal 2" block 403 is displayed by block diagram display unit 111. The "2" in "abnormal 2" block 403 indicates that it is the second abnormal block after "abnormal 1."
[0080] Also, assume that User 2 inputs “Text 5” into text input field 404 at time T 7 , and that “Text 5” is associated with “Abnormal 2” block 403 .
[0081] 7B, it is assumed that user 2 drags and drops cause block 205 into block editing area 201. As a result, block diagram editing unit 112 creates a "Cause 2-1" block 405, and block diagram display unit 111 displays a "Cause 1-1" block 405.
[0082] Also, assume that user 2 connects the "Anomaly 2" block 403 and the "Cause 2-1" block 405 with an arrow 408. As a result, the relationship editing unit 117 creates an arrow 408 connecting the "Anomaly 2" block 403 and the "Cause 2-1" block 405, and the arrow 408 is displayed by the block diagram display unit 111. Note that "2-1" in the "Cause 2-1" block 405 indicates that it is the first cause related to "Anomaly 2."
[0083] Similarly, text and images can be associated with the "Cause 2-1" block 405. In this embodiment, it is assumed that "Text 6" is entered into the text input field 406 at time T8, and "Image 3" is added to the image addition field 407 at time T9.
[0084] 7C, it is assumed that user 2 then drags and drops action block 206 into block editing area 201. As a result, a "action 2-1" block 409 is created by block diagram editing unit 112, and a "action 1-1" block 409 is displayed by block diagram display unit 111. Note that "2-1" in "action 2-1" block 409 indicates that it is the first action related to "abnormality 2."
[0085] Also, assume that User 2 connects the "Abnormality 2" block 403 and the "Measures 2-1" block 409 with an arrow 413. As a result, the relationship editing unit 117 creates an arrow 413 connecting the "Abnormality 2" block 403 and the "Measures 2-1" block 409, and the arrow 413 is displayed by the block diagram display unit 111. Note that the "2-1" in the "Measures 2-1" block 409 indicates that it is the first measure related to "Abnormality 2".
[0086] Similarly, text and images can be associated with the “action 2-1” block 409. 10 At time T 11 Add "Image 4" to image addition column 411, time T 12Assume that "Image 5" has been added to the image addition column 412.
[0087] After completing the above operations, it is assumed that User 2 presses Complete button 217. As a result, a maintenance record is created, and the operation history data (or a part of it) when this maintenance record was created is stored in record DB 106 as maintenance record data.
[0088] Here, an example of operation history data when a maintenance record is created based on the above-mentioned Figures 7A to 7C is shown in Figure 8. The items and the like included in the operation history data 414 shown in Figure 8 are as described in Figure 5.
[0089] 9 shows an example of the maintenance record created according to the above-mentioned FIGS. 7A to 7C displayed by the record display unit 103. The display contents of the maintenance record 415 shown in FIG. 9 are as described in FIG.
[0090] <Creating and displaying maintenance records as know-how> As an embodiment, the case where user 3 edits the maintenance records created by user 1 and user 2 to create an edited record as know-how will be described below, and the creation procedure and display thereof will be described.
[0091] Before starting to create a conservation record as know-how, the user 3 needs to log in to the document creation device 10 using his / her own user ID and password. The account management unit 101 performs login authentication, and if the login authentication is successful, the record creation screen display unit 102 displays the record creation screen 200 shown in FIG. 7C.
[0092] When creating a maintenance record as know-how, the user 3 first creates a know-how tab by pressing the know-how creation button 219. As described above, the know-how tab differs from a normal tab in that the inherited display contents (i.e., the block diagram displayed on the record creation screen 200 shown in FIG. 7C (including grayed-out block diagrams)) can be edited.
[0093] As shown in FIG. 10, it is assumed that user 3 has made the following edits.
[0094] The "Cause 2-1" block 405, which was connected to the "Anomaly 2" block 403 by an arrow 408, is changed to the "Cause 1-1" block 405, which essentially represents the cause of the "Anomaly 1" block 302, and is connected to the "Anomaly 1" block 302 by an arrow 501.
[0095] The "Action 2-1" block 409, which was connected to the "Abnormality 2" block 403 by the arrow 413, is also changed to an "Action 1-2" block 409 which represents the action taken for the "Abnormality 1" block 302, and is connected to the "Abnormality 1" block 302 by an arrow 502. The "1-2" in the "Action 1-2" block 409 indicates that it is the second action related to "Abnormality 1".
[0096] The "Memo 1-1" block 305 and the "Anomaly 2" block 403 are determined not to be essential information regarding the case, and are therefore excluded from the know-how.
[0097] In order to exclude a block, arrow, or line from the target, the block, arrow, or line may be displayed in a grayed-out manner to distinguish it from other blocks, arrows, or lines, or the block, arrow, or line that is the target of the know-how may be displayed in a highlighted manner.
[0098] In this way, the maintenance record as know-how is created by editing the blocks, arrows, and lines of the block diagram representing the maintenance record that has already been created. Although detailed explanation is omitted in this embodiment, the text and images associated with each block may be edited (added, deleted, changed, etc.).
[0099] After completing the above operations, it is assumed that user 3 presses the completion button 217. As a result, a maintenance record is created as know-how, and the maintenance record data of this maintenance record as know-how is stored in the know-how DB 107 by the know-how creation unit 118. The maintenance record data of a maintenance record as know-how is the maintenance record data of a maintenance record that has already been created and that has been designated as the subject of know-how by the user (or the maintenance record data that has not been excluded from the subject of know-how). However, if the text and images contained in the maintenance record data have been edited, the maintenance record data includes the edited text and images.
[0100] Here, Figure 11 shows maintenance record 504 which is a merger of maintenance record 319 shown in Figure 6 and maintenance record 415 shown in Figure 9. In contrast to this, maintenance record 505 as know-how created by Figure 10 above is shown in Figure 12. Note that maintenance record 504 shown in Figure 11 and maintenance record 505 shown in Figure 12 are displayed by record display unit 103.
[0101] The maintenance record 503 shown in Fig. 11 is simply a merger of previous maintenance records, while the maintenance record 505 shown in Fig. 12 is an edited version of this that has been interpreted and can be used secondarily as know-how. As described above, in this embodiment, the maintenance records are structured, so they can be easily edited as know-how.
[0102] <Process flow for creating maintenance records> The process flow for creating the above-described security record will be described with reference to Fig. 13. Fig. 13 is a flow chart showing an example of a process for creating a security record represented by a block diagram. It is assumed that the user has already logged in.
[0103] When creating a new maintenance record (YES in step S101), the record creation screen display unit 102 adds a new tab (step S102) and then edits (including creating) the block diagram (step S103). This editing of the block diagram is repeated until the creation of the maintenance record is completed (step S104). The editing of the block diagram is performed by the block diagram editing unit 112, the text editing unit 114, the image editing unit 116, and the relationship editing unit 117.
[0104] On the other hand, when a new maintenance record is not being created (NO in step S101) and the block diagram is being updated with a new tab (YES in step S105), the record creation screen display unit 102 adds a new tab (step S106) and then edits the block diagram (step S103).
[0105] When creating a maintenance record as know-how, after adding a know-how tab using the record creation screen display unit 102, the editing of the block diagram in step S103 described above can be repeatedly performed until the creation of the maintenance record as know-how is completed.
[0106] <Preservation record editing process flow> Next, the flow of the process of editing the block diagram in step S103 above will be described with reference to Fig. 14. Fig. 14 is a flow chart showing an example of the process of editing the maintenance record expressed by a block diagram.
[0107] When an abnormal block is added (YES in step S201), the record creation screen display unit 102 displays the abnormal block in the block editing area in response to drag and drop by the user (step S202), and edits the abnormal block (i.e., adding text, images, etc.) in response to the user's operation (step S203).
[0108] When a memo is added to the abnormal block (YES in step S204), the record creation screen display unit 102 displays the memo block in the editing area in response to drag and drop by the user (step S205), and connects the abnormal block and the memo block with a line (including an arrow; the same applies below) in response to the user's operation (step S206).The record creation screen display unit 102 also edits the memo block in response to the user's operation (step S207).
[0109] When an abnormal block already exists (YES in step S208) and a cause block is to be added (step S209), the record creation screen display unit 102 displays the cause block in the block editing area in response to drag and drop by the user (step S210), and connects the abnormal block and the cause block with a line in response to the user's operation (step S211).The record creation screen display unit 102 also edits the cause block in response to the user's operation (step S212).
[0110] When a memo is added to the cause block (YES in step S213), the record creation screen display unit 102 displays the memo block in the edit area in response to drag and drop by the user (step S214), and connects the cause block and the memo block with a line in response to the user's operation (step S215).The record creation screen display unit 102 also edits the memo block in response to the user's operation (step S216).
[0111] When adding a treatment block (YES in step S217), the record creation screen display unit 102 displays the treatment block in the block editing area in response to drag and drop by the user (step S218), and connects the abnormal block and the treatment block with a line in response to the user's operation (step S219).The record creation screen display unit 102 also edits the treatment block in response to the user's operation (step S220).
[0112] When a memo is added to the action block (YES in step S221), the record creation screen display unit 102 displays the memo block in the editing area in response to the user's drag-and-drop (step S222), and connects the action block and the memo block with a line in response to the user's operation (step S223).The record creation screen display unit 102 also edits the memo block in response to the user's operation (step S224).
[0113] <Editing process for individual blocks> A flow of editing individual blocks (abnormal block, cause block, action block, memo block) will be described with reference to Fig. 15. Fig. 15 is a flow chart showing an example of editing processing of individual blocks.
[0114] The record creation screen display unit 102 selects a block in response to a user's operation (step S301), and adds text if text is to be added (YES in step S302) (step S303), or adds an image if an image is to be added (YES in step S304) (step S305). If editing is to be continued (YES in step S306), the record creation screen display unit 102 repeats steps S302 to S306. On the other hand, if editing is not to be continued (NO in step S306) and another block is to be edited (YES in step S307), the record creation screen display unit 102 selects another block in response to a user's operation (step S301). Note that in FIG. 15, an example of adding text and an image has been described, but the same flow can also be used to change or delete text and images.
[0115] The present invention is not limited to the above-described embodiments specifically disclosed, and various modifications, changes, combinations with known technologies, etc. are possible without departing from the scope of the claims. [Explanation of symbols]
[0116] 10 Document Creation Device 11 Input Devices 12 Display device 13 External I / F 13a Recording media 14 Communication I / F 15 Processors 16 Memory Devices 17 Bus 101 Account Management Department 102 Record creation screen display section 103 Record display section 104 User Information DB 105 Operation History DB 106 Record DB 107 Know-how DB 111 Block diagram display section 112 Block Diagram Editorial Department 113 Text display section 114 Text Editing Department 115 Image display unit 116 Image Editing Department 117 Related Editorial Department 118 Know-how Creation Department
Claims
1. A first tab creation unit that creates a different first tab for each user; a block editing unit that associates content representing the recorded content with a block representing a type of the recorded content in a first tab corresponding to the user in response to an operation by the user; an association editing unit that associates the blocks to which the content is associated with each other in a first tab corresponding to the user in response to an operation by the user; a second tab creation unit that, when a first tab has already been created, creates a second tab by inheriting the blocks and the associations between the blocks in the first tab in an editable manner; an output unit that outputs, as a document, the blocks to which the content is associated in the second tab and the association between the blocks; having The first tab creation unit If a first tab has already been created, a first tab is created that inherits the blocks and the associations between the blocks in the first tab that has already been created in a non-editable manner. Document creation device.
2. a document editing unit that edits, in the second tab, a block to which the content is associated and an association between the blocks in response to a user operation; The output unit is 2. The document creation device according to claim 1, wherein the blocks to which the contents are associated and the associations between the blocks, edited by the document editing section, are output as a document that can be used secondarily.
3. The output unit is 3. The document creation device according to claim 1, further comprising: outputting, as the document, time information associated with the content for the block.
4. A first tab creation step for creating a first tab that is different for each user; a block editing step of associating content representing a recording content with a block representing a type of the recording content in a first tab corresponding to the user in response to an operation by the user; an association editing procedure for associating the blocks to which the content is associated with each other in a first tab corresponding to the user in response to an operation by the user; a second tab creation step of creating a second tab that inherits the blocks and the associations between the blocks in the first tab in an editable manner when a first tab has already been created; an output step of outputting, as a document, the blocks to which the content is associated in the second tab and the association between the blocks; The computer executes The first tab creation step includes: If a first tab has already been created, a first tab is created that inherits the blocks and the associations between the blocks in the first tab that has already been created in a non-editable manner. How to create documentation.
5. A first tab creation step for creating a first tab that is different for each user; a block editing step of associating content representing a recording content with a block representing a type of the recording content in a first tab corresponding to the user in response to an operation by the user; an association editing procedure for associating the blocks to which the content is associated with each other in a first tab corresponding to the user in response to an operation by the user; a second tab creation step of creating a second tab that inherits the blocks and the associations between the blocks in the first tab in an editable manner when a first tab has already been created; an output step of outputting, as a document, the blocks to which the content is associated in the second tab and the association between the blocks; Run the following on your computer: The first tab creation step includes: If a first tab has already been created, a first tab is created that inherits the blocks and the associations between the blocks in the first tab that has already been created in a non-editable manner. program.
Citation Information
Patent Citations
Work procedure manual creation system
JP2009193489A
Information processing system, conference management device, information processing method, method for controlling conference management device, and program
JP2011217098A
User interface program, terminal, system, and method for displaying summary text to time series data
JP2012174080A
Document creation device, method, and program
JP2017033288A
Mobile terminal, management server, work handover support system, work handover support method, and program
JP2018022389A
