JP5911694B2 - Train diagram editing system and train diagram editing method - Google Patents

Description

  Embodiments described herein relate generally to a train diagram editing system and a train diagram editing method.

  In general, a railway operator inputs data such as the arrival and departure times at each station of the train and the distance (km distance) between adjacent stations to a server such as a workstation and creates the diagram data in advance, and then operates this diagram data. Train operations are managed by displaying them on the screen as diagrams (hereinafter referred to as “diagrams”). For example, the diagram is represented in a graph form in which the distance from the first station (reference station) is plotted on the vertical axis, the time is plotted on the horizontal axis, and the names of traveling stations are arranged on the vertical axis in consideration of the distance between stations. And the operation of one train is expressed as a single line (train line) on the diagram.

  In addition, because the amount of timetable data is enormous in proportion to the number of trains operating and the number of departure and arrival stations, it is often created jointly by multiple users, and multiple edits are made to the server via the network. The work schedule is shared by building a train schedule editing system with terminals connected. In addition, by using the network, it is possible to share the diagram data on each terminal located in the company. In such a case, the entire diagram data is exclusively managed as one and consistency is maintained. Is maintained. For example, in the train diagram editing system, (1) a method for specifying other users who can share the created diagram data at the time of registration, and making it possible to refer to the work status for users other than the person in charge of creation, (2) For example, a method of temporarily lending a part of editing authority of the diagram data to other users and performing exclusive management is adopted.

JP 2007-62554 A JP 2006-27555 A

  As mentioned above, when multiple users (creators) share the creation of diagram data on the network, the data is modified or changed to maintain the consistency of the diagram data created by each However, it is necessary to work on a single diagram as a whole, but it has been difficult to perform such work on a terminal via a network in a conventional diagram editing system. Specifically, only the train number and operation number are added to the train lines displayed on the screen in the conventional system, and even if only the train lines are referenced, the department administrator is responsible for the department or person in charge of the creator. I couldn't figure out my name. Also, it was not a mechanism that can extract only the diamond data to be managed from a large amount of diamond data created by multiple creators on the network and compare them with each other. In particular, in recent years, there are cases where trains cross between companies (or across countries), and joint work in such a case is associated with greater difficulty.

  Therefore, in view of the above-described problems of the prior art, the present invention can efficiently create train streaks by sharing a plurality of train streaks, and easily edit and change the person in charge of train streaks created by general users. An object is to provide a diamond editing system and a diamond editing method that can be performed.

The train schedule editing system according to the present embodiment includes a diagram management server that centrally manages train line information including at least a train number, a train operation date, an operation sequence, an operation station, a departure time, and an arrival time, and a network connected to the diagram management server It is composed of a plurality of diamond editing terminals that are connected and edit train line information.

  The diamond management server includes a database unit and a data registration / update unit. The database section includes user setting information defining the relationship between the logged-in user by the diamond editing terminal and the authority level thereof, train line information, and authority setting information defining the relationship between the person in charge of editing having the authority to edit the train line information and the upper user. Remember. The data registration / update unit performs registration / update processing for the database unit in response to a request from the diagram editing terminal.

The diamond editing terminal includes a data editing unit, a train line acquisition unit, a train line display unit, and a train line coupling unit . When the logged-in user is defined as an upper user of the person in charge of creation in the authority setting information, the data editing unit edits the authority setting information and the train line information created by the person in charge of creation based on the input information of the upper user. Then, the registration / update processing by the edited data is requested to the data registration / update unit. The train line acquisition unit acquires train line information for which the login user has editing authority from the database unit. The train line display unit displays the acquired train line information. The train line combination unit newly creates two train line information related to the same train operation date created by a user whose authority level is lower than that of the logged-in user based on the comparison result of the operation sequence, operation station, departure time and arrival time. As a result, the data registration / update unit is requested to register / update the database unit based on the new train line information.

