Information processing device, information processing method, and program

Abstract

It will be possible to calculate the reduction effect of an application based on its usage history. [Solution] An information processing device that executes an application that accepts data input for each predetermined task includes: a reception unit that accepts input of a first value for calculating the difference between the time required when the user performs the predetermined task using the application and the time required when the user performs the predetermined task without using the application, or a second value indicating the difference; a calculation unit that calculates the reduction effect when the application is used during the predetermined period based on the usage history of the application used for the predetermined task during the predetermined period and the first value, or the reduction effect based on the usage history and the second value; and an output unit that outputs a screen displaying the reduction effect calculated by the calculation unit to a terminal.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing method, and a program.

Background Art

[0002] Techniques for quantitatively evaluating how much business efficiency can be improved by introducing a system having a search function have been studied.

[0003] On the other hand, in recent years, tools for supporting the creation of applications with no-code or low-code have become widespread. In such tools, a user can easily create an application capable of recording records including values input into fields by arranging fields prepared in advance on the application screen.

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the prior art, it is not possible to calculate the reduction effect of an application based on the usage history of the application.

[0005] The present invention has been made in view of the above points, and an object thereof is to make it possible to calculate the reduction effect of an application based on the usage history of the application.

Means for Solving the Problems

[0006] To solve the above problems, an information processing device that executes an application that accepts data input for each predetermined task includes: a reception unit that accepts input of a first value for calculating the difference between the time required when the user performs the predetermined task using the application and the time required when the user performs the predetermined task without using the application, or a second value indicating the difference; a calculation unit that calculates the reduction effect when the application is used during the predetermined period based on the usage history of the application used for the predetermined task during the predetermined period and the first value, or the reduction effect based on the usage history and the second value; and an output unit that outputs a screen displaying the reduction effect calculated by the calculation unit to a terminal. [Effects of the Invention]

[0007] Based on the application's usage history, it becomes possible to calculate the reduction effect of the application. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of the system configuration in the first embodiment. [Figure 2] This figure shows an example of the hardware configuration of the introduction effect calculation device 10 in the first embodiment. [Figure 3] This figure shows an example of the functional configuration of the application creation device 20 and the implementation effect calculation device 10 in the first embodiment. [Figure 4] This diagram shows an example of the home screen display for an app creation service. [Figure 5] This figure shows an example of the display of the business application creation screen. [Figure 6] This figure shows an example of the business application creation screen after the business application creation process is complete. [Figure 7] This is a sequence diagram illustrating an example of the processing procedure for creating a business application in the first embodiment. [Figure 8]This diagram shows an example of updating the home screen after creating a business application. [Figure 9] This figure shows an example of how the initial screen of an app looks. [Figure 10] This figure shows an example of how the app screen will look. [Figure 11] This is a sequence diagram illustrating an example of the processing steps performed when using a business application. [Figure 12] This diagram shows an example of the configuration of a customer management database. [Figure 13] This figure shows an example configuration of the operation log storage unit 25. [Figure 14] This figure shows an example of how the initial screen of the app looks when one or more records exist. [Figure 15] This is a sequence diagram illustrating an example of the processing procedure for calculating the effectiveness of introducing a business application in the first embodiment. [Figure 16] This figure shows an example of the display of the required time setting screen in the first embodiment. [Figure 17] This figure shows an example of the display of the instruction screen for calculating the introduction effect in the first embodiment. [Figure 18] This figure shows an example of the display of the implementation effect output screen in the first embodiment. [Figure 19] This flowchart illustrates an example of the processing procedure for obtaining the number of records in a business application and calculating the implementation effect in the first embodiment. [Figure 20] This flowchart illustrates an example of the processing procedure for obtaining the number of records in a business application and calculating the implementation effect in the second embodiment. [Figure 21] This figure shows an example of the display of the required time setting screen in the third embodiment. [Figure 22] This flowchart illustrates an example of the processing procedure for obtaining the number of records in a business application and calculating the implementation effect in the third embodiment. [Figure 23] This figure shows an example of the display of the implementation effect output screen in the third embodiment. [Figure 24] This is a diagram showing an example of the functional configuration of the user terminal 30 in the fifth embodiment. [Figure 25] This is a sequence diagram for explaining an example of the processing procedure of the calculation process of the introduction effect of the business application in the fifth embodiment. [Figure 26] This is a sequence diagram for explaining an example of the processing procedure of the calculation process of the introduction effect of the business application in the sixth embodiment.

Embodiments for Carrying Out the Invention

[0009] Hereinafter, embodiments of the present invention will be described based on the drawings. FIG. 1 is a diagram showing an example of the system configuration in the first embodiment. In FIG. 1, one or more user terminals 30 are connected to the application creation device 20 and the introduction effect calculation device 10 via a network such as a LAN (Local Area Network) or the Internet. The introduction effect calculation device 10 is connected to the application creation device 20 via a network such as a LAN or the Internet.

[0010] The application creation device 20 is one or more computers that provide a service (hereinafter referred to as "application creation service") for assisting in the creation of applications in non-code or low-code. The application is created by determining the arrangement positions on the screen for one or more fields for receiving the input of values registered as records. The service may be provided as a cloud service. In the present embodiment, an example in which an application used for a predetermined work in business (hereinafter referred to as "business application") is the creation target will be described, but the present embodiment is also applicable to applications for uses other than business.

[0011] Users of the application creation service can create business applications that record records containing the values ​​entered into each field in a database, etc., by placing one or more fields of any type from several pre-defined types of fields (setting items) on the screen (form) of the business application using a GUI (Graphical User Interface), and setting a name (hereinafter referred to as "field name") for each field, thereby associating the value entered into each field with the field name of that field. Field types are distinguished by the type (data type) of the value entered into the field. Examples of types include strings, numbers, and attachments.

[0012] The user terminal 30 is a terminal used by users who create business applications using the application creation device 20. The user terminal 30 also requests the implementation effect calculation device 10 to calculate the implementation effect of the business application in response to user instructions. The implementation effect of a business application refers to the effect (reduction in time and monetary costs) evaluated based on the difference between the time required to perform a prescribed task if the business application is not used (hereinafter referred to as "pre-implementation time") and the time required to perform the prescribed task if the business application is used (hereinafter referred to as "post-implementation time").

[0013] The implementation effect calculation device 10 is one or more computers that calculate the implementation effect of a business application over a predetermined period, and is an example of an information processing device.

[0014] Figure 2 shows an example of the hardware configuration of the introduction effect calculation device 10 in the first embodiment. As shown in Figure 2, the introduction effect calculation device 10 is built using a computer and includes a CPU 101, ROM 102, RAM 103, HD 104, HDD (Hard Disk Drive) controller 105, display 106, external device connection I / F (Interface) 108, network I / F 109, data bus 110, keyboard 111, pointing device 112, DVD-RW (Digital Versatile Disk Rewritable) drive 114, and media I / F 116.

[0015] Of these, the CPU 101 controls the operation of the entire introduction effect calculation device 10. The ROM 102 stores programs used to drive the CPU 101, such as IPL. The RAM 103 is used as the work area for the CPU 101. The HD 104 stores various data such as programs. The HDD controller 105 controls the reading or writing of various data to the HD 104 according to the control of the CPU 101. The display 106 displays various information such as cursors, menus, windows, characters, or images. The external device connection I / F 108 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and printers. The network I / F 109 is an interface for data communication using the communication network 100. The data bus 110 is an address bus and data bus, etc., for electrically connecting each component such as the CPU 101 shown in Figure 2.

