Service application cooperation system and service application cooperation method

Abstract

To provide a service application cooperation system capable of improving provided functions of the provided service and of responding to diversifying service function requirements.SOLUTION: A service application cooperation system 2 comprises: a talented person acquisition unit 201 for acquiring talented person data 100 of each user from talented person data 110 in which the correspondence relation between users and an organization is registered; an application data generating unit for generating service application data for providing the service to each of the users from the talented person data of each of the users by referring to organization-service combined master information in which the default service is registered to the organization user; and a data cooperation unit 203 for linking the service application data to a provisioning unit 300 which provisions the services for each user.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a service application cooperation system and a service application cooperation method.

Background Art

[0002] In recent years, there has been a desire to speed up the use of IT services. To achieve this desire, provisioning technologies for pre-setting a network and preparing the allocation of server storage resources in advance have been spreading.

[0003] Provisioning targets include hardware devices such as servers and networks, services, and service accounts. For example, a system is known in which an account for a specific service is automatically generated (provisioned) based on new user information registered in a human resource management system.

[0004] The abstract of Patent Document 1 describes that "provisioning resources and management resources are drawn from the entire pool of resources. Management resources and managed resources are dynamically related on the network to ensure the execution of the requested on-demand management function. The management system controls the network between devices that are managed and provisioned." As a result, there is an effect that even when resources are linked to each other, only a minimum amount of network overhead is caused.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] Conventionally, service allocation was automatically triggered by changes in personnel, such as hiring and firing. As a result, it was not possible to customize services, such as changing default services or adding options.

[0007] In addition, in conventional provisioning, only uniform service contents could be set, and it was not possible to change the service contents set by organizational units or the cost bearer of the service at the start of service use. In conventional provisioning, there was no interface for users to change services such as adding options, and it was not possible to change the settings of default services after the start of use.

[0008] Therefore, an object of the present invention is to improve the service provision function of provisioned services and to meet diversified service function requirements.

Means for Solving the Problems

[0009] To solve the above problems, a service application cooperation system of the present invention includes: a human resource data acquisition unit that acquires human resource data of each user from a human resource database in which the correspondence relationship between users and organizations is registered; an application data creation unit that creates service application data for preparing services for each user from the human resource data of each user by referring to organization-service combination master information in which default services for users of the organization are registered; and a data cooperation unit that cooperates the service application data with a provisioning unit that provisions services for each user.

[0010] The service application linkage method of the present invention includes: a human resource data acquisition unit acquiring human resource data of each said user from a human resource database in which the correspondence relationship between users and organizations is registered; an application data creation unit referring to organization-service combination master information in which default services for users of an organization are registered, and creating application data for preparing services for each said user; and a data linkage unit linking the said application data to a provisioning unit that provisions services for each said user.

[0011] Other means will be described in the mode for carrying out the invention.

Effects of the Invention

[0012] According to the present invention, the provisioning function of the provisioned service is improved, and it becomes possible to respond to diversified service function requirements.

Brief Description of the Drawings

[0013]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Mode for Carrying Out the Invention

[0014] Hereinafter, the mode for carrying out the present invention will be described in detail with reference to each figure. FIG. 1 is a configuration diagram of the service application cooperation system 2 according to the present embodiment and its related systems. The service application cooperation system 2 cooperates with the human resource management system 1 and the service provision system 3 to support the provisioning of services for human resources.

[0015] The human resource management system 1 includes a human resource database 110 and manages human resources. The human resource management system 1 provides the human resource data 100 registered in the human resource database 110 to the service application cooperation system 2. The service application cooperation system 2 refers to the human resource data 100 and applies for the services to be provided to each person to the service provision system 3. The service application cooperation system 2 includes a cooperation unit 200, an application management unit 210, a contract management unit 220, and a billing management unit 230. The cooperation unit 200 receives a service application based on the human resource data 100, refers to the cooperation database 104 and the application database 103, and transmits the cooperation database 104 to the provisioning unit 300 described later.

