DFR PLM Integration Options

There are different options for integrating DFR with your PLM system when supporting the new part creation process. There are different variables to consider when considering the best option including:

  • Do you have more than one PLM system
  • Does your PLM system support classification data and structure
  • Do you need to see commercial data (e.g. Pricing) and technical data together
  • Do you still have legacy parts to classify e.g. new acquistions
  • Does your classification structure support all your parts
big-DFR PLM Integrations

3 Options for Integration Process

Option #1
Two Way – DFR <-> PLM

Option #2
One Way – PLM -> DFR

Option #3
One Way – DFR -> PLM

Two Way Interface

  • Allows communication both ways between the PLM System and DFR
  • Parts created in PLM System and pushed to DFR for cleansing/classification/updates
  • Once updated, parts are pushed back to PLM System – parallel workflows
  • The Push can be accomplished in multiple ways, automatically/manually

Optimal when you have a team that is dedicated to keeping the data clean and enforcing standards.  Added benefit of taking advantage of the what each piece of software does best.

(Click to enlarge image)

PLM -> DFR Interface

  • Parts are created and controlled in PLM until final approval
  • Only approved and classified parts are sent to DFR system
  • Avoids having incomplete/unclassified parts in DFR system
  • The push can be accomplished in multiple ways, automatically/manually

The common way to support PLM to DFR integration is to use the API to make this push.  Optimal if engineering is doing the new part introduction process and they don’t want to leave the PLM system BUT you want to make the data available to others in the organization who may not have access to PLM.  Useful to augment the part data in DFR with non-PLM Data (Ex. Cost, business attributes, supplier info, etc.)

(Click to enlarge)

DFR -> PLM Interface

  • Parts are created and controlled in DFR until final approval
  • Only approved and classified parts are sent to the PLM system
  • Avoids having incomplete/unclassified parts in the PLM system
  • The Push can be accomplished in multiple ways, automatically/manually

Necessary when you want to give the customer a common NPI experience when multiple PLM systems exist.  Avoids implementing NPI in every PLM system.

(Click to enlarge)

3 Ways to Enable Data Transfer for Each Option

API Transfer
Requires Development

Manual Export
No Setup Required

Scheduled Automated Export
Requires Setup

*Each option assumes PLM can support classification and your classification structure is mature – supporting most of your parts.

Have questions? Contact us

Contact Us