Skip to main content

Filter by idea status

Filter by product

6851 Ideas

ptcstatus to differentiate between subscription and perpetual licensesAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Mechanical Engineering design.   IT administrator.    Creo Parametric users.2. What version of Creo Parametric are you currently running?Creo 8.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video."We have Creo Simulation Basic ENG (formerly Pro/ Creo 3.0) Flt Lic perm license and Creo Simulation Basic ENG (formerly Pro/ Creo 9.0) Flt Lic Subscription license on one of our license servers. When we run ptcstatus on a client machine, both of these show up as MECBASICENG_License.   As a result, the user won't be able to know which is used or available.     Is it possible for you to improve your ptcstatus.bat script to include the license type (formerly Pro/ Creo 3.0 and  formerly Pro/ Creo 9.0 in this case) and/or the expiry date,  If this is too much info to display, maybe you can have the ptcstatus.bat script accept an option parameter say "v" for verbose. So when user runs ptcstatus -v, he will get a more detailed output which will enable him to differentiate between Creo Simulation Basic ENG (formerly Pro/ Creo 3.0) and Creo Simulation Basic ENG (formerly Pro/ Creo 9.0) Current output of ptcstatus:MECBASICENG_License 0 1MECBASICENG_License 0 1MECBASICUI_License 0 1MECBASICUI_License 0 1ptcstatus output. users cannot tell which MECBASICENG_License is for the perm (Creo 3) and which is for the subscription lincese (creo 9). Our license file:#MECBASICENG_License 1 Creo Simulation Basic ENG (formerly Pro/ Creo 3.0 Flt Lic perm 2A10xxxx#MECBASICUI_License 1 Creo Simulation Basic UI (formerly Pro/M Creo 3.0 Flt Lic perm 2A10xxxx#MECBASICENG_License 1 Creo Simulation Basic ENG (formerly Pro/ Creo 9.0 Flt Lic 30-may-2023 1R234xxxx#MECBASICUI_License 1 Creo Simulation Basic UI (formerly Pro/M Creo 9.0 Flt Lic 30-may-2023 1R234xxxx4. What is the use case for your organization?ptcstatus5. What business value would your suggestion represent for your organization?Allow our users to know if the feature licenses have been fully used.    Also, if ptcstatus can show the expiry date, our users can alert the organization IT admins of it.   Sometimes, the IT admins can forget to renew the licenses before they expire.  This also makes good business sense to you PTC since it ensures timely renewal by your customers.

Creo-MBD -- Boost PMI usage by user based attributesAcknowledged

Creo-MBD -- Boost PMI usage by user based attributesDigitalization, in engineering by Model Based Definition leads instantly to the questions beyond standard quality characteristics on the CAD model:how to track/handle/identify detached data sets of the CAD-model in data network and/or in diverse post processes/systemshow to  enrich standard semantic information set in PMIs to support processing topics in workflows, indicators/hints,  machining issues, analysis, manufacturing, ...This is not in contradiction with given data models in neutral data formats like STEP and JT.They already offer the possibility for additional user attributes in standard PMIs as well as definitions of non standard classified PMIs. Requirement:Provide  user based attributes(properties) for PMI in CreoEnsure that user based PMI attributes are exported correctly to neutral data formats JT & STEPUse Cases:add a UUID to characteristic/PMI to identify characteristics-object independently from CAD-Model as data set in all subsequent IT processes/systemsAdd key/value pair(s) to extend standard PMI information setsRegarding various manufacturing methods it enables PMI information which could not be represented in currently standardized PMI classes e.g. ; criticality of specifications, special machining or IT processing, functions to enable specific Creo Toolkit Applications, Exclusion of PMIs for specific post processes, etc.one way to enrich semantical information which must be attached to the model for future upcoming use cases, not covered in (present) standard Business Value:If a 3-D-CAD-Model should replace a drawing, leveraging the digital approch, this medium acts like a data container which must serve data processing/analysis topics and various manufacturing topics, already described in use cases. Without requested PMI enhancement MBD approach will be truncated.@Mfridman : acc. your requestReference to chat this EHR  @tbusshoff @kschaefer 