[0016] The keyboard 111 is a type of input means equipped with multiple keys for inputting characters, numbers, and various instructions. The pointing device 112 is a type of input means for selecting and executing various instructions, selecting processing targets, and moving the cursor. The DVD-RW drive 114 controls the reading or writing of various data to the DVD-RW 113, which is an example of a removable recording medium. Note that it is not limited to DVD-RW, but may also be DVD-R, etc. The media I / F 116 controls the reading or writing (storage) of data to the recording medium 115, such as flash memory.

[0017] The application creation device 20 and the user terminal 30 may also have the same hardware configuration as shown in Figure 2. The application creation device 20 and the implementation effect calculation device 10 may be implemented using the same computer. In this case, the functional blocks of the application creation device 20 and the functional blocks of the implementation effect calculation device 10 will be contained within a single computer system.

[0018] Figure 3 shows an example of the functional configuration of the application creation device 20 and the implementation effect calculation device 10 in the first embodiment. In Figure 3, the application creation device 20 has an application creation unit 21 and an application operation unit 22. Each of these units is realized by processing that one or more programs installed in the application creation device 20 cause the CPU of the application creation device 20 to execute. The application creation device 20 also utilizes an application information storage unit 23, a record storage unit 24, and an operation log storage unit 25. Each of these storage units can be realized, for example, using an auxiliary storage device of the application creation device 20, or a storage device that can be connected to the application creation device 20 via a network.

[0019] The application creation unit 21 provides a GUI (e.g., a web page) for creating business applications to the user terminal 30 and accepts input from the user of information necessary for creating business applications (hereinafter referred to as "input information"). Specifically, the application creation unit 21 accepts input of the placement location of one or more fields from a plurality of pre-prepared field types for the business application form (screen), as well as the field name for those fields. The application creation unit 21 also accepts input of the name of the business application to be created, an icon representing the business application, etc. Therefore, the input information includes the application name, icon (icon name), field names and location information of each placed field, etc.

[0020] The application creation unit 21 creates a business application based on the input information. Specifically, the application creation unit 21 displays a screen containing each field placed in the business application, accepts input values ​​for each field through the screen, and creates the business application to register the input values ​​for each field in a database or the like, associating them with the field names of each field. It also generates information about the created business application (hereinafter referred to as "application information").

[0021] The application creation unit 21 stores the generated application information in the application information storage unit 23. The application information includes the application name, application ID, icon, and field information for each field. Field information includes the field name, field type, and position information on the form.

[0022] The application operation unit 22 generates a screen for the business application selected by the user on the user terminal 30 based on the application information of that business application, and displays it on the user terminal 30. The application operation unit 22 transmits the operations performed via that screen to the business application.

[0023] The business application performs operations on the record corresponding to the business application in response to operations transmitted from the application operation unit 22, and records history information (hereinafter referred to as "operation log") indicating the content of the operations in the operation log storage unit 25. Record operations include adding, deleting, or editing records.

[0024] The record storage unit 24 stores a database (hereinafter referred to as "application DB") in which records corresponding to each business application are recorded.

[0025] On the other hand, the implementation effect calculation device 10 has a reception unit 11, an acquisition unit 12, a calculation unit 13, and an output unit 14. Each of these units is realized by processing that one or more programs installed in the implementation effect calculation device 10 cause the CPU 101 to execute. The implementation effect calculation device 10 also utilizes a setting information storage unit 15. The setting information storage unit 15 can be realized using, for example, an HD 104, or a storage device that can be connected to the implementation effect calculation device 10 via a network.

[0026] The reception unit 11 receives input (setting) of a first value, or a second value indicating the difference, for calculating the difference between the pre-implementation time, which is the time required when the user performs a predetermined task using the business application, and the post-implementation time, which is the time required when the user performs the predetermined task without using the business application. The reception unit 11 records the received setting information in the setting information storage unit 15. In the following description, we will mainly explain the case where the first value (pre-implementation time and post-implementation time) is the setting information, but the second value may also be the setting information.

[0027] The acquisition unit 12 acquires the usage history (number of records) registered in the record storage unit 24 by the business application used for a predetermined task during a predetermined period. In the first embodiment, the acquisition unit 12 acquires the number of records by referring to the operation log (history information) recorded in the operation log storage unit 25.

[0028] The calculation unit 13 calculates the cost reduction effect when using the business application over a predetermined period based on the usage history (number of records) acquired by the acquisition unit 12 and a first value, or the cost reduction effect based on the number of records and a second value, as the cost reduction effect of introducing the business application.

[0029] The output unit 14 outputs a screen to the user terminal 30 that displays the reduction effect (implementation effect) calculated by the calculation unit 13.

[0030] The following describes the processing procedures performed by the application creation device 20 or the implementation effect calculation device 10. First, the processing procedures performed by the application creation device 20 when creating a business application will be described.

[0031] When the user terminal 30 accesses the application creation device 20, the application creation unit 21 of the application creation device 20 displays the home screen of the application creation service on the user terminal 30.

[0032] Figure 4 shows an example of the home screen display of the app creation service. In Figure 4, the home screen 510 includes an app list 511 and an app creation button 512. The app list 511 is an area that displays a list of app names of business applications that have already been created. The app names of business applications that have already been created can be identified by referring to the app information storage unit 23. The app creation button 512 is a button for receiving instructions to create a new business application.

[0033] When the user presses the app creation button 512, the app creation unit 21 displays the business app creation screen on the user terminal 30.

[0034] Figure 5 shows an example of the display of the business application creation screen. In Figure 5, the business application creation screen 520 includes an icon area 521, an application name area 522, a field area 523, a form area 524, a cancellation button 525, and an application creation button 526, and is a screen that provides a predetermined format for creating a business application. In other words, the business application is created based on the format of the business application creation screen 520.

[0035] The icon area 521 is an area for selecting an icon for the business application to be created (hereinafter referred to as the "target application"), and is also the area where the selected icon is displayed. Specifically, in the initial state, the icon area 521 displays an initial image. The initial image is the default icon as the initial value. When the user performs a predetermined operation such as selection on the icon area 521, a list of candidate icons is displayed. When the user selects one icon from this list, that icon is displayed in the icon area 521. In other words, the user can customize the icon area 521 to set an icon suitable for the target application.

[0036] The application name area 522 is an area for accepting input of a string indicating the application name of the target application. Initially, the application name area 522 displays a default application name, such as "New Business Application". Users can customize it to enter an appropriate application name for the target application in the application name area 522.

[0037] Field area 523 is an area that displays a list of field types that can be selected as placement targets for the target application (hereinafter referred to as "field types").

[0038] Form area 524 is the area corresponding to the form (screen) of the target application. In its initial state, nothing is placed in form area 524.

[0039] The Cancel Creation button 525 is a button that accepts a command to cancel the creation of the target application. The Create Application button 526 is a button that accepts a command to proceed with the creation of the target application.

[0040] For example, the user first operates the icon area 521 to select the icon of the target application. Next, the user enters the name of the target application into the application name area 522.

[0041] Next, the user drags and drops one of the field types included in the field area 523 to any location in the form area 524, thereby placing a field of that field type at the drop location. The user then sets a field name for the placed field. If multiple fields are to be placed on the form of the target application, the user repeats the process of placing the field types and setting the field names. Figure 5 shows an example where a field of type string is placed in the form area 524.

[0042] Once the above steps are completed, the business application creation screen 520 will look like Figure 6, for example.

[0043] Figure 6 shows an example of the business application creation screen after the business application creation process is complete. In Figure 6, the same parts as in Figure 5 are denoted by the same reference numerals. Figure 6 shows an icon selected and "Customer Management Application" entered as the application name. It also shows an example where four fields, "Company Name," "Department Name," "Contact Person Name," and "Address," are placed in form area 524. These four fields are of type string. A business application with such fields, as its name ("Customer Management Application") suggests, is a business application designed to support the recording and management of customer information. Users of the Customer Management Application can electronically record customer information by entering values ​​into each field.

