JP2007062554A - Operation diagram cooperating plan producing system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve the workability of traffic diagram producing work by a plurality of users for producing a plurality of different diagrams having dependence, and to shorten a diagram producing work period. <P>SOLUTION: Of diagram planning work carried out by diagram editing terminals 1100a to 1100c, the diagram and a public opening range which are completed and can be opened to the public can be inputted by a user, and the contents of that is shared by a diagram management server 1200. From the diagram management server 1200, the newest work information contents and sharing partner designating information are sent to the user designated to share. Therefore, without being waited until the whole of the diagram is completed by a preceding user, a plurality of users can simultaneously produce the plurality of cooperation diagrams such as a train diagram, a vehicle operating diagram, and a crew operating diagram, and the diagram producing work period can be shortened. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an operation diagram cooperation plan creation system and method for supporting a traffic diagram creation work by mutual cooperation among a plurality of users in a traffic diagram creation work.

  The traffic schedule plan, especially the railway schedule plan, is roughly divided into three schedules. When creating a schedule, work is divided into many specialists / planning departments. That is, the train schedule represented by the timetable, the vehicle operation diagram that expresses the operation schedule of the vehicle that actually runs on the train diagram, and the train operation schedule of the driver who operates the train and the crew in charge of the in-vehicle duties It is a crew operation diagram.

  However, because each diagram is interdependent, in order to create the entire railway diagram as a rational plan, close coordination between the experts / planning departments in charge of the related diagram plans It is necessary to proceed with diamond creation work while taking it.

  As a technique for solving such a problem, there are Patent Document 1 and Patent Document 2. Patent Document 1 is a technique for automatically creating a train schedule in which the vehicle operation diagram and the crew operation diagram that have been created are taken into a computer and the consistency between these two diagrams is taken. Patent Document 2 is a technology that uses a plurality of different computers connected via a network to improve mutual cooperation by sharing work contents in real time among a plurality of users who are executing plans.

