JP2007172379A - User ID automatic management system - Google Patents

Abstract

Unnecessary user ID registration and new user ID registration based on user ID usage information and user affiliation / posture information are automatically and efficiently managed without increasing the management workload. An automatic user ID management system is provided.
A data processing unit that sequentially executes a totaling function for registered user usage records, a function for creating batch adjustment data, and a batch adjustment function for registered user information, a registered user affiliation / posture information database, and success / failure of logon / logoff. The recording database 3 and the registered user information master database 4 and various databases 5 to 8 are provided, and the data processing unit 1 registers the registered user affiliation / posture information database 2, the logon / logoff success / failure recording database 3, and the registered user information master at the preset date and time. Predetermined data is read from the database 4, and the registered user usage record aggregation, batch adjustment data creation, and batch adjustment of registered user information are sequentially executed and output using the data and various databases 5 to 8.
[Selection] Figure 1

Description

  The present invention relates to an automatic user ID management system, and in particular, appropriately adjusts user IDs whose use frequency of the business system is low, user IDs whose affiliation / post in the business system have been changed, and the like so that the user ID is optimally efficient. The present invention relates to a user ID automatic management system that is managed in an automatic manner.

  Generally, in a business system having a user ID authentication method used inside a company, a user's business change or a user change within the company is usually performed. Usage frequency and usage form will change. In addition, information such as user IDs registered in the business system may have a significant effect depending on the form of use. Therefore, in modern society where the importance of security is recognized, it exists in a distributed manner. There is an increasing need to collectively manage each user ID registered in the business system.

