Application management system, application management method, and program

Abstract

An application management system (10) comprises: a storage unit (100) that stores a plurality of templates relating to application settings, the templates being respectively associated a plurality of use cases; a construction unit (102) that constructs a usage environment of an application, on the basis of a template corresponding to a use case based on a user input from among the templates, and a parameter based on the user input; and an execution unit (103) that executes the application on the basis of the usage environment of the application constructed by the construction unit (102).

Description

Application management system, application management method and program

[0001] The present disclosure relates to an application management system, an application management method, and a program.

[0002] In recent years, application usage environments have been constructed on external servers and provided to users. For example, cloud servers provide applications that users can use regardless of location, time, device, etc. In such applications, if users can customize the applications, it becomes possible to provide applications that are more suited to the user's requirements.

[0003] Patent Document 1 discloses a software market system that allows even users without specialized knowledge to easily customize the software. According to the software market system of Patent Document 1, a user can easily check the behavior of the software when customized by changing parameters by operating a user terminal.

[0004] JP 2015-005242 A

[0005] However, in the software market system of Patent Document 1, the user has to change various parameters and check the operation by himself, which causes a problem that the user has to work a lot when customizing.

[0006] In view of the above circumstances, an object of the present disclosure is to provide an application management system, an application management method, and a program that can provide applications that meet user requirements without increasing the user's workload.

[0007] In order to achieve the above object, the application management system according to the present disclosure includes: a storage means for storing a plurality of templates relating to application settings, each template corresponding to a respective one of a plurality of use cases; a construction means for constructing an application usage environment based on a template among the templates corresponding to a use case based on user input and parameters based on the user input; and an execution means for executing the application based on the application usage environment constructed by the construction means.

[0008] According to the present disclosure, it is possible to provide an application that meets the user's requirements without increasing the user's workload.

[0009] FIG. 1 is a diagram showing the overall configuration of an application management system according to an embodiment of the present disclosure. FIG. 2 is a diagram showing an example of a use case selection screen displayed on a user terminal according to an embodiment of the present disclosure. FIG. 3 is a diagram showing an example of a parameter input screen displayed on a user terminal according to an embodiment of the present disclosure. FIG. 4 is a diagram showing the functional configuration of an application management system according to an embodiment of the present disclosure. FIG. 5 is a diagram showing data stored in a memory unit of an application management system according to an embodiment of the present disclosure. FIG. 6 is a diagram showing an example of a fee unit price table stored in a memory unit of an application management system according to an embodiment of the present disclosure. FIG. 7 is a diagram showing an example of a hardware configuration of an application management system according to an embodiment of the present disclosure.

[0010] Hereinafter, an application management system according to an embodiment of the present disclosure will be described with reference to the drawings. In each drawing, the same or equivalent parts are denoted by the same reference numerals.

[0011] (Embodiment) An application management system 10 according to an embodiment will be described with reference to FIG. 1 . The application management system 10 constructs a usage environment for one or more applications related to a device 30 and provides one or more applications to a user. More specifically, when a user operates a user terminal 20 to input a usage case for the application and parameters related to the application, the application management system 10 constructs a usage environment for the application based on the usage case and parameters input by the user and provides the application to the user. The user can use the application by accessing the application management system 10 via the user terminal 20. The application management system 10 is an example of an application management system according to the present disclosure.

[0012] The application management system 10 includes a database server 11, an application server 12, and a web server 13. The application management system 10 may include, for example, a single server computer that realizes the functions of the database server 11, the application server 12, and the web server 13. Alternatively, for example, the application management system 10 may include multiple server computers, each of which realizes the functions of the database server 11, the application server 12, and the web server 13. For simplicity's sake, unless otherwise specified, the application management system 10 will be assumed to be realized by a single server computer below.

[0013] The application management system 10, the user terminal 20, and the device 30 are communicatively connected to a network NT. The application management system 10 communicates with the user terminal 20 and the device 30 via the network NT. The network NT is, for example, the Internet. Alternatively, the network NT may be a local network provided at a production site. When the network NT is the Internet, the application management system 10 is realized by one or more server computers provided, for example, on a cloud.

