WO2025109902A1 - Accommodation transaction proposal system - Google Patents

Abstract

A system of the present invention stores accommodation range information for managing KPIs of a plurality of users, parameters associated with the KPIs, and the accommodation range of the parameters, and policy management information for managing policies for improving one or more KPIs. The system determines, for a KPI group which includes a designated KPI and a KPI related to the designated KPI, a policy group for improving the designated KPI and other KPIs in the KPI group by using the accommodation range of the parameters as a constraint, creates a policy combination that includes the determined policy group and satisfies a preset condition, and presents information on the policy combination to a user related to the KPI group.

Description

Loan transaction proposal system Incorporation by Reference

This application claims priority to Japanese Patent Application No. 2023-196722, filed on November 20, 2023, the contents of which are incorporated herein by reference.

The present invention relates to generating measures to improve KPIs.

As a related art of the present application, there is JP2018-195308A. This document discloses that "the system comprises a module for collecting and merging data from industrial processing units and pre-processing the data to remove outliers and missing values. Furthermore, the system generates customized output from the data to identify important variables that affect a given process performance indicator. The system also builds a predictive model for the key performance indicators including important features and determines operating points for optimizing the key performance indicators with minimal user intervention. In particular, the system receives input from the user about the key performance indicators to be optimized and informs the user of outputs from various steps in the analysis that help the user effectively manage the analysis and make appropriate operating decisions."

Social issues such as an increase in unpredictable risks and environmental problems are on the rise. In order to maintain the resilience of social infrastructure systems and solve social issues such as carbon neutrality, multiple stakeholders must accommodate their individual circumstances, build mutually cooperative relationships, and aim to increase overall value.

Patent Document 1 shows a technique for adjusting the parameters of other processes in order to improve the KPIs of a particular process, but does not support mutual cooperation between stakeholders. Therefore, a system that supports stakeholders in sharing their individual circumstances and cooperating with each other is desirable.

One aspect of the present invention is a system for proposing a trade of a loan, the system including a processor and a memory, the memory storing loan range information for managing KPIs, parameters associated with the KPIs, and loan ranges of the parameters for multiple users, and policy management information for managing policies for improving one or more KPIs, the processor acquires from a user a designated KPI to be improved and information on the loan range of the parameters associated with the designated KPI, and for a KPI group including a KPI related to the designated KPI, determines a group of policies for improving the designated KPI and other KPIs of the KPI group by referring to the policy management information, with the loan range of the parameters associated with the KPIs of the KPI group as a constraint, creates a combination of policies that satisfies a preset condition in the group of policies, and presents information on the combination of policies to a user related to the KPI group to obtain a response of approval or disapproval of the combination of policies.

One aspect of the present invention is to help stakeholders share their individual circumstances and cooperate with each other.

Configurations and effects other than those described above will become clear from the description of the embodiments below.

FIG. 1 is a block diagram showing an example of the configuration of a system according to an embodiment of the present specification. FIG. 2 is a block diagram for explaining the relationship between the processing modules of the business-to-business transaction device. 13 shows an example of a flowchart of a KPI relationship model generation process. 13 shows an example of the configuration of a KPI and related indicator performance data table. 13 shows an example of the configuration of a KPI and related indicators relationship analysis table. 1 shows an example of the configuration of a KPI relationship analysis table. 13 shows an example of a flowchart of a KPI relationship model generation process. 13 shows an example of a screen for a user to register the flexibility range of a parameter associated with the KPI. 13 shows an example of a flowchart of a process for registering a loan target and a loan range in a loan target/range specification process. 13 shows an example of the configuration of a facility range table for managing information on facility targets and facility ranges. 13 shows an example of a flowchart of a KPI group creation process. 13 shows an example of the configuration of a KPI group table. 13 shows an example of an input screen for a user to generate a loan request. 13 shows an example of a flowchart of an information acquisition process in the loan target/range specification process. 13 shows an example of a flowchart of a policy generation process in the loan transaction plan generation process. 13 shows an example of the structure of a policy table. 13 shows an example of a flowchart of a policy combination generation process in the loan transaction plan generation process. 13 shows an example of the structure of a policy combination table. 13 shows an example of the configuration of a policy combination KPI comprehensive evaluation table. 13 shows an example of a flowchart of a credit transaction negotiation process by a transaction proposal notification/reply reception program. 13 shows an example of a screen for presenting to a user policies corresponding to the user in a policy combination and requesting the user to respond as to whether or not to accept the presented policies.

In the following, where necessary for convenience, the description will be divided into multiple sections or examples, but unless otherwise specified, they are not unrelated to each other, and one is a partial or complete modification, detail, supplementary explanation, etc., of the other. Furthermore, in the following, when the number of elements (including the number, numerical value, amount, range, etc.) is mentioned, it is not limited to that specific number, and may be more or less than the specific number, except when otherwise specified or when it is clearly limited in principle to a specific number.

