Information processing system, information processing apparatus, server device, program, cloud or method

Abstract

To provide an information processing system, an information processing apparatus, a server device, a program, a cloud or a method configured to support planning more appropriately.SOLUTION: A computer program causes a system to operate as: acquisition means which acquires data including master data and task data pertaining to a plan represented by a table formed by rows and columns; and display means which performs display in accordance with a display logic, by using first data representing a relation of data in the master data and the task data pertaining to the plan and second data representing a relation of data between data in the display logic and the master data and the task data pertaining to the plan. The second data includes data indicating tables, rows and columns in the mask data and the task data pertaining to the plan, and data indicating a relation regarding the data indicating the tables, rows and columns used in the display logic.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The technology disclosed in this application relates to an information processing system, an information processing apparatus, a server apparatus, a program, a cloud, or a method.

Background Art

[0002] In recent years, using an information processing apparatus to assist in planning has been considered.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Non-Patent Documents

[0004]

Non-Patent Document 1

Non-Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in order to appropriately carry out planning, there are situations where computer technology is not utilized. Therefore, various embodiments of the present invention provide an information processing system, an information processing apparatus, a server apparatus, a cloud, a program, or a method to solve the above problems.

Means for Solving the Problems

[0006] One embodiment according to the present application is A system that An acquisition means for acquiring data including master data and task data related to a plan, which is represented by a table composed of rows and columns, A display means for displaying along a display logic by using first data indicating the relationship of data in the master data and task data related to the plan, and second data indicating the relationship between the master data and task data related to the plan and the data in the display logic, A computer program for operating as

[0007] Another embodiment according to the present application is wherein the system An acquisition step of acquiring data including master data and task data related to a plan, which is represented by a table composed of rows and columns, A display step of displaying along a display logic by using first data indicating the relationship of data in the master data and task data related to the plan, and second data indicating the relationship between the master data and task data related to the plan and the data in the display logic, A method for executing

[0008] Another embodiment according to the present application is An acquisition unit for acquiring data including master data and task data related to a plan, which is represented by a table composed of rows and columns, A display unit for displaying along a display logic by using first data indicating the relationship of data in the master data and task data related to the plan, and second data indicating the relationship between the master data and task data related to the plan and the data in the display logic, A system comprising

[0009] Another embodiment according to the present application is An acquisition unit for acquiring data including master data and task data related to a plan, which is represented by a table composed of rows and columns, A display control unit that causes display in accordance with display logic by using first data indicating the relationship of data in master data and task data related to a plan, and second data indicating the relationship between the master data and task data related to the plan and the data in the display logic. A cloud including the above.

Effect of the Invention

[0010] According to one embodiment of the present invention, planning can be more appropriately supported.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5A

Figure 5B

Figure 6A

Figure 6B

Figure 6C

Figure 6D

Figure 7A

Figure 7B

Figure 7C

Figure 8A

Figure 8B

Figure 8C

Figure 8D

Figure 9A

Figure 9B

Figure 10A

Figure 10B

Figure 10C

Figure 11A

Figure 11B

Figure 11C

Figure 11D

Figure 11E

Figure 11F

Figure 11G

Figure 12A

Figure 12B

Figure 12C

Figure 12D

Figure 12E

Figure 12F

Figure 12G

Figure 13A

Figure 13B

Figure 13C

Figure 13D

Figure 13E

Figure 13F

Figure 13G

Figure 14A

Figure 14B

Figure 15A

Figure 15B

Figure 15C

Figure 15D

Figure 15E

Figure 16A

Figure 16B

Figure 16C

Figure 16D

Figure 16E

Figure 17

Figure 18A

Figure 18B

Figure 19A

Figure 19B

Figure 20

Figure 21

Figure 22

Figure 23A

Figure 23B

Figure 23C

Figure 23D

Figure 23E

Figure 23F

Figure 24A

Figure 24B

Figure 24C

Figure 24D

Figure 24E

Figure 24F

Figure 25A

Figure 25B

Figure 25C

Figure 25D

Figure 26A

Figure 26B

Figure 26C

Figure 26D

Figure 26E

Figure 27A

Figure 27B

Figure 27C

Figure 27D

Figure 27E

Figure 28A

Figure 28B

Figure 28C

Figure 28D

Figure 28E

Figure 29A

Figure 29B

Figure 29C

Figure 29D

Figure 29E

Figure 30A

Figure 30B

Figure 30C

Figure 30D

Figure 30E

Figure 31A

Figure 31B

Figure 31C

Figure 31D

Figure 31E

Figure 32

Figure 33

[0012] 1. Summary An example of the technology disclosed in the present application is to use information processing technology to assist in planning.

[0013] As an example of the overall image including each hardware, for example, FIG. 1 can be cited. In this figure, the systems of each embodiment described in detail below correspond to the server or cloud 101. In the present specification, the term "system" may be composed of one or more information processing apparatuses. Further, the system may include a network connecting a plurality of information processing apparatuses. Further, the system may include one or more user terminals and / or administrator terminals in this figure.

[0014] The administrator terminals 102a and 102b are terminals for managing the system. They may have functions such as adjusting parameters regarding the functions provided by the systems of each embodiment described later and displaying the status of the system.

[0015] In this figure, two cases of the administrator terminal are shown, but it is not limited to two, and there may be one or more administrator terminals.