Japanese Patent Laid-Open No. 7-52801 (Overall) JP-A-10-236310 (Overall)

  However, when the technique disclosed in Patent Document 1 is applied, the following problems occur. In other words, after creating any one of the diamonds that make up a traffic diagram, creating another dependent diagram later allows the creation of the next diagram until a certain diagram is completed. Not efficient. In addition, since it is essential to ensure consistency with a diamond that has already been completed, the subsequent diamond may be created in a form that does not match the actual situation.

  Moreover, in the technique disclosed in Patent Document 2, a user A who creates a train diagram, a user B who creates a vehicle operation diagram, and a user C who creates a crew member operation diagram use devices of the same technology The following problems arise. That is, the user A cannot switch the work content sharing partner to the user B alone, or to both the users B and C according to the progress of the work. Even in an actual railway schedule plan, the planning work of the train schedule and vehicle operation schedule is advanced to some extent, and after the timetable and vehicle operation schedule are fixed, the crew operation schedule is created, and such a problem is assumed.

  The present invention has been made in view of the above circumstances, and an object of the present invention is an operation diagram cooperation plan capable of improving the efficiency of work of a plurality of users who create a plurality of diagrams having dependencies in a traffic diagram creation work. Is to provide a system.

  The main feature of the present invention is that a plurality of diagram editing terminals accept user input to create / change diagram data, and create / change the diagram data, its disclosure period, and users to be disclosed. The designated disclosure range designation information is transmitted to the diagram management server, and the diagram management server uses the diagram data for the designated publication period among the created / changed diagram data. It is to send to the editing terminal.

  According to a preferred embodiment of the present invention, a plurality of users who create a plurality of interdependent relationships such as a train diagram, a vehicle operation diagram, and a crew member operation diagram share a mutual work status data in parallel. Can proceed. Therefore, it is possible to improve the efficiency of diamond creation as a whole railway diagram plan and speed up the diamond creation.

  Embodiments of the present invention will be described below.

  FIG. 1 is a schematic functional configuration diagram of a traffic schedule management system including an operation schedule linkage planning system according to an embodiment of the present invention. As shown in the figure, the traffic diagram management system of this embodiment is configured by connecting three diagram editing terminals 1100a to 1100c and a diagram management server 1200 to each other via a network 1300 such as the Internet.

  Each of the diamond editing terminals 1100a to 1100c is configured to have the same function, and is a computer (information processing) device used by a person in charge (user) who performs a planned work. Generally, input devices 1150a to 1150c including a keyboard and a pointing device and display devices 1140a to 1140c such as liquid crystal and CRT are provided. In the following description, reference numerals a to c are omitted, common functions will be described, and only the explanations will be given with reference numerals a to c.

  The diamond editing terminal 1100 includes a processing device 1110, a storage device 1120 connected to the processing device, and an external storage device 1130. The storage device 1120 includes a change history management table 1121 and a public history management table 1122. The change history management table 1121 manages a log of update processing executed by the plan creation unit 1113 for the diagram data stored in the work DB 1131. The disclosure history management table 1122 manages the change history of the other diagram editing terminal 1100 received from the diagram management server 1200. The external storage device 1130 has a work DB 1131 for managing diagram data.

  The diagram editing terminal 1100 is equipped with hardware and software for communication (not shown). Therefore, it is possible to transmit and receive data via the network 1300 using them.

  The diamond editing terminal 1100 implements various functions by loading a program installed in the storage device 1120 into the processing device 1110 and executing it in the processing device 1110. For this reason, the processing device 1110 is not shown, but has a central processing unit (CPU), a memory, and the like. The diagram editing terminal 1100 includes a screen display unit 1111, a plan start unit 1112, a plan creation unit 1113, a plan transmission unit 1114, a status update unit 1115, and a disclosure history display unit 1116 as functions to be realized. The diamond editing terminal 1100 realizes the specific functions described below by executing programs corresponding to these functional units (means).

  The screen display unit 1111 displays on the display device 1140 a GUI (Graphical User Interface) that accepts user input and a diagram that graphically represents the diagram data stored in the work DB 1131. When the plan start unit 1112 receives input from the user via the GUI provided by the screen display unit 1111, the plan start unit 1112 extracts the diagram data necessary for creating the plan from the master DB 1231 of the diagram management server 1200 and stores it in the work DB 1131. Store. The plan creation unit 1113 receives a user operation via the input device 1150, executes a change operation of the diagram data stored in the work DB 1131, and writes an operation log in the change history management table 1121. The plan creation unit 1113 includes rules for executing plan creation in advance. The plan transmission unit 1114 receives user input via the GUI provided by the screen display unit 1111, and transmits the plan update information created from the change history management table 1121 and the diagram data in the work DB 1131 to the diagram management server 1200. To do. The status update unit 1115 creates status information indicating the disclosure range (publication period and user to be published) of the diamond data stored in the master DB 1231 based on the user input received via the screen display unit 1111, and the diagram management server Send to 1200. Based on the disclosure history management table 1122, the disclosure history display unit 1116 performs highlighting on the diagram data designated by the user on the diagram displayed by the screen display unit 1111.

  The diagram management server 1200 is a computer (information processing) device including a processing device 1210, a storage device 1220 connected to the storage device, and an external storage device 1230 including a storage medium such as a magnetic disk. In the external storage device 1230, a master DB 1231 that is accessed by at least two or more diamond editing terminals 1100a, 1100b,. In the storage device 1220, a status management table 1221 for managing the disclosure range (publication period and disclosure target user) of the diagram data stored in the master DB 1231, and the plan update information received from the diagram editing terminal 1100 are sent to other users. A plan update management table 1222 for managing information to which transmission history information is added is provided.

  The processing device 1210 includes a plan update unit 1211, a status update unit 1212, a public information creation unit 1213, and a public information transmission unit 1214, and implements specific functions by executing the corresponding programs. The plan update unit 1211 receives data and plan update information in the work DB 1131 from the plan transmission unit 1114 of the diagram editing terminal 1100 and updates the master DB 1231 and the plan update management table 1222. The status update unit 1212 receives status information from the status update unit 1115 of the diagram editing apparatus 1100 and updates the status management table 1221. The public information creation unit 1213 creates public information including difference information between the master DB 1231 and the work DB 1131 included in each diagram editing terminal 1100 from the status information and the plan update management table 1222. The public information transmission unit 1214 transmits the public information and the diagram data of the master DB 1231 to the designated diagram editing terminal 1100.

  FIG. 2 is an explanatory diagram showing the flow of processing (thick line arrows) and the flow of information (thin line arrows) in the service diagram cooperation planning system according to one embodiment of the present invention. In this figure, only functional units necessary for explanation are shown, but the diamond editing terminals 1100a to 1100c operated by the respective users a to c have the same functional units as explained in FIG. I have. The user a faces the diagram editing terminal 1100a and assumes that the train planning work is being executed, and the screen display unit 1111 displays the created planning screen on the display device 1140a (FIG. 1).

  2 will be described with reference to FIGS. 3 to 14 which are necessary operation screens, data tables, processing flow diagrams, and the like.

  First, FIG. 3 is a diagram showing an example of a plan creation screen in the service diagram cooperation planning system according to one embodiment of the present invention. The plan creation screen includes a plan start panel 310, a diagram display panel 320, a plan transmission panel 330, a status update panel 340, and a public information display panel 350. Each of these panels has an input space for receiving a user instruction, and buttons for executing functions provided in the diagram editing terminal 1100. The plan start panel 310 includes a plan number input space 311 for inputting a plan number, a plan period input space 312 for inputting a plan period, and a plan start 313 button for executing the plan start unit 1112 of FIG. In this example, when the plan start button 313 is pressed, the plan start unit 1112 of FIG. 2 is executed based on the information of the plan number “1001” and the plan period “N to N + 5”.

  Returning to FIG. 2, the description of the flow of processing will be continued. The plan start unit 1112 extracts from the master DB 1231 of the diagram management server 1200 the diagram data necessary for creating the plan based on the plan period and the plan operation being executed by the diagram editing terminal 1100, and the work DB 1131 on the own terminal. Copy to.

  FIG. 4 is a diagram showing a diagram data structure in the service diagram cooperation planning system according to the embodiment of the present invention. The schedule data is mainly composed of (a) a train schedule indicating the arrival / departure of a train, (b) a vehicle operation schedule indicating a vehicle operation schedule, (c) a crew operation schedule indicating a train crew schedule of the crew. A general term for data related to train operation. In this embodiment, the above three diagrams are defined as diagram data and the description will be continued.

  4100 is a data structure diagram of a train diagram. One record indicates one train unit, and at least the following items are held. That is, first, an execution date 4110 indicating the date on which the train actually operates, a train number 4120 indicating the unique identification number of the train, and then a starting station / starting time 4130 indicating the starting station and starting time of the train. Further, there are an intermediate station / time 4140 indicating an intermediate station on which the train passes and an arrival / departure time, and an end station / end time 4150 indicating an end station and an end time. For example, the record 4161 indicates that “the train has a train number A on N days, passes through Omiya from Tokyo first, and arrives at Hachinohe”.

  4200 is a data structure diagram of the vehicle operation diagram. One record indicates one unit of the vehicle operation schedule, and at least the following items are held. That is, firstly, there are an enforcement date 4210 indicating the day on which the operation schedule is executed, an operation number 4220 indicating the unique identification number of the operation schedule, and then an initial station / time 4230 indicating the operation start station and start time. Further, there are a station / time 4240 indicating the operation end station and the end time, and a connecting train 4250 indicating a train schedule through which the vehicle passes from the start to the end. For example, the record 4261 is “Operating a vehicle that has an operation number of 1 luck every N days, starts in Tokyo, and ends at Omiya via train schedules A, B, D, G, H. "Schedule".

  4300 is a data structure diagram of a crew member operation diagram. One record indicates one unit of the crew schedule of the crew, and at least the following items are held. That is, first, an enforcement date 4310 indicating the day on which the train operation schedule is executed, an operation number 4320 indicating a unique identification number of the train crew schedule, and then a first station / first time 4330 indicating the train departure first station and the first departure time. is there. Further, there are a train station ending station and an end station / end time 4340 indicating the end time, and a transit train 4350 indicating a train schedule for the crew to transfer from the start to the end. For example, record 4361 indicates that “the train crew schedule has an operation number of A luck on N day, starts in Tokyo, transfers trains A, B and D, and ends in Sendai”. .

  Creating the above-mentioned diagram data is a plan creation task, and different users a to c perform the plan creation task for each train diagram, vehicle operation diagram, and crew member operation diagram. However, between the train diagram information table 4100, the vehicle operation diagram information table 4200, and the crew member operation diagram information table 4300, such as the connecting train 4250 of the vehicle operation diagram 5200 and the transfer train 4350 of the crew member operation diagram 5300, etc. Are closely related. For this reason, the vehicle operation / crew crew operation planning work greatly depends on the result of the train planning work, and a train diagram is necessary to execute the vehicle operation / crew crew operation planning work.

  In addition, since there is a relationship between the vehicle operation diagram and the crew member operation plan task between the vehicle operation plan task and the crew member operation plan task, the crew member operation plan task greatly depends on the vehicle operation plan task. In addition, a vehicle operation diagram is required to execute the crew member operation plan operation.

  In the planning work, a diagram that graphically displays diagram data is used. FIG. 5 is an example of a diagram in the service diagram cooperation planning system according to one embodiment of the present invention. 5100 is a train diagram illustrating only the train diagram. The vertical axis 5110 is a station, the horizontal axis 5120 is time, and the course of one train diagram is shown as one oblique line. For example, the train diagram record 4161 in FIG. 4 is shown as a hatched line 5131 on the train diagram diagram 5100.

  Reference numeral 5200 denotes a vehicle / crew operator operation diagram illustrating a vehicle / crew operator operation diagram in addition to the train diagram. Train diagram Similar to FIG. 5100, the vertical axis 5210 represents the station, the horizontal axis 5220 represents the time, and the course of one train diagram is shown as one oblique line. The vehicle operation diagram shows an operation schedule for one vehicle operation diagram by a set of a circle-shaped start point, a box-shaped connection indicating a connection between train diagrams, and an end point of a triangle mark. The vehicle operation diagram 4261 in FIG. 4 is illustrated as a start point 5231, linkages 5232 to 5235, and an end point 5236. Similarly to the vehicle operation diagram, the crew member operation diagram also shows a train operation schedule for one crew member operation diagram with a set of start point, connecting point, and end point. The crew member operation diagram 4361 in FIG. 4 is illustrated as a dotted line 5240.

  Returning to FIG. 2, the description of the flow of processing will be continued. The diagram editing terminal 1100a is executing a train diagram plan, and executes the plan start unit 1112 in response to an input of the train plan period N to N + 5 days. For this reason, the train schedule whose enforcement date is N to N + 5 days is copied from the master DB 1231 of the diagram management server 1200 to the work DB 1131 of the own terminal 1100. Other diamond editing terminals 1100b and 1100c are also partially omitted in illustration, but have the same functions as the diamond editing terminal 1100a as described above. In the present embodiment, it is assumed that vehicle operation planning work and crew member operation planning work for N to N + 5 days are being executed at the diamond editing terminals 1100b and 1100c, respectively. Further, in 1100b, the plan starting unit 1112 reads out the train schedule and vehicle operation schedule whose enforcement date is N to N + 5 from the master DB 1231 of the diagram management server 1200 and copies it to the work DB 1131 in the own terminal 1100b. And Furthermore, in 1100c, it is assumed that the train schedule, the vehicle operation schedule, and the crew operation schedule whose enforcement dates are N to N + 5 are copied from the master DB 1231 of the diagram management server 1200 to the work DB 1131 in the own terminal 1100c.

  In the description of the present embodiment, the processing data by the diagram editing terminal 1100a that executes the train schedule plan is shared by the diagram editing terminals 1100b and 1100c that are executing the vehicle operation diagram planning task and the crew member operation diagram planning task, respectively. Proceed with the explanation.

  After the diagram data is copied to the work DB 1131 of the diagram editing terminal 1100a, the diagram data is shown as a diagram on the display panel 320 of the plan creation screen in FIG. The plan creation unit 1113 uses the input device 1150 to perform an operation by drag / drop or pull-down menu selection on the diagram in FIG. 3 to change the diagram data in the work DB 1131 to change the change history. Write to the management table 1121.

  FIG. 6 is a data structure diagram of the change history management table 1121 in the service diagram cooperation planning system according to the embodiment of the present invention. One record indicates one unit of the change history and has the following items. That is, first, the plan number 6100 and the enforcement date 6200 of the diamond data to be changed. Next, there are an identification number 6300 indicating any one of a train number, a vehicle operation number, or a crew member operation number, and a change content 6400 indicating the content of the change operation. Furthermore, it is an item of a time stamp 6500 indicating the time when the change was executed and a transmission flag 6600 indicating a transmission history to the diagram management server 1200. The example of FIG. 6 shows that the history records of 6710, 6720, and 6730 have been written by performing a change operation on the data of A train 4161, B train 4162, and H train 4165 of the train diagram table 4100 of FIG. Yes. Also, regarding the change history 6710 of A, it has already been transmitted to the diagram management server 1200.

  Returning to FIG. 2, the description of the processing is continued. The plan creation unit 1113 advances the plan creation, finalizes the plan, and publishes the created plan for a part that may be disclosed to the user b of the other vehicle operation plan work and the user c of the crew member operation plan work. For the release, the plan created by the schedule editing unit 1100 by the plan transmission unit 1114 is transmitted to the diagram management server 1200, and the status update unit 1115 transmits to other persons in charge b and c via the diagram management server 1200. To execute.

  The planned transmission unit 1114 is executed by inputting the enforcement date to be transmitted in the transmission date input space 331 provided in the planned transmission panel 330 in FIG. 3 and pressing the planned transmission button 332. A record without a change history transmission flag for the diagram data having the corresponding enforcement date in the change history management table 1121 and a diagram data having the corresponding enforcement date in the work DB 1131 are transmitted to the diagram management server 1200 as plan update information. In addition, the transmission flag 6300 included in the record of the change history management table 1121 transmitted in this process is rewritten as transmission ON. In this description, the value of the transmission date input space in FIG. 3 is N, N + 1. Therefore, the schedule transmission unit 1114 manages the schedule data indicated by 4161 to 4165 in the train schedule information table 4100 in FIG. 4A among the schedule data stored in the work DB 1131 as the plan update information. Transmit to server 1200. Also, 6720 and 6730 in FIG. 6 in the change history management table 1121 are transmitted to the diagram management server 1200 as planned update information, and the transmission flag 6600 of the record is rewritten to ON.

  Upon receiving the plan update information from the diagram editing terminal 1100, the diagram management server 1200 updates the master DB 1231 and the plan update management table 1222 by the plan update unit 1211.

  FIG. 7 is a data structure diagram of the plan update management table 1222 in the service diagram cooperation planning system according to the embodiment of the present invention. One record indicates one unit of the update history, and each item shown below is held. That is, first, the plan number 7100, the enforcement date 7200 of the updated diamond data, the identification number 7300, and then the change content 7400 and the time stamp 7500. Furthermore, it has items of a vehicle release time stamp 7600 and a crew member release time stamp 7700. The plan number 7100, the enforcement date 7200, the identification number 7300, the change content 7400, and the time stamp 7500 are the plan number 6100, the enforcement date 6200, the identification number 6300, the change content 6400, and the time stamp 6500 of the change history management table 1121 in FIG. It is an item of consent. If a record having the same value as the combination of the change history enforcement date 6200 and the identification number 6300 received as the plan update information exists in the plan update management table 1222, the record is overwritten by the change history. If it does not exist, it is added as a new record. The vehicle release time stamp 7600 and the crew member release time stamp 7700 are copies of the data held by the time stamp 7500 when the updated contents of the diagram data corresponding to the history are disclosed to the user of the vehicle / crew operator operation planning work, respectively. It is. If the time stamp 7500 and the vehicle / crew crew release time stamps 7600 and 7700 have the same value, this indicates that the update content has already been released, and if it is different or blank, the update content has not yet been released. Is shown.

  In the example of FIG. 7, the update content corresponding to the history of the record 7810 is disclosed to the user of the vehicle operation plan task, but is not disclosed to the user of the crew member operation plan task. The update contents related to the previous A-class 7810 shown in FIG. In addition, the update contents corresponding to the history of 7820 and 7830 are not disclosed.

  Returning to FIG. 2, the description of the processing is continued. The status update unit 1115 inputs the execution date of the plan to be published and the publication target range in the update date input space 341 and the public work input space 342 provided in the status update panel 340 in FIG. Press. The disclosure target range is only the vehicle operation planning work, the crew operation planning work only, or both. As a result, status information is created and transmitted to the diagram management server 1200.

  In this way, the schedule update executed by each of the diamond editing terminals 1100a to 1100c and whether or not they can be released are collected in the diagram management server 1200.

  FIG. 8 is a data structure diagram of status information in the service schedule cooperation planning system according to the embodiment of the present invention. The status information includes items of a plan number 8100, a start enforcement date 8200 of a period to be disclosed, an end enforcement date 8300, and a disclosure work 8400 indicating a disclosure range. In the example of FIG. 8, the update contents for N days are fully disclosed, that is, disclosed to both the vehicle operation plan work and the crew operation plan work, and the update contents for N + 1 days are disclosed only to the person in charge of the vehicle work operation. It is shown that.

  Returning to FIG. 2, the description of the processing is continued. Upon receiving status information from the diagram editing terminal 1100, the diagram management server 1200 updates the status management table 1221 based on the content received by the status update unit 1212, and moves the processing to the public information creation unit 1213.

  FIG. 9 is a data structure diagram of the status management table 1221 in the service schedule cooperation planning system according to the embodiment of the present invention. One record represents the disclosure range of the plan for one execution date, and has items of a plan number 9100, an execution date 9200 of the plan to be disclosed, and a disclosure work 9300 indicating the disclosure target range. The enforcement date 9200 and the public service 9300 are items having the same meanings as the public period 8200-8300 and the public service 8400 in FIG. 8, respectively. When the status management table 1221 has a record having the same enforcement date as the status information disclosure period 8200-8300 to be updated, it is overwritten by the status information, and when it does not exist, it is added as a new record.

  Returning to FIG. 2, the description of the processing is continued. The public information creation unit 1213 creates public information based on the plan update management table 1222.

  FIG. 10 is a process flow diagram of the public information creation unit 1213 in the service diagram cooperation planning system according to the embodiment of the present invention. In step 1001, status information is received from the status update unit 1212. In step 1002, an update history record having an enforcement date corresponding to the disclosure period in the status information is extracted from the planned update management table 1222. Here, let S be the extracted set. The status information in this description is the two records shown in FIG. 8, but the description of the processing will be continued by taking 8510 records as a specific example. Since the disclosure period of 8510 records is N days, 7810 and 7820 records are set S in the planned update management table 1222 of FIG. In step 1003, one record is extracted from S. The record extracted here is Y. Further, the description will be continued assuming that 7810 is taken out as an example. In step 1004, the contents of the status information disclosure task 8400 received in step 1001 are determined. If the value of the disclosure task is a vehicle disclosure or all disclosure, the process proceeds to step 1005. The process moves to step 1007. In the status information (8510 record in FIG. 8), which is a specific example in this description, the value of the public work 8400 is all public, so the process proceeds to step 1005. In step 1005, the value of the time stamp 7500 of the record extracted as Y from the planned update management table 1222 of FIG. 7 is compared with the value of the vehicle disclosure time stamp 7600. If the two values are the same, the process proceeds to 1010. If so, the process proceeds to 1006. In step 1006, the value of the time stamp 7500 is copied to the vehicle disclosure time stamp 7600, and the process proceeds to 1009. In step 1009, the Y plan number 7100, the enforcement date 7200, the identification number 7300, and the change content 7400 are stored in the buffer, and the process proceeds to 1010. In Y shown in this example (7810 in FIG. 7), the time stamp 7500 and the vehicle disclosure time stamp 7600 have the same value, and thus the process proceeds to step 1010 by the process of step 1005. In step 1010, it is determined whether or not the status information disclosure work 8400 received in step 1001 is fully disclosed. If it is fully disclosed, the process proceeds to step 1007, and if not fully disclosed, the process proceeds to step 1011. Proceed. In the status information (8510 in FIG. 8) in this description, since the value of the public work 8400 is all public, the process proceeds to step 1007. In step 1007, the time stamp 7500 of the record extracted as Y from the plan update management table 1222 of FIG. 7 is compared with the value of the crew release time stamp 7700. If the two values are the same, the process proceeds to 1010, and the values are different. If so, the process proceeds to 1008. In Y shown in this example (7810 in FIG. 7), the values of the time stamp 7500 and the crew member public time stamp 7700 are different, and the processing proceeds to step 1008. In step 1008, the value of the time stamp 7500 is copied to the crew member public time stamp 7700, and the process proceeds to 1009. In this description, at 1009, the values of the plan number “1001” of Y (7810 in FIG. 7), the enforcement date “N days”, the identification number “A”, and the change content “change line number” are stored in the buffer. , The process proceeds to Step 1010. In step 1010, the process proceeds to step 1007 by the same control as described above, and the process proceeds to 1011 by the control in step 1007. In step 1011, it is determined whether S is an empty set. If it is an empty set, the process proceeds to step 1012. If it is not an empty set, the process proceeds to step 1003. In this description, since the set S still contains 7820 in FIG. 7, the process proceeds to step 1003. Processing is performed with 7820 in FIG. 7 as Y, and processing is repeated with status information as 8520 in FIG. In step 1012, public information is created from the data stored in the buffer, and the process ends.

  In this way, the public information creation unit 1213 in the diagram management server 1200 creates public information based on the executed schedule creation / update and the contents of the plan update management table 1222 along the publication range.

  FIG. 11 is a data structure diagram of public information in the service schedule cooperation planning system according to the embodiment of the present invention. One record indicates one unit of public information, and has items of a disclosure destination 11100 indicating a disclosure target, a plan number 11200, an enforcement date 11300 of a diamond data to be disclosed, an identification number 11400, and a change content 11500.

  In this description, the status information is 8510 in FIG. 8, and the public information created in the processing of 7810 in FIG. 7 by the update history extracted from the planned update management table 1222 is 1161. In addition, the public information 1162 and 1163 created by the status information 8510 and the update history in the process 7820 are 1162 and 1163, respectively. Furthermore, the public information created in the update history 7830 in the status information 8520 becomes 1164.

  Returning to FIG. 2, the description of the processing is continued. The public information transmitting unit 1214 in the diamond management server 1200 transmits the diamond data of the master DB 1231 that is the effective date of disclosure and the public information created by the public information creating unit 1213 to the corresponding diamond editing terminals 1100b and 1100c.

  In the present description, a train schedule with an enforcement date of N, N + 1 is transmitted to the diagram editing terminal 1100b in charge of vehicle operation work. In addition, a diagram with an enforcement date of N days is transmitted to the diagram editing terminal 1100c in charge of crew member operation. Furthermore, 1162 and 1164 of FIG. 11 are transmitted to the diagram editing terminal 1100b as public information, and 1161 and 1163 of FIG. 11 are transmitted to the diagram editing terminal 1100c.

  The diagram editing terminals 1100b and 1100c that have received the public information and the train diagram copy the received train diagram to the work DB 1131 of their own terminal, and write the public information to the public history management table 1122. Therefore, the users who are in charge of planning operations of the vehicle operation and crew operation diagrams toward the diagram editing terminals 1100b and 1100c are disclosed among the completed train diagrams based on the user's intention to execute the train diagram planning operations. Share possible information.

  FIG. 12 is a data structure diagram of the public history management table 1122 in the service diagram cooperation planning system according to the embodiment of the present invention. Each time the public information is received, it has items of a public version 12100 that counts up one by one, a plan number 12200, an enforcement date 12300 of the diamond data to be published, an identification number 12400, and a change content 12,500. This example shows the disclosure history management table 1122 of the diagram editing terminal 1100b in charge of the vehicle operation work of FIG. The public information received in the processing flow of this description is 1262, 1263, the public version 12100 is 2 and 1261 is received before that, and the public version 12100 is 1.

  Returning to FIG. 2, the description of the processing is continued. After receiving the public information, all the diagram editing terminals 1100a to 1100c display a diagram on the display panel 320 of FIG.

  FIG. 13 is a diagram showing a diagram displayed on the screen of the diagram editing terminals 1100b and 1100c in FIG. 2 when receiving public information in the service diagram cooperation planning system according to the embodiment of the present invention. In the diagram 1310 displayed on the diagram editing terminal 1100b in FIG. 2, the diagram data for which the identification number and the change content are specified in the received public information is highlighted from other diagrams. In the example of FIG. 13, train diagram data 1311 and 1312 specified by the public information 1162 and 1164 of FIG. 11 are highlighted as bold broken lines.

  On the other hand, in the diagram 1320 displayed on the diagram editing terminal 1100c in FIG. 2, the train diagram data 1321 and 1322 designated by the public information 1161 and 1163 in FIG. 11 are highlighted as bold broken lines. The schedule edit data 1100b and 1100c in FIG. 2 have received the same schedule date N train schedule data, but since the train schedule received in the previous stage of this description is different, the public information indicating the change difference is different respectively. The highlighted points are different in the diagram.

  Returning to FIG. 2, the description of the processing is continued. The public history display unit 1116 in the diamond editing terminals 1100b and 1100c receives the input in the public version selection input space 351 of the public version selection panel 350 in FIG. 3, and the processing is executed by pressing the display button 352.

  FIG. 14 is an example of a vehicle operation diagram in which the process of the public history display unit 1116 is executed on the plan creation screen of the diagram editing terminal 1100b in the operation diagram cooperation planning system according to the embodiment of the present invention. By inputting a public version in the public version selection space 1451 and pressing a display button 1452, the diamond data for which the identification number and change contents are designated in the public information of an arbitrary version is highlighted. In the example of FIG. 14, the version “1, 2” is selected by the public version selection input unit 1451 as the highlight display target, and the display command button 1452 is pressed. As a result, the diagram data having the enforcement date and identification number specified by the records 1261 to 1263 in the disclosure history management table 1122 shown in FIG. 12 are highlighted with bold broken lines 1421 to 1423.

  To summarize the embodiment of the present invention described above, first, a diagram management server that transmits and receives diagram data between a plurality of diagram editing terminals 1100a to 1100c and these diagram editing terminals and has a master database 1231. 1200. The diagram editing terminal includes a plan creation unit (means) 1113 that accepts user input and creates / changes diagram data. Further, a plan transmission unit (means) 1114 is provided for transmitting to the diagram management server the creation / change of the diagram data, the disclosure period, and the disclosure range designation information designating the user to be published. On the other hand, the diagram management server transmits the diagram data of the specified publication period among the created / changed diagram data to the diagram editing terminal used by the user designated as the disclosure target. 1214 is provided. As a result, an operation diagram cooperation plan creation system is configured.

  Here, the plurality of diagram editing terminals 1100a to 1100c according to the preferred embodiment of the present invention described in detail are summarized as follows.

  First, (1) a screen display unit (means) 1111 that accepts user input and has a diagram display function of diagram data, and (2) a plan start unit that imports diagram data to be created from the diagram management server into its own terminal ( Means) 1112. Next, (3) making a change to the diagram data graphically displayed on the screen display unit (means), writing the result to the work database 1131 and writing the change history to the change history management table 1121 Part (means) 1113. Also, (4) a plan transmission unit (means) 1114 is provided for transmitting the specified diagram data in the work database and the change history for the diagram data managed in the change history management table to the diagram management server. . Further, (5) a status update unit (means) 1115 is provided for transmitting to the diagram management server the disclosure range specifying information specifying the disclosure period of the transmitted diagram data and the user to be disclosed. Also, (6) a public history display unit (means) 1116 for graphically displaying the diamond data changed by another user received from the diamond management server, and (7) a change history to the diamond data by the plan creation means. And a change history management table to be managed. Finally, (8) a public history management table 1122 for managing a change history for the diamond data executed by the other user for each timing received from the diamond management server is provided.

  On the other hand, the diagram management server 1200 according to the preferred embodiment of the present invention described in detail is summarized as follows.

  First, (1) plan update means for updating the schedule data of the master database 1231 and the plan update management table 1222 based on the diagram data received from the diagram editing terminal and the change history is provided. Next, (2) having a status update unit (means) 1211 for updating the status management table 1221 based on the disclosure range designation information received from the diagram editing terminal. Also, (3) Create difference information between the diagram data in the work database of the diagram editing terminal currently used by the user designated for disclosure and the same data in the master database from the disclosure range designation information and the plan update management table A public information creation unit (means) 1213 is provided. Further, (4) a public information transmission unit (means) 1214 for transmitting the data corresponding to the public period among the difference information created by the public information creation unit and the diagram data of the master database to the designated diagram editing terminal. Have. Finally, (5) a status management table 1221 for managing the disclosure range designation information received from the diagram editing terminal, and (6) the contents of the change history received from the diagram editing terminal and the transmission status of the change history to other terminals The plan update management table 1222 is managed.

  According to an embodiment of the present invention, a user who is in charge of each of the diagram planning tasks for a plurality of diagram editing terminals 1100a to 1100c is a completed diagram based on the intention of the user who executes the other diagram planning tasks. Among them, information that can be made public can be shared. Therefore, without waiting for the completion of the diamond for a long period of time by each user, a part of the completed and publicly available diamonds can be shared with each other and used for their own diamond creation work, improving the operation schedule creation efficiency be able to. As a result, it is possible to shorten the work period of the entire coordinated diamond creation work.