The system or device in this specification may be a physical computer system (one or more physical computers) or a system built on a group of computing resources (multiple computing resources) such as a cloud infrastructure. The computer system or group of computing resources may include one or more interface devices (including, for example, a communication device and an input/output device), one or more storage devices (including, for example, a memory (main memory) and an auxiliary storage device), and one or more arithmetic devices.

When a function is realized by a program being executed by a computing device, the defined processing is performed using a storage device and/or an interface device, etc., as appropriate, and therefore the function may be at least a part of one or more computing devices. Processing described using the function as the subject may be processing performed by a system including one or more computing devices.

The program may be installed from a program source. The program source may be, for example, a program distribution computer or a computer-readable storage medium (for example, a computer-readable non-transitory storage medium). The description of each function is an example, and multiple functions may be combined into one function, or one function may be divided into multiple functions.

FIG. 1 is a block diagram showing an example of the configuration of a system according to one embodiment of this specification. The business-to-business loan transaction system 1 includes a business-to-business loan transaction device 10 and an external data storage device 15 that is accessed by the business-to-business loan transaction device 10 via a network. Companies are stakeholders. Stakeholders refer to interested parties, and include not only companies, but also any of a variety of groups and organizations.

The inter-company lending transaction device 10, for example, manages resource or constraint lending transactions between stakeholders in the system to achieve a more appropriate combination of KPIs in the supply chain.

The inter-company financing transaction device 10 includes a CPU 101, which is a calculation device, a memory 102, which is a main storage device, a communication device 103, and a program storage device 104, which is an auxiliary storage device. The calculation device may be configured as desired, and may include one or more processors (including cores), such as a CPU or a microprocessor.

The program storage device 104 stores a KPI relationship model generation module 106, a loan target/scope identification module 107, a loan transaction proposal generation module 108, a loan transaction negotiation module 109, and a data input/output module 110.

The KPI relationship model generation module 106 includes a KPI relationship model generation program 111. The loan target/scope specification module 107 includes a loan target/scope specification program 112. The loan transaction proposal generation module 108 includes a measure generation program 113 and a measure combination generation program 114. The loan transaction negotiation module 109 includes a transaction proposal notification/response reception program.

The CPU 101 operates as a specific functional unit by executing processes according to the programs stored in the program storage device 104. In the following explanation, the processes may be explained with the programs (including modules) as the subject, but since the programs are executed by the CPU 101 to perform the specified processes while appropriately using storage resources (e.g., memory) and/or interface devices (communication ports), the subject of the processes may also be explained as the CPU 101 or the inter-company financing transaction device 10 that includes the CPU 101.

The data storage device 15 stores the database 151. The data storage device 15 is composed of one or more storage devices. Examples of storage devices include devices that include non-volatile storage media such as HDDs (Hard Disk Drives) and SSDs (Solid State Drives), and may also be devices that include volatile storage media such as DRAMs.

FIG. 2 is a block diagram for explaining the relationship between the processing of the modules of the business-to-business loan transaction device 10. The data input/output module 110 executes data input/output processing 205. The data input/output module 110 receives input data from the terminal device 18 of the stakeholder company, and transmits output data to the terminal device 18. FIG. 2 shows one terminal device 18 as an example, but the terminal device 18 of each stakeholder is connected to the business-to-business loan transaction system 1 via a network. The terminal device 18 may be a device that serves as an interface for a user to input and output data, or may be a device for accessing a device that holds stakeholder data.

The data input/output module 110 communicates with other functional units within the inter-company loan transaction system 1, and transmits and receives necessary data. The data input/output module 110 communicates with the KPI relationship model generation module 106, the loan target/scope identification module 107, the loan transaction proposal generation module 108, and the loan transaction negotiation module 109, and also registers information in the database 151 and reads information from it.

The KPI relationship model generation module 106 executes the KPI relationship model generation process 201 based on information from the stakeholder (user) received via the data input/output module 110. The KPI relationship model generation module 106 stores the generated KPI relationship model in the database 151 and passes it to the loan transaction proposal generation module 108.

The loan transaction plan generation module 108 executes the loan transaction plan generation process 202. The loan transaction plan generation module 108 transmits and receives information to and from the loan target/range identification module 107 and the data input/output module 110. The loan target/range identification module 107 executes the loan target/range identification process 203. The loan target/range identification module 107 transmits and receives information to and from the loan transaction plan generation module 108 and the data input/output module 110. The loan transaction negotiation module 109 executes the loan transaction negotiation process 204. The loan transaction negotiation module 109 transmits and receives information to and from the data input/output module 110.

