Automated Workflow Plan Validation Using Knowledge-Based Reasoning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current device capability description languages in print shops are inefficient in describing relationships between devices and the effects of these devices on workflow plans, making it difficult to validate workflow plans, especially in 'lights out' automation scenarios where all effects are not known a priori.
Innovation Solution
Converting device capability descriptions into data indicative of facts and operators for a knowledge-based reasoning system, which also converts workflow plans into goal state properties, allowing for validation and synthesis of executable plans using a domain-independent or domain-dependent planner.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If device capability description languages are used to describe device capabilities, then device capabilities can be documented, but the languages are inefficient in describing relationships between devices and effects on workflow plans
Solution Approach 1:
The patent transforms device capability descriptions from static capability listings into dynamic state representations with facts, predicates, and operators. This parameter change enables the system to track how devices alter workflow state (e.g., image size changes from 8.5×11 to 17×11 after imposition) and validates workflows by checking if planned operations can achieve goal states, thereby improving validation accuracy without proportionally increasing complexity.
2Extent of automation
If automated validation is implemented for lights out workflow automation, then workflow execution can be automated, but validation cannot be performed when effects are not known a priori
Solution Approach 1:
The patent performs preliminary action by converting device capability descriptions into facts, predicates, and operators before workflow validation. This pre-processing creates a knowledge base that the automated planner can use to validate workflows even when effects are not known a priori. The system synthesizes missing information by reasoning about device capabilities and workflow goals, enabling reliable automated validation in lights out scenarios.
Solution Approach 2:
The patent introduces an automated planner as an intermediary between device capability descriptions and workflow validation. This mediator translates capabilities into a formal representation (facts, predicates, operators) and uses reasoning to validate whether planned operations can achieve desired goal states. The intermediary handles uncertainty by synthesizing missing information through logical reasoning, maintaining validation reliability while enabling high-level automation.
3Adaptability or versatility
If multiple device capability description languages are used (XCAP, JDF), then various device capabilities can be described, but it complicates how devices communicate and validates workflow plans
Solution Approach 1:
The patent applies universality by creating a unified representation framework (facts, predicates, operators) that can represent capabilities from multiple device capability description languages (XCAP, JDF, and others). This universal framework serves as a common language that simplifies device communication and workflow validation while maintaining the ability to describe diverse device capabilities. The automated planner reasons over this unified representation, eliminating the need to handle multiple language formats separately.
Data Source
AI summary
An improved automated planning method and system includes the use of an automated planner for validating a workflow plan with respect to device capabilities. As such, the present invention provides for an improved method and system for implementing and managing workflow plans utilized in printing environments such as, for example, print shops. A plurality of device capability descriptions can be converted into a data indicative of facts and operators for utilizing in a knowledge-based reasoning system. Next, a workflow plan can be converted into properties indicative of a goal state. The goal state and the data indicative of facts and operators can then be utilized in association with a domain-independent or domain-dependent planner to determine if said workflow plan is valid and executable in order to thereby validate said workflow plan.