Maintenance device and application system

[0074] (first embodiment)

[0075] Figure 1 to Figure 16 It is a figure of 1st Embodiment. figure 1 It is a block diagram of the structure of the application system in the first embodiment. like figure 1 As shown, the application system of this embodiment includes application modules (system management server 100, system DB server 110), and maintenance modules (maintenance server 200, maintenance DB server 210).

[0076] The application module controls (executes) all application functions. The system management server 100 provides one or more application functions based on the operation screen to the terminal devices (the administrator terminal 300 and the operator terminal 400 ) connected via the network N such as the Internet. The system DB server 110 stores systems such as information provided by the system management server 100 to the connected terminal device and information input from the terminal device, and the system management server 100 provides information necessary for application functions. The application functions of the contact center system include data input processing, output processing of input data, analysis processing, retrieval processing, and the like.

[0077] The maintenance module controls (executes) all maintenance functions of one or more operation screens corresponding to the functions provided by the application module. The maintenance server 200 transmits the editing program to the administrator terminal connected via the network N, provides a maintenance environment based on the screen editor, and executes the reception of maintenance result information and the generation of screen information in the maintenance work using the screen editor. The maintenance DB server 210 stores all screen information of each operation screen, screen information of each layout version of the operation screen, and information required for maintenance operations using the screen editor.

[0078] The application system of the present embodiment communicates using, for example, the HTTP protocol implemented by HTML, XHTML, or other technologies, and transmits the data of the operation screen to each terminal device of the operator terminal 400 and the administrator terminal 300 . The browser (display control unit 331 ) preinstalled in each terminal device displays the operation screen on the terminal device by reading the screen data. like figure 1 As shown, the administrator terminal 300 includes a communication control unit 310 that controls communication with the application system via the network N; a storage unit (main storage device, auxiliary storage device, etc.) 320; a control unit (CPU) 330; a display device 340, and a mouse , keyboard and other input devices 350 . In addition, the operator terminal 400 is the same as the administrator terminal 300, and may have a voice input device, a call function, and the like, as necessary, in addition to the above-mentioned components.

[0079] figure 2 This is an example of a block diagram of the configuration of the application system of the present embodiment. The system management server 100 includes a control unit (CPU) 101 , a communication control unit 102 , and a memory 103 . The system management server 100 includes: an authentication unit 1001 that performs authentication processing using access control information (eg, operator ID and password) input by the operator terminal 400; a screen generation unit 1002 that generates screen information to be transmitted to the operator terminal 400; Various controls (screen display control such as screen transition, reception control such as input data or instruction commands, execution and control of processing performed by various application functions, data transfer to the operator terminal 400 are performed from operation inputs input perpendicular to the terminal 400 . The system control unit 1003 that controls the transmission of data, etc., etc.); and the data processing unit 1004 that performs data input/output control to the system DB server 110 . The control unit (CPU) 101 is in charge of the overall control of the above-mentioned parts, and the screen generation unit 1002 , the system control unit 1003 , and the data processing unit 1004 function as an application control unit of the application system.

[0080] The system DB server 110 stores system management information 111 , screen information 112 , client information 113 , and event information 114 . The system management information 111 stores access control information used for authentication processing, user information using the application system, and the like.

[0081] image 3 An example of the screen information 112 is shown. The screen information 112 includes screen configuration information, screen block information, and item information. The screen configuration information includes the layout version of each operation screen, the block ID, and the display order of the information blocks (or the display position based on the coordinate information in the screen). The screen structure of the operation screen of the present embodiment is divided into a plurality of information blocks, screen items are associated with each information block, and one operation screen includes a plurality of information blocks. The screen block information uses the block ID of the screen configuration information as a key, and includes detailed information such as the block name and block area (block size in the screen) of each information block.

[0082] Each screen item (label, text input box, selection button (radio button), checkbox, pull-down menu, date and time input) displayed on the screen is saved according to the item ID in the item information. /time and date display fields, tables, etc.), and each item is associated with the screen by using the block ID as a key. The item information includes: item ID, item type, block ID, data storage location, label ID, size 1 (height), size 2 (width), display position within the information block (for example, the coordinates of the information block area information). The data storage location is information indicating the storage location in the system DB server 110 for data and the like input through the operation screen. The data storage location is, for example, column information (Column 1 of Table 1) of the data table of the system DB server 110 where the event information 114 is stored. In addition, the label ID is associated with label information (character information) stored in a label master table (not shown).