First, the generation of the KPI relationship model will be explained. The KPI relationship model generation program 111 generates a KPI relationship model in accordance with user input or based on the analysis of data input by the user. The KPI relationship model indicates whether there is a relationship between KPIs and whether the increase/decrease relationship is positive or negative.

If the increase or decrease in the target KPI and the related KPIs is the same, the relationship between them is positive, and if the opposite is true, the relationship is negative. In other words, in a positive relationship, the related KPIs increase as the target KPI increases, and the related KPIs decrease as the target KPI decreases. On the other hand, in a negative relationship, the related KPIs decrease as the target KPI increases, and the related KPIs increase as the target KPI decreases.

An example of a method for generating a KPI-relationship model will now be described. FIG. 3 shows an example of a flowchart of the KPI-relationship model generation process 201. The KPI-relationship model generation program 111 acquires performance data of KPIs and related indicators from the database 151 (S11). The performance data of KPIs and related indicators is received from the outside by the data input/output module 110 and stored in the database 151.

FIG. 4 shows an example of the configuration of the KPI and related indicator performance data table 310. The KPI and related indicator performance data table 310 manages performance data on time variations of indicators for all stakeholders (all target users). The managed indicators include KPIs and indicators other than KPIs. The KPIs are specified in advance by the user.

In the configuration example shown in FIG. 4, the KPI and related indicator performance data table 310 includes an indicator ID column 311, an indicator name column 312, a timestamp column 313, and a value column 314. The indicator ID column 311 shows an ID that identifies each indicator, and the indicator name column 312 shows the name of each indicator. In this example, KPIs are given names consisting of "KPI" and a number, and indicators other than KPIs are given names consisting of "indicator" and a number. The timestamp column 313 shows the time in the time variation of the indicator, and the value column 314 shows the value of each indicator at each time.

Returning to FIG. 3, the KPI relationship model generation program 111 constructs a relationship model between the KPI and related indicators, and identifies related indicators that affect the fluctuation of the KPI (S12). Related indicators are KPIs or indicators other than KPIs. The related indicators for each KPI may be specified by the user, and the KPI relationship model generation program 111 may analyze performance data for the KPIs and related indicators and identify the related indicators for each KPI from the analysis results. Note that various methods are known for evaluating the relevance between two time-varying variables, and any method may be used.

FIG. 5 shows an example of the configuration of the KPI and related indicator relationship analysis table 320. The KPI and related indicator relationship analysis table 320 shows indicators (including KPIs and non-KPIs) related to each KPI. As described above, the KPI and related indicator relationship analysis table 320 can be created by a user or by the KPI relationship model generation program 111. The KPI and related indicator relationship analysis table 320 may be temporarily stored in the memory 102, or may be saved in the database 151.

In the example shown in FIG. 5, the KPI and related indicator relationship analysis table 320 includes an indicator ID column 321, an indicator name column 322, a related indicator ID column 323, and a relationship column 324. The indicator ID column 321 and the indicator name column 322 indicate the ID and name of the target indicator. These are the same as those in the KPI and related indicator performance data table 310. The related indicator ID column 323 indicates the ID of the indicator related to the target indicator. Note that one indicator can be related to one or more indicators. The relationship column 324 indicates whether the relationship between the two indicators is positive or negative.

Returning to FIG. 3, the KPI relationship model generation program 111 further identifies whether there is a relationship between KPIs and whether the relationship between KPIs is positive or negative based on whether the KPI fluctuation is similar or different relative to the fluctuation of the indicator (S13). The related indicator of a KPI is a KPI or an indicator other than a KPI (non-KPI indicator). If the related indicator is a KPI, the positive or negative relationship between them is determined. A positive relationship is a relationship in which two related KPIs both increase and decrease, and a negative relationship is a relationship in which two KPIs show opposite changes. In a positive relationship, an increase in one KPI leads to an increase in the other KPI, and a decrease in the other KPI leads to a decrease in the other KPI. In a negative relationship, an increase in one KPI leads to a decrease in the other KPI, and a decrease in one KPI leads to an increase in the other KPI.

When a KPI and a non-KPI indicator are associated, the presence or absence of a relationship between the two KPIs via the non-KPI indicator is identified. The method of identifying the presence or absence of a relationship between KPIs is, for example, to determine that the two KPIs have a positive relationship if the indicator IDs of the associated indicators match at least a certain percentage of positive and negative when the related indicators are extracted. Alternatively, if the indicator IDs match at a certain percentage, but the positive and negative relationships do not match, it can be determined that the two KPIs have a negative relationship.

