Process and Operation Feasibility
For a non-optional process or operation, feasibility modules are used to specify two kinds of conditions:
• Conditions under which it is possible (in the context of the current routing) to use the process or operation in the creation of the current part. If the conditions aren’t met, the current routing fails.
• Conditions under which it is required (in the context of the current routing) to use the process or operation in the creation of the current part. If the conditions aren’t met, the current routing fails.
For an optional process or operation, the feasibility module specifies just the first kind of condition (conditions under which it is possible); the optionality module specifies the second kind (see
Process and Operation Optionality).
The module should return true if the conditions are met, and return false otherwise.
So for example an injection molding feasibility module might check for compatibility between the process and the current material; the feasibility module for a tube laser hole cutting operation might check that the hole is large enough and not flanged, threaded, or countersunk (see the examples below).
When you navigate to the CSL modules for a node (see
Navigating from the Template Graph to the Data for a Given Node), if the node has a feasibility module, the module’s
Type Name field is set
routingRule, and the label
routingRule appears next to the folder icon.
Feasibility module names should start with pfr (for processes) or ofr (for operations) and end with .csl.
This section includes the following subsections: