This is not the right section to start such discussion but I could not find a better one.
There are many papers and documentation that explain that lean principles can be applied for PLM implementation and/or PLM will benefits of lean thinking during its implementation and deployment.
However, here I am interested in something slightly different.
My company has just undertaken a big cultural change to become a lean organisation. 10% of the staff is going to be green belt by the end of this year and 1% black belt. All executives and local MD will be white belt.
The company has a plm system currently a third party software that drives workflows. It is used to convert eBOM to mBOM, and it is integrated to our ERP and also PDM (which is used as a CAD storage location). We have sharepoint, a few access databases, many copies of the same document in many locations (share drives, harddrives, emails etc....). All this is used quite widely.
At first glance it seems that my company already master PLM but we do not have for instance a product configurator yet nor a project management system.
Therefore, if I promote Windchill as a PLM system the value for the company may be seen as limited as "we already have one" (short of speak, please note I have been using Windchill for over 8years and joined that new company only 3 months ago).
The more I learn about the lean principles the more I realize that Windchill is well fitted to support them. (reduce wastes, improve collaboration) and this would be an opportunity to make Windchill be used outside product development (Finance have to manage documentations, they have approval and change processes), Procurement, sales, quality etc... too
To help me build my case, I am looking at examples, papers etc... where unlike PTC's competitors such as Siemens or Autodesk, Windchill will delivery benefits well behind PLM processes and help companies to become lean. In other words I want to say that Windchill is a Knowledge (Work) Management Systems that include PLM rather than just a PLM system.
Does that make sense ?
What do you think ? Anyone from PTC who was confronted to such situation before ?
Thanks a lot
Indirectly it sure can help, I'll try to explain myself.
I have implemented Windchill (ProjectLink) integrated with a procurement system (which manages metadata, orders, items/quantities other than documents) but this business generates a huge load of documents each with its own process to be managed and handling it buy network, FTP and email makes it a mess I don't need to explain.
To improve the speed and the collaboration between my customer's buyers, the vendors, 3<sup>rd</sup> party inspection companies and 3<sup>rd</sup> party engineering company
Knowing windchill/java possibilities gives us knowledge to advise/influence the definition of the architecture of the system and data, the level of security and automation/integrations, but most importantly you have to be skeptic and critic about the entire process (lifecycle/workflows/security/time consuming activities/re-work) and you must have the owners of this process at your side, for that you have to be very gentle and measure your words to criticize his process, people tend to defend current process as their child, other people participating in the process tend to not like change.