JP2015005032A - Engineering schedule management system, engineering schedule management method and engineering schedule management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To eliminate duplication of resources or works on the basis of the priority while considering limiting conditions such as order and delivery date.SOLUTION: An engineering schedule management system 10a includes: a display section 51; an engineering schedule DB41; a work input section 12 that receives inputs etc. on a work plan and a work; a resource input section 11 that receives inputs etc. on resources; a work attribute setting section 6 for setting work attributes; a work order relation setting section 7 that sets relationship among the works; a PERT execution section 21 for obtaining the float for each work; a priority evaluation section 22 that sets the priority on the basis of the work float and a predetermined evaluation function; a resources collapse execution section 23 that distributes resources to plural works; and an execution ES management section 33a that registers or updates the engineering schedule DB41 while adjusting the engineering schedule data.

Description

  Embodiments described herein relate generally to an engineering schedule management apparatus, an engineering schedule management method, and an engineering schedule management program for managing an engineering schedule such as work.

  In general, in an engineering schedule management apparatus in design and development work, an initial plan is formulated, and a deviation between the plan and the actual is grasped at the implementation stage, and the plan is reviewed everywhere.

  As an engineering schedule management device in such a design and development work, the difference from the initial plan occurs in the form of the occurrence of a pending matter. For example, tracking of the pending matter processing and document completeness is performed, and progress management is performed. Yes.

  In the process management support system, the issue input means for registering the issues generated during the design process and the resolution thereof, the issue management means for managing the issues and the current solution status of each development document, It is known to provide a progress grasping means for estimating the current completeness and man-hour of a document, and a process management means for displaying a deviation from the plan based on the progress prediction and changing the plan (for example, see Patent Document 1).

JP-A-10-240797

  Since regular projects are ordered in bulk, we will focus on completing the project by the deadline by creating a schedule for the entire project and shortening the critical path.

  However, plant construction projects are often ordered separately from customers, and individual delivery dates are often set for reasons such as witness tests. In addition, there is a lot of complication that the same designer is in charge of multiple projects.

  In the engineering schedule device based on the technology mentioned above, even if the schedule created for each project is appropriate for a single plan, the overall schedule integrating them is the work of the same designer or worker, etc. However, there is a problem that the schedule becomes inoperable such as overlapping at the same time.

  In the engineering schedule device based on the above-described technology, the critical path is normally defined as “the longest series of work from the first work to the final work in the project”, and the float is defined as “the end date of the entire project. Is defined as “a period during which the start of a task can be delayed within a range that does not delay”.

  However, in the engineering schedule device based on the technology described above, the concept of “the end date of the entire project” is ambiguous because the order and delivery are set in each project item. There was a problem that the concept could not be applied.

  The problem to be solved by the embodiments of the present invention is that an engineering schedule can be generated and managed based on the priority order in consideration of constraints such as ordering and delivery date, without duplication of resources and work. To provide an engineering schedule management device, an engineering schedule management method, and an engineering schedule management program.

  In order to solve the above-described problem, an engineering schedule management apparatus according to an embodiment is an engineering schedule management apparatus that manages an engineering schedule for a plurality of operations planned in a target engineering schedule. The engineering schedule management apparatus receives an input or an edit for a work plan and a work content including at least a work target and a work period related to the plurality of works, and inputs or edits for resources used in the plurality of works. A resource input unit; a work attribute setting unit that sets a work attribute that can associate the work plan with the resource and that can collate the work content for each of the plurality of tasks; and the work plan According to the setting by the work attribute setting unit and the work context setting unit for each engineering schedule, the work context setting unit for setting the context between the tasks based on the context between the operations related to the process The plurality of operations, the operation plan, the operation attributes, and the context between the operations And an engineering schedule DB that associates the resources with each other and stores them as engineering schedule data, a PERT execution unit that obtains a float that is a margin period of the work for each work based on the engineering schedule data, and each of the plurality of works Based on the float and a predetermined evaluation function, a priority evaluation unit that sets a priority order for ranking whether to perform any of the plurality of operations first, and the engineering schedule A resource landslide execution unit that allocates the resources for a plurality of operations, and adjusts the engineering schedule data according to the resource allocation for the plurality of operations by the resource landscaping execution unit, the engineering schedule An engineering schedule management unit that registers or updates in the engineering schedule DB and searches from the engineering schedule DB based on key data included in the engineering schedule data, and controls display when the engineering schedule data is input and edited And a display unit.

  In order to solve the above-described problem, the engineering schedule management method of the embodiment is an engineering schedule management method used for an engineering schedule management apparatus that manages the engineering schedule for a plurality of operations planned in the target engineering schedule. It is. In the engineering schedule management method, the engineering schedule management apparatus accepts input or editing for each of the following steps, that is, a work plan and work content including at least work targets and work periods for the plurality of works, The resource input step for accepting input or editing for the resources used in the plurality of operations, the operation plan and the resources can be associated with each of the plurality of operations, and the operation contents can be collated. A work attribute setting step for setting a work attribute; and a work context setting step for setting a context between the work based on a context between work related to the process of the work plan in the work input step; For each engineering schedule, According to the setting in the attribute setting step and the work context setting step, the engineering schedule data is associated with the plurality of work, the work plan, the work attribute, the context between the work and the resource, and the engineering schedule data is linked to the engineering schedule data. For each of the plurality of operations, an engineering schedule data storage step stored in an engineering schedule DB included in the apparatus, a PERT execution step for obtaining a float that is a margin period of the operation for each operation based on the engineering schedule data, and A priority evaluation step for setting a priority order for ranking which one of the plurality of operations to be executed first based on a float and a predetermined evaluation function; and the engineering schedule A resource landslide execution step for allocating the resources for the plurality of operations planned in a network, and after the resource landslide execution step, the engineering schedule data is adjusted according to the resource allocation for the plurality of operations. An engineering schedule management step for registering or updating the engineering schedule in the engineering schedule DB; and a display step for controlling display on the display section of the engineering schedule management device when inputting and editing the engineering schedule data; The engineering schedule is registered in the engineering schedule DB in response to completion of the input or editing in the work input step and the resource input step. Performing an engineering schedule management step of recording or updating.

  In order to solve the above-described problem, the engineering schedule management program according to the embodiment is an engineering that causes a computer to operate as an engineering schedule management apparatus that manages the engineering schedule for a plurality of operations planned in the target engineering schedule. It is a schedule management program. The engineering schedule management program is configured to input the computer with a work input unit that accepts input or editing of a work plan and work content including at least a work target, a work period, and work resources related to the plurality of works, and resources used in the plurality of works. Alternatively, a resource input unit that accepts editing, and a work attribute setting unit that sets a work attribute that can associate the work plan with the resource and that can collate the work content, for each of the plurality of works. A work context setting unit for setting the context between the tasks based on the context between the tasks related to the process of the work plan, and the work attribute setting unit and the work context setting unit for each engineering schedule. The plurality of operations, the operation plan, and the operation attribute An engineering schedule DB for storing the engineering schedule data in association with the context and the resources between the operations, and a PERT execution unit for obtaining a float that is a margin period of the operations for each operation based on the engineering schedule data; A priority evaluation unit for setting a priority order for ranking which one of the plurality of operations is performed first based on the float and a predetermined evaluation function for each of the plurality of operations; A resource landslide execution unit that allocates the resources for the plurality of operations planned in an engineering schedule, and adjusts the engineering schedule data according to the resource allocation for the plurality of operations by the resource landslide execution unit, The engine A ring schedule is registered or updated in the engineering schedule DB, and an engineering schedule management unit that searches from the engineering schedule DB based on key data included in the engineering schedule data, and when the engineering schedule data is input and edited It is made to operate | move as the said engineering schedule management apparatus provided with the display part which controls display.

  According to the engineering schedule management apparatus, the engineering schedule management method, and the engineering schedule management program according to the embodiment of the present invention, in consideration of constraints such as ordering and delivery date, resources, duplication of work, etc. are eliminated based on priority. Can create and manage engineering schedules.

