Choosing the Right Data Formats to Share Product Content

Transcription

1 Technology, M. Halpern, R. Knox Research Note 11 August 2003 Choosing the Right Data Formats to Share Product Content The array of open and proprietary formats for exchanging technical data for product life cycle management can be confusing. The appropriate format will depend on business requirements and extent of use across a value chain. Core Topic ERP II, Supply Chain & Manufacturing: Engineering and Manufacturing Strategies, Applications and Technologies Key Issue How will successful enterprises select, deploy and manage plant operations and engineering solutions to minimize risk and achieve optimum ROI? Strategic Planning Assumptions No common standard for product data exchange will be adopted by any industry before 2008 (0.8 probability). Although the boundaries between technical and commercial data exchange continue to blur, no single standard that embraces both types of product data will emerge before 2008 (0.9 probability). Note 1 Process Manufacturers Process manufacturers use generic formats such as HTML, XML and Microsoft formats; however, Gartner is unaware of broadly adopted standards that cater to process manufacturers' PLM needs. Despite more than 20 years of effort, no standard for product data exchange (PDE) has emerged (see "PDE Is Still an Engineering and Production Challenge"). Instead, users have a myriad of formats from which to choose, each with a different focus. Here, we summarize the status of established and emerging formats that enterprises should be aware of, and we assess their maturity. To date, Gartner is unaware of any broadly used PDE formats for process manufacturers to share recipes or related processspecific information (see Note 1). Therefore, most of the formats addressed here focus on requirements for discrete manufacturers to share data that defines products and resulting manufacturing processes. The scope here does not include standards or formats used to support commercial transactions (see "Product Content and Data Management Promises Savings"). Enterprises that need to select PDE formats should use this research to survey their most-likely options. Figure 1 summarizes the current positioning of the mostcommonly employed PDE standards. Breadth describes the scope of coverage the format addresses. Openness describes the accessibility of nomenclature, syntax and structure to a broad audience. Gartner Reproduction of this publication in any form without prior written permission is forbidden. The information contained herein has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations thereof. The reader assumes sole responsibility for the selection of these materials to achieve its intended results. The opinions expressed herein are subject to change without notice.

2 Figure 1 The Most-Relevant Formats for PDE Expansive STEP STEPML XML UPR XT SAT IGES SGML DXF Breadth Microsoft Formats JT VRML VDA Focused PDF HTML Proprietary Source: Gartner Research (July 2003) Openness Standards-Driven The descriptions that follow explain the positions of the formats in Figure 1, describe how they support PDE needs and provide advice on how enterprises can use them. DXF A proprietary format developed by Autodesk, Data Exchange Format (DXF) is used extensively to share content created in AutoCAD. It is used most frequently to exchange information captured on two-dimensional AutoCAD drawings. Its breadth encompasses geometry, dimensioning and annotation, and it generally gets high marks for reliability and quality of support. Users that have a need to import and export content from AutoCAD drawings should explore DXF. Enterprises that need to share AutoCAD information across architectural engineering, construction, discrete manufacturing, government and process manufacturing industries can all benefit from DXF. XML A subset of Standard Generalized Markup Language (SGML), Extensible Markup Language (XML) was developed by the World Wide Web Consortium (W3C) in It is a metalanguage that 11 August

3 defines other languages, as well as legal characters and rules for creating "elements" and "attributes" of XML schema or document-type definitions. XML is used for data models in many application domains, including high-technology, automotive and aerospace industries. Therefore, we include it here. However, there are probably more XML formats than industries they support. PDX, PLM XML and Standard for the Exchange of Product Model Data Markup Language (STEPml) are three notable examples of PDE mechanisms that may have longevity. The National Electronics Manufacturing Initiative (NEMI) promotes PDX as a format to exchange product data for hightechnology industries. EDS's product life cycle management (PLM) business unit has embarked on an ambitious XML adoption called PLM XML that is suitable across discrete manufacturing industries. STEPml is the XML representation of the STEP standards described below. STEPml employs the same data models for components and resources as STEP. However, STEPml substitutes XML for the data-modeling language Express, which supports STEP. STEPml holds greater promise for broad adoption than STEP, because commercial users employ XML for other applications, such as business-to-business (B2B) transactions and application integration. They are not usually aware of Express, which focuses on engineering needs. The pervasive impact of XML on PDE is likely to grow; however, efforts to adopt it for PDE have only just begun, so it will be difficult to determine which XML schema will dominate. No XML-based method of PDE will dominate across discrete and process industries before 2008 (0.9 probability). Users should track the development of XML-based schema and employ them tactically when it makes sense to do so. HTML Hypertext Markup Language (HTML), the "publishing language of the Web," is a markup language (written in SGML) that is based on a fixed set of tags which represent content in a consistent way when viewed in a browser. The tags define formats (such as lists and fonts), content categories (for example, tables and photos), links between content components and mechanisms for including other content in a target document. If new tags are needed, HTML must be revised by the W3C; unlike XML, it is not a language for creating tags. Other formats (like those of the Microsoft Office suite) can be output to HTML for viewing on the Web to communicate, but not dynamically update, product information. Its major value is in relating product information to a 11 August

4 broad community. Virtually any industry can get value from using it this way. IGES The Initial Graphics Exchange Specification (IGES) was developed by the U.S. National Bureau of Standards which is now the National Institute for Standards and Technology (NIST) in the 1980s. It is still used extensively for sharing two- and three-dimensional drawings and 3-D wireframe plus surface models for fabricated parts used in the industry. However, discrete manufacturers are most likely to use IGES. STEP has eclipsed IGES in importance. Enterprises that use IGES should be investigating migration to STEP. Companies with large legacy databases should maintain some level of IGES investment. JT JT (formerly Jupiter format) is a proprietary format for visualization owned by EDS. Discrete manufacturers use it for collaboration on product development and design reviews. Its functionality embraces many of the activities that product development organizations might consider in design reviews, such as generating cross-sectional views of three-dimensional computer-aided design (CAD) models, calculating physical properties and adding notes. Many discrete manufacturing industries use JT for conducting design reviews, sharing rationales for engineering changes, creating digital mock-ups, manufacturing process planning studies and documenting released parts for production. The Automotive Industry Action Group promotes it heavily. JT supports a broad range of CAD formats, including Dassault Systemes' CATIA; EDS PLM's Unigraphics, I-DEAS and NX; Autodesk's AutoCAD and Inventor; and the Parametric Technology Corp. (PTC) Pro/Engineer. However, it is not comprehensive in its support of nongeometric information needed for manufacturing and marketing. Discrete manufacturers, particularly in automotive and aerospace industries, should consider JT to communicate geometric design information and related annotation. Microsoft Office The primary applications in the Microsoft Office suite are a word processor, a presentation application and a spreadsheet program. Although these are not PDE applications, they are often used to capture PDE data: textual descriptions in Microsoft Word, graphical representations of products in PowerPoint and data 11 August

5 elements (such as part names and numbers) in Excel spreadsheets. Although the ubiquity and relative inexpensiveness of these tools make them useful for their stated purpose, and as precursor data development tools to full-scale PDE applications, the office products themselves have no PDE intelligence. So, users cannot validate or integrate the data in product-aware ways. In lieu of a universally adopted, inexpensive PDE standard, many companies employ the Microsoft Office formats to represent product data. It makes sense to take tactical advantage of these formats; however, manufacturers should not make them the cornerstone of a PDE strategy. They should ensure, however, that any strategic PDE project prioritizes the ability to share information using these Microsoft Office formats. PDF The Portable Document Format (PDF) was released by Adobe in 1993 as an interchange format that preserved the look and feel of source files. It has become a preferred document archiving format, because it preserves the exact presentation of the original document. It is also indexable and searchable, which is not a strength of image formats, such as Tag Image File Format (TIFF), Joint Photographers Experts Group (JPEG) and Graphic Image File (GIF). PDF does not directly encode PDE information in the data stream, although future versions with XML embedded will be capable of integrating PDE data, with the PDF rendering data. This would make PDF more powerful in supporting PDE. If a core standard were XML-based (such as STEPml) and had rendering information associated with it (such as the PDF format), PDF could become a leading standard in openness and breadth. Users in all industries should track continued PDF development, particularly PDF with integrated XML. STEP When first developed in the late 1980s, STEP went beyond previous standards with its goal of addressing full PLM. It includes a data-modeling language (Express), the data models for components and resources, the application interface for accessing the models and test suites for evaluating standards compliance. The goal of STEP is to provide a neutral, public definition of product data that is independent of any particular application and enables data sharing among many applications. Gartner is not aware of any enterprise that has been able to embrace STEP in its entirety for sharing product data in an open environment. However, enterprises have been able to adopt 11 August

