Correction processing system, correction processing program, and recording medium

The correction processing system addresses discrepancies in reservation management systems by dividing operation histories into seat units and generating correction data to align aggregated values with actual sales, ensuring accurate sales performance calculation.

JP2025140552AActive Publication Date: 2025-09-29RAILWAY INFORMATION SYST
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2024040021
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-03-14
Publication Date
2025-09-29
Estimated Expiration
2044-03-14

AI Technical Summary

Technical Problem

Existing reservation management systems face challenges in accurately calculating sales performance due to discrepancies in operation logs, particularly when changes in boarding or disembarking stations occur, making it difficult to identify and correct these discrepancies in large volumes of data.

Method used

A correction processing system that corrects operation histories by dividing them into seat units, identifies specific types of discrepancies, and generates correction data to align aggregated values with actual sales results, using an operation history acquisition, seat unit history creation, and corrected history output mechanism.

Benefits of technology

Enables accurate calculation of seat sales performance by correcting operation histories to match actual sales figures, ensuring precise analysis even in complex reservation scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025140552000001_ABST
    Figure 2025140552000001_ABST
Patent Text Reader

Abstract

To provide a correction processing system for correcting an operation history of a reservation management system that manages reservations and sales of seats for transportation means, so as to enable accurate calculation of sales results based on the operation history (operation log) of the reservation management system.SOLUTION: A correction processing system 1 comprises: control means 2 for controlling all of primary functions of the correction processing system 1; communication means 3 capable of communicating with a reservation management system 10; operation history acquisition means 4 for acquiring an operation history from the reservation management system 10; seat-unit history creation means 5 for creating a seat-unit history by dividing the operation history into seats; corrected history output means 6 for determining whether or not the seat-unit history for each seat corresponds to a specific type, generating, based on the determination result, correction data for correcting the seat-unit history of the specific type, and outputting a corrected history obtained by adding the correction data to the seat-unit history; and recording means 7 for recording the corrected history.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 correction processing system for correcting the operation history of a reservation management system that manages the reservation and sale of seats on transportation means, a correction processing program, and a recording medium on which this correction processing program is recorded. [Background technology]

[0002] Nowadays, reservations and purchases of seats for transportation such as railways are made via networks such as the Internet from terminals installed at the ticket counters of railway companies or from terminals of the purchaser. Requests for reservation and purchase of seats received via these networks are processed by a reservation management system that manages all seat reservations and sales. For example, Patent Document 1 describes a seat reservation system that receives seat reservation information regarding reserved seats on trains from an operating terminal connected to a network, and enables inquiries about available seats based on the past number of available seats and the number of passengers disembarking at each stop.

[0003] In addition to seat reservations, the reservation management system also accepts requests for changes and cancellations to reservation details. Each of these requests is processed by the reservation management system and then recorded as an operation log of the reservation management system. This operation log contains various information related to seat reservations, reservation cancellations, and reservation changes (hereinafter, "reservation sales, reservation cancellations, and reservation changes" are referred to as "reservation sales, etc."). For example, if the means of transportation is rail, the operation log contains information such as the train number, which is an identification number used to identify the train, the train's departure date, seat location, and the names of boarding and alighting stations. Therefore, by utilizing the accumulated operation log as so-called big data, it becomes possible to analyze sales performance and understand demand from various perspectives, such as by train, by departure date, or by boarding and alighting station. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 5952224 Summary of the Invention [Problem to be solved by the invention]

[0005] Since operation logs are accumulated for each request received by the reservation management system, in other words, for each operation of the reservation management system, they must be aggregated according to certain standards in order to analyze seat sales performance.Conventionally, for example, for operation logs with the same train type, departure date, and boarding / alighting station names, a report would be created by treating the aggregate value obtained by subtracting the number of operation logs related to reservation cancellations from the total number of operation logs related to reservation sales, without taking reservation changes into consideration, or, when reservation changes are taken into consideration, treating changes to reservation details as new reservation sales, and listing the total number of operation logs related to reservation changes alongside the above-mentioned aggregate value, and treating these as sales performance when creating a report.

[0006] However, in the above-mentioned reports, discrepancies between the total value and actual sales occurred when, for example, the boarding station or disembarking station or both were changed, the boarding section was changed, or part of the boarding section was canceled, etc. Furthermore, in reservation management systems that collectively process requests related to advance sales, etc., the number of operation logs was enormous, making it practically difficult to identify the cause of discrepancies when they occurred and correct them each time.

[0007] Therefore, the present invention aims to provide a correction processing system, a correction processing program, and a recording medium on which this correction processing program is recorded, which corrects the operation history (operation log) of a reservation management system that manages the reservation and sale of seats on transportation means in order to enable accurate calculation of sales results based on the operation history (operation log) of the reservation management system. [Means for solving the problem]

[0008] In order to solve the above problem, the correction processing system of the present invention is a correction processing system that corrects the operation history of a reservation management system that manages the reservation and sale of seats for a means of transportation in order to calculate sales results for the seats based on the operation history of the reservation management system, and is equipped with an operation history acquisition means that acquires the operation history from the reservation management system, a seat unit history creation means that creates a seat unit history by dividing the operation history into seat units, and a corrected history output means that determines whether the seat unit history for each seat corresponds to a specific type, and if the seat unit history corresponds to the specific type, generates correction data for correcting the seat unit history of the specific type, and outputs a corrected history in which this correction data is added to the seat unit history, wherein the specific type is a type that causes an aggregated value obtained by aggregating the seat unit history to contradict the sales results, and the corrected history output means generates the correction data to make the aggregated value match the sales results.

[0009] In the above invention, a recording means for recording the corrected history is provided, and the corrected history output means may have a same seat history addition determination function for searching the corrected histories recorded by the recording means for a same seat history that is the corrected history of the same seat as the seat unit history created by the seat unit history creation means, and, if a same seat history is found, including the same seat history in the seat unit history for each seat, determining whether or not it corresponds to the specific type.

[0010] In the above invention, the corrected history output means may identify the seat based on the operation date of the transportation means, the type of the transportation means, and the position of the seat, which are included in the operation history.

[0011] In the above invention, the operation history may include a sales history indicating that the seat was sold by specifying a travel section, and a cancellation history indicating that the sale of the seat was canceled by specifying a specified section.

[0012] In the above invention, the specific type may be a first type consisting only of the cancellation history, and the correction data may be the sales history for correction to offset the cancellation history of the first type.

[0013] In the above invention, the specific type may be a second type consisting only of multiple sales histories specifying the same travel section, and the correction data may be a cancellation history for correction to offset sales histories other than the latest sales history among the sales histories of the second type.

[0014] In the above invention, the specific type is a third type consisting of the sales history and the cancellation history in which the specified section is included within the travel section of the sales history, and the correction data may be the cancellation history for correction to offset the sales history of the third type, the sales history for correction to offset the cancellation history of the third type, and the sales history for correction to restore the portion of the sales history of the third type in which the travel section does not overlap with the specified section.

[0015] In the above invention, the specific type is a fourth type consisting of the sales history and the cancellation history in which part of the travel section of the sales history overlaps with part of the specified section, and the correction data may be the cancellation history for correction to offset the sales history of the fourth type, the sales history for correction to offset the cancellation history of the fourth type, and the sales history for correction to restore the part of the sales history of the fourth type in which the travel section does not overlap with the specified section.

[0016] In the above invention, the specific type is a fifth type consisting of the sales history and the cancellation history in which the travel section of this sales history is included within the specified section, and the correction data may be the cancellation history for correction to offset the sales history of the fifth type, and the sales history for correction to offset the cancellation history of the fifth type.

[0017] In the above invention, the specific type is a sixth type consisting of the sales history and the cancellation history in which the specified section does not overlap with the travel section of this sales history, and the correction data may be the sales history for correction to offset the cancellation history of the sixth type.

[0018] In the above invention, the specific type is a seventh type consisting of a plurality of sales histories and a cancellation history in which all of the travel sections of each of these sales histories are included within the specified section, and the correction data may be the cancellation history for correction to offset each of the sales histories corresponding to each of the sales histories of the seventh type, and the sales history for correction to offset the cancellation history of the seventh type.

[0019] In the above invention, the specific type is an eighth type consisting of a plurality of sales histories and a cancellation history in which at least one of the travel sections in these sales histories is included within the specified section and at least one of the travel sections overlaps with a portion of the specified section, and the correction data may be the cancellation history for correction to offset each of the sales histories corresponding to each of the sales histories of the eighth type, the sales history for correction to offset the cancellation history of the eighth type, and the sales history for correction to restore the portion of the sales history of the eighth type in which the travel section does not overlap with the specified section.

[0020] In order to solve the above problem, the correction processing program of the present invention corrects the operation history of a reservation management system that manages the reservation and sale of seats for a means of transportation in order to calculate sales results for the seats based on the operation history of the reservation management system, and includes: an operation history acquisition step that acquires the operation history from the reservation management system; a seat unit history creation step that creates a seat unit history by dividing the operation history into seat units; and a corrected history output step that determines whether the seat unit history for each seat corresponds to a specific type, and if the seat unit history corresponds to the specific type, generates correction data for correcting the seat unit history of the specific type, and outputs a corrected history by adding this correction data to the seat unit history, wherein the specific type is a type that causes an aggregated value of the seat unit history to contradict the sales results, and the corrected history output step causes a computer to execute the steps of: generating the correction data to make the aggregated value match the sales results.

[0021] In order to solve the above problem, a computer-readable recording medium according to the present invention is characterized in that the correction processing program is recorded thereon. [Effects of the Invention]

[0022] According to the correction processing system of the present invention, when the seat unit history for each seat is of a specific type (a type that causes the aggregated value of the seat unit history to contradict the seat sales performance), the corrected history output means generates correction data for correcting the seat unit history of the specific type so that the aggregated value of the seat unit history matches the seat sales performance, and outputs a corrected history in which this correction data is added to the seat unit history. Therefore, by aggregating the corrected history that reflects the correction data, it is possible to calculate an accurate seat sales performance.

[0023] According to the correction processing system of the present invention, the corrected history output means has a same-seat history addition determination function, and searches for same-seat history from the corrected history recorded by the recording means, and if same-seat history is found, it determines whether the same-seat history is included in the seat-unit history for each seat and falls under a specific type. Therefore, even if there is seat-unit history that has already been processed by the correction processing system, it is possible to search for same-seat history from this processed seat-unit history and determine whether the seat-unit history including the same-seat history falls under a specific type. Therefore, it is possible to determine the seat-unit history for each seat without omission.

[0024] According to the correction processing system of the present invention, the corrected history output means identifies the seat based on the operation date of the means of transport, the type of transport, and the seat position included in the operation history, thereby enabling accurate seat identification.

[0025] According to the correction processing system of the present invention, the operation history includes a sales history indicating that a seat was sold by specifying a boarding section, and a cancellation history indicating that a seat sale was canceled by specifying a specific section. Therefore, a cancellation history in the operation history in which a section that matches the boarding section specified in the sales history is specified as the specific section can be recognized as a cancellation history in which the entire sales history is canceled, and a cancellation history in which a section that partially matches the boarding section specified in the sales history is specified as the specific section can be recognized as a change history for changing the boarding section in the sales history. Therefore, the inclusion of a sales history and a cancellation history in the operation history makes the system capable of responding to changes in reservation details.