The block diagram which shows the structure of the engineering schedule management apparatus which concerns on 1st Embodiment. The figure which shows an example of a structure of a resource table and a resource plan table. The figure which shows an example of a structure of a work plan table. The figure which shows an example of a link | link with a work plan table and a work attribute table. The figure which shows another example of the correlation with a work plan table and a work attribute table. The figure which shows an example of a structure of a work context table. The figure which shows an example of the data collation process by the back-and-front work collation part. The figure which shows an example of the connection process of the back and front work by the back and front work connection part. The figure which shows an example of the work advance processing by the PERT implementation part. The figure which shows an example which calculated the float of each operation | work. The figure which shows an example of the resource landslide process by a resource landslide execution part. The figure which shows another example of the resource landslide process by a resource landslide execution part. The flowchart which shows the engineering schedule management processing flow used for an engineering schedule management apparatus. The block diagram which shows the structure of the engineering schedule management apparatus which concerns on 2nd Embodiment. The figure which shows the example of the process of the pending work by the pending management part. The figure which shows the example of the process of the pending work by the pending management part. The figure which shows the example of the process of the pending work by the pending management part. The figure which shows the example of the process of the pending work by the pending management part. The figure which shows an example of a progress rate table.

  Hereinafter, an engineering schedule management device, an engineering schedule management method, and an engineering schedule management program according to embodiments of the present invention will be specifically described with reference to the drawings. Here, the same or similar parts are denoted by common reference numerals, and redundant description is omitted. Each of the following embodiments described here will be described by taking an example of an engineering schedule management device used in a plant such as a power plant.

