Guest post from LiveWorx Sponsor KPIT Technologies, Robert Morrison - Manager, Products & Innovation
“The only individuals in the organization who use data in the PLM system are the ones who put it there.”WIndchill Customer PTC
How true is this quote!
PLM systems largely contain vital and expensive Engineering IP assets which are locked away behind complex systems built using old technologies. And even today, in many organizations PLM systems are perceived as ‘Engineering data management systems’ and are barely used beyond the engineering function.
The true value of a PLM system within an organization is only realized when critical product information is made available ‘just-in-time & just-in-context’ to wider areas of an organization such as manufacturing, procurement, services, support and sales.
Availability of ‘just-in-time & just-in-context’ product information from the PLM creates value with:
- Enhanced operational efficiencies
- Lowered instances of engineers being interrupted to provide product data
- Better and faster decision making
- Identification of costs associated with utilizing parts which are high cost or low inventory
- Reduced manufacturing delays due to using long lead time items with other viable alternatives
- Improved collaboration with vendors
- Providing vendors with restricted access to product specific information such as BOM’s, CAD etc
- Extended user adoption
- Historically lost ROI from PLM covered with enterprise wide PLM adoption
PTC’s Navigate, a Role and Task based application development paradigm unleashes the possibilities of making relevant product information readily accessible for different roles within the organization.
While Windchill already comes with a host of role based apps as a built-in capability, organizations can leverage the PTC Navigate and Thingworx platforms to develop customized role based navigation applications tailored to their specific needs.
From your organizations perspective, what could these specific needs be? Or What kind of role based navigate applications will expand the adoption of PLM system?
Here are my 2 cents to get you thinking…
Start Thinking Role-Based
Step 1 - Identify areas of frequent “can you get me” interactions
- Can you get me this drawing
- Can you get me the cost of this item
Step 2 - Break the interaction down to one of the two:
- Roles in the organization which infrequently need PLM data
- Purchasing, Supply Chain, Marketing
- Tasks which involve multiple systems of record
- Combined views of PLM, ERP, MES
At KPIT, we often had interactions with our clients which went on these lines,..
“We need a way to compare my Engineering and Manufacturing BOMs to identify differences between them.”
As a response to this need, KPIT has developed a BOM Comparison Application - a Role-based app built on PTC Navigate. The application compares the EBOM and MBOM from different PLM/ERP systems and highlights differences between them.
Built on the PTC Navigate platform, KPIT has also come up with a few other role based apps such as a ‘Supplier Scorecard Application’. This application prepares a supplier performance scorecard by pulling the supplier related information on various product and quality parameters from PLM & ERP systems.
‘PLM Business Connectors’ is another example of KPIT’s role-based application with which PTC Navigate Apps can now work and interact with data in non-PTC systems using KPIT’s Business Connectors. This provide the powerful capabilities of having a single portal for interacting with engineering data from multiple PLM systems.
Do you have a user story which can evolve into a role based navigation app for your organizational needs? Share it with KPIT here.
For more information on cutting-edge tools to improve business processes, register for LiveWorx 18, June 17-20, in Boston!