[0016] The user terminals 103a and 103b are terminals used by the users of the system. The user may be a person who examines a plan using this system. The user may input data related to the plan via the user terminal. The user terminal is provided with an input device and may input various data. For example, data related to master data, data related to task data, first data, and / or second data, etc. may be input. The user terminal may be provided with an output device. For example, the output device may be a display, and may display a display related to a violation of a constraint condition described later and a display of a change candidate. In this figure, two cases of the user terminal are shown, but it is not limited to two, and there may be one or more user terminals.

[0017] 2. Examples 2.1. Example 1 One example of the system may have some or all of the functions described in FIG. 2. For example, one example of the system may have a sheet data input unit, a view setting input unit, a data storage unit, a view logic storage unit, and a view output unit. Also, another example of the system may have a view setting input unit, a data storage unit, a view logic storage unit, and a view output unit. Also, another example of the system may have a view output unit. Also, another example of the system may have a sheet data input unit, a view setting input unit, and a data storage unit. Details of such functions will be described later. Also, the input / output relationships of the functions in FIG. 2 are as shown in FIG. 3.

[0018] Here, each function may obtain data in various ways. For example, each function may obtain data from the memory in the information processing device, may obtain data from the input device of the information processing, or may obtain data through receiving communication from another information processing device.

[0019] Next, the flow of one example of the system will be described from the perspective of a user of one example of the system using FIG. 4.

[0020] Here, an example in the following situation will be used. Consider developing a UI for scheduling operations for multi-variety, small-batch production, where multiple products are produced on one line in a chemical production plant. There may be a total of three production lines. The products that can be produced may include those specific to each line and those in common. For each production line, the amount that can be produced per hour for the same product may be the same or different. Each production line may be able to produce products while switching the products to be made. When switching the product on a certain line, it is necessary to stop production once and replace the production equipment, which requires preparation time. Since this preparation time varies depending on the combination of products before and after the switch, the production efficiency is different. Therefore, it is necessary to create an appropriate plan.

[0021] The functions used by the system in this example are as shown in Figure 4. Also, the data used by such functions are as shown in Figures 5A and 5B.

[0022] Step 1 The user first creates a plan. Specifically, master data related to the plan and task data related to the plan are prepared.

[0023] In this application document, the master data may be basic data. The master data may be, for example, data related to equipment, data related to utility costs, data related to products, etc. The data related to equipment may include, for example, if it is a production equipment, products that the production equipment can manufacture, the period required to produce the products, the raw materials required to produce the products and their quantities, the frequency of maintenance and the period of maintenance, etc. Also, the data related to equipment may include, if it is an inspection equipment, products that can be inspected, items that can be inspected, the period required for inspection, etc. Also, the data related to utility costs may include data on costs such as electricity bills, water bills, gas bills, steam bills, etc. Since the master data is the basic data of the equipment as described above, it is basically not changed, but it may be changed according to adjustments of the equipment, changes in fees, etc.

[0024] On the other hand, the task data may be data used according to the project. For example, it may be data on an order for a product from a client. For example, if there is an order to manufacture 100 lots of Product A, it may be data for manufacturing 100 lots of Product A. For example, it may be data such as putting X amount of raw material B and Y amount of raw material C into equipment Z to manufacture Product A.

[0025] Examples of master data include FIGS. 6A to 6D. FIG. 6A defines, as product master data, the relationships among product name, packaging form, and tons per unit. FIG. 6B defines the production line. FIG. 6C defines, as line product master data, the relationships among production line name, product name, packaging form, normal daily production tons, production tons on the stop day, and production tons on the restart day. Note that the production volume may differ depending on whether it is a day when the product is switched or a day when the product is not switched. In this figure, the normal daily production tons when there is no product switch, the day when production is stopped and switched to another product, and the day when production of another product is stopped and production of this product is started are defined separately. FIG. 6D defines, as line switch master data, the relationships among production line name, product name before switch, packaging form before switch, product name after switch, packaging form after switch, switchability, production volume on the day immediately before switch, and production volume on the day immediately after switch.

[0026] Also, examples of task data include FIGS. 7A to 7C. FIG. 7A defines, as a sales plan, sales date, product name, packaging form, tons, price per ton, customer, sales accuracy, and sales plan ID. FIG. 7B defines, as a production task, production start date, production end date, production line name, product name, packaging form, whether it is a fixed task, whether there is a first switch, and whether there is a last switch. FIG. 7C defines, as the initial inventory of the product, date, product name, packaging form, warehouse name, tons, and stock ID.

[0027] In addition, the user may prepare FIGS. 8A to 8D and FIGS. 9A to 9D in addition to such master data and task data.

