Transportation planning management device and transportation planning management method

The transportation plan management device addresses the challenge of identifying and addressing KPI non-compliance by analyzing causal relationships, allowing for improved transportation plan revisions that meet threshold requirements.

JP2024167641APending Publication Date: 2024-12-04HITACHI LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023083853
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-22
Publication Date
2024-12-04

AI Technical Summary

Technical Problem

Conventional transportation plan evaluation methods fail to identify the reasons why key performance indicators (KPIs) do not meet required thresholds, making it difficult to revise transportation plans effectively, especially in complex scenarios with numerous variables, placing a heavy burden on users.

Method used

A transportation plan management device and method that analyzes causal relationships between KPIs and variables, identifies inconsistent KPIs, determines their causes, and generates revised transportation plans to meet threshold requirements using a processor, memory, and storage section with functional units for KPI analysis, causal relationship determination, and transportation plan generation.

Benefits of technology

Enables the creation of revised transportation plans that improve KPIs by understanding the reasons behind non-compliance with thresholds, facilitating efficient and informed plan revisions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024167641000001_ABST
    Figure 2024167641000001_ABST
Patent Text Reader

Abstract

To generate a revised transportation plan that takes into account the causal relationship of KPIs that do not meet a required threshold for the transportation plan of a transportation service.SOLUTION: A transportation planning management device includes: a storage unit that stores existing transportation plan information indicating existing transportation plans for a predetermined transportation service, transportation service KPI information including KPI indicating performance indicators for the existing transportation plan information, and statistical information related to the transportation service; an inconsistency KPI identification unit that identifies inconsistent KPIs that do not meet predetermined request thresholds on the basis of the existing transportation plan information and transportation service KPI information; a causal relationship determination unit that analyzes inconsistent KPIs and statistical information and determines the causal relationship between the relevant variables in the subset of statistical information extracted from the KPIs and statistical information; and a transportation plan generation unit that generates revised transportation plan information that satisfies the required threshold value by using the existing transportation plan information and the determined causal relationship.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a transportation plan management device and a transportation plan management method. [Background technology]

[0002] In transportation services, transportation planning is used to manage the departure and arrival times of trains, buses, etc. in a transportation network, taking into account operational costs and demand. Traditionally, transportation planning is done manually by carriers, taking into account the infrastructure of the transportation network and passenger needs.

[0003] In recent years, in order to realize a sustainable society, transportation operators such as railway companies and bus companies are being required to develop flexible transportation plans to carry out transportation efficiently, taking into account fluctuations in demand for transportation services and the impact on the environment. The transportation plan itself has been conventionally used to manage the movement of moving bodies such as trains and buses. For example, JP 2019-092347 A (Patent Document 1) discloses an automatic driving control device that controls trains according to a transportation plan.