The schematic functional block diagram of the traffic diagram management system provided with the operation diagram cooperation plan system by one Embodiment of this invention. Explanatory drawing showing the flow of processing (thick line arrow) and the flow of information (thin line arrow) in the service diagram cooperation plan system by one embodiment of the present invention. The figure which shows the example of a plan creation screen by one Embodiment of this invention. The figure which shows the diagram data structure by one Embodiment of this invention. The example of the diagram according to one embodiment of the present invention. The data structure figure of the change history management table by one Embodiment of this invention. The data structure figure of the plan update management table by one Embodiment of this invention. The data structure figure of the status information by one Embodiment of this invention. The data structure figure of the status management table by one Embodiment of this invention. The processing flow figure of the public information creation part by one Embodiment of this invention. The data structure figure of the public information by one Embodiment of this invention. The data structure figure of the public history management table by one Embodiment of this invention. The diagram shown on the diagram edit terminal screen by one embodiment of the present invention. The example of the vehicle operation diagram which performed the process of the open history display part in the plan creation screen of the diagram edit terminal by one Embodiment of this invention.

Explanation of symbols

  1100a to 1100c ... diagram editing terminal, 1200 ... diagram management server, 1300 ... network, 1110 ... processing device, 1120 ... storage device, 1130 ... external storage device, 1140 ... display device, 1150 ... input device, 1111 ... screen display unit, 1112 ... Plan start part, 1113 ... Plan creation part, 1114 ... Plan transmission part, 1115 ... Status update part, 1116 ... Public history display part, 1121 ... Change history management table, 1122 ... Public history management table, 1131 ... Work database (Work DB), 1210 ... Processing device, 1220 ... Storage device, 1230 ... External storage device, 1211 ... Plan update unit, 1212 ... Status update unit, 1213 ... Public information creation unit, 1214 ... Public information transmission unit, 1221 ... Status management table, 1222 ... Planned update tube Table, 1231 ... the master database (master DB).

