Schedule data creating apparatus and schedule data creating method

Abstract

A schedule data creating apparatus (1) creates schedule data (SD) for deciding an execution schedule which is a schedule for executing a plurality of jobs of different kinds in a time series. An input / output section (13) acquires table data (TD) which describes schedule conditions for each combination between jobs in a table form, and acquires request data (RD) which is data for specifying a plurality of jobs which are the object of creation of the schedule data (SD). A schedule creating section (12) arranges the plurality of jobs specified by the request data (RD) in a time series in such a manner that each of the plurality of jobs satisfies the schedule conditions based on the table data (TD), thereby creating the schedule data (SD). The input / output section (13) outputs the schedule data (SD) or the table data (TD).

Description

Technical Field

[0001] The present invention relates to a timetable data producing device and a timetable data producing method. Background Art

[0002] For example, Patent Document 1 discloses a schedule data creation device that uses a learned model to generate a medical facility utilization schedule. In Patent Document 1, the schedule generation device includes an acquisition unit that acquires surgery list data and a learned model, and a generation unit that generates medical facility schedule data. The acquisition unit stores the acquired surgery list data and learned model in a storage unit. Based on the surgery list data and learned model stored in the storage unit, the generation unit generates the medical facility schedule data, which is a schedule for a predetermined period of time at the medical facility.

[0003] Prior art literature

[0004] Patent Literature

[0005] Patent Document 1: Japanese Patent Application Laid-Open No. 2020-003862 Summary of the Invention

[0006] Problems to be solved by the invention

[0007] To create a timetable that cannot be processed computationally, training data containing source code written in a computer language must be provided to the timetable data creation device. However, source code is a specialized data structure. Creating training data is extremely complex and time-consuming. Furthermore, maintaining and improving training data is also complex and time-consuming.

[0008] The present invention has been made in view of the above-mentioned problems, and an object of the present invention is to provide a timetable data creating device and a timetable data creating method capable of creating timetable data based on data having a simple structure.

[0009] Solutions for solving problems

[0010] A schedule data creation device according to one embodiment of the present invention acquires table data describing schedule conditions for each combination of tasks in a table format, and acquires request data specifying a plurality of tasks for which the schedule data is to be created. Based on the table data, the schedule data creation device arranges the plurality of tasks specified by the request data in a time series so that each of the plurality of tasks satisfies the schedule conditions, thereby creating the schedule data. The schedule data creation device outputs the schedule data or the table data.

[0011] Effects of the Invention

[0012] According to the present invention, schedule data can be created from data with a simple structure. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 This is a block diagram showing the configuration of a schedule data creation device according to this embodiment.

[0014] Figure 2 This is a flowchart showing the flow of processing related to the schedule data creation method related to this embodiment.

[0015] Figure 3 This is an explanatory diagram showing a two-dimensional table determined by table data.

[0016] Figure 4 It is an explanatory diagram showing the priority of work items.

[0017] Figure 5 It is an explanatory diagram showing request data.

[0018] Figure 6 This is an explanatory diagram showing an example of a restriction condition.

[0019] Figure 7 This is an explanatory diagram showing an example of a restriction condition.

[0020] Figure 8 It is an explanatory diagram showing a new two-dimensional table.

[0021] Figure 9 It is an explanatory diagram showing schedule conditions described by source code.

[0022] Figure 10 This is an explanatory diagram showing a basic arrangement of a plurality of work items specified by request data.

[0023] Figure 11 This is an explanatory diagram of the vehicle trial production schedule determined by the schedule data.

[0024] Figure 12 This is an explanatory diagram of the vehicle trial production schedule determined by the schedule data. DETAILED DESCRIPTION

[0025] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the description of the drawings, the same reference numerals are given to the same parts and their description will be omitted.

[0026] Reference Figure 1The structure of the schedule data creating apparatus 1 will be described. The schedule data creating apparatus 1 according to the present embodiment is an apparatus that creates schedule data SD. The schedule data SD is data for determining an execution schedule in which a plurality of jobs different in kind are executed in a time series. Here, the "job" is a general term for various kinds of work and the like that can be executed in a time series.