Recently, a management system for managing user IDs used inside a company has been developed in such various circumstances, and one of them is disclosed in Japanese Patent Laid-Open No. 2003-186559. There is a license management system. The license management system disclosed in Japanese Patent Application Laid-Open No. 2003-186559 monitors usage status of a license program by a user who has acquired a license and uses usage monitoring means for forming usage status information representing the usage status, and a license program If there is a license request for the use of the program that exceeds the number of licenses that can be permitted, the license usage permission granted to users who have not used the program based on the usage status information formed by the usage monitoring means And a license management device that is changed so as to give a license permission for the use of the program to a user who has newly requested the license use permission.
JP 2003-186559 A

  Since the license management system disclosed in Japanese Patent Application Laid-Open No. 2003-186559 performs license use permission and license use permission release based on use status information indicating the use status of a license program by a user, the license management system is simply used. For users with low program usage frequency, the license usage permission status is automatically changed to the license usage permission release status, and it is necessary to change to the license usage permission status again when using the licensed program. In this respect, it cannot be said that it is excellent in usability and adaptability.

  The present invention has been made in view of such a technical background. The purpose of the present invention is to cancel the registration of unnecessary user IDs and new user IDs based on user ID usage status information and user affiliation / posture information. It is an object of the present invention to provide an automatic user ID management system that can perform user ID management automatically and efficiently without increasing the management workload.

  In order to achieve the above object, a user ID automatic management system according to the present invention includes a data processing unit in which a registered user usage record totaling function, a batch adjustment data creation function, and a registered user information batch adjustment function are sequentially executed. A registered user affiliation / posture information database that can be changed by an external operation, a logon / logoff success / failure record database supplied with record information from another similar system, a registered user information master database, and various databases, The processing unit reads predetermined data from each of the registered user affiliation / posture information database, logon / logoff success / failure record database, and registered user information master database at a predetermined date and time, and reads the read data and various databases. Use the total of registered user usage records, one Creating adjustment data, sequentially executing the batch control of the registered user information comprises a configuration means for outputting a result of the adjustment.

  In the above configuration means, the data processing unit is a user who is determined to be unnecessary at the time of batch adjustment of registered user information based on the recorded contents of the registered user affiliation / posture information database and the logon / logoff success / failure record database. The processing for invalidating the user ID after deleting the ID record is performed.

  Further, in the above configuration means, the various databases are a categorized usage count database, a simultaneous connection user transition data database, a user classification database, and a batch adjustment data database, and the data processing unit is a registered user. When the usage record totaling function is executed, the usage number totaling database by affiliation, the simultaneous connection user transition data database, and the user classification database are used, and when the batch adjustment data creation function is executed, the user classification database and the batch adjustment data database are And the batch adjustment data database is used when executing the batch adjustment function for registered user information.

  As described above, according to the user ID automatic management system of the present invention, by providing the above-described configuration means, unnecessary user ID deregistration based on user ID usage status information and user affiliation / posture information, Registration of a new user ID can be performed automatically and efficiently without increasing the management work load. Specifically, first, personnel information and users in the business system By automatically comparing ID registration information, you can find and correct usage authority setting errors in the business system, and secondly, use authority in the business system is lost due to retirement, etc. Since the related user ID is automatically deleted so as to meet the point in time, the possibility of unauthorized use of the user ID can be greatly reduced. Because the setting of the usage authority in the actual business system is compared by the division of roles that combines the affiliation and position that are normally used, it may be possible to make a detailed comparison compared to the case of comparison only by affiliation Fourth, there is an effect that it can be used to confirm whether or not the use authority of the user ID registered in the business system is appropriate at that time.

  Hereinafter, embodiments of a user ID automatic management system according to the present invention will be described with reference to the drawings.

  FIG. 1 is a block diagram showing a main configuration of an embodiment in the user ID automatic management system.

  As shown in FIG. 1, this user ID automatic management system includes a data processing unit 1, a registered user affiliation / posture information database 2, a logon / logoff success / failure record database 3, a registered user information master database 4, It consists of a usage count total database 5, a simultaneous connection user transition data database 6, a user classification database 7, a batch adjustment data database 8, and a processing result output unit 9. In addition, an external data input unit 10, A plurality of other business system servers 11 (1) to 11 (N) are provided. The data processing unit 1 includes a registered user usage record totaling processing unit 1 (1), a batch adjustment data creation processing unit 1 (2), and a registered user information batch adjustment processing unit 1 (3). .

  In this case, the registered user affiliation / posture information database 2 is connected to the external data input unit 10 and includes information such as the name, affiliation / posture, and contact information of each user registered in the business system. . Information directly related to users is stored, and the success / failure record database 3 of logon / logoff is connected to each of a plurality of other business system servers 11 (1) to 11 (N), and each user ID registered in the business system Log-on / log-off success / failure record information is stored, and the registered user information master database 4 is connected to each of a plurality of other business system servers 11 (1) to 11 (N) and registered with the business system. ID, name, affiliation / position information, valid flag, and the like are stored.

  The registered user usage record totaling processing unit 1 (1) reads and inputs the registered user affiliation / posture information from the registered user affiliation / posture information database 2 and the logon / logoff success / failure record from the logon / logoff success / failure record database 3. Calculates the cumulative total of user IDs by affiliation within the aggregation period, writes the calculation result to the usage count aggregation database 5 by affiliation, and reads the logon / logoff success / failure record, and the business system by time within the input aggregation period Calculating the number of successful logon users with the user ID, and writing the calculation result into the simultaneous connection user transition data database 6, reading the logon / logoff success / failure record, and the registered user information from the registered user information master database 4, Number of successful logons of user IDs to the business system within the entered aggregation period It is calculated, and performs the calculation result and by comparing the preset threshold writing use frequency corresponding to the threshold in the user classification database 7 process.

  The batch adjustment data creation processing unit 1 (2) reads the registered user affiliation / posture information from the registered user affiliation / posture information database 2 and the registered user information from the registered user information master database 4, and is registered in the business system. It is determined whether or not the affiliation / posture information of the user ID matches the affiliation / posture information of the registered user information, the process of writing the determination result in the user classification database 7, and the matching result using the matching result A user ID that matches the set threshold value is selected as an automatic adjustment target, and a process of writing the selection result in the batch adjustment data database 8 is performed.

  Further, the registered user information batch adjustment processing unit 1 (3) reads the write data of the batch adjustment data database 8 and executes a preset adjustment process for the registered user information registered in the business system. The result is written into the processing result log list which is the processing result output unit 9.

  The other business system servers 11 (1) to 11 (N) externally connected to the user ID automatic management system are described as being connected to a plurality (N) of servers. Only one unit may be connected.

  Here, various functions executed by the user ID automatic management system will be described in order.

  First, FIG. 2 is an explanatory diagram showing a processing procedure of a user usage record totaling process executed by the registered user usage record totaling processing unit 1 (1) of the data processing unit 1. In FIG. 2, the same components as those shown in FIG.

  As shown in FIG. 2, the registered user usage record totaling processing unit 1 (1) includes the number of user IDs by affiliation within the total period read from the affiliation / posture information database 2 of the registered user, and the logon / logoff success / failure record database. Using the number of user IDs by affiliation within the aggregation period read out from No. 3, the affiliation usage number aggregation process A1 and the simultaneous connection user number data creation process A2 are performed, and the processing results of the affiliation usage number aggregation process A1 belong to The data is written in the separate usage number totalization database 5 and the processing result of the simultaneous connection user number data creation processing A2 is written in the simultaneous connection user transition data database 6. At the same time, using the registered user information, the number of user IDs by affiliation, and the number of user IDs by affiliation within the counting period read from the registered user information master database 4, a user ID based on a preset threshold for each user ID A user classification process A3 indicating another usage frequency is performed, and the processing result of the user classification process is written in the user classification database 7.

  Here, FIG. 11 is an explanatory diagram showing an example of information data stored in the affiliation / posture information database 2 of the registered user shown in FIG.

  As shown in FIG. 11A, the information data includes items such as name, affiliation, job title, and contact information. Among them, the name represents the user name registered in the business system, and the affiliation is the business system. Represents the affiliation information of the registered user, the title represents the title information of the person having the user ID registered in the business system, and the contact address represents the contact information such as the user's email registered in the business system FIG. 11 (b) shows an actual example.

  FIG. 12 is an explanatory diagram showing an example of information data stored in the logon / logoff success / failure record database 3 shown in FIG.

  As shown in FIG. 12 (a), the information data includes items such as date, time, user ID, and event. Among them, the date indicates the date when the event is recorded, and the time indicates the event. The user ID represents the user ID that generated the event, and the event represents one of logon success, logon failure, or logoff, and FIG. 12B shows an actual example.

  Further, FIG. 13 is an explanatory diagram showing an example of information data stored in the registered user information master database 4 shown in FIG.

  As shown in FIG. 13A, the information data includes items such as a user ID, name, affiliation, post, valid flag, etc. Among them, the user ID represents a user ID registered in the business system, Each of the name, affiliation, and title is the same as the information data in the registered user's affiliation / posture information database 2, and the valid flag represents flag information that is permitted to log on to the business system. FIG. The example is shown.

  On the other hand, FIG. 14 is an explanatory diagram showing an example of information data stored in the affiliation usage count database 5 shown in FIG.

  As shown in FIG. 14 (a), the information data includes items such as a start date, an end date, affiliation, and the number of uses. Among them, the start date represents the start date of the total period, and the end date is the total. It represents the end date of the period, the affiliation represents the affiliation as the aggregation unit, the number of uses represents the accumulated information of the user ID corresponding to the department to be aggregated, and FIG. 14 (b) shows an actual example. is there.

  FIG. 15 is an explanatory diagram showing an example of information data stored in the simultaneous connection user transition data database 6 shown in FIG.

  As shown in FIG. 15A, the information data includes items such as date, time, number of users, etc., in which the date represents the recording date of the number of users, and the time represents the recording time of the number of users. The number of users represents information on the number of users who are logged on simultaneously at a specific date and time, and FIG. 15B shows an actual example thereof.

  FIG. 16 is an explanatory diagram showing an example of information data stored in the user classification database 7 shown in FIG.

  As shown in FIG. 16A, the information data includes items such as a user ID, a last logon date, a usage frequency, a matching, and a comparison date. Among these items, the user ID is information in the registered user information master database 4. Same as the data, the last logon date represents the logon date when the user ID was last successfully logged on, the usage frequency represents the usage frequency set based on the preset threshold within the totaling period, and the matching is the comparison date This represents information indicating the result of information comparison between the registered user information master database 4 and the registered user affiliation / postal information database 2, and the comparison date is an information comparison between the registered user information master database 4 and the registered user affiliation / postal information database 2. FIG. 16B shows an example of the implementation date.

  Next, FIG. 3 is an explanatory diagram showing a processing procedure of batch adjustment data creation processing executed by the batch adjustment data creation processing unit 1 (2) of the data processing unit 1. In FIG. 3, the same components as those shown in FIG.

  As shown in FIG. 3, the number of user IDs by affiliation in the counting period read from the registered user's affiliation / posture information database 2 and the registered user information in the counting period read from the registered user information master database 4 are used. A matching process A4 with affiliation information for comparing the roles of each affiliation and job title is performed, and the processing result is written in the user classification database 7. Next, the information data of the user classification database 7 is read, unmatching and invalid user selection processing A5 for selecting a user ID that does not match the preset condition is executed, and the processing result is written in the batch adjustment data database 8.

  Here, FIG. 17 is an explanatory diagram showing an example of information data stored in the batch adjustment data database 8 shown in FIG.

  As shown in FIG. 17A, the information data includes items such as a user ID, a processing type, a processing date, and an adjustment status. Among them, the user ID represents a user ID that is a target of batch adjustment, The process type represents preset adjustment process type information, the process date represents the execution date of the batch adjustment process, the adjustment status represents the adjustment process result information, and FIG. 17B shows an actual example. It is.

  Next, FIG. 4 is an explanatory diagram showing a processing procedure of user registration information batch adjustment processing executed by the user registration information batch adjustment processing unit 1 (3) of the data processing unit 1. In FIG. 3, the same components as those shown in FIG.

  As shown in FIG. 4, the registered user information in the counting period read from the registered user information master database 4 and the batch adjustment data information in the counting period read from the batch adjustment data database 8 are used in the business system. User ID unmatching and invalid user batch adjustment processing A 6 are executed, and the processing result is written in the processing result log list 9. Thereby, the processing result log list 9 is written with, for example, information contents as shown in FIG. 4, that is, an execution start date and time, an execution start date and time, a target date, and a process type and a process result for each user ID. .

  Next, a specific process in each of the processes A1 to A6 illustrated in FIGS. 2 to 4 will be described.

  FIG. 5 is a flowchart showing a processing procedure of the affiliation usage count totaling process A1 executed by the user usage record totaling processing unit 1 (1) shown in FIG.

  The processing procedure of the affiliation usage count totaling process A1 will be described with reference to the flowchart shown in FIG.

  First, in step S <b> 1, the user usage record aggregation processing unit 1 (1) receives the aggregation period input by the user ID administrator through the external data input unit 10.

  Next, in step S2, the user usage record aggregation processing unit 1 (1) reads the date / user ID / event within the aggregation period from the logon / logoff success / failure record database 3 based on the received aggregation period.

  Next, in step S3, the user usage record aggregation processing unit 1 (1) deletes the duplicate user ID using the read date / time / user ID / event.

  Subsequently, in step S4, the user usage record aggregation processing unit 1 (1) uses the read date / time / user ID / event and the affiliation-specific user ID of the aggregation period read from the affiliation / posture information database 2 of the registered user. Matching between the user ID and the affiliation information is achieved.

  Subsequently, in step S5, the user usage record aggregation processing unit 1 (1) selects one piece of affiliation information among the affiliation information that has achieved matching with the user ID.

  Next, in step S6, the user usage record aggregation processing unit 1 (1) determines whether or not the number of pieces of affiliation information to be selected has been exhausted. When it is determined that the number of belonging information has not yet disappeared (N), the process proceeds to the next step S7. On the other hand, when it is determined that the number of belonging information has already disappeared (Y), another step S8. Migrate to

  Next, in step S7, the user usage record totaling processing unit 1 (1) adds 1 to the total value to which it belongs. When this process ends, the process returns to the previous step S5, and the operations after step S5 are repeatedly executed.

  In step S8, the user usage record aggregation processing unit 1 (1) writes the start date, end date, affiliation, and aggregation value of the aggregation period in the affiliation usage aggregation database 5, and this series of affiliation usage aggregation is performed. The process A1 is terminated.

  FIG. 6 is a flowchart showing a processing procedure of the simultaneous connection user number data creation processing A2 executed by the user usage record aggregation processing unit 1 (1) shown in FIG.

  The processing procedure of the simultaneous connection user number data creation processing A2 will be described with reference to the flowchart shown in FIG.

  First, in step S11, the user usage record totaling processing unit 1 (1) succeeds in logon of the event in the data information of the totaling period input from the logon / logoff success / failure record database 3 by the affiliation usage count totaling process A1. And log off and record information.

  Next, in step S12, the user usage record aggregation processing unit 1 (1) selects one of the selected logon success and logoff information.

  Next, in step S13, the user usage record aggregation processing unit 1 (1) determines whether or not the number of pieces of information to be selected has been exhausted. When it is determined that the number of information items to be selected has not yet disappeared (N), the process proceeds to the next step S13. On the other hand, when it is determined that the number of information items to be selected has already disappeared (Y) This series of processing procedures is terminated.

  Subsequently, in step S13, the user usage record aggregation processing unit 1 (1) reads the date / time / user number data with the newest date and time from the simultaneous connection user transition data database 6.

  Subsequently, in step S14, the user usage record totaling processing unit 1 (1) determines whether or not the event type of the read date / time / user number data is successful logon data. When it is determined that the data is successful logon (Y), the process proceeds to the next step S16. On the other hand, when it is determined that the data is logoff (N), the process proceeds to another step S17.

  In the next step S15, the user usage record aggregation processing unit 1 (1) adds 1 to the user number data of the read date / time / user number data because the event log-on is successful.

  In step S16, the user usage record totaling processing unit 1 (1) subtracts 1 from the user number data of the read date / time / user number data because the event was logged off.

  Next, in step S <b> 17, the user usage record aggregation processing unit 1 (1) overwrites the user number data added or subtracted to the simultaneous connection user transition data database 6. When this process ends, the process returns to the previous step S11, and the processes after step S11 are sequentially executed again.

  Further, FIG. 7 is a flowchart showing a processing procedure of the user classification processing A3 executed by the user usage record aggregation processing unit 1 (1) shown in FIG.

  The process procedure of the user classification process A3 will be described with reference to the flowchart shown in FIG.

  First, in step S <b> 21, the user usage record aggregation processing unit 1 (1) reads one user ID selected from the registered user information master database 4.

  Next, in step S22, the user usage record aggregation processing unit 1 (1) determines whether or not there is no user ID to be selected. When it is determined that there are no user IDs to be selected yet (N), the process proceeds to the next step S23. On the other hand, when it is determined that there are no user IDs to be selected yet (Y), this series of steps is performed. The processing procedure of is terminated.

  Next, in step S23, the user usage record totaling processing unit 1 (1) performs the logon success in the past half year from the execution date in this example, the preset period that matches the user ID read from the logon / logoff success / failure record database 3. Select the recorded data.

  In step S24, the user usage record totaling processing unit 1 (1) deletes the duplicate date from the selected record data of successful logon.

  Subsequently, in step S25, the user usage record totaling processing unit 1 (1) determines whether there is any selected record data with an overlapping date. When it is determined that there is no selected recording data with a date that already overlaps (Y), the process proceeds to the next step S26, while it is determined that there is still selected recording data with a date that overlaps. If it is (Y), the process proceeds to another step S27.

  In the next step S26, the user usage record totaling processing unit 1 (1) sets the user ID read in the previous step S21 without usage frequency and no last logon date, and sets the set user ID as the user classification. Write to database 7.

  In step S27, the user usage record aggregation processing unit 1 (1) determines whether there are 25 or more records of the record data with the duplicate date. When it is determined that the number of records is 25 or more (Y), the process proceeds to the next step S28, whereas when it is determined that the number of records is 25 or less (N), the process proceeds to another step S29.

  Next, in step S28, the user usage record aggregation processing unit 1 (1) sets the last logon date to the user ID read in the previous step S21 with a high usage frequency, and sets the set user ID as the user. Write to the classification database 7.

  Next, in step S29, the user usage record aggregation processing unit 1 (1) determines whether or not there are 6 or more records of the record data of the duplicate date. When it is determined that the number of records is 6 or more (Y), the process proceeds to the next step S30. On the other hand, when it is determined that the number of records is 6 or less (N), the process proceeds to another step S30.

  Subsequently, in step S30, the user usage record totaling processing unit 1 (1) sets the last logon date during the usage frequency for the user ID read in the previous step S21, and sets the set user ID to the user classification database 7. Write to.

  In step S31, the user usage record aggregation processing unit 1 (1) sets and sets the last logon date during the usage frequency for the user ID read in the previous step S21, and sets the set user ID to the user classification database. Write to 7. When this process ends, the process returns to the previous step S21, and the processes after step S21 are sequentially executed again.

  FIG. 8 is a flowchart showing a processing procedure of matching processing A4 with affiliation information executed by the batch adjustment data creation processing unit 1 (2) shown in FIG.

  The processing procedure of the matching processing A4 with affiliation information will be described using the flowchart shown in FIG.

  First, in step S <b> 32, the batch adjustment data creation processing unit 1 (2) reads record data of one user ID / name / affiliation / position selected from the registered user information master database 4.

  Next, in step S33, the batch adjustment data creation processing unit 1 (2) determines whether or not there is no record data of the user ID / name / affiliation / position to be selected. When it is determined that the user ID / name / affiliation / position record data to be selected has not yet been lost (N), the process proceeds to the next step S34, while the user ID / name / affiliation / to be already selected. When it is determined that there is no more recorded data for the post (Y), this series of processing procedures is terminated.

  Subsequently, in step S34, the batch adjustment data creation processing unit 1 (2) selects and reads the affiliation / position corresponding to the name read in step S32 from the registered user affiliation / position information database 2.

  Subsequently, in step S35, the batch adjustment data creation processing unit 1 (2) determines whether or not there is affiliation / position information corresponding to the name read in step S34. When it is determined that there is no corresponding affiliation / posture information (Y), the process proceeds to the next step S36, and when it is determined that there is corresponding affiliation / posture information (N), the process proceeds to another step S37. To do.

  In the next step S36, the batch adjustment data creation processing unit 1 (2) sets the affiliation / posture information corresponding to the name read in step S34 as “no matching affiliation”, and sets the set affiliation / posture information to the user classification database 7 Write to.

  Next, in step S37, the batch adjustment data creation processing unit 1 (2) determines whether the affiliation / position information corresponding to the name read in step S34 is the same. When it is determined that the corresponding affiliation / posture information matches (Y), the process proceeds to the next step S38, and when it is determined that the corresponding affiliation / posture information does not match (N) The process proceeds to step S39.

  Subsequently, in step S38, the batch adjustment data creation processing unit 1 (2) sets matching / matching in the affiliation / postal information corresponding to the name read in step S34, and the set affiliation / postal information is stored in the user classification database 7. Write.

  Subsequently, in step S39, the batch adjustment data creation processing unit 1 (2) sets the affiliation / posture information corresponding to the name read in step S34 as a mismatch, and sets the set affiliation / posture information in the user classification database 7 Write to. When this process ends, the process returns to the previous step S32, and the processes after step S32 are sequentially executed again.

  Further, FIG. 9 is a flowchart showing a processing procedure of unmatching and invalid user selection processing A5 executed by the batch adjustment data creation processing unit 1 (2) shown in FIG.

  The processing procedure of the unmatching and invalid user selection processing A5 will be described with reference to the flowchart shown in FIG.

  First, in step S41, the batch adjustment data creation processing unit 1 (2) reads the recorded data of one user ID / matching / last logon date selected from the user classification database 7.

  Next, in step S42, the batch adjustment data creation processing unit 1 (2) determines whether there is no record data of the record data of the user ID / matching / last logon date to be selected. When it is determined that there is no recording data of the user ID / matching / final logon date to be selected yet (N), the process proceeds to the next step S43, while the user ID / matching / final logon to be selected already. When it is determined that there is no recording data for the date (Y), this series of processing procedures is terminated.

  Subsequently, in step S43, the batch adjustment data creation processing unit 1 (2) determines whether or not the recording data in step S42 is set without matching affiliation. When it is determined that the recording data is set without matching affiliation (Y), the process proceeds to the next step S44, and on the other hand, it is determined that the recording data is set other than without matching affiliation (N ) Shift to another step S43.

  In the next step S44, the batch adjustment data creation processing unit 1 (2) sets the processing type of the recording data in step S42 to deletion, and writes the set processing type deletion recording data in the batch adjustment data database 8. When this process ends, the process returns to the previous step S41, and the processes after step S41 are sequentially executed again.

  In other step S45, the batch adjustment data creation processing unit 1 (2) determines whether or not the recording data in step S42 is set to match mismatch. When it is determined that the recording data is set to match mismatch (Y), the process proceeds to the next step S46, while when it is determined that the recording data is set to other than matching mismatch (N). Shifts to another step S43.

  Subsequently, in step S46, the batch adjustment data creation processing unit 1 (2) sets the processing type of the recording data in step S42 to invalidation, and sets the recording data for which the processing type is invalidated as the batch adjustment data database 8. Write to.

  Next, in step S47, the batch adjustment data creation processing unit 1 (2) determines that the last logon date of the recording data in step S42 is within a preset period from the process execution date, in this example, within the past half year before the process execution date. Determine whether or not. Then, when it is determined that the last logon date is within the past half year before the process execution date (Y), the process proceeds to the next step S48, and on the other hand, the final logon date is determined to be before the past half year before the process execution date. If (N), the process returns to the previous step S41, and the processes after step S41 are sequentially executed again.

  In the next step S48, the batch adjustment data creation processing unit 1 (2) sets the processing type of the recording data in step S42 to deletion, and writes the set recording data for deletion of the processing type in the batch adjustment data database 8. When this process ends, the process returns to the previous step S41, and the processes after step S41 are sequentially executed again.

  Further, FIG. 10 is a flowchart showing the processing procedure of the user registration information batch adjustment processing A6 executed by the user registration information batch adjustment processing unit 1 (3) shown in FIG.

  The procedure of the user registration information batch adjustment process A6 will be described with reference to the flowchart shown in FIG.

  First, in step S 51, the user registration information batch adjustment processing unit 1 (3) writes the date and time at the start of this processing in the processing result log list 9.

  Next, in step S 52, the user registration information batch adjustment processing unit 1 (3) reads one selected user ID / processing type / processing date / adjustment status recording data from the batch adjustment data database 8.

  Next, in step S53, the user registration information batch adjustment processing unit 1 (3) determines whether there is no record data of user ID / processing type / processing date / adjustment status to be selected. When it is determined that there is no record data to be selected (Y), the process proceeds to the next step S54. On the other hand, when it is determined that there is no record data to be selected (N). The process proceeds to another step S55.

  Subsequently, in step S54, the user registration information batch adjustment processing unit 1 (3) writes the date and time when the recording data is completed into the processing result log list 9.

  In step S55, the user registration information batch adjustment processing unit 1 (3) sets the processing date set in the recording data to be earlier than the processing execution date, and the adjustment status value is not adjusted. Determine whether or not. When it is determined that the recording data satisfies such setting requirements (Y), the process proceeds to the next step S56, and on the other hand, it is determined that the recording data does not satisfy such setting requirements ( N), the process returns to the previous step S52, and the processing after step S52 is repeated.

  In the next step S56, the user registration information batch adjustment processing unit 1 (3) determines whether or not the processing type invalidation setting is set in the recording data. When it is determined that the processing type of the recording data is set to invalidation (Y), the process proceeds to the next step S57, while the processing type of the recording data is set to a setting other than invalidation. If it is determined that there is (N), the process proceeds to another step S58.

  Next, in step S57, the user registration information batch adjustment processing unit 1 (3) sets the processing type of the recording data to invalidation, and stores the set processing type invalidation recording data in the registered user information master database 4. To do. When this process ends, the process proceeds to later step S60.

  In step S58, the user registration information batch adjustment processing unit 1 (3) determines whether or not the processing type deletion setting is set in the recording data. If it is determined that the processing type of the recording data is set to delete (Y), the process proceeds to the next step S59, while the processing type of the recording data is set to a setting other than deletion. When it is determined (N), the process returns to the previous step S52, and the processes after step S52 are repeated.

  Subsequently, in step S59, the user registration information batch adjustment processing unit 1 (3) deletes the recording data that matches the user ID corresponding to the processing type deletion because the processing type value in the recording data is deletion. To do.

  Next, in step S <b> 60, the user registration information batch adjustment processing unit 1 (3) writes the date and time at the time when there is no recorded data in the processing result log list 9 to the processing result log list 9 as the end of execution. When this process ends, the process returns to the previous step S52, and the processes after step S52 are repeated. Processes are executed sequentially.

  As described above, according to the present embodiment, unnecessary user ID deregistration and new user ID registration are increased based on user ID usage status information and user affiliation / posture information. Therefore, user ID management can be performed automatically and efficiently.