Next, the KPI relationship model generation program 111 saves the presence or absence of relationships between KPIs and the positive or negative relationship in the database 151 (S14). Figure 6 shows an example of the configuration of the KPI relationship analysis table 330. The KPI relationship analysis table 330 shows information on the KPI relationship model and manages the relationships between KPIs. The KPI relationship analysis table 330 manages the presence or absence of relationships between KPIs and the positive or negative relationship. KPI pairs not shown in the table have no relationship. As described above, the KPI relationship analysis table 330 is stored in the database 151.

In the example configuration shown in FIG. 6, the KPI relationship analysis table 330 includes an indicator ID column 331, an indicator name column 322, an indicator ID column 333, a KPI name column 334, and a relationship column 335. The indicator ID column 331 and the indicator name column 322 indicate the indicator ID and name of one of the two related KPIs. The indicator ID column 333 and the KPI name column 334 indicate the indicator ID and name of the other of the two related KPIs. The relationship column 335 indicates whether the relationship between the two KPIs is positive or negative.

Next, another example of a method for generating a KPI relationship model will be described. FIG. 7 shows an example of a flowchart of the KPI relationship model generation process 201. The KPI relationship model generation program 111 acquires KPI performance data (S21). Here, the format of the KPI performance data is the same as that of the KPI and related indicator performance data table 310, but the indicators are all KPIs.

Next, the KPI relationship model generation program 111 analyzes the correlation between the KPIs (S22), and identifies whether there is a relationship between the KPIs and whether the relationship is positive or negative based on the correlation (S23). This generates the KPI relationship analysis table 330. The KPI relationship model generation program 111 saves the KPI relationship analysis table 330, which indicates whether there is a relationship between the KPIs and whether the relationship is positive or negative, in the database 151 (S24).

Next, the process 203 for identifying the target and range of loans will be explained. The process 203 for identifying the target and range of loans will include a process for registering the target and range of loans in response to input from the stakeholder (user), and a process for acquiring information on specific KPIs from the registered information. First, the process for registering the target and range of loans in response to user input will be explained. Here, the process for registering the target and range of loans will be explained, and the process for acquiring information on the possible range of loans will be explained later.

FIG. 8 shows an example of a screen for a user to register the flexible range of a parameter (also called an index, which can also be a KPI) associated with the KPI. In the following, for example, the display device of the terminal device 18 displays the flexible range registration screen. The flexible range registration screen includes a field 41 for inputting the target KPI, and a field for specifying the flexible range associated with the KPI.

The fields for specifying the flexible range specifically include a field 42 for inputting flexible target parameters associated with the target KPI, a field 43 for inputting the flexible range of each parameter, and a field 44 for inputting the validity period of each flexible range. The target parameters are parameters that affect changes in the target KPI. The flexible range depends on the target parameter and can be, for example, a numerical range or a value representing a selectable item.

In the example shown in FIG. 8, a flexible range of two parameters is set for one KPI. The number of parameters associated with a KPI can be one or more. Information is entered into these fields by the user on the terminal device 18. When the register button 45 is selected, the input information is sent from the terminal device 18 to the inter-company flexible transaction device 10 together with the user ID.

FIG. 9 shows an example of a flowchart of the process of registering the loan target and loan range in the loan target/range specification process 203. The process of registering the loan target and loan range can be executed at any time, and may be registered periodically or in response to a loan request, which will be described later. For example, the loan target/range specification program 112 receives information on the loanable target and range from the user via the terminal device 18.

For example, as shown in FIG. 8, the accommodation target/range identification program 112 receives information on the target KPI, the accommodation target parameters associated with the target KPI, the accommodation range, and the validity period from the user via the terminal device 18 along with the user ID (S31). Next, the accommodation target/range identification program 112 saves a data set including the user ID, the target KPI, the target parameters, the accommodation range of the target parameters, and the validity period in the database 151 (S32).

FIG. 10 shows an example of the configuration of a lending range table 340 that manages information on lending targets and lending ranges. The lending range table 340 is stored in the database 151. In the example configuration of FIG. 10, the lending range table 340 includes a user ID column 341, an indicator ID column 342, a KPI name column 343, a parameter column 344, a lending range column 345, and a validity period column 346.

The user ID column 341 indicates an ID that identifies the user who owns the lending target. The indicator ID column 342 indicates the indicator ID of the KPI of the lending target. The KPI name column 343 indicates the name of the KPI with which the lending range is associated. The parameter column 344 indicates the parameter of the lending target. The lending range column 345 indicates the lendable range of the lending target parameter. The validity period column 346 indicates the validity period of the lending target. One or more lending target parameters are defined for one KPI. The validity period may be omitted.