[0083] Furthermore, in this embodiment, the input screen 1 is composed of a plurality of information blocks, and the information blocks are associated with screen items, but the present invention is not limited to this, and the input screen 1 may not be divided into a plurality of information blocks. , instead using the layout version to associate the screen items contained in each information block with the input screen 1.

[0084] The event information stores input data input from the input screen 1 of each layout version generated from the screen information 112 . like Figure 4 As shown, the event information includes version information and event detailed information corresponding to the event. For example, in the present embodiment, when the operator of the contact center system inputs the reception history of each customer, the data input by the operator through the input screen 1 corresponds to event information.

[0085] Figure 5 This is an example of the input screen 1 generated from the screen information 112 . Figure 5 The illustrated input screen 1 is an operation screen displayed on the operator terminal 400 after the system management server 100 has undergone the authentication process. The contact center system assigns event IDs to inquiries from incoming customers, distinguishes them by event IDs, and inputs and saves the inquiries from customers. Even if it is an inquiry from the same customer, if the content of the inquiry is different, a separate event ID is assigned, and a plurality of event IDs are linked to the same customer. That is, the event ID of the present embodiment is information for identifying input data input through the input screen.

[0086] The event ID is identification information automatically generated by a predetermined algorithm on the system side. The event ID may consist of a character string containing numbers, letters, and the like. For example, the system control unit 1003 of the system management server 100 can automatically generate an event ID according to the received operation instruction of the operator. Furthermore, when new data is input in response to a customer inquiry or the like, the system control unit 1003 may display the generated event ID on the input screen of the operator terminal 400 . At this time, the system control unit 1003 transmits the generated event ID to the operator terminal 400, and the browser 331 of the operator terminal 400 displays the received event ID in the event ID item of the input screen. In addition, when registering the input data (according to the Figure 5 The system control unit 1003 generates an event ID, does not display the event ID on the operator terminal 400, but stores the registered input data in the system DB server 110 in association with the event ID.

[0087] The version information corresponding to the event (the layout version information corresponding to the input data) includes the event ID, the layout version of the input screen 1, and comments (eg, description of the screen). The version information corresponding to the event is information that associates the input data managed by the event ID with the layout version of the input screen 1 in which the input data is input.

[0088] The layout version is information allocated to manage a plurality of screen layouts of one operation screen, and indicates, for example, the maintenance transition (history) of the input screen 1 . For example, if the input screen 1 in use without maintenance work is used, the layout version is "1". Screen 1 is assigned multiple layout versions.

[0089] like Figure 4 As shown, the layout version is associated one-to-one with input data (event information), which is used to manage which layout version of the input screen 1 the input data is associated with, that is, with which screen layout state of the input screen 1 screen corresponding to the project.

[0090] Event details hold various data in a table structure. For example, the event detailed information includes a plurality of columns from column 1 to column N, and one piece of event detailed information is stored for each event ID. Each column is associated with each screen item of the input data, as indicated by event ID (column 1), customer ID (column 2), and status (column 3). Each column of this embodiment is Figure 5 The data storage location of the screen items (input items, selection items, etc.) of each information block shown in the example of .

[0091] like figure 2 As shown, the maintenance server 200 includes a control unit (CPU) 201 , a communication control unit 202 , and a memory 203 . The maintenance server 200 includes: an authentication unit 2001 ; a screen editing control that transmits an editor program of an operation screen related to an application function provided by the system management server 100 to the administrator terminal 300 and controls the editing function executed by the administrator terminal 300 part 2002; a screen information generating part 2003 that receives maintenance information of the operation screen maintained by the operation input on the administrator terminal 300 and generates the screen information; The received maintenance information is reflected in the maintenance information reflection control unit 2005 of the application module. The control unit (CPU) 201 is responsible for the overall control of each of the above-mentioned parts. The screen information generation unit 2003 , the check unit 2004 , the maintenance information reflection control unit 2005 , and the like function as a maintenance control unit of the maintenance module.

[0092]The maintenance DB server 210 stores screen maintenance information 211 , version management information 212 , data storage location information 213 , and temporary registration information 214 .

[0093] like Image 6 As shown, the version management information 213 includes one or more layout versions associated with the input screen 1, and version information such as the application date, application end date, and completion date of each layout version (indicating the operation screen used in the application module). is applicable, and which is the latest layout version). The data storage location information 213 stores storage location information of all screen items of each layout version of the input screen 1 . For example, table fields containing event details and input items associated with each table field.