It is a block diagram which shows the principal part structure of the embodiment in this user ID automatic management system. It is explanatory drawing which shows the process sequence of the user utilization record total process performed in the registration user utilization record total process part of a data processing part. It is explanatory drawing which shows the process sequence of the batch adjustment data creation process performed in the batch adjustment data creation processing part of a data processing part. It is explanatory drawing which shows the process sequence of the batch adjustment process of the user registration information performed in the user registration information batch adjustment process part of a data processing part. It is a flowchart which shows the process sequence of the utilization number totaling process classified by affiliation performed by the user usage record totaling process part shown by FIG. It is a flowchart which shows the process sequence of the simultaneous connection user number data creation process performed in the user utilization record totalization process part shown in FIG. It is a flowchart which shows the process sequence of the user classification | category process A3 performed by the user utilization record totalization process part shown in FIG. It is a flowchart which shows the process sequence of a matching process with the affiliation information performed by the batch adjustment data creation process part shown in FIG. It is a flowchart which shows the process sequence of the unmatching and invalid user selection process which are performed in the batch adjustment data creation process part shown in FIG. FIG. 5 is a flowchart showing a processing procedure of user registration information batch adjustment processing executed by a user registration information batch adjustment processing unit shown in FIG. 4. FIG. FIG. 3 is an explanatory diagram illustrating an example of information data stored in a affiliation / posture information database of a registered user illustrated in FIG. 1. FIG. 3 is an explanatory diagram illustrating an example of information data stored in a logon / logoff success / failure record database illustrated in FIG. 1. It is explanatory drawing which shows an example of the information data stored in the registration user information master database shown in FIG. It is explanatory drawing which shows an example of the information data stored in the utilization number totaling database according to affiliation shown in FIG. It is explanatory drawing which shows an example of the information data stored in the database for simultaneous connection user transition data shown in FIG. It is explanatory drawing which shows an example of the information data stored in the user classification database shown in FIG. It is explanatory drawing which shows an example of the information data stored in the database for batch adjustment data shown in FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Data processing part 1 (1) Registered user utilization record totaling processing part 1 (2) Batch adjustment data creation processing part 1 (3) Registered user information batch adjustment processing part 2 Registered user affiliation / posture information database 3 Logon / logoff success / failure record Database 4 Registered user information master database 5 Usage count database by affiliation 5 Simultaneously connected user transition data database 7 User classification database 8 Batch adjustment data database 9 Processing result output unit 10 External data input units 11 (1) to 11 (N Other business system server

Claims (3)

Registered user usage record totaling function, batch adjustment data creation function and registered user information batch adjustment function are sequentially executed, registered user affiliation / posture information database that can be changed by external operation, and other A log-on / log-off success / failure record database and a registered user information master database to which record information is supplied from the same kind of system, and various databases, and the data processing unit at the predetermined date and time, Predetermined data is read from each of the post information database, the logon / logoff success / failure record database, and the registered user information master database, and using the read data and the various databases, the registered user usage records are aggregated and collectively adjusted data Creation and batch adjustment of registered user information User ID automated management system running, and outputs the result of the adjustment. The data processing unit records a user ID determined to be unnecessary at the time of collective adjustment of the registered user information based on the recorded contents of the registered user affiliation / posture information database and the logon / logoff success / failure record database. 2. The user ID automatic management system according to claim 1, wherein processing for invalidating the user ID is performed. The various databases are a categorized usage count database, a concurrent user transition data database, a user classification database, and a batch adjustment data database, and the data processing unit has a registered user usage record counting function. Use the above-mentioned number-of-affiliation usage totaling database, the database for user transition data and the user classification database at the time of execution, and use the user classification database and the batch adjustment data database for the execution of the batch adjustment data creation function. 3. The user ID automatic management system according to claim 1, wherein the batch adjustment data database is used when executing a batch adjustment function of user information.

Images