Fully support of an "Inheritance feature" in an MBD world by REUSE FeatureAcknowledged

Inside an MBD world a full annotated model is the basic for a digital production. How do we handle REUSE feature from other models or out of a library? OK, Merge is a nice solution, and is supporting the digital MBD approach 100%, if there is no dimension or features which need to get changed or modified or suppressed. As soon as a merged library part get modified, it's not a standards library file anymore (inside Windchill) and need to get copied and renamed. A variable reuse of feature is missing inside CREO. More and more library parts are similar and can be used in different sizes, that’s a kind of flexible library reuse part. Inheritance Feature is the answer for it. But there are some limitations inside an inheritance feature, because it’s working complete different as a merge feature. The idea of an inheritance feature is to make a reuse feature flexible and possible to modify. First, some advantages of an inheritance feature: Dimension modification during placement suppress feature, modify parameters An Inheritance feature is like a flexible reuse of single or multiple features which are fully annotated and can be stored inside a write protected library Without loosing the reference to its base model But there are also a lot of disadvantages, which will block every company to use inheritance feature for a flexible reuse approach. What needs to get changed to support an inheritance feature to fulfil MBD inside a digital thread. Datum System can cause issues and conflicts, here it should use the same solution as MERGE feature Datum symbol cannot get moved to another position GD&T annotations are uncomfortable to move Colors out of the library model (base) should get transferred In case of pattern, datum system is wrong. Here each pattern instance needs his unique datum system. Creo should rename for each pattern instance the datum symbols and relations to corresponding GD&T tolerances. Like Merge is doing. A Datum sysmbol is unique Inheritance should support a pattern ISO GPS conform by using correct Datums PTC need to modify inheritance feature to work the same way as a merge feature. Without those requested changes, a reuse of feature in a flexible way is not possible. Merge is no solution here to support flexible inheritance features for an automated and controled reuse process.

Increasing the number of decimal places displayed for attributesAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.The organization where I work is in the manufacturing industry.In the organization I am responsible for the CAD and PDM system administration.I support about 800 Creo View users (and 300 Creo Parametric users). 2. What product and version are you currently running?We are currently working with Creo View 8.1.0.0 (and Creo Parametric 7.0.10.0).3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.In the attribute display, the number of decimal places is currently limited to 6.It should be possible to increase this limit.If it goes according to our requirements to at least 8 decimal places.4. What is the use case for your organization?Since we mainly have parts made of steel, the corresponding density of 0.00000785 (= 7.85e-06) kg/mm³ is defined in the Creo Parametric start model.Thus, in Creo Parametric the mass property parameter PRO_MP_DENSITY has the value 7.850000e-06: In the Creo View visualization, however, the attribute has a rounded value of 0.000008: But we would need the exact value in Creo View as well!5. What business value would your suggestion represent for your organization?Our reviewers in the department for article and drawing approval use various Creo View attributes for plausibility checks.However, since the values are only displayed rounded to 6 decimal places by default, calculation errors occur from time to time as a result.These errors could be avoided if the exact values were displayed in the attributes or if the number of decimal places could be increased.

PACK AND GO FUNCTIONALITY IN CREO PARAMETRICAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Hello team, I am Kamlesh Joshi from GMMSPL. i am a Mechanical engineer and an Application engineer.2. What version of Creo Parametric are you currently running?Currently I am using the Creo 9.0.2.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. While doing the save a backup of the Creo assembly currently we do not have any functionality to backup the related, linked drawing. When we do back up of the current assembly, only related parts and assembly which are consumed in the current open assembly that only backup.And let us say if we want to back up the drawing of the backed up assembly then we have to find it all manually by opening each drawing then back up. so this method is very easy for 2 to 3 drawing but if we have more than 20, 50 200 drawing or more than that then it is very difficult to find out the linked drawing of the back up assembly. So if PTC Creo can gives us the option to to do the single functionality where we can do the PACK AND GO like functionality then it will be the game changing.4. What is the use case for your organization? For sharing the specific data with designer, vendor and technical partner or customer5. What business value would your suggestion represent for your organization?It will save a lot of time in the process and result in to the very less headache