The figure which shows the example of whole structure of the train schedule edit system which concerns on Embodiment 1. FIG. The figure which shows the hardware structural example of the diagram management server and diagram editing terminal which are shown in FIG. The block diagram which shows the example of whole structure of the diagram management server and diagram editing terminal which are shown in FIG. The figure which shows the specific example of the memory content of the train stripe operation plan table shown in FIG. The figure which shows the specific example of the memory content of the authority setting information table shown in FIG. The figure which shows the specific example of the memory content of the user information table shown in FIG. The figure which shows the specific example of the train stripe registration / update screen displayed on the diagram edit terminal shown in FIG. The figure which shows the specific example of the train stripe display screen displayed on the diamond edit terminal shown in FIG. The figure explaining the data transition of the train line operation plan table before and behind the joint process of a train line. The figure explaining the data transition of the authority setting information table before and behind the joint process of a train line. The figure which shows the specific example of the train stripe coupling | bonding in the same department in the train stripe display screen displayed on the diagram edit terminal shown in FIG. The figure explaining the data transition of the train stripe operation plan table before and after the train stripe collective joining process in the train operation day unit. The figure explaining the data transition of the authority setting information table before and behind the collective joining process of the train stripes by train operation day unit. The sequence diagram which shows the specific example of the registration process of the train line in the diamond edit system shown in FIG. The flowchart which shows the specific example of the train stripe display process in the diamond edit system shown in FIG. The sequence diagram which shows the specific example of the person in charge person change process of the train line in the diamond edit system shown in FIG. The sequence diagram which shows the specific example of the train stripe coupling | bonding process in the diamond edit system shown in FIG. The sequence diagram which shows the specific example of the train stripe collective joining process per train operation day in the diamond edit system shown in FIG. The figure which shows the specific example of the authority setting information table in the train schedule edit system which concerns on Embodiment 2. FIG. The figure which shows the specific example of the user information table in the train schedule edit system which concerns on Embodiment 2. FIG. The figure explaining the data transition of the train line operation plan table before and behind the joint process of a train line. The figure explaining the data transition of the authority setting information table before and behind the joint process of a train line. The figure which shows the specific example of the train stripe coupling | bonding between different divisions in the train stripe display screen displayed on the diagram edit terminal shown in FIG. The figure which shows the specific example of the memory content of the authority setting information table in the train schedule edit system which concerns on Embodiment 3. FIG. The figure which shows the specific example of the memory content of the user information table in the train schedule edit system which concerns on Embodiment 3. FIG.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
<Embodiment 1>
FIG. 1 is a diagram illustrating an example of the overall configuration of a train schedule editing system according to the first embodiment. As shown in the figure, the train schedule editing system includes a schedule management server 1 that centrally manages train line information including at least a train number, a train operation date, an operation station, a departure time, and an arrival time. The train line is composed of a plurality of diamond editing terminals 3 that are connected via the network 2 and edit train line information that has been newly created or has been created. Information is stored and managed in the database of the diagram management server 1.

  FIG. 2 is a diagram illustrating a hardware configuration example of the diagram management server 1 and the diagram editing terminal 3 illustrated in FIG. 1. As shown in the figure, a computer applied to the diagram management server 1 and the diagram editing terminal 3 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, and an input / output. The interface 14 includes a system bus 15, an input device 16, a display device 17, an auxiliary storage device 18, and a communication device 19.

  The CPU 11 is a processing device that executes various arithmetic processes using programs, data, and the like stored in the ROM 12 and the RAM 13. The ROM 12 is a read-only storage device that stores basic programs and environment files for causing the computer to function. The RAM 13 is a storage device that stores a program executed by the CPU 11 and data necessary for execution of each program, and can be read and written at high speed. The input / output interface 14 is a device and a program that mediate connection between various hardware and the system bus 15. The system bus 15 is an information transmission path shared by the CPU 11, ROM 12, RAM 13 and input / output interface 14.

  The input / output interface 14 is connected with hardware such as an input device 16, a display device 17, an auxiliary storage device 18, and a communication device 19. The input device 16 is a device that processes input from a user, and is, for example, a keyboard or a mouse. The display device 17 is a device that displays a calculation result, a creation screen, and the like to the user, and is a CRT, a liquid crystal display, a plasma display, or the like, for example. The auxiliary storage device 18 is a large-capacity storage device that stores programs and data, and is, for example, a hard disk device.

  FIG. 3 is a block diagram showing an example of the overall configuration of the diagram management server 1 and the diagram editing terminal 3 shown in FIG. As shown in the figure, the diagram management server 1 includes a server side communication unit 101, a database unit 102, a user authentication unit 103, a data extraction unit 104, a data combination availability determination unit 105, a data registration / update unit 106, and a person in charge. A change message notification unit 107 is provided.

  The server-side communication unit 101 is an interface that performs data communication with a terminal-side communication unit 301 to be described later. The server-side communication unit 101 receives data transmitted from the diagram editing terminal 3 and receives a user authentication unit 103, a data extraction unit 104, and data As appropriate, the data is output to the combination availability determination unit 105, the data registration / update unit 106, and the person-in-charge change message notification unit 107, and the processing result in each unit is transmitted to the diagram editing terminal 3.

  The database unit 102 defines the relationship between the logged-in user who uses the diagram editing terminal 3 and the user information that defines the relationship between the authority level, the train line information, and the person in charge of editing that has the authority to edit the train line information and the higher-level user. It is a storage device that stores authority setting information. Here, each information is held in the train line operation plan table 102A, the authority setting information table 102B, and the user information table 102C.

  FIG. 4 is a diagram showing a specific example of the stored contents of the train line operation plan table 102A shown in FIG. Here, the train line operation plan table 102A is a train number for identifying a train line, a train operation date, an operation sequence, a stop (passing / stopping), an operating station (departure / departure station and passing station), and a line used at the operating station. The departure time and the arrival time are included in the data items.

  FIG. 5 is a diagram showing a specific example of the contents stored in the authority setting information table 102B shown in FIG. Here, the authority setting information table 102B includes the train number, the train operation date, the authority level, the person in charge of creation, and the department manager in the data items.

  FIG. 6 is a diagram showing a specific example of the stored contents of the user information table 102C shown in FIG. Here, the user information table 102C includes the user ID, authority level, department, and department administrator in the data items.

