Consona Corporation Logo Contact Consona  |    Call (888) 8 CONSONA

Product Data Management

The purpose of the Product Data Management (PDM) module is to maintain documents. This means that any important document (a drawing, process sheet, engineering change request, change notice, or any other document type) can be represented by a record within the PDM system. The system has predefined document classes (such as a drawing) and the user can additionally classify documents using a user-defined field "document type", which is a sub-classification of document class. This codifying of documents facilitates the search and maintenance of documents.

Product Data Management brings all vital product information under one roof (actually one central server). The actual text or image of the document is contained within an attachment; the document record contains a pointer to the attachment, which may be stored in a different area on the system or in the database as a BLOB. These documents can be any file that can be stored on the server, including CAD drawings, Visio drawings, and Word documents.

The specific revision of a document can be associated with a number of revisions of a design item, or production item, or a production item's routing, or even another document. The establishment of a revision whether on the document or item or routing) will be set by a unique number or letter. Using the INFIMACS II notes capability, an attachment can be created and then linked to a document revision. Then the document revision, from within Document Maintenance or Engineering Change Control, can be associated with an item, routing, or document. For example, drawings and specifications for an engineering item can be retrieved directly from the Engineering Item Master maintenance program. The association of an existing document can be made to a new item during the item creation process. In the same way, an association of a document with an existing item can be made during the document creation process.

The routing that is related to a production item has revisions as well. Therefore, a revision of a routing can be related to multiple revisions of a production item, which in turn can have a document revision that is associated with an item’s routing. In this way, when a routing is extracted for a work order, the revision of the item, having been specified on the work order, will not only pull the correct routing, but will also make sure that the correct drawing revision for the item and the correct document revisions associated with the manufacturing and assembly are also identified.

Managers control table and field level security by defining an organizational structure that may or may not parallel that in INFIMACS II.

Documents must be checked in and checked out, allowing complete control over the revision process. In addition, change order control can be enforced on the revision process.


  • Store and retrieve documents by revision
  • Control document revisions through change orders
  • Associate document revisions to item revisions of:
    • Engineering Items
    • Design Items
    • Other Documents
    • Engineering Change Order
    • Routings


  • Program, table, and field level security
  • One document revision can be associated with many item revisions
  • One item revision can be associated with many document revisions
  • Each document revision exists as a unique file on the server
Six Steps to a Successful ERP Implementation