Long term archiving (LTA) of digital product data, which are not based on technical drawings. VDA Working Group "CAD/CAM"

Transcription

1 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 1 of 47 VDA Long term archiving (LTA) of digital product data, which are not based on technical drawings Part 2: LTA Reference Process 4958 This recommendation serves to establish basic, common requirements regarding the processes, data and organization of the long-term archiving of digital product data generated during product development. It is the result of the project carried out by the VDA Long-Term Archiving project group, which is part of the VDA CAD/CAM working group. The VDA recommends its appliance. Part 1 identifies requirements relating to the long-term archiving of product data that exists in digital form only and summarizes certain legal and technical aspects. Part 1 provides the basis for the other parts of the recommendation. Part 2 describes typical application scenarios and provides recommendations for designing the processes used to prepare the data for long-term archiving, the archiving of the data itself, and the process steps required to access and reprocess the archived data. The primary goal is safeguarding the quality of the data and the documents. Part 3 defines the minimum requirements to be satisfied by the archived information regarding the information in the 3D CAD representations and product structure descriptions from the user s point of view and concerning the process definition. Part 4 provides recommendations for the verification of reliable LTA workflows and data quality as a crucial part of any LTA architecture. Work on Parts 3 ff. is currently in progress. They will be published once this work has been completed. Therefore modifications are possible. 1 st Edition from June 2005 VDA Working Group "CAD/CAM" Published by: Verband der Automobilindustrie Copyright Westendstraße 61 Copies and any other form of Postfach duplication must include a correct Frankfurt citation of the source. Telefon 069/ Telefax 069/ Internet: www@vda.de

2 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 2 of 47 Disclaimer The VDA recommendations Long-Term Archiving (LTA) of digital Product Data, which are not based on technical drawings are recommendations that are available for anyone to use. Anyone using these recommendations is responsible for ensuring that they are used correctly. The VDA recommendations give due consideration to the prevailing state-of-the-art at the time of publication. Use of the VDA recommendations does not allow a person to avoid assuming responsibility for his or her actions. In this respect, everyone acts at their own risk. The VDA and the parties involved in drawing up the VDA recommendations assume no liability whatsoever. We request that anyone encountering an error or the possibility of an incorrect interpretation when using the VDA recommendations contact the VDA immediately so that any errors can be rectified. The document is a translated version of the German edition. Therefore the German document represents the original and shall be referenced in the case of discrepancies. Due to the translation it might be possible that the English text gives place for interpretations, because terms are often grounded deep in the original language and therefore it is not possible in any case to translate them uniquely into another language.

3 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 3 of 47 Content 1 OBJECTIVE SCOPE LIST OF ABBREVIATIONS, DEFINITIONS AND NORMATIVE REFERENCES Abbreviations Definitions Normative references Terms from OAIS (ISO 14721) Role description Role Data Creator Role Preparer (Archive) Role Consumer Role Administrator Role Management Role Examination team Role Archive Role Archive GUI Role Quality agent Role Validation agent USAGE OF INTERNATIONAL STANDARDS FUNDAMENTALS AND CONCEPTS FOR LONG TERM ARCHIVING OAIS Reference model OAIS environment Build up OAIS Data package Differentiation OAIS VDA Data verification and data validation Data verification Data Validation Approach to the accomplishment of a data validation Definition core model Appliance of the core model PROCESS DESCRIPTION REFERENCE PROCESS Data Preparation...21 Detailing of Data Preparation Preserved Data Selection Initiate Quality Agent Data Verification...21

4 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 4 of Automatic creation of Validation Properties possible? Automatic Creation of Validation Properties Create Preservation Description Information (PDI) Create Descriptive Information (DI) Create Submission Information Package (SIP) Manual Creation Validation Properties Error handling for data preparation...22 Detailing Data Verification Ingest...24 Detailing Ingest Submit for Ingest Receive Data Check Quality Assurance Send Confirmation Generate Archival Information Package (AIP) Examination Content Information (CI) Error Handling for denied Submission Information Package (SIP) Receive Confirmation...25 Detailing Generate Archival Information Package (AIP) Archival Storage...27 Detailing Archival Storage AIP Transfer to Main Storage Initiate Digital Time Signature Process Set Digital Time Signature Store to Media Storage Assurance Update Descriptive Information (DI) Update Meta Data Base Confirm the Archiving Generate Confirmation Report Receive Confirmation Receive Confirmation Disaster Recovery Error Handling for Archival Storage Manual Edition of Descriptive Information (DI) Retrieval...29 Detailing Retrieval Request Retrieval Data Access Data Selection Prepare Data for Dissemination Generate Dissemination Information Package (DIP) Provide Dissemination Information Package (DIP)...29 Detailing Data Selection...30 Detailing Generate Dissemination Information Package (DIP) Data usage Optional: Remove...35

5 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 5 of 47 Detailing Optional: Remove Remove Request Initiate Remove Process Access Data Selection Removal Delete CI and PDI of AIP Error Check Removal AIP Add Removal Information to Descriptive Information Confirmation of Removal Generate Confirmation Report Receive Confirmation Report Automatic Remove Request Error Report of Removal Error handling for AIP Deletion Failures Ingest of Pre-existing Data DATA ELEMENTS AIP (Archival Information Package) OAIS Definition Copy of AIP Authentication Secret Key Automatic remove request CI (Content Information) General definition CI in native format Data General definition Analysis results Formatting and documents standards In archive format In native format In target format Process control data Quality criteria Quality rules Validation property rules DI (Descriptive Information) DIP (Dissemination Information Package) Information Access granted information Access input information Access validation information Access denied information Authentication information Check digital signature information Confirmation information Confirmation deletion Content Information...40