[0026] According to the correction processing system of the present invention, the specific type is a first type consisting only of cancellation history, and the correction data is a sales history for correction to offset the cancellation history of the first type. Furthermore, according to the correction processing system of the present invention, the specific type is a second type consisting only of multiple sales histories specifying the same travel section, and the correction data is a cancellation history for correction to offset sales histories other than the most recent sales history among the sales histories of the second type. Furthermore, according to the correction processing system of the present invention, the specific type is a third type consisting of a sales history and a cancellation history in which a specified section is included within the travel section of this sales history, and the correction data is a cancellation history for correction to offset the sales history of the third type, a sales history for correction to offset the cancellation history of the third type, and a sales history for correction to restore the portion of the sales history of the third type in which the travel section does not overlap with the specified section.

[0027] Furthermore, according to the correction processing system of the present invention, the specific type is a fourth type consisting of a sales history and a cancellation history in which part of the travel section of this sales history overlaps with part of a specified section, and the correction data is a cancellation history for correction to offset the sales history of the fourth type, a sales history for correction to offset the cancellation history of the fourth type, and a sales history for correction to restore the part of the sales history of the fourth type in which the travel section does not overlap with the specified section. Furthermore, according to the correction processing system of the present invention, the specific type is a fifth type consisting of a sales history and a cancellation history in which the travel section of this sales history is included within a specified section, and the correction data is a cancellation history for correction to offset the sales history of the fifth type, and a sales history for correction to offset the cancellation history of the fifth type. Furthermore, according to the correction processing system of the present invention, the specific type is a sixth type consisting of a sales history and a cancellation history in which a specified section does not overlap with the travel section of this sales history, and the correction data is a sales history for correction to offset the cancellation history of the sixth type.

[0028] Furthermore, according to the correction processing system of the present invention, the specific type is a seventh type consisting of multiple sales histories and cancellation histories in which all of the travel sections of each of these sales histories are included within a specified section, and the correction data is a cancellation history for correction to offset each sales history corresponding to each sales history of the seventh type, and a sales history for correction to offset the cancellation history of the seventh type. Furthermore, according to the correction processing system of the present invention, an eighth type is composed of a plurality of sales histories and cancellation histories in which at least one of the travel sections in these sales histories is included within a specified section and at least one section overlaps with a portion of the specified section, and the correction data are cancellation histories for correction to offset each sales history corresponding to each sales history of the eighth type, sales histories for correction to offset the cancellation histories of the eighth type, and sales histories for correction to restore the portions of the sales history of the eighth type whose travel sections do not overlap with the specified section of the cancellation history of the eighth type.

[0029] If the corrected history has been corrected to correspond to the specific types described above, the aggregated value will match the sales performance, making it possible to accurately calculate sales performance based on the operation history of the reservation management system. Furthermore, by using the correction processing program of the present invention or a recording medium on which this correction processing program is recorded, it is possible to achieve the same effects as the above-mentioned correction processing system. [Brief explanation of the drawings]

[0030] [Figure 1] FIG. 1 is an explanatory diagram showing the relationship between a correction processing system and a reservation management system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a functional block diagram showing the outline of functions of the correction processing system and the reservation management system according to the embodiment of the present invention. [Figure 3] FIG. 3 is an explanatory diagram showing an operation history management table in which operation histories of the correction processing system according to the embodiment of the present invention are collected. [Figure 4] FIG. 4 is an explanatory diagram showing a seat unit history management table in which seat unit histories of the correction processing system according to the embodiment of the present invention are aggregated. [Figure 5] FIG. 5 is an explanatory diagram (1) for explaining a correction pattern by the post-correction history output means of the correction processing system according to the embodiment of the present invention. [Figure 6]FIG. 6 is an explanatory diagram (2) for explaining the correction pattern by the post-correction history output means of the correction processing system according to the embodiment of the present invention. [Figure 7] FIG. 7 is an explanatory diagram (3) for explaining the correction pattern by the post-correction history output means of the correction processing system according to the embodiment of the present invention. [Figure 8] FIG. 8 is a flowchart for explaining an outline of the processing from acquisition of an operation history to creation of a seat-by-seat history in the correction processing system according to the embodiment of the present invention. [Figure 9] FIG. 9 is a flowchart for explaining an outline of the processing from searching for a same seat history to outputting a corrected history in the correction processing system according to the embodiment of the present invention. [Figure 10] FIG. 10 is a flowchart (1) for explaining the process by the post-correction history output means in the correction processing system according to the embodiment of the present invention. [Figure 11] FIG. 11 is a flowchart (2) for explaining the process by the post-correction history output means in the correction processing system according to the embodiment of the present invention. [Figure 12] FIG. 12 is a flowchart (3) for explaining the process by the post-correction history output means in the correction processing system according to the embodiment of the present invention. [Figure 13] FIG. 13 is a flowchart (4) for explaining the process by the post-correction history output means in the correction processing system according to the embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0031] Next, an embodiment of a correction processing system according to the present invention will be described with reference to Figures 1 to 13. The transportation means of the correction processing system of this embodiment includes all transportation means for transporting people and luggage, such as conventional trains, buses other than trains, ships, and passenger planes. In the following explanation, an example will be given in which the transportation means is a Shinkansen train.

[0032] FIG. 1 is an explanatory diagram showing the relationship between a correction processing system 1 and a reservation management system 10 according to this embodiment. The reservation management system 10 accepts reservations and sales of Shinkansen seats and manages all processes related to reservations and sales. The reservation management system 10 is connected to a network N and accepts requests for seat reservations, reservation cancellations, and reservation changes (hereinafter, "reservation purchases, reservation cancellations, and reservation changes" are referred to as "reservation purchases, etc.") via the network N from external devices such as reservation terminals 20 installed at railway companies and mobile terminals 30 such as smartphones of potential purchasers. Network N includes all kinds of networks, such as the Internet, in-house LANs (Local Area Networks) constructed using dedicated lines, inter-company LANs, WANs (Wide Area Networks), etc., and is connected to network N using either wired or wireless communication methods.

[0033] A request for a reservation purchase or the like received from an external device is accepted as an operation instruction for executing a predetermined operation in the reservation management system 10. After the operation instruction is processed by the reservation management system 10, it is recorded in the reservation management system 10 as a history of operations (operation history) related to the reservation and sale of Shinkansen seats in the reservation management system 10. The accumulated and recorded operation history is output as a report and can be used as so-called big data for calculating the sales performance of Shinkansen seats, etc. However, if the operation history recorded in the reservation management system 10 is simply added and subtracted without any processing and totaled, the total value will be inconsistent with the actual sales performance of seats. Therefore, the correction processing system 1 corrects the operation history obtained from the reservation management system 10 based on predetermined conditions, thereby preventing the total value calculated from the operation history from being inconsistent with the actual sales performance.

[0034] FIG. 2 is a functional block diagram showing the outline of functions of the correction processing system 1 and the reservation management system 10. As shown in FIG. The reservation management system 10 is a server capable of processing and recording large volumes of electronic data, such as requests for seat reservations and purchases, and operation history related to advance sales, etc., and is equipped with a control means 11 that comprehensively controls the main functions of the reservation management system 10, a communication means 12 that is connected to the network N and is capable of communicating with external devices via the network N, a reservation management means 13 that collectively manages processing related to Shinkansen seat reservations and sales, etc., and a recording means 14 that records operation history in the reservation management system 10.

[0035] The control means 11 is composed of a microcomputer equipped with a CPU (Central Processing Unit) that performs various processes according to a program, a ROM (Read Only Memory) that is a storage device that stores electronic data such as programs for operating the CPU and from which the electronic data can be read, and a RAM (Random Access Memory) that is a storage device that can both read and write electronic data. The communication means 12 communicates with devices and systems other than the reservation management system 10, for example, external devices such as the reservation terminal 20 and the correction processing system 1. The reservation management means 13 processes requests for reserving and purchasing Shinkansen seats received from external devices as operational instructions for reserving and selling seats to the reservation management system 10. The recording means 14 records the history of operations processed by the reservation management means 13 in a recording device such as an HDD (Hard Disk Drive) or SSD (Solid State Drive) provided in the reservation management system 10.

[0036] The correction processing system 1 includes a control means 2 that controls the main functions of the correction processing system 1, a communication means 3 that can communicate with the reservation management system 10, an operation history acquisition means 4 that acquires operation history from the reservation management system 10, a seat unit history creation means 5 that creates seat unit history by dividing the operation history into seat units, a corrected history output means 6 that determines whether the seat unit history for each seat corresponds to a specific type, generates correction data for correcting the seat unit history of the specific type based on this determination result, and outputs a corrected history in which this correction data is added to the seat unit history, and a recording means 7 that records the corrected history.

[0037] The control means 2 is composed of a microcomputer equipped with a CPU that performs various processes according to a program, a ROM that stores electronic data such as programs for operating the CPU and that can read this electronic data, and a RAM that can both read and write electronic data. The communication means 3 is connected to the reservation management system 10 via either a wired or wireless communication method, and communicates with the reservation management system 10. The operation history acquisition means 4 acquires the operation history recorded in the recording device of the reservation management system 10 by the recording means 14 at predetermined intervals via the communication means 3. The predetermined period is, for example, one day, but can be set to any period. The procedure by which the operation history acquisition means 4 acquires the operation history from the recording device of the reservation management system 10 corresponds to the "operation history acquisition procedure."

[0038] 3 shows an operation history management table 40 that aggregates operation histories acquired from the reservation management system 10 by the operation history acquisition means 4. Records 40a to 40g, which are each an operation history, store various information related to seats that have been reserved or sold in the reservation management system 10. The information stored in each operation history (records 40a to 40g) of the operation history management table 40 includes, in addition to the "departure date" and "departure time" of the Shinkansen, the "operation date" and "operation time" indicating the date and time when the reservation management system 10 accepted and processed the operation instruction, the "train name" of the Shinkansen, the "train number" of the Shinkansen, the "upbound or downbound classification" indicating whether the train is an upbound or downbound train, the "boarding station name" and the "alighting station name" indicating the names of the stations where passengers board and alight, the "operation content" indicating the type of operation history, the "total number of people" indicating the number of people covered by the operation history, and the number of people covered by the operation history. The operation history management table 40 includes information such as "car number" indicating the car in which the target seat is located, "block" indicating the section in which the target seat in the operation history is located, and "seat location" indicating the location of the target seat in the operation history, and each piece of information is stored in the "Departure date", "Departure time", "Operation date", "Operation time", "Train name", "Train number", "Up / Down direction", "Boarding station name", "Departing station name", "Operation content", "Total number of people", "Car number", "Block", and "Seat location" columns.

[0039] Furthermore, among the above-mentioned information, the "operation content" stores information indicating the type of operation history; specifically, it stores either a "sales history" indicating that a Shinkansen seat has been reserved and sold, or a "cancellation history" indicating that a Shinkansen seat reservation has been cancelled, with the "sales history" displayed as "sale" and the "cancellation history" displayed as "cancellation." Furthermore, the "boarding station name" and "descending station name" specified in the operation history (sales history or cancellation history) indicate the boarding section in the sales history or the specified section in the cancellation history. Therefore, based on the information on the "operation content," "boarding station name," and "descending station name," it is possible to identify whether the operation history is a sales history in which a seat was reserved and sold by specifying a boarding section from which station to which station, or a cancellation history in which a reservation and sale was cancelled by specifying a section from which station to which station.

