Planning a Project Control Group

Before you begin a project control group, you must plan your project control group resources. Here are questions to consider and conditions to meet for a modeling projects within a project control group:
  • After you know which users are assigned to the projects within a project control group, a SAS Model Manager administrator must ensure that the user is assigned to the appropriate SAS Model Manager user group and role. For more information, see SAS Model Manager User Groups, Roles, and Tasks and the SAS Model Manager: Administrator's Guide.
  • How do you want to structure the projects within the project control group in the Project Tree? A project control group is a subfolder of an organizational folder. The Project Tree enables multiple levels of organizational folders so that you can customize how you structure the Project Tree. For example, your Project Tree could be similar to your business departmental hierarchy or it could list individual project names. For more information, see Organizing the Project Tree.
  • What models do you want to use in each project of the control group? If the models were created using SAS Enterprise Miner, SAS/STAT, or the SAS/ETS procedures COUNTREG and SEVERITY, all model components are available to SAS Model Manager when you import the model. Only models that are contained in an SPK file can be imported using the Create Projects from a Control Table feature. At least one SPK file must be prepared for each project and the SPK files should be placed in the same location. If your model is a SAS code model or a PMML model that is not contained in an SPK file, you must import it separately into the desired project within the project control group, and you must ensure that you have imported all of the model component files. For more information, see Import SAS Code Models and R Models Using Local Files and Import PMML Models.
  • What model function do you want to use in each project of the control group?
    SAS Model Manager has several model function types:
    • Analytical
    • Prediction
    • Classification
    • Segmentation
    • Any
    After the model function is specified for the project control group, the Model Function property for a project cannot be changed. Ensure that the types of models that you are going to use in each project of the project control group fit within the selected model function type. For more information, see Types of Model Functions.
  • How do you want to define your project input and output variables? When you create a project control group, you can import the variables using input and output prototype tables, copy the variables from an existing champion model, or define individual variables. The project variables are set for each project within the project control group. If you use prototype tables to define the project input and output variables, the tables must be registered in the SAS Metadata Repository using SAS Management Console, or you must create a libref for files that are stored on a local or network drive before you create the project control group. For more information, see About Defining Project Input and Output Variables.
  • What method do you want to use to track the progress of a version? The Workflow Console enables you to track the progress of activities from the version level for each individual project within a control group. A SAS Model Manager administrator can create a workflow and associate it with a version. You can also use the life cycle feature to track the life cycle of models at the version level.
    • If you decide to use the workflow process to track the progress of activities for a version, you do not need to use the life cycle feature to monitor the progress of milestones and tasks. However, you must select a life cycle when creating a project control group, but you do not need to use the life cycle feature. You can associate a workflow at the version level for each project with the control group. For more information, see Overview of Workflow Console.
    • If you decide to use the life cycle feature to monitor the progress of your version, you must plan your milestones and the tasks for each milestone before you can create a version for each individual project within a project control group. When you have that information, you then create a life cycle template. The life cycle template enables you to assign users at the version level to complete projects and to monitor the progress of your project. For more information, see Creating Life Cycle Templates.
  • When you publish project champion models from a project control group to the SAS Metadata Repository, you must specify a folder to which you can publish the project champion models. You might need to create a folder in the SAS Metadata Repository, if one does not already exist. For more information, see Publish Models to the SAS Metadata Repository.
  • After your project champion models are in a production environment, you can monitor the performance of the project champion models within a project control group in SAS Model Manager using your organization's operational data. If you use SAS Model Manager to monitor performance of projects within a project control group, you must first prepare performance tables using the operational data and then register the tables in the SAS Metadata Repository using SAS Management console or create a libref for files that are stored on a local or network drive. For more information, see Creating a Performance Table.
  • When you run performance monitoring reports, you can set up performance index alert and warning conditions to notify users if conditions exceed the indexes. For more information, see Performance Index Warnings and Alerts.