JP2002312506A - Method and system for distributing application program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide the distribution service of an application program. SOLUTION: This system is constituted of an application management side server 1 for providing a service, user side terminal 2 and local server 3 for using the service, and a network 4. The server 1 is provided with a program library 11 for storing program information, a registered used data base 12 for storing registered user information, a program preparing part 13 for performing the maintenance of a program in the program library 11, a program executing part 14 for executing simulation on the server, a program executing part 14 for executing simulation on the server, an authentication charging part 15 for settling the charge of a program to be purchased by the user, and a communication processing part 16 for executing processing by transmitting and receiving the program, data, and command or the like with the user side terminal 2.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a system for distributing application programs via a network.

[0002]

2. Description of the Related Art In the process industry, it is common to introduce a computer system into the operation management of a plant, and the operation management and control are advanced and advanced. When performing plant operation management, not only monitor measurement data taken directly from measuring equipment, but also, for example, use the measurement data to calculate operation management of plant equipment performance, material balance, heat balance, etc. It is not uncommon to monitor these values after they have gone there. In order to perform such operation monitoring, an application program corresponding to the purpose is required.

[0003] The above-mentioned application programs are developed by the user on their own or created by requesting external programmers or the like, and thus require time and effort. Recently,
An application program is distributed from a server to a terminal device via a network (Japanese Patent Application Laid-Open No. H11-316602).

[0004]

In the above prior art, a program for managing the operation of a plant can be obtained via a network. However, since the operation management of the plant must have a high-level control function, there is a problem that the function of the terminal device is required to be high-level.

An object of the present invention is to provide a method and system for distributing an application program using a terminal device which does not require high functions in view of the problems of the prior art.

[0006]

SUMMARY OF THE INVENTION The present invention, which achieves the above object, comprises a server for managing an application program, a user terminal, and a local server for plant operation management, which are connected by a network. In the method of distributing a desired application program from the server to the local server, the server acquires process data from the local server via the user terminal when simulating the application program to be distributed.

Further, the server is characterized in that, when there is a distribution request of the application program from the user terminal after the simulation, the server distributes the application program to the local server and bills the user terminal.

[0008]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a plurality of embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a configuration diagram schematically showing a first embodiment of the present invention. The first embodiment includes a server 1 on the application management side that provides a service, a terminal 2 and a local server 3 on the user side that uses the service, and a network 4.
The local server 3 is connected to a plant 6 via a distributed control device (DCS) 5. Although FIG. 1 shows only one set of the terminal 2 and the local server 3, a plurality of terminals and local servers may be provided. The server 1, the terminal 2, and the local server 3 are connected to each other via a network 4.

FIG. 2 shows the configuration of the server. Server 1
A program library 11 for storing program information, a registered user database 12 for storing registered user information, a program creating unit 13 for maintaining programs in the program library 11, and a program for executing a simulation on a server A program execution unit 14, an authentication and billing unit 15 for specifying a registered user and settling a fee for a program purchased by the user, and a program, data, and commands transmitted and received between the user-side terminal 2 and the like. A communication processing unit 16 that performs processing is provided.

FIG. 3 shows the configuration of the terminal. The terminal 2 receives the program distributed from the server 1 and the local server 3
A storage device 21 for storing process data and the like transmitted from the server 1, a program creating unit 22 for maintaining a program in the program database 31 of the local server 3, and a program between the server 1 and the local server 3. And a communication processing unit 23 for transmitting and receiving data, commands, and the like to perform processing.

FIG. 4 shows the configuration of the local server. The local server 3 includes a program database 31 for storing programs, a process data database 32 for storing process data, a program execution unit 33, and a communication processing unit 3 for performing communication processing between the terminal 2
4 is provided.

Server 1, terminal 2, and local server 3
Are the display units 17, 24, 35 and the input unit 18,
25 and 36 are provided. For example, the display unit has a CRT display, and various calculation results on a computer,
The contents of various databases can be displayed. The input unit includes all or a part of input operation devices such as a keyboard, a mouse, and a touch panel, and receives various instructions to the computer.

FIG. 5 shows the data structure of each database in the server. The program library 11 stores program information. The program information includes a program name, a service classification, a keyword, a program specification, a program file, a program fee, and the like, and is configured for each program.