[0028] Here, FIGS. 8A to 8D may define the relationship between the data and metadata in the master data and task data, which are used in the sheet data input section described in the following step 2 (in this application documents, it may also be referred to as the first data, and FIGS. 8A to 8D may be an example of the first data). As will be described later, the metadata may be, for example, IDs such as sheet (or table: s), column (field: f), and row (row: r). The first data may define the relationship between the data and these sheets, columns, and rows. For example, more specifically, as will be described later, the "product master" of the master data defines rows regarding product name, packaging form, and tons per unit (see FIG. 6), while the first data defines the structure of the "product master" regarding product name, packaging form, and tons per unit (see FIG. 8B). By doing so, the structure of the "product master" in the master data (FIG. 6) is utilized with the structure of the first data (FIG. 8B), and the sheet input section generates a sheet (FIG. 13B) associated with the metadata s2 (and the "product master" regarding columns (FIG. 11B) that may be included in such a sheet, where f9, f10, f11 are associated with each column as metadata, and the "product master" regarding rows (FIG. 12B) where r8 to r13 of the metadata are associated while being associated with f9, f10, and f11 of the columns). By the first data defining the structure including the variable names of such master data and task data, the system has the advantage of being able to handle the structure including the variable names of the master data and task data. Note that the first data itself may or may not include such metadata (f, s, r). Also, such first data may define the data type for the master data and task data. Such a data type may have a function of assigning a data type to the master data and task data prepared by the user. For example, in FIG. 8, a data type such as string or boolean is defined for each variable, and such a data type may be assigned to the variables in the master data and task data by the sheet input section.That is, even when a user uses master data and / or task data in a table with an arbitrary variable name and / or an arbitrary structure, when the relationship between the variable name and / or structure of such master data and / or task data is specified in the first data, a system in one example has the advantage of being able to be used for drawing by prepared view logic as described later by using such first data.

[0029] Also, FIGS. 9A to 9B may define the relationship between master data and task data and data in display logic, which are used in the view setting data input section described in the following step 3 (in this application document, it may also be referred to as second data, and FIGS. 9A to 9B may be an example of the first data). That is, by being able to define such a relationship by the second data, there is an advantage that any display logic (for example, display logic prepared in the past, display logic in another field, etc.) can be used. In particular, as described later, when display logic is used for a production plan related to a factory, such display logic can be used as it is, with few modifications, or with the concept of previously developed display technology, etc., in display logic for a shipping plan, which is a completely different field. Also, such second data may include a definition of a data type for master data and task data. Such a data type has a function of verifying the data type assigned to the master data and task data prepared by the user. In particular, where these data can be used within view logic, if the data types of these data are confirmed or error-handled within view logic, the view logic may become complicated. In step 3, by collectively checking the data types, there is significance in being able to reduce the confirmation and error handling within view logic.

[0030] Step 2 Next, a system in an example may create data associated with each other by one or more IDs from master data defined by such a table and task data defined by the table. Note that a system in an example may create a plurality of files having data associated with each other by these IDs.

[0031] For example, a sheet data input unit in a system in an example may acquire a table data group and a schema data group and generate a sheet data group. The table data group and the schema data group may be a file or an input from a user. The function of the sheet data input unit may be a function of receiving a table data group to be output as a UI from the outside and a schema data group that is schema data for the table data group, converting it into the format of sheet data, and saving it.

[0032] The function of the sheet data input unit is more specifically as shown in FIG. 10A. Here, the specific data type is as shown in FIGS. 10B and 10C. Note that the schema data group is as shown in FIGS. 8A to D, and the table data group is shown in FIGS. 6 and 7.

[0033] As a result, the sheet data input unit may generate FIG. 11 (field data group: fields(xls)), FIG. 12 (row data group: rows(xlsx)), and FIG. 13 (sheet data group: sheets(xlsx)). Specifically, it shows FIG. 11A (production task), FIG. 11B (product master), FIG. 11C (production line), FIG. 11D (line product master), FIG. 11E (line changeover master), FIG. 11F (initial inventory of products), FIG. 11G (sales plan), FIG. 12A (production task), FIG. 12B (product master), FIG. 12C (production line), FIG. 12D (line product master), FIG. 12E (line changeover master), FIG. 12F (initial inventory of products), FIG. 12G (sales plan), FIG. 13A (production task), FIG. 13B (product master), FIG. 13C (production line), FIG. 13D (line product master), FIG. 13E (line changeover master), FIG. 13F (initial inventory of products), FIG. 13G (sales plan). These sheet data groups (and the field data group and row data group included in the sheet data group) may include metadata (s) indicating sheets, metadata (f) indicating fields, and metadata (r) indicating rows.

[0034] If the user has prepared tables related by ID, this step may not be necessary. However, for users who have previously considered plans using Excel files, such tables have been used to manage device data and task data. Since these can be used to formulate plans with general business common sense without programming knowledge by sales staff, etc., it can be said that the display format has a low threshold for user understanding. One example system can use such widely used Excel files as input, so that users do not need to newly learn how to use the software, can easily formulate plans, and can enjoy the advantages of the example system described below. In particular, plans in factories, etc. (for example, production plans for producing chemicals from raw materials, inspection plans for chemicals, filling plans for chemicals, purchase plans for raw materials, etc.) have previously been considered using tables composed of matrices on Excel files (for example, Figures 6 and 7, etc.), so the convenience is extremely high if these tables can be used as they are.

[0035] Note that the sheet data output unit has a function of reading sheet data from the data storage unit, converting it into a table data group and a schema data group which is schema data for the table data group, and outputting it. The input is a sheet data group, the input destination is the data storage unit, the output is a table data group and a schema data group, and the output destination may be the user or a linked program.

[0036] Step 3 Next, one example system may perform a process of associating the data names in the drawing logic with the data names in the task data and mask data related to the plan.

[0037] For example, in one example system, the view setting data input unit receives view setting data that associates a sheet data group with a sheet association setting, converts it into view data, and saves it. The view setting data may be from a memory, a file, or an input from a user.