[0040] For example, among the records in the operation history management table 40, record 40a has an "operation content" of "sales," and the "boarding station name" is "Tokyo" and the "descending station name" is "Nagoya," so it can be seen that this is a sales history in which the boarding section is specified as from Tokyo Station to Nagoya Station. On the other hand, for example, record 40d has an "operation content" of "cancel," and the "boarding station name" is "Nagoya" and the "descending station name" is "Shin-Osaka," so it can be seen that this is a cancellation history specifying the route from Nagoya Station to Shin-Osaka Station. Record 40d is a cancellation history corresponding to record 40b, which is a sales history, and also specifies the same "boarding station name" and "descending station name" as record 40b ("boarding station name" is "Nagoya" and "descending station name" is "Shin-Osaka"), so it can be seen that this is a cancellation history that specifies the entire boarding section in the sales history of record 40b (the entire boarding section from Nagoya Station to Shin-Osaka Station) and cancels the reservation sale of that section. In this case, for example, if the "name of disembarking station" in record 40d is "Kyoto," this is a cancellation history that cancels the pre-order sale by specifying a portion (the portion from Kyoto Station to Shin-Osaka Station) of the entire riding section (the entire riding section from Nagoya Station to Shin-Osaka Station) in the sales history of record 40b, and such a cancellation history is a change history that changes part of the content of the pre-order sale.

[0041] Furthermore, each operation history (each record) compiled in the operation history management table 40 includes not only operation history for one seat, but also operation history for which multiple seats are specified. For example, in record 40a, "ABC" is stored in the "seat location," indicating that this operation history is a sales history for the pre-sale of three seats: seats "A," "B," and "C." Therefore, in record 40a, "3" is also stored in the "total number of people," indicating that the number of people targeted in the sales history is three. Furthermore, among the information stored in each operation history (each record), information related to "departure date," "departure time," "train name," "train number," "up / down classification," "car number," "block," and "seat location" is seat identification information that can identify a seat. Note that it is not necessary to use all of the information as seat identification information; for example, if a seat can be identified using only "departure date," "train name," "train number," "car number," and "seat location," only this information may be used, or, in addition to this information, for example, a unique identification number that can identify the seat may be assigned to each seat, and this identification number may be used as seat identification information. The "type" of the Shinkansen is specified using the "train name" and "train number" from the information mentioned above, and the "seat location" of the Shinkansen is specified using the "car number," "block," and "seat location" from the information mentioned above. Furthermore, the "departure date" from the information mentioned above corresponds to the "operation date" of the means of transportation.

[0042] The seat-unit history creation means 5 creates seat-unit histories by dividing the operation history aggregated in the operation history management table 40 by seat units. Fig. 4 shows a seat-unit history management table 50 that aggregates the seat-unit histories created by the seat-unit history creation means 5. When an operation history specifies multiple seats, the seat-unit history creation means 5 divides the operation history by seat units to create seat-unit histories. Here, dividing the operation history by seat units is a concept that includes duplicating an operation history (record) in the operation history management table 40 in which multiple seats are specified, according to the number of seats stored in the "seat position" of that record, and creating a new record by changing the "seat position" information of that record and the duplicated record.

[0043] For example, the seat-unit history creation means 5 divides record 40a, which specifies multiple seats, from the records in the operation history management table 40 into seat units to create a seat-unit history. At this time, the seat-unit history creation means 5 copies two new records from record 40a to match the number of seats in the "seat position" of record 40a (three seats: seats "A," "B," and "C"). Then, for record 40a and the two copied records, the "seat position" is changed to "A," "B," and "C," respectively. The "total number of people" of each record is also changed to "1." In this way, the seat-unit history created corresponding to record 40a is records 50a to 50c (FIG. 4).

[0044] Note that, like the operation history management table 40, the seat-unit history management table 50 has a “Departure Date”, a “Departure Time”, an “Operation Date”, an “Operation Time”, a “Train Name”, a “Train Number”, a “Up / Down Passenger Division”, a “Boarding Station Name”, a “Departure Station Name”, an “Operation Content”, a “Total Number of Passengers”, a “Car”, a “Block”, and a “Seat Location” column, each of which stores information similar to that of each operation history aggregated in the operation history management table 40. Therefore, for example, among the seat-unit histories (records 50a to 50n) aggregated in the seat-unit history management table 50, the information about “Departure Date”, “Train Name”, “Train Number”, “Car”, “Block”, and “Seat Location” of records 50a, 50b, and 50c match the information about “Departure Date”, “Train Name”, “Train Number”, “Car”, “Block”, and “Seat Location” of record 40a, which also indicates that records 50a to 50c are seat-unit histories created corresponding to record 40a.

[0045] Furthermore, for example, the seat-unit history creation means 5 divides record 40d, which specifies multiple seats, among the records in the operation history management table 40, into seat units to create a seat-unit history. At this time, the seat-unit history creation means 5 copies one new record from record 40d to match the number of seats in the "seat position" of record 40d (two seats, "seat D" and "seat E"). Then, for record 40d and the copied record, the "seat position" is changed to "D" and "E", respectively. The "total number of people" of each record is also changed to "1". The seat-unit histories created in this way corresponding to record 40d are records 50g and 50h (FIG. 4). In this case too, the information regarding "departure date," "train name," "train number," "car number," "block," and "seat location" in records 50g and 50h matches the information regarding "departure date," "train name," "train number," "car number," "block," and "seat location" in record 40d, which indicates that records 50g and 50h are seat-based histories created in correspondence with record 40d. It should be noted that, for a record in the operation history management table 40 in which only one seat is designated, the seat unit history creating means 5 treats the record as it is as seat unit history. Moreover, the procedure for creating a seat unit history by the above-mentioned seat unit history creating means 5 corresponds to the "seat unit history creating procedure."

[0046] The corrected history output means 6 checks the seat-unit history aggregated in the seat-unit history management table 50 for each seat, and determines whether the seat-unit history for each seat corresponds to a specific type. At this time, the corrected history output means 6 identifies the seat of the seat-unit history to be processed based on various information included in the seat-unit history. Specifically, the corrected history output means 6 identifies the seat based on the "Shinkansen operation date (departure date)," "Shinkansen type (train name and train number)," and "Shinkansen seat location (car number, block, and seat location)" included in the seat-unit history. Then, the corrected history output means 6 checks the seat-unit history for each identified seat, and determines whether the seat-unit history of that seat corresponds to a specific type. Here, a specific type is a type that causes the aggregated value when seat-level history is compiled to contradict the sales record of Shinkansen seats. For example, when the seat-level history of a certain seat is compiled and viewed chronologically, a cancellation history exists after the sales history that specifies and cancels part of the travel section of this sales history (a change history that changes part of the travel section in the sales history).

[0047] More specifically, for example, suppose a reservation is made for a certain seat with a boarding section from Tokyo Station to Shin-Osaka Station, and then the boarding section is changed to Shinagawa Station from Nagoya Station. In this case, if the seat-level history for that seat is aggregated and checked, after a sales history with the boarding station name "Tokyo" and the disembarking station name "Shin-Osaka" (sales history with the boarding section specified as Tokyo Station to Shin-Osaka Station), there will be a cancellation history with the boarding station name "Tokyo" and the disembarking station name "Shinagawa" (cancellation history in which the reservation sale is canceled by specifying the section from Tokyo Station to Shinagawa Station), and a cancellation history with the boarding station name "Nagoya" and the disembarking station name "Shin-Osaka" (cancellation history in which the reservation sale is canceled by specifying the section from Nagoya Station to Shin-Osaka Station). Note that the cancellation history specifying the section from Tokyo Station to Shinagawa Station and the cancellation history specifying the section from Nagoya Station to Shin-Osaka Station are treated as change history in which the boarding section in the sales history is changed from Shinagawa Station to Nagoya Station.

[0048] To ascertain the actual sales figures for that seat, if the seat-level history (the one sales history and two cancellation history mentioned above) were simply added and subtracted to tally up, the result would be one sales history for the boarding section from Tokyo Station to Shin-Osaka Station, one cancellation history for the cancellation section from Tokyo Station to Shinagawa Station, and one cancellation history for the cancellation section from Nagoya Station to Shin-Osaka Station. While only one seat sold for the boarding section from Shinagawa Station to Nagoya Station should be counted, a mechanical tally would result in one seat sold for the boarding section from Tokyo Station to Shin-Osaka Station, one seat whose sales were canceled for the section from Tokyo Station to Shinagawa Station, and one seat whose sales were canceled for the section from Nagoya Station to Shin-Osaka Station, resulting in a total that contradicts the actual sales figures. The greater the number of seat-level history entries of a specific type, as described above, the greater the discrepancy between the aggregated value of the seat-level history and the actual sales figures.

[0049] Therefore, the corrected history output means 6 checks the seat unit history for each seat and determines whether the seat unit history of that seat falls into a specific type. If the seat unit history falls into a specific type (a type that causes a discrepancy between the aggregated value of the seat unit history and actual sales performance), it generates correction data for correcting the seat unit history of the specific type and outputs a corrected history in which this correction data is added to the seat unit history. The correction data generated by the corrected history output means 6 is, for example, a sales history for correction to offset unnecessary cancellation history, a cancellation history for correction to offset unnecessary sales history, and a sales history for correction to restore a portion of the sales history to be offset, and is used to make the aggregated value of the seat unit history match the actual sales performance. Note that the sales history for correction to restore a portion of the sales history to be offset is used in cases where the seat unit history falls under a specific type, because the corrected history output means 6 may generate correction data to offset all of the seat unit history for that specific type, and correction data to restore the necessary portion of the sales history to be offset. Specifically, for example, if the seat unit history is of a specific type that is composed of a sales history and a cancellation history that cancels part of the travel section of the sales history after the sales history, the corrected history output means 6 generates a sales history for correction and a cancellation history for correction to offset these sales history and cancellation history, respectively, and also generates correction data to restore the part of the sales history to be offset whose travel section does not overlap with the section specified in the cancellation history. In such cases, a sales history for correction to restore part of the sales history is used. The specific types and the correction patterns by the corrected history output means 6 will be described later. The series of steps from determining whether or not the seat unit history for each seat by the corrected history output means 6 described above corresponds to a specific type, generating correction data for correcting the seat unit history of the specific type, to outputting the corrected history in which the correction data is added to the seat unit history, corresponds to the "corrected history output procedure."

[0050] The recording means 7 acquires the corrected history output from the corrected history output means 6 and records it in a recording device such as an HDD or SSD. The recording device in which the corrected history is recorded may be one provided in the correction processing system 1 or may be an external recording device connected to the correction processing system 1, but since the corrected history output from the corrected history output means 6 is cumulatively recorded, it is preferable that the recording device be one that is capable of recording a relatively large amount of electronic data. The procedure by which the recording means 7 records the corrected history corresponds to the "recording procedure."

