cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

ProjectLink Automatic Scheduled Update Improvements

ProjectLink Automatic Scheduled Update Improvements

With Windchill 11, the new scheduled synchronization is intended to update a ProjectLink project's shared objects (Parts, Documents, CAD Objects, etc.), when the data changes, as I understand.

 

We would request that some Preferences should be made available, so that scheduled sync can be configured to match various business requirements. Below are three gaps, between our business requirements and standard functionality:

 

Business Requirement: We at Harman are trying to use ProjectLink to share data with our contract manufacturers. That is, we share to a Project all the BOM, AML, Part, Document, and Change Notice data, which are needed to manufacturer several Harman end items. We want to share the latest configuration of the needed manufacturing data, **and nothing more**.

 

Problem #1: Unfortunately, the scheduled sync process will automatically add undesired CAD objects and wtParts to a Project, even though those objects were not shared during the initial collector and sharing process. The undesired, automatically-shared objects contain sensitive, proprietary information, and they add clutter and confusion, in an already-complicated Project data maintenance process. According to PTC (ref tech support case C14774026), there are no controls or preferences on this, except to set Synchronize Sharing to Manual, which completely disables scheduled sync. The Preferences (under Integral Operations/ Update Project Collector and Integral Operations/ Add to Project Collector) affect only the initial share, and subsequent manual Project updates. The Scheduled Update disregards those preferences, and instead, it updates everything that is linked in any way, to the initially-shared objects! There are no preferences or controls for this behavior.

 

Problem #2: The scheduled sync and other standard functionality do not completely update Parts or Documents which were initially shared. If a Part is Revised, the new Revision will be automatically added, but the old Revision remains shared to the Project, which adds clutter and confusion. If a Document is Revised, the new Revision is not automatically added. A user must do that manually.

 

Problem #3: New objects, are not added by the Scheduled Sync function. That is, new Parts or Documents which are added to the structure of an outsource End Item; or newly complete Change Notices. Instead, a user must manually add these objects. We try to accomplish this during the CN process, but it’s error-prone and easy to miss.

1 Comment
nsamardzija
10-Marble
Status changed to: Acknowledged