[0038] The function of the view setting data input unit is more specifically as shown in FIG. 14A. Here, the specific data type is as shown in FIG. 14B. Note that the view setting data input unit may generate a dependent sheet field data group ((view)DependSheetField(xlsx)), a dependent sheet data group ((view)DependSheet(xlsx)), and view data (View(xlsx)), and these data are as shown in FIGS. 15, 16, and 17 respectively. Here, FIGS. 15A (production task), 15B (product master), 15C (production line), 15D (line product master), 15E (line switching master) are shown, FIGS. 16A (production task), 16B (product master), 16C (production line), 16D (line product master), 16E (line switching master) are shown, and FIG. 17 (Gantt chart) is shown.

[0039] Note that the view setting data output unit has a function of converting view data into view setting data that associates a sheet data group with a sheet association setting and outputting it. The input is view data, the input destination is the data storage unit, the output is view setting data, and the output destination is the user or the screen.

[0040] In addition, the data storage unit has a function of inputting sheet data and view data and storing them in a database, or a function of reading sheet data and view data from the database and outputting them. Here, when inputting, the input is sheet data and view data, and the input sources thereof may be a sheet data input unit, a view data input unit, a sheet data editing unit, a view output unit, and a view data editing unit. Also, when outputting, the output is sheet data and view data, and the output destinations may be a sheet data output unit, a view data output unit, a view data editing unit, a sheet data editing unit, and a UI input data processing unit.

[0041] In addition, the view logic storage unit has a function of storing the logic, created by a developer, that has requirements for a necessary group of sheet data and outputs a UI, and the view logic. The output may be the view logic. Examples of the view logic may be those listed in FIG. 18A, and other examples may be those listed in FIG. 18B.

[0042] An example system has an advantage that by performing the process of associating the data name in the drawing logic with the data names in the task data and mask data related to the plan in this step 3, the names used in the drawing logic and the data names in the task data and mask data related to the plan can be freely set.

[0043] That is, when adding new user interfaces or modifying user interfaces and using the user interface with names corresponding to data input and output, it was necessary to develop both the data input / output section and the user interface section. In particular, when a user uses a plan in a table in a familiar environment such as an Excel file and freely sets the sheet name, field names of the table, etc., or freely changes the structure of the table, it is necessary to similarly change the name of the drawing software of the user interface in response to these changes (for example, if not only the name but also the matrix and relationship of the table are changed, it means that the data structure is changed, so the drawing program also needs to be changed and modified from the perspective of data access). In particular, when formulating a factory plan, the user may make repeated plan changes from the perspectives of quality improvement and mass production efficiency when designing a new chemical product (for example, new settings for temperature control, changes in the location of storage facilities, changes in manufacturing equipment, changes in the lanes of manufacturing equipment, and consideration of chemical reaction variations). Since the plan also needs to be changed in response to these changes, it was previously necessary to change the drawing software each time.

[0044] In contrast, in one example of a system, when performing the process of associating the data name in the drawing logic with the data names in the task data and mask data related to the plan, even if the user freely uses the plan in a table in a familiar environment such as an Excel file and freely sets the sheet name, field names of the table, etc., or freely changes the data structure, there is an advantage that the drawing logic can be used with only the burden of changing the association (for example, the first data and the second data) between the data name in the drawing logic and the data names in the task data and mask data related to the plan.

[0045] Step 4 Next, one example of a system may perform drawing processing based on view logic.

[0046] For example, the view output unit of a system in one example may display a list of saved view data and actually output the view to the screen based on the view data selected by the user. Also, when multiple view data are saved, it may be possible to switch the view to be displayed. The sheet data described in the view data may be displayed in the view. Also, operations on the view may be reflected in the sheet data described in the view data. Further, changes to the sheet data may be reflected on the screen.

[0047] The view output unit of a system in one example may obtain the sheet data and view data saved in the data storage unit and the view logic saved in the view logic storage unit, and output them to the UI input data of the view output unit.

[0048] Also, as an example of the specific procedure in the view output section, the example for reading is shown in FIG. 19A, and the example for writing is shown in FIG. 19B. One example of the system may use view logic for drawing. Here, the view logic itself may be prepared by the user or by the system developer himself / herself. One example of the system obtains and uses such prepared view logic, and can draw along with the view logic by using the first data and / or the second data to handle the differences in variable names and structures between the view logic and the master data and / or task data prepared by the above-mentioned user. Note that in addition to preparing the master data and task data related to the above-mentioned plan, the user may also prepare the first data, the second data, and the view logic. In this case, the user needs to prepare the first data and the second data to adjust the variable names and data structures between the view logic and the master data and task data related to the plan after understanding the variable names and data structures used in the view logic. However, even in this case, there is an advantage that the burden of changing the inside of the view logic in response to the change of the master data and task data related to the plan is reduced. On the other hand, the user only needs to prepare the master data and task data related to the above-mentioned plan, and does not need to prepare the first data, the second data, and the view logic. In this case, developers other than the user need to prepare the first data, the second data, and the view logic. Even in this case, there is no need to change the view logic in response to the change of the master data and task data related to the user's plan. Simply changing the first data and the second data is sufficient, so there is an advantage that the development burden of the view logic is reduced and reuse can be promoted. In particular, as will be described later in this application document, for example, the view logic used for the Gantt chart display in the plan related to a factory can be used (or used with a reduced change burden) as the view logic for the same Gantt chart display in the plan related to shipping in a different field.

[0049] Here, two examples of a part of it will be described.

[0050] 2.1.1. Drawing Example 1 Suppose there is an instruction in the view logic to "draw all row data with the column named key=line_name in the sheet with key=lines as a system".

[0051] In this case, a sample system reads the data of "the sheet with key=lines, which further has the column named key=line_name" by loading the instructions within the following view logic.

[0052] const demoPlantlinesDependSheet = { key: "lines", displayName: "Production Line", dependSheetFields: [ { key: "line_name", displayName: "Line Name", type: "string",}, ],};

[0053] Furthermore, a sample system, in this case, uses the following sheet data, field data, and row data groups to obtain the data of "read the sheet with id s3. The required column is the field f12". Here, it may be specified by being associated with lines and line_name.

[0054] And a sample system may draw the strings L01 and L02 described in r14 and r15 as a system along the view logic based on the received data.

[0055] ·Sheet data TIFF2025109369000002.tif21169

[0056] ·Field data TIFF2025109369000003.tif23159

[0057] ·Row data groups TIFF2025109369000004.tif26155

[0058] The example actually drawn here may be as follows. TIFF2025109369000005.tif20150

[0059] 2.1.2. Drawing Example 2 In view logic, assume that there is an instruction for each row that "prepare a Gantt chart at the location of line_name during the period from date_produce_start to date_produce_end, display product_name and packing_type as characters, change the key mark according to the value of is_locked, and determine the shape and color of the tip and end of the Gantt according to the values of is_switch_occured_first and is_switch_occured_end".

[0060] In this case, first, a system of an example reads the following definitions.

[0061] const demoPlantTasksDependSheet = { key: "tasks", displayName: "Tasks", dependSheetFields: [ { key: "date_produce_start", displayName: "Task start date", type: "date",}, { key: "date_produce_end", displayName: "Task end date", type: "date",}, { key: "line_name", displayName: "Production line name", type: "string",}, { key: "product_name", displayName: "Product name", type: "string",}, { key: "packing_type", displayName: "Packaging type name", type: "string",}, { key: "is_locked", displayName: "Lock setting", type: "boolean",}, { key: "is_switch_occured_first", displayName: "Start date switch", type: "boolean",}, { key: "is_switch_occured_last", displayName: "End date switch", type: "boolean",}, ],};

[0062] Furthermore, in this case, one example of the system uses the following sheet data, field data, and the row data group in FIG. 20 to obtain the corresponding sheet data, field data, and row data, draw tables and field names, etc. Then, one example of the system Based on the received data with key = line_products, for each row, numbers can be drawn as the production tons for the normal production date, stop date, and restart date from line_name, product_name, and packing_type. Based on the received data with key = line_switches, for each row, numbers can be drawn as the production tons for the corresponding switch date based on the product and packaging type name.

[0063] · Sheet data TIFF2025109369000006.tif21169

[0064] · Field data group TIFF2025109369000007.tif62170

[0065] An example depicted in the above Examples 1 and 2 is shown in FIG. 21. In this figure, line L1 indicates that A01 is manufactured on the 1st to 3rd days (however, since the 3rd day includes a switch, the production volume on the 3rd day is less at 20t compared to the daily production volume of 33t on the 1st and 2nd days), and A02 is manufactured from the 4th to 17th days (however, the production volume on the 4th and 17th days is less at 20t due to the switch, while the daily production volume from the 5th to 16th days is 33t). Here, the user may be able to change the switch between A01 and A02 on line L01 (between the 3rd and 4th days) at the input means. For example, on the touch panel, the end part (right end part) of A01 and / or the start part (left end part) of A02 may be moved along the left and right of line L1. Besides the touch panel, this location may be moved along the left and right by a mouse or other pointing functions. The end part (right end part) of this A01 corresponds to the fact that date_produce_end with id r1 in FIG. 20 indicates April 3, and the start part (left end part) of A02 This corresponds to the fact that in FIG. 20, date_produce_start with id r5 indicates April 4th. And due to the association of the above second data, the variables in the display logic and the data in the data storage unit associated by the metadata are associated with each other. Therefore, the left - right movement of the end part (right end part) of the above A01 corresponds to the increase or decrease of the date (April 3rd) of date_produce_end with id r1 in FIG. 20, and the left - right movement of the head part (left end part) of A02 corresponds to the increase or decrease of the date (April 4th) of date_produce_start with id r5 in FIG. 20. Furthermore, the data associated through the metadata in such a data storage unit is also associated with the master data and / or task data used by the user due to the relationship of the first data. Correspondingly, the planned dates (the manufacturing end date of A01 and the manufacturing start date of A02) are also associated and changed. In this way, by changing the numerical values on the interface displayed by the display logic, the master data and / or task data prepared by the user may also be variable. Due to such two - way interactive data fluctuations, the user has the advantage that they can adjust the displayed content and also adjust the original plan.

[0066] 2.2. Example 2 In addition to part or all of the system of Example 1, the system of Example 2 may further include a view data editing unit and a sheet data editing unit.

[0067] FIG. 22 illustrates the functions including such a view data editing unit and a sheet data editing unit.

[0068] The sheet data editing unit may take the data storage unit as the input source, take the sheet data group as the input, and take the data storage unit as the output destination to output the sheet data group. The sheet data editing unit may enable the addition, deletion, and editing of the rows of table data. Also, the sheet data editing unit may add, delete, and edit the schema data.