[0051] Furthermore, in the correction processing system 1, the corrected history output means 6 has a same seat history addition determination function. The corrected history output means 6 with this same seat history addition determination function searches for corrected history of the same seat as the seat unit history created by the seat unit history creation means 5 from among the corrected histories recorded in the recording device by the recording means 7. If the search results in a corrected history of the same seat as the seat unit history created by the seat unit history creation means 5, the corrected history is included as the same seat history in the seat unit history created by the seat unit history creation means 5, and a determination is made as to whether it corresponds to a specific type. In other words, if there is a same seat history (seat unit history and correction data) for the same seat that has been previously processed by the corrected history output means 6, the corrected history output means 6 with the same seat history addition determination function determines the seat unit history by including the same seat history. Therefore, for example, when the seat unit history of a certain seat created by the seat unit history creation means 5 consists only of sales history, and there is a sales history that specifies the same boarding section as the boarding section specified in the sales history as the same seat history, the corrected history output means 6, which has a same seat history addition determination function, determines whether the sales history created by the seat unit history creation means 5 and the sales history of the same seat history, together with the sales history of the same seat history, correspond to a specific type as the seat unit history to be processed. In the above example, since the seat unit history is composed of the sales history created by the seat unit history creation means 5 and the sales history of the same seat history and corresponds to a specific type, the corrected history output means 6 generates a cancellation history (correction data) for correction to offset the sales history of the same seat history, and outputs the sales history created by the seat unit history creation means 5, the sales history of the same seat history, and the cancellation history for correction to offset the sales history of the same seat history as the corrected history. The above-described determination procedure by the corrected history output means 6 for including the same seat history in the seat unit history corresponds to the "same seat history addition determination procedure."

[0052] In the present embodiment, the correction processing system 1 is configured to include hardware such as a CPU, ROM, RAM, and HDD. However, the correction processing system 1 may also be configured to be implemented as software. When the correction processing system 1 is implemented as software, it may be implemented as a correction processing program stored and executed in the ROM and RAM of a computer equipped with hardware such as a CPU, ROM, RAM, and HDD. The correction processing program may cause the computer to perform the functions of the operation history acquisition means 4, the seat-based history creation means 5, the corrected history output means 6, and the recording means 7, such as an operation history acquisition procedure, a seat-based history creation procedure, a corrected history output procedure, and a recording procedure. Therefore, for example, the correction processing system 1 may be implemented by recording the correction processing program on a recording medium such as a CD-ROM and loading the recording medium into a computer. In this case, the recording medium may be, for example, a CD-ROM, a flexible disk, an optical disk, or any other storage device such as an HDD or SSD.

[0053] Furthermore, the correction processing system 1 can be realized by downloading the correction processing program to a computer via a network N such as the Internet, in addition to reading the correction processing program from a recording medium. Furthermore, the correction processing program may be realized as SaaS (Software as a Service) by an ASP (Application Service Provider) without downloading it to a computer. In this case, the program is provided as a cloud service configured to be accessible via the network N.

[0054] 5 to 7 are explanatory diagrams for explaining the correction patterns by the corrected history output means 6. In each correction pattern in the figure, sales history is indicated by a white square ("□"), and cancellation history is indicated by a white triangle ("△"). Furthermore, for the correction data generated by the corrected history output means 6, sales history for correction (sales history for correction) is indicated by a black square ("■"), and cancellation history for correction (cancellation history for correction) is indicated by a black triangle ("▲"). In the following explanation, sales history for correction will be referred to as "sales history for correction" and cancellation history for correction will be referred to as "cancellation history for correction", as in the notation in the figures. In addition, for each correction pattern in the figure, the "output data" corresponds to the "post-correction history," and the sales history, cancellation history, sales history for correction, and cancellation history for correction are displayed in chronological order with the most recent one at the bottom. Note that the first and second correction patterns shown in Figure 5 are cases where the history does not fall into a specific type, and the third and subsequent correction patterns shown in Figure 5 and the correction patterns shown in Figures 6 and 7 are all cases where the history does fall into a specific type, but these correction patterns are examples, and the cases where the corrected history output means 6 determines that the seat-unit history falls into a specific type will be explained in detail in the explanation of the correction process described below.

[0055] The first correction pattern is when the seat-unit history consists of only one sales history with the boarding station name "A" and the disembarking station name "B" (sales history with the boarding section specified as from Station A to Station B). In this case, there is no other seat-unit history for the same seat other than that sales history, so the aggregated value of the seat-unit history does not contradict the actual sales performance, and the seat-unit history does not fall into a specific type. Therefore, the corrected history output means 6 determines that the seat-unit history does not fall into a specific type, and outputs only that sales history as the corrected history without generating correction data. The second correction pattern is when the seat-unit history consists of only one sales history with the boarding station name "A" and the disembarking station name "B" (sales history with the boarding section specified as from Station A to Station B), and one cancellation history that was operated after the operation of this sales history and specified the same section (from Station A to Station B) as the boarding section of the sales history. In this case, the boarding section of the sales history matches the section specified in the cancellation history, and the sales history and cancellation history cancel each other out, so there is no contradiction between the aggregated value of the seat-unit history and the actual sales performance, and the seat-unit history does not fall into a specific type. Therefore, the corrected history output means 6 determines that the seat-unit history does not fall into a specific type, and outputs the sales history and cancellation history as corrected history without generating correction data.

[0056] On the other hand, the third correction pattern to the twelfth correction pattern are types that cause a discrepancy between the aggregated value of the seat unit history and the actual sales performance, and correspond to specific types. The third correction pattern is a case where the seat unit history is composed of only cancellation history, and corresponds to the first type among the specific types. For example, in the third correction pattern, the seat-unit history consists of only one cancellation history (a cancellation history specifying the section from Station A to Station B) in which the boarding station name is "A" and the disembarking station name is "B." In this case, the corrected history output means 6 determines that the seat-unit history corresponds to a specific type, and based on this determination result, generates a correction sales history (correction data) to offset the cancellation history. Specifically, the corrected history output means 6 generates a correction sales history that specifies the same boarding section as the section specified in the cancellation history. Thereafter, the corrected history output means 6 outputs a corrected history in which the correction sales history is added to the seat-unit history. As a result, when the corrected history is compiled, the unnecessary cancellation history is offset by the correction sales history, so that the compiled value does not contradict the actual sales performance.

[0057] The fourth correction pattern is a case where the seat unit history is composed of only a plurality of sales histories specifying the same travel section, and corresponds to the second type among the specific types. For example, in the fourth correction pattern, the seat-unit history is composed of only two sales histories (sales histories in which the boarding station name is "A" and the disembarking station name is "B") (sales histories in which the boarding section is specified as from Station A to Station B). In this case, the corrected history output means 6 determines that the seat-unit history corresponds to a specific type, and based on this determination result, generates a correction cancellation history (correction data) to offset the sales history other than the sales history with the most recent operation date and time among the multiple sales histories. Specifically, the corrected history output means 6 specifies the same boarding section (from Station A to Station B) as the sales history other than the sales history with the most recent operation date and time (the sales history with the older operation date and time in the fourth correction pattern), and generates a correction cancellation history to offset the sales history with the older operation date and time. Thereafter, the corrected history output means 6 outputs a corrected history in which the correction cancellation history is added to the seat-unit history. As a result, when the corrected history is tallied, the unnecessary sales history is offset by the correction cancellation history, so that the tallied value does not contradict the actual sales performance. The operation date and time of the seat unit history is specified using the "operation date" and "operation time" included in the seat unit history.

[0058] The fifth and sixth correction patterns are cases where the seat-unit history is composed of a sales history and a cancellation history with a newer operation date and time than the sales history, and further where the travel section in the sales history includes a specific section specified in the cancellation history. In other words, the fifth and sixth correction patterns are cases where the travel section in the sales history includes a section specified in the cancellation history, and correspond to the third type of specific types. For example, in the fifth correction pattern, the seat unit history is made up of one sales history in which the boarding station name is "A" and the disembarking station name is "C" (sales history in which the boarding section is specified as from Station A to Station C), and one cancellation history operated after the operation of this sales history in which the boarding station name is "A" and the disembarking station name is "B" (cancellation history in which the section from Station A to Station B is specified). In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and based on this determination result, generates a correction cancellation history (correction data) for offsetting the sales history, a correction sales history (correction data) for offsetting the cancellation history, and a correction sales history (correction data) for restoring the portion of the sales history to be offset whose boarding section does not overlap with the section specified in the cancellation history. Specifically, the corrected history output means 6 generates a corrected cancellation history that specifies the same boarding section (Station A to Station C) as the boarding section in the sales history, a corrected sales history that specifies the same boarding section (Station A to Station B) as the section specified in the cancellation history, and a corrected sales history for restoring part of the sales history, in which the boarding section is the portion of the boarding section in the sales history (Station A to Station C) that does not overlap with the section specified in the cancellation history (Station A to Station B) (Station B to Station C). Thereafter, the corrected history output means 6 outputs the corrected history in which the correction cancellation history and correction sales history are added to the seat unit history. As a result, when the corrected history is tallied, the unnecessary sales history and cancellation history are offset by the correction cancellation history and correction cancellation history, and only the necessary sales history remains, so that the tallied value does not contradict the actual sales performance.

[0059] Also, for example, in the sixth correction pattern, the seat unit history is made up of one sales history in which the boarding station name is "A" and the disembarking station name is "D" (sales history in which the boarding section is specified as Station A to Station D), and one cancellation history operated after the operation of this sales history in which the boarding station name is "B" and the disembarking station name is "C" (cancellation history in which the section from Station B to Station C is specified). In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and based on this determination result, generates a correction cancellation history (correction data) for offsetting the sales history, a correction sales history (correction data) for offsetting the cancellation history, and a correction sales history (correction data) for restoring the portion of the sales history in which the boarding section does not overlap with the section specified in the cancellation history. Specifically, the corrected history output means 6 generates a corrected cancellation history that specifies the same boarding section (Station A to Station D) as the boarding section in the sales history, a corrected sales history that specifies the same boarding section (Station B to Station C) as the section specified in the cancellation history, and a corrected sales history for restoring part of the sales history, specifying as the boarding section the portion of the boarding section (Station A to Station D) in the sales history that does not overlap with the section specified in the cancellation history (Station B to Station C) (Station A to Station B and Station C to Station D). Thereafter, the corrected history output means 6 outputs the corrected history in which the correction cancellation history and correction sales history are added to the seat unit history. As a result, when the corrected history is tallied, the unnecessary sales history and cancellation history are offset by the correction cancellation history and correction cancellation history, and only the necessary sales history remains, so that the tallied value does not contradict the actual sales performance.

[0060] The seventh correction pattern is when the seat-unit history is composed of a sales history and a cancellation history with a newer operation date and time than the sales history, and further, part of the travel section in the sales history overlaps with part of the specified section specified in the cancellation history, and this corresponds to the fourth type of specific types. For example, in the seventh correction pattern, the seat unit history is made up of one sales history in which the boarding station name is "B" and the disembarking station name is "D" (sales history in which the boarding section is specified as from Station B to Station D), and one cancellation history operated after the operation of this sales history in which the boarding station name is "A" and the disembarking station name is "C" (cancellation history in which the section from Station A to Station C is specified). In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and based on this determination result, generates a correction cancellation history (correction data) for offsetting the sales history, a correction sales history (correction data) for offsetting the cancellation history, and a correction sales history (correction data) for restoring the portion of the sales history that does not overlap with the section specified in the cancellation history. Specifically, the corrected history output means 6 generates a corrected cancellation history that specifies the same boarding section (Station B to Station D) as the boarding section in the sales history, a corrected sales history that specifies the same boarding section (Station A to Station C) as the section specified in the cancellation history, and a corrected sales history for restoring part of the sales history, specifying as the boarding section the portion of the boarding section in the sales history (Station B to Station D) that does not overlap with the section specified in the cancellation history (Station A to Station C) (Station C to Station D). Thereafter, the corrected history output means 6 outputs the corrected history in which the correction cancellation history and correction sales history are added to the seat unit history. As a result, when the corrected history is tallied, the unnecessary sales history and cancellation history are offset by the correction cancellation history and correction cancellation history, and only the necessary sales history remains, so that the tallied value does not contradict the actual sales performance.

