I have a question; suppose you have the "save_objects changed_and_specified" and you save the assembly.
Do all its constituent parts also get saved? Or just the ones that the system thinks have changed?
I have a question; suppose you have the "save_objects changed_and_specified" and you save the assembly.
Do all its constituent parts also get saved? Or just the ones that the system thinks have changed?
If it's a parameter that is supplied/controlled in Windchill then that change is made before the file is opened, so Creo should not be able to know that it has been changed. Flagging everything as changed that follows an undetectable change is tricky.
One way to handle this would be to keep a full, read-only, duplicate of the entire model database and then create a 'working' version and check both entire structures against each other to see if there is any change. This seems like a lot of overhead.
The other is to include in various routines the ability to set a 'changed' flag, so that logic can be applied to tell purposeful changes, initiated by the user from automated changes that result from evaluating the model logic. That is, if another user opens the same model and gets the same results, even if the model is different is there any reason to say that it has changed?
Suppose the change is that it automatically updates to the current date, so that it is always changed, every time it is opened. Is it worth while to check that into Windchill every time?
But the fact is that Creo 2 was able to detect this change, and Creo 3 does not. Somewhat off-topic, but I feel that when comparing the "response times of Windchill-interaction" between Creo 2 and Creo 3, the former wins... One of my explanations is that Creo 3 seems to know more about "out of date" objects than Creo 2 did (you have this "Notification Center" in its status that tells the user that they're not using the latest version of the model).
I maintain that keeping track of the model's "parameter table" and comparing the last stored to what's been generated after the file is retrieved and regenerated does not seem like a lot of "overhead".
In conclusion: I appreciate your arguments - I think they're insightful and discussions with you about implementation details are interesting. I do wish someone from PTC would pipe-in. Let's see what the support call brings...
In my previous job, we did an extensive research on this during the design of a Global Windchill System to support around ~8K user base.
Here is the summary of what we found
Are you looking to get both EPM and WTDocuments?
For EPMDocument / CAD Documents
- Name, Number - EPMDocumentMaster table
- VERSIONIDA2VERSIONINFO, ITERATIONIDA2ITERATIONINFO from EPMDocument table.
- File size from applicationdata table
Link
- EPMDocument table's ida3masterreference = EPMDocumentmaster's ida2a2
- holdertocontent table's ida3a5 = EPMDocument table's ida2a2
- holdertocontent table's ida3b5 = applicationdata's ida2a2
For WTDocuments/Non Cad documents
- Replace EPMDocument with WTDocument, EPMDocumentMaster with WTDocumentMaster
- For non cad documents, you can get the filename from applicationData table.
We are planning to integrate Windchill system with Teamcenter Enterprise. As per PTC Sales need to buy Windchill external licenses for each user to integrate this systems, which is not feasible at this moment due to project budget limitation.
I am looking for possible ways or scenario of integration in which we don't need to buy the licenses.
Any suggestion will be more helpful.
Thanks,
Devidas
I appreciate all the responses.
For those with a similar error in the future: I had to roll-back my machine to my latest working state. No solution here fixed my problem..
Good luck,
Ammar
For those with a similar problem in the future.. Solution was:
Enter in command prompt "hostname", and make sure the server in D:\ptc\creo_view_adapters\sw_setup\adapter.pvi and the worker administration configuration host have the same value as the one returned by the command prompt.
This value is not necessarily the Windchill URL (part in bold) XYZ.com\Windchill\app... It was the computer name...
Good luck,
Ammar
The active window + the ones that the system thinks have changed.
Which way are you trying to push/pull information? PTC Navigate licenses can be purchased in an "Active Daily User" license model that allows the licenses to be shared among many different users (but only one unique user per 24 hour period per license.) These licenses also allow you to use ThingWorx to connect to other systems in order to present combined data to the end user in a single interface. Might be worth at least looking at.
Binesh,
How long ago was your previous job?
Another consideration on your database vendor of choice should be the risk of receiving an "unfavourable" Oracle licensing audit. We have just recently had the "benefit" of a compliance audit (of our circa£50K estate of Oracle) and we were presented with a bill of £300K to pay within 30 days or face sanction !!!
It took us about a 4 man weeks of work (and numerous conference calls) to gather enough evidence to get them to accept that we were working within the terms of the OLSA and for them to finally withdraw the claim. I was worried at one point that my company was going to roll over and have to pay the bill, but we managed to fend them off eventually.
Needless to say, I have successfully migrated my TEST Windchill System to MS SQL Server and our PROD System will be switched in the coming month or so - the performance looks like it will not be impacted. This, along with re-archtecting my remote DR System to use Veeam Replication rather than Application level replication means that I will have totally eradicated Oracle from the company by the summer.
There is no way that I will ever be a customer of Oracle again.
Ben
I'm not a developer, but I believe the custom PN wizard validator route was pretty in depth and few weeks of work. In our case this also implements several other customizations so cannot easily be extracted standalone. I'm happy to share the functional spec, if interested? We have 8 validators in total (see below), which are reasonably generic in nature. Frankly speaking, I think PTC should have made half of them out of the box.
I would also like validate that CAD models are not promoted before any dependents, not just assembly dependents. A change of mindset and working practice is required first as bottom up approval is completely at odds with top down CAD model strategies.
Catching issues in the workflow is easier, but you are responding to a problem rather preventing a problem from ever occurring.
Open to information trading
Hi Tom,
Thanks for reply. I am not sure how much PTC Navigate will help in this integration but will try to check more details.
we have developed one internal tool (standalone application) which is used to link teamcenter items (Like WTPart in windchill) to other PDM system objects. Also this application allows to sync attributes, perform basic PDM operations (Check-out, check-in, Revise, Promote,...etc) from Teamcenter to PDM system and vice versa. As only limited set of people will use this application to link objects. Other users will use the related systems to search that object data.
Our overall objective is to reduce user effort to update data in 2 systems and synchronization of data will happen in background by integration app.
Regards,
Devidas
Imagine to have the BOM of a production line that is located in multiple manufacturing sites....
We want to add information like the sparepart number, sparepart location that is specific to a single manufacturing site to an existing released WTpart within the BOM of the production line - and we do not want to have the need to checkout / revise the WTpart to add this information.
What would be the best approach to do that?
do you have simpler documentation to use rehost utility as a trick to silently installa windchill ?
Hi
what is your Windchill version
before 10.2, there's the ERP Material business object that allow that. But if I remember, need to create each time a BOM View specific to the Plant (even if the BOMs are the same in different plant ...)
PTC has reviewed this in 10.2 m30
with a new Enterprise Data business object. It is a versionnable object that can be set up to handle attributes/documents for a specific BOM view or plant
And the big new compare to old ERPMaterila, is that we can create a specific Plant Data without creating a specific BOM view
regards
Hi Gregory Thanks for your reply - We are on 11.0 M010. I found the Enterprise Data Object in Type Manager.
Do you know how / where to setup the ink between the BOM object and the Enterprise Data Object?
Thanks,
Stephan
In windchill 11 parts link search is integrated with the advanced search.
Please have a look at the documentation:
Regards,
Riccardo