Have you found a way to carry out a trial before a complete change is implemented? For example using the deviation and waiver functions? I've been trying to write a change process around the functionality of windchill, but so far I haven't found a satisfactory way of managing trials as part of the change process
Dave, good day, You tell "if your VP requests you to make a change then change request isn't required". The question is - who is responsible than in case because of your changes some types of other subsystems will be affected? Like you create a change in the harness network and because of that some thermal parameters inside the main are becoming not ok. Should you then immidieatly blame VP or maybe it's better to fill up those change requests manually to avoid gaps in your documents workflow? Thanks. Sergey
Sergey, Every organization has to determine the business rules under which it will operate. Luckily Windchill has the flexibility to accommodate whatever rules you decide. In our case, our rules were based around rapid development, not assigning blame. In that case, it was the responsibility of the Change Notice creator (usually me) to determine the scope of the change and write the appropriate Change Tasks. If you want to mandate Change Requests, you can do that. My point is that Windchill doesn't force you to have a Change Request for a Change Notice if you determine one is not necessary. Dave
@@CADPLMGuy If you want to mandate Change Requests, you can do that. Dave, Maybe it's not about "whom to blame" but "whom to inform" about changes. Back to my example - if something has mutual influence like two subsystems I've put as an example - it's better for a chief of design to be informed that VP, or President (or even President of Russia) told an engineer to do something. In your lecture, you've told us that it's better to allow everybody to fill up the Change request. That's a good point - If a chief of design thinks like it's not important (change request)- that's ok. He can do it - but everybody in the design team should have information about something which is important and which may have influence for the future. That's my point, Dave. Thank you.
So again, you can decide what business rules work best for your organization. Also, in another video, I showed how you can subscribe people to objects. When I was the Change Admin, I also subscribed relevant parties to Change Requests and Change Notices as necessary. Also, to be clear, at 15:11, I am clear to say "in my personal opinion" regarding the ability for anyone to create Change Requests. I do not want to imply that it is absolutely better. Your mileage may vary and your organization may require different rules - and Windchill has the flexibility to accomplish this.
The embedded browsers are based off Chrome and Internet Explorer. For standalone, I have been fine with Chrome, Firefox, and IE. I have not tried Edge yet. I do not believe PTC states a preference but I remember last year Firefox had some issues with Creo View. Those might be resolved.
Great Video! Is there an Option to choose a specific Change Admin 1? For Example: I create a Change Request and i want excatly one Person to approve this Change Request. Thank you! Keep on doing Videos.. There are not many Video about Creo/Windchill PTC..
Windchill is all about configuration and customization. It's all based on how your Windchill admins define your workflows and business rules. I am using the OOTB configuration.
@@CADPLMGuy Thank you for answering. I think you misunderstood my question. The assignee should not be able to edit any part of the Change Task other than resulting objects. Otherwise they could just change the finishing date or the reviewer.
Have you found a way to carry out a trial before a complete change is implemented? For example using the deviation and waiver functions? I've been trying to write a change process around the functionality of windchill, but so far I haven't found a satisfactory way of managing trials as part of the change process
No, I’ve never needed to... I don’t know what the parameters or requirements of a trial would be...
Dave, good day,
You tell "if your VP requests you to make a change then change request isn't required".
The question is - who is responsible than in case because of your changes some types of other subsystems will be affected? Like you create a change in the harness network and because of that some thermal parameters inside the main are becoming not ok.
Should you then immidieatly blame VP or maybe it's better to fill up those change requests manually to avoid gaps in your documents workflow?
Thanks.
Sergey
Sergey,
Every organization has to determine the business rules under which it will operate. Luckily Windchill has the flexibility to accommodate whatever rules you decide.
In our case, our rules were based around rapid development, not assigning blame. In that case, it was the responsibility of the Change Notice creator (usually me) to determine the scope of the change and write the appropriate Change Tasks.
If you want to mandate Change Requests, you can do that. My point is that Windchill doesn't force you to have a Change Request for a Change Notice if you determine one is not necessary.
Dave
@@CADPLMGuy If you want to mandate Change Requests, you can do that.
Dave,
Maybe it's not about "whom to blame" but "whom to inform" about changes.
Back to my example - if something has mutual influence like two subsystems I've put as an example - it's better for a chief of design to be informed that VP, or President (or even President of Russia) told an engineer to do something.
In your lecture, you've told us that it's better to allow everybody to fill up the Change request. That's a good point - If a chief of design thinks like it's not important (change request)- that's ok. He can do it - but everybody in the design team should have information about something which is important and which may have influence for the future.
That's my point, Dave.
Thank you.
So again, you can decide what business rules work best for your organization. Also, in another video, I showed how you can subscribe people to objects. When I was the Change Admin, I also subscribed relevant parties to Change Requests and Change Notices as necessary.
Also, to be clear, at 15:11, I am clear to say "in my personal opinion" regarding the ability for anyone to create Change Requests. I do not want to imply that it is absolutely better. Your mileage may vary and your organization may require different rules - and Windchill has the flexibility to accomplish this.
What is the PTC preferred browser to use for Windchill?
The embedded browsers are based off Chrome and Internet Explorer. For standalone, I have been fine with Chrome, Firefox, and IE. I have not tried Edge yet. I do not believe PTC states a preference but I remember last year Firefox had some issues with Creo View. Those might be resolved.
Great Video! Is there an Option to choose a specific Change Admin 1? For Example: I create a Change Request and i want excatly one Person to approve this Change Request. Thank you! Keep on doing Videos.. There are not many Video about Creo/Windchill PTC..
Windchill is all about configuration and customization. It's all based on how your Windchill admins define your workflows and business rules. I am using the OOTB configuration.
How do Assignees add Objects to the resulting Objects of a Change Task without giving them permission to edit the Change Task?
If they don't have permissions, they should contact a Change Admin.
@@CADPLMGuy Thank you for answering. I think you misunderstood my question. The assignee should not be able to edit any part of the Change Task other than resulting objects. Otherwise they could just change the finishing date or the reviewer.
If those are your business rules, you should write those into your workflows.
@@CADPLMGuy Thank you, I didn't know this was possible. We are currently looking into change notices for our company.