[0014] The database server 11 is a database server that manages data related to applications, and in particular manages templates and a fee unit price table, which will be described later.

[0015] The application server 12 executes internal processes among the processes to be executed by the application management system 10, excluding processes related to the interface with the user terminal 20 and the device 30. The interface-related processes are executed by the web server 13. The application server 12 accesses the database server 11 as needed. The application server 12 particularly executes processes for constructing an application usage environment and executes internal processes for the constructed application. Furthermore, the application server 12 acquires data acquired by the web server 13 from the user terminal 20 and the device 30 as needed. Furthermore, the application server 12 outputs data to be output to the user terminal 20 and the device 30 to the web server 13 as needed.

[0016] The web server 13 executes processing related to the interface with the user terminal 20 and the device 30. The web server 13 provides, for example, an interface by way of a web page and an API (Application Programming Interface) that enables the user terminal 20 and the device 30 to access the application management system 10. Data acquired by the web server 13 from the user terminal 20 and the device 30 is output to the application server 12 as needed, and data output by the application server 12 to the web server 13 is output to the user terminal 20 and the device 30 as needed.

[0017] In this way, the database server 11 manages data related to the application, the application server 12 executes internal processing, and the web server 13 executes processing related to the interface, thereby realizing each function of the application management system 10.

[0018] The user terminal 20 is a terminal device owned by a user who uses an application provided by the application management system 10. The user terminal 20 includes at least a display device for displaying a screen and an input device for accepting user input. The user terminal 20 is, for example, a personal computer installed at the user's workplace or a smartphone carried by the user. The user operates the user terminal 20 to input an application use case, for example, on a use case selection screen 21 shown in FIG. 2, and input parameters on a parameter input screen 24 shown in FIG. 3. The screens shown in FIGS. 2 and 3 are provided by the web server 13 in response to the user terminal 20 accessing the application management system 10 via the network NT.

[0019] The user can notify the application management system 10 of a use case by checking a check box 22 and pressing a confirm button 23 on a use case selection screen 21 shown in Fig. 2. Similarly, the user can notify the application management system 10 of a parameter by inputting a parameter in a parameter input box 25 on a parameter input screen 24 shown in Fig. 3 and pressing a confirm button 26.

[0020] The device 30 is a device related to an application provided by the application management system 10. The device 30 is, for example, a programmable logic controller installed at a production site. For example, when the application management system 10 creates a usage environment for an application that visualizes information about the device 30 and provides the environment to a user, the device 30 periodically or in response to a request from the application management system 10 transmits information about itself to the application management system 10 via the network NT. The device 30 is an example of a device according to the present disclosure.

[0021] The functional configuration of the application management system 10 will be described with reference to Figure 4. The application management system 10 includes a storage unit 100, an interface unit 101, a construction unit 102, an execution unit 103, a fee calculation unit 104, and a template management unit 105. Each functional component shown in Figure 4 is realized by a database server 11, an application server 12, and a web server 13.

[0022] As shown in FIG. 5 , the storage unit 100 stores a plurality of templates TP and a fee unit price table RT. Each template TP and fee unit price table RT is created in advance, for example, by an administrator of the application management system 10. However, as will be described later, a user can change, add, or delete templates TP as needed using the template management unit 105. The storage unit 100 also stores data generated when the construction unit 102 (described later) constructs an application usage environment and data generated when the execution unit 103 executes an application, as needed. The storage unit 100 is realized, for example, by the database server 11. The storage unit 100 is an example of a storage means according to the present disclosure.

[0023] Each template TP is used when the construction unit 102 (described later) constructs an application usage environment. Each template TP is a template related to application settings, such as which applications to construct and how to construct each application. Each template TP is associated with a respective one of multiple use cases. For example, one template TP is associated with a use case called "history management of project files installed in a device," while another template TP is associated with a use case called "visualization of device information." Each template TP includes information related to the settings of one or more applications because multiple applications may be required depending on the use case. For example, in the use case called "visualization of device information," multiple applications may be envisioned, such as an application that simply displays device information numerically and an application that displays device information graphically. In such use cases, a user can simplify the effort of constructing a usage environment for multiple applications simply by selecting a use case.