[0069] FIG. 23A is an example of the sheet data displayed by the sheet data editing unit. Here, the display name, name may refer to the sheet data. Also, the column names may display the field data in the sheet data, and the rows may display the row data in the sheet data.

[0070] FIG. 23B is an example of a screen that displays details of a sheet to be edited by the sheet data editing unit. In this figure, an example is shown where the display name (production task), variable name (task_schedule), summary, etc. are marked. FIG. 23C is an example of adding field data displayed by the sheet data editing unit. Also, FIG. 23D is an example of editing or deleting field data displayed by the sheet data editing unit.

[0071] FIG. 23E is an example of a display for selecting view logic displayed by the view data editing unit. FIG. 23F is an example of a screen for setting reference data displayed by the view data editing unit. That is, the view data editing unit may be able to set the association between the master data and task data related to the plan by the user and the data in the view logic. In this figure, an example is shown where the user associates "production line", "cost per day during stoppage (in thousands of yen)", "presence of parallel lines", "line name", "system", "task", "task end date", "task start date" in the master data and task data related to the plan with "production line", "line stoppage cost / day", "is there a parallel line", "production line name", "parallel line group", "production task", "production end date", "production start date" in the view logic, respectively.

[0072] For example, the topmost menu in the frame (here, "Production Line") may be the setting of dependent sheet data, the title may be the displayName of dependSheet in view logic, and the pull-down options may be a list of sheet data that exists in the content. The selected sheet may be written as the dependent sheet of view data. Also, the second menu in the frame (here, the menu after "Cost per Day during Stoppage (in thousands of yen)") may be the setting of dependent sheet field data. The title may be the displayName and type of dependSheetFields in view logic, and the pull-down options may be a list of field data that the sheet data set as dependent sheet data has. The selected field data may be written as the dependent sheet field data of view data.

[0073] Note that the type of each field data is also displayed in the pull-down of field data in the association, and options with inconsistent types are invalidated. Therefore, there is an advantage that associations can be made between data with matching data types.

[0074] 2.3. Example 3 Examples 1 and 2 explained examples related to plans such as production, inspection, filling, and purchasing in factories and the like, but they may also be applicable to examples of other plans. For example, in a shipping plan regarding which ship to move the cargo to which port at what timing, an example system may be applicable. Conventionally, on an Excel file, plans have been considered using a table composed of rows and columns. Therefore, in such a shipping plan as well, the system of this example may be applied in the same manner as in Examples 1 and 2.

[0075] FIG. 24 is an example of master data and / or task data prepared by a user in relation to a ship allocation plan. Here, FIG. 24A shows tasks. The fields in this figure are partial, and the fields in this figure may have, for example, amount, date_arrival_loading_port, date_arrival_unloading_port, date_departure_loading_port, date_laycan_end, date_laycan_start, date_loading_end, date_loading_start, date_task_end, date_task_start, date_unloading_end, dadte_unloading_start, days_loading, days_task, days_to_loading_port, days_to_unloading_port, days_unloading, is_fixed, loading_port_id, loading_port_name, material_id, material_name, ship_id, ship_name, ship_speed_level, source_unloading_port_id, source_unloading_port_name, task_id, task_kind, unloading_port_id, unloading_port_name. FIG. 24B shows ships. FIG. 24C shows port_distances. FIG. 24D shows plant_schedules. FIG. 24E shows plants. FIG. 24F shows materials.

[0076] FIG. 25 may be an example of first data in the ship allocation plan. Further, FIG. 26 may be an example of second data in the ship allocation plan.

[0077] FIG. 27 is an example of a sheet data group generated by the sheet input unit using the relationship of the first data in FIG. 25 with respect to the master data or task data in FIGS. 24A to 24F (sheets.xlsx). More specifically, FIG. 27A may be a tasks sheet. FIG. 27B may be a ships sheet. FIG. 27C may be a port_distance sheet. FIG. 27D may be a plants sheet. FIG. 27E may be a materials sheet. Note that such a sheet data group may include FIG. 28 of field.xlsx and FIG. 29 of row.xlsx. FIGS. 28A and 29A may be tasks sheets. FIGS. 28B and 29B may be ships sheets. FIGS. 28C and 29C may be port_distances sheets. FIGS. 28D and 29D may be plants sheets. FIGS. 28E and 29E may be materials sheets.

[0078] In the shipping plan, the view setting data input unit may use a dependent sheet data group ((view) DependSheet (xlsx) in FIG. 30), a dependent sheet field data group ((view) DependSheetField (xlsx) in FIG. 31), and view data (View (xlsx) in FIG. 32). More specifically, FIGS. 30A and 31A may be tasks. FIGS. 30B and 31B may be ships. FIGS. 30C and 31C may be port_distances. FIGS. 30D and 31D may be plants. FIGS. 30E and 31E may be materials.

[0079] With the above configuration, an example system may be applicable to the shipping plan.

[0080] 3. About Various Embodiments The computer program according to the first aspect is " A system, an acquisition means for acquiring data including master data and task data related to a plan, which is represented by a table composed of rows and columns, Display means for displaying in accordance with display logic using first data indicating the relationship between data and metadata in master data and task data related to a plan, and second data indicating the relationship between master data and task data related to a plan and data in display logic. It is a "computer program for operating as".