The authority levels held in the authority setting information table 102B and the user information table 102C of the diagram management server 1 are as follows.
[Authority 0]: This is an authority level representing a person in charge of creation who is a general user, and only train lines whose own user ID is set in the user column of the authority setting information table 102B can be edited.

[Authority 3]: This is an authority level representing a department administrator user, and all train lines having their own user ID set in the department administrator column of the authority setting information table 102B can be edited.

  The user authentication unit 103 is a program that performs user authentication by referring to the user information table 102C based on the user ID and input password of the user who uses the diagram editing terminal 3. The authority level of the login user acquired at the time of authentication is output to the data extraction unit 104 together with the user ID.

  The data extraction unit 104 extracts the train line information to be displayed on the diagram editing terminal 3 side from the train line operation plan table 102A according to the authority level of the login user acquired from the user authentication unit 103, and the server side communication unit A program to be transmitted to the diagram editing terminal 3 via 101.

When the train line information on the same train operation date to be combined is acquired from the diagram editing terminal 3 side, the data combination availability determination unit 105 includes an operation station and an operation included in the train line information related to the previous train and the subsequent train. This is a program for acquiring the order, departure time, and arrival time from the train line operation plan table 102A and determining whether or not the train line can be combined.
The data registration / update unit 106 is a program for registering / updating train line information in response to a registration / update request from the diagram editing terminal 3.

  The person-in-charge change message notifying unit 107 changes when the person in charge of creation in the train line information stored in the train line operation plan table 102A is changed by the registration / update process in the data registration / update unit 106. This is a program for notifying the person in charge change message to the diagram editing terminal 3 being used by the person in charge of creation and outputting new train line information in real time.

  The diagram editing terminal 3 includes a terminal-side communication unit 301, an input unit 302, a data editing unit 303, a train line acquisition unit 304, a train line display unit 305, a train line combination unit 306, and a train line batch combination unit 307. Yes.

  The terminal-side communication unit 301 is an interface that performs data communication with the server-side communication unit 101, and includes an input unit 302, a data editing unit 303, a train line acquisition unit 304, a train line display unit 305, and a train line connection unit 306. The data output from the train line batch coupling unit 307 is transmitted to the server side communication unit 101, and the data received from the server side communication unit 101 is appropriately output to each unit.

  The input unit 302 is an input interface for the terminal user to input information to the data editing unit 303, the train line acquisition unit 304, the train line combination unit 306, and the train line batch combination unit 307 on various input screens.

  The data editing unit 303 includes train line information including a train number, a train operation date, a service station, a departure time and an arrival time, a department, an authority level, and a train input from a higher-level user such as a department administrator on the train line registration / update screen. This is a program that transmits authority setting information including a user ID to the diagram management server 1 and requests registration / update of train line information and authority setting information stored in the database unit 102. The train line registration / update screen is displayed on condition that user authentication is completed between the diagram management server 1 and the diagram editing terminal 3. FIG. 7 is a diagram showing a specific example of a train line registration / update screen displayed on the diagram editing terminal 3 shown in FIG. The train operation station (departure / departure station) and time information input on this screen are held in the train line operation plan table 102A. The train line is uniquely identified by the combination of the train number and the train operation date, and the authority level, department, and user ID for each train line are held in the authority setting information table 102B. Corresponding to the registration information in the train line operation plan table 102A and the authority setting information table 102B, the user information table 102C also has a relationship between the user ID and the department administrator who is a higher-order user as user default information. Therefore, the person in charge of the creation and the department manager can be searched by using the train number as a key on the diagram management server 1 side.

  Further, the data editing unit 303 is based on the input information of the department manager (upper user) when the login user is defined as the department manager (upper user) of the person in charge of creation (general user) in the authority setting information. Each of the authority setting information and the train line information created by the person in charge of editing is edited, and the data registration / update unit 106 has a function of requesting registration / update processing with the edited data.

  The train line acquisition unit 304 requests the data extraction unit 104 of the diagram management server 1 to extract all the train line information that the login user has the editing authority, and the train line information stored in the database unit 102 and the train line information stored therein. It is a program that acquires the corresponding authority setting information. The train line display unit 305 is a program that creates and displays a train line display screen based on the train line information and authority setting information acquired by the train line acquisition unit 304. Specifically, the person in charge of creation for each train number in the authority setting information table 102B and the department for each user ID in the user information table 102C are held, so the user extracted from the authority setting information table 102B using the train number as a key Department information is extracted from the user information table 102C using the ID as a key. The information extracted on the diagram management server 1 side is transmitted to the diagram editing terminal 3 side, and the user ID of the person in charge of creation and the department to which the creator is assigned are displayed on a train line display screen.

  FIG. 8 is a diagram showing a specific example of a train stripe display screen displayed on the diagram editing terminal 3 shown in FIG. Here, the vertical axis represents the distance, the horizontal axis represents the time, and the operation station name is attached on the vertical axis according to the operation order. In addition, train line information is represented by an arrow line in the coordinates, and a train number, a user ID, and a department are written in the vicinity of the train line, and which user in which department is a train line creator. It is possible to grasp whether. In the same screen, the authority setting information held in the diagram management server 1 is also displayed on the screen of the diagram editing terminal 3 together with the train line information.

  The train line combination unit 306 is based on a comparison result of operation sequence, operation station, departure time, and arrival time based on two train line information related to the same train operation date created by a user whose authority level is lower than that of the logged-in user. This program is combined into new train streak information and requests registration / update of the database unit 102 from the data registration / update unit 106 based on the new train streak information. Before executing this combining process, a request for determining whether data can be combined is sent to the data combining determination unit 105 of the diagram management server 1, and when a combining possible notification is received from the data combining determination unit 105. Only executed. Specifically, when the department administrator is a login user, the arrival time at the same station is earlier than the departure time among the train lines of the same department displayed on the screen of the diagram editing terminal 3. Two self-created train lines can be combined as one train line.

  9 and 10 are diagrams for explaining data transitions in the train line operation plan table 102A and the authority setting information table 102B before and after the train line combination process. Here, new train streak information obtained by combining two records displayed in shaded areas is registered. In addition, although the two records before the combination are deleted, the train number 111A of the previous train is taken over as the train number of new train line information.

  In addition, the train number 112A of a back train and the train number designated separately by the user can also be used as a train number attached to new train line information. For example, when the person in charge of creating two train lines is the user A and the user B, respectively, the workload can be distributed by designating the user C. Also, if the train manager's user ID is used for the trainer number set in the person in charge of creation, it is possible to transfer the editing authority of train lines after joining to the department manager and restrict editing by general users. Become. That is, there is an advantage that the train line creation work can be efficiently carried out by sharing a plurality of general users, and finally the department manager can collectively manage the adjustment.

  Moreover, FIG. 11 is a figure which shows the specific example of the train stripe coupling | bonding in the same department in the train stripe display screen displayed on the diagram edit terminal 3 shown in FIG. Here, a state in which the screen display changes corresponding to the data transition in FIGS. 9 and 10 is shown.

  The train streak collective coupling unit 307 displays another train operation day having a train number related to the concatenation process executed by the train streak concatenating unit 306 when a collective coupling of train streaks is requested from the logged-in user on the train streak display screen. Are extracted and displayed as candidates, and the same combination process as the combination process executed by the train line combination unit 306 is executed for the train operation date selected by the user.

  FIGS. 12 and 13 are diagrams for explaining data transitions in the train line operation plan table 102A and the authority setting information table 102B before and after the train line batch combining process in units of train operation days. Here, the five records displayed in the shaded state are those of the train operation date (2011/07/07) designated by the user, but the train line (2 records) of the train number 112A related to the same date is the train number. It is combined with the 111A train streak and registered as new train streak information. That is, the same processing as the train line combination processing on the train operation date (2011/07/07) described in FIG. 9 to FIG. 10 is also performed when another train operation date (2011/07/02) is designated. Shows the case.