[0027] In the present embodiment, a vehicle trial schedule for trial-manufacturing a hybrid vehicle is exemplified. That is, the "job" is a work item required for trial-manufacturing a hybrid vehicle. There are a plurality of kinds of work items such as assembly of a vehicle body, painting, and installation of parts, and the vehicle trial schedule in which the plurality of work items different in kind are executed in a time series is determined by the schedule data SD. That is, by executing the plurality of work items different in kind in a time series according to the vehicle trial schedule determined by the schedule data SD, a hybrid vehicle can be trial-manufactured.

[0028] The schedule data creating apparatus 1 is constituted mainly of a computer 10 and a storage section 20.

[0029] The computer 10 is constituted mainly of a CPU, a ROM, a RAM, an input / output interface, and the like. A computer program for causing the computer 10 to function as the schedule data creating apparatus 1 is installed in the computer 10. By executing the computer program, the computer 10 functions as a plurality of information processing circuits provided in the schedule data creating apparatus 1. In the present embodiment, an example in which the plurality of information processing circuits provided in the schedule data creating apparatus 1 are realized by software is shown, but of course, dedicated hardware for executing each information processing shown below can be prepared to constitute the information processing circuits. Alternatively, the plurality of information processing circuits can be constituted by independent hardware.

[0030] The computer 10 is provided with a code creating section 11 (control section), a schedule creating section 12 (control section), and an input / output section 13 (input section, output section) as the plurality of information processing circuits.

[0031] The code creating section 11 rewrites the table data TD into a source code. The table data TD is data that describes a schedule condition for each combination between work items in a table form. Here, the schedule condition is a condition that should be satisfied on a time axis between work items different in kind. On the other hand, the source code is a code described in a computer language, and is a code that describes an instruction that should be processed by a computer.

[0032] The schedule creation unit 12 creates schedule data SD based on the request data RD and the source code created by the code creation unit 11. The request data RD is used to specify a plurality of work items, from among all the types of work items described in the table data TD, for which the schedule data SD is to be created. Specifically, the plurality of work items specified by the request data RD include two or more work items selected from among all the types of work items described in the table data TD. However, the plurality of work items specified by the request data RD may also include all the types of work items described in the table data TD.

[0033] The schedule creating unit 12 creates schedule data SD by arranging a plurality of work items specified by the request data RD in time series based on the source code so that each of the plurality of work items satisfies the schedule conditions.

[0034] The input / output unit 13 is connected to the storage unit 20 and the external device 30. The input / output unit 13 obtains the table data TD and the request data RD from the storage unit 20. Alternatively, the input / output unit 13 obtains the table data TD and the request data RD from the external device 30.

[0035] The input / output unit 13 is connected to an input device 40 for a user to input information. The input / output unit 13 can acquire information inputted by the user using the input device 40.

[0036] Furthermore, the input / output unit 13 outputs the schedule data SD and the table data TD to the external device 30. The input / output unit 13 can also output the schedule data SD and the table data TD to the display 50 for displaying information.

[0037] The storage unit 20 stores the table data TD and the request data RD acquired by the input / output unit 13 from the external device 30 . The storage unit 20 also stores the schedule data SD created by the schedule creation unit 12 .

[0038] Reference Figure 2 A timetable data creation method executed by the timetable data creation device 1 according to this embodiment will be described.

[0039] In the following description, it is assumed that three types of hybrid vehicles corresponding to a sedan, a wagon, and a onebox are prototyped.

[0040] In the trial production of a hybrid vehicle, ten work items are required: (A) body assembly, (B) painting, (C) underfloor assembly, (D) first body assembly, (E) module component installation, (F) second body assembly, (G) chassis component installation, (H) installation adjustment, (I) module component assembly, and (J) module component transportation. When describing the work items in the drawings below, sometimes only letters A to J are used instead of specific names ( Figure 8 wait).