[0016] The service application linkage system 2 imports user information from the human resources management system 1 and sends user-service information to the provisioning section 300 of the service provision system 3. The service application linkage system 2 can further vary the service cost bearer for provisioning based on the user information and the organization-service combination master information 101 (see Figure 2). Thereby, the service application linkage system 2 can respond to the diversifying demands of users.

[0017] The application management section 210 manages the application status of services for each user with reference to the application database 103. The application management section 210 causes the service application data of each user to be displayed on a display section (not shown) and accepts setting changes to this service application data by the IT administrator. The data linkage section 203 (see Figure 2) transmits the service application data whose settings have been changed by the application management section 210 to the provisioning section 300 as linkage data. Note that after the service for each user has been provisioned, the application management section 210 may change the settings of the service for this user based on the contract data of this user. According to the application management section 210, the IT administrator can change the services provided to each user, for example, add options or change the device delivery destination.

[0018] The contract management section 220 manages the contract database 105 for the services provided to each user with reference to the contract database 105. The contract management section 220 registers contract data in the contract database 105, which stores the correspondence between each user and the service prepared for this user, the service provided to this user, and the cost bearer of this service, based on the linkage data.

[0019] The billing management unit 230 manages the billing database 106 of the services provided to each user with reference to the billing database 106. The billing management unit 230 registers billing data for billing the organization for the consideration of the service in the billing database 106 based on the contract data in which each user, the service provided to the user, and the cost bearer of the service are stored.

[0020] The service providing system 3 includes a provisioning unit 300 and service providing platforms 301, 302, 303. The provisioning unit 300 generates (provisions) an account so that a designated user can receive a designated service among the service providing platforms 301, 302, 303. The service providing platform 301 provides service aa to the user. The service providing platform 302 provides service bb to the user. The service providing platform 303 provides service cc to the user.

[0021] Each user uses the account generated by the provisioning unit 300 to access the service providing platform 301 to enjoy service aa, access the service providing platform 302 to enjoy service bb, and access the service providing platform 303 to enjoy service cc. Note that the number of service providing platforms is not limited to three.

[0022] In this embodiment, the service application cooperation system 2 dynamically changes the data passed to the provisioning unit 300 of the service providing system 3, enabling service customization and changes after service provision. When the service application cooperation system 2 sends user information to the provisioning unit 300, it automatically generates a cooperation database 104 (see FIG. 2) for service application.

[0023] The service application linkage system 2 of this embodiment creates default application data 102 that reflects the service setting content for each affiliated organization by using the organizational information of the human resources data 100 and the organization-service combination master information 101 (see FIG. 2). When there are changes to the default application data 102, the service application linkage system 2 performs data linkage with the provisioning unit 300 after reflecting the changes in the settings made by the administrator.

[0024] FIG. 2 is a block diagram showing the operation of the service application linkage system 2. The linkage unit 200 of the service application linkage system 2 includes a human resources data acquisition unit 201, an application data creation unit 202, a data linkage unit 203, and the organization-service combination master information 101.

[0025] The human resources data acquisition unit 201 acquires the human resources data 100 of each user from the human resources database 110 (see FIG. 1) of the human resources management system 1 and delivers it to the application data creation unit 202. The application data creation unit 202 creates default application data 102 for preparing services for each user from the human resources data 100 of each user by referring to the organization-service combination master information 101. The organization-service combination master information 101 has the default services for the users of the organization registered, and the configuration will be described with FIGS. 4 and 5 below.

[0026] FIG. 3 is a diagram showing an example of the human resources database 110. The human resources database 110 is composed of an individual ID column, a name column, an email address column, a company code column, an organization code column, a cost bearer column, and an activation date column. That is, the correspondence between users and organizations is registered in the human resources database 110.