Hereinafter, the operation of the train diagram editing system configured as described above will be described in detail with reference to the drawings.
FIG. 14 is a sequence diagram showing a specific example of a train streak registration process in the diagram editing system shown in FIG.
In S1401, the diagram editing terminal 3 creates train line information for its own charge.
In S1402, the diagram editing terminal 3 transmits the train line information created in S1401 to the diagram management server 1.
In S1403, the diagram management server 1 receives train line information created by the diagram editing terminal 3 used by a train line creation person (general user).

In S1404, the diagram management server 1 extracts authority setting information from the train line information received in S1403, and stores it in the authority setting information table 102B.
In S1405, the diagram management server 1 stores the train line information received in S1403 in the train line operation plan table 102A.

FIG. 15 is a flowchart showing a specific example of the train line display process in the diagram editing system shown in FIG.
In S1501, the diagram management server 1 acquires the authority level of the login user at the time of the authentication process.

In S1502, the diagram management server 1 determines whether the authority level of the login user is the authority level of the department administrator. If it is determined that the department manager is selected, the process advances to step S1503. On the other hand, if it is determined that the user is not a department manager, the process proceeds to S1504.
In S1503, the diagram management server 1 acquires all train lines of its own department from the database unit 102 (train line operation plan table 102A) based on the authority level of the department manager.

  In S1504, the diagram management server 1 determines whether the authority level of the login user is the authority level of the general user. If it is determined that the user is a general user, the process advances to step S1505. On the other hand, if it is determined that the user is not a general user, the process advances to step S1507.

  In step S <b> 1505, the diagram management server 1 acquires train line information for its own charge from the database unit 102 based on the authority level of the general user.