6 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 6 of Confirmation remove Descriptive Information error information Digital time signature Disaster recovery error information Error fix of meta information Filter information for accessible data Meta data base update information Reference information Reset archiving trigger Selection information Storage information Storage error information Target format information Technical error fixing information Trigger information Validation failure information Key data Key ring Data in native format New validation properties from archive formatted file No PDI (Preservation Description Information) General definition PDI in target format PI (Packaging Information) Report General definition Confirmation report Content error report Data preparation error report Error report Error report removal Error fixing report Integrity failure report Meta data base update report Results report System error report Validation report Verification information report Request General definition Access request Authentication Remove request Time stamp Results...44

7 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 7 of General definition Analysis results for validation properties Check for removal information Validation results Verification results Rules Access rules Automatic remove request Validation rules Secret key Select source for validation properties Signature document order SIP (Submission Information Package) General definition SIP data in archive format: Support Time stamp Validation Properties Yes...45 APPENDIX A METHODOLOGY OF PROCESS DESCRIPTION SIMPLIFIED ACTIVITY DIAGRAM DOCUMENT STRUCTURE...47

8 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 8 of 47 List of figures Figure 1: OAIS environment...13 Figure 2: Context Data object representation information Information object...14 Figure 3: OAIS functional entities...14 Figure 4: Build up of an OAIS Information package...14 Figure 5: Data verification and data validation...15 Figure 6: General approach to a validation using Validation Properties (VP) illustrated by the example of a conversion from a SIP to an AIP...16 Figure 7: Example of the validation of information...17 Figure 8: Core model and extending possibilities schematically...18 Figure 9: Appliance of the core model...19 Figure 10: Overview data flow...20 Figure 11: Data Preparation...21 Figure 12: Data Verification...23 Figure 13: Ingest...24 Figure 14: Generate AIP...26 Figure 15: Archival Storage...27 Figure 16: Retrieval...29 Figure 17: Data Selection...30 Figure 18: Generate DIP...31 Figure 19: Automatic Validation of Dissemination Information Package (DIP)...32 Figure 20: Data Verification for DIP...34 Figure 21: Optional: Remove...35 Figure 22: Data Selection Removal...37 Figure 23: Example of a simplified activity diagram...46 Figure 24: Hierarchical structure of the process description...47

9 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 9 of 47 1 Objective The part 2 of VDA 4958 Long term archiving (LTA) of digital product data, which are not based on technical drawings provides recommendations for the layout of LTA processes. Its validity is connected to the other parts of the recommendation. 2 Scope The recommendations are relevant for development and documentation processes, which are based on 3D representations (3D master models). These representations give a description of the current existing, established and the technical status quo of the 2D archiving processes, which are no longer applicable, due to technical or economical reasons for the 3D-mastermodels. The reference process description obtains to 3D CAD data within the scenarios written above. In case of the reference process implementation it is necessary to fulfil the common legal rules and recommendations of archiving, like security and backup services within the archiving system, for these digital data. The used definitions do not represent a system description. The addressed systems are only described throughout their functionality, which are relevant for and necessary to the archiving and retrieval process. 3 List of abbreviations, definitions and normative references 3.1 Abbreviations 3D three Dimensional AIC AIP Application Interpreted Construct Archival Information Package AP214 Application Protocol 214 ISO CAD CAx CI CRC DI DIP EDV EU GUI HTML ID IDEF ISO OAIS PDI PDM PI Computer Aided Design Computer Aided Technologies like CAD, CAM (Computer Aided Manufacturing), CAE (Computer Aided Engineering) or CAT (Computer Aided Testing) Content Information Cyclic Redundancy Checks Descriptive Information Dissemination Information Package Elektronische Daten Verarbeitung European Union Graphical User Interface HyperText Markup Language Identification Integration DEFinftion for function modelling International Organization for Standardization Reference Model for an Open Archiving Information System Preservation Description Information Product Data Management Package Information

10 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 10 of 47 SIP STEP TDM UML V VDA VP WORM Submission Information Package STandard for the Exchange of Product Model Data Team Data Management Unified Modelling Language Volume Verband der Automobilindustrie Validation Properties Write once read many 3.2 Definitions 3D model: is a three dimensional representation of digital data which describe a product by defining the shape of the product. Archiving: Certified processes for the writing, storing / retention and retrieval of information within the archive. Core model: Identifies the necessary minimum of the data, rules and dependencies, which ensures the interpretability (concerning functionality and features) during the archiving period. Digital engineering-signature: is a digital signature, which will be normally used to confirm of the correctness of the document. Important for the signature is the reference to the signing person. Digital time- signature: normally an automatic created digital signature, which seals a document. Important for the signature is the time stamp. Document: A document is a logical container for product defining data. A document may be associated to an item or another object and is either represented in physical (paper, microfiche) or digital form. File: A file is an atomic container of data on a computer storage medium Master model (also 3D Master): is a 3D model representation of a product and contains the detailed geometric description of the shape, but also information about e.g. mass, tolerance and further product defining data. A master model is normally used as the source for deriving further documents needed for the product description. Meta data: combine all non geometric product data Validation Properties: Predefined parameters which are used to check the validity of, for example, a geometric model or the hierarchy of a product structure after the conversion of Content Information. Validation properties examples include centre of gravity and number of assembly knots within a product structure. Version: A version represents a specific stage of design or maturity of a part, document, or geometric model. 3.3 Normative references The recommendation leans against existing standards with a high diffusion rate. ISO : Industrial automation systems and integration - Product data representation and exchange: Part 214 Application Protocol: Core data for automotive mechanical design processes ISO 14721: Space data and information transfer systems - Open archival information system - Reference model

