How ILOG Rule Studio Scorecard Modeler Works

Scorecards are new artifacts, managed in ILOG JRules through the ILOG Rule Studio Scorecard Modeler module. Users design rule applications for simple or complex scorecards as part of the rule flow and pass the results (scores with reasons) to subsequent areas in the applications.

A typical scoring application starts with a score model, which is usually created with statistical analysis software. In the score model, a set of attributes, which is relevant to make final business decisions, are selected.

A scorecard represents an assessment, opinion, or prediction about a customer or a prospect. Unlike other decision metaphors—such as decision tables or decision trees—where you set values for rule conditions and actions, the properties and values for rule conditions and rule actions in scorecards are generated from the values entered in the scorecard. Partial scores are summed for an overall score, and the result can be used by other rulesets, functions, decision tables, and decision trees in a project.

Optionally, a reason code can be generated for each rule that is fired. A reason code provides users with meaningful feedback about each partial score and its contribution to the score result.

Creating your first scorecard in ILOG Rule Studio Scorecard Modeler is easily done in a few short steps:

1. Design Your Scorecard
2. Add and assign reason codes
3. Assign scorecard properties
4. Select the reasoning strategy
5. Add your scorecard to the rule flow
6. Test your scorecard