[0024] The fee unit price table RT is a table that associates use cases and parameters with fee unit prices, as shown in Fig. 6. This fee unit price table RT makes it possible to identify a fee unit price from the use case and parameters entered by the user.

[0025] Referring again to Figure 4, the interface unit 101 communicates with the user terminal 20 and the device 30 via the network NT. In particular, the interface unit 101 receives data including use cases and parameters input by the user from the user terminal 20, and transmits to the user terminal 20 data necessary for constructing a screen to be output to the user terminal 20. The data necessary for constructing a screen to be output to the user terminal 20 is, for example, information that needs to be presented to the user and data of a web page that represents the screen on which the information is presented. The interface unit 101 is realized, for example, by the web server 13.

[0026] The construction unit 102 constructs a usage environment for one or more applications based on a template TP corresponding to a usage case input by a user via the user terminal 20, among the templates TP stored in the storage unit 100, and parameters input by the user via the user terminal 20. The construction unit 102 stores data generated during the construction of the usage environment in the storage unit 100 as necessary. For example, the construction unit 102 stores in the storage unit 100 the usage case and parameters input by the user, setting information required for executing each application, and the like. The construction unit 102 is realized by, for example, the application server 12. The construction unit 102 is an example of a construction means according to the present disclosure.

[0027] The execution unit 103 executes the application based on the application usage environment constructed by the construction unit 102. The execution unit 103 communicates with the interface unit 101 as necessary. For example, the execution unit 103 communicates with the interface unit 101 to execute processing in response to a user input. Furthermore, for example, the execution unit 103 communicates with the interface unit 101 to output data required to construct a screen showing the execution result to the user terminal 20. The execution unit 103 stores data generated during the execution of the application in the storage unit 100 as necessary. For example, the execution unit 103 stores information acquired from the device 30 in the storage unit 100. The execution unit 103 is realized by, for example, the application server 12. The execution unit 103 is an example of an execution means according to the present disclosure.

[0028] The fee calculation unit 104 refers to the fee unit price table RT stored in the memory unit 100 and calculates the usage fee for the application executed by the execution unit 103 based on the fee unit price corresponding to the use case and parameters related to the application. The fee calculation unit 104 also causes the interface unit 101 to display a screen presenting the calculated usage fee on the user terminal 20. For example, when a trial period of a certain period is set when an application is provided, the fee calculation unit 104 can present to the user an estimate of the usage fee after the trial period has expired based on the fee unit price. The fee calculation unit 104 is realized, for example, by the application server 12. The fee calculation unit 104 is an example of a fee calculation means according to the present disclosure.

[0029] The template management unit 105 can change, add, or delete templates TP stored in the storage unit 100 based on input by the user to the user terminal 20. This allows the user to flexibly customize applications according to their needs while using existing templates TP. In particular, the user can change, add, or delete templates TP without having special authority related to the application management system 10. The template management unit 105 is realized by, for example, the application server 12 and the database server 11. The template management unit 105 is an example of a template management means according to the present disclosure.

[0030] An example of the hardware configuration of the application management system 10 will be described with reference to Fig. 7. As described above, the application management system 10 shown in Fig. 7 is realized by, for example, a server computer. Note that when the application management system 10 is realized by multiple server computers, each server computer is realized by the hardware configuration shown in Fig. 7.

[0031] The application management system 10 includes a processor 1001 , a memory 1002 , an interface 1003 , and a secondary storage device 1004 , which are connected to each other via a bus 1000 .

[0032] The processor 1001 is, for example, a CPU (Central Processing Unit). The processor 1001 loads an operating program stored in a secondary storage device 1004 into a memory 1002 and executes the program, thereby realizing each function of the application management system 10.

