Skip to main content
C
CR_988805612-Amethyst
12-Amethyst
July 25, 2023
Solved

Promotion Requests - Windchill

  • July 25, 2023
  • 3 replies
  • 2241 views

I'm sure this has been asked in some form already but what is the purpose or advantage of using Promotion Requests vs. the Change Management process of CN's & CR's?

Our company here uses Promotion Requests to vault different revisions of new designs before they are officially released. I was curious what other reasons someone would use a Promotion Request?

 

-CR

Best answer by jbailey

I think they both have their place. We typically use promotion requests for initial release of items. For the change process though, you get a lot of added functionality... Tying to end items, effectivity, approving a change before work is done, tracking complex implementation actions in the change notice vs several promotion requests. In WC 12.0.2 and newer, you can "Plan" changes before anything ever gets revised, so that you only actually revise objects once the change request has been approved.  Try fixing that nightmare after a few weeks of work on a project determines they revised something they didnt need to...

 

 

3 replies

jbailey
jbailey18-OpalAnswer
18-Opal
July 25, 2023

I think they both have their place. We typically use promotion requests for initial release of items. For the change process though, you get a lot of added functionality... Tying to end items, effectivity, approving a change before work is done, tracking complex implementation actions in the change notice vs several promotion requests. In WC 12.0.2 and newer, you can "Plan" changes before anything ever gets revised, so that you only actually revise objects once the change request has been approved.  Try fixing that nightmare after a few weeks of work on a project determines they revised something they didnt need to...

 

 

    avillanueva
    23-Emerald I
    avillanueva23-Emerald I
    23-Emerald I
    July 26, 2023

    @jbailey agree with your post. For the longest time we only used CR/CNs to release things. We use same process both for initial release vs rev/FFF changes where part number changes.  The thought process was that user's only need to learn one process. The process of releasing is also a review and approve process. Why should initial release be any different than follow on changes? In fact, you would want the highest level of review on that initial release since all your design issues exist at that time. We have the same CCB involved in those releases.

     

    Where CR/CN did not make sense was for lower level documents that are less critical to the design. Those were traditional adhoc signed, for the longest time manually and there were looser requirements on who signs off.  For those, we adopted a Promotion Request process where the users picks the approvers, admins validate that approvers are sufficient and they are sent tasks to conduct review/approval. There is some confusion as to which process to use but its not a huge issue. 

     

    In both cases, we make use of discussion forum to track comments, replies and confirmation that issues are resolved for an audit trail.

      B
      23-Emerald III
      BenLoosli23-Emerald III
      23-Emerald III
      July 26, 2023

      We only use Promotion Requests in Windchill. It allows us to 'lock' a design revision so any changes must be made by revising the part to the next higher revision or creating a new part.

      We did try change notices and change tasks a few years ago, but then our processes changed and management decided to not try to implement the new process in Windchill. 

        Terms & ConditionsAccessibility statement