Case study · Titan Makina

Engineering data reaches the ERP by rule and record, not by hand

An integration that moves product and material data from SolidWorks PDM to Netsis, lets departments work on the same data card and logs every transfer.

Before

Item masters, product trees and material data created in design were typed into Netsis by hand. The same information was written separately in R&D, production and purchasing, which took a lot of time and let records drift apart.

A typo or missing field in manual entry only surfaced in production, as the wrong material or missing information. Nobody could trace who changed a record and when.

What we built

Reading from PDMItem and technical data are read directly from SolidWorks PDM variables; the value the engineer entered is the single source.
Shared data cardR&D, production engineering and purchasing complete their own fields on the same card; who checked and approved it is recorded.
Transfer to NetsisCard and supplier data are written to Netsis by software; a value with no match in the ERP raises a warning before transfer.
Visible errorsConnection or query errors are shown on screen with the real cause; changes to critical fields are emailed to the people concerned.

After

Engineering data now goes to the ERP once, from its source and by rule. Re-typing the same information in several departments, and the inconsistencies of manual entry, are gone.

Which department a card is waiting in, who approved it and when it reached the ERP are now traceable. The integration keeps growing as part of the Titan Management System we are building with Titan Makina.

Together with Bella Binary, we are developing the Titan Management System, which will deliver the end-to-end digital transformation of our company as part of the Titan Transformation Programme.

Mehmet Fatih KonaklıR&D Manager · Titan Makina

Facing a similar problem?

Tell us how you work today; in the first call we will say plainly what can change and what you do not need.