[0041] Here, body assembly is the process of assembling the body, and painting is the process of painting the body. Underfloor assembly is the process of assembling the underfloor, first body assembly is the process of assembling the first body, and second body assembly is the process of assembling the second body and other body parts. Modular component installation is the process of installing modularized components such as lithium-ion batteries. Chassis component installation is the process of installing chassis components. Installation adjustment is the process of adjusting installed components. Modular component assembly is the process of assembling multiple components to create modularized components. Modular component transportation is the process of transporting modularized components.

[0042] First, in step S10, the input / output unit 13 acquires table data TD. The table data TD acquired by the input / output unit 13 is used by the code generating unit 11 as will be described later.

[0043] like Figure 3 As shown, table data TD is defined in the form of a two-dimensional table 100, which is defined by a column-oriented item group 101 and a row-oriented item group 102. In two-dimensional table 100, the types of work items are described in each of the column-oriented item group 101 and the row-oriented item group 102. In two-dimensional table 100, cells 103 located at the intersection of the types of work items described in the column-oriented item group 101 and the row-oriented item group 102 describe schedule conditions.

[0044] Each cell 103 is described with "L" or "R." "L" indicates that the work item described in the column-oriented item group 101 is executed before the work item described in the row-oriented item group 102. Conversely, "R" indicates that the work item described in the column-oriented item group 101 is executed later than the work item described in the row-oriented item group 102. For example, "L" is described in the cell 103 at the intersection of "Body Assembly" described in the column-oriented item group 101 and "Painting" described in the row-oriented item group 102. This description allows the user to understand that body assembly is executed before painting.

[0045] In addition to "L" or "R," each cell 103 also contains a number. This number represents the interval (time) required between the work item described in the column-oriented item group 101 and the work item described in the row-oriented item group 102. For example, the cell 103 at the intersection of "Modular Component Installation" described in the column-oriented item group 101 and "Modular Component Delivery" described in the row-oriented item group 102 contains "R0.5." This indicates to the user that modular component installation is performed at least 0.5 hours after modular component delivery.

[0046] The schedule conditions for each cell 103 include the relative order of different types of work items, such as whether the work items described in the column-oriented item group 101 should be executed before or after the work items described in the row-oriented item group 102. The schedule conditions also include the required intervals between different types of work items. If intervals are not required, only "L" or "R" is described in the two-dimensional table 100, and the numerical description is omitted.

[0047] Priority is pre-set for each task based on the timeline. Figure 4 In the example shown, priorities are expressed as numbers, and work items with smaller numbers indicate that they require work to be performed sooner. The two-dimensional table 100 defined by the table data TD is created in advance based on the priorities set for each work item.

[0048] In step S11, the input / output unit 13 acquires the request data RD. The request data RD acquired by the input / output unit 13 is used by the schedule creation unit 12. Figure 5 In the illustrated example, the plurality of work items specified by the request data RD correspond to all types of work items described in the table data TD.

[0049] In addition, in the request data RD, required time, which is the time required to execute the work items, is associated with each of the plurality of work items. Figure 5 In the request data RD shown, required times for a plurality of work items are associated with each of vehicle types A (SED) corresponding to a sedan, B (WAG) corresponding to a station wagon, and C (OBX) corresponding to a van.

[0050] In step S12, the input / output unit 13 obtains constraints. Constraints are conditions that must be met in addition to the schedule conditions in the vehicle trial production schedule. Constraints are digitized in a predetermined format and obtained by the input / output unit 13 from the storage unit 20 or the external device 30. The constraints obtained by the input / output unit 13 are used by the schedule creation unit 12. In this embodiment, three constraints are illustrated.

[0051] The first constraint condition is, for example, a constraint corresponding to a production line. Figure 6 The first constraint outlines the following. Hybrid vehicles are trial-produced using a main production line and a sub-production line. The main production line is the production line (the main execution body) that performs eight tasks: body assembly, painting, underfloor assembly, first body assembly, module component installation, second body assembly, chassis component installation, and installation adjustments. The main production line consists of three lines: Line 1, Line 3, and each line is assigned to one of the three vehicle models.

