JP6289431B2 - Entrance application management apparatus, control method and program thereof - Google Patents

Description

  The present invention relates to an entrance application management apparatus, a control method thereof, and a program, and more particularly, to a technique for enabling an entrance application to be easily performed.

  In a data center in which network devices and various servers are integrated, it is necessary to maintain a high level of security. In the past, when entering a data center, the person in charge of which company enters, or by e-mail or telephone, the application for entry to the target data center is made individually. Depending on the data center, the contents of information received at the time of application and admission are different, which increases the man-hour for application.

  For example, there is a prior art as disclosed in Patent Document 1 regarding the issue of digitizing an application for entrance. However, in the conventional computerized system related to the admission procedure, an e-mail or a telephone can only be replaced with a Web browser.

  Patent Document 2 is intended to make it possible to apply for simple entry / exit in an emergency in an electronic entry / exit system, and it is possible to make a simple entry application even in an emergency. However, it does not provide a simple admission application even during normal times.

Japanese Patent Laying-Open No. 2005-044206 JP, 2014-099158, A

  In the conventional entrance application system, it is common to enter the person who is going to enter each time and accept the entrance application. Moreover, it was only possible to accept an application for admission to one data center.

  This invention is made | formed in view of the said situation, Comprising: It aims at making it possible to apply for an entrance easily.

In order to achieve the above object, the present invention provides:
A group master in which a group name and a group name related to the group are associated with each other, a person in charge master in which a person in charge name, a data center name that can be used by the person in charge, and a company name to which the person in charge belongs are linked A storage unit for storing
Using the person-in-charge master, an admission control unit that generates a list of data center names stored corresponding to persons in charge who wish to enter,
A communication unit that transmits a list of the generated data center names to a person-in-charge terminal;
With
The admission control unit
When receiving the name of the data center desired to enter from the person in charge terminal,
Using at least the person-in-charge master and the group master,
Extract the name of the person in charge who wants to enter and the name of the person in charge who can enter the data center together with the person in charge.
A field that lists the name of the applicant, a companion person selection field for selecting a person in charge who wishes to enter the data center together from a list of names of persons who can enter the data center together with the person in charge, Generate data for the application screen that includes the entry field corresponding to the name of the data center you wish to enter,
The communication unit is
The generated entry application screen data is transmitted to the person-in-charge terminal.

  According to the present invention, it is possible to easily apply for an entrance.

1 is an overall view of an entrance application management system including an embodiment of the present invention. It is a figure which shows an example of the group master in the said embodiment, a company master, and a person in charge master. It is a figure which shows an example of the entrance application master in the said embodiment. It is a conceptual diagram of the explanatory example 1 of the said embodiment. It is a conceptual diagram of the explanatory example 2 of the said embodiment. It is a conceptual diagram of the explanatory example 3 of the said embodiment. It is a figure which shows the group master in a description example 1, a company master, and a person in charge master. It is a figure which shows the group master in the example 2, a company master, and a person in charge master. It is a figure which shows the group master in the example 3, a company master, and a person in charge master. It is a figure which shows the example of the group master screen of the said embodiment. It is a figure which shows the modification of UI for group registration in FIG. It is a figure which shows the example of the company master screen of the said embodiment. It is a figure which shows the example of the group selection screen in the said embodiment. It is a figure which shows an example of the person in charge master screen of the said embodiment. It is a flowchart which shows the flow of the entrance application in the said embodiment. It is a figure which shows an example of the entrance application screen of the said embodiment. It is a figure which shows an example of the application inquiry list | wrist of the said embodiment.

  Embodiments of the present invention will be described below with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and overlapping description may be simplified or omitted.