In S1506, the diagram management server 1 transmits the train line information acquired in S1503 or S1505 to the diagram editing terminal 3, and the diagram editing terminal 3 receives this and displays it on the screen, and ends the process.
In S1507, the diagram management server 1 transmits a login error message to the diagram editing terminal 3, and the diagram editing terminal 3 receives the message and displays it on the screen, and ends the process.

FIG. 16 is a sequence diagram showing a specific example of the train line person-in-charge changing process in the diagram editing system shown in FIG.
In S1601, the diagram editing terminal 3 used by the department manager changes the person in charge of train line creation in the department on the screen.
In S1602, the diagram editing terminal 3 transmits a person-in-charge change request to the diagram management server 1 based on the person-in-charge information changed on the screen.

In S1603, the diagram management server 1 changes the person in charge of creating the corresponding train line based on the person-in-charge change request received.
In S1604, the diagram management server 1 uses the diagram editing terminal 3 to acquire user information of the logged-in user from the user information table 102C, and creates a user list.

In S <b> 1605, the diagram management server 1 collates the user list created in S <b> 1604 with the person in charge of train line creation related to the change in S <b> 1603, and detects a notification target person.
In S1606, the diagram management server 1 transmits a person-in-charge change message to the diagram editing terminal 3 used by the notification subject.
In S1607, the diagram editing terminal 3 used by the person to be notified displays the received person-in-charge change message on the screen.

  In this way, when the person in charge of train line creation is changed by the department administrator, the diagram management server 1 applies the change to the diagram editing terminal 3 used by the person in charge of train line creation related to the change. Information is shared in real time, and the information is displayed on the diagram editing terminal 3 on the screen.

FIG. 17 is a sequence diagram showing a specific example of the train line coupling process in the diagram editing system shown in FIG.
In S <b> 1701, the diagram editing terminal 3 arbitrarily selects two or more train lines to be combined based on a mouse operation or the like on the screen by the login user in the train line combination mode.

In S <b> 1702, the diagram editing terminal 3 transmits to the diagram management server 1 the train numbers and the train operation dates for the previous train and the subsequent train before the combination selected on the screen.
In S <b> 1703, the diagram management server 1 acquires, from the train line operation plan table 102 </ b> A, the train with the maximum operation order from the train station information of the previous train based on the received information.

  In S <b> 1704, the diagram management server 1 acquires, from the train line operation plan table 102 </ b> A, the train with the smallest operation order from the train station operation station information based on the received information.

  In S1705, the diagram management server 1 compares the operation station information acquired in S1703 and S1704 and determines whether or not train lines can be combined. If it is determined that train lines can be combined, the process advances to step S1708. On the other hand, if it is determined that train lines cannot be coupled, the process proceeds to S1706.

