JP6055690B2 - Vehicle allocation candidate extraction method and apparatus - Google Patents

Vehicle allocation candidate extraction method and apparatus Download PDF

Info

Publication number
JP6055690B2
JP6055690B2 JP2013025104A JP2013025104A JP6055690B2 JP 6055690 B2 JP6055690 B2 JP 6055690B2 JP 2013025104 A JP2013025104 A JP 2013025104A JP 2013025104 A JP2013025104 A JP 2013025104A JP 6055690 B2 JP6055690 B2 JP 6055690B2
Authority
JP
Japan
Prior art keywords
vehicle
inspection
candidate extraction
allocation candidate
next day
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
JP2013025104A
Other languages
Japanese (ja)
Other versions
JP2014151849A (en
Inventor
佳裕 伊東
佳裕 伊東
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Priority to JP2013025104A priority Critical patent/JP6055690B2/en
Publication of JP2014151849A publication Critical patent/JP2014151849A/en
Application granted granted Critical
Publication of JP6055690B2 publication Critical patent/JP6055690B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Description

車両割当を支援するシステムに関する。
特に当日の検査実施状況及び車両運行区間を考慮した車両割当支援システムである。
The present invention relates to a system that supports vehicle allocation.
In particular, this is a vehicle allocation support system that takes into consideration the inspection implementation status and vehicle operation section on the day.

鉄道における車両割当は通常車両運用計画に基づき、どの車両を割当てるかを車両基地で行っている。しかし、この車両割当は数日前までに計画を行い、変更がない場合はその計画に従って車両割当を行う。しかし、ダイヤが乱れた場合には車両運用が変更し、かつ使用可能な車両も少なくなる。そこで、当日のダイヤ乱れ時に効率的な車両割当を行うためのシステムが重要となる。これに関係する技術として、特許文献1が挙げられる。特許文献1では、車両基地から中央指令所へ当日検査の状況をデータで送信するシステムが開示されている。   The vehicle allocation in the railway is based on the normal vehicle operation plan, which vehicle is allocated at the vehicle base. However, this vehicle allocation is planned several days before, and if there is no change, the vehicle allocation is performed according to the plan. However, when the schedule is disturbed, the vehicle operation is changed and the number of usable vehicles is also reduced. Therefore, a system for efficiently allocating vehicles at the time of schedule disturbance on the day becomes important. Patent document 1 is mentioned as a technique relevant to this. In patent document 1, the system which transmits the condition of the inspection on the day from a vehicle base to a central command center is disclosed.

特開平9-226588号公報JP-A-9-226588

しかし、特許文献1では、当日検査終了時刻に関する精度が高くないため、想定していた時間に車両の検査が終了せずに車両を割当てることが出来ない等の問題が発生する。また、リアルタイムのステータスしか考慮されていないため、中央指令所で使用可能と判断した場合においても翌日の運用に影響を及ぼす可能性が高い。   However, in Patent Document 1, since the accuracy with respect to the inspection end time on the day is not high, there arises a problem that the vehicle cannot be allocated without completing the inspection of the vehicle at the expected time. In addition, since only real-time status is taken into account, even if it is determined that it can be used at the central command office, there is a high possibility of affecting the operation of the next day.

そこで本願発明では、検査終了時刻の精度を上げるために検査難易度、検査実績及び検査担当者を考慮することでより精度の高い検査終了時刻を予測する。また、システムとして翌日の運用及び検査種別を考慮することで当日急遽使用した場合でも翌日への車両運用乱れを軽減すると供に使用可能な車両を絞ることが可能となる。   Therefore, in the present invention, in order to increase the accuracy of the inspection end time, the inspection end time with higher accuracy is predicted by considering the inspection difficulty level, the inspection results, and the person in charge of inspection. In addition, considering the operation and inspection type of the next day as a system, even if the vehicle is used suddenly on the day, it is possible to narrow down the vehicles that can be used together with reducing vehicle operation disturbance to the next day.

本発明によれば、検査終了時刻を精度高く判定することが可能になる。また、翌日以降の運用を考慮することで翌日以降の乱れが軽減し、当日の車両運用がスムーズになる。   According to the present invention, it is possible to determine the inspection end time with high accuracy. Moreover, by considering the operation after the next day, the disturbance after the next day is reduced, and the vehicle operation on that day becomes smooth.

車両割当支援システムのシステム構成図である。It is a system configuration figure of a vehicle allocation support system. 車両割当可能区間及び車両基地選択処理を示すフローチャートである。It is a flowchart which shows a vehicle allocatable section and a vehicle base selection process. 車両割当優先度を決定するための処理を示すフローチャートである。It is a flowchart which shows the process for determining vehicle allocation priority. 車両割当の優先度が低となった場合の判定処理を示すフローチャートである。It is a flowchart which shows the determination process when the priority of vehicle allocation becomes low. 検査中車両の判定処理を示すフローチャートである。It is a flowchart which shows the determination process of the vehicle under test | inspection. 検査終了確度判定処理を示すフローチャートである。It is a flowchart which shows a test | inspection completion probability determination process. 車両割当を行う優先度を点数形式で表したテーブルである。It is the table which represented the priority which performs vehicle allocation in the score format. 各車両において本処理を行った際の結果を纏めた表である。It is the table | surface which put together the result at the time of performing this process in each vehicle. 車両の基本情報を格納しているテーブルである。It is a table storing basic information of vehicles. 車両の割当状況を格納しているテーブルである。It is a table which stores the allocation situation of vehicles. 車両の検査計画に関する情報を格納しているテーブルである。It is the table which stores the information regarding the inspection plan of vehicles. 当日分の車両検査及び割当の情報を格納しているテーブルである。It is the table which stores the information of the vehicle inspection and allocation for the day. 車両検査の項目及び検査の難易度を格納しているテーブルである。It is a table which stores the item of vehicle inspection, and the difficulty of inspection. 検査車両の実績を格納しているテーブルである。It is a table which stores the track record of an inspection vehicle.

以下、図面を用いて本発明に関する実施の形態を説明する。   Hereinafter, embodiments of the present invention will be described with reference to the drawings.

図1は、車両割当支援システムのシステム構成の例を示すものである。本システムは、端末101、車両検索サーバ102、各種データベース(103から108)、検査実績サーバ109、ネットワーク110、携帯端末111を用いることで実行できる。ここで、車両検索サーバの処理部(CPU)は、当日車両割当可否判定処理、未割当車両抽出処理、翌日運用有りの優先度判定処理、検査中車両判定処理、検査終了確度判定処理についての機能を実行する。   FIG. 1 shows an example of a system configuration of a vehicle allocation support system. This system can be executed by using the terminal 101, the vehicle search server 102, various databases (103 to 108), the inspection result server 109, the network 110, and the portable terminal 111. Here, the processing unit (CPU) of the vehicle search server is a function of the vehicle assignment availability determination process, unassigned vehicle extraction process, priority determination process with next-day operation, vehicle inspection process during inspection, and inspection end probability determination process. Execute.

次に全体の処理の流れを説明する。まず、リアルタイムに検査状況を反映する処理から説明を行う。携帯端末111から伝送路110を経由して検査実績サーバ109へ検査実績(検査日、車両ID、検査ID、検査ID枝番、検査項目、担当者情報)を送信する。検査実績サーバ109にデータ送信後に検査実績(検査ID、車両ID、検査項目ID、検査枝番ID、検査項目、検査終了時刻、検査日、担当者情報)のデータを検査実績テーブル105へデータを格納していく。以上よりリアルタイムな検査データを検査実績テーブル105にデータを格納可能となる。次にダイヤ乱れが発生した場合について説明する。まず、端末001から伝送路110を経由し、車両検索サーバ102へ接続を行う。各サーバ内の処理で必要な車両情報(車種、系式、車両ID等の情報)、車両割当情報(当日、翌日分の車両割当情報)、検査計画情報(検査日、車両ID、検査ID、検査名等の情報)を各テーブルより収集する。次に、処理について詳しく見ていく。まず、リアルタイム処理について説明する。検査実績サーバ109よりリアルタイムに検査実績テーブル105へ検査実績(検査ID、車両ID、検査項目ID、検査枝番ID、検査項目、検査終了時刻、検査日、担当者情報)を反映し、格納する。次に日次バッチ処理について説明する。日次バッチ処理にて当日分車両割当情報及び車両検査計画情報を集計する。処理としては車両情報テーブル106(車両ID、型式、形式、車両番号、編成ID、休車情報)、車両割当テーブル107(車両ID、当日運用ID、翌日運用ID、翌々日運用ID)、検査計画テーブル108(検査ID、検査日、車両ID、検査項目ID、翌日運用ID)からデータをマージして当日分車両検査/割当テーブル103(車両ID、運用ID、検査ID、休車情報)を作成する。本処理を行うことで事前に当日分のみの車両割当情報を絞ることが可能となる。次にマスタデータである。検査項目テーブル104はマスタデータとする。検査項目テーブル(検査項目ID、検査枝番ID、検査名、検査項目、検査難易度)は車両の新規登録時にデータを登録する形態とする。作成されたデータは車両検索サーバにて処理を行う際に必要に応じてSQLを用いて呼び出して使用する形態とする。処理については図2以降で説明をする。   Next, the overall processing flow will be described. First, the process of reflecting the inspection status in real time will be described. Inspection results (inspection date, vehicle ID, inspection ID, inspection ID branch number, inspection item, person in charge information) are transmitted from the portable terminal 111 to the inspection result server 109 via the transmission path 110. After sending data to the inspection result server 109, the inspection result (inspection ID, vehicle ID, inspection item ID, inspection branch number ID, inspection item, inspection end time, inspection date, person in charge information) data is transferred to the inspection result table 105. Store it. As described above, real-time inspection data can be stored in the inspection result table 105. Next, a case where a diamond disturbance occurs will be described. First, a connection is made from the terminal 001 to the vehicle search server 102 via the transmission path 110. Vehicle information (information such as vehicle type, system, vehicle ID, etc.) required for processing in each server, vehicle allocation information (vehicle allocation information for the current day and the next day), inspection plan information (inspection date, vehicle ID, inspection ID, Information such as examination name) is collected from each table. Next, we will look at the processing in detail. First, real-time processing will be described. Reflect and store the inspection results (inspection ID, vehicle ID, inspection item ID, inspection branch ID, inspection item, inspection end time, inspection date, person in charge information) in the inspection result table 105 in real time from the inspection result server 109 . Next, daily batch processing will be described. The vehicle allocation information and vehicle inspection plan information for the current day are tabulated by daily batch processing. As processing, vehicle information table 106 (vehicle ID, model, format, vehicle number, organization ID, stop information), vehicle allocation table 107 (vehicle ID, same day operation ID, next day operation ID, next day operation ID), inspection plan table Merge data from 108 (inspection ID, inspection date, vehicle ID, inspection item ID, next day operation ID) and create vehicle inspection / assignment table 103 (vehicle ID, operation ID, inspection ID, rest information) for the day . By performing this process, it is possible to narrow down the vehicle allocation information for the current day in advance. Next is master data. The inspection item table 104 is assumed to be master data. The inspection item table (inspection item ID, inspection branch number ID, inspection name, inspection item, inspection difficulty) is configured to register data when a new vehicle is registered. The created data is called and used using SQL as necessary when processing is performed by the vehicle search server. The process will be described with reference to FIG.

ここで、図2から図6までのフローチャートで使用するテーブルについて説明する。図9から図14までは本システムのインプットであるテーブルについて示している。   Here, the tables used in the flowcharts of FIGS. 2 to 6 will be described. FIG. 9 to FIG. 14 show tables that are inputs of this system.

図9は車両の基本情報を格納しているテーブルである。本システムのインプットとなる。   FIG. 9 is a table storing basic vehicle information. It becomes the input of this system.

図10は車両の割当状況を格納しているテーブルである。本システムのインプットとなる。   FIG. 10 is a table storing the allocation status of vehicles. It becomes the input of this system.

図11は車両の検査計画に関する情報を格納しているテーブルである。本システムのインプットとなる。   FIG. 11 is a table storing information relating to a vehicle inspection plan. It becomes the input of this system.

図12は当日分の車両検査及び割当の情報を格納しているテーブルである。本システムでは1日毎に更新される中間データとなる。   FIG. 12 is a table storing vehicle inspection and allocation information for the current day. In this system, intermediate data is updated every day.

図13は車両検査の項目及び検査の難易度を格納しているテーブルである。本システムではマスタデータとなる。   FIG. 13 is a table storing vehicle inspection items and inspection difficulty levels. In this system, it becomes master data.

図14は検査車両の実績を格納しているテーブルである。本システムのインプットとなる。   FIG. 14 is a table storing the results of the inspection vehicle. It becomes the input of this system.

次に、本システムの処理をフローチャートを用いて説明する。   Next, the processing of this system will be described using a flowchart.

図2は、車両割当を行うためのメイン処理である。図3のフローチャートを参照しながら説明を行う。まず、未割当車両抽出処理(S0001)を行う。ここでは車両運用されていない車両を抽出する処理である。検索方法としては図1の当日分検査/割当テーブルより運用IDがNULLのものを全て抽出する処理とする。この処理の詳細については図3で説明を行う。次に、休車判定処理(S0002)を行う。休車判定処理とは車両を割当てることが出来ない車両を判定する処理である。休車とは廃車になる直前の車両等で通常割当を行うことが出来ない車両のことである。この判定でNGの場合は車両割当対象外(S0003)とし、車両の割当対象外とし、図7の車両評価テーブルへ書き出す。一方、休車でない車両はOKとなり、検査種別判定(S0004)の処理に移る。検査種別判定とは鉄道における検査の種別を判定する処理である。鉄道における検査には清掃、仕業検査、交番検査、重要部検査、全般検査などがある。そのうちの交番検査、重要部検査、全般検査については検査項目が多く検査時間が掛かるため本処理では車両割当対象外(S0005)とし、図7の車両評価テーブルへ書き出す。一方でそれ以外の検査及び清掃の場合は検査等の時間が短いため車両割当の対象とする。そのため、仕業検査及び清掃の場合は翌日運用判定(S0006)に移る。翌日運用判定とは翌日に該当の車両が運用に割当たっているかどうかの判定を行うステップである。翌日に運用が割当てられている場合は車両を翌日までにその箇所へ移動する必要があるため、運用が厳しくなる。そのため、翌日に運用が割当っている場合は車両運用割当優先度を-5(S0007)とし、図7の車両評価テーブルへ書き出す。車両割当優先度とは車両の割当優先度を数値化したものである。車両割当優先度については最上位を+10とし最下位をー8とここでは定義する。次に翌日運用有の優先度判定処理(S0008)を行う。詳細については図4の処理で説明を行う。次に、翌日運用なしの場合の処理である。翌日運用無しの場合は前述の車両運用の制限が少なく、翌日に車両を元に戻すだけで済む。そのため、車両割当優先度を下げることはしない。次に、現在ステータス判定(S0009)を行う。現在ステータス判定とは車両が現在検査中かどうかを判定するステップである。現在検査中の場合には車両を直ぐに動かすことが出来ないため車両割当の制限があると判断する。現在車両の検査中と判断された車両については検査中車両判定処理(S0010)を行う。検査中車両判定処理については図5の処理で説明を行う。一方、検査中車両判定処理において車両の検査が完了している場合には車両割当優先度+10(S0011)とし、図7の車両評価テーブルへ書き出す。この車両が最も優先度の高い車両と判断する。   FIG. 2 shows a main process for performing vehicle allocation. This will be described with reference to the flowchart of FIG. First, unassigned vehicle extraction processing (S0001) is performed. Here, it is a process of extracting a vehicle that is not operated. As a retrieval method, the processing for extracting all null operation IDs from the current day inspection / allocation table of FIG. Details of this processing will be described with reference to FIG. Next, a stoppage determination process (S0002) is performed. The stoppage determination process is a process for determining a vehicle to which a vehicle cannot be assigned. A closed vehicle is a vehicle that cannot be assigned normally, such as a vehicle just before it is scrapped. If this determination is NG, the vehicle is not assigned (S0003), the vehicle is not assigned, and is written in the vehicle evaluation table of FIG. On the other hand, vehicles that are not at rest are OK, and the process proceeds to inspection type determination (S0004). The inspection type determination is a process for determining the type of inspection in the railway. Railway inspections include cleaning, work inspection, police box inspection, critical part inspection, and general inspection. Of these inspections, the alternating inspection, the important part inspection, and the general inspection have many inspection items, and it takes an inspection time. In this process, the inspection is excluded from the vehicle allocation target (S0005) and is written in the vehicle evaluation table of FIG. On the other hand, other inspections and cleanings are subject to vehicle allocation because of the short inspection time. Therefore, in the case of work inspection and cleaning, the operation moves to the next day operation determination (S0006). The next day operation determination is a step of determining whether or not the corresponding vehicle is assigned to operation on the next day. When operation is assigned on the next day, it is necessary to move the vehicle to that location by the next day, which makes operation difficult. Therefore, if operation is allocated the next day, the vehicle operation allocation priority is set to -5 (S0007), and it is written in the vehicle evaluation table of FIG. The vehicle allocation priority is a numerical value of the vehicle allocation priority. The vehicle allocation priority is defined here as +10 for the highest and -8 for the lowest. Next, priority determination processing (S0008) is performed with the next day operation. Details will be described in the processing of FIG. Next, it is a process when there is no operation the next day. When there is no operation on the next day, there are few restrictions on the vehicle operation described above, and it is only necessary to return the vehicle to the previous day. Therefore, the vehicle allocation priority is not lowered. Next, a current status determination (S0009) is performed. The current status determination is a step of determining whether the vehicle is currently being inspected. If the vehicle is currently being inspected, it is determined that there is a limitation on vehicle allocation because the vehicle cannot be moved immediately. For a vehicle that is currently determined to be inspected, the in-inspection vehicle determination process (S0010) is performed. The vehicle determination process during inspection will be described with reference to the process of FIG. On the other hand, when the vehicle inspection is completed in the in-inspection vehicle determination process, the vehicle allocation priority is set to +10 (S0011), and the result is written in the vehicle evaluation table of FIG. It is determined that this vehicle has the highest priority.

図3は、未割当車両でかつ特定の運行区間内に入る車両の抽出を行う処理である。未割当車両とは当日運用されていない車両のことを指す。まず、指令側で運行可能区間の入力(S0101)を行う。運行可能区間とはダイヤ乱れが発生した場合に運行可能な区間のことを指す。たとえばA駅〜B駅〜C駅があるとした場合にA駅〜B駅にて事故等の運行不能区間が発生した場合に運行可能区間をB駅〜C駅とする。次に該当工場判定処理(S0102)である。該当工場判定処理とは運行可能区間内にある車両工場を抽出する処理である。ここで言う車両工場とは車両の保管及び検査等を行うものと定義する。次に、該当工場選択(S0103)である。該当工場選択とは該当工場判定処理にて抽出した工場の中から指令が出庫させたい工場の選択を行うステップである。最後に未割当車両抽出処理(S0104)である。未割当車両抽出処理とは該当工場選択で選択した工場の中で運用が未割当である車両の抽出を行う処理である。これは図1の当日分車両検査/割当テーブル103(車両ID、運用ID、検査ID、休車情報)にて運用IDがNULLの場合の車両を抽出する処理である。   FIG. 3 is a process for extracting unassigned vehicles and vehicles that fall within a specific operation section. An unallocated vehicle refers to a vehicle that is not operated on that day. First, the operation side is entered on the command side (S0101). The operable section refers to a section that can be operated when a time disturbance occurs. For example, if there is an A station to a B station to a C station, and an inoperable section such as an accident occurs at the A station to the B station, the operable section is defined as the B station to the C station. Next, the relevant factory determination process (S0102) is performed. The relevant factory determination process is a process for extracting a vehicle factory in the operable section. The vehicle factory as used herein is defined as a vehicle that is stored and inspected. Next, the relevant factory is selected (S0103). The relevant factory selection is a step of selecting a factory for which the command is to be issued from the factories extracted in the relevant factory determination process. Finally, unallocated vehicle extraction processing (S0104). The unassigned vehicle extraction process is a process for extracting a vehicle that is not assigned to an operation in the factory selected by the factory selection. This is a process of extracting a vehicle when the operation ID is NULL in the vehicle inspection / assignment table 103 (vehicle ID, operation ID, inspection ID, rest information) for the day of FIG.

図4は、翌日運用がある場合の優先度判定処理である。翌日運用がある場合とは翌日以降に車両の運用割当が行われている場合の処理である。まず、翌日運用開始駅選択(S0201)を端末001にて行う。翌日運用開始駅選択とは翌日の運用開始駅を指令にて選択入力するステップである。運用開始駅とは1日の運用を始めるにあたり最初にどこの駅からスタートするかという基準駅のことである。以上より、翌日の運用開始駅を判定することが可能となる。次に開始駅判定処理(S0202)である。開始駅判定処理とは翌日運用開始駅選択にて選択した駅が翌日以降の運用開始駅が同一駅かどうかを判定する処理となる。翌日運用開始駅が不一致の場合は車両割当対象外とし、図7の車両評価テーブルへ書き出す。開始駅判定で一致した場合は現在のステータス判定(S0204)を行う。現在ステータス判定とは車両が現在検査中かどうかを判定するステップとなる。現在車両の検査中と判断された場合は検査中車両判定処理(S0205)を行う。検査中車両判定処理については図6の処理で説明を行う。次に、車両割当優先度を+2(S0206)すし、図7の車両評価テーブルへ書き出す。これは車両割当優先度を補正するための処理である。一方、検査中車両判定処理において車両の検査が完了している場合には車両割当優先度+5(S0207)とし、図7の車両評価テーブルへ書き出す。この車両は翌日運用がある場合の車両の中では優先度の高い車両として判断する。   FIG. 4 shows a priority determination process when there is a next day operation. The case where there is operation on the next day is processing when the operation allocation of the vehicle is performed after the next day. First, the next day operation start station selection (S0201) is performed at the terminal 001. The next day operation start station selection is a step of selecting and inputting the operation start station of the next day by a command. The operation start station is a reference station which station starts from the beginning of the day operation. From the above, it becomes possible to determine the operation start station of the next day. Next is start station determination processing (S0202). The start station determination process is a process for determining whether the station selected in the next day operation start station selection is the same station as the operation start station after the next day. If the next day operation start station does not match, it is excluded from the vehicle allocation target and is written in the vehicle evaluation table of FIG. If there is a match in the starting station determination, the current status determination (S0204) is performed. The current status determination is a step of determining whether the vehicle is currently being inspected. If it is determined that the vehicle is currently being inspected, a vehicle under inspection determination process (S0205) is performed. The vehicle determination process during inspection will be described with reference to the process of FIG. Next, the vehicle allocation priority is increased by +2 (S0206) and written to the vehicle evaluation table of FIG. This is a process for correcting the vehicle allocation priority. On the other hand, if the vehicle inspection is completed in the in-inspection vehicle determination process, the vehicle allocation priority is set to +5 (S0207), and the result is written in the vehicle evaluation table of FIG. This vehicle is determined as a vehicle having a high priority among vehicles in the case of operation on the next day.

図5は検査中車両判定処理を行うステップである。まず。使用開始時刻及び車両基地の入力(S0301)を端末001にて行う。この処理では使用開始時刻及び出庫させたい車両基地を入力することでシステム側に制約を設けることが可能となる。使用開始時刻とはダイヤ乱れ等が発生した場合に車両の出庫をさせたい時刻のことを指す。また、出庫させたい車両基地とはどこの基地の車両を出庫させたいのかを入力する処理のことである。次に時刻、場所判定(S0302)である。時刻、場所判定とは使用開始時刻及び車両基地の入力で入力された内容とその車両基地にて検査を行っている車両の検査終了予定時刻を判定する処理である。検査終了予定時刻とは車両の検査が終了する予定時刻のことである。検査が終了する予定時刻は車両の検査を行う人が携帯端末007から入力を行うことで入手する。時刻、場所判定で検査予定時刻を超える場合については車両割当優先度を−10(S0303)とし車両の割当優先度を下げ、図7の車両評価テーブルへ書き出す。一方、時刻、場所判定で検査予定時刻を越えない場合については検査終了確度判定処理(S0304)を行う。検査終了確度判定処理とは検査終了予定時刻通りに検査が終わるかどうかを検査難易度から判定する処理である。検査終了確度判定処理の詳細については図6にて説明する。   FIG. 5 shows steps for performing the vehicle determination process during inspection. First. The terminal 001 inputs the use start time and the vehicle base (S0301). In this process, it is possible to set restrictions on the system side by inputting the use start time and the vehicle base to be delivered. The use start time refers to the time at which the vehicle is to be released when a time disturbance or the like occurs. In addition, the vehicle base to be issued is a process of inputting which base vehicle to output. Next is time and place determination (S0302). The time and place determination is processing for determining the use start time and the contents input at the input of the vehicle base and the scheduled end time of inspection of the vehicle being inspected at the vehicle base. The scheduled inspection end time is the scheduled time when the vehicle inspection ends. The scheduled time when the inspection is completed is obtained by inputting from the portable terminal 007 by a person who inspects the vehicle. When the scheduled inspection time exceeds the time and place determination, the vehicle allocation priority is set to -10 (S0303), the vehicle allocation priority is lowered, and the result is written in the vehicle evaluation table of FIG. On the other hand, when the time and place determination does not exceed the scheduled inspection time, an inspection end probability determination process (S0304) is performed. The inspection end probability determination process is a process for determining from the inspection difficulty level whether or not the inspection is completed according to the scheduled inspection end time. Details of the inspection end probability determination process will be described with reference to FIG.

図6は検査終了確度判定処理を行うステップである。このステップでは検査終了予定時刻を確実に守れるかどうかを判定する。まず、残検査項目難易度判定処理(S0401)を行う。残検査項目難易度判定処理とは残りの検査項目をピックアップし、難易度の高い検査数を判定する処理である。難易度のレベルは予め設定しておき、そのレベルに応じて車両の割当優先度を決定する。検査の難易度は1〜5で設定し、難易度が4、5の検査が全体の半分以上ある場合は車両割当優先度を−5(S0402)とし、図7の車両評価テーブルへ書き出す。それ以外の場合は車両割当優先度を+5(S0403)とし、図7の車両評価テーブルへ書き出す。以上により車両の割当優先度が決定する。   FIG. 6 is a step for performing an inspection end probability determination process. In this step, it is determined whether or not the scheduled end time of inspection can be surely observed. First, the remaining inspection item difficulty level determination process (S0401) is performed. The remaining inspection item difficulty level determination process is a process of picking up the remaining inspection items and determining the number of inspections with a high degree of difficulty. The level of difficulty is set in advance, and the allocation priority of the vehicle is determined according to the level. The inspection difficulty level is set from 1 to 5. If inspections with difficulty levels of 4 and 5 are more than half of the entire inspection, the vehicle allocation priority is set to -5 (S0402), and is written in the vehicle evaluation table of FIG. In other cases, the vehicle allocation priority is set to +5 (S0403), and is written in the vehicle evaluation table of FIG. The vehicle allocation priority is determined as described above.

図8は図2から図6までで行った処理の結果を纏めた表である。まず、車両1は休車の車両を指す。この車両は休車のため休車判定処理でNGとなるためこの車両は割当対象が判断される。次に車両2である。この車両は交番検査が割り当っている車両である。休車判定ではOKであるが検査種別判定でNGとなり、車両の割当対象害となる。次に車両3である。この車両は翌日運用ありで、翌日の開始駅がNGの場合の車両である。この車両は翌日運用判定でNGかつ開始駅判定でNGとなるため車両の割当対象外し、図7の車両評価テーブルへ書き出す。次に車両4である。この車両は翌日運用ありで、翌日の開始駅はOKで検査終了している車両である。この場合の車両は現在使用可能であり、また翌日の運用にも問題がないため割当対象とし、車両の割当可能とする。車両割当優先度としては+2と判断される。次に車両5である。この車両は翌日運用ありで、翌日の開始駅がOKの場合の車両で、検査が未終了の車両である。しかし時刻/場所判定でNGのため車両割当対象外とし、図7の車両評価テーブルへ書き出す。次に車両6である。この車両は翌日運用ありで、翌日の開始駅がOKの場合の車両で、検査は未終了の車両である。しかしこの車両は残検査の難易度が高いものが少ないため、検査終了の精度が高いため割当対象とする。また、割当優先度は+2とする。次に車両7である。この車両は翌日運用ありで、翌日の開始駅がOKの場合の車両で検査未終了であり、検査の難易度が高いものが多く残っているという状況である。そのため車両の割当は対象とするが車両割当優先度は低くなり、−8となる。次に車両8である。この車両は翌日運用なしで、検査が終了もしくは待機車両である。そのため、車両の割当優先度は高く、+10となる。この車両は最も優先して出庫すべき車両となる。次に車両9である。この車両は翌日運用なしで、検査が未終了の車両である。また、時刻/場所判定でNGのため車両の割当対象外とし、図7の車両評価テーブルへ書き出す。次に車両10である。この車両は翌日運用なしで、検査が未終了の車両である。さらに、検査の難易度が高いものが少なく時刻どおりに検査が終了する可能性が高いため、車両の割当優先度は+5となる。この車両は車両8の次に優先して出庫すべき車両となる。次に車両11である。この車両は翌日運用なしで、検査が未終了の車両である。さらに、検査の難易度が高いものが多く時刻どおりに検査が終了する可能性が低いため、車両の割当優先度は−5となる。   FIG. 8 is a table summarizing the results of the processing performed in FIGS. First, the vehicle 1 indicates a closed vehicle. Since this vehicle is closed, it is judged as “NG” in the stop determination process, so that this vehicle is determined to be assigned. Next is the vehicle 2. This vehicle is the vehicle to which the police inspection is assigned. Although it is OK in the stoppage determination, it becomes NG in the inspection type determination, and is a harm to be assigned to the vehicle. Next is the vehicle 3. This vehicle is in operation when the next day is in operation and the starting station on the next day is NG. Since this vehicle is NG in the next day operation determination and NG in the start station determination, it is excluded from the vehicle allocation target and is written in the vehicle evaluation table of FIG. Next is the vehicle 4. This vehicle is in operation the next day, and the next day's starting station is OK and the vehicle has been inspected. The vehicle in this case can be used now, and since there is no problem in the next day's operation, the vehicle is assigned and the vehicle can be assigned. The vehicle allocation priority is determined to be +2. Next is the vehicle 5. This vehicle is in operation when the next day is in operation and the starting station of the next day is OK, and the vehicle has not been inspected. However, because it is NG in the time / place determination, it is excluded from the vehicle allocation target, and is written in the vehicle evaluation table of FIG. Next is the vehicle 6. This vehicle is in operation when the next day is in operation and the starting station of the next day is OK, and the inspection has not been completed. However, since there are few vehicles that have a high degree of difficulty for the remaining inspection, this vehicle is an assignment target because the accuracy of the inspection end is high. The allocation priority is +2. Next is the vehicle 7. This vehicle is in operation on the next day, and the inspection is not completed for the vehicle when the starting station of the next day is OK, and there are many remaining high difficulty inspections. Therefore, although vehicle allocation is targeted, the vehicle allocation priority is low and becomes -8. Next is the vehicle 8. This vehicle is not operated the next day, and the inspection is completed or is a standby vehicle. Therefore, the allocation priority of the vehicle is high and becomes +10. This vehicle is the vehicle that should be delivered with the highest priority. Next is the vehicle 9. This vehicle is not operated the next day, and has not been inspected. Also, because the time / location determination is NG, the vehicle is not assigned and is written in the vehicle evaluation table in FIG. Next is the vehicle 10. This vehicle is not operated the next day, and has not been inspected. Furthermore, since there are few things with high inspection difficulty and it is highly likely that the inspection will be completed on time, the vehicle allocation priority is +5. This vehicle is a vehicle that should be delivered prior to the vehicle 8. Next is the vehicle 11. This vehicle is not operated the next day, and has not been inspected. Furthermore, since there are many things with high inspection difficulty and it is unlikely that the inspection will be completed according to the time, the allocation priority of the vehicle is -5.

101:端末、102:車両検索サーバ、109:検査実績サーバ、111:携帯端末。 101: terminal, 102: vehicle search server, 109: inspection result server, 111: portable terminal.

Claims (8)

運用に割り当てる車両の候補を抽出する車両割当候補抽出方法であって、
翌日運用判定処理部が、複数の車両についての、翌日の運用状況情報から翌日に運用が予定されているかを判定し、当該判定の結果に応じて所定の点数をカウントする翌日運用判定ステップと、
検査中車両判定処理部が、前記複数の車両についての、現在の車両検査状況情報から、現時の車両の検査状況を判定し、当該判定に応じた所定の点数をカウントする検査中車両判定ステップと、
割当車両候補抽出処理部が、前記翌日運用判定ステップと前記検査中車両判定ステップとでカウントした点数を合算することで、列車毎に割当しやすさを示す優先度情報を算出する割当車両候補抽出ステップと、
を備えることを特徴とする車両割当候補抽出方法。
A vehicle allocation candidate extraction method for extracting vehicle candidates to be allocated to operation,
The next day operation determination processing unit determines whether the next day operation is scheduled from the next day operation status information for a plurality of vehicles, and counts a predetermined score according to the determination result,
An in-inspection vehicle determination processing unit that determines the current vehicle inspection status from the current vehicle inspection status information for the plurality of vehicles, and counts a predetermined score according to the determination; ,
The assigned vehicle candidate extraction processing unit calculates priority information indicating ease of assignment for each train by adding the points counted in the next day operation determination step and the in-inspection vehicle determination step. Steps,
A vehicle allocation candidate extraction method comprising:
請求項1に記載の車両割当候補抽出方法において、
前記検査中車両判定ステップで、現在検査中と判定された場合、更に、残りの検査項目についての検査難易度を判定し、当該検査難易度の判定結果に基いて所定の点数をカウントすることを特徴とする車両割当候補抽出方法。
In the vehicle allocation candidate extraction method according to claim 1,
When it is determined that the current inspection is in progress in the vehicle inspection step, the inspection difficulty level for the remaining inspection items is further determined, and a predetermined score is counted based on the determination result of the inspection difficulty level. A characteristic vehicle allocation candidate extraction method.
請求項2に記載の車両割当候補抽出方法において、
前記検査中車両判定ステップでは、難易度が高い場合に負の点数をカウントすることを特徴とする車両割当候補抽出方法。
In the vehicle allocation candidate extraction method according to claim 2,
The vehicle allocation candidate extraction method, wherein in the in-inspection vehicle determination step, a negative score is counted when the difficulty level is high.
請求項2又は3に記載の車両割当候補抽出方法において、
前記残りの検査項目が複数ある場合は、当該複数の検査項目の難易度のうち半数の割合を占める難易度で前記点数を決定することを特徴とする車両割当候補抽出方法。
In the vehicle allocation candidate extraction method according to claim 2 or 3,
The vehicle allocation candidate extraction method, wherein when there are a plurality of the remaining inspection items, the score is determined based on a difficulty that occupies a half of the difficulty of the plurality of inspection items.
運用に割り当てる車両の候補を抽出する車両割当候補抽出装置であって、
複数の車両についての、翌日の運用状況情報から翌日に運用が予定されているかを判定し、当該判定の結果に応じて所定の点数をカウントする翌日運用判定処理部と、
前記複数の車両についての、現在の車両検査状況情報から、現時の車両の検査状況を判定し、当該判定に応じた所定の点数をカウントする検査中車両判定処理部と、
前記翌日運用判定処理部と前記検査中車両判定処理部とでカウントした点数を合算することで、列車毎に割当しやすさを示す優先度情報を算出する割当車両候補抽出処理部と、
を備えることを特徴とする車両割当候補抽出装置。
A vehicle allocation candidate extraction device that extracts vehicle candidates to be allocated to operation,
The next day operation determination processing unit that determines whether operation is scheduled for the next day from the operation status information for the next day for a plurality of vehicles, and counts a predetermined score according to the result of the determination,
About the plurality of vehicles, from the current vehicle inspection status information, the current vehicle inspection status information is determined, a vehicle in-inspection determination processing unit that counts a predetermined score according to the determination,
An assigned vehicle candidate extraction processing unit that calculates priority information indicating ease of allocation for each train by adding the points counted by the next day operation determination processing unit and the vehicle determination processing unit under inspection;
A vehicle allocation candidate extraction apparatus comprising:
請求項5に記載の車両割当候補抽出装置において、
前記検査中車両判定処理部で、現在検査中と判定された場合、更に、残りの検査項目についての検査難易度を判定し、当該検査難易度の判定結果に基いて所定の点数をカウントすることを特徴とする車両割当候補抽出装置。
In the vehicle allocation candidate extraction device according to claim 5,
When it is determined that the current inspection is being performed by the in-inspection vehicle determination processing unit, the inspection difficulty for the remaining inspection items is further determined, and a predetermined score is counted based on the determination result of the inspection difficulty. A vehicle allocation candidate extraction device characterized by the above.
請求項6に記載の車両割当候補抽出装置において、
前記検査中車両判定処理部は、難易度が高い場合に負の点数をカウントすることを特徴とする車両割当候補抽出装置。
In the vehicle allocation candidate extraction device according to claim 6,
The vehicle allocation candidate extraction device, wherein the in-inspection vehicle determination processing unit counts a negative score when the difficulty level is high.
請求項6又は7に記載の車両割当候補抽出装置において、
前記残りの検査項目が複数ある場合は、当該複数の検査項目の難易度のうち半数の割合を占める難易度で前記点数を決定することを特徴とする車両割当候補抽出装置。
In the vehicle allocation candidate extraction device according to claim 6 or 7,
When there are a plurality of the remaining inspection items, the score is determined based on the difficulty that occupies a half of the difficulty of the plurality of inspection items.
JP2013025104A 2013-02-13 2013-02-13 Vehicle allocation candidate extraction method and apparatus Active JP6055690B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2013025104A JP6055690B2 (en) 2013-02-13 2013-02-13 Vehicle allocation candidate extraction method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2013025104A JP6055690B2 (en) 2013-02-13 2013-02-13 Vehicle allocation candidate extraction method and apparatus

Publications (2)

Publication Number Publication Date
JP2014151849A JP2014151849A (en) 2014-08-25
JP6055690B2 true JP6055690B2 (en) 2016-12-27

Family

ID=51574120

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2013025104A Active JP6055690B2 (en) 2013-02-13 2013-02-13 Vehicle allocation candidate extraction method and apparatus

Country Status (1)

Country Link
JP (1) JP6055690B2 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017213964A (en) * 2016-05-31 2017-12-07 東日本旅客鉄道株式会社 Vehicle operation work assisting device and vehicle operation work assisting system
JP7022039B2 (en) 2018-09-11 2022-02-17 株式会社日立製作所 Vehicle allocation support systems, methods, and programs

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6446912B1 (en) * 2000-11-29 2002-09-10 General Electric Company Railcar maintenance management method
JP5075577B2 (en) * 2007-10-29 2012-11-21 株式会社東芝 Vehicle operation plan creation apparatus and method
JP5746840B2 (en) * 2010-09-03 2015-07-08 株式会社日立製作所 Vehicle operation management method and server
JP2013010388A (en) * 2011-06-28 2013-01-17 Ntt Data Sekisui Systems Corp Vehicle operation plan preparation device

Also Published As

Publication number Publication date
JP2014151849A (en) 2014-08-25

Similar Documents

Publication Publication Date Title
US8401726B2 (en) Maintenance interval determination and optimization tool and method
CN106960300B (en) Method and device for realizing initial inventory of medicine logistics industry
CN106709679B (en) Method and device for allocating tasks of stacker
US20140365265A1 (en) Semiconductor bullet lot dispatch systems and methods
CN106529917B (en) Workflow processing method and device
Wang et al. A simulation analysis of part launching and order collection decisions for a flexible manufacturing system
US20200293027A1 (en) Information processing device, control method thereof, and control program
JP6055690B2 (en) Vehicle allocation candidate extraction method and apparatus
JP2011111058A (en) Operation arrangement support device and operation arrangement system using the device
CN105303245B (en) Traffic analysis system and traffic analysis method
CN115760068A (en) Electromechanical equipment maintenance method and system for rail vehicle
JP5271139B2 (en) Diamond management method, program, and diamond management apparatus
US20060100844A1 (en) Test time forecast system and method thereof
JP2004078917A (en) Process for optimization and synchronization for manufacture
JP2008046746A (en) Process managing system
US20220283578A1 (en) Resource Allocation System for Maintaining a Production Facility
Wang et al. Collation delay optimization using discrete event simulation in mail-order pharmacy automation systems
JPH08137961A (en) Processing system and its managing method for information on product
JP2017154536A (en) Crew operation management system and crew operation management method
Xie et al. Efficient order picking methods in robotic mobile fulfillment systems
Serna-Ampuero et al. Inventory Management Model under the Lean Warehousing Approach to Reduce the Rate of Returns in SME Distributors
JP7348051B2 (en) Work instruction system and work instruction method
EP4036826A1 (en) Method for predicting the daily available capacity of a parcel pick-up station and computerized locker banks
US20210237269A1 (en) Intervention systems and methods for robotic picking systems
JP2022122297A (en) Data evaluation system and posts evaluation method

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20151126

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20160815

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20160823

A521 Request for written amendment filed

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20161014

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20161108

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20161205

R151 Written notification of patent or utility model registration

Ref document number: 6055690

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R151