JP2001347948A - Inspection planning device, method, and recording medium in railway vehicle - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a vehicle inspection planning device for planning a highly efficient vehicle inspection scheme. SOLUTION: This inspection planning device is characterized in that inspection records of the railway vehicle, actual running distance data of the vehicle are stored in the database and this device is provided with a means for drafting the vehicle inspection scheme from the inspection records and the actual running data of the vehicle and a means changing extraction conditions of an inspection target vehicle.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and an apparatus for preparing an inspection plan for a railway vehicle using a computer.
In particular, the present invention relates to a method and an apparatus for planning and evaluating the result of planning.

[0002]

2. Description of the Related Art Heretofore, a plan for inspection of railway vehicles (appropriation of vehicles to be inspected) has been performed based on the experience of an inspection plan creator.

[0003] Recently, information necessary for preparing an inspection plan for a railway vehicle is input using input means such as a keyboard or a mouse, and the input data is defined for the inspection plan drafted by the inspection plan creator. The computer evaluates whether various constraints are satisfied.

[0004] The evaluation by the computer is displayed on a screen of a display device.
You have manually created an inspection plan.

A technique for inputting data of a vehicle operation plan necessary for creating an inspection plan has been put to practical use as a vehicle operation plan creation support device. As an apparatus for supporting the preparation of a vehicle operation plan, for example, Japanese Patent Application Laid-Open No. 8-85459 discloses that (1) constraint conditions consisting of an operation schedule of operation equipment and an inspection plan are input, and (2) a horizontal axis represents a date. , Each element of the two-dimensional matrix with the vertical axis as the operation number of the operating equipment is used as a node, and the above constraint conditions are coded as the connection state between nodes on adjacent dates to create an operating connection code for the operating equipment,
(3) rearrange the created operation code using random numbers, (4) convert the rearranged operation connection code into an operation connection matrix, and (5) convert the converted operation connection matrix to the above-mentioned constraint conditions. It is evaluated based on the degree of constraint satisfaction indicating whether or not it is provided. If the above evaluation is out of the predetermined range, the above (3) to
An operation planning method for operating equipment has been proposed, in which the step of (5) is repeated until the evaluation becomes a predetermined one and converted into an optimal operating connection matrix, thereby creating an operating plan for the operating equipment. .

JP-A-11-245819 discloses a train schedule and an inspection plan stored in a database, and a means for generating a vehicle operation plan from the train schedule and the inspection plan.
Evaluating means for evaluating the generated vehicle operation plan based on a sum of evaluation amounts for each of a plurality of evaluation criteria, and modifying the vehicle operation plan so that the evaluation value becomes a predetermined value or more. As a vehicle operation plan creation device for creating a plan, there has been proposed a vehicle operation plan creation device having a configuration including means for changing weights for a plurality of evaluation criteria.

[0007]

However, in the above-mentioned JP-A-8-85459 and JP-A-11-245819, an inspection plan is created by manual input, and an inspection plan creator is required. Input operation is required.

For this reason, when the number of railway vehicles to be inspected increases, the time required for planning becomes longer, the work load of the inspection plan creator increases, and it is difficult to create an efficient inspection plan. Become.

SUMMARY OF THE INVENTION Accordingly, the present invention has been made in view of the above-mentioned problems, and has as its object to provide a railway vehicle inspection plan automatic preparation apparatus and method for automatically and efficiently preparing a railway vehicle inspection plan, and a recording method. To provide a medium.

[0010]

In order to achieve the above object, an inspection record of a railway vehicle and a data record of the number of kilometers actually traveled by the vehicle are stored in a database, and the vehicle is obtained from the inspection record and the actual traveling data of the vehicle. A means for creating an inspection plan and a means for changing conditions such as an execution cycle of a vehicle to be inspected are provided, and it is possible to cope with a change in the execution cycle depending on the type of inspection.

[0011]

Embodiments of the present invention will be described. The present invention includes a database for storing the inspection record of the railway vehicle and the traveling result data, and referring to the database, from the inspection record of the railway vehicle and the traveling result data, the inspection plan of the railway vehicle. Is automatically created, and the execution cycle condition of the railcar to be inspected is changed from the created inspection plan.