Claims (10)

  A diamond management server that transmits / receives diamond data to / from these diamond editing terminals and has a master database and the diamond editing terminal accepts user input and creates / changes diamond data. A plan transmitting means for performing, a plan transmitting means for transmitting creation / change to the diagram data, a disclosure period thereof, and a disclosure range designating information designating a user to be disclosed to the diagram management server; and the diagram management server In the operation, the system comprises public information transmitting means for transmitting diagram data of a specified publication period among created / changed diagram data to a diagram editing terminal used by a user designated as a publication target. Diamond cooperation plan creation system.   2. The diagram editing terminal according to claim 1, wherein the diagram editing terminal graphically displays diagram data, accepts and displays a user's input by the plan creation means, and diagram data of the disclosure period received from the diagram management server. An operation diagram cooperation plan creation system comprising display means for highlighting on the diagram.   In Claim 1, the said plan preparation means in the said diamond edit terminal is provided with the work database which writes the created / changed result, and the change history management table which writes a change history, The said plan transmission means includes the said Sending specific diagram data in the work database to the diagram management server, extracting an unsent history from the corresponding change history in the change history management table, and transmitting it to the diagram management server A feature schedule system creation system.   In Claim 1, the said plan transmission means creates the information which designated the range which can be disclosed in the enforcement date unit among the diagram data transmitted to the said diamond management server, and designated the user made public as the plan operation unit. An operation schedule linkage planning system characterized by   2. The plan transmission unit according to claim 1, wherein the schedule transmission means designates the disclosure target user in the business unit using the business name in the diagram data transmitted to the diagram management server, and designates a plurality of business operations at a time. This is a service schedule cooperation plan creation system.   The diamond editing terminal according to claim 1, further comprising: a change history management table for writing a change history; and a public history management table for recording the change history received from the diamond management server. An operation diagram characterized by recording a plan number, an execution date, an identification number, and information on a change content of a change history received from a diagram management server, and a count number of the change history received from the diagram management server. Collaboration planning system.   2. The diagram editing terminal according to claim 1, wherein the diagram editing terminal includes a screen display means for displaying a diagram of diagram data, a disclosure history management table for recording a change history received from the diagram management server, and a release version provided in the screen display means. An operation comprising: a selection unit; and means for highlighting diagram data indicated by a change history in the disclosure history management table having corresponding version information according to a user input from the disclosure version selection unit Diamond cooperation plan creation system.   2. The screen editing unit according to claim 1, wherein the plurality of diagram editing terminals accepts user input and has a screen display function for displaying diagram data of diagram data, and a plan start unit for importing plan data to be created from the diagram management server to the own terminal. A plan creation means for making a change to the diagram data graphically displayed on the screen display means and writing the result to the work database and writing the change history to the change history management table; and a designated diagram in the work database. Plan transmission means for transmitting the data and the change history for the diamond data managed in the change history management table to the diamond management server, and the disclosure range designation specifying the disclosure period of the transmitted diamond data and the user to be published Status update means for transmitting information to the diamond management server, and the diamond management server The public history display means for graphically displaying the diamond data changed by the other user received, the change history management table for managing the change history to the diamond data by the plan creation means, and the diagram executed by the other user An operation diagram cooperation plan creation system comprising a disclosure history management table for managing a change history for data at each timing received from the diagram management server.   2. The diamond management server according to claim 1, wherein the diagram management server receives the schedule data received from the diagram editing terminal, the schedule data of the master database based on the change history, the plan update means for updating the plan update management table, and the diamond editing terminal. Status update means for updating the status management table based on the published range designation information, and the work editing database of the diagram editing terminal used by the user designated as the publication target from the publication range designation information and the plan update management table Public information creation means for creating difference information between the diagram data in the master database and the diamond data in the master database, the difference information created by the public information creation unit, and the data corresponding to the publication period among the diagram data in the master database Public information transmission means for transmitting to a designated diamond editing terminal; A status management table for managing the disclosure range designation information received from the diagram editing terminal, and a plan update management table for managing the contents of the change history received from the diagram editing terminal and the transmission status of the change history to other terminals. A service schedule cooperation plan creation system characterized by that.   A plan creation step for creating / changing diagram data in response to user input at a plurality of diagram editing terminals, creation / change of the diagram data, a publication period, and a publication range designation designating a user to be published A plan transmission step for transmitting information to a diagram management server, and a diagram used by a user designated as a disclosure target of diagram data for a specified publication period among the diagram data created / changed in the diagram management server. An operation diagram cooperation plan creation method comprising: a public information transmission step for transmission to an editing terminal.

Images