Windchill Ideas

In a state of the art PLM system you want to keep the data quality as high as possible. You enfore the users to fill out required attributes, to follow special formatting rules etc. But it is common that values which got entered for a source object are not any longer valid for a copy of it. And even for a new revision of the same object some attributes might not be valid anymore. Windchill should support such a configuration OOTB by preference seetings which specifies Attributes to be reset on "Save As" = IBA1, IBA2, Master IBA4, not sure about MBA3 - modeled but would be superb to support all kinds of attributes Attributes to be reset on "Revise" = IBA1, IBA2 - in my opinion it would be sufficient to support just IBAs Attribute Reset value on "Save As" = Default, Remove Attribute Reset value on "Revise" = Default, Remove Default will set the Default defined in the type manager Remove will remove the value after revise/copy and will enforce new data entry again for required attributes ... View more

Components of Creo Parametric assemblies are represented in Windchill by CAD usage links which have attribute quantity.unit set to each. In some cases it is useful to have another quanitiy.unit, for example meter (for bars, rails, ...). It would be nice if we could to set designated parameters in Creo components, which are mapped in Windchill to quantity.amount and quantity.unit of CAD usage link. At the moment, such a mapping is not recognized by Windchill. It would also be helpful if these attributes are then mapped to the corresponding attributes of the part usage link through the build of WTParts. Otherwise, the BOM of the WTPart must be corrected manually by deleting and reinserting such a component. Then, this BOM component is no longer associative to the CAD model, and always needs to be updated manually. No one wants to have this behavior. The attached document explains the desired technique with some screen shots. A similar behavor is already implemented for find number and line number as IBAs of CAD usage link, which are then mapped to attributes of the corresponding part usage link via preferences build.find.number.attribute and build.line.number.attribute. [Zemsky, Jeff: PTC Live Global: BOM and Configuration Management Best Practices, 2014-11-19] ... View more

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders. Manufacturing Industry, Administrator 2. What version of Windchill are you currently running? 12.0.2 3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Currently, we cannot control the default location of Change Tasks. In the OIR, you can only specify 'Default' as the folder.id. You can specify the default location for other Change objects (Change Request and Change Notice) but if you try to do that with the Change Task... it will error and you cannot create the Change Task. 4. What is the use case for your organization? This would give us the ability to keep similar objects stored in the same folders within contexts. For example: We would like to the Change Requests, Change Notices and Change Tasks in the same sub-folder of our Products. 5. What business value would your suggestion represent for your organization? This would increase the organization of the system. It would increase the performance of the system by keeping infrequently used items in non-root folders ... View more

Enable checkbox "Publish as Positioning Assembly" for non admin users. E.g. Mechanical Engineers should also be allowed to create monolithic reps. At the moment it´s only allowed for admins (wcadmin, Site Admin, Org Admin, Product Manager). see Case: https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS141614   should only effect additional representations (not default representations)     and it should be possible to limit the currently administrative functionality (e.g. to a group of non administrator members)   ... View more

For an efficient navigation at table views (e.g. workspace, search results...), more than three sorting criteria for the table columns are needed! Please enable more than three sorting criteria in table views! At the moment it´s not part of Windchill functionality, see https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS136045 Please vote for it! Thank you. ... View more

The collector windows, e.g. for collecting affected objects, should have a "Saved Filters" icon (similar to PSB). It would be acceptable if the functionality to "Save Filters" and "Manage Filters" would remain on the PSB page only. But it is essential to have access to all saved filters from within the collector window - instead of having to edit the Default Filter every single time... ... View more

For being able to manage material in an homogeneous way in all modules of Windchill: - Soft typable, Versionnable, Searchable, Lifecycle manageable to able to manage it as any other Windchill obejct. - Should be able to Structure Material object to be able to represent Alloys or composite. - being able to define mechanical , chemical and others characteristics - Usable in Workgroupmanagers for storing CAD material files and search in in Libraries (more than one library.  not only one path like in config.pro) - usable to affect material to WTPart - usable in Reporting with Bill of material and other Windchill modules (cost, mass, material repartition, ROHS, REACH, etc ...) -searcheable to able to search WTart or CADDocument using this material -material should be searchable also in Classification search (Material have to be classifiable himself.  to be able to create a "Material Library" with classified objects) -able to see reference link to a material from a CAD or WTPart ... View more