[0094] The screen maintenance information 212 includes screen information of the latest layout version stored in the screen information of the application module, and also includes screen information of all other layout versions of the input screen 1 . like Figure 7 As shown, the screen maintenance information 212 includes screen configuration information of the latest version "3", version "2", and version "1". The picture block information is the same as the picture block information of the above application module. The item information is also the same as the item information of the above-mentioned application module, each item information is stored according to the item ID, and each layout version item ID is associated with each of all layout versions in the input screen 1 .

[0095] like Figure 7 As shown, screen items common to layout versions are associated with the same item ID. That is, for screen items shared between layout versions, the screen items associated with the current (before change) layout version continue to maintain the association with the layout version after maintenance (after change), and the data storage location is also in the current layout version. The data storage location in . In other words, the relationship between the screen item before the change and the data storage location does not change, and the layout version after the change inherits the screen item associated with the layout version before the change as it is for the common screen items, and is associated with the layout version after the change. Associated.

[0096] Figure 8 Indicates an example of the screen editor. The screen editor provides users with maintenance functions for operating screens. The screen editor supports screen maintenance of the information blocks and screen items of the latest or past layout version of the specified operation screen. The screen editor includes an information block display area D1, a maintenance operation area D2, an item (part) display area D3, and a property area D4.

[0097] The maintenance server 200 transmits an editing program (an editor screen information having a screen editing function) to the connected administrator terminal 300 . The browser 331 of the administrator terminal 300 reads the received editing program and displays it on the display device 340 . The browser 331 performs editing processing of screen items in accordance with an operation instruction from the input device 350 . At this time, the administrator inputs the operation screen to be maintained and the layout version through the screen editor. The maintenance server 200 extracts the screen information (screen configuration information, screen block information, item information) of the corresponding layout version from the screen maintenance information of the maintenance DB server 210 according to the received operation screen selection information (operation screen identification information and layout information). ), and transmits the screen information of the read layout version to the administrator terminal 300 . The browser 331 of the administrator terminal 300 displays the received screen information on the screen editor. The received screen information is stored in the storage unit 320 .

[0098] by Figure 8 The administrator selects the information block (basic information, customer information, product information, inquiry information, etc.) displayed in the information block display area D1. The browser 331 displays the block information selected by the management in the maintenance operation area D2 based on the screen information received from the maintenance server 200 . The administrator can edit the information block displayed in the maintenance operation area D2 such as addition, change, deletion of screen items, and size change of the information block.

[0099] In addition, the administrator can add new information blocks. Figure 8 An example of screen maintenance for adding a new information block to the latest layout version 3 of the input screen 1 (event screen 1) is shown. For example, the administrator selects "information block" in the item area D3, and inserts (drag and drop) the information block 1 in the information block display area, so that the information block can be added to the input screen 1. 1. When the information block 1 is selected in the information block display area D1, the browser 331 displays the display area T1 corresponding to the information block 1 in the maintenance operation area D2. The administrator can expand or reduce the size of the display area T1, or drag and move each item in the item display area D3 within the display area T1, thereby arranging the screen items at any position. Further, by performing text input on the label information and adjusting the size of the configured screen items, a new information block 1 can be created for the input screen 1 . In addition, in the attribute information display area D4, the attribute information (data attribute, font, height, width, position, etc.) of the arranged screen items can be operated.

[0100] The result information of the maintenance operation described above, that is, change information for changing the screen information of the received operation screen, is stored in the storage unit 340 . Changes can be saved in real time for operation input in the screen editor, or after maintenance work is completed.