[0033] The memory 1002 is a main storage device configured, for example, by a RAM (Random Access Memory). The memory 1002 stores the operating program that the processor 1001 reads from the secondary storage device 1004. The memory 1002 also functions as a working memory when the processor 1001 executes the operating program.

[0034] The interface 1003 is an I / O (Input / Output) interface such as a serial port, a USB (Universal Serial Bus) port, or a network interface.

[0035] The secondary storage device 1004 is, for example, a flash memory, a hard disk drive (HDD), or a solid state drive (SSD). The secondary storage device 1004 stores the operating programs executed by the processor 1001.

[0036] An example of the operation of application management by the application management system 10 will be described with reference to Figure 8. Application management here includes building an application usage environment, executing the application, and estimating the application usage fee. Also, here, a trial period is assumed to last for a certain period from the start of application usage, and no usage fee is to be paid before the application is executed. The operation shown in Figure 8 is initiated, for example, when a user operates the user terminal 20 to access the application management system 10 and inputs the application usage case and parameters.

[0037] The construction unit 102 of the application management system 10 identifies the use case and parameters input by the user operating the user terminal 20 via the interface unit 101 of the application management system 10 (step S1).

[0038] The construction unit 102 identifies a template TP corresponding to the use case identified in step S1 from the templates TP stored in the storage unit 100 (step S2).

[0039] The construction unit 102 constructs an application usage environment based on the template TP identified in step S2 and the parameters identified in step S1 (step S3).

[0040] The execution unit 103 of the application management system 10 executes the application based on the usage environment established in step S3 (step S4).

[0041] The fee calculation unit 104 of the application management system 10 refers to the fee unit price table RT stored in the storage unit 100, and determines the fee unit price based on the use case and parameters determined in step S1 (step S5).

[0042] The fee calculation unit 104 estimates the usage fee based on the fee unit price determined in step S5 (step S6).

[0043] The interface unit 101 transmits to the user terminal 20 data necessary for constructing a screen that presents the execution result by the execution unit 103 and the usage fee estimate by the fee calculation unit 104 to the user, thereby presenting the execution result and the usage fee estimate to the user (step S7). The application management system 10 then terminates its application management operation. Thereafter, steps S4 to S7 can be executed as appropriate, for example, in response to access from the user terminal 20.

[0044] The above describes the application management system 10 according to an embodiment. According to the application management system 10, an application usage environment is constructed based on a template TP corresponding to a use case input by a user. Therefore, the user can be provided with an application that matches the use case from the beginning, reducing the effort required to change parameters and check operation. In other words, according to the application management system 10, an application that meets the user's requirements can be provided without increasing the user's effort.

[0045] Furthermore, with the application management system 10, a user can receive an application that corresponds to a use case simply by selecting a necessary use case from multiple use cases presented on the use case selection screen 21 shown in Fig. 2. Therefore, the user does not need to consider for himself which application to select for the use case.

[0046] Furthermore, the application management system 10 allows users to quickly receive an application and obtain a usage fee estimate simply by entering their usage case and parameters, allowing users to easily try out an application.

[0047] (Modification) In the application management system 10 according to the embodiment, parameters may be automatically determined based on a setting file related to the device 30, instead of the user directly inputting the parameters.

[0048] For example, as shown in FIG. 9 , the application management system 10 further includes a parameter determination unit 106. The parameter determination unit 106 reads a setting file related to the device 30 and automatically determines parameters based on the read setting file. The setting file related to the device 30 is, for example, a project file that is embedded in the device 30 and managed by an engineering tool. The parameter determination unit 106 may read the project file embedded in the device 30 by communicating with the device 30 via the interface unit 101 based on an input operation by a user on the user terminal 20. Alternatively, the user may copy the project file to the user terminal 20 and transmit it to the application management system 10, and the parameter determination unit 106 may read the project file via the interface unit 101. In either case, the parameter determination unit 106 reads the project file and automatically determines parameters based on the user's input. The parameter determination unit 106 is an example of a parameter determination means according to the present disclosure.