[0027] In the personal ID column, the identifier of the individual user is stored. In the name column, the name of the individual user is stored. In the email address column, the contact email address of the individual user is stored. In the company code column, the code information of the company to which the individual user belongs is stored. In the organization code column, the code information of the organization to which the individual user belongs is stored. In the cost bearer column, the code information of the bearer of the cost (consideration) of the service enjoyed by the individual user is stored. In the activation date column, the activation date and time of the account issued to the individual user are stored. In each row of this human resource database 110, the human resource data 100 of each user is registered.

[0028] Returning to FIG. 2, the description will continue. The application data creation unit 202 creates default application data 102 based on the human resource data 100 and the organization / service combination master information 101. The organization / service combination master information 101 is composed of the organization / service combination master information 101a in FIG. 4 and the organization / service combination master information 101b in FIG. 5.

[0029] The organization / service combination master information 101a in FIG. 4 includes a company code column, an organization code column, an initial cost bearer value column, and a set column. In the company code column, the code information of the company to which the individual user belongs is stored. In the organization code column, the code information of the organization to which the individual user belongs is stored. In the initial cost bearer value column, the code information that is the initial value of the bearer of the cost (consideration) of the service enjoyed by the individual user is stored. In the set column, the setting type related to the service enjoyed by the user is stored.

[0030] The organization / service combination master information 101b in FIG. 5 includes a set column, a service column, and a setting value column. The set column stores set information related to the services enjoyed by the user. By joining the set column of the organization - service combination master information 101b and the set column of the organization - service combination master information 101a using SQL (Structured Query Language), the services associated with the company code and organization code and their set value groups can be obtained.

[0031] The service column stores a plurality of services associated with this set information. The setting value column stores the setting values related to this service. Specifically, for the Type - A set information, service aa and setting a1, and service bb and setting value b1 are associated. For the Type - B set information, service aa and setting a1 and service cc and setting value c1 are associated.

[0032] Returning to Figure 2 to continue the explanation. Based on the company code and organization code of the human resource data 100, the application data creation unit 202 acquires the initial value of the cost bearer and the set information from the organization - service combination master information 101a and 101b. And since the set column of the organization - service combination master information 101b and the set column of the organization - service combination master information 101a are joined by SQL, the application data creation unit 202 can acquire the services and setting values corresponding to the set information. Thereby, the application data creation unit 202 creates the default application data 102 and delivers it to the application management unit 210.

[0033] Figure 6 is a diagram showing an example of the default application data 102. The default application data 102 includes an individual ID column, a name column, an email address column, a company code column, an organization code column, a cost bearer column, an activation date column, and further includes a service aa setting value column, a service bb setting value column, and a service cc setting value column. That is, the default application data 102 is the human resource data 100 with the setting value columns related to each service added.

[0034] The application management unit 210 of the service application cooperation system 2 is configured to include a data presentation setting change and addition unit 211 (see FIG. 2). This data presentation setting change and addition unit 211 presents the default application data 102 to the user, accepts the setting change of the service by the user, and creates the application database 103.

[0035] FIG. 7 is a diagram showing an example of the application database 103. The application database 103 is composed of a personal ID column, a name column, an email address column, a company code column, an organization code column, a cost bearer column, an activation date column, a service aa setting value column, a service bb setting value column, and a service cc setting value column. Note that the application database 103 shown in this FIG. 7 is composed of the same columns as the default application data 102 shown in FIG. 6, and application data for applying for services is registered in each row.

[0036] Each row of the application database 103 shown in FIG. 7 and the default application data 102 shown in FIG. 6 have the same content, but the setting values related to the service may be changed by the user (IT administrator).

[0037] FIG. 8 is a diagram showing an example of the cooperation database 104. The cooperation database 104 is composed of a personal ID column, a name column, an email address column, an activation date column, a service column, and a setting value column. The cooperation database 104 is obtained by decomposing the application database 103 for each service and expanding it into each row.

[0038] FIG. 9 is a diagram showing an example of the contract database 105. The contract database 105 is composed of a contract ID column, a personal ID column, a name column, an email address column, a company code column, an organization code column, a cost bearer column, a service name column, an amount column, a start date column, and an end date column. And contract data is registered in each row of the contract database 105.