Next, the process of generating KPI groups will be explained. The KPI group generation process generates KPI groups from KPIs that are related to each other. Figure 11 shows an example of a flowchart of the KPI group creation process. Here, it is assumed that KPI groups are generated by the policy generation program 113.

The policy generation program 113 obtains the KPI relationship analysis table 330 from the database 151 (S35). Next, the policy generation program 113 analyzes the relationships between KPIs in the KPI relationship analysis table 330, creates KPI groups, and saves the information in the database 151 (S36).

A KPI group is a group consisting of KPIs that are directly or indirectly related. The KPI relationship analysis table 330 shows pairs of KPIs that are related to each other. The policy generation program 113 includes both related KPI pairs, where at least one of the two related KPI pairs is related, in the same KPI group. For example, if one related KPI pair is composed of KPI1 and KPI2, and the other related KPI pair is composed of KPI1 and KPI3, KPI1, KPI2, and KPI3 are included in the same KPI group.

The policy generation program 113 stores information about each generated KPI group in the KPI group table 350, and saves the KPI group table 350 in the database 151. Figure 12 shows an example of the configuration of the KPI group table 350. The KPI group table 350 manages the information about the KPI groups.

In the configuration example shown in FIG. 12, the KPI group table 350 indicates the KPI group to which each related KPI pair belongs. It includes a group ID column 351, an indicator ID column 352, a KPI name column 353, an indicator ID column 354, a KPI name column 355, and a relationship column 356. The group ID column 351 indicates an ID that identifies the KPI group. The indicator ID column 352 and the KPI name column 353 indicate the indicator ID and name of one of the two related KPIs.

The indicator ID column 354 and KPI name column 355 show the indicator ID and name of the other KPI of the two related KPIs. The relationship column 336 shows whether the relationship between the two KPIs is positive or negative. By forming a KPI group with KPIs that have an influencing relationship as described above, it becomes possible to propose more appropriate measures. Note that KPI groups may also be formed by other methods.

Next, the loan transaction plan generation process 202 will be described. The loan transaction plan generation process 202 includes a process for generating measures and a process for generating a combination of measures. First, the policy generation process will be described. The policy generation process is executed by the policy generation program 113 in response to a loan request from a user.

FIG. 13 shows an example of an input screen for a user to generate a loan request. The loan request input screen is a screen for inputting information on the target KPI that the user wishes to improve, the loanable parameters of that KPI, and the loanable range. For example, the loan target/range identification program 112 transmits the information on this screen to the terminal device 18 in response to a request from the user.

In the example screen of FIG. 13, the loan request input screen includes a target KPI input field 51 and a field indicating the loanable range. The field indicating the loanable range includes a target parameter input field 52, a loan range input field 53, and a validity period field 54. The target parameters are related to the target KPI and can affect the target KPI.

The user may be able to input new information on the lending range of the target KPI, that is, the target parameters and lending range, and the lending range information may be obtained from the lending range table 340 and displayed. For example, in response to the user's designation of a target KPI, the lending target/range identification program 112 obtains information on the lending range of parameters related to the KPI of the user ID from the lending range table 340. In other words, it obtains information on the target parameters, lending range, and validity period. The lending target/range identification program 112 displays information on the lending range of the target parameters. The user may or may not be able to update the target parameters, lending range, and validity period on the lending request input screen.

FIG. 14 shows an example of a flowchart of the information acquisition process in the loan target/range identification process 203. The loan target/range identification program 112 acquires the target user ID and the name or ID of the KPI from the terminal device 18 (S47). The loan target/range identification program 112 acquires information on the loan target parameters, loanable range, and expiration date corresponding to the acquired user ID and KPI from the loan range table 340 in the database 151 (S48).

The target KPI is the objective variable of the optimization problem described below. The flexible parameters and flexible range are the constraints of the optimization problem described below. Figure 13 shows an example of specifying one KPI as the target of a flexibility request, but the user can specify multiple KPIs and their flexible ranges at the same time.

FIG. 15 shows an example of a flowchart of the policy generation process in the credit transaction proposal generation process 202. The policy generation program 113 sequentially selects one KPI from one or more target KPIs specified by the user, and executes the process shown in FIG. 15.

First, the policy generation program 113 obtains the KPI group of the selected target KPI (S41). Specifically, the policy generation program 113 obtains information on all KPIs in the KPI group to which the target KPI belongs from the KPI group table 350. Next, the policy generation program 113 obtains the flexibility range corresponding to the KPI group (S42).

Specifically, the policy generation program 113 obtains information on the loan range including the loan target parameters of all KPIs in the KPI group and the loan range from the loan range table 340. The loan range information obtained from the loan range table 340 is information on records whose effective period includes the time when the policy is to be executed. The time when the policy is to be executed may be specified by the user, for example, or may be the time when this process is executed.