<Configuration>
FIG. 1 shows an overall view of an admission application management system including an admission application management apparatus according to this embodiment.
FIG. 1 shows an embodiment in which the present invention is implemented as an entrance management system for managing the entrance of a person into a plurality of data centers. FIG. 1 shows management of the entrance application management apparatus 10 in addition to the entrance application management apparatus 10. An administrator terminal 21 used by a person, a person-in-charge terminal 22 used by a person in charge who wishes to enter the data center, and a plurality of data centers 23-1 to 23-n (n is a positive integer. 23 ”) and a plurality of receiving devices 24-1 to 23-n (hereinafter collectively referred to as“ receiving devices 24 ”) that accept applications to the data centers provided corresponding to each of the plurality of data centers 23. Is written).

  The entrance application management apparatus 10, the administrator terminal 21, the person-in-charge terminal 22, and the reception apparatus 24 are connected via a network (for example, the Internet) to perform communication. Note that the entrance application management apparatus 10 and each of the plurality of data centers 23 do not need to be connected. Further, the entrance application management apparatus 10 may be implemented by a server accommodated in the data center 23.

  The administrator terminal 21, the person-in-charge terminal 22, and the reception device 24 are realized by, for example, a personal computer, a tablet computer, a smartphone, or the like having a general configuration. In this embodiment, since the application layer is implemented by HTTP, it is preferable to include software (such as a browser) that can process HTTP and a display device. There may be one data center 23 instead of a plurality.

  The entrance application management apparatus 10 is realized, for example, by causing a server computer having a general configuration to execute an entrance management software program. The entrance application management apparatus 10 includes a communication unit 11, a storage unit 12, and an entrance control unit 13.

  The communication unit 11 is connected to a network, and communicates with each device such as the administrator terminal 21, the person-in-charge terminal 22, and the data center 23 via the network. For example, it is realized by a network interface card (NIC).

  As illustrated in FIG. 2, the storage unit 12 stores at least the following three table data, “group master”, “company master”, and “person in charge master”. For example, it is realized by a hard disk and database software. The storage unit 12 may store an entrance application master in addition to these three table data.

  Information for identifying a group such as a group name is registered in the group master. The group master also stores which group the group is associated with and the correspondence between the groups.

  In the company master, information identifying the company such as a company name and information accompanying the company such as an address are registered. In addition, the company master includes data that stores which company belongs to which group (or which group belongs to the company) and associates the company with the group.

  In the person-in-charge master, information for identifying the person in charge such as the name of the person in charge and the user ID, and information associated with the person in charge such as a password and contact information are registered. The person-in-charge master stores which data center the person in charge can use, which company the person in charge corresponds to, and the data center that can be used by the person in charge and the company to which the person belongs. Contains data. Here, the person-in-charge master is stored for each group, but one person-in-charge master may be stored in all groups. Further, when a person-in-charge master is created for each group, the same person-in-charge may be stored in person-in-charge masters of a plurality of different groups.

Furthermore, the storage unit 12 may also store an entrance application master as shown in FIG.
For each admission application, the admission application master is required to enter the name of the applicant who applied for admission, the name of the person in charge who will enter with the applicant, the name of the data center that he wants to enter, and the data center. Input items are registered at least in association with each other. The entry application master increases by one entry for each entry application.

  The entrance control unit 13 controls the communication unit 11 and the storage unit 12. For example, a program stored in a hard disk drive is developed in a RAM and executed by a CPU (Central Processing Unit).

<Operation>
Hereinafter, the flow of processing of the admission application method by the admission application management system including the admission application management apparatus of the present embodiment will be described. In order to apply for an entrance, it is necessary for an administrator to register information on the group, company, and person in charge in the entrance application management apparatus 10 using the administrator terminal 21 in advance. First, the flow of information processing when the administrator terminal 21 applies for registration of each information will be described below.