In the present invention, the database includes:
The running results of the railway vehicle, the inspection results, the operation plan information, the plan constraints are stored, and by referring to the database, a railway vehicle that may be out of inspection is extracted, and the extracted railway vehicle is extracted. Automatically set the date of the inspection. In extracting a railway vehicle that may be out of the inspection, a previous inspection date is obtained from the inspection result of the railway vehicle with reference to the database, and a one-time inspection date is obtained based on the traveling result of the railway vehicle. Calculate the average mileage per day.

[0013] In automatically setting the inspection execution date of the railway vehicle, a final inspection date is obtained from the inspection results of the railway vehicle, an inspection cycle date of an inspection target rank is added, and the inspection of the railway vehicle is completed. Calculate the day of occurrence.

Further, in automatically setting the inspection execution date of the railway vehicle, a final inspection date is obtained from the inspection results of the railway vehicle, and an inspection cycle distance of an inspection target rank and an average mileage per day are used. Then, the date on which the inspection has expired is calculated.

When preparing a rolling stock inspection plan for the railway vehicle, a scheduled enforcement date is set in consideration of the number of days the vehicle will be closed.

The conditions for changing the inspection plan are as follows:
Select inspection cycle distance priority or inspection cycle day priority.
Alternatively, a priority inspection rank is changed as a condition for changing the inspection plan.

According to the present invention, there is provided an inspection plan preparation condition database in which a running result of a vehicle, an inspection result, operation plan information, plan constraint conditions, and plan change conditions are stored.
An inspection target vehicle that extracts a vehicle that may be out of inspection based on operation plan information, traveling results, and inspection results stored in the inspection plan creation condition database, and automatically sets an inspection execution date. A allocating unit, (b) an inspection plan storage unit for storing the generated inspection plan, and (c) an inspection plan stored in the inspection plan storage unit are stored in the inspection plan creation condition database. Whether or not the plan constraint condition is satisfied is determined based on the operation plan information, the number of vehicles that can be processed daily at the inspection location,
A constraint condition determination unit that stores the determination result in the inspection plan storage unit; (d) an inspection target vehicle condition selection unit that selects the conditions of the inspection target vehicle; and (e) a test target vehicle based on the inspection plan change condition. An inspection target vehicle condition determining unit that performs a condition determination, wherein the inspection target vehicle allocation unit, the constraint condition determining unit, the inspection target vehicle condition selecting unit, and the inspection target vehicle condition determining unit are programs executed on a computer. By its processing,
The function is realized. In this case, the present invention is realized by reading out the program from a recording medium (a floppy (registered trademark) disk, hard disk, magnetic tape medium, CD-ROM, DVD, semiconductor memory, etc.) on which the program is recorded, and executing the program. Can be implemented.

[0018]

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram showing an embodiment of the present invention; FIG. 1 is a diagram showing a configuration of an embodiment of a vehicle inspection plan creation device of the present invention.

Referring to FIG. 1, one embodiment of the present invention is:
Inspection plan creation condition database 6, inspection target vehicle allocation unit 1, constraint determination unit 2, inspection target vehicle condition determination unit 3, inspection plan storage unit 7, display unit 4, inspection target vehicle condition selection unit 5, a display device 8, and an input device 9.

The inspection plan creation condition database 6 stores the actual driving results of the vehicle, the inspection results, the operation plan information, the plan constraint conditions, and the plan change conditions.

The vehicle to be inspected 1 assigns a locomotive (vehicle) that may be out of inspection, based on the operation plan information, running results, and inspection results stored in the inspection plan preparation condition database 6. Extract and set the date of inspection automatically.

The generated inspection plan is stored in the inspection plan storage 7.

The constraint condition judging section 2 stores whether or not the inspection plan stored in the inspection plan storage section 7 satisfies the plan restriction conditions stored in the inspection plan preparation condition database 6. Judgment is made based on the operation plan and the number of vehicles that can be processed daily at the inspection location. This determination result is stored in the inspection plan storage unit 7.

