JP2017120453A - Plan management system, method, and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a plan management system, a method, and a recording medium with which comparison between a plurality of objects can be easily performed in terms of Gantt chart display of a production plan.SOLUTION: A plan management system 301 for managing a plan holds display attribute information on a plan screen including at least one or more of the size of the plan screen, display position of a Gantt chart, display range of the Gantt chart, order of the vertical axis elements of the Gantt chart, and information identifying work elements of the Gantt chart, stores the display attribute information in attribute holding means 307, and reflects the display attribute information held in the attribute holding means to the plan screen.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a plan management system for managing a production plan at a manufacturing site.

  Conventionally, at a manufacturing site, a production plan of a product to be manufactured in a predetermined period such as a monthly unit or a daily unit is created, and manufacturing is performed according to the production plan. In general, the production plan is expressed by a Gantt chart that represents which manufacturing apparatus and which worker are used from when to when to manufacture a certain group of products.

  There are various production plan creation methods, for example, a backward method and a forward method. The backward method is a method of allocating work so that the order can meet the delivery date, going back from the delivery date of the order. On the other hand, the forward method is a method of assigning orders in order from the manufacturing start time.

  When a production site manager creates a production plan, he or she tries to create an optimal production plan according to the situation at that time, such as the operating status of the manufacturing apparatus and the worker's office status. In this trial, it is necessary to compare production plans in order to determine which parameters will change to produce a more appropriate production plan, or which production plan to use among multiple production plans. Become. At this time, for example, in the production plan created by the backward method, orders are concentrated near the delivery time, so the display range of the Gantt chart is around the delivery time. On the other hand, in the production plan created by the forward method, orders are concentrated near the manufacturing start time, so the display range of the Gantt chart is near the manufacturing start time.

  As described above, since the display position and display range of the Gantt chart differ depending on the production plan creation method, the administrator has to adjust the display position and display range of the Gantt chart each time the comparison is performed so that the comparison is easy.

  As a method for facilitating comparison of a plurality of screens, there is a technique disclosed in Patent Document 1. The technique disclosed in Patent Document 1 is a technique for automatically scrolling the second screen so that the object corresponding to the object on the first screen is always displayed on the second screen. According to this technique, it is possible to always display an object to be compared on both screens.

JP 2008-52621 A

  However, if the production plan creation method is changed, the production order of orders is often different. For this reason, when the prior art is used for comparison of production plans, for example, when the display position of the first Gantt chart is scrolled in the time axis direction, the display position of the second Gantt chart is frequently scrolled. This makes it difficult to compare.

  Then, an object of this invention is to provide the plan management system and method and recording medium which make the comparison of a some target object easy in view of the said subject.

In order to achieve the above object, the plan management system according to the present invention provides:
Attribute holding means for holding display attribute information of the planning screen;
Attribute storage means for storing display attribute information in the attribute holding means;
And an attribute reflecting means for reflecting the display attribute information held by the attribute holding means on the plan screen.

  According to the plan management system concerning the present invention, a plurality of objects can be easily compared.

The figure which shows the example of the hardware constitutions of the plan management system which concerns on this invention, and a logical structure The figure which shows the example of the hardware constitutions of the management server which concerns on this invention The figure which shows the example of the flow of the whole process in the plan management system concerning this invention The figure which shows the example of the management screen of the plan management system which concerns on this invention The figure which shows the example of the flow of the plan display process of the plan management system which concerns on this invention The figure which shows the example of the plan screen of the plan management system which concerns on this invention The figure which shows the example of the flow of the various processes in the plan management system which concerns on this invention The figure which shows the example of the display attribute information in the plan management system which concerns on this invention

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

[First embodiment]
In the first embodiment, an example will be described in which comparison of plans is facilitated by duplicating the display attribute of the first plan screen on the second plan screen.

  A first embodiment to which the present invention is applied will be described below.

<Hardware configuration of printing system>
FIG. 1A shows a hardware configuration of the plan management system in the present embodiment.

  In FIG. 1A, reference numeral 101 denotes a manufacturing site for manufacturing a product. A management server and a manufacturing apparatus, which will be described later, are installed, and an administrator or a worker performs a manufacturing action here to manufacture the product. Reference numeral 102 denotes a management server that operates the plan management system. Details of the management server will be described later. Reference numeral 103 denotes a manufacturing apparatus for manufacturing a product.