[0052] Meanwhile, the secondary production line is a production line (the main execution body) that performs two tasks: module assembly and module transport. The secondary production line consists of only one line. Therefore, the three modules used in the three vehicle models are serially trial-produced on the secondary production line.

[0053] The second constraint condition is, for example, a constraint corresponding to grouping of a plurality of work items. Figure 7 The following summarizes the second constraint. It is desirable to perform vehicle body assembly, painting, underfloor assembly, and first vehicle body assembly in a continuous manner. Therefore, these tasks are grouped together and cannot be performed separately. Similarly, it is desirable to perform module assembly and module transport in a continuous manner. Therefore, these tasks are grouped together and cannot be performed separately.

[0054] The third constraint is synchronization between different production lines. When operations performed on the main production line and those performed on the secondary production line are interconnected, synchronization between the production lines is necessary. Module component installation on the main production line involves installing modules delivered via module component transport on the secondary production line. Therefore, synchronization constraints apply to both module component installation and module component transport.

[0055] In addition, when there are multiple constraints, these constraints are given priorities. This allows identification of the order in which the constraints are to be applied. In this embodiment, the constraints are applied in the order of the first constraint, the second constraint, and the third constraint.

[0056] In step S13, the code making section 11 and the schedule making section 12 make the schedule data SD based on the table data TD, the request data RD, and the restriction condition. The processing of making the schedule data SD will be described specifically below.

[0057] First, the code making section 11 sorts the two-dimensional table 100 decided by the table data TD and converts it into a two-dimensional table 110. The two-dimensional table 110 is defined by three groups of items in the column direction, and a plurality of cell sets 111 are prepared in the row direction. The code making section 11 extracts one group of work items different in kind and the schedule condition described in the cell 103 at the cross position of the one group of work items from the two-dimensional table 100. Then, the code making section 11 describes the extracted information in the cell set 111.

[0058] In each cell set 111, the work item described in the group 101 of items in the column direction of the two-dimensional table 100 is described in the cell at the leftmost column. In addition, the work item described in the group 102 of items in the row direction of the two-dimensional table 100 is described in the cell at the center column. Further, the schedule condition is described in the cell at the rightmost column. Such a description method is regulated in advance, and the code making section 11 makes the two-dimensional table 110 in accordance with the regulation. Thus, by interpreting the two-dimensional table 110 based on the regulation, the meaning of the two-dimensional table 110 can be understood. For example, it is assumed that "A, B, L" is described from the left column to the right column in the cell set 111 of a certain row. In this case, the user can read that the body assembly is performed before painting by reading the cell set 111 from the left to the right.

[0059] Further, the form of the table data TD acquired by the input / output section 13 can not be the two-dimensional table 100 but the two-dimensional table 110. In this case, the code making section 11 can omit the processing of converting from the two-dimensional table 100 to the two-dimensional table 110.

[0060] The code making section 11 rewrites the data described in the cell set 111 of the two-dimensional table 110, specifically the table data TD, into a source code. The rewriting into the source code is performed on all the cell sets 111 described in the two-dimensional table 110.

[0061] In this embodiment, the source code is described using "IF" and "then". Specifically, the code generation unit 11 extracts the data described in the cell set 111. For example, in a certain cell set 111, the columns from the left to the right are described as "A, B, L". When the data is extracted from the cell set 111, the code generation unit 11 describes "IF A and B then A <B”这一源代码。计算机10根据该源代码能够理解在存在“A”和“B”这样的作业项目的情况下“A”小于“B”这一条件。在源代码中,“A”与“B”在时间轴上应满足的关系被置换为“A”小于“B”这样的大小关系。

