Working with decision records and decision gates
The Lifecycle tracker allows you to add and monitor different types of activities, among them decisions.
As shown in the following example image of the Lifecycle tracker, there are two types of decisions: decision records and decision gates.
Decision records
Decision records are an activity type that allows you to capture any pertinent information regarding the decisions you and other stakeholders make about the AI use case.You can add as many decision records as you want. They are created with the status Completed, and the status doesn't evolve.
Decision records are not carried forward when an asset advances to the next lifecycle stage.
You can use the stage stepper tabs in the Lifecycle tracker to go back and revisit the decision records you and others created in an earlier lifecycle stage.
You can edit the decision records that you have added, but not those that others have added.
Add a decision record to the Lifecycle tracker
Tip If you add a decision record and don't see it in the task table, increase the value of the Rows per page setting in the Lifecycle tracker or go to the last page of activities.
Requirements and permissions
- You have a global role with the Product Rights > AI Governance global permission. The out-of-the-box AI Business User and Data Scientist global roles have this permission.
- You have the Asset > Lifecycle Management > Decision Record resource permission for the community or domain in which the AI Use Case asset or AI Model asset is stored.
If you don't have the required permissions, the Add Activity button is not shown.
Steps
- Open the relevant asset page.
- In the Lifecycle tracker, click Add Activity, and then select Decision record.
The Decision Record dialog box appears. - Enter the details of the decision you want to capture.
- Click Add.
A decision record with the status Complete is added to the Lifecycle tracker.
You can edit the decision records that you have added, but not those that others have added.
Decision gates
Decision gates capture the decision details specifically when stakeholders decide to change the AI use case from one lifecycle stage to another, for example from Ideation to Development, or vice versa.
Decision gates are triggered when you use the Move to <stage> button in the Lifecycle tracker, to advance or revert the lifecycle stage of an asset. The Move to <stage> dialog box prompts you to describe the decisions and justification for advancing or reverting the stage of the AI use case or AI model, for example stakeholder decisions, recommendations from Legal, or committee meeting minutes.
Decision gates are not carried forward when the AI use case status evolves.
You can use the stage stepper tabs to go back and revisit the decision gate details in an earlier lifecycle stage.
You can edit the decision gate details that you have provided, but not those that others have provided.
For more information on the lifecycle of AI models and AI use cases, go to Asset Lifecycle management.