![]() I have created a new Virtual pdf Document within the folder in my Vault that I use to store Templates. 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. If however we create an EPDM Template to utilise a Serial Number and our existing Metadata rules we can automate this process too. A suitable comment is also added to the file to record this.Īs 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. 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. Once created the User can then 'Replace' that Virtual Document with a 'real' document at any time. In the screen shots I have created a 'virtual' PDF. vcd but on creation the user is prompted for a name and file extension which determines which DataCard to display alongside it. There is a standard function within EPDM to create a Virtual Document within the Vault. ![]() ![]() ![]() 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. 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?". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |