Previously I discussed there were 2 common data management myths. The first was Windows Explorer is a data management system.
Before I start my second rant let’s come to an agreement that Part Number = File Name. Pure and simple. No more “Bracket” file names. Descriptions for file names is absolutely absurd. How many Brackets does your company make?
The second, and I know some of you out there are going to kick and scream and even possibly wait for me after my presentation at SolidWorks World to beat me down, is that Smart Part Numbers are indeed smart. Are you kidding me??????
2 Scenarios
Scenario 1: One of my green horn students starts at a company: This is followed by the severely under-defined orientation about the company, maybe even an even further degraded CAD standards orientation. This is if they are lucky. Now they are ready to begin modifying documents for you or even begin a new design for you. But wait, first they must read a 4000 page document on how to create part numbers. If this part is aluminum it starts with an “A” unless the forecast is partly cloudy, then it is “Alum”, so on and so forth. So not only does my scared little green horn have to overcome the company culture but now learn basically a new language for part numbers.
Scenario 2: One of my green horn students starts at a company: This is followed by the severely under-defined orientation about the company, maybe even an even further degraded CAD standards orientation. This is if they are lucky. Now they are ready to begin modifying documents for you or even begin a new design for you. You instruct them to hit a certain button (usually the Save or Ctrl+S) and viola a part number is magically created for them and a window pops up that tells them exactly what information about the file is required; i.e. Description, Material, Hardness Spec, Material Treatment like paint or anodize (otherwise known as finish), project, etc…
In the first scenario most companies will give a new employee about 60 days to comply with company policies. But they will need to anticipate part number screw ups for the next 40 years.
In the second scenario if the employee manages through the 60 – 90 day evaluation period there should be no problem with part number issues.
Let us discuss the idea of the “Smart Part Number”. As I said in my previous rant, every single designer and now I will add, the rest of the organization, has the best way to name files, organize files and for some reason they believe everyone else understands what is happening in their polka dotted world they call a brain. Smart Numbers were probably developed by marketing geniuses. they call it the “Model Mask”. Here is the problem I see. Model Masks will inevitably be require to evolve if a company is truly out to make money. Companies looking to make money will continually strive to define the next innovative product, and if we work on the concept that innovation is the implementation on a new product that enters the market adding new market value then we need to agree that more than likely that parameter has not been defined so we run into 2 situations, innovation is halt because it does not fit the model mask or it is slowed until a new model mask is generated, tested and implemented.
I am throwing out some serious terminology here like Implementation (which assumes that companies are continually refreshing employees on the standards and are continually assessing their performance with measurable matrices), innovation (defined above, but many companies are willing to run the old if it ain’t broke do not fix).
Falling back to the first installment where I discussed increasing productivity to make more money, look at the 2 scenarios discussed earlier and you tell me which one can offer instant productivity out of a green horn, learning/memorizing a 4000 page How to Create a Part Number book or just hit save, the system will tell you what other info is required.
Now how does this tie into PDM systems you ask? Well thank you for asking, I have implemented and maintained about 10 PDM systems for companies and part of my implementation is setting up the system with part number schemes that when you do a Save or Ctrl+S the data management system takes control an doles out the next available serial number. Notice I said serial number. 000000001 -9999999999 are very useful part numbers. With data management one does not have to worry about descriptive part numbers, there are other more powerful ways of finding the file you need without some complicated matrix to sort through.
The power of data management systems are that they inject steroids into your custom properties. Most of these systems resemble the Dewy Decimal System at your local library. As I said before in Scenario 2, during the save a part number is established then a pop up box indicates additional information that your company requires when creating a part number. Custom Properties are the meta data that is included in the file. It is the same exact concept behind Windows Media Player or I-tunes, when you load a CD or download a song the extra data that shows up in the player is the meta data, Song Name, Artist, Genre, etc… Notice that this is search-able in those tools. PDM should be viewed sort of like these tools. The difference is now you will have the ability to log revisions, describe the changes, and have a viewable history without the need for a designer to rename, pack and go and all the other workarounds we modelers have come up with.
Now instead of a model mask matrix you can use search tools similar to Google searching Advanced Search Features. The model mask may be a good tool to develop required fields needed before a save can be completed. Make sure the fields are descriptions of the information that will be inputted into them. Then you can create drop down lists, or fields that are linked to outside databases to ensure the information is entered correctly.
Anyhow, the purpose of this rant was to dethrone the concept of Smart Part Numbers. Much easier to instruct a person to hit the save button than to try to teach them a numbering scheme that will inevitably change or become way to confusing and cumbersome to use.
There will be more to come.
Hey Chris,
Nice article indeed. It appears that you saw a nerve that you were trying to hit in people and instead of taking precise aim, you pulled out a shot gun at near point blank range to ensure you got em’. I like it, but I have a question for you.
You mentioned in your post that “Part Number = File Name. Pure and simple”. How then do you handle part files that contain configurations? Or do you not condone the use of configurations? It seems that you are a big proponent for efficiency (as I am) and want to do things only once, or if that is not possible, to at least minimize the work as much as possible.
I do agree with your statement about “smart Part Numbers”…as there is really no such thing since any system will break eventually, even a pure sequential one as it too will eventually reach the limits of data management systems (maybe in extreme conditions but its true).
Are the tools that you use to setup your PDM systems available anywhere already, if not are you willing to share?
Thanks,
Jason
The Honda, Suzuki, Toyota, and Nissan factories use “smart part numbers”. I love them; for example, you can look at a smart part number and know exactly what the part is, no BOM required. Conversely, if you have a part in your hands, you can guess correctly it’s part number.
Devon T. Sowell
http://www.3-ddesignsolutions.com
Devon,
I do understand your comments, and I used to agree. Then I started implementing these things. It was nice, but I was not aware of the overhead it took for these systems. Money and time that in my opinion is better spent on innovative ideas that your company sells.
My questions to you: If your organization is using part numbers, how long does it take for a newbie to the company to learn your new language? Then, how often does someone have to maintain that system?
Using a sequential numbering scheme with a system that has very common and easy to use search fields requires at the most 1 month to get comfortable with. Usually you can see productivity within the first week.
Maintaining a sequesntial numbering scheme is done only when you have completely exhausted all of your numbers. Then you may indeed have to add an A to the next series of part numbers, then B, then C.
Jason,
I generally do not reccomend configurations. But in some cases it is the most productive way to complete documentation. If your company is going to use configurations that needs to be decided before implementation. I have implemented it before in different ways:
One off items = 000000000 thru 999999999
Tabbed or configured = 000000000_ thru 999999999_
In this example not configured items have a 9 digit part number. Configured files have a 9 digit part number with a _ at the end. So the base file name would be 000000001_ and the configutation # would then be 000000001_01. I recommend Design tables for this where you can set up the Configuration name to be File Name Concanated to next available tab number..
This seemed to be the best recieved method.
You also asked about the tools for my PDM System. My tool de’jour is DBWorks. I have been using it for many years, even before SolidWorks added PDMWorks Work Group and Enterprise to its packages.
I still find that the scalability and ability to work with SolidWorks features liike configurations is still 2nd to none. When reviewing PDM systems and using configurations you need to verify whether the PDM system will allow individual configuration revision management or not. If I change the length in only 1 configuration but not the other 98 should the other 98 have to go through revision approval? I will post a list that I used to work with companies to design their PDM.
Chris
Hi Chris –
I enjoyed reading your posts. Your first post mentioned vocational education. Are you teaching data management as part of curriculum?
Best Regards,
Joy Garon
RE:”My questions to you: If your organization is using part numbers, how long does it take for a newbie to the company to learn your new language? Then, how often does someone have to maintain that system?”
In my experiences, I’ve worked, as a Contractor, for Honda, Toyota, Suzuki, and Yamaha, this is not a big issue. For example Toyota; they currently maintain about 400,000 part numbers. Their system has been in place for many years and is easily learned.
Yes, sequential part numbers are easier to implement but not necessarily easier to maintain.
Devon Sowell
http://www.3-ddesignsolutions.com
Working from inside a couple of companies with semi-start numbers, I can say we spend more time maintaining the system than we ever gain from using it. One company I worked had dumb numbers; part number was never an issue at this company and no time was ever spent in maintaining it whatsoever. No learning curve, no arguments about whether this part is that category or this, no work to expand the system when new types of parts were introduced, no mis-identification issues, no multi-classification issues, not one second wasted pulling a part number from this or that category (vs just pull the next number of a single class), no specialist who “knew” which type numbers to pull, etc. In my experience, there is significant waste associated with smart numbers.
Hello Joy,
As it is right now we are using SolidWorks Explorer as our data management for the students. On of the lessons that teaches our students about the importance of good data management is I have them work on a project and allow them to name the files whatever they want. At the end of the project I explain the file namoes that must be turned in. They have to use a combination of SolidWorks and Windows Explorer to make the necessary changes. Generally ten parts, 2 sub assemblies and 1 Main assembly. They generally get the point after that.
That being said I am working to implement data management here for a couple of reasons:
1, It is easy
2. Reduce individual student file maintainence. We definitely spend toom uch time on this issue.
Hi Chris –
Will you be at SWW? If so, look me up. I’d like to talk to you about ideas for using PDM to manage student projects.
Regards,
Joy
For configurations we make the parent part a drawing number that is not one of the part numbers. That part feeds the drawing views with dimensions x,y.. All of the part family are revised together (one tabulated drawing). If a revision cannot apply to all the family, you start a new family.
In the PDM, there are data records for each configuration, but they all point to a common file name.
Please forgive me for I have just played with SW in the past. But I do have over 20 years of experience in the CAD field. I am also wondering about a company that I have consulted with that is”moving” to SW from an enterprise system that is tied to manufacturing, test, QA and integration with SAP. This company creates commercial and industrial equipment. Their assemblies are several thousand component (unique components) assemblies. I am really concerned that they are taking a huge step backwards. Espeicallly because the lack of part versioning and versioning rules in SW. Yes, data management is critical to the success of an good design organization. You do not sell product, you sell the by-product of your companies design data. The design data is your IP! Protect it. Organize it. Search it. Re-use it. You can’t really do any of these without a PDM system to protect it and organize it. You may need an PLM system to search and re-use your data..this really depends on your “PDM” systems functionality.
Anyway, I have a basic understanding of SW and file structures and configurations. All these things work well if you do not have organize and search and reuse your data. As soon as you through tabulated drawings and configurations into the picture you have just compounded the complexity of your data management. Can someone tell me how well the SW PDM programs handle these complexity? I am also interested in understanding how a company handles workflows when you have designated design group with file ownerships and designated manufacturing groups that need to work with design data? Do you allow manufacturing write access to your SW files to create flat patterns or another group to do FEA or quality group to store measurement data to compare data from recieved parts vs design parts? I see this as a huge problem. Thanks for reading.