Next, the measure generation program 113 sets an optimization problem in which one or more KPIs including the target KPI are used as objective variables to search for measures within the flexibility range associated with each of the KPIs constituting the KPI group (S43), and calculates one or more solutions to the optimization problem (S44). The explanatory variables of the optimization problem for each KPI are set in advance, and the flexibility range of the KPI group can be a constraint on the variables of the optimization problem. The optimal value of one or more KPIs of the KPI group including the target KPI is searched for. A KPI other than the specified target KPI may be included in the objective variable. The measure generation program 113 saves the output measures and the KPI values at the time of implementing the measures in the database 151. Note that measures may also be determined by other methods.

FIG. 16 shows an example of the configuration of the policy table 360. The policy table 360 manages information about policies generated by the policy generation program 113. The policy table 360 is stored in the database 151. In the example configuration of FIG. 16, the policy table 360 includes a policy ID column 361, a user ID column 362, an index ID column 363, a KPI name column 364, a parameter column 365, a policy column 366, a KPI estimate column 367, and an execution column 368.

The measure ID column 361 indicates an ID that identifies the generated measure. The user ID column 362 indicates the ID of the user who should implement the measure, and the generated measure is presented to that user. The indicator ID column 363 indicates the ID of the target KPI used as the objective variable in creating the measure. The KPI name column 364 indicates the name of the KPI indicated by the indicator ID. The parameter column 365 indicates the target parameter associated with the target KPI. One measure may include one or more actions, that is, one or more parameters may be specified.

The measure column 366 indicates the range of values of the target parameter specified by the measure. For example, the measure can specify a specific value for the target parameter or a range of different possible values. The KPI estimate column 367 indicates the estimated value of the target KPI by the measure. For measures that have been implemented, the actual value may be stored instead of an estimate. The execution column 368 indicates whether the measure has been implemented. An implemented measure indicates that it has already been implemented.

Next, the policy combination generation process in the loan transaction plan generation process 202 will be described. FIG. 17 shows an example of a flowchart of the policy combination generation process in the loan transaction plan generation process 202. The policy combination generation program 114 identifies the target user, target KPI, and target period, and obtains a group of policies (implemented/not yet implemented) (S51).

The target users are all users related to the target KPI, and the target KPI is one or more KPIs specified by the target user for policy generation and other KPIs of the KPI group to which they belong. The target period is set in advance and is a predetermined period that includes the execution of this process (present). The target period may be composed of, for example, the present and either the past and future from the present, or either one of the predetermined periods.

The policy group is a group of policies generated for each of the target KPIs specified by the target user and the KPIs of the KPI groups to which they belong, and is stored in the policy table 360. The policy group obtained can include policies that have been proposed and executed in the past, policies that have been proposed in the past but not executed, and policies that are being proposed this time but not executed.

Next, the policy combination generation program 114 checks the overlap of the transferable parameters and value ranges between policies in each time period in the present and future in the group of policies acquired above, and identifies policies that cannot be executed simultaneously in each time period (S52). Each policy combination includes at least one of the policies created in response to a current request from the user. If two policies have a common target parameter and the value ranges of the common parameters of the two policies do not overlap even partially (including one numerical value), it is determined that the policies cannot be executed simultaneously.

The policy combination generation program 114 creates policy combinations from policies that can be executed simultaneously in each time period, both in the present and in the future. Policy combinations for each time period are sometimes called policy combinations for each time period or partial policy combinations. One or more policy combinations are generated for each time period.

Furthermore, the policy combination generation program 114 selects one policy combination from each time period to construct a policy combination for the target period consisting of a series of partial policy combinations. This may be called a policy combination for the target period, a policy combination for the target period, or an overall policy combination. The policy combination generation program 114 can generate multiple overall policy combinations consisting of different partial policy combinations.

Next, the policy combination generation program 114 acquires the achievement conditions for the overall evaluation of the KPI group (S54). The achievement conditions for the overall evaluation of the KPI group are set in advance and indicate the conditions that the values of the target KPI group obtained by each overall policy combination must satisfy. The target KPI group may be a KPI group that constitutes the same KPI group as the user-specified KPI, or it may be a collection of multiple KPI groups related to the user involved in the KPI group.

The conditions for achieving the overall evaluation of KPIs, for example, stipulate the conditions for individual KPIs and the relationships between KPIs within the target period. The conditions for an individual KPI can, for example, specify the acceptable range of values for that KPI resulting from a combination of measures in the current and future target period.