11 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 11 of Terms from OAIS (ISO 14721) For the process description VDA references the functional model of Open Archival Information System OAIS of ISO Ensuring the greatest possible compatibility to OAIS and its terms and definitions this document refers to the detailed descriptions of the terminology used in ISO (see 5.1). A selection of fundamental terms from ISO14721 (OAIS) will be explained as following: Archival Information Package (AIP): The AIP consists of the following elements: - Content Information (CI) (archiving formatted and optionally native formatted) - Packaging Information (PI) - Preservation Description Information (PDI) (Validation Properties, context information for the Content Information) - Digital Signature Information Archival Storage : The process comprises accompanying process steps of the archival storage process steps. This includes the update of the Descriptive Information (DI) (meta data for the AIP s), the physical storage of the data as well as an examination for possible errors. Content Information (CI): includes the set of information that is the original target of preservation. Descriptive Information (DI): represents the meta data of the archiving system. The DI is the set of information, consisting primarily of Package Descriptions, which is provided to Data Management to support the finding, ordering, and retrieving by Consumers of archived information holdings. The descriptive information will be extended with the storage information (e.g. according to ISO9660). Information package : are data packages used for the communication with and within the archival system Ingest: During the Ingest process the role preparer submits the Submission Information Package (SIP) from the preparation environment into the archiving environment. Package Information (PI): is used to bind and identify the components of an Information Package. Provenance Information: Provenance describes the source of the Content Information, which has had custody of it since its origination, and its history (including processing history). Preservation Description Information (PDI): is the information which is necessary for adequate preservation of the Content Information and which can be categorized as Provenance, Reference, Fixity, and Context information. Remove: During the remove process the data will be deleted from the archival system. Data removal can be initiated either by the roles Administrator or by an automatic request generated by the archive. Retrieval: Retrieval of archived data from the archive for a consumer. The process includes a recommended access check, provides functionality for a data search to select the required data and for converting them into the desired data format: Presentation Information: is an information, which is necessary to make the information presentable for the consumer, (e.g. display presentation of a 3D CAD model) Submission Information Package (SIP): consists of the following main information objects: - Content (native formatted data) - Preservation Descriptive Information (Validation Properties) - Context information (regarding the content information) - Packaging Information:

12 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 12 of Role description The enlisted roles are part of the process description. The roles secure the assigned process steps as well as the relating functions. They can either be persons or system roles. They do not represent any system limits Role Data Creator The data creator is an organization, person, or client system, which provides the information to be preserved. This can include other archives or internal archive personnel or system components. Typical roles of type "data creator" may be. System Designers, Design Engineers, Subcontractors, Manufacturers or Test Engineers Role Preparer (Archive) The preparer (Archive) is an organization, person, or IT-system, which prepares the information to be archived This can include other archives or internal archive personnel or system components. Preparation procedures include e.g. the Generation of AIP process Role Consumer The consumer is an organization, person, or client system, which interacts with the services offered by the archive to find preserved information of interest and to access that information in detail. This can include other archives, as well as internal archive personnel or system components. Typical roles of type "consumer" may be Design Engineers, Suppliers, Manufactures, Customers, Regulatory and Certification Agencies or Quality Departments Role Administrator The Administrator is an organization or person, that is responsible for the management of the archive and daily operation. The role performs actions such as access control, monitoring and error handling. The role is not directly involved in the archiving and retrieval processes. The role may not be responsible for the administration of further external tools like quality agents, the evolved TDM, CAx, PDM or Data Exchange applications Role Management Management represents a person or department, which is responsible for the management of the automotive product. The management makes strategic decisions, e.g. Removal of data from the archive Role Examination team Represents the approving organizations or persons of a company. The approving team approves the AIP before the AIP is stored within the archive Role Archive The Archive is the archiving environment, which usually supports at least the key functions of an archiving architecture according ISO (OAIS). Key functions are administration, data management, archival storage, access control, preservation planning Role Archive GUI The Archive GUI represents a graphical user interface. The user of the archive will interact with the archive via the GUI.

13 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 13 of Role Quality agent It is recommended that the Quality Agent is a system (tool set) but it may be an organization or person which is responsible for completeness, quality and consistency of the data to be retained according to a defined list of quality criteria Role Validation agent The Validation agent is primary a system (tool set) or secondary an organization or person, which is responsible for verification of the validity of the data content. 4 Usage of international standards To fulfil the long term archiving of product data in an adequate process and data quality, the reference process description, the used data formats and the data packages are based on international standardized methods, concepts and standards (see chapter 3.3 ff. and 6). The use of international standards raises the level of acceptance for the designated community and raises the level of interoperability between systems and data formats. Furthermore the usage of standards improves the length of time the data may be kept without a loss and simplifies the definition of processes, system architecture, implementation and certification. 5 Fundamentals and concepts for long term archiving 5.1 OAIS Reference model OAIS environment The OAIS environment is derived from the interaction of four roles: producers, consumers, management and the archive itself. Figure 1: OAIS environment Within the interaction information will be exchanged, which are relevant for the archiving inside the archiving system. These information are defined as the knowledge base. Data object can be information of any kind. They exist in two ways, in a physical representation (e.g., as a paper document) or in a digital representation. During the interaction (data exchange) between the roles the representation will change. This kind of alteration is combined under the term of Representation Information. The Representation Information is an information which is necessary to convert the received information into a user understandable form (e.g., display of a 3D CAD model on a screen). An information object is only interpretable by an IT- system. The following figure clarifies the context.

14 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 14 of 47 Figure 2: Context Data object representation information Information object The interactions within the OAIS environment are explicitly described using main functions, system data and data packages. The following figure gives an overview of the elements used in OAIS. Figure 3: OAIS functional entities OAIS focuses on the five main process modules: Preservation Planning, Data Management, Ingest, Archival Storage, Access and Administration Build up OAIS Data package Within the information exchange (data to the Archive or data from the Archive to the target system) special data packages will be used. According to the relevant process the content of these data packages can differ, but the basic build up of the packages is independent from the relevant process. The following figure describes the basic build up of the information packages Figure 4: Build up of an OAIS Information package The Content Information (CI) represents the information which is the original target of preservation. The CI will be further described by the Preservation Description Information. The package may