The registered user database 12 stores registered user information. The registered user information includes a name, an address, a user ID, a password, an access history to a server computer, and the like, and is configured for each user.

FIG. 6 shows a data structure of each database in the local server. Program database 3
1 stores program information. The program information includes a program name of a program executed on the local server, a program file, and the like, and is configured for each program.

The process database 32 stores process data information. The process data information includes a tag name, a process data value, a unit, a time, and the like, and is configured for each process data.

The operation of this embodiment will be described in detail with reference to the flowcharts of FIGS. 7 and 8 and the sequence diagram of FIG. In the flowchart of FIG. 7, first, the application developer develops a program (step S701), and registers the developed program in the program library 12 of the server 1 (step S702).

Next, the operation of the authentication / billing unit 15 of the server 1 will be described with reference to the flowchart of FIG. First, the authentication and billing unit 15 waits for a connection request from the user terminal 2 (step S801). When the user accesses the server 1 from the terminal 2 via the network 4 and makes a connection request to the server, user authentication is performed (step S80).
2). The server causes the user ID and password to be input, searches the registered user database 12, and determines whether or not the user is a registered user (step S803). If the user is not a registered user, an error message is displayed on the terminal computer (step S891), and the connection is released (step S807). On the other hand, if the user is a registered user, the process is executed based on a request from the user (step S804). The processing content of step S804 will be described later.

Then, when the process is completed, it is determined whether or not a billing process is necessary (step S80).
5). If a billing process is required, a billing process is executed (step S806), and the connection is released (step S80).
7). If the billing process is unnecessary, the connection is immediately released without performing the billing process (step S807).

The payment means based on the user ID, the password, and the billing process is determined in advance by the application management side and the user side. That is, the user ID and password are distributed to the user as confirmation that the settlement means has been determined.

Referring to FIG. 9, step S804 in FIG.
The details of the processing will be described. FIG. 9 shows an example in which a program for estimating the concentration at the outlet of the reactor is required, and explains the procedure for obtaining the program.

When it is confirmed that the user is an authorized user, the storage of the access history is started (step S901), and the provided service is displayed (step S902). The display of the provided service is such that the user can select a service by displaying a menu screen as shown in FIG. 10, for example. The provided service name indicates a service classification registered as program information of the program library 11. The service classification includes a soft sensor provision service, a process analysis service, a model identification support service, and the like.

When the user selects the soft sensor providing service 1001 from the provided services (step S
903), the server displays the program name that can be provided and allows the user to select it (step S904). For example, the selection screen of a program to be provided is a program menu shown in FIG.

As the provided program name, a program name registered as program information of the program library 12 is displayed. The program name should be such that the contents of the program can be understood. For example, there are a reactor outlet concentration estimation program, a pipe concentration estimation program, and a temperature estimation program.

If the user selects the reactor outlet concentration estimation program 1101 from the provided programs (step S905), the server displays the specifications of the program on a screen as shown in FIG. For example, the specification of the reactor outlet concentration estimation program includes definitions of the type of reactor, temperature distribution, reaction formula, reaction rate, reaction rate constant, and the like.

After the user confirms the program specifications, the server displays an input screen for program setting items as shown in FIG. 13 (step S906), and prompts the user to input.
The program setting items need to be determined in advance by the user among the items included in the program specifications. For example, there are a reactor volume, a reaction order, and a reaction rate constant.

When the user inputs program setting items (step S907), the server displays a process data input screen as shown in FIG. 14 (step S90).
8) Ask the user to input. The user requests necessary process data from the local server (step S90).
9), the local server acquires necessary information from the process data database 32 in response to the request (step S910), and displays it on the terminal (step S911).
The user inputs process data from the displayed information to the server (step S912).

Here, from step S908 to step S908
The operation of 912 will be described in more detail with reference to the flowcharts of FIGS. 16 shows the operation of the server, FIG. 17 shows the operation of the terminal, and FIG. 18 shows the operation of the local server.

When the server requests the terminal to input process data (steps S1601 and S1701),
The terminal requests the local server to display the process data (steps S1702 and S1801). In order to acquire the process data from the database 32, the local server requests the terminal to input a process data search condition (steps S1802 and S1703). As a method for inputting search conditions, the local server displays a screen as shown in FIG.
02, a search condition such as time 1903 is input (steps S1704 and S1803). For example, as a search condition, the tag FIC003 is input as 1 hour from 10:00 on January 1, 2001.