[0039] In the contract ID column, the identifier of the contract related to the service provided to this user is stored. In the service name column, the name of the service provided to this user is stored. In the amount column, the amount of the service provided to this user is stored. In the start date column, the start date of the service provided to this user is stored. In the end date column, the end date of the service provided to this user is stored.

[0040] Note that in the personal ID column, name column, email address column, company code column, organization code column, and cost bearer column, information similar to each column stored in the application database 103 is stored. This contract database 105 is created by the contract management department 220 based on the output information of the application management department 210.

[0041] Figure 10 is a diagram showing an example of the billing database 106. The billing database 106 is composed of a billing month column, a company code column, a cost bearer column, a service name column, a unit price column, a quantity column, and an amount column. In each row of the billing database 106, the billing data to be billed to the company for each month and for each service is registered.

[0042] In the billing month column, the month for which the service amount is billed is stored. In the company code column, the code information of the company to which the service amount is billed is stored. In the cost bearer column, the information of the entity responsible for bearing the service amount (cost) is stored. In the service name column, the name of the service is stored. In the unit price column, the unit price of the service is stored. In the quantity column, the quantity of this service is stored. In the amount column, the total amount (cost), which is the consideration for receiving this service, is stored.

[0043] This billing database 106 is created by the billing management department 230 based on the output information of the contract management department 220. Figure 11 is a flowchart showing the overall application process. Initially, the external human resource management system 1 creates human resource data 100 (step S10). Then, the human resource data acquisition unit 201 of the service application linkage system 2 acquires the human resource data 100 from the external human resource management system 1 (step S11).

[0044] The application data creation unit 202 creates default application data 102 using the human resource data 100 acquired in step S11 and the organization / service combination master information 101, using the services or / and default values set in advance for each company code and organization code (step S12), and registers it in the application database 103.

[0045] The application management unit 210 presents the default application data 102 to the IT administrator (step S13) to enable confirmation of the setting content. The IT administrator determines whether there is a setting change from the default application data 102 (step S14). If there is a setting change from the default application data 102 (Yes), the IT administrator changes the settings of the default application data 102 (step S15). Thereby, the application management unit 210 accepts changes to the cost bearer, service, and setting values, and overwrites and saves them in the application database 103. If there is no setting change from the default application data 102 (No), the process proceeds to step S16.

[0046] In step S16, the data linkage unit 203 creates linkage data from the application database 103, registers it in the linkage database 104, and performs data linkage with the provisioning unit 300 X days before the account activation date. That is, the data linkage unit 203 links the service application data registered in the linkage database 104 to the provisioning unit 300. The provisioning unit 300 acquires the linkage data in the linkage database 104 and stores it in the queue. Note that the X days for determining the timing of data linkage to the provisioning unit 300 may be arbitrarily set by this IT administrator or the like.

[0047] The provisioning unit 300 provisions services based on the linked data registered in the linked database 104 (step S17). On the activation date, the provisioning unit 300 links the email address for account activation and the setting value information to the service provisioning platforms 301 to 303. Each of the service provisioning platforms 301 to 303 activates the account based on the information linked from the provisioning unit 300. After the processing of step S17, the processing of FIG. 11 ends.

[0048] FIG. 12 is a flowchart of the default application data generation process by the linking unit 200. The linking unit 200 acquires the human resource data 100 from the external human resource management system 1 through the human resource data acquisition unit 201 (step S20). The human resource data 100 is data indicating a person and their affiliated organization.

[0049] Next, the linking unit 200 acquires information regarding the affiliated organization of the human resource data 100 from the organization - service combination master information 101 (step S21). Based on the acquired information regarding the affiliated organization, the linking unit 200 creates default application data 102 for each human resource (step S22).