15 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 15 of 47 change during its generation and archiving process, e.g. the data will be packed. This kind of information, and further system relevant information, like the size of the package will be combined and stored within the Package Information. The Descriptive Information represents the meta data for the Archive. Part of the Descriptive Information could be a short title and description of the archived data as well as reference information e.g. storage place within the archive Differentiation OAIS VDA OAIS provides a detailed description of dependencies and interactions of the main functionalities within the archiving architecture. The basic functionality of e.g. the module Archival Storage shall be achieved by an implementation of a current existing archiving software and hardware. Therefore the module Archival Storage is out of scope of VDA VDA extends the functionality of the archival storage module about the usage of a digital time signature. There are no recommendations regarding the definition of the archiving format or descriptions that ensures the data quality within OAIS. This will affect the definition of the minimum subset of information, which must at least be available ensuring that the data will be interpretable by a user after a retention period X. 5.2 Data verification and data validation Validation Source data Validation compares two models against each other Vol < Tolerance if TRUE validation passed Target data conversion Volume1 = x m 3 Volume1 = y m 3 Verification Check result TRUE verification failed Verification: compares model against set of rules Verification rule: ARE THERE CRACKS WITHIN THE SHAPE? Check result FALSE verification passed Figure 5: Data verification and data validation Data verification The data verification ensures the data quality of the data to be archived. Verification rules shall ensure that a data representation meets the quality requirements within defined tolerances. A verification is successful if no verification rule is violated. Only verification rules belonging to the core model (see chapter 5.3) are part of VDA Data Validation Data validation aims at the examination, whether e.g. the prepared (converted) Content Information (CI) correspond to the Content Information, which were sent to the archive. Validating can be accomplished by a direct comparison based on pre-defined Validation Properties (VP). I.e.,

16 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 16 of 47 the Validation Properties, which are created in the source system will be compared with the Validation Properties, which are created within the process based on the converted CI. If a creation of new Validation Properties is not possible out of the converted CI, the following methods can be used as a substitute: - conversion loop: data in the native data format are converted into a neutral data format and back again into the native format. Subsequently, the new Validation Properties are created out of the resulting native data from the loop and will be compared with the Validation Properties of the source data. - verification of the archived data based on a set of rules Approach to the accomplishment of a data validation 2. Transfer to Archive 1. Creation of defined VP- generated by the source system SIP Source Document AIP 5. Feedback to system 3. Creation of defined VP-generated by the target system Archive Document 4. Comparison of validation properties Figure 6: General approach to a validation using Validation Properties (VP) illustrated by the example of a conversion from a SIP to an AIP In step 1 pre-defined values for the examination (Validation Properties) are generated within the source system. The VP are stored in the SIP. Within step 2 the SIP is converted into an AIP during the transfer into the archive, i.e., into the LTA data format. In step 3 the generation of new VP out of the LTA data format of the AIP takes place. A comparison of the old and new VP is now possible within step 4. In a further step 5 the result of validation (feedback information) is made available. If the data validation is not successful the Producer or Preparer may have to improve the data quality on demand. The following illustration shows an example, how to proceed the validation of the Validation Property V=1m³ of a 3D CAD model. A more detailed description of the elements used in Figure 7 follows in chapter 7.

17 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 17 of 47 Mapping CI CATIA- FILE, include Props. V=1M 3 S I P Generated for Validation PDI Fixitiy: Source Val. Props: V=1M 3 Conversion CI STEP File, include Props. V=1.001M 3 Generated for Validation Fixitiy: Target Val. Props: V=1.001M 3 A I P PDI Provenance: Source Val. Props -> V=1M 3 Provenance: Result: Rejection/ Acceptance inf. DI DI Archive Admin.data Part Name, ID,.. Archive Admin.data Part Name, ID, Digital signature for AIP. Validation of: SIP/ CI <-> AIP CI, by using Val. Props. Result: between Val. Props., incl. Rejection/ Acceptance information new entry Figure 7: Example of the validation of information The Validation Property V with its value 1m³ is defined within the producing system. This value is part of the Content Information of the SIP and is written into the PDI during data preparation. Within the Ingest process the SIP is converted into an AIP. Due to the conversion processes the value of the VP within the Content Information of the AIP can slightly differ from the original value (here: V=1,001m³). For validating purposes the Validation Property is newly generated out of the converted Content Information. This has the new value V=1,001m³ either. The value is stored within the PDI as fixity information. The original value of the Validation Property is additionally stored as provenance information within the PDI of the AIP. A comparison of the original and new Validation Property is now possible. The result of the investigation is also stored within the PDI of the AIP as provenance information. Thus the results are available for a later Retrieval process. 5.3 Definition core model The core model identifies the necessary minimum of data, which is needed to preserve the interpretability of the designed model (concerning functionality and characteristics) during the retention period. The core model consists of defined data elements, the representations of the model and the requirements regarding the data quality 1, which the data elements shall accomplish. The use of a core model does not exclude the archiving of additional information or a redundant storage in an alternative format. These alternative formats can offer additional functionalities regarding, e.g., preservation of additional knowledge about the designed model or concerning a support of interoperability between the used systems. Nevertheless it should be taken into account that these additional information are exposed to an increased risk of becoming useless during the 1 The definition of data quality can base on e.g. following documents: - VDA4955: Extent and quality of CAD/CAM-data - SASIG - Product Data Quality (PDQ) Guidelines for the Global Automotive Industry, which are currently submitted to the ISO as New Work Item Proposal (NWIP). They contain definitions of rules regarding data quality (geometry). - EN of the AECMA-STAN LOTAR project describes a set of rules through the Core Model for 3D Explicit Geometry Data, which is based on EXPRESS rules.

18 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 18 of 47 retention period, since it does not have to correspond to the quality requirements of the LTA as, e.g., a representation in a standardized LTA conform data format. The extension of the archive packages concerning additional information must be specified in the agreements, which are made between the archive organization and its customer (Preparer, potential consumer). The following illustration shows one possibility to extend the core model of a single geometrical part with additional information and formats. Content Information e.g. profile of a single part within the standard tolerances Extension of formats Extension of information Core Model z.b. Advanced B-REP acc. to AIC 514 ISO10303 Archived STEP-File, contains created geometry definition and history Archived CATIA Source-File AIP Archived Vismock-Up JT-File: Tesselated Geometry Figure 8: Core model and extending possibilities schematically The actual content of the core model is a geometrical model, represented by, e.g., an Advanced B- Rep model converted according to ISO (AIC514). In this case additional content of the archive package could be a construction history, the proprietary CAD-file (CATIA source file) and/or a JT-file with the tessellated representation of the CAD geometry 5.4 Appliance of the core model Within the data preparation process the data, which are to be archived, are prepared by the Preparer. Due to the conversion of the data into the LTA conform data representation it is in most cases not possible and often also not necessary (economically) to retain the entire spectrum of functionalities and intentions of the models. The Preparer shall prepare the data in a way that the fundamental functions remain, which are necessary, e.g., for the homologation of an assembly. It is ensured by the definition of the core model defining the relevant data extent for the LTA (see VDA4958-3). The core model is represented first by data in the native format, which are converted into the LTA data format within the Ingest process. The examination of the correct conversion takes place via a data validation.

19 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 19 of 47 Producer Content Information (Native Model) Represented by SIP (Native Format) Other Content Information (not retained in the archive) Content Information relevant for retention Represented by Represented by Consumer LTA relevant Design Content DIP (Native Format) Converter Controls Core Model Controls Converter AIP (3DModel in LTA Format, e.g. STEP AP 214) Archive System Ingest Retrieval t Figure 9: Appliance of the core model The applied neutral AIP data format should at least provide a level of stability preventing fundamental changes of the archived data across the retention period. Due to the long retention periods it can be possible that an archive data format will no longer be supported. This leads to the fact, that it could be necessary to convert the original data format into a new data format within the retention period. The use of standardized and revealed data representations however can provide protection against multiple iterated conversions. Within the Retrieval process the archive data is converted into a further representation (DIP). This representation depends on the kind of the Retrieval. If an inspection of the data is sufficient, it is possible to use a Viewer Tool. Another case could be the import of the data into a current/future CAD system. For this purpose the data must be converted into the proprietary (native) data format of the target system. The conversion steps are controlled by the core model and the Validation Properties.

20 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 20 of 47 6 Process description reference process In the following the LTA reference process is described according to the methodology and illustration in Appendix A. Figure 10: Overview data flow The process step "overview data flow" is organized along the life cycle of the data to be archived. For this the role "Producer" has to create the Content Information. Afterwards, the role "Preparer (archive) has to prepare the created Content Information for archiving during the Data Preparation process. Afterwards the resulting Submission Information Package (SIP) will be sent during an Ingest process to the Archive System. Within the Archival Storage process the SIP will be converted into an Archival Information Package (AIP). This includes the conversion of native formatted product data into the archive format as well as the signing of the data with a digital time signature. The process Archival Storage contains the accompanying steps of the data archiving. For reuse or viewing, the data Consumer has the ability to retrieve the archived data. The archiving system provides in addition the optional Remove Process step. The Ingest process for pre existing data describes the automatic process of conversion and storage of an already existing archive (and data) into the recommended archive format. The phases 'Data Generation' and 'Data Usage' and enclosing Process steps are out of VDA-LZA. The phases and the process steps are only integrated for process modelling reasons.

21 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 21 of Data Preparation Figure 11: Data Preparation The data to be archived will be prepared by the Preparer. This includes a defined automated data verification, performed e.g. by the role Quality Agent. Data Preparation also includes the creation of Validation Properties. These process steps can be supported by the role Quality Agent too. If necessary the Preparer may perform an error handling, because only the role Preparer has the responsibility for the Content Information. Detailing of Data Preparation Preserved Data Selection The Preparer selects data for archiving within a domain depended process. The process step represents the initial trigger for the archiving process. As an example, the selection can be performed by a product structure viewer of a CAD/PDM system or by a release trigger information coming from the Data Creator. The selected e.g. CAD or Meta information defines the Content Information (CI) of the future SIP Initiate Quality Agent The process is necessary due to special requirements of long term archiving. The Content Information must meet with the recommended data quality criteria, ensuring the readability and interpretation of the archived data by future systems. The process step is under the responsibility of the role Preparer Data Verification The role Quality Agent performs a data verification. The data verification includes the analysis of the current data quality according to the recommended data quality demands. A verification is successful if no verification rule is violated.