<Group registration>
Here, a group is a set that can be set freely, such as a team spanning a plurality of companies, departments within a company, and a project team, as well as setting one company as one group. Further, groups can be associated with one-to-one, one-to-one, N-to-one, and N-to-N. Furthermore, a group can be related not only by the relationship between a parent and a child but also by connecting three or more groups such as a parent, a child, and a grandchild.

  For example, FIG. 4, FIG. 5, and FIG. 6 show conceptual diagrams depicting the relationship between a group, a company, and a person in charge. FIG. 4 is a conceptual diagram showing a group of a store and two end users of the store. The group names are “A dealer”, “end user B company”, and “end user C company”. “A dealer” and “end user B company” are “A dealer” and “end user C company”. Is transactionally relevant. In this case, the group name “A dealer” is the company name “A dealer”, and employees “A” and “B” belonging to the company name “A dealer” belong to the group. Similarly, the group name “end user B company” is the company name “B company”, and employees “C” and “D” of the company belong to this group. Such a relationship is represented as shown in FIG. 7 by using “group master”, “company master”, and “person in charge master” shown in FIG.

  FIG. 5 is a conceptual diagram showing each group included in a project composed of a plurality of teams in a large-scale company and its cooperating companies. As shown in FIG. 5, the group names include “management team”, “accounting team”, “infrastructure team”, and “subcontractor”. The “Management Team” manages all the groups associated with the subordinates, and the “Accounting Team”, “Infrastructure Team”, and “Subcontractor” are responsible for the application of the “Management Team” person in charge. Person is extracted. “Accounting team” and “Infrastructure team” have a business relationship with “Subcontractor”, and the person in charge of “Accounting team” and “Infrastructure team” is extracted when the person in charge of “Subcontractor” is applied. However, the person in charge of the “management team” of the upper group is not extracted. The “subcontractor” has a business relationship with the “accounting team” and the “infrastructure team”, but the person in charge of the “subcontractor” is responsible for the “accounting team” and “infrastructure team” of the upper group. Are not extracted. Therefore, “Mr. J from Company F” is added to the person in charge of “Accounting Team” and “Infrastructure Team”. Such a relationship can be represented as shown in FIG. 8 using “group master”, “company master”, and “person in charge master” shown in FIG.

  FIG. 6 is a conceptual diagram showing a case where the unit of a group is a company and the company is an affiliated company of a company with which each group has a relationship. In this example, the group names include “parent company”, “subsidiary H”, “subsidiary I”, and “subsidiary company”. Such a relationship can be represented by using “group master”, “company master”, and “person in charge master” shown in FIG. The “parent company” shown in FIG. 6 manages all the groups related to the lower level, and the “parent company” has “subsidiary H”, “subsidiary I” and “grandchild” when the person in charge of the application applies for the admission. The person in charge of “company” is extracted. “Subsidiary H” and “Subsidiary I” are transactionally related to “Parent company”, but when the person in charge of “Subsidiary H” and “Subsidiary I” applies for admission, Not extracted. When the person in charge of “Subsidiary H” applies for the admission, the person in charge of the “subsidiary company” of the related subordinate group is extracted. Since it is not associated with the “company”, the person in charge of the “subsidiary company” is not extracted. In addition, “subsidiary company” has a business relationship with “subsidiary H”, but the person in charge of “subsidiary company” does not extract the person in charge of “subsidiary H” of the superior group.

  In this way, a person in charge can be managed by association between a group and the group without being bound by an existing company or organization. However, it has been explained that subordinate groups can extract the person in charge of all groups, and those in charge of the upper group cannot be extracted. However, only the subordinate group that is one level lower can be extracted, or the upper group that is one level higher can be extracted. The extraction level may be changed.

  To perform group registration, the administrator terminal 21 first transmits a group master screen request to the entrance application management apparatus 10 via the network. Next, when the communication unit 11 receives a group master screen request from the administrator terminal 21, the entrance control unit 13 of the entrance application management apparatus 10 receives group master screen data based on the group master stored in the storage unit 12. The group master screen data is transmitted to the administrator terminal 21 using the communication unit 11.

FIG. 10 shows an example of the group master screen.
The group master screen is a user interface for performing operations such as displaying, inputting, and changing group master information. The operations include group registration (new creation) and group change (registration content change). The group master screen in FIG. 10 includes at least a “group name” for identifying a group and a “related group” indicating a group related to the group.

  In the example of FIG. 10, when group registration is performed using the group master screen, the top line is used. The top line is not filled in. In the “Group name” field, enter the group name, and in “Related group”, select the related group name from the list of registered group names. Has a column for selecting. A plurality of related group names can be selected. Furthermore, change the information for the “Add new button” that sends the group registration application that includes information about the entered group name and the selected related group, and the already registered “Group name” and “Related group”. The group master screen includes items necessary for group registration and change, such as the “Change” button that sends the group change application to be performed. In addition, the user interface for group registration is not limited to the example of FIG. 10, For example, what is shown in FIG. 11 may be used.

  After that, when the admission application management apparatus 10 receives the group registration application from the administrator terminal 21 that has transmitted the data of the group master screen in FIG. 10 to the communication unit 11, the group name associated with the group name included in the received group registration application The name is associated and registered in the group master of the storage unit 12.

<Company registration>
The company information is also registered in the company master of the storage unit 12 in the same manner as the group registration. First, the administrator terminal 21 transmits a company master screen request to the entrance application management apparatus 10 via the network. Next, when the communication unit 11 receives a company master screen request from the administrator terminal 21, the entrance control unit 13 of the entrance application management apparatus 10 receives the company master screen data based on the company master stored in the storage unit 12. And the company master screen data is transmitted to the manager terminal 21 using the communication unit 11.

