EP1480144A1 - La planification et le séquencement pour un système et une méthode de rétablissement de défaillance - Google Patents

La planification et le séquencement pour un système et une méthode de rétablissement de défaillance Download PDF

Info

Publication number
EP1480144A1
EP1480144A1 EP04009991A EP04009991A EP1480144A1 EP 1480144 A1 EP1480144 A1 EP 1480144A1 EP 04009991 A EP04009991 A EP 04009991A EP 04009991 A EP04009991 A EP 04009991A EP 1480144 A1 EP1480144 A1 EP 1480144A1
Authority
EP
European Patent Office
Prior art keywords
capabilities
production
jobs
less
work units
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
EP04009991A
Other languages
German (de)
English (en)
Inventor
Markus P. J. Fromherz
Daniel G. Bobrow
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.)
Xerox Corp
Original Assignee
Xerox Corp
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 Xerox Corp filed Critical Xerox Corp
Publication of EP1480144A1 publication Critical patent/EP1480144A1/fr
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • 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/80—Management or planning

Definitions

  • This invention relates generally to the control and management of automated manufacturing systems, and more particularly to a system and method for failure recovery and state transitioning of a reconfigurable production system.
  • Model-based planning and scheduling (the system control software) in production systems is often used only for creating schedules for normal behavior, but is not involved in recovering from failures in the execution of these schedules and in transitioning from inconsistent to consistent states of the system.
  • the entire system is stopped when one of its modules goes off-line or declares a fault.
  • simple recovery procedures are invoked (e.g., to purge all work units currently in the process path and not yet delivered), and the system is then restarted to produce the uncompleted part of the current job.
  • a computer controlled system provides for configuration-specific recovery of operation in a reconfigurable production system having a plurality of modules with a plurality of alternative capabilities for processing work units.
  • the system includes a system controller having planning, scheduling, and performance failure identification functions.
  • the planning function plans utilization of selected module capabilities in the production of jobs having not less than one work unit and the scheduling function schedules utilization of selected module capabilities in the production of jobs.
  • the failure identification function identifies the failure of module capabilities to perform the work units for a scheduled job.
  • said planning function further comprises:
  • a method for configuration-specific recovery of operation in a reconfigurable computer controlled production system having a plurality of modules with a plurality of alternative capabilities for processing work units includes planning and scheduling utilization of selected module capabilities in the production of jobs having not less than one work unit. Performance commands are provided to the modules within the manufacturing system and performance failure of any module capabilities in the production of a job is identified.
  • scheduling the utilization of module capabilities in the production of jobs comprises scheduling capabilities according to a plurality of capability representations.
  • not less than one of said capability representations comprises work units included within said at least one production system.
  • not less than one of said capability representations comprises modules included within said at least one production system.
  • the method further comprises cross-linking said plurality of information representations.
  • the method further comprises recovering from performance failure of not less than one of said selected module capabilities in the production of said jobs having not less than one work unit.
  • identifying performance failure of not less than one of said selected module capabilities comprises:
  • an article of manufacture in the form of a computer usable medium having computer readable program code embodied in the medium which, when the program code is executed by the computer causes the computer to perform method steps for configuration-specific recovery of operation in a reconfigurable computer controlled production system having a plurality of modules with a plurality of alternative capabilities for processing work units.
  • the method includes planning and scheduling utilization of selected module capabilities in the production of jobs having not less than one work unit. Performance commands are provided to the modules within the manufacturing system and performance failure of any module capabilities in the production of a job is identified.
  • Disclosed herein is a method and system that tracks and monitors the status of scheduled production functions within a system controller, in which the controller provides for continued use of all available system capabilities and reports system state and updated module models as necessary after each capability is executed. To accomplish this, the current schedule and the events reported by system modules are incrementally integrated in a coordinated manner as jobs are executed and a log of plan execution may be formed. These forms of information give the system control software the ability to better report system status to an operator, and they provide a basis for planning for failure recovery and state transitioning. For a system state provided in a detailed, constraint-based format, the system and method create a new plan and schedule to produce the unfinished job elements, using the capabilities of the system and the original job constraints. In contrast to existing approaches to scheduling, the system and method described herein explicitly consider purging and re-creation as one of the capabilities that could be executed to produce the jobs. The system and method also contemplates multiple mechanisms for purging job elements, including human intervention.
  • the system and method apply to control software used for multi-step production processes such as manufacturing, printing, or assembly and provide for the handling of complex operations over complex paths to provide flexible routing, optimal productivity, and optimal load balancing.
  • control software used for multi-step production processes such as manufacturing, printing, or assembly
  • complex operations over complex paths to provide flexible routing, optimal productivity, and optimal load balancing.
  • numerous specific details are set forth in order to provide a thorough understanding of the present invention. It would be apparent, however, to one skilled in the art to practice the invention without such specific details. In other instances, specific implementation details have not been shown in detail in order not to unnecessarily obscure the present invention.
  • Figure 1 illustrates a controller for planning and scheduling normal and fault recovery operations in conformance with one embodiment of the subject system.
  • system controller 110 receives descriptions of work units to be produced from any known type of job input source. These descriptions correspond to descriptions of the desired output products or other goals to be achieved. They may specify attributes (or properties) of the products, values or ranges or general constraints for these attributes, and possibly constraints on the timing of the production (e.g., deadlines), but generally without specifying how the products are to be produced.
  • System controller 110 also receives, along paths 130, capability models and performance log information from each module 120 in the system.
  • the capability models are descriptions of how the modules move and transform work units, generally together with information about the attributes and timing of the work units. Models may be sent to the system controller only once when the production system is started up, or the models may be updated regularly or when changes occur. Such changes in the modules (and therefore in the models) may, for example, be the reconfiguration of the modules, changes in timing values, and the unavailability of resources (and thus some capabilities).
  • the capability models include, for example, timing constraints (e.g., the duration of execution of a capability, the time during which a resource is occupied, or the reservation of a resource), feature constraints (e.g., limits on the size of the work units being processed, transformation of the work units such as changing the orientation of a part or adding two parts together), and commands (e.g., the names or identifications of the operations corresponding to the capabilities, together with times and possibly other information).
  • timing constraints e.g., the duration of execution of a capability, the time during which a resource is occupied, or the reservation of a resource
  • feature constraints e.g., limits on the size of the work units being processed, transformation of the work units such as changing the orientation of a part or adding two parts together
  • commands e.g., the names or identifications of the operations corresponding to the capabilities, together with times and possibly other information.
  • the timing and feature constraints describe when and how a capability can be applied to a work unit.
  • the commands are the commands that are sent
  • Modules 120 may encompass many varying types of production systems, for example machine modules of a print engine, such as a feeder module, mark engine module, finisher module, or transport module.
  • modules 120 may include the analysis modules of a biotech screening system, which may comprise a preparation module, heating module, mixing module, analysis module, or transport robot.
  • Manufacturing line modules may include a machining module, assembling module, testing module, transport robot, or packaging module.
  • a packaging line may include a bottle filling module or a labeling module.
  • System controller 110 considers all possible system capabilities when searching for schedules for the desired work units.
  • Planning and scheduling some or all of the desired work units of one or more jobs results in a set of selected and scheduled capabilities.
  • the system controller 110 sends the instruction commands corresponding to the scheduled capabilities to modules 120 along paths 140.
  • Each of the modules then performs its task sequence for the completion of the specified job.
  • path 150 which illustrates the path of the work units being processed, work may cycle repeatedly within a particular module 120 before moving to the next module in succession, or work may cycle repeatedly among several modules before passing to a third module.
  • path 150 which illustrates the path of the work units being processed
  • work may cycle repeatedly within a particular module 120 before moving to the next module in succession, or work may cycle repeatedly among several modules before passing to a third module.
  • Only three modules 120 are illustrated for the purposes herein, it will be understood that a system may include numerous modules, depending on the complexity of the job requirements.
  • the modules may have various configurations within a system that is reconfigurable. Additionally there is also capability for operator feedback as to the work being scheduled on the modules and the state of the system at any
  • the system control software plans and schedules jobs by selecting capabilities, determining the timing variables of these capabilities, and identifying and recovering from failures to execute scheduled capabilities.
  • Figure 2 illustrates the planning, scheduling, monitoring, reporting, and an approach to identifying and recovering from failures by the system controller.
  • method steps are described in terms of data received and provided to each subsequent step in the process.
  • Each of the steps 220, 230, and 240 in this process may be executed in sequence (one after the other) or concurrently. In either case, each step consumes data 225, 235, or discrepancies between schedule and execution provided by a previous step or another action within the system, and produces data 235, 245, and ultimately 270 for subsequent steps or other system operations.
  • Consuming and producing this data is generally done incrementally, where a step is processing one data item after another, but may also be done in batches, as will be obvious to one skilled in the art of real-time software.
  • a description of the work units 225, or job to be performed is provided to the controller. If diagnostic jobs have to be performed, corresponding work units are inserted concurrently into the job queue.
  • the controller also has the models of the system modules available together with the current state of the system and information as to discrepancies between schedule and execution 260, e.g., which operations are currently performed by the modules, and any capabilities it may have previously planned and scheduled.
  • the selected work units plus any optional diagnostic work units 225 are then transmitted to step 220, which plans and schedules the capabilities for the selected work units, taking into consideration the capability model for each module. This step is repeated for each work unit and diagnostic work unit selected in the previous step, and a set of scheduled capabilities 235 is created.
  • failures are identified and a recovery mode is identified based on schedule and execution discrepancy data from 260. Concretely, any (significant) discrepancy between schedule and execution points to a possible failure.
  • the software has to identify whether the reported execution will still satisfy the constraints given by jobs and models. For example, if a work unit stays longer in a module than expected, will it overlap (i.e., collide) with other scheduled work units? If a work unit is delayed, will it still satisfy the precedence constraints with respect to other work units? If a work unit transformation (e.g., change in orientation) wasn't executed, can that be compensated for? This reasoning can be done by modifying the schedule based on the module reports and then checking it against the constraints.
  • a work unit transformation e.g., change in orientation
  • the scheduler's facility to generate correct schedules can be used to detect if production is becoming inconsistent due to execution differences. For example, if operations on a work unit are delayed, work units of the same jobs may be produced out of order (and thus precedence constraints will be violated) or work units may collide (and thus resource constraints will be violated). By comparing and integrating such execution differences into its schedules, the scheduler can immediately detect such inconsistencies.
  • the detailed system state provides a basis for determining whether and how the system can recover from the failure. For example, a typical result of failure is that parts of a job will violate their precedence constraints (i.e., would come out in a different order than desired because of delays of some work units) or will not be produced at all (because modules that were scheduled to produce them went off-line). The state will help identify those parts, such that the system control software can recover, perhaps by re-planning or rerouting these jobs. System failure identification and failure recovery mode are provided to planning and scheduling step 220 for incorporation into the dynamic system schedule.
  • Scheduled capabilities 235 are in turn provided to step 240, at which the controller sends the commands 245 corresponding to the scheduled capabilities to the individual modules. This step is repeated for each scheduled capability. Modules incrementally report the execution of capabilities at the same level of detail as defined in their models.
  • a transport module may define a "move" capability with an input time, an output time, an input work unit (and its attributes), an output work unit (and its attributes), and some constraints between these (e.g., time constraints between the time variables, attribute transformations between the work unit variables, etc.); if the system control software selects and schedules that capability (determining values for the time and attribute variables), a command will be sent to the module to execute this capability at the given time, and the module will report back the actual values (or the differences to the expected values) for the model variables (times, attributes, resources).
  • These module reports 255 are logged at 250 and integrated to build a detailed log of the execution of its schedules.
  • the log may explicitly or implicitly include a history of the system's behavior. For example, instead of a single value for timing values, the log may maintain a distribution of values, including frequency or likelihood of occurrence. This information is then utilized to update the system status 260 and generate a system report 270.
  • modules may report their behavior only if it deviates (significantly) from the expected behavior, which reduces reporting overhead. Since modules have access to their own models, no special communication with the system controller is needed. In order to determine whether a module is about to fail, it is necessary to know the current observed behavior values and the limits on those values. However, closeness to a failure also depends on controllability, i.e., "within 5% of the limit" may be acceptable for a module with tight control but near-catastrophic for a module that has poor sensing capabilities.
  • the method uses the capabilities of the manufacturing system with its modules and the original job constraints. In contrast to existing approaches to scheduling, the method explicitly considers purging and re-creation as one of the options for job production. Additionally, both recovery and re-creation of in-process job elements have to be viewed in the context of other job elements that were already planned and scheduled. As an example, consider a job consisting of two elements. The production of element 2 may have been started first (e.g., because it takes longer to produce than element 1). The planner/scheduler has a schedule for both elements, but the system was only producing the second one when it encountered a fault. Consequently, the planner/scheduler has to schedule both together in order to guarantee correct production.
  • element 1 it may be possible to delay or reroute production of element 2 sufficiently that element 1 can be produced in the meantime and delivered before 2.
  • element 1 could no longer be moved ahead of 2 and therefore element 2 has to be purged, and both job elements have to be produced from scratch.
  • FIG. 3 a flow chart illustrates an example embodiment of operations utilized in planning for the recovery of work units and the planning of new work units according to the subject invention.
  • a plan is formulated to recover in-process work units for current or future production purposes.
  • the method queries the system at 320 to identify whether additional work units are to be recovered. If additional work units are to be recovered, the plan is adjusted at 310 and the query is repeated until all recovery units have been identified. New work units are then planned at 330.
  • the primary advantages to the approach are the reduction of waste and production time in the face of faults.
  • the method attempts recovery by restarting from the current state of the system if that is more efficient than restarting production from scratch. (Conversely, if purging and re-creating in-process work units is more efficient, that is preferred.)
  • the method tries to make use of the variety of available capabilities to optimize recovery. There is no need for a separate, heuristics-based recovery algorithm.
  • the approach is configuration-independent and thus easily reused for arbitrary reconfigurable production systems that can be modeled in this framework.
  • a work unit or job to be planned is selected at step 410 based on the input job description.
  • the controller determines the capabilities needed to produce the work unit without utilizing off-line resources at step 420.
  • An off-line resource is any module or partial module that is currently unavailable, e.g., because it is powered down or broken.
  • the controller considers all possible system capabilities, excluding the capabilities of the off-line resource(s), from which alternative capabilities are selected.
  • the controller determines if capabilities are available to produce the work unit at step 430.
  • step 440 If sufficient capabilities are not available, subsequent work units of the same job are temporarily removed from consideration at step 440 and the controller returns to step 410 to select another work unit to be planned. If no capability remains available for a desired work unit, all subsequent work units of the same job will be delayed, even if they could be produced, in order to avoid out-of-order output delivery.
  • timing constraints such as the amount of time required for each task within a job (e.g., the duration of a transport operation or a processing step), constraints on the intervals during which resources are occupied, and the reservation of resources during such intervals are modified by selection variables and posted to the controller at step 450.
  • Selection variables are Boolean variables, one for each capability, that become either TRUE (the capability is selected) or FALSE (the capability is not selected). Selection variables are created automatically for each capability by the planning step.
  • Constraints on the selection variables determine that, for example, only one of several alternative capabilities for the same output can be selected (i.e., only its selection variables can be TRUE).
  • the modification of constraints is constraint-type-dependent. Allocation intervals in resource allocations, for example, are multiplied by the selection variables. The effect of these constraint modifications is that some constraints, such as a resource allocation, become only effective if the corresponding capability is being selected.
  • the controller posts to memory constraints on selection variables and common modules to the constraint store at step 460.
  • real-time constraints and order constraints are posted to the controller.
  • the output variables of all alternative capabilities are connected to a single time variable, which is then used in the precedence constraints.
  • the job constraints reserve resources for a job and all possible exit ports of capabilities being considered for work units in the job. If only part of a job is being scheduled at this point, the selected resource is reserved for the openended future, and otherwise for the duration of the job. This also ensures that jobs will be delivered correctly even if parts of them have not yet been produced due to off-line resources.
  • the sequence of steps presented is only one example embodiment for the method disclosed herein. It will be apparent to one skilled in the art that numerous alternate step sequences would produce a similar result.
  • selection variables allows the scheduler to consider all possible, alternative plans concurrently and to select one by instantiating its selection variable.
  • An alternative to this method is to use search to go over the alternative plans, one after another, keeping the one with the best schedule.
  • planning of all capabilities precedes scheduling (finding the time values).
  • scheduling and scheduling are interleaved. In either case, the end result is a single plan and schedule for each work unit.
  • Figure 5 illustrates an example embodiment detailing the ordering of operations to accomplish planning for recovery of in-process work units.
  • the controller selects a work unit to be planned from among the in-process work units at 510.
  • the capabilities to produce the work unit from the beginning are identified at 520.
  • two sets of capabilities are considered during recovery: the capabilities producing the desired output product from the current location and state of the work unit (''recovery capabilities", subscript "r” in the example pseudo code hereinbelow); and capabilities purging and re-creating the desired output product (“purge capabilities” and "create capabilities", subscripts "p” and “c” hereinbelow).
  • Recovery and purge capabilities start from the current location, while "create” capabilities are regular system capabilities producing the product from the beginning.
  • the controller determines the capabilities that can purge the in-process work unit from its current location.
  • the definition of "current location" is implementation-specific. It may be assumed, for example, that the capability which was scheduled to be executed at the time of the fault can be completed. Consequently, recovery and purge capabilities can start from the exit port of the corresponding module.
  • the planner/scheduler could first attempt to create a regular schedule from the current state. If this fails, it would identify those parts that violate constraints (e.g., timing or precedence constraints) and first plan and schedule their purging. The controller would then plan and schedule the jobs again. This could also be done in multiple iterations.
  • the controller identifies capabilities that can repair the in-process work unit from its current location at 540 and determines whether sufficient capabilities are available at 550. If sufficient capabilities are not available, the controller cancels subsequent work units of the same job and temporarily removes them from consideration at 560. A new work unit is then selected at 510 and the identification of capabilities is repeated for the new work unit. Alternatively, if the current capability cannot be completed, either the entire module has to be declared as off-line (and re-creation is the only option), or the current capability has not been executed, but the work unit's state is known (and both recovery and re-creation are options), or the state of the work unit is unknown (i.e., the work unit has to be purged and recreation is again the only option).
  • the controller posts timing constraints modified by selection variables for all capabilities at 570. Constraints on selection variables and common modules is posted at 580 to enable the system to either repair the fault or purge the work unit and reproduce it. Constraints on the selection variables determine that, for example, only one of several alternative capabilities for the same output can be selected (i.e., only its selection variables can be TRUE).
  • the constraints are defined such that, for each work unit, either only a repair capability or a purge capability together with a reproduce (i.e., create) capability will be selected.
  • the modification of constraints is constraint-type-dependent. Allocation intervals in resource allocations, for example, are multiplied by the selection variables.
  • the controller posts real-time constraints and order constraints at 590 for use by the scheduler before it returns to 510 to select another work unit to be planned.
  • step 610 the controller selects those capabilities to be scheduled, which may be all or a subset of the capabilities provided by the planning step.
  • the controller reserves exit resources for planned capabilities within the same jobs at step 620. Since all work units of the same job are constrained to be delivered to the same final exit port, the resource connected to that same final exit port, corresponding for example to a finisher stack in a print engine, cannot be used by other jobs until the job is finished.
  • step 630 the controller then solves for timing and selection variables of planned capabilities. This can be accomplished using a number of constraint solving or constrained optimization techniques, which are known to those skilled in the art.
  • the planner may identify all work units up to and including the ones currently in process (using the order required by the job description). This is the minimal set of work units to be included in the recovery. Additionally, the planner/scheduler may consider human capabilities in its plan. For example, if certain work units cannot be purged or cleared automatically, the planner may first be used to determine which job elements need to be handled by the operator and which it can process automatically. The operator may then be asked to decide how to handle those work units that cannot be purged or cleared automatically before the system proceeds.
  • Schedule repair e.g., changing the timings or actions in the schedule without creating an entirely new plan and schedule, can be accomplished using a number of constraint solving or constrained optimization techniques, which are known to those skilled in the art.
  • code as used herein, or “program” as used herein, is any plurality of binary values or any executable, interpreted or compiled code which can be used by a computer or execution device to perform a task. This code or program can be written in any one of several known computer languages.
  • a "computer”, as used herein, can mean any device which stores, processes, routes, manipulates, or performs like operation on data.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Physics & Mathematics (AREA)
  • Educational Administration (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Game Theory and Decision Science (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • General Factory Administration (AREA)
EP04009991A 2003-04-28 2004-04-27 La planification et le séquencement pour un système et une méthode de rétablissement de défaillance Ceased EP1480144A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/424,620 US7139629B2 (en) 2003-04-28 2003-04-28 Planning and scheduling for failure recovery system and method
US424620 2003-04-28

Publications (1)

Publication Number Publication Date
EP1480144A1 true EP1480144A1 (fr) 2004-11-24

Family

ID=33097907

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04009991A Ceased EP1480144A1 (fr) 2003-04-28 2004-04-27 La planification et le séquencement pour un système et une méthode de rétablissement de défaillance

Country Status (3)

Country Link
US (1) US7139629B2 (fr)
EP (1) EP1480144A1 (fr)
JP (1) JP4786139B2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1936459A3 (fr) * 2006-12-19 2014-11-12 Palo Alto Research Center Incorporated Manipulation d'exceptions
CN108614526A (zh) * 2016-12-13 2018-10-02 中国科学院沈阳自动化研究所 一种可重构的生产过程管理系统

Families Citing this family (141)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3951835B2 (ja) 2002-07-03 2007-08-01 株式会社日立製作所 業務管理方法及び業務処理システム
US7226049B2 (en) 2003-06-06 2007-06-05 Xerox Corporation Universal flexible plural printer to plural finisher sheet integration system
JP4485763B2 (ja) * 2003-07-10 2010-06-23 株式会社日立製作所 運用管理方法及び装置
US7512455B2 (en) * 2004-03-29 2009-03-31 Palo Alto Research Center Incorporated Method for self-synchronization of modular production systems
US7185888B2 (en) 2004-03-29 2007-03-06 Palo Alto Research Center Incorporated Rotational jam clearance apparatus
US8255422B2 (en) * 2004-05-28 2012-08-28 Microsoft Corporation Highly reliable and scalable architecture for data centers
US7396012B2 (en) * 2004-06-30 2008-07-08 Xerox Corporation Flexible paper path using multidirectional path modules
US7188929B2 (en) * 2004-08-13 2007-03-13 Xerox Corporation Parallel printing architecture with containerized image marking engines
US8407077B2 (en) * 2006-02-28 2013-03-26 Palo Alto Research Center Incorporated System and method for manufacturing system design and shop scheduling using network flow modeling
US7649645B2 (en) 2005-06-21 2010-01-19 Xerox Corporation Method of ordering job queue of marking systems
US7024152B2 (en) * 2004-08-23 2006-04-04 Xerox Corporation Printing system with horizontal highway and single pass duplex
US7742185B2 (en) 2004-08-23 2010-06-22 Xerox Corporation Print sequence scheduling for reliability
US7493055B2 (en) * 2006-03-17 2009-02-17 Xerox Corporation Fault isolation of visible defects with manual module shutdown options
US20070002085A1 (en) * 2005-06-30 2007-01-04 Xerox Corporation High availability printing systems
US7542059B2 (en) * 2006-03-17 2009-06-02 Xerox Corporation Page scheduling for printing architectures
US9250967B2 (en) * 2004-08-23 2016-02-02 Palo Alto Research Center Incorporated Model-based planning with multi-capacity resources
US7123873B2 (en) 2004-08-23 2006-10-17 Xerox Corporation Printing system with inverter disposed for media velocity buffering and registration
US7245838B2 (en) * 2005-06-20 2007-07-17 Xerox Corporation Printing platform
US7308218B2 (en) * 2005-06-14 2007-12-11 Xerox Corporation Warm-up of multiple integrated marking engines
US7136616B2 (en) * 2004-08-23 2006-11-14 Xerox Corporation Parallel printing architecture using image marking engine modules
US7302199B2 (en) * 2005-05-25 2007-11-27 Xerox Corporation Document processing system and methods for reducing stress therein
US7619769B2 (en) * 2005-05-25 2009-11-17 Xerox Corporation Printing system
US7224913B2 (en) * 2005-05-05 2007-05-29 Xerox Corporation Printing system and scheduling method
US7787138B2 (en) * 2005-05-25 2010-08-31 Xerox Corporation Scheduling system
US7336920B2 (en) * 2004-09-28 2008-02-26 Xerox Corporation Printing system
US7751072B2 (en) * 2004-09-29 2010-07-06 Xerox Corporation Automated modification of a marking engine in a printing system
US20060114497A1 (en) * 2004-11-30 2006-06-01 Xerox Corporation Printing system
US7162172B2 (en) * 2004-11-30 2007-01-09 Xerox Corporation Semi-automatic image quality adjustment for multiple marking engine systems
US7245856B2 (en) * 2004-11-30 2007-07-17 Xerox Corporation Systems and methods for reducing image registration errors
US7412180B2 (en) * 2004-11-30 2008-08-12 Xerox Corporation Glossing system for use in a printing system
US7305194B2 (en) * 2004-11-30 2007-12-04 Xerox Corporation Xerographic device streak failure recovery
US7310108B2 (en) 2004-11-30 2007-12-18 Xerox Corporation Printing system
US7791751B2 (en) * 2004-11-30 2010-09-07 Palo Alto Research Corporation Printing systems
US7283762B2 (en) 2004-11-30 2007-10-16 Xerox Corporation Glossing system for use in a printing architecture
US7540484B2 (en) * 2005-02-02 2009-06-02 Xerox Corporation System of opposing alternate higher speed sheet feeding from the same sheet stack
US7226158B2 (en) * 2005-02-04 2007-06-05 Xerox Corporation Printing systems
US7617017B2 (en) * 2005-02-18 2009-11-10 Gm Global Technology Operations, Inc. System and method for resource reallocation based on ambient condition data
US8819103B2 (en) 2005-04-08 2014-08-26 Palo Alto Research Center, Incorporated Communication in a distributed system
US8081329B2 (en) 2005-06-24 2011-12-20 Xerox Corporation Mixed output print control method and system
US7873962B2 (en) * 2005-04-08 2011-01-18 Xerox Corporation Distributed control systems and methods that selectively activate respective coordinators for respective tasks
US7791741B2 (en) * 2005-04-08 2010-09-07 Palo Alto Research Center Incorporated On-the-fly state synchronization in a distributed system
US8014024B2 (en) * 2005-03-02 2011-09-06 Xerox Corporation Gray balance for a printing system of multiple marking engines
US7697151B2 (en) * 2005-03-25 2010-04-13 Xerox Corporation Image quality control method and apparatus for multiple marking engine systems
US7258340B2 (en) * 2005-03-25 2007-08-21 Xerox Corporation Sheet registration within a media inverter
US7416185B2 (en) * 2005-03-25 2008-08-26 Xerox Corporation Inverter with return/bypass paper path
US7206536B2 (en) * 2005-03-29 2007-04-17 Xerox Corporation Printing system with custom marking module and method of printing
US7444108B2 (en) * 2005-03-31 2008-10-28 Xerox Corporation Parallel printing architecture with parallel horizontal printing modules
US7245844B2 (en) * 2005-03-31 2007-07-17 Xerox Corporation Printing system
US7272334B2 (en) * 2005-03-31 2007-09-18 Xerox Corporation Image on paper registration alignment
US7706007B2 (en) * 2005-04-08 2010-04-27 Palo Alto Research Center Incorporated Synchronization in a distributed system
US7566053B2 (en) * 2005-04-19 2009-07-28 Xerox Corporation Media transport system
US7593130B2 (en) * 2005-04-20 2009-09-22 Xerox Corporation Printing systems
US20060244980A1 (en) * 2005-04-27 2006-11-02 Xerox Corporation Image quality adjustment method and system
US20060268287A1 (en) * 2005-05-25 2006-11-30 Xerox Corporation Automated promotion of monochrome jobs for HLC production printers
US7486416B2 (en) * 2005-06-02 2009-02-03 Xerox Corporation Inter-separation decorrelator
US8004729B2 (en) * 2005-06-07 2011-08-23 Xerox Corporation Low cost adjustment method for printing systems
US7451697B2 (en) * 2005-06-24 2008-11-18 Xerox Corporation Printing system
US7310493B2 (en) * 2005-06-24 2007-12-18 Xerox Corporation Multi-unit glossing subsystem for a printing device
US7387297B2 (en) * 2005-06-24 2008-06-17 Xerox Corporation Printing system sheet feeder using rear and front nudger rolls
US7433627B2 (en) * 2005-06-28 2008-10-07 Xerox Corporation Addressable irradiation of images
US8259369B2 (en) 2005-06-30 2012-09-04 Xerox Corporation Color characterization or calibration targets with noise-dependent patch size or number
US8203768B2 (en) * 2005-06-30 2012-06-19 Xerox Corporaiton Method and system for processing scanned patches for use in imaging device calibration
US7647018B2 (en) * 2005-07-26 2010-01-12 Xerox Corporation Printing system
US7496412B2 (en) 2005-07-29 2009-02-24 Xerox Corporation Control method using dynamic latitude allocation and setpoint modification, system using the control method, and computer readable recording media containing the control method
US7466940B2 (en) * 2005-08-22 2008-12-16 Xerox Corporation Modular marking architecture for wide media printing platform
US7474861B2 (en) * 2005-08-30 2009-01-06 Xerox Corporation Consumable selection in a printing system
US7911652B2 (en) * 2005-09-08 2011-03-22 Xerox Corporation Methods and systems for determining banding compensation parameters in printing systems
US7430380B2 (en) * 2005-09-23 2008-09-30 Xerox Corporation Printing system
US7495799B2 (en) * 2005-09-23 2009-02-24 Xerox Corporation Maximum gamut strategy for the printing systems
US7444088B2 (en) * 2005-10-11 2008-10-28 Xerox Corporation Printing system with balanced consumable usage
US7811017B2 (en) * 2005-10-12 2010-10-12 Xerox Corporation Media path crossover for printing system
US8711435B2 (en) * 2005-11-04 2014-04-29 Xerox Corporation Method for correcting integrating cavity effect for calibration and/or characterization targets
US7719716B2 (en) * 2005-11-04 2010-05-18 Xerox Corporation Scanner characterization for printer calibration
US7660460B2 (en) * 2005-11-15 2010-02-09 Xerox Corporation Gamut selection in multi-engine systems
US7280771B2 (en) * 2005-11-23 2007-10-09 Xerox Corporation Media pass through mode for multi-engine system
US7519314B2 (en) * 2005-11-28 2009-04-14 Xerox Corporation Multiple IOT photoreceptor belt seam synchronization
US7706737B2 (en) 2005-11-30 2010-04-27 Xerox Corporation Mixed output printing system
US7575232B2 (en) * 2005-11-30 2009-08-18 Xerox Corporation Media path crossover clearance for printing system
US7636543B2 (en) * 2005-11-30 2009-12-22 Xerox Corporation Radial merge module for printing system
US7922288B2 (en) * 2005-11-30 2011-04-12 Xerox Corporation Printing system
US7912416B2 (en) 2005-12-20 2011-03-22 Xerox Corporation Printing system architecture with center cross-over and interposer by-pass path
US7826090B2 (en) * 2005-12-21 2010-11-02 Xerox Corporation Method and apparatus for multiple printer calibration using compromise aim
US7756428B2 (en) * 2005-12-21 2010-07-13 Xerox Corp. Media path diagnostics with hyper module elements
US8102564B2 (en) * 2005-12-22 2012-01-24 Xerox Corporation Method and system for color correction using both spatial correction and printer calibration techniques
US7746524B2 (en) * 2005-12-23 2010-06-29 Xerox Corporation Bi-directional inverter printing apparatus and method
US7624981B2 (en) * 2005-12-23 2009-12-01 Palo Alto Research Center Incorporated Universal variable pitch interface interconnecting fixed pitch sheet processing machines
US7963518B2 (en) * 2006-01-13 2011-06-21 Xerox Corporation Printing system inverter apparatus and method
US8477333B2 (en) * 2006-01-27 2013-07-02 Xerox Corporation Printing system and bottleneck obviation through print job sequencing
US7630669B2 (en) * 2006-02-08 2009-12-08 Xerox Corporation Multi-development system print engine
US7672006B2 (en) * 2006-02-22 2010-03-02 Xerox Corporation Multi-marking engine printing platform
US8194262B2 (en) * 2006-02-27 2012-06-05 Xerox Corporation System for masking print defects
US7965397B2 (en) * 2006-04-06 2011-06-21 Xerox Corporation Systems and methods to measure banding print defects
US8330965B2 (en) 2006-04-13 2012-12-11 Xerox Corporation Marking engine selection
US7681883B2 (en) * 2006-05-04 2010-03-23 Xerox Corporation Diverter assembly, printing system and method
US7679631B2 (en) 2006-05-12 2010-03-16 Xerox Corporation Toner supply arrangement
US7800777B2 (en) * 2006-05-12 2010-09-21 Xerox Corporation Automatic image quality control of marking processes
US7382993B2 (en) * 2006-05-12 2008-06-03 Xerox Corporation Process controls methods and apparatuses for improved image consistency
US7865125B2 (en) * 2006-06-23 2011-01-04 Xerox Corporation Continuous feed printing system
US7856191B2 (en) * 2006-07-06 2010-12-21 Xerox Corporation Power regulator of multiple integrated marking engines
US7924443B2 (en) * 2006-07-13 2011-04-12 Xerox Corporation Parallel printing system
US8607102B2 (en) * 2006-09-15 2013-12-10 Palo Alto Research Center Incorporated Fault management for a printing system
US7766327B2 (en) * 2006-09-27 2010-08-03 Xerox Corporation Sheet buffering system
US7857309B2 (en) * 2006-10-31 2010-12-28 Xerox Corporation Shaft driving apparatus
US7819401B2 (en) * 2006-11-09 2010-10-26 Xerox Corporation Print media rotary transport apparatus and method
US7969624B2 (en) * 2006-12-11 2011-06-28 Xerox Corporation Method and system for identifying optimal media for calibration and control
US8159713B2 (en) * 2006-12-11 2012-04-17 Xerox Corporation Data binding in multiple marking engine printing systems
US7945346B2 (en) * 2006-12-14 2011-05-17 Palo Alto Research Center Incorporated Module identification method and system for path connectivity in modular systems
US8100523B2 (en) * 2006-12-19 2012-01-24 Xerox Corporation Bidirectional media sheet transport apparatus
US7559549B2 (en) 2006-12-21 2009-07-14 Xerox Corporation Media feeder feed rate
US8693021B2 (en) * 2007-01-23 2014-04-08 Xerox Corporation Preemptive redirection in printing systems
US7934825B2 (en) * 2007-02-20 2011-05-03 Xerox Corporation Efficient cross-stream printing system
US7676191B2 (en) 2007-03-05 2010-03-09 Xerox Corporation Method of duplex printing on sheet media
US7894107B2 (en) * 2007-04-27 2011-02-22 Xerox Corporation Optical scanner with non-redundant overwriting
US20080268839A1 (en) * 2007-04-27 2008-10-30 Ayers John I Reducing a number of registration termination massages in a network for cellular devices
US8253958B2 (en) * 2007-04-30 2012-08-28 Xerox Corporation Scheduling system
US8169657B2 (en) 2007-05-09 2012-05-01 Xerox Corporation Registration method using sensed image marks and digital realignment
US7590464B2 (en) * 2007-05-29 2009-09-15 Palo Alto Research Center Incorporated System and method for on-line planning utilizing multiple planning queues
US7689311B2 (en) * 2007-05-29 2010-03-30 Palo Alto Research Center Incorporated Model-based planning using query-based component executable instructions
US7925366B2 (en) * 2007-05-29 2011-04-12 Xerox Corporation System and method for real-time system control using precomputed plans
US8203750B2 (en) 2007-08-01 2012-06-19 Xerox Corporation Color job reprint set-up for a printing system
US7697166B2 (en) * 2007-08-03 2010-04-13 Xerox Corporation Color job output matching for a printing system
US7590501B2 (en) 2007-08-28 2009-09-15 Xerox Corporation Scanner calibration robust to lamp warm-up
US20090292941A1 (en) * 2008-05-22 2009-11-26 Nec Laboratories America, Inc. Proof-guided error diagnosis (ped) by triangulation of program error causes
US8219437B2 (en) 2008-07-10 2012-07-10 Palo Alto Research Center Incorporated Methods and systems for constructing production plans
US8145334B2 (en) * 2008-07-10 2012-03-27 Palo Alto Research Center Incorporated Methods and systems for active diagnosis through logic-based planning
US8266092B2 (en) * 2008-07-10 2012-09-11 Palo Alto Research Center Incorporated Methods and systems for target value path identification
US7937175B2 (en) * 2008-07-10 2011-05-03 Palo Alto Research Center Incorporated Methods and systems for pervasive diagnostics
US8165705B2 (en) * 2008-07-10 2012-04-24 Palo Alto Research Center Incorporated Methods and systems for continuously estimating persistent and intermittent failure probabilities for production resources
US8612050B2 (en) * 2008-07-29 2013-12-17 Palo Alto Research Center Incorporated Intelligent product feed system and method
US8169626B2 (en) 2008-08-29 2012-05-01 Xerox Corporation Using buffers to support uncertainties in marking engine execution
KR101627132B1 (ko) * 2008-12-15 2016-06-13 삼성전자 주식회사 로봇 및 그 복구 방법
US8359110B2 (en) * 2009-03-23 2013-01-22 Kuhn Lukas D Methods and systems for fault diagnosis in observation rich systems
US8265980B2 (en) * 2009-04-21 2012-09-11 International Business Machines Corporation Workflow model for coordinating the recovery of IT outages based on integrated recovery plans
US7976012B2 (en) 2009-04-28 2011-07-12 Xerox Corporation Paper feeder for modular printers
US8458710B2 (en) * 2009-09-03 2013-06-04 Hewlett-Packard Development Company, L. P. Scheduling jobs for execution on a computer system
US20120185286A1 (en) * 2011-01-17 2012-07-19 Palo Alto Research Center Incorporated Online continual automated planning framework based on timelines
CN102103649B (zh) * 2011-03-16 2013-02-20 北京航空航天大学 一种装备rms分析仿真任务的逻辑流程建立方法
US8924779B2 (en) * 2012-03-30 2014-12-30 Lsi Corporation Proxy responder for handling anomalies in a hardware system
US9870295B2 (en) * 2014-07-18 2018-01-16 General Electric Company Automation of workflow creation and failure recovery
US11181882B2 (en) * 2017-06-19 2021-11-23 The Boeing Company Dynamic modification of production plans responsive to manufacturing deviations
US10976712B2 (en) * 2018-02-05 2021-04-13 Honeywell International Inc. Method and system to provide cost of lost opportunity to operators in real time using advance process control

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1996040558A1 (fr) * 1995-06-07 1996-12-19 Tetra Laval Holdings & Finance S.A. Systeme de diagnostic pour un appareil mu par un servomoteur
US6216109B1 (en) * 1994-10-11 2001-04-10 Peoplesoft, Inc. Iterative repair optimization with particular application to scheduling for integrated capacity and inventory planning
US6233493B1 (en) * 1998-09-16 2001-05-15 I2 Technologies, Inc. Computer-implemented product development planning method

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2038939C (fr) * 1989-08-10 1997-06-17 Satomi Furukawa Dispositif de commande de production
DE69032508T2 (de) * 1989-12-22 1999-03-25 Tandem Computers Inc., Cupertino, Calif. Fehlertolerantes Rechnersystem mit Online-Wiedereinfügung und Abschaltung/Start
JP2915066B2 (ja) * 1990-04-26 1999-07-05 マツダ株式会社 生産工程管理方法及び装置
JPH0413529A (ja) * 1990-04-27 1992-01-17 Hitachi Ltd 加工又は組立装置
US5095342A (en) 1990-09-28 1992-03-10 Xerox Corporation Methods for sheet scheduling in an imaging system having an endless duplex paper path loop
US5159395A (en) 1991-08-29 1992-10-27 Xerox Corporation Method of scheduling copy sheets in a dual mode duplex printing system
JPH071298A (ja) * 1993-06-11 1995-01-06 Sanken Electric Co Ltd ユニット型物品生産装置とそれを使用した物品生産ラインシステム
JPH07237095A (ja) * 1993-12-27 1995-09-12 Hitachi Ltd 多品種連続生産方法及び装置
US5838899A (en) * 1994-09-20 1998-11-17 Stratus Computer Digital data processing methods and apparatus for fault isolation
US5557367A (en) 1995-03-27 1996-09-17 Xerox Corporation Method and apparatus for optimizing scheduling in imaging devices
JP3283717B2 (ja) * 1995-04-12 2002-05-20 株式会社リコー 部品供給装置
JPH08287140A (ja) * 1995-04-12 1996-11-01 Yokogawa Electric Corp 操業計画の作成方法及び装置
US5696893A (en) 1995-06-07 1997-12-09 Xerox Corporation System for generically describing and scheduling operation of modular printing machine
JPH09184069A (ja) * 1995-12-28 1997-07-15 Canon Inc 連続体の製造工程管理方法及び表示制御方法
US5826104A (en) 1996-04-15 1998-10-20 Mci Communications Corporation Batch program status via tape data set information for dynamically determining the real time status of a batch program running in a main frame computer system
US6115646A (en) 1997-12-18 2000-09-05 Nortel Networks Limited Dynamic and generic process automation system
JPH11235648A (ja) * 1998-02-17 1999-08-31 Toshiba Corp 製造計画管理装置、製造計画管理方法、及び、製造計画管理プログラムを記録したコンピュータ読み取り可能な記録媒体
US6785586B1 (en) * 2001-02-23 2004-08-31 Advanced Micro Devices, Inc. Method and apparatus for adaptively scheduling tool maintenance
JP2002331444A (ja) * 2001-05-07 2002-11-19 Denso Corp 製造装置
JP2002358108A (ja) * 2001-05-31 2002-12-13 Star Micronics Co Ltd 工作機械の加工システム
JP2003062739A (ja) * 2001-08-28 2003-03-05 Ibiden Co Ltd 生産ラインシステム、生産ラインシステムの制御方法、ワーク処理システム
US6978187B1 (en) * 2001-12-12 2005-12-20 Advanced Micro Devices, Inc. Method and apparatus for scheduling production lots based on lot and tool health metrics
US6999829B2 (en) * 2001-12-26 2006-02-14 Abb Inc. Real time asset optimization

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6216109B1 (en) * 1994-10-11 2001-04-10 Peoplesoft, Inc. Iterative repair optimization with particular application to scheduling for integrated capacity and inventory planning
WO1996040558A1 (fr) * 1995-06-07 1996-12-19 Tetra Laval Holdings & Finance S.A. Systeme de diagnostic pour un appareil mu par un servomoteur
US6233493B1 (en) * 1998-09-16 2001-05-15 I2 Technologies, Inc. Computer-implemented product development planning method

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LEVER J ET AL: "CONSTRAINT LOGIC PROGRAMMING FOR SCHEDULING AND PLANNING", BT TECHNOLOGY JOURNAL, BT LABORATORIES, GB, vol. 12, no. 4, October 1994 (1994-10-01), pages 73 - 80, XP002187386, ISSN: 1358-3948 *
TOBIAS MÜLLER: "Practical Investigation of Constraints with Graph Views", PRINCIPLES AND PRACTICE OF CONSTRAINT PROGRAMMING - CP 2000, 6TH INTERNATIONAL CONFERENCE, vol. 1894, September 2000 (2000-09-01), BERLIN HEIDELBERG, pages 320 - 336, XP002295837, ISSN: 0302-9743, Retrieved from the Internet <URL:www.springerlink.com/index/3RG1C72MJHU3W9TN.pdf> [retrieved on 20040903] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1936459A3 (fr) * 2006-12-19 2014-11-12 Palo Alto Research Center Incorporated Manipulation d'exceptions
CN108614526A (zh) * 2016-12-13 2018-10-02 中国科学院沈阳自动化研究所 一种可重构的生产过程管理系统

Also Published As

Publication number Publication date
JP4786139B2 (ja) 2011-10-05
US20040216002A1 (en) 2004-10-28
US7139629B2 (en) 2006-11-21
JP2004326787A (ja) 2004-11-18

Similar Documents

Publication Publication Date Title
US7139629B2 (en) Planning and scheduling for failure recovery system and method
JP4571819B2 (ja) 異なったジョブ優先度のシステムおよび方法のための予測可能でプリエンプティブのプラニングおよびスケジューリング
US6856845B2 (en) Monitoring and reporting incremental job status system and method
US8315898B2 (en) Planning and scheduling reconfigurable systems around off-line resources
CA2447067C (fr) Systemes reconfigurables de planification et d&#39;etablissement d&#39;horaires pour taches regulieres et de diagnostic
EP1600836B1 (fr) Traitement d&#39;erreur dans des systèmes de production, combinant une planification en ligne avec des règles prédéterminées
US7230736B2 (en) Planning and scheduling reconfigurable systems with alternative capabilities
CN108182108A (zh) 一种定时任务集群及其执行方法
JP4815195B2 (ja) ジョブ実行管理方法、ジョブ実行管理システム及びジョブ実行管理プログラム
CN110611707A (zh) 一种任务调度的方法及装置
KR20240125497A (ko) 다중 작업장 및 작업장 수행 능력 기반의 연속적 생산 계획 전역 최적화 스케줄링 방법 및 장치
US7451132B2 (en) System and method for production planning utilizing on-line state-space planning
Ecker et al. Scheduling tasks on a flexible manufacturing machine to minimize tool change delays
CN112346842A (zh) 一种基于有向无环图的工作流任务调度方法
CN117149378A (zh) 智能汽车操作系统的任务调度方法、装置、设备及介质
Felli et al. Process plan controllers for non-deterministic manufacturing systems
Jain et al. Experiences with backward simulation based approach for lot release planning
De Sousa et al. Finite-time consensus and readjustment three-stage filter for predictive schedules in fms
US20220270012A1 (en) System and method for providing short-term dispatching decisions for operating a number of resources involved in a number of production processes under consideration of long-term objectives
JPH07175856A (ja) 設備の選択を提供する方法と装置
De Sousa et al. Scheduler with Buffer and Transportation Constraints for Inserting Rush Orders Without Deadlocks During Agent Convergence
CN116541581A (zh) 一种分布式应用批量发布的方法
Felli et al. Ratchev, Svetan (2017) Process plan controllers for non-deterministic manufacturing systems. In: International Joint Conference on Artificial Intelligence (IJCAI), 19-25 August 2017, Melbourne, Australia.
JPH07234898A (ja) 初期時限決定方法及び装置
Salman et al. Effect of Optimal Sequencing in Flexible Manufacturing System on Physical representation & Analysis time using CPN

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL HR LT LV MK

17P Request for examination filed

Effective date: 20050524

17Q First examination report despatched

Effective date: 20050617

AKX Designation fees paid

Designated state(s): DE FR GB

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20110209