22 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 22 of Automatic creation of Validation Properties possible? The Preparer has to decide, if a manual or automatic creation of Validation Properties is performed Automatic Creation of Validation Properties The Preparer (Archive) initiates the source system to generate Validation Properties automatically. The Validation Properties are used later on for validation within the process step "INGEST - Generate AIP". Possible Validation Properties are: - Validation Properties for 3D CAD Data, e.g. weight, centre of gravity. - Validation Properties for meta data information, e.g. Hash code It is recommended that Validation Properties shall be extracted from the Content Information directly. Alternatively Validation Properties can be generated manually and saved within the Preservation Description Information (PDI) Create Preservation Description Information (PDI) The Preparer (Archive) creates the Preservation Description Information (PDI). The PDI is the information which is necessary for adequate preservation of the Content Information and which can be categorized as Provenance, Reference, Fixity, and Context information. As an addition for VDA4958, the Producer shall integrate Validation Properties information into the PDI to ensure the existence of Validation Properties for later automatic validation processes Create Descriptive Information (DI) The Preparer (Archive) creates a set of Descriptive Information (DI) which includes archive meta data meeting the archives requirements. The Descriptive Information includes a reference to the data verification results report Create Submission Information Package (SIP) The Preparer creates a SIP by combining the DI, PDI and CI into one package, supported by the system. The SIP contains also Packaging Information (PI). The PI is that information which, either actually or logically, binds, identifies and relates the CI and PDI. The SIP will be transferred to the archive. The formats of the packages are defined in a submission agreement between the Preparer and the archiving organization. After the preparation of the Information Package the source data may get the status read only, so that changes yield into a new version of the data Manual Creation Validation Properties The Preparer may have the possibility to create a set of predefined Validation Properties manually, in the case that the producing system is not able to calculate the needed Validation Properties. The manual creation of Validation Properties must be documented within the archiving process for reasons of traceability. This includes the basis data for the Validation Properties and the expected results Error handling for data preparation In case of defective Content Information the Producer is responsible for the analysis and error handling for the Data Preparation process.

23 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 23 of 47 Detailing Data Verification Figure 12: Data Verification The role Quality Agent performs a data verification. The data verification includes the analysis of the current data quality according to the recommended data quality demands. A verification is successful if no verification rule is violated Load Set of Data Quality Rules The Quality Agent loads the set of data quality rules relevant for the Content Information e.g. 3D CAD model Verifying Content Information (CI) The Quality Agent verifies the Content Information against the relevant set of data quality rules Generate Verification Information Report The Quality Agent generates a verification information report which contains the verification results Verification o.k.? The Preparer (Archive) must decide whether the result of the verification corresponds to the recommended data quality rules. In the case of a positive decision the Data Preparation process is continued. In the case of a negative decision the Preparer (Archive) must again accomplish the Data Preparation process. This can lead to the fact that e.g. 3D CAD models must be revised or a further analysis concerning the data quality has to be conducted. The Preparer should come to the decision if necessary in consultation of the Producer.

24 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 24 of Ingest Figure 13: Ingest During the Ingest process the role Preparer submits the Submission Information Package (SIP) from the preparation environment into the archiving environment. The archive receives the data packages and checks if the SIP contains data of the recommended format and then generates the Archival Information Package (AIP). Detailing Ingest Submit for Ingest The Preparer initiates the submission of the SIP from the working environment to the archive Receive Data The archive receives the SIP. The SIP shall be kept within the archives working environment for further processing during the Ingest process, due to validation reasons Check Quality Assurance The process step checks the quality of the ingested data. This includes the successful transfer of the SIP to the staging area. For digital submissions, these mechanisms might include Cyclic Redundancy Checks (CRCs), or Checksums associated with each data file, or the use of system log files to record and identify any file transfer, or checking for media read/write errors. In addition to OAIS recommendations, the function checks the types of data formats used and the existence of PDI within the received SIP. The exchanged data and its representations must be stipulated in the submission agreement between the Archive and the Producer. Stipulations may cover aspects such as: - CAD data formats and Model files - PDM data formats such as STEP.

25 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 25 of Send Confirmation The Archive creates a report of the successful receiving of the SIP into the archives working environment Generate Archival Information Package (AIP) The Archive performs the generation of an Archival Information Package (AIP) automatically. This includes the conversion of the Content Information from the submitted native format into the archiving format, the validation of the converted data and generation of any additional Descriptive Information (the meta data for the Content Information) Examination Content Information (CI) This process step is optional and synchronizes with the Producer's digital engineering signature process, such that the examination team will check the Content Information. After the check the archive proceeds with the process. In exceptional cases that the Content Information does not pass the check, it has to be adapted within another Data Generation process. The process step Data Generation has to be restarted again Error Handling for denied Submission Information Package (SIP) Within this process the Preparer has to perform an error handling procedure in the case of incomplete transition of the SIP. This includes that the process step Data Preparation has to be done again regarding the stipulation made between the Data Creator, the Preparer and the Archive Receive Confirmation The Preparer receives the confirmation which includes the information about the SIP s successful ingestion. Detailing Generate Archival Information Package (AIP)

26 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 26 of 47 Figure 14: Generate AIP The archive performs the generation of an Archival Information Package (AIP) automatically. This includes the conversion of the Content Information from the submitted native format into the archiving format, the validation of the converted data and generation of any additional Descriptive Information (the meta data for the Content Information) Check Current Format The Archive checks and has to decide if the current data format of the SIP Content Information belongs to the agreed data formats. Possible data formats can be : - CAD / Meta information in native data formats - SIP in neutral data formats. Based on the analysed SIP format, the archive initiates either the conversion of the native formatted content information into the archive format or the automatic validation of the SIP into the neutral data format Convert Content Information (CI) The archives converts the native formatted Content Information into the recommended neutral archive format. The conversion will be supported by preservation planning Automatic Validation of SIP The archive (or the validation agent) performs an automatic validation process. Aim of this process is to check if the converted content information accords with the original model representation. The validation will be done by the comparison of defined validation properties Provide Validation Report The archive provides a validation report Validation ok? The archive has to verify if the validation was performed according predefined rules supported from preservation planning. If the validation was correct, the archive will perform the generation of the archive Information package. In cases of occurring failures the archive creates an error report, which is related to the validation Generate Package The Archive will generate the Information Package (IP) by adding Content Information and Preservation Descriptive Information into one package. The addition of Packaging Information finishes the generation of the Information Package Error Handling for Generate AIP In cases of erroneous generation of Information packages the Preparer is responsible for the error handling.