FIG. 12 shows an example of the company master screen.
The company master screen is a user interface for performing operations such as display, input, and change of company master information. The operation includes registration of company information (new creation) and change of company information (change of registered contents). The company master screen in FIG. 12 includes a “company name” for identifying a company and a “affiliation group” indicating a group to which the company belongs (or a group belonging to the company, which will be omitted below). At least. In addition, there may be an “address” that is the location of the company.

  In the example of FIG. 12, when registering company information using the company master screen, the top line is used. The top line is not filled in. The “Company Name” field is for entering the company name, and “Affiliation Group” is the group name that belongs from the list of already registered group names. Has a column for selecting. Multiple group names can be selected. Furthermore, change the information for the “Add new button” that sends information about the entered company name and the selected group to which the company belongs, and the “Company name” and “Affiliation group” already registered. The company master screen includes information necessary for registration and change of company information, such as a “change” button for sending a company change application. Note that the user interface for registering company information is not limited to the example of FIG.

  After that, when the entrance application management apparatus 10 receives the company registration application to the communication unit 11 from the administrator terminal 21 that has transmitted the data of the company master screen of FIG. 12, the company name and the group to which the company belongs belongs to the received company registration application. The name is associated and registered in the company master of the storage unit 12.

<Registered person in charge>
The person-in-charge information is also registered in the person-in-charge master of the storage unit 12 as in the group registration. First, the administrator terminal 21 transmits a person-in-charge master screen request to the entrance application management apparatus 10 via the network. Next, when the communication unit 11 receives the person-in-charge master screen request from the administrator terminal 21, the entrance control unit 13 of the entrance application management apparatus 10 extracts the group name from the group master stored in the storage unit 12, and Data of a group name list screen for selecting a group name from a list of names is generated, and data of the group name list screen is transmitted to the administrator terminal 21 using the communication unit 11. FIG. 13 is a diagram illustrating an example of the group name list screen. The group name list screen shown in FIG. 13 also serves as a group selection screen capable of selecting any one of the displayed groups.

  After generation and transmission of the group name list screen by the entrance control unit 13, the administrator terminal 21 selects a group name from the group name list screen and transmits the selected group name to the entrance application management apparatus 10 via the network. To do. Then, the entrance control unit 13 of the entrance application management apparatus 10 receives the group name from the administrator terminal 21 by the communication unit 11, and the person-in-charge master screen based on the person-in-charge master and the company master stored in the storage unit 12. The data of the person in charge master screen is transmitted to the manager terminal 21 using the communication unit 11.

FIG. 14 is a diagram illustrating an example of a person-in-charge master screen.
The person-in-charge master screen is a user interface for performing operations such as displaying, inputting, and changing information on the person-in-charge master. The operations include registration of person-in-charge information (new creation) and change of person-in-charge information (change of registered contents). The person-in-charge master screen in FIG. 14 includes a “user ID” for identifying the person in charge, a “name” of the person in charge, a “use data center” indicating a data center that can be used by the person in charge, and the person in charge. Including at least “affiliation company” indicating the company to which the company belongs. In addition, “User level”, “Birth date”, “Face photo”, “Contact” to determine the user's authority such as “Password” of the person in charge, “Furigana” of name, or person in charge or administrator (For example, e-mail address, telephone number, etc.) "or the like.

  In the example of FIG. 14, when registering company information using the person-in-charge master screen, the top row is used. The top row is not filled in, and is stored in the storage unit 12 of the entrance application management apparatus 10 in the column for entering the user ID in “User ID” and in the “Company name”. In the company master, a list of company names registered corresponding to the previously selected group is displayed, and at least a column for selecting a company name to which the person in charge belongs from the company list is included. The “use data center” also includes a column for selecting a name of the data center 23 that the person in charge is permitted to use from a list of names of the plurality of data centers 23. A plurality of data center names that can be used can be selected. In addition, a “add new button” for sending a person registration application including information on the entered user ID, the selected company name, and the selected available data center name, ”,“ Affiliated company ”,“ Usage data center ”The person in charge master screen includes information necessary to register and change the person in charge information, such as the“ Change ”button to send a person in charge change request to change information. . Note that the user interface for registering the person-in-charge information is not limited to the example of FIG.

  The registration to each master will be described below using a specific example.