[First Embodiment]
FIG. 1 is a block diagram illustrating a configuration of an engineering schedule management apparatus according to the first embodiment. Hereinafter, the engineering schedule management apparatus of the first embodiment shown in FIG. 1 will be described with reference to FIGS. 2 to 13 as appropriate.

  The engineering schedule management apparatus according to the first embodiment manages an engineering schedule which is a process in which work such as construction and design is incorporated.

  The engineering schedule management apparatus 10a shown in FIG. 1 generates an engineering schedule that is a target of a project in accordance with an input or editing operation by an operator (input / editor) or the like. The engineering schedule management apparatus 10a manages the generated engineering schedule.

  For this purpose, the engineering schedule management apparatus 10a includes an input / editing means 1, an adjusting means 2, an operating means 3a, a storage means 4, and a display means 5, as shown in FIG.

  The input / editing means 1 is a means for inputting and editing necessary data (engineering schedule data) for planning and changing the target engineering schedule.

  The adjusting unit 2 is a unit that adjusts the schedule for completing the work within a predetermined period with respect to the target engineering schedule. For this purpose, the adjusting unit 2 accesses the engineering schedule data and changes the engineering schedule data as necessary.

  The operation unit 3a registers or updates (adds, changes, deletes, etc.) the engineering schedule data in the engineering schedule DB 41 for the target engineering schedule. Further, the operation means 3a can search the engineering schedule DB 41 for key data included in the engineering schedule data.

  The storage means 4 is a table related to engineering schedules and an engineering schedule DB (database) 41 for storing data included in these tables, a work area (not shown) (memory for storing temporary data), an OS (operating system), application software, etc. Remember. The storage unit 4 includes, for example, a memory and a hard disk.

  In the engineering schedule DB 41, a plurality of tables whose data structures are defined in advance are registered. In addition, engineering schedule data is input or edited and registered in these tables and the engineering schedule DB 41. The engineering schedule DB 41 and a plurality of tables and engineering schedule data registered therein will be described later.

  The display unit 5 includes a display unit 51 that controls and displays engineering schedule data that is input, edited, and managed in the engineering schedule management apparatus 10a.

  First, the configuration of the input / editing means 1 will be described.

  As shown in FIG. 1, the input / editing unit 1 includes a resource input unit 11, a work input unit 12, a work attribute setting unit 6, and a work context setting unit 7.

  The resource input unit 11 receives input or editing for resources used in a plurality of operations.

  For example, the resource input unit 11 accepts input or editing of resource input data including a resource number, a resource name, a resource use start date and time, a resource use end date and time, a resource supply available amount, and a supply method for specifying a resource. In particular, in the case of human resources for design work, a resource number (such as a user ID) that can identify an individual and a personal name such as a designer are registered in the resource name. Thereby, it is possible to adjust a specific worker so that another work is not allocated with overlapping work periods.

  The resource supplyable amount indicates an amount that can be supplied per unit time when the supply method is defined as “constant”. If what is necessary when the resource is a material is regularly supplied, there is no need to consider in unit time, so the supply method is defined by “total amount”.

  For example, in the case of a human resource to which a specific person is allocated, the maximum resource supply amount is 1 and the minimum is 0 (meaning including holidays, vacations, and breaks). Therefore, the resource supply possible amount needs to be registered in a linked or related table (for example, resource plan table T22 in FIG. 2) described later based on the person's work table (work plan table or the like).

  The engineering schedule DB 41 stores engineering schedule data including at least work plan data and work attribute data for each work. In addition, the engineering schedule data includes context data for setting a context for a work process for each connection between works. The engineering schedule data includes resource data used for work. These data are linked (associated) as necessary, as will be described later. Thereby, a plurality of operations in the project can be managed and operated as a series of engineering schedules.

  The engineering schedule DB 41 shown in FIG. 1 includes a resource table T21, a resource plan table T22, a work plan table T31, a work attribute table T32, a work pre-relationship table T41, and the like, as will be described later. In these tables, as will be described later, engineering schedule data necessary for creating an engineering schedule for a project is stored. The work plan table T31 is representative of work plan tables T31A and T31B described later. The same applies to the work attribute table T32.

  FIG. 2 shows an example of the configuration of the resource table T21 and the resource plan table T22.

  Resource data relating to available resources is registered in advance in the resource table T21. Here, the resources are workers, machines, equipment, materials, and the like. The resource data includes at least a resource number and a resource name. The resource number is assigned a number that can be uniquely specified, for example, for an individual who is an operator or for each machine, facility, material, etc. such as an overhead crane. The resource name is, for example, a name for each worker or a name of a machine, equipment, material, or the like.

  The resource plan table T22 is created for each project, and stores resource plan data necessary for creating an engineering schedule. Specifically, the resource plan table T22 stores resource plan data that is input or edited based on the resource input data that is input via the resource input unit 11.

  The resource plan table T22 includes, for each resource number, a resource plan including, for example, a resource use start date and time indicating a work start scheduled date and time, a resource use end date and time indicating a work end scheduled date and time, a resource supply available amount, and a supply method. Data is stored.

  For example, if the resource is an overhead crane, the project start date and time and end date and time are set as the resource use start date and resource use end date and time if there is an operator regardless of the time of day. . If there is one overhead crane at the work place, “1” is set as the resource supply capability. In addition, since one machine is an integrated machine, the supply method is set to “constant”.

  For example, when the resource is a material, the delivery date of the material is set as the resource use start date and time, and the resource use end date and time may be indefinite, but the project end date is set for convenience. The amount of resources that can be supplied includes the weight and quantity of the material. For example, “total amount” is set as the supply method.

  As shown in FIG. 2, the resource input unit 11 associates a resource table T21 and a resource plan table T22 that can be associated with the same resource number.

  The work input unit 12 receives input or editing for work plans and work contents including at least work targets and work periods related to a plurality of works. In other words, the work input unit 12 receives input or editing of work-related input data (work input data).

  The work input unit 12 accepts input or editing of work input data including, for example, a work number for identifying a work, a work name, a work start date and time, an end date and time, work attributes, and the like. The work input data is classified into work plan data as described later, work attribute data including work contents, and the like.

  The work plan table T31 stores work plan data related to work plans for each work.

  FIG. 3 shows an example of the configuration of the work plan table T31.

  As shown in FIG. 3, the work plan table T31 includes a work name, a work start date and time, an end date and time, and a dummy flag for each work number for specifying a work including a design work and a related local / factory work, for example. Store work plan data.

  In the dummy flag, for example, 1 is input as data when there is a context with work input by another person (an operator in another department), and 0 is not set as data when the self (an operator in the own department) inputs. Is entered.

  Even when 0 is input to the dummy flag, the start date / time and end date / time can be adjusted later, and therefore may be provisional. The operator in the own department and the operator in the other department use, for example, a login ID or a user ID when an operator (input / editor) who has access authority to log in to the engineering schedule management apparatus 10a logs in. Thus, it is possible to classify operators and work departments.

  The work input unit 12 accepts input and editing of work plan data for the work plan table T31, for example, via a man-machine interface (keyboard, mouse, etc.). The result of the input or editing is displayed on the screen by the display unit 51.

  For example, when the time axis scale 61 (for example, FIG. 9) is provided in the horizontal direction on the display screen by the display unit 51, the input work schedule is time elapses from the left to the right in the time axis scale 61 (reference (Date based on point). Further, a rectangle or the like having a width (horizontal width in the horizontal direction in FIG. 9) corresponding to the work period (work end date and time—work start date and time) from any position on the time axis scale 61 corresponding to the work start date and time is displayed. Is done. Here, the input schedule is, for example, the start date / time and end date / time of work in the work plan table T31 shown in FIG.

  As described above, in each work, the horizontal length of the rectangle on the display screen by the display unit 51 represents the work period, and the work name is displayed on the display screen. A rectangle in which the work name (for example, work A shown in FIG. 9) is displayed is referred to as a work bar.

  For example, when the work bar on the display screen is moved by the operator, the work input unit 12 edits the start date and time and the end date and time of the work in the work plan data accordingly. That is, the work start date and time and the end date and time corresponding to the time axis position of the work bar after movement are reflected in the work plan data.

  When the dummy flag of the work plan data is 1, the display unit 51 controls the display by rounding or coloring four corners of the rectangle to distinguish it from the work bar when the dummy flag is 0 on the display screen. The As a result, it is possible to easily identify whether another person (an operator in another department) needs to have a context with other work.

  In addition to this, the display unit 51 controls the display of the screen for inputting and editing the above-described work input data, the table format screen for displaying various tables, the work bar for editing the engineering schedule, and the like. .

  The work attribute setting unit 6 inputs a work attribute that can associate at least a work plan and a resource and can collate work contents for each of a plurality of works. The work attribute setting unit 6 sets work attribute data related to the work attribute for each work. For this purpose, the work attribute setting unit 6 includes a work attribute data generation unit 13 and a front and rear work attribute data generation unit 14.

  Here, the work attribute indicates, for example, a work target, a work field, a resource used for the work, a constraint condition in the schedule, and the like. The work attribute data includes, for example, a work number (ID) that can identify a work, a work target, a work field, a resource used for the work, and a flag related to constraints in the schedule.

  The work attribute data generation unit 13 receives input and editing of work attribute data via the resource input unit 11 or the work input unit 12. The input or edited work attribute data is stored in the work attribute table T32. The work attribute table T32 is prepared or generated in advance.

  Specifically, when the operator inputs work attribute data, a work number is selected and input to link to work plan data (for example, work plan table T31A shown in FIG. 4). The work attribute data generation unit 13 accepts input and editing for the work attribute table T32A linked to the work plan table T31A including the selected and entered work number.

  FIG. 4 shows an example of linking the work plan table T31A and the work attribute table T32A.

  As shown in FIG. 4, the work attribute table T32A includes, for each work number, a work target system, a work target device, a fixed flag, a resource number, an input resource amount, a pending flag, a work (including design). Work attribute data including a field, one (target book # 1) or a plurality of target books (# 1 to #N, N is a positive number of 2 or more) is stored.

  Here, the amount of input resources is the amount of resources that are actually scheduled to be input in the work, and is different from the supplyable amount of resources that can be supplied. The fixed flag is set for work (including events) whose schedule is difficult to change such as witness test and delivery date. For example, when “1” (the flag is set) is set in the fixed flag, the PERT execution unit 21 and the resource landslide execution unit 23 described later automatically change the schedule for the operation with the fixed flag set. It is not possible. In other words, the work including the fixed flag can be a constraint condition in the engineering schedule.

  In addition, the pending flag is set for a task having a pending item (referred to as a pending task). For example, when “1” (flag is set) is set (set) in the pending flag, the work is a pending task, and when “0” is set in the pending flag, the task is not a pending task. In the case of pending work, it is not necessary to input data for the work start date and time and the end date and time (process etc.) of the work plan data at the time of input by the operator, and these date and time are input later. The pending work will be described later.

  The work plan table T31A storing the work plan data input via the resource input unit 11 or the work input unit 12 and the work attribute table T32A described above are linked by the work number “T001”.

  Although it is a series of engineering schedules in one project, for example, it is not the responsibility of the operator who enters the work (work of the own department), but it is necessary to coordinate with the engineering schedule including work entered by other departments . For example, if the work of your own department can only be performed after the work of the other department, or if the work of the other department cannot be done unless the work of your own department is completed, not only the engineering schedule including the work of your own department, It is necessary to create a link (link) with the engineering schedule including the work of the department.

  For this purpose, the work attribute setting unit 6, for example, the engineering schedule of the work (one work) input by the own department and the work (other work) input by other departments such as other design workers and field workers. ) With the engineering schedule.

  For the collation, data that is a search key in the engineering schedule DB 41 is input to the pre- and post-operation attribute data generation unit 14 via the resource input unit 11 or the work input unit 12. The before and after work attribute data generation unit 14 compares the work attribute of one work with the work attribute of another work in a series of engineering schedules, and inputs the work attribute as to whether the work is related to the context.

  FIG. 5 shows another example of linking the work plan table T31B and the work attribute table T32B.

  When a context is determined between one work and another work, especially when the context is related to a work input by another person (another department), 1 is input as a dummy flag.

  For example, as shown in FIG. 5, the work plan table T31B includes a work number “S001”, a work name “RCW pump design”, a start date and time “2012/1/7 8:00”, and an end date and time. “2012/1/8 17:00” and a dummy flag “1” are stored. The work attribute table T32B stores a work number “S001”, a system “RCW”, a device “RCW pump”, a work field “control design”, and a target book # 1 “Electric Control Deployment Connection Diagram”.

  Note that the work attribute table T32B in FIG. 5 is an example input by an operator in another department, and the number of items to be input is smaller than the example of the work attribute table T32A in FIG. 4 input by an operator in its own department. Shall. That is, since the work attribute table T32B is a work attribute for a dummy work, at least some items that can be collated are input.

  The work context setting unit 7 sets the context between the work based on the work context related to the work planning process. For this purpose, the work context setting unit 7 accepts input and editing of the context between works for a plurality of work in the engineering schedule via the work input unit 12. The work context setting unit 7 collates work attributes with respect to work that is subject to context between work. The work context setting unit 7 sets the context between the work according to the work attribute collation result for the work that is the target of the context between the work.

  For this purpose, the work context setting unit 7 includes a context data generation unit 15, a front / rear work collation unit 16, a front / rear work selection unit 17, and a front / rear work connection unit 18.

  The context data generation unit 15 accepts input or editing regarding the context between operations. The context data generation unit 15 generates work context data based on input or editing of the context between tasks. Further, the context data generation unit 15 displays the context between the input or edited work on the display screen via the display unit 51.

  FIG. 6 shows an example of the configuration of the work sequence table T41. Specifically, the work context table T41 shown in FIG. 6 is defined by work A defined by the work plan data and work attribute data shown in FIG. 4, and work plan data and work attribute data shown in FIG. It is an example which registers the context with work B.

  The work sequence table T41 is a table for setting a preceding work and a subsequent work. As shown in FIG. 6, the work context table T41 stores work context data including work numbers (eg, T001 and T002) indicating preceding work and subsequent work for each connection number (eg, C001). The connection number is a number assigned to specify which of the preceding work and the succeeding work is connected by the input or editing operation.

  Specifically, between the tasks input or edited by the work input unit 12, the work bar is displayed as a line segment or an arrow on the display screen controlled by the display unit 51, for example, with the preceding work as the starting point and the subsequent work as the ending point. Connect with wires. That is, the context data generation unit 15 establishes a context between the tasks input and edited by the task input unit 12. As a result, the context data generation unit 15 generates work context data indicating the relationship between the preceding work T001 and the subsequent work T002, as shown in FIG. 6, and the work context data is stored in the work context table T41. Stored.

  The pre- and post-operation verification unit 16 is connected via the context data generation unit 15, for example, a previous operation in which an operator of the own department inputs or edits an engineering schedule or work, and an operator in another department inputs or edits an engineering schedule or work. Check with subsequent work. In this collation, the pre / post work collation unit 16 calculates the degree of coincidence for the work attributes based on the work attributes for the pre-work and post-work to be collated.

  In FIG. 7, an example of the data collation process by the back-and-front work collation part 16 is shown.

  The work attributes can be registered in, for example, work attribute tables T32A and T32B shown in FIG. As shown in FIG. 7, for example, when the four matching items set (or registered) in the work attribute tables T32A and T32B match, the pre- and post-work collation unit 16 assigns weights to each item, for example. And 80% (in this case, 5 items in the work attribute table T32B as a reference).

  In addition, with respect to the system to be worked and the equipment to be worked, when the possibility of erroneous input is low compared to other items, the weighting method in which the preceding and following work collation unit 16 weights them. You may determine using.

  The pre- and post-operation selection unit 17 selects between operations in the engineering schedule, that is, whether one operation is a previous operation and the other operation is a subsequent operation.

  For example, it is assumed that a work bar displayed on the display unit 51 is selected by the operator using a pointing device or the like for a work for which work attributes have been input via the pre- and post-work attribute data generation unit 14. Based on the degree of coincidence calculated by the pre- and post-operation collating units 16, the pre- and post-operation selecting unit 17 displays work names and the like on the selected work bar or in the vicinity in descending order of coincidence. At this time, for example, when the operator clicks and selects a work name displayed on the display screen, the front-rear work connection unit 18 determines the front-rear relationship between the previous work and the rear work.

  The front-rear work connection unit 18 links the previous work (preceding work) to the rear work (subsequent work) between the works for which the front-rear relation is selected by the front-rear work selecting unit 17. That is, as described above, the front-rear work connection unit 18 determines the front-rear relationship between the previous work and the rear work.

  In FIG. 8, an example of the connection process of the front and rear work by the front and rear work connection part 18 is shown.

  FIG. 8 shows a plurality of operations such as customer adjustment T11, system design T12, system design T13, equipment design T14, and circuit design T15.

  The engineering schedule (hereinafter, schedule) of the work input by another department is SD51, and the work schedule input by the own department is SD52. Specifically, the schedule SD51 is a work schedule composed of customer adjustment T11 and system design T12, and the schedule SD52 is a work schedule composed of system design T13, equipment design T14, and circuit design T15.

  For example, the system design T13 shown in FIG. 8 is a work linked to the work plan table T31B and work attribute table T32B of the work number “S001” shown in FIG. Further, the system design T12 shown in FIG. 8 is a work linked to the work plan table T31A and work attribute table T32A of the work number “T001” shown in FIG.

  In the schedule SD51 and the schedule SD52, it is assumed that the correspondence relationship between the system design T12 and the dummy flag (shown in FIG. 7) of the system design T13 is selected via the pre- and post-operation selecting unit 17 as illustrated in FIG. At this time, the anteroposterior work connection unit 18 determines the work anteroposterior relation between the system design T12 and the equipment design T14 based on the work anteroposterior relation table T41 (eg, FIG. 6). That is, it is determined that the work is the preceding work “T001” (system design T12) and the subsequent work “T002” (device design T14).

  Further, since the work of the system design T13 is the dummy flag “1”, the work of the system design T12 with the dummy flag “0” corresponding to this is the preceding work connected to the device design T14 as shown in FIG. It is said. Further, the work of the device design T14 is a subsequent work connected to the system design T12 as shown in FIG.

  When the correspondence relationship between the system design T12 and the dummy flag of the system design T13 is selected by the pre- and post-operation selection unit 17, the pre- and post-operation connection unit 18 connects the system design T12, the system design T13, and the device design T14. Do.

  As shown in FIG. 8, the front-rear work connection unit 18 links the previous work to the rear work between the works for which the front-rear work selection unit 17 has selected the front-rear relation. For example, the front-rear work connection unit 18 connects the system design T12 and the device design T14, for which the front-rear relationship is selected, on the display screen of the display unit 51 with a broken line or a broken-line arrow via the system design T13. .

  Further, when the front-rear work connection unit 18 determines the front-rear relationship in accordance with the input from the operator, the system design T13 set as a dummy is removed from the display screen of the display unit 51 as shown in FIG. Design T12 and equipment design T14 are connected. For example, a thicker line than the line before confirmation is displayed so that the operator can determine the connection relationship between the system design T12 and the device design T14 (corresponding to the connection number C001 in FIG. 6).

  As a result, the pre- and post-operation connection unit 18 connects the schedule SD51 and the schedule SD52 as indicated by the schedule SD53 in FIG.

  As described above, for example, in one project, even if the operator of the own department and the operator of the other department each input a schedule, the schedules can be combined into one later.

  Next, the configuration of the adjusting unit 2 will be described.

  As shown in FIG. 1, the adjustment unit 2 includes a PERT execution unit 21, a priority order evaluation unit 22, and a resource landslide execution unit 23.

  The PERT execution part 21 calculates | requires the float of each operation | work using the method of PERT which is mentioned later about the target engineering schedule.

  For this reason, the PERT execution unit 21 sets the context relationship set in the front-rear work connection unit 18 based on the work for which a fixed flag is set in an event (including work) such as an order corresponding to the work start timing. Based on the connection indicating, the work is advanced in advance for the target engineering schedule.

  Here, PERT (Program Evaluation and Review Technique) is generally a kind of model of project management, and is a technique for analyzing work required to complete a project.

  Further, in the present embodiment, the term “float” means “a period during which the start of a certain work can be delayed within a range in which the end date of the entire project is not delayed”. That is, it indicates a margin (a margin period) in the work time schedule.

  In the conventional normal PERT method, for example, after moving forward from the first work of the project to the last work based on the context of the work, the first work and the final work are fixed, and how much margin the target work has Was calculated.

  On the other hand, in the present embodiment, taking into consideration that ordering and delivery date are one of the important constraints of the project, events such as ordering and delivery date are set to work with a fixed flag. As a result, on the engineering schedule, the allowance is calculated for each work based on the relationship between the work to be fixed (work with the fixed flag set) and the work not fixed (work with no fixed flag set). . If a plurality of margin allowances can be calculated, the one with the least allowance is selected, and the selected allowance is set as the float of the work.

  FIG. 9 shows an example of a work advancement process by the PERT execution unit 21. FIG. 10 shows an example of calculating the float of each work.

  Assume that the operator has entered or edited the work, work plan, context, etc. of a plurality of work, and has created a general engineering schedule SD61 as shown in FIG. 9, for example.

  The PERT execution unit 21 left-aligns the engineering schedule SD61 with respect to the time axis scale 61 (advances ahead of time) on the basis of the link (link) of the front-rear relationship set by the front-rear work connection unit 18. In such a case, no movement is performed for a fixed flag.

  The PERT execution unit 21 pays attention to a path (set as a milestone) on which a fixed flag is set, and selects a path that passes between milestones. Note that the path refers to a connection path in time series of work bars (work) shown in FIG. 9, for example.

  In the example of the engineering schedule SD61 shown in FIG. 9, there is no path from the order # 2 to the delivery date # 1, and therefore there are three other paths shown below.

Patha: Order # 1 to Delivery # 1
Pathb: Order # 2 to Delivery # 2
Pathc: Order # 1 to Delivery # 2
Each of these three passes is a milestone.

  Furthermore, the PERT execution unit 21 obtains the float of each work in each path while ignoring the influence of other paths.

  First, the PERT execution part 21 carries out the left alignment of the schedule with respect to the engineering schedule SD61 based on the context between the operations. As a result, the PERT execution unit 21 generates an engineering schedule SD62 shown in FIG.

  Next, the PERT execution part 21 calculates | requires the float of the work in each path | pass shown in FIG. 10 based on the produced | generated engineering schedule SD62.

  For example, in the path (Pathb) from the order # 2 to the delivery date # 2 in the engineering schedule SD62 in FIG. 9, the float of the work F is 7 days between the work H and the delivery date # 2, the work F and the work H That is a total of 9 days, with 2 working intervals.

  The PERT execution unit 21 calculates the float in each path as described above, and sets the strictest float among the paths to which the work belongs (the shortest float among the paths) as the float of the work.

  For example, as shown in FIG. 10, the operation A belongs to the Paths of Patha and Pathc, and the shortest float among the paths is 7 days in Pathc. Work B belongs only to the path of Patha, and the shortest float of the paths is 9 days in Patha. Similarly, as shown in FIG. 10, the shortest float among the paths is also obtained in operations C to H.

  As described above, the PERT execution unit 21 obtains the float of each work.

  For each float, the priority evaluation unit 22 calculates a priority with an evaluation function based on, for example, a penalty when delivery is not in time, a contract amount when delivery is possible without problems, and the like. The priority order evaluation unit 22 assigns priorities (high priority order to low priority order) from the work of a float with a high priority.

  Note that the evaluation function may include not only the cost based on the penalty, the contract amount, etc., but also a function based on, for example, work man-hours to be compared between one person's duplicate work and many people's duplicate work, work efficiency, and the like. The evaluation function is prepared in advance and is used when the priority evaluation unit 22 calculates the priority.

  The resource hill-climbing execution unit 23 performs resource hill-climbing based on the constraint condition of the resource supply possible amount stored in the resource plan table T22 for each resource number. A resource abandonment refers to the allocation of resources that are assigned to a task with a higher priority when a worker is allocated to another task including at least the same period.

  Further, the resource hill-climbing execution unit 23 can check resource allocation for work between engineering schedules in different projects. Furthermore, when the priority ranking for the project is determined by, for example, the priority ranking evaluation section 22, the resource hillside execution section 23 can also allocate resources accordingly.

  Here, in the example illustrated in FIG. 10, for example, it is assumed that the human resources of the work B and the work C are the same (there is at least one same worker). That is, since it is impossible to simultaneously input workers to the work B and the work C, it is necessary to set either the work B or the work C as the previous work. In order to simplify the explanation, it is assumed that the priority evaluation unit 22 evaluates the evaluation function based on the size of a specific float. For example, the delivery date # 2 is the most restrictive condition.

  FIG. 11 shows an example of the resource landslide processing by the resource hillside execution unit 23, and FIG. 12 shows another example. Here, the work C with a small float shown in FIG. 11 (7 days shown in FIG. 10) is the preceding execution SD71, and the work B with a large float shown in FIG. 12 (9 days shown in FIG. 10) is the preceding execution SD72.

  Comparing the results of the preceding execution SD71 and the preceding execution SD72, the margin after the operation H becomes longer when the operation C with a small float is performed in advance. For example, in the preceding execution SD71, the margin after the work H is 7 days, whereas in the preceding execution SD72, the margin after the work H is 5 days.

  In such a case, the priority order evaluation unit 22 evaluates that there is no allowance (delivery allowance) for the delivery date # 2 in the direction where the float of the work H is smaller, so the work C is performed before the work B. Decide that. In other words, the priority order evaluation unit 22 evaluates the prior execution SD 71 shown in FIG.

  As described above, the resource collapse execution unit 23 performs the work C ahead of the work B determined by the priority evaluation unit 22 when the human resources of the work B and the work C are the same, for example. Receive evaluation results (priority). As a result, the resource collapse execution unit 23 allocates resources for work according to the priority order evaluated by the priority order evaluation unit 22. In other words, the resource hill-climbing execution unit 23 performs resource allocation such as the preceding execution SD 71 shown in FIG.

  The resource collapse execution unit 23 allocates linked resources based on priority when the work periods overlap between the tasks in the engineering schedule and at least some of the linked resources cannot be allocated. In addition, work ranking is performed between tasks. On the other hand, in other cases, the resource hillside execution unit 23 allocates resources for a plurality of operations based on the engineering schedule data.

  The resource landslide execution part 23 outputs the adjustment result by the adjustment means 2 to the operation means 3a.

  Next, the configuration of the operation unit 3a will be described.

  As shown in FIG. 1, the operation means 3a has an implementation ES (engineering schedule) management unit 33a.

  The implementation ES management unit 33a receives the adjustment result by the adjustment unit 2 from the resource hillside implementation unit 23 for the engineering schedule to be processed. The implementation ES management unit 33a registers or updates (adds, changes, deletes, etc.) the engineering schedule data reflecting the adjustment result in the engineering schedule DB 41 for the target engineering schedule.

  Specifically, for the engineering schedule that is input or edited by the input / editing means 1 and adjusted by the adjusting means 2 as described above, the implementation ES management unit 33a includes the resource table T21, the resource plan table T22, and the work plan table. Stored in T31, work attribute table T32, work pre- and post-relationship table T41, or associated. Accordingly, the implementation ES management unit 33a registers or updates the engineering schedule DB 41 in the engineering schedule DB 41.

  Further, the implementation ES management unit 33a can search the engineering schedule DB 41 for key data included in the engineering schedule data.

  Next, an engineering schedule management process flow used in the engineering schedule management apparatus 10a shown in FIG. 13 will be described.

  In the engineering schedule management process flow shown in FIG. 13, for example, after the engineering schedule management apparatus 10a is powered on, the following process of step S1 is started.

  The work input unit 12 receives input or editing for work targets and work contents including at least work targets and work periods related to a plurality of works (step S1).

  The resource input unit 11 receives input or editing for resources used in a plurality of operations (step S2).

  The work attribute setting unit 6 sets a work attribute that can associate a work plan and a resource and can collate work contents for each of a plurality of works (step S3).

  The task context setting unit 7 sets the context between tasks based on the context between tasks related to a plurality of tasks in step S1 (step S4).

  For each engineering schedule, the engineering schedule DB 41 associates a plurality of works, work plans, work attributes, contexts between works, and resources according to the settings by the work attribute setting unit 6 and the work context setting unit 7. The schedule data is stored (step S5).

  The PERT execution part 21 calculates | requires the float which is a work margin period for every operation | work based on engineering schedule data (step S6).

  The priority order evaluation unit 22 sets a priority order for ranking which one of the plurality of works to be executed first based on the float and a predetermined evaluation function for each of the plurality of works (step S7). .

  The resource landslide implementation unit 23 allocates resources for a plurality of operations planned in the engineering schedule (step S8).

  After step S8, the implementation ES management unit 33a adjusts the engineering schedule data according to the allocation of resources for a plurality of operations (step S9).

  The display unit 51 controls display when inputting and editing the engineering schedule data (step S10).

  The implementation ES management unit 33a registers or updates the engineering schedule in the engineering schedule DB 41 (step S11).

  The work input unit 12 and the resource input unit 11 wait for whether the input or editing operation is finished (step S12). When the operation is not finished (No in Step S12), the work input unit 12 and the resource input unit 11 return the process to Step S1. On the other hand, when the operation is finished (Yes in step S12), the work input unit 12 and the resource input unit 11 finish this process.

  The main device configuration of the engineering schedule management apparatus 10a shown in FIG. 1 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), a keyboard, and a mouse. Further, a configuration (computer) including a monitor or the like may be used.

  In the case of such a configuration, for example, a program for executing the engineering schedule management process as described above is provided in the engineering schedule management device 10a, and each of the engineering schedule management devices 10a is executed by the CPU, RAM, etc. according to the program. The processing in the processing unit (each processing unit shown in FIG. 1) is executed.

  In addition to a configuration in which an operator directly inputs and edits from a keyboard, a mouse, etc., the engineering schedule management apparatus 10a includes communication means such as a network card, and inputs and edits from outside via a LAN or the like. May be provided.

  According to the first embodiment, it is possible to generate and manage an engineering schedule by taking into consideration constraints such as ordering and delivery date, and eliminating duplication of resources and work based on priority.

