Creating Gated and Non-Gated Process Models

By creating a process model, Process Designers ensure that similar projects follow the same process from start to completion. The basic steps to create a gated or non-gated model are the same and described below. For gated models, continue by adding stages, gates, and so forth as appropriate to the model type. Non-gated models are created with a single stage.

For information about creating idea models, see Creating Idea Process Models.

To create a gated or non-gated process model:

From the System menu, select Process > All Models.

To narrow the process model list, search by the process model name, system name, or class.

Do one of the following:

To add a new model - Click Add New in the upper right corner of the page.
To create a new model based on an existing model - Click in the Copy column to create a copy that can be used as a base to build a new model.
To edit an existing model - Click the name of the model to open it for editing.

See How Changing Process Models Affects Open and Closed Projects to understand what changes are applied to open and closed projects.

If you selected to add a new model, complete the following information to identify and describe the model:

Required fields display with red text and an asterisk * if the field is empty.

Field	Description
Name	Enter a name, up to 64 characters long, which identifies the process model. More... Give the model a name that clearly indicates which projects use the model so Process Managers recognize the model to select when creating projects.
System Name	Enter a unique, shorter name that identifies the process model when importing and exporting models between environments.
Class	Select the class to which the model belongs. The class you select determines if the model is a gated or non-gated model, based on the process type defined in that class.
Description	(Optional) Enter a description of the purpose and use of the model. The description should provide additional details about the type of projects that are appropriate for this model.
Configuration Access Groups	Select the access group(s) to which this process model belongs. More... The access group(s) displayed are based on the current user's access group permissions, and the process model defaults to the highest level access group listed. Note that the process model is only added to access groups that are checked. It does not propagate to child access groups unless those child groups are checked. Edit the configuration access group on the Security tab of the process model.

Click Create to create the model.
On the Process Definition tab, complete the following information in the Process Editor section to define display and behavior for projects based on the model:

Field	Description
Name	Edit the name of the process model.
System Name	Edit the system name.
Class	Edit the class selection. To modify the class, the new selected class must have the same Process Type. If there are multiple classes of the same Process Type (gated, non-gated, idea), those classes display for selection. If there are no classes of the same Process Type, the field displays as read-only.
Description	Edit the description.
Project Name Metric	To set a project name automatically based on a metric value, click and select the metric that determines the name. Only metrics associated to the project are available for selection. See Automating Projects Using Metrics in Process Models. If a metric is selected: Ensure the metric required to set the project name is available for edit on the project creation page so the name can be populated accordingly. Ensure that the selected metric's formula does not include the project name, or a metric that includes the project name. Note: If the metric's calculation returns no value, the project name is set to the class name. If a metric is selected here, the project name is read only within the project pages.
Project ID Metric	To set a project ID automatically based on a metric value, click and select the metric that determines the ID. Only metrics associated to the project are available for selection. See Automating Projects Using Metrics in Process Models. If a metric is selected: Ensure that the metric required to set the project ID is available for edit on the project creation page so the ID can be generated accordingly. Ensure that the selected metric's formula does not include the project ID, or a metric that includes the project ID. Note: If the metric's calculation returns no value, the project ID is set to the system project ID. If a metric is selected here, the project ID is read only within the project pages. If the Auto-Generate Project IDs system parameter is enabled, this option is not available.
Project Link Rules	Click Project Link Rules to define a set of rules and conditions that are used to link related projects for all projects that use this process model. See Linking Related Projects. You can only edit link rules for process models to which you have configuration access group rights. Only process models to which you have configuration access groups display for selection when linking related projects. However, you can edit rules linked to multiple models even if some models you only have view access groups rights to.
Active	Select this check box when the model is ready to use in projects.
Disable Add New	Select this check box to disable the ability to create new projects through the Add New Project page or Add New button pods. Use this setting to create a model for projects that, for example, are only created through project migration, project import, or as elements in the Planning Board.
Hide from Add New page and drop-downs	Select this check box to remove the model from the list of models on the Add New Project page. Use this setting to create a model for projects that, for example, are only created through an Add New button pod within a project.
Set gates page to read-only	If this is a gated model, select this option to disable the ability to edit gate content and gate dates within a project either directly on the project's Gates layout pages, or via the process graphic. Select this option only if you use other means to set project gate dates and decisions within the projects that use the model, such as using automated steps within workflows.
Default Project Manager	To set a default Project Manager for new projects created based on this model, select one of the following options: To assign a Project Manager automatically - Select the User option and click to select the Accolade user that will automatically be assigned as the Project Manager. To assign a Project Manager automatically based on a metric value - Select the Metric option and click to select a metric whose value determines the Accolade user that is assigned as the Project Manager. Selecting a metric enables automatic routing of ideas, concepts, and projects to the correct business leader based on other project criteria such as business area, product line, or geographic location. See Automating Projects Using Metrics in Process Models. Only users assigned the Project Manager user role and only metrics associated to the model are available for selection. Process Managers can assign a different manager at the project-level after a project is created. Ensure metrics scheduled to calculate only on project create do not reference team leader metadata if the default project manager metric is set.
Lead/Manager required on create	Select this check box to require a project manager be selected before project creation or migration. This setting does not enforce project manager selection for Ideation, Innovation Planning, importing projects, or workflow migration.
Default Portfolio Child Model	Select the model that is used for projects created when the Create Child Project button is used within a page layout assigned to this model. The model you are creating must be based on a class that is set as a portfolio class to select a default model. Only models you have appropriate access group view or configuration rights to display for selection.
Allow Mid-Process Project Start for Creation	If this is a gated model, select from the following options: No - Projects created using this model start at the beginning of the process, and do not allow a project to start mid-process. This is the default setting. Select by Stage - Projects created using this model can start in a selected stage within the process. Select this option if the model starts with a stage to ensure that projects can start at the beginning of the process. Select By Gate - Projects created using this model can start in a selected gate within the process. Select this option if the model starts with a gate to ensure that projects can start at the beginning of the process.
Allow Mid-Process Start for Migration	If this is a gated model, select from the following options: No - Projects migrated to this model start at the beginning of the process, and do not allow a project to start mid-process. This is the default setting. Select by Stage - Projects migrated to this model can start in a selected stage within the process. Select this option if the model starts with a stage to ensure that projects can start at the beginning of the process. Select By Gate - Projects migrated to this model can start in a selected gate within the process. Select this option if the model starts with a gate to ensure that projects can start at the beginning of the process.
Extend project edit rights	Select this check box to allow the extension of project edit rights to selected team members. When enabled, Project Managers can select team members who are allowed to edit project information that is available on project page layouts, such as the Project Home page or any other custom project pages.

(Optional) Define the documents associated to the model in the Document Management section with the following settings:

Field	Description
Related Document Categories	Enter the list of categories that are available for related documents added to projects based on the model. Separate the list items using the pipe ( \| ) character. For example, enter Specs\|Designs\|Schedules to create three categories that use those same names. If the model contains no categories, all related documents are added to the Default category.
Protect versions from deletion	Select this option to disable the deletion of all documents in a project. If set, users on a project cannot delete any deliverable, activity, related document, or gate document version. In addition, users cannot delete an activity if it contains a version. Selecting this option overrides any Allow versions to be deleted settings for individual deliverables, activities, and gate documents. To allow the deletion on an individual document basis, clear this option and set the Allow versions to be deleted option at the individual document level.

Field

Description