[0050] After the linking unit 200 stores the default application data 102 in the application database 103 (step S23), the processing of FIG. 12 ends. FIG. 13 is a flowchart of the application data update and linked data creation process by the application management unit 210. The application management unit 210 presents the registered default application data 102 to the IT administrator (step S30).

[0051] The IT administrator determines whether there is a setting change from the default application data 102 (step S31). For example, the IT administrator determines whether there is a setting change from the default application data 102 based on whether each user hopes to change the settings. If there is a setting change from the default application data 102 (Yes), the IT administrator changes the settings of the default application data 102 to make it the application data for the service (step S32). Specifically, this includes adding options, changing the cost bearer, etc.

[0052] After that, the application management department 210 overwrites the application data for the service (step S33), and the process proceeds to step S34. On the other hand, if there is no setting change from the default application data 102 in step S31 (No), the process proceeds to step S34. In step S34, when the application management department 210 creates linkage data from the application data for the service and registers it in the linkage database 104 (step S34), the process in FIG. 13 ends.

[0053] FIG. 14 is a flowchart of the linkage process by the data linkage unit 203 to the provisioning unit 300. The data linkage unit 203 outputs the linkage data registered in the linkage database 104 to a CSV (comma separated values) file (step S40). When the data linkage unit 203 performs data linkage of the CSV file to the provisioning unit 300 (step S41), the process in FIG. 14 ends.

[0054] FIG. 15 is a diagram showing screen 4 displayed by the application management department 210. On screen 4, the default application data 102 is displayed in tabular form. The checkbox 41 is for selecting the data in the first row. The checkbox 42 is for selecting the data in the second row. By the IT administrator clicking and selecting any one of the checkboxes 41 and 42 to make the corresponding row editable, this default application data 102 can be arbitrarily edited.

[0055] The configuration and effects of the present invention will be described below.

[0056] [1] A human resource data acquisition unit (201) that acquires the human resource data (100) of each said user from a human resource database (110) in which the correspondence relationship between the user and the organization is registered; An application data creation unit (202) that creates service application data for preparing services for each said user from the human resource data (100) of each said user with reference to the organization / service combination master information in which the default services for the users of the organization are registered; A data linkage unit (203) that links the service application data to a provisioning unit (300) that provisions services for each said user; A service application linkage system (2), characterized by comprising the above.

[0057] Thereby, the provisioning function of the services to be provisioned can be improved, and it is possible to respond to diversified service function requirements. Without individually making service applications for each user, it is possible to make a batch service application for the entire organization.

[0058] [2] Further comprising an application management unit (210) that causes the display unit to display the service application data of each said user and accepts setting changes to the service application data; The data linkage unit (203) transmits the service application data whose settings have been changed by the application management unit (210) to the provisioning unit (300) as linkage data; The service application linkage system (2) according to claim 1, characterized by the above.

[0059] Thereby, it is possible to make a service application that takes into account the circumstances of individual users, without being limited to services uniform for the organization.

[0060] [3] Based on the linkage data in which the correspondence relationship between each of the users and the services prepared for the user is stored, a contract management unit (220) that registers contract data in which each of the users, the services provided to the user, and the cost bearer of the service are stored in a contract database (105), The service application linkage system (2) according to claim 2, further comprising

[0061] This contract database (105) enables easy management of the contract status of each user.

[0062] [4] After the service for each of the users is provisioned, the application management unit (210) changes the settings of the service for the user based on the contract data of the user. The service application linkage system (2) according to claim 3, further comprising

[0063] This contract database (105) enables easy grasp of the current contract status of each user and easy change of service settings.

[0064] [5] A billing management unit (230) that registers billing data for billing the organization for the service consideration based on the contract data in which each of the users, the services provided to the user, and the cost bearer of the service are stored in a billing database (106), The service application linkage system (2) according to claim 3, further comprising

[0065] With this billing database (106), the organization to which each user belongs can know the service consideration in a lump sum and can easily implement the billing process.