FIG. 9 is a diagram illustrating an example of each master in which various types of information in the case of an affiliated company having a parent company, two subsidiaries, and a grandchild company illustrated in the conceptual diagram of FIG. 6 are registered.
For example, in the group master screen, “parent company”, which is the group name of the parent company, is entered in “group name”, and “related group” is the group name of the parent company, “parent company” and the two subsidiaries. When a certain “subsidiary H” and “subsidiary I” are selected, various types of information are registered in the group master based on the input selected data. Here, when the two subsidiaries are not yet registered, the related group cannot be associated with each subsidiary on the group master screen. In that case, after the group master registration of each subsequent subsidiary, the association with each subsidiary is performed again. Similarly, on the group master screen, “Subsidiary H” is entered as the group name of one subsidiary, “Subsidiary H”, which is its own group name, and “Grandchild” of the related grandchild company. "Company" is selected and the data is registered in the group master. “Subsidiary I” is input as the group name of the other subsidiary, and “Subsidiary I”, which is its own group name, is selected and registered in “Related Group”. In the group master screen, “Grandchild Company” is entered as the group name of the grandchild company, and “Grandchild Company”, which is its own group name, is selected for “Related Group” and registered in the group master. .

  Next, on the company master screen, “company G”, which is the company name of the parent company, is input as “company name”, and “parent company”, which is the group name of the parent company, is selected as “affiliation group”. Then, various information is registered in the company master based on the selected data. Similarly, the names of companies “H Company” and “Company I” are also entered for each subsidiary, and “Subsidiary H” and “Subsidiary I” are selected and registered in the group to which they belong. In addition, in the company master screen, in the case of a subsidiary company, “Company J” is entered as the company name, but “Osan” is working for the group of “Subsidiary H”. "Subsidiary H" and "Subsidiary" are selected and registered in the company master.

  Next, when registering the person-in-charge master, first, “parent company” which is the group name of the parent company is selected from the group name list screen, and “G001”, “ “Mr. L” is input as “Name”, and “DC4” is selected as “Usage Data Center”. In addition, since “G company” is registered as “affiliation group” in the company master, the “parent company” that is the selected group name is “G company” in the “affiliation company” on the person in charge master screen. Is displayed in such a manner that “Company G” is selected, and various pieces of information are registered in the person-in-charge master whose group name is “Parent company” based on the input selected data. In addition, when “Subsidiary H”, which is the group name of one subsidiary, is selected from the group name list screen, “Subsidiary H”, which is the selected group name, is registered as “Affiliation group” in the company master. Since “H Company” and “J Company” are present, “Company H” and “J Company” are displayed in the “Affiliated Company” on the person-in-charge master screen so that they can be selected. And “Company J” are selected, and various information is registered in the person-in-charge master whose group name is “Subsidiary H” together with the other input-selected data. Registration of other persons in charge and persons in other groups are also registered in the same manner.

  As a result, only the person in charge of the subsidiary and the subsidiary company can select at the time of application for entry to the data center.

  After that, when the admission application management apparatus 10 receives the person-in-charge registration application to the communication unit 11 from the administrator terminal 21 that has transmitted the data on the person-in-charge master screen of FIG. 14, the received user ID, company name, data center name, Are registered in the person-in-charge master of the storage unit 12.