[0049] In the embodiment, the applications provided by the application management system 10 are applications related to the devices 30, but the applications provided by the application management system 10 do not necessarily have to be applications related to the devices 30. For example, the applications may be general-purpose applications such as schedule management applications or chat applications.

[0050] 7, the application management system 10 includes a secondary storage device 1004. However, the present invention is not limited to this, and the secondary storage device 1004 may be provided outside the application management system 10, and the application management system 10 and the secondary storage device 1004 may be connected via an interface 1003. In this configuration, removable media such as a USB flash drive or a memory card may also be used as the secondary storage device 1004.

[0051] 7, the application management system 10 may be configured with a dedicated circuit using an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), etc. In the hardware configuration shown in FIG. 7, some of the functions of the application management system 10 may be realized by a dedicated circuit connected to the interface 1003, for example.

[0052] The programs used in the application management system 10 can be stored and distributed on computer-readable recording media such as CD-ROMs (Compact Disc Read Only Memory), DVDs (Digital Versatile Discs), USB flash drives, memory cards, HDDs, etc. By installing such programs on a specific or general-purpose computer, the computer can function as the application management system 10.

[0053] Furthermore, the above-mentioned program may be stored in a storage device owned by another server on the Internet, and the program may be downloaded from that server.

[0054] The present disclosure allows various embodiments and modifications without departing from the broad spirit and scope of the present disclosure. Furthermore, the above-described embodiments are intended to explain the present disclosure and do not limit the scope of the present disclosure. In other words, the scope of the present disclosure is defined by the claims, not the embodiments. Various modifications made within the scope of the claims and the meaning of equivalent disclosures are considered to be within the scope of the present disclosure.

[0055] 10 Application management system, 11 Database server, 12 Application server, 13 Web server, 20 User terminal, 21 Use case selection screen, 22 Check box, 23 Decision button, 24 Parameter input screen, 25 Parameter input box, 26 Decision button, 30 Equipment, 100 Storage unit, 101 Interface unit, 102 Construction unit, 103 Execution unit, 104 Fee calculation unit, 105 Template management unit, 106 Parameter determination unit, 1000 Bus, 1001 Processor, 1002 Memory, 1003 Interface, 1004 Secondary storage device, NT Network, RT Fee unit price table, TP Template.

Claims

1. An application management system comprising: a storage means for storing a plurality of templates relating to application settings, each template corresponding to a respective one of a plurality of use cases; a construction means for constructing an application usage environment based on a template among the templates corresponding to a use case based on user input and parameters based on the user input; and an execution means for executing the application based on the application usage environment constructed by the construction means.

2. The application management system according to claim 1, wherein each of the templates is a template relating to settings for a plurality of applications, and the construction means constructs a usage environment for the plurality of applications.

3. An application management system as described in claim 1 or 2, wherein the storage means further stores a fee unit price table that associates use cases and parameters with fee unit prices, and further comprises a fee calculation means that refers to the fee unit price table and calculates the usage fee for the application executed by the execution means based on the fee unit price corresponding to the use case and the parameters related to the application.

4. An application management system according to any one of claims 1 to 3, wherein the application includes an application for managing a device, and further comprising parameter determination means for automatically determining the parameters based on a setting file for the device input by the user.

5. The application management system according to any one of claims 1 to 4, further comprising a template management means for changing, adding, or deleting the templates stored in the storage means based on an input from the user.

6. An application management method in which a computer constructs an application usage environment based on a template corresponding to a usage case based on user input and parameters based on the user input, from among a plurality of templates related to application settings, each template corresponding to a usage case based on a plurality of usage cases, and executes the application based on the constructed application usage environment.

7. A program that causes a computer to construct an application usage environment based on a template corresponding to a usage case based on user input and parameters based on the user input, from among a plurality of templates related to application settings, each template corresponding to a usage case based on a plurality of usage cases, and execute the application based on the constructed application usage environment.

Images