[0101] After completing the maintenance work on the operation screen using the screen editor, the administrator selects the check button B1 of the screen editor to check, display and confirm the operation screen after maintenance. When the check button B1 is selected, the browser 331 reflects the change information generated by the maintenance work in the screen information of the current layout version. The browser 331 transmits maintenance information including the change information and screen information of the current layout version to the maintenance server 200 .

[0102] The maintenance server 200 saves the selection information of the check button B1 and the received maintenance information as the temporary registration information 214 . The maintenance server 200 generates inspection screen information using the maintenance information stored in the temporary registration information 214 and stores it in the temporary registration information 214 .

[0103] The maintenance server 200 generates an operation screen after maintenance based on the generated inspection screen information, and transmits it to the administrator terminal 300 . The administrator can view the post-maintenance operation screen generated from the inspection screen information transmitted to the administrator terminal 300 .

[0104] After viewing and confirming the operation screen generated from the inspection screen information, the administrator can reflect the operation screen (inspection screen information) after maintenance to the application module by selecting the release button B2. When the release button B2 is selected, the maintenance server 200 refers to the version management information 211 to obtain the serial number "3" of the latest layout version before maintenance. The maintenance server 200 adds 1 to the acquired layout version "3", and assigns a new layout version "4" to the inspection screen information. Then, the maintenance server 200 reflects the screen information of the layout version 4 to the maintenance DB server 210 and the system DB server 110 .

[0105] Specifically, as Figure 9 As shown, the maintenance server 200 adds the layout version 4 for the input screen 1 to the version management information 211 of the maintenance DB server 210 . In addition, when a new screen item is added to the input screen 1 of the added layout version 4, the maintenance server 200 newly assigns a data storage position column corresponding to the added screen item to the data storage position information 213 of the input screen 1, and updates Data storage location information 213 . At this time, the maintenance server 200 associates the data storage location of the added screen item with the column of the data table used in the past layout version of the input screen 1 . That is, even if the layout version is changed, each layout version can be regarded as a data table referenced by the data storage location of the screen item, and can be set as one data table provided in the input screen 1 . Furthermore, as described above, for screen items shared between layout versions, the screen items associated with the previous layout version continue to be associated with the layout version after the change, and the data storage location in the past layout version is stored. The position also continues to be associated with the changed layout version.

[0106] like Figure 10 As shown, the maintenance server 200 reflects each information of the layout version 4 in the screen configuration information, screen block information, and item information of the maintenance DB server 210 , and updates the screen maintenance information 212 .

[0107] Further, the maintenance server 200 rewrites the screen information of the layout version 4 to the screen configuration information and the screen block information of the system DB server 110 , respectively, and updates the screen information 112 . As described above, since the system DB server 110 saves only the latest layout version, when a new layout version of the input screen 1 is generated, the screen information 112 of the previously saved layout version is deleted, and the screen information 112 of the newly updated layout version is saved. . Then, a new item ID corresponding to the newly added screen is assigned to the item information of the screen information 112, and a new column assigned in the data table as the data storage location of the new item ID, and the existing item ID are saved. The associated information remains the same.

[0108] Figure 12 It is a figure which shows the input screen 1 of the layout version "4" displayed on the operator terminal 300. like Figure 12 shown, the input screen 1 of layout version "4" is in Figure 5 In the input screen 1 of the layout version "3" shown, the information block 1 is added between the customer information block B2 and the product information block B3. In addition, the information blocks other than the information block 1, that is, the newly added screen items other than the information block 1, are the screen items shared with the layout version "3", and the data storage location of the shared screen items other than the information block 1 Still the data save location in layout version "3".

[0109] Figure 13 there is Figure 12 An example of input data entered in input screen 1 of layout version "4". Figure 13 The event information of the event ID "C7" input from the input screen 1 shown is associated with the layout version "4" in the version information corresponding to the event, and each screen item of the layout version "4" is stored in the event detailed information input data. At this time, the data input to the screen item associated with the information block 1 is stored in the column newly allocated to the event detailed information. On the other hand, the screen items shared with the layout version "3" are still stored in the column of the data storage location used by the layout version "3".