<Application for admission>
Next, the flow of information processing when the person-in-charge terminal 22 used by the person in charge who wishes to enter the building applies for entry will be described below with reference to the flowchart of FIG.

  First, the person-in-charge terminal 22 and its user are authenticated (S101). When an entrance application URL corresponding to the entrance application management apparatus 10 is input to the browser of the person-in-charge terminal 22, the person-in-charge terminal 22 transmits an authentication screen request to the entrance application management apparatus 10. When the entrance control unit 13 of the entrance application management apparatus 10 receives an authentication screen request from the communication unit 11, the entrance control unit 13 reads the authentication screen from the storage unit 12 and transmits the authentication screen to the person-in-charge terminal using the communication unit 11. The authentication screen includes fields for inputting “user ID” and “password”. Furthermore, what is necessary for authentication such as a “send button” for transmitting the input user ID and password is included in the authentication screen. Upon receiving the authentication screen, the person-in-charge terminal 22 displays the received authentication screen on the browser.

  Thereafter, when the entrance application management apparatus 10 receives the “user ID” and the “password” from the person-in-charge terminal 22, the combination of the received user ID and password is stored in an authentication database (not shown) stored in the storage unit 12. Check whether it is stored in As a result of the collation, if it is not confirmed that the user has the right authority, an error screen is transmitted to the person-in-charge terminal 22. If the verification is successful, a data center selection screen is transmitted to the person-in-charge terminal 22.

  Here, the admission application management device 10 stores the data center name registered in the person-in-charge master stored in the storage unit 12 corresponding to the collated person-in-charge user ID (data center name available to the person in charge). ) Is extracted (S102), and a data center selection screen for selecting the data center name to be used this time from the list of data center names available to the extracted person in charge is transmitted to the person in charge terminal 22 (S103). Upon receiving the data center selection screen, the person-in-charge terminal 22 displays the data center selection screen on the browser. When a person in charge selects a data center name desired to be used from the list of available data center names by the person in charge, the person-in-charge terminal 22 transmits the selected entry desired data center name to the entrance application management apparatus 10. . When the admission control unit 13 of the admission application management apparatus 10 receives an admission desired data center name from the person-in-charge terminal 22 to the communication unit 11 (S104), an admission application screen including an input item column corresponding to the admission desired data center name. Is transmitted to the person-in-charge terminal 22 using the communication unit 11 (S105 to S107).

  Here, the generation of the data of the entrance application screen will be described in detail. The entrance control unit 13 of the entrance application management apparatus 10 uses at least the person-in-charge master and group master stored in the storage unit 12 together with the person in charge of the collated user ID (hereinafter referred to as “applicant”). The names of persons in charge who can enter the data center (hereinafter referred to as “accompanying persons in charge”) are extracted. First, the name stored in correspondence with the user ID of the applicant (hereinafter referred to as “name of the applicant”) is extracted from the person-in-charge master. Furthermore, from the person-in-charge master, other than the applicant, the name of the person in charge who is stored corresponding to the group to which the applicant belongs and whose data center name to be entered is stored as the use data center (hereinafter referred to as “application”). The name of the person in charge other than the person "is extracted. Further, a related group name (hereinafter referred to as “applicant related group”) stored in association with the group name to which the applicant belongs is extracted from the group master. Furthermore, from the person-in-charge master stored corresponding to the group name of the related group of the extracted applicant, it is stored in the person-in-charge master of that group, and the desired data center name is stored as the use data center. The name of the person in charge (hereinafter referred to as the “name of person in charge of the applicant”) is extracted. A combination of the extracted “name of the person in charge other than the applicant” and “name of the person in charge related to the applicant” is the “name of person who can be accompanied”. After this extraction, the admission control unit 13 of the admission application management apparatus 10 selects the person who wishes to enter the data center together with the applicant from the column in which the applicant's name is entered and a list of persons in charge who can accompany him / her. Data for an entrance application screen including an accompanying person selection field for selecting a name and an input item field corresponding to the desired data center name is generated. When displaying the name of a person in charge, the company name to which the person in charge belongs may be extracted and displayed using the person in charge master.

  FIG. 16 is a diagram illustrating an example of an entrance application screen. FIG. 16 is a diagram showing an example of an entrance application screen in the case of an affiliated company having a parent company, two subsidiaries, and a grandchild company shown in the conceptual diagram of FIG. 6 and the information registration example of each master in FIG. An example of extracting a person in charge who can be accompanied when the user ID “G001” is authenticated and “DC4” is selected as the use desired data center will be described below with reference to FIG.

  First, the name “Mr. L” stored in correspondence with the user ID “G001” of the applicant is extracted from the person-in-charge master. Further, from the person in charge master, a person other than Mr. L who is stored in correspondence with the group “parent company” to which Mr. L belongs, and whose desired data center name “DC4” is stored as the use data center. Extract the name of. However, although “M” is stored in association with the group “parent company” to which L belongs, “DC 4” is not stored as the usage data center, so there is no subject. Next, from the group master, the related group names “subsidiary H”, “subsidiary I”, “subsidiary company” (“parent company” are their own groups) stored in association with the group name “parent company” to which the applicant belongs. (Omitted). Further, from the person-in-charge master stored in association with the extracted related group “subsidiary H” of the applicant, the data-center name “DC4” desired to enter is stored as the use data center. The names “Mr. N” and “Mr. O” of the stored person in charge are extracted. In addition, the name of the person in charge is extracted from the person-in-charge master stored corresponding to the related group “subsidiary I” of the applicant, but “DC4” is used for “Mr. P” and “Mr. Q”. Since it is not stored as a center, there is no subject in the related group “Subsidiary I”. Further, from the person-in-charge master stored corresponding to the extracted related group “sub-company” of the applicant, the person-in-charge master of that group is stored, and the desired data center name “DC4” is used as the use data center. The stored name “R” of the person in charge is extracted. Therefore, “Mr. N”, “Mr. O”, and “Mr. R” are extracted as the names of persons who can be accompanied.