The inspection target vehicle condition determining unit 3 includes an input device 9
Of the inspection target vehicle condition selection unit 5 to determine whether to omit the inspection based on the upper / lower relationship according to the inspection type and whether the inspection period is to be set to the number of days or the mileage (km Number).

The judgment is made in the inspection plan preparation condition database 6
The result is stored in the inspection plan storage unit 7. At the time of input operation, the display unit (display control unit) 7 extracts data from the inspection plan storage unit 7 and
(Cathode ray tube), display device (display device) 8 such as LCD (liquid crystal display).

The driving results, inspection results, operation plan information, plan constraint conditions, and plan change conditions stored in the inspection plan creation condition database 6 will be described.

[Running Result] The running result stores the cumulative running distance (unit: kilometers) of each vehicle, the running distance after inspection (unit: kilometers) for each rank, and the number of running days after inspection.

FIG. 2 shows the number of kilometers traveled after inspection (abbreviated as "kilo") and the number of days. For each vehicle number, the inspection date, inspection type, kilometer after inspection, and number of days after inspection (each inspection rank) After-inspection information for each test) is stored.

[Inspection] Next, the inspection will be described.
Railway cars are required to be regularly inspected by ministerial ordinance. The types of tests are roughly classified into two types: long-term tests and short-term tests. Further, in some cases, each company performs an inspection by setting a more detailed inspection rank among long-term inspection and short-term inspection. For example, some companies (business operators) provide three ranks for long-term inspection and four ranks for short-term inspection.

An inspection cycle is determined for the inspection. In the inspection cycle, the number of days after the inspection and the number of kilometers traveled after the inspection are defined as numerical values. Failure to carry out the inspection before the inspection cycle is exceeded will result in a violation of the Ministerial Ordinance. During the inspection cycle,
If the vehicle has not run for one day, it will be closed. The number of days of suspension is subtracted from the number of days in the inspection cycle. However, the maximum number of days of suspension is also specified, and it is not possible to set unlimited suspension.

[Inspection Results] The inspection results store the history of the inspections performed in the past for each vehicle. When the inspection is performed, the rank type of the performed inspection and the period during which the inspection is performed are stored.

[Operation plan information] The operation plan information stores information on which driving schedule the vehicle operates.

[Plan Plan Constraints] The plan plan constraints are the following constraints.

(1) The inspection execution date is set before the date when the vehicle is out of inspection.

(2) If an operation plan has been set after the date when the vehicle has expired, a warning is displayed to prompt the user to change the operation plan.

(3) When the inspection of the vehicle has expired, the date of the upper inspection and the date of the lower inspection are compared. If the period of the date is shorter than the inspection cycle of the lower inspection, the upper inspection is performed first. To enforce.

(4) When setting the inspection execution date of the vehicle,
Do not exceed the maximum number of days of suspension during the inspection cycle.

[Plan Change Condition] The plan change condition is as follows.
The change conditions are as follows.

(1) When changing the inspection execution date of a vehicle, it is selected whether to give priority to the inspection cycle of the target inspection for the kilometer or the number of days.
Cause recalculation.

(2) When changing the inspection execution date of a vehicle, when a priority inspection rank is changed, recalculation is performed and the inspection execution date is reset.

(3) When changing the inspection execution date of the vehicle, no operation plan is set on the changed date.
If an operation plan is set on the changed date, a warning is displayed to urge the change of the operation plan.

Next, the processing of one embodiment of the present invention will be described. FIG. 3 is a flowchart showing a flow of processing of a long-term inspection plan in one embodiment of the present invention.

In step 301, the number of years is obtained from the date when the processing is started, and this is set as an initial value. For example, if the date when the process started is March 10, 2000, the target year = “12” is set.

In step 302, the vehicle to be inspected is extracted by the vehicle to be inspected 1 and is allocated to the extracted vehicle.

The past inspection results are taken out from the inspection plan preparation condition database 6, and the number of days from the last inspection date to the present date is calculated.