[0044] When the application creation button 526 is pressed on the business application creation screen 520 in Figure 6, the processing procedure in Figure 7 is executed.

[0045] Figure 7 is a sequence diagram illustrating an example of the processing steps for creating a business application in the first embodiment.

[0046] In step S101, the user terminal 30 sends input information for the business application creation screen 520 to the application creation device 20 in response to the press of the application creation button 526. This input information includes the icon name of the icon displayed in the icon area 521, the application name displayed in the application name area 522, and the field information of each field located in the form area 524.

[0047] The application creation unit 21 of the application creation device 20 creates a business application based on the input information (S102). At this time, the application creation unit 21 generates application information based on the input information and records the application information in the application information storage unit 23. Basically, the application information includes the application ID in addition to the information contained in the input information. Therefore, the application information includes the application ID, icon, application name, field information for each field, etc. The application creation unit 21 also generates an application DB corresponding to the created business application in the record storage unit 24. Hereinafter, the application DB for the customer management application will be referred to as the "customer management DB". At this point, the customer management DB has no records registered.

[0048] Next, the app creation unit 21 regenerates the home screen 510 based on the list of app names stored in the app information storage unit 23 and displays the home screen 510 on the user terminal 30 (S103).

[0049] Figure 8 shows an example of updating the home screen after creating a business application. In Figure 8, the same parts as in Figure 4 are denoted by the same reference numerals. In the home screen 510 of Figure 8, the name of the target application ("Customer Management Application") has been newly added to the application list 511. The home screen 510 is a screen that is displayed to all users not only when creating a business application but also when using an existing business application, and users can select the business application to use from the application list 511. Therefore, when the home screen 510 as shown in Figure 8 is displayed, not only the user who created the Customer Management Application but also other users can use the target application.

[0050] Next, I will explain the usage phases of the business application.

[0051] For example, when the user terminal 30 of the user who created the customer management app or another user (hereinafter referred to as "app user") is displaying the home screen 510 shown in Figure 8, if the app user selects "Customer Management App" in the app list 511, the customer management app will display the initial screen of the customer management app (hereinafter referred to as "app initial screen") on the user terminal 30 based on the app information of the customer management app.

[0052] Figure 9 shows an example of the initial screen display of the application. In Figure 9, the initial screen 530 of the application includes a record list area 531 and an add record button 532.

[0053] The record list area 531 is the area that displays a list of records registered in the customer management database based on values ​​previously entered by users of the customer management application. In Figure 9, corresponding to the situation when the customer management application is used for the first time, no records have been registered in the customer management database, so no records are displayed in the record list area 531.

[0054] The record addition button 532 is a button that accepts instructions to add (register) a new record (customer information) using the customer management application.

[0055] Therefore, if an app user wants to enter customer information using the customer management app, they press the Add Record button 532.

[0056] When the record addition button 532 is pressed, the app creation unit 21 displays the main screen of the customer management app (hereinafter referred to as the "app screen") on the user terminal 30 of the app user, based on the app information of the customer management app.

[0057] Figure 10 shows an example of the application screen display. In Figure 10, the application screen 540 includes an icon area 541, an application name area 542, a form 543, a cancel button 544, and a save button 545. The icon area 541 is the area where the icon of the customer management application is displayed. The application name area 542 is the area where the application name of the customer management application is displayed. The form 543 is the area that contains the fields set for the customer management application and accepts value input through each field. Note that since Figure 10 corresponds to Figure 6, the form 543 in Figure 10 contains the fields that were placed in the form area 524 of Figure 6. The cancel button 544 is a button that accepts a command to cancel input. The save button 545 is a button that accepts a command to save the values ​​entered in each field.

[0058] Once values ​​are entered for each field and the save button 545 is pressed, the processing procedure shown in Figure 11 is executed.

[0059] Figure 11 is a sequence diagram illustrating an example of the processing steps performed when using a business application.

[0060] In response to the press of the save button 545, the user terminal 30 sends a record operation request to the application creation device 20, which includes the application ID of the business application being used (in this case, the "customer management application") (S201). If the save button 545 is pressed on the application screen 540 in Figure 10, the operation request indicates "add record" and includes the values ​​entered for each field, associated with the field names of each field. In addition to "add record," there are also "edit record" and "delete record" operations.

[0061] Next, the application operation unit 22 transmits the operation request to the customer management application corresponding to the application ID contained in the operation request (S202). The customer management application performs the operation in response to the operation request on the application DB (customer management DB) corresponding to the customer management application in the record storage unit 24 (S203).

[0062] Figure 12 shows an example of the configuration of a customer management database. As shown in Figure 12, the customer management database is a database that stores records containing the values ​​entered for each field, associated with the field names of the fields set for the customer management application. Figure 12(1) shows the state when the first record is registered in the customer management database. Figure 12(2) shows the state when multiple records have been registered by repeating the processing procedure in Figure 11.

[0063] Next, the customer management application records an operation log in the operation log storage unit 25, which shows the details of the operation performed on the customer management database (S204).

[0064] Figure 13 shows an example of the configuration of the operation log storage unit 25. Each row in Figure 13 corresponds to one operation log. One operation log includes items such as date and time, application ID, operator ID, operator name, and operation type. The date and time is the date and time (date and time) when the record operation was performed. The application ID is the application ID of the business application that performed the record operation (in the case of Figure 11, the customer management application). The application name is the name of the business application. The operator ID and operator name are the ID and name of the user of the user terminal 30 that gave the instruction regarding the operation. The operation type is information indicating whether the operation is "add record," "edit record," or "delete record." When the processing procedure in Figure 11 is executed based on pressing the add record button 532 on the application initial screen 530, the operation type is "add record."

[0065] Next, the customer management application sends all records registered in the customer management database to the application operation unit 22 (S205). Based on these records, the application operation unit 22 regenerates the application initial screen 530 and displays the application initial screen 530 on the user terminal 30 (S206).

[0066] Figure 14 shows an example of the initial screen display of the application when one or more records exist. In Figure 14, the same reference numerals are used for parts identical to those in Figure 9, and their explanations are omitted as appropriate.

[0067] The initial application screen 530 in Figure 14 corresponds to the state of the customer management database as shown in Figure 12 (2). Therefore, the record list area 531 contains the records shown in Figure 12 (2). Additionally, an edit button 533 and a delete button 534 have been added to each record.

[0068] The edit button 533 is a button for receiving an edit instruction for the corresponding record. Editing a record means changing the values ​​of some or all of the items (fields) in that record. When the edit button 533 for any record is pressed, the application operation unit 22 displays the application screen 540 (Figure 10) with that record as the target of processing on the user terminal 30. In this case, the values ​​registered in that record are displayed in each field of the application screen 540. When the user changes the value of one or more fields and presses the save button 545, the same processing procedure as in Figure 11 is executed. However, in step S203, the customer management application does not add a new record, but rather changes the values ​​of the record that was targeted for processing. Also, in step S204, the customer management application records an operation log that includes "record editing" as the operation type.

[0069] Furthermore, on the initial app screen 530 (Figure 14), the delete button 534 is a button for receiving instructions to delete the corresponding record. Deleting a record means removing that record from the customer management database. When the delete button 534 for any record is pressed, the same processing procedure as in Figure 11 is executed. However, in step S201, the user terminal 30 requests the deletion of the record. Also, in step S203, the customer management app deletes the record from the customer management database. Also, in step S204, the customer management app records an operation log that includes "delete record" as the operation type.

[0070] Next, we will explain how to calculate the effects of introducing a business application. Figure 15 is a sequence diagram illustrating an example of the processing steps for calculating the effects of introducing a business application in the first embodiment.

