After reviewing production
monitoring reports, you might find that it is necessary to retire
a champion model and replace it with a new champion model that performs
better. You might also find that the project is no longer viable,
and you need to retire the project.
You can retire a champion
model and replace it with a new champion model that resides in any
version folder for the project.
Use the following table
to determine the tasks to perform when you retire a champion model:
State of the Champion
Model
|
|
A new champion model
is available in the same version folder
|
Set the new model as
the champion model.
Update the model life
cycle milestones status as appropriate. Approval of some tasks was
based on the previous champion model.
Note: If
the characteristic or stability analysis shows significant changes,
set a new champion model in a different version folder. The bin definition
that is used in characteristic and stability analysis is based on
the data that was developed for the first champion model that was
selected in the version and does not change after it is created. An
out-of-date bin definition might cause incorrect characteristic or
stability analysis.
|
A new champion model
is available in a different version folder.
|
Set the model as the
champion model.
|
A new champion model
is not available when you want to retire a model but not retire the
project.
|
Set the project State property
to be inactive.
After a new model is
ready, do the following:
-
Set the model as the champion model.
-
Update the appropriate life cycle
milestone tasks. If the new champion model is in the same version
folder as the previous champion model, ensure that milestone tasks
are based on the new champion model and not on the previous champion
model.
-
Set the project State property
to be active.
|
No other champion models
are planned for the project and the project is to be retired.
|
Set the project State property
to be retired.
(Optional) Set the default
version life cycle retire status as completed.
|