PLM Integration & PLM Migration

ITI TranscenData's focus is mechanical CAD & PLM integration and PLM & ERP integration. We provide a suite of PLM integrations through vendor/OEM partnerships with the major PLM vendors; such as ENOVIA, PTC, and Siemens PLM.
In addition to building software integrations, ITI TranscenData PLM integration services group manages custom PLM implementations, and consulting projects, including preliminary discoveries, requirements gathering, technical architecture development, risk mitigation and deployment.

MCAD & PLM Integration
MCAD & PLM integration allows for effective change management, secure enterprise-wide data access, and team collaboration for MCAD data; enabling the realization of globally distributed product development teams.
The following topics need to be addressed as part of an MCAD/PLM Integration implementation.
- Data access & control (user, group, role based access)
- Part number generation and access
- Check-in, check-out, version control & design change notification
- MCAD model attribute synch to PLM attributes
- MCAD model renaming and "cloning"
- Formats and standard part management
- Derived output generation, storage and enterprise access
- MCAD model lifecycle management (promote, demote, sign-offs, release and revise)
- MCAD structure and E-BoM synch
- ECR/ECO integration with MCAD model change
- Customer, supplier, design partner data exchange
Legacy MCAD/PDM to PLM Migration

A fundamental aspect of the value proposition for the implementation of an MCAD & PLM integration is a high quality, efficient, and cost effective migration of the legacy PDM/MCAD data to the new PLM system.
- Quality, efficient, and cost effective PDM/MCAD to PLM data migration is a challenging objective. It requires a joint/collaborative effort to carefully assess several important trade-offs.
- Should the initial migration target be simple MCAD data management, or should the initial target be a fully integrated PLM/ECO/MCAD solution?
- How and when should the MCAD drawing *viewables* be migrated?
- Should you migrate one legacy PDM/MCAD system at a time, or do a merged big-bang migration?
- How much historical (previous revisions/versions) data should be migrated?
- How much PDM/MCAD data clean-up should be done prior to migration vs. automatically, as part of the migration?
- How long can the PDM/MCAD system be down during the production migration?
- How much automated vs. manual validation should be done to the migrated data?
More information about ITI Transcendata's PLM solutions and services on http://www.transcendata.com