6 STEP piecemeal to support specific types of data and specific projects. Enterprises working on complex projects involving mechanical or mechatronic design should explore STEP. It has been adopted most proactively by the military and NASA, as well as by enterprises serving the automotive, aerospace and defense industries. Enterprises involved with these sectors should consider STEP. SGML Developed in the 1980s, SGML is focused on document data structures. Its widest use was for the U.S. military and the Computer-Aided Acquisition and Logistics Support (CALS) program. SGML, the language from which XML is derived, is more complex and is being replaced in many areas by XML, because of XML's greater simplicity, the broader availability of XML-aware applications and the adoption of XML as a standard data exchange format. For example, the U.S. Defense Department is making the transition to XML. SGML is of decreasing importance and will be used less in the future than XML. UPR Note 2 PLM Software Concepts Object history refers to the sequences of operations used to create models of parts and products. Feature definitions refer to the grouping of CAD geometries into higher-level entities (such as holes, pockets and ribs) that engineers and manufacturing specialists can interpret directly. Design constraints refer to rules that users must follow when changing a design. Modern PLM software uses these concepts extensively to streamline the communication of product information and to enhance the ability to modify designs. Universal Product Representation (UPR) is a new proprietary format promoted by Proficiency for sharing geometric and nongeometric product information about three-dimensional computer models that describe a product. UPR is one of the few formats promoted that can capture object history, feature definitions and design constraints (see Note 2), as well as geometry. The format continues to improve, and it does a good job of communicating geometry and the most-common features and constraints. However, it is not yet exhaustive in its ability to recognize and capture the full set of features, constraints and operators important to object history that would satisfy the mainstream market. Although UPR is making progress, it will not be a mature format for the mainstream market before YE04 (0.8 probability). UPR best serves Type A (technologically adventurous) enterprises in automotive, aerospace and construction equipment industries that are willing to take risks for competitive advantage. 11 August

7 VDA Verband der Automobilindustrie (VDA) is a German standard for two- and three-dimensional CAD geometry data exchange, with a particular focus on the automotive industry. VDA has key strengths in the precision and robustness with which it supports the exchange of 2-D and 3-D geometries. However, it does not support the broad range of data needed for activities such as manufacturing planning or maintenance, repair and overhaul (MRO) necessary for complete life cycle support. Enterprises working with German automotive original equipment manufacturers (OEMs) and suppliers should be familiar with VDA. VRML Acronym Key B2B business-to-business CAD computer-aided design CALS Computer-Aided Acquisition and Logistics Support DXF Data Exchange Format ERP enterprise resource planning GIF Graphic Image File IGES Initial Graphics Exchange Specification JPEG Joint Photographers Experts Group MRO maintenance, repair and overhaul NEMI National Electronics Manufacturing Initiative NIST National Institute for Standards and Technology OEM original equipment manufacturer PDE Product data exchange PDF Portable Document Format PLM product life cycle management PTC Parametric Technology Corp. ROI return on investment SGML Standard Generalized Markup Language WC3 WorldWideWeb Consortium STEPml Standard for the Exchange of Product Model Data Markup Language TIFF Tag Image File Format UPR Universal Product Representation VDA Verband der Automobilindustrie VRML Virtual Reality Modeling Language XML Extensible Markup Language Virtual Reality Modeling Language (VRML) is an open visualization standard for capturing three-dimensional geometric content for display. Although VRML has the advantage over EDS's JT of being more open, it does not have JT's functionality for extensively supporting design review functions such as markup. VRML is used primarily to display geometric content. However, users can attach attributes to VRML models, including notes and links to product documentation. VRML is a viable candidate for enterprises across all industries that need to visualize geometric models for digital mock-up, design review and support of virtual reality software. XT XT is a proprietary format owned by EDS PLM for the exchange of geometric information created with its Parasolids modeling kernel. Enterprises use it primarily to share three-dimensional geometry. It does not have capabilities to share nongeometric information, such as feature definitions, object history or design constraints. This format has been used industrially for years and has proved reliable. Any discrete manufacturer with a need to exchange geometry with Parasolids-based CAD software, such as Unigraphics, NX, SolidEdge and SolidWorks, should consider XT. Bottom Line: Manufacturing enterprises have an array of proprietary and open-exchange standards they can use to support their product life cycle management needs. Selecting the appropriate format depends on the nature of the product data to be shared, the nature of the activity the product data must support and the types of data formats that other enterprises in the extended supply chain (including suppliers, customers, partners and competitors) are using. 11 August