ENOVIA - PPR Hub Gateway (PGW) provides an data exchange infrastructure that is based on STEP format. This infrastructure is used for performing data exchange in STEP AP203, AP214, PDM Schema 1.1 and ENOV_DATAX Express Schema (a neutral ENOVIA VPM object model) protocols. The same infrastructure can also be used for performing migration from CDM, ENOVIAVPM, or ENOVIAPM to ENOVIA VPM.
The PGW infrastructure allows for extensive data validation and healing during export and import. The infrastructure consists of several components, each with a specialized function to perform on the exchanged data: extraction, validation, mapping and reconciliation. Activation or de-activation of these components results in object-level custom exchange definition. For instance, an administrator may define that an exchange partner receive a complete BoM (Bill of Materials) along with all attached CAD documents, while another partner receive only the BoM.
For further customization, CAA-RADE C++ Advanced Development configuration (CDC) is required to create new exchange components, for instance to receive legacy data migration.
A STEP-based import and export infrastructure that can be customized to support non-standard formats.
Ability to implement extensive data validation, data exchange rules, reconciliation and healing rules during data exchange
Ability to perform batch command import/migration and export
Ability to perform reconciliation on partial imports
Product Key Customer Benefits
Enhanced collaboration with the extended enterprise use exchange standards such as STEP AP203, AP214, and PDM Schema to exchange assembly structures along with all associated 3D design data with suppliers and partners who might be using different product data management systems.
Exchange all ENOVIA objects perform exchanges on all types of ENOVIA objects: EBOM, document, configuration and variants, change management, clash objects, etc.
Well-identified exchange procedures... four functions (components) related with a data exchange or migration process has been identified: data extraction, validation, mapping and healing (reconciliation). Separating the infrastructure into these four well-identified components provides customers with a clear data exchange procedure. PGW provides data extraction, validation and healing(reconciliation) components. Mapping components for STEP, PDM Schema, ENOVIAVPM, CDM and ENOVIAPM are delivered with the ENOVIA PPR STEP Part 21 Adapter (STH) product.
Extensive validation and control on the exchanged data allow a data exchange administrator to select the types of objects to be exchanged with a partner based on projects. Validation and rules can be set up without the use of CAA-RADE tools. During an export process, each object is extracted from the database using an extractor. The administrator can activate all extractors allowing all types of objects to be extracted, or select only certain extractors allowing for certain objects to be exchanged with the supplier. For instance, one partner may get only the product structure while another partner may get the product structures with all attached documents. The sample principle applies on the import procedure. Each object received from a supplier must be checked, merged and reconciled with the master data in the database. If an OEM wants to receive only certain objects from the suppliers, then only the components for these objects need to be activated. For instance, certain attributes such as supplier's designer name can be filtered out, while other attributes such as part price needs to be kept.
Data migration and re-use use the same infrastructure to perform data migration to ENOVIA VPM. Import mapping for STEP, PDM Schema, ENOVIAVPM, CDM and ENOVIAPM are delivered in the optional ENOVIA PPR STEP Part 21 Adapter product. CAA-RADE C++ Advanced Development configuration (CDC) can be utilized to develop a custom mapper component (.exx file) to address other formats. A step-by-step batch command mode is available for performing mass data migration to VPM. This mode provides an administrator better control of the amount of data migrated in one batch and the content of the exchanged file as it progresses from one function to another (extract, validate, map, merge, etc). A detailed step-by-step migration guide is provided.
Reconciliation on partial imports an automatic reconciliation function is provided specifically to manage the exchange of a subsection of a product structure. For example a car manufacturer subcontracts the design of a car to several suppliers, each responsible for designing different components of the car. The OEM can use the partial import function to reconcile the partial designs coming from the suppliers with the complete car structure. When partial import is performed, the newly inserted sub-assembly will inherit any relationship that the replaced sub-assembly had with the rest of the product structure.