[0061] The eighth correction pattern is a case where the seat unit history is composed of a sales history and a cancellation history with a newer operation date and time than the sales history, and further, the travel section in the sales history is included in the specified section specified in the cancellation history. In other words, the eighth correction pattern is a case where the travel section in the sales history is included in the section specified in the cancellation history, and corresponds to the fifth type of specific types. For example, in the eighth correction pattern, the seat unit history is composed of one sales history in which the boarding station name is "B" and the disembarking station name is "C" (sales history in which the boarding section is specified as from Station B to Station C), and one cancellation history operated after the operation of this sales history in which the boarding station name is "A" and the disembarking station name is "D" (cancellation history in which the section from Station A to Station D is specified). In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and based on this determination result, generates a correction cancellation history (correction data) for offsetting the sales history and a correction sales history (correction data) for offsetting the cancellation history. Specifically, the corrected history output means 6 generates a correction cancellation history that specifies the same section (from Station B to Station C) as the boarding section of the sales history, and a correction sales history that specifies the same boarding section (from Station A to Station D) as the section specified in the cancellation history. Thereafter, the corrected history output means 6 outputs the corrected history by adding the correction cancellation history and correction sales history to the seat unit history. As a result, when the corrected history is tallied, the unnecessary sales history and cancellation history are offset by the correction cancellation history and correction cancellation history, so that the tallied value does not contradict the actual sales performance.

[0062] The ninth correction pattern is when the seat-unit history is composed of a sales history and a cancellation history with a newer operation date and time than the sales history, and further, the travel section in the sales history does not overlap with the specified section specified in the cancellation history, which corresponds to the sixth type of specific types. For example, in the ninth correction pattern, the seat unit history is composed of one sales history in which the boarding station name is "C" and the disembarking station name is "D" (sales history in which the boarding section is specified as from Station C to Station D), and one cancellation history operated after the operation of this sales history in which the boarding station name is "A" and the disembarking station name is "B" (cancellation history in which the section from Station A to Station D is specified). In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and based on this determination result, generates a corrective sales history (correction data) to offset the cancellation history. At this time, the corrected history output means 6 generates a corrective sales history that specifies the same boarding section (from Station A to Station B) as the section specified in the cancellation history. After that, the corrected history output means 6 outputs the corrected history by adding the sales history for correction to the seat-unit history. As a result, when the corrected history is tallied, the unnecessary cancellation history is offset by the sales history for correction, so that the total value does not contradict the actual sales performance.

[0063] The tenth and eleventh correction patterns are cases where the seat unit history is composed of multiple sales histories and one cancellation history with a newer operation date and time than these sales histories, and further, a section that includes all of the travel sections in each of the multiple sales histories is specified as a predetermined section in the cancellation history. In other words, this is a case where all of the travel sections in each of the multiple sales histories are included in the section specified in the cancellation history, and this corresponds to the seventh type of specific types. For example, in the tenth correction pattern, the seat unit history, in order from oldest to newest operation date and time, includes a sales history with the boarding station name "A" and the disembarking station name "B" (sales history with the boarding section specified as from Station A to Station B), a sales history with the boarding station name "B" and the disembarking station name "C" (sales history with the boarding section specified as from Station B to Station C), and a sales history with the boarding station name "C" and the disembarking station name "D" (sales history with the boarding section specified as from Station C to Station D), followed by a cancellation history with the boarding station name "A" and the disembarking station name "D" (cancellation history with the section specified as from Station A to Station D). In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and based on this determination result, generates a correction cancellation history (correction data) for offsetting each sales history corresponding to each sales history, and a correction sales history (correction data) for offsetting the cancellation history. Specifically, the corrected history output means 6 generates, corresponding to each travel section of each sales history, a correction cancellation history specifying station A to station B, a correction cancellation history specifying station B to station C, a correction cancellation history specifying station C to station D, and a correction sales history specifying the same travel section (station A to station D) as the section specified in the cancellation history. Thereafter, the corrected history output means 6 outputs the corrected history by adding the correction cancellation history and correction sales history to the seat unit history. As a result, when the corrected history is tallied, the unnecessary sales history and cancellation history are offset by the correction cancellation history and correction sales history, so that the tallied value does not contradict the actual sales performance.

[0064] Also, for example, in the eleventh correction pattern, the seat unit history includes, in order from oldest to newest operation date and time, a sales history with the boarding station name "A" and the disembarking station name "B" (sales history with the boarding section specified as from Station A to Station B), a sales history with the boarding station name "C" and the disembarking station name "D" (sales history with the boarding section specified as from Station C to Station D), and then a cancellation history with the boarding station name "A" and the disembarking station name "D" (cancellation history with the section specified as from Station A to Station D). In this case as well, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and based on this determination result, generates, for each sales history, a correction cancellation history (correction data) for offsetting the respective sales history, and a correction sales history (correction data) for offsetting the cancellation history. Specifically, the corrected history output means 6 generates, corresponding to each travel section of each sales history, a corrected cancellation history specifying station A to station B, a corrected cancellation history specifying station C to station D, and a corrected sales history specifying the same travel section (station A to station D) as the section specified in the cancellation history. Thereafter, the corrected history output means 6 outputs the corrected history by adding the correction cancellation history and correction sales history to the seat unit history. As a result, when the corrected history is tallied, the unnecessary sales history and cancellation history are offset by the correction cancellation history and correction sales history, so that the tallied value does not contradict the actual sales performance.

[0065] The 12th correction pattern is a case where the seat-unit history is composed of multiple sales histories and one cancellation history with a newer operation date and time than these sales histories, at least one of the travel sections in each sales history is included in the specified section specified in the cancellation history, and at least one of the travel sections in each sales history overlaps with part of the specified section specified in the cancellation history, and this corresponds to the 8th type of specific types. For example, in the 12th correction pattern, in order from oldest to newest operation date and time, there is a sales history with the boarding station name "A" and the disembarking station name "C" (sales history where the boarding section is specified as from Station A to Station C via Station B), a sales history with the boarding station name "C" and the disembarking station name "D" (sales history where the boarding section is specified as from Station C to Station D), a sales history with the boarding station name "D" and the disembarking station name "F" (sales history where the boarding section is specified as from Station D to Station F via Station E), and then a cancellation history with the boarding station name "B" and the disembarking station name "E" (cancellation history where the section from Station B to Station E is specified). In this case, part of the riding section in the sales history from Station A to Station C via Station B (Station B to Station C) overlaps with part of the section specified in the cancellation history (Station B to Station E), and part of the riding section in the sales history from Station D to Station F via Station E (Station D to Station E) overlaps with part of the section specified in the cancellation history (Station B to Station E). Furthermore, in the sales history with Station C to Station D as the riding section, all of its riding sections are included in the section specified in the cancellation history (Station B to Station E). In this case, the corrected history output means 6 determines that the seat-unit history corresponds to a specific type, and based on this determination result, generates, for each sales history, a correction cancellation history (correction data) for offsetting each sales history, a correction sales history (correction data) for offsetting the cancellation history, and a correction sales history (correction data) for restoring the part of each sales history whose riding section does not overlap with the section specified in the cancellation history. Specifically, the corrected history output means 6 generates, corresponding to each travel section of each sales history, a corrected cancellation history specifying Station A to Station C, a corrected cancellation history specifying Station C to Station D, a corrected cancellation history specifying Station D to Station F, a corrected sales history specifying the same travel section (Station B to Station E) as the section specified in the cancellation history, and a corrected sales history for restoring part of the sales history, specifying Station A to Station B and Station E to Station F as the travel sections, which are the parts of all travel sections (Station A to Station F) in the multiple sales histories that do not overlap with the section specified in the cancellation history (Station B to Station E).

[0066] The above describes the correction pattern when the seat unit history is composed of sales history indicating that a Shinkansen seat has been sold and cancellation history indicating that the sale of a Shinkansen seat has been canceled. In addition to regular reservations, which are recorded as sales history, there is also a type of reservation sales for Shinkansen seats called "seat number input sales," which allows for additional reservations for seats that have already been reserved and sold. This "seat number input sales" is primarily used on the reservation terminals 20 installed at railway companies when a reservation sale is made for a specific seat and then the details of the reservation sale are changed while the seat remains reserved. Specifically, "seat number input sales" is used, for example, when a specific seat that has already been reserved and sold is shortened while the seat remains reserved, or when a specific seat is first designated (seat reservation) at the user's request, and then a new reservation sale is made later while the seat remains reserved when the user purchases a ticket at a station ticket counter, etc. Therefore, in addition to sales history and cancellation history, it is expected that the operation history and seat-by-seat history will also include seat number input sales history indicating that a seat number input sale was made.

[0067] Therefore, the following describes the correction patterns by the corrected history output means 6 when the seat unit history includes a seat number input sales history. Note that the correction patterns shown below are also examples, and each seat unit history corresponds to a specific type. Also, illustrations of the correction patterns are omitted. Furthermore, the seat number input sales history contains the same information as the sales history and cancellation history, except that the "operation content" indicating the type of operation history is displayed as "seat entry" in the operation history management table 40 and the seat unit history management table 50. Therefore, just like the sales history and cancellation history, it is possible to identify the boarding section specified in the seat number input sales history from the boarding and alighting station names, and it is also possible to create a seat unit history corresponding to the seat number input sales history from the operation history that includes the seat number input sales history.

[0068] For example, the thirteenth correction pattern is when the seat unit history is composed of multiple seat number input sales histories that specify the same travel section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type and generates a correction cancellation history (correction data) to offset the seat number input sales history other than the latest seat number input sales history. Note that the correction cancellation history in this case is the same as the correction cancellation history for offsetting sales history, and is configured so that unnecessary seat number input sales history can be offset using this correction cancellation history. The fourteenth correction pattern is when the seat unit history is composed of a sales history and, after this sales history, a seat number input sales history that specifies the same boarding section as the sales history. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type and generates a correction cancellation history (correction data) to offset the sales history. Furthermore, the fifteenth correction pattern is when the seat unit history is composed of a seat number input sales history and a sales history that specifies the same boarding section as the seat number input sales history after the seat number input sales history. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type and generates a correction cancellation history (correction data) to offset the seat number input sales history.