<Hardware configuration of management server>
Next, the hardware configuration of the management server will be described with reference to FIG.

  In FIG. 2, 201 is a central control unit that reads, interprets, and executes a computer program stored on a storage device 206 (to be described later) and controls a later-described RAM 203 and display 204 connected to the bus via a bus 209 (to be described later). It is an arithmetic processing unit (CPU: Central Processing Unit). A read only memory (ROM) 202 performs input / output control at a low level with hardware connected to the bus. Reference numeral 203 denotes a random access memory (RAM) that temporarily stores information when the CPU 201 calculates. Reference numeral 204 denotes a display for displaying a calculation result by the CPU.

Reference numeral 205 denotes a keyboard that receives input from the user. However, in the case where the terminal is a smart device, the keyboard 205 does not have to be attached since it includes a touch panel. Reference numeral 206 denotes a storage device that stores programs and data used for calculation.
Reference numeral 207 denotes a network I / F (I / F: interface) connected to a network such as a local network, an intranet, or the Internet. Reference numeral 208 denotes a pointing device such as a mouse or a trackball that accepts coordinates designated by the user on the screen. A bus 209 is a signal line to which the CPU 201 to the pointing device 208 are connected.

  Since the hardware configuration of the management server is not a main requirement of the present invention, a detailed description thereof will be omitted.

<Logical configuration of the plan management system>
Next, the logical configuration of the plan management system in this embodiment will be described with reference to FIG.

  Reference numeral 301 denotes a plan management system in the present embodiment. A control unit 302 controls the entire plan management system. A display unit 303 displays a management screen and a plan screen described later. An input unit 304 receives an instruction from the administrator. Reference numeral 305 denotes a plan information holding unit that holds information for calculating a production plan such as capability information of a manufacturing apparatus and an operation day of a production site (hereinafter, plan information) and information related to an order.

  A planning unit 306 calculates a production plan. Reference numeral 307 denotes an attribute holding unit that holds information related to the display of the plan screen (hereinafter, display attribute information). Reference numeral 308 denotes an attribute storage unit that stores display attribute information in the attribute storage unit. Reference numeral 309 denotes an attribute reflection unit that reflects display attribute information on the plan screen. A history holding unit 310 holds a history of display attribute information. Reference numeral 311 denotes a reflection cancellation unit that cancels reflection of display attribute information. Reference numeral 312 denotes a buffer memory that holds information being calculated.

<Overall process flow in the plan management system>
Next, the overall processing flow in the plan management system will be described with reference to FIG.

  In step S <b> 101, the control unit 302 displays a management screen for inputting / outputting information with the administrator on the display unit 303.

  Here, the management screen will be described with reference to FIG. In FIG. 4, 401 is a management screen of the plan management system. Reference numeral 402 denotes an order reading button for reading an order. Reference numeral 403 denotes a plan creation button for creating a plan. Reference numeral 404 denotes a plan display button for displaying a plan. Reference numeral 405 denotes a close button for ending the plan management system.

  In step S102, the control unit 302 waits for an input from the administrator.

  In step S103, the control unit 302 determines whether there is an order reading instruction. If there is an instruction, the control unit 302 proceeds to step S104, and if there is no instruction, the process proceeds to step S109.

  In step S <b> 104, the control unit 302 displays an order selection screen (not shown) and accepts an order from the administrator and designation of plan information. Specifically, the control unit 302 reads the order and plan information from the plan information holding unit 305 and displays the list on the order selection screen. The order selection screen includes a list of orders, a list of plan information, and a determination button, and can accept selection of an order and plan information from the administrator and pressing of the determination button. When the control unit 302 receives the pressing of the determination button, the control unit 302 acquires data corresponding to the order selected by the administrator and the plan information from the plan information holding unit 305 and writes the data in the buffer memory 312.

  In step S105, the control unit 302 determines whether there is a plan creation instruction. If there is an instruction, the control unit 302 proceeds to step S106, and if there is no instruction, the process proceeds to step S107.

  In step S <b> 106, the control unit 302 creates a plan based on the read order and plan information, and writes the plan in the buffer memory 312. In the present embodiment, a pile-up method is used as a plan creation method. However, the plan creation method is not limited to this. For example, a linear programming method or a combinational optimization method may be used, and any creation method may be used as long as the plan can be created. Since the plan creation method is not the main requirement of the present invention, a detailed description is omitted.

  In step S107, the control unit 302 determines whether there is a plan display instruction. If there is an instruction, the control unit 302 proceeds to step S108, and if there is no instruction, the process proceeds to step S109.

  In step S108, the control unit 302 displays the plan on the plan screen in a Gantt chart format. Details of the plan display process will be described later with reference to FIG.

  Here, the plan screen will be described with reference to FIG.

  In FIG. 6A, reference numeral 501 denotes a plan screen. Reference numeral 502 denotes a Gantt chart. Reference numeral 503 denotes a resource column for displaying resources related to manufacturing such as manufacturing apparatuses and workers. Reference numeral 504 denotes a plan column that indicates from when to when the work corresponding to the order is performed. Reference numerals 505 to 509 denote printing operations corresponding to orders 1 to 5, respectively. Reference numerals 510 to 514 denote cutting operations corresponding to orders 1 to 5, respectively. Reference numeral 515 denotes a scroll bar for controlling the vertical display position of the Gantt chart. Reference numeral 516 denotes a scroll bar for controlling the horizontal display position of the Gantt chart. Reference numeral 517 denotes a close button for closing the plan screen. The example of FIG. 6A is a result of planning orders 1 to 5 by the forward method. Printing operations corresponding to orders 1 to 5 are planned in order from 9:00, and then orders 1 to 5 are handled. Cutting operations are planned in order.

  In step S109, the control unit 302 determines whether there is an instruction to close the screen. If there is an instruction, the process proceeds to step S110, and if there is no instruction, the process returns to step S102.

  In step S110, the control unit 302 closes the opened screen and ends the process.