[0110] Figure 14 This is a flowchart of the flow of the processing (new input processing) of the application system of the present embodiment.

[0111] like Figure 14 As shown, the operator side is connected to the system management server 100 through the operator terminal 400 . The authentication unit 1001 of the system management server 100 performs authentication processing using the access control information received from the operator terminal 400 (S401, S101).

[0112] The system control unit 1003 of the system management server 100 outputs an instruction to generate an operation screen to the screen generation unit 1002 . The screen generation unit 1002 reads out the screen information 112 from the system DB server 110 and generates an operation screen. At this time, the screen generation unit 1002 refers to the version management information 211 of the maintenance DB server 210, checks the applicable date and the latest layout version (S102), and reads the screen information 112 from the system DB server 110 (S103). Further, HTML conversion processing or the like is performed on the read screen information 112 to generate screen data of the input screen 1 that can communicate using HTTP protocols such as HTML or XHTML (S104). The screen generation unit 1002 transmits the generated screen data to the operator terminal 400 (S105). At this time, the system management server 100 may read out the screen information 112 from the system DB server 110 in advance or at a predetermined timing, and store the screen information 112 in the memory 103 . The screen generation unit 1002 generates the input screen 1 with reference to the screen information 112 stored in the memory 103 .

[0113]The operator inputs various data in response to a customer's inquiry or the like according to the input screen 1 displayed on the operator terminal 400 ( S402 ). by choosing Figure 5 The registration button of the button transmits the input data input from the input screen 1 from the operator terminal 400 to the system management server 100 . The input data transmitted from the operator terminal 400 at this time may be layout version information including the input screen 1 .

[0114] The system control unit 1003 outputs the received input data to the data processing unit 1004 . The data processing unit 1004 performs data storage processing on the received input data (S106). Specifically, as described above, an event ID is generated for newly input input data, and the event ID is associated with the layout version of the input screen 1 and stored in version information corresponding to the event. Then, the data processing unit 1004 saves the input data associated with the event ID in the corresponding field in the event detailed information of the data storage location associated with the screen item. Then, the input data received by the system control unit 1003 is temporarily stored in the memory 103, and at a predetermined timing, one or more input data stored in the memory 103 is output to the data processing unit 1004, and the data processing unit 1004 stores the data. deal with.

[0115] Figure 15 It is a flowchart showing the flow of processing (input data read processing) of the application system of the present embodiment.

[0116] The operator can designate an event ID with respect to the input data input on the input screen 1, and can view the content of the customer's inquiry. For example, for a customer's re-inquiry, when the first answer is input, the input data is searched based on the customer name to determine the event ID, and the event can be designated and read. As a method of specifying an event ID, in addition to retrieving by client name, it is also possible to have a processing status (in progress, completed, etc.), read and display the object by specifying the status, and specify the event ID to be referenced.

[0117] For example, the operator searches for the object to be displayed on the screen based on the customer name, and therefore, inputs the identified event ID to Figure 5 The event ID input field of the basic information of the input screen 1 shown is displayed (S403). The browser 331 transmits the input event ID to the system management server 100 . The system control unit 1003 refers to each event version using the received event ID and identifies the layout version of the input screen 1 associated with the input event ID ( S107 ). When the identified layout version is the latest layout version, that is, the latest layout version stored in the system DB server 110 (YES in S108 ), the system control unit 1003 selects the screen stored in the system DB server 110 or the memory 103 from the screen The information 112 reads out screen information (S109). On the other hand, when the identified layout version is not the latest layout version (NO in S108 ), the screen information of the identified layout version is read out with reference to the screen maintenance information 212 of the maintenance DB server 210 and stored in the memory 103 ( S110).

[0118] After reading out the screen information of the layout version associated with the input event ID, the system control unit 1003 outputs the read screen information to the screen generation unit 1002 (S111), and then reads out the event ID from the event detailed information. Determined input data (S112). Next, the system control unit 1003 transmits, to the operator terminal 400, an input screen 1 including the input screen 1 generated from the screen generation unit 1002 based on the association between the layout version and the screen item and the association between the screen item and the storage location of the input data. Input data read from the event detailed information corresponding to each screen item of the screen data. (S113).