[0069] Furthermore, for example, the 16th correction pattern is a case where the seat unit history is composed of a seat number input sales history and, after this seat number input sales history, a cancellation history in which a section included in the boarding section of the seat number input sales history is designated as a predetermined section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, generates a correction cancellation history (correction data) for offsetting the seat number input sales history, and a correction sales history (correction data) for offsetting the cancellation history, and further generates a correction seat number input sales history (correction data) for restoring the portion of the seat number input sales history whose boarding section does not overlap with the section designated in the cancellation history. The seat number input sales history for correction is a seat number input sales history (correction data) for correction used to restore a part of the seat number input sales history that is offset. Furthermore, the seventeenth correction pattern is when the seat unit history is composed of a sales history and, after this sales history, a seat number input sales history that specifies a section included in the travel section of the sales history as the travel section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, generates a correction cancellation history (correction data) to offset the sales history, and further generates a correction sales history (correction data) to restore the part of the sales history whose travel section does not overlap with the travel section of the seat number input sales history. The 18th correction pattern is a case where the seat unit history is composed of a seat number input sales history and, after this seat number input sales history, a seat number input sales history that specifies a section included in the boarding section of the seat number input sales history as the boarding section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, generates a correction cancellation history (correction data) to offset the seat number input sales history other than the latest seat number input sales history, and further generates a correction seat number input sales history (correction data) to restore the portion of the offset seat number input sales history whose boarding section does not overlap with the boarding section of the latest seat number input sales history.

[0070] Furthermore, for example, a 19th correction pattern is a case where the seat unit history is composed of a seat number input sales history and, after this seat number input sales history, a cancellation history that specifies a section that overlaps with part of the boarding section of the seat number input sales history as part of the specified section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, generates a correction cancellation history (correction data) for offsetting the seat number input sales history, and a correction sales history (correction data) for offsetting the cancellation history, and further generates a correction seat number input sales history (correction data) for restoring the part of the seat number input sales history whose boarding section does not overlap with the section specified in the cancellation history. The 20th correction pattern is a case where the seat unit history is composed of a seat number input sales history and a cancellation history that specifies a section that includes the boarding section of the seat number input sales history as a specified section after the seat number input sales history. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and generates a correction cancellation history (correction data) for offsetting the seat number input sales history, and a correction sales history (correction data) for offsetting the cancellation history. Furthermore, the 21st correction pattern is when the seat unit history is composed of a sales history and, after this sales history, a seat number input sales history that specifies a section that overlaps with part of the travel section of the sales history as part of the travel section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, generates a correction cancellation history (correction data) to offset the sales history, and further generates a correction sales history (correction data) to restore the part of the sales history whose travel section does not overlap with the travel section of the seat number input sales history.

[0071] Furthermore, for example, the 22nd correction pattern is a case where the seat unit history is composed of a sales history and, after this sales history, a seat number input sales history that specifies a section that includes the boarding section of the sales history as the boarding section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type and generates a correction cancellation history (correction data) to offset the sales history. Furthermore, the 23rd correction pattern is when the seat unit history is composed of a seat number input sales history and a seat number input sales history that follows this seat number input sales history and specifies a section that overlaps with part of the travel section of the seat number input sales history as part of the travel section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, generates a correction cancellation history (correction data) to offset the seat number input sales history other than the latest seat number input sales history, and further generates a correction seat number input sales history (correction data) to restore the part of the seat number input sales history to be offset, whose travel section does not overlap with the travel section of the latest seat number input sales history. The 24th correction pattern is when the seat unit history is composed of a seat number input sales history and a seat number input sales history that specifies a section that includes the seat number input sales history as the boarding section after the seat number input sales history. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type and generates a correction cancellation history (correction data) to offset all but the most recent seat number input sales history.

[0072] Furthermore, for example, the 25th correction pattern is a case where the seat unit history is composed of multiple sales histories and, after these sales histories, a seat number input sales history that specifies a section that includes all of the travel sections of each sales history as the travel section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and generates multiple correction cancellation histories (correction data) corresponding to each sales history to offset each sales history. The 26th correction pattern is a case where the seat unit history is composed of a plurality of seat number input sales histories and, after these seat number input sales histories, a cancellation history in which a section including all of the boarding sections of each seat number input sales history is designated as a predetermined section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and generates a plurality of correction cancellation histories (correction data) for offsetting each seat number input sales history and a correction sales history (correction data) for offsetting the cancellation history, corresponding to each seat number input sales history. Furthermore, the 27th correction pattern is when the seat unit history is composed of multiple seat number input sales histories and, after these seat number input sales histories, a seat number input sales history that specifies a section that includes all of the boarding sections of each seat number input sales history as the boarding section. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, and generates multiple correction cancellation histories (correction data) for offsetting each seat number input sales history in response to each seat number input sales history other than the latest seat number input sales history.

[0073] Furthermore, for example, the 28th correction pattern is a case where the seat unit history is composed of multiple sales histories with consecutive travel sections and seat number input sales histories that follow these sales histories, where at least one of the travel sections in each sales history is included in the travel section of the seat number input sales history, and where a portion of the travel section in each sales history other than the travel section included in the seat number input sales history overlaps with a portion of the travel section in the seat number input sales history. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, generates multiple correction cancellation histories (correction data) corresponding to each sales history with consecutive travel sections to offset each sales history, and further generates correction sales histories (correction data) to restore the portion of the sales history to be offset whose travel section does not overlap with the travel section in the seat number input sales history. Furthermore, the 29th correction pattern is a case where the seat unit history is composed of multiple seat number input sales histories with consecutive travel sections and cancellation histories following these seat number input sales histories, where at least one of the travel sections in each sales history is included in the section specified in the cancellation history, and where a portion of the travel section in each sales history other than the travel section included in the section specified in the cancellation history overlaps with a portion of the section specified in the cancellation history. In this case, the corrected history output means 6 determines that the seat unit history corresponds to a specific type, generates multiple correction cancellation histories (correction data) corresponding to each seat number input sales history to offset each seat number input sales history, generates correction sales histories (correction data) to offset the cancellation histories, and further generates correction seat number input sales histories (correction data) to restore the portion of the seat number input sales history to be offset whose travel section does not overlap with the section specified in the cancellation history. Furthermore, the 30th correction pattern is a case where the seat unit history is composed of multiple seat number input sales histories with consecutive travel sections and the latest seat number input sales history after these seat number input sales histories, and at least one of the travel sections in each of the consecutive seat number input sales histories is included in the travel section of the latest seat number input sales history, and part of each of the travel sections in each of the consecutive seat number input sales histories overlaps with a section other than the section included in the latest seat number input sales history. In this case, multiple correction cancellation histories (correction data) are generated corresponding to each of the consecutive seat number input sales histories to offset each seat number input sales history, and correction seat number input sales histories (correction data) are also generated to restore the portion of the offsetting seat number input sales history whose travel section does not overlap with the travel section of the latest seat number input sales history.

[0074] Next, the processing in the correction processing system 1 will be described with reference to FIGS. FIG. 8 is a flowchart for explaining an outline of the processing from the acquisition of an operation history by the operation history acquisition means 4 to the creation of a seat-unit history by the seat-unit history creation means 5. In FIG. First, the operation history acquisition means 4 acquires the operation history from the reservation management system 10 (S001). Next, the seat unit history creation means 5 creates a seat unit history from the operation history acquired by the operation history acquisition means 4 (S002). At this time, the seat unit history creation means 5 checks the operation history for each record, and if there is a record that targets multiple seats, it divides the record into seat units based on the information stored in the "seat position" column of that record. Thereafter, the seat unit history created by the seat unit history creation means 5 is output (S003).

[0075] FIG. 9 is a flowchart for explaining an outline of the process from searching for the same seat history to outputting the corrected history. First, the seat-unit history created by the seat-unit history creation means 5 is input as a file to the corrected history output means 6 (S101). Next, the corrected history output means 6 stores the seat-unit history of the first record to be processed in a work area to check the seat-unit history for each record (S102). Next, the seat of the seat-unit history record stored in the work area is identified based on the seat identification information (in the correction processing system 1, this is the Shinkansen "departure date," "type," and "seat location" of the Shinkansen). Based on the identified seat, a search is performed (S103) for the same seat history, which is the corrected history of the same seat as the identified seat, from the corrected histories recorded by the recording means 7. Thereafter, if the search results in the existence of the same seat history (S104), the corrected history output means 6 stores the record of the same seat history in the work area (S105). Then, the work area stores the record of the seat unit history to be processed and the record of the same seat history corresponding to the seat of this record. Next, the corrected history output means 6 determines whether the seat unit history (including the same seat history) stored in the work area corresponds to a specific type or not and performs a process (correction process) to generate corrected data (S106). The correction process by the corrected history output means 6 will be described in detail later. When the correction process by the corrected history output means 6 is completed, the next seat unit history record to be processed is stored in the work area (S107). Next, it is determined whether the newly stored seat unit history record is for the same seat as the seat unit history record previously stored in the work area (S108). If the determination result is that the seat unit history is for the same seat, correction processing is performed on the seat unit history (including the same seat history) including the newly stored record in the work area (S106). Thereafter, the processing from step S106 to step S108 is repeated until a seat unit history record for a different seat is stored in the work area. When a seat unit history record for a different seat is stored in the work area, the corrected seat unit history (including the same seat history) processed up to that point is output as the corrected history together with the correction data (S109). Furthermore, although not shown in the figure, the output corrected history is then recorded on a recording medium by the recording means 7.

[0076] On the other hand, if the search result indicates that there is no identical seat history (S104), the seat unit history record to be processed next is stored in the work area (S107). The work area then stores the newly stored seat unit history record and the seat unit history record previously stored in the work area. Next, it is determined whether the newly stored seat unit history record is for the same seat as the seat unit history record previously stored in the work area (S108). If the determination result indicates that the seat is for the same seat, correction processing is performed on the seat unit history including the newly stored record in the work area (S106). The processing from step S106 to step S108 is then repeated until a seat unit history record for a different seat is stored in the work area. When a seat unit history record for a different seat is stored in the work area, the seat unit history (including the identical seat history) that has been corrected up to that point is output as corrected history together with the correction data (S109).

[0077] On the other hand, it is determined whether the newly stored seat unit history record in the work area is for the same seat as the seat unit history record previously stored in the work area (S108), and if the determination result is that it is not for the same seat, in other words, if a seat unit history record for a different seat has been stored in the work area, the processes from step S102 to step S109 are performed for the newly stored seat unit history record for a different seat in the work area. Thereafter, the above-described processing (S102 to S109) is executed until all records of the seat unit history to be processed are completed.

[0078] 10 to 13 are flowcharts for explaining the correction process in the corrected history output means 6. In the following, an example of the correction process will be described assuming that the seat unit history (input record) to be processed and stored in the work area is a sales history or a cancellation history, and the correction process will be described later assuming that the seat unit history (input record) includes a seat number input sales history. First, the corrected history output means 6 searches for identical seat history in the corrected history (hereinafter, the "corrected history" is also referred to as "accumulated data") based on the seat of the seat unit history (input record) to be processed stored in the work area (S201). From the search results, it is determined whether or not there is a record corresponding to the identical seat history in the cumulative data (S202). If there is no record corresponding to the identical seat history, it is determined whether the operation content of the seat unit history (input record) to be processed is a cancellation of a pre-order sale, in other words, whether or not the seat unit history is a cancellation history (S204). Then, if the seat unit history (input record) is a cancellation history, the corrected history output means 6 determines that the seat unit history corresponds to a specific type. Then, a corrective sales history (correction record), which is correction data for offsetting the cancellation history (input record), is generated (S205), and this correction record and the cancellation history (input record) are stored in the work area (S206). Thereafter, the correction process ends (FIG. 13). In this case, the correction pattern is, for example, the third correction pattern. On the other hand, if the operation content of the seat unit history is not a cancellation of a pre-order sale, in other words, if the seat unit history is a sales history, the corrected history output means 6 determines that the seat unit history does not correspond to a specific type. Therefore, no correction data is generated, and the sales history (input record) remains stored in the work area (S206), and then the correction process ends (FIG. 13). Note that the correction pattern in this case is, for example, the first correction pattern.

