Route Management: Understanding the "Blocking Maturity" State

Introduction

The Route Management app in the Collaborative Industry Innovator (CSV) role allows you to create and manage sequential route tasks to complete/approve certain business activity. For example, you can define a route containing tasks that must be approved in certain order to finalize some review assessment.

With the Route Management, you can easily find status of each route tasks and identify all the stakeholders involved in the route process with complete traceability. This is also useful to reduce the time on product development phases such as initial engineering validation, compliance review, and costing assessment.

Understanding the "Blocking Maturity" State

In the R2022x FD02 release, the new functionality was introduced in this app that lets you block Maturity State promotion of objects added in the Route Content until the route is completed. This blog is an attempt to simplify the major combinations of “Route Completion Action” options along with the “Blocking Maturity” state options.

Case 1

When you set up the “Route Completion Action” as “Promote Connected Objects” and “Blocking Maturity” state as of the content as “None”:

  1. The Maturity State of the content of the route can be changed before route’s completion.
  2. When the route is completed, the content’s Maturity State is NOT automatically promoted to the next state.

Use: With this, out of all the content added in the Route, you can set up Blocking Maturity as “None” for the content that you would not like to promote automatically to next state after route’s completion.

Case 2.1

When you set up the “Route Completion Action” as “Promote Connected Objects” and “Blocking Maturity” state as of the content as “Current State”:

  1. The Maturity State promotion of its content is blocked until the route is completed.
  2. When the route is completed, the content’s Maturity State is automatically promoted to the next state.

Note: The Current State in this example means that the Blocking Maturity state of the content is same as its Maturity State while adding it in the route content.

Case 2.2

When you set up the “Route Completion Action” as “Promote Connected Objects” and “Blocking Maturity” state as of the content as “Future State”:

  1. Route’s Maturity State cannot be promoted to the “To Do” until the Maturity State of the object is same as Blocking Maturity state of the object.
  2. The Maturity State promotion of its content is blocked beyond the “Blocking Maturity” state until the route is completed. In this case, you can promote the document in above image from In Work > Frozen state but not beyond it until the route is completed.
  3. When the route is completed, the content’s Maturity State is automatically promoted to the next state. In this case, the document in above image will be automatically promoted from Frozen > Released state after route completion.

Note: The Future State in this example means that the Blocking Maturity state of the content is set as one of the next Maturity State of the content. For example, Maturity State of the document = In Work; Blocking Maturity of the document = Frozen.

Case 3

When you set up “Route Completion Action” as “Notify Route Owner” and “Blocking Maturity” state of the content as “None”:

  1. The Maturity State of the content in the route can be changed before route’s completion.
  2. After completion of route:
  • The Maturity State of the content is not automatically promoted.
  • When all tasks are completed, route owner receives a notification.

Case 4

When you set up “Route Completion Action” as “Notify Route Owner” and “Blocking Maturity” state of the content as “Current State”:

  1. The Maturity State promotion of its content is blocked until the route is completed.
  2. After completion of route:
  • The Maturity State of the content is not automatically promoted.
  • When all tasks are completed, route owner receives a notification.

TL;DR? Here's a Summary for you:

Notes:

  1. When you add an object in the content for which the “Blocking Maturity” is not supported, following warning message appears “Blocking Maturity cannot be set to the current maturity state of the newly added content..”
  2. Setting the “Blocking Maturity” state is not supported for the following Object Types yet. It is planned to be supported soon.
  • Physical Product
  • 3DShape
  • Drawing
  • XCADNonPSBaseRepReference