[0071] In step S301, the reception unit 11 of the implementation effect calculation device 10 displays a screen (hereinafter referred to as the "required time setting screen") on the user terminal 30 that allows the user to set the required time before implementation and the required time after implementation for each business application. Step S301 may be executed, for example, in response to a request from the user terminal 30 that is sent in response to user input to the user terminal 30.

[0072] Figure 16 shows an example of the display of the required time setting screen in the first embodiment. In Figure 16, the required time setting screen 550 has an application selection area 551, a pre-installation required time setting area 552, a post-installation required time setting area 553, an add button 554, and a save button 555.

[0073] The application selection area 551 contains one or more pull-down lists, and for each pull-down list, it is possible to select the business applications to be included in the calculation of implementation effects. Each pull-down list includes the application names of the application information stored in the application information storage unit 23 as options.

[0074] The pre-implementation time setting area 552 is an area for receiving input (setting) of the pre-implementation time for each business application selected in the dropdown list of the application selection area 551.

[0075] The Post-Implementation Time Setting Area 553 is an area in the Application Selection Area 551 that accepts input (setting) of the post-implementation time required for each business application selected in the corresponding dropdown list.

[0076] Pre-implementation time for a particular business application refers to the time required for tasks corresponding to registering one record in that business application before its implementation (for example, in the case of a customer management application, the task of recording one customer's information in a prescribed document or database). Post-implementation time for a particular business application refers to the time required to register one record using that business application. Pre-implementation time and post-implementation time do not necessarily have to be measured precisely and may be values ​​evaluated based on the user's perception.

[0077] The add button 554 is a button that accepts a command to add one line of input area to the application selection area 551, the pre-installation time setting area 552, and the post-installation time setting area 553.

[0078] The save button 555 is a button that accepts instructions to save the information entered (set) in the application selection area 551, the pre-implementation time setting area 552, and the post-implementation time setting area 553 (hereinafter referred to as "setting information"). The setting information includes the application ID, application name, pre-implementation time, and post-implementation time for each business application that is the target of the calculation of implementation effects.

[0079] Note that Figure 16 shows an example where both the time required before implementation and the time required after implementation are entered, but this is not the only example. Ultimately, it is sufficient for the user to be able to identify the time saved between before and after implementation, i.e., the difference in time, through user input. Therefore, the user may input the difference in time between the time required before implementation and the time required after implementation, or they may input the time required before implementation and the reduction rate after implementation and calculate the difference in time. The time required before implementation and the time required after implementation are examples of the first value. The time required before implementation and the reduction rate after implementation also correspond to examples of the first value. The difference in time between the time required before implementation and the time required after implementation is an example of the second value.

[0080] When input is made on the time setting screen 550 and the save button 555 is pressed, the user terminal 30 transmits the setting information to the implementation effect calculation device 10 (S302).

[0081] When the reception unit 11 of the implementation effect calculation device 10 receives (accepts) the setting information, it stores the setting information in the setting information storage unit 15 (S303). Therefore, the setting information storage unit 15 stores the application ID, application name, pre-implementation time, and post-implementation time for each business application that is the subject of the implementation effect calculation.

[0082] Subsequently, steps S311 and beyond are executed at the user's discretion. At the start of step S311, the user terminal 30 displays a screen for receiving instructions from the user to calculate the implementation effect (hereinafter referred to as the "implementation effect calculation instruction screen").

[0083] Figure 17 shows an example of the display of the instruction screen for calculating the implementation effect in the first embodiment. In Figure 17, the instruction screen for calculating the implementation effect 560 includes a start date input area 561, an end date input area 562, and a calculation button 563.

[0084] The start date input area 561 is for receiving input for the start date of the period to be used for calculating the implementation effect (hereinafter referred to as the "target period"). The end date input area 562 is for receiving input for the end date of the target period. The calculation button 563 is a button for receiving instructions to calculate the implementation effect for the target period.

[0085] When the user enters the start and end dates of the target period and presses the calculate button 563, the user terminal 30 sends a request to calculate the implementation effect to the implementation effect calculation device 10 (S311). This calculation request includes the target period information (start date and end date).

[0086] When the calculation unit 13 of the implementation effect calculation device 10 receives the calculation request, it obtains setting information (application ID, application name, pre-implementation time, and post-implementation time for each business application to be used for calculating the implementation effect) from the setting information storage unit 15 (S312, S313).

[0087] Next, the calculation unit 13 specifies a set of application IDs included in the configuration information and sends a request to the acquisition unit 12 to obtain the number of records for each business application (hereinafter referred to as "target application") whose application ID is included in that set (S314). Here, the number of records for a business application refers to the number of records stored in the application DB corresponding to that business application. The number of records for a business application is an example of the usage history registered by the business application. The usage history may also include the number of logins or the number of times the application's processing has been executed.

[0088] The acquisition unit 12 acquires all operation logs from the operation log storage unit 25 in response to the acquisition request (S315, S316). Subsequently, the acquisition unit 12 acquires (calculates) the usage history (number of records) for each target application based on the acquired operation logs (S317). Subsequently, the acquisition unit 12 transmits the usage history (number of records) for each target application to the calculation unit 13 (S318). In this way, the number of records is calculated based on the operation logs. Therefore, the operation logs are also an example of the usage history.

[0089] Next, the calculation unit 13 calculates the implementation effect for each target application during the target period based on the pre-implementation time and post-implementation time received by the reception unit 11, and the usage history (number of records) acquired for each target application by the acquisition unit 12 (S319). Subsequently, the calculation unit 13 transmits the calculated implementation effect to the output unit 14 (S320).

[0090] The output unit 14 outputs (displays) the implementation effect to the user terminal 30 (S321). For example, the output unit 14 generates a screen including the implementation effect (hereinafter referred to as the "implementation effect output screen") and displays the implementation effect output screen on the user terminal 30.

[0091] Figure 18 shows an example of the display of the implementation effect output screen in the first embodiment. In Figure 18, the implementation effect output screen 570 includes an application-specific output area 571 and a total implementation effect output area 572.

[0092] The application-specific output area 571 is an area that shows, for each target application, the time required before implementation, the time required after implementation during the target period, and the implementation effect during the target period.

[0093] The total implementation effect output area 572 is the area that shows the total implementation effect. The total implementation effect is the sum of the implementation effects (reduction in required time) for each target application.

[0094] Next, we will explain the details of steps S317 and S319. Figure 19 is a flowchart illustrating an example of the processing procedure for acquiring the number of records in the business application and calculating the implementation effect in the first embodiment. Steps S401 to S405 in Figure 19 correspond to the record acquisition process executed by the acquisition unit 12 in step S317 of Figure 15.

[0095] First, the acquisition unit 12 executes a loop process L1, which includes steps S401 to S404, for each operation log acquired from the operation log storage unit 25 (Figure 13). The operation log that is the target of processing in the loop process L1 is hereinafter referred to as the "target log".

[0096] In step S401, the acquisition unit 12 determines whether the "date and time" of the target log falls within the target period. If the "date and time" of the target log falls within the target period (Yes in S401), the acquisition unit 12 determines whether the application name of the target log is included in the configuration information (S402). In other words, it determines whether the business application related to the target log is the target application. Note that the application ID may be used instead of the application name. If the "application name" of the target log is included in the configuration information (Yes in S402), the acquisition unit 12 determines whether the "operation type" of the target log is "record addition" (S403). In other words, it determines whether the target log is an operation log recorded in conjunction with the addition of a record to the application DB. If the "operation type" of the target log is "record addition" (Yes in S403), the acquisition unit 12 adds the target log to the target list (S404). The target list is a list structure data for storing operation logs used to count the number of records of the target application, and is empty in its initial state.

[0097] If the "date and time" of the target log is not within the target period (No in S401), if the application name of the target log is not included in the configuration information (No in S402), or if the "operation type" of the target log is not "add record" (No in S403), the acquisition unit 12 will not add the target log to the target list.

[0098] Once loop processing L1 is executed for all operation logs, the target list will contain operation logs recorded when each target application added a record within the target period. In this state, the acquisition unit 12 classifies the operation logs in the target list by target application and sets the number of operation logs for each target application as the number of records for each target application (S405). In other words, since the operation logs included in the target list were recorded when records were added, the number of records can be estimated by counting the number of such operation logs.

[0099] The following steps S406 to S409 correspond to the calculation process of the introduction effect performed by the calculation unit 13 in step S319 of Figure 15.

[0100] First, the calculation unit 13 executes a loop process L2, including steps S406 to S408, for each target application whose operation log is included in the target list. The target application being processed in the loop process L2 is hereinafter referred to as "Target Application X".

[0101] In step S406, the calculation unit 13 obtains the pre-implementation time required for the target application X from the configuration information. Next, the calculation unit 13 obtains the post-implementation time required for the target application X from the configuration information (S407). Subsequently, the calculation unit 13 calculates (pre-implementation time required - post-implementation time required) × number of records, and takes the calculation result as the implementation effect of the target application X (S408). That is, the calculation unit 13 calculates a third value as the implementation effect (reduction effect) by multiplying the difference between the pre-implementation time required and the post-implementation time required by the number of records. The "number of records" here is the number of records obtained for the target application X in step S405.

[0102] Once loop processing L2 has been executed for all target applications, the implementation effect has been calculated for each target application. In this state, the calculation unit 13 calculates the sum of the implementation effects for each target application (S409).

[0103] The above processing procedure yields the information that can be included in the implementation effect output screen 570 (Figure 18).

[0104] As described above, according to the first embodiment, the effect of introducing a business application can be calculated based on the difference between the number of records registered by the business application and the time required for work before and after the introduction of the business application. Therefore, it is possible to calculate the reduction effect of the application based on the application usage history (number of records).

[0105] Furthermore, by calculating the number of records from the operation logs, it is possible to determine the number of records for each business application without accessing each application's database.

[0106] Next, a second embodiment will be described. The differences between the second embodiment and the first embodiment will be described. Therefore, points not specifically mentioned may be the same as in the first embodiment.

[0107] In the first embodiment, the number of operation logs with the operation type "add record" was used as the number of records. However, records can be deleted, and deleted records may have been registered in error. Also, since deleted records do not exist in the application DB, the number of "add record" operation logs may not exactly match the number of records in the application DB. In the second embodiment, taking these possibilities into consideration, an example is described in which deleted records are not included in the implementation effect. By doing so, it is expected that the implementation effect can be calculated more accurately.

[0108] In the second embodiment, the processing procedure in Figure 19 is replaced by the processing procedure in Figure 20. Figure 20 is a flowchart illustrating an example of the processing procedure for obtaining the number of records in the business application and calculating the implementation effect in the second embodiment. In Figure 20, the same step numbers are used for steps that are the same as in Figure 19, and their explanations are omitted as appropriate.

[0109] In Figure 20, steps S403 and S405 in Figure 19 are replaced with S403a and S405a.

[0110] In step S403a, the acquisition unit 12 determines whether the "operation type" of the target log is "record addition" or "record deletion". If the "operation type" of the target log is "record addition" or "record deletion" (Yes in S403a), the acquisition unit 12 adds the target log to the target list (S404). Therefore, in the second embodiment, operation logs related to "record addition" or "record deletion" are added to the target list for each target application.

[0111] In step S405a, the acquisition unit 12 classifies the operation logs in the target list into "record addition" and "record deletion" for each target application, and uses the number of "record deletion" operation logs minus the number of "record addition" operation logs as the number of records for each target application. As a result, the number of deleted records is no longer included in the number of records for each target application.

[0112] The process from this point onward is the same as in the first embodiment. Therefore, in step S408, the implementation effect is calculated based on the number of such records.

[0113] Next, a third embodiment will be described. The differences between the third embodiment and the first embodiment will be described. Therefore, points not specifically mentioned may be the same as in the first embodiment.

[0114] In each of the embodiments described above, an example was given in which the effectiveness of introducing a business application was evaluated by the amount of work time saved by introducing the business application. In the third embodiment, an example is given in which the economic cost reduction, taking into account labor costs, is included in the effectiveness of the introduction.

[0115] In the third embodiment, the configuration of the required time setting screen 550 differs from that in Figure 16. Figure 21 shows an example of the display of the required time setting screen in the third embodiment. In Figure 21, the same reference numerals are used for parts identical to those in Figure 16, and their descriptions are omitted.

[0116] The time required setting screen 550 shown in Figure 21 further includes an hourly wage setting area 556. The hourly wage setting area 556 is an area for receiving input of an hourly wage (hereinafter simply referred to as "hourly wage"), which is an example of the labor costs of a person who performs work using the business application (hereinafter referred to as "worker"). The value of the hourly wage to be entered may be, for example, the average hourly wage of workers in the organization, or the hourly wage of a specific worker. In the third embodiment, the same time required setting screen 550 as in Figure 16 may also be used. In this case, the hourly wage may be a predetermined fixed value, such as the industry average. However, by setting the hourly wage on the time required setting screen 550, it is possible to calculate a more accurate reduction cost according to the user environment.

[0117] The processing procedure in Figure 19 is replaced by the processing procedure in Figure 22. Figure 22 is a flowchart illustrating an example of the processing procedure for obtaining the number of records in the business application and calculating the implementation effect in the third embodiment. In Figure 22, steps identical to those in Figure 19 are given the same step numbers, and their explanations are omitted as appropriate.

[0118] In Figure 22, step S410 is added at the end. In step S410, the calculation unit 13 calculates the reduction cost (fourth value) by multiplying the sum calculated in step S409 by the hourly wage. In this case, if the unit of the sum is minutes, the hourly wage is multiplied by the value obtained by dividing the sum by 60.

[0119] As a result, in step S321 of Figure 15, the implementation effect output screen 570, as shown in Figure 23, is displayed on the user terminal 30.

[0120] Figure 23 shows an example of the display of the implementation effect output screen in the third embodiment. In Figure 23, the same reference numerals are used for parts that are the same as in Figure 18, and their descriptions are omitted. The implementation effect output screen 570 shown in Figure 23 further includes a reduction cost display area 573. The reduction cost display area 573 is an area that displays the reduction cost calculated in step S410 of Figure 22.

[0121] As described above, according to the third embodiment, the user can economically understand the effects of introducing the business application.

[0122] Furthermore, the third embodiment may be combined with the second embodiment.

[0123] Next, a fourth embodiment will be described. The differences between the fourth embodiment and the above embodiments will be described. Therefore, points that are not specifically mentioned may be the same as in the above embodiments.

[0124] In each of the embodiments described above, an example was given of calculating the number of records in the application database of each business application from the operation log. However, if each application database is accessible from the outside, the acquisition unit 12 may acquire the number of records in each application database by directly counting them.

[0125] In this case, the acquisition unit 12 responds to the request from the calculation unit 13 in step S314 of Figure 15 to acquire the number of records for each target application, and acquires the number of records from the application DB of that target application. The acquisition unit 12 then transmits the acquired number of records to the calculation unit 13 (S318).

[0126] As described above, the same effects as those of each of the above embodiments can be obtained in the fourth embodiment as well.

[0127] Next, a fifth embodiment will be described. The differences between the fifth embodiment and the above embodiments will be described. Therefore, points not specifically mentioned may be the same as in the above embodiments.

[0128] In the fifth embodiment, we will describe an example in which the user terminal 30 displays various screens via a web browser, and the implementation effect calculation device 10 functions as a web server that executes web applications. In the fifth embodiment, the business application is also a web application.

[0129] Figure 24 shows an example of the functional configuration of a user terminal 30 in the fifth embodiment. In Figure 24, the user terminal 30 has a web browser 31. The web browser 31 is a general-purpose web browser and includes a browser engine 311, a scripting engine 312, and a network engine 313.

[0130] Browser engine 311 interprets HTML (HyperText Markup Language) data and CSS (Cascading Style Sheets) data that make up a web page and displays the web page.

[0131] Script engine 312 executes scripts that make up a web page (for example, JavaScript®).

[0132] The network engine 313 sends HTTP requests and receives HTTP responses.

[0133] Figure 25 is a sequence diagram illustrating an example of the processing procedure for calculating the effectiveness of introducing a business application in the fifth embodiment. The sequence diagram in Figure 25 shows the processing procedure corresponding to steps S311 onwards in the sequence diagram of Figure 15. However, steps S501 to S508 in Figure 25 show the processing procedure for displaying the effectiveness calculation instruction screen 560 (Figure 17), which is not explicitly shown in Figure 15.

[0134] In response to a user's instruction to display the implementation effect calculation instruction screen 560 (Figure 17), the browser engine 311 inputs the URL associated with the instruction, which is the destination of the HTTP request to the implementation effect calculation device 10, into the network engine 313 (S501). The network engine 313 sends an HTTP request to the URL (S502). The URL may, for example, be registered in the bookmarks of the web browser 31, associated with a menu on a menu screen provided by the implementation effect calculation device 10, or directly entered by the user.

[0135] The output unit 14 of the implementation effect calculation device 10 generates an HTTP response containing web content data (HTML data, CSS data, and scripts (hereinafter referred to as "JS")) in response to the HTTP request (S503). Subsequently, the output unit 14 sends the HTTP response to the user terminal 30 (S504).

[0136] The Web content data in question is an example of Web content data for displaying a first Web page (implementation effect calculation instruction screen 560 (Figure 17)) that accepts input of data (start date and end date) used to calculate a predetermined period (target period) for which the implementation effect is to be calculated, and an instruction to execute the calculation of the implementation effect, and a second Web page (implementation effect output screen 570 (Figure 18, etc.)) that displays the calculated implementation effect, and includes at least a script that performs a process of sending the data entered on the first Web page to the implementation effect calculation device 10, and a process of displaying the second Web page that displays the implementation effect.

[0137] Next, when the network engine 313 of the user terminal 30 receives the HTTP response sent in step S504, it inputs the HTML data, CSS data, and JS contained in the HTTP response into the browser engine 311 (S505). The browser engine 311 inputs the JS input from the network engine 313 into the script engine 312 (S506). The script engine 312 loads the JS (S507) and requests the browser engine 311 to update the screen (S508). The screen update includes displaying a new screen.

[0138] Here, the HTTP response generated in step S503 may include the filename of the JS file rather than the actual JS file itself. In this case, in step S507, the script engine 312 accesses the file based on the filename and downloads the JS file. This method involves loading the JS file as an external file.

[0139] Furthermore, the Web content data includes a first Web page (implementation effect calculation instruction screen 560 (Figure 17)) that accepts input of data (start date and end date) used to calculate a predetermined period (target period) for calculating the implementation effect and instructions to execute the calculation of the implementation effect, and a second Web page (implementation effect output screen 570 (Figure 18, etc.)) that displays the calculated implementation effect, and a script that at least executes the process of sending the data entered on the first Web page to the implementation effect calculation device 10 and the process of displaying the second Web page that displays the implementation effect. The script included in the Web content data includes not only JS written directly in HTML, but also JS that is downloaded by receiving access based on the file name using a method of loading JS as an external file.

[0140] Next, the browser engine 311 displays a web page as the implementation effect calculation instruction screen 560 (Figure 17) based on the HTML data and CSS data (S509).

[0141] When the user enters the start and end dates of the target period on the implementation effect calculation instruction screen 560 (Figure 17) (S510) and clicks the calculate button 563 (S511), the browser engine 311 notifies the script engine 312 of the click of the calculate button 563 (S512). The script engine 312, in response to the notification from the browser engine 311, executes JS (S513) and inputs a request to calculate the implementation effect to the network engine 313 (S514). This calculation request includes the target period information (start date and end date). The network engine 313 sends an HTTP request as this calculation request to the implementation effect calculation device 10 (S515). This HTTP request is an example of the HTTP request that was sent when JS was executed on the user terminal 30 and includes the data entered on the implementation effect calculation instruction screen 560 (Figure 17) displayed on the user terminal 30 based on the Web content data.

[0142] When the calculation unit 13 of the implementation effect calculation device 10 receives the HTPT request, it obtains the start date and end date from the HTPT request (S516). Subsequently, the calculation unit 13 calculates the implementation effect for each business application to be used for calculating the implementation effect during the target period from the start date to the end date (S517). The calculation method may be the same as in each of the embodiments described above.

[0143] Next, the output unit 14 (an example of a communication unit) generates an HTTP response containing JSON (JavaScript® Object Notation) describing the calculated implementation effects, in order for the user terminal 30 to execute JS and display the implementation effect output screen 570 (Figure 18, etc.) (S518). Subsequently, the output unit 14 sends the HTTP response to the user terminal 30 (S519).

[0144] When the network engine 313 of the user terminal 30 receives the HTTP response, it inputs the implementation effects contained in the HTTP response to the script engine 312 (S520). The script engine 312 executes JS (S521) and requests the browser engine 311 to update the displayed content of the web page (S522). Based on the HTML data and CSS data obtained in step S505, the browser engine 311 displays the updated screen, the implementation effects output screen 570 (Figure 18, etc.) (S523).

[0145] As described above, in the fifth embodiment, the implementation effect calculation instruction screen 560 (Figure 17) and the implementation effect output screen 570 (Figure 18, etc.), and the execution of processing corresponding to operations on each of these screens are realized by a single-page application. Specifically, when displaying the implementation effect calculation instruction screen 560, the user terminal 30 is delivered not just Web content data for displaying the implementation effect calculation instruction screen 560, but Web content data for displaying both the implementation effect calculation instruction screen 560 and the implementation effect output screen 570, which includes JavaScript that executes processing such as screen transitions corresponding to operations on the implementation effect calculation instruction screen 560. Therefore, since the screen transition from the implementation effect calculation instruction screen 560 to the implementation effect output screen 570 is executed by JavaScript, the user terminal 30 does not need to download the Web content data for the implementation effect output screen 570. As a result, it is possible to solve technical issues such as improving the display speed of the implementation effect output screen 570 and reducing the communication load during screen transitions.

[0146] Next, a sixth embodiment will be described. The differences between the sixth embodiment and the fifth embodiment will be described. Therefore, points not specifically mentioned may be the same as in the fifth embodiment.

[0147] Figure 26 is a sequence diagram illustrating an example of the processing procedure for calculating the effects of introducing a business application in the sixth embodiment.

[0148] Steps S601 to S616 are almost identical to steps S501 to S516 in Figure 25. However, as will be clear from the following description, the JS (script) included in the HTTP response generated in step S603 differs from that of the fifth embodiment.

[0149] In step S617, the calculation unit 13 acquires the target operation log set and configuration information. The configuration information is the pre-implementation time and post-implementation time for each business application that is the target of the implementation effect calculation, which are stored in the configuration information storage unit 15. The target operation log set is the set of operation logs used to calculate the implementation effect during the target period. When calculating the implementation effect in the same manner as in the first embodiment, the target operation log set is the set of operation logs for the business application whose implementation effect is to be calculated, where the "operation type" is "add record" and the date and time fall within the target period. When calculating the implementation effect in the same manner as in the second embodiment, the target operation log set is the set of operation logs for the business application whose implementation effect is to be calculated, where the "operation type" is "add record" or "delete record" and the date and time fall within the target period.

[0150] Next, the output unit 14 generates an HTTP response containing the target operation log set and configuration information in JSON format (S618). Subsequently, the output unit 14 sends the HTTP response to the user terminal 30 (S619).

[0151] When the network engine 313 of the user terminal 30 receives the HTTP response, it inputs the target operation log set and configuration information contained in the HTTP response into the script engine 312 (S620).

[0152] Next, the script engine 312 calculates the implementation effect based on the target operation log set and configuration information by executing the processes associated with the input of the target operation log set and configuration information in JS (S621). The method for calculating the implementation effect based on the target operation log set and configuration information is the same as in each of the embodiments described above.

[0153] Thus, the sixth embodiment differs from the fifth embodiment in that the JS also includes the process of calculating the implementation effect, and the script engine 312 functions as the calculation unit 13. In other words, the calculation of the implementation effect can also be performed by the user terminal 30.

[0154] Next, the script engine 312 executes the process associated with the completion of the calculation of the implementation effect in JS (S622), and requests the browser engine 311 to update the display content of the web page, which is the implementation effect calculation instruction screen 560 (Figure 17) (S623). Based on the HTML data and CSS data obtained in step S605, the browser engine 311 displays the updated web page, which is the implementation effect output screen 570 (Figure 18, etc.) (S624).

[0155] In the above example, the target operation log set is shown as being included in the HTTP response. However, the number of records for each business application, calculated in step S405 of Figure 19 or step S405a of Figure 20, may also be included in the HTTP response. In this case, no processing is required in JS to calculate the number of records.

[0156] As described above, according to the sixth embodiment, the user terminal 30 can perform the calculation of the implementation effect. As a result, for example, the processing load of the implementation effect calculation device 10 can be reduced. Furthermore, when displaying the implementation effect calculation instruction screen 560, the user terminal 30 is delivered not only as Web content data for displaying the implementation effect calculation instruction screen 560, but also as Web content data for displaying both the implementation effect calculation instruction screen 560 and the implementation effect output screen 570, and which includes JavaScript that performs processing such as screen transitions in response to operations on the implementation effect calculation instruction screen 560. Therefore, since the screen transition from the implementation effect calculation instruction screen 560 to the implementation effect output screen 570 is performed by JavaScript, the user terminal 30 does not need to download the Web content data for the implementation effect output screen 570. As a result, it is possible to solve technical issues such as improving the display speed of the implementation effect output screen 570 and reducing the communication load during screen transitions.

[0157] Furthermore, the implementation effect calculation device 10 is not limited to a general-purpose server computer. The implementation effect calculation device 10 may be, for example, an output device such as a PJ (Projector), IWB (Interactive White Board: an electronic whiteboard with the ability to communicate with each other), or digital signage, a HUD (Head Up Display) device, industrial machinery, imaging devices, sound collection devices, medical equipment, networked home appliances, a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet device, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, or a desktop PC.

[0158] Furthermore, each function of each of the above embodiments can be realized by one or more processing circuits. Hereinafter, "processing circuit" as used herein includes processors programmed to execute each function by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), and conventional circuit modules designed to execute the functions described above.