As another example, an example of extracting a person in charge who can be accompanied when authentication is performed using the user ID “H001” and “DC4” is selected as a use desired data center will be described below.
First, the name “Mr. N” stored in correspondence with the user ID “H001” of the applicant is extracted from the person-in-charge master. Further, from the person in charge master, the person in charge is stored in correspondence with the group “Subsidiary H” other than Mr. N and the data center name “DC4” desired to enter is stored as the use data center. The name of the person. Then, “Mr. O” is extracted as a target person. Next, the related group name “sub-subsidiary company” stored in association with the group name “subsidiary H” to which the applicant belongs is extracted from the group master. Further, from the person-in-charge master stored corresponding to the extracted related group “sub-company” of the applicant, the person-in-charge master of that group is stored, and the desired data center name “DC4” is used as the use data center. The stored name “R” of the person in charge is extracted. Therefore, “Mr. O” and “Mr. R” are extracted as the names of persons in charge who can accompany them.

  Note that the user interface for applying to the data center is not limited to the example of FIG.

  When the person-in-charge terminal 22 receives the data of the entrance application screen, the person-in-charge terminal 22 displays the received entrance application screen on the browser. When the applicant selects and inputs each field, the application application data including the applicant's name and the selected or input data is transmitted to the entrance application management apparatus 10.

  When the admission control unit 13 of the admission application management device 10 receives the admission application data from the person-in-charge terminal to the communication unit 11 (S108), the admission application form corresponding to the admission desired data center name is read from the storage unit 12, Enter the data included in the received admission application data in the corresponding fields (S109) in each column of the format of the read admission application form, and accept the format of the entered admission application form corresponding to the desired data center name It transmits to the apparatus 24 using the communication part 11 (S110).

  Here, the admission control unit 13 of the admission application management device 10 does not transmit the format of the admission application form to the reception device 24 corresponding to the name of the desired data entry center, but the URL to the home page displaying the application inquiry list. You may make it transmit the permission request containing. In this case, when the admission control unit 13 of the admission application management apparatus 10 receives the admission application data from the person-in-charge terminal to the communication unit 11, the admission application master corresponding to the desired data entry name is read from the storage unit 12. The data included in the received entry application data is input to each item of the read entry application master, and the input entry application master is stored in the storage unit 12. Thereafter, the admission control unit 13 of the admission application management device 10 transmits a permission request including a URL to a home page displaying an application inquiry list to the reception device 24 corresponding to the desired data center name using the communication unit 11. . The application inquiry list is a list created by the admission control unit 13 of the admission application management device 10 based on the admission application master stored in the storage unit 12 and lists admission applications to the data center 23. It is. FIG. 17 shows an example of the application inquiry list.

  As shown in FIG. 17, in one entry of the application inquiry list, the name of the data center desired to enter, the name of the applicant described in the admission application data, and the person in charge who wishes to enter the data center together with the applicant. The name and the input item corresponding to the desired data center name are displayed at least in association with each other. In addition, for each entry, items necessary for admission, such as a button for admission permission, are included in the application inquiry list and displayed. The name of the applicant and the name of the person in charge may display the name of the company to which the person in charge belongs.

  The accepting device 24 connects to the homepage of the application inquiry list generated by the admission application management device 10 based on the received URL, gives permission to the admission application using the user interface as shown in FIG. The data center name is transmitted to the entrance application management apparatus 10 together with the data center name. When the admission control unit 13 of the admission application management device 10 receives this permission from the communication unit 11, the admission permission that the admission application to the admission desired data center is permitted to the person in charge terminal 22 using the communication unit 11 is permitted. Send notifications.

  According to the above-described embodiment, the storage unit 12 of the entrance application management apparatus 10 has a “group master”, and collects persons in charge belonging to different companies or divides persons in charge of the same company. Therefore, it is possible to easily apply for an admission with an input of a person who wants to enter the data center together with the applicant.

  The above-described embodiment is a preferred embodiment of the present invention, and various modifications can be made without departing from the scope of the present invention. For example, in the above-described embodiment, the group name is used as information for specifying a group and the company name is used as information for specifying a company. However, each process may be performed using a group ID and a company ID. Good. Each process in the present embodiment described above can be executed using hardware, software, or a composite configuration of both.

  In the case of executing processing using software, it is possible to install and execute a program in which a processing sequence is recorded in a memory in a computer incorporated in dedicated hardware. Alternatively, the program can be installed and executed on a general-purpose computer capable of executing various processes.

DESCRIPTION OF SYMBOLS 10 Entrance application management apparatus 11 Communication part 12 Memory | storage part 13 Entrance control part 21 Manager terminal 22 Person in charge terminal 23 Data center 24 Reception apparatus

Claims (5)

