Managing ModelCHECK Validation during Check In
Creo Parametric allows you to use ModelCHECK™ as a "gatekeeper" to the Windchill database, which means that to be successfully checked in, models must meet ModelCHECK criteria. This gatekeeper functionality is controlled by the Windchill server, which references the read-only ModelCHECK parameters contained in the models.
Configuring ModelCHECK in Creo Parametric
To enable the gatekeeper functionality, you must first edit the ModelCHECK configuration to enable ModelCHECK to add the required parameters to the data. From the ModelCHECK Configuration window within Creo Parametric, edit the initialization file (config_init.mc) and change the following objects.
• Set MC_ENABLE to Y
This enables ModelCHECK, and is required even if the config.pro option modelcheck_enabled is set to ‘yes.’
• Set MODE_RUN to Y
This enables individual run modes of ModelCHECK: Interactive, Batch, Regenerate, and Save. At least one run mode must be enabled.
• Set ADD_DATE_PARM to Y
This creates a parameter called MODEL_CHECK in the model files of all models that are checked. This parameter contains the date and time when ModelCHECK was last run.
• Set ADD_ERR_PARM to Y
This creates a parameter called MC_ERRORS in all models that are checked. This parameter contains the number of errors found in the model when ModelCHECK was last run.
• Set ADD_CONFIG_PARM to Y
This creates a parameter called MC_CONFIG in all models that are checked. This parameter contains the names of the ModelCHECK configuration files used for a final check of the model.
• Set ADD_MODE_PARM to Y
This creates a parameter called MC_MODE in all models that are checked. This parameter contains the mode in which ModelCHECK was run on the model.
• Set ADD_VERIFIED_PARM to Y
This allows the creation of a parameter called MC_VERIFIED in all models that are checked.
After editing the settings, save the configuration. As a result of this change, anytime you run ModelCHECK, these new read-only parameters are added to the data files.
 |
For more information, see the ModelCHECK Help Topic Collection documentation.
|
Configuring ModelCHECK in Windchill
After configuring ModelCHECK in Creo Parametric, configure Windchill using the following steps.
1. In the Windchill Type and Attribute Management utility ( > > ), expand the Manage Types node and find and select the CAD Document subtype of EPM Document. Click Edit from the Action menu for the type to enter edit mode, and click the new attribute icon 
on the Attributes tab to access the New Attribute window and proceed to create attributes with following names and attribute types:
on the Attributes tab to access the New Attribute window and proceed to create attributes with following names and attribute types:◦ MC_ERRORS -- (integer)
◦ MODEL_CHECK -- (string)
◦ MC_CONFIG -- (string)
◦ MC_MODE -- (string)
◦ MC_VERIFIED -- (boolean)
| | If 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. |
2. When you are done creating the attributes, in the attribute information page for the last created MC_<ERRORS/CONFIG/MODE or VERIFIED> attribute, select the Visibility tab. In the Screen Type column find the screen types, Create New, Edit, and EPM Upload, and set the value for each of the screen types to Value Hidden. Then click Save.
3. Repeat the setting of Value Hidden in the screen types of Create New, Edit, and EPM Upload for the remaining MC_<ERRORS/CONFIG/MODE or VERIFIED> attributes. When all four attributes have had their visibility values set, click Done to exit the edit mode of the CAD Document type page. You can then close the Type and Attribute Management utility. For more information on attribute visibility, see Viewing and Setting Attribute Visibility.
4. Set the preference > > to yes (the default is no) to enable ModelCHECK.
5. Set the appropriate modelCHECK preferences (also in > ) to configure ModelCHECK, as follows:
◦ Set ModelCHECK Number of Errors to specify the maximum number of ModelCHECK errors allowed. The default is 0.
◦ Set ModelCHECK Number of Hours to specify the maximum allowable hours between a ModelCHECK verification at the client and the actual model checkin to Windchill. The default is 24.
| | Wildfire 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/reusable 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. |
◦ Set ModelCHECK Mode to specify the run mode used to execute ModelCHECK: Disabled, Interactive (default), Regenerate Explicit, Regenerate Implicit, Regenerate Always, Save, or Batch.
| | Executing VDA Checks will set the MC_MODE value to MC_VDA. This value of MC_MODE is not supported by ModelCHECK Gatekeeper. |
◦ SetModelCHECK Configuration to specify the ModelCHECK Configuration files to be used for validation for each LifeCycle name in a specific syntax.
(For example:
<Lifecycle_1>:<mch_file1>,<mcs_file1> <Lifecycle2>:<mch_file2>,<mcs_file2>...
The configuration specified by the "Default" life cycle state is fallback behavior. Typical examples are as follows:
▪ Default:check/default_checks.mch,start/nostart.mcs,constant/inch.mcn
▪ Basic:check/basic_checks.mch,start/basic_start.mcs,constant/inch.mcn
▪ Release:check/release_checks.mch,start/release_start.mcs,constant/inch.mcn
▪ Approval:check/approval_checks.mch,start/approval_start.mcs,constant/inch.mcn
▪ Review:check/review_checks.mch,start/review_start.mcs,constant/inch.mcn
| | 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. • IF (PTC_WM_LIFECYCLE EQ Basic) config=(check/basic_check.mch)(start/basic_start.mcs)(constant/inch.mc n)(status/basic_status.mcq) • IF (PTC_WM_LIFECYCLE EQ Release) config=(check/release_check.mch)(start/release_start.mcs)(constant/inch. mcn)(status/release_status.mcq) • IF (PTC_WM_LIFECYCLE EQ Approval) config=(check/approval_check.mch)(start/approval_start.mcs)(constant/i nch.mcn)(status/approval_status.mcq) • IF (PTC_WM_LIFECYCLE EQ Review) config=(check/review_check.mch)(start/review_start.mcs)(constant/inch. mcn)(status/review_status.mcq) • ELSE set the fallback (CADDocument OIR - LifeCycle Name at context level) • ELSE config=(check/basic_check.mch)(start/basic_start.mcs)(constant/inch.mc n)(status/basic_status.mcq) |
| | 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. |