The local server searches for process data according to the input search conditions (step S1804), and displays the search results on the terminal (steps S1805 and S17).
05). As a display method of the search result, a screen as shown in FIG. 20 is displayed, and for example, the process data is displayed every other minute for one hour. The terminal looks at the displayed process data and inputs necessary data to the server (steps S1706 and S1602). In the terminal, until the process data requested by the server is completely input (step S
1707), Steps S1702 to S170
Repeat 6.

When the server has the necessary information for the reactor outlet concentration estimation program, the server executes a simulation in the program execution unit 14 (step S913). The result of the simulation is transmitted to the terminal (step S9).
14). The execution result is displayed on a screen example as shown in FIG. 15, and the simulation execution conditions and the like are also displayed.

The user evaluates the program based on the result of the simulation (step S91).
5). If it is determined that the simulated program is necessary, the server requests the server to distribute the program (step S916). The server distributes the program in response to the distribution request (step S91).
7). The distributed program is stored in the storage device on the terminal (step S918), and when the distribution is completed, the terminal transmits a distribution end signal to the server (step S91).
9). The server that has received the distribution end signal ends the storage of the access history (step S920).

The user installs the distributed program on the local server (Step S921). The installed program is executed after the user sets various setting items.

According to the present embodiment, when distributing an application program from a server to a local server, the server simulates the program and provides the result after confirming the result to the terminal. During this simulation, the terminal reads the process data requested by the server from the local server and provides it to the server,
It is not necessary for the terminal to own the process data and the like, and the server and the local server need only be mediated, so that a high-performance computer device required for the local server is not required.

Next, a second embodiment of the present invention will be described with reference to the drawings. The configuration of the second embodiment is the same as that shown in FIG. The configurations of the server 1, the terminal 2, and the local server 3 are the same as those shown in FIGS. Hereinafter, description will be made focusing on the processing content of step S804 (FIG. 8), which is an operation part different from the first embodiment.

FIG. 21 shows the contents of the processing in step S804 in the second embodiment. Here, the procedure of obtaining the reactor outlet concentration estimating program in a required example is described.

When the user is confirmed as an authorized user, the storage of the access history is started (step S2401), and the provided service is displayed (step S2402). When displaying the provided service, for example, by displaying a screen as shown in FIG. 22, it is possible to allow the user to select a service and to search for a program.

If the user selects the program search 2101 (step S2403), the server displays a program search screen and prompts the user to input search conditions such as keywords (step S2404). The search condition input screen of the program is, for example, as shown in FIG. 23, and a keyword is input.

When the user inputs the density 2201 as a search condition (step S2405), the server searches the program library 11 for a program that matches the search condition. As a search result, a display screen as shown in FIG. 24 is displayed, and a program name including the keyword “density” is displayed, and the user is made to select (step S2406).

As a method of displaying the search results, it is possible to simply display, as the program information in the program library 11, one that matches the keyword registered in advance. However, the registered user information in the registered user database 12 and the past From the access history or the like, a program that is often used by the user may be preferentially displayed.

When the user selects the reactor outlet concentration estimation program 2301 from the search results (step S
2407), Step S2407 for subsequent operations
Steps S2423 to S2423 are the same as steps S905 to S921 in the first embodiment.

According to the second embodiment, when the user does not know the program name he / she wants to provide, the target program is searched and provided from the keyword or the past history, so that it is convenient to use.

[0043]

According to the present invention, a user can easily obtain a required application program by distributing it from a server without taking time and effort for developing the application program.

[Brief description of the drawings]

FIG. 1 is a configuration diagram schematically showing an embodiment of the present invention.

FIG. 2 is an internal configuration diagram of a server according to one embodiment.

FIG. 3 is an internal configuration diagram of a terminal according to one embodiment.

FIG. 4 is an internal configuration diagram of a local server according to one embodiment.

FIG. 5 is a data configuration diagram of a database in a server.

FIG. 6 is a data configuration diagram of a database in a local server.

FIG. 7 is a flowchart showing a procedure for registering an application program in a program library according to one embodiment.