[0081] The computer program according to the second aspect is the same as that in the first aspect, " The second data includes data indicating the relationship between the fields in the table and the column and the tables and fields used in the display logic."

[0082] The computer program according to the third aspect is the same as that in the first aspect or the second aspect, " The configuration displayed by the display means includes an input reception element, For the system, Rewriting means for rewriting the task data corresponding to the input to the input reception element." It further operates as".

[0083] The computer program according to the fourth aspect is the same as that in any one of the first to third aspects, " The first data indicating the relationship between the data in the master data and task data related to the plan includes the structural relationship of the data in the master data and task data related to the plan, Using the structural relationship, a relationship is generated between the data in the master data and task data related to the plan and metadata indicating a table, a column, or a row."

[0084] The computer program according to the fifth aspect is the same as that in any one of the first to fourth aspects, " The data type in the first data is used to assign a data type to the mask data and task data related to the plan."

[0085] The computer program according to the sixth aspect is, in any one of the first to fifth aspects, " The data type in the second data is used for verifying the data types of the mask data and the task data related to the plan."

[0086] The computer program according to the seventh aspect is, in any one of the first to sixth aspects, " In the case where the plan is a production plan, the input reception element includes data indicating a production device, a production line, a product to be produced, a production start date, a production end date, and / or a product inventory transition."

[0087] The computer program according to the eighth aspect is, in any one of the first to seventh aspects, " In the case where the plan is a shipping plan, the input reception element includes data indicating a ship to be shipped, the cargo of the ship to be shipped, a rake can start date, a rake can end date (the necessity of bringing coal within the contract period), an outbound departure date of the shipping, an outbound arrival date of the shipping, a return departure date of the shipping, and / or a return arrival date of the shipping."

[0088] The computer program according to the ninth aspect is, in any one of the first to eighth aspects, " The system First editing means capable of editing the relationship related to the first data For operating as"

[0089] The computer program according to the tenth aspect is, in any one of the first to ninth aspects, " The system Second editing means capable of editing the relationship related to the second data For operating as"

[0090] The method according to the eleventh aspect is, " When the system An acquisition step of acquiring data including master data and task data related to a plan, which is represented by a table composed of rows and columns. A display step of displaying along a display logic by using first data indicating the relationship of data within the master data and task data related to the plan, and second data indicating the relationship between the master data and task data related to the plan and the data within the display logic. A method of executing.

[0091] The method according to the twelfth aspect is, in the eleventh aspect, " The system includes a memory."

[0092] The system according to the thirteenth aspect is " An acquisition unit that acquires data including master data and task data related to a plan, which is represented by a table composed of rows and columns. A display unit that displays along a display logic by using first data indicating the relationship of data within the master data and task data related to the plan, and second data indicating the relationship between the master data and task data related to the plan and the data within the display logic. A system including the above."

[0093] The system according to the fourteenth aspect is, in the thirteenth aspect, " The system includes a memory."

[0094] The cloud according to the fifteenth aspect is " An acquisition unit that acquires data including master data and task data related to a plan, which is represented by a table composed of rows and columns. A display control unit that causes to display along a display logic by using first data indicating the relationship of data within the master data and task data related to the plan, and second data indicating the relationship between the master data and task data related to the plan and the data within the display logic. A cloud including the above."

[0095] The cloud according to the 16th aspect is the one in which, in the 15th aspect, " the cloud includes a memory".

[0096] 4. Information Processing Apparatus The mobile terminal, server, or cloud used in the above system may be composed of one or more information processing apparatuses. As shown in FIG. 33, the information processing apparatus 10 may have a bus 11, an arithmetic unit 12, a storage device 13, an input device 14, a display device 15, and a communication IF 16. Further, the information processing apparatus 10 may be directly or indirectly connected to other information processing apparatuses via a network 19. Further, the information processing apparatus 10 may be connected to a database (not shown). Further, the database may be included in the information processing apparatus 10.

[0097] The bus 11 may have a function of transmitting information among the arithmetic unit 12, the storage device 13, the input device 14, the display device 15, and the communication IF 16.

[0098] Examples of the arithmetic unit 12 include, for example, a processor. This may be a CPU or an MPU. Further, it may have a graphics processing unit, a digital signal processor, etc. In short, the arithmetic unit 12 may be any device that can execute program instructions.

[0099] The storage device 13 is a device for recording information. This may be either an external memory or an internal memory, and may be either a main memory or an auxiliary memory. Further, it may be a magnetic disk (hard disk), an optical disk, a magnetic tape, a semiconductor memory, etc. Further, it may have a storage device via a network or a storage device on a cloud via a network.

[0100] Registers, L1 caches, L2 caches, etc., which store information at a location close to the arithmetic unit, may be included within the arithmetic unit 12 in the schematic diagram of this figure. However, in the design of computer architecture, the storage device 13 may include these as devices for recording information. In short, it is sufficient that the arithmetic unit 12, the storage device 13, and the bus 11 are configured to cooperate to execute information processing.

[0101] The storage device 13 can be provided with a program for executing functions related to the present invention. Also, it can appropriately record data necessary for executing functions related to the present invention.

[0102] Also, the above describes the case where the arithmetic unit 12 is executed based on a program provided in the storage device 13. However, as one form of the combination of the above bus 11, arithmetic unit 12, and storage device 13, the information processing related to this system may be realized by a programmable logic device capable of changing the hardware circuit itself or a dedicated circuit with determined information processing to be executed.

