PDXpert PLM software features: File management
PDXpert PLM can:
- Attach a
virtually unlimited number of files to any document,
part, change or organization
- Include the contents of your files within your free-form text search
results
-
Associate a file with either a document or part
generally, or to a specific revision of that item
- Control critical design files internally, or refer to
uncontrolled "background" external information via URL
(e.g., vendor website)
The PDXpert PLM repository for electronic data is "file format neutral".
It can contain any Windows file, including CAD files, computer source and
binary code, PDFs, text specifications, presentations, budget spreadsheets, and
graphic images.
After a file has been copied into the
library, it can be indexed for searching with the appropriate Windows
“IFilter”. Commonly-indexed file formats include Microsoft Office, Adobe PDF
and similar text formats; CAD files often rely on IFilters provided by the
CAD publisher. (For more information, see
Fast file content
searches using IFilters.)
Files may be checked out for modification, copied as
the basis for a new design, or simply viewed with the authoring software or
a
downloadable third-party viewer application.
Each file can be assigned to an
item master, or a specific revision of an item. Item master
files can be managed within the library or may be located in
an outside location (such as supplier or customer website).
Revision-level files can't be modified or deleted from the revision record
after it's
been formally released.
Any number of electronic file attachments may be associated with any item
(document, part, change). For example, it's common to attach the original
CAD file to a specific revision record, as well as a PDF for system users
who do not have access to the original CAD tool.
Library files are maintained separately from the database tables, which
increases performance while significantly reducing the risk
of file loss due to operating system, hardware, or database
errors. Files are assigned unique aliases on check-in,
eliminating naming conflicts.
Users view copies of the checked-in file, while the original file remains
securely in the library.