[0062] Similarly, in a cell set 111, "E, I, R" is described from the left column to the right column. When extracting data from this cell set 111, the code generator 11 writes the source code "IF E and I then E>I." Based on this source code, the computer 10 understands that, given the existence of work items "E" and "I," the condition "E" is greater than "I." In the source code, the relationship between "E" and "I" on the time axis is replaced with a magnitude relationship where "E" is greater than "I."

[0063] Furthermore, in a cell set 111, "E, J, R0.5" is described from the left column to the right column. When extracting data from this cell set 111, the code creation unit 11 writes source code such as "IF E and J then E>J+0.5." Based on this source code, the computer 10 understands that, given the existence of work items "E" and "J," the condition "E" must be greater than "J+0.5." In the source code, the relationship that "E" and "J" should satisfy on the time axis is replaced with a magnitude relationship such that "E" is greater than "J+0.5."

[0064] By replacing the magnitude relationship understood from the source code with a temporal relationship, the computer 10 can understand the conditions that must be satisfied between different types of work contents on the time axis, namely, the schedule conditions. The code generation unit 11 outputs the generated source code to the schedule generation unit 12.

[0065] The schedule creation unit 12 creates schedule data SD based on the request data RD. First, the schedule creation unit 12 arranges the 10 work items specified by the request data RD in a time series, thereby creating a basic schedule for the vehicle trial production schedule. The basic schedule for the vehicle trial production schedule is created so that each of the 10 work items satisfies the size relationship (schedule conditions) defined in the source code. Specifically, the schedule creation unit 12 compares the size relationships of the 10 work items based on the source code and prioritizes the work items that are evaluated as smaller. Constraints are also considered in the arrangement of the work items.

[0066] like Figure 10 As shown, the schedule creation unit 12 divides the 10 work items specified by the request data RD into the main line and the sub-line, and arranges the work items for each line.

[0067] In the main production line, 8 work items become the objects of arrangement. The schedule making unit 12 arranges the 8 work items from left to right based on the source code in such a way that each of the 8 work items satisfies the size relationship (i.e., the schedule condition) defined by the source code. Thus, the 8 work items are arranged in the order of body assembly, painting, underfloor assembly, first body assembly, module component installation, second body assembly, chassis component installation, and installation adjustment. After the 8 work items are arranged, if the arrangement of each work item does not meet the second constraint condition, it is corrected to meet the second constraint condition. Thus, the body assembly, painting, underfloor assembly and first body assembly are arranged in a group, reflecting the second constraint condition.

[0068] In the secondary production line, two work items become the objects of arrangement. The schedule making unit 12 arranges the two work items from left to right based on the source code in such a way that the two work items each satisfy the size relationship defined by the source code (i.e., the schedule condition). Thus, the two work items are arranged in the order of module component assembly and module component transportation. After the two work items are arranged, if the arrangement of each work item does not satisfy the second constraint condition, it is corrected to meet the second constraint condition. Thus, the module component assembly and the module component transportation are arranged in a group, reflecting the second constraint condition.

[0069] Furthermore, module component installation is an operation that is performed based on the delivery of module components. There is an operational linkage between module component installation and module component delivery. In this case, even for work items belonging to the main production line and the auxiliary production line, the schedule creation unit 12 arranges them so that each work item satisfies the size relationship defined by the source code. In other words, the schedule creation unit 12 arranges the work so that module component delivery precedes module component installation, and sets an interval of at least 0.5 hours between module component delivery and module component installation. This reflects the third constraint.

[0070] The schedule creating unit 12 creates schedule data SD corresponding to each of the three vehicle models based on the basic arrangement of the vehicle trial production schedule. The schedule data SD is determined by a time sequence diagram in which a plurality of work items are arranged in time series on a time axis. Figure 11 As shown, the 10 work items are arranged in chronological order on the time axis, following the arrangement shown in the basic layout of the vehicle trial production schedule. In this time sequence diagram, each work item is displayed with a length corresponding to the required time Ta to Tj. The time sequence diagram arranges the work items separately for the main production line and the auxiliary production line. The main production line consists of three lines corresponding to different vehicle models, so the schedules for each line are presented in parallel. Meanwhile, the auxiliary production line consists of a single line, so the schedules corresponding to the three vehicle models are presented serially.