<Plan display process flow>
Next, the flow of the plan display process will be described with reference to FIG.

  In step S201, the control unit 302 refers to the display attribute holding unit 307 and acquires the display attribute information when the display attribute information is held. If not, the initial value is acquired. Details of the display attribute information will be described later.

  In step S202, the control unit 302 acquires the plan written in the buffer memory 312 and creates and displays a plan screen.

  In step S203, the control unit 302 waits for an input from the administrator.

  In step S204, the control unit 302 determines whether there is an instruction to change the display position of the Gantt chart. If there is an instruction, the process proceeds to step S205, and if there is no instruction, the process proceeds to step S206.

  In step S205, the control unit 302 changes the display position of the Gantt chart. The change of the Gantt chart display will be described later.

  In step S206, the control unit 302 determines whether there is an instruction to change the display range of the Gantt chart. If there is an instruction, the process proceeds to step S207, and if there is no instruction, the process proceeds to step S208.

  In step S207, the control unit 302 changes the display range of the Gantt chart.

  In step S208, the control unit 302 determines whether there is a display attribute storage instruction. If there is an instruction, the process proceeds to step S209. If there is no instruction, the process proceeds to step S210. As an input method of the display attribute storage instruction, the C key on the keyboard is pressed.

  In step S209, the control unit 302 performs display attribute storage processing. Details of the display attribute storing process will be described later.

  In step S210, the control unit 302 determines whether there is a display attribute reflection instruction. If there is an instruction, the process proceeds to step S211, and if there is no instruction, the process proceeds to step S212. As an input method of the display attribute reflection instruction, the V key on the keyboard is pressed.

  In step S211, the control unit 302 performs display attribute reflection processing. Details of the display attribute reflection processing will be described later.

  In step S212, the control unit 302 determines whether there is a reflection cancellation instruction. If there is an instruction, the process proceeds to step S213, and if there is no instruction, the process proceeds to step S214. As a method for inputting the reflection cancel instruction, the Z key on the keyboard is pressed.

In step S213, the control unit 302 performs display attribute cancellation processing to return to the state before the display attribute information is reflected on the plan screen. Details of the display attribute cancellation processing will be described later.
In step S214, the control unit 302 determines whether the close button has been pressed. If there is an instruction, the process proceeds to step S215. If there is no instruction, the process returns to step S203.

  In step S215, the control unit 302 closes the plan screen.

<Flow of attribute storage processing>
Next, the flow of attribute storage processing will be described with reference to FIG.

  In step S <b> 301, the attribute storage unit 308 acquires display attribute information of the current plan screen from the buffer memory 312.

  Here, the display attribute information will be described with reference to FIG.

  In FIG. 8, reference numeral 601 denotes display attribute information. Reference numeral 602 denotes an item representing display attribute information. Reference numeral 603 denotes a value for each item of the display attribute information. Reference numerals 604 and 605 denote the horizontal size and vertical size of the screen, respectively. The unit is pixel. Reference numerals 606 and 607 denote horizontal and vertical display magnifications of the Gantt chart, respectively. 608 and 609 are horizontal and vertical scroll positions of the Gantt chart, respectively. The unit is pixel. In the example of FIG. 8, the screen size is 600 pixels wide and 400 pixels long. The display magnification of the Gantt chart is 12.5 times wide and 1.7 times long. This indicates that the scroll position is 500 pixels wide and 0 pixels long.

  In step S <b> 302, the attribute storage unit 308 stores the acquired display attribute information in the attribute storage unit 307.

