.jpg)
.jpg)
A conversation I often have with EnterprisePDM (EDPM) Customers is one around the topic of "How do I incorporate scanned data into my Vault's metadata rules, naming conventions and Workflows?". The document in question could come from a number of sources; marked-up printouts, posted documents, material certificates or (the example I will use today) a 'Calibration Report' which is completed by hand but needs to be stored in the Vault, with a reminder for next time the Machine in question needs to be calibrated again.
There is a standard function within EPDM to create a Virtual Document within the Vault. These have a built in file extension of .vcd but on creation the user is prompted for a name and file extension which determines which DataCard to display alongside it.
In the screen shots I have created a 'virtual' PDF.
Once created the User can then 'Replace' that Virtual Document with a 'real' document at any time. When the user selects the replacement file the document is copied to the Vault location and takes on the name, metadata and lifecycle status of the Virtual Document it has replaced. A suitable comment is also added to the file to record this.
As useful as it is, the user still needs to create the Virtual Document in the correct Vault location and define a suitable name for it. If however we create an EPDM Template to utilise a Serial Number and our existing Metadata rules we can automate this process too. The following Checklist will describe the process I have used to create a Template for the creation / management of a Calibration Report; a form filled out on the shop floor then scanned in for storage with a reminder of when the next calibration is due.
When I run the Template the Virtual 'placeholder' is correctly named, stored in the correct location within the Vault and all the (searchable) Metadata assigned.
I can then simply locate the placeholder and 'replace' it with the pdf scan of the physical document.
By adding a 'Calibration Date' Variable to the DataCard I can now set up a my Search Favourites to alert me on the Calibrations required in any given time period.
The Custom Search Card shown above uses the Variable Search Control. The topic of searching in EPDM, and the flexibility of this particular type of search, is something that I will be presenting as part of my What's New / Hints and Tips presentation at our 2014 Launch events this year and something that I will be revisiting with some additional Tips in my Webcast later this month.
Thanks for stopping by. For more information about EnterprisePDM be sure to visit the product pages.
Service Pack | Release Month |
SP0 | October 2012 |
SP1 | November 2012 |
SP2 | January 2013 |
SP3 | April 2013 |
SP4 | June 2013 |
SP5 | October 2013 |
HOWZAT!!!
Our nation will soon be in mourning when the Australian cricket team claw back those coveted ashes. How can our acclaimed 11 be blown away with such ease by the Aussie bowlers? It is tempting to be critical when you see the ultra-slow-mo of the ball making a mess of the stumps or that little nick to the slips, but consider, for a moment, the speed of events. Mitchell Johnson is hurling the leather at 95 mph. A simple calc tells me that the ball travels the 22 yards from bowler's hand to the batsman in about 0.5 secs - that isn't much time to adjust your body and move the bat to ball.
I wondered what that would look like and decided to knock up a quick Motion study in SolidWorks. Since Motion uses real-world physics to calculate the movements, it is an accurate simulation of what really happens. I added an initial velocity to the ball of 95 mph at 2 degrees from the horizontal and at about the correct height. I added 'Contacts' between the ball, pitch and stumps and after a little adjustment knocked the stumps over.
I also took advantage of the new 2014 Sunlight option and picked December in Australia to get realistic lighting and the right shadow length and orientation for 4.00 pm in the afternoon.
Here is what it looks like in 'real' time. (Note this might play more slowly than in real life if you have a slow internet connection).
Not so easy is it? For those of you who blinked, here is a replay at 1/10 speed.
Of course Motion does more than knock stumps over. We can do things like trace the flight of the ball and plot the velocity as shown in the images below ...
The graph shows that the velocity increases as it leaves the bowler's hand (due to gravity) and then takes a sudden change at 0.4 secs when it hits the ground - friction causes it to slow up a little. It then takes another change at 0.5 secs when it hits the stumps before continuing at about 37 m/s.
Motion remains one of the best kept secrets in SolidWorks and is invaluable engineering tool, even if it simply proves how good the Aussie bowlers are!
by Andy Fulcher
Technical Manager
Solid Solutions Management Ltd