Next, the running results are taken out, and the running kilometers after the final inspection is performed are calculated.

Then, the number of days off from the last inspection day is taken out, and the number of days after inspection is calculated within a specified maximum number of days.

From the above calculation results, the date when the inspection expires is calculated according to the following equation (1a) or (1b).

If the inspection cycle is the number of days, the final inspection date + the number of inspection cycles-the number of days off (1a) If the inspection cycle is kilometers, the current day + the number of days off from the vehicle + (inspection cycle-after inspection) Traveling km) / (Average traveling km per day)… (1b)

Depending on the inspection rank, the inspection cycle includes a rank in which a kilo (distance) and the number of days are set, and a rank in which either the kilo (distance) or the number of days is set.

In the case where the number of inspection cycles and the number of kilometers are set, the one closer to the expiration date is adopted.

The number of days for car suspension is not unlimited but an upper limit that can be set is determined. If the number of days for car suspension has not reached the upper limit, the set number of days is used as it is. Result is,
It is stored in the inspection plan storage database 7.

In step 303, the constraint condition judging section 2 checks whether or not the constraint condition of the plan is satisfied. The plan constraint conditions are the above four conditions.

From the inspection plan storage database 7 to the display unit 4
The operator confirms the result output to the display device 8 by the operator, and proceeds to step 305 if the condition is satisfied, and proceeds to step 304 if the condition is not satisfied.

In step 304, when the constraint condition is not satisfied, a correction process is manually performed. The operator performs input from the input device 9 and manually allocates the vehicle (creates a vehicle inspection plan) while visually checking items output to the display device 8 by the display unit 4. The inspection plan, which is the allocation result, is stored in the inspection plan storage unit 7.

In step 305, the inspection target vehicle condition determining unit 3 determines the conditions of the inspection target vehicle based on the plan change condition.

In step 305, the operator changes the conditions of the vehicle to be inspected output from the inspection plan storage unit 7 through the input device 9 by the inspection vehicle condition selection unit 5. The change operation is output to the display device 8 by the display unit 4, and the operator can visually confirm the change in the condition of the vehicle.

When the plan change condition is selected by the inspection target vehicle condition selection unit 5, it is selected whether to give priority to the inspection cycle in kilos or to the number of days. At this time,
When the inspection cycle of the target inspection rank is only kilos or days, the change cannot be made.

When there are two inspection cycles, the one with a shorter inspection end date is used. Then, the recalculation is performed in kilos or days, and the inspection execution date can be reset.
The reset result is stored in the inspection plan storage 7.

When a plan change condition is selected by the inspection target vehicle condition selection unit 5, the target inspection rank is changed, and the scheduled execution date is recalculated.

Since the upper inspection date is given priority according to the plan constraint, the lower inspection is changed to priority, and the scheduled execution date is recalculated and reset. The reset result is stored in the inspection plan storage 7.

