Registering the whole pipeline, not just the model

A trained model rarely produces the exact number the business acts on. Often there is a last step between the model's output and the decision it drives: a threshold, a calibration, a business weight. That logic tends to live in a downstream script or a spreadsheet, disconnected from the model it depends on. When the model is refreshed or republished, the adjustment is easy to lose, and the score that reaches production no longer matches the score the team validated.

The Model Registration node in SAS Model Studio (2026.05) gives that logic a home. Because the node accumulates score code from every preceding node in the pipeline, any post-model adjustment you build with a SAS Code node travels with the model into SAS Model Manager. You register one artifact that already knows how to produce the business-ready output.

A use case: weighting predictions for decisioning

We will use HMEQ, the home equity loan dataset many SAS users already know. The target BAD flags whether an applicant defaulted. The model returns a probability of default for each application. The credit team, though, does not act on probability. They act on dollars at risk. A 40% default probability on a large, requested loan is a bigger exposure than a 70% probability on a small one.

The fix is a single derived score: expected loss, calculated as the default probability multiplied by the requested loan amount. It is a trivial expression. The hard part has always been keeping it attached to the model. Build it in a SAS Code node placed after the modeling node, and the Model Registration node carries it through to Model Manager as part of the published score code.

Step by step in Model Studio

Build the baseline pipeline. Start from the Data node with the HMEQ data and BAD assigned as the target (event level 1). Add any preprocessing you’d like, then add a Supervised Learning node such as Gradient Boosting. Run it. Note the posterior probability variable the node generates, P_BAD1.

Add a SAS Code node after the modeling node. Connect the Supervised Learning node to the SAS Code node so that its parent already generates score code. This placement is what lets the SAS Code node contribute to the accumulated score code downstream.

Author the weighting logic as score code. In the SAS Code node editor, add the expression that creates your derived output variable:

/* Expected loss: weight the default probability by the requested
loan amount so reviewers can rank applications by dollars at
risk, not probability alone. */
length EL_dollars 8;
EL_dollars = P_BAD1 * LOAN;

‘LOAN’ is already an input in HMEQ, so it is carried through the pipeline and available when the published model runs. If you derive the weight from a variable that is not a model input, make sure it is retained so scoring can reach it.

Run the SAS Code node. Confirm ‘EL_dollars’ appears in the output and the values look right against a few known records.

Add a Model Registration node after the SAS Code node. Run it. The node accumulates score code from both the Supervised Learning node and the SAS Code node, along with the artifacts required to register the model.

Register or publish from the node menu. The Model Registration node does not register automatically. Once it has run successfully, use the node menu options to register the model to SAS Model Manager, and publish to a destination if you are ready.

Verify in Model Manager. Open the registered model and confirm the score code includes the ‘EL_dollars’ calculation. The weighting logic is now part of the governed model, not a separate step someone has to remember to rerun.

What you have built

In a few steps, we took a standard supervised pipeline and made it carry its own decision logic. The Supervised Learning node produces the default probability; the SAS Code node turns that probability into expected loss in dollars, and the Model Registration node packages both into a single model registered in SAS Model Manager.

The advantage is that the business logic and the model are now one governed artifact. The expected-loss calculation is no longer a separate script that someone must remember to run, reconcile, or update when the model is refreshed. Whoever scores the model gets dollars at risk directly, computed the same way every time. The logic is versioned with the model, visible in Model Manager, and travels wherever the model is published. You register once, and the decision-ready output comes with it.

Learn more

Conversational pipeline building with SAS Viya Copilot in Model Studio

SAS Viya Workbench & SAS Model Manager for Model Training and Deployment: SAS Models

From fraud detection to fraud resolution: Building an AI voice agent with SAS Viya and LLMs

Unlocking agentic AI potential with MCP tools in SAS Retrieval Agent Manager

Registering the whole pipeline, not just the model was published on SAS Users.