[0079] On the other hand, in the search results for the same seat history, it is determined whether there is a record corresponding to the same seat history in the cumulative data (S202), and if there is a record corresponding to the same seat history, the latest record of the same seat history is set as the record to be compared (S203). Next, for the seat unit history (input record) to be processed, it is determined whether the operation content is a pre-sale, in other words, whether the seat unit history is a sales history (S207). If the seat unit history is a sales history, it is determined whether the travel section of this sales history is the same as the travel section of the comparison record of the same seat history corresponding to the sales history (S208). If the travel section of the sales history is the same as the travel section of the comparison record, the corrected history output means 6 determines that the seat unit history corresponds to a specific type. Then, a correction cancellation history (correction record) is generated as correction data to offset the comparison record (S209), and this correction record and the sales history (input record) are stored in the work area (S210). Thereafter, the correction process ends (FIG. 13). The correction pattern in this case is, for example, the fourth correction pattern or the fifteenth correction pattern.

[0080] In determining whether the travel sections are the same (S208), if the travel section of the sales history (input record) and the travel section of the comparison record are not the same, it is determined whether the travel section of the sales history contains the travel section of the comparison record (S211). If the travel section of the sales history contains the travel section of the comparison record, the corrected history output means 6 determines that the seat unit history corresponds to a specific type. Then, a correction cancellation history (correction record) is generated, which is correction data for offsetting the comparison record (S212). Furthermore, it is confirmed whether there is a travel section that overlaps with the travel section of the sales history in other records other than the comparison record in the same seat history corresponding to the sales history (S213). Here, it is determined whether or not there is a portion of the travel section of another record of the same seat history that overlaps with the travel section of the sales history (S214). If there is another record whose travel section overlaps with the travel section of the sales history, a correction cancellation history (correction record) is generated as correction data to offset the other record (S215). Furthermore, if there is a portion of the travel section of the other record that does not overlap with the travel section of the sales history, a correction sales history (correction record) is generated as correction data to restore the portion of the other record whose travel section does not overlap with the travel section of the sales history (S216). Then, these correction records and the sales history (input record) are stored in the work area (S217). Thereafter, the correction process ends (Figure 13). On the other hand, in the determination of whether or not there is an overlap between the boarding section of another record of the same seat history and the boarding section of the sales history (S214), if there is no other record whose boarding section overlaps with the boarding section of the sales history, the correction record generated in step S212 and the sales history (input record) are stored in the work area (S217). Then, the correction process ends (Figure 13).

[0081] In determining whether the travel section of the sales history contains the travel section of the comparison record (S211), if the travel section of the sales history does not contain the travel section of the comparison record, it is determined whether the travel section of the sales history is contained in the travel section of the comparison record (S218). If the travel section of the sales history is contained in the travel section of the comparison record, the corrected history output means 6 determines that the seat unit history corresponds to a specific type. Then, a correction cancellation history (correction record) is generated as correction data for offsetting the comparison record (S219), and a correction sales history (correction record) is generated as correction data for restoring the portion of the comparison record whose travel section does not overlap with the travel section of the sales history (S220). Then, these correction records and the sales history (input record) are stored in the work area (S221). The correction process then ends (Figure 13).

[0082] If the travel section of the sales history does not include the travel section of the comparison record, or if the travel section of the sales history is not included in the travel section of the comparison record, it is determined whether or not a portion of the travel section of the sales history overlaps with a portion of the travel section of the comparison record (S222). If a portion of the travel section of the sales history overlaps with a portion of the travel section of the comparison record, the corrected history output means 6 determines that the seat unit history corresponds to a specific type. Then, a correction cancellation history (correction record) is generated as correction data for offsetting the comparison record (S223). In addition, a correction sales history (correction record) is generated as correction data for restoring the portion of the comparison record whose travel section does not overlap with the travel section of the sales history (S224). Furthermore, it is confirmed whether or not there is a travel section that overlaps with the travel section of the sales history in other records other than the comparison record in the same seat history corresponding to the sales history (S225). Here, it is determined whether or not there is a portion of the travel section of another record of the same seat history that overlaps with the travel section of the sales history (S226). If there is another record whose travel section overlaps with the travel section of the sales history, a correction cancellation history (correction record) is generated as correction data to offset the other record (S227). Furthermore, if there is a portion of the travel section of the other record that does not overlap with the travel section of the sales history, a correction sales history (correction record) is generated as correction data to restore the portion of the other record whose travel section does not overlap with the travel section of the sales history (S228). Then, these correction records and the sales history (input record) are stored in the work area (S229). Thereafter, the correction process ends (Figure 13). On the other hand, in determining whether the travel section of another record in the same seat history overlaps with the travel section of the sales history (S226), if there is no other record whose travel section overlaps with the travel section of the sales history, the correction record generated in steps S223 and S224 and the sales history (input record) are stored in the work area (S229), and then the correction process ends (Figure 13).

[0083] Next, in determining whether a portion of the travel section in the sales history overlaps with a portion of the travel section in the comparison record (S222), if the travel section in the sales history does not overlap with a portion of the travel section in the comparison record, it is confirmed whether there is a travel section in other records other than the comparison record in the same seat history corresponding to the sales history that overlaps with the travel section in the sales history (S230). Here, it is determined whether there is a portion of the travel section in the other records in the same seat history that overlaps with the travel section in the sales history (S231), and if there is another record whose travel section overlaps with the travel section in the sales history, the corrected history output means 6 determines that the seat-unit history corresponds to a specific type. Then, a correction cancellation history (correction record), which is correction data for offsetting the other records, is generated (S232). If the travel section of the other record does not overlap with the travel section of the sales history, a sales history for correction (correction record) is generated (S233), which is correction data for restoring the travel section of the other record that does not overlap with the travel section of the sales history. Then, these correction records and the sales history (input record) are stored in the work area (S234). Then, the correction process ends (Figure 13). On the other hand, in determining whether or not there is an overlapping portion of the travel section of another record of the same seat history with the travel section of the sales history (S231), if there is no other record whose travel section overlaps with the travel section of the sales history, the corrected history output means 6 determines that the seat unit history does not correspond to a specific type. Then, the sales history (input record) is stored in the work area (S234), and then the correction process ends (Fig. 13).

[0084] In determining (S207) whether the operation content of the seat unit history (input record) to be processed is a pre-sale (whether the seat unit history is a sales history), if the seat unit history is not a sales history, it is determined whether the operation content of the seat unit history is a cancellation of a pre-sale, in other words, whether the seat unit history is a cancellation history (S235). Here, if the seat unit history is not a cancellation history, an alarm is output (S236), and then the correction process ends (Fig. 13). In determining whether the seat unit history is a cancellation history (S235), if the seat unit history is a cancellation history, it is determined whether the section specified in this cancellation history is the same as the travel section of the comparison record of the same seat history corresponding to the cancellation history (S237). Here, if the section specified in the cancellation history is the same as the travel section of the comparison record, the corrected history output means 6 determines that the seat unit history corresponds to a specific type. Then, a correction cancellation history (correction record) is generated as correction data for offsetting the comparison record (S238). Furthermore, a correction sales history (correction record) is generated as correction data for offsetting the cancellation history (input record) (S239). Then, these correction records and the correction sales history (input record) are stored in the work area (S240). Thereafter, the correction process ends (FIG. 13). In the above case, if the record to be compared is a sales history, the sales history will be offset by the cancellation history, so the correction process may be terminated without generating correction data. In such a configuration, the corrected history output means 6 determines that the seat unit history does not correspond to a specific type, and the second correction pattern is selected.

[0085] On the other hand, in determining whether the section specified in the cancellation history is the same as the travel section of the comparison record (S237), if the section specified in the cancellation history is not the same as the travel section of the comparison record, it is determined whether the section specified in the cancellation history contains the travel section of the comparison record (S241). Here, if the section specified in the cancellation history contains the travel section of the comparison record, the corrected history output means 6 determines that the seat-unit history corresponds to a specific type. Then, a correction cancellation history (correction record) is generated, which is correction data for offsetting the comparison record (S242). Furthermore, it is confirmed whether there is a travel section that overlaps with the section specified in the cancellation history in other records other than the comparison record in the same seat history corresponding to the cancellation history (S243). Here, it is determined whether the travel section of another record of the same seat history overlaps with the section specified in the cancellation history (S244). If there is another record whose travel section overlaps with the section specified in the cancellation history, a correction cancellation history (correction record) is generated as correction data to offset the other record (S245). If there is a travel section of the other record that does not overlap with the section specified in the cancellation history, a correction sales history (correction record) is generated as correction data to restore the portion of the other record whose travel section does not overlap with the section specified in the cancellation history (S246). Furthermore, a correction sales history (correction record) is generated as correction data to offset the cancellation history (S247). Then, these correction records and the cancellation history (input record) are stored in the work area (S248), and the correction process is then completed (FIG. 13). The correction pattern in this case is, for example, the 10th correction pattern, the 11th correction pattern, or the 26th correction pattern. On the other hand, in determining whether or not the travel section of another record of the same seat history overlaps with the section specified in the cancellation history (S244), if there is no other record whose travel section overlaps with the section specified in the cancellation history, a sales history for correction (correction record) is generated as correction data for offsetting the cancellation history (S247). Then, the correction record generated in steps S242 and S247 and the cancellation history (input record) are stored in the work area (S248), and the correction process then ends (Figure 13). The correction pattern in this case is, for example, the 8th correction pattern or the 20th correction pattern.

[0086] In determining whether the section specified in the cancellation history contains the travel section of the comparison record (S241), if the section specified in the cancellation history does not contain the travel section of the comparison record, it is determined whether the section specified in the cancellation history is contained in the travel section of the comparison record (S249). Here, if the section specified in the cancellation history is contained in the travel section of the comparison record, the corrected history output means 6 determines that the seat unit history corresponds to a specific type. Then, a correction cancellation history (correction record) is generated as correction data for offsetting the comparison record (S250). In addition, a correction sales history (correction record) is generated as correction data for restoring the portion of the comparison record whose travel section does not overlap with the section specified in the cancellation history (S251). In addition, a correction sales history (correction record) is generated as correction data for offsetting the cancellation history (S252). Then, these correction records and the cancellation history (input record) are stored in the work area (S253), and then the correction process ends (FIG. 13). Note that the correction pattern in this case is, for example, the fifth correction pattern, the sixth correction pattern, or the sixteenth correction pattern.

[0087] If the section specified in the cancellation history does not include the travel section of the comparison record, or if the section specified in the cancellation history is not included in the travel section of the comparison record, it is determined whether or not a portion of the section specified in the cancellation history overlaps with a portion of the travel section of the comparison record (S254). If a portion of the section specified in the cancellation history overlaps with a portion of the travel section of the comparison record, the corrected history output means 6 determines that the seat-unit history corresponds to a specific type. Then, a correction cancellation history (correction record) is generated as correction data for offsetting the comparison record (S255). In addition, a correction sales history (correction record) is generated as correction data for restoring the portion of the comparison record whose travel section does not overlap with the section specified in the cancellation history (S256). Furthermore, it is confirmed whether or not there is a travel section that overlaps with the section specified in the cancellation history in records other than the comparison record in the same seat history corresponding to the cancellation history (S257). Here, it is determined whether the travel section of another record of the same seat history overlaps with the section specified in the cancellation history (S258). If there is another record whose travel section overlaps with the section specified in the cancellation history, a correction cancellation history (correction record) is generated as correction data to offset the other record (S259). If there is a travel section of the other record that does not overlap with the section specified in the cancellation history, a correction sales history (correction record) is generated as correction data to restore the portion of the other record whose travel section does not overlap with the section specified in the cancellation history (S260). Furthermore, a correction sales history is generated as a correction record (correction data) to offset the cancellation history (S261). Then, these correction records and the cancellation history (input record) are stored in the work area (S262), and the correction process is then completed (FIG. 13). The correction pattern in this case is, for example, the 12th correction pattern or the 29th correction pattern. On the other hand, in the determination of whether or not there is a portion of the boarding section of another record of the same seat history that overlaps with the section specified in the cancellation history (S258), if there is no other record whose boarding section overlaps with the section specified in the cancellation history, a correction sales history (correction record) is generated as correction data to offset the cancellation history (S261). Then, the correction record generated in steps S255, S256, and S261 and the cancellation history (input record) are stored in the work area (S262), and the correction process then ends (Figure 13). The correction pattern in this case is, for example, the 7th correction pattern or the 19th correction pattern.

[0088] In determining whether the section specified in the cancellation history overlaps with part of the travel section of the comparison record (S254), if the section specified in the cancellation history does not overlap with part of the travel section of the comparison record, it is checked whether other records other than the comparison record in the same seat history corresponding to the cancellation history have travel sections that overlap with the section specified in the cancellation history (S263). Here, it is determined whether the travel sections of other records in the same seat history overlap with the section specified in the cancellation history (S264), and if there is another record whose travel section overlaps with the section specified in the cancellation history, the corrected history output means 6 determines that the seat-unit history corresponds to a specific type. Then, a correction cancellation history (correction record), which is correction data to offset the other records, is generated (S265). Furthermore, if the travel section of the other record does not overlap with the section specified in the cancellation history, a sales history for correction (correction record) is generated as correction data for restoring the travel section of the other record that does not overlap with the section specified in the cancellation history (S266). Furthermore, a sales history for correction (correction record) is generated as correction data for offsetting the cancellation history (S267). Then, these correction records and the cancellation history (input record) are stored in the work area (S268), and the correction process is then completed (Figure 13). The correction pattern in this case is, for example, the seventh correction pattern or the nineteenth correction pattern. On the other hand, when it is determined (S264) whether the travel section of another record of the same seat history overlaps with the section specified in the cancellation history, if there is no other record whose travel section overlaps with the section specified in the cancellation history, the corrected history output means 6 determines that the seat unit history corresponds to a specific type. Then, a corrected sales history (correction record) is generated (S267), which is correction data for offsetting the cancellation history. Then, this correction record and the cancellation history (input record) are stored in the work area (S268), and the correction process is then completed (Figure 13). The correction pattern in this case is, for example, the 9th correction pattern.

[0089] The correction process has been explained above when it is assumed that the seat unit history (input record) to be processed stored in the work area is a sales history or a cancellation history. Next, we will explain the case when it is assumed that the seat unit history (input record) to be processed stored in the work area includes a seat number input sales history. When the seat unit history (input record) includes seat number input sales, a step of determining whether the seat unit history (input record) is a seat number input sales history is provided between the step of determining whether the seat unit history (input record) is a sales history (S207) and the step of determining whether the seat unit history (input record) is a cancellation history (S235) in the flowcharts shown in Figures 10 to 13. Then, in determining whether the seat unit history (input record) is a seat number input sales history, if the seat unit history is a seat number input sales history, the same processing as when the seat unit history is a sales history, specifically, the processing corresponding to steps S208 to S234, is also performed on the seat number input sales history. On the other hand, in the step of determining whether the seat unit history (input record) is a seat number input sales history, if the seat unit history (input record) is not a seat number input sales history, the process proceeds to the step of determining whether the seat unit history is a cancellation history (S235). In this way, by configuring the system to include a determination as to whether the seat unit history is a seat number input sales history and processing corresponding to steps S208 to S234 between the determination as to whether the seat unit history is a sales history (S207) and the determination as to whether the seat unit history is a cancellation history (S235), the correction process by the corrected history output means 6 can be made to correspond to seat number input sales. In this case, the correction patterns exemplified above as the 13th correction pattern, 14th correction pattern, 17th correction pattern, 18th correction pattern, 21st correction pattern to 25th correction pattern, 27th correction pattern, 28th correction pattern, and 30th correction pattern are added.

[0090] Although the embodiments of the present invention have been described in detail above, the present invention is not limited to the above-described embodiments, and various design modifications can be made to the present invention without departing from the scope of the claims.

[0091] For example, in the embodiment of the present invention, an example is shown in which a recording means 7 for recording the corrected history is provided and the corrected history output means 6 has a same seat history addition judgment function for making judgments on seat unit history including same seat history, but the corrected history output means 6 may be configured to make judgments only on seat unit history created by the seat unit history creation means 5 without having the recording means 7. [Explanation of symbols]

[0092] 1. Correction processing system 2. Control measures 3. Means of communication 4. Operation history acquisition method 5. Seat-by-seat history creation method 6 Corrected history output method 7 Recording Method 10 Reservation Management System 11 Control measures 12. Means of communication 13 Reservation Management Methods 14 Recording means 20 Reservation terminal 30 Mobile Devices 40 Operation history management table 40a~40g ​​records 50 Seat-by-seat history management table 50a~50n records N Network

Claims

1. A correction processing system that corrects an operation history of a reservation management system that manages the reservation and sale of seats for a transportation means in order to calculate a sales performance of the seats based on the operation history of the reservation and sale of the seats, an operation history acquisition means for acquiring the operation history from the reservation management system; a seat unit history creating means for creating a seat unit history by dividing the operation history into seat units; a corrected history output means for determining whether the seat unit history for each seat corresponds to a specific type, and if the seat unit history corresponds to the specific type, generating correction data for correcting the seat unit history of the specific type, and outputting a corrected history obtained by adding the correction data to the seat unit history, the specific type is a type that causes a total value obtained by aggregating the seat unit history to be inconsistent with the sales performance, the corrected history output means generates the corrected data for making the aggregated value coincide with the sales performance. A correction processing system comprising:

2. a recording means for recording the post-correction history, The corrected history output means has a same seat history addition determination function for searching the corrected histories recorded by the recording means for a same seat history that is the same as the seat unit history created by the seat unit history creation means, and, if there is a same seat history, for determining whether or not the same seat history corresponds to the specific type by including the same seat history in the seat unit history for each seat.

2. The correction processing system according to claim 1.

3. the corrected history output means identifies the seat based on the operation date of the transportation means, the type of the transportation means, and the position of the seat, which are included in the operation history; 3. The correction processing system according to claim 1 or 2.

4. The operation history includes a sales history indicating that the seat was sold by specifying a boarding section, and a cancellation history indicating that the sale of the seat was canceled by specifying a predetermined section.

3. The correction processing system according to claim 1 or 2.

5. The specific type is a first type consisting of only the revocation history, The correction data is the sales history for correction to offset the cancellation history of the first type.

5. The correction processing system according to claim 4.

6. the specific type is a second type configured only of a plurality of sales histories in which the same travel section is designated, the correction data is the cancellation history for correction to offset the sales history other than the latest sales history among the sales history of the second type, 5. The correction processing system according to claim 4.

7. the specific type is a third type that is configured from the sales history and the cancellation history in which the specified section is included in the travel section of the sales history, the correction data is the cancellation history for correction to offset the sales history of the third type, the sales history for correction to offset the cancellation history of the third type, and the sales history for correction to restore a portion of the sales history of the third type in which the riding section does not overlap with the specified section; 5. The correction processing system according to claim 4.

8. the specific type is a fourth type that is configured from the sales history and the cancellation history in which a part of the travel section in the sales history overlaps with a part of the specified section, the correction data is the cancellation history for correction to offset the sales history of the fourth type, the sales history for correction to offset the cancellation history of the fourth type, and the sales history for correction to restore a portion of the sales history of the fourth type in which the riding section does not overlap with the specified section; 5. The correction processing system according to claim 4.

9. the specific type is a fifth type that includes the sales history and the cancellation history in which the boarding section of the sales history is included in the predetermined section, The correction data is the cancellation history for correction to offset the sales history of the fifth type, and the sales history for correction to offset the cancellation history of the fifth type.

5. The correction processing system according to claim 4.

10. The specific type is a sixth type that includes the sales history and the cancellation history in which the predetermined section does not overlap with the riding section of the sales history, The correction data is the sales history for correction to offset the cancellation history of the sixth type.

5. The correction processing system according to claim 4.

11. the specific type is a seventh type that includes a plurality of sales histories and the cancellation histories in which all of the travel sections in each of the sales histories are included within the predetermined section, The correction data is the cancellation history for correction to offset each of the sales histories corresponding to each of the sales histories of the seventh type, and the sales history for correction to offset the cancellation history of the seventh type.

5. The correction processing system according to claim 4.

12. The specific type is an eighth type that is composed of a plurality of the sales histories and the cancellation histories in which at least one of the travel sections in the sales histories is included within the specified section and at least one of the travel sections overlaps with a part of the specified section, The correction data includes the cancellation history for correction to offset each of the sales histories corresponding to each of the sales histories of the eighth type, the sales history for correction to offset the cancellation history of the eighth type, and the sales history for correction to restore a portion of the sales history of the eighth type in which the riding section does not overlap with the specified section.

5. The correction processing system according to claim 4.

13. A correction processing program for correcting an operation history of a reservation management system that manages the reservation and sale of seats for a transportation means in order to calculate a sales performance of the seats based on the operation history, an operation history acquisition step of acquiring the operation history from the reservation management system; a seat unit history creation step for creating a seat unit history by dividing the operation history into seat units; a corrected history output procedure for determining whether the seat unit history for each seat corresponds to a specific type, and if the seat unit history corresponds to the specific type, generating correction data for correcting the seat unit history of the specific type, and outputting a corrected history in which the correction data is added to the seat unit history, the specific type is a type that causes a total value obtained by aggregating the seat unit history to be inconsistent with the sales performance, the corrected history output step generates the corrected data for making the aggregated value coincide with the sales performance. A correction processing program that causes a computer to execute the above steps.

14. A computer-readable recording medium storing the correction processing program according to claim 13. A computer-readable recording medium.

Citation Information

Patent Citations

  • Information providing device, information providing method, information providing program and recording medium

    JP2013015927A

  • Reservation number predictor

    JP2020175686A

  • Simple copying machine

    JP1984052224A