Group name and a group master and the associated group name is associated associated with the group, contact name and the person in charge usage data center name available to the person in charge is the person in charge of the group name that belongs tied A storage unit for storing the master;
Using the person-in-charge master, an entrance control unit that generates a list of usage data center names stored corresponding to the applicant who is the person in charge who wishes to enter the building,
A communication unit that transmits the generated list of use data center names to the person-in-charge terminal;
With
The admission control unit
When receiving the name of the data center desired to enter from the person-in-charge terminal,
From the previous SL person in charge master, other than the applicant, stored corresponding to the group to which the applicant belongs, and, to extract the name of the person admission desired data center name is stored as usage data center,
From the group master , extract the related group name stored in relation to the group name to which the applicant belongs,
From the person-in-charge master, a related person name that is stored in relation to the extracted related group name and is a person in charge whose entry data center name is stored as the use data center is extracted.
The extracted applicant other than the person's name and a related person in charge name and name of the person in charge with the admission can be the person in charge to the data center together,
A field that lists the name of the applicant, a companion person selection field for selecting a person in charge who wishes to enter the data center together from a list of names of persons who can enter the data center together with the person in charge, Generate data for the application screen that includes the entry field corresponding to the name of the data center you wish to enter,
The communication unit is
The admission application management device, wherein the generated data on the admission application screen is transmitted to the person-in-charge terminal. The storage unit further stores a company master in which a company name is associated with a group name to which the company belongs,
The admission control unit, when inputting information from the administrator terminal to the person in charge master, based on the company master, the group name associated with the group selected in advance by the person in charge terminal, The admission application management apparatus according to claim 1, wherein the admission application management apparatus is displayed so as to be selectable as a company name to which the person in charge belongs. The storage unit stores an entrance application master,
Before entry gallery controller, when it receives the admission application data including data entered in each field of the entrance application screen from the representative terminal, the admission application data received on the admission applicant master of the storage unit Add
The communication unit sends a permission request including an address to an application inquiry list homepage for permitting admission created based on the admission application master to the name of the data center that desires admission included in the received admission application data. The admission application management device according to claim 1, wherein the admission application management device is transmitted to a corresponding reception device. Group name and a group master and the associated group name is associated associated with the group, contact name and the person in charge usage data center name available to the person in charge is the person in charge of the group name that belongs tied A control method for an entrance application management device comprising a storage unit for storing a master,
Using the person-in-charge master to generate a list of use data center names stored corresponding to the applicant who is in charge of entering the building;
Transmitting the generated list of use data center names to a person-in-charge terminal;
When receiving the name of the data center desired to enter from the person-in-charge terminal,
From the previous SL person in charge master, other than the applicant, stored corresponding to the group to which the applicant belongs, and, to extract the name of the person admission desired data center name is stored as usage data center,
From the group master , extract the related group name stored in relation to the group name to which the applicant belongs,
From the person-in-charge master, a related person name that is stored in relation to the extracted related group name and is a person in charge whose entry data center name is stored as the use data center is extracted.
A step of setting the name of the person in charge who can enter the data center together with the person in charge with the name of the person in charge other than the applicant and the name of the related person in charge,
A field that lists the name of the applicant, a companion person selection field for selecting a person in charge who wishes to enter the data center together from a list of names of persons who can enter the data center together with the person in charge, Generating data for an entrance application screen including an input item field corresponding to a data center name desired to enter;
And a step of transmitting the generated data of the entrance application screen to the person-in-charge terminal. Group name and a group master and the associated group name is associated associated with the group, contact name and the person in charge usage data center name available to the person in charge is the person in charge of the group name that belongs tied A program that is executed by a computer having a storage unit that stores a master,
Using the person-in-charge master to generate a list of use data center names stored corresponding to the applicant who is in charge of entering the building;
Transmitting the generated list of use data center names to a person-in-charge terminal;
When receiving the name of the data center desired to enter from the person-in-charge terminal,
From the previous SL person in charge master, other than the applicant, stored corresponding to the group to which the applicant belongs, and, to extract the name of the person admission desired data center name is stored as usage data center,
From the group master , extract the related group name stored in relation to the group name to which the applicant belongs,
From the person-in-charge master, a related person name that is stored in relation to the extracted related group name and is a person in charge whose entry data center name is stored as the use data center is extracted.
A step of setting the name of the person in charge who can enter the data center together with the person in charge with the name of the person in charge other than the applicant and the name of the related person in charge,
A field that lists the name of the applicant, a companion person selection field for selecting a person in charge who wishes to enter the data center together from a list of names of persons who can enter the data center together with the person in charge, Generating data for an entrance application screen including an input item field corresponding to a data center name desired to enter;
And transmitting the generated data of the entrance application screen to the person-in-charge terminal.

Images