An Approach to Accessing Product Data Across System and Software Revisions', Advanced Engineering Informatics, Vol

Citation for published version: Ball, A, Ding, L & Patel, M 2008, 'An approach to accessing product data across system and software revisions', Advanced Engineering Informatics, vol. 22, no. 2, pp. 222-235. https://doi.org/10.1016/j.aei.2007.10.003 DOI: 10.1016/j.aei.2007.10.003 Publication date: 2008 Document Version Peer reviewed version Link to publication NOTICE: this is the author’s version of a work that was accepted for publication in Advanced Engineering Informatics. Changes resulting from the publishing process, such as peer review, editing, corrections, structural formatting, and other quality control mechanisms may not be reflected in this document. Changes may have been made to this work since it was submitted for publication. A definitive version was subsequently published in Advanced Engineering Informatics, vol 22, issue 2, 2008, DOI 10.1016/j.aei.2007.10.003 University of Bath Alternative formats If you require this document in an alternative format, please contact: [email protected] General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. Take down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. Download date: 26. Sep. 2021 An Approach to Accessing Product Data across System and Software Revisions Alexander Ball1, Lian Ding2, and Manjula Patel1 1UKOLN, University of Bath, Bath, UK 2Department of Mechanical Engineering, University of Bath, Bath, UK 3rd October 2007 Abstract Long-term users of engineering product data are hampered by the ephemeral nature of CAD file formats and the applications that work with them. STEP, the Standard for the Exchange of Product Model Data (ISO 10303), promises to help with meeting this challenge, but is not without problems of its own. We present a complementary solution based on the use of lightweight file formats to preserve specific aspects of the product data, in conjunction with a registry of relevant representation information as defined by the Open Archival Information System Reference Model (ISO 14721). This registry is used to iden- tify suitable destination file formats for different purposes, and provides a resource to aid in the recovery of information from these formats in the future. 1 Introduction One of the major problems facing long-term users of engineering data is a lack of compatibility between software systems, specifically between competing systems and between different generations of the same system. This can partly be explained by market forces, and the consequent tactics used by vendors to encourage customer loyalty, and partly by genuine conceptual differences between systems. In conse- quence, data created using a particular piece of software is in danger of becoming inaccessible to its creators once that piece of software is retired or replaced as part of ongoing modernization. Several possible solutions to this problem present themselves. One is investment in specialist migration tools that can convert files between competing file formats. Another is to develop a standard exchange format; this is the eventual aim of STEP [1]. The problem with both of these solutions is that the results of the conversions can be unpredictable in quality — or else rather costly — and may involve a certain degree of data loss. A third solution is to develop emulators or virtual machines that simulate the native application; however, without the ability to extract the data into the replacement application the scope for re-using the data remains severely limited, due to a lack of interoperability with newer systems or a lack of designer expertise in the old application. The problem of access to data across software and system revisions is therefore serious, and it is unlikely that a wholly satisfactory solution will be forthcoming 1 Preprint of: A Ball, L Ding, M Patel (2008). ‘An approach to accessing product data across system and software revisions.’ Advanced Engineering Informatics 22:2. 222–235. DOI: 10.1016/j.aei.2007.10.003. in the near future. Nevertheless, it is the contention of this paper that the meta- problem — how to determine the best possible course of action in a given set of circumstances — is soluble. Given a registry of information relating to the interpre- tation of data files, it would be possible to interrogate this registry to look up the characteristics of various file formats, and to assess the benefits and drawbacks of any available migration/emulation options. The paper begins with a review of the advantages and disadvantages of STEP as an exchange and preservation format (section 3), and then identifies some candi- date lightweight representations for inclusion in an exchange or preservation strat- egy (section 4). The concept of representation information is introduced in section 5, along with an example of gathering representation information and a demonstration of its use as a decision-making resource via automated tools. 2 Challenges for current PLM practice Product Lifecycle Management (PLM) aims to provide a shared platform for effectively capturing, representing, organizing, retrieving and reusing product-related lifecycle information across companies, and to support the integration of the existing software systems, including CAD/CAM/CAE and ERP/CRM/SCM. Currently, the main challenge for PLM is information sharing and exchange, for the following reasons: • The scope of PLM includes not only data held in a highly structured form (e.g. geometric models, databases of one IT solution or another), but also information stored in less structured or formal ways (e.g. text documents), and even the tacit knowledge of employees (e.g. design rationale and lessons learned). It is the long term objective of PLM to represent and organize all this information and knowledge in digital format, and to make it traceable and retrievable throughout the product lifetime, but currently there is still no effective solution. • Several commercial application systems have been developed and rapidly en- hanced to support different phases of the product lifecycle. For a PLM system to be successful, it must integrate these advanced application systems, and be able to incorporate newly developed applications into existing systems. To date, however, most PLM systems’ integrative capabilities are limited to specific transactions. One of the reasons for this is the multiplicity of document and proprietary format types that need to be handled. • Product life can be in the order of decades. This leads to two problems. Firstly, challenges of traceability and retrieval of information and knowledge during the product lifecycle need to be met such that files in older versions are ac- cessed by the latest/future application tools. Secondly, during the product life, especially in a collaborative environment, changes occur many times across different situations and contexts. These changes further affect product content, metadata and configurations in files of various and varying format. In order to handle this evolution effectively throughout the whole product life, strategies are needed for updating, reporting and merging these changes on different se- mantic levels. 2 Preprint of: A Ball, L Ding, M Patel (2008). ‘An approach to accessing product data across system and software revisions.’ Advanced Engineering Informatics 22:2. 222–235. DOI: 10.1016/j.aei.2007.10.003. • With the trend towards globalization, PLM needs to support a collaborative environment where information and knowledge is transmitted between geo- graphically distributed applications and users [2–4]. Conventional representations such as CAD models are not optimized for such environments. From the above discussion, it can be seen that conventional representations/file formats are unable to meet the requirements of PLM; new representations — indeed the whole future direction of file formats — need to be explored. 3 Standard for the Exchange of Product Model Data 3.1 STEP as a preservation and access tool STEP (STandard for the Exchange of Product Model Data) is an international standard addressing the representation and exchange of product data [1]. Over the last two decades, STEP has been expanded from the product design phase to incorporate later life-cycle phases, such as maintenance and repair, and extended to cover aerospace, automotive, electrical, electronic, and other industries. In its initial con- ception, STEP focused on information exchange in the phases of product design and machining, producing Application Protocols (AP) such as AP203 (Configuration con- trolled 3D designs of mechanical parts and assemblies), AP204 (Mechanical design using boundary representation), AP214 (Core data for automotive mechanical design processes), and AP224 (Mechanical product definition for process plans using machining features) [5–8]. Although these parts have been widely applied in industry and the academic community — for example, AP203 delivers CAD data in a neutral format that is readable by most CAD systems — according to Pratt, Anderson and Ranger [9] the initial STEP parts have three potential problems for CAD model exchange: 1) the original designer’s intent (e.g. concerning features and constraints) may be lost or misunderstood; 2)

Load more