The conditions for the relationship between KPIs can be specified from the perspective of fairness between KPIs of different users. This makes it possible to maintain a high level of KPIs overall while realizing fairness between KPIs of users. For example, the policy combination generation program 114 calculates an evaluation value for each user from at least some of the values of the KPIs for the target period according to a specified function. At this time, the past values of each of the user's KPIs are obtained from the KPI and related indicator performance data table 310, and the current and future values are obtained from the policy table 360. One or more evaluation values may be defined for each user.

The achievement conditions, for example, define the conditions that must be met by the evaluation values calculated from at least some of the KPIs of each user. The policy combination generation program 114 compares the evaluation values between users and determines whether the comparison results meet the achievement conditions for the overall evaluation of the KPI group. For example, it may be required that the difference in evaluation values between each user pair is within a pre-specified range.

The evaluation value may be, for example, a weighted average of the users' KPIs in the target period, and the percentage difference in evaluation values between users may be required to be within a specified value; for example, the weighted average may be calculated using the time average of each KPI in the target period. The period for which the evaluation value is calculated may be the entire target period or a portion of the target period. The weighted average may be calculated for certain KPIs, which may be a portion of the KPIs of any user.

The policy combination generation program 114 searches for an overall policy combination that satisfies the achievement conditions of the acquired KPI group overall evaluation (S54). Furthermore, the policy combination generation program 114 outputs the overall policy combination that satisfies the achievement conditions to the policy combination table 370 and stores it in the database 151 (S55).

FIG. 18 shows an example of the configuration of a policy combination table 370. The policy combination table 370 includes a policy combination ID column 371, a policy ID column 372, a user ID column 373, an index ID column 374, a KPI name column 375, a parameter column 376, a policy column 377, and an execution column 378.

The measure combination ID column 371 indicates an ID that identifies the measure combination. The measure ID column 372 indicates an ID that identifies the measures included in each measure combination. The user ID column 373 indicates the ID of the target user of the measure. The indicator ID column 374 indicates the indicator ID of the KPI that is expected to be improved by the measure. The KPI name column 375 indicates the name of the KPI indicated by the indicator ID. The parameter column 376 indicates the parameter associated with the KPI, and the measure column 377 indicates the range of parameter values specified by the measure. The execution column 378 indicates whether the measure has been executed.

FIG. 19 shows an example of the configuration of a policy combination KPI overall evaluation table 380. The policy combination KPI overall evaluation table 380 includes a policy combination ID column 381, a user ID column 382, a KPI evaluation value ID column 383, and a KPI evaluation value column 384.

The policy combination ID column 381 indicates an ID that identifies the policy combination. The user ID column 382 indicates the ID of the target user of the policy combination. The KPI evaluation value ID column 383 indicates the ID of the KPI evaluation value for the target user of the policy combination. The KPI evaluation value column 384 indicates the value of the KPI evaluation value.

Next, the loan transaction negotiation process 204 will be described. Figure 20 shows an example of a flowchart of the loan transaction negotiation process 204 by the transaction proposal notification/answer reception program 115. The transaction proposal notification/answer reception program 115 inquires of the user related to the policy combination as to whether or not the policy combination is acceptable, and obtains the response. This makes it possible to propose a policy combination that is acceptable to the related user.

The transaction proposal notification/answer reception program 115 acquires a group of policy combinations and KPI evaluation values for the policy combinations from the policy combination table 370 and the policy combination KPI overall evaluation table 380 (S61). The transaction proposal notification/answer reception program 115 identifies the policy combination with the highest designated evaluation value (S62). The calculation method for the designated evaluation value is specified in advance and is determined based on the value of the target KPI group. For example, the designated evaluation value may be the total value of the weighted average of the users' KPIs in the target period, or a statistical value (e.g., the reciprocal of the average value) obtained from the difference in the weighted average of the KPIs between users. The weighted average may be calculated for a portion of the users' KPIs.

The transaction proposal notification/answer reception program 115 notifies all users who are the targets of the measures included in the measure combination of the measures for that user (S63). Specifically, the transaction proposal notification/answer reception program 115 notifies the user whose execution column 378 in the measure combination table 370 indicates "not executed" and whose user ID column 373 indicates information about the measure indicated in the measure ID column 372 of the same record. Users of measures that have been executed may also be notified.

The transaction proposal notification/response receiving program 115 receives responses from the users regarding whether or not to allow the execution of each measure (S64). The transaction proposal notification/response receiving program 115 determines whether all users have responded with permission for execution (S65).

If any user rejects the proposed measures (S65: NO), the transaction proposal notification/response reception program 115 deletes the target combination of measures from the candidates (S66). The flow then returns to step S62.

If all users have responded that they wish to allow execution (S65: YES), the transaction proposal notification/response reception program 115 sends a request to each related user to execute the proposed measures (S67). The transaction proposal notification/response reception program 115 saves information about the combination of measures to be executed in the performance information (S68).