[Second Embodiment]
FIG. 14 is a block diagram illustrating a configuration of an engineering schedule management apparatus according to the second embodiment. Hereinafter, the engineering schedule management apparatus of the second embodiment shown in FIG. 14 will be described with reference to FIGS. 15 to 19 as appropriate.

  The engineering schedule management apparatus of the second embodiment further includes operation means in addition to the configuration of the engineering schedule management apparatus of the first embodiment.

  Specifically, the engineering schedule management apparatus 10b includes an input / editing means 1, an adjusting means 2, an operating means 3b, a storage means 4, and a display means 5, as shown in FIG.

  The operation means 3b is a means for operating the progress management of the project after the start of the project, incorporation of the pending work into the schedule, and the like.

  Hereinafter, the configuration of the operation unit 3b illustrated in FIG. 14 will be mainly described.

  The operation means 3b includes a pending management unit 31, a progress management unit 32, and an implementation ES (engineering schedule) management unit 33b.

  For example, if a problem occurs while the schedule is being implemented based on an already registered engineering schedule, it is necessary to register the work for handling the problem (pending work) as an additional work to the engineering schedule. Sometimes.

  In such a case, the problem management unit 31 can register the problem work in the already registered engineering schedule or the engineering schedule being created. The pending management unit 31 enables the pending work to be input, edited, and registered in the engineering schedule DB 41 for each engineering schedule.

  The pending management unit 31 generates a second engineering schedule in which the pending work is incorporated (inserted) based on the first engineering schedule.

  In this case, the suspension management unit 31 temporarily registers the first engineering schedule without inserting the suspension operation immediately (for example, sets the suspension flag in FIG. 4 to “1”), and inserts the suspension operation later. The second engineering schedule can be generated and registered in the engineering schedule DB 41. In addition, it is possible to cancel (discard) the pending work without inserting it and maintain the registration in the engineering schedule DB 41 as the first engineering schedule.

  The input, editing and registration of the pending work are processed via the work input unit 12. In addition, the setting of the context between the engineering schedule work and the pending work created so far is processed through the pending manager 31. Specifically, the concern management unit 31 sets (sets) “1” in the concern flag of the work attribute data associated with the pending work.

  15, FIG. 16, FIG. 17 and FIG. 18 show an example of the process of the pending work by the pending manager 31. FIG.

  For example, it is assumed that the engineering schedule (work A to work E) illustrated in FIG. 15 is registered in the engineering schedule DB 41. Then, it is assumed that the operator performs editing to add the pending work F (the pending flag “1”) to the engineering schedule.

  In the engineering schedule (first engineering schedule) shown in FIG. 15, an example of an arrangement pattern in which the pending work F is placed in the process before or after the work C is the engineering schedule (second engineering schedule) shown in FIG. 16. As described above, there are a plurality of types of arrangement patterns that can be implemented. Assume that the arrangement patterns (1) to (6) of the engineering schedule shown in FIG. 16 are possible arrangement patterns.

  In the first engineering schedule, the operator drags the pending work input by the work input unit 12 onto the arrow line input / output from the work for which the operator wants to set the context on the display screen of the display unit 51 using a mouse or the like. -Perform an AND drop operation.

  With this operation, the pending work can be inserted before and after the work already registered in the first engineering schedule (before and after the process). The concern management unit 31 sets the previous operation or the subsequent operation as the operation bar selected by the previous / next operation selection unit 17 according to the insertion position.

  Specifically, for example, as shown in FIG. 17, the operator drags a pending work F that has not yet been set on the display screen of the display unit 51 and is stretched between the work A and the work C. By dropping so as to overlap the arrow line, it is possible to easily insert the pending work F and set the context. Thereby, the arrangement pattern (1) of the second engineering schedule shown in FIG. 16 can be easily set.

  Further, for example, as shown in FIG. 18, an operator drags a pending work F that has not yet been set on the display screen by the display unit 51, and an arrow line stretched between the work C and the work D By dropping so as to overlap with both the arrow line extending between the work C and the work E, it is possible to easily insert the pending work F and set the context. Thereby, the arrangement pattern (6) of the second engineering schedule shown in FIG. 16 can be easily set.

  As a result, work attribute data, work plan data, contextual data, and the like associated with the pending work F are reflected in the data corresponding to the insertion position. When the context between the works is determined, “0” is set (reset) in the pending flag of the work attribute data linked to the pending work F.

  As described above, the problem management unit 31 can generate the second engineering schedule in which the problem work is incorporated into the first engineering schedule. That is, the concern management unit 31 reflects work attribute data, work plan data, contextual data, and the like based on the generated second engineering schedule on each table associated with the first engineering schedule. As a result, the engineering schedule DB 41 is updated as the second engineering schedule in which the pending work is incorporated.

  Further, for example, when a pending work is temporarily registered as an additional work without being incorporated into the engineering schedule, and it is no longer necessary to add the pending work to the engineering schedule later, the temporarily registered pending work can be discarded. In this case, the concern management unit 31 can keep the first engineering schedule in the engineering schedule DB 41.

  For example, when the already-registered engineering schedule is in progress, the pending work described above may be inserted before or after any work in the middle of the schedule.

  In the present embodiment, the engineering schedule can be easily changed according to the degree of progress of the project not only before the start of the project but also after the start. In addition, when it is determined that it is not necessary to add a pending work, it is not necessary to change the engineering schedule without adding the pending work.

  If the engineering schedule has already progressed and some work has been completed, the fixed work can be set as a restriction condition by setting the fixed flag to “1”, and a pending work can be added.

  The progress management unit 32 performs progress management on work including pending work. The progress management unit 32 registers the progress rate for each work number and each progress measurement date and time in association with the work plan table T31 in order to perform progress management for each work. Here, the progress rate is an index indicating the degree of achievement of work (for example, a range of 0 to 100%).

  Therefore, the progress management unit 32 receives an input of the progress rate for each work number and progress measurement date and time, and registers the input progress rate and the like in the progress rate table T51 of the engineering schedule DB 41. Thereby, progress management can be performed for a plurality of operations linked to the engineering schedule in the project.

  For this purpose, in the engineering schedule DB 41, a progress rate table T51 for storing progress rate data related to the progress rate of work is generated and registered by the progress management unit 32 as appropriate. Further, the registered progress rate table T51 can be updated as appropriate.

  FIG. 19 shows an example of the progress rate table T51. Specifically, FIG. 19 shows an example of the progress rate table T51 associated with the work plan table T31A together with the work attribute table T32A.

  For example, regarding the work specified by the work number “T001”, the operator inputs that the progress rate is “5%” at the progress measurement date “2012/1/7 10:00”, and the progress management unit 32 is used. As shown in FIG. 19, it is stored in the progress rate table T51. The progress rate table T51 is registered or updated in the engineering schedule DB 41 in association with the work specified by the work number “T001” stored in the work plan table T31A.

  The implementation ES management unit 33b makes it possible to refer to the engineering schedule of one project processed as described above whether or not there is a similar design in another project from the engineering schedule DB 41 by keyword search or the like.

  An operator retrieves a project from the engineering schedule DB 41 via the work input unit 12 using, for example, a specific worker name (corresponding to a resource name) as a key. The implementation ES management unit 33b searches the resource table T21 of a plurality of engineering schedules for a resource name that matches a specific worker name as a key. Note that combinations of AND conditions, OR conditions, and the like are possible using a plurality of search keys.

  For example, the implementation ES management unit 33b displays, on the display unit 51, a list of engineering schedule project names associated with the resource table T21 that stores the matched resource names. As a result, the operator can easily search for projects including similar work. As a result, it can be used as a reference when scheduling the same type of project or conducting periodic inspections.

  In the present embodiment configured as described above, a float can be set in consideration of constraints such as ordering and delivery date, and duplication of resources can be eliminated based on priority. Furthermore, even after the registered pending work is temporarily registered (suspended) in the engineering schedule and the schedule is started, the temporarily registered pending work can be easily added to or deleted from the engineering schedule.

  According to the second embodiment, it is possible to eliminate duplication of resources and work based on the priority order in consideration of constraints such as ordering and delivery date. Furthermore, the engineering schedule can be generated and managed while the pending work that is a matter of concern is suspended in the engineering schedule. This makes it possible to easily generate and manage an engineering schedule that causes a pending work. Moreover, the engineering schedule can be managed by easily adding or deleting a pending work later.