[0071] After this series of processing, schedule data SD is generated. In this embodiment, schedule data SD is determined by a time sequence diagram that arranges multiple work items in a time sequence on a time axis. Based on this schedule data SD, the execution schedule for executing the multiple work items in a time sequence can be understood from the time sequence arrangement of the multiple work items.

[0072] In addition, when creating the timetable data SD, there may be multiple pattern candidates in the arrangement of the work items. Figure 12 As shown, the combination with the shortest total work time may be used as the final solution of the schedule data SD. However, this consideration is merely an example, and the final solution of the schedule data SD may be determined by taking into account factors required for prototype production of a hybrid vehicle.

[0073] In step S14 , the input / output unit 13 outputs the schedule data SD and the table data TD.

[0074] As described above, in this embodiment, the input / output unit 13 acquires table data TD describing schedule conditions for each combination of work items in a tabular format, and acquires request data RD specifying a plurality of work items to be generated for schedule data SD. Based on the table data TD, the schedule generation unit 12 arranges the plurality of work items specified by the request data RD in a time series so that each of the plurality of work items satisfies the schedule conditions. Thus, the schedule generation unit 12 creates a time sequence diagram in which the plurality of work items are arranged in time series as schedule data SD. The input / output unit 13 outputs the schedule data SD generated by the schedule generation unit 12, and also outputs the table data TD used in generating the schedule data SD.

[0075] According to this embodiment, table data TD is data that describes schedule conditions for each combination of work items in a tabular format and is created with a simple structure. Therefore, users can easily create table data TD and easily understand the contents described in table data TD. Furthermore, the schedule data creation device 1 can output table data TD, thereby providing users with the opportunity to utilize table data TD. In this case, users can also easily understand the contents described in table data TD. This makes it easy to maintain or modify table data TD. Thus, the schedule data creation device 1 can create schedule data SD based on data with a simple structure.

[0076] In this embodiment, a plurality of work items are executed by one or more execution entities, such as the main line and the sub-line. The execution periods of work items executed by the same execution entity do not overlap.

[0077] Work items executed by the same execution subject have a relationship in which the execution periods of the work items do not overlap. In the case of such work items, schedule data SD can be created with high reliability by arranging the plurality of work items in time series.

[0078] In the present embodiment, required time is associated with each of a plurality of work items in the request data RD, and the schedule creating unit 12 arranges the plurality of work items in time series in consideration of the required time.

[0079] This allows a plurality of work items to be arranged in time series in consideration of the time required for each work item, thereby making it possible to create timetable data SD with high reliability.

[0080] The code generating unit 11 rewrites the table data TD into source code in which instructions to be processed by the computer are described. The schedule generating unit 12 arranges a plurality of work items in time series based on the source code.

[0081] According to this configuration, by rewriting table data TD into source code, the schedule creation unit 12 can process the contents described in table data TD as instructions. Thus, the schedule creation unit 12 can understand table data TD from the source code and can appropriately create schedule data SD.

[0082] The schedule conditions include the relative order of different types of work items when executing them, and the required intervals between different types of work items.

[0083] According to this configuration, by using the precedence relationship and the interval, it is possible to define the conditions that should be satisfied between different types of work items on the time axis. This allows the priorities of multiple work items to be appropriately identified and the schedule data SD to be created.

[0084] Furthermore, table data TD is a two-dimensional table 100 defined by row-oriented item groups and column-oriented item groups. The types of work items are described in row-oriented item groups 102 and column-oriented item groups 101, respectively. The intersection of the types of work items described in row-oriented item groups 102 and column-oriented item groups 101 describes the schedule conditions.

[0085] With this structure, table data TD is constructed in the form of a two-dimensional table 100. Therefore, users can easily understand the schedule conditions between different types of work items based on the two-dimensional table 100 determined by the table data TD. This reduces the complexity of creating table data TD. Furthermore, since only the two-dimensional table 100 needs to be analyzed, the user can improve the workability of modifying the table data TD.

