PitCon
For product development, companies generally use a CAD program for construction design and a PDM system for the documentation of that process. The collaboration between these diverse systems however, does not always run smoothly, almost guaranteeing an aggrieved collaboration between different organizational divisions.
Our solution - PitCon:
In comparison to the numerous interfaces offered on the market that generally only connect two systems with each other, PitCon (PITERION Innovative Connector) represents a connector solution that contains numerous out of the box interfaces. Using a socket connection, a bi-directional synchronization facility is created that enables fluent processing. In addition, the client is able to introduce different systems because of the Multi-CAD / Multi-PDM architecture. Data consistency can be assured and significantly improved using PitCon.
Your Benefit:
- PitCon enables smooth synchronization of PDM and CAD data through its simple, yet well thought out architecture
- In combination with PITERION’s Integrated Workspace (SelectBest), the design and development process reaches a pinnacle of efficiency. Working with PDM and CAD systems is improved through the integrated user interface. Cost saving potentials are very high.
- PitCon supports the Multi-CAD environment with its high-performance and exceedingly efficient data transfer. Data exchange between the PDM client server and CAD applications takes place via a standardized XML format.
- Protects your IT assets through Multi-CAD / Multi-PDM architecture and the possibility of interconnecting two applications via the flexible socket connection running on different computers.The user can for example, connect his PDM application which is running on a conventional notebook with Windows 32bit, to a CAD application which is installed on powerful 65bit Linux hardware.
- Users can share a CAD and CAE working environment. This offers an enormous cost savings potential.
- Reusability: PitCon connectors were developed as highly scaleable right from the start so that they could be used again in a new system landscape after a system changeover.
|