In step S1706, the diagram management server 1 transmits a connection impossible notification to the diagram editing terminal 3 used by the department administrator.
In S1707, when the diagram editing terminal 3 used by the department administrator receives the notification that the combination is not possible, this is displayed on a pop-up on the screen, prompts the department administrator to reselect the train stripe, and returns to S1701.

In S1708, the diagram management server 1 transmits a combination possible notification to the diagram editing terminal 3 used by the department administrator.
In S <b> 1709, the diagram editing terminal 3 transmits the new train line information after the combination and the train number designated for the train line information to the diagram management server 1.

  In S1710, the diagram management server 1 receives the train line information, and stores new train line information using the designated train number as a key in the train line operation plan table 102A. It is assumed that the train line information that is the basis of the new train line information is deleted from the train line operation plan table 102A in order to avoid data duplication.

  In S1711, the diagram management server 1 detects a notification target person from among the logged-in users, and transmits a person-in-charge change message to the diagram editing terminal 3 used by the notification target person. Examples of the person to be notified include a person in charge of creating each train line before joining, a person in charge of creating a train line after joining, and the like. The person to be notified can be arbitrarily set.

In S1712, the diagram management server 1 transmits the train line information after the change to the diagram editing terminal 3 used by the department manager and the person to be notified.
In S1713, the diagram editing terminal 3 used by the department manager displays the received train line information on the screen.
In S1714, the diagram editing terminal 3 used by the notification target person (general user) displays the received person-in-charge change message and the train line information after the change on the screen.

  As described above, at the time of login by the department manager, all the train lines related to the department supervised by the department manager are transmitted from the diamond management server 1 to the diagram editing terminal 3, and then the two specified by the diamond editing terminal 3 are used. Two train lines can be combined into one by receiving the train line at the diagram management server 1 and checking the availability of the combination process on the server side.

FIG. 18 is a sequence diagram showing a specific example of train stripe batch combining processing in units of train operating days in the diagram editing system shown in FIG.
In S <b> 1801, the diagram management server 1 acquires train line information related to the front train and the rear train before joining in the joining process executed immediately before. In addition, although the train line information before the combination is temporarily stored in the storage area of the diagram management server 1 or the diagram editing terminal 3, it may be stored in either.

In S1802, the diagram management server 1 refers to the train line operation plan table 102A, and acquires another train operation day having the train line information acquired in S1801.
In S <b> 1803, the diagram management server 1 transmits another train operation date acquired in S <b> 1802 to the diagram editing terminal 3.
In S1804, the diagram editing terminal 3 displays another train operation date information on the screen.

In S1805, the diagram editing terminal 3 transmits another train operation date designated by a mouse operation or the like from the list of train operation dates displayed on the screen by the department administrator to the diagram management server 1.
In S1806, the diagram management server 1 executes a batch combining process with the train number executed immediately before the received train operation date.

  In this way, after performing the combination process shown in FIG. 17 in the diagram management server 1, performing the combination process on the trains having the same train number on another train operation day, the workload of the diamond editing is reduced. Further reduction is possible.

Therefore, according to the train schedule editing system according to the present embodiment, the following effects are produced.
(1) In the authority setting information table 102B, by holding the authority level, the person in charge of creation (train line creation user name), and the department administrator (superior user) of train line creation, the editing authority for each user and department is retained. Management can be performed.
(2) The train line creation department administrator can confirm the user ID of the train stripe creation person (general user) held in the authority setting information table 102B, and can appropriately change the person in charge of creation as an upper user.
(3) The person in charge of creating the changed train line can quickly take over the work of editing the train line that has been changed in charge by receiving the person-in-charge change message on the diagram editing terminal 3 in real time.
(4) By displaying the authority level and the person in charge of creation held in the authority setting information table 102B on the screen, the department administrator can easily select and check the train lines in his department.
(5) By narrowing down the train line initially displayed based on the user ID of the user who has logged into the diagram management server 1 and its authority level, the person in charge of the creation (general user) can select the train line he / she is in charge of as a diagram editing terminal. 3 can be easily confirmed and edited. It should be noted that reference lines may be displayed even for train lines other than those in charge, and in this case, editing operations can be performed in accordance with train lines created by other users.
(6) Since the department manager can combine the train lines of his / her department, the train lines that have been divided into a plurality can be combined into a new train line.
(7) Since the joining process performed in (6) can be reflected on other train operating days under a predetermined condition, if multiple dates can be specified, The batch joining process can be performed continuously.

