Personnel assignment planning device and personnel assignment planning system
Through personnel arrangement planning equipment and systems, combined with operational data and passenger participation evaluation, the problems of multitasking and flexible arrangement of employees in railway operations are solved, and efficient operation under the trend of unmanned ambition is achieved.
Patent Information
- Application Number
- JP2023084326
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-23
- Publication Date
- 2024-12-05
AI Technical Summary
The existing technology is difficult to achieve meticulous and flexible employee arrangements in railway operations, especially under the trend of labor savings, efficiency improvements and unmanned sites. Traditional employee allocation methods cannot meet the needs of multitasking and respond to employee absences.
Using personnel arrangement planning equipment and systems, through the first and second personnel arrangement planning sections, create employee allocation plans based on operational data, and evaluate the possibility of passenger participation, and generate a new layout plan including passenger participation.
Under the trend of labor saving and unmanned development, meticulous and flexible work execution has been achieved, reducing the number of personnel while ensuring smooth operation.
Smart Images

Figure 2024167977000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a personnel allocation planning device and a personnel allocation planning system. [Background technology]
[0002] Conventionally, an information processing device capable of creating a crew schedule for public transportation such as a railway has been proposed (for example, see Patent Document 1). Patent Document 1 discloses an information processing device capable of creating a work schedule (crew schedule) based on constraint conditions, and discloses a technique for tuning the priority and weight of soft constraint conditions in order to easily accommodate changes and additions to constraints on-site. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2022-45174 A Summary of the Invention [Problem to be solved by the invention]
[0004] Incidentally, currently, in the personnel allocation plan of railway organizations, personnel are allocated to each position, such as drivers, conductors, and station staff. Therefore, personnel allocation plans are drawn up with a surplus in the number of people for each position (task), for example, in order to be able to respond to passenger support and employee absences. However, in the future, for example, in railway organizations, it is predicted that the trend toward further labor saving, efficiency, and unmanned stations will continue. In this case, it is required that each employee be able to handle multiple tasks, so that the tasks can be executed in detail and flexibly with a small number of people. In addition, depending on the situation, it is quite conceivable to adopt a work style in which some of the tasks that employees have previously performed are requested to passengers. In order to meet such demands, it is necessary to build a new system for drawing up personnel allocation plans.
[0005] The present invention has been made to meet the above demands. An object of the present invention is to provide a personnel allocation planning device and a personnel allocation planning system that enable detailed and flexible execution of tasks with a small number of personnel, even if the trend toward further labor-saving, efficiency, and automation advances in public transportation such as railways. [Means for solving the problem]
[0006] In order to solve the above problems, the personnel allocation plan development device of the present invention includes a first personnel allocation planning unit and a second personnel allocation planning unit. The first personnel allocation planning unit acquires operation data of a public transportation facility and develops an employee allocation plan for a plurality of tasks required for the operation of the public transportation facility corresponding to the operation data. In addition, when it becomes necessary to change the employee allocation plan created by the first personnel allocation planning unit, the second personnel allocation planning unit evaluates the possibility of passengers' participation in tasks and creates a new allocation plan that includes passengers' participation in tasks based on the evaluation results.
[0007] In order to solve the above problem, a personnel allocation planning system of the present invention includes an operation data creation unit that creates operation data for a public transportation facility, and the personnel allocation planning device of the present invention. Effect of the Invention
[0008] According to the present invention configured as described above, even if the trend for further labor saving, efficiency, automation, etc. continues to accelerate in public transportation such as railways, it is possible to devise personnel deployment plans that enable tasks to be carried out in a detailed and flexible manner with a small number of personnel. [Brief description of the drawings]
[0009] [Figure 1] 1 is a functional block diagram of a personnel shift planning device and a personnel shift planning system according to an embodiment of the present invention. FIG. [Diagram 2] 1 is a diagram illustrating a hardware configuration of a personnel shift planning device according to an embodiment of the present invention. [Diagram 3]2 is a diagram showing an example of a data configuration of a train schedule stored in a train schedule storage unit of a personnel shift planning device according to an embodiment of the present invention; FIG. [Figure 4] FIG. 2 is a diagram showing an example of the configuration of data stored in a role database of the personnel shift planning device according to one embodiment of the present invention. [Diagram 5] FIG. 2 is a diagram showing an example of the configuration of data stored in a concurrent job possibility database of the personnel shift planning device according to one embodiment of the present invention. [Figure 6] 4 is a diagram showing an example of the configuration of data stored in an employee skill database of the personnel shift planning device according to one embodiment of the present invention; FIG. [Figure 7] FIG. 2 is a diagram showing an example of the configuration of data stored in a passenger assistance possibility database of a personnel shift planning device according to an embodiment of the present invention. [Figure 8] FIG. 2 is a diagram showing an example of the configuration of data stored in a facility database of the personnel shift planning device according to one embodiment of the present invention. [Figure 9] 2 is a diagram showing an example of the configuration of performance data (currently operating data) input to a personnel shift planning device according to an embodiment of the present invention. FIG. [Figure 10] FIG. 2 is a diagram showing an example of a display screen of passenger support application software installed on a passenger's mobile terminal in a personnel shift planning system according to one embodiment of the present invention. [Figure 11] 5 is a flowchart showing the procedure of personnel shift planning processing (optimization processing) performed by the personnel shift planning device according to one embodiment of the present invention. [Figure 12] 10 is a flowchart showing a procedure for updating a personnel shift plan taking into account passenger assistance possibility, which is performed by the personnel shift planning device according to one embodiment of the present invention. [Figure 13] 10 is a flowchart showing a procedure for updating a personnel shift plan that takes into account changes in the operation mode of each job, the procedure being performed in the personnel shift plan planning device according to one embodiment of the present invention. [Figure 14]1 is a diagram showing an example display (employee unit display) of a personnel shift plan created by a personnel shift planning device according to an embodiment of the present invention. FIG. [Figure 15] 1 is a diagram showing an example display (bar diagram display) of a personnel shift plan created by a personnel shift planning device according to an embodiment of the present invention. FIG. [Figure 16] 1 is a diagram showing an example display (train unit display) of a personnel shift plan at the time of planning created by the personnel shift planning device according to one embodiment of the present invention. FIG. [Figure 17] FIG. 11 is a diagram showing an example display (train unit display) of an updated personnel shift plan created by the personnel shift plan planning device according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, a personnel shift planning device and a personnel shift planning system according to an embodiment of the present invention that can be used in public transportation will be specifically described with reference to the drawings. Note that the following description will be given by taking a railway as an example of public transportation.
[0011] [Configuration of personnel shift planning system] Fig. 1 is a functional block diagram of a personnel shift planning device according to an embodiment of the present invention and a personnel shift planning system (personnel allocation planning system) including the personnel shift planning device. Note that Fig. 1 shows only functional units related to the creation (planning) process of a personnel shift plan.
[0012] 1, the personnel shift planning system 1 includes a personnel shift planning device 10 (personnel allocation planning device) and a train diagram planning device 20 (operation data creation unit). The personnel shift planning device 10 is connected to the train diagram planning device 20 by a communication line (wireless and / or wired) via a communication network 31.
[0013] The train schedule planning device 20 creates a train operation table (hereinafter referred to as a "train schedule") and transmits the created train schedule (operation data) to the personnel shift planning device 10 via the communication network 31. The specific configuration of the train schedule will be explained later with reference to the drawings. Then, based on the train schedule transmitted from the train schedule planning device 20, the personnel shift planning device 10 creates a proposal for the allocation of employees to various tasks for each train on the day of operation (hereinafter referred to as a "personnel shift plan proposal").
[0014] In addition, in the personnel shift planning system 1 of this embodiment, information on passengers who can assist with tasks such as assisting wheelchair passengers in getting on and off and security at stations is registered in advance. This registration is performed by the passengers themselves using passenger assistance application software. The personnel shift planning device 10 can be connected to the mobile terminal 30 of the registered passenger who can provide assistance by a communication line (wireless and / or wired) via the communication network 32. When requesting assistance with a task from a passenger, for example, an assistance request email or the like is sent from the personnel shift planning device 10 to the mobile terminal 30 of the passenger.
[0015] [Configuration of personnel shift planning device] As shown in FIG. 1, the personnel shift planning device 10 functionally comprises a personnel shift planning unit 11 (first personnel allocation planning unit), a personnel shift plan updating unit 12 (second personnel allocation planning unit), and a memory unit 13.
[0016] The personnel shift plan creation unit 11 creates a proposed personnel shift plan for the planning date based on various data stored in the storage unit 13. Furthermore, the personnel shift plan update unit 12 updates the proposed personnel shift plan (creates a new proposed personnel shift plan) when it becomes necessary to change the proposed personnel shift plan created by the personnel shift plan creation unit 11 on the day of operation of the proposed personnel shift plan. As shown in FIG. 1, the personnel shift plan update unit 12 has a passenger assistance evaluation unit 14 and an operation mode change evaluation unit 15, and the processing contents of these components will be described in detail later.
[0017] 1, the personnel shift plan updating unit 12 (passenger assistance evaluation unit 14 and operation mode change evaluation unit 15) is connected to the personnel shift plan planning unit 11 in terms of processing function. Furthermore, the personnel shift plan planning unit 11, the passenger assistance evaluation unit 14, and the operation mode change evaluation unit 15 are each connected to the storage unit 13 in terms of processing function.
[0018] (1) Overview of processing in the personnel shift planning department and personnel shift plan updating department The personnel shift planning unit 11 creates a personnel shift plan proposal using an optimization solver based on various data (e.g., role data described below) stored in the memory unit 13 prior to the day of operation (at the time of planning).
[0019] The "optimization solver" here refers to software (solver) used to obtain an optimal solution to a mathematical optimization problem, and various optimization solvers have been developed in the past according to the mathematical optimization problem. In this embodiment, as the optimization solver, for example, a solver for obtaining an optimal solution to a mathematical optimization problem called a mixed integer programming problem (MIP) (hereinafter referred to as an "MIP solver") is used. As this MIP solver, an existing MIP solver can be used. In addition, when using the optimization solver, constraint conditions that are conditions to be observed when obtaining a solution to the target mathematical optimization problem are created. In this embodiment, the personnel shift planning unit 11 creates constraint conditions using various data stored in the train schedule storage unit 13a, role database 13b, concurrent job availability database 13c, and employee skill database 13d in the storage unit 13, which will be described later.
[0020] Furthermore, when any changes occur to the personnel shift plan on the day of operation, the personnel shift planning unit 11 performs the process of creating the personnel shift plan again based on various data reflecting the changes, in response to a request from the passenger assistance evaluation unit 14 or the operation mode change evaluation unit 15. When creating (updating) the personnel shift plan, the personnel shift planning unit 11 uses the optimization solver in the same way as when planning.
[0021] In the process of creating (updating) a personnel shift plan using an optimization solver by the personnel shift planning unit 11, multiple solutions (personnel shift plans) may be obtained. In this case, for example, one of the multiple personnel shift plans is adopted by the operator of the personnel shift planning device 10 or a person in charge of train operation plans (hereinafter referred to as an "operational manager, etc."). Note that the details of the process of creating (updating) a personnel shift plan (process of creating a new personnel shift plan) by the personnel shift planning unit 11 will be described later with reference to the drawings.
[0022] The passenger assistance evaluation unit 14 evaluates whether or not passengers can provide assistance with some tasks on the day of operation, for example, when there is a new request for boarding and disembarking assistance for wheelchair passengers or kindergarten field trips, or when an employee is absent due to illness or the like. If passenger assistance is necessary and possible, the passenger assistance evaluation unit 14 creates a new personnel shift plan (new allocation plan) that includes the passenger as a person in charge of the tasks on that day. In other words, when it becomes necessary to change the task person on the day of operation, the passenger assistance evaluation unit 14 updates (creates) the personnel shift plan taking into account the passenger's ability to provide assistance.
[0023] In the process of creating a new personnel shift plan proposal by the passenger assistance evaluation unit 14, the passenger assistance evaluation unit 14 acquires various data reflecting the changes (e.g., role data, which will be described later) and requests the personnel shift plan formulation unit 11 to create a personnel shift plan proposal. Upon receiving the request, the personnel shift plan formulation unit 11 executes a personnel shift plan proposal creation process using an optimization solver based on the various data reflecting the changes, and outputs (returns) the result to the passenger assistance evaluation unit 14. The passenger assistance evaluation unit 14 then evaluates the possibility of passenger assistance for the updated personnel shift plan proposal. Note that the details of the personnel shift plan update process (the process of creating a new personnel shift plan proposal) by the passenger assistance evaluation unit 14 will be described later with reference to the drawings.
[0024] The operation mode change evaluation unit 15 evaluates whether or not it is possible to change the operation mode (manual / automatic / remote) of each task on the day of operation, in order to respond to, for example, a new request for boarding / disembarking assistance or an employee's absence. If the operation mode for some tasks is changeable, the operation mode change evaluation unit 15 creates a new personnel shift plan proposal (another new allocation plan) that reflects this. In other words, when it becomes necessary to change the task personnel on the day of operation, the operation mode change evaluation unit 15 updates (creates) the personnel shift plan proposal, taking into account the possibility of changing the operation mode of each task.
[0025] Specifically, the operation mode change evaluation unit 15 evaluates, for example, a case where the mode of driving work is changed between manual and automatic, and creates a new personnel shift plan proposal. Also, the operation mode change evaluation unit 15 evaluates, for example, a case where the mode of security work is changed between manual, automatic, and remote, and creates a new personnel shift plan proposal. Furthermore, the operation mode change evaluation unit 15 evaluates, for example, a case where the mode of ticket gate work is changed between manual, automatic, and remote, and creates a new personnel shift plan proposal.
[0026] In the process of creating a new personnel shift plan proposal by the operation mode change evaluation unit 15, the operation mode change evaluation unit 15 generates various data reflecting the changes (for example, role data, etc., described later) and requests the personnel shift plan formulation unit 11 to create a personnel shift plan proposal. The personnel shift plan formulation unit 11, which has received the request, executes a personnel shift plan proposal creation process using an optimization solver based on the various data reflecting the changes, and outputs (returns) the result to the operation mode change evaluation unit 15. Then, the operation mode change evaluation unit 15 performs an evaluation process on the updated personnel shift plan proposal based on the viewpoint of facilities, etc. Note that the details of the personnel shift plan update process (new personnel shift plan proposal creation process) by the operation mode change evaluation unit 15 will be described later with reference to the drawings.
[0027] As described above, both the updating process of the proposed personnel shift plan by the passenger assistance evaluation unit 14 and the updating process of the proposed personnel shift plan by the operation mode change evaluation unit 15 are processes performed to deal with the case where it becomes necessary to change the proposed personnel shift plan on the day of operation. In this case, it is sufficient to perform either the updating process of the proposed personnel shift plan by the passenger assistance evaluation unit 14 or the updating process of the proposed personnel shift plan by the operation mode change evaluation unit 15, but the priority order between the two processes is arbitrary. However, for example, from the viewpoint of performing all the tasks (roles described later) by employees as much as possible and not relying on passengers, the updating process of the proposed personnel shift plan by the operation mode change evaluation unit 15 is executed with priority. Then, when an appropriate solution (proposed personnel shift plan) cannot be obtained by the updating process of the proposed personnel shift plan by the operation mode change evaluation unit 15, the updating process of the proposed personnel shift plan by the passenger assistance evaluation unit 14 may be executed.
[0028] The various processing functions of the above-mentioned personnel shift planning unit 11, passenger assistance evaluation unit 14, and operation mode change evaluation unit 15 are controlled by software, i.e., a processor interpreting and executing a program for realizing each function. However, the present invention is not limited to this, and some or all of the above-mentioned various processing functions may be configured by hardware. In addition, while the present embodiment is configured to include both the passenger assistance evaluation unit 14 and the operation mode change evaluation unit 15, a configuration may be configured to include only one of the passenger assistance evaluation unit 14 and the operation mode change evaluation unit 15.
[0029] (2) Memory Configuration The memory unit 13 stores various data used in the creation (update) process of a personnel shift plan proposal by the personnel shift plan formulation unit 11, the passenger assistance evaluation unit 14, and the operation mode change evaluation unit 15. As shown in Fig. 1, the memory unit 13 has a train schedule memory unit 13a, a role database 13b, a concurrent job availability database 13c, an employee skill database 13d, a passenger assistance possibility database 13e, a facility database 13f, a performance data memory unit 13g, and a congestion information memory unit 13h.
[0030] 1, the train schedule storage unit 13a is connected to the train schedule planning device 20 via a communication network 31. The train schedule storage unit 13a stores a train schedule planned by the train schedule planning device 20. The train schedule stored in the train schedule storage unit 13a is a train schedule for a target date for planning a personnel shift plan.
[0031] The role database 13b stores data indicating the relationship between each of the stop stations and running sections (between stop stations) on the running route and the number of people required for each of the various tasks at each of the stop stations and running sections for each train. The tasks defined in the role database 13b include, for example, train operation monitoring tasks during automatic operation, train operation tasks during manual operation, ticket inspection tasks within stations, security tasks within stations and on trains, and tasks for assisting passengers in getting on and off. In the following, the tasks defined in the role database 13b, i.e., tasks required for train operation, are referred to as "roles."
[0032] The concurrent role database 13c stores information on concurrent roles that are defined for each train. The employee skill database 13d stores information on the skills (roles that can be assumed) of each employee. The passenger assistance possibility database 13e stores various information on the assistance possibility of each registered passenger who can provide work assistance. The equipment database 13f stores information on various facilities (e.g., platform doors, railroad crossings, elevated tracks, etc.) installed at each of the stops and running sections (between stops).
[0033] The actual data storage unit 13g stores information about train schedules in operation on the day (actual data described later). The congestion information storage unit 13h stores information indicating the current and past congestion conditions at the stops and running sections (between stops) of each train, which are specified in the train schedule, role data, and actual data described later.
[0034] The data stored in each of the above-mentioned role database 13b, concurrent job availability database 13c, employee skill database 13d, and passenger assistance possibility database 13e is updated as appropriate when a data change occurs. In addition, although not shown, information on train timetables during operation (performance data described below) and information indicating the current congestion status are appropriately transmitted to the personnel shift planning device 10 from, for example, a system that manages the operation status of trains on the day of operation. The specific configuration of the data stored in each database and each memory unit will be described later with reference to the drawings.
[0035] [Hardware configuration of the personnel shift planning device] In the personnel shift planning system 1 of this embodiment, the personnel shift planning device 10 can be configured with an arithmetic processing device such as a computer device having a calculation function and a communication function. Fig. 2 is a block diagram showing an example of a hardware configuration of a computer device 100 applicable as the personnel shift planning device 10.
[0036] The computer device 100 includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, and a RAM (Random Access Memory) 103, all connected to a bus line 108. The computer device 100 also includes a network I / F (Interface) 104, an operation unit 105, a display unit 106, and a non-volatile storage 107, all connected to the bus line 108. Although not shown in Fig. 2, the computer device 100 also includes various interfaces used when executing input / output processing of various data (various information) between the computer device 100 and external devices.
[0037] The CPU 101 reads out the program code of the software for realizing various processing functions of the personnel shift planning device 10 from the ROM 102 to the RAM 103 and executes it. At this time, variables and parameters generated during the calculation process are also temporarily written to the RAM 103.
[0038] The network I / F 104 is configured, for example, by a network interface card (NIC) or the like, and transmits and receives various data to and from each device connected via wireless communication.
[0039] The operation unit 105 is composed of, for example, keys and buttons, generates an operation signal according to the operation content input by an operator, and supplies the operation signal to the CPU 101. The display unit 106 is composed of, for example, a liquid crystal panel, and displays characters, images, and the like on a screen. The display unit 106 may also be composed of a touch panel, in which case the display unit 106 and the operation unit 105 are integrally configured.
[0040] The non-volatile storage 107 can be configured with, for example, a hard disk drive (HDD), a solid state drive (SSD), a flexible disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a non-volatile memory, etc. The non-volatile storage 107 stores an operating system (OS) and various parameters, as well as a program for causing the computer device 100 to function as the personnel shift planning device 10. Note that information (data) such as programs, tables, and files that realize the various functions of the personnel shift planning device 10 may be stored in a recording medium such as an IC card, an SD card, or a DVD, other than the ROM 102 or the non-volatile storage 107.
[0041] [Configuration of various data stored in the memory unit] Next, configuration examples of various data stored in the storage unit 13 of the personnel shift planning device 10 will be described with reference to Fig. 3 to Fig. 9. Although not shown, the storage unit 13 stores not only the following data but also various data used when calculating evaluation points of a personnel shift plan proposal in an update process of the personnel shift plan proposal (see Figs. 12 and 13 described later).
[0042] (1) Example of train timetable Fig. 3 is a diagram showing an example of the data configuration of a train schedule (table) stored in the train schedule storage unit 13a. As shown in Fig. 3, the train schedule specifies, for each scheduled train (train number), the train type, vehicle number, train number before the operation, train number after the operation, and arrival and departure times at each station. For example, for a train with train number "003" (hereinafter referred to as "train 003") scheduled to operate, the following information (data) is specified in the train schedule.
[0043] As shown in Fig. 3, the train type of train 003 (the "Type" column in the figure) is specified as a local train, and the car number (the "Car" column in the figure) is specified as the number "11." The "Car" column also specifies the operating mode, manual or automatic, and since train 003 is operated manually, the "Car" column of train 003 is specified with information indicating manual operation ("(Manual)" in the figure).
[0044] The train numbers before and after the operation of 003 train (the "Previous Operation" and "Next Operation" columns in the figure) are specified as train numbers "002" and "010", respectively. In other words, before the operation of this train, 003 train is operated as train 002, and after the operation of this train, it is operated as train 010. Note that in cases where there is no previous operation train, such as train 107 in Figure 3, and the train arrives at Station A directly from the depot, information to that effect ("Departing from depot" in the figure) is specified in the "Previous Operation" column.
[0045] The arrival and departure times of 003 train at Station A (the "Arrival at Station A" and "Departure at Station A" columns in the diagram) are specified as 8:00 and 8:01, respectively, and the arrival and departure times of 003 train at Station B (the "Arrival at Station B" and "Departure at Station B" columns in the diagram) are specified as 8:05 and 8:06, respectively. The arrival and departure times of 003 train at Station C (the "Arrival at Station C" and "Departure at Station C" columns in the diagram) are specified as 8:10 and 8:11, respectively. Additionally, the arrival and departure times of 003 train at Station D (the "Arrival at Station D" and "Departure from Station D" columns in the diagram) are specified as 8:15 and 8:17, respectively. In addition, when a train passes through stations B and C without stopping, such as train 107 (express) in Figure 3, information to that effect ("Passing" in the figure) is specified in the "Arrival at Station B" to "Departure from Station C" columns.
[0046] (2) Example of data structure stored in the role database 4A and 4B are diagrams showing examples of the configuration of role data (table) stored in the role database 13b. Role data is provided for each train specified in the train timetable, and here, an example of the configuration of role data (business data) set for train 003 is shown. In this embodiment, role data is set for each train (train number) for each type of operation mode (manual operation or automatic operation). FIG. 4A is an example of the configuration of role data when train 003 is operated manually, and FIG. 4B is an example of the configuration of role data when train 003 is operated automatically.
[0047] In each role data, the number of staff required for each role (task) is specified for each stop station and running section (between stop stations) on the running route of train 003, as shown in Figures 4A and 4B. Note that the role data is set in advance, for example, by the operation manager, taking into consideration information such as the number of passengers and passenger demographics estimated from information such as train type, running route, running time, and train intervals.
[0048] The role "operation monitoring" defined in Figures 4A and 4B is the task of monitoring automatic operation from within the train when it is automatic, and the role "driving" is the task of driving the train when it is manually operated (the task of a conventional driver). The role "ticket inspection" defined in the figures is the task of ticket inspection at a stopping station (the task of a conventional station staff member), and the role "security" is the task of security at a stopping station or within the train. Also, the role "boarding and alighting assistance" defined in the figures is the task of, for example, assisting wheelchair passengers with boarding and alighting, and assisting children with boarding and alighting during kindergarten field trips. Although not shown in the figures, other roles defined in the role data include, for example, "in-car ticket inspection," "station guidance," "in-car guidance," and "sales."
[0049] For example, when train 003 is operated manually, at station A, the number of staff required for each of the roles "ticket gate" and "security" is specified as "2," and the number of staff required for other roles is specified as "0," as shown in Fig. 4A. Also, for example, when train 003 is operated manually, the number of staff required for each of the roles "operation" and "security" is specified as "1," and the number of staff required for other roles is specified as "0," in the running section between stations A and B.
[0050] On the other hand, for example, when train 003 is operated automatically, at station A, the required number of personnel is specified as "2" for each of the roles "ticket gate" and "security", and the required number of personnel is specified as "0" for other roles, as shown in Fig. 4B. Also, for example, when train 003 is operated automatically, the required number of personnel is specified as "1" for each of the roles "operation monitoring" and "security", and the required number of personnel is specified as "0" for other roles, in the running section from station A to station B.
[0051] 4A and 4B, the number of people required for the roles of "driving monitor" and "driving" is set to "0" and "1", respectively, during manual driving, and the number of people required for the roles of "driving monitor" and "driving" is set to "1" and "0", respectively, during automatic driving. The number of people required for other roles is the same regardless of the driving mode.
[0052] (3) Example of data structure stored in the concurrent position database 5A and 5B are diagrams showing an example of the configuration of concurrent duty data (table) stored in the concurrent duty database 13c. The concurrent duty data is provided for each train specified in the train timetable, and here, an example of the configuration of concurrent duty data set for the 003 train is shown. In this embodiment, concurrent duty data is set for each train (train number) and for each type of operation mode (manual operation or automatic operation). FIG. 5A shows an example of the configuration of concurrent duty data when the 003 train is operated manually, and FIG. 5B shows an example of the configuration of concurrent duty data when the 003 train is operated automatically.
[0053] In each concurrent role data, the relationship between the concurrent roles is specified as shown in Figures 5A and 5B. In each concurrent role data, other roles that can be concurrently held for a given role are indicated with a "◯" mark, and other roles that cannot be concurrently held are indicated with a "X" mark.
[0054] For example, when train 003 is operated manually, as shown in Figure 5A, the relationships between roles that can be held in combination are as follows: The roles that can be held in combination with the role "operation monitoring" are security and boarding / alighting assistance, and the roles that cannot be held in combination with the role "operation monitoring" are driving and ticket gate. There are no roles that can be held in combination with the role "driving", and the role "driving" cannot be held in combination with all other roles. The roles that can be held in combination with the role "ticket gate" are security and boarding / alighting assistance, and the roles that cannot be held in combination with the role "ticket gate" are operation monitoring and driving. The roles that can be held in combination with the role "security" are operation monitoring, ticket gate, and boarding / alighting assistance, and the role that cannot be held in combination with the role "security" is driving. Additionally, the roles that can be held in combination with the role "boarding / alighting assistance" are operation monitoring, ticket gate, and security, and the role that cannot be held in combination with the role "boarding / alighting assistance" is driving.
[0055] On the other hand, the relationship between roles and whether they can be shared when train 003 is operated automatically is the same as that when train 003 is operated manually, as shown in Figure 5B.
[0056] In the example shown in FIG. 5A (data on whether or not concurrent roles can be performed during manual driving), information on the role "driving monitoring" is also specified, but the present invention is not limited to this. During manual driving, the role "driving monitoring" does not exist, so information on the role "driving monitoring" does not need to be specified in the concurrent role data shown in FIG. 5A, and the role "driving monitoring" may not be concurrently performed at all (marked with "x"). In the example shown in FIG. 5B (data on whether or not concurrent roles can be performed during automatic driving), information on the role "driving" is also specified, but the present invention is not limited to this. During automatic driving, the role "driving" does not exist, so information on the role "driving" does not need to be specified in the concurrent role data shown in FIG. 5B.
[0057] (4) Example of data structure stored in employee skills database Fig. 6 is a diagram showing an example of the configuration of employee skill data (table) stored in the employee skill database 13d. In the employee skill data, information on the roles that can be assumed by each employee is specified, as shown in Fig. 6. In the employee skill data, roles that a specific employee can assume are indicated with a "◯" mark, and roles that cannot be assumed are indicated with an "X" mark.
[0058] In the example shown in Fig. 6, the roles that "Employee 1" and "Employee 2" can assume are operation monitoring, driving, ticket gates, and boarding and alighting assistance, and the role that they cannot assume is security. In addition, the role that "Employee N" can assume is boarding and alighting assistance, and they cannot assume other roles.
[0059] (5) Example of data structure stored in the passenger assistance capability database Fig. 7 is a diagram showing an example of the configuration of passenger assistance possibility data (table) stored in passenger assistance possibility database 13e. In the passenger assistance possibility data, as shown in Fig. 7, information on the role that can be supported and the feasibility of performing the role is specified for each registered passenger who can be supported. In the example shown in Fig. 7, the roles that "Passenger A" can support are security and boarding / disembarking assistance, and the feasibility of performing the role "security" is 10%, and the feasibility of performing the role "boarding / disembarking assistance" is 60%.
[0060] In addition, the passenger assistance possibility data indicates the feasibility of a passenger's assistable role as a percentage, as shown in Fig. 7. For example, if the passenger assistance possibility data specifies a feasibility of 10% for a specific role, this indicates that the passenger can perform the specific role once for every 10 requests to perform the specific role. This feasibility value is set based on each passenger's past assistance performance for the specific role.
[0061] 7, the passenger assistance possibility data stores, for example, information on the section of use and past assistance implementation information (for example, information on the number of assistance implementations for each role and the date and time of assistance implementation) for each registered passenger. This information is used in the evaluation process of the updated personnel shift plan proposal created by the passenger assistance evaluation unit 14, the selection process of passengers to whom assistance is requested, and the like (see FIG. 12 described later).
[0062] (6) Example of data structure stored in the equipment database Fig. 8 is a diagram showing an example of the configuration of facility data (table) stored in the facility database 13f. As shown in Fig. 8, the facility data specifies whether or not various facilities are installed at each of the stop stations and running sections (between stop stations) on the train's running route. Note that the facility data shown here is for the stop stations and running sections on the train's running route specified by the train diagram shown in Fig. 3.
[0063] The equipment data shown in Fig. 8 specifies whether or not equipment such as "platform doors," "elevated tracks," and "railroad crossings" are installed. In addition, although not shown in Fig. 8, the equipment data also specifies "cameras (in stations, in trains)" and "remote equipment (ticket gates)" as equipment items.
[0064] In the facility data, if platform screen doors are installed, a "1" is specified in the "Platform Screen Doors" column, and if platform screen doors are not installed, a "0" is specified in the "Platform Screen Doors" column. In the facility data, if an elevated section is installed, a "1" is specified in the "Elevated" column, and if an elevated section is not installed, a "0" is specified in the "Elevated" column. In addition, in the facility data, the number of installed level crossings (0,1,2,3...) is specified in the "Crossing" column.
[0065] Furthermore, the facility data also specifies the quality of "visibility" for the stops and running sections. The quality of "visibility" is specified as a numerical value determined in advance by, for example, an operations manager, and a numerical value within the range of -2 to +2 is specified in the "visibility" column in the facility data. When "visibility" is good and very good, "1" and "2" are specified in the "visibility" column, respectively, and when "visibility" is poor and very poor, "-1" and "-2" are specified in the "visibility" column, respectively. When "visibility" is determined to be neither good nor poor, "0" is specified in the "visibility" column.
[0066] In the example shown in Fig. 8, at "Station A", platform screen doors and an elevated section are installed, there are no railroad crossings, and "visibility" is good, so "1" is specified in the "platform screen doors", "elevated section", and "visibility" columns, and "0" is specified in the "railroad crossing" column. Also, for example, in the running section from "Station A to Station B", an elevated section is installed, there are no railroad crossings, and "visibility" is good, so "1" is specified in the "elevated section" and "visibility" columns, and "0" is specified in the "platform screen doors" and "railroad crossing" columns.
[0067] The various information defined in the equipment data is used in the evaluation process of the updated personnel shift plan proposal created by the operation mode change evaluation unit 15 (see FIG. 13 described later).
[0068] (7) Example of data structure stored in the performance data storage unit Fig. 9 is a diagram showing an example of the data structure of the performance data (table) stored in the performance data storage unit 13g. The performance data is data showing the current train operation status, and has the same structure as the train schedule shown in Fig. 3. That is, the performance data specifies, for each train (train number) currently in operation, the train type, vehicle number, train number before the operation, train number after the operation, and arrival and departure times at each station.
[0069] The example shown in Fig. 9 shows an example of the data structure when the current train operation is performed according to the schedule. Therefore, the result data shown in Fig. 9 has the same structure as the train schedule shown in Fig. 3. However, for example, if a specific train is running behind schedule, the arrival and departure times of the specific train at each station stored in the result data will differ from those specified in the train schedule.
[0070] (8) Example of data structure stored in the congestion information storage unit Although an example of the configuration of the information indicating the current congestion status stored in the congestion information storage unit 13h is not illustrated, the information indicating the current congestion status is linked to the stop stations and running sections (between stop stations) of each train defined in the train schedule, role data, and performance data. The congestion information storage unit 13h stores not only information indicating the current congestion status of the stop stations and running sections of each train, but also information indicating past congestion status. This information indicating past congestion status is also linked to the stop stations and running sections of each train defined in the train schedule, role data, and performance data.
[0071] [Configuration of passenger mobile devices] The passenger's mobile terminal 30 has a calculation function and a communication function, and can be configured as a portable calculation processing device such as a smartphone, tablet, etc. Passenger support application software is installed on the passenger's mobile terminal 30, and various information is registered by the passenger's operation on the passenger support application started on the mobile terminal 30. Note that a support request from the personnel shift planning device 10 to the registered passenger's mobile terminal 30 is made using a communication tool such as email, SMS (Short Message Service), LINE (registered trademark), etc.
[0072] In addition, on the passenger assistance application, information such as the passenger's own past assistance record is displayed. FIG. 10 is a diagram showing a display mode of information such as the passenger's own past assistance record displayed on the display screen 30a of the passenger's mobile terminal 30. The display screen 30a of the mobile terminal 30 displays, for each type of role that can be used to assist passengers, the number of past assistances (the "cumulative" column in the figure), information such as the latest assistance execution date and execution station (the "latest" column in the figure). In addition, the display screen 30a of the mobile terminal 30 also displays information such as, for example, commuter pass information (section, etc.) and the number of points the passenger has acquired as a result of assistance execution ("25pt" in the figure). Although not shown in the figure, the various information of each registered passenger is stored in the storage unit 13.
[0073] [Process flow of personnel shift planning (optimization) process] Next, a description will be given of a processing flow of a personnel shift planning process (optimization process) using an optimization solver executed by the personnel shift planning unit 11 of the personnel shift planning device 10. FIG. 11 is a flowchart showing the procedure of the personnel shift planning process executed by the personnel shift planning unit 11.
[0074] The personnel shift planning process shown in Fig. 11 is executed, for example, not only when creating a personnel shift plan at the time of planning, but also when updating a personnel shift plan on the day of operation (optimization process in Figs. 12 and 13 described later). Note that the personnel shift planning process by the personnel shift planning unit 11 is controlled by the CPU 101 in Fig. 2.
[0075] First, the personnel shift planning unit 11 receives a train schedule (see FIG. 3) from the train schedule planning device 20 via the communication network 31 (S1). In addition, in the process of S1, the personnel shift planning unit 11 stores the received train schedule in the train schedule storage unit 13a.
[0076] Next, the personnel shift plan making unit 11 repeatedly executes the processes of S2 to S6 described below for each stop station (e.g., "Station A" in FIG. 4A) and each running section (e.g., "Station A to Station B" in FIG. 4A) of each train for which a personnel shift plan is to be made. For example, for train 003, the processes of S2 to S6 described below are repeatedly executed in the order of "Station A," "Station A to Station B," "Station B," "Station B to Station C," "Station C," and so on.
[0077] First, the personnel shift planning unit 11 converts the train schedule into constraint conditions (S2). In this process, the personnel shift planning unit 11 creates constraint conditions corresponding to each piece of information specified in the train schedule.
[0078] As an example of the process of converting to constraint conditions for train schedules, consider the case where the currently running process is performed for a specific station of a specific train (for example, train 003 in FIG. 3, etc.). In this case, in the process of S2, the personnel shift plan making unit 11 creates a constraint condition expressed by, for example, the following formula, using the arrival and departure times at specific stations (for example, stations A to D in FIG. 3, etc.) specified in the train schedule.
[0079]
number
[0080] The above constraint condition on arrival time specifies that the time at which a given train arrives at a given station must be after the departure time from the previous station plus the inter-station time (travel time). The first constraint condition on departure time specifies that the time at which a given train departs from a given station must be after the arrival time plus the stop time. The second constraint condition on departure time specifies that the time at which a given train departs from a given station must be after the departure time specified in the train timetable. Note that the first constraint condition on departure time also includes the case where a given train departs from a given station before the departure time specified in the train timetable, so the second constraint condition on departure time is provided to avoid including this case.
[0081] Next, the personnel shift planning unit 11 converts the role data into constraint conditions (S3). In this process, the personnel shift planning unit 11 creates constraint conditions corresponding to the relationship between each role defined in the role data and the required number of people.
[0082] Here, as an example of the process of converting role data into constraint conditions, for example, constraint conditions generated for the roles "security" and "operation monitoring" at a specific station will be described. In this case, in the process of S3, the personnel shift planning unit 11 creates constraint conditions expressed by the following formulas for the roles "security" and "operation monitoring".
[0083]
number
[0084] The "People" mentioned in the above constraints j,k " is a variable that indicates whether employee j takes on role k or not, and is a decision variable in the optimization solver. The index "j" is the employee identification number (j = 1 to N in Figure 6), and the index "k" indicates the type of role. If employee j takes on role k, j,k If =1 is set and the person is not in charge, j,k = 0 is set. In addition, the "required number of security guards" and the "required number of driving supervisors" in the above constraints are the required numbers of personnel specified for the roles "security" and "driving supervisor" in the role data (see Figs. 4A and 4B), respectively.
[0085] The constraint condition on the number of security guards stipulates that the number of employees in charge of the role "role" must be equal to or greater than the required number of security guards. The constraint condition on the number of driving monitors stipulates that the number of employees in charge of the role "driving monitor" must be equal to or greater than the required number of driving monitors. Although a detailed explanation is omitted, in the process of S3, constraint conditions are created in a similar manner for each of the other roles (driving, ticket gate, boarding and alighting assistance, etc.) stipulated in the role data shown in Figures 4A and 4B.
[0086] Next, the personnel shift planning unit 11 converts the concurrent role possibility data into a constraint condition (S4). In this process, the personnel shift planning unit 11 creates a constraint condition corresponding to the concurrent role possibility between the prescribed roles in the concurrent role possibility data.
[0087] Here, as an example of the process of converting concurrent job possibility data into constraint conditions, a constraint condition created for the concurrent job possibility of the roles "security" and "operational monitoring" at a specific station of a specific train (for example, train 003 in FIG. 3) will be described. As shown in FIG. 5A and FIG. 5B, the roles "security" and "operational monitoring" can be concurrently held, so in the process of S4, the personnel shift plan creation unit 11 creates a constraint condition for all employees regarding the concurrent job possibility of the roles "security" and "operational monitoring" represented by the following formula.
[0088]
number
[0089] If employee j has the roles of "security" and "driving monitoring" simultaneously, j,警備員役割 =1 and person j,運転監視員役割 = 1, and the sum of the two is 2, so the above constraint on the possibility of concurrent roles is satisfied. In addition, if employee j is in charge of only one of the roles "security" and "driving monitoring", j,警備員役割 and people j,運転監視員役割 Since one of the roles is 1 and the other is 0, the sum of the two is 1, and the above constraint on the possibility of concurrent roles is satisfied. Furthermore, if employee j is not in charge of both the roles "security" and "driving monitoring", j,警備員役割 and people j,運転監視員役割 Since both are 0, the sum of the two is 0, and the above constraint condition regarding the possibility of concurrent duties is satisfied. In other words, the above constraint condition regarding the possibility of concurrent duties specifies that there may be an employee who is in charge of (concurrently) both the roles of "security" and "driving monitoring", there may be an employee who is in charge of only one of the two roles, or there may be an employee who is in charge of neither role. Although a specific explanation is omitted, in the process of S4, constraint conditions corresponding to the possibility of concurrent duties between other roles (for example, between security and ticket gates, between driving monitoring and boarding and alighting assistance, etc.) specified in the concurrent duties data shown in Figures 5A and 5B are also created in the same way.
[0090] Next, the personnel shift planning unit 11 converts the employee skill data into constraint conditions (S5). In this process, the personnel shift planning unit 11 creates constraint conditions corresponding to the roles that each employee can and cannot handle, which are defined in the employee skill data.
[0091] Here, as an example of the process of converting employee skill data into constraint conditions, a constraint condition created for an employee j who can assume the role of "security" (marked with "◯" in FIG. 6) but cannot assume the role of "driving monitoring" (marked with "×" in FIG. 6) will be described. In this case, in the process of S5, the personnel shift planning unit 11 creates a constraint condition expressed by the following formula for the skills of employee j.
[0092]
number
[0093] Since employee j can play the role of “security guard”, under the above constraints on the security guard role, employee j may play the role of “security guard” ( j,警備員役割 =1), no need to be in charge (people j,警備員役割 On the other hand, since employee j cannot take on the role of “operation monitoring”, the above constraints on the operation supervisor role stipulate that employee j cannot take on the role of “operation monitoring” (person j,運転監視員役割 = 0) is defined. Although a detailed description is omitted, in the process of S5, for other employees defined in the employee skill data shown in FIG. 6B, constraint conditions corresponding to the skills of each employee (roles that can be assumed and roles that cannot be assumed) are similarly created.
[0094] Next, the personnel shift planning unit 11 uses an optimization solver to find a solution (decision variable "personnel") that satisfies the various constraints described above. j,k In this process, for example, an existing MIP solver can be used as the optimization solver. This process determines the number of employees in charge of each role (the number of employees for each role k) at the specified stop station or in the specified running section of the specified train currently being processed. j,k = 1) is determined as the solution. Note that this process may result in multiple solutions.
[0095] The above-mentioned processes from S2 to S6 are repeatedly performed for each stop station and each running section (between stop stations) of each train for which a personnel shift plan is to be created, thereby creating a personnel shift plan proposal. Note that, at this time, multiple personnel shift plans may be created.
[0096] Next, the personnel shift planning unit 11 outputs the created personnel shift plan (S7). After the process of S7, the personnel shift planning unit 11 ends the personnel shift planning process (optimization process).
[0097] The contents of the output process of the personnel shift plan proposal in the process of S7 change depending on the execution timing of the personnel shift plan formulation process (optimization process).
[0098] For example, when the above-mentioned personnel shift planning process is performed at the time of planning (first execution timing) before the day of operation, in the process of S7, the personnel shift planning unit 11 can output the created personnel shift plan proposal to the display unit (display unit 106 in FIG. 2, etc.) of the personnel shift planning device 10. As a result, the personnel shift plan proposal is displayed on the display unit. In this case, for example, when there are multiple personnel shift plans obtained, the operation manager or the like can check the contents of the multiple displayed personnel shift plans and select one personnel shift plan proposal from among them. The display mode of the personnel shift plan proposal will be described later with reference to the drawings.
[0099] As described later, the above-mentioned personnel shift planning process (optimization process) may be called and executed in the personnel shift plan update process shown in FIG. 12 or FIG. 13 described later. In this case, however, first, immediately after starting the personnel shift plan update process, the above-mentioned personnel shift planning process (optimization process) is executed based on the updated role data and / or the updated employee skill data (S12, S22 described later: second execution timing). Then, if a solution is not obtained by the personnel shift planning process, the personnel shift planning process (optimization process) is executed again based on role data that takes into account the passenger support possibility or the possibility of changing the role operation mode (S15, S25 described later: third execution timing).
[0100] When the personnel shift planning process (optimization process) is performed at the second execution timing, in the process of S7, the personnel shift planning unit 11 first sets the difference amount between the personnel shift plan before the update (at the time of planning) and the personnel shift plan after the update as an objective function. Next, the personnel shift planning unit 11 sets the difference amount between the personnel shift plan before the update and the personnel shift plan after the update as an objective function. j,k " has been changed, the difference amount is added by 1, and the one with the smallest total difference amount is determined as the solution (updated personnel shift plan proposal). At this time, multiple updated personnel shift plans may be determined. Then, in the process of S7, the personnel shift plan formulation unit 11 outputs the execution result of the optimization process to the passenger assistance evaluation unit 14 or the operation mode change evaluation unit 15.
[0101] On the other hand, when the personnel shift planning process (optimization process) is performed at the third execution timing, in the processing of S7, the personnel shift planning unit 11 outputs an updated personnel shift plan proposal that takes into account the possibility of passenger assistance or the possibility of changing the operation mode of the role to the passenger assistance evaluation unit 14 or the operation mode change evaluation unit 15.
[0102] [Process flow for updating personnel shift plan proposal considering passenger assistance possibility] Next, a process flow of updating a proposed personnel shift plan considering passenger assistance possibility, which is executed by the passenger assistance evaluation unit 14 of the personnel shift planning device 10, will be described. Fig. 12 is a flowchart showing the procedure of updating a proposed personnel shift plan executed by the passenger assistance evaluation unit 14. Note that the updating process of the proposed personnel shift plan by the passenger assistance evaluation unit 14 is controlled by the CPU 101 in Fig. 2. Also, the updating process of the proposed personnel shift plan considering passenger assistance possibility shown in Fig. 12 is executed when it becomes necessary to change the proposed personnel shift plan on the day of operation.
[0103] First, the passenger assistance evaluation unit 14 acquires the updated role data and / or employee skill data for the day, and also acquires a personnel shift plan proposal for the day (at the time of planning) (S11).
[0104] On the day of operation, for example, when a new role of "boarding / alighting assistance" becomes necessary at a specific station, the role data for that day (see Figs. 4A and 4B) is updated by, for example, the operation manager or the like. Specifically, the operation manager or the like creates role data in which a required number of people, such as "1", is specified for the role of "boarding / alighting assistance" at a specific station in the role data for that day, and the updated role data is stored in the role database 13b. In this case, in the process of S11, the passenger assistance evaluation unit 14 acquires the updated role data for that day stored in the role database 13b.
[0105] Furthermore, if an employee (such as a driver or station staff) is absent on the day of operation, the employee skill data (see FIG. 6) is updated, for example, by the operations manager. Specifically, in the employee skill data, all roles of the absent employee are marked as unavailable (with an "X" mark), and the updated employee skill data is stored in the employee skill database 13d. In this case, in the process of S11, the passenger assistance evaluation unit 14 acquires the updated employee skill data stored in the employee skill database 13d.
[0106] Furthermore, on the day of operation, for example, if a new role of "boarding and disembarking assistance" becomes necessary at a specific station and an employee is absent, in processing S11, the passenger assistance evaluation unit 14 acquires both the updated role data for that day and the updated employee skill data.
[0107] In addition, a personnel shift plan for the day, which is determined (selected) in advance by, for example, an operation manager, is input to the personnel shift planning device 10 before the day of operation and stored in the storage unit 13. Therefore, in the process of S11, the passenger assistance evaluation unit 14 acquires the personnel shift plan for the day stored in advance in the storage unit 13.
[0108] Next, the passenger assistance evaluation unit 14 executes an optimization process using the difference between the personnel shift plan of the day (at the time of planning) acquired in the process of S11 and the updated personnel shift plan as an objective function (S12). In the process of S12, the passenger assistance evaluation unit 14 calls and executes a personnel shift plan formulation process (optimization process) using an optimization solver by the personnel shift plan formulation unit 11 described in FIG. 11. At this time, in the process of S7 in FIG. 11 described above, a personnel shift plan that minimizes the difference between the personnel shift plan of the day and the updated personnel shift plan is obtained as a solution (updated personnel shift plan). Then, in the process of S7 in FIG. 11 described above, the execution result of the optimization process is output from the personnel shift plan formulation unit 11 to the passenger assistance evaluation unit 14.
[0109] Next, the passenger assistance evaluation unit 14 determines whether or not a solution (an updated personnel shift plan) has been obtained in the optimization process of S12 (S13).
[0110] In S13, when the passenger assistance evaluation unit 14 determines that a solution has been obtained (when S13 is judged as YES), the passenger assistance evaluation unit 14 ends the process of updating the proposed personnel shift plan. Note that a solution (an updated personnel shift plan) is obtained in the optimization process of S12 when a new personnel shift plan is obtained without assistance from passengers. Then, when S13 is judged as YES, the updated personnel shift plan obtained in the optimization process of S12 is output to and displayed on the display unit (display unit 106 in FIG. 2, etc.) of the personnel shift planning device 10. Note that, when there are multiple updated personnel shift plans obtained in the optimization process of S12, one updated personnel shift plan is determined from among them by, for example, the operation manager, etc.
[0111] On the other hand, if the passenger assistance evaluation unit 14 determines in S13 that a solution has not been obtained (if S13 is judged as NO), the passenger assistance evaluation unit 14 repeatedly executes the processes of S14 to S16 described below for each role in which passengers can participate. Note that the roles in which passengers can participate include, for example, boarding and disembarking assistance, security, station guidance, etc.
[0112] If the result of S13 is NO, the passenger assistance evaluation unit 14 first creates role data by deleting the specific roles (e.g., boarding and disembarking assistance) in which the passenger currently being processed can participate from the updated role data for the day obtained by the processing of S11 (S14).
[0113] Next, the passenger assistance evaluation unit 14 executes an optimization process using the role data from which the predetermined role in which the passenger can participate, currently being the processing target, has been deleted (S15). In the process of S15, the passenger assistance evaluation unit 14 calls and executes a personnel shift plan formulation process (optimization process) using the optimization solver by the personnel shift plan formulation unit 11 described in FIG. 11. That is, in the optimization process of S15, it is assumed that the passenger will take on the predetermined role in which the passenger can participate, currently being the processing target, and a personnel shift plan formulation that allows employees to take on roles other than the predetermined role is obtained as a solution. Note that the optimization process of S15 may obtain multiple solutions (updated personnel shift plan proposals).
[0114] Next, the passenger assistance evaluation unit 14 calculates an evaluation score for the solution (the updated personnel shift plan proposal) obtained in the optimization process of S15 (S16). In this process, the passenger assistance evaluation unit 14 calculates an evaluation score according to information such as the number of users (the number of commuter pass holders, etc.), the number of people registered in the passenger assistance application, the number of people who have participated in passenger assistance in the past, and the time period in the station or travel section where the passenger is assisted. These pieces of information are acquired by referring to, for example, the performance data showing the current operation status, the number of passengers registered in the passenger assistance possibility data, and various information stored in the passenger assistance possibility data (the number of assistance implementations for each passenger's role, the date and time of assistance implementation, etc.). Note that information regarding the number of users (the number of commuter pass holders, etc.) in the station or travel section where the passenger is assisted is stored in the storage unit 13, although not shown in the figure.
[0115] In the calculation process of the evaluation points in S16, as shown in Fig. 12, for example, if the number of commuter pass holders at the stop station or running section (between stop stations) supported by the passenger is 2000 or more and less than 4000, the evaluation point is added by 1 point. For example, if the number of commuter pass holders is 4000 or more and less than 80000, the evaluation point is added by 2 points, and if the number of commuter pass holders is 8000 or more and less than 16000, the evaluation point is added by 3 points. Also, for example, if the number of commuter pass holders is 16000 or more and less than 320000, the evaluation point is added by 4 points, and if the number of commuter pass holders is 32000 or more, the evaluation point is added by 5 points.
[0116] In addition, in the evaluation point calculation process of S16, if the number of registered users in the passenger assistance application at the stop station or running section (between stop stations) supported by the passenger is, for example, 200 or more and less than 400, the evaluation point is increased by 1 point. For example, if the number of registered users is 400 or more and less than 800, the evaluation point is increased by 2 points, and if the number of registered users is 800 or more and less than 1600, the evaluation point is increased by 3 points. Also, for example, if the number of registered users is 1600 or more and less than 3200, the evaluation point is increased by 4 points, and if the number of registered users is 3200 or more, the evaluation point is increased by 5 points.
[0117] In addition, in the evaluation score calculation process of S16, if the number of participants in past passenger assistance at the stop station or running section (between stops) assisted by the passenger is, for example, 20 or more and less than 40, the evaluation score is increased by 1 point, and if the number of participants is 40 or more and less than 80, the evaluation score is increased by 2 points. Also, for example, if the number of participants is 80 or more and less than 160, the evaluation score is increased by 3 points, if the number of participants is 160 or more and less than 320, the evaluation score is increased by 4 points, and if the number of participants is 320 or more, the evaluation score is increased by 5 points.
[0118] Furthermore, in the process of calculating the evaluation score in S16, if the time period during which the passenger is assisted at a stop station or a running section (between stops) is during rush hour, the evaluation score is deducted by 5 points. In other words, the greater the number of users, the greater the number of registered users, and the greater the number of passengers who can be assisted, the higher the evaluation score will be, and the lower the evaluation score will be during busy times. When such an evaluation is performed, it becomes possible to select a personnel shift plan suitable for the passenger assistance performance and the current operation situation.
[0119] Then, after repeating the above-mentioned processes of S14 to S16 for all roles in which passengers can participate, the passenger assistance evaluation unit 14 selects a passenger participation personnel shift plan proposal from the multiple solutions (updated personnel shift plan proposals) obtained by the processes of S14 to S16 (S17). In this process, the passenger assistance evaluation unit 14 selects an updated personnel shift plan proposal (hereinafter referred to as a "passenger participation plan") based on the evaluation score of each solution (updated personnel shift plan proposal). Specifically, the passenger assistance evaluation unit 14 selects a predetermined number of passenger participation plans including the passenger participation plan with the highest evaluation score.
[0120] Next, the passenger assistance evaluation unit 14 selects a passenger to whom assistance is requested (S18). In this process, the passenger assistance evaluation unit 14 evaluates each passenger based on the passenger's work participation record information and the passenger's current location information, and selects a passenger to whom assistance is requested based on the evaluation result. The passenger's work participation record information used in the process of S18 includes information on each registered passenger, such as the past performance time of the requested role and the past number of times the requested role has been performed. In the process of S18, the passenger assistance evaluation unit 14 refers to the passenger assistance possibility data to acquire various information on each registered passenger, such as the past performance time of the requested role and the past number of times the requested role has been performed. In the process of S18, the passenger assistance evaluation unit 14 also acquires the location information of the passenger's mobile terminal 30 as the passenger's current location information.
[0121] In the passenger evaluation process in S18, as shown in FIG. 12, for example, if the requested role was performed within six months in the past, one evaluation point is added. For example, if the requested role was performed once in the past, one evaluation point is added, if it was performed twice, two evaluation points are added, and if it was performed three times, three evaluation points are added. Also, for example, if the passenger's current location is within 500 m from the support location (station), three evaluation points are added. Furthermore, for example, if the passenger's arrival time at the support location (station) is later than the time of the required support, the passenger is excluded as the condition is not met. The passenger's arrival time at the support location (station) is predicted from the passenger's current location and past performance information (support implementation time).
[0122] Then, in the process of S18, the passenger assistance evaluation unit 14 requests assistance from a predetermined number of passengers with high evaluation points based on the result of the evaluation process. This assistance request is made by automatically sending, for example, an assistance request email from the passenger assistance evaluation unit 14 to the mobile terminal 30 of the passenger.
[0123] As described above, in the process of selecting passengers to whom assistance is requested (S18), various information about each passenger, such as the time when the role was performed in the past, the number of times the role was performed in the past, and the current location information of the passenger are used as evaluation information regarding the possibility of the passenger participating in the role. By performing such evaluation, passengers who are likely to provide assistance can be reliably selected.
[0124] After the process of S18, the passenger assistance evaluation unit 14 ends the above-mentioned process of updating the personnel shift plan. If there are multiple passenger participation plans selected in the above-mentioned process of updating the personnel shift plan by the passenger assistance evaluation unit 14 and for which the passengers have accepted the support, one passenger participation plan is selected from among them by, for example, the operation manager. Then, the passenger participation plan (updated personnel shift plan) selected by the passenger assistance evaluation unit 14 is output to and displayed on the display unit (display unit 106 in FIG. 2, etc.) of the personnel shift planning device 10. The display manner of the passenger participation plan will be described later with reference to the drawings.
[0125] [Process flow for updating personnel shift plan proposals taking into account changes in role operation modes] Next, a process flow of updating a proposed personnel shift plan considering a change in the operation mode of a role, which is executed by the operation mode change evaluation unit 15 of the personnel shift plan planning device 10, will be described. Fig. 13 is a flowchart showing the procedure of updating a proposed personnel shift plan executed by the operation mode change evaluation unit 15. Note that the updating process of the proposed personnel shift plan by the operation mode change evaluation unit 15 is controlled by the CPU 101 in Fig. 2. Also, the updating process of the proposed personnel shift plan considering a change in the operation mode of a role shown in Fig. 13 is executed when it becomes necessary to change the proposed personnel shift plan on the day of operation.
[0126] First, the operation mode change evaluation unit 15 acquires the updated role data and / or employee skill data for the day, and also acquires the personnel shift plan for the day (at the time of planning) (S21). The process of S21 by the operation mode change evaluation unit 15 is performed in the same manner as the process of S11 by the passenger assistance evaluation unit 14 described above.
[0127] Next, the operation mode change evaluation unit 15 executes an optimization process using the difference between the personnel shift plan of the day (at the time of planning) acquired in the process of S21 and the updated personnel shift plan as an objective function (S22). In the process of S22, the operation mode change evaluation unit 15 calls and executes a personnel shift plan formulation process (optimization process) using an optimization solver by the personnel shift plan formulation unit 11 described in FIG. 11. At this time, in the process of S7 in FIG. 11 described above, a personnel shift plan that minimizes the difference between the personnel shift plan of the day and the updated personnel shift plan is obtained as a solution (updated personnel shift plan). Then, in the process of S7 in FIG. 11 described above, the execution result of the optimization process is output from the personnel shift plan formulation unit 11 to the operation mode change evaluation unit 15.
[0128] Next, the operation mode change evaluation unit 15 judges whether or not a solution (an updated personnel shift plan) has been obtained in the optimization process of S22 (S23).
[0129] In S23, when the operation mode change evaluation unit 15 determines that a solution has been obtained (when S23 is judged as YES), the operation mode change evaluation unit 15 ends the update process of the personnel shift plan proposal. Note that a solution (an updated personnel shift plan proposal) is obtained in the optimization process of S22 when a personnel shift plan proposal is obtained without changing the operation mode of each role (task). Then, when S23 is judged as YES, the updated personnel shift plan proposal obtained in the optimization process of S22 is output to and displayed on the display unit (display unit 106 in FIG. 2, etc.) of the personnel shift planning device 10. Note that, when there are multiple updated personnel shift plans obtained in the optimization process of S22, one operation mode change proposal is determined from among them by, for example, the operations manager, etc.
[0130] On the other hand, if the operation mode change evaluation unit 15 determines in S23 that a solution has not been obtained (if S23 is judged as NO), the operation mode change evaluation unit 15 repeatedly executes the processes of S24 to S26 described below for each role defined in the role data (Figures 4A and 4B).
[0131] If the result of S23 is NO, the operation mode change evaluation unit 15 first creates role data by changing the operation mode of the role currently being processed (e.g., driving, security, ticket gate, etc.) from the updated role data for the day obtained by the processing of S21 (S24).
[0132] For example, if the role currently being processed is driving and its operation mode is to be changed from "manual" to "automatic", the role data to be used in the process of S24 is changed from role data for manual driving (FIG. 4A) to role data for automatic driving (FIG. 4B). On the other hand, if the role currently being processed is driving and its operation mode is to be changed from "automatic" to "manual", the role data to be used in the process of S24 is changed from role data for automatic driving (FIG. 4B) to role data for manual driving (FIG. 4A).
[0133] Also, for example, if the role currently being processed is security and its operation mode is to be changed from "manual" to "remote", in the processing of S24, the required number of personnel specified for the role "security" in the role data to be used is changed to "0". On the other hand, for example, if the role currently being processed is security and its operation mode is to be changed from "remote" to "manual", in the processing of S24, the required number of personnel specified for the role "security" in the role data to be used is changed to "1" or the like.
[0134] Furthermore, for example, if the role currently being processed is a ticket gate and its operation mode is to be changed from "manual" to "automatic" or "remote", the required number of staff specified for the role "ticket gate" in the role data to be used is changed to "0" in the processing of S24. On the other hand, for example, if the role currently being processed is a ticket gate and its operation mode is to be changed from "automatic" or "remote" to "manual", the required number of staff specified for the role "ticket gate" in the role data to be used is changed to "1" or the like in the processing of S24.
[0135] Next, the operation mode change evaluation unit 15 executes an optimization process using role data in which the operation mode of the role currently being processed has been changed (S25). In the process of S25, the operation mode change evaluation unit 15 calls and executes a personnel shift plan formulation process (optimization process) using the optimization solver by the personnel shift plan formulation unit 11 described in Fig. 11. Note that, in the optimization process of S25, multiple solutions (updated personnel shift plan proposals) may be obtained.
[0136] Next, the operation mode change evaluation unit 15 calculates an evaluation score for the solution (updated personnel shift plan proposal) obtained in the optimization process of S25 (S26). In this process, an evaluation score is calculated according to facilities, visibility, congestion status, etc. at the stop stations or running sections (between stop stations) of the train whose operation mode has been changed in each updated personnel shift plan proposal. Therefore, the operation mode change evaluation unit 15 performs the calculation process of the evaluation score in S26 by referring to, for example, facility data (see FIG. 8) of the stop stations and running sections of the train whose operation mode has been changed, and current and past congestion information at the stop stations and running sections stored in the congestion information storage unit 13h.
[0137] Specifically, when the operation mode of the role is changed from "manual" to "automatic" or "remote", the following calculation process of the evaluation points is performed. For example, when the role to be processed is driving and platform screen doors are installed at the stop station of the train to be evaluated, three points are added to the evaluation points as shown in FIG. 13. Also, when the role to be processed is driving and one railroad crossing is installed at the stop station or running section (between stop stations) of the train to be evaluated, one point is subtracted from the evaluation points. For example, when the role to be processed is driving and two railroad crossings are installed at the stop station or running section of the train to be evaluated, two points are subtracted from the evaluation points. Furthermore, when the role to be processed is driving and three railroad crossings are installed at the stop station or running section of the train to be evaluated, three points are subtracted from the evaluation points.
[0138] For example, if the role of the processing target is driving, and the stop or running section (between stop stations) of the train to be evaluated is elevated, 3 points are added to the evaluation score. Also, for example, if the role of the processing target is driving, the evaluation score indicating the quality of visibility is increased or decreased by an evaluation score (-2 points to +2 points) predefined by, for example, the traffic manager. Furthermore, for example, if the role of the processing target is driving, and there is no congestion on the day at the stop or running section of the train to be evaluated, 1 point is added to the evaluation score.
[0139] Also, for example, if the role of the processing target is security and a camera is installed in the station where the train to be evaluated stops or in the train, one point is added to the evaluation point as shown in FIG. 13. For example, if the role of the processing target is security and there is no congestion on the day at the station where the train to be evaluated stops or in the section (between stations), one point is added to the evaluation point. For example, when the role of the processing target is security, the evaluation point indicating whether the station where the train to be evaluated stops or the section where the train to be evaluated runs is a time period or section requiring caution is increased or decreased by an evaluation point (-2 points to +2 points) defined in advance by, for example, the operation manager. The evaluation point regarding the time period or section requiring caution is set based on past congestion information, etc. at the station where the train to be evaluated stops or the section where the train to be evaluated runs.
[0140] Furthermore, for example, if the role of the processing target is a ticket gate and no remote equipment is installed in the stop station of the train to be evaluated, it is excluded from the evaluation as shown in FIG. 13. For example, if the role of the processing target is a ticket gate and a camera is installed in the stop station of the train to be evaluated, one point is added to the evaluation point. For example, if the role of the processing target is a ticket gate and there is no congestion on the day at the stop station of the train to be evaluated, one point is added to the evaluation point. Also, for example, if the role of the processing target is a ticket gate, the evaluation point indicating whether the stop station (stop time period) of the train to be evaluated is a time period / section requiring caution is added or subtracted by an evaluation point (-2 points to +2 points) defined in advance by, for example, the operation manager. When the above-mentioned evaluation is performed, it becomes possible to select a personnel shift plan suitable for the facilities and congestion status of the stop station or running section of the train whose operation mode has been changed.
[0141] Then, after repeating the above-mentioned processes of S24 to S26 for all roles defined in the role data, the operation mode change evaluation unit 15 selects a personnel shift plan proposal after the operation mode change from the obtained multiple solutions (personnel shift plan proposals after update) (S27). In this process, the operation mode change evaluation unit 15 selects an updated personnel shift plan proposal (hereinafter referred to as an "operation mode change proposal") based on the evaluation points of each solution (personnel shift plan proposal after update) calculated in S26. Specifically, the operation mode change evaluation unit 15 selects a predetermined number of operation mode change proposals including the operation mode change proposal with the highest evaluation point.
[0142] After the process of S27, the operation mode change evaluation unit 15 ends the update process of the proposed personnel shift plan described above. Then, the operation mode change proposal (the updated personnel shift plan proposal) determined by the operation mode change evaluation unit 15 is output to and displayed on the display unit (display unit 106 in FIG. 2, etc.) of the personnel shift planning device 10. The display mode of the operation mode change proposal will be described later with reference to the drawings. Also, when there are multiple operation mode change proposals selected in the update process of the proposed personnel shift plan by the operation mode change evaluation unit 15 described above, one operation mode change proposal is determined from among them, for example, by the operations manager, etc.
[0143] [Various display modes for personnel shift plan proposals] Next, various display modes of the personnel shift plan created by the personnel shift plan creating device 10 of this embodiment will be described.
[0144] (1) Example of personnel shift plan displayed by employee Fig. 14 is a diagram showing a first display mode, on an employee basis, of a personnel shift plan proposal created by any one of the personnel shift plan proposal unit 11, the passenger assistance evaluation unit 14, and the operation mode change evaluation unit 15 of the personnel shift plan proposal device 10. Fig. 15 is a diagram showing a second display mode, on an employee basis, of a personnel shift plan proposal created by any one of the personnel shift plan proposal unit 11, the passenger assistance evaluation unit 14, and the operation mode change evaluation unit 15 of the personnel shift plan proposal device 10.
[0145] In a first display mode of the proposed personnel shift plan by employee, the relationship between the role of each employee and the train number for which each role is performed is displayed in a table format, as shown in Fig. 14. In a second display mode of the proposed personnel shift plan by employee, the relationship between the role of each employee and the time for which each role is performed is displayed in a bar diagram format, as shown in Fig. 15. Note that, for the sake of simplicity, only the display mode for employee 1 will be described here, and the display mode for employee 2 will not be described.
[0146] In the first display mode per employee, for example, for employee 1, the train number "Train 015" is displayed in the role "Operation Monitoring" column, and the train numbers "Train 003" and "Train 010" are displayed in the role "Operation" column, as shown in Fig. 14. That is, in the created personnel shift plan proposal, employee 1 is in charge of operation monitoring for train 015, and is in charge of operation for trains 003 and 010.
[0147] In addition, in the first display mode by employee, "015 Train A Station," "015 Train B Station," and "015 Train C Station" are displayed as combinations of train numbers and stop stations in the "Ticket Gate" and "Boarding and Alighting Assistance" columns for employee 1. Furthermore, in the first display mode by employee, the train number "015 Train" is displayed in the "Security" column for employee 1. That is, in the created personnel shift plan proposal, employee 1 is in charge of not only operation monitoring for train 015, but also ticket gates, security, and boarding and alighting assistance.
[0148] The bar timetable displayed in the column for employee 1 shown in FIG. 15 shows the relationship between each train number and role that employee 1 shown in FIG. 14 is responsible for and the time period during which the role is performed. In the second display mode for employee units, as shown in FIG. 15, the bar timetable shows that employee 1 is in charge of driving 003 train (manual) from 8:00 to just after 9:00. In the second display mode for employee units, the bar timetable shows that employee 1 is in charge of driving monitoring and security of 015 train (automatic) from 9:10 to just after 10:10 after driving 003 train (manual). In addition, below the bar timetable for driving monitoring and security of 015 train (automatic) in FIG. 15, the bar timetable shows that employee 1 is in charge of ticket gates and boarding and alighting assistance at each stop (Station A, Station B, and Station C) of 015 train (automatic).
[0149] (2) Example of personnel shift plan displayed by train Fig. 16 is a diagram showing a display mode of a personnel shift plan proposal at the time of planning, for each train, created by the personnel shift plan creation unit 11 of the personnel shift plan creation device 10. Fig. 17A is a diagram showing a display mode of a passenger participation plan (an updated personnel shift plan proposal) for each train, created by the passenger assistance evaluation unit 14 of the personnel shift plan creation device 10. Fig. 17B is a diagram showing a display mode of an operation mode change proposal (an updated personnel shift plan proposal) for each train, created by the operation mode change evaluation unit 15. Figs. 16, 17A, and 17B show examples in which information on the type of each train, vehicle number (operation mode), previous operation, and next operation are also displayed.
[0150] In the display mode of the personnel shift plan draft created by the personnel shift plan creation unit 11 at the time of planning (before the day of operation) on a train-by-train basis, as shown in FIG. 16, the employees in charge of each role are displayed for each train. For example, the personnel shift plan draft at the time of planning displays that employee 4 will be in charge of the roles of "operational monitoring," "ticket gate," and "security" for train 005 (automatic). Note that the example shown in FIG. 16 shows a case in which boarding and alighting assistance is not required for train 005 (automatic) at the stage of creating the personnel shift plan draft at the time of planning. Therefore, in the display mode of the personnel shift plan draft at the time of planning shown in FIG. 16, there is no employee in charge of the role of "boarding and alighting assistance" for train 005 (automatic).
[0151] FIG. 17A is a diagram showing a display mode of a passenger participation plan created by the passenger assistance evaluation unit 14 for each train when, for example, new boarding and alighting assistance is requested for the 005 train on the day of operation of the personnel shift plan at the time of planning shown in FIG. 16. In this case, the personnel shift plan update process by the passenger assistance evaluation unit 14 described in FIG. 12 is performed, and, for example, if the employees alone cannot handle the new boarding and alighting assistance, a request for assistance is made to passengers. FIG. 17A shows a display example for each train when passenger A is in charge of the newly requested boarding and alighting assistance for the 005 train in the passenger participation plan created by the passenger assistance evaluation unit 14. Therefore, in this case, passenger A is displayed in the role "boarding and alighting assistance" column for the 005 train (automatic).
[0152] On the other hand, FIG. 17B is a diagram showing a display mode of the proposed operation mode change by train created by the operation mode change evaluation unit 15 when, for example, employee 1 is absent on the day of operation of the proposed personnel shift plan at the time of planning shown in FIG. 16. Also, the example shown in FIG. 17B shows a case where the operation mode of train 003 is changed from "manual" to "automatic" in order to deal with employee 1's absence. In this case, the role data of train 003 is changed from role data for manual operation (FIG. 4A) to role data for automatic operation (FIG. 4B), and employee skill data of employee 1 (FIG. 6) is all set to unavailable (marked with "x"). Then, using these updated role data and employee skill data, the operation mode change evaluation unit 15 performs the update process of the proposed personnel shift plan described in FIG. 13. FIG. 17B shows a display example of trains when employee 7 is in charge of the role "operation monitoring" of train 003 in the proposed operation mode change created by the operation mode change evaluation unit 15. Therefore, in this case, as shown in Figure 17B, the operation mode displayed in the "Vehicle" column for train 003 is changed from "Manual" to "Automatic," "Employee 7" is newly displayed as the person in charge in the "Operation Monitor" role column, and the "Operation" role column is changed to show no person in charge.
[0153] [Various effects] As described above, in the personnel shift planning system 1 and the personnel shift planning device 10 of the present embodiment, even if a situation occurs on the day of operation that forces the operation plan to be changed, the role data, employee skill data, etc. are appropriately changed and a new personnel shift plan is created again. In addition, at this time, the personnel shift plan is created taking into consideration the role concurrent availability data of each employee, the possibility of passenger assistance, and / or changes to the operation mode of each role. Therefore, in the personnel shift planning system 1 and the personnel shift planning device 10 of the present embodiment, even if a situation occurs on the day of operation that forces the operation plan to be changed, it is possible to execute roles (tasks) in detail and flexibly with a small number of personnel.
[0154] Furthermore, the personnel shift planning technology of the present embodiment described above will be able to respond to future needs, such as the promotion of measures to further reduce labor, improve efficiency, and automate stations, and the need to execute roles (tasks) in a more detailed and flexible manner with fewer personnel.
[0155] In addition, the personnel shift planning system 1 and the personnel shift planning device 10 of the present embodiment have a function for creating a passenger-participation type personnel shift plan, and by using this function, it is possible to divide roles beyond the boundaries between service providers and beneficiaries. In this case, it becomes possible for the whole society to be involved in the operation of public transportation facilities, so that the public transportation facilities can be maintained with fewer personnel.
[0156] Furthermore, the personnel shift planning system 1 and the personnel shift planning device 10 of this embodiment are provided with a personnel shift planning function that takes into account changes in the manner in which roles are used, so that employees alone can respond to various situations as much as possible.
[0157] [Various variations] Although the personnel shift planning system 1 and the personnel shift planning device 10 according to one embodiment of the present invention have been described above, the present invention is not limited thereto. For example, the following various modified examples can be adopted, and the same effects as those of the above embodiment can be obtained in the following various modified examples.
[0158] In the above embodiment, an example has been described in which the passenger assistance evaluation unit 14 and / or the operation mode change evaluation unit 15 update the personnel shift allocation plan when it becomes necessary to change the personnel shift allocation plan created at the time of planning on the day of operation, but the present invention is not limited to this. For example, when it is recognized that it is necessary to change the personnel shift allocation plan after the creation of the personnel shift allocation plan at the time of planning and before the day of operation, the personnel shift allocation plan may be updated at that time by the passenger assistance evaluation unit 14 and / or the operation mode change evaluation unit 15. In this case, in the evaluation process of the updated personnel shift allocation plan, the evaluation is performed using only various information (number of users, number of registered users, past assistance performance of passengers, facility data, etc.) other than information obtained on the day of operation, such as information on the congestion situation on the day and passenger location information.
[0159] In the above embodiment, a railroad is used as an example of public transportation, but the present invention is not limited to this. For example, the technology of the present invention can be applied to any public transportation that creates an operation plan and a corresponding personnel shift plan in advance. For example, the technology of the present invention can also be applied to the process of creating personnel shift plans for buses, airplanes, etc.
[0160] In addition, the above-mentioned embodiment has been described in detail and specifically with respect to the configuration of the system and device in order to easily explain the present invention, and is not necessarily limited to the configuration having all of the described configurations. In addition, the present invention may have various other applications and modifications without departing from the gist of the present invention described in the claims. [Explanation of symbols]
[0161] 1... Personnel shift planning system, 10... Personnel shift planning device, 11... Personnel shift planning unit, 12... Personnel shift plan update unit, 13... Memory unit, 13a... Train schedule memory unit, 13b... Role database, 13c... Concurrent job availability database, 13d... Employee skill database, 13e... Passenger assistance possibility database, 13f... Equipment database, 13g... Performance data memory unit, 13h... Congestion information memory unit, 14... Passenger assistance evaluation unit, 15... Operation mode change evaluation unit, 20... Train schedule planning device, 30... Passenger's mobile terminal
Claims
1. a first personnel allocation planning unit that acquires operation data of a public transportation facility and creates an allocation plan for employees to a plurality of tasks required for the operation of the public transportation facility corresponding to the operation data; and a second personnel allocation planning unit that, when it becomes necessary to change the employee allocation plan created by the first personnel allocation planning unit, evaluates the possibility of passengers participating in work and creates a new allocation plan including the passengers' participation in work based on the results of the evaluation. Personnel allocation planning device.
2. The second personnel allocation planning unit has a function of evaluating the possibility of changing the operation mode of the work and, based on the result of the evaluation, creating another new staffing plan that reflects the change in the operation mode of the work, in addition to the function of creating a new staffing plan that includes the participation of the passengers in the work when it becomes necessary to change the staffing plan created by the first personnel allocation planning unit. The personnel allocation planning device according to claim 1 .
3. a storage unit capable of storing the operation data, task data defining the relationship between the plurality of tasks and the number of people required for each task, concurrent task data defining whether concurrent tasks can be performed between tasks, employee skill data defining tasks that the employees can handle, and passenger assistance possibility data defining information regarding the possibility of passengers participating in the tasks; the first personnel allocation planning unit creates constraint conditions based on the operation data, the work data, the concurrent job data, and the employee skill data, and creates an employee allocation plan that satisfies the created constraint conditions; The second personnel allocation planning unit, when it becomes necessary to change the employee allocation plan created by the first personnel allocation planning unit, evaluates the possibility of the passenger's participation in work using the passenger assistance possibility data. The personnel allocation planning device according to claim 1 .
4. When a plurality of new personnel allocation plans are created, the second personnel allocation planning unit evaluates each of the new personnel allocation plans based on information on the possibility of the passengers participating in work and information on the current operation status, and selects the new personnel allocation plan based on the result of the evaluation. The personnel allocation planning device according to claim 1 .
5. The second personnel allocation planning unit identifies passengers who can handle the new allocation plan based on performance information of the passengers' work participation, and transmits a support request to the identified passengers. The personnel allocation planning device according to claim 4.
6. When a plurality of new personnel allocation plans are created, the second personnel allocation planning unit evaluates each of the new personnel allocation plans based on information on facilities installed on the route of the public transportation system and information on a current operation status, and selects the new personnel allocation plan based on a result of the evaluation. The personnel allocation planning device according to claim 2.
7. an operation data creation unit that creates operation data of public transportation; a first personnel allocation planning unit that acquires the operation data created by the operation data creation unit and creates a plan for allocating employees to a plurality of types of work required for the operation of the public transportation system corresponding to the operation data; and a second personnel allocation planning unit that, when it becomes necessary to change the employee allocation plan created by the first personnel allocation planning unit, evaluates the possibility of passengers participating in work and creates a new allocation plan including the passengers' participation in work based on the results of the evaluation. Personnel allocation planning system.
Citation Information
Patent Citations
Device and method for supporting operation and arrangement of crew
JP2004243857A
Operation arrangement support system and operation arrangement support method
JP2013035502A
Movement support system, movement support apparatus, movement support method and movement support program
JP2018173693A
Information processing apparatus, information processing method, and program
JP2020021375A
Train boarding / alighting support system and service provision method
JP2022165202A