[0119] The operator can update various data in accordance with the customer's inquiry or the like from the input screen 1 including the input data called by specifying the event ID ( S404 ). For example, by selecting Figure 5 The registration button of the operator terminal 400 transmits the event ID, layout version and input data from the operator terminal 400 to the system management server 100 . The data processing unit 1004 stores each received information in a column corresponding to the event detailed information specified by the event ID (S114).

[0120] Figure 16 It is a flowchart showing the maintenance process flow of the application system of this embodiment.

[0121] like Figure 16 As shown, the administrator side connects to the maintenance server 200 through the administrator terminal 300 . The authentication unit 2001 of the maintenance server 200 performs authentication processing using the access control information received from the administrator terminal 300 (S301, S201). After the authentication process, the screen editing control unit 2002 transmits an editing program (editing screen information having a screen editing function) to the connected administrator terminal 300 (S202). The browser 331 of the administrator terminal 300 reads the received editing program and displays it on the display device 340 . The browser 331 edits the screen item according to the operation instruction of the operation input device 350, and the screen editing control unit 2002 starts to control the screen editor (S302, S203).

[0122] The administrator performs input through the screen editor of the maintenance operation screen and the layout version screen (S303). The screen editing control unit 2002 reads out the screen information of the corresponding layout version from the screen maintenance information of the maintenance DB server 210 according to the received operation screen selection information (operation screen identification information and layout version) (S204), and transmits it to the administrator terminal 300 (S205).

[0123] When the administrator completes the maintenance work of the operation screen through the screen editor (S304), the administrator selects Figure 5 Check button B1 in the screen editor of . After selecting the check button B1, the browser 331 transmits the maintenance information including the change information and the screen information of the current layout version to the maintenance server 200 (S305).

[0124] The screen editing control unit 2002 receives the selection information of the check button B1 and the maintenance information, and saves the received maintenance information as the temporary registration information 214 . The screen information generation unit 2003 generates inspection screen information using the maintenance information stored in the temporary registration information 210, and stores it in the temporary registration information 214 (S206, S207).

[0125] The inspection unit 2004 performs the same processing as the screen generation unit 1002, generates an operation screen after maintenance based on the inspection screen, and transmits it to the administrator terminal 300 (S208). The administrator can view the post-maintenance operation screen generated based on the inspection screen information and transmitted to the administrator terminal 300 .

[0126] The administrator confirms the operation screen generated based on the inspection screen information, and reflects the operation screen after maintenance to the application module by selecting the release button B2 ( S307 ). When the release button B2 is selected, the maintenance information reflection control unit 2005 refers to the version management information 211 to obtain the serial number of the latest layout version before maintenance. The maintenance information reflection control unit 2005 adds 1 to the acquired layout version, and assigns a new layout version to the inspection screen information.

[0127] The maintenance information reflection control unit 2005 adds the layout version assigned to the input screen 1 to the version management information 211 of the maintenance DB server 210 . When a new screen item is added, the maintenance information reflection control unit 2005 assigns a data storage position column corresponding to the added screen item to the data storage position information 213 of the input screen 1 and updates the data storage position information 213 . In addition, the maintenance information reflection control unit 2005 updates the screen maintenance information 212 by reflecting the screen information of the newly allocated layout version on the screen configuration information, screen block information, and item information of the maintenance DB server 210, respectively.

[0128] Further, the maintenance information reflection control unit 2005 records the screen information of the newly allocated layout version in the screen configuration information and screen block information of the system DB server 110, respectively, and updates the screen information 112 (S209).

[0129] As described above, in the present embodiment, the layout version for identifying the screen layout is assigned to the input screen 1 of the operation screen, and the input screen 1 and the screen item are not directly related, but the screen item is related by the layout version of the input screen 1 . Therefore, when screen maintenance is performed on the input screen 1, a different layout version from the current layout version before maintenance is assigned to the input screen 1. Thus, by performing screen maintenance, the input screen 1 is associated with a plurality of layout versions associated with screen items.