27 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 27 of Archival Storage Figure 15: Archival Storage The process comprises accompanying process steps of the archival storage process steps. This includes the update of the Descriptive Information (DI) (meta data for the AIP s), the physical storage of the data as well as an examination for possible errors. Each company should meet the general recommendations for an archive system and its security. These general recommendations are out of scope. Process Steps #4, #5, #7 and #12 are out of scope of VDA They are only shown for completeness. Detailing Archival Storage AIP Transfer to Main Storage The Archive transfers the AIP from the working environment to the physical storage environment and generates the Administrators trigger information for the generation of a digital time signature Initiate Digital Time Signature Process The Administrator initiates the digital time signature process Set Digital Time Signature The Archive sets a digital (time) signature according to the applicable EU-digital signature law. This assures the data integrity, readability and exchangeability during the retention period, and may be used as evidence when identifying the provenance of the information Store to Media The Archive stores the AIP physically onto a medium according to meet the requirements of long term archiving and the availability of the stored data.

28 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 28 of Storage Assurance The storage assurance function validates the successful transfer of the AIP to the staging area. For digital submissions, these mechanisms might include Cyclic Redundancy Checks (CRCs) or checksums associated with each data file, or the use of system log files to record and identify any file transfer or media read/write errors Update Descriptive Information (DI) The Archive updates the set of descriptive information regarding the storage assurance and digital time signature information Update Meta Data Base The Archive generates a new entry within the archives meta data base. The new entry contains the descriptive information plus the reference information, which defines the storage location Confirm the Archiving The archive confirms the archiving process after the update of the meta data base Generate Confirmation Report The Archive generates a confirmation report which includes the feedback information Receive Confirmation The Administrator receives the archival confirmation which includes the information about the AIPs successful storage Receive Confirmation Optional the Preparer receives the archival confirmation, which includes the information about the AIPs successful storage Disaster Recovery The archive duplicates the AIP and stores the duplicate in separately Error Handling for Archival Storage Within this process the Administrator is responsible for the error fixing procedures in case of incorrect storage of archiving information packages, update of meta data base or preparation for disaster recovery Manual Edition of Descriptive Information (DI) The Administrator must have the ability to edit and attach several descriptions to the AIPs. The additional Descriptive Information could be, for example, the end of production date for a product - this is not known at the time the data is stored. The changes must be marked and be traceable.

29 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 29 of Retrieval Figure 16: Retrieval The process includes a recommended access check, provides functionality for a data search to select the required data and the generation of a Dissemination Information Package (DIP). The generation of the DIP should meet the requirements of the data receiver (Consumer/ Administrator). Detailing Retrieval Request Retrieval Data The role Consumer/ Administrator initiates a retrieval request for a data package. The request shall contain all information needed for the successful retrieval process i.e. selection of requested data Access The Archive centrally supervises the access rights for each role. Access has to be documented Data Selection The Archive provides the functions to search for the requested data. Simultaneously the user s access rights are checked Prepare Data for Dissemination The Archive prepares the data for the retrieval, which includes checks of the validity of digital time signatures and the provision of copies of the AIP for dissemination Generate Dissemination Information Package (DIP) The archive generates the Dissemination Information Package (DIP), which is derived from one or more AIPs. The DIP generation includes any conversion of Content Information into the required data format and validates the converted data Provide Dissemination Information Package (DIP) The Archive transfers the DIP from archive environment to consumer's working environment.

30 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 30 of 47 Detailing Data Selection Figure 17: Data Selection The Archive provides the functions to search for the requested data. Simultaneously the user s access rights are checked Check for References This process step checks if the data has references to other archived data packages. In cases of positive results, i.e. the data is referenced or references another data package, the references are read out Perform Filter for Data Collection The Archive performs a filter function for the requested data depending on the consumers innocuousness rating Readout of DI The Archive has to read out the descriptive information for the requested data. In cases of complete request information (e.g. exact part number, product structure information) the archive just has to interpret the descriptive information for that part. In cases of only partly know request information by the consumer, the archive has to readout the descriptive information of all e.g. parts which belongs to that request information Provide Collection The Archive provides the list of stored elements which belong to the request information and which accord to the access rights of the consumer Provide list of possible target formats for data The Archive provides the list of possible target formats for data.

31 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 31 of Select Data The consumer / administrator has to select that kind of information from archives provided list, which is of interest Receive Selection The Archive receives the data selection of the consumer / administrator. Detailing Generate Dissemination Information Package (DIP) Figure 18: Generate DIP The Archive generates the Dissemination Information Package (DIP), which is derived from one or more AIPs. The DIP generation includes any conversion of Content Information into the required data format and validates the converted data Analyze Content Information (CI) The Archive analyses the content information within the AIP Convert Content Information to target format The Archive performs a data conversion of Content Information from archive format into the target format Automatic Validation of Dissemination Information Package (DIP) The Archive performs an automatic validation process. Aim of this process is to check if the converted content information accords with the origin (archived) model representation. The validation will be done by the comparison of defined validation properties, i.e. validation properties generated by the origin (archive) system and validation properties newly generated within this process step Receive Validation Failure Report The administrator receives the validation failure report.

32 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 32 of Data Verification for Dissemination Information Packages (DIP) The Archive (or the system role quality agent) performs a data verification. The data verification includes the analysis of the current data quality according to the recommended data quality demands. A verification is successful if no verification rule is violated Convert PDI into target format Convert PDI into target format Generate Package The archive will generate the Information Package (IP) by adding content information and preservation descriptive information into one package. The addition of packaging information finishes the generation of the information package. Detailing Automatic Validation of Dissemination Information Package (DIP) Figure 19: Automatic Validation of Dissemination Information Package (DIP) The Archive performs an automatic validation process. Aim of this process is to check if the converted content information accords with the origin (archived) model representation. The validation will be done by the comparison of defined validation properties, i.e. validation properties generated by the origin (archive) system and validation properties newly generated within this process step Analyze Data for Validation Properties for Retrieval The Archive analyzes the current data for the existence of validation properties which should either be either stored within the Content Information and/or the Preservation Description Information Are Val. Props. within CI? The Archive checks if validation properties are stored within the Content Information Select Validation Properties from Content Information

33 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 33 of 47 The Archive has to select validation properties within the Content Information. If no Validation Properties are found within the Content Information, the following process step will be conducted: Select Validation Properties from PDI The Archive has to readout the validation properties from the PDI in case of missing PDI in the Content Information Calculate new Validation Properties from Content Information The validation agent calculates new validation properties from the analyzed contend information. The calculation of validation properties is predefined and have to be stored within the archive Start Automatic Validation for DIP The Validation Agent performs the validation whereas the model representation of the stored and the converted model will be checked based on Validation Property values Validation o.k.? The Archive has to verify if the validation was performed according predefined rules supported from preservation planning. If the validation was correct, the archive will perform the generation of the archive Information package. In cases of occurring failures the archive creates a validation failure report Generate Validation Failure Report The validation agent generates a validation failure report, which will be provided to the administrator Receive Validation Failure Report The Administrator receives the validation failure report. Detailing Data Verification for Dissemination Information Packages (DIP)

34 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 34 of 47 Figure 20: Data Verification for DIP The Archive (or the system role Quality Agent) performs a data verification. The data verification includes the analysis of the current data quality according to the recommended data quality demands. A verification is successful if no verification rule is violated Load Set of Data Quality Rules The Quality agent loads the set of data quality rules relevant for the Content Information e.g. 3D CAD model Verifying Content Information The Quality Agent verifies the Content Information against the relevant set of data quality rules Generate Verification Information Report The Archive generates a verification information report which contains the verification results Data Verification for DIP ok? The Administrator has to decide if the verification analysis results bears up against the recommended data quality criteria. In case of a positive decision the data verification process will be continued. In case of negative results the Administrator has to restart the data verification process Error Handling for Data Verification The Administrator has to perform, if possible, an error handling for data verification process. 6.5 Data usage The process step Data Usage includes the import of the content information and the preservation descriptive information out of the DIP into the (future) target system (viewer,...). The process step is out of scope for VDA

35 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 35 of Optional: Remove Figure 21: Optional: Remove Data removal can be initiated either by the roles Administrator or by an automatic request generated by the archive. The removal can be performed in two ways: - deletion of relevant data or - outsourcing of data, for example into a (technical) museum, which does not meet the requirements of a long term archive. The process includes access control functionality for security reasons and data selection functionality for manual selection. The Content Information of the AIP will be deleted from the archive, but the deletion information remains within the archive's meta data. The remove process checks afterwards the data is correctly deleted and provides a status report. Because data may be stored on permanent media, each company has to decide if a removal process of data be implemented. The process steps #5 'delete CI and PDI of AIP' and #6 'error check removal AIP' are integrated for process modelling (completeness) reasons. Detailing Optional: Remove Remove Request The management should decide on the length of retention periods and removal requirements. If data is declared as removable, the management initiates a remove request for the archive Initiate Remove Process The administrator has to initiate the remove process for defined information after getting the managements notification of the removal or an automatic remove request generated by the archive.

36 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 36 of Access The Archive centrally supervises the access rights for each role. Access has to be documented Data Selection Removal The Archive provides functions to search for the requested data Delete CI and PDI of AIP The Archive deletes the Content and Preservation Information from the physical storage. It is recommended that the AIP s Descriptive Information will remain within the archives meta data base and will be updated with the deletion information of that AIP Error Check Removal AIP The Archive checks the complete deletion of Content and Preservation Description Information from the archives physical storage Add Removal Information to Descriptive Information The Archive logs the deletion of the Content Information and Preservation Description Information and updates its meta data base. The update can contain the following entries: - Deletion of which AIP - Deletion date and time - Who initiated the deletion Confirmation of Removal The Archive confirms the complete deletion of the AIP and the update of its meta data base Generate Confirmation Report The Archive generates a confirmation report which includes the feedback information for the administrator about the removal procedures Receive Confirmation Report The Administrator receives the removal confirmation report Automatic Remove Request The Archive may automatically generate a remove request. The request is based on domain dependent requirements, defined by the Management. This can include expired archiving periods for documents e.g. 50 years. After this archiving period the data could be deleted Error Report of Removal In cases of partial deletion of AIP information, the Archive generates an error report for the Administrator Error handling for AIP Deletion Failures The Administrator has to perform an error handling procedure in cases of partial deletion of AIP s.

37 VDA Recommendation 4958 Part 2, 1 st Edition, June 2005 Page 37 of 47 Detailing Data Selection Removal Figure 22: Data Selection Removal Check for References This process step checks if the removal data has references to other archived data packages. In cases of positive results, the removal process has to be stopped. References from the data to be removed yielding to other information packages will be deleted together with the removal information packages Readout of DI The Archive has to read out the descriptive information for the requested data. In cases of complete request information (e.g. exact part number, product structure information) the archive has just to interpret the descriptive information for that part. In cases of only partly known request information by the consumer, the archive has to readout the descriptive information of all e.g. parts which belongs to that request information Provide Collection The Archive provides the list of stored elements which belongs to the request information and which accords to the access rights of the consumer Select Data The Administrator has to select that kind of information from archives provided list, which is of interest Receive Selection The Archive receives the data selection of the Administrator Check for Remove Confirmation The Archive requests a safety confirmation for the deletion of the Content Information Confirm the Removal The Administrator confirms the removal of the AIP within the archive.