FIG. 21 shows an example of a screen for presenting to a user measures that correspond to that user in a measure combination and requesting the user's response as to whether or not to approve the presented measures. This makes it possible to efficiently obtain a response from the user as to whether or not to approve the implementation. The measure presentation screen includes a section 71 showing the target KPI, a section 72 showing the target parameters, and a section 73 showing the measures. It also includes a section 74 showing the overall KPI of the presented user and other users involved in the measure combination, and a graph 75 showing the change in the overall KPI estimates for the presented user and other users involved in the measure combination during the target period.

The target KPI is the target KPI of the measure for which permission to execute is being sought, and is the KPI of the user. The target parameter is a parameter of the target KPI, and the measure indicates the range of values for that parameter. The overall KPI estimate is a value calculated from the user's KPIs using a pre-defined method.

The overall KPI estimate may be, for example, a value obtained from the achievement conditions in the loan transaction proposal generation process 202 (step S53), or a value calculated from a specified evaluation value (step S62) that is referenced when presented to the user in the loan transaction negotiation process 204. As an example, a weighted average of the users' KPIs may be used. This makes it possible to know the relationship of interests between users. The user can respond with buttons 76 and 77 as to whether or not to approve the implementation of the proposed measures.

The present invention is not limited to the above-described embodiments, but includes various modified examples. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and are not necessarily limited to those having all of the configurations described. It is also possible to replace 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. It is also possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

Furthermore, each of the above configurations, functions, processing units, etc. may be realized in hardware, for example by designing some or all of them as an integrated circuit. Furthermore, each of the above configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the programs, tables, files, etc. that realize each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card or SD card.

Furthermore, the control lines and information lines shown are those considered necessary for the explanation, and do not necessarily show all control lines and information lines on the product. In reality, it can be assumed that almost all components are interconnected.

Claims (8)

A credit transaction proposal system,
A processor;
A memory,
The memory includes:
KPIs, parameters associated with the KPIs, and flexibility range information for managing the flexibility range of the parameters for a plurality of users;
policy management information for managing policies for improving one or more KPIs;
The processor,
Acquire from a user a designated KPI to be improved and information on a flexible range of parameters associated with the designated KPI;
For a KPI group including a KPI related to the designated KPI, determining a group of measures for improving the designated KPI and other KPIs of the KPI group by referring to the measure management information, with the flexibility range of the parameter associated with the KPI of the KPI group as a constraint;
A combination of measures is created that satisfies a preset condition in the group of measures.
A trade proposal system that presents information on the combination of measures to a user related to the KPI group in order to obtain a response as to whether or not the combination of measures is acceptable. The system for proposing a credit transaction according to claim 1,
The memory stores KPI relationship information for managing relationships between a plurality of KPIs;
The KPI group is made up of KPIs that the KPI-related information indicates have a relationship with, in this flexibility transaction proposal system. The system for proposing a credit transaction according to claim 1,
The processor determines the group of measures by solving an optimization problem having as objective variables at least a portion of KPIs in the KPI group, including the specified KPI. The system for proposing a credit transaction according to claim 1,
The processor creates the combination of measures so that measures having different values of a common parameter are not executed simultaneously. The system for proposing a credit transaction according to claim 1,
The processor generates a combination of multiple measures that satisfies the preset condition,
When a negative response to a proposed combination of measures is received from any user of the KPI group, the system re-presents information on another combination of measures selected from the multiple combinations of measures to the user of the KPI of the KPI group. The system for proposing a credit transaction according to claim 2,
The memory stores performance data relating to the plurality of KPIs,
The processor analyzes the relationships between the multiple KPIs in the performance data and creates the KPI relationship information. The system for proposing a credit transaction according to claim 1,
The predetermined condition defines a relationship that must be satisfied by an evaluation value calculated from at least a portion of KPIs of each user of the policy combination. 1. A method for a system offering a credit transaction, comprising:
The system comprises:
KPIs, parameters associated with the KPIs, and flexibility range information for managing the flexibility range of the parameters for a plurality of users;
policy management information for managing policies for improving one or more KPIs;
The method further comprises the steps of:
Acquire from a user a designated KPI to be improved and information on a flexible range of parameters associated with the designated KPI;
For a KPI group including a KPI related to the designated KPI, determining a group of measures for improving the designated KPI and other KPIs of the KPI group by referring to the measure management information, with the flexibility range of the parameter associated with the KPI of the KPI group as a constraint;
A combination of measures is created that satisfies a preset condition in the group of measures.
A method for presenting information about the combination of measures to a user associated with the KPI group to obtain a response indicating whether or not the combination of measures is acceptable.

Images