WO2021153158A1 - 多主体連携計画システムおよび多主体連携計画方法 - Google Patents

多主体連携計画システムおよび多主体連携計画方法 Download PDF

Info

Publication number
WO2021153158A1
WO2021153158A1 PCT/JP2020/049290 JP2020049290W WO2021153158A1 WO 2021153158 A1 WO2021153158 A1 WO 2021153158A1 JP 2020049290 W JP2020049290 W JP 2020049290W WO 2021153158 A1 WO2021153158 A1 WO 2021153158A1
Authority
WO
WIPO (PCT)
Prior art keywords
plan
cooperation
cooperation destination
rate
response
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2020/049290
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
優美子 石戸
小林　雄一
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Priority to US17/789,156 priority Critical patent/US20230033597A1/en
Priority to CN202080091588.XA priority patent/CN114902253A/zh
Priority to DE112020005660.0T priority patent/DE112020005660T5/de
Publication of WO2021153158A1 publication Critical patent/WO2021153158A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06315—Needs-based resource requirements planning or analysis
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Program-control systems
    • G05B19/02—Program-control systems electric
    • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/41865—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by job scheduling, process planning, material flow
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/80—Management or planning

Definitions

  • the present invention relates to a multi-subject cooperation planning system and a multi-subject cooperation planning method.
  • service provision is realized as planned by creating an operation plan for each resource.
  • the operation plan of each resource is created by each management organization, and if any inconsistency occurs between each plan, adjustment work is required. For this reason, efforts are being made to ensure consistency between plans and to create feasible plans as a whole.
  • supply chain scheduling including allocation of supply sources such as parts, production schedules of multiple factories, and allocation of delivery resources can be done from the allocation of supply sources by sharing the information required for scheduling and the results of each scheduling.
  • Techniques for sequentially creating see Patent Document 1 and the like have been proposed.
  • Patent Document 2 "a technique that enables efficient and quick execution of matching processing between plans while appropriately maintaining the confidentiality of information related to plans between each organization that manages plans that cooperate with each other"
  • Patent Document 1 it is assumed that a plurality of factories accept a plan assigned to each and produce according to the plan.
  • the entity that manages and plans the resources required to provide services may span multiple companies or multiple departments of the same company, and as a result, for each planning entity.
  • the preferred plan may vary from planner to planner. In such cases, no method is given to coordinate between the plans and formulate a feasible plan as a whole.
  • Patent Document 2 discloses a method of quickly performing matching processing between plans, but a method of adjusting the inconsistency and formulating a feasible plan as a whole is given. Not.
  • an object of the present invention is to provide a technique that facilitates adjustment of the overall plan by making it possible to formulate an operation plan that is easily agreed by other planning entities.
  • a preferred aspect of the present invention is a plan generation device that generates a plurality of plan plans that satisfy a given constraint condition, an evaluation device that evaluates the plan plan by the first algorithm and generates a self-evaluation value, and a plan plan.
  • an evaluation estimation device that generates a cooperation destination estimation evaluation value by evaluating with a second algorithm different from the first algorithm, and a cooperation destination rate calculation device that calculates a rate representing the weight of the cooperation destination estimation evaluation value. It is a system. This system evaluates multiple plans based on self-evaluation values, collaborative estimated evaluation values, and objective functions calculated from rates.
  • Another preferred aspect of the present invention is a multi-subject collaboration planning method executed by an information processing device including a CPU and a storage device.
  • the first step of reading the constraint conditions from the storage device the second step of the CPU generating a plurality of draft plans satisfying the constraint conditions, and the CPU evaluating the plurality of draft plans by the first algorithm.
  • Third step of generating a self-evaluation value a fourth step in which the CPU evaluates a plurality of plans with a second algorithm different from the first algorithm and generates a collaborative estimated evaluation value, a storage device.
  • the CPU makes a purpose from the self-evaluation value, the cooperation destination estimated evaluation value, and the cooperation destination rate information for a plurality of plan proposals.
  • the sixth step of calculating the function the seventh step in which the CPU presents at least one selected from the plan to the cooperation destination and obtains a response, the CPU records the contents of the response in the storage device as past response information.
  • An example of the configuration described in the embodiment is a multi-subject cooperation planning system, in which a data reading device that reads an acceptance / rejection response to a plan from a plan cooperation destination and a plurality of plan plans that satisfy given constraint conditions are generated.
  • a plan generation device an evaluation estimation device that estimates the evaluation of the plan proposal from the cooperation destination, and a rate calculation device that calculates the rate representing the priority of the cooperation destination in a given time. Therefore, a means to select multiple values of the objective function calculated from the evaluation value of the own organization, the rate of the cooperation destination, and the evaluation estimation value from the cooperation destination and propose to the cooperation destination, and all cooperation Includes a means of displaying the details of the previously accepted plan.
  • the display displays information including the evaluation of the own organization, the evaluation estimated value from the cooperation destination, and the cooperation destination rate.
  • FIG. 1 is a system configuration diagram showing the system configuration in the embodiment.
  • reference numeral 100 is a multi-subject cooperation planning system
  • reference numeral 101 is a plan cooperation destination response providing device
  • reference numeral 102 is a network
  • reference numeral 103 is an evaluation device for own plan
  • reference numeral 104 is a data reading device
  • reference numeral 105 is a control device.
  • Code 106 is a plan generation device
  • code 107 is an evaluation estimation device from a cooperation destination
  • code 108 is a rate calculation device of a cooperation destination
  • code 109 is a DB device
  • code 110 is a terminal device
  • code 111 is past response information and code.
  • 112 is constraint condition information
  • code 113 is additional constraint condition information
  • code 114 is plan proposal information
  • code 115 is estimated evaluation index information from the cooperation destination
  • code 116 is cooperation destination rate information
  • code 117 is the plan cooperation destination system. ..
  • the multi-subject cooperation planning system 100, the planning cooperation destination system 117, and the planning cooperation destination response providing device 101 can communicate with each other via the network 102.
  • two networks 102 are connected via the plan cooperation destination response providing device 101, but this is an example, and there is no limitation on the network configuration.
  • the plan cooperation destination response providing device 101 relays the communication between the multi-subject cooperation planning system 100 and the planning cooperation destination system 117, but the planning cooperation destination response providing device 101 is omitted and the multi-subjects are omitted.
  • the cooperation planning system 100 and the plan cooperation destination system 117 may be configured to communicate directly with each other.
  • the multi-subject cooperation planning system 100 and the planning cooperation destination systems 117-1,117-2 are systems for managing the resources provided for each business or service. Now, as an example, it is assumed that the multi-subject cooperation planning system 100 manages the resource group A, the planning cooperation destination system 117-1 manages the resource group B, and the planning cooperation destination system 117-2 manages the resource group C. .. These multi-subject cooperation planning system 100 and the planning cooperation destination systems 117-1, 117-2 may be operated by different business entities (for example, corporations), or may be operated by different departments of one business entity. ..
  • the multi-subject cooperation planning system 100 shall plan the service using the resource group A.
  • the number of subjects is three, A to C, but of course, the present embodiment can be applied in the same manner even if the number of subjects is four or more.
  • the plan cooperation destination response providing device 101 is one or more types of other resource groups (resource group B) necessary for providing services in cooperation with the resource group A that creates an operation plan using the multi-subject cooperation planning system 100. , Resource group C, etc.) Provides planning information for the management organization. These plan information shall be transmitted from the plan cooperation destination system 117-1, 117-2 to the plan cooperation destination response providing device 101. Further, the plan cooperation destination response providing device 101 receives the plan information of the resource group A, and receives a response such as an approval or a correction request from another resource group management organization to the provided resource group A. Received from 1,117-2 and provided to the multi-tasking cooperation planning system 100.
  • the plan cooperation destination systems 117-1 and 117-2 may have the same configuration as the multi-subject cooperation planning system 100, but in this embodiment, the above plan information and the input of the response such as the approval or correction request are accepted and the plan is planned. It suffices to have at least a function of transmitting to the cooperation destination response providing device 101 and a function of receiving the transmission from the planning cooperation destination response providing device 101. It is assumed that the person in charge of each resource group management organization inputs the plan information and the approval or correction request.
  • resource group A is resources related to vehicle operation
  • resource group B is human resources related to operations such as drivers
  • resource group C is resources required for maintenance (equipment / equipment and maintenance). It is assumed that it is a human resource such as a member).
  • the plan cooperation destination response providing device 101 makes an approval response or revision request of the operator personnel management department and the maintenance department to the plan related to the resource A group formulated by the vehicle operation plan management department. Transmit to 100.
  • the plan related to the resource group A is approved by the operator personnel management department and the maintenance department
  • the operator personnel plan and the maintenance planning method created by each department are provided to the multi-subject cooperation planning system 100.
  • the revision request contains information in the form of providing constraints that the revision plan must meet. Generally, it is provided via HTTP (HyperText Transfer Protocol) via the Internet.
  • the network 102 is a medium for connecting the plan cooperation destination response providing device 101 and the multi-subject cooperation planning system 100, such as the Internet or a dedicated network.
  • the network 102 may be in the form of wired or wireless, and may consist of a plurality of networks.
  • the multi-organization cooperation planning system 100 is a resource group under its own organization management (this example) in order to provide services in cooperation with one or more resource groups under the control of another organization (resource groups B and C in this example). Then, the allocation plan of the resource group A) is created.
  • the multi-tasking cooperation planning system 100 includes an evaluation device 103 for its own plan, a data reading device 104, a control device 105, a plan generation device 106, an evaluation estimation device 107 from a cooperation destination, a rate calculation device 108 at a cooperation destination, and a DB device. It is configured to include 109 and a terminal device 110.
  • the own plan evaluation device 103 is a device that calculates the evaluation value seen from the own department (in this example, the vehicle operation plan management department) with respect to the plan draft generated by the plan draft generation device 106. For example, in the evaluation of the operation plan of resources related to vehicle operation, the amount of transportation by the vehicle is used as the evaluation standard.
  • the data reading device 104 receives the data provided by the planning cooperation destination response providing device 101 as an input, and is restricted when there is past response information 111 on the DB device 109 and there is a revision request in the form of a constraint condition. It is a device that saves conditions as additional constraint condition information 113.
  • the control device 105 is a device that controls each device constituting the multi-subject cooperation planning system 100 so as to formulate a multi-subject cooperation plan as a system.
  • the control device 105 also controls known processes executed by a general PC, such as transmission / reception of data via the network 102.
  • the plan generation device 106 is a device that reads the constraint condition group stored in the constraint condition information 112 and the additional constraint condition information 113 and generates one or more operation plan proposals of the resource group A that satisfies the constraint condition group.
  • the evaluation estimation device 107 from the cooperation destination is the cooperation destination (management organization such as resource group B and resource group C. In this example, the operator personnel management department and the maintenance department) with respect to the plan draft generated by the plan draft generation device 106. It is a device that calculates the evaluation estimated value seen from the viewpoint. Since the plan is evaluated from a different standpoint from the evaluation device 103 of the own plan, an evaluation algorithm different from the evaluation device 103 of the own plan is used. For example, in the operation plan of resources required for maintenance, the operating rate of equipment is used as an evaluation standard.
  • the cooperation destination rate calculation device 108 is a device that calculates a rate indicating the importance of each organization that manages resource group B, resource group C, etc. for an organization that manages resource group A using the multi-subject cooperation planning system 100. Is.
  • the DB device 109 is a database (DB) that holds the data created by each device, and includes past response information 111, constraint condition information 112, additional constraint condition information 113, plan proposal information 114, and estimated evaluation index information from the cooperation destination. It is configured to include data such as 115 and cooperation destination rate information 116.
  • the DB has functions for registering data, searching for data, extracting related data, and deleting data.
  • the DB device 109 is realized by a general PC, and in that case, the DB device can be realized by using a general PC and general DB software running on the general PC.
  • the terminal device 110 is a terminal operated by the operator of the multi-subject cooperation planning system 100.
  • the terminal device 110 is a device that displays the operation plan of the drafted resource group A and advances the processing flow by receiving the approval of the operator.
  • the data used includes the data described below.
  • the past response information 111 is a response to the operation plan of resource group A proposed by the multi-tasking cooperation planning system 100, such as approval, selection, and rejection with additional constraints from management organizations such as resource group B and resource group C. Information.
  • the constraint condition information 112 is the constraint condition recognized by the resource group A when making an operation plan for the resource group A. This is a condition that enables physical continuous movement of the vehicle, such as the presence / absence of a vehicle, the presence / absence of a railroad track, and sufficient travel time, for example, when the resource group A is a resource related to vehicle operation. including. Further, for example, when the resource group A is a resource related to maintenance, the presence / absence of maintenance equipment, the presence / absence of maintenance personnel, and the presence / absence of sufficient maintenance time are included.
  • Additional constraint condition information 113 is an additional constraint condition imposed by an organization that provides services in cooperation with resource group A, such as a management organization of resource group B and resource group C, when formulating an operation plan for resource group A.
  • resource group A is a resource related to vehicle operation
  • resource group C is a resource related to maintenance
  • the organization that manages resource group C says, "A specific vehicle is specified by a specific time for maintenance. Imposing an additional constraint of "move to location”.
  • the estimated evaluation index information 115 from the collaborative partner is the estimated value information of the evaluation of the operation plan of the resource group A from the viewpoint of the management organization such as the resource group B and the resource group C. It may be a set of evaluation estimates for each plan, or a function for calculating evaluation estimates from an operation plan.
  • the cooperation destination rate information 116 is the importance information of the management organizations such as resource group B and resource group C as seen from the management organization of resource group A. The details of these data will be described later.
  • each device or system of FIG. 1 may be configured by using a single PC, or may share functions by any plurality of PCs.
  • the configuration of each device the internal configuration of a general PC will be described with reference to the diagram showing the configuration of the PC 200 in FIG.
  • reference numeral 201 is a CPU
  • reference numeral 202 is a memory
  • reference numeral 203 is an interface
  • reference numeral 204 is a network interface
  • reference numeral 205 is a keyboard
  • reference numeral 206 is a screen
  • reference numeral 207 is a mouse
  • reference numeral 208 is a hard disk.
  • the CPU 201 is a central processing unit, which is a device capable of executing a program recorded in the memory 202 or transferred in advance from the hard disk 208 to the memory 202.
  • the program can be used by a PC and may be introduced by a removable storage medium.
  • a device for reading the storage medium is connected to the interface 203.
  • the program may be introduced into the PC by the network interface 204 via the communication medium (communication line or carrier wave on the communication line), if necessary.
  • Memory 202 temporarily records programs and data.
  • Interface 203 is for connecting devices in the PC system.
  • the network interface 204 is a device for communicating with a PC or the like outside the PC system.
  • the keyboard 205 is a device operated by the operator of the PC system in order to input commands and data to the PC system.
  • the screen 206 is a device for displaying the processing result and the like.
  • the mouse 207 is a device that specifies a position on the screen and conveys some action to the CPU 201 by moving a pointer displayed on the screen and causing an operator to press a button at an arbitrary place.
  • the mouse 207 can be replaced by another pointing device such as a touch panel. When replacing the mouse 207 with a touch panel, the pointer is usually unnecessary.
  • the hard disk 208 is a device for storing programs and data, and can be configured by, for example, a magnetic disk, a non-volatile memory, or the like.
  • the programs and data stored in the hard disk 208 are normally retained even when the power of the hard disk 208 is turned on after the power is turned off.
  • An operating system (OS) may be installed in the hard disk 208 in advance. By doing so, it becomes possible to specify the program by using the file name.
  • the OS is the basic software of a computer, and a generally widely known OS can be used.
  • each device may be configured by one PC, or all the devices may be configured by one PC. Alternatively, one device may be composed of a plurality of PCs connected by a network.
  • the functions equivalent to the functions realized by the program can also be realized by hardware such as FPGA (Field Programmable Gate Array) and ASIC (Application Specific Integrated Circuit). Next, the data structure will be described.
  • FIG. 3 is a diagram showing a data structure of the past response information 111 in the embodiment.
  • Proposal ID 301 is a number that uniquely identifies the plan proposal processing to other organizations.
  • the proposal ID is generated when the operation plan draft generated by the plan draft generation device 106 is transmitted to the specific plan cooperation destination system 117.
  • the plan ID 302 is a number that uniquely identifies the proposed operation plan of the resource group A.
  • the plan ID is generated when the operation plan is generated by the plan generation device 106. For example, when the same plan proposal is proposed to a plurality of different organizations, it is recorded using the same plan ID and a different proposal ID.
  • the proposal destination 303 the name of the proposal destination organization in the proposal process is described.
  • the proposal date and time 304 and the response date and time 305 are the date and time when the management organization of the resource group A sends the plan proposal to the proposal destination and the response from the proposal destination organization to the plan proposal.
  • the date and time received from 101 is described.
  • the rate fluctuation 306 the rate fluctuation value when the proposal destination approves and rejects the plan is described.
  • the number before the symbol “/” indicates the rate fluctuation value when the proposal destination approves
  • the number after the proposal indicates the rate fluctuation value when the proposal destination rejects.
  • the rate fluctuation 306 changes with time, and the value is calculated by the evaluation estimation device 107 from the cooperation destination described later.
  • Response 307 is the response of the proposal destination to the proposal.
  • the additional constraint 308 describes the additional constraint when the response from the proposal destination is rejected and the additional constraint is requested.
  • the response and additional constraints of the proposal destination shall be input by the operator of the proposal destination using, for example, the keyboard of the plan cooperation destination system 117.
  • FIG. 4 is a diagram showing the data structure of the constraint variable in the constraint condition information 112 in the embodiment.
  • the variable name 401 represents a variable to be decided in order to describe the operation plan, that is, a decision variable.
  • Type 402 represents the type of variable. Possible types of variable types include, for example, integers, real numbers, character variables, and Boolean variables. Explanation 403 explains the meaning of variables. For example, the "variable" X (1,1) can take an integer value and represents the flight number in which equipment 1 is used first.
  • the data structure of the constraint variable shall be defined by the operator (for example, the administrator of the resource group A), input from the terminal device 110, and stored in the DB device 109 before the system operation.
  • FIG. 5 is a diagram showing a data structure of the constraint condition to be satisfied by the determination variable in the constraint condition information 112 in the embodiment.
  • the constraint ID 501 is an ID that uniquely defines the constraint.
  • the content of the constraint is described in the content of the constraint 502. For example, although the "constraint ID" is "1", the “constraint content” is "LT (1,1) ⁇ 40". That is, it means that it takes 40 minutes or more for the first flight of the aircraft 1 to arrive at the next stop.
  • the constraint content of the constraint condition shall be defined by the operator (for example, the administrator of the resource group A), input from the terminal device 110, and stored in the DB device 109 before system operation.
  • the plan generation device 106 can refer to the constraint conditions to be satisfied when drafting the operation plan of resource A.
  • FIG. 6 is a diagram showing the data structure of the additional constraint condition that the determination variable should satisfy in the additional constraint condition information 113 in the embodiment.
  • the additional constraint ID601 is an ID that uniquely defines the additional constraint.
  • the content of the additional constraint is described in the content of the additional constraint 602.
  • the “additional constraint ID” is "1001”
  • the additional restriction content 602 is input to the plan cooperation destination system 117 when the operator of the proposal destination to which the draft operation plan is proposed does not simply approve.
  • the additional constraint content 602 cites the variable name 401 of the constraint variable data shown in FIG.
  • the additional restriction content 602 the content transmitted from the plan cooperation destination response providing device 101 is recorded in the DB device 109 by the data reading device 104.
  • the plan generation device 106 can refer to the additional constraint conditions to be satisfied when drafting the operation plan of resource A. .. Next, the data structure of the draft plan information 114 in the embodiment will be described.
  • FIG. 7 is a diagram showing the data structure of the plan draft information 114 in the embodiment.
  • the plan draft information 114 is generated by the plan draft generation device 106.
  • the plan ID 701 is a number that uniquely identifies the operation plan draft of the resource group A.
  • the variable name 702 is a decision variable to be decided in the plan, and the value 703 describes the value of the decision variable in the plan.
  • a draft plan with a particular plan ID is explained by being given values for all determinants. That is, all plans with a "plan ID" of "1” have a value of "X (1,1)" of "5", a value of "X (1,2)” of "3", and so on. It is expressed by giving the value of the decision variable of.
  • the data structure of the estimated evaluation index information 115 from the collaborator in the embodiment will be described.
  • FIG. 8 is a diagram showing the data structure of the estimated evaluation index information 115 from the cooperation partner in the embodiment.
  • the estimated evaluation index information 115 is generated by the evaluation estimation device 107 from the cooperation partner.
  • Proposal ID 801 is a number that uniquely identifies the plan proposal process to other organizations.
  • the plan ID 802 is a number that uniquely identifies the operation plan draft of the resource group A in this embodiment.
  • the scheduled date and time of the proposal 803 describes the scheduled date and time when the plan represented by the plan ID is transmitted to the plan cooperation destination response providing device 101 by the proposal process represented by the proposal ID.
  • Estimated evaluation values 804,807 from other organizations indicate the evaluation values of the draft plan evaluated from the standpoint of other organizations (in this example, the management bodies of resources B and C).
  • the algorithm for evaluation shall be set from the terminal device 110 before operating the system.
  • the algorithm for evaluation may be created and provided by another organization itself.
  • the algorithm for evaluation may be time-invariant or time-dependent.
  • the algorithm is time-dependent. That is, even in the same plan, the estimated evaluation value changes depending on the planned proposal date and time 803. This is because even the same organization may have to give priority to the convenience of its own organization depending on the time.
  • the time-dependent algorithm may be the same as the evaluation algorithm of the evaluation device 103 of the self-plan.
  • the rate fluctuation value 805,806,808,809 is calculated by the evaluation estimation device 107 from the cooperation destination based on the estimated evaluation value 804,807.
  • the rate fluctuation value is calculated with the policy that the lower the estimated evaluation of other organizations, the larger the rate increase rate at the time of approval and the smaller the rate decrease rate at the time of refusal. That is, the rate fluctuation value is determined depending on both the estimated evaluation and the response of other organizations. For example, if the estimated evaluation value is low but the approval is given, it should be reflected in the rate of the organization as a reward.
  • the estimated evaluation value 804 of B for the plan proposal specified by the plan ID "1" and the proposal ID "1" is "80".
  • B's rate fluctuation value 805 is "0
  • B rejects the proposal B's rate fluctuation value 806 is "-20”.
  • the estimated evaluation value 807 of C for the proposal is "60”
  • the rate fluctuation value 808 when C accepts the proposal is "+20”
  • the rate fluctuation value 809 when rejecting the proposal is "0".
  • FIG. 9 is a diagram showing the data structure of the cooperation destination rate information 116 in the embodiment.
  • the cooperation destination rate information 116 is updated by calculating the rate value with reference to the estimation evaluation index information 115 by the cooperation destination rate calculation device 108 each time the response of approval or refusal from the cooperation destination is received.
  • the date 901 and the time zone 902 are dates and time zones that uniquely identify a time zone having a certain width.
  • the rate values of the cooperation destinations on the date 901 and the time zone 902 are described. That is, the rate value 903 of B in "6: 00-7: 00" of "2018/12/01" is "50", and the rate value 904 of C is "60".
  • the data structure has been described above. Next, the processing will be described. First, the outline processing of the system will be described.
  • FIG. 10 is a schematic diagram of the processing flow S1000 of the system in the embodiment.
  • Step S1001 is a process in which the CPU 201 of the control device 105 instructs the terminal device 110 to wait for an operator command.
  • Step S1002 is a process in which the CPU 201 of the terminal device 110 displays a command waiting screen on the screen 206 of the terminal device 109.
  • Step S1003 is a process in which the operator of the multi-subject cooperation planning system 100 instructs the terminal device 110 to make an operation plan for the resource group A.
  • Step S1004 is a process in which the CPU 201 of the terminal device 110 reports the operator command reception to the control device 105.
  • Step S1005 is a process in which the CPU 201 of the control device 105 instructs the plan plan generation device 106 of the operation plan plan of the resource group A.
  • step S1006 the CPU 201 of the plan generation device 106 instructs the data reading device 104 to read the constraint condition information 112 and the additional constraint condition information 113, and the data reading device 104 reads the data.
  • Step S1007 is a process in which the CPU 201 of the plan draft generation device 106 creates a plurality of types of plan plans that satisfy the constraint condition information 112 and the additional constraint condition information 113, and saves them in the DB device 109 as the plan plan information 114.
  • a plan that satisfies the given constraints can be created by using a general-purpose mathematical optimization tool such as a CP solver or a MIP solver.
  • Step S1008 is a process in which the CPU 201 of the control device 105 instructs the evaluation estimation device 107 from the cooperation destination to calculate the cooperation destination evaluation estimation value for the plan proposal stored in the plan proposal information 114.
  • Step S1009 is a step in which the CPU of the evaluation estimation device 107 from the cooperation destination calculates the estimated value of the evaluation from the cooperation destination and saves it in the DB device 109 as the estimation evaluation index information 115 from the cooperation destination.
  • the evaluation estimated value (804,807 in FIG. 8) from the cooperation destination may be designed as a function for the operation plan of the resource group A, for example. For example, if the operation plan of resource group A is a railway main line operation plan and the partner B is an organization that manages resources related to maintenance, the evaluation from B's point of view is for the berth of each vehicle and for maintenance.
  • the function may be designed as a function consisting of the time of arrival at the berth, the time of departure from the berth for the next Japan flight operation, and the scheduled date and time of the plan proposal.
  • the function is designed by collecting the evaluation value data given by the operator B for the past plan, and using general data mining technology such as curve fitting and machine learning. May be good.
  • the planned date and time of the plan proposal may be calculated by adding a certain number of times to the planning time, for example.
  • the CPU of the evaluation estimation device 107 from the cooperation destination changes the rate of the cooperation destination organization when the proposal plan is accepted or rejected by the cooperation destination organization based on the evaluation estimation value. Is calculated. This may be calculated using, for example, a reference value for estimated evaluation is set for acceptance and rejection, and a difference from the reference value is used.
  • the estimated evaluation value of B for the draft plan may be EV
  • the reference value at the time of acceptance may be SV_accept
  • the rate fluctuation ⁇ R_accept at the time of acceptance may be calculated by the equation (1).
  • the estimated evaluation value of B for the plan may be EV
  • the reference value at the time of refusal may be SV_reject
  • the rate fluctuation at the time of refusal may be calculated by the equation (2).
  • any other function may be designed for the calculation of the rate fluctuation value.
  • it may be designed as a function in which the rate fluctuation value depends on the proposed time.
  • step S1010 the CPU 201 of the control device 105 reads the plan draft information 114, the estimated evaluation index information 115 from the cooperation destination, the cooperation destination rate information 116, and the evaluation result of the evaluation device 103 of the own plan, and one or more plans.
  • This is a process of selecting a plan and transmitting it to the plan cooperation destination response providing device 101.
  • the plan proposal to be transmitted to the plan cooperation destination response providing device 101 is evaluated and sorted by, for example, the objective function of the equation (3).
  • one or a plurality of plans that increase the objective function are preferentially selected from a plurality of plans.
  • the selected plan may be selected by having the operator of the multi-subject cooperation planning system 100 display and select a plurality of the selected plans on the terminal device 110, and the selected plan may be transmitted to the plan cooperation destination response providing device 101.
  • the largest objective function may be automatically transmitted to the plan cooperation destination response providing device 101.
  • V_A is the KPI (Key Performance Indicator) evaluation of the own organization for the plan
  • EV_B and EV_C are the evaluation estimates from B and C for the plan
  • R_B and R_C are the organization B and the organization C, respectively.
  • V_A is calculated by the evaluation device 103 of the own plan by the first algorithm.
  • EV_B and EV_C are calculated by the evaluation estimation device 107 from the cooperation destination by the second and third algorithms.
  • R_B and R_C are calculated by the cooperation destination rate arithmetic unit 108.
  • an arbitrary function consisting of R_B and R_C may be used as a weight.
  • step S1011 the CPU 201 of the plan cooperation destination response providing device 101 presents the contents of the selected plan proposal to the cooperation destination, acquires an acceptance / rejection response for each proposal, saves the result in the past response information 111, and saves the result. This is a process of reporting the response acquisition to the control device 105.
  • Step S1012 is a process in which the cooperation destination rate calculation device 108 calculates the cooperation destination rate.
  • the cooperation destination rate calculation device 108 may refer to the past response information 111 shown in FIG. 3 and update the rate for each entry according to the content of the response 307.
  • a predetermined number of entries may be batch-processed.
  • the updated rate value is recorded as the cooperation destination rate information 116.
  • an appropriate weighting function set for each cooperation destination may be applied to the sum.
  • a function of the cooperation destination rate in the operation time of one day is determined in advance based on the flexibility and seriousness of the resource operation of the cooperation destination, and this function is translated and scaled based on the sum.
  • the cooperation destination rate may be calculated by.
  • Step S1013 is a process in which the control device 105 reads the past response information 111 and determines whether or not there is a plan that all the cooperation destinations accept. If it exists, the process proceeds to step S1014, and if it does not exist, the process proceeds to step S1015.
  • Step S1014 is a process in which the CPU 201 of the terminal device 110 displays the plan and the rate information of the cooperation destination on the screen of the terminal device 110.
  • Step S1015 is a process in which the CPU 201 of the data reading device 104 reads the additional constraint from the past response information 111 and saves it in the DB as the additional constraint condition information 113. After step S1015 processing, the process returns to step S1005 based on the updated additional constraint information.
  • step S1013 if there is no plan accepted by all the collaborators even after the predetermined time or the predetermined step has elapsed, in step S1014, the CPU 201 of the terminal device 110 is displayed on the screen of the terminal device 110. The process may be terminated by displaying that the contact information has not been accepted.
  • step S1104 the result display screen will be described with reference to FIGS. 11 and 12.
  • FIG. 11 is a diagram showing an outline of the result display screen in the embodiment.
  • code 1101 is the result display screen
  • code 1102 is the operation plan display unit
  • code 1103 is the plan switching tab
  • code 1104 is the KPI display unit
  • code 1105 is the rate ratio display unit
  • code 1106 is the rate display switching button. be.
  • the result display screen 1101 is displayed on the screen 206 of the terminal device 110.
  • the operation plan display unit 1102 is a part that displays the operation plan of the resource group A accepted by all the cooperation partners. If multiple plans are accepted, the other plans are displayed by pressing the plan switching tab 1103.
  • the KPI display unit 1104 displays related KPIs such as the KPIs in the own organization and the estimated evaluation from the cooperation partner for the plan proposal displayed by the operation plan display unit 1102.
  • the rate ratio display unit 1103 displays the current ratio of the cooperation destination rate. By pressing the rate display switching button 1106, the time change of the cooperation destination rate may be displayed instead of the current ratio.
  • FIG. 12 shows a display screen switched to the time change display of the rate.
  • FIG. 12 is a diagram in which the display format of the cooperation destination rate information is switched among the result display screens in the embodiment.
  • reference numeral 1201 is a rate-time change display unit.
  • the rate-time change display unit displays the time change of the cooperation destination rate as the time on the horizontal axis and the rate on the vertical axis.
  • the rate display switching button 1106 is pressed, the display returns to the current ratio display of the linked rate.
  • FIG. 13 is a flow chart illustrating the flow up to the creation of the overall plan in the embodiment.
  • process S1000 the multi-subject cooperation planning system 100 creates an operation plan for resource A.
  • This process is the process described with reference to FIG.
  • process S1013 one or more plan proposals accepted by all collaborators have been created.
  • process S1014 This result is displayed to the operator of the multi-subject cooperation planning system 100 as shown in FIG. 11 or 12 (process S1014).
  • the operator uses the terminal device 110 to select one to be proposed to the cooperation destination.
  • control device 105 of the multi-subject cooperation planning system 100 is selected as the planning cooperation destination system 117-1,117-2 via the network 102-1, the planning cooperation destination response providing device 101, and the network 102-2. Notify the contents of the operation plan of resource A.
  • the cooperation destination creates an operation plan of own resources B and C so as to match the operation plan of resource A received by the plan cooperation destination systems 117-1, 117-2.
  • This process may be manually created at the cooperation destination.
  • the plan cooperation destination systems 117-1 and 117-2 may be automatically created by providing a configuration equivalent to the plan draft generation device 106.
  • the cooperation destination sends the operation plans B and C of its own resources to the plan cooperation destination response providing device 101 in the plan cooperation destination systems 117-1 and 117-2.
  • the plan cooperation destination response providing device 101 integrates the operation plans of resources A, B, and C to generate an overall plan. Since the contents of the operation plan of each resource and their integration are well known, details are omitted.
  • the plan cooperation destination response providing device 101 transmits the overall plan to the multi-subject cooperation planning system 100 and the planning cooperation destination systems 117-1,117-2.
  • the overall plan generation process S5000 and the notification process S6000 are performed by the plan cooperation destination response providing device 101, but the plan cooperation destination response providing device 101 is omitted, and the multi-subject cooperation planning system 100 processes the processing S5000. It can also be configured to perform processing S6000.
  • the multi-subject cooperation planning system 100 creates the operation plan of resource A for which the approval of the cooperation destination has been obtained. This plan is sent to the collaborator, and the collaborator creates an operation plan for resources B and C according to this plan.
  • the overall plan is completed by integrating the operation plans of each resource.
  • the overall plan can be created more efficiently than the conventional method of creating the overall plan by performing the coordination work between the plans after formulating the operation plan of each resource.
  • the objective function for evaluating the plan generated by the plan draft generation device 106 of the multi-subject cooperation planning system 100 includes the evaluation element of the cooperation destination in addition to the self-evaluation element. For this reason, it is possible to propose a plan that is easy for the collaborators to agree on. Further, since the evaluation elements of the cooperation destinations are weighted, it is easy to adjust the contents of the plan generated by the plan draft generation device 106 even when there are a plurality of cooperation destinations.
  • the multi-subject cooperation planning system 100 collects the responses from the cooperation destination, and the cooperation destination rate calculation device 108 calculates the weight of the cooperation destination based on the response.
  • the weight of the cooperation destination By adjusting the weight based on the past response of the cooperation destination, the behavioral characteristics of the cooperation destination can be reflected in the objective function. For example, by adjusting the weight of the collaborative partner based on the response contents of approval and refusal to the plan, the weight of the collaborative partner becomes large, and it can be expected that the future plan will be given preferential treatment. For this reason, each planning entity voluntarily formulates a plan that is easier to agree on in consideration of the convenience of other entities, and if there is inconsistency between plans, the entity that can transfer will be motivated to voluntarily transfer. be able to. Therefore, coordination between plans can be facilitated and expedited.
  • the provision of transportation services by railroad was explained as an example, but it can be similarly applied to the fields of aviation, ships and other passengers and transportation.
  • this embodiment can also be applied in the fields of manufacturing and distribution when adjusting the operation plans of a plurality of resources.
  • the resources are A, B, and C for the sake of explanation, but it goes without saying that the same can be applied to resources of 2 or 4 or more.
  • the present invention is not limited to the above-mentioned embodiment, and includes various modified examples.
  • the above-described embodiment has been described in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to the one including all the described configurations.
  • it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment and it is also possible to add the configuration of another embodiment to the configuration of one embodiment.
  • each of the above configurations, functions, processing units, processing means, etc. may be realized by hardware by designing a part or all of them by, for example, an integrated circuit. Further, each of the above configurations, functions, and the like may be realized by software by the processor interpreting and executing a program that realizes each function. Information such as programs, tables, and files that realize each function can be placed in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.
  • SSD Solid State Drive
  • control lines and information lines indicate those that are considered necessary for explanation, and not all control lines and information lines are necessarily indicated on the product. In practice, it can be considered that almost all configurations are interconnected.
  • the application fields of the present invention are not limited to the railway business, but include aircraft operation and MaaS (Mobility as a Service). It can also be applied to resource allocation in the transportation service industry, production industry, and other service industries.
  • Multi-subject cooperation planning system 101... Plan cooperation destination response providing device 102... Network 103 ... Multi-subject cooperation planning system 104... Data reading device 105... Control device 106... Plan generator 107... Evaluation estimation device from the partner 108... Cooperation destination rate arithmetic unit 109... DB device 110 ... Terminal device 111... Past response information 112... Constraint information 113... Additional constraint condition information 114... Plan information 115... Estimated evaluation index information from the partner 116... Linkage rate information 1101... Result display screen 1102... Operation plan display section 1103... Plan switching tab 1104... KPI display 1105... Rate ratio display 1106... Rate display switching button 1201... Result display screen

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Operations Research (AREA)
  • Game Theory and Decision Science (AREA)
  • Development Economics (AREA)
  • Marketing (AREA)
  • Educational Administration (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • General Factory Administration (AREA)
PCT/JP2020/049290 2020-01-29 2020-12-29 多主体連携計画システムおよび多主体連携計画方法 Ceased WO2021153158A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US17/789,156 US20230033597A1 (en) 2020-01-29 2020-12-29 Multi-subject cooperation plan system and multi-subject cooperation plan method
CN202080091588.XA CN114902253A (zh) 2020-01-29 2020-12-29 多主体协同计划系统及多主体协同计划方法
DE112020005660.0T DE112020005660T5 (de) 2020-01-29 2020-12-29 Planungssystem und planungsverfahren für eine multi-subjekt-kooperation

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020-012131 2020-01-29
JP2020012131A JP7408417B2 (ja) 2020-01-29 2020-01-29 多主体連携計画システムおよび多主体連携計画方法

Publications (1)

Publication Number Publication Date
WO2021153158A1 true WO2021153158A1 (ja) 2021-08-05

Family

ID=77078347

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/049290 Ceased WO2021153158A1 (ja) 2020-01-29 2020-12-29 多主体連携計画システムおよび多主体連携計画方法

Country Status (5)

Country Link
US (1) US20230033597A1 (https=)
JP (1) JP7408417B2 (https=)
CN (1) CN114902253A (https=)
DE (1) DE112020005660T5 (https=)
WO (1) WO2021153158A1 (https=)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7799421B2 (ja) * 2021-10-04 2026-01-15 株式会社日立製作所 計画整理案立案装置、計画整理案立案装置による計画整理案立案方法及びコンピュータプログラム
JP2025030449A (ja) * 2023-08-23 2025-03-07 株式会社日立製作所 リソース管理システム、統合リソース管理装置、及びリソース管理方法
WO2025158489A1 (ja) * 2024-01-22 2025-07-31 三菱電機株式会社 保守計画作成支援装置、保守計画作成支援方法、及び保守計画作成支援プログラム

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015068231A1 (ja) * 2013-11-07 2015-05-14 株式会社 日立製作所 計画連携システムおよび計画連携方法
WO2018220885A1 (ja) * 2017-05-31 2018-12-06 株式会社日立製作所 生産計画作成装置、生産計画作成方法及び生産計画作成プログラム

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5630070A (en) * 1993-08-16 1997-05-13 International Business Machines Corporation Optimization of manufacturing resource planning
EP1163604A4 (en) * 1998-11-30 2002-01-09 Siebel Systems Inc ASSIGNMENT MANAGER
US7043320B1 (en) * 2003-10-16 2006-05-09 Jrg Software, Inc. Method and apparatus for planning a manufacturing schedule using an adaptive learning process
JP4786935B2 (ja) * 2004-05-18 2011-10-05 株式会社神戸製鋼所 生産計画作成方法及び生産計画作成装置、並びにプログラム
JP5643502B2 (ja) 2009-10-30 2014-12-17 アスプローバ株式会社 複数工場の生産スケジュール作成方法
WO2013084268A1 (ja) * 2011-12-09 2013-06-13 株式会社日立製作所 異主体間連携による資源融通方式
CN105243233B (zh) * 2015-11-04 2016-08-24 中南大学 一种复杂山区铁路线站协同优化方法
JP6461779B2 (ja) * 2015-12-21 2019-01-30 株式会社日立製作所 計画調整システムおよび計画調整方法
JP6689316B2 (ja) * 2018-06-05 2020-04-28 株式会社日立製作所 計算機システム及び学習制御方法
US11403600B1 (en) * 2018-06-25 2022-08-02 United Services Automobile Association (Usaa) Systems and methods for interactive scheduling
US20200104173A1 (en) * 2018-09-29 2020-04-02 CA Software Österreich GmbH Communication process load balancing in an automation engine

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015068231A1 (ja) * 2013-11-07 2015-05-14 株式会社 日立製作所 計画連携システムおよび計画連携方法
WO2018220885A1 (ja) * 2017-05-31 2018-12-06 株式会社日立製作所 生産計画作成装置、生産計画作成方法及び生産計画作成プログラム

Also Published As

Publication number Publication date
US20230033597A1 (en) 2023-02-02
JP7408417B2 (ja) 2024-01-05
CN114902253A (zh) 2022-08-12
DE112020005660T5 (de) 2022-09-01
JP2021117851A (ja) 2021-08-10

Similar Documents

Publication Publication Date Title
US11023831B2 (en) Optimizing a business model of an enterprise
Zak The methodology of multiple criteria decision making/aiding in public transportation
US11941560B2 (en) Systems and methods for generating construction models for construction projects
Visintin et al. Development and implementation of an operating room scheduling tool: an action research study
US20110093539A1 (en) System And Method For Innovation And Idea Management
KR101798336B1 (ko) 국가직무능력표준 기반의 직무 자동매칭 서비스 방법 및 그를 이용하는 시스템
Enayati et al. Ambulance redeployment and dispatching under uncertainty with personnel workload limitations
PG Petroianu et al. A light‐touch routing optimization tool (RoOT) for vaccine and medical supply distribution in Mozambique
WO2021153158A1 (ja) 多主体連携計画システムおよび多主体連携計画方法
US20230316197A1 (en) Collaborative, multi-user platform for data integration and digital content sharing
Chen et al. A quality management approach to guide the executive management team through the product/service innovation process
JP2021117851A5 (https=)
Villarreal et al. A Lean transportation approach for improving emergency medical operations
Bertsimas et al. Policy analytics in public school operations
Arendt et al. Intelligent control of freight services on the basis of autonomous multi-agent transport coordination
Feldhaus et al. Incorporating costing study results into district and service planning to enhance immunization programme performance: a Zambian case study
Kjellmark et al. Toward Construction 5.0: Bridging AI and People through Continuous Learning
WO2021250946A1 (ja) 多主体連携計画システムおよび多主体連携計画方法
Dohan et al. Value stream mapping in lean healthcare: A brief introduction and application
Bensbih et al. On line appointment systems in a patient centric strategy: a qualitative approach in a case study for hospitals in Morocco
JP2006119917A (ja) 工程管理支援システム、工程管理支援方法及び工程管理支援プログラム
Farr et al. Planning guide for computer program development
Ding et al. Supplier capacity analysis for a manufacturing firm with a case study
Barton et al. Digitalization in companies: From theoretical approaches to practical
Jolayemi et al. A composite process for establishing and continuously maintaining end-to-end visibility in multi-tier supplier network systems

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20916393

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 20916393

Country of ref document: EP

Kind code of ref document: A1