FIG. 8 is a flowchart showing an operation procedure of an authentication and billing unit of the server according to one embodiment.

FIG. 9 is a sequence diagram showing a procedure for distributing an application program according to one embodiment.

FIG. 10 is an explanatory diagram showing a screen example of a method for selecting a provided service.

FIG. 11 is an explanatory view showing a screen example of a method of selecting a provided program.

FIG. 12 is an explanatory diagram showing an example of a display screen of a program specification of a provided program.

FIG. 13 is an explanatory diagram showing an example of an input screen of a program setting item of a provided program.

FIG. 14 is an explanatory diagram showing an example of an input screen of process data of a provided program.

FIG. 15 is an explanatory diagram showing a display screen example of a simulation execution result of a provided program.

FIG. 16 is a flowchart showing an example of an operation procedure of a server when acquiring process data.

FIG. 17 is a flowchart showing an example of the operation procedure of the terminal when acquiring process data.

FIG. 18 is a flowchart showing an example of the operation procedure of the local server when acquiring process data.

FIG. 19 is an explanatory diagram showing an example of an input screen for search conditions for process data.

FIG. 20 is an explanatory diagram showing an example of a display screen of a search result of process data.

FIG. 21 is a sequence diagram showing a distribution procedure of an application program in the second embodiment.

FIG. 22 is an explanatory diagram showing a screen example of a method for selecting a provided service in the second embodiment.

FIG. 23 is an explanatory diagram showing an example of an input screen for a search condition of a provided program in the second embodiment.

FIG. 24 is an explanatory diagram showing an example of a display screen of a search result of a provided program in the second embodiment.

[Description of Signs] 1 ... server, 2 ... terminal, 3 ... local server, 4 ... network, 5 ... distributed control device, 6 ... plant, 11 ...
Program library, 12 registered user database, 13 program creation unit, 14 program execution unit, 15 authentication charging unit, 16 communication processing unit, 17 display unit, 18 input unit, 21 storage unit, 22 unit Program creation unit, 23 communication processing unit, 24 display unit, 25 input unit, 31 program database, 32 process data database, 33 program execution unit, 34 communication processing unit, 35 display unit, 36 ... Input section.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Katsuyuki Suzuki, Inventor 7-2-1, Omika-cho, Hitachi City, Ibaraki Pref. Hitachi, Ltd. Power and Electric Development Laboratory (72) Inventor Katsumi Hanashima Katsumi, Kawasaki, Kanagawa Prefecture 890 Kashimada Industrial Systems Division, Hitachi, Ltd. (72) Inventor Kazuhiko Okamoto 890 Kashimada, Saitama-ku, Kawasaki-shi, Kanagawa Prefecture F-term, Industrial Systems Division, Hitachi, Ltd. 5B076 BB06 FB05 FC10

Claims (5)

[Claims] 1. A server that manages an application program, a user terminal, and a local server that performs plant operation management are connected via a network, and a desired application program is distributed from the server to the local server in response to a request from the user terminal. The method for distributing an application program, wherein the server acquires process data from the local server via the user terminal when simulating the application program to be distributed. 2. The server according to claim 1, wherein the server distributes the application program to the local server and charges the user terminal when the distribution of the application program is requested from the user terminal after the simulation. Characteristic application program distribution method. 3. The terminal according to claim 1, wherein the terminal inputs a search condition for searching for an application program, and the server searches for a corresponding application program based on the search condition. Application program delivery method. 4. A system in which a server that manages a plurality of application programs, a user terminal, and a local server that performs operation management of a plant are connected via a network, and an application program that runs on the local server is distributed from the server. Manages application programs,
Means for performing maintenance, means for selecting an application program based on specifications requested from the user terminal, means for executing a simulation based on plant data on a local server, a database for registering user information, distribution The user terminal evaluates a simulation result of the application program, requests program distribution, and receives a result of the billing process from a server. Means, and means for communicating via a network, wherein the local server is a database for storing application programs and plant data, means for executing the application programs, Ri out means delivery system of the application program, characterized in that, and having a means for communicating over a network. 5. The application program according to claim 4, wherein the application program has a keyword corresponding to a function of the application program, and further includes means for selecting an application program based on a keyword from the user terminal. Delivery system.