[0086] Furthermore, the input / output unit 13 acquires table data TD input from the external device 30 .

[0087] According to this configuration, the schedule data creating device 1 can use the table data TD created by the external device 30 .

[0088] In addition, the input-output unit 13 can also obtain schedule conditions from the input device 40 for the user to input information, and generate table data TD based on the schedule conditions, thereby obtaining table data. For example, the user uses the input device 40 to input a combination of work items and a schedule condition corresponding to the combination. The input method using the input device 40 is voice or character string. At this time, the user inputs the combination of work items and the schedule condition according to a predetermined article structure. For example, the user inputs "'Vehicle body assembly' is performed 'before' 'Painting'". The input-output unit 13 understands the article structure of the input article and creates a two-dimensional table 100. Specifically, the input-output unit 13 describes "Vehicle body assembly" in the column-direction item group 101 in the two-dimensional table 100, describes "Painting" in the row-direction item group 102, and describes "L" in the cell 103 at the intersection of these work items, and so on.

[0089] According to this configuration, the schedule data creation device 1 itself can create table data TD according to the schedule conditions input by the user. In this case, the user only needs to input the schedule conditions and the like using a text structure, eliminating the need for complicated work.

[0090] The schedule creating unit 12 arranges the plurality of work items in time series in consideration of constraint conditions that are conditions to be satisfied in addition to the schedule conditions in the execution schedule.

[0091] According to this configuration, conditions other than the schedule conditions can be added, and thus schedule data can be created taking various viewpoints into consideration.

[0092] In addition, as restriction conditions, there are the trial production order such as which model should be prioritized for trial production, the capacity of the trial production equipment such as the number of production lines, the number of vehicles that can be trial-produced within a specified period, the trial production site where the trial production is carried out, and the transportation period for transporting parts to the trial production site.

[0093] The timetable data creation method according to the above-described embodiment has technical features corresponding to those of the above-described timetable data creation device 1 , and produces the same effects as those of the timetable data creation device 1 .

[0094] As described above, although the embodiments of the present invention are described, it should not be understood that the description and drawings constituting part of this disclosure limit the present invention. Based on this disclosure, various alternative embodiments, examples, and application techniques will become apparent to those skilled in the art.

[0095] For example, the schedule data creation device and schedule data creation method of this embodiment describe a vehicle trial production schedule for trial production vehicles. However, any execution schedule that executes multiple tasks of varying types in a time series may be used. Alternatively, a test schedule that performs various experiments on trial production vehicles in a time series may be used. Furthermore, a vehicle scheduling schedule in which service vehicles providing passenger services perform various tasks in a time series may also be used.

[0096] Description of Reference Numerals

[0097] 1: Schedule data creation device; 10: Computer; 11: Code creation unit (control unit); 12: Schedule creation unit (control unit); 13: Input / output unit (input unit, output unit); 20: Storage unit; TD: Table data; SD: Schedule data; RD: Request data.

Claims

1. A schedule data creation device for creating schedule data for determining an execution schedule, wherein the execution schedule is a schedule for executing a plurality of different types of tasks in a time series, wherein: It has an input unit, a control unit and an output unit, The input unit acquires table data describing schedule conditions for each combination of different types of tasks in a table format, wherein the schedule conditions are conditions that should be satisfied between the tasks on a time axis. The input unit acquires request data for specifying the plurality of jobs to be created for the schedule data from among all types of jobs described in the table data. The control unit converts the two-dimensional table of the first format determined by the table data into a two-dimensional table of the second format, The control unit rewrites the second-format two-dimensional table into source code describing instructions to be processed by the computer. The control unit creates the schedule data by arranging the plurality of jobs specified by the request data in time series based on the source code so that each of the plurality of jobs satisfies the schedule condition. The output unit outputs the schedule data generated by the control unit, The output unit outputs the two-dimensional table of the first format used in creating the schedule data. The first form of the two-dimensional table is defined by a row-oriented item group and a column-oriented item group, wherein the row-oriented item group and the column-oriented item group respectively describe types of work, and the intersection of the types of work described in the row-oriented item group and the types of work described in the column-oriented item group describes the schedule condition. The second form of the two-dimensional table specifies a cell set in the row direction corresponding to the three item groups specified in the column direction. In the first cell of the cell set, the type of work described by the item group in the column direction in the two-dimensional table of the first form is described. In the second cell of the cell set, the type of work described by the item group in the row direction in the two-dimensional table of the first form is described. In the third cell of the cell set, the schedule condition at the intersection position in the two-dimensional table of the first form is described.