When the scheduled inspection execution date is changed, a condition indicated by the plan change condition (plan change condition: if an operation plan is set on the changed date, a warning is displayed, and the change of the operation plan is displayed. If the prompting is satisfied, a warning is displayed on the display device 8 via the display unit 4.

At step 306, whether or not the vehicle allocation according to the inspection plan is completed is output to the display device 8. When it is determined that the allocation has been completed and the operator selects the operation end from the input device 9, the operation proceeds to the end. If the allocation is not completed and the operator selects the continuation of the operation from the input device 9, the process proceeds to step 305.

FIG. 4 is a flowchart showing the flow of processing of a short-term inspection plan in one embodiment of the present invention. FIG.
In the short-term inspection plan, the month of the day is the target month for the start of the inspection plan creation, while the process flow in FIG. 3 of the long-term inspection plan sets the year of the day as the start year of the inspection plan creation. Except for differences, the processing flow of FIG. 4 is the same as the processing flow shown in FIG.

In step 401, the number of months is taken from the date when the processing is started, and is set as an initial value. For example, if the date when the processing started is March 10, 2000, the target month = “3” is set.

In step 402, the vehicle to be inspected is extracted by the vehicle to be inspected 1 and the vehicle to be inspected is allocated.

First, the past inspection results are retrieved from the database 6 and the number of days from the last inspection date to the present date is calculated.

Next, the running results are taken out, and the running kilometers after the final inspection is performed are calculated.

Then, the number of days off from the last inspection day is taken out, and the number of days after inspection is calculated within a specified maximum number of days.

From the above calculation results, the date when the inspection expires is calculated.

When the inspection cycle is the number of days, the final inspection day + the number of inspection cycle days−the number of days off (1a), and when the inspection cycle is kilo, the current day + the number of days off the vehicle + (inspection cycle kilo -Traveled kilometers after inspection) / (Average traveled kilometers per day) ... (1b).

Depending on the inspection rank, the inspection cycle includes a rank in which the number of kilometers and the number of days are set, and a rank in which either the number of kilometers or the number of days is set. If two or more inspection cycles are set for kilos or days, the one near the expiration date is adopted. The number of days of car suspension is not unlimited, but a settable upper limit is determined. If the number of days of car suspension has not reached the upper limit, the set number of days is used as it is. The result is stored in the inspection plan storage 7.

At step 403, the constraint condition judging section 2 checks whether or not the constraint condition of the plan is satisfied. The constraints are four conditions. The operator visually confirms the result output from the inspection plan storage database 7 to the display device 8 via the display unit 4, and proceeds to step 405 when the condition is satisfied, and proceeds to step 404 when the condition is not satisfied. move on.

In step 404, when the constraint condition is not satisfied, the correction process is manually performed. The operator performs input from the input device 9 and manually allocates the vehicle while visually checking items output to the display device 8 under the control of the display unit 4. The allocation result is stored in the inspection plan storage unit 7.

In step 405, the inspection target vehicle condition determination unit 3 makes a condition determination based on the plan change condition. In this step, the operator changes the conditions of the vehicle through the input device 9 using the inspection target vehicle condition selection unit 5 output from the inspection plan storage database. The operation is output to the display device 8 by the display unit 4, and the operator can visually confirm the operation.

When the schedule change condition is selected by the inspection target vehicle condition selection unit 5, the user selects whether to give priority to the inspection cycle in kilos or to the number of days. At this time, when the inspection cycle of the target inspection rank is only kilometers or only days, it cannot be changed. If there are two types of inspection cycles, the one with the shorter inspection end date is adopted, so that it is recalculated here in kilos or days and the inspection execution date can be reset. The reset result is stored in the inspection plan storage 7.

When the schedule change condition is selected by the inspection target vehicle condition selection unit 5, the inspection rank to be inspected is changed and the scheduled execution date is recalculated. Since the higher-level inspection date is prioritized due to the plan constraint, the lower-level inspection is prioritized, and the scheduled execution date is recalculated and reset. The reset result is stored in the inspection plan storage 7.

When the scheduled test execution date is changed and the plan change condition satisfies the above condition, a warning is displayed on the display device 8 via the display unit 4.

At step 406, whether or not the vehicle allocation according to the inspection plan has been completed is output to the display device 8. When the operator selects the end of the operation from the input device 9 assuming that the allocation has been completed, the process proceeds to the end. On the other hand, when the allocation is not completed and the operator selects the continuation of the operation from the input device 9, the process proceeds to step 405.

[0080]

As described above, according to the present invention,
The constraints and conditions related to the inspection plan preparation are stored in the database in advance, and the inspection plan of the railway vehicle can be automatically created, and the inspection execution cycle can be changed.
This has the effect of increasing the efficiency of the inspection plan creation process.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of an embodiment of the present invention.

FIG. 2 is a diagram for explaining one embodiment of the present invention;
It is a figure showing a running record.

FIG. 3 is a flowchart showing a long-term inspection plan process in one embodiment of the present invention.

FIG. 4 is a flowchart showing a process of a short-term inspection plan in one embodiment of the present invention.

[Explanation of symbols]

 DESCRIPTION OF REFERENCE NUMERALS 1 inspection target vehicle allocation unit 2 constraint condition determination unit 3 inspection target vehicle condition determination unit 4 display unit 5 inspection target vehicle condition selection unit 6 inspection plan creation condition database 7 inspection plan storage unit 8 display device 9 input device

Claims (21)

[Claims] 1. A database for storing an inspection record of a railway vehicle and actual driving data, and an inspection of the railway vehicle based on the inspection record and the actual traveling data of the railway vehicle stored in the database. A vehicle inspection plan creating device, comprising: means for automatically creating a plan; and means for changing an inspection execution cycle condition of a railway vehicle to be inspected from the created inspection plan. 2. The database stores running results, inspection results, operation plan information, and plan constraint conditions of the railroad vehicle, and there is a possibility that an out-of-inspection may occur with reference to the database. The vehicle inspection plan creation device according to claim 1, further comprising: means for extracting a railway vehicle; and means for automatically setting an inspection execution date of the extracted railway vehicle. 3. The means for extracting a railway vehicle which may be out of inspection may refer to the database,
The previous inspection date is obtained from the inspection result of the railway vehicle,
3. The vehicle according to claim 2, further comprising: means for calculating an average traveling distance per day based on the traveling performance of the railway vehicle.
The described vehicle inspection plan creation device. 4. A means for automatically setting an inspection execution date of the railway vehicle, obtains a final inspection date from the inspection results of the railway vehicle, and adds an inspection cycle date of an inspection target rank to the final inspection date. 3. The vehicle inspection plan creating device according to claim 2, wherein a date when the inspection of the railway vehicle is completed is calculated. 5. A means for automatically setting an inspection execution date of a railway vehicle, obtains a final inspection date from an inspection result of the railway vehicle, and determines an inspection cycle distance of an inspection target rank and an average mileage per day. 4. The vehicle inspection plan creation device according to claim 3, wherein the date on which the inspection is to be stopped is calculated using: 6. A method for automatically preparing an inspection plan for a railway vehicle, wherein the means for automatically preparing an inspection plan for the railway vehicle sets a scheduled enforcement date in consideration of the number of days of suspension of the railway vehicle. The vehicle inspection plan creation device according to claim 1, wherein: 7. A means for changing an execution cycle condition of a railway vehicle to be inspected from the created inspection plan, selects inspection cycle distance priority or inspection cycle day priority as a condition for changing the inspection plan draft. 2. The vehicle inspection plan creation device according to claim 1, further comprising means for performing. 8. A means for changing an execution cycle condition of a railway vehicle to be inspected from the created inspection plan includes means for changing an inspection rank which is prioritized as a condition for changing the inspection plan. The vehicle inspection plan creation device according to claim 1, wherein: 9. A method for preparing a vehicle inspection plan using a computer, wherein the inspection record of the railway vehicle is referred to by referring to a database storing inspection records of a railway vehicle and actual driving data. Automatically creating an inspection plan for the railway vehicle from the actual driving data, and changing the inspection execution cycle condition of the railway vehicle to be inspected from the inspection plan. How to create a vehicle inspection plan. 10. The railway vehicle stores running results, inspection results, operation plan information, and plan constraint conditions of the railway vehicle, and refers to the database to refer to the railway vehicle which may be out of inspection. 10. The vehicle inspection plan creating method according to claim 9, wherein the inspection execution date of the extracted railway vehicle is automatically set. 11. Extraction of a railway vehicle with a possibility of running out of inspection, the database is referred to, a previous inspection date is obtained from the inspection result of the railway vehicle, and a running result of the railway vehicle is obtained. 11. The vehicle inspection plan creating method according to claim 10, wherein an average mileage per day is calculated based on the following. 12. Automatically setting an inspection execution date of the railway vehicle, obtaining a final inspection date from the inspection results of the railway vehicle, adding an inspection cycle date of an inspection target rank,
The vehicle inspection plan creating method according to claim 10, wherein a date at which the inspection of the railway vehicle is completed is calculated. 13. Automatically setting the inspection execution date of the railway vehicle, obtaining a final inspection date from the inspection results of the railway vehicle, determining an inspection cycle distance of an inspection target rank on the final inspection date, and 11. The date on which the inspection has expired is calculated using the average traveling distance of the vehicle.
The vehicle inspection plan creation method described. 14. The vehicle inspection plan creating method according to claim 9, wherein, when the vehicle inspection plan for the railway vehicle is created, a scheduled execution date is set in consideration of the number of days during which the vehicle is closed. 15. The vehicle inspection plan creating method according to claim 9, wherein a priority of the inspection cycle distance or a priority of the inspection cycle day is selected as a condition for changing the inspection plan. 16. The vehicle inspection plan creating method according to claim 9, wherein a priority inspection rank is changed as a condition for changing the inspection plan. 17. A step of setting an inspection plan creation start year, and referring to a database storing running results of railroad vehicles, inspection results, operation plan information, plan constraint conditions, and plan change conditions. Based on the stored operation plan information, running results, and inspection results, a vehicle that may be out of inspection is extracted as a vehicle to be inspected, and an inspection plan for the inspection vehicle is automatically created and stored. And outputting the inspection plan draft to check whether the plan constraint conditions stored in the database are satisfied, and if the constraint conditions are not satisfied, Modifying the stored inspection plan; and performing a condition determination of the vehicle to be inspected based on the plan change condition stored in the database. Comprising the steps, a vehicle inspection planning wherein the. 18. When the inspection cycle is the number of days, the final inspection date + the number of inspection cycles−the number of days off the car, and when the inspection cycle is distance, the current day + the number of days off the car + (inspection cycle distance−run after inspection) distance)
18. The vehicle inspection plan creation method according to claim 17, wherein a date on which the inspection of the railway vehicle expires is calculated from / (average mileage per day). 19. An inspection plan preparation condition database storing vehicle running results, inspection results, operation plan information, plan constraint conditions, and plan change conditions, and operation stored in the inspection plan preparation condition database. Based on the plan information, running results, and inspection results, a railway vehicle that may be out of inspection is extracted, and an inspection target vehicle allocation unit that automatically creates an inspection plan for the railway vehicle, An inspection plan storage unit for storing the inspection plan, and whether the inspection plan stored in the inspection plan storage unit satisfies the plan constraint stored in the inspection plan creation condition database. Operation plan information,
A constraint condition determination unit that makes a determination based on the number of vehicles that can be processed daily at an inspection location and stores the determination result in the inspection plan storage unit, and selects a condition determination of a railway vehicle to be inspected according to an instruction from an input device. A vehicle inspection plan creating device, comprising: an inspection target vehicle condition selection unit that performs inspection; and an inspection target vehicle condition determination unit that determines a condition of a railway vehicle to be inspected based on the plan change condition. 20. The driving record stored in the inspection plan preparation condition database includes information on an accumulated driving distance of each vehicle, a driving distance after inspection, and a number of days after inspection for each rank. The vehicle inspection plan creation device according to claim 19. 21. An inspection plan preparation condition database storing vehicle running results, inspection results, operation plan information, plan constraint conditions, and plan change conditions, an inspection plan storage unit for storing the inspection plan, (A) extracting a railway vehicle that may be out of inspection based on the operation plan information, running results, and inspection results stored in the inspection plan creation condition database, and inspecting the railway vehicle Inspection vehicle allocation processing for automatically creating a plan, (b) the inspection plan stored in the inspection plan storage unit,
Whether or not the plan constraint conditions stored in the inspection plan creation condition database are satisfied is determined based on operation plan information and the number of vehicles that can be processed at each inspection location on a daily basis, and the determination result is stored in the inspection plan storage. (C) an inspection vehicle condition selection process of selecting a condition determination of a railway vehicle to be inspected based on an instruction from the input device; and (d) a plan change condition based on the plan change condition. A recording medium storing a program for causing a computer to execute the inspection target vehicle condition determination process of determining the condition of the railroad vehicle to be inspected and the above-described processes (a) to (d).