[0004] Patent document 1 describes the technology as follows: "The automatic driving control device includes a creation unit 104, a calculation unit 101, and a control unit 105. The creation unit creates a running plan including a target speed of the train in a specified section. The calculation unit calculates the train acceleration that will make the train's running speed in the specified section the target speed, based on at least one of the air resistance and line conditions of the specified section. The control unit controls the acceleration and deceleration of the train in the specified section in accordance with the calculated train acceleration." [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2019-092347 A Summary of the Invention [Problem to be solved by the invention]

[0006] The automatic operation control device described in Patent Document 1 controls the acceleration and deceleration of a train based on air resistance and line conditions so that the train's running speed becomes a target speed defined in a running plan. The automatic operation control device described in Patent Document 1 is said to be able to improve train ride comfort and energy saving effects.

[0007] Meanwhile, as a method for evaluating the performance of transportation plans used in transportation services, measures based on key performance indicators (KPIs) are sometimes used. These KPIs are quantitative indicators that indicate the performance of transportation services with respect to various factors, such as the operating costs, expected revenues, environmental impact, and energy efficiency of a given transportation plan. If a particular KPI in a transportation plan does not meet a predetermined required threshold, it is desirable to revise the transportation plan so that the KPI meets the required threshold.

[0008] However, while conventional KPI-based evaluation methods can identify KPIs that do not meet the required threshold, it is difficult to determine how to revise a transportation plan so that the KPI meets the required threshold because the reason why the KPI does not meet the required threshold is unclear. In particular, in the case of a complex situation such as a transportation service in which many variables such as the number of transportation routes, congestion level, and passenger waiting time are involved, a lot of specialized knowledge is required to understand the causal relationships between these variables and KPIs and to appropriately revise the existing transportation plan, which places a heavy burden on users who manage the transportation plan.

[0009] According to the means described in Patent Document 1, it is possible to control trains using a transportation plan that takes into account specific performance indicators such as energy efficiency, but it does not describe any means for proposing specific revisions to improve KPIs while taking into account the causal relationships between numerous variables and KPIs.

[0010] Therefore, the present disclosure aims to provide a transportation plan management means that is capable of generating a revised transportation plan with improved KPIs by analyzing the reasons why KPIs do not meet required thresholds while taking into account the causal relationships between numerous variables and KPIs for transportation plans of transportation services. [Means for solving the problem]

[0011] In order to solve the above problems, one representative transportation plan management device of the present invention includes a processor, a memory, and a storage unit, and the storage unit includes existing transportation plan information indicating an existing transportation plan for a specified transportation service, transportation service KPI information including a KPI indicating a performance index for the existing transportation plan information, and statistical information related to the transportation service, and the memory includes an inconsistent KPI identification unit that identifies an inconsistent KPI among the KPIs that does not meet a specified required threshold based on the existing transportation plan information and the transportation service KPI information, a causal relationship determination unit that analyzes the inconsistent KPI and the statistical information and determines a causal relationship between the inconsistent KPI and a related variable in a subset of statistical information extracted from the statistical information, and a transportation plan generation unit that generates revised transportation plan information in which the inconsistent KPI satisfies the required threshold using the existing transportation plan information and the determined causal relationship. Effect of the Invention

[0012] According to the present disclosure, it is possible to provide a transportation plan management means that is capable of analyzing the reasons why KPIs do not meet required thresholds while taking into account the causal relationships between numerous variables and KPIs for transportation plans of transportation services, and generating revised transportation plans with improved KPIs. Other objects, configurations and effects will become apparent from the following description of the preferred embodiment of the invention. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 illustrates a computer system for implementing an embodiment of the present disclosure. [Diagram 2] FIG. 2 is a diagram illustrating an example of a configuration of a transportation plan management system according to an embodiment of the present disclosure. [Diagram 3] FIG. 3 is a diagram illustrating a logical configuration of functional units and databases included in the transportation plan management device according to an embodiment of the present disclosure. [Figure 4] FIG. 4 illustrates an overall flow of a transportation plan management method according to an embodiment of the present disclosure. [Diagram 5] FIG. 5 is a diagram illustrating an example of the flow of the causal relationship determination process according to the embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram illustrating an example of the flow of the causal relationship analysis process according to the embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram illustrating an example of the flow of a transportation plan generation process according to an embodiment of the present disclosure. [Figure 8] FIG. 8 is a diagram illustrating an example of a case where the time parameter L according to an embodiment of the present disclosure is set as a dimension parameter. [Figure 9] FIG. 9 is a diagram illustrating an example of a case where the vehicle parameter M according to the embodiment of the present disclosure is set as a dimension parameter. [Figure 10] FIG. 10 is a diagram illustrating an example of a case where the station parameter N according to the embodiment of the present disclosure is set as a dimension parameter. [Figure 11] FIG. 11 is a diagram illustrating an example of a causal relationship diagram according to an embodiment of the present disclosure. [Figure 12] FIG. 12 is a diagram illustrating a dimension parameter setting interface according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the present invention is not limited to the embodiment. In addition, in the description of the drawings, the same parts are denoted by the same reference numerals. In addition, terms such as "first," "second," and "third" may be used to describe various elements or components in this disclosure, but it will be understood that these elements or components should not be limited by these terms. These terms are used only to distinguish one element or component from another element or component. Thus, a first element or component discussed below can also be referred to as a second element or component without departing from the teachings of the inventive concept.

[0015] Next, referring to Fig. 1, a computer system 100 for implementing an embodiment of the present disclosure will be described. The mechanisms and devices of the various embodiments disclosed herein may be applied to any suitable computing system. The main components of the computer system 100 include one or more processors 102, memory 104, a terminal interface 112, a storage interface 113, an I / O (input / output) device interface 114, and a network interface 115. These components may be interconnected via a memory bus 106, an I / O bus 108, a bus interface unit 109, and an I / O bus interface unit 110.

[0016] Computer system 100 may include one or more general purpose programmable central processing units (CPUs) 102A and 102B, collectively referred to as processors 102. In some embodiments, computer system 100 may include multiple processors, while in other embodiments, computer system 100 may be a single CPU system. Each processor 102 executes instructions stored in memory 104 and may include an on-board cache.

[0017] In one embodiment, memory 104 may include random access semiconductor memory, storage devices, or storage media (either volatile or non-volatile) for storing data and programs. Memory 104 may store all or a portion of the programs, modules, and data structures that implement the functions described herein. For example, memory 104 may store a transportation planning management application 150. In one embodiment, transportation planning management application 150 may include instructions or descriptions that execute on processor 102 the functions described below.

[0018] In some embodiments, transportation planning management application 150 may be implemented in hardware via semiconductor devices, chips, logic gates, circuits, circuit cards, and / or other physical hardware devices instead of or in addition to a processor-based system. In some embodiments, transportation planning management application 150 may include data other than instructions or descriptions. In some embodiments, cameras, sensors, or other data input devices (not shown) may be provided to communicate directly with bus interface unit 109, processor 102, or other hardware of computer system 100.

[0019] Computer system 100 may include a bus interface unit 109 that provides communication between processor 102, memory 104, display system 124, and I / O bus interface unit 110. I / O bus interface unit 110 may couple to an I / O bus 108 for transferring data to and from various I / O units. I / O bus interface unit 110 may communicate via I / O bus 108 with multiple I / O interface units 112, 113, 114, and 115, also known as I / O processors (IOPs) or I / O adapters (IOAs).

[0020] Display system 124 may include a display controller, a display memory, or both. The display controller may provide video, audio, or both data to display device 126. Computer system 100 may also include one or more sensors or other devices configured to collect data and provide the data to processor 102.

[0021] For example, computer system 100 may include biometric sensors to collect heart rate data, stress level data, etc., environmental sensors to collect humidity data, temperature data, pressure data, etc., and motion sensors to collect acceleration data, movement data, etc. Other types of sensors may also be used. Display system 124 may be connected to a display device 126, such as a standalone display screen, a television, a tablet, or a handheld device.

[0022] The I / O interface unit provides the ability to communicate with various storage or I / O devices. For example, the terminal interface unit 112 may be attached to user I / O devices 116, such as user output devices, such as a video display, a television with speakers, and user input devices, such as a keyboard, a mouse, a keypad, a touchpad, a trackball, buttons, a light pen, or other pointing device. A user may use a user interface to enter input data or instructions to the user I / O devices 116 and the computer system 100, and receive output data from the computer system 100, by manipulating the user input devices. The user interface may be displayed on a display, played through speakers, or printed via a printer, for example, via the user I / O devices 116.

[0023] Storage interface 113 allows attachment of one or more disk drives or direct access storage device 117 (usually a magnetic disk drive storage device, but may be an array of disk drives or other storage devices configured to appear as a single disk drive). In some embodiments, storage device 117 may be implemented as any secondary storage device. Contents of memory 104 may be stored in storage device 117 and retrieved from storage device 117 as needed. I / O device interface 114 may provide an interface to other I / O devices such as printers, fax machines, etc. Network interface 115 may provide a communications path to allow computer system 100 and other devices to communicate with each other. This communications path may be, for example, network 130.

[0024] In one embodiment, computer system 100 may be a device that receives requests from other computer systems (clients) without a direct user interface, such as a multi-user mainframe computer system, a single-user system, or a server computer, etc. In other embodiments, computer system 100 may be a desktop computer, a portable computer, a laptop, a tablet computer, a pocket computer, a telephone, a smartphone, or any other suitable electronic device.

[0025] Next, a transportation plan management system according to an embodiment of the present disclosure will be described with reference to FIG.

[0026] FIG. 2 is a diagram illustrating an example of a configuration of a transportation plan management system 200 according to an embodiment of the present disclosure. The transportation plan management system 200 is a system for generating a revised transportation plan in which the KPI is improved after analyzing the reason why the KPI does not satisfy a required threshold while considering the causal relationship between many variables and the KPI for a transportation plan of a transportation service. As shown in FIG. 2, the transportation plan management system 200 includes a transportation plan management device 210, a communication network 250, and a user terminal 260. In the transportation plan management system 200, the transportation plan management device 210 and the user terminal 260 may be connected to each other via the communication network 250.

[0027] The transportation plan management device 210 is a device for generating a revised transportation plan in which inconsistent KPIs that do not satisfy a specified required threshold in an existing transportation plan are revised so that the inconsistent KPIs satisfy the required threshold, and as shown in FIG. 2, mainly includes a memory 220, a storage unit 230, a processor 244, and an input / output unit 246. In one embodiment, the transportation planning manager 210 may be implemented by the computer system 100 shown in FIG.

[0028] The memory 220 includes a memory for implementing the functions of the transportation planning management means according to an embodiment of the present disclosure. The memory may be for storing a transportation plan management application 150. The transportation plan management application 150 may include processing instructions for implementing functions of software modules such as a KPI analysis unit 222, a causal relationship management unit 224, an amendment proposal unit 226, and a transportation plan management unit 228, as shown in FIG.

[0029] The KPI analysis unit 222 is a functional unit that identifies inconsistent KPIs that do not meet specified required thresholds based on existing transportation plan information and transportation service KPI information stored in the transportation service information DB232 described later, and extracts information (a subset of statistical information) for determining causal relationships related to the identified inconsistent KPIs from the transportation service information DB232 and the local community information DB234. The details of the operation of the KPI analysis unit 222 will be described later, and therefore will not be described here.

[0030] The causal relationship management unit 224 is a functional unit for determining the causal relationship that exists between the inconsistent KPI identified by the KPI analysis unit 222 and the related variables in the subset of extracted statistical information, and for generating inconsistency hypothesis information that indicates the reason why the inconsistent KPI does not meet the required threshold value. The details of the operation of the causal relationship management unit 224 will be described later, and therefore will not be described here.

[0031] The revision proposal unit 226 is a functional unit that generates variable change operation information indicating a recommended variable change operation for related variables that are causally related to the inconsistency KPI based on the inconsistency hypothesis information determined by the causal relationship management unit 224, and calculates the amount of change in the inconsistency KPI when the variable change operation is performed. The details of the operation of revision proposing unit 226 will be described later, and therefore will not be described here.

[0032] The transport plan management unit 228 is a functional unit for generating revised transport plan information in which the inconsistent KPI satisfies the required threshold value, using the existing transport plan information and the determined causal relationship. The details of the operation of the transportation plan management unit 228 will be described later, and therefore will not be described here.

[0033] The memory unit 230 is a memory area that contains a database (hereinafter, "DB") for storing various information related to an embodiment of the present disclosure, and may include a transportation service information DB232 and a local community information DB234, as shown in FIG. 2.

[0034] The transportation service information DB 232 is a database for storing transportation service information related to a transportation service. The transportation service information stored in the transportation service information DB 232 may be information obtained from a transportation company that operates a transportation service, for example. The local community information DB 234 is a database for storing local community information related to the local community in which the transportation service is provided. The local community information DB 234 may be acquired from any third party such as a local government, an administrative agency, a company, or an organization, or may be acquired by a sensor installed in the community. Note that, in FIG. 2, a configuration is shown as an example in which the transportation service information DB232 and the local community information DB234 are stored in the memory unit 230 of the transportation plan management device 210, but in reality, the information stored in the transportation service information DB232 and the local community information DB234 can also be stored in an external server (e.g., a server owned by a transportation company or a server of a local government) that is communicatively connected to the transportation plan management device 210, and can be obtained as needed via the communication network 250.

[0035] The processor 244 is a processing unit for executing processing instructions stored by the memory 220 that define the functionality of each functional unit of the transportation planning management application 150 .

[0036] The input / output unit 246 is a functional unit for receiving information input to the transportation plan management device 210 and outputting data such as revised transportation plan information generated by the transportation plan management device 210. In an embodiment, the input / output unit 246 may include, for example, a keyboard, a mouse, a display that displays a GUI (Graphical User Interface), and the like. In an embodiment, the input / output unit 246 may provide the user terminal 260 with a GUI that inputs and outputs various types of information.

[0037] Communications network 250 may include, for example, a local area network (LAN), a wide area network (WAN), a satellite network, a cable network, a WiFi network, or any combination thereof.

[0038] The user terminal 260 is a terminal device that can be used by a user of the transportation plan management device 210. By using the user terminal 260, the user can input information such as existing transportation plan information, transportation service KPI information, and dimension parameters described later, and can confirm information such as revised transportation plan information output by the transportation plan management device 210. As an example, the user terminal 260 may include, for example, a smartphone, a smart watch, a tablet, a personal computer, or the like of a user who manages transportation plans at a transportation company, and is not particularly limited. For ease of explanation, FIG. 2 illustrates an example of a configuration including one user terminal 260. However, the number of user terminals 260 is not limited, and a configuration including a plurality of user terminals 260 is also possible.

[0039] According to the transportation plan management system 200 described above, it is possible to analyze the reason why a KPI does not meet a required threshold while taking into account the causal relationships between numerous variables and KPIs for a transportation plan for a transportation service, and then generate a revised transportation plan with improved KPIs.

[0040] Next, with reference to FIG. 3, a logical configuration of functional units and databases included in the transportation plan management device according to the embodiment of the present disclosure will be described.

[0041] FIG. 3 is a diagram showing a logical configuration of functional units and databases included in the transportation plan management device 210 according to an embodiment of the present disclosure.

[0042] As described above, the transportation plan management device 210 includes two databases, the transportation service information DB 232 and the local community information DB 234, and four functional units, the KPI analysis unit 222, the causal relationship management unit 224, the revision proposal unit 226, and the transportation plan management unit 228. Each of the transportation service information DB 232 and the local community information DB 234 may include a subordinate database, and each of the KPI analysis unit 222, the causal relationship management unit 224, the revision proposal unit 226, and the transportation plan management unit 228 may include a subordinate functional unit. Therefore, the subordinate databases and subordinate functional units included in each database and functional unit will be described here.

[0043] The transportation service information DB232 is a database for storing transportation service information related to transportation services, and may include an existing transportation plan information DB401, a transportation service KPI information DB402, an infrastructure information DB403, a vehicle configuration information DB404, a map information DB405, a weather information DB407, and a passenger movement information DB406, as shown in Fig. 3. As described above, various information included in the transportation service information DB232 may be obtained, for example, from a transportation company that provides the transportation service.

[0044] The existing transportation plan information DB401 is a database that stores existing transportation plan information indicating an existing transportation plan in the transportation service. This existing transportation plan information may include, for a predetermined period, information identifying a transportation process implemented as a transportation service, information identifying a vehicle used to implement the transportation process, information indicating a departure position and an arrival position of the transportation process, information on the number of transportation processes, information on the required time of the transportation process, and information on the number of passengers of the transportation process. As described later, this existing transportation plan information is used to generate revised transportation plan information with improved inconsistency KPIs, and may be created and input by, for example, a user (client, etc.) of the transportation plan management device.

[0045] The transportation service KPI information DB402 is information on KPIs related to existing transportation plan information stored in the existing transportation plan information DB401, and information indicating a required threshold value for each KPI. As described above, these KPIs are quantitative indicators indicating the performance of the transportation service with respect to various elements in the existing transportation plan information. For example, in one embodiment, these KPIs may include performance indicators for the operating costs, expected revenue, environmental impact, and energy efficiency of the transportation plan. The required threshold is information that specifies the range of performance required for each KPI. In this disclosure, a KPI that does not meet the required threshold (i.e., deviates from the range) is called an "inconsistent KPI." As an example, in the transportation service KPI information DB402, if there is a KPI in existing transportation plan information such as "vehicle utilization rate = 45%" and the required threshold for that KPI is "60% to 70%, " it is identified as an "inconsistent KPI" that does not meet the KPI required threshold.

[0046] The infrastructure information DB 403 is a database that stores infrastructure information indicating existing infrastructure in an area where a transportation service is provided. This existing infrastructure may include information identifying, for example, railroad tracks, stations, vehicles, electric wires, ticket gates, etc., used in the transportation service.

[0047] The vehicle configuration information DB 404 is a database that stores information indicating the configuration of vehicles (trains, buses, etc.) used in the transportation service. This vehicle configuration may include, for example, information identifying the vehicles in the train, the number of passengers in the vehicle, the vehicles before and after a specific vehicle, etc.

[0048] The map information DB 405 is a database that stores map information related to the area where the transportation service is provided. This map information may include two-dimensional or three-dimensional maps, satellite photos, information related to the altitude of the area where the transportation service is provided, etc.

[0049] Weather information 406 is a database that stores weather information related to the area where the transportation service is provided. This weather information may include information indicating the temperature, humidity, amount of rainfall, amount of snowfall, hours of sunshine, etc., of the area where the transportation service is provided.

[0050] The passenger movement information DB 407 is a database that stores passenger movement information indicating the movement history of passengers who use the transportation service. This passenger movement information may include, for example, information such as the date and time, type (train or bus), departure position, arrival position, required time, and waiting time of the transportation route used by the passenger in the past.

[0051] The local community information DB234 is a database for storing local community information related to the community in which the transportation service is provided, and may include a population information DB411, a resident movement information DB412, a transportation means information DB413, a tax information DB414, an economic information DB415, and a customer satisfaction information DB416, as shown in Fig. 3. As described above, the various information stored in the local community information DB234 may be obtained from any third party such as a local government, an administrative agency, a company, or an organization, or may be obtained by a sensor installed in the community.

[0052] The population information DB 411 is a database that stores population information indicating the population of the area where the transportation service is provided. This population information may include, for example, information indicating the population living in the area and the floating population staying in the area for work, school, tourism, etc.

[0053] The resident movement information DB 412 is a database that stores resident movement information indicating the movement of residents living in the area where the transportation service is provided. This resident movement information may include, for example, information on the number of people who moved into the area and information on the number of people who moved out of the area over a certain period of time.

[0054] The transportation information DB 413 is a database that stores transportation information indicating transportation provided in a specific area. This transportation information may include, for example, information on services such as buses, trains, and monorails provided in the specific area and their usage records.

[0055] The tax information DB 414 is a database that stores tax information on residents who live in the area where the transportation service is provided. This tax information may include, for example, information on the average tax amount, income, and delinquent tax of residents who live in the area.

[0056] The economic information DB 415 is a database that stores economic information related to the economy of the region in which the transportation service is provided. This economic information may include information on the major industries, production information, employment rate, etc. in the region.

[0057] The customer satisfaction information DB 416 is a database that stores customer satisfaction information indicating the degree of satisfaction with the transportation service of customers of the transportation service who live in the area where the transportation service is provided. This customer satisfaction information may include information regarding customer satisfaction with multiple transportation services and transportation itineraries, and customer travel preferences (preferring routes with short travel times, preferring routes with fewer transfers, etc.).

[0058] Of the various information stored in the above-mentioned transportation service information DB232 and local community information DB234, the existing transportation plan information DB401 and the transportation service KPI information DB402 are used to identify inconsistent KPIs in the existing transportation plan information that do not meet the required thresholds, as described below. Meanwhile, various information stored in the infrastructure information DB403, the vehicle configuration information DB404, the map information DB405, the weather information DB406, the passenger movement information DB407, the population information DB411, the resident movement information DB412, the means of transport information DB413, the tax information DB414, the economic information DB415, and the customer satisfaction information DB416 is used to identify the causal relationship related to the identified inconsistent KPI. Hereinafter, the information stored in the infrastructure information DB403, the vehicle configuration information DB404, the map information DB405, the weather information DB406, the passenger movement information DB407, the population information DB411, the resident movement information DB412, the means of transport information DB413, the tax information DB414, the economic information DB415, and the customer satisfaction information DB416 and used to identify the causal relationship is collectively referred to as "statistical information" 315.

[0059] The KPI analysis unit 222 includes an inconsistency KPI identification unit 421 that identifies inconsistent KPIs that do not meet a specified required threshold based on existing transportation plan information and transportation service KPI information stored in the transportation service information DB 232, and an information extraction unit 422 that extracts information (a subset of statistical information) from the statistical information 315 for determining the causal relationship related to the identified inconsistency KPI. The details of the operation of the KPI analysis unit 222 will be described later, and therefore will not be described here.

[0060] The causal relationship management unit 224 includes a causal relationship determination unit 431 that determines the causal relationship that exists between the inconsistent KPI identified by the KPI analysis unit 222 and related variables in the extracted subset of statistical information, and a hypothesis reasoning unit 432 that generates inconsistency hypothesis information indicating the reason why the inconsistent KPI does not satisfy the required threshold. The details of the operation of the causal relationship management unit 224 will be described later, and therefore will not be described here.

[0061] The revision proposal unit 226 includes an operation determination unit 441 that generates variable change operation information indicating a recommended variable change operation for related variables that are causally related to the inconsistency KPI based on the inconsistency hypothesis information determined by the causal relationship management unit 224, and a KPI change calculation unit 442 that calculates the amount of change in the inconsistency KPI when the variable change operation is performed. The details of the operation of revision proposing unit 226 will be described later, and therefore will not be described here.

[0062] The transportation plan management unit 228 includes a reception unit 451 that outputs a causal relationship diagram showing the determined causal relationship, inconsistency hypothesis information, variable change operation information, and the amount of change in the inconsistency KPI when the variable change operation is performed and receives input from a user, and a transportation plan generation unit 452 that, when an approval input approving the variable change operation is received, generates revised transportation plan information in which the inconsistency KPI is revised to satisfy the required threshold by reflecting the variable change operation in the existing transportation plan information.

[0063] According to the transportation plan management device 210 shown in FIG. 3, it is possible to analyze the reason why a KPI does not satisfy a required threshold while taking into account the causal relationships between numerous variables and KPIs for a transportation plan of a transportation service, and then generate a revised transportation plan with improved KPIs.

[0064] Next, with reference to FIG. 4, an overall flow of a transportation plan management method according to an embodiment of the present disclosure will be described.

[0065] Fig. 4 is a diagram showing an example of an overall flow of a transportation plan management method 400 according to an embodiment of the present disclosure. The transportation plan management method 400 shown in Fig. 4 is a method for generating a revised transportation plan in which the KPI is improved after deriving the reason why the KPI does not satisfy the required threshold while considering the causal relationships between many variables and KPIs regarding the transportation plan of the transportation service, and is executed by each functional unit of the transportation plan management device 210 shown in Figs. 2 and 3.

[0066] First, in step S402, the KPI analysis unit 222 acquires the transportation service information stored in the transportation service information DB 232 and the local community information stored in the local community information DB 234. As described above, the information acquired here includes the existing transportation plan information and the transportation service KPI information used to identify the inconsistent KPI, and the statistical information used to identify the causal relationship (for example, the statistical information 315 shown in FIG. 3). Here, the case where the KPI analysis unit 222 acquires all the transport service information and the local community information has been described as an example, but the present disclosure is not limited to this, and for example, when the transport service information and the local community information are stored in a remote third-party server, the KPI analysis unit 222 can first acquire existing transport plan information and transport service KPI information for identifying inconsistent KPIs, and after identifying the inconsistent KPIs, acquire only statistical information related to these inconsistent KPIs from the server. This makes it possible to save bandwidth for transmitting information with a low degree of relevance to the inconsistent KPIs.

[0067] Next, in step S404, the inconsistent KPI identification unit 421 of the KPI analysis unit 222 identifies an inconsistent KPI based on the existing transportation plan information and the transportation service KPI information acquired in step S402. As described above, the transportation service KPI information is information indicating KPI information related to the existing transportation plan information and the required threshold value for each KPI. Therefore, the inconsistent KPI identification unit 421 can identify a KPI that does not satisfy the specified required threshold value as an inconsistent KPI among the transportation service KPI information corresponding to the specific existing transportation plan information. As an example, in the transportation service KPI information, a required threshold value of "60% to 70%" is specified for the KPI "vehicle utilization rate", and in the existing transportation plan information, when "vehicle utilization rate = 45%", the inconsistent KPI identification unit 421 may identify "vehicle utilization rate" as an inconsistent KPI.

[0068] Next, in step S406, the information extraction unit 422 of the KPI analysis unit 222 receives an input from a user that specifies a dimension parameter that specifies a search range of statistical information based on the influence range of the inconsistent KPI. The influence range of the inconsistent KPI here is information for identifying where, when, and what the inconsistent KPI affects. The dimension parameter is information that is set based on the influence range of the inconsistent KPI and specifies the maximum search range for extracting information related to the inconsistent KPI (a subset of statistical information) from the statistical information. In an embodiment, the user of the transportation plan management device 210 may set the dimension parameter to a dimension parameter setting interface 1200 shown in FIG. 12 and displayed via the user terminal 260. In one embodiment, the dimension parameters may include, for a search performed on statistical information, time parameters specifying the temporal range (e.g., from what time until what time the inconsistent KPI occurred), location parameters specifying the spatial range (e.g., the geographical location or coordinates where the inconsistent KPI occurred), vehicle parameters specifying the target range (e.g., from how many cars in front of the target vehicle until how many cars behind the target station the inconsistent KPI occurred), station parameters specifying the station range (e.g., from how many cars in front of the target station until how many cars behind the target station the inconsistent KPI occurred), and characteristic information specifying the target range (e.g., the energy efficiency of the vehicle in which the inconsistent KPI occurred, etc.). The dimension parameters may be set to include the same range as the range of influence of the inconsistent KPI. However, since related variables that have a causal relationship with the inconsistent KPI may exist outside the range of influence of the inconsistent KPI, it is desirable to set the dimension parameters to a range wider than the range of influence of the inconsistent KPI. Details of steps S406 to S412 will be described later in the causal relationship determination process 500 with reference to FIG. 5, and therefore will not be described here.

[0069] Next, in step S408, the information extraction unit 422 extracts a subset of statistical information for determining the causal relationship regarding the inconsistent KPI from the statistical information acquired in step S402 (statistical information 315 shown in FIG. 3) based on the dimension parameters set in step S406.

[0070] Next, in step S410, the causal relationship determination unit 431 of the causal relationship management unit 224 determines a causal relationship regarding the inconsistent KPI by using the subset of statistical information extracted in step S408. Here, the causal relationship determination unit 431 may determine multiple causal relationships for one inconsistent KPI. This causal relationship is a causal relationship that exists between the inconsistent KPI and any data element in the statistical information (hereinafter, "related variable"), and includes a relationship in which the inconsistent KPI is influenced by the related variable and a relationship in which the inconsistent KPI influences the related variable.

[0071] Next, in step S412, the causal relationship determination unit 431 of the causal relationship management unit 224 calculates the accuracy for each causal relationship determined in step S410. This accuracy is a value indicating the accuracy of a specific causal relationship, and may be a credibility calculated when determining a causal relationship.

[0072] Next, in step S414, the causal relationship determination unit 431 identifies the causal relationship with the highest accuracy for each inconsistent KPI. This is used to derive the reason why the inconsistent KPI occurred as the most certain causal relationship that affects (or is affected by) the specific inconsistent KPI. In one embodiment, if there are multiple causal relationships that satisfy a predetermined accuracy threshold, these multiple causal relationships may be identified.

[0073] Next, in step S416, the causal relationship determination unit 431 determines whether the process has been completed for all inconsistent KPIs identified in step S404 (whether the most accurate causal relationship has been identified). If the process has not been completed for all inconsistent KPIs, the process returns to step S406, and the subsequent steps are performed for the target inconsistent KPI. On the other hand, if the process has been completed for all inconsistent KPIs, the process proceeds to step S418.

[0074] Next, in step S418, the a priori reasoning unit 432 of the causal relationship management unit 224 generates inconsistency hypothesis information indicating the reason why the inconsistency KPI does not satisfy the required threshold, based on the causal relationship with the highest accuracy identified in step S414. The details of steps S418 to S424 will be described later in the causal relationship analysis process 600 shown in FIG. 6 and the transportation plan generation process 700 shown in FIG. 7, and therefore will not be described here.

[0075] Next, in step S420, the operation determination unit 441 of the amendment proposal unit 226 generates variable change operation information indicating a variable change operation for making the inconsistency KPI satisfy the required threshold based on the inconsistency hypothesis information generated in step S418, and the KPI change calculation unit 442 calculates the amount of change in the inconsistency KPI when the variable change operation is performed. The variable change action here is information that specifies a recommended change to a variable that is in a causal relationship with the inconsistent KPI. For example, if it is determined that the inconsistent KPI with "congestion level" is in a causal relationship with a related variable with "number of trains", the action determination unit 441 may determine a variable change action that recommends "adjusting the number of trains".

[0076] Next, in step S422, the reception unit 451 of the transportation plan management unit 228 outputs a causal relationship diagram showing the causal relationship between the inconsistent KPI and the related variables, inconsistency hypothesis information, variable change operation information, and the amount of change in the inconsistent KPI when the variable change operation is performed, and displays them to the user of the transportation plan management device 210, and receives feedback indicating whether or not to approve the variable change operation.

[0077] Next, in step S424, when the transport plan generating unit 452 of the transport plan management unit 228 receives an approval input from the user approving the variable change operation output in step S422, the transport plan generating unit 452 generates revised transport plan information by reflecting the variable change operation in the existing transport plan information. This revised transport plan information is transport plan information in which related variables are adjusted so that the inconsistent KPI satisfies the required threshold value.

[0078] According to the transportation plan management method 400 described with reference to Fig. 4, it is possible to determine a causal relationship between an inconsistent KPI that does not satisfy a predetermined required threshold and a related variable in statistical information related to the inconsistent KPI, and derive a reason why the inconsistent KPI did not satisfy the required threshold based on the causal relationship. Also, it is possible to generate revised transportation plan information in which the related variable is adjusted so that the inconsistent KPI satisfies the required threshold based on the reason derived in this way.

[0079] Next, with reference to FIG. 5, a flow of the causal relationship determination process according to the embodiment of the present disclosure will be described.

[0080] Fig. 5 is a diagram showing an example of the flow of a causal relationship determination process 500 according to an embodiment of the present disclosure. The causal relationship determination process 500 shown in Fig. 5 is a process for extracting a subset of statistical information related to the inconsistent KPI from the statistical information based on a dimension parameter that specifies a search range for the statistical information, and determining a causal relationship existing between the inconsistent KPI and a related variable in the extracted subset of statistical information, and is executed by the information extraction unit 422 of the KPI analysis unit 222 and the causal relationship determination unit 431 of the causal relationship management unit 224. Note that Figure 5 illustrates an example in which the scope of influence of an inconsistent KPI is defined using parameters related to time, vehicles, and stations; however, the present disclosure is not limited to this, and the scope of influence of an inconsistent KPI may be defined using any other parameters, such as the energy efficiency of a vehicle.

[0081] First, in step S502, the information extraction unit 422 determines the range of influence of the inconsistent KPI. Here, the information extraction unit 422 may determine the range of time, vehicle, and station that deviates from the required threshold for the inconsistent KPI identified in step S404 of the above-mentioned transportation plan management method 400 based on, for example, existing transportation plan information stored in the existing transportation plan information DB 401 and KPI information stored in the transportation service KPI information DB 402. As an example, the information extraction unit 422 may determine the start time, start vehicle, start station, end time, end vehicle, end station, etc. of the inconsistent KPI as the range of influence of the inconsistent KPI.

[0082] Next, in step S504, the information extraction unit 422 sets a dimension parameter and a step size based on the extent of influence of the inconsistent KPI determined in step S504. In one embodiment, the information extraction unit 422 may display the extent of influence of the inconsistent KPI determined in step S504 to the user via, for example, a dimension parameter setting interface 1200 described later, and have the user adjust and confirm the extent of influence, and then finalize and set the values ​​of the dimension parameter and the step size. The step size here means the size of the target elements (l, m, n described below) spread at one time when searching for statistical information using the dimension parameters, and may be set for each dimension parameter. In principle, the smaller the step size, the finer the subset of statistical information is extracted, enabling more accurate causal relationship determination; however, the processing time increases, so it is desirable to set this step size taking into consideration the desired accuracy of causal relationship determination and the processing time.

[0083] As an example, the information extraction unit 422 may set, as dimension parameters for searching statistical information based on the influence range of the inconsistent KPI, a time parameter L (e.g., 60 minutes) that specifies the time range and its step size a (e.g., 3 minutes), a vehicle parameter M (e.g., 10 vehicles before and after) that specifies the range of vehicles and its step size b (e.g., 1 vehicle), and a station parameter N (e.g., 6 stations) that specifies the range of stations and its step size c (e.g., 1 station). These dimension parameters specify the maximum range of a search performed on the statistical information. The dimension parameters may be set to include the same range as the range of influence of the inconsistent KPI, but since related variables that have a causal relationship with the inconsistent KPI may exist outside the range of influence of the inconsistent KPI, it is desirable to set the time parameter L, the vehicle parameter M, and the station parameter N to a range wider than the range of influence of the inconsistent KPI.

[0084] Next, in step S506, the information extraction unit 422 initializes the value of the target element for searching for statistical information and starts searching for statistical information. The target element here is a value that identifies specific data in the statistical information, and may be set based on the dimension parameters. For example, when there are a time parameter L, a vehicle parameter M, and a station parameter N as the dimension parameters, the information extraction unit 422 may set a target time l that identifies a specific time, a target vehicle m that identifies a specific vehicle, and a target station n that identifies a specific station. After that, the information extraction unit 422 sets the target time l, the target vehicle m, and the target station n to "0", and determines whether information corresponding to the target time l, the target vehicle m, and the target station n exists in the statistical information.

[0085] Next, in step S508, the information extraction unit 422 identifies information corresponding to any one of the target time l, the target vehicle m, and the target station n from the statistical information, and extracts it as a subset of the statistical information. More specifically, the information extraction unit 422 may extract information that satisfies a search range defined in the following formula 1 as the subset of the statistical information.

number

[0086] Next, in step S510, the causal relationship management unit 224 analyzes the subset of statistical information extracted in step S508 and the inconsistent KPI identified in step S404 of the above-mentioned transportation plan management method 400 to determine a causal relationship regarding the inconsistent KPI. The causal relationship here is a causal relationship that exists between the inconsistent KPI and a related variable in the statistical information, and includes a relationship in which the inconsistent KPI is influenced by the related variable and a relationship in which the inconsistent KPI influences the related variable. The related variable here may be data regarding any feature or attribute in the statistical information. As an example, the causal relationship management unit 224 may determine that the inconsistent KPI with the "congestion level" and the related variable with the "number of trains" are in a causal relationship. Here, as a means for analyzing the subset of statistical information and the inconsistent KPI and determining the causal relationship, a machine learning model trained to determine the causal relationship may be used, and is not particularly limited here. In addition, when determining the causal relationship, the causal relationship management unit 224 may generate related variables that are in a causal relationship with the target inconsistent KPI and a causal relationship formula that indicates the degree of influence of each related variable on the inconsistent KPI.

[0087] Next, in step S512, the causal relationship management unit 224 calculates the accuracy of the causal relationship of the inconsistent KPI determined in step S510. This accuracy is a value indicating the accuracy of a specific causal relationship, and may be a credibility calculated when determining the causal relationship. In one embodiment, the causal relationship management unit 224 may calculate the accuracy of the causal relationship by a causal relationship formula generated when determining the causal relationship.

[0088] Next, in step S514, the causal relationship management unit 224 determines whether the target time l is equal to or greater than the time parameter L. If the target time l is equal to or greater than the time parameter L, the process proceeds to step S518. If the target time l is not equal to or greater than the time parameter L, the process proceeds to step S516.

[0089] Next, in step S516, the causal relationship management unit 224 adds the step size a of the target time l to the target time l, and returns to step S508.

[0090] Next, in step S518, the causal relationship management unit 224 determines whether the target vehicle m is equal to or greater than the vehicle parameter M. If the target vehicle m is equal to or greater than the vehicle parameter M, the process proceeds to step S522. If the target vehicle m is not equal to or greater than the vehicle parameter M, the process proceeds to step S520.

[0091] Next, in step S520, the causal relationship management unit 224 adds the step size b of the target vehicle m to the target vehicle m, and returns to step S508.

[0092] Next, in step S522, the causal relationship management unit 224 determines whether the target station n is equal to or greater than the station parameter N. If the target station n is equal to or greater than the station parameter N, the process proceeds to step S524. If the target station n is not equal to or greater than the station parameter N, the process ends.

[0093] Next, in step S524, the causal relationship management unit 224 adds the step size c of the target station n to the target station n, and returns to step S508.

[0094] 5, in the causal relationship determination process 500, the dimension parameters are used to extract information from the statistical information that corresponds to a search range including the time, location, and target at which the inconsistent KPI occurred and that may have a causal relationship with the inconsistent KPI. The information thus extracted can then be analyzed together with the inconsistent KPI to determine the causal relationship regarding the inconsistent KPI. As will be described later, the causal relationship derived in this manner can be used to determine the reason why a particular KPI did not satisfy the required threshold, or to generate revised transportation plan information in which the inconsistent KPI has been revised to satisfy the required threshold.

[0095] Next, the flow of the causal relationship analysis process 600 according to the embodiment of the present disclosure will be described with reference to FIG.

[0096] Fig. 6 is a diagram showing an example of the flow of a causal relationship analysis process 600 according to an embodiment of the present disclosure. The causal relationship analysis process 600 shown in Fig. 6 is a process for analyzing the causal relationship of the inconsistent KPI determined by the above-mentioned causal relationship determination unit 431, generating inconsistency hypothesis information indicating the reason why the inconsistent KPI does not satisfy the required threshold, and generating a recommended variable change action so that the inconsistent KPI satisfies the required threshold, and is executed by the causal relationship management unit 224 and the revision proposal unit 226.

[0097] First, in step S602, the hypothesis reasoning unit 432 of the causal relationship management unit 224 acquires information on the causal relationship existing between the inconsistent KPI and the related variables, determined by the above-mentioned causal relationship determination unit 431 (see the transportation plan management method 400 and the causal relationship determination process 500).

[0098] Next, in step S604, the hypothesis reasoning unit 432 sets an accuracy threshold for evaluating causal relationships. This accuracy threshold is information that specifies a boundary line for distinguishing between causal relationships that are highly certain and accurate enough to be used for creating inconsistent hypothesis information and those that are not, among the determined causal relationships, and may be, for example, a lower limit of the accuracy value. This accuracy threshold may be freely set by, for example, a user of the transportation plan management device 210. In one embodiment, this accuracy threshold may be, for example, "70%."

[0099] Next, in step S606, the hypothesis reasoning unit 432 determines whether the causal relationship of each inconsistent KPI acquired in step S602 satisfies the accuracy threshold set in step S604. If the accuracy of the causal relationship of a specific inconsistent KPI satisfies the accuracy threshold, the process proceeds to step S608, and if the accuracy of the causal relationship of the inconsistent KPI does not satisfy the accuracy threshold, the process proceeds to step S618.

[0100] In step S618, if the accuracy of the causal relationship of the inconsistent KPI does not satisfy the accuracy threshold, the hypothesis reasoning unit 432 determines that the inconsistent KPI is independent (i.e., not influenced by other variables) because it was not possible to determine a reliable causal relationship for the inconsistent KPI, and proceeds to step S620.

[0101] In step S608, the hypothetical reasoning unit 432 generates an element list related to the causal relationship of the inconsistent KPI that satisfies the accuracy threshold. This element list is a list that lists all KPIs and related variables that are in a causal relationship, and may be generated based on terms in a causal relationship formula generated when determining the causal relationship, for example. As an example, when the causal relationship formula is Formula 2 shown below, the element list is "Data1, Data2, Data4".

number

[0102] Next, in step S610, the hypothetical reasoning unit 432 calculates the degree of influence on the inconsistency KPI of each element in the element list generated in step S608. The influence here is a measure that quantitatively indicates the degree of influence that a specific element has on the inconsistency KPI, and can be calculated by the causal relationship formula generated when the causal relationship is determined. In one embodiment, the abductive reasoning unit 432 may also determine the database in which each element in the element list is identified (eg, the weather information DB 406, the economic information DB 415, etc. shown in FIG. 3).

[0103] Next, in step S612, the hypothesis reasoning unit 432 identifies a main variable that satisfies a predetermined influence criterion based on the influence of each element calculated in step S610. This influence criterion is information that specifies a boundary line for distinguishing between variables that have a significant influence on the inconsistency KPI and variables that do not, and may be, for example, a lower limit of the influence. This influence criterion may be freely set by, for example, a user of the transportation plan management device 210. In addition, the main variable is a variable that has a significant influence among variables that have a causal relationship with the inconsistency KPI.

[0104] Next, in step S614, the hypothetical reasoning unit 432 generates inconsistency hypothesis information indicating the reason why the inconsistency KPI does not satisfy the required threshold value based on the main variables identified in step S610. Here, the reason why the inconsistency KPI does not satisfy the required threshold value may be expressed in natural language. Here, the abductive reasoning unit 432 may generate inconsistency hypothesis information according to the polarity (whether direct proportionality or inverse proportionality) of the relationship of the primary variable to the inconsistency KPI in the causal relationship formula generated when determining the causal relationship. For example, when KPI1 is below the required threshold and primary variable A is directly proportional to KPI1, the abductive reasoning unit 432 may generate a sentence indicating that "KPI1 is determined to be inconsistent because primary variable A is low" as the inconsistency hypothesis information. As another example, when KPI1 is below the required threshold and primary variable A is inversely proportional to KPI1, the abductive reasoning unit 432 may generate a sentence indicating that "KPI1 is determined to be inconsistent because primary variable A is high" as the inconsistency hypothesis information. In addition, in one embodiment, the abductive reasoning unit 432 may use an existing abductive reasoning method (eg, a machine learning model trained to perform abductive reasoning) to determine inconsistent hypothesis information.

[0105] Next, in step S616, the operation determination unit 441 of the revision proposal unit 226 generates variable change operation information indicating a variable change operation for making the inconsistency KPI satisfy the required threshold based on the inconsistency hypothesis information generated in step S414, and the KPI change calculation unit 442 calculates the amount of change in the inconsistency KPI when the variable change operation is performed. Here, when there are multiple variable change operations for making the inconsistency KPI satisfy the required threshold, the operation determination unit 441 may generate these multiple variable change operations as candidates to be presented to the user.

[0106] As described above, the variable change operation here is information that specifies a recommended change to a variable that is causally related to the inconsistency KPI, and can be determined based on the inconsistency hypothesis information generated in step S414. In one embodiment, the operation determination unit 441 may determine how the main variable needs to be changed so that the inconsistency KPI satisfies the required threshold by using the causal relationship formula generated at the time of causal relationship determination and the inconsistency hypothesis information. As an example, when it is determined that the inconsistency KPI with the "congestion degree" is causally related to the main variable with the "number of trains", and the inconsistency hypothesis information indicating the reason that "the congestion degree is determined not to satisfy the threshold because the number of trains is small" is determined, the operation determination unit 441 may determine a variable change operation indicating a recommended change to the "number of trains" so that the inconsistency KPI with the "congestion degree" satisfies the required threshold based on the inconsistency hypothesis information and the causal relationship formula. Furthermore, after the variable change operation is determined, the KPI change calculation unit 442 calculates the amount of change in the inconsistency KPI, which indicates how the inconsistency KPI will change when the variable change operation is performed. As an example, the KPI change calculation unit 442 may calculate that when the variable change operation of "increasing the number of trains per hour by one" is performed, the KPI with "operating cost" will be "+10%" and the inconsistency KPI with "congestion level" will be "-25%".

[0107] Next, in step S620, the operation determination unit 441 determines whether processing has been completed for all causal relationships determined in step S606 to satisfy the accuracy threshold (whether inconsistency hypothesis information, variable change operation information, and KPI change amount information have been generated). If processing has not been completed for all causal relationships, the process returns to step S606, and subsequent steps are performed for unprocessed causal relationships. On the other hand, if processing has been completed for all causal relationships, the process proceeds to the revised transportation plan generation process 700 shown in FIG. 7.

[0108] According to the causal relationship analysis process 600 shown in FIG. 6, by analyzing the causal relationship determined for an inconsistent KPI that does not satisfy a predetermined required threshold, it is possible to generate inconsistency hypothesis information indicating the reason why the inconsistent KPI did not satisfy the required threshold, and to generate variable change operation information indicating appropriate changes to key variables that have a significant effect on the inconsistent KPI so that the inconsistent KPI satisfies the required threshold.

[0109] Next, a transportation plan generation process according to an embodiment of the present disclosure will be described with reference to FIG. Fig. 7 is a diagram showing an example of the flow of a transportation plan generation process 700 according to an embodiment of the present disclosure. The transportation plan generation process 700 shown in Fig. 7 is a process for generating a revised transportation plan based on the inconsistency hypothesis information and variable change operations generated in the causal relationship analysis process 600, and is executed by the transportation plan management unit 228 shown in Fig. 2.

[0110] First, in step S702, the reception unit 451 of the transportation plan management unit 228 acquires information on inconsistent KPIs, causal relationship diagrams, inconsistency hypothesis information, variable change operations, and KPI change amounts from the KPI analysis unit 222, the causal relationship management unit 224, and the revision proposal unit 226.

[0111] Next, in step S704, the reception unit 451 checks whether the transportation plan is set to be automatically generated. If the transportation plan is not set to be automatically generated, the process proceeds to step S706. If the transportation plan is set to be automatically generated, the process proceeds to step S714.

[0112] Next, in step S706, the reception unit 451 outputs the inconsistency KPI, the causal relationship diagram, the inconsistency hypothesis information, the variable change operation, and the KPI change amount information to the user terminal 260 via, for example, the input / output unit 246 shown in FIG. 2, and displays them to the user.

[0113] Next, in step S708, the accepting unit 451 accepts feedback on the information displayed on the user terminal 260 in step S706 from the user via, for example, the input / output unit 246 shown in Fig. 2. This feedback may include, for example, an input approving the variable changing operation displayed in step S706 or an input specifying a correction to the variable changing operation.

[0114] Next, in step S710, the reception unit 451 determines whether the variable change operation has been approved based on the feedback received in step S708. If the variable change operation has not been approved, the process proceeds to step S712. If the variable change operation has been approved, the process proceeds to step S714.

[0115] If the variable change action is not approved, in step S712, the action determination unit 441 of the revision proposal unit 226 generates a new variable change action for making the inconsistency KPI satisfy the required threshold based on the user's input for correcting the variable change action and the inconsistency hypothesis information generated for the inconsistency KPI, and the KPI change calculation unit 442 calculates the amount of change in the inconsistency KPI when the new variable change action is performed. After that, the process returns to step S706.

[0116] If the variable change operation is approved, in step S714, the transport plan generation unit 452 generates a revised transport plan by reflecting the approved variable change operation in the existing transport plan information, thereby revising inconsistent KPIs that did not meet the specified required threshold in the existing transport plan so that they meet the required threshold. As an example, when inconsistency hypothesis information is determined for an inconsistency KPI with "congestion degree" indicating the reason that "the number of trains is small, so it is determined that the congestion degree does not meet the threshold," the operation determination unit 441 may generate a revised transportation plan by applying a variable change operation to the existing transportation plan information that appropriately increases the "number of trains" based on this inconsistency hypothesis information and a causal relationship formula so that the inconsistency KPI with "congestion degree" meets the required threshold.

[0117] Next, in step S716, the transportation plan generating unit 452 outputs the revised transportation plan generated in step S714 to the user terminal 260 via, for example, the input / output unit 246 shown in FIG. 2, and displays it.

[0118] According to the transportation plan generation process 700 described with reference to Figure 7, the reason why inconsistent KPIs that do not meet the required threshold value do not meet the required threshold value can be derived, and a revised transportation plan can be generated that reflects appropriate variable change operations for improving these KPIs in the existing transportation plan, and the revised transportation plan can be provided to the user.

[0119] Next, the concept of the dimension parameter according to the embodiment of the present disclosure will be described with reference to Figs. 8 to 10. As described above, the dimension parameter according to the embodiment of the present disclosure is set based on the influence range of the inconsistent KPI, and is information that specifies the maximum range of a search for extracting information related to the inconsistent KPI (a subset of the statistical information) from the statistical information. In an embodiment, the dimension parameter may include, for a search performed on the statistical information, a time parameter that specifies a temporal range, a location parameter that specifies a spatial range, a vehicle parameter that specifies an object range, a station parameter that specifies a station range, and feature information that specifies an object range. By using such dimension parameters, it is possible to identify information (a subset of statistical information) that is highly likely to have a causal relationship with a specific inconsistent KPI from among the statistical information. Note that the dimension parameters may be set to include the same range as the range of influence of the inconsistent KPI, but since related variables that have a causal relationship with the inconsistent KPI may also exist outside the range of influence of the inconsistent KPI, it is desirable to set the dimension parameters to a range wider than the range of influence of the inconsistent KPI.

[0120] In Figures 8 to 10, the dimension parameters are explained with reference to a graph in which the horizontal axis indicates time and the vertical axis indicates stations, but this is an example for explaining the concept of the dimension parameters, and the types and application forms of the dimension parameters are not limited to this.

[0121] FIG. 8 is a diagram showing an example of a case where a time parameter L according to an embodiment of the present disclosure is set as a dimension parameter. In FIG. 8, the time parameter "L" is the maximum time range (e.g., 60 minutes) of a search for extracting information related to an inconsistent KPI (a subset of statistical information) from statistical information, "L1" indicates the time when an inconsistency in a specific KPI occurs, and "L2" indicates the time when the inconsistency in the KPI is resolved. "x 5 " indicates the time range corresponding to the inconsistency KPI (i.e., the time span from L1 to L2). "M" indicates the maximum range of vehicles to be searched, and "N" indicates the maximum range of stations to be searched. "t" indicates the step size (e.g., 5 minutes) for searching the time range defined in the time parameter L. The target time "l" is an integer incremented by step size t in the range from 0 to L that identifies a specific time when performing a search over the range of the time parameter L.

[0122] In this way, by setting the time parameter L as the dimension parameter, it is possible to identify and extract information (a subset of the statistical information) corresponding to the time range in which the inconsistent KPI occurred from the statistical information. In addition, by using the information corresponding to the time range in which the inconsistent KPI occurred to determine the causal relationship regarding the inconsistent KPI, it is possible to determine the causal relationship regarding the inconsistent KPI with high accuracy.

[0123] FIG. 9 is a diagram showing an example of a case where a vehicle parameter M according to an embodiment of the present disclosure is set as a dimension parameter. In FIG. 9, the vehicle parameter "M" is the maximum range (e.g., 10 vehicles in front and behind) of vehicles to be searched for extracting information related to the inconsistent KPI (a subset of the statistical information) from the statistical information, "M1" indicates a vehicle in which an inconsistency in a specific KPI has occurred, and "M2" indicates a vehicle in which the inconsistency in the KPI has been resolved. 5" indicates the range of vehicles corresponding to the inconsistent KPI (i.e., the width from M1 to M2). If M1=M2, it indicates that the inconsistent KPI occurs for only one vehicle. "t" indicates the step size (e.g., one vehicle) for searching the vehicle range defined in the vehicle parameter M. The target vehicle "m" is an integer that identifies a particular vehicle when performing a search over the range of the vehicle parameter M, and is incremented by the step size t in the range from 0 to M.

[0124] In this way, by setting the vehicle parameter M as the dimension parameter, it is possible to identify and extract information (a subset of the statistical information) corresponding to the range of vehicles in which an inconsistent KPI has occurred from the statistical information. In addition, by using the information corresponding to the vehicle in which an inconsistent KPI has occurred to determine the causal relationship regarding the inconsistent KPI, it is possible to determine the causal relationship regarding the inconsistent KPI with high accuracy.

[0125] FIG. 10 is a diagram showing an example of setting a station parameter N as a dimension parameter according to an embodiment of the present disclosure. In FIG. 10, the station parameter "N" is the maximum range (e.g., 10 stations before and after) of stations to be searched for extracting information related to the inconsistent KPI (a subset of the statistical information) from the statistical information, "N1" indicates a station where a specific KPI inconsistency occurred, and "N2" indicates a station where the KPI inconsistency has been resolved. "x 5 " indicates the range of stations that correspond to the inconsistent KPI (i.e., the range from N1 to N2). If N1=N2, it indicates that the inconsistent KPI occurs for only one station. "t" indicates the step size (e.g., one station) for searching the station range defined in the station parameter N. The target station "n" is an integer that identifies a particular station when performing a search over the range of station parameter N, and is incremented by step size t in the range from 0 to N.

[0126] In this way, by setting the station parameter N as a dimension parameter, it is possible to identify and extract information (a subset of statistical information) corresponding to the range of stations where an inconsistent KPI has occurred from the statistical information. In addition, by using the information corresponding to the station where an inconsistent KPI has occurred to determine the causal relationship regarding the inconsistent KPI, it is possible to determine the causal relationship regarding the inconsistent KPI with high accuracy.

[0127] Next, a cause-and-effect diagram according to an embodiment of the present disclosure will be described with reference to FIG.

[0128] 11 is a diagram illustrating an example of a causal relationship diagram 1100 according to an embodiment of the present disclosure. As described above, the causal relationship determination unit 431 according to an embodiment of the present disclosure can determine a causal relationship between an inconsistent KPI that does not satisfy a required threshold and a related variable in a subset of statistical information. In an embodiment, the causal relationship determination unit 431 may visualize the determined causal relationship as a causal relationship diagram 1100 as shown in FIG. 11 and provide it to a user.

[0129] The causal diagram 1100 shown in Fig. 11 is a causal loop diagram (CLD) that expresses the presence or absence of a causal relationship between an inconsistent KPI and a related variable in the form of a directed graph network. In the causal diagram 1100, each of the KPIs 1110 related to the transportation service and the related variables 1120 in the subset of statistical information can be represented as a different node. Also, the causal relationship existing between the KPIs 1110 and the related variables 1120 can be represented as a bidirectional arrow. As described above, these KPIs 1110 are KPIs stored in the Transportation Service KPI Information DB 402, such as operational costs, projected revenues, environmental impact, and energy efficiency of a transportation plan, and the related variables 1120 are related variables in a subset of statistical information extracted from the Transportation Service Information DB 232 and the Community Information DB 234.

[0130] As an example, in the causal diagram 1100, C1 " 1111 is "KPIP2 ", "KPI S2 " "Data B1 " and "Data S4 " is connected to "KPI C1 " 1111 is "KPI P2 " and "KPI S2 " and "Data B1 " and "Data S4 It can be said that there is a causal relationship between the related variables and KPIs. C1 " 1111 is "Congestion level", "KPI P2 " is "Number of trains", "KPI S2 " corresponds to the KPI "passenger waiting time" and "Data B1 " is "rainy weather", "Data S4 " may correspond to a related variable to "residential population." In addition, this "KPI C1 The causal relationship regarding "1111" can be expressed by a causal relationship formula generated when the causal relationship determination unit 431 determines the causal relationship, as in Formula 3 shown below.

number

[0131] As shown in Figure 11, the causal relationships determined for inconsistent KPIs are visualized as a causal relationship diagram 1100 as shown in Figure 11 and provided to the user, allowing the user to easily understand other KPIs and related variables that affect a specific KPI.

[0132] Next, a dimension parameter setting interface according to an embodiment of the present disclosure will be described with reference to FIG.

[0133] 12 is a diagram showing a dimension parameter setting interface 1200 according to an embodiment of the present disclosure. As described above, in the transportation plan management means according to an embodiment of the present disclosure, information (a subset of statistical information) used to determine the causal relationship is identified based on dimension parameters set based on the influence range of the inconsistent KPI. These dimension parameters may be set by the user, for example, through the dimension parameter setting interface 1200 shown in FIG.

[0134] As shown in FIG. 12, a dimension parameter setting interface 1200 may include a parameter name setting window 1205, a range direction setting window 1210, a maximum value setting window 1215, a step size setting window 1220, an add / delete button 1225, and a confirm button 1230.

[0135] The parameter name setting window 1205 is an interface window for setting the name of a dimension parameter. In an embodiment, the user may select a specific dimension parameter from among dimension parameters prepared in advance. In an embodiment, the user may custom set a new dimension parameter. As an example, the dimension parameters may be set as follows: "time" that specifies the time range of a search performed on statistical information, "number of trains" that specifies the range of an object (target train), "number of stations" that specifies the spatial range, "energy consumption per kilometer" as a feature for specifying the range of an object (target train), etc.

[0136] The range direction setting window 1210 is an interface window for specifying whether the search range of a particular dimension parameter should include before, after, or both before and after the target element (target time, target station, target vehicle, etc.).

[0137] The maximum value setting window 1215 is an interface window for specifying the maximum value of the search range of a specific dimension parameter. For example, as shown in Fig. 12, the maximum value of the dimension parameter with "time" may be set to "60 minutes," and the maximum value of the dimension parameter with "number of trains" may be set to "20."

[0138] The step size setting window 1220 is an interface window for specifying the minimum step value of a particular dimension parameter. In principle, the smaller the step size, the finer the subset of statistical information is extracted, and the more accurate the causal relationship determination becomes possible. However, since the processing time increases, it is desirable to set this step size taking into consideration the desired accuracy of the causal relationship determination and the processing time.

[0139] The add / delete button 1225 is a button for adding a new dimension parameter or deleting an existing dimension parameter.

[0140] The confirm button 1230 is a button for confirming and saving all the information related to the dimension parameters after they have been input.

[0141] As described above, the dimension parameter setting interface 1200 described with reference to Fig. 12 makes it possible to set a dimension parameter indicating the range of influence of an inconsistent KPI. Furthermore, by using the dimension parameter set in this way, it is possible to extract a subset of statistical information related to a specific inconsistent KPI from among the statistical information, enabling causal relationship determination with high accuracy.

[0142] As described above, in the transportation plan management means according to the embodiment of the present disclosure, when an inconsistent KPI that does not satisfy a predetermined required threshold is identified in an existing transportation plan for a transportation service, a causal relationship between the inconsistent KPI and a related variable that affects the inconsistent KPI is determined, and a recommended variable change action for the related variable is determined based on the determined causal relationship. After that, by reflecting the determined variable change action in the existing transportation plan, a revised transportation plan can be generated in which the inconsistent KPI is revised to satisfy the required threshold.

[0143] In the transportation plan management means according to the embodiment of the present disclosure, the causal relationship regarding the inconsistent KPI is determined based on statistical information including information regarding the transportation service (e.g., infrastructure, vehicle configuration, passenger movement) and information regarding the local community to which the transportation service is provided (e.g., population, resident movement, tax, economy, customer satisfaction). In this way, by identifying related variables that affect a specific KPI from a wide range of information, it becomes possible to propose various variable change operations to the user to improve a specific inconsistent KPI, thereby improving the flexibility of the transportation plan.

[0144] In addition, in the transportation plan management means according to the embodiment of the present disclosure, information (a subset of statistical information) used to determine the causal relationship related to the inconsistent KPI is extracted from the statistical information based on dimension parameters that define the search range (time range, spatial range, range of the object) that takes into account the range of influence of the inconsistent KPI. In this way, by using information limited to a range related to a specific inconsistent KPI, rather than all statistical information, to determine the causal relationship, it is possible to reduce processing time, save computing resources, and perform more detailed and accurate causal relationship determination.

[0145] In addition, in the transportation plan management means according to the embodiment of the present disclosure, after determining the causal relationship regarding the inconsistent KPI, a causal relationship diagram visualizing the causal relationship between the inconsistent KPI and related variables, various variable change operations for improving the inconsistent KPI, and information on the change amount of the KPI when the variable change operation is adopted are output to the user. As a result, the user who has confirmed this information can easily grasp the related variables that affect a specific inconsistent KPI, the countermeasures for improving the KPI, and the impact of each measure on the KPI, thereby improving various KPIs such as operating costs, expected revenue, environmental impact, and energy efficiency in the transportation plan, and realizing the efficiency of the operation of the transportation service.

[0146] In this way, according to the transportation plan management means of an embodiment of the present disclosure, it is possible to generate a revised transportation plan with improved KPIs after analyzing the reason why the KPIs do not meet the required thresholds while taking into account the causal relationships between numerous variables and KPIs for the transportation plan of a transportation service.

[0147] As described above, the transportation plan management means according to the embodiment of the present disclosure includes the following aspects.

[0148] (Aspect 1) A transportation planning management device, A processor, a memory, and a storage unit are provided, The storage unit is existing transportation plan information indicating existing transportation plans for a given transportation service; Transportation service KPI information including KPIs indicating performance indicators for the existing transportation plan information; and statistical information relating to said transportation services; The memory includes: an inconsistent KPI identification unit that identifies an inconsistent KPI that does not satisfy a predetermined required threshold among the KPIs based on the existing transportation plan information and the transportation service KPI information; a causal relationship determination unit that analyzes the inconsistent KPI and the statistical information and determines a causal relationship between the inconsistent KPI and a related variable in a subset of statistical information extracted from the statistical information; A transportation plan generating unit that generates revised transportation plan information by using the existing transportation plan information and the determined causal relationship so that the inconsistency KPI satisfies the required threshold value; The transportation plan management device according to claim 1, further comprising: a processing instruction for causing the processor to function as a

[0149] (Aspect 2) receiving, from a user, an input of a dimension parameter that specifies a search range of the statistical information based on an impact range of the inconsistent KPI; an information extraction unit that extracts, from the statistical information, a subset of the statistical information that corresponds to the search range defined by the dimension parameters; 2. The transportation plan management device according to claim 1, further comprising:

[0150] (Aspect 3) The dimension parameters are: The inconsistency KPI includes any one of a time parameter that defines a time range of the inconsistency KPI, a location parameter that defines a spatial range of the inconsistency KPI, a vehicle parameter that defines an object range of the inconsistency KPI, and a feature parameter that defines an object range of the inconsistency KPI. 3. A transportation plan management device according to aspect 2.

[0151] (Aspect 4) Calculating the degree of influence of each of the related variables determined to have a causal relationship with the inconsistent KPI on the inconsistent KPI; Identifying a key variable among the related variables whose calculated influence satisfies a predetermined influence criterion; a hypothesis inference unit that generates inconsistency hypothesis information indicating a reason why the inconsistency KPI does not satisfy the required threshold value based on the identified main variable; 4. The transportation plan management device according to any one of aspects 1 to 3, further comprising:

[0152] (Aspect 5) an operation determination unit that generates variable change operation information indicating a recommended variable change operation for the main variable so that the inconsistency KPI satisfies the required threshold based on the generated inconsistency hypothesis information; A KPI change calculation unit that calculates the amount of change in the inconsistency KPI when the variable change operation is performed; 5. The transportation plan management device according to claim 4, further comprising a revision suggestion unit having:

[0153] (Aspect 6) The transportation plan generation unit outputting a causal relationship diagram showing a causal relationship between the inconsistency KPI and the main variable, the inconsistency hypothesis information, the variable change operation information, and an amount of change in the inconsistency KPI when the variable change operation is performed; When an approval input for approving the variable change operation is received, the variable change operation is reflected in the existing transportation plan information, thereby generating the revised transportation plan information. 6. A transportation plan management device according to claim 5,

[0154] (Aspect 7) The statistical information is infrastructure information indicating existing infrastructure in the area in which the transportation service is provided; map information relating to the area in which said transportation services are provided; weather information relating to the area in which said transportation services are provided; Demographic information regarding the area in which said transportation services are provided; Population mobility information relating to the area in which the transportation service is provided; Tax information relating to the region in which said transportation services are provided; Vehicle configuration information indicating a configuration of vehicles used in the transportation service; Passenger movement information indicating the movement history of passengers using the transportation service; and Customer satisfaction information indicating customer satisfaction with the transportation service. 7. The transportation plan management device according to any one of aspects 1 to 6.

[0155] Although the embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment, and various modifications are possible without departing from the gist of the present invention. [Explanation of symbols]

[0156] 150 Transportation Planning and Management Application 200 Transportation Planning and Management System 210 Transportation Planning and Management Device 220 Memory 222 KPI analysis department 224 Causal Relationship Management Department 226 Revision Proposal Department 228 Transportation Planning and Management Department 232 Transport Service Information DB 234 Community Information DB 244 processors 246 Input / output section 250 Communication Network 260 User Terminals

Claims

1. A transportation planning management device, A processor, a memory, and a storage unit are provided, The storage unit is existing transportation plan information indicating existing transportation plans for a given transportation service; Transportation service KPI information including KPIs indicating performance indicators for the existing transportation plan information; and statistical information relating to said transportation services; The memory includes: an inconsistent KPI identification unit that identifies an inconsistent KPI that does not satisfy a predetermined required threshold among the KPIs based on the existing transportation plan information and the transportation service KPI information; a causal relationship determination unit that analyzes the inconsistent KPI and the statistical information and determines a causal relationship between the inconsistent KPI and a related variable in a subset of statistical information extracted from the statistical information; A transportation plan generating unit that generates revised transportation plan information by using the existing transportation plan information and the determined causal relationship so that the inconsistent KPI satisfies the required threshold value; The transportation plan management device according to claim 1, further comprising: a processing instruction for causing the processor to function as a

2. receiving, from a user, an input of a dimension parameter that specifies a search range of the statistical information based on an influence range of the inconsistent KPI; an information extraction unit that extracts, from the statistical information, a subset of the statistical information that corresponds to the search range defined by the dimension parameters; The transportation plan management device according to claim 1 , further comprising:

3. The dimension parameters are: The inconsistent KPI includes any one of a time parameter that defines a time range of the inconsistent KPI, a location parameter that defines a spatial range of the inconsistent KPI, a vehicle parameter that defines an object range of the inconsistent KPI, and a feature parameter that defines an object range of the inconsistent KPI.

3. The transportation plan management device according to claim 2.

4. Calculate the degree of influence on the inconsistent KPI for each of the related variables determined to have a causal relationship with the inconsistent KPI; Identifying a key variable among the related variables whose calculated influence satisfies a predetermined influence criterion; a hypothesis inference unit that generates inconsistency hypothesis information indicating a reason why the inconsistency KPI does not satisfy the required threshold value based on the identified main variable; The transportation plan management device according to claim 1 , further comprising:

5. an operation determination unit that generates variable change operation information indicating a recommended variable change operation for the main variable so that the inconsistency KPI satisfies the required threshold value based on the generated inconsistency hypothesis information; A KPI change calculation unit that calculates a change amount of the inconsistent KPI when the variable change operation is performed; The transportation plan management device according to claim 4, further comprising an amendment suggestion unit having:

6. The transportation plan generation unit outputting a causal relationship diagram showing a causal relationship between the inconsistent KPI and the main variable, the inconsistency hypothesis information, the variable change operation information, and an amount of change in the inconsistent KPI when the variable change operation is performed; When an approval input for approving the variable change operation is received, the variable change operation is reflected in the existing transportation plan information, thereby generating the revised transportation plan information.

6. The transportation plan management device according to claim 5 .

7. The statistical information is infrastructure information indicating existing infrastructure in the area in which the transportation service is provided; map information relating to the area in which said transportation services are provided; weather information relating to the area in which said transportation services are provided; Demographic information regarding the area in which said transportation services are provided; Population mobility information relating to the area in which the transportation service is provided; Tax information relating to the region in which said transportation services are provided; Vehicle configuration information indicating a configuration of vehicles used in the transportation service; Passenger movement information indicating the movement history of passengers using the transportation service; and Customer satisfaction information indicating customer satisfaction with the transportation service.

2. The transportation plan management device according to claim 1 .

8. A transportation plan management method implemented by computer software in a transportation plan management device, comprising: The transportation planning and management device A processor; a memory for storing program instructions; A storage unit, The storage unit is existing transportation plan information indicating existing transportation plans for a given transportation service; Transportation service KPI information including KPIs indicating performance indicators for the existing transportation plan information; and statistical information relating to said transportation services; The program instructions stored in the memory include: Identifying an inconsistent KPI that does not satisfy a predetermined required threshold among the KPIs based on the existing transportation plan information and the transportation service KPI information; A step of setting dimension parameters including any one of a time parameter that defines a time range of the inconsistent KPI, a position parameter that defines a spatial range of the inconsistent KPI, and a feature parameter that defines an object range of the inconsistent KPI; extracting a subset of the statistical information corresponding to a range defined by the dimension parameters from the statistical information; analyzing the misaligned KPIs and the subset of statistical information to determine causal relationships between the misaligned KPIs and related variables in the subset of statistical information; A step of calculating an influence degree on the inconsistent KPI for each of the related variables determined to have a causal relationship with the inconsistent KPI; identifying a key variable among the related variables whose calculated influence satisfies a predetermined influence criterion; generating mismatch hypothesis information indicating the reason why the mismatch KPI does not satisfy the required threshold based on the identified key variables; generating variable change action information indicating a recommended variable change action for the main variable so that the mismatch KPI satisfies the required threshold based on the generated mismatch hypothesis information; Calculating the amount of change in the inconsistent KPI when the variable change operation is performed; A step of outputting to a user a causal relationship diagram showing a causal relationship between the inconsistency KPI and the main variable, the inconsistency hypothesis information, the variable change operation information, and an amount of change in the inconsistency KPI when the variable change operation is performed; When an approval input for approving the variable change operation is received, the variable change operation is reflected in the existing transportation plan information, thereby generating revised transportation plan information in which the inconsistent KPI is revised to satisfy the required threshold value; The transportation planning and management method is characterized by having the processor execute the above steps.

Citation Information

Patent Citations

  • Automatic operation controller

    JP2019092347A