Skip to main content
LinkedIn
Copied!

Table of Contents

Replacing models in predictions

Improve a prediction by replacing a low-performing model with a high-accuracy model. You can also replace a model with a scorecard or a field in the data model that contains a score.

For example, in a customer engagement context, you can replace a scorecard that is used to predict churn with a PMML or H2O machine learning model.

You can replace both the outcome-based and supporting models in predictions.

Ensure that Prediction Studio and your Business Change pipeline are configured to support the model update feature. For a list of prerequisites, see Updating active models in predictions.

Plan your changes by checking which model types you can use to replace your current models, and which mode you can use to deploy the new models (shadow mode, replace, direct replace). For more information, see Active and candidate model type combinations.

  1. Log in to your application:

    1. Log in as a data scientist to the Business Operations Environment (BOE).

    2. In the header of Dev Studio, click the name of your current application, and then click Switch Application.

    3. From the list, select the overlay application.

  2. Switch the portal to Prediction Studio.

  3. In the navigation pane of Prediction Studio, click Predictions.

  4. From the list of predictions, open a prediction that you want to change, and then click the Models tab.

  5. To the right of the model that you want to change, click the More icon, and then click Replace model.

    • If the active model that you want to replace is a scorecard or field, go to 6.
    • If the active model that you want to replace is an adaptive or predictive model, go to 7.
  6. In the Replace model dialog box, choose the entity with which you want to replace the active model:

    Options Actions
    Replace with a machine learning model Click Model, and then go to 7.
    Replace with a scorecard
    1. Select Scorecard, and then click Next.

    2. Select the scorecard to directly replace the current model, and then click Replace.

      The scorecard replaces the current model. This is the end of the procedure.
    Replace with a field in the data model
    1. Select Field, and then click Next.

    2. Select a field that you want to use to predict outcomes, and then click Replace.

      The field replaces the current model. This is the end of the procedure.
  7. Optional:

    If you want to use a validation data set to compare the active model and the candidate model, in the Replace model dialog box, select the Compare the models field.

    If you clear the Compare the models field, the Replace model window will not prompt you to select a data set for the comparison. You can add a validation data set later when you evaluate the model.
  8. Select the source of the new model to replace the current model:

    Choices Actions
    Use a file-based model
    1. Click Upload.

    2. In the Select a PMML, H2O MOJO or Pega OXL file section, add a model to replace the current model.

    Use a cloud-based model
    1. Click Machine learning service.

    2. In the Machine learning service field, select the machine learning service from which you want to run the model.

      Pega Platform currently supports Google AI Platform and Amazon SageMaker models.
    3. In the Model field, select a model to replace the current model.

    4. Optional:

      In the Upload model metadata file section, add a metadata file with input mapping and outcome categories for the model.

      You can create a metadata file by clicking Download template and mapping the JSON input fields to Pega Platform fields in the template. For information about the metadata file properties and the available values, see Metadata file specification for predictive models.
    Choose a model from Pega Platform
    1. Click Model list.

    2. Select a model to replace the current model.

  9. Optional:

    In the Add model documentation (optional) section, upload a documentation file for the model.

  10. Click Next.

  11. If you selected the Compare the models field in step 7, add a validation data set and the outcome column to compare the two models, and then click Next.

    The outcome column contains the response labels for the outcome.
  12. In the Summary section, in the Model name field, enter a name for the new model, and then click Add model.

    You can view the new model by expanding the twist arrow to the left of the current model. The new model name includes the number of the branch that contains the model change, for example, Validate Churn (M-7012).
    A candidate model in a prediction
    A prediction containing an active churn model and a candidate churn
                                model with the status configuration in progress.
  13. Wait a few seconds for the analysis of the new model to complete. If necessary, refresh the page by clicking Actions Refresh .

The model update work group gets notification emails when the candidate model has any of the following statuses:
  • CONFIGURATION FAILED
  • VALIDATION FAILED
  • READY FOR REVIEW

If the configuration of artifacts or validation of predictors fails, open the model by clicking its name, and read the error message in the Model comparison window. Resolve the error and resume the analysis or reject the model. For more information, see Model update statuses and notifications.

When the configuration and validation are successful, the model is ready for review.

Evaluate the candidate model. For more information, see Evaluating candidate models.
    Did you find this content helpful?

    Have a question? Get answers now.

    Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

    Ready to crush complexity?

    Experience the benefits of Pega Community when you log in.

    We'd prefer it if you saw us at our best.

    Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

    Close Deprecation Notice
    Contact us