HOW TO ENABLE MODELCHECK GATEKEEPER IN WINDCHILL ?
I found the below statement in ptc forum, but I am unable to find the location inside preference management.
PTC Creo Modelcheck Validation—Specifies whether to perform PTC Creo Modelcheckvalidation at check in. The default is NO. Enables the PTC Creo Modelcheck Gatekeeper when set to YES.
There is a page in the Windchill help documentation that is reasonably good at explaining it. You can find it here:
If that does not work I copied the contents of the page below - minus some other check in configurations that are not relevant to your query:
Configuring Check In
NoteFor more information, see the ModelCHECK Help Topic Collection documentation.
Configuring ModelCHECK in Windchill
NoteIf you click Apply after creating an attribute, the New Attribute window stays open for creation of the next attribute. When you have created all the attributes, click Done to exit the New Attribute window. You are returned to the edit mode for the CAD Document type, with the information page for the last-created attribute open in the right-side pane. For more information, see Creating a New Attribute.
NoteWildfire 4.0 M100 and Windchill PDMLink 9.1 M030(1) change the behavior of ModelCHECK Gatekeeper and mark files as out of date with ModelCHECK based on the Workspace status, not a time increment. The status is stored in the MC_VERIFIED parameter/global attribute when available. ModelCHECK Number of Hours is still required for any software combination where at least one component is using an older date code.
NotePrior to PDMLink 9.1 M030(1) ModelCHECK Mode is not a valid ModelCHECK Gatekeeper option and is not available to be set.Executing VDA Checks will set the MC_MODE value to MC_VDA. This value of MC_MODE is not supported by ModelCHECK Gatekeeper.
You need to configure the ModelCHECK conditions in Creo Parametric to obtain the appropriate configurations for the respective LifeCycle Name. A typical example to configure condition.mcc is as follows:
The Windchill OIR (Object Initialization Rule) pertaining to a CAD document for a context should be examined for the default LifeCycle Name. The fallback value of conditions.mcc for a workspace should match that of the OIR Lifecycle Name.
I first created the global attributes - where it is obvious where to set it as Integer.
You then just reference it here. There is a section in the Windchill User Guide on how to create attributes. Clicking the question mark on that screen shot will probably take you to the right place.
You may see some other posts on this topic from me. I'm violently opposed to the way PTC has provided this functionality - preventing check in. In general, you want all data to be checked in, and to allow users to freely develop concepts w/o having to run disciplined checks.
Instead, it makes sense to force use of ModelCheck and no errors before release. Can easily set up to have a workflow process branch based on the ModelCheck attribute values.
Preventing checkin is the last thing you want to do if someone doesn't know how to fix the errors.
I agree. I've had users simply delete features that gave errors because they didn't know how to fix them, usually from problems they had created. This snow-balls into other areas that were previously OK, making for hours of work to save one user a few minutes to figure out.
Just goes to show that in general PTC doesn't use their own software and doesn't understand what is important to businesses that use it. No CAD admin / CAD user would have ever even proposed to prevent check-in as the way to enforce checking.
Here's the scenario where I work now...
We design engines, so lots of complex parts, surfaces & datum features. Correct mass & C.O.G is very important.
If the above items are correct then it can still be a pain even at an early stage of the design. Waiting until the parts are released is often too late and just means more work to correct the items at a later stage.
Although we request that users checkin the models in a certain quite often they forget or cant be bothered.
I have configured model check to only check the bare minimum of what we require:
Layer status, material assignment, mass > 0, parameters, start datums, etc.
I think it's too difficult to police bad modelling methods so I've removed all associated options.
I have also set up conditions so if the part is a concept/scheme part then it wont run model check.
All parts that are physically made have a certain numbering scheme and will be subjected to a modelcheck.
I think this setup would be OK to use with the windchill gatekeeper and no doubt the modelcheck settings will be tweaked once the users have been using it for a while.
If you disable MC for objects at the concept level (State I assume?) then what's to stop your users from checking it in that way then changing the state afterwards?
Same question for the numbering scheme. I am assuming if the files are not the correct scheme then MC won't run? So the users check the files in without the correct scheme then rename the files afterwards.
Been on solidworks for the last 6 months so need to refresh my memory on this topic.
When I say concept I mean't parts or assemblies that were purely for testing out a design or analysing something.
In these files users tend to perform quick modelling tasks to achieve their goal so don't want to be hindered by exact requirements like layer status or masses stopping them checking it into to pdm.
It did seem to work quite well once users understand the differences between the two naming conventions.
It was never left too late before a proper number was required on parts that were intended for manufacture so after that they were subjected to the normal MC checks & stopped by the gatekeeper.
To be honest I would rather not have gatekeeper enabled but I've worked at so many companies that use ProE/Wildfire/Creo over the years where at least half the users leave the models in a bad state when checked in.
I'm facing similar issue. I could not able to unable the modelcheck gate keeper in windchill, Please let me know did get the solution. below is the snap I could see. I didn't find site tab.
I've commented on this before but can't help doing so again.
PTC has provided the ModelCheck Gatekeeper with good intent, but the mechanics are that it prevents check-in, which I personally think is absolutely the wrong place to put the control. The designer may not know how to get rid of the error, and is not able to check in, allowing someone else to fix it. Also, development in general should be allowed with any errors, allowing free conceptual work.
What we had in place at Alcon for years, and now have at Edwards is code in workflow (promotion / change) that branches on the value of MC_ERRORS > 0. Very easy to do, and allows the control to be only at / after release without hindering free development in any way.
Can also add code that pays attention to the related attributes (when ModelCheck was run, what config files, etc.) since those are all written to CAD File parameters, and available as CAD Doc attributes.
In my humble opinion, PTC should really revisit this, eliminating the GateKeeper as is and instead provide standard workflow code.
Note: We started soft - allowed users to acknowledge ModelCheck errors for a time and go on, then later having a hard branch to require rework.
Here I have attached the pictures, In the windchill preference management operations I couldn't find any model check options and trying to understand whether my organization has to customize the settings?
Been a while but I think I remember doing it at the site admin settings.
HQ was in China so we asked the pdm admin guy there to enable it.
This link above explains it in some detail