Posts Tagged ‘PDM’
Thursday, March 17th, 2016
Like many of the ingredients in a manufacturing organization’s computer technology alphabet soup, such as ERP, SCM, CRM, not to mention CAD, CAM, and CAE, product lifecycle management (PLM) for years has been touted as being the final frontier for integrating all manufacturing IT functions. Honestly, though, can it truly provide all that the various vendors are promising? I have asked myself that question for several years now: Is PLM a great hope or just another great and continuing hype?
It seems that every vendor defines PLM in a manner that best suits their respective existing product lines and business practices, and not always necessarily the processes of the customers they are trying to serve. Therein lies a big part of the PLM problem. PLM should address processes and not just products, especially the vendors’. Too few vendors still stress the processes they are claiming to improve over the products (and perpetual services) they are selling.
It also seems like everybody (yes, now including just about every CAD vendor big and small) has at least tried to get into the PLM act, regardless of whether they should or should not based on their development and integration capabilities or the needs of their customers. Even database giant, Oracle, has said for years that it wants to be a major PLM player, although the company has eluded that it doesn’t want to dirty its hands with traditional CAD/CAM stuff. Oracle wants to look at the bigger picture, although it has never elaborated on what that picture is.
Tuesday, October 28th, 2014
It’s almost November, so with just two months left of this year, it’s not too early to start thinking about what we’ll be covering in 2015. The calendar below reflects what we perceive as some of the most important topics today, as well as feedback from our readers and other supporters.
The main theme for each month will be covered in an extended article or series of articles so that the topic can be covered in a more comprehensive way. We’ll also be covering some of the major MCAD events throughout the year, reporting what we see and hear from vendors, partners, and attendees.
If you have any thoughts of topics you would like to see covered in 2015, feel free to contact me at firstname.lastname@example.org or 719.221.1867.
We look forward to an exciting 2015 and providing you with the MCAD content you want most for improving your design, engineering, and manufacturing processes.
Keep MCADCafe.com your source for all things MCAD. It’s going to be a great year!
Tuesday, July 1st, 2014
Editor’s Note: This is the fourth installment of a series of four evaluation articles of CAD/PDM systems for SMBs.
PTC Windchill PDM Essentials is intended to bring collaborative engineering to smaller companies for organizing and managing product content so that they can improve design reuse, broaden access to product information across roles, and ensure control over design versions and release processes.
PDM Essentials is basically a role-based, template-based, pre-configured bundle in an optimized Microsoft Windows environment.
PTC Windchill PDM Essentials is a scaled-down version of PDMLink, Windchill’s primary data management solution, allowing smaller firms to manage CAD data and product development-related Microsoft Office documents.
Windchill PDM Essentials Quick Tour Video
Friday, June 13th, 2014
Editor’s Note: This is the third installment of a series of four evaluation articles of CAD/PDM systems for SMBs.
Siemens’s Teamcenter Rapid Start is a product data management (PDM) solution that is preconfigured, yet extensible. As a preconfigured deployment option of Teamcenter, it is intended to address the most common PDM needs of SMBs. With its “simplified” installation process, Teamcenter Rapid Start applies preconfigured best practices to common engineering tasks and processes for SMBs.
In a stand-alone environment, all server and all client applications are installed on each machine. In a shared environment, server applications are installed on a single server. Each machine has network access to the server and has only the client applications installed.
The video that follows shows how to get started with Teamcenter Rapid Start PDM, and includes demos on CAD data management, document management, and process management.
Teamcenter Rapid Start
Thursday, May 29th, 2014
Editor’s Note: This is the second installment of a series of four evaluation articles of CAD/PDM systems for SMBs.
SolidWorks Enterprise PDM is one of two PDM products offered by DS SolidWorks and is a separate purchase. SolidWorks Workgroup PDM is available integrated inside of SolidWorks Premium and Professional.
Data cards are crucial elements for managing design data with EPDM because they contain metadata about the files, folders, items, and templates in the vault database. Data card information is stored centrally, so users can search and locate information about files, folders, items, and templates without needing local copies.
By adding controls such as text fields, list boxes, check boxes, and tabs, data cards are used for managing the design process.
Friday, May 16th, 2014
Editor’s Note: This is the first installment of a series of four evaluation articles of CAD/PDM systems for SMBs.
Autodesk Vault Profession is one of three levels available from the company. Also available are Vault Basic and Vault Workgroup.
Vault Professional is a standalone application providing access to vault data. Integrated add-in clients for CAD and non-CAD applications are used to manage data. When working on files managed by any vault-type system, it is important to note that copies of files that are stored in the vault are checked out. Files are never directly edited in the vault; these files are read-only until they are checked out. In effect, copies of files are checked out of the vault for editing. In a vaulting scheme, a file can be checked out only by one user at a time. Changes made to checked out files are sent back to the server when a file is checked in.
Wednesday, February 26th, 2014
As most of us know who deal with the digital design world, for many years, all of the major CAD vendors have been stressing the vital importance of managing the design and manufacturing data created using their software. Surprisingly though, even after all of the talk of imminent disaster, still relatively few design and manufacturing companies, especially SMBs, have a formal PDM system of any type in place beyond Windows Explorer and Excel.
Some of the reasons we hear for PDM not being deployed include the perceptions (and experiences) that PDM is time consuming and expensive to implement. Also, some companies are perfectly happy with a sort of homegrown approach – Windows Explorer and Excel spreadsheets. In many cases these provide legitimate reasons for not implementing a formal PDM system, but times and circumstances are changing, and reasons for not implementing PDM are becoming weaker and weaker.
While most SMBs have made the transition from 2D to 3D, we have found that many of these same companies are finally exploring how to manage the mountains of CAD and associated product development and project data with a dedicated PDM system. These companies are seeking real solutions that are more capable and scalable than handling just files and folders with Excel spreadsheets and Windows Explorer. For example, PDM systems that connect the design department to the shop floor; will connect to other systems, such as MRP; and are scalable, so the system can grow as the company grows.
Because of the interest shown by our readers in PDM, we are in the process of exploring and evaluating several options for product and project management.
Keep in mind, these evaluations will be PDM systems only. Although the line between PDM and PLM systems is blurring, we’ll focus and restrict these evaluations to PDM only.
Check out the following video that clearly delineates the differences between PDM and PLM.
Friday, January 13th, 2012
Last time, based largely on vendors’ marketing language, PLM was defined as a comprehensive system and process that integrates, interfaces, and interacts with every other IT system within an organization, including CAD, ERP, CRM, etc. While this occurs at a peer level, the PLM oversees and, to a certain extent, controls all data exchanges.
I think, however, there is a better definition and model of what PLM actually should be. Unlike many vendors’ definitions, PLM is not a peer system to other systems, such as ERP, SCM, and CRM. Rather, PLM is the intellectual property backbone of an enterprise. While the other subsystems deliver indirect cost-reducing improvements, none of them have any measurable impact on delivering top-line, revenue enhancing results and only a minor impact on lowering direct costs. The only way to positively impact top-line revenues is to develop and build innovative, higher-quality products, and PLM is the only system of the four that addresses these issues.
In this context, PLM transforms ideas to profits, capturing customer experiences, and generating ideas for new products. Along the way, the intellectual property undergoes several transformations (such as ideas to concepts, concepts-to-prototypes, prototypes-to-products, and so on) and interacts with the other systems. Ideally, a well-implemented PLM system provides a comprehensive framework that lets all the other systems and disparate groups of users to easily interact with an enterprises’ intellectual property so anyone can add value to it.
I think the revised definition and vision finally get to the heart of what a PLM was always envisioned to be, but thus far, executed and implemented by only a few PLM vendors – an intellectual property asset manager that can be used universally within an organization.
Ultimately, the success of PLM is dependent on two things. First, it is imperative that vendors communicate comprehensively and truthfully what their PLM offerings can do and integrate with, as well as what their customers can reasonably expect in terms of gains and ROI. Second, customers must educate themselves to the true needs of their organizations and how they expect PLM to fit in with the rest of their existing and future IT infrastructures. Only then will customer expectations and vendor promises meet for improving processes and resulting products through intellectual property asset management.
Can vendors pull off what PLM was truly meant to fulfill? I think so, and more and more vendors will do so, increasingly with cloud-based services that are just beginning, but should decrease implementation costs and increase productivity through being available to anyone anywhere.
Wednesday, January 11th, 2012
Like many of the ingredients in a manufacturing organization’s computer technology alphabet soup, such as ERP, SCM, CRM, not to mention CAD, CAM, and CAE, product lifecycle management (PLM) for years has been touted as being the “next big thing” and the the final frontier for integrating all manufacturing IT functions. Honestly, though, can it truly provide all that the various vendors are promising? I have asked myself that question for several years now — is PLM a great hope or just another great hype?
It seems that every vendor defines PLM in a manner that best suits their respective existing product lines and business practices, and not always necessarily the processes of the customers they are trying to serve. Therein lies a big part of the PLM problem. PLM should address processes and not just products – neither the vendors’ nor their customers’ – and too few vendors to this point have stressed the processes they are claiming to improve over the products and services they are trying to sell.
It also seems like everybody (yes, now including just about every CAD vendor big and small) is at least trying to get into the PLM act, regardless of whether they should or should not based on their development and integration capabilities or the needs of their customers. Even database giant, Oracle, says it wants to be a major PLM player, although the company has eluded that it doesn’t want to dirty its hands with traditional CAD/CAM stuff — it wants to look at the bigger picture, although it doesn’t elaborate what that picture is.
Although they are quite different in requirements, approach, implementation, and task load, I continue to see PLM and PDM (product data management) regarded practically as equals in vendors’ conference presentations and promotional advertising. Using these acronyms interchangeably only adds to the confusion that already exists in the PLM marketplace. However, it does give more vendors more opportunities to say that they “do PLM.” By definition, PDM handles only data and is a subset of PLM; whereas PLM, to many peoples’ thinking, should interface and interact with every other IT system within an organization, including ERP, CRM, etc. at a similar level as a peer system.
So, is PLM fulfilling the prophesy that the vendors have promised? That’s the question we’ll tackle in the next MCADCafe Blog.