Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Hole Table Parameter changes should be alerted to the user.Acknowledged

1. Describe the ProblemWhen a hole file has been updated by the admin.  The user should be notified when the edit a hole that some thing has changed.   Currently, the parameters are updated without notifying the user of the change. Case 1: We want to update the Fasterner_ID to a decimal format.1) User gets a change order to change hole depth of an existing hole.  Hole was 1/4-20 using the old hole file.2) User opens part, edits the definition of the hole to modify the hole depth.3) User OK's the edit4) The hole fastener ID has been updated to .073-64 hole without alerting the user. (First hole in the detail file)5) Hole information is incorrectly shown on design documents Case 2:  Administrator remove a legacy hole detail file from the load Point.1) User gets a change order to change hole depth of an existing hole.  Hole was 1/4-20 using the old hole file.2) User opens part, edits the definition of the hole to modify the hole depth.3) User OK's the edit4) The hole fastener ID has been updated to 2-56 helicoil  hole without alerting the user. (First hole of the first file in the load point)   (Thread Type and Screw Size parameters changed without alerting the user)5) Hole information is incorrectly shown on design documents.   Design information has potentially be lost. At a minimum Creo should recognize that Screw Size and/or Thread Type don't match what is currently in the load point.   Then alert the user there has been a change.  This could extend to other parameters such as clearance drill sizes. Better would be that the warning could also suggest a new selection.   IF the same thread type is available, THEN Creo could suggest the nearest size based on drill size.Ideally, there could be some kind of replacement table that would pop-up.   With the current parameters displayed, then the user could select different tables or sizes and get a real time comparison of the differences.(function() { var wrapper = document.getElementById('lia-vid-6377537653112w200h132r54'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})();(view in My Videos)2. Are you using a workaround?We are keeping old hole files in the HOLES load point so that legacy designs are less likely to be broken during an update.3. What is the use case for your organization?We want to update the hole detail files to be compliant with common standards and conventions. But when we update the FASTENER_ID or delete a hole file, then Creo will update some of the hole parameters without notifying the user.4. What impact does this problem currently have on your organization?This problem can lead to confusion or to drawing/design errors.

ModelCHECK: Required ability to use asterisks in ModelCHECK configuration filesAcknowledged

1. Describe the Problem It would be helpful if there was a way to use asterisks in ModelCHECK's configuration files, e.g. in the condition.mcc file, to call a special check profile if the model contains one or more parameters that begin with "USR_", for example. If "MODE_UPDATE" is set to "Yes" in config_init.mc and the "EXTRA_PARAMS" option in the *.mch file is also set to "Yes", all parameters that are not present in the template defined under "PRT_TEMPLATE" in the *.mcs file will be deleted. This means that all parameters added by the user will be deleted. This is dangerous because not all parameters are used by a relation and these are therefore deleted by ModelCHECK. By using an asterisk in the condition.mcc file, it could be detected whether there are multiple user-defined parameters that begin with "USR_", for example. This condition in the condition.mcc file could look like this: IF (USR_*) config=(check/mat.mch)(check/usr.mch)(start/mat_mm.mcs)(start/usr_mm.mcs)(constant/mm.mcn)(status/status.mcq) (name/Userparameters) Or like this:IF (CONF_*) config=(check/mat.mch)(check/kon.mch)(start/mat_mm.mcs)(start/kon_mm.mcs)(constant/mm.mcn)(status/status.mcq) (name/Configuratorparameters)In this case, you could set "EXTRA_PARAMS" in the *.mch file to "no" to prevent ModelCHECK from deleting these parameters.Would it be possible for PTC to create a new condition called PRT_PARAM_WANTED or ASM_PARAM_WANTED in the *.mcs file to prevent the deletion of parameters beginning with, for example, "USR_"? This could look something like this: PRT_PARAM_WANTED USR_*Therefore, it should also be possible to use asterisks in the condition. This would also allow parameters beginning with "USR_" to be deleted. This could look something like this: PRT_PARAM_UNWANTED USR_* 2. Are you using a workaround?There's no workaround. You can only allow the deletion of all parameters that aren't included in the template. However, this will also delete all custom parameters. Or you can prohibit the deletion of all parameters. It's not possible to specifically control the deletion of parameters.3. What is the use case for your organization?If it were possible to use asterisks, one could, for example, delete all parameters in legacy data that don't begin with a specific text, such as "USR_." This would improve data quality and allow legacy data to be brought up to a new company standard.4. What impact does this problem currently have on your organization?Old parameters currently have to remain in the models because there is no way to delete them specifically and without huge effort.

Modelcheck to Check for invalid GD&T (or not created by GD&T Advisor)Under Consideration

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We design and manufacture high-end electronics. I am the CAD Manager / PTC SME. Stakeholders for this idea include our Creo user community. 2. What version of Creo Parametric are you currently running?8.0.5.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.Creo already gives an indication to the user that their GD&T is not valid. This is done either by a red underline or by using GD&T Advisor. However, modelcheck should flag an error if there is a blatant non-compliance. For instance, modelcheck should flag this:   It would also be great for ModelCheck to have a separate check for any GD&T not created using the Advisor. 4. What is the use case for your organization?Like all organization's, employees come and go. Which means that we hire engineers with different skill levels of GD&T. As they learn, we want to make sure they don't design or release data that is blatantly wrong. Something so obvious, can be checked by an automated system, and does not need to be caught by a person later and spend time reworking.5. What business value would your suggestion represent for your organization?This would quicken the release/review process. This would ensure proper design intent on the drawings. This would ensure the parts are manufactured and inspected correctly.   Since Creo already does the check, it would just mean that modelcheck needs to read that data and report on it.   @lwestbrook