Skip to main content
P
PThapar12-Amethyst
12-Amethyst
March 21, 2024
Solved

Re-number revision on creo

  • March 21, 2024
  • 2 replies
  • 3361 views

Hi,

I have a drawing on windchill/creo that I am revising. The current state is at "created" and rev "09". I made my revisions to the drawing but need to change the revision level to "10" instead of "09" before I release this revision. Is there a way to do this other than deleting the revision that I created and creating a brand new revision at "10" and doing my updates all over again? 

 

Thanks!
Paarth

    Best answer by PThapar

    To close this thread - 

    I discussed this issue with the admins of my organization and the business rules require me to first release my rev 09 drawing before making a new rev 10 or changing the existing rev to 10. That is the process I followed, but it can be different according to the amount of privileges a user has, along with business rules of the org. 

     

    2 replies

    avillanueva
    23-Emerald I
    avillanueva23-Emerald I
    23-Emerald I
    March 21, 2024

    You might need to explain your current lifecycle state model, revision scheme and configuration. Everyone is different.  If I read this right, 09 was the latest revision at the "created" state (not released?). You should always revise first then make the changes. To avoid you losing work, you can have the object open in session in Creo. Revise the drawing to 10 and it might ask if you want to replace in session. SAY NO to that and right after that message, save the drawing. it will check out the drawing and save your modifications down to revision 10 in your workspace. You should then be allowed to check it in. 

     

    As a safety net, you should not allow changes to be made to a previous version. For example, when items are in their final state in my system (Released), users lose modify rights. And they can only revise once it is released. This forces new revisions to be created first before modifications can be made.

      H
      Hari_Vara16-Pearl
      16-Pearl
      March 22, 2024

      Hi,

      On top of what Villanueva explained, I think if there is an "Cancelled" state in your Lifecycle definitions, will be useful, wherein it means that Rev 09 is never "Released" for use., it was rather cancelled. Think of transitioning that "Created" Rev 9 to cancelled.

      Then allowing it to be  "Revise"d to Rev 10, will make it as a better process, 

      Its all your Windchill implementation and Uncaptured Business Requirements that plays here.

      SOPs are always a moving target in an evolving PLM system!

       

      Cheers

      Hari

       

      P
      PThapar12-AmethystAuthor
      12-Amethyst
      March 22, 2024

      Hey Hari,

      Thanks for your response! There is a cancelled state in my PLM so that would be an option, although I don't want to use it provided that there is a rev 09 in a different PLM (see my response to Villanueva) and I feel that it would be confusing if the revision showed up as cancelled. If nothing else work, then this might be the route to go if my stakeholders agree to it. 

       

      Thanks!

       

      P
      PThapar12-AmethystAuthorAnswer
      12-Amethyst
      April 4, 2024

      To close this thread - 

      I discussed this issue with the admins of my organization and the business rules require me to first release my rev 09 drawing before making a new rev 10 or changing the existing rev to 10. That is the process I followed, but it can be different according to the amount of privileges a user has, along with business rules of the org. 

       

      Terms & ConditionsAccessibility statement