2. The timetable data creating device according to claim 1, wherein: The multiple tasks are executed by one or more execution entities. The periods of execution of the works by the same execution entity do not overlap.

3. The timetable data creating device according to claim 2, wherein: In the request data, required time, which is time required to execute the job, is associated with each of the plurality of jobs. The control unit arranges the plurality of jobs in time series in consideration of the required time.

4. The timetable data creating device according to any one of claims 1 to 3, wherein: The schedule conditions include: The relative sequencing of tasks when performing different types of work; and The intervals required between different types of work.

5. The timetable data creating device according to any one of claims 1 to 3, wherein: The input unit acquires the table data input from an external device.

6. The timetable data creating device according to any one of claims 1 to 3, wherein: The input unit acquires the schedule conditions from an input device for a user to input information, and acquires the table data by generating the table data based on the schedule conditions.

7. The timetable data creating device according to any one of claims 1 to 3, wherein: The control unit arranges the plurality of jobs in time series in consideration of a constraint condition that is a constraint to be satisfied in addition to the schedule condition in the execution schedule.

8. The timetable data creating device according to claim 7, wherein: The constraints are those corresponding to the production line. In a case where the plurality of jobs include jobs performed on a main line and jobs performed on a sub-line, the schedule data is prepared for each line, and the schedule conditions are satisfied between the main line and the sub-line.

9. The timetable data creating device according to claim 8, wherein: When a plurality of jobs that are expected to be performed continuously are grouped together and schedule data is created for each production line, the schedule data is also created while maintaining the grouping.

10. A method for creating timetable data for determining an execution timetable, wherein the execution timetable is a timetable for executing a plurality of different types of tasks in a time series, wherein: The computer performs the following processing: Acquiring table data describing, in a table format, schedule conditions for each combination of different types of jobs, the schedule conditions being conditions that should be satisfied between the jobs on a time axis; acquiring request data for specifying the plurality of jobs to be created for the schedule data from among all types of jobs described in the table data; Converting the two-dimensional table of the first form determined by the table data into a two-dimensional table of the second form, Rewrite the second two-dimensional table into source code describing instructions that a computer should process. creating the schedule data by arranging the plurality of jobs specified by the request data in time series based on the source code so that each of the plurality of jobs satisfies the schedule condition; outputting the generated schedule data; outputting the two-dimensional table of the first format used in creating the schedule data, The first form of the two-dimensional table is defined by a row-oriented item group and a column-oriented item group, wherein the types of work are described in the row-oriented item group and the column-oriented item group, respectively, and the intersection of the types of work described in the row-oriented item group and the types of work described in the column-oriented item group describes the schedule condition. The second form of the two-dimensional table specifies a cell set in the row direction corresponding to the three item groups specified in the column direction. In the first cell of the cell set, the type of work described by the item group in the column direction in the two-dimensional table of the first form is described. In the second cell of the cell set, the type of work described by the item group in the row direction in the two-dimensional table of the first form is described. In the third cell of the cell set, the schedule condition at the intersection position in the two-dimensional table of the first form is described. 11 . A computer-readable storage medium storing a computer program for executing the schedule data producing method according to claim 10 when the computer program is executed by a processor.

12. A computer program product comprising a computer program for executing the timetable data production method according to claim 10 when the computer program is executed by a processor.

Images