I agree HTML5 offers so many new possibilities and efficiency improvement as well as compatibility.
Java is old tech now
I hope Windchill 11 will no longer use Java and make the most of HTML5 even for Creo View..... but that is a different topic.
Regarding DTI. I think we kind of all agree. I hope Bjorn Saup will comment and I look forward to reading his second post (pressure on, the audience is waiting lol)
Have a good day all,
Good day everyone,
Glad to see this blog is so well received. Just wanted to let you know Bjoern is on holiday and will return September 7 - he will be responding then.
Thank you for your questions; please keep them coming.
I don't succeed very well to explain the difference between file management and document management to someone how basically don't want to listen. Do you have a dominant key differentiator or a business case to make your point? What makes Windchill so special and can't be solved in SharePoint?
The way I try to explain is that you have in one environment WTDocuments, WTParts and Tasks, that they are all interconnected to each other, that they all have history, workflows, .... But that's in general too complicated, so freightening for managers.
When I try to re-educate our novice Windchill users, I mostly have a hard time to convince them not to rely on folders to structure their information. I try to make my point by saying that if people had to approach the internet via a Windows Explorer way navigating up and down in a folder structure, it wouldn't that successful as it is now.
Second, folders in Windchill are helpful for configuring acces rights. This is another requirement, not always compatible by the way end-users want to structure folders.
So DTI pictures Windchill folders in the Windows Explorer, making it difficult for me to keep users away from folders. Maybe I should install DTI without the explorer integration.
Although we have some users that use the Windows folder structure to access PDMLink, and like it, it has a major problem that I have not found a good way to deal with. It is not a complete structure of WC and only contains files/folders that are navigated too:
Does anyone know a way to work with the windows folder structure in a better way?
maybe a new idea should be created to include in the Windows Explorer DTI a Recent documents ?
So kind of like WS functionality for documents, but accessed via Windows Explorer. That could certainly help, however the other issue of the structure being duplicated for each user, is still a major show stopper.
I am afraid. I do not have a magic formula. You are right it is damn complicated.
I think there is a consensus between us all that it is first to introduce it WTpart and related documents. After that, expend it to documents not related to WTpart.
I will soon (well maybe in 12/18 months) see how successful I am with my new company.
If I could get Quality dept and their QMS (which is just a lot of files badly managed on a shared drive (they want to move to Sharepoint for version control.....) into Windchill then I will be very pride of this achievement....
remind me 18months
To me, it is about keeping as much as possible information under one roof.
I see Sharepoint as a duplication (in less powerful and I come back to this) than Windchill (even if one day a Sharepoint developer went mad at me by saying this and he said that sharepoint will eat Windchill and the like at breakfast, but he never told me how Sharepoint could handle document structure and even less CAD documents) of Windchill.
In addition Windchill as out of the box functionality that Sharepoint does not have such as
and of course the inability of Sharepoint to link documents with product structure.
I am yet to see what Sharepoint can do that Windchill can't. Therefore it is obvious to me that if it is agreed that a company should only need one document manager, then it should be Windchill.
Under one roof is only good if it is good under that roof.
When the UI of WC is so deprived of some basic functionality, I honestly wonder which is better, several softwares that do well what they do (even though there is duplication) vs. one software that really messes up some basic stuff making it harder on the users. Currently we have both in place where WC is used for several types of things in Engineering, while we also have separate software to handle other aspects of the company (Sales, Quality, EPM, Purchasing, Network Drives). This is despite WC having the "capability" of doing most of these things. As the saying goes, WC is truly a "jack of all trades..."
I indeed do not intend to have all documents in Windchill, only documents that can help engineers to develop better machines. This is a very broad definition, e.g. quality audits or assembly instructions should be part of Windchill. Supplier invoices for example aren't.
About the UI of Windchill, I see occasional users playing around and finding their way to information in Windchill remarkably well. Although other users (how are supposed to be regulars) don't. I think its more a matter of attitude then of UI, although the UI plays its role of course.
Suppose not all relevant information is under one rooftop, how are you managing access rights? And change? And most of all, how do you avoid confusion among people, may they select by themselves where to put documentation? Do you allow in the company a Windchill clan, and a SharePoint clan, and a clan that belongs nowhere?
Considerations for what they are worth.