RSA module definition. |
|
Differences between RSA and base RCO function blocks. |
|
Range Source manipulation. |
|
Configure RSA Modules. |
|
RSA Applications. |
RSA module definition
RSA function blocks eliminate or weight items instead of decisions. Items that remain after an elimination are available to the function blocks that follow.
An RSA module:
Is a series of function blocks that starts with a range-defining block and usually ends with an item selection.
May be part of a routing logic or output logic module.
The RSA module, in effect, is pre-processing logic that:
Selects an item and
Sets or stores data about the selected item.
This data can then be used by base RCO function blocks to make routing decisions and generate output.
If your RSA module starts in the routing logic, the range source list (or selected item) is available to the output logic of any remaining decision, where you can continue your RSA module.
Differences between RSA and base RCO function blocks.
RSA function blocks are different from Routing and other base RCO function blocks in the following ways:
|
Traditional RCO |
Range Source Architecture |
Item Source |
Source Region |
Range Source (non persistent) |
Eliminates |
Decisions |
Items |
Item Destination |
Destination Region |
If the RSA module is in an RLM: Item(s) not eliminated from the range source are available for further processing to subsequent function blocks within the same routing or output logic module. These subsequent blocks may execute traditional RCO elimination logic to choose a Decision. Changes made to an item's standard attributes, extended attributes, or to the TADB persist and remain available when the item is processed by other routing or output logic modules. A selected item is available to, and may be routed by, the remaining Decision's Output Logic Module. |
Range Source Manipulation
In traditional RCO, one or more source regions may be routed to one or more destination regions. But the order in which items are processed by a routing logic module is primarily determined by the order in which items are queued. Depending on how decisions are eliminated, one or another item at the head of a decision's source region will be processed next. If necessary, an RCO may even reject an item by routing it to a Detainment region. But the item, once it has left its source, must go somewhere.
However, there are situations where it is advantageous to apply logic before items leave their source regions. In those situations, RSA provides supplemental logic to:
Set the range of sources by range, criteria or solve (query). |
|
Select, or sequence, the next item to process through elimination and weighting. |
|
Assign sequence numbers, e.g. rotation numbers, to items in the range source. |
|
Substitute the order associated with an item in the range source for the order of another item at a particular region location. |
|
Apply a hold to items that take effect when they enter a range. |
Note: A routing logic module (RLM) that uses RSA function blocks does not need to determine any routing decisions. The RLM can be used merely to modify attributes of items in the range source. For example, a range of items can be placed on hold or assigned rotation numbers. The modification persists after the control cycle executing the function blocks is completed without necessarily moving any items. In this case there is no decision elimination. Therefore, make sure to include only one decision in the RCO's Decisions folder, or configure a Multiple output module.
Important: RSA function blocks with Attribute Name and Attribute Value parameters support standard and extended attributes.
TADB attributes may be accessed using the:
RSA function blocks that support named solves (queries) or
RSA function blocks that support solve (query) expressions (using the reserved name SOLVE instead of the attribute name) or
TADB function blocks to access TADB attributes directly.
Configure RSA modules. |
|
Range Source Architecture overview. |