XML to solve PDM and EAI issues?

The ability to migrate data between PDM (product data management) systems, access your legacy data without needing to maintain redundant applications, and open up PDM vaults to a broader range of applications and users, are just some of the benefits claimed by UK-based PDM consultancy firm, Solass, following the announcement of its new XML-based (eXtensible Mark-up Language) strategy this month. The spate of recent mergers amongst the main PDM vendors is posing problems for many end users. In some cases companies are forced to change to a new application (which can be a complex project in itself) even though they have already spent a lot of time and resources implementing the ‘old’ system. Solass reckons it has the answer though. Tony Jessop, Solass’ sales and marketing director, commented: “We’re talking with a number of major corporations who are trying to work out a future strategy for PDM, which includes access to their legacy data. “Having invested a great deal in their current systems, some of which are becoming obsolete, they’re looking to protect this investment. They want a more transparent way of working with their next generation of systems where they don’t feel so locked in.” Solass’ strategy uses the XML standard to define a non-proprietary based approach to migration and co-existence. This helps firms unlock themselves from vendors, giving more freedom in the evaluation of software and allows migration to take place in a timeframe best suited to each business. Application-specific software agents (Solass is currently developing one of these for Sherpa PDM users) augment existing product data to create a standard, compliant XML repository. Using XML conversion engines, Solass then tailors the exact format in-line with each client’s business needs – for example, the Product Data eXchange (PDX) standard or the Open Applications Group Interoperability Standard (OAGIS). These agents can then interact with the XML-aware repositories enabling the information to be used for a variety of purposes. Jessop cites two examples here: linking with the firm’s own EAI (enterprise application integration) tools as part of an overall integration strategy; or wholesale migration of data to a new target application. “We initially defined this process to ease the migration issues between PDM systems. However, we’re seeing a lot of interest in establishing XML-aware repositories of active data for specific applications. It would only be a small step to having an XML-aware, enterprise-wide repository on which any application can act,” added Jessop.