[0130] In the present embodiment, the screen maintenance of the input screen 1 is managed by the layout version, and the layout version and the screen item are associated and managed. Therefore, it is possible to flexibly perform data management (data saving and reading) by keeping the data storage location before the layout version change for common screen items with different layout versions.

[0131] Since the event ID for identifying the input data is associated and stored with the layout version of the input screen 1, the layout version of the input screen 1 can be specified by specifying the event ID, and the screen item associated with each layout version can be specified. In other words, the input data corresponding to the event ID is input, the layout version of the input screen 1 is determined, the input screen 1 of the layout version associated with the event ID can be generated from the layout version, and the data can be read from the data storage location (data readout). Pick). Therefore, the compatibility of the input data with the input screen 1 can be automatically ensured.

[0132] In the present embodiment, a maintenance environment can be realized in which, when maintenance work is performed on the input screen 1, the input screen 1 after the maintenance work and the original input screen 1 before the maintenance work are not separately managed (for example, (Do not generate screen information independent of the screen information included in the original input screen, or do not manage the data storage location corresponding to the original input screen independently), for the input screen 1 changed by the maintenance work, the pre-change, change Each subsequent version is associated with a different version, and the input data and each screen item are managed by each layout version.

[0133] For screen items shared between layout versions, the screen items associated with the previous layout version continue to be associated with the layout version after the change, and similarly, for the data save location, the data save location in the past layout version remains the same as the previous layout version. The association of the changed layout version. Therefore, for the input screen 1, even if the layout version is different, the screen item and the data storage location are the same and do not change. Therefore, for example, it is possible to analyze the specified data in all layout versions, and during the analysis, since the data can be read from the same data storage location, the efficiency of the analysis process can be improved.

[0134] In the above-mentioned embodiment, the example in which the application module (system management server 100, system DB server 110) and the maintenance module (maintenance server 200, maintenance DB server 210) are constituted separately has been described, but the system DB server may be 110 is integrated with the maintenance server 200, or instead of the screen information 112 held by the system management server 110, application control is performed with reference to the screen maintenance information of the maintenance DB server 210. In addition, each part of the maintenance server 200 may be integrated with the system management server 100 .

[0135] In the above-described embodiment, the screen information 112 is divided into screen configuration information and screen block information, but information blocks may be associated as screen items. For example, an item ID can be assigned to the information block and stored in the item information, "basic information block" can be stored in the item type, "XY coordinates (XY coordinates in the operation screen)" can be stored in the position, and "XY coordinates (XY coordinates in the operation screen)" can be stored in the information area. The "XY coordinates (XY coordinates in the operation screen") are stored in the position of the screen item of the block.

[0136] In the above-described embodiment, when returning from layout version 4 to which information block 1 is added to layout version 3 without information block 1, for example, it is performed by deleting information block 1 in the screen item of layout version 4. During the screen maintenance of , the input screen 1 can be returned to the screen item of layout version 3.

[0137]At this time, since the screen maintenance is performed for layout version 4, a new input screen 1 (assignment) of layout version 5 after information block 1 is deleted from layout version 4 is associated with the same screen item as layout version 3 is generated. The different layouts of version 5. In this way, the maintenance history of each stage of the layout version can be made clear. In particular, although the layout version is different, the screen item and the data storage location are shared, so that it is possible to provide easy and efficient screen maintenance management.

[0138] In addition, when the operation screen of the current layout version is returned to the previous layout version during operation, one operation screen may have multiple layout versions as described above, but during operation, the screen in the input work may be Separate operation screens such as the basic input screen and the custom screen are managed. The event screen that is only used for a certain period of time is managed as a custom screen with respect to the base screen, and the custom screen is used during the event, and returns to the basic input screen after the event ends. Provided that it is used as described above, it is not necessary to perform screen maintenance for one operation screen every time before and after the event.

[0139] The application system may also be configured as follows. In accordance with Japanese, Chinese, Korean, English and other languages, each screen information is associated with the layout version and saved, so that when the content of the same database is displayed, the screen layout and the label name of the screen item consistent with the language selected by the user are provided. .