[0159] Furthermore, the apparatus described in each of the above embodiments represents only one of several computing environments for carrying out the embodiments disclosed herein.

[0160] In one embodiment, the implementation effect calculation device 10 includes multiple computing devices, such as a server cluster. These computing devices are configured to communicate with each other via any type of communication link, including networks and shared memory, and perform the processing disclosed herein. Similarly, the application creation device 20 may include multiple computing devices configured to communicate with each other.

[0161] Although embodiments of the present invention have been described in detail above, the present invention is not limited to these specific embodiments, and various modifications and changes are possible within the scope of the gist of the present invention as described in the claims.

[0162] Examples of the present invention are as follows:

[0163] <1> An information processing device that executes an application that accepts data input for each predetermined task, A receiving unit that receives input of a first value for calculating the difference between the time required when the user performs the predetermined task using the application and the time required when the user performs the predetermined task without using the application, or a second value indicating the difference. A calculation unit that calculates the reduction effect when the application is used during a predetermined period based on the usage history of the application used for the predetermined work during the predetermined period and the first value, or the reduction effect based on the usage history and the second value, An output unit that outputs a screen to a terminal displaying the reduction effect calculated by the calculation unit, An information processing device characterized by having the following features.

[0164] <2> The system includes an acquisition unit that references history information recorded in response to operations on the application and acquires the usage history of the application over a predetermined period. Characterized by <1> The information processing device described.