-Ability to dynamically load Attributes or Informations from Windchill as CreoView parameters when opening a representation from a WTpart or any Viewable.      for example, WTPart attributes on a "content" linked CAD Drawing , or adding related  Change Request  information ....      Provide an API to be able to customize and add logic to retrieve and add significant parameter in creo View -when partcentric, when open Creo View from a WTpart page, load in the same creo view session all the related Doc or CADdoc (ie not only the 3Dmodel but also linked CAD drawings, WTdocs ...) -Being able to design watermarks specifically for 3D or 2D formats (for several paging format, A3, A4 , landscape, etc ....) -Being able to choose , notably for 2D formats, if the watermark have to respect the zooming ratio.(and not stay with a fix size when zooming in a drawing) The need is in a "pure Part centric"  approach, being able to Vizualize, Stamp and/or print drawings (or other documents) with WTPart informations. Even if it is a "generic" multi part drawing. Or being able to have CAD drawings without any typical part information (BOM and part numbers, line numbers for drawing baloons, version, lifecycle state, title block, validators , etc ...) and only display/stamp them "on the fly" when print or viz ... View more

Windchill is not having delete option for products. But it is present for projects. There might be some cases where user by mistake create any product in Windchill and then wants to delete that. As currently there is no option for deletion, that product remains as it is in Windchill. Loss of data present in that product will be major concern here, but if we can give some constraint to users that they need to move/purge data before deletion and should not allow then to delete it until they do this, then data loss issue also would not there. Also user should resolve all access policies related to that product before deleting it. ... View more

CS27407Regular Expression Constraint is not working for number attribute in Windchill Currently this is not supported but it is a common requirement that we need to ensure propper numbering. It is not always practical to use full autonumbering without allowing override. Therefore the number should be validated. Yes, there are workarounds like a Listener on create and rename or via a business rule prior release which is the easiest. But it would be slick to have it correct right from the beginning ... View more

For the moment it is not possible to change the display of real number ( now up to 14 significant digits) (CS36590) It would be better if you could change this to avoid for example: 14.0000000000 ... View more

Add an option to the constraints to allow you to put a suggested value list to any attribute in Windchill. This constraint must allow you to use a global enumeration as a suggested value list, and you also must have the option to create descrite constraint list without global enumeration. if you place a constraint on an attribute, you should recieve a picklist in the layout (create, edit, workspace, classification tree, ...) of which you can pick a value, but a the same time you must be able to manually alter or enter any text you like, in case the picklist does not provide you with the right text. you should call this picklist setting "must pick from picklist", so you can switch it on or off, like you had in the old Cocreate Workmanager or Model Manager interface. this kind of behaviour already exists in windchill, but it only works for link attribute in the Structure editor. This must be expanded to any other attribute, and it must work with global enumerations aswell. ... View more

It is often difficult to keep track of all the objects in a workspace. Therefore it would be useful if the objects could be shown as a structure. I am thinking of something similar like the view "As a Structure" or "As a Structure with Associated Objects". ... View more

In the Windchill Help there is: Note Conditions are not currently reflected in the end-user user interface. Therefore, even if you set up conditions in the Type and Attribute Management utility, they have no effect on the end-user user interface. Enhancements are planned to close this gap in a future Windchill release. There are 2 articles about it: CS54319 CS130750 It is absurd: PTC implemented a functionality that sometimes works and sometimes doesn't work. They suggest to do not use it and if you open cases about it they reply that it is not supported. My conditions are working fine in the user-interface but now in 10.2 I have an error in the Structure Tab. I created the case 12519853 and ptc created the spr 2263263 but now they are banning me because it is not supported. I think that ptc must close the gap immediately. ... View more

Give me the ability to delete a specific iteration of a specific revision in PDM Link. ... View more

Currently parts ,CAD documents and documents are supported in Windchill swagger. Windchill Swagger APIs should support QMS module for Windchill Quality solutions ... View more

Via a support call to PTC, I was informed that the 'The permission for Reassign task/ Work item is hardcoded in WorkItemAdminActionsValidator.java. This action is only allowed for owners and Admins. There is no way to achieve this from Policy Administrator.' Per my company's business practice, I want the people assigned to roles ‘Change Manager’ and ‘Team Leader’ to be able to reassign assignments. I don’t want to give the users in these roles to administrator privileges. It also is redundent to assign the users to descrete roles and to the 'Product Manager' role. The abitlty to re-assign is basic functionality and the permission should be controlled via the ACL. Thanks! Kathy ... View more

For many customers, documents are just as critical as engineering documents such as CAD models and drawings and require manipulation of mulitple documents at once. The only effective means of accomplishing this is to add the documents to a Windchill Workspace. Unfortunatley, this capability is not yet available and needs to be added to Windchill. Supporting documents in Workspaces would also allow authors, reviewers and approvers to collect documents from various locations in Windchill into a common collection that can be updated and modified at anytime without navigating to all the individual documents. Please vote if you'd like to see this capability in a future release of Windchill. ... View more

In Windchill 10, the State information is far out on the right of the name and revision information in all the tabs. It would be nice to display the State beside the Revision. Suggestion for localization of the Revision, beside Revision ... View more