Using PDXpert PLM software with an MRP system

PDXpert product lifecycle management software is designed to import your design data from "upstream" applications such as CAD, as well as export your approved product data to "downstream" manufacturing applications like MRP/ERP and support applications like CRM and field service.

In this application note, we'll outline the general strategy for moving released part and bill of materials (BOM) data from the PDXpert PLM system to your manufacturing software application.

PDXpert facilities for exporting data to MRP and other systems

PDXpert is built on a relational database containing data attributes. These data are contained in a row/column format which is then mapped to real-world object representations of parts, documents, change forms and related entities (BOMs, suppliers, approvers, file attachments, etc.). The relational database design efficiently contains the data, but is not particularly easy to manipulate.

For transferring data outside the database, PDXpert represents objects using XML, which is extracted from the database using the internal part, document and change object model definitions. The XML dataset is defined by the PLMX specification (www.plmx.org), which is a PLM-oriented data definition. You can use the PDXpert Report/Export Wizard to export PLMX files, which can contain item attributes as well as file attachments.

As with any XML file, PDXpert's PLMX files may be reformatted into other useful file formats by applying an XML transformation file ("XSLT"). PDXpert conveniently contains a Data Transformations collection that contains XSLT code that can be applied using the Report/Export Wizard. In a single operation, you can export PLM database objects in text-based file formats such as XML, Excel XLS(X), comma-delimited CSV, tab-delimited text, and Access database tables.

Downstream ERP/MRP systems (from QuickBooks, SAGE and Epicor up to Oracle/SAP, and even cloud-based systems like NetSuite) will typically have an import facility. Some systems can accept all PLM data in a single file, while others may require separate imports for item master records, BOM relationships, and approved supplier part relationships. The PDXpert XSLT maps the PLM system's internal representation of this data to your specific manufacturing system.

Exporting parts, BOMs and approved suppliers to MRP

Preparing for export

You have substantial flexibility in determining the point at which your released product data is transformed from PDXpert's PLMX format to your MRP system's format:

• Transform the PLMX data within PDXpert using a Data Transformation collection member, which exports it in a format that's compatible with your MRP import
• Export the PLMX file and transform it using your MRP's import tools
• Export the PLMX file and transform it using intermediary transformation tools

PDXpert has predefined Data Transformations that may be used with your MRP import utility. Alternatively, a Data Transformation can be designed that precisely matches the column/row requirements of the MRP import tool.

Exporting your released data

PDXpert has a built-in facility called the Report/Export Wizard. With a few clicks, the Wizard lets you specify the required data transformation, accepts the items to be reformatted and exported, and creates the file in the selected location.

Using your exported data

Upon release of an Engineering Change Notice (or your equivalent implementing change form), the change workflow can specify that an email notification be sent to the person responsible for importing new information into the MRP system. The person runs the MRP import utility to obtain the released PLM part and BOM data.

Alternatively, the changed data can be exported from PDXpert into a shared folder, and the MRP system can poll the directory for changed files.

In either case, the PDXpert export / MRP import only needs to occur when a change form workflow has been completed.

System initialization and data migration

While product data typically flows from the PLM system into the MRP, there's one significant counter-flow: using existing MRP part, bill of materials and supplier information to initialize the PLM database. Your MRP can often export the master item list into a CSV or similar text file, which we can then import for you as starting values for your new PDXpert PLM application.

Although the source for initializing your PLM software is often production information captured in an MRP system (anything from QuickBooks to an enterprise ERP), the data source may also be a collection of Excel spreadsheet BOMs, a file server folder containing your CAD and PDF files, perhaps some Access database part records, or Word templates for engineering changes. Since this legacy data may be loosely structured, it will need to be analyzed, restructured, cleaned, and mapped to the PDXpert database schema before it's used.

After your legacy data is well-structured, the data can be imported using both database tools and XSLT tools. After this one-time activity populates your PLM system, all further data transactions represent approved incremental changes to your product definition, and will be handled as data exports from the PLM system to your production and support applications.

This application note was relevant to the PDXpert software release that was current at time of publication. Product changes since that time may affect its utility. We'd be happy to assist you in assessing the applicability of this note to your situation.