<Flow of attribute reflection processing>
Next, the flow of attribute reflection processing will be described with reference to FIG.

  In step S <b> 311, the attribute reflection unit 309 determines whether there is display attribute information in the attribute holding unit 307. If there is display attribute information, the process proceeds to step S312, and if not, the process ends.

  In step S312, the attribute reflection unit 309 acquires display attribute information of the current plan screen from the buffer memory 312.

  In step S 313, the attribute reflection unit 309 stores the acquired display attribute information in the history holding unit 310.

  In step S <b> 314, the attribute reflection unit 309 acquires display attribute information from the attribute holding unit 310.

  In step S315, the attribute reflection unit 309 changes the display attribute information of the plan screen with the acquired display attribute information.

<Flow of reflection cancellation processing>
Next, the flow of the reflection cancellation process will be described with reference to FIG.

  In step S321, the reflection cancellation unit 311 determines whether there is display attribute information in the history holding unit 310. If there is display attribute information, the process proceeds to step S322, and if not, the process ends.

  In step S <b> 322, the reflection cancellation unit 311 acquires display attribute information from the history storage unit 310.

  In step S323, the reflection cancellation unit 311 changes the display attribute information on the plan screen with the acquired display attribute.

  In step S324, the reflection cancellation unit 311 deletes the display attribute information acquired from the history holding unit 310.

<Plan comparison flow>
Next, the flow when comparing plans will be described with reference to FIGS.

  First, in order to obtain a plan for manufacturing orders 1 to 5, the manager causes the plan management system to plan in a forward manner and obtain the plan of FIG. FIG. 6A shows the result (plan 1) of planning work corresponding to orders 1 to 5 by the forward method.

  Next, for the sake of comparison, the administrator causes the plan management system to plan in the backward manner, and obtains the plan of FIG. 6B. FIG. 6B shows a result (plan 2) of planning work corresponding to orders 1 to 5 in the backward manner.

  Next, in order to compare the plan 1 and the plan 2, the manager reduces the display magnification so that the first work of the plan 1 and the last work of the plan 2 can be displayed, and the result of FIG. FIG. 6C shows the result of reducing the horizontal display magnification so that the plan 1 from 9:00 to 17:00 can be seen.

  Next, in order to match the display of plan 2 with plan 1, the administrator reflects the display attribute information of plan 1 in plan 2 and obtains the result of FIG. FIG. 6D shows the result of reflecting the display attribute information of FIG. By reflecting, the display magnification in the horizontal direction is lowered, and the plan from 9:00 to 17:00 can be seen in the plan 2 as well.

  As described above, according to the technique described above, when comparing a plurality of plans, the display attribute information of one plan is saved and reflected as the display attribute information of another plan. Can be compared.

[Other embodiments]
In the embodiment, the display attribute information is the screen size, the display magnification of the Gantt chart, and the scroll position. However, the display attribute information is not limited to this. For example, the order of the vertical axis elements of the Gantt chart such as the display order of resources may be used, and the Gantt chart such as a color or pattern that distinguishes the work corresponding to the order may be used. Information for identifying each work element may be used. Depending on the plan creation parameters, the order of resources used in multiple plans may differ. By arranging the display order of resources among a plurality of plans, it is possible to make comparison easier. As for the display attribute information, any information may be used as long as the information is related to the plan display.

  In the embodiment, the input method of the display attribute storage instruction, the display attribute reflection instruction, and the reflection cancellation instruction is a keyboard key input. However, the method of inputting each instruction is not limited to this. For example, a button corresponding to each instruction may be provided on the plan screen, and the button may be input by the administrator pressing the button. Alternatively, the display attribute may be reflected by a mouse drag and drop operation. For example, display attributes may be saved and reflected by dragging and dropping a mouse from one plan screen to two plan screens.

  When displaying on the touch panel, a different touch gesture may be assigned to each instruction, and the corresponding instruction process may be executed by detecting the input of the touch gesture. Furthermore, any input method may be used as long as it can determine each instruction.

  Moreover, in the said Example, the object which reflects display attribute information was made into the plan screen. However, the present invention is not limited to this. For example, an image display screen of image editing software or a 3D object display screen of 3D object design software may be used. Furthermore, any screen may be used as long as it is a system display screen capable of displaying a plurality of screens for displaying objects.

  In the above embodiment, the Gantt chart is a resource Gantt chart with resources as vertical axis elements. However, the Gantt chart is not limited to this, and may be an order Gantt chart with orders as vertical axis elements. .

  Moreover, in the said Example, it was supposed that the plan management system operate | moves with the management server installed in the manufacturing site. However, the operation location of the plan management system is not limited to this. For example, the plan management system may be operated by a server installed at another site of the manufacturing company and accessed from a client terminal on the manufacturing site. Further, it may be operated by a cloud server and accessed from a client terminal at the manufacturing site.

  In the embodiment, the display attribute reflection process acquires one display attribute information held by the attribute holding unit 307 and reflects it on the plan screen. However, the method of reflecting the display attribute is not limited to this. For example, a plurality of display attribute information may be held, and a plurality of display attribute information may be presented and selected when reflected.

<Storage medium>
Note that the present invention can be applied to a system composed of a plurality of devices (for example, a host computer, an interface device, a reader, a printer, etc.), or an apparatus composed of a single device (for example, a copier, a facsimile machine, etc.). It may be applied.

Another object of the present invention is to supply a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus,
Needless to say, this can also be achieved by the computer (or CPU or MPU) of the system or apparatus reading and executing the program code stored in the storage medium.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the storage medium storing the program code constitutes the present invention.

  As a storage medium for supplying the program code, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.

Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on the instruction of the program code. Do some of the actual processing,
Needless to say, the process includes the case where the functions of the above-described embodiments are realized.

  Further, after the program code read from the storage medium is written to a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

101 printing site, 102 management server, 103 manufacturing equipment,
301 plan management system 302 control unit 303 display unit 304 input unit
305 plan information storage unit, 306 plan unit, 307 attribute storage unit, 308 attribute storage unit,
309 Attribute reflection unit, 310 history holding unit, 311 reflection cancellation unit,
312 Buffer memory

Claims (9)

In a plan management system that manages plans,
Attribute holding means (S302) for holding display attribute information of the plan screen;
Attribute storage means (S209) for storing display attribute information in the attribute holding means;
Attribute reflecting means (S211) for reflecting display attribute information held by the attribute holding means on the plan screen;
A plan management system comprising: Furthermore, history holding means (S313) for holding display attribute information before reflecting display attribute information on the plan screen, reflection canceling means (S213) for returning to a state before display attribute information is reflected on the plan screen, The plan management system according to claim 1, further comprising: The attribute reflecting means stores the display attribute information of the plan screen in the history holding means when the attribute holding means holds display attribute information, and displays the display attribute information held by the attribute holding means. The plan management system according to claim 2, wherein the plan management system is applied to a plan screen. The display attribute information includes at least one or more of the size of the planning screen, the display position of the Gantt chart, the display range of the Gantt chart, the order of the vertical axis elements of the Gantt chart, and information for identifying each work element of the Gantt chart. The plan management system according to claim 1 characterized by things. In the plan management method for managing plans,
An attribute holding step (S302) for holding display attribute information of the plan screen;
An attribute storage step (S209) for storing display attribute information in the attribute holding step;
An attribute reflection step (S211) for reflecting display attribute information held by the attribute holding step on the plan screen;
A plan management method characterized by comprising: Furthermore, a history holding step (S313) for holding display attribute information before reflecting the display attribute information on the plan screen, a reflection canceling step (S213) for returning to the state before the display attribute information is reflected on the plan screen, The plan management method according to claim 5, further comprising: In the attribute reflection step, when the attribute holding step holds display attribute information, the display attribute information of the plan screen is saved in the history holding step, and the display attribute information held by the attribute holding step is stored. The plan management method according to claim 6, wherein the plan management method is applied to a plan screen. The display attribute information includes at least one or more of the size of the planning screen, the display position of the Gantt chart, the display range of the Gantt chart, the order of the vertical axis elements of the Gantt chart, and information for identifying each work element of the Gantt chart. The plan management method according to claim 5 characterized by things. A recording medium for recording a plan management program,
In plan management to manage plans,
An attribute holding function (S302) for holding display attribute information of the plan screen;
An attribute storage function (S209) for storing display attribute information in the attribute holding function;
An attribute reflection function (S211) for reflecting display attribute information held by the attribute holding function on the plan screen;
The recording medium characterized by recording the program which implement | achieves.