<Embodiment 2>
The diamond management system according to the present embodiment is different from the diamond management system according to the first embodiment only in the configuration of the database unit 102 of the diamond management server 1, and the processes in the diamond management server 1 and the diamond editing terminal 3 are the same. is there. Therefore, in the following, portions different from the first embodiment will be described in detail.

  19 and 20 are diagrams respectively showing specific examples of storage contents of the authority setting information table 102B and the user information table 102C in the train schedule editing system according to the second embodiment. Here, for the authority setting information table 102B shown in FIG. 5 and the user information table 102C shown in FIG. 6, the data items of the operator manager (user with [authority 6]) who is the upper user of the department manager Has been added. [Authority 6] is an authority level representing the operator administrator, and a user having this authority level has a train line whose user ID is set in the operator administrator column of the authority setting information table 102B. You can edit everything.

  FIG. 21 and FIG. 22 are diagrams for explaining data transitions in the train line operation plan table 102A and the authority setting information table 102B before and after the train line combination process, respectively. When the authority setting information table 102B in FIG. 22 is referenced using the train number 111A acquired from the record stored in the train line operation plan table 102A in FIG. 21 as a key, the user ID of the person in charge of creating the train line is the user A It can be seen that the user ID of the department administrator is user AA and the user ID of the business administrator is user AAA. Therefore, the business administrator of the user AAA can edit the train stripes created by all the users A and users AA in the company whose authority level is a general user regardless of the department. FIG. 21 shows that when the business manager designates the three records displayed in shades, they are sequentially combined by the same process as in the first embodiment and updated to two records with the same train number. Has been. Moreover, FIG. 23 is a figure which shows the specific example of the train stripe coupling | bonding between different departments in the train stripe display screen displayed on the diagram edit terminal 3 shown in FIG. Here, the screen display changes in response to the data transitions shown in FIGS. 21 and 22, and the new train streak is assigned the number (111A) designated by the business manager as the train number. The person in charge of the creation is also changed to only user A.

As described above, the train schedule editing system according to the present embodiment defines the operator manager as the upper user of the department manager in the database unit 102, and thus the following effects in addition to the effects of the first embodiment. Is played.
(1) When the logged-in user is an operator manager, train lines can be collectively managed across different departments in the same company.
(2) In the case of (1), even when the department manager is absent, the operator manager can arbitrarily edit the train stripes created by the company and change the person in charge of creation.

<Embodiment 3>
The diamond management system according to the present embodiment is different from the diamond management system according to the first embodiment only in the configuration of the database unit 102 of the diamond management server 1, and the processes in the diamond management server 1 and the diamond editing terminal 3 are the same. . Therefore, in the following, portions different from the first embodiment will be described in detail.

  24 and 25 are diagrams respectively showing specific examples of the contents stored in the authority setting information table 102B and the user information table 102C in the train schedule editing system according to the third embodiment. Here, data items of supervisors (users with [authority 9]) are added to the authority setting information table 102B shown in FIG. 19 and the user information table 102C shown in FIG. [Authority 9] is an authority level representing the highest user, and a user having this authority level edits all train lines in which his / her user ID is set in the supervisor column of the authority setting information table 102B. Shall be able to.

  Here, what kind of user is assumed as a supervisor will be described in detail by taking the railway situation in Europe as an example. In Europe, railway transportation is liberalized, and railway operators can operate trains freely on the railway infrastructure. In particular, train lines such as international trains that cross the European border require coordination among railway operators in multiple countries. However, if each operator creates train lines freely, there is a problem in operation. Is likely to occur. For example, train streaks that run between Country A and Country B are created by a railway operator in Country A on Country A and by a railway operator in Country B on Country B. However, there is a case where the diagram created in this way does not sufficiently adjust between trains, and there is a possibility that a waiting time occurs at a place where the tracks intersect and a large train delay occurs. Therefore, a user newly installed to centrally manage a plurality of train stripes created by a plurality of companies and straddling a country is the supervisor of this embodiment.