[0103] The input device 14 is for inputting information, but it may have other functions. Examples of the input device 14 include pointing devices such as a keyboard, a mouse, a touch panel, or a pen-type pointing device.

[0104] The display device 15 has, for example, a display, but it may have other functions. Also, the display device 15 may be a liquid crystal display, a plasma display, an organic EL display, etc. In short, any device capable of displaying information may be used. Also, it may partially include the input device 14 like a touch panel.

[0105] Network 19 transmits information together with communication IF 16. That is, it has a function that enables information of information processing device 10 to be transmitted to other information terminals 18 via the network. Communication IF 16 may be in any connection format, such as USB, IEEE 1394, Ethernet (registered trademark), PCI, SCSI, etc. Network 19 may be either wired or wireless, and may use an optical fiber, a coaxial cable, an Ethernet cable, etc.

[0106] In this figure, it has been described as one information processing device 10, but information processing device 10 may be composed of a plurality of information processing devices. The plurality of information processing devices may be connected internally or externally. Also, when information processing device 10 is composed of a plurality of information processing devices, their owners may be different. Also, the person operating information processing device 10 as the system according to the present invention may be different from the owner of information processing device 10.

[0107] Also, in the description of each embodiment in this application document, what has been described as system processing may be processed by one or more servers, the cloud, or one or more servers and the cloud.

[0108] It goes without saying that the invention examples described in the embodiments of this application document are not limited to those described in this application document, and can be applied to various examples within the scope of its technical idea. Also, in this application document, display logic may also be referred to as view logic. Also, a table may be composed of one or more columns and one or more rows. Data indicating a table may directly indicate the table itself or may indirectly indicate the table. For example, when there is one table in one sheet on an Excel file, such a sheet may indicate one table within that sheet. The sheet of the figure in this application may, in this sense, indicate the table within such a sheet by the data indicating the sheet.

[0109] In addition, the processes and procedures described in the present application documents may be realized not only by those explicitly described in the embodiments but also by software, hardware, or a combination thereof. Further, the processes and procedures described in the present application documents may be implemented as a computer program and executed on various computers. For example, the processes and procedures for realizing the systems of the above-described embodiments may be implemented as a computer program and executed on various computers. Also, these computer programs may be stored in a storage medium. Further, these programs may be stored in a non-transitory storage medium.

Claims

1. A system, an acquisition means for acquiring data including master data and task data related to a plan, which are represented by a table composed of rows and columns, a display means for displaying along a display logic by using first data indicating the relationship of data in the master data and task data related to the plan, and second data indicating the relationship between the master data and task data related to the plan and the data in the display logic, a computer program for operating as.

2. The second data includes data indicating the relationship between data indicating a table, columns, and rows in the master data and task data related to the plan, and data indicating a table, columns, and rows used in the display logic. The computer program according to claim 1.

3. The configuration displayed by the display means includes an input reception element, The system, a rewriting means for rewriting the task data in response to an input to the input reception element, The computer program according to claim 1 or 2 for further operating as.

4. The first data indicating the relationship of data in the master data and task data related to the plan includes the structural relationship of data in the master data and task data related to the plan, generating an association between data in the master data and task data related to the plan and metadata indicating a table, column, or row by using the structural relationship, The computer program according to claim 1 or 2.

5. The data type in the first data is used to assign a data type to the mask data and task data related to the plan. The computer program according to claim 1 or 2.

6. The data type in the second data is used for verifying the data type of the mask data and task data related to the plan. The computer program according to claim 1 or 2.

7. When the plan is a production plan, the input reception element includes data indicating a production device, a production line, a product to be produced, a production start date, a production end date, and / or the inventory transition of the product. The computer program according to claim 3.

8. In the case where the plan is a shipping plan, the input reception element includes data indicating the ship to be shipped, the cargo of the ship to be shipped, the start date of the laycan, the end date of the laycan (the necessity of bringing coal within the contract period), the outbound departure date of the shipping, the outbound arrival date of the shipping, the return departure date of the shipping, and / or the return arrival date of the shipping. The computer program according to claim 3.

9. The system The first editing means capable of editing the relationship related to the first data The computer program according to claim 1 or 2 for operating as

10. The system The second editing means capable of editing the relationship related to the second data The computer program according to claim 1 or 2 for operating as

11. The system An acquisition step of acquiring data including master data and task data related to a plan, which are represented by a table composed of rows and columns; A display step of displaying along a display logic using first data indicating the relationship of data within the master data and task data related to the plan, and second data indicating the relationship between the master data and task data related to the plan and the data within the display logic; A method of executing.

12. The system includes a memory The method according to claim 11.

13. An acquisition unit that acquires data including master data and task data related to a plan, which are represented by a table composed of rows and columns; A display unit that displays along a display logic using first data indicating the relationship of data within the master data and task data related to the plan, and second data indicating the relationship between the master data and task data related to the plan and the data within the display logic; A system comprising.

14. The system includes a memory The system according to claim 13.

15. An acquisition unit that acquires data including master data and task data related to a plan, which are represented by a table composed of rows and columns; A display control unit that causes to display along a display logic using first data indicating the relationship of data within the master data and task data related to the plan, and second data indicating the relationship between the master data and task data related to the plan and the data within the display logic; A cloud comprising.

16. The cloud includes a memory The cloud according to claim 15.

Images