[Other Embodiments]
As mentioned above, although several embodiment of this invention was described, these embodiment is shown as an example and is not intending limiting the range of invention. For example, the features of the embodiments may be combined. Furthermore, these embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the invention described in the claims and equivalents thereof as well as included in the scope and gist of the invention.

  DESCRIPTION OF SYMBOLS 1 ... Input / editing means, 2 ... Adjustment means, 3a, 3b ... Operation means, 4 ... Storage means, 5 ... Display means, 6 ... Work attribute setting part, 7 ... Work context setting part, 10a, 10b ... Engineering schedule Management device, 11 ... Resource input unit, 12 ... Work input unit, 13 ... Work attribute data generation unit, 14 ... Pre- and post-work attribute data generation unit, 15 ... Pre- and post-relationship data generation unit, 16 ... Pre- and post-work verification unit, 17 ... Work selection unit, 18: Pre- and post-work connection unit, 21 ... PERT execution unit, 22 ... Priority evaluation unit, 23 ... Resource hillside execution unit, 31 ... Concern management unit, 32 ... Progress management unit, 33a, 33b ... Implementation ES ( Engineering schedule) management unit, 41 ... engineering schedule DB (database), 51 ... display unit, 61 ... time axis scale

Claims (8)

An engineering schedule management device that manages the engineering schedule for a plurality of operations planned in the target engineering schedule,
A work input unit that accepts input or editing of work targets related to the plurality of work, a work plan including at least a work period, and work content;
A resource input unit that accepts input or editing for resources used in the plurality of operations;
For each of the plurality of work, a work attribute setting unit that sets a work attribute that can associate the work plan with the resource and that can collate the work content;
Based on the context between operations related to the process of the work plan, a task context setting unit that sets the context between the tasks,
For each engineering schedule, according to the settings by the work attribute setting unit and the work context setting unit, the plurality of work, the work plan, the work attributes, the context between the work, and the resources are linked. Engineering schedule DB to store as engineering schedule data;
Based on the engineering schedule data, a PERT execution unit for obtaining a float that is a margin period of the work for each work;
A priority evaluation unit that sets a priority for ranking which one of the plurality of operations to be performed first based on the float and a predetermined evaluation function for each of the plurality of operations;
A resource landslide implementation unit that allocates the resources for the plurality of operations planned in the engineering schedule;
Key data included in the engineering schedule data by adjusting the engineering schedule data in accordance with the allocation of the resources for the plurality of operations by the resource hillside execution unit, registering or updating the engineering schedule in the engineering schedule DB, An implementation engineering schedule management unit that searches from the engineering schedule DB based on
A display unit that controls display of the engineering schedule data when inputting and editing the engineering schedule data. The resource landslide implementation unit performs linking based on the priority when the work period overlaps between the works in the engineering schedule and at least a part of the linked resources cannot be allocated. The resource allocation and the work ranking between the tasks are performed, and in other cases, the resources are allocated to the plurality of tasks based on the engineering schedule data. The engineering schedule management device described in 1. A pending work which is a work not included in the first engineering schedule among the engineering schedules can be registered in the engineering schedule DB together with the plurality of works included in the first engineering schedule, and the first engineering schedule The engineering schedule management apparatus according to claim 1, further comprising a pending management unit capable of generating a second engineering schedule in which the pending work is incorporated. The predetermined evaluation function includes a function based on a cost calculation based on an income when delivered on time according to a predetermined deadline of the engineering schedule or a penalty when the delivery is not in time. The engineering schedule management apparatus according to any one of claims 3 to 4. The progress management part which registers or updates to the engineering schedule DB based on the input or edit about the progress rate of the work for each work in the engineering schedule is further provided. 5. The engineering schedule management device according to any one of 4. The execution engineering schedule management unit, when another engineering schedule similar to the target engineering schedule is registered based on the key data included in the engineering schedule data, from the engineering schedule DB The engineering schedule management apparatus according to any one of claims 1 to 5, wherein an engineering schedule can be extracted. An engineering schedule management method used for an engineering schedule management apparatus that manages the engineering schedule for a plurality of operations planned in a target engineering schedule,
The engineering schedule management device has the following steps:
A work input step for accepting input or editing with respect to a plurality of work targets, a work plan including at least a work period, and work contents;
A resource input step for accepting input or editing for resources used in the plurality of operations;
For each of the plurality of tasks, a task attribute setting step that sets a task attribute that can associate the task plan with the resource and that can collate the task content;
A task context setting step for setting a context between the tasks based on a context between tasks related to the process of the work plan during the task input step;
For each engineering schedule, according to the settings in the work attribute setting step and the work context setting step, the plurality of work, the work plan, the work attributes, the context between the work, and the resources are linked. An engineering schedule data storage step for storing engineering schedule data in an engineering schedule DB provided in the engineering schedule management device;
PERT execution step for obtaining a float which is a margin period of the work for each work based on the engineering schedule data;
A priority evaluation step for setting a priority for ranking which one of the plurality of operations to be performed first based on the float and a predetermined evaluation function for each of the plurality of operations;
A resource landslide implementation step of allocating the resources for the plurality of operations planned in the engineering schedule;
An implementation engineering schedule management step of adjusting the engineering schedule data according to the resource allocation for the plurality of operations after the resource mountain collapse implementation step, and registering or updating the engineering schedule in the engineering schedule DB;
When inputting and editing the engineering schedule data, a display step of performing display control on a display unit provided in the engineering schedule management device;
An engineering schedule management step of executing or executing an engineering schedule management step of registering or updating the engineering schedule in the engineering schedule DB in response to completion of the input or editing in the work input step and the resource input step. Management method. An engineering schedule management program that causes a computer to operate as an engineering schedule management apparatus that manages the engineering schedule for a plurality of operations planned in the target engineering schedule,
The engineering schedule management program causes the computer to
A work input unit that receives input or edit for a work plan and work content that includes at least a work target, a work period, and a work period; a resource input unit that receives input or edit for resources used in the plurality of work;
For each of the plurality of tasks, a work attribute setting unit that sets a work attribute that can associate the work plan with the resource and that can collate the work content;
Based on the context between operations related to the process of the work plan, a task context setting unit that sets the context between the tasks,
For each engineering schedule, according to the settings by the work attribute setting unit and the work context setting unit, the plurality of work, the work plan, the work attributes, the context between the work, and the resources are linked. Engineering schedule DB to store as engineering schedule data;
Based on the engineering schedule data, a PERT execution unit for obtaining a float that is a margin period of the work for each work;
A priority evaluation unit that sets a priority for ranking which one of the plurality of operations to be performed first based on the float and a predetermined evaluation function for each of the plurality of operations;
A resource landslide implementation unit that allocates the resources for the plurality of operations planned in the engineering schedule;
Key data included in the engineering schedule data by adjusting the engineering schedule data in accordance with the allocation of the resources for the plurality of operations by the resource hillside execution unit, registering or updating the engineering schedule in the engineering schedule DB, An implementation engineering schedule management unit that searches from the engineering schedule DB based on
An engineering schedule management program, comprising: a display unit configured to display and control the engineering schedule data when inputting and editing the engineering schedule data.

Images