[0165] <3> The receiving unit further receives the predetermined period specified by the user. Characterized by <1> or <2> The information processing device described.

[0166] <4> The reception unit receives input of the first value or the second value for each of the multiple applications. The calculation unit calculates the sum of the reduction effects for each of the multiple applications, The output unit causes the terminal to output a screen displaying the sum of the reduction effects. Characterized by <1> ~ <3> Any of the information processing devices described above.

[0167] <5> The output unit causes the terminal to output a screen displaying the reduction effect for each application. Characterized by <4> The information processing device described.

[0168] <6> The time required when a user performs the aforementioned predetermined task using the aforementioned application is the time required to input the aforementioned data for each of the aforementioned predetermined tasks. Characterized by <1> ~ <5> Any of the information processing devices described above.

[0169] <7> The aforementioned usage history is the number of records registered by the application, The calculation unit calculates a third value obtained by multiplying the previous difference by the number of records as the reduction effect. Characterized by <1> ~ <6> Any of the information processing devices described above.

[0170] <8> The calculation unit calculates a fourth value obtained by multiplying the third value by labor costs as the reduction effect. Characterized by <7> The information processing device described.

[0171] <9> An information processing device that runs an application that accepts data input for each predetermined task, A reception procedure for receiving input of a first value, or a second value indicating the difference, for calculating the difference between the time required when the user performs the predetermined task using the application and the time required when the user performs the predetermined task without using the application. A calculation procedure for calculating the reduction effect when the application is used during a predetermined period, based on the usage history of the application used for the predetermined work during the predetermined period and the first value, or the reduction effect based on the usage history and the second value, An output procedure that causes a terminal to output a screen displaying the reduction effect calculated in the above calculation procedure, An information processing method characterized by performing the following.