[0066] [6] A step in which a human resource data acquisition unit (201) acquires the human resource data (100) of each of the users from a human resource database (110) in which the correspondence relationship between the users and the organization is registered, The application data creation unit (202) creates application data for preparing services for each of the users by referring to the organization-service combination master information in which the default services for the users of the organization are registered. The data linkage unit (203) links the application data to the provisioning unit (300) that provisions the services for each of the users. A service application linkage method characterized by comprising the above.

[0067] Thereby, the provisioning function of the provisioned service can be improved and diversified to meet the diverse service function requirements. It is possible to batch-apply for services for the entire organization without individually applying for services for each user.

[0068] (Modification example) The present invention is not limited to the above-described embodiments and includes various modification examples. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. It is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Further, it is also possible to add, delete, or replace other configurations for a part of the configuration of each embodiment.

[0069] Each of the above configurations, functions, processing units, processing means, etc. may be realized by hardware such as an integrated circuit for a part or all of them. Each of the above configurations, functions, etc. may also be realized by software by a processor interpreting and executing a program for realizing each function. Information such as a program, table, file, etc. for realizing each function can be placed in a recording device such as a memory, hard disk, SSD (Solid State Drive), or a recording medium such as a flash memory card, DVD (Digital Versatile Disk).

[0070] In each embodiment, the control lines and information lines show those considered necessary for explanation, and not necessarily all the control lines and information lines on the product. In reality, it may be considered that almost all components are interconnected.

Explanation of Signs

[0071] 1 Human Resource Management System 2 Service Application Linkage System 3 Service Provision System 110 Human Resource Database 100 Human Resource Data 101 Organization / Service Combination Master Information 102 Default Application Data (Service Application Data) 103 Application Database 104 Linkage Database 105 Contract Database 106 Billing Database 200 Linkage Section 201 Human Resource Data Acquisition Section 202 Application Data Creation Section 203 Data Linkage Section 210 Application Management Section 211 Data Presentation Setting Change / Addition Section 220 Contract Management Section 230 Billing Management Section 300 Provisioning Section 301 - 303 Service Provision Infrastructure 4 Screen 41, 42 Check Box

Claims

1. A human resources data acquisition unit that acquires the human resources data of each said user from a human resources database in which the correspondence relationship between the user and the organization is registered; An application data creation unit that creates service application data for preparing services for each said user from the human resources data of each said user by referring to the organization / service combination master information in which the default services for the users of the organization are registered; A data linkage unit that links the service application data to a provisioning unit that provisions services for each said user; A service application linkage system, characterized by comprising the above.

2. The service application linkage system according to claim 1, further comprising an application management unit that displays the service application data of each said user on a display unit and accepts changes to the settings of the service application data; The data linkage unit transmits the service application data whose settings have been changed by the application management unit to the provisioning unit as linkage data. The service application linkage system according to claim 1, characterized by the above.

3. A contract management unit that registers contract data in which the correspondence relationship between each said user and the service prepared for the user, the service provided to the user, and the cost bearer of the service are stored in a contract database based on the linkage data in which the correspondence relationship between each said user and the service prepared for the user is stored; The service application linkage system according to claim 2, further comprising the above.

4. The service application linkage system according to claim 3, characterized in that the application management unit changes the settings of the service for the user based on the contract data of the user after the service for each said user has been provisioned. The service application linkage system according to claim 3, characterized by comprising the above.

5. A billing management unit that registers billing data for billing the organization for the consideration of the service in a billing database based on the contract data in which the correspondence relationship between each said user, the service provided to the user, and the cost bearer of the service are stored; The service application linkage system according to claim 3, further comprising the above.

6. The step of the human resources data acquisition unit acquiring the human resources data of each said user from a human resources database in which the correspondence relationship between the user and the organization is registered; The step of the application data creation unit creating application data for preparing services for each said user by referring to the organization / service combination master information in which the default services for the users of the organization are registered; The step of causing the data linking unit to link the application data to a provisioning unit that provisions services for each of the users; A service application linking method, characterized by comprising the above.

Images