Thus, the train diagram editing system according to the present embodiment has the following effects in addition to the effects of the first embodiment by defining the supervisor in the database unit 102.
(1) Since the supervisor has the authority to edit train lines individually created by a plurality of operators, it is possible to efficiently carry in between different operators.
(2) As in the above example, when one train enters country B from country A, it is possible to manage the country A side diagram and the country B side diagram together. Further, even in a train crossing a railroad crossing, the supervisor can detect and correct a plan passing through the crossing at the same time in the plan through the diagram editing terminal 3.
(3) Since the supervisor has the authority to edit train lines created by multiple operators, in the case of the above example, the supervisor corrects the train lines of the country A side operator and the country B side operator. Train streaks can be corrected together. In addition, when the train line is revised by the supervisor and the time when the train arrives from country A is before the time when it leaves the country B, the train schedule will be edited. As in the case of the first embodiment and the second embodiment, the system can execute the train line coupling process based on the supervisor authority level.
(4) The supervisor setting information management table 102B and the user information table 102C of the diagram management server 1 hold supervisor information for managing train lines across the operators, so that even when the operator manager is absent. Supervisors can edit train streaks and change the person in charge.

  As mentioned above, although some embodiment of this invention was described, these embodiment is shown as an example and is not intending limiting the range of invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the spirit of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

DESCRIPTION OF SYMBOLS 1 ... Diamond management server 2 ... Network 3 ... Diamond edit terminal 11 ... CPU
12 ... ROM
13 ... RAM
DESCRIPTION OF SYMBOLS 14 ... Input / output interface 15 ... System bus 16 ... Input device 17 ... Display device 18 ... Auxiliary storage device 19 ... Communication device 101 ... Server side communication unit 102 ... Database unit 102A ... Train stripe operation plan table 102B ... Authority setting information table 102C ... User information table 103 ... User authentication part 104 ... Data extraction part 105 ... Data combination availability determination part 106 ... Data registration / update part 107 ... Person in charge change message notification part 301 ... Terminal side communication part 302 ... Input part 303 ... Data editing Unit 304 ... train streak acquisition unit 305 ... train streak display unit 306 ... train streak coupling unit 307 ... train streak collective coupling unit

Claims (3)

A schedule management server that centrally manages train line information including at least train number, train operation date, operation sequence, operation station, departure time and arrival time;
A plurality of diagram editing terminals that are network-connected to this diagram management server and edit the train line information;
Consists of
The diamond management server
User information that defines the relationship between the logged-in user by the diagram editing terminal and the authority level thereof, the train line information, and authority setting information that defines the relationship between the creator in charge of editing the train line information and the upper user The database part
A data registration / updating unit that performs registration / updating processing on the database unit in response to a request from the diamond editing terminal;
With
The diamond editing terminal
When the logged-in user is defined as the upper user of the person in charge of creation in the authority setting information, the authority setting information and the train line information created by the person in charge of creation based on input information of the upper user A data editing unit for requesting the registration / update process with the edited data to the data registration / update unit,
A train line acquisition unit that acquires the train line information that the login user has the editing authority from the database unit;
A train line display unit for displaying the acquired train line information;
The diagram editing terminal uses the train sequence information, the train station, the departure time, and the arrival information for the two train line information related to the same train operation date created by a user whose authority level is lower than that of the login user. Based on the time comparison result, the train line is combined as new train line information, and the data registration / update unit requests registration / update of the database unit based on the new train line information. A coupling part ;
The train diagram edit system that is characterized in that obtain Bei the. When the person in charge of creation in the train line information is changed by the registration / update process in the data registration / update unit, the diamond management server is used by the person in charge of creation related to the change. notifies personnel change message to the editing terminal, the new train train diagram edit system of claim 1, wherein further comprise a person change message notification unit the line information and outputs in real time. A schedule management server that centrally manages train line information including at least a train number, train operation date, operation sequence, operation station, departure time and arrival time, and a network connection to this diagram management server, and edits the train line information In a computer system comprising a plurality of diamond editing terminals,
The diagram management server defines the relationship between the logged-in user by the diagram editing terminal and the authority level, the user information that defines the relationship between the authority level, the train line information, and the person in charge of creation who has the authority to edit the train line information. Storing the authority setting information to be stored in the database;
When the logged-in user is defined as the higher-level user of the person in charge of creation in the right-setting information, the diagram editing terminal is controlled by the right-setting information and the person in charge of creation based on input information of the higher-order user. A data editing step of editing the created train line information and requesting the registration / update processing of the database with the edited data to the diagram management server,
A data registration / update step in which the diamond management server performs the registration / update process for the database in response to a request from the diamond editing terminal;
The train edit terminal, the train line acquisition step of acquiring the train line information that the login user has the editing authority from the database,
The train editing terminal displays the train line information obtained by the train line display step,
The diagram edit terminal, the authority level are two of the train line information the service order according to the same of the train service day to lower user than that of the logged-in user is created, the service station, the departure time and the arrival A train streak coupling step for combining the new train streak information based on the time comparison result and requesting the database management server to register / update the database based on the new train streak information ; ,
Train diagram edit how to characterized in that it has a.

Images