[0172] <10> An information processing device that runs an application that accepts data input for each predetermined task, A reception procedure for receiving input of a first value, or a second value indicating the difference, for calculating the difference between the time required when the user performs the predetermined task using the application and the time required when the user performs the predetermined task without using the application. A calculation procedure for calculating the reduction effect when the application is used during a predetermined period, based on the usage history of the application used for the predetermined work during the predetermined period and the first value, or the reduction effect based on the usage history and the second value, An output procedure that causes a terminal to output a screen displaying the reduction effect calculated in the above calculation procedure, A program to execute.

[0173] <11> An information processing device that runs a web application, A receiving unit that accepts input of a first value for calculating the difference between the time required when a user performs a predetermined task using the Web application and the time required when the user performs the predetermined task without using the Web application, or a second value indicating the difference. A storage unit that stores the usage history of the predetermined tasks performed by the user using the Web application, including at least the date, A calculation unit that calculates the reduction effect when the aforementioned web application is used over a predetermined period, A communication unit that communicates with the terminal, It has, Web content data for displaying a first web page that accepts input of data used to calculate the predetermined period and an instruction to perform the calculation of the reduction effect, and a second web page that displays the calculated reduction effect, the web content data includes a script that performs at least the following: a process of sending the data entered on the first web page to the information processing device, and a process of displaying the second web page that displays the reduction effect, and the web content data is transmitted to the terminal. When the communication unit receives an HTTP request transmitted by the execution of the script on the terminal, which includes the data entered on a first web page displayed on the terminal based on the web content data, the calculation unit calculates the reduction effect over a predetermined period calculated based on the received data, based on the usage history including dates that match the predetermined period, and the first value or the second value. The communication unit includes the calculated reduction effect in the HTTP response, which is a response to the HTTP request, and sends it to the terminal in order for the terminal to execute the script and display the second web page. An information processing device characterized by the following:

