Metadata for Long Term Preservation of Product Data Josh Lubell National Institute of Standards and Technology WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data October 20, 2010

WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 22 Long-term archival of product model data is challenging… Product lifecycle may be an order of magnitude longer than the modeling s/w lifecycle Examples: aircraft, buildings, power plants Semantic richness needed for long-term socio-technical concerns Environmental, forensic, regulatory Content information standards not a silver bullet Accuracy is critical for product quality and manufacturability Product model may contain many information types Neutral exchange standards (STEP) Proprietary formats Geometry Finite element models Multimedia

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 3 …but vitally important Manufacturing drives worker productivity more than any other major sector 3D model-based definition needed to outperform overseas competitors with lower labor costs So addressing the LTA challenges is critical

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 4 Industrial R&D in 2007 From “Manufacturing Resurgence: A Must for U.S. Prosperity.” Joel Popkin and Company. Prepared for NAM January 2010 Billions of Dollars and Percent

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 55 3D visualization example

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 6 Takeaways Communicates things a picture or collection of “paper” documents cannot Complements rather than replaces the original CAD model PMI callouts help communicating how to manufacture the part — arguably better than an annotated 2D drawing Product data can include arbitrary attachments such as notes, spreadsheets, multimedia These attachments are important and need to be managed and monitored, even if CAD and CAM systems do not understand their data formats

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 77 Addressing the challenges Metadata is key Essential for information retrieval Essential for an Open Archival Information System (OAIS) Questions Where do we get engineering-specific metadata for product model LTA? Can library metadata XML standards help? Metadata sources from the product data world?

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 88 OAIS Information Package

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 999 What is Descriptive Information? As defined in OAIS: “The set of information provided to Data Management to support the finding, ordering, and retrieving of information holdings by Consumers.” Why do we need it? It’s where much of the domain-specific metadata resides Currently implemented metadata standards are too generic to meet the needs of engineers. OAIS is (necessarily) vague about DM

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 10 Examples of product data- specific DI Design stage (conceptual, development, production) Whether a model includes PMI annotations conforming to ASME/ISO standards High-level assembly information

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 11 Metadata sources

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 12 Library standards: a closer look METS (Metadata Encoding Transmission Standard) For Packaging Information Widely implemented Customizable via profile mechanism Product data packaging? Dublin Core For Descriptive Information Widely implemented Embeddable in METS RDF encoding enables modularity and processing using “semantic” tools Unlike many other library standards

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 13 And now on to product metadata… Technical Data Package (TDP) (MIL-STD-31000): Technical description of an item adequate for supporting an acquisition strategy, production, and engineering and logistics support Serves as a contract between manufacturer and customer, or supplier and manufacturer May call out models, drawings, associated lists, specifications, standards, performance requirements, quality assurance provisions, software documentation TDP metadata and contents dependent on activity, actors, lifecycle stage

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 14 TDP option selection worksheet

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 15 Continued

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 16 METS top-level elements

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 17 TDP/METS mapping METS sectionTDP metadata Descriptive Metadata ( ) TDP Level, Drawing Formats, Applicability of Standards Administrative Metadata ( ) Type and Format, CAGE Code and Document Numbers File Section ( )[locations of required TDP elements and associated lists] Structural Map ( )TDP Elements Required, Associated List

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 18 METS profile for TDP Seems straightforward Would make MIL-STD easier to implement XML tools could determine validity of a TDP TDP requirements computer-interpretable Digital repository tools could ingest, manage, and provide access to TDPs

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 19 Product Data and Lifecycle Management (PDM/PLM) Evolution Title block in drawings File management Complex software supporting Version control of product models Design modification management Engineering change management PDM/PLM systems bridge engineering data and business data

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 20 PLCS Product Life Cycle Support Framework for PLM specifications (not really a “Standard”) Becoming popular in aerospace and defense industries STEP AP239 is foundation Defines framework for creating implementable Data Exchange Specifications (DEXs) Includes Reference Data Library (RDL) formally defining controlled vocabulary for representing business-specific concepts

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 21 PLCS DEX architecture OASIS

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 22 PLCS Templates Specify how to use an AP239 subset + reference data for a particular purpose If AP239 is the foundation of PLCS, templates are the load-bearing walls Constituents – Input and reference parameters – Instantiation Path (IP) specifying which PLCS entities to instantiate and in which order – Can contain other templates

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 23 PLCS is a rich source of DI Scope covers entire product lifecycle Reference Data Library Encoded in OWL Extensible Can be combined with Dublin Core and other sources of linked data Can be processed using “semantic” tools

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 24 PLCS reference data example Identifier_type Identification_code Organization_identification_code NCAGE_codeDUNS_codeCAGE_code is-a …

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 25 Extracting DI from reference data RDL more detailed and fine-grained than needed DI coarser-grained OWL encoding facilitates DI extraction, combining with Dublin Core Challenge is determining what to extract This is where analysis of access use cases comes in 25

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 26 PLCS for LTA of PDM/PLM content LOTAR – Baselined PDM information (as-designed, as- built, as-maintained) US Navy – Ship product structure

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 27 PLCS issues Template mechanism is non-standard, unfamiliar to most software developers – Affects PLCS suitability for long-term archival Limited tool support – Affects quality of OAIS ingest Validation of instance data a challenge – Exchange specifications specified using multiple languages Reference data lacks expressiveness

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 28 A possible solution Represent templates as UML activity diagrams with added semantics (UML profile) Use UML class diagram to represent instantiated entities

October 20, 2010 WVU/NETL/NCAST Workshop on Digital Preservation of Complex Engineering Data 29 Summary Long-term archiving of product data poses unique challenges Library metadata standards can help Technical Data Package metadata can be represented using METS DI can be extracted from the PLCS reference data library PLCS has some issues as a representation for LTA of PDM/PLM content