[0174] <12> An information processing device that runs a web application, A receiving unit that accepts input of a first value for calculating the difference between the time required when a user performs a predetermined task using the Web application and the time required when the user performs the predetermined task without using the Web application, or a second value indicating the difference. A storage unit that stores the usage history of the predetermined tasks performed by the user using the Web application, including at least the date, A communication unit that communicates with the terminal, It has, Web content data for displaying a first web page that accepts input of data used to calculate the predetermined period and an instruction to execute the calculation of the reduction effect when the web application is used during the predetermined period, and a second web page that displays the calculated reduction effect, the web content data includes a script that performs at least the following: a process of sending the data entered on the first web page to the information processing device, a process of calculating the reduction effect, and a process of displaying the second web page that displays the reduction effect, and the web content data is sent to the terminal. When the communication unit receives an HTTP request sent by the execution of the script on the terminal, which includes the data entered on the first web page displayed on the terminal based on the web content data, the communication unit sends an HTTP response to the terminal including a usage history including a date that matches the predetermined period, and the first value or the second value, in order for the terminal to execute the script, calculate the reduction effect, and display the second web page. An information processing device characterized by the following: [Explanation of Symbols]

[0175] 10. Device for calculating the effect of introduction 11 Reception Department 12 Acquisition Department 13 Calculation Section 14 Output section 15. Configuration Information Storage Unit 20 App creation devices 21 App Development Department 22 App Operation Section 23. Application Information Storage Unit 24 Record storage unit 25 Operation log storage unit 30 User terminals 31 Web Browsers 311 Browser Engines 312 Script Engine 313 Network Engine [Prior art documents] [Patent Documents]

[0176] [Patent Document 1] Japanese Patent Publication No. 2005-031910

Claims

1. An information processing device that executes an application that accepts data input for each predetermined task, A receiving unit that receives input of a first value for calculating the difference between the time required when the user performs the predetermined task using the application and the time required when the user performs the predetermined task without using the application, or a second value indicating the difference. A calculation unit that calculates the reduction effect when the application is used during a predetermined period based on the usage history of the application used for the predetermined work during the predetermined period and the first value, or the reduction effect based on the usage history and the second value, An output unit that outputs a screen to a terminal displaying the reduction effect calculated by the calculation unit, An information processing device characterized by having the following features.

2. The system includes an acquisition unit that references history information recorded in response to operations on the application and acquires the usage history of the application for a predetermined period. The information processing apparatus according to claim 1, characterized in that it is a product of the present invention.

3. The receiving unit further receives the predetermined period specified by the user. The information processing apparatus according to claim 1, characterized in that it is a product of the present invention.

4. The reception unit receives input of the first value or the second value for each of the multiple applications. The calculation unit calculates the sum of the reduction effects for each of the multiple applications, The output unit causes the terminal to output a screen displaying the sum of the reduction effects. The information processing apparatus according to claim 1, characterized in that it is a product of the present invention.

5. The output unit causes the terminal to output a screen displaying the reduction effect for each application. The information processing apparatus according to feature 4.

6. The time required when a user performs the aforementioned predetermined task using the aforementioned application is the time required to input the aforementioned data for each of the aforementioned predetermined tasks. The information processing apparatus according to claim 1, characterized in that it is a product of the present invention.

7. The aforementioned usage history is the number of records registered by the application, The calculation unit calculates a third value obtained by multiplying the previous difference by the number of records as the reduction effect. The information processing apparatus according to claim 1, characterized in that it is a product of the present invention.

8. The calculation unit calculates a fourth value obtained by multiplying the third value by labor costs as the reduction effect. The information processing apparatus according to claim 7, characterized in that it is a product of the same name.

9. An information processing device that runs an application that accepts data input for each predetermined task, A reception procedure for receiving input of a first value, or a second value indicating the difference, for calculating the difference between the time required when the user performs the predetermined task using the application and the time required when the user performs the predetermined task without using the application. A calculation procedure for calculating the reduction effect when the application is used during a predetermined period, based on the usage history of the application used for the predetermined work during the predetermined period and the first value, or the reduction effect based on the usage history and the second value, An output procedure that causes a terminal to output a screen displaying the reduction effect calculated in the above calculation procedure, An information processing method characterized by performing the following.

10. An information processing device that runs an application that accepts data input for each predetermined task, A reception procedure for receiving input of a first value, or a second value indicating the difference, for calculating the difference between the time required when the user performs the predetermined task using the application and the time required when the user performs the predetermined task without using the application. A calculation procedure for calculating the reduction effect when the application is used during a predetermined period, based on the usage history of the application used for the predetermined work during the predetermined period and the first value, or the reduction effect based on the usage history and the second value, An output procedure that causes a terminal to output a screen displaying the reduction effect calculated in the above calculation procedure, A program to execute.

11. An information processing device that executes a web application, A receiving unit that receives input of a first value for calculating the difference between the time required when a user performs a predetermined task using the Web application and the time required when the user performs the predetermined task without using the Web application, or a second value indicating the difference. A storage unit that stores the usage history of the user performing the predetermined task using the Web application, including at least the date, A calculation unit that calculates the reduction effect when the aforementioned web application is used over a predetermined period, A communication unit that communicates with the terminal, It has, Web content data for displaying a first web page that accepts input of data used to calculate the predetermined period and an instruction to execute the calculation of the reduction effect, and a second web page that displays the calculated reduction effect, the web content data includes a script that performs at least the following: a process of causing the data entered on the first web page to be transmitted to the information processing device, and a process of displaying the second web page that displays the reduction effect, and the web content data is transmitted to the terminal. When the communication unit receives an HTTP request transmitted by the execution of the script on the terminal, which includes the data entered on the first web page displayed on the terminal based on the web content data, the calculation unit calculates the reduction effect during the predetermined period calculated based on the received data, based on the usage history including the date that matches the predetermined period, and the first value or the second value. The communication unit includes the calculated reduction effect in the HTTP response, which is a response to the HTTP request, and sends it to the terminal in order for the terminal to execute the script and display the second web page. An information processing device characterized by the following:

12. An information processing device that executes a web application, A receiving unit that receives input of a first value for calculating the difference between the time required when a user performs a predetermined task using the Web application and the time required when the user performs the predetermined task without using the Web application, or a second value indicating the difference. A storage unit that stores the usage history of the user performing the predetermined task using the Web application, including at least the date, A communication unit that communicates with the terminal, It has, Web content data for displaying a first web page that accepts input of data used to calculate the predetermined period and an execution instruction to calculate the reduction effect when the web application is used during the predetermined period, and a second web page that displays the calculated reduction effect, wherein the web content data includes a script that performs at least the following: a process of sending the data entered on the first web page to the information processing device, a process of calculating the reduction effect, and a process of displaying the second web page that displays the reduction effect, and the web content data is transmitted to the terminal. When the communication unit receives an HTTP request transmitted by the execution of the script on the terminal, which includes the data entered on the first web page displayed on the terminal based on the web content data, the communication unit sends an HTTP response to the terminal including a usage history including a date that matches the predetermined period and the first value or the second value, in order to calculate the reduction effect by having the terminal execute the script and display the second web page. An information processing device characterized by the following:

Images